hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.3.5 Application detection and control requirements
| The application detection and control feature comprise the request to detect the specified application traffic, report to the PCF on the start or stop of application traffic and to apply the specified enforcement and charging actions.
The PCF shall instruct the SMF on which applications to detect and whether to report... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.3.6 Support for session management related network capability exposure
| Support for network capability exposure enables an AF (e.g. an external ASP) to request the following session management related policy control functionality from the NEF:
- Set or change a chargeable party at AF session setup (see clause 4.15.6.4 and 4.15.6.5 of TS 23.502 [3]);
- Set up an AF session with required Q... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.3.7 Traffic steering control
| Traffic Steering Control refers to the capability to activate/deactivate traffic steering policies from the PCF in the SMF for the purpose of:
- steering the subscriber's traffic to appropriate operator or 3rd party service functions (e.g. NAT, antimalware, parental control, DDoS protection) in the N6-LAN or 5G-LAN ty... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.3.8 Handling of Payload Headers
| Handling of Payload Headers refers to the capability to provide Header Handling Control information according to Application Function influence on Handling of Payload Headers as described in clause 5.6.17 of TS 23.501 [2]. This is only supported in non-roaming and home-routed scenarios.
|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.4 Network slice related policy control requirements
| The network slice related policy control requirements include:
- Limitation of the data rate per network slice.
|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 4.5 Energy related policy control requirements
| The PCC framework may support service adjustments for the UE based on Energy Consumption information and/or Energy Saving Indicator subscription information. Service adjustments are policy driven modifications to QoS, charging, or service treatment, initiated based on information exposed via the EIF as defined in claus... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5 Architecture model and reference points
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.1 General
| This specification describes the policy and charging control framework for the 5G system. The interaction between network functions is represented in two ways:
- A service-based representation, where network functions enable other authorized network functions to access their services. This representation also includes... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.2 Reference architecture
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.2.1 Non-roaming architecture
| The reference architecture of policy and charging control framework for the 5G System is comprised by the functions of the Policy Control Function (PCF), the Session Management Function (SMF), the User Plane Function (UPF), the Access and Mobility Management Function (AMF), the Network Exposure Functionality (NEF), the... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.2.2 Roaming architecture
| Figure 5.2.2-1 shows the local breakout roaming architecture of the policy and charging control framework for the 5G System:
Figure 5.2.2-1: Overall roaming reference architecture of policy and charging control framework for the 5G System - local breakout scenario
Figure 5.2.2-1a: Overall roaming reference archit... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.2.3 Void
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3 Service-based interfaces and reference points
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.1 Interactions between PCF and AF
| Npcf and Naf enable transport of application level session information and Ethernet/IP port management information from AF to PCF. Such information includes, but is not limited to:
- IP filter information or Ethernet packet filter information to identify the service data flow for policy control and/or differentiated c... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.2 Interactions between PCF and SMF
| Npcf and Nsmf enable the PCF to have dynamic control over the policy and charging behaviour at a SMF.
Npcf and Nsmf enable the signalling of policy and charging control decisions and support the following functionality:
- Creation of a SM Policy Association as defined in clause 4.16 of TS 23.502 [3];
- Request for p... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.3 Interactions between PCF and AMF
| Npcf and Namf enable the PCF to provide Access and Mobility related policy information to the AMF as well as to provide UE policy information to the UE via the AMF and support the following functionality:
- Creation and Deletion of an AM Policy Association as defined in clause 4.16 of TS 23.502 [3];
- Creation and De... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.4 Interactions between V-PCF and H-PCF
| For roaming scenario, the interactions between V-PCF and H-PCF through Npcf enables:
- Creation of an UE Policy Association as defined in clause 4.16 of TS 23.502 [3];
- Relay of notification of changes from the V-PCF in the VPLMN to the H-PCF as defined in clause 4.16 of TS 23.502 [3];
- Provision of UE policy info... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.5 Interactions between PCF and UDR
| The Nudr enables the PCF to access policy control related subscription information and application specific information stored in the UDR. The Nudr interface supports the following functions:
- request for policy control related subscription information and application specific information from the UDR;
- provisionin... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.6 Interactions between SMF and CHF
| The interactions between SMF and CHF enable online and offline charging.
The N40 reference point is defined for the interactions between SMF and CHF in the reference point representation.
Since the N40 reference point resides between the SMF and CHF in the HPLMN, home routed roaming and non-roaming scenarios are supp... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.7 Void
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.8 Interactions between PCF and CHF
| The Nchf enables the PCF to access policy counter status information relating to subscriber spending from CHF and support the following functionality:
- Request for reporting of policy counter status information from PCF to CHF and subscribe to or unsubscribe from spending limit reports (i.e. notifications of policy c... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.9 Interactions between SMF and NEF
| Nsmf and Nnef enable transport of PFDs from the NEF (PFDF) to the SMF for a particular application identifier or for a set of application identifiers. It is achieved with the support of the following functionality:
- Creation, updating and removal of individual or the whole set of PFDs from the NEF (PFDF) to the SMF;
... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.10 Interactions between NEF and PCF
| Npcf and Nnef enable the negotiation of policy and charging control behaviour between PCF and NEF by supporting the following functionality:
- service specific policy and charging control;
- sponsor data connectivity including usage monitoring;
- Application Function influence on traffic routing;
- Application Func... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.11 Interactions between NWDAF and PCF
| The Nnwdaf enables the PCF to request or subscribe to and be notified on analytics specified in clause 6 of TS 23.288 [24]. The specific list of analytics and how these analytics can be used by the PCF is described in clause 6.1.1.3.
The N23 reference point is defined for the interactions between NWDAF and PCF in the ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.12 Interactions between PCF for the UE and PCF for the PDU Session
| Npcf services enable reporting of PDU Session related events detected by the PCF for the PDU Session to the PCF for the UE. Such events are described in clause 6.1.3.18, e.g. reporting the start and stop of application traffic detection and UE reporting of URSP rule enforcement.
|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.13 Interactions between PCF and TSCTSF
| Npcf enables transport of application level session information from TSCTSF to PCF and Ethernet or IP port management information between PCF and TSCTSF. Such information includes, but is not limited to:
- information required to enable setting up an AF session with support for Time Sensitive Communication and Time Sy... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.14 Interactions between NWDAF and NEF (PFDF)
| The Nnwdaf enables the NEF (PFDF) to request or to subscribe to and to be notified of the PFD Determination analytics as specified in TS 23.288 [24].
NOTE: How PFD Determination analytics can be used by the NEF (PFDF) is described in clause 6.1.2.3.1.
|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 5.3.15 Interactions between EIF and PCF
| The Neif enables the PCF to subscribe to and to be notified of exposure of Energy Consumption information as described in clause 5.2.28.2 of TS 23.502 [3]. Details of exposure information and how these can be used by the PCF is described in clause 6.1.1.6.
The N113 reference point is defined for the interactions betwe... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6 Functional description
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1 Overall description
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1 General
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.1 PCF Discovery and Selection
| The procedures for PCF Discovery and Selection by the AMF and by the SMF are described in TS 23.501 [2].
The procedure to ensure that a consumer NF (e.g. an AF, NEF or PCF for the UE) reaches the PCF selected for a PDU Session is described in clause 6.1.1.2.
The procedure to ensure that a consumer NF (e.g. an AF) rea... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.2 Binding an AF request targeting an UE address to the relevant PCF
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.2.1 General
| When multiple and separately addressable PCFs have been deployed, a network functionality is required in order to ensure that a consumer NF (e.g. AF) needing to send policies about UE traffic identified by an UE address can reach over N5 the PCF holding the corresponding PDU Session information. This network functional... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.2.2 The Binding Support Function (BSF)
| The BSF has the following characteristics:
- The BSF stores internally information about the corresponding selected PCF:
- For a certain PDU Session, the BSF stores internally information about the user identity, the DNN, the UE (IP or MAC) address(es), the S-NSSAI, the selected PCF address and if available the assoc... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.3 Policy decisions based on network analytics
| Policy decisions based on network analytics allow PCF to perform policy decisions taking into account analytics information defined for Analytics IDs listed in TS 23.288 [24]. The analytics information may be provided by NWDAF directly or via DCCF, depending on the deployment of NWDAF or DCCF. Local configuration in th... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.4 Policy decisions based on spending limits
| Policy decisions based on spending limits is a functionality that allows PCF taking actions related to the status of policy counters that are maintained in the CHF. The CHF in the non-roaming case or the H-CHF in the Home Routed roaming case provides policy counters for spending limits to the (H-)PCF for the PDU Sessio... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.5 Policy control decisions based on awareness of URSP rule enforcement
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.5.1 General
| Based on operator policy, the PCF may, together with any other input for PCC decisions (see clause 6.2.1.2), make policy control decisions based on awareness of URSP rule enforcement for an application by using the following mechanisms:
- Policy control decisions based on awareness of URSP rule enforcement with UE ass... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.5.2 Policy control decisions based on awareness of URSP rule enforcement with UE assistance
| The PCF may obtain UE reporting of URSP rule enforcement as described in clause 6.6.2.4.
Based on the received URSP rule enforcement information, the PCF for the PDU Session may interact with the PCF for the UE as described in clause 4.16.16 of TS 23.502 [3]. The PCF for the UE may adjust the URSP rules based on the n... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.5.3 Policy control decisions based on awareness of URSP rule enforcement without UE assistance
| The PCF for the UE may subscribe to Analytics ID "PDU Session traffic analytics" described in TS 23.288 [24] for traffic monitoring of known traffic in order to verify the the traffic according to provisioned URSP rule(s). If the PCF for the UE is notified by the NWDAF about traffic which is not expected according to a... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.1.6 Policy decisions based on Energy Consumption information
| Policy decisions based on Energy Consumption information is a functionality that allows PCF taking policy decisions based on Energy Consumption information that are maintained in the EIF.
The PCF performs discovery and selection of EIF as defined in clause 6.3.27 of TS 23.501 [2] and subscribes/unsubscribes to Energy ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2 Non-session management related policy control
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.1 Access and mobility related policy control
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.1.1 General
| The access and mobility related policy control encompasses the management of service area restrictions, the management of the RFSP Index, the management of the UE-AMBR, the management of the UE Slice-MBR, the slice replacement management, the management of the SMF selection and the management of the Network Identity wi... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.1.2 Handling of the AM Policy Association
| In the non-roaming scenario, the establishment of the AM Policy Association is determined as follows. First, the AMF checks the AM Policy Association indicator received from UDM and establishes the AM Policy Association if its value is "enabled" and do not establish the AM Policy Association if its value is "disabled".... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.1.3 Deferred Access and Mobility Related Policy Information
| When the PCF provides access and mobility related policy information (defined in clause 6.5) to the AMF, the PCF may also provide a Deferred Access and Mobility Related Policy Information. The Deferred Access and Mobility Related Policy Information, is composed of an activation time, a deactivation time and a list of a... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2 UE policy control
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2.1 General
| The 5GC shall be able to provide policy information from the PCF to the UE. Such UE policy information includes:
1) Access Network Discovery & Selection Policy (ANDSP): It is used by the UE for selecting non-3GPP accesses and for selection of the N3IWF in the PLMN. The structure and the content of this policy are spec... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2.2 Distribution of the policies to UE
| The UE policy control enables the PCF to provide UE access selection related policy information, PDU Session related policy information, V2X Policy information, ProSe Policy information, A2X Policy information and Ranging/Sidelink Positioning Policy information to the UE, i.e. UE policies, that includes Access network ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2.3 URSP rule provisioning in EPS
| When a UE attaches initially in EPS and PDN connectivity request message is sent together with initial attach request, or the UE requested PDN connectivity procedure is performed for the first PDN connection or when the UE handovers from 5GS to EPS, PCF for the UE may need to update the URSP rules in the UE:
- During ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2.4 Distribution of VPLMN specific URSP rules to the UE
| The H-PCF may provision VPLMN specific URSP Rules to UE for the purpose of routing traffic to the VPLMN. The H-PCF provides VPLMN specific URSP Rules. The Network Slice Selection Policies of the VPLMN specific URSP Rules contain values that are associated with the HPLMN. The DNN Selection Policies of the VPLMN specific... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.2.5 Handling of the UE Policy Association
| In the non-roaming scenario, the establishment of the UE Policy Association is determined as follows. First, the AMF checks the UE Policy Association indicator received from UDM and establishes the UE Policy Association if its value is "enabled" and do not establish the UE Policy Association if its value is "disabled".... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.3 Management of packet flow descriptions
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.3.1 PFD management
| The Management of Packet Flow Descriptions enables the UPF to perform accurate application detection when PFD(s) are provided by an ASP and then to apply enforcement actions as instructed in the PCC Rule.
The operator is able to configure pre-defined PCC Rules in the SMF or dynamic PCC Rules in the PCF that include at... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.3.2 Packet Flow Description
| PFD (Packet Flow Description) is a set of information enabling the detection of application traffic.
Each PFD may be identified by a PFD id. A PFD id is unique in the scope of a particular application identifier. Conditions for when PFD ID is included in the PFD is described in TS 29.551 [17]. There may be different P... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.4 Negotiation for future background data transfer
| The AF may contact the PCF via the NEF (and Npcf_BDTPolicyControl_Create service operation) to request a time window and related conditions for future background data transfer (BDT).
NOTE 1: The NEF may contact any PCF in the operator network.
The AF request shall contain an ASP identifier, the volume of data to be t... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.5 Policy Control Request Triggers relevant for AMF
| The Policy Control Request Triggers relevant for AMF are listed in the tables below and define the conditions when the AMF shall interact again with PCF after the AM Policy Association Establishment or UE Policy Association Establishment.
The PCF provides Policy Control Request Triggers to the AMF indicating a specifi... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.6 AF influence on Access and Mobility related policy control
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.6.0 General
| The AF influence on Access and Mobility related policy control refers to the AF capability to request a service area coverage or the indication that high throughput is desired for a UE.
Two methods enable the AF to influence Access and Mobility related policy control (see clause 4.15.6.9 of TS 23.502 [3] for the relat... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.6.1 AF request Access and Mobility related Policy Control for a UE
| This clause applies to non-roaming, i.e. cases where the PCF, AF, AMF and SMF belong to the serving PLMN, or the AF belongs to a third party with which the Serving PLMN has an agreement. AF influence on Access and Mobility related policy control does not apply in the case of Home Routed or Local breakout roaming cases.... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.6.2 AF request to influence on Access and Mobility related Policy Control
| This clause applies to non-roaming and LBO roaming i.e. to cases where the involved entities (AF, PCF, SMF, AMF) belong to the Serving PLMN, or the AF belongs to a third party with which the Serving PLMN has an agreement. In LBO roaming, the AF request targets any inbound roaming UEs (identified by their home PLMN ID(s... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.2.7 Negotiation for planned data transfer with QoS requirements
| The AF may contact the PCF via the NEF by invoking Npcf_PDTQPolicyControl_Create service operation to request a time window for planned data transfer with QoS requirements (PDTQ).
NOTE 1: The NEF may contact any PCF in the operator network.
The AF request shall contain an ASP identifier, either a QoS Reference or ind... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3 Session management related policy control
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.1 General
| The session management related policy control functionality of the Policy and Charging control framework for the 5G system provides the functions for policy and charging control as well as event reporting for service data flows.
The PCF evaluates operator policies that are triggered by events received from the AF dire... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.2 Binding mechanism
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.2.1 General
| The binding mechanism is the procedure that associates a service data flow (defined in a PCC rule by means of the SDF template), to the QoS Flow deemed to transport the service data flow. For service data flows belonging to AF sessions, the binding mechanism shall also associate the AF session information with the QoS ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.2.2 Session binding
| Session binding is the association of the AF session information to one and only one PDU Session. The PCF shall perform the session binding, which may take the following PDU Session parameters into account:
a) For an IP type PDU Session, the UE IPv4 address and/or IPv6 prefix as specified in TS 23.501 [2], in addition... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.2.3 PCC rule authorization
| PCC Rule authorization is the selection of the 5G QoS parameters, described in clause 5.7.2 of TS 23.501 [2], for the PCC rules.
The PCF shall perform the PCC rule authorization for dynamic PCC rules belonging to AF sessions that have been selected in step 1, as described in clause 6.1.3.2.2, as well as for PCC rules ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.2.4 QoS Flow binding
| QoS Flow binding is the association of a PCC rule to a QoS Flow within a PDU Session. The binding is performed using the following binding parameters:
- 5QI;
- ARP;
- QNC (if available in the PCC rule);
- Priority Level (if available in the PCC rule);
- Averaging Window (if available in the PCC rule);
- Maximum D... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.3 Reporting
| Reporting refers to the differentiated PDU Session resource usage information (measured at the UPF) being reported by the SMF to the CHF.
NOTE 1: Reporting usage information to the CHF is distinct from credit management. Hence multiple PCC rules may share the same charging key for which one credit is assigned whereas ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.4 Credit management
| The credit management applies only for service data flow with online charging method and shall operate on a per charging key basis. The SMF should initiate one charging session with the CHF for each PDU Session subject to charging, in order to perform credit management within the charging session.
NOTE 1: Independent ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.5 Policy Control Request Triggers relevant for SMF
| The Policy Control Request Triggers relevant for SMF define the conditions when the SMF shall interact again with PCF after a PDU Session establishment as defined in the Session Management Policy Establishment and Session Management Policy Modification procedure as defined in TS 23.502 [3].
The PCR triggers are not ap... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.6 Policy control
| QoS control refers to the authorization and enforcement of the maximum QoS that is authorized for a service data flow, for a QoS Flow or for the PDU Session. A service data flow may be either of IP type or of Ethernet type. PDU Sessions may be of IP type or Ethernet type or unstructured.
The PCF, in a dynamic PCC Rule... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.7 Service (data flow) prioritization and conflict handling
| Service pre-emption priority enables the PCF to resolve conflicts where the activation of all requested active PCC rules for services would result in a cumulative authorized QoS which exceeds the Subscribed Guaranteed bandwidth QoS.
NOTE 1: For example, the PCF may use the pre-emption priority of a service, the activa... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.8 Termination action
| The termination action indicates the action which the SMF instructs the UPF to perform for all PCC rules of a Charging key for which credit is no longer available. The functional description for termination actions is described in TS 32.255 [21].
The SMF shall revert the termination action related instructions for the... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.9 Handling of packet filters provided to the UE by SMF
| Traffic mapping information is signalled to the UE by the SMF in the Packet Filter Sets of QoS rules as defined in TS 23.501 [2].
The network shall ensure that the traffic mapping information signalled to UE reflects the QoS Flow binding of PCC rules, except for those extending the inspection beyond what can be signal... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.10 IMS emergency session support
| PDU Sessions for IMS Emergency services are provided by the serving network to support IMS emergency when the serving network is configured to support emergency services. The serving network may be either a PLMN or a SNPN. Emergency services are network services provided through an Emergency DNN and may not require a s... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.11 Multimedia Priority Service support
| Multimedia Priority Services (MPS) is defined in TS 23.501 [2], TS 23.502 [3] and in TS 23.228 [5], utilising the architecture defined for 5GS.
Subscription data for MPS is provided to PCF through the N36/Nudr. To support MPS service, the PCF shall subscribe to changes in the MPS subscription data for Priority PDU con... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.12 Redirection
| Redirection of uplink application traffic is an option applicable in SMF or in UPF.
PCF may control redirection by provisioning and modifying dynamic PCC rules over the N7 interface, or activate/deactivate the predefined redirection policies in SMF. The PCF may enable/disable redirection and set a redirect destination... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.13 Resource sharing for different AF sessions
| The P-CSCF (i.e. AF) may indicate to the PCF that media of an AF session may share resources with media belonging to other AF sessions according to TS 23.228 [5]. For every media flow, the P-CSCF may indicate that the media flow may share resources in both directions or in one direction only (UL or DL).
The PCF makes ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.14 Traffic steering control
| Traffic steering control is triggered by the PCF initiated request and consists of steering the detected service data flows matching application detection filters or service data flow filter(s) in PCC Rules. The traffic steering control consists in one or both of the following:
- Application Function influence on traf... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.15 Resource reservation for services sharing priority
| An AF may indicate to the PCF that a media flow of an AF session is allowed to use the same priority as media flows belonging to other AF sessions (instead of the service priority provided for this media flow). In this case, the AF will provide a priority sharing indicator in addition to the application identifier and ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.16 3GPP PS Data Off
| This feature, when activated by the user, prevents traffics via 3GPP access except for 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 22.011 [15] and TS 23.221 [16], that are the only allowed services in both downlink and uplink direction when the 3G... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.17 Policy decisions based on spending limits
| An extended description of this clause is defined in clause 6.1.1.4.
|
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.18 Event reporting from the PCF
| The AF may subscribe/unsubscribe to notifications of events from the PCF for the PDU Session to which the AF session is bound. The AF can either subscribe/unsubscribe directly at the PCF or indirectly via an NEF or a TSCTSF.
The PCF for the UE may subscribe/unsubscribe to notifications of events from the PCF for the P... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.19 Mission Critical Services support
| Mission Critical Services are defined in TS 23.501 [2], TS 23.502 [3] and in TS 23.280 [23], utilising the architecture defined for 5GS.
Subscription data for MCX services are provided to PCF through the N36/Nudr. To support MCX services, the PCF shall subscribe to changes in the MCX services subscription data for Pri... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.20 Access Traffic Steering, Switching and Splitting
| As specified in TS 23.501 [2], the Access Traffic Steering, Switching and Splitting (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 ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.21 QoS Monitoring control
| The QoS Monitoring control refers to the enabling of real-time measurements of QoS Monitoring parameters for a service data flow.
An AF may request measurements for one or more of the QoS Monitoring parameters defined in clause 5.45 of TS 23.501 [2].
NOTE 1: The QoS Monitoring parameters which can be measured are par... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.22 AF session with required QoS
| The AF may request that a data session to a UE is set up with a specific QoS (e.g. low latency or PDV) and priority handling. The AF can request the network to provide QoS for the AF session based on the service requirements with the help of a QoS Reference parameter that refers to pre-defined QoS information. Instead ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.23 Support of integration with Time Sensitive Networking
| Time Sensitive Networking (TSN) support is defined in TS 23.501 [2], where the 5GS represents logical TSN bridge(s) based on the defined granularity model. The TSN AF and PCF interact to perform QoS mapping as described in clause 5.28.4 of TS 23.501 [2].
The PCF provides the following parameters to the TSN AF:
- 5GS ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.24 Policy control for redundant PDU Sessions
| As specified in clause 5.33.2.1 of TS 23.501 [2], in order to support highly reliable URLLC services, two redundant PDU Sessions over the 5G network may be established such that the 5GS sets up the user plane paths of the two redundant PDU Sessions to be disjoint. The policy control for redundant PDU Session specifies ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.25 User Plane Remote Provisioning of UE SNPN Credentials in Onboarding Network
| User Plane Remote Provisioning of UE SNPN Credentials in Onboarding Network is specified in clause 5.30.2.10.4 of TS 23.501 [2].
User Plane Remote Provisioning of UE SNPN Credentials is provided through a DNN and S-NSSAI used for onboarding.
For a PDU Session with a DNN and S-NSSAI used for onboarding, the PCF may ma... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.26 Packet Delay Variation monitoring and reporting
| The AF may send a request to PCF for Packet Delay Variation (i.e. between UE and PSA UPF) monitoring and reporting, together with the request for packet delay monitoring and reporting. The PCF may generate the authorized QoS Monitoring policy for the service data flow based on both, Packet Delay Variation monitoring re... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27 Support of eXtended Reality and Interactive Media Services
| |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27.1 Exposure of network information
| For support of real-time media codec/traffic adaptation to the network conditions, the AF may subscribe for exposure of 5GS network information.
When the AF requests the network to provide QoS for the AF session (as described in clause 6.1.3.22), the AF may also provide the subscription to the following information ba... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27.2 UL/DL policy control based on round-trip latency requirement
| The AF may provide a round-trip (RT) latency indication together with a single direction delay requirement between the UE and the PSA UPF expressed as the QoS Reference or the individual QoS parameters (as described in clause 6.1.3.22). The RT latency indication indicates the need to meet the RT latency requirement of ... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27.3 Support for delivery of multi-modal services
| Enablers to support interactive media services that require high data rate and low latency communication, e.g. cloud gaming, AR/VR/XR services and tactile/multi-modal communication services are defined in TS 23.501 [2] clause 5.37.2.
For the delivery of a multi-modal service, the AF may request to the PCF directly (or... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27.4 PDU Set based handling
| PDU Set based handling support is defined in clause 5.37.5 of TS 23.501 [2]. The AF may provide the Protocol Description (UL and/or DL) and/or On-path N6 Signalling Information as described in TS 23.501 [2].
The PCF shall, based on local configuration or on information received from the AF, include the UL and/or DL Pr... |
eacaad9195b2438bfe291ec7f8703532 | 23.503 | 6.1.3.27.5 Data Burst Based Handling
| The Data Burst Based Handling includes the detection and marking of End of Data Burst, the identification and marking of time to next Data Burst and the identification and marking of Data Burst Size.
The detection and marking of End of Data Burst is defined in clause 5.37.8.3 of TS 23.501 [2]. Based on the AF provided... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.