Section: 4.26 Support for Personal IoT Network service
Content: The 5GS can support the Personal IoT Network (PIN) service (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ]  [8]). The PIN enables the Personal IoT Network Elements (PINEs) to communicate with each other via PIN direct communication, PIN indirect communication or PIN-DN communication. For the PIN indirect communication and PIN-DN communication, a UE acting as a PIN Element with Gateway Capability (PEGC) enables the PINEs behind the PEGC to connect to the network and to communicate with other PINEs within the PIN or with the DN via the PDU session established for PIN. A PEGC may serve one or more PINs. The PEGC establishes only one PDU session for each PIN. The PEGC establishes different PDU sessions for different PINs based on different DNNs and S-NSSAIs. The PEGC may establish only one PDU session for multiple PINs if traffic differentiation for multiple PINs is not required in 5GS. NOTE 1: The PIN direct communication is out of the scope of 3GPP. The PIN, PEGC, and PINEs are managed by PIN Element with Management Capability (PEMC) and optionally the corresponding application function. Each PIN contains at least one PEGC and at least one PEMC. The PIN architecture is captured in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ]  [8]. The 5GS supports the delivery of URSP rules which include the PIN ID to a PEGC registered to 5GS (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ]  [8] and 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [10]). The 5GS is enhanced to support the PDU session management for PIN to ensure the end-to-end QoS requirement. The end-to-end QoS requirement for each PINE over PIN indirect communication and over PIN-DN communication includes: a) the QoS requirement in the 3GPP access network; and b) the QoS requirement in the non-3GPP access network. The N3QAI is introduced to enable a PEGC to perform the QoS differentiation for the PINEs in the non-3GPP access network. If the UE supports receiving the N3QAI, the network may provide the N3QAI associated with the QoS flow during the PDU session establishment procedure as defined in subclause 6.4.1 or during the PDU session modification procedure as defined in subclause 6.4.2. NOTE 2: How the PEGC applies N3QAI is outside the scope of the present document. The non-3GPP delay budget refers to the delay budget between the PEGC and the PINE in the non-3GPP access network. If the UE supports providing the non-3GPP delay budget, the UE may provide the network with the non-3GPP delay budget for the one or more QoS flows associated with the PDU sessions for a PIN during the PDU session modification procedure as defined in subclause 6.4.2. The network takes into account the received non-3GPP delay budget to ensure the end-to-end QoS requirement of a PINE. NOTE 3: The support of a 5G-RG or a FN-RG acting as a PEGC is not specified in this release of specification. NOTE 4: The support of redundant PDU sessions does not apply for PIN.