hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.1 General
| As described in TS 23.501 [2], 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 [2], each FN-RG or 5G-RG accessing the 5G System shall be assigned a Permanent Equipment Identifier (PEI).
The clauses below descr... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.2 SUPI and SUCI for 5G-BRG support
| For PLMNs, the SUPI for a 5G-BRG shall contain an IMSI, as described in clause 5.9.2 of TS 23.501 [2]. The SUPI for accessing SNPN is defined in clause 4.16.1.
The SUCI provided by the 5G-BRG to the network contains the concealed SUPI, as described in TS 33.501 [11].
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.3 SUPI and SUCI for FN-BRG support
| 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-AG... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 [2], 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 i... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.5 Line ID
| The Line ID is defined in BBF Specifications, see BBF TR-470 [38].
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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].
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 [2]. The 5G-RG shall present this PEI to the network independent of access technology used... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.8 Global Line Identifier
| 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.... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.10 RAT types dedicated for Wireline access
| The AMF, as described in TS 23.501 [2] 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. The RAT Type may allow to distinguish between Wireline, Wireline-Cable access andWireline-BBF access.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.7.11 SUPI and SUCI for N5GC device or AUN3 device support
| The SUPI for non-5G capable (N5GC) device or AUN3 device connecting via CRG shall contain a network-specific identifier. A SUPI containing a network-specific identifier takes the form of a Network Access Identifier (NAI) as defined in TS 23.003 [14].
The SUCI provided by the W-AGF to the AMF is derived from the EAP-Id... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.8 Security aspects
| TS 23.501 [2] 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.... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.9 Support of specific services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.9.0 General
| This clause specifies high level definition of services specific for WWC scenario.
PWS functionality as described in TS 23.041 [40] is not supported for Wireline access but may be supported by RG(s) connected over 3GPP access.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.11 Fixed Wireless Access
| For the 5G-RG connected to 5GC via NG-RAN the specifications defined TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] 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 [2], clause 5.17. This is con... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.12 Hybrid Access
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 archit... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 [2] 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.12.3 Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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.
For a 5G-RG, a Multi-Access PDU Session may use user-plane resources of an as... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.12.3.2 Void
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.12.3.3 Void
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.13 Support of FN-RG
| 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 in TS 23.501 [2]. 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 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: ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.15 Support for IMS services
| When FN RG is used, support IMS Emergency sessions without a SUPI are not supported.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.16 Access to non-public networks via wireline access network
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 t... |
fb6d29e6a362615ca2c901270a8a42ba | 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, therefor... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 4.17 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services
| |
fb6d29e6a362615ca2c901270a8a42ba | 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-5GA... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ma... |
fb6d29e6a362615ca2c901270a8a42ba | 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 (ba... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 5 Network Function
| |
fb6d29e6a362615ca2c901270a8a42ba | 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].
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 5.1 Network Function Functional description
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 L4... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 6 Control and User Plane Protocol Stacks
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 6.1 General
| This clause specifies the protocol stacks between 5G-RG, FN-RG and 5GS entities for supporting W-5GAN.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 6.2 Control Plane Protocol Stacks for W-5GAN
| |
fb6d29e6a362615ca2c901270a8a42ba | 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-... |
fb6d29e6a362615ca2c901270a8a42ba | 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]. F... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 6.3 User Plane Protocol Stacks for W-5GAN
| |
fb6d29e6a362615ca2c901270a8a42ba | 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-A... |
fb6d29e6a362615ca2c901270a8a42ba | 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 def... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7 System procedure
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.1 General
| This clause describes the differences in respect the procedures defined in TS 23.502 [3] clause 4.
|
fb6d29e6a362615ca2c901270a8a42ba | 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].
|
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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 B... |
fb6d29e6a362615ca2c901270a8a42ba | 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.50... |
fb6d29e6a362615ca2c901270a8a42ba | 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 establis... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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 numbe... |
fb6d29e6a362615ca2c901270a8a42ba | 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 p... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.2.2 Service Request procedures
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 Servic... |
fb6d29e6a362615ca2c901270a8a42ba | 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 Se... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.2.3 5G-RG and FN-RG Configuration Update
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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, ... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.2.5 AN Release
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 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-ARC... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.2.6 N2 procedures
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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-bin... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.2.8 Connection, Registration and Mobility Management procedures for AUN3 devices
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 requ... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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 initia... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.3 Session Management procedures
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.3.1 5G-RG Requested PDU Session Establishment via W-5GAN
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 c... |
fb6d29e6a362615ca2c901270a8a42ba | 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] cl... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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 func... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.3.8 Session Management Procedures for AUN3 devices
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 Ses... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ste... |
fb6d29e6a362615ca2c901270a8a42ba | 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 releas... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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 roami... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.6 Handover procedure
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.6.3 Handover procedures between 3GPP access / 5GC and W-5GAN access
| |
fb6d29e6a362615ca2c901270a8a42ba | 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: Hand... |
fb6d29e6a362615ca2c901270a8a42ba | 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 S... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.