Section: J.1 Procedure for PIN service
Content: Figure J.1-1: Procedure for PIN service PIN is a subscribed service, and a user needs to coordinate with the Mobile Network Operator to subscribe for PIN service. When a user subscribes for a PIN, the subscription data includes the DNN and S NSSAI allocated by the MNO for the PIN service. The PIN user's PEGC UE(s) are then provisioned with appropriate URSP rules to enable the PEGC UE to route the PIN traffic using the DNN and S NSSAI allocated for the PIN. Figure J.1-1 provides a high level procedure for PIN service. Step 1: Step 1 is performed using O&M. A user subscribes to the Mobile Network Operator (MNO) for PIN service. The user provides the list of PEGC UE(s) that are part of the PIN. The MNO verifies the request, performs necessary checks e.g. whether the UEs are allowed to act as PEGC, whether all the requested PEGC UEs are part of the same UDM group etc. If the request is authorized by the MNO, the MNO: - allocates a dedicated DNN, S NSSAI for the PIN; - if the PIN has a single PEGC UE, then updates the PEGC UE subscription with the DNN, S NSSAI allocated for the PIN; - if the PIN has more than one PEGC UE, then creates a group subscription following the 5G VN group management principles as specified in clause 5.29.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. The information on the External Group ID and associated DNN and S-NSSAI is provided to the AF for PIN; - if local switching is required, configures in the SMF set and/or in the NRF that the DNN allocated for the PIN is served by a specific SMF set. NOTE: It is assumed that all PEGC UEs that are members of a PIN are part of the same UDM Group ID. If the PEGC UEs requested by the user for PIN creation are not part of the same UDM Group ID, the MNO migrates all the PEGC UEs into a single UDM Group ID for creating the group subscription. Step 2: For routing PIN traffic by the PEGC UE, the AF provides guidance for URSP generation to the 5GC. The AF uses a UE ID (i.e. GPSI) as the target UE if the PIN contains a single PEGC UE. If the PIN contains more than one PEGC UE, then the AF uses External Group ID as the target UEs for providing URSP guidance to the 5GC. The AF request contains DNN, S NSSAI allocated to the user for the PIN service and the traffic descriptor components in the URSP rule request from the AF contains the PIN ID. The NEF authorizes the request received from the AF and stores the information in the UDR as "Application Data". The NEF can use the procedure for authorization of service specific parameter provisioning as specified in clause 4.15.6.7a to authorize the AF request by the UDM. In this case: - if the request is for an individual UE, the UDM checks if the DNN and S NSSAI in the AF request is allowed for the UE; - if the request is for a group of UEs, the UDM checks whether the group related data (e.g. DNN/S NSSAI group related data, see table 4.15.6.3b-1) is authorized for the group. If the AF request is authorized, the NEF stores the AF requested information in the UDR as the "Application Data" (Data Subset setting to "Service specific information"). Step 3: The PCF receives a Nudr_DM_Notify notification of data change from the UDR, generates the URSP rules and initiates UE Policy delivery as specified in clause 4.2.4.3 to provision the URSP rules in the PEGC UE(s). For routing of PIN traffic by the PEGC UE(s), the URSP policies provided to the PEGC UE(s) contain URSP rule with PIN ID as traffic descriptor. Step 4: The AF provides QoS requirements for the PIN traffic following procedures for AF requested QoS for a UE or group of UEs not identified by a UE address as specified in clause 4.15.6.14. Step 5: When the PEGC UE(s) detect PIN traffic, it uses the provisioned URSP rules to identify PDU session to route the traffic as specified in clause 6.6.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]. The 5GC further performs session management and user plane management as described in Annex P, clause P.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. When 5G VN Group is not used for a PIN and if the PIN contains more than one PEGCs, then the AF request for URSP guidance and QoS requirements is targeted to each individual PEGC UEs that are part of the PIN.