Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.316  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.5…   4.7…   4.10…   4.10b…   4.11…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   9.5…   10…   A…   C… 
4.11 Fixed Wireless Access  4.12 Hybrid Access  4.12.1 General  4.12.2 Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN  4.12.3 Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN  4.13 Support of FN-RG  4.14 Support of slicing  4.15 Support for IMS services  4.16 Access to non-public networks via wireline access network  4.16.1 Access to SNPN services via wireline access network  4.16.2 Access to Public Network Integrated NPN services via wireline access network  4.17 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services  4.17.1 General  4.17.2 ECN marking for L4S  4.17.3 PDU Set based Handling 
...

 

4.11  Fixed Wireless Access  p. 30

For the 5G-RG connected to 5GC via NG-RAN the specifications defined TS 23.501, TS 23.502 and TS 23.503 applies with the following modification:
  • The UE corresponds to the 5G-RG.
  • The 5G-RG may support LTE access connected to EPC and EPC interworking as defined in clause 5.17 of TS 23.501. This is controlled by SMF Selection Subscription data defined in Table 5.2.3.3.1-1 of TS 23.502.
  • The configuration of 5G-RG via ACS server based on TR-069 [18] and TR-369 [19] is specified clause 9.6.
  • The Home Routing roaming is supported for 5G-RG connected via NG RAN in this release.
  • 5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 of TS 23.501
  • The LBO roaming for 5G-RG connected via NG RAN is not specified in this release.
  • The LADN service defined in clause 5.6.5 in TS 23.501 applies to the 5G-RG connected to 5GC via 3GPP access. The specification in clause 5.6.5 in TS 23.501 applies via 5G-RG replacing UE with the following difference:
    • UE Configuration Update procedure is referred to the procedures in clause 7.2.3.1.
  • If the 5G-RG is registered via both 3GPP access and W-5GAN, and the AMF has received W-AGF identities from the AGF, the AMF may provide the W-AGF identities to the SMF also when AMF forwards N1 SM container sent by the 5G-RG via 3GPP access.
Up

4.12  Hybrid Access  p. 31

4.12.1  General  p. 31

This clause specifies the support of Hybrid Access considering both the support of PDU session and MA PDU session.
Hybrid Access applies to a 5G-RG capable of connecting to both NG-RAN and to W-5GAN. Hybrid Access also applies to a 5G-RG capable of connecting to W-5GAN/5GC and E-UTRAN/EPC using EPC interworking architecture. Hybrid Access does not apply to FN-RG.
The following Hybrid Access scenarios are supported with single-access PDU sessions:
  • Hybrid Access using PDU session carried only on a single access, either NG-RAN or W-5GAN, but that cannot be simultaneously on both accesses. Such PDU Session can be handed over between NG-RAN and W-5GAN using procedures described in clause 4.9.2 of TS 23.502, but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN.
  • Hybrid Access using single access connectivity for 5G-RG supporting LTE/EPC and EPC interworking. In that case mobility between W-5GAN/5GS and E-UTRAN/EPC is handled using interworking procedures described in clause 4.11.3 of TS 23.502, but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN.
The following Hybrid Access scenarios are supported with multi-access connectivity:
  • Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN and operator-controlled traffic steering. This scenario is further detailed in clause 4.12.2.
  • Hybrid Access with simultaneous multi-access connectivity to LTE/EPC and W-5GAN/5GS using EPC interworking. This scenario is further detailed in clause 4.12.3.
In this Release of the specification, a RG that supports MA PDU Sessions and LTE/EPC access as described in clause 4.12.2, shall also support MA PDU using LTE/EPC as 3GPP access as defined in clause 4.12.3.
Up

4.12.2  Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN  p. 31

This clause applies to the case where multi-access PDU Session connectivity via NG-RAN and W-5GAN is supported in the 5G-RG and network. The Hybrid Access architecture of 5G-RG is defined in TS 23.501 in Figure 4.2.8.4-1. This scenario uses the ATSSS solution described in clause 5.33 of the Release 16 version of TS 23.501, with the following difference:
  • UE is replaced by 5G-RG.
  • Non-3GPP access(es) is specifically referred to wireline access.
