hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3.1 General
| For MCPTT calls based on the IP connectivity functionality in the IOPS mode of operation, floor control is performed by using floor control messages among the MCPTT clients without a centralized MCPTT server. The MCPTT client can transmit voice packets over the IOPS MC connectivity function once it is granted the right... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3.2.1 IOPS floor request
| Table 10.5.3.2.1-1 describes the information flow for the IOPS floor request, from the floor participant to another floor participant, which is used to request the floor for media transfer. The packet(s) carrying the IOPS floor request are transmitted from the requesting MCPTT client to the IOPS MC connectivity functio... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3.2.2 IOPS floor taken
| Table 10.5.3.2.2-1 describes the information flow for the IOPS floor taken, from the floor participant to the floor participant, which is used to indicate the floor is granted to an MCPTT user. The packet(s) carrying the IOPS floor taken are transmitted from the originating MCPTT client to the IOPS MC connectivity func... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3.3 IOPS floor control during silence
| If a floor arbitrator does not exist, figure 10.5.3.3-1 shows the successful high level floor control procedure during periods when there is no detectable talker in an IOPS group call based on the IP connectivity functionality.
NOTE 1: The description also applies to IOPS private calls.
Pre-conditions:
- MCPTT user... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6 MCData service
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1 IOPS short data service (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.1 General
| The support of the MCData short data service (SDS) based on the IP connectivity functionality in the IOPS mode of operation enables that the service is provided by the MCData clients over the IOPS MC connectivity function. The IOPS MC connectivity function provides IP connectivity for the communication among MCData use... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.2.1 IOPS MCData standalone data request
| Table 10.6.1.2.1-1 describes the information flow for the IOPS MCData standalone data request from one MCData client to another MCData client. The packet(s) carrying the IOPS MCData standalone data request are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution to the target... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.2.2 IOPS MCData data disposition notification
| Table 10.6.1.2.2-1 describes the information flow for the IOPS MCData data disposition notification from one MCData client to another MCData client. The packet(s) carrying the IOPS MCData data disposition notification are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution t... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.2.3 IOPS MCData group standalone data request
| Table 10.6.1.2.3-1 describes the information flow for the IOPS MCData group standalone data request from one MCData client to other MCData clients. The packet(s) carrying the IOPS MCData group standalone data request are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution to... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.3 IOPS one-to-one standalone SDS using signalling control plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.3.1 General
| When an MCData user initiates an IOPS standalone SDS data transfer with another MCData user using the signalling control plane based on the IP connectivity functionality, the MCData client retrieves the connectivity information of the target MCData user (i.e. the MCData UE's IP address) from the IOPS connectivity clien... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.3.2 Procedure
| The procedure in figure 10.6.1.3.2-1 describes the case where an MCData user is initiating an IOPS one-to-one MCData communication for sending standalone SDS data over signalling control plane to another MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transactio... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.4 IOPS group standalone SDS using signalling control plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.4.1 General
| IOPS group standalone SDS using signalling control plane based on the IP connectivity functionality can use pre-configured information provided to MCData clients prior to initiating the data service. When an MCData client initiates an IOPS group standalone SDS based on the IP connectivity functionality it uses the pre-... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.6.1.4.2 Procedure
| The procedure in figure 10.6.1.4.2-1 describes the case where an MCData user is initiating an IOPS group MCData communication for sending standalone SDS data over signalling control plane to an IOPS MCData group, with or without disposition request. Standalone refers to sending unidirectional data in one transaction.
... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.7 MC IOPS notification
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.7.1 General
| In the IOPS mode of operation, it is assumed that the IOPS MC system does not have connectivity to the primary MC system due to the backhaul failure. Therefore, the primary MC system cannot be aware of the initiation of the IOPS operation and the corresponding activation of an IOPS MC connectivity function within the p... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.7.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.7.2.1 MC IOPS notification
| Table 10.7.2.1-1 describes the information flow MC IOPS notification from the MC service client to the primary MC service server.
Table 10.7.2.1-1: MC IOPS notification
Information element
Status
Description
MC service ID
M
The identity of the MC service user providing the notification
IOPS MC system informatio... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.7.3 MC IOPS notification procedure
| Figure 10.7.3-1 describes the IOPS MC notification procedure when an MC service user has left an active IOPS MC system and enters the primary MC system.
Pre-conditions:
- There is an active IOPS MC connectivity function and the neighbouring cells of the IOPS MC system are part of the primary MC system.
- The MC ser... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 1 Scope | The present document specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP‑CANs (e.g. GPRS, Fixed Broadband, EPC, etc.):
- Flow Based Charging for network usage, including charging control and online credit control, for service data ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 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.
- Fo... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 3 Definitions, symbols and abbreviations | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [8] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [8].
application detection filter: A logic used to detect packets generated by an applica... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [8] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [8].
ADC Application Detection and Control
AF Application Function
AMBR Aggregat... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4 High level requirements | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.1 General requirements | It shall be possible for the PCC architecture to base decisions upon subscription information.
It shall be possible to apply policy and charging control to any kind of 3GPP IP‑CAN and any non-3GPP accesses connected via EPC complying with TS 23.402 [18]. Applicability of PCC to other IP‑CANs is not restricted. However,... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.2 Charging related requirements | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.2.1 General | In order to allow for charging control on service data flow, the information in the PCC rule identifies the service data flow and specifies the parameters for charging control. The PCC rule information may depend on subscription data.
In order to allow for charging control on detected application traffic identified by ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.2.2 Charging models | The PCC charging shall support the following charging models both for charging performed by PCEF and charging performed by TDF:
- Volume based charging;
- Time based charging;
- Volume and time based charging;
- Event based charging;
- No charging.
NOTE 1: The charging model - "No charging" implies that charging contro... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.2.3 Examples of Service Data Flow Charging | There are many different services that may be used within a network, including both user-user and user-network services. Service data flows from these services may be identified and charged in many different ways. A number of examples of configuring PCC rules for different service data flows are described below.
EXAMPL... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3 Policy control requirements | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.1 General | The policy control features comprise gating control and QoS control.
The concept of QoS class identifier and the associated bitrates specify the QoS information for service data flows and bearers on the Gx and Gxx reference points. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.2 Gating control | Gating control shall be applied by the PCEF on a per service data flow basis.
To enable the PCRF gating control decisions, the AF shall report session events (e.g. session termination, modification) to the PCRF. For example, session termination, in gating control, may trigger the blocking of packets or "closing the gat... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.3 QoS control | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.3.1 QoS control at service data flow level | It shall be possible to apply QoS control on a per service data flow basis in the PCEF.
QoS control per service data flow allows the PCC architecture to provide the PCEF with the authorized QoS to be enforced for each specific service data flow. Criteria such as the QoS subscription information may be used together wit... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.3.2 QoS control at IP‑CAN bearer level | It shall be possible for the PCC architecture to support control of QoS reservation procedures (UE-initiated or network-initiated) for IP‑CANs that support such procedures for its IP‑CAN bearers in the PCEF or the BBERF, if applicable. It shall be possible to determine the QoS to be applied in QoS reservation procedure... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.3.3 QoS Conflict Handling | It shall be possible for the PCC architecture to support conflict resolution in the PCRF when the authorized bandwidth associated with multiple PCC rules exceeds the Subscribed Guaranteed bandwidth QoS. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.3.4 QoS control at APN level | It shall be possible for the PCRF to authorize the APN-AMBR to be enforced by the PCEF as defined in TS 23.401 [17]. The APN-AMBR applies to all IP‑CAN sessions of a UE to the same APN and has separate values for the uplink and downlink direction.
It shall be possible for the PCRF to provide the authorized APN-AMBR val... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.3.4 Subscriber Spending Limits | It shall be possible to enforce policies based on subscriber spending limits as per TS 22.115 [27]. The OCS shall maintain policy counter(s) to track spending for a subscription. These policy counters must be available in the OCS prior to their use over the Sy interface.
NOTE 1: The mechanism for provisioning the polic... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.4 Usage Monitoring Control | It shall be possible to apply usage monitoring for the accumulated usage of network resources on a per IP-CAN session and user basis. This capability is required for enforcing dynamic policy decisions based on the total network usage in real-time.
The PCRF that uses usage monitoring for making dynamic policy decisions ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.5 Application Detection and Control | The application detection and control feature comprise the request to detect the specified application traffic, report to the PCRF on the start or stop of application traffic and to apply the specified enforcement and charging actions.
The application detection and control shall be implemented either by the TDF or by t... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.6 RAN user plane congestion detection, reporting and mitigation | It shall be possible to transfer RAN user plane congestion information from the RAN to the Core Network in order to mitigate the congestion by measures selected by the PCRF and applied by the PCEF/TDF/AF. The detailed description of this functionality can be found in TS 23.401 [17] and TS 23.060 [12]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.7 Support for service capability exposure | It shall be possible to transfer information related to service capability exposure between the PCRF and the AF via an SCEF (see TS 23.682 [42]). |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.8 Traffic Steering Control | Traffic Steering Control refers to the capability to activate/deactivate traffic steering policies from the PCRF in the PCEF, the TDF or the TSSF 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 ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 4.9 Management of Packet Flow Descriptions in the PCEF/TDF using the PFDF | Management of Packet Flow Descriptions in the PCEF/TDF using the PFDF refers to the capability to create, update or remove PFDs in the PFDF via the SCEF (as described in TS 23.682 [42]) and the distribution from the PFDF to the PCEF or the TDF or both. This feature may be used when the PCEF or the TDF is configured to ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5 Architecture model and reference points | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.1 Reference architecture | The PCC functionality is comprised by the functions of the Policy and Charging Enforcement Function (PCEF), the Bearer Binding and Event Reporting Function (BBERF), the Policy and Charging Rules Function (PCRF), the Application Function (AF), the Traffic Detection Function (TDF), the Traffic Steering Support Function (... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2 Reference points | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.1 Rx reference point | The Rx reference point resides between the AF and the PCRF.
NOTE 1: The AF may be a third party application server.
This reference point enables transport of application level session information from AF to PCRF. Such information includes, but is not limited to:
- IP filter information to identify the service data flow... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.2 Gx reference point | The Gx reference point resides between the PCEF and the PCRF.
The Gx reference point enables the PCRF to have dynamic control over the PCC behaviour at a PCEF.
The Gx reference point enables the signalling of PCC decision, which governs the PCC behaviour and it supports the following functions:
- Establishment of Gx se... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.3 Reference points to subscriber databases | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.3.1 Sp reference point | The Sp reference point lies between the SPR and the PCRF.
The Sp reference point allows the PCRF to request subscription information related to the IP‑CAN transport level policies from the SPR based on a subscriber ID, a PDN identifier and possible further IP‑CAN session attributes, see Annex A and Annex D. For example... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.3.2 Ud reference point | The Ud reference point resides between the UDR and the PCRF, acting as an Application Frontend as defined in TS 23.335 [25]. It is used by the PCRF to access PCC related subscription data when stored in the UDR.
The details for this reference point are described in TS 23.335 [25] and TS 29.335 [26]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.4 Gy reference point | The Gy reference point resides between the OCS and the PCEF.
The Gy reference point allows online credit control for service data flow based charging. The functionalities required across the Gy reference point are defined in TS 32.251 [9] and is based on RFC 4006 [4]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.5 Gz reference point | The Gz reference point resides between the PCEF and the OFCS.
The Gz reference point enables transport of service data flow based offline charging information.
The Gz interface is specified in TS 32.240 [3]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.6 S9 reference point | The S9 reference point resides between a PCRF in the HPLMN (H‑PCRF) and a PCRF in the VPLMN (V‑PCRF).
For roaming with a visited access (PCEF and, if applicable, BBERF in the visited network), the S9 reference point enables the H‑PCRF to (via the V‑PCRF):
- have dynamic PCC control, including the PCEF and, if applicabl... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.7 Gxx reference point | The Gxx reference point resides between the PCRF and the BBERF. This reference point corresponds to the Gxa and Gxc, as defined in TS 23.402 [18] and further detailed in the annexes.
The Gxx reference point enables a PCRF to have dynamic control over the BBERF behaviour.
The Gxx reference point enables the signalling o... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.8 Sd reference point | The Sd reference point resides between the PCRF and the TDF.
The Sd reference point enables a PCRF to have dynamic control over the application detection and control behaviour at a TDF.
The Sd reference point enables the signalling of ADC decision, which governs the ADC behaviour and it supports the following functions... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.9 Sy reference point | The Sy reference point resides between the PCRF and the OCS.
The Sy reference point enables transfer of policy counter status information relating to subscriber spending from OCS to PCRF and supports the following functions:
- Request for reporting of policy counter status information from PCRF to OCS and subscribe to ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.10 Gyn reference point | The Gyn reference point resides between the OCS and the TDF.
The Gyn reference point allows online credit control for charging in case of ADC rules based charging in TDF. The functionalities required across the Gyn reference point are defined in TS 32.251 [9] and is based on RFC 4006 [4]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.11 Gzn reference point | The Gzn reference point resides between the TDF and the OFCS.
The Gzn reference point enables transport of offline charging information in case of ADC rule based charging in TDF.
The Gzn interface is specified in TS 32.240 [3]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.12 Np reference point | The Np reference point resides between the RCAF and the PCRF.
The Np reference point enables transport of RAN User Plane Congestion Information (RUCI) sent from the RCAF to the PCRF for all or selected subscribers, depending on the operator's congestion mitigation policy.
The Np reference point supports the following f... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.13 Nt reference point | The Nt reference point enables the negotiation between the SCEF and the PCRF about the recommended time window(s) and the related conditions for future background data transfer. The SCEF is triggered by an SCS/AS (as described in TS 23.682 [42]) which requests for this negotiation and provides necessary information to ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.14 St reference point | The St reference point resides between the TSSF and the PCRF.
The St reference point enables the PCRF to provide traffic steering control information to the TSSF.
The St reference point supports the following functions:
- Provision, modification and removal of traffic steering control information from PCRF to the TSSF. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.15 Nu reference point | The Nu reference point resides between the SCEF and the PFDF and enables the 3rd party service provider to manage PFDs in the PFDF as specified in TS 23.682 [42]. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.16 Gw reference point | The Gw reference point resides between the PFDF and the PCEF.
The Gw reference point enables transport of PFDs from the PFDF to the PCEF for a particular Application Identifier or for a set of Application Identifiers.
The Gw reference point supports the following functions:
- Creation, updating and removal of individua... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 5.2.17 Gwn reference point | The Gwn reference point resides between the PFDF and the TDF.
The Gwn reference point enables transport of PFDs from the PFDF to the TDF for a particular Application Identifier or for a set of Application Identifiers.
The Gwn reference point supports the following functions:
- Creation, updating and removal of individu... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6 Functional description | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1 Overall description | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.0 General | The PCC architecture works on a service data flow level. The PCC architecture provides the functions for policy and charging control as well as event reporting for service data flows. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.1 Binding mechanism | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.1.1 General | The binding mechanism is the procedure that associates a service data flow (defined in a PCC and QoS rule, if applicable, by means of the SDF template), to the IP‑CAN bearer deemed to transport the service data flow. For service data flows belonging to AF sessions, the binding mechanism shall also associate the AF sess... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.1.2 Session binding | Session binding is the association of the AF session information to one and only one IP‑CAN session.
The PCRF shall perform the session binding, which shall take the following IP‑CAN parameters into account:
a) The UE IPv4 address and/or IPv6 network prefix;
b) The UE identity (of the same kind), if present.
NOTE 1: In... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.1.3 PCC rule authorization and QoS rule generation | PCC Rule authorization is the selection of the QoS parameters (QCI, ARP, GBR, MBR, etc.) for the PCC rules.
The PCRF shall perform the PCC rule authorization for complete dynamic PCC rules belonging to AF sessions that have been selected in step 1, as described in clause 6.1.1.2, as well as for PCC rules without corres... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.1.4 Bearer Binding | Bearer binding is the association of the PCC rule and the QoS rule (if applicable) to an IP‑CAN bearer within that IP‑CAN session. This function resides in the Bearer Binding Function (BBF).
The Bearer Binding Function is located either at the BBERF or at the PCEF, depending on the architecture (see clause 5.1). The BB... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.2 Reporting | Reporting refers to the differentiated IP‑CAN resource usage information (measured at the PCEF/TDF) being reported to the online or offline charging functions.
NOTE 1: Reporting usage information to the online charging function is distinct from credit management. Hence multiple PCC/ADC rules may share the same charging... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.3 Credit management | The credit management applies for online charging only and shall operate on a per charging key basis. The PCEF should initiate one credit management session with the OCS for each IP‑CAN Session subject to online charging, unless specified otherwise in an IP‑CAN specific annex. Alternatively, the PCEF may initiate one c... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.4 Event Triggers | The Event Reporting Function (ERF) performs event trigger detection. When an event matching the event trigger occurs, the ERF shall report the occurred event to the PCRF. The Event Reporting Function is located either at the PCEF or, at the BBERF (if applicable) or, at the TDF for solicited application reporting (if ap... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.5 Policy Control | Policy control comprises functionalities for:
- Binding, i.e. the generation of an association between a service data flow and the IP‑CAN bearer transporting that service data flow;
- Gating control, i.e. the blocking or allowing of packets, belonging to a service data flow or specified by an application identifier, to... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.6 Service (data flow) Prioritization and Conflict Handling | Service pre-emption priority enables the PCRF 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.
For example, when supporting network controlled QoS, the PCRF may use the pre-emption ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.7 Standardized QoS characteristics | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.7.1 General | The service level (i.e. per SDF or per SDF aggregate) QoS parameters are QCI, ARP, GBR and MBR.
Each Service Data Flow (SDF) is associated with one and only one QoS Class Identifier (QCI). For the same IP‑CAN session multiple SDFs with the same QCI and ARP can be treated as a single traffic aggregate which is referred ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.7.2 Standardized QCI characteristics | This clause specifies standardized characteristics associated with standardized QCI values. The characteristics describe the packet forwarding treatment that an SDF aggregate receives edge-to-edge between the UE and the PCEF (see figure 6.1.7‑1) in terms of the following performance characteristics:
1 Resource Type (GB... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.7.3 Allocation and Retention Priority characteristics | The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. The priority level defines the relative importance of a resource request. This allows deciding whether a bearer establishment or modification request can be accepted or needs to be rejected... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.8 Termination Action | The termination action applies only in case of online charging. The termination action indicates the action, which the PCEF/TDF should perform when no more credit is granted. A packet that matches a PCC rule/ADC rule, indicating a charging key for which no credit has been granted, is subject to a termination action.
Th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.9 Handling of packet filters provided to the UE by PCEF/BBERF | The network shall ensure that the traffic mapping information negotiated with the UE reflects the bearer binding of PCC/QoS rules, except for those extending the inspection beyond what can be signalled to the UE. The PCC/QoS rules may restrict what traffic is allowed compared to what is explicitly negotiated with the U... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10 IMS Emergency Session Support | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.1 Architecture model and Reference points | Emergency bearer services (i.e. IP-CAN session for the IMS emergency services) are provided by the serving network to support IMS emergency when the network is configured to support emergency services. Emergency services are network services provided through an Emergency APN and may not require a subscription depending... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.2 PCC Rule Authorization and QoS rule generation | The PCC Rule Authorization and QoS Rule generation function selects QoS parameters that allow prioritization of IMS Emergency sessions. If an IMS Emergency session is prioritized the QoS parameters shall contain an ARP value that is reserved for intra-operator use of IMS Emergency services. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.3 Functional Entities | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.3.1 PCRF | The PCRF shall determine based on the PDN-id if an IP-CAN Session concerns an IMS emergency session.
For an IP-CAN session serving an IMS emergency session, the PCRF makes authorization and policy decisions that restrict the traffic to emergency destinations, IMS signalling and the traffic to retrieve user location inf... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.3.2 PCEF | The PCEF initiates the IP‑CAN Session termination if the last PCC rule for this IP‑CAN session is removed according to existing procedure.
In addition, at reception of an IP‑CAN Session Modification Request triggered by the PCRF for an IP‑CAN session serving an IMS emergency session that removes all PCC rules with a QC... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.3.3 P-CSCF | The P‑CSCF performs according to existing procedure:
- At reception of an indication that an IMS emergency session is established, the P‑CSCF sends IMS service information to the PCRF.
- At reception of an indication that an IMS emergency session is released, the P‑CSCF interacts with the PCRF to revoke the IMS service... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.10.4 PCC Procedures and Flows | At Indication of IP-CAN Session Establishment that includes a PDN-id that identifies an Emergency APN the PCRF ignores subscription information from the SPR. The PCRF uses locally configured operator policies to make authorization and policy decisions.
At Indication of IP-CAN Session Establishment and Gateway Control S... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11 Multimedia Priority Service Support | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.1 Architecture model and Reference points | Subscription data for MPS is provided to PCC through the Sp reference point. To support MPS service, the PCRF shall subscribe to changes in the MPS subscription data for Priority EPS Bearer Service. Dynamic invocation for MPS is provided from an AF, using the Priority indicator, over Rx. Dynamic invocation for Data Tra... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.