hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.2 PCC rule authorization and QoS rule generation | For MPS service, the PCRF shall generate the corresponding PCC/QoS rule(s) with the ARP/QCI parameters as appropriate for the prioritized service.
For non-MPS service, the PCRF shall generate the corresponding PCC/QoS rule(s) as per normal procedures, without consideration whether the MPS Priority EPS Bearer Service is... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.3 Priority EPS Bearer Service | The MPS Priority EPS Bearer Service targets the ARP and/or QCI of bearer(s), enabling the prioritization of all traffic on the same bearer.
The PCRF shall, at the activation of the Priority EPS Bearer Service:
- modify the ARP of the default bearer as appropriate for the Priority EPS Bearer Service under consideration ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.4 Bearer priority for IMS Multimedia Priority Services | In addition to the mechanism specified in clause 6.1.11.2, IMS Multimedia Priority Services may require upgrade of the dedicated IM CN signalling bearer and the default bearer, e.g. in order to mitigate the IP-CAN session termination due to resource limitation at a location change the default bearer and dedicated IM CN... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.5 Bearer priority for MPS for Data Transport Service | MPS for Data Transport Service enables the prioritization of all traffic on the default bearer and other bearers upon AF request. The QoS modification to the default bearer and other bearers is done based on operator policy and regulatory rules by means of local PCRF configuration.
NOTE 1: If no configuration is provid... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.11.6 Priority for MPS for Messaging | MPS for Messaging (specified in clause 4.3.18.1 of TS 23.401 [17]) requires MPS priority on the IM CN signalling bearer for messages delivered via SMS over IP (TS 23.204 [56]) and via IMS Messaging (clause 5.16 of TS 23.228 [39]). IMS Session-based Messaging also requires MPS priority for media flow(s).
When the P-CSCF... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.12 ADC rule authorization | ADC Rule authorization refers to the PCRF decision about which predefined and/or dynamic ADC rules to activate for a TDF session and is only applicable in case of solicited application reporting.
It may also comprise the selection of parameters (monitoring key, enforcement actions etc.) for dynamic ADC rules to be appl... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.13 Redirection | Redirection of application traffic is an option applicable in the TDF or the PCEF enhanced with ADC.
PCRF may control redirection by provisioning and modifying dynamic ADC rules over the Sd interface for a TDF, or dynamic PCC rules over the Gx interface for a PCEF enhanced with ADC. The PCRF may enable/disable redirect... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.14 Resource sharing for different AF sessions | The P-CSCF (i.e. AF) may indicate to the PCRF that media of an AF session may share resources with media belonging to other AF sessions according to TS 23.228 [39]. 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 PCRF make... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.15 Reporting of RAN user plane congestion information | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.15.1 General | RAN User Plane Congestion Information (RUCI) is reported to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions.
The RUCI includes the following information:
- The IMSI identifying the UE impacted by congestion;
- eNB identifier, ECGI or SAI identifying the eNB, E-... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.15.2 Reporting restrictions | Depending on the operator's congestion mitigation policy, it may not be necessary to have RUCI reporting for all users. An operator shall be able to specify restrictions for RUCI reporting on a per UE per APN basis. Reporting restrictions can be used to activate or deactivate the RUCI reporting. Reporting restrictions ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.15.3 UE mobility between RCAFs | A RCAF is assumed to serve a geographical area. A UE may move from the area handled by one RCAF to an area handled by a different RCAF. RCAF nodes cannot detect mobility by themselves: an RCAF node cannot differentiate whether a UE that is no longer affected by congestion has moved to another RCAF or not. When a given ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.16 Negotiation for future background data transfer | The AF may contact the PCRF via the SCEF (and the Nt interface) to request a time window and related conditions for future background data transfer.
NOTE 1: The SCEF may contact any PCRF in the operator network.
The AF request shall contain an ASP identifier, the volume of data to be transferred per UE, the expected am... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.17 Traffic Steering Control | Traffic steering control is triggered by the PCRF initiated request and consists in applying a specific (S)Gi-LAN traffic steering policy for traffic detected based on application level information or service data flow level information for the purpose of steering the subscriber's selected traffic to appropriate (S)Gi-... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.18 PCC support of NBIFOM | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.18.1 General | Clause 6.1.18 refers to Network Based IP Flow Mobility as described in TS 23.161 [43].
When PCC control for NBIFOM applies for an IP-CAN session:
- Multiple IP-CAN types (3GPP EPS and Non 3GPP EPS) may be simultaneously associated with the same IP-CAN session.
- The PCRF sends PCC rules including NBIFOM related informa... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.18.2 NBIFOM impacts on IP-CAN procedures | PCC support of NBIFOM requires following modifications to IP-CAN session procedures:
- IP-CAN session establishment.
During the IP-CAN session establishment, the PCEF informs the PCRF about the UE and network support of NBIFOM and the requested NBIFOM mode (defined in TS 23.161 [43]). The PCRF takes a policy decision o... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.19 Resource reservation for services sharing priority | To enable the usage of the same bearer, an AF may indicate to the PCRF 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 ad... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.20 Management of Packet Flow Descriptions using the PFDF | The Management of Packet Flow Descriptions (PFDs) enables the PCEF and TDF to perform accurate application detection when PFDs are provided by an ASP (via the SCEF and the PFDF) and then to apply enforcement actions as instructed in the PCC/ADC Rule.
The operator is able to configure pre-defined PCC/ADC Rules in the PC... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.1.21 3GPP PS Data Off | This feature, when activated by the user, prevents downlink traffic and may prevent uplink traffic via 3GPP access except for 3GPP PS Data Off Exempt Services.
NOTE 1: Preventing uplink packets that don't belong to 3GPP Data Off Exempt Services in PDN GW implies that the exempt uplink packets in the UE have traversed t... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2 Functional entities | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1 Policy Control and Charging Rules Function (PCRF) | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.0 General | The PCRF encompasses policy control decision and flow based charging control functionalities.
The PCRF provides network control regarding the service data flow detection, gating, QoS and flow based charging (except credit management) towards the PCEF and/or TDF.
The PCRF provides network control regarding the applicati... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.1 Input for PCC decisions | The PCRF shall accept input for PCC decision-making from the PCEF, the BBERF if present, the TDF if present, the SPR and if the AF is involved, from the AF, as well as the PCRF may use its own predefined information. These different nodes should provide as much information as possible to the PCRF. At the same time, the... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.2 Subscription information management in the PCRF | The PCRF may request subscription information from the SPR for an IP‑CAN session at establishment or a gateway control session at establishment. The subscription information may include user profile configuration indicating whether application detection and control should be enabled. The PCRF should specify the subscri... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.3 V-PCRF | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.3.1 General | The V-PCRF (Visited-Policy and Charging Rules Function) is a functional element that encompasses policy and charging control decision functionalities in the V-PLMN. The V-PCRF includes functionality for both home routed access and visited access (local breakout).
The V‑PCRF determines based on the subscriber identity i... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.3.2 V-PCRF and Home Routed Access | The V-PCRF provides functions to proxy Gxx interactions between the BBERF and the H-PCRF as follows:
- Gateway Control Session establishment and termination;
- Gateway Control and QoS Policy Rules Provision;
- Gateway Control and QoS Rule Request.
The V-PCRF provides functions to enforce visited operator policies regar... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.3.3 V-PCRF and Visited Access (local breakout) | The V-PCRF provides functions to:
- Enforce visited operator policies regarding QoS authorization requested by the home operator e.g. on a per QCI or service basis as indicated by the roaming agreements. The V-PCRF informs the H-PCRF when a request has been denied and may provide the acceptable QoS Information for the ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.4 H-PCRF | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.4.1 General | The H‑PCRF (Home‑Policy and Charging Rules Function) is a functional element that encompasses policy and charging control decision functionalities in the H‑PLMN and in the VPLMN. The H‑PCRF includes functionality for both home routed access and visited access (local breakout).
If a Gateway Control Session is used and a... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.4.2 H-PCRF and Home Routed Access | The H‑PCRF shall use the S9 reference point to proxy information to the BBERF via the V‑PCRF for the following related Gxx procedures:
‑ Gateway Control Session establishment and termination;
‑ Gateway Control and QoS Policy Rules Provision;
‑ Gateway Control and QoS Rule Request.
If an IP‑CAN session termination is re... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.4.3 H-PCRF and Visited Access (Local Breakout) | The H‑PCRF shall use the S9 reference point to proxy information to the PCEF (and indirectly also to the BBERF when the Gateway Control Session is not proxied to the H-PCRF and indirectly also to the TDF) via the V‑PCRF for the following related Gx procedures:
- Indication of IP‑CAN Session Establishment and Terminatio... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.5 Handling of Multiple BBFs associated with the same IP‑CAN session | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.5.1 Handling of two BBFs associated with the same IP-CAN session during handover | The procedures specified in this clause apply when the case of multiple BBFs occurs during handovers. The two BBFs can be located in two separate BBERFs, or one BBF is located in the PCEF and the other one in a BBERF. If the PCRF determines that there is more than one BBF associated with the same IP‑CAN session, the PC... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.1.5.2 Handling of multiple BBFs with IP-CAN session flow mobility | The procedures specified in this clause apply when the case of multiple BBFs occurs during flow mobility scenarios as specified in TS 23.261 [23]. The multiple BBFs can be located in either separate BBERFs, or one BBF is located in the PCEF and the other ones in separate BBERFs. If the PCRF determines that there is mor... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2 Policy and Charging Enforcement Function (PCEF) | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.1 General | The PCEF encompasses service data flow detection, policy enforcement and flow based charging functionalities.
This functional entity is located at the Gateway (e.g. GGSN in the GPRS case and PDG in the WLAN case). It provides service data flow detection, user plane traffic handling, triggering control plane session man... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.2 Service data flow detection | This clause refers to the detection process that identifies the packets belonging to a service data flow. Each PCC rule contains a service data flow template, which 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 detecti... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.3 Measurement | The PCEF shall support 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 application detection filt... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.4 QoS control | The PCEF enforces the authorized QoS for an IP‑CAN bearer according to the information received via the Gx interface and depending on the bearer establishment mode.
Only the GBR per bearer is used for resource reservation (e.g. admission control in the RAN). The MBR (per PCC rule / per bearer) is used for rate policing... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.5 Application Detection | The PCEF shall detect Start and Stop of the application traffic for the PCC rules used for application detection (i.e. with application identifier) that the PCRF has activated at the PCEF. The PCEF shall report, if the PCRF has subscribed to the event, unless the notification is muted for the specific PCC Rule, to the ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.2.6 Traffic steering | When the PCRF provides a Traffic Steering Policy Identifier(s) in a PCC rule, the PCEF shall enforce the referenced traffic steering policy for the service data flow. A traffic steering policy is locally configured and can be used for the uplink, the downlink or for both directions.
To enforce the traffic steering poli... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 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 IP‑CAN user plane behaviour. The AF shall communicate with the PCRF to transfer dynamic session information, required for PCRF decisions as well as to receive IP‑CAN specific information and no... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.4 Subscription Profile Repository (SPR) | The SPR logical entity contains all subscriber/subscription related information needed for subscription-based policies and IP‑CAN bearer level PCC rules by the PCRF. The SPR may be combined with or distributed across other databases in the operator's network, but those functional elements and their requirements for the... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.5 Online Charging System | The Online Charging System (OCS) performs online credit control functions as specified in TS 32.240 [3].
The OCS may trigger the PCEF to initiate an IP‑CAN bearer service termination at any point in time.
NOTE: As the OCS performs the credit control per charging key basis (and thus has not necessarily the knowledge abo... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.6 Offline Charging System (OFCS) | The Offline Charging System is specified in TS 32.240 [3].
There may be several OFCSs in a PLMN. The default OFCS addresses (i.e. the primary address and secondary address) shall be locally pre-configured within the PCEF and TDF. OFCS addresses may also be passed once per IP‑CAN session or TDF session from the PCRF to ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.7 Bearer Binding and Event Reporting Function (BBERF) | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.7.1 General | The BBERF includes the following functionalities:
- Bearer binding.
- Uplink bearer binding verification.
- Event reporting to the PCRF.
- Sending or receiving IP‑CAN-specific parameters, to or from the PCRF. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.7.2 Service data flow detection | The service data flow detection at the BBERF is identical to the detection at PCEF with the following modifications:
- If the service data flow is tunnelled at the BBERF, the BBERF uses information on the mobility protocol tunnelling header provided by the PCRF and the QoS rules to detect the service data flows.
For th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.7.3 QoS Control | The ARP, GBR, MBR and QCI are used by the BBERF in the same way as in the PCEF for resource reservation.
When access network is not utilizing QCI based QoS parameters, the BBERF shall be able to convert a QoS class identifier value to QoS attribute values used in the access network and determine the QoS class identifie... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.8 User Data Repository (UDR) | The UDR is a functional entity that acts as a single logical repository storing user data. As such it may contain all subscriber/subscription related information needed by the PCRF. In deployment scenarios where the UDR is used it replaces the SPR. The UDR provides a unique reference point to fetch these subscriber/sub... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.9 Traffic Detection Function (TDF) | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.9.1 General | The TDF is a functional entity that performs application detection and reporting of detected application and its service data flow description to the PCRF. The TDF supports solicited application reporting and/or unsolicited application reporting. The application detection filter may be extended with the PFDs provided b... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.9.2 Traffic steering | When the PCRF provides a Traffic Steering Policy Identifier(s) in an ADC rule, the TDF shall enforce the referenced traffic steering policy for the application. A traffic steering policy is locally configured and can be used for the uplink, the downlink or for both directions.
To enforce the traffic steering policy, th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.10 RAN Congestion Awareness Function (RCAF) | A RAN Congestion Awareness Function (RCAF) is an element which reports RAN User Plane Congestion Information (RUCI) via the Np interface to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. The RCAF sends the RUCI to the PCRFs serving the UEs' PDN connections as... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.11 Service Capability Exposure Function (SCEF) | A Service Capability Exposure Function (SCEF) is an element which provides a means to securely expose the services and capabilities provided by 3GPP network interfaces (for further details see TS 23.682 [42]). |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.12 Traffic Steering Support Function (TSSF) | The TSSF is a function that receives traffic steering control information from the PCRF and ensures that the related traffic steering policy is enforced in the (S)Gi-LAN.
A traffic steering policy is locally configured in TSSF and can be used for uplink, downlink or for both directions. To ensure that the traffic steer... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.2.13 Packet Flow Description Function (PFDF) | A Packet Flow Description Function (PFDF) is an element which stores PFDs associated with an application identifier and transfers them to the PCEF/TDF via Gw/Gwn interface to enable the PCEF/TDF to perform application detection when the PFDs are managed by a 3rd party SP.
The PFDF receives PFDs for an application ident... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.3 Policy and charging control rule | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 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 of... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.3.2 Policy and charging control rule operations | Policy and charging control rule operations consist of activation, modification and de-activation of PCC rules.
Activation of a dynamic PCC rule provides the PCC rule information to the PCEF via the Gx reference point.
Activation of a predefined PCC rule provides an identifier of the relevant PCC rule to the PCEF via t... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.4 IP‑CAN bearer and IP‑CAN session related policy information | The purpose of the IP‑CAN bearer and IP‑CAN session related policy information is to provide policy and charging control related information that is applicable to a single IP‑CAN bearer or the whole IP‑CAN session respectively. The PCRF provides the IP‑CAN bearer and IP‑CAN session related policy information to the PCE... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.5 Quality of Service Control rule | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.5.1 General | The Quality of Service control rule (QoS rule) comprises the information that is required to enable the user plane detection and the QoS control for a service data flow in the BBERF. The packets detected by applying the service data flow template of a QoS rule are designated a service data flow.
NOTE 1: The BBERF only ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.5.2 Quality of Service control rule operations | QoS control rule operations consist of activation, modification and de-activation of QoS rules.
Activation of a dynamic QoS rule provides the QoS rule information to the BBERF via the Gxx reference point.
An active QoS rule means that:
- the service data flow template shall be used for service data flow detection;
- th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.6 Usage Monitoring Control specific information | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.6.1 General | The Usage Monitoring Control information comprises the information that is required to enable user plane monitoring of resources for individual applications/services, groups of applications/services, for an IP-CAN session or for a TDF session.
Table 6.6: Usage Monitoring Control related information
Information name
Des... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.6.2 Usage Monitoring Control operations | Usage monitoring on IP‑CAN session, TDF session or monitoring key level is active in the PCEF or TDF provided that certain conditions are met. The conditions for continued monitoring on session level are:
- For IP-CAN session level monitoring at the PCEF, an IP-CAN session is active and a volume and/or time threshold v... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.7 S2c based IP flow mobility Routing rule | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.7.1 General | The clause 6.7 refers to UE based IP flow mobility as described in TS 23.261 [23].
The routing rule comprises the information that is required for the PCRF to install the QoS rules for a service data flow at the right BBERF in flow mobility scenarios. The PCRF relies on the IP flow mobility routing information containe... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.7.2 Routing rule operations | IP flow mobility routing rule operations consist of installation, modification and removal of routing rules.
During installation of a routing rule, the PCEF provides the routing rule information to the PCRF via the Gx reference point. The PCRF uses all the installed routing rules related to an IP‑CAN Session to select ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.8 Application Detection and Control Rule | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.8.1 General | The Application Detection and Control rule (ADC rule) comprises the information that is required in order to:
- identify the rule;
- detect the Start and Stop of traffic for a certain application;
- apply enforcement actions and charging for the application traffic detected by the rule;
- apply charging for the applica... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.8.2 Application Detection and Control rule operations over Sd | Application Detection and Control rule operations apply to solicited reporting and consist of activation, modification and deactivation of ADC rules.
Activation: The PCRF provides the ADC Rule identifier to the TDF. The PCRF may provide data for usage monitoring and enforcement control for a dynamic ADC rule.
An active... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.9 Policy decisions based on spending limits | Policy decisions based on spending limits is a function that allows PCRF taking actions related to the status of policy counters that are maintained in the OCS.
The identifiers of the policy counters that are relevant for a policy decision in the PCRF may be stored in the PCRF or possibly in SPR. The PCRF is configured... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.11 Traffic Steering Control Information | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.11.1 General | The traffic steering control information comprises the information that is required to enable traffic steering for a detected application or service data flow. The traffic steering control information is transferred:
- From the PCRF to the PCEF within PCC rules over Gx reference point;
- From the PCRF to the TDF within... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.11.2 Traffic Steering Control Operations over St | Traffic steering control operations over St consists of provisioning, modification and removal of traffic steering control information.
Provisioning: Provisioning of traffic steering control information to the TSSF includes the activation of traffic steering policy, so that the traffic detected by the service data flow... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.12 NBIFOM Routing rule | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.12.1 General | The NBIFOM routing rule comprises the information about the UE request to associate an access type to a service data flow filter. The NBIFOM routing rules are provided by the PCEF to the PCRF during IP‑CAN session establishment or modification.
The PCEF derives NBIFOM routing rules based on the Routing Rules received f... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 6.12.2 NBIFOM Routing rule operations | NBIFOM routing rule operations consist of creation, modification and removal of a NBIFOM routing rule.
At creation of a NBIFOM routing rule, the PCEF provides the NBIFOM routing rule information to the PCRF. The PCRF checks if there is a PCC Rule with a corresponding service data flow template installed in the PCEF. If... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7 PCC Procedures and flows | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.1 Introduction | The specification of the PCC procedures and flows is valid for the general scenario. Access specific information is included in Annex A, Annex D, Annex H and Annex P.
The description includes procedures for IP‑CAN Session Establishment, Modification and Termination. The IP‑CAN Session modification comprises IP‑CAN bear... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.2 IP‑CAN Session Establishment | This clause describes the signalling flow for IP‑CAN Session establishment as well as network prefix and/or IP address assignment to the UE. The AF is not involved.
Figure 7.2-1: IP‑CAN Session Establishment
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Sessi... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.3 IP‑CAN Session Termination | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.3.1 UE initiated IP‑CAN Session termination | Figure 7.3.1: IP‑CAN Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access is used (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), the V‑PCRF should proxy the GW (BBERF) initiated Gateway Control... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.3.2 GW (PCEF) initiated IP‑CAN Session termination | Figure 7.3.2: GW (PCEF) Initiated IP‑CAN Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access is used (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), the V‑PCRF should proxy the GW (BBERF) initi... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.4 IP‑CAN Session Modification | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.4.1 IP‑CAN Session Modification; GW (PCEF) initiated | This clause describes the signalling flow for the IP‑CAN Session modification initiated by the GW (PCEF). These modifications include IP‑CAN bearer establishment and termination as well as modification if the triggering conditions given to the PCEF are fulfilled.
For the PCEF enhanced with ADC, the reason for such a mo... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.4.2 IP‑CAN Session Modification; PCRF initiated | This clause describes the signalling flow for the IP‑CAN Session modification initiated by the PCRF. The AF or TDF or the OCS or the TSSF may be involved. An example of PCRF inputs that may trigger the procedure include:
- Initiation and authorization of a session-based service for which an IP‑CAN Session is modified.
... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.4.3 Void | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.5 Update of the subscription information in the PCRF | Figure-7.6: Procedure for update of the subscription information in the PCRF
1. The SPR detects that the related subscription profile of an IP‑CAN session has been changed.
2. If requested by the PCRF, the SPR notifies the PCRF on the changed profile.
3. The PCRF responds to the SPR.
4. The PCRF stores the updated prof... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.6 PCRF Discovery and Selection | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.6.1 General principles | This clause describes the underlying principles for PCRF selection and discovery:
- A single logical PCRF entity may be deployed by means of multiple and separately addressable PCRFs.
- The H‑PCRF must be able to correlate the AF service session information received over Rx with the right IP‑CAN session (PCC Session bi... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.6.2 Solution Principles | In order to ensure that all Diameter sessions for Gx, S9, Gxa/Gxc, Rx, Sd (when the unsolicited application reporting applies) and Np for a certain IP‑CAN session reach the same PCRF when multiple and separately addressable PCRFs have been deployed in a Diameter realm, an optional logical "Diameter Routing Agent (DRA)"... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7 Gateway Control Session Procedures | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.1 Gateway Control Session Establishment | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.1.0 General | There are two cases considered for Gateway Control Session Establishment:
1. The PCEF establishes the IP‑CAN Session during the Gateway Control session establishment. This happens when the UE attaches to the EPC for the first time and when the UE establishes a new PDN Connection.
2. There exists an established IP‑CAN S... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.1.1 Gateway Control Session Establishment during Attach | Figure 7.7.1.1-1: Gateway Control Session Establishment during Attach
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Establishment between the BBERF in the VPLMN and the H-PCRF over S9 based ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.