hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.3 TSC Assistance Container determination by TSCTSF | The TSCTSF constructs TSC Assistance Container (defined in Table 5.27.2-2) based on information provided (directly or via NEF) by the AF for IP or Ethernet type PDU Sessions, or by the DetNet controller for IP type PDU Sessions.
In the case of an AF request, the AF may provide Flow Direction, Burst Arrival Time (option... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.4 TSCAI determination based on TSC Assistance Container | The SMF determines the TSCAI (defined in Table 5.27.2-1) for the QoS Flow based on the TSC Assistance Container of the PCC rule bound to the QoS Flow. This clause is applicable irrespective of whether the TSC Assistance Container is determined by the TSN AF or by the TSCTSF.
The Burst Arrival Time and Periodicity compo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.5 RAN feedback for Burst Arrival Time offset and adjusted Periodicity | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.5.1 Overview | If the NG-RAN receives a TSCAI containing a BAT Window or the Capability for BAT adaptation for a QoS Flow, the NG-RAN can determine a BAT offset in order to align the arrival of the traffic bursts with the next expected transmission opportunity over the air interface in each direction (i.e. DL or UL). The BAT offset c... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.5.2 Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity | If the NG-RAN receives a Burst Arrival Time and Burst Arrival Time Window in the TSCAI for a QoS Flow, the 5GS will perform the following actions:
- The NG-RAN can determine a BAT offset in order to align the expected arrival of the traffic bursts (as indicated in the BAT) with the time when the next transmission over ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.2.5.3 Reactive RAN feedback for Burst Arrival Time adaptation | If the RAN receives the capability for BAT adaptation without a Burst Arrival Time in the TSCAI and notification control is enabled for this QoS Flow, the 5GS will perform the following actions:
- If NG-RAN determines that the PDB of the QoS flow cannot be fulfilled in DL and UL direction, then if supported, NG-RAN sha... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.3 Support for TSC QoS Flows | TSC QoS Flows use a Delay-critical GBR resource type and TSC Assistance Information. TSC QoS Flows may use standardized 5QIs, pre-configured 5QIs or dynamically assigned 5QI values (which requires signalling of QoS characteristics as part of the QoS profile) as specified in clause 5.7.2. For each instance of Periodicit... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.4 Hold and Forward Buffering mechanism | DS-TT ports and NW-TT ports support a hold and forward mechanism to schedule traffic as defined in IEEE Std 802.1Q [98] if 5GS is to participate transparently as a bridge in a TSN network. That is, the hold and forward buffering mechanism in this release of the specification provides externally observable behaviour ide... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.27.5 5G System Bridge delay | This clause applies if 5GS is integrated as a bridge into an IEEE TSN network.
In order for the 5G System to participate as a TSN bridge according to transmission gate schedules specified, the 5GS Bridge is required to provide Bridge Delays as defined in IEEE Std 802.1Q [98] for each port pair and traffic class of the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28 Support of integration with TSN, Time Sensitive Communications, Time Synchronization and Deterministic Networking | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.0 General | Clause 5.28 defines the 5GS integration in TSN DN as a 5GS bridge.
In this scenario, 5GS is deployed in a TSN DN to provide wireless connectivity. From the perspective of the TSN DN, the 5GS is modelled as a Layer 2 Ethernet Bridge of the TSN DN.
In addition to supporting interoperation with TSN, 5GS also supports Time... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.1 5GS bridge management for TSN | 5GS acts as a Layer 2 Ethernet Bridge. When integrated with IEEE TSN network, 5GS functions acts as one or more TSN Bridges of the TSN network. The 5GS Bridge is composed of the ports on a single UPF (i.e. PSA) side, the user plane tunnel between the UE and UPF and the ports on the DS-TT side. For each 5GS Bridge of a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.2 5GS Bridge configuration for TSN | The configuration information of 5GS Bridge as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], includes the following:
- Bridge ID of 5GS Bridge.
- Configuration information of scheduled traffic on ports of DS-TT and NW-TT:
- Egress ports of 5GS Bridge, e.g. ports on DS-TT and NW-TT;
- Traffic classes and their prio... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.3 Port and user plane node management information exchange in 5GS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.3.1 General | Port number for the PDU Session is assigned by the UPF during PDU session establishment. The port number for a PDU Session shall be reported to the SMF from the UPF and further stored at the SMF. The SMF provides the port number via PCF to the TSN AF or TSCTSF. TSN AF or TSCTSF maintains an association between the port... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.3.2 Transfer of port or user plane node management information | Port management information is transferred transparently via 5GS between TSN AF or TSCTSF and DS-TT or NW-TT, respectively, inside a Port Management Information Container (PMIC). User plane node management information is transferred transparently via 5GS between TSN AF or TSCTSF and NW-TT inside a user plane node Manag... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.3.3 VLAN Configuration Information for TSN | The CNC obtains the 5GS bridge VLAN configuration from TSN AF according to clause 12.10.1.1 of IEEE Std 802.1Q [98]. The TSN AF and UPF/NW-TT are pre-configured with same 5GS bridge VLAN configuration.
NOTE: In this Release, the VLAN Configuration Information are pre-configured at the TSN AF and the NW-TT and is not ex... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.4 QoS mapping tables for TSN | The mapping tables between the traffic class and 5GS QoS Profile is provisioned and further used to find suitable 5GS QoS profile to transfer TSN traffic over the PDU Session. QoS mapping procedures are performed in two phases: (1) QoS capability report phase as described in clause 5.28.1 and (2) QoS configuration phas... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.5 Support of integration with IETF Deterministic Networking | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.5.1 General | 5GS acts as a DetNet Router according to the architecture defined in clause 4.4.8.4. When integrated with an IETF Deterministic Network, 5GS acts as one or more routers. A 5GS router is composed of the ports on a single UPF (i.e. PSA) network side, the user plane tunnel between the UE and UPF and the ports on the devic... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.5.2 5GS DetNet node reporting | The TSCTSF may provide exposure information to the DetNet controller using information collected from the 5GS entities. The exposure information can be used by the DetNet controller to build up the network topology information. The exposure may be based on IETF RFC 8343 [151] and IETF RFC 8344 [152].
The TSCTSF may col... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.28.5.3 DetNet node configuration mapping in 5GS | The TSCTSF maps the parameters in the DetNet YANG configuration to 5GS parameters as defined in clause 6.1.3.23b of TS 23.503 [45].
The TSCTSF determines the UE address to bind the DetNet configuration as follows:
- When available, the TSCTSF uses the identity of the incoming and outgoing interface to determine the aff... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.29 Support for 5G LAN-type service | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.29.1 General | The service requirements for 5G LAN-type service are specified in TS 22.261 [2].
A 5G Virtual Network (VN) group consists of a set of UEs using private communication for 5G LAN-type services. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.29.2 5G VN group management | 5G System supports management of 5G VN Group identification and membership (i.e. definition of 5G VN group identifiers and membership) and 5G VN Group data (i.e. definition of 5G VN group data). The 5G VN Group management can be configured by a network administrator or can be managed dynamically by AF.
A 5G VN group is... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.29.3 PDU Session management | Session management as defined for 5GS in clause 5.6 is applicable to 5G-VN-type services with the following clarification and enhancement:
- A UE gets access to 5G LAN-type services via a PDU Session of IP PDU Session type or Ethernet PDU Session type.
- A PDU Session provides access to one and only one 5G VN group. Th... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.29.4 User Plane handling | User Plane management as defined for 5GS in clause 5.8 is applicable to 5G LAN-type services with the following clarifications:
- There are three types of traffic forwarding methods allowed for 5G VN communication:
- N6-based, where the UL/DL traffic for the 5G VN communication is forwarded to/from the DN;
NOTE 1: Opti... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30 Support for non-public networks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.1 General | A Non-Public Network (NPN) is a 5GS deployed for non-public use, see TS 22.261 [2]. An NPN is either:
- a Stand-alone Non-Public Network (SNPN), i.e. operated by an NPN operator and not relying on network functions provided by a PLMN, or
- a Public Network Integrated NPN (PNI-NPN), i.e. a non-public network deployed wi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2 Stand-alone Non-Public Networks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.0 General | SNPN 5GS deployments are based on:
- the architecture depicted in clause 4.2.3;
- the architecture for 5GC with Untrusted non-3GPP access (Figure 4.2.8.2.1-1) for either access to SNPN services via a PLMN (and vice versa) or for direct access to SNPN via non-3GPP access;
- the architecture for 5GC with Trusted non-3GPP... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.1 Identifiers | The combination of a PLMN ID and a Network identifier (NID) identifies an SNPN.
NOTE 1: The PLMN ID used for SNPNs is not required to be unique. PLMN IDs reserved for use by private networks can be used for non-public networks, e.g. based on mobile country code (MCC) 999 as assigned by ITU [78]). Alternatively, a PLMN ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.2 Broadcast system information | NG-RAN nodes or Trusted non-3GPP access networks which provide access to SNPNs broadcast the following information:
- One or multiple PLMN IDs;
- List of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to; and
NOTE 1: It is assumed that an NG-RAN node supports broadcasting a total of twelve ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.3 UE configuration and subscription aspects | An SNPN-enabled UE is configured with the following information for each subscribed SNPN:
- PLMN ID and NID of the subscribed SNPN;
- Subscription identifier (SUPI) and credentials for the subscribed SNPN;
- Optionally, an N3IWF FQDN and the MCC of the country where the configured N3IWF is located;
- Optionally, if the... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.4 Network selection in SNPN access mode | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.4.1 General | An SNPN-enabled UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode the UE selects and registers with SNPNs over Uu as described in clause 5.30.2.4. Network selection in SNPN access mode for access to SNPN services via Untrusted non-3GPP access, Trusted non-3GPP access and Wireline acces... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.4.2 Automatic network selection | NOTE 1: If the UE has multiple subscriptions (SNPN and/or PLMN) it is assumed that the subscription to use for automatic selection is determined by implementation specific means prior to network selection.
If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Lo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.4.3 Manual network selection | For manual network selection UEs operating in SNPN access mode provide to the user the list of SNPNs (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available SNPNs the UE has respective SUPI and credentials for. If the UEs supports access to an SNPN using credentials fr... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.5 Network access control | If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a self-assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to temporarily prevent the UE from automatically selecting and registering with the same SNPN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.6 Cell (re-)selection in SNPN access mode | UEs operating in SNPN access mode only select cells and networks broadcasting both PLMN ID and NID of the selected SNPN or its equivalent SNPN.
NOTE: Further details on the NR idle and inactive mode procedures for SNPN cell selection is defined in TS 38.331 [28] and in TS 38.304 [50]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.7 Access to PLMN services via stand-alone non-public networks | To access PLMN services, a UE in SNPN access mode that has successfully registered with an SNPN may perform another registration via the SNPN User Plane with a PLMN (using the credentials of that PLMN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Sessi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.8 Access to stand-alone non-public network services via PLMN | To access SNPN services, a UE that has successfully registered with a PLMN over 3GPP access may perform another registration via the PLMN User Plane with an SNPN (using the credentials of that SNPN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Session ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.9 SNPN connectivity for UEs with credentials owned by Credentials Holder | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.9.1 General | SNPNs may support UE access using credentials owned by a Credentials Holder separate from the SNPN. In this case the Session Management procedures (i.e. PDU Sessions) terminate in an SMF in the SNPN.
When an SNPN supports UE access using credentials assigned by a Credentials Holder separate from the SNPN, it is assumed... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.9.2 Credentials Holder using AAA Server for primary authentication and authorization | The AUSF and the UDM in SNPN may support primary authentication and authorization of UEs using credentials from a AAA Server in a Credentials Holder (CH).
- Only NSI based SUPI is supported and the SUPI is used to identify the UE during primary authentication and authorization towards the AAA Server. SUPI privacy is ac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.9.3 Credentials Holder using AUSF and UDM for primary authentication and authorization | An SNPN may support primary authentication and authorization of UEs that use credentials from a Credentials Holder using AUSF and UDM. The Credentials Holder may be an SNPN or a PLMN. The Credentials Holder UDM provides to SNPN the subscription data.
NOTE 1: A list of functionalities not supported in SNPN is provided i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.10 Onboarding of UEs for SNPNs | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.10.1 General | Onboarding of UEs for SNPNs allows the UE to access an Onboarding Network (ONN) for the purpose of provisioning the UE with SNPN credentials for primary authentication and other information to enable access to a desired SNPN, i.e. (re-)select and (re-)register with SNPN.
To provision SNPN credentials in a UE that is co... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.10.2 Onboarding Network is an SNPN | 5.30.2.10.2.1 General
A UE configured with Default UE credentials may register with an ON-SNPN for the provisioning of SO-SNPN credentials.
5.30.2.10.2.2 Architecture
Figures 5.30.2.10.2.2-1, 5.30.2.10.2.2-2 and 5.30.2.10.2.2-3 depict the architecture for Onboarding of UEs in an ON-SNPN.
Figure 5.30.2.10.2.2-1: Archite... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.10.3 Onboarding Network is a PLMN | 5.30.2.10.3.1 General
A UE configured with PLMN credentials in USIM for primary authentication may register with a PLMN for the provisioning of SO-SNPN credentials.
5.30.2.10.3.2 Network selection and Registration
This clause applies only when the UE is not in SNPN access mode.
When the UE is using PLMN credentials for... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.10.4 Remote Provisioning of UEs in Onboarding Network | 5.30.2.10.4.1 General
Remote Provisioning of UEs that registered with an Onboarding Network enables provisioning the UE with SNPN credentials for primary authentication and other information to enable access to the desired SNPN.
Onboarding Services are provided using a PDU Session for DNN and S-NSSAI used for onboardin... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.11 UE Mobility support for SNPN | If the UE moves its 3GPP access between SNPN and PLMN, the network selection is performed as specified in TS 23.122 [17] and UE performs initial registration as specified in clause 4.2.2.2.2 of TS 23.502 [3].
NOTE 1: When the UE moves its 3GPP access between SNPN and PLMN, it is up to UE implementation to activate/deac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.12 Access to SNPN services via Untrusted non-3GPP access | Access to SNPN services via Untrusted non-3GPP access network follows the specification in the previous 5.30.2 clauses with the differences as specified in this clause.
N3IWF selection is supported as follows:
- When UE registers to SNPN with credentials owned by the SNPN, UE uses the same N3IWF selection procedure as ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.13 Access to SNPN services via Trusted non-3GPP access | Access to SNPN services via Trusted non-3GPP access network follows the specification in the previous (sub)clauses of clause 5.30.2 with the differences as specified in this clause.
To access SNPN services via a Trusted non-3GPP access network, the UE follows the procedure for accessing a PLMN via a Trusted non-3GPP ac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.14 Access to SNPN services via wireline access network | Access to SNPN services via a wireline access network is specified in TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.2.15 Access to SNPN services for N5CW devices | Devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in an SNPN via a trusted WLAN access network that supports a TWIF function. To access SNPN services the N5CW device performs the following procedure:
- A WLAN ac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3 Public Network Integrated NPN | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3.1 General | 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. The existing network slicing functionalities apply as described in clause 5.15. When a PNI-NPN is made available via a PLMN, then the UE shall have a subsc... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3.2 Identifiers | The following is required for identification:
- A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID;
- A CAG cell broadcasts one or multiple CAG Identifiers per PLMN;
NOTE 1: It is assumed that a cell supports broadcasting a total of twelve CAG Identifiers. Further details are defined ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3.3 UE configuration, subscription aspects and storage | To use CAG, the UE, that supports CAG as indicated as part of the UE 5GMM Core Network Capability, may be pre-configured or (re)configured with the following CAG information, included in the subscription as part of the Mobility Restrictions:
- an Allowed CAG list i.e. a list of CAG Identifiers the UE is allowed to acce... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3.4 Network and cell (re-)selection and access control | The following is assumed for network and cell selection and access control:
- The CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell (see TS 38.300 [27], TS 38.304 [50]);
NOTE 1: The above also implies that cells are either CAG cells or normal PLMN cells. For network sharing s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.30.3.5 Support of emergency services in CAG cells | Emergency Services are supported in CAG cells, for UEs supporting CAG, whether normally registered or emergency registered as described in clause 5.16.4 and in clause 4.13.4 of TS 23.502 [3].
A UE may camp on an acceptable CAG cell in limited service state as specified in TS 23.122 [17] and TS 38.304 [50], based on ope... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31 Support for Cellular IoT | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.1 General | This clause provides an overview about 5GS optimisations and functionality for support of Cellular Internet-of-Things (Cellular IoT, or CIoT) according to service requirements described in TS 22.261 [2]. Cellular IoT is in earlier 3GPP releases also referred to as Machine Type Communication (MTC) (see clause 4.3.17 of ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.2 Preferred and Supported Network Behaviour | At registration, a UE includes its 5G Preferred Network Behaviour indicating the network behaviour the UE can support and what it would prefer to use.
NOTE: If the UE supports S1-mode then the UE will indicate the supported EPS Network Behaviour Information in the S1 UE network capability IE.
The 5G Preferred Network B... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.3 Selection, steering and redirection between EPS and 5GS | The UE selects the core network type (EPC or 5GC) based on the broadcast indications for both EPC and 5GC and the UE's EPC and 5GC Preferred Network Behaviour. Networks that support NB-IoT shall broadcast an indication whether N3 data transfer is supported or not in system information.
When the UE performs the registra... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.4 Control Plane CIoT 5GS Optimisation | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.4.1 General | The Control Plane CIoT 5GS Optimisation is used to exchange user data between the UE and the SMF as payload of a NAS message in both uplink and downlink directions, avoiding the establishment of a user plane connection for the PDU Session. The UE and the AMF perform integrity protection and ciphering for the user data ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.4.2 Establishment of N3 data transfer during Data Transport in Control Plane CIoT 5GS Optimisation | If UE and AMF have successfully negotiated N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may decide to establish N3 data transfer for any PDU session for which Control Plane Only Indicator was not incl... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.4.3 Control Plane Relocation Indication procedure | For intra-NB-IoT mobility when UE and AMF are using Control Plane CIoT 5GS Optimisation, the CP Relocation Indication procedures may be used. The purpose of the CP Relocation Indication procedure is to request the AMF to authenticate the UE's re-establishment request (see TS 33.501 [29]) and initiate the establishment ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.5 Non-IP Data Delivery (NIDD) | Functions for NIDD may be used to handle Mobile Originated (MO) and Mobile Terminated (MT) communication for unstructured data (also referred to as Non-IP). Such delivery to the AF is accomplished by one of the following two mechanisms:
- Delivery using the NIDD API;
- Delivery using UPF via a Point-to-Point (PtP) N6 t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.6 Reliable Data Service | The Reliable Data Service (RDS) may be used between the UE and NEF or UPF when using a PDU Session of PDU Type 'Unstructured'. The service provides a mechanism for the NEF or UPF to determine if the data was successfully delivered to the UE and for the UE to determine if the data was successfully delivered to the NEF o... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7 Power Saving Enhancements | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.1 General | To enable UE power saving and to enhance MT reachability while using MICO mode, e.g. for CIoT, the following features are specified in the following clauses:
- Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC_INACTIVE;
- MICO mode with Extended Connected Time;
- MICO mode with Active Time;
-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.2 Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC-INACTIVE | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.2.1 Overview | The UE and the network may negotiate over non-access stratum signalling the use of extended idle mode DRX for reducing its power consumption, while being available for mobile terminating data and/or network originated procedures within a certain delay dependent on the DRX cycle value. Extended DRX in CM-IDLE is support... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.2.2 Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC | 5.31.7.2.2.0 General
For WB-E-UTRA and LTE-M connected to 5GC, the extended idle mode DRX value range will consist of values starting from 5.12s (i.e. 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 2621.44s (almost 44 min). For NB-IoT, the extended idle mode DRX value range will start from 20.48s (i.e. 20.48s, 40.96s,... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.2.3 Paging for a UE registered in a tracking area with heterogeneous support of extended idle mode DRX | When the UE is registered in a registration area with heterogeneous support of extended idle mode DRX (e.g. comprising WB-E-UTRA and NR cells) and has negotiated eDRX, the AMF shall, for any paging procedure, perform at least one paging attempt during a PTW.
NOTE: Heterogeneous support of extended idle mode DRX in trac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.2.4 Paging for extended DRX for RRC_INACTIVE in NR connected to 5GC | For NR, the NG-RAN may request the CN to handle mobile terminated (MT) communication for the UE configured with eDRX for RRC_INACTIVE state by means of the Connection Inactive procedure with CN based MT communication handling Procedure (see clause 4.8.1.1a of TS 23.502 [3]). This allows the CN to apply high latency com... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.3 MICO mode with Extended Connected Time | When a UE, using MICO mode, initiates MO signalling or MO data and the AMF is aware of pending or expected MT traffic, the AMF may keep the UE in CM-CONNECTED state and the RAN may keep the UE in RRC_CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivere... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.4 MICO mode with Active Time | During a Registration procedure the UE may optionally request an Active Time value from the AMF as part of MICO Mode negotiation. In response, if the AMF receives an Active Time value from the UE and determines that the MICO mode is allowed for the UE, the AMF may assign an Active Time value for the UE, e.g. based on l... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.7.5 MICO mode and Periodic Registration Timer Control | If the Expected UE Behaviour indicates the absence of DL communication, the AMF may allow MICO mode for the UE and allocate a large periodic registration timer value based on e.g. Network Configuration parameters to the UE so that the UE can maximise power saving between Periodic Registration Updates.
If the Expected U... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.8 High latency communication | Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions as specified in clause 5.31.7 or due to discontinuous coverage as described in clause 5.4.13. "High latency" refers to the initial response time before normal... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.9 Support for Monitoring Events | The Monitoring Events feature is intended for monitoring of specific events in the 3GPP system and reporting such Monitoring Events via the NEF. The feature allows NFs in 5GS to be configured to detect specific events and report the events to the requested party. Clause 5.20 further discusses the Monitoring capabilitie... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.10 NB-IoT UE Radio Capability Handling | NB-IoT Radio Capabilities are handled in the network independently from other RATs' Radio Capabilities, see clause 5.4.4.1. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.11 Inter-RAT idle mode mobility to and from NB-IoT | Tracking Areas are configured so that they do not contain both NB-IoT and other RATs' cells, so when the UE is changing RAT type to or from NB-IoT while remaining registered with 5GC, the UE will perform the Mobility Registration Update procedure, see clause 5.3.2.3. When the UE is changing RAT type to or from NB-IoT a... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.12 Restriction of use of Enhanced Coverage | Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300 [30].
The usage of Enhanced Coverage requires use of extensive resources (e.g. radio and signalling resources). Specific subscribers can be restricted to use the Enhanced Coverage feature through Enhanced Coverage Restricted information that is stored... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.13 Paging for Enhanced Coverage | Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300 [30].
Whenever N2 is released and Paging Assistance Data for CE capable UE is available for the UE, the NG-RAN sends it to the AMF as described in clause 4.2.6 of TS 23.502 [3].
The AMF stores the received Paging Assistance Data for CE capable UE and ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.14 Support of rate control of user data | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.14.1 General | The rate of user data sent to and from a UE (e.g. a UE using CIoT 5GS Optimisations) can be controlled in two different ways:
- Serving PLMN Rate Control;
- Small Data Rate Control.
Serving PLMN Rate Control is intended to allow the Serving PLMN to protect its AMF and the Signalling Radio Bearers in the NG-RAN from the... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.14.2 Serving PLMN Rate Control | The Serving PLMN Rate Control value is configured in the (V-)SMF.
NOTE 1: Homogeneous support of Serving PLMN Rate Control in a network is assumed.
At PDU Session establishment and PDU Session modification, the (V-)SMF may inform the UE and UPF/NEF of any per PDU Session local Serving PLMN Rate Control that the Serving... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.14.3 Small Data Rate Control | The (H-)SMF may consider, e.g. based on operator policy, subscription, DNN, S-NSSAI, RAT type etc. to determine whether to apply Small Data Rate Control or not. The (H-)SMF can send a Small Data Uplink Rate Control command to the UE using the PCO information element. The (H-)SMF informs the UPF or NEF of any Small Data... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.15 Control Plane Data Transfer Congestion Control | NAS level congestion control may be applied in general for all NAS messages. To enable congestion control for control plane data transfer, a Control Plane data back-off timer is used, see clause 5.19.7.6. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.16 Service Gap Control | Service Gap Control is an optional feature intended for CIoT UEs to control the frequency at which these UEs can access the network. That is, to ensure a minimum time gap between consecutive Mobile Originated data communications initiated by the UE. This helps reducing peak load situations when there are a large number... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.17 Inter-UE QoS for NB-IoT | To allow NG-RAN to prioritise resource allocation between different UEs accessing via NB-IoT when some of the UEs are using Control Plane CIoT 5GS Optimisation, NG-RAN may, based on configuration, retrieve from the AMF the subscribed NB-IoT UE Priority for any UE accessing via NB-IoT by using the UE's 5G-S-TMSI as the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.18 User Plane CIoT 5GS Optimisation | User Plane CIoT 5GS Optimisation enables transfer of user plane data from CM-IDLE without the need for using the Service Request procedure to establish Access Stratum (AS) context in NG-RAN and UE.
If the following preconditions are met:
- UE and AMF negotiated support User Plane CIoT 5GS Optimisation (see clause 5.31.... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.19 QoS model for NB-IoT | 5GC QoS model described in clause 5.7 applies to NB-IoT with the following requirements:
- The default QoS rule shall be the only QoS rule of a PDU Session for a UE connected to 5GC via NB-IoT. There is only one QoS Flow (corresponding to the default QoS rule) per PDU session.
- Reflective QoS is not supported over NB-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.31.20 Category M UEs differentiation | This functionality is used by the network to identify traffic to/from Category M UEs, e.g. for charging differentiation.
A Category M UE using E-UTRA shall provide a Category M indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 36.331 [51].
When the UE has provided a Category M indi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32 Support for ATSSS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.1 General | The ATSSS feature is an optional feature that may be supported by the UE and the 5GC network.
The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network and two independent N... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.