Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.316  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   4.5…   4.7…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   10…   A…

 

4.7  Identifiers
4.7.1  General
As described in TS 23.501, each subscriber in the 5G System shall be allocated one 5G Subscription Permanent Identifier (SUPI) for use within the 3GPP system. As described in TS 23.501, each FN-RG or 5G-RG accessing the 5G System shall be assigned a Permanent Equipment Identifier (PEI).
The clauses below describe specific aspects for supporting 5G-RG and FN-RG.
4.7.2  SUPI and SUCI for 5G-BRG support
The SUPI for an 5G-BRG shall contain an IMSI, as described in TS 23.501, clause 5.9.2.
The SUCI provided by the 5G-BRG to the network contains the concealed SUPI, as described in TS 33.501.
4.7.3  SUPI and SUCI for FN-BRG supportWord-p. 20
The SUPI for an FN-BRG subscription shall, based on operator configuration, either contain an IMSI or a GLI as defined in clause 4.7.8. A SUPI containing a GLI takes the form of a NAI whose user part is the GLI and whose realm part is an identifier of the operator owning the subscription.
The SUCI provided by the W-AGF to the 5GC for FN-BRG always corresponds to a SUPI containing a GLI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the actual SUPI that, depending on operator configuration, contains either an IMSI or the same GLI that was provided in the SUCI.
As described in TS 23.003, the SUCI also contains an identifier of the Home network, i.e. the identifier of the operator owning the subscription.
Up
4.7.4  SUPI and SUCI for 5G-CRG and FN-CRG support
The SUPI for a FN-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501, or a GCI (Global Cable identifier defined in clause 4.7.9).
The SUPI for a 5G-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501, or a GCI (Global Cable identifier defined in clause 4.7.9).
Only 5G-CRG whose SUPI corresponds to an IMSI may use 3GPP access to connect to 5GC.
A SUPI containing a GCI takes the form of a NAI where the user part is the GCI and the realm part is an identifier of the operator managing the subscription.
The SUCI provided by the 5G-CRG to the network contains the concealed SUPI, as described in TS 33.501.
The SUCI provided to the network for FN-CRG support always corresponds to a SUPI containing a GCI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the SUPI that, depending on operator configuration, contains either an IMSI or the same GCI than in the SUCI.
As described in TS 23.003, for both cases where the SUCI contains an IMSI or contains a GCI, the SUCI contains an identifier of the Home network i.e. an identifier of the operator managing the subscription.
NOTE:
If the SUCI contains an IMSI, the identifier of the operator managing the subscription is carried in the MCC/MNC part of the IMSI as defined in TS 23.003.
Up
4.7.5  Line ID
The Line ID is defined in BBF Specifications, see BBF WT-470 [38].
4.7.6  HFC identifier
The HFC_Identifier may contain a cable modem MAC address or an overall HFC account identifier, as defined by CableLabs in DOCSIS MULPI [8].
4.7.7  PEI
If the 5G-RG (i.e. 5G-BRG and 5G-CRG) supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN), the 5G-RG must be allocated a Permanent Equipment Identifier (PEI) in the IMEI or IMEISV format, as described in TS 23.501. The 5G-RG shall present this PEI to the network independent of access technology used by the 5G-RG (3GPP access technology or W-5GAN access technology).
If the 5G-BRG supports only W-5GAN access, the PEI shall contain the 5G-BRG MAC address.
If the 5G-CRG supports only W-5GAN access, the PEI shall contain the cable modem MAC address.
For FN-RG (i.e. FN-BRG and FN-CRG), the W-AGF shall provide a PEI containing:
  • The FN-RG MAC address: this shall be used by the W-AGF when it is known by configuration that the MAC address received by the W-AGF is unique (no other entity can use the same MAC address) and corresponds to the permanent MAC address configured on the RG by the manufacturer.
  • NOTE 1:
    This assumes that the W-AGF can see the actual permanent MAC address of the FN-RG and not the MAC address of any intermediate entity (e.g. DSLAM).
  • The MAC address received by the W-AGF, together with an indication provided by the W-AGF that this address cannot be used as an Equipment identifier of the FN-RG: this shall be used by the W-AGF when the conditions to provide a PEI containing the FN-RG MAC address are not met.
  • NOTE 2:
    This is to support the case of legacy deployments for FN RG where either multiple FN RG can share the same MAC address or where the MAC address received by the W-AGF is not that of the FN RG but the MAC address of an intermediate entity between the FN RG and the W-AGF.
    NOTE 3:
    When the PEI contains an indication that the MAC address cannot be used as an Equipment identifier of the FN-RG, the PEI cannot be trusted for regulatory purpose but it can be stored in CDR and used for troubleshooting.
