hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ff4f1b98dccc19c082b3edc28daa7f19 | 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 ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27 Support of eXtended Reality and Interactive Media Services
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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 ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 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... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27.6 Traffic Parameter Information and Traffic Parameter Measurement
| The Traffic Parameter Information and Traffic Parameter Measurement apply to the UE power saving as specified in clause 5.37.8 of TS 23.501 [2].
The PCF may, based on the AF provided periodicity information, generate a PCC Rule with Traffic Parameter Information and Traffic Parameter Measurement, see clause 6.3.1.
Th... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27.7 Traffic identification and differentiated QoS for multiplexed media flows
| Traffic identification and differentiated QoS for multiplexed media flows is as defined in clause 5.37.11 of TS 23.501 [2] and enables differentiated QoS handling for (S)RTP media flows that are multiplexed on the same end-to-end transport layer connection.
When the UE indicates the support for (S)RTP Multiplexed Medi... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27.8 Support of transferring media related information over N6
| Support of transferring media related information over N6 is defined in clause 5.37.9 of TS 23.501 [2].
If the media traffic is transferred using connect-UDP, the AF provides On-path N6 Signalling Information for connect-UDP and the PCF generates PCC rules including this On-path N6 Signalling Information, as specified... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27.9 Expedited Data Transfer with Reflective QoS
| The AF may request Expedited Data Transfer with reflective QoS to expedite the transfer of larger payloads for XR applications by requesting two media flows that contain the same SDF filter with different QoS requirements, and the information for transmission of media related information over N6 as described in clause ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.27.10 Support of RAN-controlled UL bitrate recommendation
| The AF may provide a RAN-Controlled UL Bitrate Recommendation Indication for a media flow (see clause 5.37.12 of TS 23.501 [2]) within the AF session with required QoS procedure (as specified in clause 6.1.3.22). The PCF, based on the information received from AF and local operator policies, may then provide the RAN-Co... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.28 AF requested QoS for a UE or group of UEs not identified by a UE address
| The AF may request that the data session(s) for a UE (identified by a GPSI) or a group of UEs (identified by an External Group ID) for a specific DNN and S-NSSAI are set up with a specific QoS (e.g. low latency or PDV) and priority handling. The request from the AF may also include parameters for QoS monitoring and par... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.29 Network Slice replacement for a PDU Session
| The Network Slice Replacement is specified in clause 5.15.19 of TS 23.501 [2].
The PCF may set the Network Slice Replacement trigger event in the SMF as defined in clause 6.1.3.5.
When a new PDU Session is established and the SMF receives both an S-NSSAI and an Alternative S-NSSAI, the SMF includes both the replaced ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.30 Handling of Payload Headers Control
| The Handling of Payload Headers is defined in clause 5.6.17 of TS 23.501 [2]. When AF provides Header Handling Control information in a request, the PCF determines whether AF influence on Handling of Payload Headers is allowed considering the Handling of Payload Headers indication in the PDU Session policy control subs... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.3.31 Policy control for non-3GPP devices connecting behind a UE
| The support of QoS differentiation for non-3GPP devices connecting behind a UE using a Non-3GPP Device Identifier is specified in clause 5.52 of TS 23.501 [2].
The SMF may receive, from the UE, the Non-3GPP Device Identifier(s) and the corresponding user plane address(es) in the UE initiated PDU session modification p... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.4 Network slice related policy control
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.4.1 General
| Network slice related policy control supports limitation of the data rate per network slice.
A Maximum Slice Data Rate can be configured for an S-NSSAI (indicating the network slice subject to network slice data rate limitation control) by the operator (e.g. based on an SLA related to the network slice). The Maximum S... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.4.2 Limitation of data rate per network slice with assistance of the NWDAF
| If the NWDAF is used for network slice data rate analysis, the PCF consumes the analytics from the NWDAF and receives the Data Volume Dispersion Analytics statistics outputs for all UEs of the network slice as defined in TS 23.288 [24]. The PCF subscribes to the NWDAF for periodic reporting when it becomes responsible ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.4.3 Limitation of data rate per network slice with PCF based monitoring
| If the NWDAF is not deployed or is not to be used for network slice data rate analysis, the UDR maintains the Remaining Maximum Slice Data Rate per S-NSSAI and the PCF interacts with the UDR to deduct the value of the authorized Session-AMBR and the MBR of every GBR SDF from the Remaining Maximum Slice Data Rate per S-... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.5 Group related policy control
| Group related policy control supports limitation of the data rate per group and is only applicable to 5G VN groups, as described in clause 5.29.2 of TS 23.501 [2].
The Maximum Group Data Rate defines the maximum allowed aggregate data rate across all GBR and Non-GBR QoS Flows within the 5G VN group.
A Maximum Group D... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.1.6 Void
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2 Network functions and entities
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1 Policy Control Function (PCF)
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.1 General
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.1.1 Session management related functionality
| The PCF provides the following session management related functionality:
- Policy and charging control for a service data flows;
- PDU Session related policy control;
- PDU Session event reporting to the AF.
The PCF provides authorized QoS for a service data flow and other network control regarding service data flo... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.1.2 Non-session management related functionality
| The PCF provides the following non-session management related functionality:
- Access and mobility related policy control (as described in clause 6.1.2.1);
- UE policy information control (as described in clause 6.1.2.2);
- Negotiation for future BDT (as described in clause 6.1.2.4);
- Negotiation for planned data ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.1.3 Network slice related functionality
| The PCF provides the following network slice related functionality:
- Limitation of the data rate per network slice (as described in clause 6.1.4).
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.1.4 Group related functionality
| The PCF provides the following group related functionality:
- Limitation of the data rate per 5G VN group (as described in clause 6.1.5).
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.2 Input for PCC decisions
| The listed information below is not intended to be complete and describes only examples of the information that can be provided by the respective NF.
The PCF shall accept input for PCC decision-making from the SMF, the AMF, the CHF, the NWDAF if present, the UDR and if the AF is involved, from the AF, as well as the P... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.3 Policy control subscription information management
| The PCF may request subscription information at PDU Session establishment, PDU Session modification, during AM Policy Association Establishment procedure and during the UE Policy Association Establishment procedure.
The PCF may receive notifications on changes in the subscription information. Upon reception of a notif... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.4 V-PCF
| The V-PCF is a functional element that encompasses policy control decision functionalities in the VPLMN.
For session management related policy control, the V-PCF only includes functionality for local breakout roaming scenario based on roaming agreements.
For UE policy control, the V-PCF receives the UE policy from th... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.5 H-PCF
| The H-PCF is a functional element that encompasses policy control decision functionalities in the HPLMN.
For session management related policy control, the H-PCF only includes functionality for home routed roaming scenario and provides the same functionality as the PCF in the non-roaming case.
For UE policy control, ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.6 Application specific policy information management
| The application specific information used for policy control includes:
- Negotiation of BDT information stored in the UDR as Data Set "Policy Data" and Data Subset "Background Data Transfer data": It contains an ASP identifier, Non-IP information or IP 3-tuple to identify the Application server, a transfer policy toge... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.7 Usage monitoring
| The PCF supports usage monitoring control for a PDU Session or per Monitoring Key. Usage is defined as either volume or time of user plane traffic.
The PCF may receive usage monitoring related information per DNN and S-NSSAI combination and UE from the UDR, i.e. the overall amount of allowed resources (based either on... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.8 Sponsored data connectivity
| The PCF may authorise an application service provider to request specific PCC decisions (e.g. authorisation to request sponsored IP flows, authorisation to request QoS resources) based on sponsored data connectivity profile from the UDR. For sponsored data connectivity, the PCF may receive a usage threshold from the AF... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.9 Monitoring the data rate per Network Slice for a UE
| A PCF may support monitoring of data rate per S-NSSAI for a UE. The monitoring is performed by aggregating the Session-AMBR values and the MBR values allocated to each PCC Rule (belonging to a GBR service data flow) in all PDU Sessions established for a UE in that S-NSSAI. To enable this monitoring, the SMF selects the... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.10 Monitoring the data rate per Network Slice
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.10.1 General
| The PCF supports monitoring and limitation of the data rate per S-NSSAI.
If the S-NSSAI is subject to network slice data rate limitation the Remaining Maximum Slice Data rate per S-NSSAI is stored in the UDR as Data Set "Policy Data" and Data Subset "Network Slice Specific Policy Control Data" as defined in clause 6.2... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.10.2 Monitoring the data rate per Network Slice by using QoS parameters
| For the purpose of monitoring the data rate per S-NSSAI, the PCF shall perform the following for an SM Policy Association with an S-NSSAI subject to data rate limitation:
- At the establishment of a SM Policy Association, the PCF shall check whether the Remaining Maximum Slice Data Rate is higher than the Authorized S... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.11 Monitoring the data rate per Group
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.11.1 General
| The PCF supports monitoring and limitation of the data rate per 5G VN group.
If the group is subject to data rate limitation the Maximum Group Data Rate for the group is stored in the UDR as defined in clause 5.29.2 of TS 23.501 [2].
The PCF interacts with the UDR to update the Maximum Group Data Rate specific policy... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.11.2 Monitoring the data rate per Group by using QoS parameters
| For the purpose of monitoring the data rate per group, the PCF shall perform the same operations as for the monitoring of the data rate per network slice described in clause 6.2.1.10.2 with the following differences:
- Instead of handling Maximum Slice Data Rate per S-NSSAI, the UDR and PCF handles the Maximum Group D... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.12 VPLMN Specific Offloading Policy
| For Home Routing roaming scenario, the PCF for the PDU Session in HPLMN may provide the VPLMN Specific Offloading Policy for the local part of the DN in VPLMN for the HR-SBO PDU Session (see the clause 6.7 of TS 23.548 [33]).
If the PCF receives over the SM Policy Association a Serving Network identifier indicating th... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.1.13 Local Offloading Management Policy
| In the non-roaming scenario if the PCF receives over the SM Policy Association a Local Offloading Policy indication (see the clause 6.10 of TS 23.548 [33]), the PCF may provide the Local Offloading Management Policy or (if available) the associated Offload Identifier to the SMF. The Offload Identifier is unique within ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2 Session Management Function (SMF)
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.1 General
| The SMF is responsible for the enforcement of the policy decisions related to service data flow detection, authorized QoS, charging, gating, traffic usage reporting, packet routing and forwarding and traffic steering. The SMF controls the policy and charging enforcement which includes the binding of service data flows ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.2 Service data flow detection
| The Service Data Flow detection uses the service data flow template included in a PCC Rule provide by the PCF. The service data flow template defines the data for the service data flow detection as a set of service data flow filters or an application identifier referring to an application detection filter. The SMF maps... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.3 Measurement
| The SMF shall ensure that the UPF supports data volume, duration, combined volume/duration and event based measurement for charging. The Measurement method indicates what measurement type is applicable to the PCC rule.
NOTE 1: Event based charging is only applicable to predefined PCC rules and PCC rules using an appli... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.4 QoS control
| The SMF receives the authorized QoS for a service data flow in the PCC rule. The SMF derives the QoS parameters for a QoS Flow (other than the QoS Flow associated with the default QoS rule) based on the PCC rule information of the PCC rule(s) bound to this QoS Flow:
- The SMF shall set the QoS Flow parameters 5QI and ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.5 Application detection
| The SMF shall instruct the UPF to detect the Start and Stop of the application traffic for the PCC rules used for application detection (i.e. with application identifier) that the PCF has activated at the SMF.
If the PCF has subscribed to the event and notification is not muted for the specific PCC Rule, the SMF shall... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.6 Traffic steering
| The SMF shall support traffic steering control as defined in clause 6.1.3.14.
The SMF may be configured with the traffic steering policy IDs related to the mechanism enabling traffic steering to the N6-LAN, DN and/or DNAIs associated with N6 traffic routing requirements.
Upon receiving a PCC rule which contains the t... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.7 Access Traffic Steering, Switching and Splitting
| The SMF may support functionality for traffic steering, switching and splitting within a MA PDU Session, as described in TS 23.501 [2].
Upon receiving a PCC rule which contains the MA PDU Session Control information, the SMF shall instruct the UPF accordingly and shall also create and provide applicable ATSSS rules to... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.2.8 Network Slice Replacement
| The SMF may support functionality for Network Slice Replacement, as described in clause 6.1.3.29 and in clause 5.15.19 of TS 23.501 [2].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.3 Application Function (AF)
| The Application Function (AF) is an element offering applications that require dynamic policy and/or charging control over the user plane behaviour and/or an element requesting non-session based network capability exposure. In this specification, the functionality of the AF is only defined with respect to the interacti... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.4 Unified Data Repository (UDR)
| The Unified Data Repository (UDR) is defined in TS 23.501 [2].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.5 Charging Function (CHF)
| The Charging Function is specified in TS 32.240 [8].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.6 Void
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.7 Network Exposure Function (NEF)
| The Network Exposure Function (NEF) is defined in TS 23.501 [2] and additionally supports the following policy related functionalities:
- Service specific policy and charging control;
- Management of packet flow descriptions;
- Sponsor data connectivity including usage monitoring (as defined in clause 6.2.1.1);
- N... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.8 Access and Mobility Management Function (AMF)
| The Access and Mobility Management Function (AMF) is defined in TS 23.501 [2] and additionally supports the following policy related functionalities:
- Enforcement of access and mobility related policies received from the PCF;
- Transfers of UE policy information received from the PCF to the UE via N1 interface;
- R... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.9 Network Data Analytics Function (NWDAF)
| The Network Data Analytics Function (NWDAF) is defined in TS 23.288 [24].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.10 Void
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.2.11 Time Sensitive Communication and Time Synchronization Function (TSCTSF)
| The Time Sensitive Communication and Time Synchronization Function (TSCTSF) is defined in TS 23.501 [2].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.3 Policy and charging control rule
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.3.1 General
| The Policy and charging control rule (PCC rule) comprises the information that is required to enable the user plane detection of, the policy control and proper charging for a service data flow. The packets detected by applying the service data flow template of a PCC rule form a service data flow.
Two different types o... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.3.2 Policy and charging control rule operations
| Policy and Charging Rule operations consist of activation, modification and de-activation of PCC rules. The PCF may activate, modify and deactivate a PCC rule at any time. However, the modification is applicable to dynamic PCC rules only.
Activation of a dynamic PCC rule provides the PCC rule information to the SMF. A... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.4 PDU Session related policy information
| The purpose of the PDU Session related policy information is to provide policy and charging control related information that is applicable to a single Monitoring key or the whole PDU Session respectively. The PCF may provide PDU Session related policy information to the SMF together with PCC rules or separately.
Table... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.5 Access and mobility related policy information
| To enable the enforcement in the 5GC system of the access and mobility policy decisions made by the PCF for the control as described in clause 6.1.2.1, the 5GC system may provide the Access and mobility related policy information from the PCF to the AMF.
Table 6.5-1 lists the AMF access and mobility related policy inf... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6 UE policy information
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.1 Access Network Discovery & Selection Policy Information
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.1.1 General
| The Access Network Discovery & Selection policy is an optional policy that may be provided to UE by the network.
In this release of the specification, the Access Network Discovery & Selection policy shall contain only rules that aid the UE in selecting a WLAN access network. Rules for selecting other types of non-3GPP... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.1.2 UE selecting a WLANSP rule
| The UE, when not operating in SNPN access mode, may be provisioned with multiple valid WLANSP rules (by the HPLMN and by the VPLMN when the UE is roaming). A WLANSP rule is valid if it meets the validity conditions included in the WLANSP rule (if provided).
When the UE is in the home the UE uses the valid WLANSP rules... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.1.3 UE procedure for selecting a WLAN access based on WLANSP rules
| The UE (or N5CW device) shall apply the procedure in this clause when the UE (or N5CW device) is provisioned with WLANSP rules and:
a) when the UE initiates untrusted non-3GPP access to 5GC and attempts to select a WLAN access network; or
b) when the UE initiates trusted non-3GPP access to 5GC by executing the Access... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2 UE Route Selection Policy information
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.1 Structure Description
| The UE Route Selection Policy (URSP) includes a prioritized list of URSP rules.
Table 6.6.2.1-1: UE Route Selection Policy
Information name
Description
Category
PCF permitted to modify in a URSP
Scope
URSP rules
1 or more URSP rules as specified in table 6.6.2.1-2
Mandatory
Yes
UE context
The structure of... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.2 Configuration and Provision of URSP
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.2.1 General
| The UE may be provisioned (signalled) with URSP rules by PCF of the HPLMN. When the UE is roaming, the PCF in the HPLMN may update both the non-VPLMN specific and VPLMN specific URSP rules in the UE. For URSP rules, the UE shall support the provisioning (signalling) from the PCF in the HPLMN, as specified in TS 24.501 ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.2.2 URSP rules for an SNPN-enabled UE
| An SNPN-enabled UE, while registered in an SNPN, may be provisioned (signalled) with URSP rules by the PCF of the SNPN. For URSP rules, the UE shall support the provisioning (signalling) from the PCF in the SNPN as specified in TS 24.501 [22]. In addition, the UE may be also pre-configured with URSP rules for the SNPN ... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.2.3 Void
| |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.3 UE procedure for associating applications to PDU Sessions based on URSP
| For every newly detected application/PIN the UE evaluates the URSP rules in the order of Rule Precedence and determines if the application/PIN is matching the Traffic descriptor of any URSP rule. When a URSP rule is determined to be applicable for a given application/PIN (see clause 6.6.2.1), the UE shall select a Rout... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.2.4 Support of URSP rule enforcement reporting
| The UE may report URSP rule enforcement to PCF, so that PCF will be made aware about the URSP rule enforcement when a given UE enforces specific URSP rule(s) and the PCF may trigger an action upon the reception of such reporting.
In order to activate the URSP rule enforcement reporting for a URSP rule (containing Conn... |
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.3 V2X Policy information
| The V2X Policy information (V2XP) is defined in TS 23.287 [28].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.4 ProSe Policy information
| The ProSe Policy information (ProSeP) is defined in TS 23.304 [34].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.5 Ranging/Sidelink Positioning Policy information
| The Ranging/Sidelink Positioning Policy information (RSLPP) is defined in TS 23.586 [41].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.6 A2X Policy information
| The A2X Policy information (A2XP) is defined in TS 23.256 [43].
|
ff4f1b98dccc19c082b3edc28daa7f19 | 23.503 | 6.6.7 UE Policy Association supplementary information
| To enable the (H-)PCF to provide the V-PCF/AMF information that is related to UE Policy, but is to be consumed by the AMF itself (e.g. address information of CHF), the 5GC system may provide the UE Policy Association supplementary information from the (H-)PCF to the V-PCF/AMF.
Table 6.6.7-1 lists the UE Policy Associa... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 1 Scope
| The present document defines the restoration procedures in the 5G System.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 3 Definitions and abbreviations
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and 3GPP TS 29.244 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1] and 3GPP TS 29.244 [4].
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
5MBS 5G Multicast-Broadcast Services
AF/AS Application Function... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4 Restoration Procedures related to the N4 Interface
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.1 General
| This clause specifies the procedures supported in the 5G System to detect and handle failures affecting the N4 interface.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.2 N4 Failure and Restart Detection
| Across PFCP based interfaces, an SMF and UPF shall utilize the PFCP Heartbeat Request and Heartbeat Response messages to detect a peer PFCP entity failure or restart as described in clause 19A of 3GPP TS 23.007 [2].
A PFCP function shall ignore the Recovery Timestamp received in PFCP Association Setup Request and PFCP... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3 UPF Restoration Procedures
| |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3.1 General
| When a UPF fails, all its Session contexts and PFCP associations affected by the failure become invalid and may be deleted.
|
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3.2 Restoration Procedure for PSA UPF Restart
| If F-TEID and/or UE IP address allocation is performed in the UPF, the UPF shall ensure that previously used F-TEID values and/or UE IP addresses are not immediately reused after a UPF restart, in order to avoid inconsistent F-TEID and/or UE IP address allocation throughout the network and to enable the restoration of ... |
b74a934059e31377fd54db6b38e2fc17 | 23.527 | 4.3.3 Restoration Procedure for PSA UPF Failure without Restart
| Procedures for PSA UPF failure without restart are implementation specific.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.