hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.14 Support of slicing
|
Slicing as defined in TS 23.501 [2] is supported with following clarifications and modifications:
- 5G-RG may receive USRP rules mapping application flows to S-NSSAI (and other 5GC related parameters). For 5G-RG, the detection of application flows may refer to traffic from devices within the customer premises.
NOTE: In this case, even though an URSP rule refers to the IP PDU Session type, Non-IP Traffic descriptors e.g. layer 2 related Traffic descriptors can be used to identify application flows.
- For 5G-RG access over 3GPP access (FWA), slicing is supported as described in TS 23.501 [2].
- For 5G-RG access over Wireline, the Wireline access is assumed to be able to carry slicing information in W-CP together with NAS signalling between the 5G-RG and the W-AGF.
- The W-AGF shall support the same requirements for AMF selection based on slicing request from the UE than defined for N3IWF / TNGF in TS 23.501 [2] clause 5.15.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.15 Support for IMS services
|
When FN RG is used, support IMS Emergency sessions without a SUPI are not supported.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.16 Access to non-public networks via wireline access network
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.16.1 Access to SNPN services via wireline access network
|
Access to SNPN defined in clause 5.30 of TS 23.501 [2] via a wireline access network follows the same specification and procedures used for accessing a PLMN via a wireline access with the following modifications:
- The SNPN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF.
- In the case of 5G-RG connected via FWA, the 5G-RG shall support the capability defined for the SNPN-enabled UE as specified in clauses 5.30.2.3 and 5.30.2.4.1 of TS 23.501 [2] where the UE is replaced by 5G-RG.
- The access to SNPN via FN-CRG is supported as follows: the W-AGF is configured to use a SNPN Identifier (as defined in clause 5.30.2.1 of TS 23.501 [2]) instead of a PLMN Identifier in the procedure for FN-CRG Registration via W-5GAN defined in clause 7.2.1.3. The access to SNPN via FN-BRG is not supported in this Release.
- The SUPI for a 5G-CRG containing IMSI is described in clause 5.9.2 of TS 23.501 [2]. The SUPI in NSI type may include the NID of SNPN as defined in clause 28.7.2 of TS 23.003 [14].
- The SUPI for a 5G-CRG and FN-CRG containing GCI is specified in clause 4.7.4 and in clause 28.15.2 of TS 23.003 [14]. The realm part of NAI format for a SUPI containing a GCI identifying the operator owning the subscription may include the NID of the SNPN.
- The SUPI for a 5G-BRG and FN-BRG containing GLI is specified in clauses 4.7.2, 4.7.3 and 28.16.2 of TS 23.003 [14]. The realm part of NAI format for a SUPI containing a GLI identifying the operator owning the subscription may include the NID of the SNPN.
- RG using credentials owned by a Credentials Holder separate from the SNPN is not applicable. UE behind RG accessing to SNPN via N3IWF or TNGF as defined in clause 4.10 with credentials owned by Credentials Holder is supported as specified in clause 5.30.2.9 of TS 23.501 [2] where the Credentials Holder's AAA server or AUSF are reachable via N3IWF or TNGF. The support of UE behind a RG accessing to SNPN with credentials owned by Credentials Holder directly reachable from RG, i.e. without N3IWF and TNGF, is not specified in this Release.
- The onboarding procedure specified in clause 5.30.2.10 of TS 23.501 [2] is not applicable in this Release for a RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.16.2 Access to Public Network Integrated NPN services via wireline access network
|
Considering that the Public Network Integrated NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN and that the W-AGF may support more than one network slices and different W-AGFs may support different sets of network slices, therefore the access to PNI-NPN defined in clause 5.30 of TS 23.501 [2] via a wireline access network applies with the following modifications:
- In case of 5G-RG and FN-RG connected via wired physical connectivity to W-AGF the Closed Access Group does not apply to 5G-RG/FN-RG and to W-AGF. The access restriction is implicitly applied since the RG's subscription information includes only the relevant network slice(s) (i.e. the network slice(s) related to PLMN and NPI-NPN subscribed) and the fact the 5G-RG/FN-RG is physically connected to W-AGF implies that the subscribed slice(s) are applicable from the user physical location.
- In the case of 5G-RG connected via FWA, the 5G-RG may support the CAG procedure as specified in clause 5.30.3 of TS 23.501 [2] where the 5G-RG replaces the UE.
NOTE: The connection via FWA is not applicable to a FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.17 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.17.1 General
|
This clause provides an overview of W-5GAN functionalities for support of XR services (AR/VR applications) and interactive media services that require high data rate and low latency communication, as defined in clause 5.37 of TS 23.501 [2] for 5GS:
- W-5GAN may support ECN markings for L4S, see clause 4.17.2.
- W-5GAN may support PDU Set based QoS handling, see clause 4.17.3.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.17.2 ECN marking for L4S
|
In order to support ECN marking for L4S at W-AGF as specified in TS 23.501 [2], SMF provides ECN marking request per QoS flow level to the W-AGF as part of PDU Session Management procedure. If the W-AGF supports ECN marking, it applies mapping between L4S-enabled QoS profile(s) and L4S-enabled W-UP resource(s).
ECN marking for L4S in 5G-RG may be supported in UL. The SMF may send the Indication of ECN marking for L4S associated with QoS rule(s) to the 5G-RG via N1 signalling (Indication of ECN marking for L4S for a corresponding QoS Flow(s)) and applies mapping between L4S-enabled QoS rule(s) and L4S-enabled W-UP resource(s).
When ECN marking for L4S at W-AGF is enabled for downlink or uplink or 5G-RG in UL, the W-AGF or 5G-RG should set the Congestion Experienced (CE) codepoint in downlink or uplink IP packet inner header per the recommendations in IETF RFC 9330 [48], IETF RFC 9331 [49], IETF RFC 9332 [50] and implement IP-in-IP encapsulation and decapsulation as specified in IETF RFC 6040 [51] and IETF RFC 9599 [52].
NOTE: Any non-3GPP access node (i.e. W-AGF and 5G-RG) supporting L4S and acting as an IP-in-IP tunnel endpoint between the XR application client and server is assumed to implement encapsulation and decapsulation as specified in IETF RFC 6040 [51] and IETF RFC 9599 [52].
The criteria based on which W-AGF and 5G-RG decides to mark ECN bits for L4S is implementation specific.
NOTE: W-AGF and 5G-RG mapping between L4S-enabled QoS rule(s) and L4S enabled W-UP resource(s) is up to implementation.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
4.17.3 PDU Set based Handling
|
PDU Set based QoS handling, as defined in clause 5.37.5 of TS 23.501 [2], by the W-5GAN is determined by PDU Set QoS Parameters in the QoS profile of the QoS Flow and PDU Set Information provided by the PSA UPF.
For QoS Flows with PDU Set based QoS handling enabled, PDU Set QoS Parameters are determined by the PCF (based on information provided by AF and/or local configuration) and provided by SMF to the W-AGF as part of the QoS profile. Alternatively, the SMF may be configured to support PDU Set based QoS handling without receiving PCC rules from PCF. When the W-AGF receives N2 requests related to PDU Session resources, the W-AGF maps the QoS profile(s) received from the 5GC to W-UP level QoS.
For the downlink direction, the PSA UPF identifies PDUs that belong to PDU Sets and provides the PDU Set Information to the W-AGF in the GTP-U header, as described in clause 5.37.5.2 of TS 23.501 [2].
For the uplink direction, 5G-RG may identify PDU Sets, and how this is done is left to 5G-RG implementation. The SMF may send UL Protocol Description associated with the QoS rule to the 5G-RG, as described in clause 5.37.5.1 of TS 23.501 [2].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
5 Network Function
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
5.0 General
|
This clause specifies the definition network function specific for W-AGF and the delta to network function defined in TS 23.501 [2].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
5.1 Network Function Functional description
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
5.1.1 W-AGF
|
The functionality of W-AGF in the case of Wireline 5G Access network includes the following:
- Termination of N2 and N3 interfaces to 5G Core Network for control - plane and user-plane respectively.
- Handling of N2 signalling from SMF (relayed by AMF) related to PDU Sessions and QoS.
- Support of ECN marking for L4S: The SMF provides ECN marking request per QoS flow level to the W-AGF as part of PDU session management procedures.
- When ECN marking for L4S at W-AGF is enabled for downlink or uplink, the W-AGF applies the mapping between L4S-enabled QoS profile(s) and L4S-enabled W-UP resource(s) and the W-AGF should set the Congestion Experienced (CE) codepoint in downlink or uplink as per IETF RFC 9330 [48], IETF RFC 9331 [49], IETF RFC 9332 [50], IETF RFC 6040 [51] and IETF RFC 9599 [52].
NOTE: The mapping between L4S-enabled QoS rule(s) and L4S enabled W-UP resource(s) is up to implementation.
- Relaying uplink and downlink user-plane packets between the 5G-RG and UPF and between FN-RG and UPF. This involves:
- Enforcing QoS corresponding to N3 packet marking, taking into account QoS requirements associated to such marking received over N2.
- N3 user-plane packet marking in the uplink.
- Supporting AMF discovery and selection defined in TS 23.501 [2] clause 6.3.5 where the 5G-S-TMSI is not used for AMF selection since the wireline AS layer can only carry the GUAMI.
- Termination of wireline access protocol on Y4 and Y5.
- In the case of FN-RG the W-AGF acts as end point of N1 on behalf of the FN-RG.
- Support PDU Set Handling as defined in clause 4.17.3 and in clause 5.37.5 of TS 23.501 [2].
In the case of Wireline 5G Broadband Access network the definition of W-AGF functionalities is specified in BBF TR-456 [9] and WT-457 [10].
NOTE: The W-AGF is specified as AGF (Access Gateway Function) in BBF TR-456 [9] for supporting 5G-RG and FN-RG and as FMIF (Fixed Mobile Interworking Function) for supporting FN-RG only in the case of presence of BNG in WT-457 [10]. Both cases for FN-RG support, i.e. AGF and FMIF, have identical interfaces towards 5GC, i.e. it is transparent to 5GC whether AGF or FMIF is used and no difference between AGF or FMIF cases is defined in this specification.
In the case of Wireline 5G Cable Access network the definition of W-AGF functionalities is specified by CableLabs WR-TR-5WWC-ARCH [27].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6 Control and User Plane Protocol Stacks
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.1 General
|
This clause specifies the protocol stacks between 5G-RG, FN-RG and 5GS entities for supporting W-5GAN.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.2 Control Plane Protocol Stacks for W-5GAN
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.2.1 Control Plane Protocol Stacks between the 5G-RG and the 5GC
|
Figure 6.2.1-1: Control Plane stack for W-5GAN for 5G-RG
The control plane protocol stack between 5G-RG and AMF is defined in figure 6.2.1-1.
For W-5GBAN, the W-CP protocol stack between 5G-BRG and W-AGF is defined in BBF TR-456 [9]. For W-5GCAN, the W-CP protocol stack between 5G-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27].
The protocol stack between 5GC/AMF and W-AGF is defined in TS 23.501 [2] clause 8.
The W-CP protocol stack:
- supports transfer of NAS signalling between the 5G-RG and the W-AGF;
- supports to carry AS parameters (e.g. SUCI or 5G-GUTI, Requested NSSAI and Establishment Cause) and NAS packets;
- supports the setup, modification and removal of at least one W-UP resource per PDU session;
- may support the setup, modification and removal of multiple W-UP resources per PDU session.
For the 5G-RG connected via NG-RAN the protocol stack defined in TS 23.501 [2] clause 8.2.2 applies with UE corresponding to 5G-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.2.2 Control Plane Protocol Stacks between the FN-RG and the 5GC
|
Figure 6.2.2-1: Control Plane stack for W-5GAN for FN-RG
The control plane protocol stack between FN-RG and AMF is defined in figure 6.2.2-1. The W-AGF acts as an N1 termination point on behalf of FN-RG.
For W-5GBAN, the L-W-CP protocol stack, between FN-BRG and W-AGF is defined in BBF TR-456 [9] and WT-457 [10]. For W-5GCAN, the L-W-CP protocol stack between FN-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.3 User Plane Protocol Stacks for W-5GAN
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.3.1 User Plane Protocol Stacks between the 5G-RG and the 5GC
|
Figure 6.3.1-1: User Plane stack for W-5GAN for 5G-RG
The user plane protocol stack between 5G-RG and UPF is defined in figure 6.3.1-1.
For W-5GBAN, the W-UP protocol stack between 5G-BRG and W-AGF is defined in BBF TR-456 [9]. For W-5GCAN, the W-UP protocol stack between 5G-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27].
The protocol stack between 5GC/UPF and W-AGF is defined in TS 23.501 [2] clause 8.
For the W-UP protocol stack:
- W-UP supports at least one W-UP resource per PDU session. This will be the default W-UP resource.
- W-UP may support multiple W-UP resources per PDU session and associate different QoS profiles (QFIs) to different W-UP resources.
- W-UP supports transmission of uplink and downlink PDUs according to clause 4.5.
- W-UP supports access specific QoS parameters that can be mapped from 3GPP QoS parameters (e.g.5QI, RQI) received from the 5GC.
For the 5G-RG connected via NG-RAN the protocol stack defined in TS 23.501 [2] clause 8.3.1 applies with 5G-RG replacing the UE.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
6.3.2 User Plane Protocol Stacks between the FN-RG and the 5GC
|
Figure 6.3.2-1: User Plane stack for W-5GAN for FN-RG
The user plane protocol stack between FN-RG and UPF is defined in figure 6.3.2-1.
For W-5GBAN, the L-W-UP protocol stack between FN-BRG and W-AGF is defined in BBF TR-456 [9] and WT-457 [10]. For W-5GCAN, the L-W-UP protocol stack between FN-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7 System procedure
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.1 General
|
This clause describes the differences in respect the procedures defined in TS 23.502 [3] clause 4.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2 Connection, Registration and Mobility Management procedures
|
The listed parameters in the procedures are not exhaustive, but more parameters can be used as described in the protocol specifications.
Where parameters have not been described, the meaning of the parameter is the same as for 3GPP access as described in TS 23.502 [3], TS 24.501 [22], TS 38.413 [23].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.1 Registration Management procedures
|
This clause specifies delta for Registration Management procedure defined in TS 23.502 [3] clause 4.2 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.1.1 5G-RG Registration via W-5GAN
|
The 5G-RG registration management procedures are followed for both W-5GBAN and W-5GCAN.
Clause 7.2.1.1 specifies how a 5G-RG can register to 5GC via aW-5GAN. It is based on the Registration procedure specified in TS 23.502 [3] clause 4.2.2.2.2. The NAS protocol is transported between 5G-RG and W-AGF as documented in BBF TR‑456 issue 2 [43] and CableLabs WR‑TR‑5WWC‑ARCH [27]. If the 5G-RG needs to be authenticated, mutual authentication is executed between the 5G-RG and AUSF. The details of the authentication procedure are specified in TS 33.501 [11]. In Registration and subsequent Registration procedures via W-5GAN access, the NAS messages are always exchanged between the 5G-RG and the AMF. When possible, the 5G-RG can be authenticated by reusing the existing UE security context in AMF for the 5G-RG.
Figure 7.2.1.1-1 only shows authentication flow using EAP-AKA' (specifically in step 6c, step 7a and step 7b) but other methods are possible: Authentication procedures that 5G-RG and the 5GC shall support, are specified in TS 33.501 [11]. Specific EAP authentication methods (see TS 33.501 [11]) for 5G-CRG with non-3GPP identities and credentials may be used for isolated network (see TS 33.501 [11]).
Figure 7.2.1.1-1: 5G-RG Registration via W-5GAN
1. The 5G-RG connects to a W-5GAN with procedures outside the scope of 3GPP and creates an initial signalling connection using W-CP protocol stack. This connection shall support transfer of AS parameters and NAS messages between 5G-RG and W-AGF.
2. Void.
3. The 5G-RG using W-CP protocol stack sends a message that contains the Access Network parameters (GUAMI if available, the selected PLMN or SNPN, Requested NSSAI and Establishment Cause) and a NAS Registration Request message (SUCI or 5G-GUTI as defined in TS 24.501 [22], security parameters/UE security capability, NSSAI parameters, UE MM Core Network Capability, PDU session status, Follow-on request). The Establishment cause provides the reason for requesting a signalling connection with 5GC.
NOTE 1: While PLMN or SNPN selection is not supported for W-5GAN access, the 5G RG provides a selected PLMN or SNPN ID in Access Network parameters sent to the W-AGF. In this version of the specifications, this selected PLMN or SNPN ID is the home domain of the SUCI. This information is transparently transferred from 5G RG to AUSF via the W-AGF and the AMF; it ensures the AUSF and the 5G RG consider the same information for Key derivations defined in TS 33.501 [11].
NOTE 2: The steps from 1 to 3 depend on BBF decision for what protocols to use for NAS transport. The step needs to be revised based on their decision.
4. The W-AGF shall select an AMF based on the received AN parameters and local policy, as specified in clause 6.3.5 of TS 23.501 [2]. The W-AGF shall then forward the Registration Request received from the UE to the selected AMF within an N2 initial UE message (NAS message, ULI, Establishment cause, UE context request, selected PLMN or SNPN ID).
5. The selected AMF may decide to request the SUCI by sending a N2 Downlink NAS transport message (NAS Identity Request) message to W-AGF. This NAS message and the response are sent between W-AGF and 5G-RG as described in BBF TR-456 [43] and CableLabs WR‑TR‑5WWC‑ARCH [27]. In this case the RG shall answer with a NAS Identity response.
6. The AMF may decide to authenticate the 5G-RG by invoking an AUSF. In this case, the AMF shall select an AUSF as specified in TS 23.501 [2] clause 6.3.4 based on SUPI or SUCI. As defined in 33.501 [11], the AMF transfers the SUCI and the selected PLMN or SNPN ID to the AUSF.
The AUSF executes the authentication of the UE as specified in TS 33.501 [11]. The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data from UDM. The authentication packets are encapsulated within NAS authentication messages. Between W-AGF and AMF, the messages are encapsulated within N2 downlink/uplink NAS transport messages. After the successful authentication the AUSF provides relevant security related information to the AMF. If the AMF provided a SUCI to AUSF, the AUSF shall return the SUPI to AMF only after the authentication is successful.
The AMF decides if the Registration Request needs to be rerouted as described in clause TS 23.502 [3] clause 4.2.2.2.3, where the initial AMF refers to the AMF.
7a. If NAS security context does not exist, the NAS security initiation is performed as described in TS 33.501 [11]: the AMF initiates NAS Security Mode command. If the 5G-RG had no NAS security context in step 1, the UE includes the full Registration Request message as defined in TS 24.501 [22]. If an EAP-AKA' authentication was successfully executed in step 6, the AMF shall encapsulate the EAP-Success received from AUSF within the NAS Security Mode Command message. The message is encapsulated within a N2 downlink NAS transport message.
The AMF initiates a NGAP/N2 procedure to provide the 5G-AN with security context as specified in TS 38.413 [23].
7b. The W-AGF shall forward the NAS Security Mode Command message to 5G-RG.
7c. The 5G-RG completes the authentication procedure (if initiated in step 6), creates a NAS security context as defined in TS 33.501 [11] and sends the NAS Security Mode Complete message (IMEISV) to the AMF.
7d. The W-AGF relays the NAS Security Mode Complete message to the AMF in a N2 Uplink NAS transport message.
8. [Conditional] The AMF may request the PEI from the 5G-RG as described in clause 4.2.2.2.2, step 11 of TS 23.502 [3].
9. The AMF performs step 12-16 in TS 23.502 [3] clause 4.2.2.2.2. At AMF registration to UDM for the 5G-RG, the Access Type non-3GPP access is used. The RAT type used toward PCF and UDM shall indicate wireline access. The AMF determines Access Type and RAT Type based on the Global RAN Node ID associated with the N2 interface.
10. The AMF sends an N2 Initial Context Setup Request message as defined in TS 38.413 [23] and TS 29.413 [42] possibly including as additional W-AGF specific parameter the RG Level Wireline Access Characteristics.
11a. Void.
11b. Void.
12. W-AGF notifies the AMF that the 5G-RG context was created by sending a N2 Initial Context Setup Response.
13. The AMF sends N2 Downlink NAS transport with the NAS Registration Accept message (as defined in step 21 TS 23.502 [3] clause 4.2.2.2.2) to the W-AGF, which forwards the NAS Registration accept message to the 5G-RG.
14. [Conditional] The 5G-RG responds with NAS Registration Complete message as described in TS 23.502 [3] clause 4.2.2.2.2 step 22 and W-AGF forwards the NAS Registration Complete message to AMF in a N2 Uplink NAS transport message. The N2 Uplink NAS transport message to AMF may contain W-AGF identities. The AMF stores the received W-AGF identities in the UE context.
NOTE 3: The W-AGF identities contains a list of Identifiers (i.e. a list of FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF as input to select an UPF during PDU Session Establishment, as described in clauses 7.3.1.1 and 7.3.4.
15. The AMF performs step 23-24 in TS 23.502 [3] clause 4.2.2.2.2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.1.2 5G-RG Deregistration via W-5GAN
|
Figure 7.2.1.2-1: 5G-RG Deregistration procedure via W-5GAN
1. The Deregistration procedure is triggered by one of the events:
1a. For 5G-RG-initiated Deregistration as in Figure 4.2.2.3.2-1, steps 1 to 7 of TS 23.502 [3].
1b. For network initiated deregistration as in Figure 4.2.2.3.3-1, steps 1 to 6 of TS 23.502 [3].
If the 5G-RG is in CM-CONNECTED state either in 3GPP access, W-5GAN access or both:
- the AMF may explicitly deregister the 5G-RG by sending a Deregistration request message (Deregistration type, access type set to -W-5GAN) to the 5G-RG as in Figure 4.2.2.3.3-1, step 2 of TS 23.502 [3]. The 5G-RG will interpret access type set to non-3GPP as referring to wireline access.
- the UDM may want to request the deletion of the subscribers RM contexts and PDU Sessions with the reason for removal set to subscription withdrawn to the registered AMF as in Figure 4.2.2.3.3-1, step 1 of TS 23.502 [3].
2. AMF to W-AGF: The AMF sends a N2 UE Context Release Command message to the W-AGF with the cause set to Deregistration to release N2 signalling as defined in clause 4.12.4.2, step 4 of TS 23.502 [3].
3. The W-AGF may initiate the release of the signalling connection between 5G-RG and W-AGF.
NOTE: Whether this step is needed, and if so, the details of this step is defined by BBF.
4. W-AGF to AMF: The W-AGF acknowledges the N2 UE Context Release Command message by sending N2 UE Context Release Complete message to the AMF as defined in clause 4.12.4.2, step 7 of TS 23.502 [3].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.1.3 FN-RG Registration via W-5GAN
|
The FN-RG registration management procedures are followed for both W-5GBAN and W-5GCAN. The FN-RG does not support N1 but instead the W-AGF handles the NAS signalling on behalf of the FN-RG as defined by BBF TR-456 [9] and WT-457 [10] for FN-BRG and by WT-TR-5WWC-ARCH [27] for FN-CRG.
When the connectivity is established between the FN-RG and the W-AGF in the W-5GAN, the W-AGF may authenticate the FN-RG; this is controlled by local policies and defined in BBF specifications. Then when the RM state of the FN-RG is "RM-DEREGISTERED" the W-AGF shall perform registration to 5GC as described in this clause, otherwise it performs Service Request as defined in clause 7.2.2.
Once the FN-RG is in RM-REGISTERED and CM-CONNECTED the W-AGF may setup PDU session(s) on behalf of the FN-RG (as described in clause 7.3.4).
Figure 7.2.1.3-1: FN-RG Registration via W-5GAN
1. The FN-RG connects to a W-AGF (W-5GAN) via a layer-2 (L2) connection, based on Wireline AN specific procedure.
The FN-RG is authenticated by the W-5GAN based on Wireline AN specific mechanisms.
2. W-AGF selects an AMF based on the AN parameters and local policy. W-AGF may use the Line ID / HFC identifier provided from the Wireline AN to determine the 5GC and AN parameters to be used for the FN-RG registration. How the W-AGF can determine the necessary 5GC and AN parameters is defined in BBF TR-456 [9], WT-457 [10] or CableLabs WR-TR-5WWC-ARCH [27].
3. W-AGF performs initial registration on behalf of the FN-RG to the 5GC. The W-AGF sends a Registration Request to the selected AMF within an N2 initial UE message (NAS Registration Request, ULI, Establishment cause, UE context request, Allowed NSSAI, Authenticated Indication).
The NAS Registration Request contains the SUCI or 5G-GUTI of the FN-RG, security parameters/UE security capability, UE MM Core Network Capability, PDU Session Status, Follow-on request, Requested NSSAI. The 5G-GUTI, if available, has been received from the AMF during a previous registration and stored in W-AGF.
The NSSAI parameters are provided based on W-AGF configuration. Based on W-AGF configuration of the 5GC NAS parameters, one or multiple Requested S-NSSAI may be used; e.g. when the W-AGF has been configured to use a specific slice for RG management purposes.
The following differences exist, compared to 5G-RG case:
- The W-AGF use SUCI as defined in clause 4.7.3 and clause 4.7.4.
- The Authenticated Indication indicates to AMF and 5GC that the FN-RG has been authenticated by the access network.
The SUCI is built by the W-AGF based on:
- In the case of a BBF access: the GLI as defined in clause 4.7.8 together with an identifier of the Home network as described in TS 23.003 [14].
- In the case of a Cable access: the GCI as defined in clause 4.7.8 together with an identifier of the Home network as described in TS 23.003 [14].
NOTE 1: Further description for how W-AGF obtain parameters required in AS and NAS message e.g. to build the SUCI is defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27].
4 If the AMF receives a SUCI, the AMF shall select an AUSF as specified in TS 23.501 [2] clause 6.3.4 based on SUCI. If 5G-GUTI is provided, there is no need to map SUCI to SUPI and steps 5-9 can be skipped.
5. AMF sends an authentication request to the AUSF in the form of, Nausf_UEAuthentication_Authenticate. It contains the SUCI of the FN-RG. It also contains an indication that the W-5GAN has authenticated the FN-RG.
6. AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and sends a Nudm_UEAuthentication_Get Request to the UDM. It contains the SUCI of the FN-RG and indication that the W-5GAN has authenticated the FN-RG.
7. UDM invokes the SIDF to map the SUCI to a SUPI.
8. UDM sends a Nudm_UEAuthentication_Get Response to the AUSF. It contains the SUPI corresponding to the SUCI. It also contains an indication that authentication is not required for the FN-RG.
9. AUSF sends a Nausf_UEAuthentication_Authenticate Response to the AMF. This response from AUSF indicates that authentication is successful. The response contains the SUPI corresponding to the SUCI.
The procedure described in TS 23.502 [3] clause 4.2.2.2.3 may apply (the AMF decides if the Registration Request needs to be rerouted, where the initial AMF refers to the AMF).
10a. AMF initiates a NAS security mode command procedure upon successful authentication as defined in TS 33.501 [11].
The NAS security mode command is sent from the AMF to the W-AGF in a N2 Downlink NAS transport message.
10b. W-AGF responds to the AMF with a NAS Security Mode Complete message in a N2 Uplink NAS transport message. A NAS security context is created between W-AGF and AMF.
11. The AMF performs steps 11-16 in TS 23.502 [3] clause 4.2.2.2.2.
The AMF may be configured by local policies to issue EIR check:
- Only if the PEI is an IMEI; or
- Only if the PEI is an IMEI or a user device trusted MAC address.
These local policies may be defined on a per RAT Type basis.
At FN-RG registration to UDM, the Access Type non-3GPP access is used. The UDM, based on Access and Mobility Subscription information authorizes the FN-RG to access the 5GC. For FN-CRG, the AMF compares the list of serving area restrictions it receives from the UDM against the ULI from the W-AGF to check if the location information is allowed for the FN-CRG, as defined in clause 9.5.1. The AMF may also interact with the PCF for obtaining the Access and Mobility policy for the FN-RG.
12a. Upon receiving NAS Security Mode Complete, the AMF shall send an N2 Initial Context Setup Request message as defined in TS 38.413 [23] and TS 29.413 [42] including possibly as additional W-AGF specific parameter the RG Level Wireline Access Characteristics to the W-AGF.
12b W-AGF notifies to the AMF that the FN-RG context was created by sending a N2 Initial Context Setup Response.
13. The AMF sends the N2 Downlink NAS transport with NAS Registration Accept message (5GS registration result, 5G-GUTI, Equivalent PLMNs or SNPNs, Non-3GPP TAI, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, network slicing indication, Non-3GPP de-registration timer value, Emergency number lists, SOR transport container, NSSAI inclusion mode) to the W-AGF.
The following parameters are ignored by the W-AGF if received from the AMF: Emergency number lists, SOR transport container, NSSAI inclusion mode.
NOTE 2: Further description on how W-AGF handles the parameters received from 5GC is provided in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27].
14. The W-AGF sends a N2 Uplink NAS transport message, including a NAS Registration Complete message, back to the AMF when the procedure is completed. The W-AGF shall store the 5G-GUTI to be able to send it in potential later NAS procedures.
15. The AMF performs step 23-24 in TS 23.502 [3] clause 4.2.2.2.2.
The W-AGF may continue by establishing PDU session(s) on behalf of the FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.1.4 FN-RG Deregistration via W-5GAN
|
The deregistration procedure for the FN-RG is similar to that of 5G-RG described in clause 7.2.1.2 but with the following differences:
- The 5G-RG is replaced with a FN-RG.
- In step 1a and 1b, the W-AGF sends and receives NAS deregistration request/accept messages on behalf of FN-RG.
- UE-initiated deregistration procedure can be initiated by the W-AGF, when it has lost connectivity to the FN-RG.
- For both UE/Network-initiated deregistration procedures, the W-AGF may initiate the release of the signalling connection between the FN-RG and W-AGF based on legacy protocols.
NOTE: As described in clause 6.2.2, the message exchanges between the FN-RG and W-AGF are based on legacy protocols in the wireline access network.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.2 Service Request procedures
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.2.1 5G-RG Service Request procedure via W-5GAN Access
|
The Service Request procedure via W-5GAN shall be used by a 5G-RG in CM-IDLE state over W-5GAN to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access.
NOTE 1: For a W-5GAN access, the Service Request procedure is never a response to a Paging i.e. Paging does not apply on a W-5GAN access.
The Service Request procedure via W-5GAN shall be used by a 5G-RG in CM-CONNECTED state over wireline access to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access.
Figure 7.2.2.1-1: 5G-RG Triggered Service Request procedure via W-5GAN
1. The 5G-RG connects to a W-5GAN as described in step 1 of Figure 7.2.1.1-1.
2. Void.
3. The 5G-RG using W-CP protocol stack sends a message that contains the Access Network parameters (GUAMI and Establishment Cause) and a NAS Service Request message (List Of PDU Sessions To Be Activated, security parameters, PDU Session status, Uplink Data Status, 5G-S-TMSI). The Establishment cause provides the reason for requesting a signalling connection with 5GC. In this release of the specification no Selected PLMN or SNPN parameter is sent by a 5G RG.
4. The W-AGF shall then forward the Service Request received from the 5G-RG to the selected AMF within an N2 initial UE message (NAS Service Request message, User Location Information, Establishment cause, UE context request).
5. The AMF may initiate NAS authentication/security procedure as defined in step 6 and step 7 in clause 7.2.1.1.
If the UE in CM-IDLE state triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the UE and the network can exchange NAS signalling and steps 6 and 14 are skipped.
6. Steps 4-11 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU session user plane.
For each QoS Flow, the SMF may request the following to the W-AGF:
- ECN marking for L4S at W-AGF in the case of ECN marking for L4S in non-3GPP access as described in clause 5.37.3 of TS 23.501 [2].
7. (If the 5G RG was CM-IDLE) AMF sends an N2 Initial Context Setup Request message (N2 SM information received from SMF(s), RG Level Wireline Access Characteristics, GUAMI, Allowed NSSAI, UE security capability, Security Key, Trace Activation, Masked IMEISV).
If the 5G RG was CM-CONNECTED the AMF sends N2 SM information received from SMF(s).
The W-AGF ignores any UE security capability received in a N2 Initial Context Setup Request message.
NOTE 2: The UE Security Capability IE is mandatory in NGAP protocol, but it is not applicable to wireline access, so the AMF can provide any value and the W-AGF ignores it.
8. Void.
9. [Conditional, if the 5G RG was CM-IDLE] A signalling connection using W-CP protocol stack is established between the 5G-RG and W-AGF.
NOTE 3: Steps 9-11 are defined by BBF/CableLabs.
Steps 10 and 11 are carried out for each PDU Session indicated in step 7
10. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session.
11. The W-AGF sets up the W-UP resources for the PDU session. This step is specified by BBF for W-5BGAN and by CableLabs for W-5GCAN. The access dependent W-UP resource setup procedure shall map to the identity of the PDU Session associated with the W-UP resource.
12. W-AGF notifies the AMF that the 5G-RG context was created by sending a N2 Initial Context Setup Response (N2 SM information that provides AN Tunnel Info, List of accepted QoS Flows, List of rejected QoS Flows per PDU Session ID for PDU Sessions whose UP connections are activated, established QoS Flows status (active/not active) of ECN marking for L4S at W-AGF).
13. AMF sends NAS Service Accept via W-AGF to the 5G-RG.
14. All steps after step 14 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU Session user plane.
When the 5G-RG is in CM-CONNECTED state over W-5GAN access and the network receives downlink data for a PDU Session over wireline access that has no user plane connection, the steps 1-4a in clause 4.2.3.3 of TS 23.502 [3] (Network Triggered Service Request) shall be performed with the following exceptions:
- The (R)AN corresponds to an W-AGF.
- The UE corresponds to the 5G-RG.
- In step 4a of TS 23.502 [3] clause 4.2.3.3, the steps 2b-6 in figure 7.3.1.1-1 are performed to establish the W-UP resources and to establish N3 tunnel. In steps 2b and 6, no NAS message is exchanged with the UE.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.2.2 FN-RG Service Request procedure via W-5GAN Access
|
The Service Request procedure via W-5GAN shall be used by a W-AGF when the CM state in W-AGF for a FN-RG is CM-IDLE over W-5GAN to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access.
The Service Request procedure via W-5GAN shall be used by a W-AGF when the CM state in W-AGF for a FN-RG is CM-CONNECTED over wireline access to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access.
Figure 7.2.2.2-1: FN-RG Service Request procedure via W-5GAN
1. If the FN-RG has lost the L2 connection with W-AGF, the FN-RG connects to a W-AGF (W-5GAN) via a layer-2 (L2) connection, based on Wireline AN specific procedure.
2. If step 1 was done, the FN-RG may be authenticated by the W-5GAN based on Wireline AN specific procedure.
3. The W-AGF shall then send a Service Request to the selected AMF within an N2 initial UE message (NAS Service Request message, User Location Information, Establishment cause, UE context request, Auth_Indicate).
4. The AMF may initiate NAS authentication/security procedure as defined in steps 5-10 in clause 7.2.1.3.
If the W-AGF triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the W-AGF and the network can exchange NAS signalling and steps 5 and 10 are skipped.
5. Steps 4-11 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU session user plane.
6. (If the FN-RG CM state was CM-IDLE) AMF sends an N2 Initial Context Setup Request message (N2 SM information received from SMF(s), RG Level Wireline Access Characteristics, GUAMI, Allowed NSSAI, UE security capability, Security Key, Trace Activation, Masked IMEISV).
If the FN-RG CM state in W-AGF was CM-CONNECTED the AMF sends N2 SM information received from SMF(s).
The W-AGF ignores any UE security capability received in a N2 Initial Context Setup Request message.
NOTE: The UE Security Capability IE is mandatory in NGAP protocol, but it is not applicable to a wireline access, so the AMF can provide any value and the W-AGF ignores it.
Step 7 is carried out for each PDU Session indicated in step 6.
7. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session.
The W-AGF may perform BBF specific resource reservation with the AN, that is, it sets up the L-W-UP resources for the PDU session. This step is specified by BBF for W-5GBAN and by CableLabs for W-5GCAN.
8. W-AGF notifies the AMF that the FN-RG context in W-AGF was created by sending a N2 Initial Context Setup Response (N2 SM information that provides AN Tunnel Info, List of accepted QoS Flows, List of rejected QoS Flows per PDU Session ID for PDU Sessions whose UP connections are activated).
9. AMF sends NAS Service Accept to W-AGF.
10. All steps after step 14 in figure 4.2.3.2-1 of TS 23.502 [3] are performed for each requested PDU session user plane.
When the FN-RG CM state in W-AGF is CM-CONNECTED over W-5GAN access and the network receives downlink data for a PDU Session over wireline access that has no user plane connection, the steps 1-4a in clause 4.2.3.3 of TS 23.502 [3] (Network Triggered Service Request) shall be performed with the following exceptions:
- The (R)AN corresponds to an W-AGF.
- The UE corresponds to the FN-RG.
- In step 4a, the steps 6-10 in figure 7.2.2.2-1 are performed to establish the L-W-UP resources and to establish N3 tunnel. In step 6, the AMF does not send the NAS Service Accept message to the UE.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.3 5G-RG and FN-RG Configuration Update
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.3.0 General
|
This clause specifies delta for Configuration Update procedure defined in TS 23.502 [3] clause 4.2.4 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.3.1 5G-RG Configuration Update via W-5GAN Access
|
The 5G-RG Configuration Update procedures via W-5GAN may be used by the network at any time to update 5G-RG configuration which includes:
- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs.
- 5G-RG Policy (i.e. URSP) provided by the PCF.
The procedure described in TS 23.502 [3] clause 4.2.4.2 is used for the AMF to change the 5G-RG configuration for access and mobility management related parameters, with the following differences:
- The UE is replaced by the 5G-RG.
- The (R)AN corresponds to the W-5GAN.
Figure 7.2.3.1-1: 5G-RG Configuration Update procedure for access and mobility management related parameters
In Step 0, the AMF determines the necessity of 5G-RG configuration change due to various reasons, but UE mobility change is not applicable in this release of specification. If a 5G-RG is in CM-IDLE, the AMF can wait until the 5G-RG is in CM-CONNECTED state as Network Triggered Service Request is not applicable.
In step 1, the AMF sends UE Configuration Update Command to the 5G-RG. The following parameters are not included: Mapping Of Allowed NSSAI, Configured NSSAI for the Serving PLMN or SNPN, Mapping Of Configured NSSAI, MICO, Operator-defined access category definitions, SMS Subscribed Indication.
Step 2c is not applicable in this procedure.
Step 3a is not applicable since it is only for NAS parameters that can be updated without transition from CM-IDLE are included, e.g. MICO mode.
The procedure for UE Configuration Update procedure for transparent UE Policy delivery described in TS 23.502 [3] clause 4.2.4.3 is used for the PCF to change or provide new 5G-RG policies in the 5G-RG, with the following differences:
- The UE is replaced by the 5G-RG.
- The (R)AN corresponds to the W-5GAN.
- The means for carrying NAS messages between 5G-RG and W-AGF within the W-GAN are to be defined by BBF.
- Step 2 is not applicable since the Network Triggered Service Request is not applicable in the case of W-5GAN.
Figure 7.2.3.1-2: 5G-RG Configuration Update procedure for transparent UE Policy delivery
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.3.2 FN-RG related Configuration Update via W-5GAN Access
|
The FN-RG related Configuration Update procedures via W-5GAN may be used by the network at any time to update FN-RG configuration in W-AGF which includes:
- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs.
- FN-RG related Policy (i.e. URSP) provided by the PCF.
The W-AGF acts as an N1 termination point on behalf of FN-RG. Therefore, the configuration update procedures described in clause 7.2.3.1, shown in figure 7.2.3.1-1, apply to the FN-RG, with the following additional differences:
- The 5G-RG is replaced by the W-AGF which is acting as a UE towards the 5GC on behalf of the FN-RG.
- In step 1 the AMF sends the UE Configuration Update Command to the FN-RG, which is received by the W-AGF terminating the N1 and acting as a UE on behalf of the FN-RG. The W-AGF stores the UE Configuration as defined in clause 9.4. If requested by the AMF, the W-AGF shall acknowledge the UE Configuration Update Command.
- Step 2d is not applicable.
- When requested by the AMF, in step 4 the W-AGF starts the registration procedure described in clause 7.2.1.3.
- The Emergency service is not applicable.
Figure 7.2.3.2-1: FN-RG related Configuration Update procedure for access and mobility management related parameters
The procedure of UE Configuration Update procedure for transparent UE Policy delivery described in TS 23.502 [3] clause 4.2.4.3 is used by the PCF to change or provide new FN-RG policies in the W-AGF, with the following differences:
- The UE is replaced by the W-AGF which is acting as a UE towards the 5GC on behalf of the FN-RG.
- The (R)AN corresponds to the W-5GAN.
- The FN-RG is only registered over W-5GAN.
- Step 2 is not applicable since the Network Triggered Service Request is not applicable in the case of W-5GAN.
- In step 3, the W-AGF receives the delivery of UE policies on behalf of FN-RG.
- The FN-RG policies are managed by W-AGF as defined in clause 9.5.2.2.
How the W-5GAN applies the configuration update to the wireline network is to be defined by the BBF for the FN-BRG and by CableLabs for the FN-CRG.
The operator may configure the W-AGF locally by provisioning means not specified by 3GPP as an alternative to the Configuration Update procedure for UE Policy delivery. The 3GPP Configuration Update will take precedence over a locally configured policy for FN-BRGs or FN-CRGs being serviced by the 5GC.
Figure 7.2.3.2-2: FN-RG related Configuration Update procedure for transparent UE Policy delivery
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.4 Reachability procedures
|
The procedures described in TS 23.502 [3] clause 4.2.5 are not applicable for 5G-RG and FN-RG access via W-5GAN.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.5 AN Release
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.5.1 General
|
The AN Release procedure via W-5GAN access is used by the W-5GAN or the AMF to release the logical NG-AP signalling connection and the associated N3 User Plane connections between the W-5GAN and the 5GC.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.5.2 5G-RG AN Release via W-5GAN
|
The procedure will move the 5G-RG from CM-CONNECTED to CM-IDLE in AMF, and all 5G-RG related context information is deleted in the W-AGF.
Both W-AGF initiated and AMF-initiated AN release in the W-5GAN procedures are shown in Figure 7.2.5-1.
Figure 7.2.5-1: 5G-RG AN release in the W-AGF
1 The 5G-RG has already registered in the 5GC and may have established one or multiple PDU Sessions.
2. The W-AGF detects that the 5G-RG is not reachable.
3. The W-AGF sends a N2 UE Context Release Request message to the AMF This step is equivalent to step 1b of Figure 4.2.6-1 in TS 23.502 [3].
NOTE 1: The triggers for W-AGF to send UE Context Release Request are defined by BBF in [9] and in CableLabs WR-TR-5WWC-ARCH [27] and may e.g. include events where W-AGF has lost of synchronisation of physical link, loss of PPPoE session, or detects that the RG has been replaced.
NOTE 2: AN Release procedure can also be triggered by an AMF internal event and in that case step 2 and step 3 do not take place.
4. AMF to W-AGF: If the AMF receives the N2 UE Context Release Request from W-AGF or if due to an internal AMF event the AMF wants to release N2 signalling, the AMF sends an N2 UE Context Release Command (Cause) to the W-AGF. The cause indicated is cause from step 3 or a cause due to internal AMF event. This step is equivalent to step 2 in Figure 4.2.6-1 of TS 23.502 [3].
5. If the W-CP signalling connection and W-UP resources has not been released yet, the W-AGF releases the W-CP connection and W-UP resources with a procedure out of scope of 3GPP. The W-AGF sends to the 5G-RG the indication of the release reason if received in step 4.
6. W-AGF to AMF: The W-AGF confirms the release of the 5G-RG-associated N2-logical connection by returning N2 UE Context Release Complete (list of PDU Session ID(s) with active N3 user plane) to the AMF as in step 4 defined in clause 4.2.6 of TS 23.502 [3]. The AMF marks the 5G-RG as CM-IDLE state in non-3GPP access.
7. For each of the PDU Sessions in the N2 UE Context Release Complete, the steps 5 to 7 in TS 23.502 [3] clause 4.2.6 are performed (PDU Session Update SM Context). After the AMF receives the Nsmf_PDUSession_UpdateSMContext Response as in step 7 of TS 23.502 [3] clause 4.2.6, the AMF considers the N3 connection as released. If list of PDU Session ID(s) with active N3 user plane is included in step 3, then this step is performed before step 4.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.5.3 FN-RG AN Release via W-5GAN
|
The AN release procedure for the FN-RG is similar to that of 5G-RG described in clause 7.2.5.2 but with the following differences:
- The 5G-RG is replaced with a FN-RG.
- In step 5, the W-AGF may initiate the release of the L-W-CP signalling and L-W-UP resources between the FN-RG and W-AGF based on legacy protocols.
NOTE: The message exchanges between the FN-RG and W-AGF are based on legacy protocols in the wireline access network as described in clause 6.2.2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.6 N2 procedures
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.6.0 General
|
This clause specifies delta for N2 procedures defined in TS 23.502 [3] clause 4.2.7 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.6.1 N2 procedures via W-5GAN Access
|
At power up, restart and when modifications are applied, the W-AGF node and AMF use non-UE related N2 signalling to exchange configuration data. The N2 Configuration as described in TS 23.502 [3] clause 4.2.7.1 is used with the following differences:
- The 5G-AN corresponds to the W-AGF.
The Creating NGAP UE-TNLA-bindings during Registration and Service Request procedure as described in TS 23.502 [3] clause 4.2.7.2.1 is used for 5G-RG connecting to 5GC via W-5GAN Access, with the following differences:
- The 5G-AN corresponds to the W-AGF.
- The UE corresponds to 5G-RG.
The Creating NGAP UE-TNLA-bindings during Registration and Service Request procedure as described in TS 23.502 [3] clause 4.2.7.2.1 is used for FN-RG connecting to 5GC via W-5GAN Access with the following differences:
- The 5G-AN corresponds to the W-AGF.
- The UE corresponds to W-AGF on behalf of FN-RG.
- If the W-AGF does not have any UE identities (i.e. a GUAMI or a 5G-S-TMSI) for the FN-RG, e.g. during Initial Registration procedure, the following differences are further applied:
- In step 2, the W-AGF shall handle the access specific messages received from the FN-RG as described in BBF TR456 [9] and WT-457 [10], e.g. PPPoE messages, and does not forward them to the AMF via the selected TNL association. Instead, the W-AGF shall send NAS messages on behalf of the FN-RG to the AMF via the selected TNL association.
- Step 3 can only take place during the Initial Registration procedure.
- The AMF may decide to modify the NGAP UE-TNLA-binding toward other 5G-AN nodes such as W-AGF. This is done if AMF is changed and old AMF have existing NGAP UE-TNLA-bindings toward another W-AGF.
The Creating NGAP UE-TNLA-bindings during handovers as described in TS 23.502 [3] Clause 4.2.7.2.2 is not applicable to the scenario when 5G-RG or FN-RG is access to 5GC via W-5GAN.
Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release as described in TS 23.502 [3] clause 4.2.7.2.3 is used for 5G-RG connecting to 5GC via W-5GAN Access with the following exceptions:
- The 5G-AN corresponds to the W-AGF.
- The UE corresponds to 5G-RG.
Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release as described in TS 23.502 [3] clause 4.2.7.2.3 is used for FN-RG connecting to 5GC via W-5GAN Access with the following exceptions:
- The 5G-AN corresponds to the W-AGF.
- The UE corresponds to W-AGF on behalf of FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.7 5G-RG and FN-RG Capability Match Request procedure
|
This procedure is not applicable to 5G-RG and FN-RG access via wireline access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.8 Connection, Registration and Mobility Management procedures for AUN3 devices
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.8.1 AUN3 device Registration via W-5GAN
|
An authenticable non-3GPP devices (AUN3) may get connected behind 5G-RG as defined in clause 4.10c.
This clause specifies how an AUN3 device can be registered via 5G-RG.
Figure 7.2.8.1-1: 5GC registration of AUN3 device
1. The 5G-RG registers to 5GC as specified in clause 7.2.1.1:
Any AUN3 device connection request prior to step 1 shall be rejected by the 5G-RG.
2. The AUN3 device connects to the 5G-RG via non-3GPP access network (e.g., WLAN). An authentication procedure is triggered. This can be done either by AUN3 device sending a EAPOL-start frame to the 5G-RG or 5G-RG receives a frame from an unknown MAC address. The 5G-RG receives a permanent identifier from the AUN3 device (e.g. an NAI in form of username@realm). If the realm part is different from the realm associated with the PLMN that the 5G-RG belongs to, the 5G-RG stops performing following procedure and reject the AUN3 device.
NOTE: How the 5G-RG is triggered to apply procedures for AUN3 devices is defined by BBF and/or CableLabs. For example, the realm of the NAI used by AUN3 device to contact the 5G-RG can be used as a trigger for 5G-RG to apply procedures for AUN3 devices.
3. This shall be same as step 3 of 7.2.1.1-1 with the following addition:
- W-CP AN parameters may contain an indicator that the W-CP connection is for an AUN3 device;
- The 5G-RG always provides a SUCI as AUN3 device identity information in the registration request and constructs the SUCI from the NAI received within EAP-Identity issued by the AUN3 device as defined in TS 33.501 [11];
- The 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S-NSSAI; and
- When W-AGF provides (over N2) ULI to be associated with an AUN3 device, if the AUN3 device is connected behind a 5G-BRG, the W-AGF builds the AUN3's ULI using the ULI of the 5G-BRG connecting the AUN3 device. If AUN3 device is connected behind the 5G-CRG, the W-AGF builds the ULI using the GCI and HFC node ID of the 5G-CRG connecting the AUN3 device.
4. The W-AGF selects an AMF based on the received AN parameter provided by the 5G-RG and based on local policy, as specified in clause 6.3.5 of TS 23.501 [2]. The W-AGF shall determine that a W-CP connection is for an AUN3 device and apply corresponding policies.
The W-AGF sends an NGAP INITIAL UE message to the selected AMF. For an AUN3 device, the W-AGF indicates to AMF if the N2 connection relates to an AUN3 device and if there is an existing N2 connection for a 5G-RG connected to the same GLI/GCI (where the initial NAS message related with NGAP INITIAL UE message has been received).
If the W-AGF indicated for an AUN3 device that there is no existing 5G-RG N2 connection for a 5G-RG connected to the same GLI/GCI, then the AMF rejects the registration request and further steps of this procedure are skipped. Otherwise, the procedure continues.
5. AMF selects AUSF as specified in clause 6.3.4 of TS 23.501 [2].
6. The AUSF executes the authentication of the AUN3 device following TS 33.501 [11]. The AUSF selects the UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data of the AUN3 device, from UDM. EAP based authentication defined in TS 33.501 [11] is performed between the AUSF and the AUN3 device. Once the AUN3 device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF shall return the SUPI corresponding to the AUN3 device to AMF only after the authentication is successful.
7. Same as steps 7 to 12 of figure 7.2.1.1-1 with following modifications:
- If step 7 of figure 7.2.1.1-1 is a NAS Security Mode Command, it uses NULL encryption and NULL integrity protection as described in TS 33.501 [11];
- The 5G RG uses the MAC address of the AUN3 device as a PEI.
- The AMF shall reject the registration request if the W-AGF indicates to AMF in step 4 that the N2 connection relates to an AUN3 device and the parameter "AUN3 device connectivity allowed" in the Access and Mobility Subscription Data is not present or it indicates that the device is not allowed to connect as an AUN3 device.
8. The AMF sends the Registration Accept message related to the AUN3 device to the 5G-RG. This step is executed over the NAS signalling connection and the N2 connection related to the AUN3 device.
9. The 5G-RG sends the Registration Complete message related to the AUN3 device to the AMF, when the procedure is completed. This step is executed over NAS signalling connection and N2 connection related to the AUN3 device. The 5G-RG shall store the 5G-GUTI of AUN3 device to be able to use it potential later NAS procedures related with the AUN3 device.
10. The 5G-RG receives the URSP corresponding to the AUN3 device and continues by requesting the establishment of a PDU Session on behalf of the AUN3 device as specified in clause 7.3.1.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.8.2 AUN3 device De-registration via W-5GAN
|
AUN3 device may get connected behind 5G-RG as defined in clause 4.10c. This clause specifies how an AUN3 device can be de-registered via 5G-RG.
Figure 7.2.8.2-1: De-registration of an AUN3 device
1a. The AUN3 device triggers a disconnection request to the 5G-RG.
NOTE: Detail procedures how AUN3 device triggers the de-registration request is out of scope of 3GPP.
1a. The 5G-RG sends a De-registration request on behalf of the AUN3 device. This triggers step 1a of Figure 7.2.1.2-1 with the deregistration targeting the AUN3 device and not the 5G-RG. This step is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection.
1b. The network (AMF or UDM) may determine to de-register an AUN3. This triggers step 1b of Figure 7.2.1.2-1 with the deregistration targeting the AUN3 device and not the 5G-RG.
2. AMF to W-AGF: The AMF sends a N2 UE Context Release Command message to the W-AGF as defined in step 2 of Figure 7.2.1.2-1 but for the N2 connection related with the AUN3 device. W-AGF removes W-CP AN context information for the AUN3 device.
3. As defined in step 3 of Figure 7.2.1.2-1 but for the signalling connection related with the AUN3 device.
4. The W-AGF sends a N2 UE Context Release Complete message to the AMF.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.8.3 5G-RG Deregistration via W-5GAN when it is also serving AUN3 devices
|
Figure 7.2.8.3-1: 5G-RG Deregistration procedure via W-5GAN when serving AUN3 devices
1-3. The same as steps 1-3 for Figure 7.2.1-1 with the following modification:
In the case of 5G-RG initiated deregistration, 5G-RG shall first deregister each of the registered AUN3 devices connected to it (if any) before initiating the deregistration of itself.
4. W-AGF controls if there exist any AUN3 devices connected to the 5G-RG that are registered to the 5GC through the W-AGF. If there are no AUN3 devices, then steps 5 and 6 shall be ignored.
NOTE 1: How the W-AGF temporarily maintains the mapping of AUN3 devices and 5G-RG to perform steps 5 and 6 when the 5G-RG's context is released is based on implementation.
5. [conditional] For each AUN3 device identified in step 4, the W-AGF shall send AN Release request as specified in clause 4.2.6 of TS 23.502 [3]. Here, the cause should indicate the disconnection of 5G-RG.
6. [conditional] For each AUN3 device, upon receiving the AN Release request with the cause specified in step 5, the AMF shall deregister the AUN3 device as specified in clause 4.2.2.3.3 of TS 23.502 [3] , without sending a Deregistration Request message to the 5G-RG. This deregistration involves only the 5GC and the release of the signalling connection with the W-AGF.
7. The W-AGF may initiate the release of the signalling connection between 5G-RG and W-AGF.
NOTE 2: Whether this step is needed, and if so, the details of this step are defined by BBF and/or CableLabs.
8. The 5G-RG disconnects the AUN3 device. How this is done is outside of 3GPP scope.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.2.8.4 N2 release related with a 5G-RG also serving AUN3 devices
|
When a W-AGF receives a N2 UE Context Release Command for a N2 connection related with a 5G -RG, the W-AGF identifies if there exist any AUN3 device connected to the 5G-RG through the W-AGF. For each identified AUN3 device, the W-AGF invokes step 5 and 6 of Figure 7.2.8.3-1.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3 Session Management procedures
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.0 General
|
This clause specifies the delta for Session Management procedure defined in TS 23.502 [3] clause 4.3 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.1 5G-RG Requested PDU Session Establishment via W-5GAN
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.1.1 5G-RG PDU Session establishment via W-5GAN
|
Clause 7.3.1.1 specifies how a 5G-RG can establish a PDU Session via an W-5GAN as well as to hand over an existing PDU Session between 3GPP access and W-5GAN. The procedure applies in non-roaming scenarios.
The PDU Session Establishment procedure specified in TS 23.502 [3] clause 4.3.2.2.1 applies with the following changes.
Figure 7.3.1.1-1: 5G-RG PDU Session establishment via W-5GAN
1. The 5G-RG shall send a PDU Session Establishment Request message to AMF as specified in step 1 in clause 4.3.2.2.1 of TS 23.502 [3]. This message shall be sent to W-AGF via the W-CP signalling connection and the W-AGF shall transparently forward it in a N2 Uplink NAS transport message (NAS message, User location information, W-AGF identities) to AMF in the 5GC.
The W-AGF identities parameter may be included by the W-AGF and contains a list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF in step 8 in TS 23.502 [3] clause 4.3.2.2.1 as input to select an UPF.
If the 5G-RG needs Hybrid Access with Multi-Access PDU Session service, the 5G-RG requests a MA PDU Session as defined in clause 4.12. In that case, Steps of TS 23.502 [3] clause 4.3.2.2.1 apply as modified by clause 4.12.
2a. Steps 2-11 specified in TS 23.502 [3] clause 4.3.2.2.1 are executed according to the PDU Session Establishment procedure over 3GPP access with the deviation that in step 3 an additional parameter W-AGF identities received by the AMF from the W-AGF can be sent from AMF to SMF. SMF can use W-AGF identities in step 8 of TS 23.502 [3] clause 4.3.2.2.1 for UPF selection.
For each QoS Flow, the SMF may request the following to the W-AGF and 5G-RG:
- ECN marking for L4S at W-AGF in the case of ECN marking for L4S in non-3GPP access as described in clause 5.37.3 of TS 23.501 [2].
- ECN marking for L4S at 5G-RG in UL in the case of ECN marking for L4S in non-3GPP access as described in clause 4.17.2.
For the LADN service, if the AMF detects the requested DNN is corresponding to a LADN DNN or the default DNN of the requesting S-NSSAI is a LADN DNN, and the access type of 5G-RG equals to wireline access, the AMF will assign "UE Presence in LADN service area" indication to be "OUT", and provide this indication to SMF.
NOTE: This induces the SMF to reject the PDU Session establishment request
2b. As described in steps 11 and 12 of TS 23.502 [3] clause 4.3.2.2.1, the AMF shall under request of the SMF send a N2 PDU Session Resource Setup Request message to W-AGF to establish the access resources for this PDU Session. The differences with steps 11 and 12 of TS 23.502 [3] clause 4.3.2.2.1 are:
- The W-AGF shall ignore RSN if received from 5GC.
3. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session. For example, the W-AGF may decide to establish one W-UP resource and associate all QoS profiles with this W-UP resource. In this case, all QoS Flows of the PDU Session would be transferred over one W-UP resource.
4a. The W-AGF sets up the W-UP resources for the PDU session. This step is specified by BBF for W-5BGAN and by CableLabs for W-5GCAN. The access dependent W-UP resource setup procedure shall provide the identity of the PDU Session associated with the W-UP resource. The W-UP resource setup procedure should support to bind W-UP resources to individual QFI(s) as specified in clause 4.4. The W-UP resource request may also contain other access layer information (e.g., VLAN id) specific for the W5GAN.
5. After all W-UP resources are established, the W-AGF shall forward to 5G-RG via the W-CP signalling connection the PDU Session Establishment Accept message received in step 2b.
6. The W-AGF shall send to AMF an N2 PDU Session Resource Setup Response (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s), User Plane Security Enforcement Policy Notification, established QoS Flows status (active/not active) of ECN marking for L4S at W-AGF).
7. All steps specified in TS 23.502 [3] clause 4.3.2.2.1 after step 14 are executed according to the PDU Session Establishment procedure over 3GPP access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.1.2 PDU Session Establishment with ACS Discovery
|
This clause specifies how a 5G-RG can establish a PDU Session with ACS Discovery. The ACS discovery mechanism is further specified in clause 9.6.2.
When a 5G-RG performs ACS Discovery during PDU session establishment procedure, the UE Requested PDU Session Establishment via 3GPP Access as described in TS 23.502 [3] clause 4.3.2.2.1 is used, with the following differences:
- UE is replaced by 5G-RG.
- In FWA scenario the (R)AN is replaced by NG RAN access network, in wireline scenario the (R)AN is replaced by W-5GAN and in HA scenario the (R)AN represents the selected access where the PDU session is being established.
- Step 1. When the 5G-RG sends the PDU session establishment request it includes the DNN which is corresponding to the ACS (per local configuration or per URSP policies). The UE may send in PCO a request to provide ACS information. The UE may include the ACS information request in a DHCP request sent after PDU Session has been established.
- Step 4. The UDM may send the ACS information to the SMF together with the subscription data based on the DNN.
- Step 10. The SMF includes the ACS information in the N1 SM information (PCO) if it has been requested by the UE in step 1 and if it is available at the SMF (if received in Step4).
- Step 19: The 5G-RG may request to receive ACS information via DHCP as described in clause 9.6.2.
- The 5G-RG uses the received ACS information to establish a connection with the ACS.
NOTE: The ACS discovery via PCO or via DHCP are mutually exclusive.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.2 5G-RG or Network Requested PDU Session Modification via W-5GAN
|
The UE or network requested PDU Session Modification procedure via W-5GAN access is depicted in figure 7.3.2-1. The procedure applies in non-roaming scenarios.
The procedure below is based on the PDU Session Modification procedure specified in TS 23.502 [3] clause 4.3.3.2.
Figure 7.3.2-1: 5G-RG or Network Requested PDU Session Modification via W-5GAN
1. If the PDU Session Modification procedure is initiated by the UE, the UE shall send a PDU Session Modification Request message to AMF as specified in TS 23.502 [3] step 1 of clause 4.3.2.2. The message shall be sent to W-AGF via W-CP signalling connection. The W-AGF shall transparently forward the PDU Session Modification Request to AMF/SMF.
2. The steps 1a (from AMF) to 1e and steps 2-3 as per the PDU Session Modification procedure in TS 23.502 [3] clause 4.3.3.2 are executed.
For each QoS Flow, the SMF may request the following to the W-AGF and 5G-RG:
- ECN marking for L4S at W-AGF in the case of ECN marking for L4S in non-3GPP access as described in clause 5.37.3 of TS 23.501 [2].
- ECN marking for L4S at 5G-RG in UL in the case of ECN marking for L4S in non-3GPP access as described in clause 4.17.2.
3. The AMF sends N2 PDU Session Resource Modify Request (N2 SM information received from SMF, NAS message) message to the W-AGF. This step is the same as step 4 in clause 4.3.3.2.
4. The W-AGF may issue W-CP resource modification procedure (out of scope of 3GPP) with the 5G-RG that is related with the information received from SMF. Based on the N2 SM information received from the SMF, the W-AGF may perform following:
4a. [Conditional] The W-AGF may decide to create a new W-UP resource for the new QoS Flow(s).
4b. [Conditional] The W-AGF may decide to add or remove QoS Flow(s) to/from an existing W-UP resource.
4c. [Conditional] The W-AGF may decide to delete an existing W-UP resource, e.g. when there is no QoS Flow mapped to this W-UP resource.
NOTE: If the W-AGF has included the Default W-UP resource indication during the establishment of one of the W-UP resources of the PDU Session, the W-AGF may not update the mapping between QoS Flows and W-UP resources.
5. The W-AGF acknowledges N2 PDU Session Resource Modify Request by sending a N2 PDU Session Resource Modify Response Message to the AMF to acknowledge the success or failure of the request including established QoS Flows status (active/not active) of ECN marking for L4S at W-AGF.
6. Step 7 as per the PDU Session Modification procedure in TS 23.502 [3] clause 4.3.3.2 is executed.
7. The W-AGF sends the PDU Session Modification Command to 5G-RG (if received in step 3) and receives the response message from 5G-RG.
7b. [Conditional] The 5G-RG may send the established QoS Flows status (active/not active) (ECN marking for L4S at 5G-RG) via N1 SM container.
Steps 4a/4c and step 7 may happen consecutively.
8. The W-AGF forwards the NAS message to the AMF.
9. All the steps after step 10 in TS 23.502 [3] clause 4.3.3.2 are executed according to the general PDU Session Modification procedure.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.3 5G-RG or Network Requested PDU Session Release via W-5GAN
|
Clause 7.3.3 specifies how a 5G-RG or network can release a PDU Session via a W-5GAN. The 5G-RG requested PDU Session Release procedure via W-5GAN access applies in non-roaming scenarios.
If the 5G-RG is simultaneously registered to a 3GPP access in a PLMN or SNPN different from the PLMN or SNPN of the W-AGF, the functional entities in the following procedures are located in the PLMN or SNPN of the W-AGF.
NOTE: If the 5G-RG is simultaneously registered to 3GPP access in the same PLMN or SNPN as W-5GAN access, when W-5GAN is not available to the 5G-RG (e.g. 5G-RG is disconnected from W-5GAN) or 5G-RG is in CM-IDLE for W-5GAN access, the 5G-RG may perform the PDU Session Release procedure via 3GPP access as described in TS 23.502 [3] clause 4.3.4.
Figure 7.3.3-1: 5G-RG or Network Requested PDU Session Release via W-5GAN access
1. One or more PDU Sessions are already established for the 5G-RG using the procedure described in clause 7.3.1.
2. The 5G-RG sends a PDU session release request (N1 SM container (PDU Session Release Request), PDU Session ID) to the AMF via the W-AGF as defined in clause 4.3.4 of TS 23.502 [3].
3. The steps 1a (from AMF) to 3 according to the PDU Session Release procedure defined in TS 23.502 [3] clause 4.3.4.2 are executed.
4. This step is the same as step 4 in clause 4.3.4.2 of TS 23.502 [3].
5. Upon receiving AN session release request message from the AMF, the W-AGF can trigger the release of the corresponding W-UP resource with procedure out of scope of 3GPP.
6. This step is the same as step 6 in clause 4.3.4.2 of TS 23.502 [3].
7. Step 7 according to the PDU Session Release procedure defined in clause 4.3.4.2 are executed.
8. The W-AGF delivers the NAS message (N1 SM container (PDU Session Release Command), PDU Session ID, Cause) to the 5G-RG.
9. The 5G-RG sends a NAS message (N1 SM container (PDU Session Release Ack), PDU Session ID) to the W-AGF.
10. This step is the same as step 9 in clause 4.3.4.2 of TS 23.502 [3].
Steps 5 and 8 may happen consecutively. Step 9 may happen before step 5.
11. All steps after step 9 in the PDU Session Release procedure defined in TS 23.502 [3] clause 4.3.4.2 are executed.
The network requested PDU Session Release procedure via W-5GAN access is the same as the network requested PDU Session Release Procedure specified in TS 23.502 [3] clause 4.3.4.2 for Non-Roaming with the following differences:
- The (R)AN corresponds to a W-AGF.
- In step 5, upon receiving N2 SM request to release the AN resources associated with the PDU Session from the AMF, the W-AGF can trigger the release of the corresponding W-UP resource to the 5G-RG as specified in step 5, in Figure 7.3.3-1.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.4 FN-RG related PDU Session Establishment via W-5GAN
|
The procedure below is based on the PDU Session Establishment procedure specified in TS 23.502 [3] clause 4.3.2.2.1.
Figure 7.3.4-1: FN-RG related PDU Session Establishment via W-5GAN
0. [Optional] FN-RG sends an IP address/prefix request to the W-AGF via the L2 connection established in clause 7.2.1.3.
NOTE: This IP address/prefix request can also be sent by FN-RG later in this procedure; the W-AGF may store this and complete the address allocation via 5GC after the PDU session setup. The means of carrying the IP address/prefix request/response between FN-BRG and W-AGF is defined in BBF TR-456 [9], WT-457 [10] and between FN-CRG and W-AGF is defined in CableLabes WR-TR-5WWC-ARCH [27].
1. After the registration procedure is completed, the W-AGF may establish PDU session(s) on behalf of the FN-RG. The trigger for W-AGF to initiate a PDU establishment process is defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27].
The W-AGF generates a PDU session ID and derives the parameters for the PDU Session (PDU Session type, S-NSSAI, DNN, SSC mode, etc.) based on signalling received from the FN-RG (DHCP, IPv6 RS, etc.), on local configuration, and on information received from the 5GC (e.g. during the Registration procedure or when received URSP rules) and stored on the W-AGF.
If W-AGF has received a DHCPv4/DHCPv6 request from the FN-RG, it may request a PDU Session with deferred IP address allocation.
The W-AGF sends a NAS PDU Establishment Request to the AMF. This request contains the PDU Session ID, and may contain a Requested PDU Session Type, a Requested SSC mode, 5GSM Capability PCO, SM PDU DN Request Container, Number of Packet Filters. In the case of PDU Session Type IPv6 or IPv4v6, the PDU Session Establishment Request may contain an interface identifier of the FN-RG IPv6 link local address associated with the PDU Session.
The W-AGF sends NAS PDU Establishment Request in a N2 Uplink NAS transport message (NAS message, User location information, W-AGF identities).
The W-AGF identities contains a list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF in step 8 in TS 23.502 [3] clause 4.3.2.2.1 as input to select an UPF.
2a. The PDU session request is processed in the 5GC as per steps 2-11 of TS 23.502 [3] clause 4.3.2.2.1. These steps are for UPF selection and resource reservation/allocation in the UPF. With regard to TS 23.502 [3], an additional parameter is sent from AMF to SMF i.e. the list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF received by the AMF from the W-AGF. The SMF can use it in step 8 for UPF selection as per clause 4.3.2.2.1. In the case of PDU Session Type IPv6 or IPv4v6, in step 11 of TS 23.502 [3] clause 4.3.2.2.1:
- The PDU Session Establishment Accept contains the SMF IPv6 link local address associated with the PDU Session if the RAT Type in the Nsmf_PDUSession_CreateSMContext request equals to wireline access.
- The PDU Session Establishment Accept contains the interface identifier of the FN-RG IPv6 link local address if provided in step 1. Otherwise a SMF allocated FN-RG interface identifier is provided.
2b. The SMF responds via AMF as defined in step 11 of clause 4.3.2.2.1 in TS 23.502 [3] with an N2 PDU Session Resource Setup Request that includes QoS profile(s), PDU Session ID, PDU Session Establishment Accept and the N3 tunnel endpoint information for the UPF. The differences with step 11/12 of TS 23.502 [3] clause 4.3.2.2.1 are:
- The W-AGF shall ignore RSN if received from 5GC.
3. Based on its own policies, configuration and based on the QoS flows, QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session.
The W-AGF may, as defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27], perform Access specific resource reservation with the AN, that is, it sets up the W-UP resources for the PDU session.
4. The W-AGF allocates AN N3 tunnel information for the PDU Session and includes the AN N3 tunnel endpoint information in the N2 PDU Session Resource Setup Response message to the AMF.
5. The PDU session setup procedure is completed in 5GC. All steps after step 13 as specified in TS 23.502 [3] figure 4.3.2.2.1 are executed.
6a. If W-AGF requested deferred IP address allocation in step 1 and this was accepted by the network, the W-AGF sends on the user Plane of the PDU Session any DHCP or RS message received beforehand from the FN-RG to the 5GC to obtain the IP address/prefix.
6b. W-AGF completes the IP address/prefix allocation with the FN-RG via the established L2 connection. If W-AGF did not request deferred IP address allocation in step 1a, the IP address/prefix sent back to the FN-RG is the UE IP address/prefix delivered in NAS message in step 2b. If W-AGF requested deferred IP address allocation in step 1a, the IP address/prefix sent back to the FN-RG is the UE IP address/prefix delivered via deferred IP address allocation procedures in step 6a.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.5 CN-initiated selective deactivation of UP connection of an existing PDU Session associated with W-5GAN Access
|
The procedure described in TS 23.502 [3] clause 4.3.7 (CN-initiated selective deactivation of UP connection of an existing PDU Session) is used for CN-initiated selective deactivation of UP connection for an established PDU Session associated with W-5GAN Access of a 5G-RG/FN-RG in CM-CONNECTED state, with the following exceptions:
- The NG-RAN corresponds to a W-AGF.
- The user plane resource between the 5G-RG/FN-RG and W-AGF, is released not with RRC signalling but with procedure in the scope of BBF/Cablelabs.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.6 FN-RG or Network Requested PDU Session Modification via W-5GAN
|
The PDU session modification procedure for the FN-RG is similar to that of 5G-RG described in clause 7.3.2 but with the following differences:
- The 5G-RG is replaced with an FN-RG.
- W-AGF acts on behalf of FN-RG, as an endpoint for N1 signalling. The triggers for initiating PDU Session Modification by the W-AGF are defined by BBF (BBF TR-456 [9]) and Cablelabs.
- If applicable, based on BBF specification BBF TR-456 [9] and Cablelabs specification, in step 1, the W-AGF initiates a PDU Session Modification Request to the AMF on behalf of FN-RG.
- W-AGF may issue L-W-CP resource modification procedure with the FN-RG that is related with the information received from the SMF as in step 4. The actions performed by W-AGF are defined by BBF (BBF TR-456 [9]) and Cablelabs.
- In step 4, L-W-UP resources may be modified by the W-AGF.
- Steps 7a and 7b of clause 7.3.2 are not valid for the FN-RG. The W-AGF creates an Uplink NAS transport message to the AMF, which contains the PDU Session Modification Ack as in step 8.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.7 FN-RG or Network Requested PDU Session Release via W-5GAN
|
The PDU session release procedure for the FN-RG is similar to that of 5G-RG described in clause 7.3.3 but with the following differences:
- The 5G-RG is replaced with an FN-RG.
- W-AGF acts on behalf of FN-RG, as an endpoint for N1 signalling.
- In step 2, the W-AGF sends a PDU session release request to the AMF on behalf of FN-RG.
- In step 5, upon receiving AN session release request message from the AMF, the W-AGF can trigger the release of the corresponding L-W-UP resource with procedure in scope of BBF/CableLabs.
- Steps 8 and 9 of clause 7.3.3 are not valid for the FN-RG. The W-AGF creates an Uplink NAS transport message to the AMF, which contains the PDU Session Release Ack as in step 10.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.8 Session Management Procedures for AUN3 devices
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.8.1 PDU Session Establishment of AUN3 device behind 5G-RG
|
This clause specifies the PDU Session Establishment for an AUN3 device served by a 5G-RG as defined in clause 4.10c.
A distinct PDU session is established for each AUN3 device.
After the registration from the AUN3 device, the 5G-RG initiates the establishment of a PDU Session on behalf of the AUN3 device
The PDU Session is established as specified in clause 7.3.1.1 with following differences:
- Steps 1a, 1b and 2b are executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection.
- At step 3 in figure 4.3.2.2.1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session in the Nsmf_PDUSession_CreateSMContext Request sent to the SMF.
- Steps 5 and 6 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection.
- At step 7b in figure 4.3.2.2.1 [3] of TS 23.502 [3], the SMF sends in the Npcf_SMPolicyControl_Create Request the SUPI of the PDU session (i.e. the AUN3 SUPI).
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.8.2 PDU Session Modification of AUN3 device behind 5G-RG
|
This clause specifies the PDU Session Modification for an AUN3 device served by a 5G-RG as defined in clause 4.5.3.
The PDU Session modification procedure shall use clause 7.3.2 with following differences:
- Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection.
- At step 1a in figure 4.3.3.2-1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session.
- At step 2 in figure 4.3.3.2-1 of TS 23.502 [3], the SMF sends in the Npcf_SMPolicyControl_Update Request the SUPI of the PDU session (i.e. the AUN3 SUPI).
- Steps 3 and 5 are executed over the AUN3 device's N2 connection.
- Steps 7 and 8 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection.
- Only 5GC initiated PDU Session modification is supported in this Release.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.3.8.3 PDU Session Release of AUN3 device behind 5G-RG
|
This clause specifies the PDU Session Release for an AUN3 device served by a 5G-RG as defined in clause 4.10c. This clause applies only to 5G-RG.
AUN3 device may trigger explicit request for connection release, or it may be unreachable (on the 5G-RG to AUN3 device interface). In such scenarios 5G-RG may need to release the PDU session of the AUN3 device.
NOTE: How an AUN3 device can trigger the release of a PDU Session is out of scope of 3GPP specifications.
PDU session release for a specific AUN3 device can also be initiated by the 5GC (e.g., the subscription of the AUN3 device expires).
The PDU Session release procedure shall use clause 7.3.3 with following differences:
- Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection.
In step 1a of figure 4.3.4.2-1 of TS 23.502 [3], the 5G-RG sends the PDU Session Release message on the AUN3 device's NAS connection.
- Steps 4 and 6 are executed over the AUN3 device's N2 connection.
- Steps 8-10 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.4 SMF and UPF interactions
|
SMF and UPF interactions for 5G-RG and FN-RG follow the procedures defined in TS 23.502 [3] clause 4.4.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.5 User Profile management procedures
|
When 5G-RG or FN-RG is used, the User Profile management procedures in TS 23.502 [3] clause 4.5 apply, with the differences described below:
- The UE in TS 23.502 [3] clause 4.5 is replaced by 5G-RG or FN-RG.
- When 5G-RG or FN-RG is connected via W-5GAN, steering of roaming information is not applicable, since roaming is not supported.
- The AMF updates 5G-RG context and FN-RG context stored at W-AGF to modify the RG Level Wireline Access Characteristics.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6 Handover procedure
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.1 General
|
This clause includes the differences for 5G-RG comparing to TS 23.502 [3] clause 4.9.
Handover procedures in this clause are not supported for FN-RG. SRVCC is not applicable to RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.2 Handover within NG-RAN
|
If the 5G-RG is connected via FWA, the procedures in TS 23.502 [3] clause 4.9.1 apply with the differences shown as below:
- UE is replaced by 5G-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.3 Handover procedures between 3GPP access / 5GC and W-5GAN access
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.3.1 Handover of a PDU Session procedure from W-5GAN access to 3GPP access
|
This clause specifies how to hand over a 5G-RG from a source W-5GAN access to a target 3GPP access and how a 5G-RG can handover a PDU Session from W-5GAN access to 3GPP access. It is based on the PDU Session Establishment procedure for 3GPP access as specified in clause 4.3.2 of TS 23.502 [3].
Figure 7.6.3.1-1: Handover of a PDU Session procedure from W-5GAN access to 3GPP access
The Handover of a PDU Session procedure specified in TS 23.502 [3] clause 4.9.2.1 applies with the following changes.
1-2. These steps are the same as steps 1-2 in TS 23.502 [3] clause 4.9.2.1 with the difference that the UE is replaced by 5G-RG.
3. The SMF executes the release of resources in W-5GAN access by performing steps 4 to 6 specified in clause 7.3.3, followed by step 7a specified in clause 4.3.4.2 of TS 23.502 [3] in order to release the resources over the source W-5GAN access. Because the PDU Session shall not be released, the SMF shall not send the NAS PDU Session Release Command to the 5G-RG. Hence, in steps 4 and 6 of clause 7.3.3 as well as in step 7a in clause 4.3.4.2 of TS 23.502 [3], the messages do not include the N1 SM container but only the N2 PDU Session Resource Release Command (resp. Response). Since the PDU Session is not to be released, the SMF shall not execute step 7b in clause 4.3.4.2 of TS 23.502 [3] and the SM context between the AMF and the SMF is maintained.
Steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to W-5GAN access to 3GPP access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.3.2 Handover of a PDU Session procedure from 3GPP to W-5GAN access
|
This clause specifies how to hand over a 5G-RG from a source 3GPP access to a target W-5GAN access and how a 5G-RG can handover a PDU Session from 3GPP access to W-5GAN access. It is based on the PDU Session Establishment procedure for W-5GAN access as specified in clause 7.3.1.
Figure 7.6.3.2-1: Handover of a PDU Session from 3GPP access to W-5GAN access
The Handover of a PDU Session procedure specified in TS 23.502 [3] clause 4.9.2.2 applies with the following changes.
1. If the 5G-RG is not registered via W-5GAN access, the 5G-RG shall initiate Registration procedure as defined in clause 7.2.1.1.
2. The 5G-RG performs PDU Session Establishment procedure in W-5GAN access with the PDU Session ID of the PDU Session to be moved as specified in clause 7.3.1.
3 This step is the same as step 3 in TS 23.502 [3] clause 4.9.2.2 with the difference that the UE is replaced by 5G-RG. If the User Plane of the PDU Session is already deactivated in 3GPP access, this step is skipped.
Steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to W-5GAN access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.4 Handover procedures between 3GPPaccess / EPS and W-5GAN/5GC access
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.4.1 Handover from 3GPP access / EPS to W-5GAN / 5GC
|
Figure 7.6.4.1-1: Handover from EPS to W-5GAN/5GC
The procedure specified in clause 4.11.3.1 of TS 23.502 [3] (Handover from EPS to 5GC-N3IWF) applies with the following changes.
0. Initial status: one or more PDN connections have been established in EPC between the 5G-RG and the PGW-C+SMF via E-UTRAN.
1. The 5G-RG initiates Registration procedure via W-5GAN access according to clause 7.2.1.1.
2. The 5G-RG initiates a PDU Session Establishment with Existing PDU Session indication in 5GC via W-5GAN access according to clause 7.3.1.
3. This step is the same as step 3 in clause 4.11.3.1 of TS 23.502 [3].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.6.4.2 Handover from W-5GAN / 5GC access to 3GPP-access / EPS
|
Figure 7.6.4.2-1: Handover from W-5GAN/5GC to EPS
0. Initial status: one or more PDU Sessions have been established via W-5GAN / 5GC access. During PDU Session setup, and in addition to what is specified in clause 4.3.2.2.1 of TS 23.502 [3], the PGW-C+SMF sends the FQDN related to the S5/S8 interface to the HSS+UDM which stores it.
1. If the UE is not attached to EPC/E-UTRAN, the UE initiates Handover Attach procedure in E-UTRAN as described in TS 23.401 [24] for a non-3GPP to EPS handover with "Handover" indication, except note 17.
If the UE is attached in EPC/E-UTRAN, the UE initiates the PDN Connection establishment with "Handover" indication procedure as described in TS 23.401 [24].
2. The combined PGW-C+SMF initiates a network requested PDU Session Release via W-5GAN access according to clause 7.3.3, steps 4-7 to release the 5GC and W-5GAN resources with the following exception:
- Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the SMF indicates the PDU Session is moved to another system.
- The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7 Support of specific services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.0 General
|
This clause specifies the procedure for specific services for WWC scenario defined in clause 5.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1 IPTV
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1.1 Overview
|
In this Release of the specification, in order to support IPTV services, following principles apply:
- the 5G-RG supports IP PDU Session Type;
- IP multicast traffic received from N6 interface is replicated by UPF and sent over PDU Sessions;
- IGMP or MLD messages from the STB or from the 5G-RG are terminated and managed by the UPF acting as PSA;
- IGMPv2 specified in RFC 2236 [33], IGMPv3 specified in RFC 4604 [21], for MLDv1 specified in RFC 2710 [36] and MLDv2 specified in RFC 4604 [21] are supported
NOTE 1: Whether IGMP or MLD is exchanged with 5G RG or another entity (e.g. STB) is out of the scope of 3GPP.
NOTE 2: In this specification the generic term IGMP refers to both IGMPv2 and IGMPv3 unless specifically defined. The term MLD refers to both MLDv1 and MLDV2 unless specifically defined.
NOTE 3: The IGMP "Join message" and MLD "Join message" are generic terms used in this document to indicate the request of a host to join a multicast group which can express via IGMP and MLD Report message (e.g. Membership Report) or via Join message.
- The SMF controls the support of IPTV by the UPF acting as PSA using PDR, FAR, QER, URR. This includes control of which IGMP and MLD requests the UPF is to accept or to deny.
This clause describes the procedures that support IPTV in 5G system including the procedures below:
- Registration and PDU Session Establishment procedure for IPTV is shown in clause 7.7.1.1.1. The Registration Procedure is used to register to 5GS and the PDU Session Establishment Procedure is used to establish the PDU Session used for IPTV Service.
- IPTV Access procedure shown in clause 7.7.1.1.2 may, depending on the deployment, be used to access the IPTV network, e.g. completing the IPTV Authentication and IP allocation.
- Unicast/Multicast Packets transmission procedure shown in clause 7.7.1.1.3. The procedure specifies how to transmit unicast/multicast packets related with IPTV service over 5GC.
In this Release of the specification, the 5GC does not assume any traffic replication capability in the 5G AN (NG-RAN or W-5GAN).
NOTE 4: In this release of the specification, the case of different STBs behind a 5G-RG is supported only when the STBs share the same access right.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1.1.1 Registration and PDU Session Establishment procedure for IPTV
|
5G-RG perform Registration procedure described in clause 4.2.2.2.2 of TS 23.502 [3] with the following differences:
- UE is replaced by 5G-RG.
5G-RG perform PDU Session establishment procedure described in clause 4.3.2.2.1 of TS 23.502 [3] applies with the following differences and clarifications:
- UE is replaced by 5G-RG.
- In step 1 of clause 4.3.2.2.1 of TS 23.502 [3], 5G-RG may indicate within the Protocol Configuration Options element that the UE requests to obtain the IPv4 address with DHCPv4.
- 5G-RG shall establish an IP-based PDU Session with a specific (DNN, S-NSSAI) for IPTV service.
- In step 7b and 9 of clause 4.3.2.2.1 of TS 23.502 [3], the PCF provides PCC Rules including information related to IPTV Service. This is specified in clause 9.3.1.
- The SMF sends to the UPF acting as PSA N4 rules such as PDR, FAR related to IP Multicast traffic allowed for the PDU Session. This may take place at steps 10a and 16a of clause 4.3.2.2.1 of TS 23.502 [3]. Such N4 rules are further described in clause 4.6. IP Multicast traffic allowed for the PDU Session corresponds to IPTV services allowed for the user.
NOTE: The interactions between STB and 5G-RG are specified in TR-124 [5] in BBF and not shown in this clause.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1.1.2 IPTV Access procedure
|
In the case of IPTV network access control based on the DHCP procedure, 5G-RG may be configured to retrieve via DHCP the IP address that it will use to access IPTV services. The DHCP procedure described in TS 23.501 [2] clause 5.8.2.2 is carried out with the difference shown below:
- When the SMF receives the Uplink DHCP message, the SMF may be configured to insert the IPTV access control information as received in subscription data from UDM to the uplink DHCP message.
NOTE 1: The IPTV access control information can include a line ID defined in RFC 3046 [20] or any other identity which can be used to identify the IPTV subscriber. This is based on IPTV deployment and 3GPP doesn't define the IPTV access control information that the SMF copies from subscription data to DHCP signalling.
NOTE 2: The interactions between STB and 5G-RG is specified in BBF TR-124 [5].
NOTE 3: The description of interactions among the elements part of the IPTV network is out of 3GPP scope.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1.1.3 Unicast/Multicast Packets transmission procedure
|
5GS can support Unicast Service from IPTV network directly.
In order to obtain the multicast service from IPTV network, the Multicast Packets transmission procedure should be performed. The procedure in figure 7.7.1.1-3 describes how the 5G-RG joins an IP multicast group.
Figure 7.7.1.1-3: 5G-RG join IP Multicast Packets transmission procedure
1. The 5G-RG sends an IGMP or MLD Join message via the IP PDU Session user plane.
2. When UPF receives the IGMP or MLD Join, the UPF may identify IGMP and MLD packets based on PDR received over N4 as described in clause 4.6 and handle the IGMP and MLD Join accordingly based on FAR as described in clause 4.6. An example is given as below:
- If the IP Multicast Addressing information included in the IGMP or MLD Join message is allowed to be accessed via the PDU Session , the UPF shall add the PDU Session to the requested multicast group. If requested by an URR, the UPF notifies the SMF that the UE is joining to a multicast group, providing the associated IP Multicast Addressing information.
- If the IP Multicast Addressing information included in the IGMP or MLD Join message is not allowed to be accessed via the PDU Session, the UPF shall not add the PDU Session to the requested multicast group.
The UPF acts as a Multicast Router as defined in IETF RFC 2236 [33], IETF RFC 4604 [21] and IETF RFC 2710 [36]. This may include following actions:
- if the IGMP or MLD Join message is the first IGMP or MLD request the UPF has received about the target IP multicast traffic: the UPF exchanges N6 signalling such as PIM (Protocol-Independent Multicast) in order to connect to the N6 multicast distribution tree related with this IP multicast traffic; This ensures that the UPF receives the DL multicast traffic.
- The IP multicast related signalling protocol used on N6 (e.g. Sparse Mode PIM-SM) to be supported over N6 is defined by local policies on the UPF.
2b. if the SMF had set the corresponding URR Reporting trigger with a value "IP multicast join/leave" (as defined in clause 4.6.5), the UPF issues an UPF report to the SMF and the corresponding IP Multicast addressing information
2c. if the PCF had set the corresponding Policy Control Request Trigger set to "UE join to a multicast group" trigger" (as defined in clause 9.7), the SMF issues a SMF initiated SM Policy Association Modification (as defined in TS 23.502 [3] clause 4.16.5) reporting to the PCF the corresponding IP Multicast addressing information.
3-4. When the UPF receives IP multicast packets from multicast server in IPTV network, the UPF select the PDU Session(s) where to transmit the multicast packets based on the multicast group, constructed in step 2 and fulfilling the FAR and QER rules described in clause 7.7.1.1.1.
NOTE 1: The interactions between STB and 5G-RG are specified in BBF TR-124 [5] and are not shown in figure 7.7.1.1-3.
The 5G-RG may leave the IP Multicast Group as follows:
- sending an unsolicited IGMP Leave or MLD Done message;
- IGMPv2 Leave message or a IGMPv3 Membership Report with indication of State Change Record or MLD Done message to request to leave a specific IP Multicast Group. The Message may be solicited by UPF via an IGMP MLD Query message.
NOTE 2: The Membership Query is typically used in IPTV system to recover from error conditions such as when the Leave message has been dropped by intermediate node or when the STB has been powered off without being able to send a Leave Message.
Figure 7.7.1.1-4: 5G-RG leave IP Multicast Packets transmission procedure
1a The UPF acting as a Multicast Router as defined in IETF RFC 2236 [33] and IETF RFC 3376 [28] may send an IGMP Query or an MLD Query message.
1b The 5G-RG may send a IGMP or MLD Membership Report message where the address of a IP Multicast Group is no more included in the list. This message may be the answer to the query in step 1a or it may be sent unsolicited.
1c The 5G-RG may send an IGMPv2 Leave message or a IGMPv3 Membership Report with indication of State Change Record or MLD Done message to request to leave a specific IP Multicast Group.
2 When UPF receives the IGMP or MLD message in step 1b or 1c the UPF may identify the IGMP and MLD packets based on PDR received over N4 as described in clause 4.6.3 and handle the IGMP and MLD message accordingly as below:
- If the IP Multicast Addressing information included in the IGMP or MLD Report message does not include the IP address(es) of a multicast group the UPF stop forwarding the packet to the 5G-RG.
- if the UPF receives an IGMP Leave or MLD Done message, the UPF stops forwarding multicast packets related to the IP multicast Group to the 5G-RG.
The UPF acts as a Multicast Router as defined in IETF RFC 2236 [33], IETF RFC 4604 [21] and IETF RFC 2010 [37]. This may include following actions:
- the UPF may exchange N6 signalling such as PIM (Protocol-Independent Multicast) in order to leave a IP multicast Group if no other 5G-RG are connected to the same IP multicast Group; This ensures that the UPF does no more receive the DL multicast traffic, if not needed.
- The IP multicast related signalling protocol used on N6 (e.g. Sparse Mode PIM-SM) to be supported over N6 is defined by local policies on the UPF.
3. if the SMF had set the corresponding URR Reporting trigger with a value "IP multicast join/leave" (as defined in clause 4.6.5), the UPF issues an UPF report to the SMF the corresponding IP Multicast addressing information
4. if the PCF had set the corresponding Policy Control Request Trigger set to "UE join to a multicast group" trigger", the SMF issues a SMF initiated SM Policy Association Modification (as defined in TS 23.502 [3] clause 4.16.5) reporting to the PCF the corresponding IP Multicast addressing information.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
7.7.1.1.4 AF request to provision Multicast Access Control List information into UDR
|
Figure 7.7.1.1.4: AF request to provision Multicast Access Control List information into UDR
NOTE 1: The 5GC NFs used in this scenario are assumed to all belong to the same PLMN (HPLMN).
1. To create a new request, the AF invokes an Nnef_IPTV_configuration service operation. The request contains the Multicast Access Control List, a GPSI or an External Group Id, AF Transaction Id, application identifier and may contain a DNN and/or a S-NNSAI. To update or remove an existing request, the AF invokes Nnef_IPTV_configuration_Update or Nnef_IPTV_configuration_Delete service operation providing the corresponding AF Transaction Id.
2. The AF sends its request to the NEF. The NEF ensures the necessary authorization control, including throttling of AF requests and, as described in clause 4.3.6.1 of TS 23.502 [3], mapping from the information provided by the AF into information needed by the 5GC.
3. (in the case of Nnef_IPTV_configuration_Create or Update): The NEF stores the AF request information in the UDR (Data Set = Application Data; Data Subset = IPTV_configuration, Data Key = AF Transaction Internal ID, S-NSSAI and DNN and/or SUPI/Internal-Group-Id).
(in the case of Nnef_IPTV_configuration_Delete): The NEF deletes the AF requirements in the UDR (Data Set = Application Data; Data Subset = IPTV_configuration, Data Key = AF Transaction Internal ID).
The NEF responds to the AF.
4. The PCF(s) that have subscribed to modifications of AF requests (Data Set = Application Data; Data Subset = IPTV_configuration, Data Key = SUPI/Internal-Group-Id) receive a Nudr_DM_Notify notification of data change from the UDR.
5. The PCF determines if existing PDU Sessions are potentially impacted by the AF request. For each of these PDU Sessions, the PCF updates the SMF with corresponding new PCC rule(s) by invoking Npcf_SMPolicyControl_UpdateNotify service operation as described in steps 5 and 6 in clause 4.16.5 of TS 23.502 [3].
Table 7.7.1.1.4-1 shows an example of a Multicast Access Control list provided by the AF in the IPTV domain to the NEF. The Multicast Access Control List defines the access right status (i.e. fully allowed, preview allowed, not allowed) of each of the Multicast channels per subscriber identified by a GPSI.
Table 7.7.1.1.4-1: Example of a Multicast Access Control list provided by the AF in the IPTV domain
IP Multicast Addressing information 1 (related to Channel 1)
IP Multicast Addressing information 2 (related to Channel 2)
IP Multicast Addressing information 3 (related to Channel 3)
GPSI 1
Fully allowed
Not allowed
Preview allowed
The NEF maps the GPSI into the SUPI, assigned to a 5G-RG, as described in step 2 in Figure 7.7.1.1.4-1. and stores the Multicast Access Control List in the UDR as shown in Table 7.7.1.1.4-2.
Table 7.7.1.1.4-2: Example of a Multicast Access Control list stored in UDR within the Application Data Set
DataKey
IP Multicast Addressing information 1 (related to TV Channel 1)
IP Multicast Addressing information 2 (related to TV Channel 2)
IP Multicast Addressing information 3 (related to TV Channel 3)
SUPI for 5G-RG 1
Fully allowed
Not allowed
Preview allowed
SUPI for 5G-RG 2
Fully allowed
Fully allowed
Not allowed
SUPI for 5G-RG 3
Fully allowed
Preview allowed
Preview allowed
If source Specific Multicast is to be used for a TV Channel, IP Multicast Addressing information corresponds to IP Multicast address and Source IP address.
The PCF is assumed to have subscribed to relevant modifications of that UDR data defined in the Table 7.7.1.1.4-2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8 Network Function services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.0 General
|
This clause specifies the delta related to Network Function services description defined in TS 23.502 [3] clause 5.2. For 5G RG in FWA mode TS 23.502 [3] clause 5.2 applies.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.1 UDM Services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.1.1 Nudm_SubscriberDataManagement (SDM) Service
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.1.1.1 General
|
In addition to the Subscription data types used in the Nudm_SubscriberDataManagement Service, as defined in Table 5.2.3.3.1-1 of TS 23.502 [3], the additional data types defined in Table 8.1.1.1-1 below are applicable for RGs connected to 5GC via W-5GAN and AUN3 devices .
Table 8.1.1.1-1: Wireline access specific UE Subscription data types
Subscription data type
Field
Description
Access and Mobility Subscription data (data needed for UE Registration and Mobility Management)
RG Level Wireline Access Characteristics
The RG level Wireline Access Characteristics parameter provides QoS information for the W-AGF, as defined in clause 4.5.1.2. This parameter is handled by the UDM as a transparent container. This parameter may also be provisioned in subscriptions for AUN3 devices.
AUN3 device connectivity allowed.
Indicates whether the subscriber is allowed to access as an AUN3 device. Only provisioned in subscriptions for AUN3 devices.
In the case of Wireline access, the Forbidden area information within Table 5.2.3.3.1-1 of TS 23.502 [3] may correspond to a (set of) allowed Global Line ID.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.2 Void
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.3 BSF Services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.3.1 General
|
The Nbsf_Management_Register/Deregister and Discovery service operations defined in TS 23.502 [3] are extended to allow registration/deregistration and discovery of the binding information when one or multiple /128 IPv6 address or UE IPv6 prefix shorter than /64 is/are assigned to a PDU session.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4 PCF Services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4.1 General
|
PCF services defined in TS 23.502 [3] apply with modifications described in this clause.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4.2 Npcf_SMPolicyControl
|
The Npcf_SMPolicyControl_Create and Npcf_SMPolicyControl_Update, defined in TS 23.502 [3], are extended to be able to provide PCF with one or multiple allocated /128 IPv6 UE address or with UE IPv6 prefix shorter than /64.
The Npcf_SMPolicyControl_Update, defined in TS 23.502 [3], is extended to be able to provide PCF with information on a released /128 IPv6 address or on a released UE IPv6 prefix shorter than /64.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4.3 Npcf_AMPolicyControl
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4.3.1 Npcf_AMPolicyControl_Create service operation
|
The input data listed in clause 5.2.5.2.2 in TS 23.502 [3] apply when an AM Policy Association is created for a 5G-RG, except for the handling of RFSP information that applies only if a 5G RG is registered over 3GPP access.
The input information when the UE registers via W-5GAN includes the Access type set to non-3GPP access, the User Location Information including the GLI or the HFC node Id.
The output information when the UE registers via W-5GAN is defined in clause 9.5 and the Policy Control Request triggers applicable for for RG access via W-5GAN are defined in clause 9.5.3.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.4.3.2 Npcf_AMPolicyControl_Update service operation
|
The input data listed in clause 5.2.5.2.5 in TS 23.502 [3] apply when an AM Policy Association is updated for a 5G-RG or for a FN-RG, except for the notification of UE location change (if an RG registers only on Wireline access), PRA changes or RFSP index change.
PCRT on UE location change apply when a 5G RG registers on a second access (5G RG using Hybrid access).
The output information when the UE registers via W-5GAN is defined in clause 9.5 and the Policy Control Request triggers applicable when RG accesses via W-5GAN are defined in clause 9.5.3.
The Access type change trigger requests the AMF to report a new Access Type and RAT Type to the PCF. When the UE simultaneous connects over both 3GPP and wireline non-3GPP access type, the AMF reports the list of Access Type and RAT combinations available in the UE access and mobility context in the Npcf_AMPolicyControl_Update service operation.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.5 Nnef_IPTVconfiguration service
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.5.1 General
|
Service description: This service provides:
- Request authorization of NF Service Consumer requests.
- Request parameter mapping from NF Service Consumer requests to 5GC parameters and vice versa as described in clause 7.7.1.1.x
- NF Service Consumer request configuration of Multicast Access control list as described in clause 7.7.1.1.4.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.