Content for  TR 22.859  Word version:  18.2.0

Top   Top   None   None   Next
1…   5…   5.5…   5.10…   6…   A…


1  Scopep. 7

The present document is aiming at documenting potential new use cases and service requirements to enhance 5GS for the support of Personal IoT networks (PINs), including when the PIN is connected to 5GC.

2  Referencesp. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 22.261: "Service requirements for the 5G system".
TS 22.101: "Service principles".
Christiane Attig, Nadine Rauh, Thomas Franke, & Josef F. Krems (May 2017) "System Latency Guidelines Then and Now - is Zero Latency Really Considered Necessary?
TS 22.278: "Service requirements for the Evolved Packet System (EPS); Stage 1".
TR 22.858: " Study of Enhancements for Residential 5G; Stage 1".
TS 22.115: "Service aspects; Charging and billing".
TS 22.228: "Service requirements for the IP multimedia core network subsystem".
TR 22.104: "Service requirements for cyber-physical control applications in vertical domains; Stage 1".
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2"
TS 23.558: "Architecture for enabling Edge Applications (EA)"

3  Definitions and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
direct device connection:
See definition in TS 22.261.
direct network connection:
See definition in TS 22.261.
Guest PIN Element:
Is a PIN Element that is a member of one PIN (Home PIN) and can access any other PIN, if allowed to by that PIN to communicate with the Home PIN.
IoT device:
See definition in TS 22.261.
PIN direct connection:
the connection between two PIN Elements without any 3GPP RAN or core network entity in the middle.
PIN Element:
UEs or non 3GPP devices that can communicate within a PIN.
PIN Element with Gateway Capability:
a UE PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements that use PIN direct connections.
PIN Element with Management Capability:
A PIN Element with PIN management Capability has capability to manage the PIN.
Personal IoT Network:
A configured and managed group of at least one UE and one or more PIN Elements or UEs that are (pre-)authorised to communicate with each other.
The person who owns the PIN.

3.2  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Personal IoT Network
Universal Plug and Play
Digital Living Network Alliance

4  Overviewp. 9

IoT capabilities have been designed for devices that communicate using the traditional cellular network, including battery constrained devices where it is expected that the battery should last in the order of years. Recently standards have been extended to support more vertical IoT devices for factory based, audio visual, medical, mission critical and vehicular solutions. In some contexts, e.g. factory based solutions the concept of a private network has been introduced, this has the added benefit for devices that generate very little user plane traffic (e.g. sensors etc.) the traditional cellular operator might not have to dedicate resources to them in the network and the traffic can stay within the local "factory (private network) environment". There are 2 consumer segments that have similar traffic characteristics where private networks provide an advantage, where communications are predominately within the constraints of a localized IoT network:
  1. Wearable devices;
  2. Home automation
For the purpose of this discussion these will be called "Personal IoT networks" (PINs). These types of networks are very different to commercial IoT device, they are usually less rugged, most highly battery constrained and lifespan of the battery typically a couple of days or weeks. User plane traffic typically stays with a constrained environment, around the body or in the home i.e. within the PIN. Notifications can be received on smartphones that events have occurred within the PIN.
PINs have been around for a long time using others standards however their take up / adoption rate has been low compared to the general smartphone UE.
An example of a home automation PIN can be seen in Figure 4-1 where there are a number of devices in the home that either communicate directly with the hub or indirectly via a relay to the hub. A smartphone in the 5G system can receive notifications regarding events (e.g. door opens) from the home automation PIN.
Copy of original 3GPP image for 3GPP TS 22.859, Fig. 4-1: Home automation PIN
Figure 4-1: Home automation PIN
(⇒ copy of original 3GPP image)
Wearables can use a multitude of different access technologies, battery life can in some situations be severely constrained just by the physical dimension limitations e.g. glasses frames, earbuds, blood pressure monitor, pacemaker and rings. Space is also at a premium, capabilities are limited (memory, processing power, even USIM functionality might not be available). Location requirements on wearable devices, especially those with Uu interfaces can contribute to battery drain. Earbuds / Rings are very small, even an ESIM chip takes up valuable space, battery consumption and adds weight to the device. Figure 4-2 shows two wearable networks, one where all the devices communicate via the smartphone and another where glasses act as a relay for smart earbuds.
Copy of original 3GPP image for 3GPP TS 22.859, Fig. 4-2: Wearable PINs
Figure 4-2: Wearable PINs
(⇒ copy of original 3GPP image)
In summary, it is considered beneficial for 3GPP specification to address 5G system support of different use cases for PINs.

Up   Top   ToC