Up
4.7.8  Global Line IdentifierWord-p. 21
For usage with 5GC, a Global Line Identifier (GLI) is specified in order to define a globally unique identifier of the line connecting the RG to the network. In this release an RG is associated with a unique GLI.
For FN BRG, the GLI is used to build a SUCI. For FN-BRG the GLI may be used to build a SUPI. See clause 4.7.3. For all types of RG, the GLI is used as User Location Information on wireline access.
The GLI contains an identifier of the Line ID source and the Line ID value. The identifier of the Line ID source ensures the unicity of the GLI while the Line ID may not be unique in some deployments. The identifier of the Line ID source and Line ID are administered by the W-AGF operator.
The Global Line Identifier is a variable length identifier encoded as defined in TS 23.003 and in BBF WT 470 [38].
Up
4.7.9  Global Cable Identifier
For usage with 5GC, a Global Cable Identifier (GCI) is specified in order to define a globally unique identifier of the line connecting the CRG to the network. In this release an RG is associated with a unique GCI.
The GCI contains the HFC_Identifier which is defined in CableLabs WR-TR-5WWC-ARCH [27].
For FN CRG, the GCI is used to build a SUCI. For FN CRG the GCI may be used to build a SUPI. See clause 4.7.4. For all types of CRG the HFC Node ID is used to build User Location Information on Cable access.
The identifier of the HFC Node ID and the HFC_Identifier are administered by the W-AGF operator.
The Global Cable Identifier is a variable length identifier encoded as defined in TS 23.003 and CableLabs WR TR 5WWC ARCH [27].
Up
4.7.10  Dedicated RAT types for Wireline access
The AMF, as described in TS 23.501, clause 5.3.2.3, determines the RAT Type for Wireline access, taking into account the Global W-AGF Node ID and possibly ULI information provided by the W-AGF. This RAT Type may allow to distinguish between Wireline-Cable access, Wireline-DSL access and Wireline-PON access.
4.8  Security aspects
TS 23.501, clause 5.10 applies to the FN-CRG with the following deltas:
  • Mutual authentication of the FN-CRG and the wireline access network is completed as specified by CableLabs DOCSIS MULPI [8]. The successful completion of the authentication of the FN-CRG is conveyed by the W-AGF serving the FN-CRG to the AMF.
  • UE is replaced by W-AGF on behalf of the FN-CRG for the balance of TS 23.501, clause 5.10 and clauses.
  • See TS 33.501 for additional requirements
TS 23.501, clause 5.10 applies to the 5G-CRG with the following deltas:
  • The UE is replaced by the 5G-CRG
  • Signalling security aspects between the 5G-CRG and the W-AGF are specified by CableLabs in WR-TR-5WWC-ARCH [27].
  • See TS 33.501 for additional requirements
