Content for  TS 23.542  Word version:  18.4.0

The PINE (including PINE/PEMC/PEGC) sends a PINE Registration Request to the PIN server. The request includes the security credentials of the PINE received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PINE Address. If the PEMC trigger the request, this registration request carries the PIN ID of the PIN for which it is intending to register as PEMC and the PIN element may indicate whether it is to be assigned with primary or secondary PEMC role.

The PIN server checks whether the UE identified by the GPSI has subscribed to be a PEMC. Also, the PIN server can check the whether the UE identified by the GPSI has subscribed to be a PEMC itself. If subscribed, it checks the subscription of PINE whether the requesting PIN element can be assigned with primary or secondary role and authorize the PIN element accordingly. In case if the PIN has already been created, the requesting PIN element is assigned with the secondary PEMC role irrespective of the role requested by the PIN element.

The PIN server responds to the PINE with PINE Registration Response with allocated PIN client ID in successful response. If the registration procedure fails, the PIN server should give the failure response that indicates the cause of registration request failure.

The PINE/PEGC sends PINE Registration Request to the PEMC. The request includes the security credentials of the PINE received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PINE Address.

If the PEMC receives the PINE Registration Request from PINE, the PEMC may represent the PINE to register into PIN server by sending the PINE registration request to PIN server. If the PEMC represents the PINEs to perform registration procedure, it should send a PINE Registration Request to PIN server including an Indication of representation registration and Lists of PINEs/PEGCs.

The PIN server responds to the PEMC with PINE Registration Response with allocated PIN client ID in successful response. When the PINE Registration Request that containing Indication of representation registration, the PIN server shall verify whether PINE(s) and PEGC(s) included in the List of PINEs/PEGCs are allowed to fullfill the requested role or not. The PIN server responses to PEMC with a successful response and may include a list of accepted registration information and a list of rejected registration information (if any). If all the PINEs in the Lists of PINEs/PEGCs are rejected, the PIN server sends a failure response including the failure cause.

The PEMC sends the response received in step 3 to the PINE/PEGC. When the PEMC receiving the PINE Registration response from PIN server, the PEMC should extract the accepted registration information and rejected registration information (if any) for all the PINEs, and send the result to each PINE in the Lists of PINEs/PEGCs.

The PINE sends PIN registration request to the PIN server. The PIN registration request is routed to the PEGC. The PINE device identity, device credentials and other necessary formation which is also needed for PIN service authorization are included.

The PEGC identifies the received message is the PIN registration request which is allowed to be forwarded regardless the PINE is authorized or not.

The PEGC forwards the PIN registration request towards the PIN server.

The PIN server performs service authorization and verifies the PINE device with the information in the registration request. If authorized, the PIN server allocates the PIN client ID, authorization and security credentials for the PINE.

The PINE server returns the PIN registration response to the PEGC.

The PEGC forwards the PIN registration response to the PINE.

The PINE sends PIN join/discovery request to the PEGC. The PINE device identity is included.

• For the PIN join request, the PIN ID is included.
• For the PIN discovery request, the discovery criteria are included.

The PEGC identifies the received message is the PIN join/discovery request, and the PINE is not registered and authorized due to no PIN client ID and credentials in the message.

The PEGC returns the PIN join/discovery reject message to the PINE. The registration and authorization indication are also included to instruct the PINE to perform registration.

The PINE if not registered, initiates the PIN registration towards the PIN server via the PEGC as described in clause 8.4.2.2.1.

After the registration, the PINE will use the PIN client ID and credentials to initiate the PIN join/discovery again.

The PINE (including PINE/PEMC/PEGC) sends a PINE de-registration Request to the PIN server. The request includes the security credentials of the PINE received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PINE Address.

The PIN server checks whether the UE identified by the GPSI has active registration with the PIN server.

The PIN server responds to the PINE with PINE de-registration response which contains the status of the PINE de-registration request. If the PINE is successfully de-registered, the PIN server deletes all the configuration information it has related to the PIN element that is being de-registered. If the de-registration procedure fails, the PIN server should give the failure response to indicates that indicates the cause of de-registration request failure.

The PINE (including PINE/PEMC/PEGC) sends a PINE de-registration Request to the PEMC. The request includes the security credentials of the PINE received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PIN ID, PINE Address.

The PEMC sends the PINE de-registration request to PIN server.

The PIN server checks whether the UE identified by the GPSI has active registration with the PIN server. The PIN server responds to the PINE with PINE de-registration response which contains the status of the PINE de-registration request. If the PINE is successfully de-registered, the PIN server deletes all the configuration information it has related to the PIN element that is being de-registered. If the de-registration procedure fails, the PIN server should give the failure response that indicates the cause of de-registration request failure.

The PEMC sends the response received in step 3 to the PINE/PEGC.

The PINE (including PINE/PEMC/PEGC) sends a PINE update registration request to the PIN server directly or via PEGC. The request includes the security credentials of the PINE received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PINE Address. If the registration request is sent from PINE to PEGC, the PEGC delivers the PINE update registration request to the PIN server.

The PIN server checks whether the UE identified by the GPSI has active registration with the PIN server.

The PIN server responds to the PINE with PINE update registration response directly or via PEGC which contains the status of the PINE update registration request. If the update registration procedure fails, the PIN server should give the failure response to indicates that indicates the cause of update registration request failure.