The Release 17, ATSSS functionalities defined in TS 23.501, TS 23.502 and TS 23.503 are not supported, except for the feature described in clause 4.12.3.
Up

4.12.3  Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN  p. 32

4.12.3.1  General  p. 32

This clause applies to the case where multi-access connectivity via both EPC and 5GC is supported in the 5G-RG and network. In this case, multi-access connectivity using ATSSS via both EPC and 5GC may be provided as described in this clause.
For a 5G-RG, a Multi-Access PDU Session may use user-plane resources of an associated PDN Connection on 3GPP access in EPC. This enables a scenario where a MA PDU Session can simultaneously be associated with user-plane resources on 3GPP access network connected to EPC and W-5GAN connected to 5GC. Such a PDN Connection in EPS would thus be associated with multi-access capability in 5G-RG and PGW-C+SMF.
The feature is supported as defined in clause 5.32 of TS 23.501 (Release 17) and TS 23.502 (Release 17) with following differences:
  • UE is replaced by 5G-RG.
  • 5G-RG is connected to 5GC via a non-3GPP access corresponding to W-5GAN.
  • MA PDU Sessions of Ethernet PDU Session type where the 3GPP access corresponds to E-UTRAN/EPC are not applicable for 5G-RG.
Up

4.12.3.2  Void

4.12.3.3  Void

4.13  Support of FN-RG  p. 32

FN-RG is a legacy type of residential gateway that does not support N1 signalling and is not 5GC capable. The architecture to support FN-RG is depicted in clause 4.2.8.4 of TS 23.501. Support for FN-RG connectivity to 5GC is provided by means of W-AGF supporting 5G functionality on behalf of the FN-RG, e.g. UE NAS registration and session management functionality. In particular, the W-AGF supports the following functionality on behalf of the FN-RG:
  • Has access to configuration information, as defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27], to be able to serve FN-RGs and to construct AS and NAS messages.
  • Acting as end-point of N1 towards AMF, including maintaining CM and RM states and related dynamic information received from 5GC. This also includes support of URSP.
  • Mapping between Y5 towards FN-RG and N1/N2 towards 5GC as well as mapping between a Y5 user plane connection and a PDU Session user plane tunnel on N3.
Authentication of FN-RG may be done by the W-AGF, as defined by BBF and Cablelabs. The W-AGF provides an indication on N2 that the FN-RG has been authenticated. The W-AGF also provides a SUCI or a 5G-GUTI as described in TS 23.501.
Up

4.14  Support of slicing  p. 32

Slicing as defined in TS 23.501 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.
  • For 5G-RG access over 3GPP access (FWA), slicing is supported as described in TS 23.501.
  • 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 clause 5.15 of TS 23.501.
Up

4.15  Support for IMS services  p. 33

When FN RG is used, support IMS Emergency sessions without a SUPI are not supported.

4.16  Access to non-public networks via wireline access network |R18|  p. 33

4.16.1  Access to SNPN services via wireline access network  p. 33

Access to SNPN defined in clause 5.30 of TS 23.501 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 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) 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. The SUPI in NSI type may include the NID of SNPN as defined in clause 28.7.2 of TS 23.003.
  • 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. 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. 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 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 is not applicable in this Release for a RG.
Up

4.16.2  Access to Public Network Integrated NPN services via wireline access network  p. 33

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 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 where the 5G-RG replaces the UE.
Up

4.17  Support for high data rate low latency services, eXtended Reality (XR) and interactive media services |R19|  p. 34

4.17.1  General  p. 34

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 for 5GS:
Up

4.17.2  ECN marking for L4S  p. 34

In order to support ECN marking for L4S at W-AGF as specified in TS 23.501, 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 RFC 9330, RFC 9331, RFC 9332 and implement IP-in-IP encapsulation and decapsulation as specified in RFC 6040 and RFC 9599.
The criteria based on which W-AGF and 5G-RG decides to mark ECN bits for L4S is implementation specific.
Up

4.17.3  PDU Set based Handling  p. 34

PDU Set based QoS handling, as defined in clause 5.37.5 of TS 23.501, 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.
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.
Up

Up   Top   ToC