Up
4.9  Support of specific servicesWord-p. 22
4.9.0  General
This clause specifies high level definition of services specific for WWC scenario.
PWS functionality as described in TS 23.041 is not supported for Wireline access but may be supported by RG(s) connected over 3GPP access.
4.9.1  IPTV
IPTV is defined as multimedia services such as television/video/ audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. STB obtains IPTV service via RG, including 5G-RG and FN-RG, which are connected to 5GC.
The procedures to support IPTV is specified in clause 7.7.1.
4.10  UE behind 5G-RG and FN-RG
An RG connecting via W-5GAN or NG-RAN access towards 5GC can provide connectivity for a UE behind the RG to access an N3IWF or TNGF. It is assumed that the UE is 5GC capable, i.e. supports untrusted non-3GPP access and/or trusted non-3GPP access. This allows the RG, W-5GAN and the RG's connectivity via 5GC to together act as untrusted/trusted N3GPP access to support UEs behind the RG.
When FN-RG/5G-RG is serving a UE, the control and user plane packets of the UE is transported using a FN-RG/5G-RG IP PDU session and then from PSA UPF of that PDU session to an IWF. A single FN-RG/5G-RG IP PDU session can be used to serve multiple UEs.
Figure 4.10-1 shows the non-roaming architecture for a UE, behind a 5G-RG, accessing the 5GC via TNGF where the combination of 5G-RG, W-5GAN and UPF serving the 5G-RG is acting as a trusted Non-3GPP access network.
NOTE 1:
FN-RG and W-5GAN acting as trusted Non-3GPP access is not considered in this specification as it is assumed that FN-RG does not support EAP-based access control (e.g. 802.1X).
Up
The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via 5G-RG, NG-RAN or via both accesses.
The TNGF and Ta reference point are defined in TS 23.501.
NOTE 2:
The reference architecture in figure 4.10-1 only shows the architecture and the network functions directly connected to W-5GAN or TNGF, and other parts of the architecture are the same as defined in TS 23.501, clause 4.2.
NOTE 3:
The reference architecture in figure 4.10-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure.
NOTE 4:
The two N2 instances in Figure 4.10-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and W-5GAN.
Up
4.10a  Non-5G capable device behind 5G-CRG and FN-CRG.Word-p. 23
For isolated 5G networks (i.e. roaming is not considered) with wireline access, non-5G capable (N5GC) devices connecting via W-5GAN can be authenticated by the 5GC using EAP based authentication method(s) as defined in TS 33.501. The following call flow describes the overall registration procedure of such a device.
Roaming is not supported for N5GC devices
The usage of N5GC device correspond to a subscription record in UDM/UDR that is separate from that of the CRG.
Up
Step 1.
The W-AGF registers the FN-CRG to 5GC as specified in clause 7.2.1.3 or the 5G-CRG registers to 5GC as specified in clause 7.2.1.1.
Step 2.
The CRG is configured as L2 bridge mode and forwards any L2 frame to W-AGF. 802.1x authentication may be triggered. This can be done either by N5GC device sending a EAPOL-start frame to W-AGF or W-AGF receives a frame from an unknown MAC address.
How the CRG is configured to work in L2 bridge mode and how the W-AGF is triggered to apply procedures for N5GC devices is defined in CableLabs WR-TR-5WWC-ARCH [27].
Step 3.
W-AGF, on behalf of the N5GC device, sends a N1 Registration Request message to AMF with a device capability indicator that the device is non-5G capable. For this purpose, the W-AGF sends the NAS Registration Request message containing a SUCI, which is the same behavior as a W-AGF serving a FN-CRG as defined in TS 33.501.
Over N2 there is a separate NGAP connection per N5GC device served by the W-AGF.
When it provides (over N2) ULI to be associated with a N5GC device, the W-AGF builds the same ULI as the ULI of the CRG connecting the N5GC device (using the GCI of the CRG as defined in clause 4.7.9).
NOTE:
How the W-AGF determines the CRG connecting a N5GC device is specified in CableLabs WR-TR-5WWC-ARCH [27].
Step 4.
AMF selects a suitable AUSF as specified in TS 23.501, clause 6.3.4.
Step 5.
EAP based authentication defined in TS 33.501 is performed between the AUSF and N5GC device.
Once the N5GC device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF shall return the SUPI (this SUPI corresponds to a NAI that contains the username of the N5GC device and a realm as defined in TS 33.501) to AMF only after the authentication is successful.
NOTE:
Each N5GC device is registered to 5GC with its own unique SUPI.
Step 6.
The AMF performs other registration procedures as required (see TS 23.502, clause 4.2.2.2.2).
When providing a PEI for a N5GC device, the W-AGF shall provide a PEI containing the MAC address of the N5GC device. The W-AGF may, based on operator policy, encode the MAC address of the N5GC device using the IEEE Extended Unique Identifier EUI-64 format (see IEE Publication [41]).
Step 7.
The AMF sends Registration Accept message to W-AGF.
Once the registration procedure is completed, the W-AGF requests the establishment of a PDU Session on behalf of the N5GC device. Only one PDU session per N5GC device is supported. The procedure is the same as the PDU Session establishment procedure specified in clause 7.3.4 with the difference as below:
  • FN-RG is replaced by N5GC device.
