8.2 Common Information Elements
23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS
8.2.1 General
This clause provides descriptions for Information Elements which are commonly used in several procedures.
8.2.2 PIN Profile
8.2.2.1 PIN Profile in a PIN
PIN profile includes information about the static data needed for configuration for the Personal IoT networks.
Table 8.2.2.1-1: PIN Profile
Parameter Name |
Parameter Description |
PIN Server |
PEMC |
PEGC |
PIN ID |
The identifier of the PIN |
Y |
Y |
Y |
PIN Description |
Human-readable description of the PIN, for example, the company name, location or the type of service. |
Y |
Y |
Y |
Duration |
Specifies the time period of how long the PIN can be active |
Y |
Y |
Y |
Maximum number of PIN elements |
Maximum number of PIN elements allowed to join the PIN |
Y |
Y |
N |
PIN service |
List of service that a PIN can provide, including the PINE service or the service that can provided by application client on PINE: > PIN service Provider Identifier > PIN service type > PIN service Feature |
Y |
Y |
N |
PEMC list |
The list of identifiers of the PIN elements which can be allowed to take the role as PEMC (e.g.: PIN client ID, UE GPSI etc.,) and also it contains whether the role is primary or secondary > PIN Element ID > Role |
Y |
Y |
Y |
PEGC ID list |
The list of identifiers of the PIN elements which can be allowed to take the role as PEGC (e.g.: PIN client ID, UE GPSI etc.,) > PIN Element ID |
Y |
Y |
Y |
PIN Server ID |
The identifier of the PIN server that serves the PIN |
N |
Y |
Y |
PIN server Endpoint |
Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the PIN server. |
N |
Y |
Y |
PIN Elements List |
List of PIN elements which can be allowed to join the PIN > PIN element ID |
Y |
Y |
Y |
Editor’s Note: Other IEs for the purpose of enabling multiple PEMC/PEGC scenarios, e.g. procedure for role change, are FFS.
8.2.2.2 Dynamic profile information of a PIN
Dynamic profile information of a PIN contains the PIN dynamic data needed for management of the Personal IoT networks.
Table 8.2.2.2-1 describes the list of parameters that are classified as dynamic profile information and which are maintained at the PIN server, PEMC and PEGC. PIN dynamic profile information maintained at these entities are updated based on the events occurring in the PIN. Below are some of the events (not exhaustive):
– PINE joins or leaves the PIN;
– Role of PEMC or PEGC changes;
– When the services offered by the PIN changes;
– When a PINE updates the services it offers;
– When a PINE joins or leaves the PIN;
Table 8.2.2.2-1: Dynamic profile information of a PIN
Parameter Name |
Parameter Description |
PIN Server |
PEMC |
PEGC |
PIN ID |
The identifier of the PIN |
Y |
Y |
Y |
PIN Description |
Human-readable description of the PIN, for example, the company name, location or the type of service. |
Y |
Y |
Y |
Services offered |
List of services currently offered by the PIN |
Y |
Y |
N |
PEMC list |
The list of identifiers of the PIN elements which are currently serving as PEMC (e.g.: PIN client ID, UE GPSI etc.,) and whether the PEMC is authorized as primary PEMC or secondary PEMC. |
Y |
Y |
Y |
> PIN Element ID |
Y |
Y |
Y |
|
> PEMC role |
Y |
Y |
Y |
|
> Endpoint information of each PEMC (e.g. URI, FQDN, IP address) used to communicate with the PEMC. |
Y |
Y |
Y |
|
> Duration or time period this PIN element allowed to being PEMC |
||||
PEGC list |
The list of identifiers of the PIN elements which are currently serving as PEGC (e.g.: PIN client ID, UE GPSI etc.,) |
Y |
Y |
Y |
> PIN Element ID |
Y |
Y |
Y |
|
> Endpoint information of each PEGC (e.g. URI, FQDN, IP address) used to communicate with the PEGC. |
Y |
Y |
Y |
|
> Duration or time period this PIN element allowed to being PEGC |
Y |
Y |
Y |
|
> KPIs supported by this PEGC (e.g., maximum number of assigned PIN elements) |
Y |
Y |
Y |
|
> List of PIN elements being served by PEGC and their connectivity information |
||||
PIN Server Details |
The details of the PIN server that serves the PIN |
|||
> Identifier of the PIN server |
N |
Y |
Y |
|
> Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the PIN server. |
N |
Y |
Y |
|
PIN Elements List |
List of PIN elements currently registered/joined the PIN and their details |
|||
> PIN Element ID |
Y |
Y |
Y |
|
> Services offered by the the PIN element |
Y |
Y |
N |
|
> Reachability information of the PIN element |
Y |
Y |
Y |
|
> List of application clients for this PIN element: |
||||
>> Minimum KPIs required by each application client to operate effectively within the PIN (e.g., PIN bandwidth, PIN request rate, PIN response time) |
Y |
Y |
Y |
|
>> Operational schedules of each application client (e.g., time windows) |
Y |
Y |
Y |
|
> Identifier of the default PEGC authorized to service this PIN element. The PIN element will use this PEGC as the primary PEGC to relay PIN communications. Location and/or schedule information for the default PEGC may also be included such that the default PEGC may be selected by the PIN element based on its current location and proximity to the default PEGC and/or the availability schedule of the default PEGC. |
Y |
Y |
Y |
|
> Identifiers of backup PEGCs authorized to service this PIN element. The list is in prioritized order (the first PEGC listed will serve as the first backup PEGC). If the default PEGC is not available, the PIN element will use this prioritized list of PEGCs to relay PIN communications. |
Y |
Y |
Y |
Editor’s Note: Other PIN Profile IEs for the purpose of enabling multi PEMC/PEGC scenarios, e.g. procedure for role change, are FFS.
8.2.2.3 PIN client profile
Table 8.2.2.3-1 describes the list of information elements that needs to be shared by the PIN element when requesting to join the PIN.
Table 8.2.2.3-1: PIN client profile
Parameter Name |
Status |
Parameter Description |
PIN ID |
M |
The identifier of the PIN to which the PIN element wants to join |
UE identifier |
O |
PIN Element or UE identifier |
PIN client ID |
M |
The unique identity of the PIN client within PIN |
Name of the device |
O |
Human-readable name of the device (i.e. door sensor, watch, smart TV, etc) along with manufacturer details |
Application List |
O |
List of application identities |
> Application Identity |
O |
Identity of the application |
> Application schedule |
O |
Operational schedules of each application (e.g., time windows) which the |
> Application KPIs |
O |
Minimum KPIs required by each application to operate effectively within the PIN (e.g., PIN bandwidth, PIN request rate, PIN response time) |
capabilities |
M |
capabilities of the PIN client like whether it provides relay capability for other PIN elements, whether it can be assigned with the role of PEMC or PEGC etc. |
Visibility |
M |
Determines whether this PIN element is discoverable by other PIN elements within PIN, discoverable by other UEs outside the PIN etc., |
access type |
M |
Access type supported for the communication |
Layer-2 details |
O |
Layer-2 address of the PIN element |
Required services |
O |
Identifies the list of services the PINE wants to consume |
Supported services |
O |
Identifies the list of services the PINE is providing and allowed to be accessed |
Editor’s Note: Other IEs for the purpose of enabling multiple PEMC/PEGC scenarios, e.g. procedure for role change, are FFS.