Content for TS 23.542 Word version: 18.4.0

0… 5… 8… 8.3… 8.4… 8.5… 8.5.3… 8.5.4… 8.5.7… 8.5.8… 8.5.9… 8.5.10… 8.5.11… 8.5.12… 8.5.13… 8.5.14… 8.6… 8.7… 8.8… 8.9… 8.10… A…

8.1 General 8.2 Common Information Elements 8.2.1 General 8.2.2 PIN Profile 8.2.2.0 PIN Profile in a PIN 8.2.2.1 PIN Profile in a PIN 8.2.2.2 Dynamic profile information of a PIN 8.2.2.3 PIN client profile
...

8 Procedures and information flows p. 23

8.1 General p. 23

The PINE communicates with the PEMC via direct way (i.e., via WiFi, BlueTooth), or indirect way relayed by a PEGC. PINE determines to use direct way or indirect way based on the capabilites of access types supported by the PINE, PEMC and PEGC.

The Application layer must be able to influence the RAT selection for establishing connectivity to the PIN.

In order to support the PIN enabler layer communication, the IP address or port number of PIN enabler layer (PIN client) should be negotiated among PINE, PEGC and PEMC, for example, during PIN create procedure or device direct connection.

8.2 Common Information Elements p. 24

8.2.1 General p. 24

This clause provides descriptions for Information Elements which are commonly used in several procedures.

8.2.2 PIN Profile p. 24

8.2.2.0 PIN Profile in a PIN p. 24

PIN profile information include static and semi-static data and default configuration that are needed for configuration of Personal IoT Networks, such as the PEMC, PEGC and PIN server end point addresses. Information in a PIN profile is infrequently changed.

Dynamic PIN profile information includes data that are updated more frequently due to operations of a PIN, e.g. caused by PINE join or PINE leave operations. Example information include PINE lists and the services that PINEs provide.

8.2.2.1 PIN Profile in a PIN p. 24

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 PINEs allowed to join the PIN.	Y	Y	N
Allowed PIN service	List of service that can be offered within a PIN: > PIN service Provider Identifier > PIN service type > PIN service Feature	Y	Y	N
Allowed PEMC list	The list of PINE static information for PINE(s) that can be allowed to take the role of PEMC: > PINE ID > GPSI > Role (e.g., primary, secondary or both) > Port number (see NOTE)	Y	Y	Y
Allowed PEGC list	The list of PINE static information for PINE(s) that can be allowed to take the role as PEGC: > PINE identifier > GPSI > Role (e.g., primary, backup or both) > Port number (see NOTE)	Y	Y	Y
PIN Server ID	The identifier of the PIN server that serves the PIN.	N	Y	Y
PIN server Endpoint	The endpoint information (e.g., URI, FQDN) or a static IP address used to communicate with the PIN server.	N	Y	Y
Allowed PIN elements list	List of PINEs which can be allowed to join the PIN > PINE ID	Y	Y	Y

8.2.2.2 Dynamic profile information of a PIN p. 25

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
Current PIN services	List of services that are currently offered within a PIN.	Y	Y	N
PIN state	Indicates the current state of the PIN (activated or de-activated). When the PIN is in deactivated state services offered by the PIN are inaccessible and no PIN elements can join the PIN. Also PEGC closes all the communication channel it has created for the flow of application traffic from PIN elements via 5GS to the application server.	Y	Y	Y
Current PEMC list	The list of PINE dynamic information for PINE(s) that currently have the role of PEMC: > PINE identifier > Role (e.g., primary or secondary) > PEMC current IP address > Duration or time period allowed as PEMC > Heartbeat timer value (see NOTE 2)	Y	Y	Y
Current PEGC list	The list of PINE dynamic information for PINE(s) that currently have the role of PEGC: > PINE identifier > Role (e.g., primary or backup) > PEGC current IP address > Duration or time period allowed as PEGC > Maximum number of served PINE(s) > List of currently served PINE(s) information > Heartbeat timer value (see NOTE 3)	Y	Y	Y
PIN Elements List	List of PIN elements currently registered/joined the PIN and their details.
	> PINE ID	Y	Y	Y
	> Endpoint information of each PINE (e.g. URI, FQDN, IP address, port number) used to communicate with the PINE (NOTE 1).	Y	Y	Y
	> Services offered by the PIN element	Y	Y	N
	> Reachability information of the PIN element NOTE: Reachability information of the PIN element may include the IP address which is internally routable via PEGC (like LAN or Layer 2 gateway) or routable via 5GS.	Y	Y	Y
	> List of application clients for this PIN element:	Y	Y	Y
	>> 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. Location and/or schedule information for each of the backup PEGCs may also be included such that a backup PEGC may be selected by the PIN element based on its current location and proximity to a backup PEGC and/or the availability schedule of the PEGC.	Y	Y	Y
	> Heartbeat timer value defining the periodicity of heartbeat requests this PIN element sends to the PEMC to indicate this PIN element is still available within the PIN.	Y	Y	Y
NOTE 1: The port number is the port used by a PINE to expose a service within the PIN. NOTE 2: The heartbeat timer value defining the periodicity of heartbeat requests that the PEMC sends to the PIN server to indicate the PEMC is still available and serving as a PEMC. NOTE 3: The heartbeat timer value defining the periodicity of heartbeat requests that the PEGC sends to the PEMC to indicate the PEGC is still available and serving as a PEGC.

8.2.2.3 PIN client profile p. 28

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.
PINE role	O	Role of PINE: PEMC, PEGC, other.
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 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.
Port number	M	Port number of PIN client on PINE to support PIN enabler layer communication. NOTE: The port number is the port used by a PINE to expose a service within the PIN.