The W-AGF shall request the release of the NGAP connection for each N5GC device served by a CRG whose NGAP connection has been released.
5G-CRG, behaves as FN-CRG (i.e. L2 bridge mode) when handling N5GC devices.
Up
4.11  Fixed Wireless AccessWord-p. 24
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 TS 23.501, clause 5.17. 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.
NOTE:
HR roaming over 3GPP access is defined for 5G_RG but in some countries it can not apply due to local regulations.
Up
4.12  Hybrid AccessWord-p. 25
4.12.1  General
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 TS 23.502, clause 4.9.2, 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 TS 23.502, clause 4.11.3, 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.
Up
4.12.2  Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN
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 TS 23.501, clause 5.33, with the following difference:
  • UE is replaced by 5G-RG.
  • Non-3GPP access(es) is specifically referred to wireline access.
Up
4.12.3  Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GANWord-p. 26
4.12.3.1  General
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.
NOTE:
Co-existence with NBIFOM is not defined. It is assumed that NBIFOM and the multi-access connectivity described in this clause are not deployed in the same network.
The use of ATSSS with EPS interworking applies to IP-based PDU Session and PDN Connection types.
For this scenario, the general principles for ATSSS as described in TS 23.501, clause 5.32 apply, with the additions provided in this clause.
A Multi-Access PDU Session may be extended with user-plane resources via 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.
NOTE:
To the MME and SGW this is a regular PDN Connection and the support for ATSSS is transparent to MME and SGW.
The 5G-RG may operate in either single-registration mode or dual-registration mode in 3GPP access. Irrespective of whether the 5G-RG operates in single-registration mode or dual-registration mode in 3GPP access, it is assumed that the 5G-RG supports simultaneous registrations for non-3GPP access in 5GC and 3GPP access in EPC.
The multi-access connectivity described in this clause supports simultaneous connectivity using 3GPP access via EPC and W-5GAN access via 5GC.
The ATSSS rules are provided from the PGW-C+SMF to the 5G-RG via SM NAS signalling over 5GC, as described in TS 23.501, clause 5.32.2. ATSSS rules are not provided via the EPC.
After the establishment of a MA PDU Session and setting up user-plane resources in 3GPP access in EPC and non-3GPP access in 5GC, the 5G-RG distributes the uplink traffic across the two access networks as described in TS 23.501, clause 5.32.1. Similarly, the PDU Session Anchor UPF performs distribution of downlink traffic across the two access networks as described in TS 23.501, clause 5.32.1.
The PMF protocol may be used via any user plane connection, i.e. via 3GPP access in EPC or non-3GPP access in 5GC.
The PCF functionality to support ATSSS, as described in TS 23.501, clause 5.32.1 and TS 23.503 applies also in the case of interworking with EPC.
Up
4.12.3.2  PDN Connections and Multi Access PDU Sessions
When the 5G-RG wants to request a new PDN Connection in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session:
  • The 5G-RG requests establishment of a new PDN Connection when the 5G-RG is registered via 3GPP access in EPS using PDN Connection Establishment procedure. The 5G-RG provides via PCO to PGW-C+SMF the following information:
    • An indication that the PDN Connection is requested to be associated with a MA PDU Session
    • The 5G-RG's ATSSS capabilities as described in TS 23.501, clause 5.32.2 (i.e. whether the 5G-RG is capable of supporting the ATSSS-LL functionality, or the MPTCP functionality, or both)
  • The MME may select a PGW-C+SMF as described in TS 23.401 and TS 23.502, clause 4.11.0a.4.
  • NOTE 1:
    The selection of PGW-C+SMF in the correct 5GC slice requires the same mapping between EPC and 5GC slices as required for single-access PDU sessions. In order to select an ATSSS capable PGW-C+SMF it is assumed that the operator deployment ensures that all PGW-C+SMF(s) configured to support the specific APN in this network slice are also capable to support ATSSS. There is however no assumption that all PGW-U+UPFs need to support ATSSS, since PGW-C+SMF can make a selection of PGW-U+UPF taking the multi-access properties into account.
  • The PGW-C+SMF determines based its capabilities whether the request can be accepted. The PCF decides whether the multi-access connectivity is allowed or not based on operator policy and subscription data, as described in TS 23.502, clause 4.22.2. The PGW-C+SMF provides the following information in the PCO to the 5G-RG:
    • An indication whether the request for using the PDN Connection for MA-PDU Session is accepted or not.
    • If the 5G-RG has indicated that it is capable of supporting the MPTCP functionality and the PGW-C+SMF accepts to activate the MPTCP functionality, then the network provides MPTCP proxy information to the 5G-RG, as described in TS 23.501, clause 5.32.2.
    • UE Measurement Assistance Information (as described in TS 23.501, clause 5.32.2).
