Content for &nbsp; TS 23.542 &nbsp; Word version:&nbsp; 18.4.0

PEGCs (e.g., PEGC-A and PEGC-B) shall join the PIN by sending PIN management PINE join into PIN requests to the PEMC. The PIN Client Profile information (supported PIN roles, supported PEGC KPIs, Supported PEGC schedule, UE location) shall be included in the requests. The PEMC shall use this information to determine whether multiple PEGCs are needed to meet the required KPIs of the PIN and which PIN elements (e.g., PEGC-A and PEGC-B) are able to serve as PEGCs. The PEMC shall configure multiple PEGCs (e.g., PEGC-A and PEGC-B) with a role of PEGC if needed. The PEMC shall then send a PIN profile update to the PIN server informing the PIN server that of the multiple PEGCs.

When PINEs (e.g., PINE-1) send a PIN management PINE join into PIN request to the PEMC, PIN Client Profile information (application client KPIs, application client schedule, UE location) shall be included in the request. The PEMC shall use this information and the PEGC information the PEMC received in step 1 to determine the optimal default and backup PEGCs for the PINE. For example, PEMC assigns PEGC-A as the default PEGC for PINE-1, and PEGC-B as the backup PEGC for PINE-1.

Figure 8.5.4.2.2-1: PIN management with multiple PEMCs

The PEMC shall send a default PEGC (e.g., PEGC-A) PIN status notification to update its local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.

Step 4.

The PEMC shall send any backup PEGCs (e.g., PEGC-B) PIN status notification to update their local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.

Step 5.

The PEMC shall return a PIN management PINE join into PIN response to PINE-1. The response shall include updated PIN client profile information informing the PINE that it shall use a specified PEGC (e.g., PEGC-A) as its default PEGC, and a specified PEGC (e.g., PEGC-B) as its backup PEGC.

Step 6.

The PEMC shall send a PIN profile update to the PIN server informing the PIN server of a PEGC (e.g., PEGC-A) serving as the default PEGC for a PINE (e.g., PINE-1) and any PEGCs (e.g., PEGC-B) serving as backup PEGCs for a PINE.

Step 7.

Steps 2 to 6 may be repeated for any additional PINEs joining the PIN. For example, based on PIN client profile information provided by PINE-2, the PEMC configures PEGC-B to serve as the default PEGC for PINE-2 and PEGC-A to serve as the backup PEGC for PINE-2.

8.5.4.2.2 PIN management with multiple PEMCs p. 49

Figure 8.5.4.2.2-1 illustrates a procedure for managing the PIN with multiple PEMCs. PIN elements when registering with the PIN indicates that they have the capability to act as PEMC and are assigned with primary or secondary PEMC role as described in the subclause 8.4.2.2.1.

Pre-conditions:

A PIN owner or admin creates a PIN and configured multiple PEMCs.
PEMC-S is assigned with the role of secondary PEMC and PEMC-P is assigned with the role of primary PEMC.
PEMC-S has direct connection or PIN direct connection with the PEMC-P.

Reproduction of 3GPP TS 23.542, Fig. 8.5.4.2.2-1: PIN management with multiple PEMCs

PEMC-S receives a request from PIN owner or PIN admin to perform any of the PIN management operations. Some of the PIN management operations (PIN profile update, PIN element removal) shall be performed by secondary PEMC (PEMC-S) itself and some operations (PIN deletion, PIN activation and PIN deactivation) can be sent to primary PEMC (PEMC-P) which shall be validated and executed by the PEMC-P.

PEMC-S prepares the corresponding request including the required details for the requested operation and sends it to PEMC-P. These requests shall carry the PIN client ID of the PEMC-S mandatorily.

Figure 8.5.4.2.3-1: Notifying the PIN elements of PEGC details

PEMC-P on receiving the request checks whether the PEMC-S is authorized as secondary PEMC in-order to perform the operation.

Step 4.

If the authorization succeeds, PEMC-P proceeds with the requested operation.

Step 5.

PEMC-P sends the response to PEMC-S containing the status or result of the requested operation.

8.5.4.2.3 Notifying the PIN elements of PEGC details p. 50

Figure 8.5.4.2.3-1 illustrates a procedure for notifying the PIN elements about the change in default or backup PEGC when multiple PIN elements have the PEGC capability.

Pre-conditions:

The PIN is configured and PEGC-1 is the designed PEGC.
PIN elements have subscribed for PIN status as specified in clause 8.5.9.2.1.

Reproduction of 3GPP TS 23.542, Fig. 8.5.4.2.3-1: Notifying the PIN elements of PEGC details

PEGC-2 is authorized to join the PIN as specified in the sub-clause 8.4 and is assigned with the role of PEGC.

Upon joining the PIN, the PEMC determines the list of PIN elements for which PEGC-2 can act as default PEGC or backup PEGC. (e.g. PEGC-2 is designated to be the backup PEGC for PINE-1 and default for PINE-2).

Figure 8.5.5.2-1: Query PIN profile procedure

The PEMC sends the PIN status notify to PINE-1 indicating that PEGC-2 is the backup PEGC for PINE-1 as specified in as specified in clause 8.5.9.2.2.

Step 4.

The PEMC sends the PIN status notify to PINE-2 indicating that PEGC-2 is the default PEGC for PINE-2 as specified in as specified in clause 8.5.9.2.2.

8.5.4.3 Void

8.5.4.3.1 Void

8.5.5 PIN Profile Recovery p. 51

8.5.5.1 General p. 51

The PIN profile recovery procedure describes how the PEMC retrieves a PIN profile from a PIN server.

8.5.5.2 Procedure p. 51

Pre-conditions:

The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
The PIN has already been created and a PIN ID is distributed by PIN server;
The PEMC has been authorized to communicate with the PIN server;
A PIN client has already received the role of PEMC from PIN server;

The PEMC sends PIN Profile Query requests (PEMC ID, PIN ID) to the PIN server.

The PIN server determines whether the PEMC is one of the managers of the PIN. The PIN Server validates if the PEMC is authorized to perform the operation; if the PEMC is authorized, the PIN Server verifies if the PEMC is authorized to manage the PIN. The PIN server processes the request.