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.5.11 PIN services management 8.5.11.1 General 8.5.11.2 Procedures 8.5.11.2.1 PINE registering the services 8.5.11.2.2 PINE de-registering the services 8.5.11.3 Information flows 8.5.11.3.1 General 8.5.11.3.2 PIN services registration request 8.5.11.3.3 PIN services registration response 8.5.11.3.4 PIN services de-registration request 8.5.11.3.5 PIN services de-registration response
...

8.5.11 PIN services management p. 75

8.5.11.1 General p. 75

PIN elements can indicate the list of services it is offering at the time of joining the PIN by listing them as part of the PIN client profile. here could be scenarios wherein the PIN element may not be able to continue to provide the service(s) it indicated while joining or there could be scenarios where the PIN element may want to offer some more new services which were not supported earlier at the time of joining the PIN. This clause describes the procedures for managing the PIN services enabling the PIN elements to register or de-register the services.

8.5.11.2 Procedures p. 75

8.5.11.2.1 PINE registering the services p. 75

Figure 8.5.11.2.1-1 illustrates procedure of PIN element registering the new service(s).

Pre-conditions:

PIN is already created and the PIN entities PEGC, PINE-1, PINE-2, PINE-3 and PINE-4 are all part of the same PIN;
The PINE-4 is the PEMC of the PIN;

Reproduction of 3GPP TS 23.542, Fig. 8.5.11.2.1-1: PINE registering the service(s)

Figure 8.5.11.2.1-1: PINE registering the service(s)

Step 1.

PINE-1 decides to register a new service(s) that it can offer which it was not offering at the time of joining the PIN. This may happen because of the UE on which the PIN element is existing has been upgraded to offer extra services or for any other reason which could be implementation specific.

Step 2.

PINE-1 sends the PIN services registration request to the PEMC to register the new service(s). This request carries the PIN identifier, PIN element Identifier, list of new service(s) it is offering. The list of services can include a unique service id, human readable description of the service and may also contain time duration of when the service is available etc.

Step 3.

PEMC (PINE-4) on receiving the PIN services registration request checks whether the PINE-1 is allowed to register new service(s) and whether these services are allowed to be offered by the PIN by checking the PIN profile.

Step 4.

PEMC (PINE-4) sends the PIN services registration response which contains the status (success or failure) of the PIN services registration request.

Step 5.

PEMC notifies all the PIN entities including PIN server and PEGC about the details of the new services being offered and the details of the PINE offering the services. PIN server, PEMC and PEGC updates the PIN dynamic information with the details of the new service(s) being offered and the PINE which is offering it.

8.5.11.2.2 PINE de-registering the services p. 76

Figure 8.5.11.2.2-1 illustrates procedure of PIN element de-registering the service(s).

Pre-conditions:

PIN is already created and the PIN entities PEGC, PINE-1, PINE-2, PINE-3 and PINE-4 are all part of the same PIN;
The PINE-4 is the PEMC of the PIN;

Reproduction of 3GPP TS 23.542, Fig. 8.5.11.2.2-1: PINE de-registering the service(s)

Figure 8.5.11.2.2-1: PINE de-registering the service(s)

Step 1.

PINE-1 decides to de-register a service(s) that it is currently offering and which it has indicated during the PIN registration or PIN join procedure. This may happen because the UE on which the PIN element is existing might face hardware failure, services might be scheduled to be offered for a certain time period/duration or for any other reason which could be implementation specific.

Step 2.

PINE-1 sends the PIN services de-registration request to the PEMC to de-register the service(s). This request carries the PIN identifier, PIN element Identifier, list of service(s) it is de-registering. The list of services can include a unique service id, human readable description of the service.

Step 3.

PEMC (PINE-4) on receiving the PIN services de-registration request checks whether the PINE-1 is allowed to de-register service(s) by checking the PIN profile.

Step 4.

PEMC (PINE-4) sends the PIN services de-registration response which contains the status (success or failure) of the PIN services de-registration request.

Step 5.

PEMC notifies all the PIN entities including PIN server and PEGC about the details of the services being de-registered. PIN server, PEMC and PEGC updates the PIN dynamic information to remove the details of the service(s) being de-registered.

8.5.11.3 Information flows p. 77

8.5.11.3.1 General p. 77

8.5.11.3.2 PIN services registration request p. 77

Table 8.5.11.3.2-1 shows the informational elements of the PIN services registration request sent by a PIN Element to the PEMC to register for new services it is offering.

Table 8.5.11.3.2-1: PIN services registration request

Information element	Status	Description
PIN ID	M	The identifier of the PIN.
Requester PINE ID	M	The identifier of the PIN Element making the request.
List of services	M	List of services that a PINE wants to register.
> Service type	O	Indication of service type.
> Time duration	O	Availability period of service.
> Service description	O	Description of the service.
> Service Identifier	M	Identifier of the service.

8.5.11.3.3 PIN services registration response p. 78

Table 8.5.11.3.3-1 shows the informational elements of the PIN services registration response sent by PEMC to the PIN element.

Table 8.5.11.3.3-1: PIN services registration response

Information element	Status	Description
PIN ID	M	The identifier of the PIN.
Requester PINE ID	M	The identifier of the PIN Element making the request.
Result	M	Indication of whether the service registration is success or failure.
> Successful response	O	Indicates the successfully registered PIN services.
> Failure response	O	Indicates the failure of registered PIN services.

8.5.11.3.4 PIN services de-registration request p. 78

Table 8.5.11.3.4-1 shows the informational elements of the PIN services de-registration request sent by a PIN Element to the PEMC.

Table 8.5.11.3.4-1: PIN services de-registration request

Information element	Status	Description
PIN ID	M	The identifier of the PIN.
Requester PINE ID	M	The identifier of the PIN Element making the request.
List of services	M	List of services that a PINE wants to de-register.
> Service type	O	Indication of service type.
> Service description	O	Description of the service.
> Service identifier	M	Identifier of the service.

8.5.11.3.5 PIN services de-registration response p. 78

Table 8.5.11.3.5-1 shows the informational elements of the PIN services de-registration response sent by PEMC to the PIN element.

Table 8.5.11.3.5-1: PIN services de-registration response

Information element	Status	Description
PIN ID	M	The identifier of the PIN.
Requester PINE ID	M	The identifier of the PIN Element making the request.
Result	M	Indication of whether the service de-registration is success of failure.