hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.14 Support of UE-Satellite-UE communication | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.14.1 General | To support UE-Satellite-UE communication, network functions (e.g. UPF) transferring IMS user plane traffic in the 5G system shall be deployed onboard the satellites with regenerative payload that provide service link to the two UEs. The reference architecture for support of UE-Satellite-UE communication is described in... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.14.2 Setup of UE-Satellite-UE communication with IMS user plane components on-board satellites | The AMF reports the identifier of the satellite serving the UE to the SMF as part of the PDU Session establishment and update procedures as described in clauses 4.3.2 and 4.3.3 of TS 23.502 [3].
NOTE 1: The AMF can determine that the UE is accessing gNB onboard a LEO or MEO satellite and can also determine the satellit... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.14.3 Support for UE-satellite-UE communication when serving satellite changes | NOTE 1: The following mechanism assumes gNB, UL CL/L-PSA, IMS-AGW are onboard the same satellite.
In the UE-SAT-UE communication, if the UE's serving satellite changes (e.g. due to UE movement or the satellite movement), the Xn/N2-based handover procedure can be performed to change the serving gNB from that on the sour... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5 Non-3GPP access specific aspects | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.0 General | This clause describe the specific aspects for untrusted non-3GPP access, trusted non-3GPP access and W-5GAN access. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.1 Registration Management | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG or to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC via tru... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.2 Connection Management | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to the 5G-RG in the case of W-5GAN and to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC vi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.3 UE Reachability | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.3.1 UE reachability in CM-IDLE | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to 5G-RG, in the case of W-5GAN or to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.5.3.2 UE reachability in CM-CONNECTED | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG and to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6 Session Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.1 Overview | The 5GC supports a PDU Connectivity Service i.e. a service that provides exchange of PDUs between a UE and a data network identified by a DNN. The PDU Connectivity Service is supported via PDU Sessions that are established upon request from the UE.
The Subscription Information for each S-NSSAI may contain a Subscribed ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.2 Interaction between AMF and SMF | The AMF and SMF are separate Network Functions.
N1 related interaction with SMF is as follows:
- The single N1 termination point is located in AMF. The AMF forwards SM related NAS information to the SMF based on the PDU Session ID in the NAS message. Further SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.3 Roaming | In the case of roaming the 5GC supports following possible deployments scenarios for a PDU Session:
- "Local Break Out" (LBO) where the SMF and all UPF(s) involved by the PDU Session are under control of the VPLMN.
- "Home Routed" (HR) where the PDU Session is supported by a SMF function under control of the HPLMN, by ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.4 Single PDU Session with multiple PDU Session Anchors | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.4.1 General | In order to support selective traffic routing to the DN or to support SSC mode 3 as defined in clause 5.6.9.2.3, the SMF may control the data path of a PDU Session so that the PDU Session may simultaneously correspond to multiple N6 interfaces. The UPF that terminates each of these interfaces is said to support PDU Ses... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.4.2 Usage of an UL Classifier for a PDU Session | In the case of PDU Sessions of type IPv4 or IPv6 or IPv4v6 or Ethernet, the SMF may decide to insert in the data path of a PDU Session an "UL CL" (Uplink classifier). The UL CL is a functionality supported by an UPF that aims at diverting (locally) some traffic matching traffic filters provided by the SMF. The insertio... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.4.3 Usage of IPv6 multi-homing for a PDU Session | A PDU Session may be associated with multiple IPv6 prefixes. This is referred to as multi-homed PDU Session. The multi-homed PDU Session provides access to the Data Network via more than one PDU Session Anchor. The different user plane paths leading to the different PDU Session Anchors branch out at a "common" UPF refe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.5 Support for Local Area Data Network | The access to a DN via a PDU Session for a LADN is only available in a specific LADN service area. A LADN service area is a set of Tracking Areas. LADN is a service provided by the serving PLMN or the serving SNPN. It includes:
- LADN service applies only to 3GPP accesses and does not apply in Home Routed case.
- The u... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.6 Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session | At PDU Session Establishment to a DN:
- The DN-specific identity (TS 33.501 [29]) of a UE may be authenticated/authorized by the DN.
NOTE 1: the DN-AAA server may belong to the 5GC or to the DN.
- If the UE provides authentication/authorization information corresponding to a DN-specific identity during the Establishmen... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.7 Application Function influence on traffic routing | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.7.1 General | The content of this clause applies to non-roaming and to LBO deployments i.e. to cases where the involved entities (AF, PCF, SMF, UPF) belong to the Serving PLMN or AF belongs to a third party with which the Serving PLMN has an SLA agreement.
AF influence on traffic routing may apply in the case of Home Routed deployme... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.7.2 Enhancement of UP path management based on the coordination with AFs | In order to avoid or minimize service interruption during PSA relocation for a PDU session of SSC mode 3, or a PDU session with UL CL or branch point, according to the indication of "AF acknowledgment to be expected" on AF subscription to corresponding SMF events (DNAI change) (that may be provided in PCC rules receive... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.8 Selective activation and deactivation of UP connection of existing PDU Session | This clause applies to the case when a UE has established multiple PDU Sessions. The activation of a UP connection of an existing PDU Session causes the activation of its UE-CN User Plane connection (i.e. data radio bearer and N3 tunnel).
For the activation of a UP connection the service area restrictions as specified ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9 Session and Service Continuity | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.1 General | The support for session and service continuity in 5G System architecture enables to address the various continuity requirements of different applications/services for the UE. The 5G System supports different session and service continuity (SSC) modes defined in this clause. The SSC mode associated with a PDU Session do... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.2 SSC mode | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.2.1 SSC Mode 1 | For a PDU Session of SSC mode 1, the UPF acting as PDU Session Anchor at the establishment of the PDU Session is maintained regardless of the access technology (e.g. Access Type and cells) a UE is successively using to access the network.
In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, IP continuity is sup... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.2.2 SSC Mode 2 | If a PDU Session of SSC mode 2 has a single PDU Session Anchor, the network may trigger the release of the PDU Session and instruct the UE to establish a new PDU Session to the same data network immediately. The trigger condition depends on operator policy e.g. request from Application Function, based on load status, e... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.2.3 SSC Mode 3 | For PDU Session of SSC mode 3, the network allows the establishment of UE connectivity via a new PDU Session Anchor to the same data network before connectivity between the UE and the previous PDU Session Anchor is released. When trigger conditions apply, the network decides whether to select a PDU Session Anchor UPF s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.9.3 SSC mode selection | SSC mode selection is done by the SMF based on the allowed SSC modes -including the default SSC mode) in the user subscription as well as the PDU Session type and if present, the SSC mode requested by the UE.
The operator may provision a SSC mode selection policy (SSCMSP) to the UE as part of the URSP rule -see clause ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.10 Specific aspects of different PDU Session types | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.10.1 Support of IP PDU Session type | The IP address allocation is defined in clause 5.8.1
The UE may acquire following configuration information from the SMF, during the lifetime of a PDU Session:
- Address(es) of P-CSCF(s);
- Address(es) of DNS server(s).
- If the UE indicates support of DNS with security as defined in TS 33.501 [29] to the network in PC... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.10.2 Support of Ethernet PDU Session type | For a PDU Session set up with the Ethernet PDU Session type, the SMF and the UPF acting as PDU Session Anchor (PSA) can support specific behaviours related with the fact the PDU Session carries Ethernet frames.
Depending on operator configuration related with the DNN, different configurations for how Ethernet traffic i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.10.3 Support of Unstructured PDU Session type | Different Point-to-Point (PtP) tunnelling techniques may be used to deliver Unstructured PDU Session type data to the destination (e.g. application server) in the Data Network via N6.
Point-to-point tunnelling based on UDP/IP encapsulation as described below may be used. Other techniques may be supported. Regardless of... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.10.4 Maximum Transfer Unit size considerations | In order to avoid data packet fragmentation between the UE and the UPF acting as PSA, the link MTU size in the UE should be set to the value provided by the network as part of the IP configuration. The link MTU size for IPv4 is sent to the UE by including it in the PCO (see TS 24.501 [47]). The link MTU size for IPv6 i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.11 UE presence in Area of Interest reporting usage by SMF | When a PDU Session is established or modified, or when the user plane path has been changed (e.g. UPF re-allocation/addition/removal), SMF may determine an Area of Interest, e.g. based on UPF Service Area, subscription by PCF for reporting UE presence in Presence Reporting Area, etc.
For 3GPP access, the Area of Intere... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.12 Use of Network Instance | The SMF may provide a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment or N4 Modification procedures.
NOTE 1: a Network Instance can be defined e.g. to separate IP domains, e.g. when a UPF is connected to 5G-ANs in different IP domains, overlapping UE IP addresses assigned by multiple Data Net... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.13 Always-on PDU session | An always-on PDU Session is a PDU Session for which User Plane resources have to be activated during every transition from CM-IDLE mode to CM-CONNECTED state.
Based on an indication from upper layers, a UE may request to establish a PDU Session as an always-on PDU Session. The SMF decides whether the PDU Session can be... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.14 Support of Framed Routing | Framed Routing is only defined for PDU Sessions of the IP type (IPv4, IPv6, IPv4v6) and allows to support an IP network behind a UE, such that a range of IPv4 addresses or IPv6 prefixes is reachable over a single PDU Session, e.g. for enterprise connectivity. Framed Routes are IP routes behind the UE.
A PDU Session may... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.15 Triggers for network analytics | Triggers for the SMF to request for or subscribe to the analytics information from the NWDAF are internal logic may include for example:
- UE PDU Session related event subscription by other NFs (e.g. AMF, NEF);
- UE access and mobility event reports from the AMF;
- locally detected events;
- analytics information recei... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.16 Support for Service Function Chaining | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.16.1 General | Service Function Chaining, also called N6-LAN Traffic Steering, refers to the steering of subscriber's traffic flows to appropriate operator or 3rd party Service Functions (e.g. NAT, antimalware, parental control, DDoS protection) in the N6-LAN.
The content of this clause applies to non-roaming and to Home Routed roami... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.16.2 Application Function influence on Service Function Chaining | An AF may request the steering of user plane traffic to a pre-configured chain of Service Functions on N6-LAN.
In the non-roaming scenario, Application Function influence on Service Function Chaining and Application Function influence on traffic routing (as defined in clause 5.6.7) can be applicable to the same traffic... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.17 Handling of Payload Headers | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.17.1 General | Handling of Payload Headers is an optional feature that allows exchange of information in-band in the user plane packets between the application (in the UE or in the application server) and UPF in the 5GS by supporting detection, insertion, replacement, or removal of payload headers of PDUs. Handling of Payload Headers... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.6.17.2 Application Function influence on Handling of Payload Headers | An AF may request the Handling of Payload Headers in order to detect, insert, replace, or remove payload headers of PDUs as well as to subscribe to notifications on events related to detection of payload headers of PDUs or related to the actions performed on payload headers of PDUs.
For the Handling of Payload Headers,... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7 QoS model | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1 General Overview | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.1 QoS Flow | The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows). The 5G QoS model also supports Reflective QoS (see clause 5.7.5).
The QoS Flow is the finest granularity ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.2 QoS Profile | A QoS Flow may either be 'GBR' or 'Non-GBR' depending on its QoS profile. The QoS profile of a QoS Flow is sent to the (R)AN and it contains QoS parameters as described below (details of QoS parameters are described in clause 5.7.2):
- For each QoS Flow, the QoS profile shall include the QoS parameters:
- 5G QoS Identi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.3 Control of QoS Flows | The following options are supported to control QoS Flows:
1) For Non-GBR QoS Flows and when standardized 5QIs or pre-configured 5QIs are used and when the 5QI is within the range of the QFI (i.e. a value less than 64), the 5QI value may be used as the QFI of the QoS Flow.
(a) A default ARP shall be pre-configured in th... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.4 QoS Rules | The UE performs the classification and marking of UL User plane traffic, i.e. the association of UL traffic to QoS Flows, based on QoS rules. These QoS rules may be explicitly provided to the UE (i.e. explicitly signalled QoS rules using the PDU Session Establishment/Modification procedure), pre-configured in the UE or... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.5 QoS Flow mapping | The SMF performs the binding of PCC rules to QoS Flows based on the QoS and service requirements (as defined in TS 23.503 [45]). The SMF assigns the QFI for a new QoS Flow and derives its QoS profile, corresponding UPF instructions and QoS Rule(s) from the PCC rule(s) bound to the QoS Flow and other information provide... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.6 DL traffic | The following characteristics apply for processing of DL traffic:
- UPF maps User Plane traffic to QoS Flows based on the PDRs.
- UPF performs Session-AMBR enforcement as specified in clause 5.7.1.8 and performs counting of packets for charging.
- UPF transmits the PDUs of the PDU Session in a single tunnel between 5GC... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.7 UL Traffic | Following characteristics apply for processing of UL traffic:
- UE uses the stored QoS rules to determine mapping between UL User Plane traffic and QoS Flows. UE marks the UL PDU with the QFI of the QoS rule containing the matching Packet Filter and transmits the UL PDUs using the corresponding access specific resource... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.8 AMBR/MFBR enforcement and rate limitation | UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced by the UPF, if the UPF receives the Session-AMBR values from the SMF as described in clause 5.8.2.7 and clause 5.8.5.4.
For UL Classifier PDU Sessions, UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced in the SMF selected UPF that supports the UL... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.9 Precedence Value | The QoS rule precedence value and the PDR precedence value determine the order in which a QoS rule or a PDR, respectively, shall be evaluated. The evaluation of the QoS rules or PDRs is performed in increasing order of their precedence value. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.10 UE-Slice-MBR enforcement and rate limitation | If a supporting NG-RAN receives for a UE a UE-Slice-MBR (see clause 5.7.2.6) for an S-NSSAI from the AMF, the NG-RAN shall apply this UE-Slice-MBR for all PDU Sessions of that UE corresponding to the S-NSSAI which have an active user plane if feasible. In particular, the NG-RAN shall enforce this UE-Slice-MBR as follow... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.1.11 QoS aspects of home-routed roaming | In the case of home-routed roaming, the V-SMF may apply VPLMN policies related with the SLA negotiated with the HPLMN or with QoS values supported by the VPLMN. Such policies may result in a situation that the V-SMF does not accept the PDU Session or does not accept some of the QoS Flows requested by the H-SMF.
QoS con... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2 5G QoS Parameters | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.1 5QI | A 5QI is a scalar that is used as a reference to 5G QoS characteristics defined in clause 5.7.4, i.e. access node-specific parameters that control QoS forwarding treatment for the QoS Flow (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.).
Standardized... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.2 ARP | The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. This allows deciding whether a QoS Flow establishment/modification/handover may be accepted or needs to be rejected in the case of resource limitations (typically used for admission control... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.3 RQA | The Reflective QoS Attribute (RQA) is an optional parameter which indicates that certain traffic (not necessarily all) carried on this QoS Flow is subject to Reflective QoS. Only when the RQA is signalled for a QoS Flow, the (R)AN enables the transfer of the RQI for AN resource corresponding to this QoS Flow. The RQA m... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.4 Notification control | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.4.1 General | The QoS Parameter Notification control indicates to the NG-RAN that notifications of "GFBR can no longer (or can again) be guaranteed" are requested when the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled (or can be fulfilled again) for a QoS Flow (during the lifetime of the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.4.2 Usage of Notification control with Alternative QoS Profiles at handover | During handover, the prioritized list of Alternative QoS Profile(s) (if available) is provided to the Target NG-RAN per QoS Flow in addition to the QoS profile. If the Target NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to the Tar... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.4.3 Usage of Notification control with Alternative QoS Profiles during QoS Flow establishment and modification | During QoS Flow establishment and modification, a prioritized list of Alternative QoS Profile(s) can be provided to the NG-RAN for the QoS Flow in addition to the QoS profile. If the NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.5 Flow Bit Rates | For GBR QoS Flows only, the following additional QoS parameters exist:
- Guaranteed Flow Bit Rate (GFBR) - UL and DL;
- Maximum Flow Bit Rate (MFBR) -- UL and DL.
The GFBR denotes the bit rate that is guaranteed to be provided by the network to the QoS Flow over the Averaging Time Window. The MFBR limits the bit rate t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.6 Aggregate Bit Rates | Each PDU Session of a UE is associated with the following aggregate rate limit QoS parameter:
- per Session Aggregate Maximum Bit Rate (Session-AMBR).
The Session-AMBR is signalled to the appropriate UPF entity/ies to the UE and to the (R)AN (to enable the calculation of the UE-AMBR). The Session-AMBR limits the aggreg... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.7 Default values | For each PDU Session Setup, the SMF retrieves the subscribed Session-AMBR values as well as the subscribed default values for the 5QI and the ARP and optionally, the 5QI Priority Level, from the UDM. The subscribed default 5QI value shall be a Non-GBR 5QI from the standardized value range.
NOTE 1: The 5QI Priority Leve... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.8 Maximum Packet Loss Rate | The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS Flow that can be tolerated in the uplink and downlink direction. This is provided to the QoS Flow if it is compliant to the GFBR
NOTE: In this Release of the specification, the Maximum Packet Loss Rate (UL, DL) can only be prov... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.2.9 Wireline access network specific 5G QoS parameters | QoS parameters that are applicable only for or wireline access networks (W-5GAN) are specified in TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3 5G QoS characteristics | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.1 General | This clause specifies the 5G QoS characteristics associated with 5QI. The characteristics describe the packet forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the following performance characteristics:
1 Resource type (Non-GBR, GBR, Delay-critical GBR);
2 Priority Level;... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.2 Resource Type | The resource type determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base station).
GBR QoS Flows are therefore typically authorized "on demand" which requires dynamic policy and charging... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.3 Priority Level | The Priority Level associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows. The lowest Priority Level value corresponds to the highest priority.
The Priority Level shall be used to differentiate between QoS Flows of the same UE and it shall also be used to differentiate betwe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.4 Packet Delay Budget | The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF. The PDB applies to the DL packet received by the UPF over the N6 interface and to the UL packet sent by the UE. For a certain 5QI the value of the PDB is the same in UL ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.5 Packet Error Rate | The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus,... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.6 Averaging Window | Each GBR QoS Flow shall be associated with an Averaging window. The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE).
Every standardized 5QI (of GBR and Delay-critical GBR resource type) is associated with a default value for the Averaging window (sp... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.3.7 Maximum Data Burst Volume | Each GBR QoS Flow with Delay-critical resource type shall be associated with a Maximum Data Burst Volume (MDBV).
MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB.
Every standardized 5QI (of Delay-critical GBR resource type) is associated with a default value for t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.4 Standardized 5QI to QoS characteristics mapping | Standardized 5QI values are specified for services that are assumed to be frequently used and thus benefit from optimized signalling by using standardized QoS characteristics. Dynamically assigned 5QI values (which require a signalling of QoS characteristics as part of the QoS profile) can be used for services for whic... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.5 Reflective QoS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.5.1 General | Reflective QoS enables the UE to map UL User Plane traffic to QoS Flows without SMF provided QoS rules and it applies for IP PDU Session and Ethernet PDU Session. This is achieved by creating UE derived QoS rules in the UE based on the received DL traffic. It shall be possible to apply Reflective QoS and non-Reflective... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.5.2 UE Derived QoS Rule | The UE derived QoS rule contains following parameters:
- One UL Packet Filter (in the Packet Filter Set as defined in clause 5.7.6);
- QFI;
- Precedence value (see clause 5.7.1.9).
Upon receiving DL packet, one UL Packet Filter derived from the received DL packet as described in this clause is used to identify a UE der... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.5.3 Reflective QoS Control | Reflective QoS is controlled on per-packet basis by using the Reflective QoS Indication (RQI) in the encapsulation header on N3 (and N9) reference point together with the QFI and together with a Reflective QoS Timer (RQ Timer) value that is either signalled to the UE upon PDU Session Establishment (or upon PDU Session ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.6 Packet Filter Set | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.6.1 General | The Packet Filter Set is used in the QoS rule and the PDR to identify one or more packet (IP or Ethernet) flow(s).
NOTE 1: A QoS Flow is characterised by PDR(s) and QoS rule(s) as described in clause 5.7.1.1.
NOTE 2: DL Packet Filter in a Packet Filter Set of a QoS rule may be needed by the UE e.g. for the purpose of I... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.6.2 IP Packet Filter Set | For IP PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of:
- Source/destination IP address or IPv6 prefix.
- Source / destination port number.
- Protocol ID of the protocol above IP/Next header type.
- Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask.
-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.6.3 Ethernet Packet Filter Set | For Ethernet PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of:
- Source/destination MAC address.
- Ethertype as defined in IEEE 802.3 [131].
- Customer-VLAN tag (C-TAG) and/or Service-VLAN tag (S-TAG) VID fields as defined in IEEE Std 802.1Q [98].
- Customer-VLAN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.7 PDU Set QoS Parameters | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.7.1 General | PDU Set QoS Parameters are used to support PDU Set based QoS handling in the 5G-AN.
The following PDU Set QoS Parameters are specified:
1. PDU Set Delay Budget (PSDB).
2. PDU Set Error Rate (PSER).
3. PDU Set Integrated Handling Information (PSIHI).
At least one of the following shall be sent to the NG-RAN/N3IWF/TNGF/W... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.7.2 PDU Set Delay Budget | The PDU Set Delay Budget (PSDB) defines an upper bound for the delay that a PDU Set may experience for the transfer between the UE and the N6 termination point at the UPF, i.e. the duration between the reception time of the first PDU (at the N6 termination point for DL or the UE for UL) and the time when all PDUs of a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.7.3 PDU Set Error Rate | The PDU Set Error Rate (PSER) defines an upper bound for the rate of PDU Sets that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PSER de... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.7.7.4 PDU Set Integrated Handling Information | The PDU Set Integrated Handling Information (PSIHI) indicates whether all PDUs of the PDU Set are needed for the usage of the PDU Set by the application layer in the receiver side. PSIHI is an optional parameter. A QoS Flow is associated with at most one PSIHI value per direction. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8 User Plane Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.1 General | User Plane Function(s) handle the user plane path of PDU Sessions. 3GPP specifications support deployments with a single UPF or multiple UPFs for a given PDU Session. UPF selection is performed by SMF. The details of UPF selection is described in clause 6.3.3. The number of UPFs supported for a PDU Session is unrestric... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2 Functional Description | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.1 General | This clause contains detailed functional descriptions for some of the functions provided by the UPF. It is described how the SMF instructs it's corresponding UP function and which control parameters are used. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.