Content for  TS 23.542  Word version:  18.4.0

Figure 8.5.10.2.2-1 describes the PIN modification procedure to perform a PEMC role change due to the failure of the PEMC. An authorised administrator is the owner of the PIN and accesses PIN configuration using an application on a UE, which is one of the PEMC for the PIN. The authorised administrator can manage the PIN locally or through the 5G network. This procedure describes a PEMC (e.g., an authorized administrator on a UE) managing the PIN remotely via the 5G network. The procedure may be used e.g. when a PEMC is available on a UE for PIN management by an authorised administrator. When there is a local PEMC failure, the authorized administrator can be enabled to manage the PIN remotely, via the 5G network, using the following steps. Pre-conditions:

1. The PIN server has authorized the creation of the PIN.
2. The authorized administrator is the owner of the PIN and has created the PIN.
3. The authorized administrator configures the active PEMC to provide PIN management for the PIN. UE/PEMC1 is the inactive PEMC.
4. The active PEMC, PEGC, PINE-1, PINE-2, and the UE/PEMC1 are members of the PIN. PINE-1 has PEMC capability.
5. The authorized administrator leaves the local area of the PIN (e.g., in a home) and is able to access the PIN remotely through the 5G network. As a result, the authorized administrator is able to manage the PIN through the 5G network.
6. The UE/PEMC1 is subscribed to the PEGC for PIN connectivity notifications

Figure 8.5.10.2.3-1 describes a PIN modification procedure to perform a PEGC role change due to the unavailability of the PEGC. This procedure describes a PEMC detecting the unavailability of a PEGC (e.g. PEGC leaves the local service area of the PIN) and performing a PIN modification with the PIN Server to assign a new PEGC. As part of PIN management, a PEMC receives periodic PIN heartbeat messages from PEGCs to ensure PIN routing is available for members of the PIN at all times. If a PEMC does not receive the periodic PIN heartbeat messages from the PEGC, then the PEMC needs to assign a new PEGC or request the PIN server to assign the new PEGC. Pre-conditions:

1. The PIN server has authorized the PEMC to create PINs.
2. The PEMC creates a local PIN with members: PEMC, UE serving as PEGC, PINE1, and PINE2.
3. The PEMC maintains a PIN profile with information on the capabilities of each PIN member.
4. PINE2 is a PIN member that also has gateway capability.

A PIN element could have been authorized to act as PEMC for a certain duration after which it is either removed from the PIN or de-authorized to act as PEMC. Another PIN element in the PIN takes over the role of PEMC. When the duration of its role as PEMC is expiring or for some other reasons (implementation specific) the current PEMC requests another PINE to take the role of PEMC. Once the role assignment succeeds, the PIN server and other PIN elements including PEGC are notified of this role change. Figure 8.5.10.2.4-1 illustrates PEMC replacement procedure triggered internally within the PIN by current PEMC. Pre-conditions:

1. PEMC-2 PIN element has already indicated that it can act as PEMC during the registration process.
2. Dynamic profile information about the PIN is available at the current PEMC and PIN server

In some scenarios, like hardware failure, crash or power drain, the current PEGC may not be in a position to indicate to the PIN server or request the PIN server to assign the role of PEGC to another PIN element. In these cases, the PEMC on detecting the unavailability of the PIN element acting as PEGC, need to assign the PEGC role to another PINE and deliver the PIN dynamic information to the new PEGC. Figure 8.5.10.2.5-1 illustrates PEGC replacement procedure triggered by PEMC on detecting current PEGC is unavailable or PEGC role change is required. Pre-conditions:

1. PEGC-2 PIN element has already indicated that it can act as PEGC during the registration process.
2. Dynamic information about the PIN is available at the PEMC.
3. PIN has only one PIN element configured with the role of PEGC.

Void.

Table 8.5.10.3.2-1 shows the informational elements of the PIN configuration request sent by a PIN Element to the PIN server to obtain authorization for the modification of a PIN.

Table 8.5.10.3.3-1 shows the informational elements of the PIN configuration response provided by the PIN server to authorize the modification of a PIN.

Table 8.5.10.3.4-1 shows the informational elements of the PIN management request sent to PIN elements to make changes to the configuration of the PIN.

Table 8.5.10.3.5-1 shows the informational elements of the PIN management response received from the PIN element to the PIN modification request.

Table 8.5.10.3.6-1 shows the informational elements of the PIN PEMC role takeover request sent from current PEMC of the PIN to another PIN element with PEMC capability.

Table 8.5.10.3.7-1 shows the informational elements of the PIN PEMC role takeover response sent from requested PIN element to the current PEMC.

Table 8.5.10.3.8-1 shows the informational elements of the PIN PEGC role takeover request sent from current PEMC of the PIN to another PIN element with PEGC capability.

Table 8.5.10.3.9-1 shows the informational elements of the PIN PEGC role takeover response sent from requested PIN element to the current PEMC.