After the PDN Connection establishment:
  • If the 5G-RG registers to 5GC and wants to add W-5GAN user-plane resources, then the 5G-RG shall send a PDU Session Establishment Request over this access containing a "MA PDU Request" indication as described in TS 23.501, clause 5.32.2.
  • NOTE 2:
    Adding the PDU Session connectivity and user plane resources over W-5GAN in 5GS allows the PGW-C+SMF to provide ATSSS rules to the UE.
When the 5G-RG wants to request a new MA PDU Session in 5GC/W-5GAN, the description in TS 23.501, clause 5.32.2, applies. After the MA PDU Session establishment in 5GS/W-5GAN, the description in TS 23.501, clause 5.32.2, applies with the following additions:
  • If the 5G-RG is registered to EPC and wants to add user-plane resources on 3GPP access over EPC, then the 5G-RG shall send a PDN Connection Establishment Request over this access containing a "handover" indication and include a "MA PDU Request" indication in the PCO.
  • When the 5G-RG deregisters from the EPC access (but remains registered on the 5GC access), the MME will notify the PGW-C+SMF that the PDN Connection is released, as described in TS 23.401. The SMF can then notify the UPF that the access type has become unavailable.
A 5G-RG that has an established MA-PDU session over non-3GPP access in 5GC and 3GPP access in EPS, may be able to use EN-DC for the 3GPP access leg.
Depending on the RAT types supported by the 5G-RG, the PDN connection may also be handed over to 3GPP access in 5GC. For a 5G-RG supporting both E-UTRAN/EPC access and NG-RAN/5GC access, the user plane resources for 3GPP access may be moved between E-UTRAN/EPC access and NG-RAN/5GC access as described in TS 23.501, clause 5.17.2. The PDU Session and User Plane resources active over W-5GAN are not affected by such inter 3GPP access RAT change.
Up
4.12.3.3  QoS SupportWord-p. 27
The general principles for QoS support with ATSSS as described in TS 23.501, clause 5.32.4, applies, with the clarifications provided in this clause.
With an MA PDU Session associated to a PDN Connection on EPS there may be separate user-plane tunnels between the AN and the PGW-U+UPF, one associated with 3GPP access in EPC and one associated with W-5GAN in 5GS.
As described in TS 23.502, clause 4.11.1.1 and Annex C, the PGW-C+SMF maps the 5G QoS information received from PCC to EPS QoS parameters. This mapping is e.g. based on operator configuration and may result in that multiple QoS flows are mapped to a single EPS bearer. The PGW-C+SMF applies the appropriate QoS signalling in each access, e.g. to manage dedicated bearers in the access associated with EPC and QoS flows in the access associated with 5GC. The PGW-C+SMF also provides N4 rules to UPF for performing QoS enforcement and for mapping downlink traffic to appropriate GTP-U tunnels.
As described in TS 23.501, clause 5.32.4, for a GBR QoS flow, the QoS profile is provided to a single access network at a given time. GBR QoS flows (and associated MBR, GBR) are thus only enforced in either the access associated to EPC or the access associated to 5GC. In order to maintain consistency between QoS information received via AS and NAS layers in each system, the PGW-C+SMF only provides the GBR QoS information to the 5G-RG for the access where the GBR traffic is enforced.
The 5G-RG shall treat the uplink traffic sent via EPC according to the EPS QoS information received in EPC (e.g. UL TFTs) and the uplink traffic sent via 5GC according to the 5G QoS rules received in 5GS. The 5G-RG thus need to determine what access to use (3GPP and on-3GPP) before applying the uplink QoS treatment.
The UPF shall treat the downlink traffic according to the N4 rules (QER, etc.) received from PGW-C+SMF.
Up
4.13  Support of FN-RGWord-p. 28
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 WT-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
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.
  • 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.
  • 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, clause 5.15.
Up
4.15  Support for IMS services
When FN RG is used, support IMS Emergency sessions without a SUPI are not supported.

Up   Top   ToC