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.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 obtains the MPS for Messaging indication, as specified in TS 23.228 [39], the P‑CSCF may send an MPS for Messaging indication to the PCRF over the Rx interface to request the PCRF to modify the IM CN signalling bearer for MPS for Messaging. If the IM CN signalling bearer does not already receive MPS priority treatment, for example based on a prior request for MPS service that upgraded the IM CN signalling bearer, or based on the IMS Signalling Priority information in the SPR (see clause 6.2.4) and under consideration of the requirements described in clause 6.1.11.2, the PCRF shall:
- modify the ARP and QCI of the IM CN signalling bearer to values appropriate for MPS for Messaging Service.
When the PCRF receives an MPS for Messaging clearing (disabling) indication via Rx, the PCRF shall, while considering other services simultaneously requiring priority treatment of the IM CN signalling bearer as described in clause 6.1.11.2:
- modify the ARP and QCI of the IM CN signalling bearer to appropriate values according to PCRF decision. |
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 applied once the traffic is detected.
User profile configuration, received within subscription information, indicating whether application detection and control can be enabled, shall be taken into account by PCRF, when deciding on ADC rule authorization.
NOTE 1: The enforcement actions are only applicable in case of solicited application reporting.
NOTE 2: For unsolicited application reporting, all ADC rules pre-provisioned at TDF are authorized. |
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 redirection and set a redirect destination for every dynamic ADC rule or PCC rule.
Redirect information (redirection enabled/disabled and redirect destination) within a PCC Rule or within an ADC rule respectively, instructs the PCEF enhanced with ADC, or the TDF whether or not to perform redirection towards a specific redirect destination. The redirect destination may be provided as part of the dynamic PCC/ADC Rule, or may be preconfigured in the PCEF enhanced with ADC or the TDF. A redirect destination provided in a dynamic PCC/ADC Rule overrides the redirect destination preconfigured in the PCEF enhanced with ADC or in the TDF for this PCC/ADC Rule.
The redirection is enforced by the PCEF enhanced with ADC or the TDF on uplink application's traffic matching the ADC or PCC rule for which redirection is enabled. |
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 makes authorization and policy decisions for the affected AF sessions individually and generates a PCC/QoS rule for every media flow in any AF session.
If the PCRF received identical indication(s) for resource sharing for multiple AF sessions, the PCRF may request the PCEF/BBERF to realize resource sharing for the corresponding set of PCC/QoS rules. The PCRF provides a DL and/or UL sharing indication with the same value for those PCC/QoS Rules that are candidate to share resources according to the direction of resource sharing indicated by the AF.
For each direction, the PCEF/BBERF shall take the highest GBR value from each set of PCC/QoS Rules related with the same sharing indication for this direction and bound to the same bearer and uses that value as input for calculating the GBR of the bearer. For each direction, the PCEF/BBERF may take the MBR value of the most demanding PCC/QoS Rule included in each set of PCC Rules related with the same sharing indication for this direction and bound to the same bearer and uses that as input for calculating the MBR of the bearer.
The AF session termination or modification procedure that removes media flows triggers the removal of the corresponding PCC/QoS Rules from the PCEF/BBERF. The PCEF/BBERF shall recalculate the GBR (and MBR) value of the bearer whenever a set of PCC/QoS Rules with the same sharing indication changes.
Resource sharing is applied as long as there are at least two active PCC/QoS rules with the same sharing indication bound to the same bearer.
Resource sharing for different AF sessions is possible only if the P-CSCF, the PCRF and the PCEF/BBERF support it.
NOTE: This procedure assumes that applications/service logic must do the necessary coordination, e.g. pause sending or employ gating, to avoid service data flows interfering and to ensure that multiple flows comply with the combined QoS parameters. |
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-UTRAN cell or Service Area, respectively, serving the UE.
NOTE: Whether in case of E-UTRAN the eNB identifier or the ECGI is included in the RUCI is up to operator configuration in the RCAF.
- APN for which congestion information is reported;
- Congestion level or an indication of the "no congestion" state. |
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 can also be used to limit RUCI reporting. This is achieved by defining one or more sets of congestion levels, such that the RCAF indicates only that the UE experiences a congestion level within the given set but does not indicate the congestion level itself within that set. The sets must be non-overlapping such that a congestion level belongs to a single set only. Reporting restrictions can also be used to deactivate reporting of the congested cell's identifier as part of the RUCI.
NOTE: The support for the reporting restrictions is optional and used only if both the PCRF and the RCAF support this feature. |
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 RCAF indicates no congestion to the PCRF for a given UE on the Np interface, this should be interpreted as no congestion experienced at the given RCAF which does not exclude that another RCAF may report that the same UE experiences congestion.
Consistent operation for UE mobility is ensured by applying the following rules at the PCRF.
- The PCRF maintains the RCAF which has last indicated that the UE is affected by congestion.
- When a new RCAF indicates that the UE is affected by congestion, the PCRF sends a message to the old RCAF to explicitly release context at the old RCAF. |
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 amount of UEs, the desired time window and optionally, network area information (e.g. list of cell ids, TAs/RAs).
NOTE 2: A 3rd party application server is typically not able to provide any specific network area information and if so, the AF request is for the whole operator network.
The PCRF shall first retrieve all existing transfer policies stored for any ASP from the SPR. Afterwards, the PCRF shall determine, based on the information provided by the AF and other available information (e.g. network policy, congestion level (if available), load status estimation for the required time window and network area, existing transfer policies) one or more transfer policies.
A transfer policy consists of a recommended time window for the background data transfer, a reference to a charging rate for this time window and optionally a maximum aggregated bitrate (indicating that the charging according to the referenced charging rate is only applicable for the aggregated traffic of all involved UEs that stays below this value). Finally, the PCRF shall provide the transfer policies to the AF together with a reference ID. If the AF received more than one transfer policy, the AF shall select one of them and inform the PCRF about the selected transfer policy.
NOTE 3: The maximum aggregated bitrate (optionally provided in a transfer policy) is not enforced in the network. The operator may apply offline CDRs processing (e.g. combining the accounted volume of the involved UEs for the time window) to determine whether the maximum aggregated bitrate for the set of UEs was exceeded by the ASP and charge the excess traffic differently.
NOTE 4: It is assumed that the 3rd party application server is configured to understand the reference to a charging rate based on the agreement with the operator.
The selected transfer policy is finally stored by the PCRF in the SPR together with the reference ID and the network area information. The same or a different PCRF can retrieve this transfer policy and the corresponding network area information from the SPR and take them into account for future decisions about transfer policies for background data related to the same or other ASPs.
At the time the background data transfer is about to start, the AF provides for each UE the reference ID together with the AF session information to the PCRF (via the Rx interface). The PCRF retrieves the corresponding transfer policy from the SPR and derives the PCC rules for the background data transfer according to this transfer policy.
NOTE 5: The AF will typically contact the PCRF for the individual UEs to request sponsored connectivity for the background data transfer.
NOTE 6: A transfer policy is only valid until the end of its time window. The removal of outdated transfer policies from the SPR is up to implementation. |
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-LAN service functions deployed by the operator or 3rd party service provider.
The PCRF uses one or more pieces of information such as network operator's policies, user subscription, user's current RAT, network load status, application identifier, time of day, UE location, APN, related to the subscriber session and the application traffic as input for selecting a traffic steering policy.
The PCRF controls traffic steering in the PCEF, TDF or TSSF by provisioning and modifying traffic steering control information. Traffic steering control information consists of a traffic description and a reference to a traffic steering policy that is configured in the PCEF, TDF or TSSF.
The PCEF, TDF or TSSF performs necessary actions to enforce the traffic steering policy referenced by the PCRF. For enforcing the traffic steering policy, the PCEF, TDF or TSSF may support traffic steering related functions as defined by other standard organizations. The mechanism used for routing the traffic between the service functions within the (S)Gi-LAN, is out of 3GPP scope.
The traffic steering control may be deployed using PCEF only, using TDF only, or using TSSF only, or using a combination of PCEF/TDF and TSSF.
When a combination of PCEF/TDF with traffic steering control feature and TSSF is deployed, the PCEF/TDF is utilized for application detection and packet marking while traffic steering is done using TSSF. In this case the PCC/ADC Rules provided to the PCEF/TDF for application detection shall be at application level while the traffic steering control information provided to the TSSF for traffic detection and steering control shall be at service data flow level only, i.e. the Application identifier and Traffic steering policy identifier shall be included over Gx/Sd reference point for detection of the traffic and packet marking and the Service data flow filter(s) and Traffic steering policy identifier shall be included over St reference point for traffic steering control. The value used for packet marking at the PCEF/TDF (according to the Traffic steering policy identifier received from the PCRF) shall be the same as the one within the Service data flow filter (using filter information described in clause 6.2.2.2) that is sent to the TSSF and used for traffic steering. Alternatively, the Application Identifier may be used for traffic detection at the TSSF. In this case the value used for packet marking at the PCEF/TDF (according to the Traffic steering policy identifier received from the PCRF) shall be the same as the one configured in the TSSF for that Application Identifier.
NOTE 1: The above principle also enables a deployment scenario in which the PCEF/TDF acts as an uplink traffic classifier while the downlink traffic classifier, located in (S)Gi-LAN, acts only at service data flow filter level. This deployment scenario is applicable for applications with deducible service data flow filters only. In this case, the PCEF/TDF deduces the downlink service data flow description and communicates the related information to the downlink classifier.
NOTE 2: The SDF filter(s) can be used for traffic detection at the TSSF when the PCEF/TDF is configured to do packet marking and forwarding using ToS or TC values in the IP header. The Application Identifier can be used when the PCEF/TDF is configured to do packet marking and forwarding using e.g. GRE or NSH. |
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 information as defined in clause 6.3.1.
- In UE-initiated NBIFOM mode this is based on Routing Rules received from the UE.
- For network-initiated NBIFOM mode, the PCRF determines the NBIFOM related information for a PCC rule as defined in clause 6.2.1.1 (including information about UE requested mapping of IP flows to an access, Change of usability of an Access).
- A change of access may trigger the modification of the charging key or the monitoring key in a PCC rule if access dependent charging or usage monitoring is required by the operator.
- The PCRF decides whether NBIFOM applies for the IP-CAN session, based on information about the support for NBIFOM received from the PCEF and operator policies that may take into account subscription information.
- The PCEF notifies the PCRF when an access is added or removed using the event trigger defined in clause 6.1.4.
- The PCEF notifies the PCRF when an access becomes Unusable or Usable again or when the move-to-WLAN or move-from-WLAN event occurs, both events are notified to the PCRF using the event trigger "Change of the usability of an access" as defined in clause 6.1.4.
- The PCRF may reject the NBIFOM Routing Rules received from the UE based on user subscription.
In following conditions the PCRF mentioned above is the H-PCRF:
- The UE is served by its HPLMN, or
- The PDN connection is served by a PGW in the Home PLMN (Home Routed roaming configuration), or
- The PDN connection is served by a PGW in the V-PLMN (LBO configuration) and S9 is deployed and the V-PCRF supports NBIFOM. In that case, the V-PCRF acts as a relay of information.
The PCRF mentioned above is the V-PCRF in the case when, through roaming agreement, the HPLMN operator allows the VPLMN operator to operate the V-PCRF without S9; this includes authorization of roamers to use NBIFOM. In that case, network control related with subscription such as checking the total usage allowance does not apply.
NOTE 1: If the Home operator wants to enforce control of the NBIFOM functionality on a PDN connection by the H-PCRF, the Home operator should ensure that the Home Routed roaming configuration applies to this PDN connection.
NOTE 2: NBIFOM may be deployed without PCC support. This is defined in TS 23.161 [43].
In a multi access IP-CAN session, every PCC Rule is associated to one allowed access within the IP-CAN session. The information about the allowed access may be explicitly included in the PCC Rule, within the Allowed Access Type. Otherwise, the default NBIFOM access for the traffic on the IP-CAN session shall be applied as allowed access for a PCC rule. The bearer binding mechanism in the PCEF shall, in addition to the requirements defined in 6.1.1.4, ensure that a PCC Rule is associated to an IP-CAN bearer belonging to the allowed access.
The PCEF may provide the following information for each access in a multi access IP-CAN session:
- Location of the subscriber as defined in clauses A.4, H.3 and H.4.
- A serving PLMN identifier as defined in clauses A.4, H.3 and H.4.
- RAT type as defined in clauses A.4, H.3 and H.4.
For the purpose of usage monitoring in the PCEF when NBIFOM applies for an IP-CAN session, the PCRF may receive an individual Monitoring key per access from SPR. |
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 on whether NBIFOM may apply to the IP-CAN session (the hPCRF decides the NBIFOM mode according to TS 23.161 [43]) and informs the PCEF about its decision.
- Addition of an access.
When the PCEF receives both a handover request and a NBIFOM indication from the UE, the PCEF initiates an IP-CAN Session Modification procedure, to:
- Notify the PCRF about the addition of an access to the IP-CAN session together with the IP-CAN type and the RAT type of this access. If UE-initiated NBIFOM mode was selected at IP-CAN session establishment the notification contains also the default NBIFOM access selected by the UE.
- Notify the PCRF with the NBIFOM Routing Rules, if the UE included Routing Rules with the access addition request in UE-initiated NBIFOM mode.
The PCRF takes policy decisions and communicates them to the PCEF:
- The PCRF may reject the addition of the access if the multi-access IP-CAN session would correspond to an invalid combination of IP-CAN and RAT Types or is not allowed by the subscription. In this release of the specification the only allowed combination corresponds to the UE using a 3GPP access and a WLAN access.
- If network-initiated NBIFOM mode was selected at IP-CAN session establishment, the PCRF indicates the default NBIFOM access to the PCEF.
- In UE-initiated NBIFOM mode the PCRF verifies the default NBIFOM access provided by the UE. If it complies with the subscription the PCRF provides this default NBIFOM access to the PCEF. If not, the PCRF selects a different default NBIFOM access and provides it to the PCEF.
- In UE-initiated NBIFOM mode, the PCRF may receive NBIFOM Routing Rules created by the UE. The PCRF may reject a NBIFOM Routing Rule due to subscription limitations. Otherwise, the PCRF determines for each NBIFOM Routing Rule the impacted PCC rule and provides or modifies this PCC rule.
- The PCRF shall ensure that there is at least one PCC Rule that can be bound to the default bearer of each access.
- Removal of an access.
When the PCEF is informed about the removal of an access of a multi-access IP-CAN session, the PCEF initiates an IP-CAN Session Modification procedure, to notify the PCRF about the removal of an access together with the IP-CAN type and the RAT type of this access. The PCRF determines the affected PCC rules and replies with updated PCC Rules or informs about the PCC Rules that are to be removed.
The PCC rules corresponding to the removed access are then modified or deleted by the PCEF accordingly. This shall not trigger the sending of Routing Rules deletion to the UE in Network-initiated NBIFOM mode.
NOTE 2: The UE deletes the Routing Rules locally in case of removal of access as described in TS 23.161 [43].
NOTE 3: The PCRF can also decide to trigger the removal of an access by updating or removing all PCC rules that are bound to this access. The removal of all PCC Rules bound to an access removes the access unless there are PCC Rules not known to the PCRF defined in the PCEF for this particular access.
- Network-initiated IP flow mobility within a PDN connection (Network-initiated NBIFOM mode).
When a multi-access IP-CAN session has been set-up in Network-initiated NBIFOM mode, the PCRF may at any time determine that flows should be moved from a source access to a target access. In that case, the PCRF provides updated PCC Rules with a modified Allowed Access Type and the Routing Rule Identifier using an IP-CAN Session Modification procedure (i.e. the Allowed Access Type can be added, changed or removed).
The PCRF request triggers the sending of Routing Rules creation (when the Allowed Access Type is added) or Routing Rules modification (when the Allowed Access Type is changed) to the UE which may be rejected by the UE due to local radio conditions. In that case the PCRF gets notified which PCC rules cannot be modified. This notification from the PCEF contains an indication of the cause of the rejection received from the UE.
The PCRF request triggers the sending of Routing Rules deletion to the UE when the Allowed Access Type is removed.
- UE-initiated IP flow mobility within a PDN connection (UE-initiated NBIFOM mode).
When the PCEF has received a request from the UE to create / modify / delete a Routing Rule, the PCEF initiates an IP-CAN Session Modification procedure and provides the Routing Rule received from the UE to the PCRF as an NBIFOM Routing Rule. The PCRF may reject an NBIFOM Routing Rule received from the UE due to subscription limitations. Otherwise the PCRF determines and updates the impacted PCC rule (as described in 6.12.2) and provides the updated PCC rule to the PCEF.
- UE requested mapping of IP flows to an access (Network-initiated NBIFOM mode).
This procedure is only used in Network-initiated NBIFOM mode when the UE wants to request the network to apply specific mappings of IP flows to an access.
When the PCEF has received a request from the UE to have the network create / modify / delete a Routing Rule, the PCEF initiates an IP-CAN Session Modification procedure and provides the information received from the UE to the PCRF as an NBIFOM Routing Rule. The PCRF may reject an NBIFOM Routing Rule received from the UE due to subscription limitations. Otherwise the PCRF determines and updates the impacted PCC rule (as described in clause 6.12.2) and provides the updated PCC rule to the PCEF. The updated PCC rule triggers the sending of a Routing Rules creation / modification / deletion to the UE (as described above for Network-initiated IP flow mobility).
- Indication that an access becomes unusable / usable again or indication of move-to-WLAN / move-from-WLAN (Network-initiated NBIFOM mode).
The PCEF initiates an IP-CAN Session Modification procedure to notify the PCRF about the change of usability of an access to the PCRF. For every PCC rule that is currently bound to this access, the PCRF shall either change the Allowed Access Type and provide the updated PCC rule to the PCEF or remove this PCC rule. This triggers the sending of Routing Rules modification to the UE. If the PCRF receives an indication that an access become usable again, The PCRF may update the PCC rules, e.g. by changing the Allowed Access Type and provide the updated PCC rules to the PCEF. This triggers the sending of Routing Rules modification to the UE.
- Reporting Access Network Information to the AF.
The PCRF reports to the AF only Access Network Information associated with one access even though different media of the AF session are carried by different accesses.
If the PCRF has received a request for Access Network Information from the AF and PCC rules related with the AF request are bound to multiple accesses, the PCRF selects one PCC rule to be associated with Access Network Information reporting from the PCEF. The selected PCC rule should correspond to the 3GPP access: Using the 3GPP access reduces the risk of getting non-trustable location information from the S2b access of the IP-CAN session.
- UE resource request for a multi-access IP-CAN session.
When the UE wants to request the network to allocate resources for one or more IP flows in the non-default NBIFOM access, the UE shall provide a corresponding Routing Rule in the same request in the UE-initiated mode. Without such Routing Rule, the network shall reject the UE resource request.
NOTE 4: UE resource requests in the default NBIFOM access do not require a Routing Rule as the generated PCC rule will be bound to dedicated bearer in this access.
- PCRF initiated IP-CAN session modification.
When network-initiated NBIFOM mode applies and the PCRF modifies the service data flow filter or precedence in a PCC rule for which a corresponding Routing Rule exists, the PCEF shall also modify this Routing Rule at the UE accordingly.
When network-initiated NBIFOM mode applies and the PCRF removes a PCC rule for which a corresponding Routing Rule exists, the PCEF shall also remove the corresponding Routing Rule at the UE.
When UE-initiated NBIFOM mode applies and if a new PCC rule is created due to the request from the network (e.g. request from the AF or application detection information from the PCEF/TDF), the PCRF shall determine that the new PCC rule is bound to the default access. UE may initiate IP flow mobility request to bind the IP flow to another access later. |
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 addition to the application identifier and the service priority. For MCPTT, the service priority and the priority sharing indicator are defined in TS 23.179 [46]. The priority sharing indicator is used to indicate what media flows are allowed to share priority.
The PCRF makes authorization and policy decisions for the affected AF sessions individually and generates a PCC/QoS rule for every media flow as specified in clause 6.1.1.3. The application identifier and the service priority are used to calculate the ARP priority. The AF may also provide suggested pre-emption capability and vulnerability values per media flow to the PCRF. The ARP pre-emption capability and the ARP pre-emption vulnerability are set according to operator policies and regulatory requirements, also taking into consideration the application identifier and suggested values, when provided by the AF. The priority sharing indicator is stored for later use.
For PCC/QoS rules with the same QCI assigned and having an associated priority sharing indicator, the PCRF shall try to make authorization and policy decisions taking the priority sharing indicator into account and modify the ARP of these PCC/QoS rules as follows, (the original ARP values are stored for later use):
- The modified ARP priority is set to the highest of the original priority among all the PCC/QoS rules that include the priority sharing indicator;
- The modified ARP pre-emption capability is set if any of the original PCC/QoS rules have the ARP pre-emption capability set;
- The modified ARP pre-emption vulnerability is set if all the original PCC/QoS rules have the ARP pre-emption vulnerability set.
NOTE 1: Having the same setting for the ARP parameter in the PCC/QoS rules with the priority sharing indicator set enables the usage of the same bearer. Furthermore, a combined modification of the ARP parameter in the PCC/QoS rules ensures that a bearer modification is triggered when a media flow with higher service priority starts.
If the PCRF receives an indication that a PCC/QoS rule provisioning or modification failed (due to resource reservation failure) then, the PCRF may apply pre-emption and remove active PCC/QoS rules from the PCEF and then retry the PCC/QoS rule provisioning or modification procedure. If the PCRF does not apply pre-emption, the AF is notified using existing procedures (as defined in clause 6.1.5) that the resource reservation for the new media flow failed.
The AF may optionally provide pre-emption control information, including pre-emption capability and vulnerability values, in addition to the priority sharing indicator to the PCRF. If so, the PCRF shall apply pre-emption and remove active PCC/QoS rules according to this information when receiving an indication that a PCC/QoS rule provisioning or modification failed. The pre-emption control information indicates:
- whether media flows sharing priority are candidates to being pre-empted taking into account pre-emption capability and vulnerability values;
- how to perform pre-emption among multiple potential media flow candidates of same priority: most recently added media flow, least recently added media flow, media flow with highest requested bandwidth in the AF request. |
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 PCEF/TDF or dynamic PCC/ADC Rules in the PCRF that include at least an application identifier for service data flow or application detection, charging control information, i.e. charging key and optionally the Sponsor identifier or the ASP identifier or both. Depending on the service level agreements between the operator and the Application Server Provider, it may be possible for the ASP to provide individual PFDs or the full set of PFDs for each application identifier maintained by the ASP to the PCEF/TDF via the SCEF and the PFDF. The PFDs become part of the application detection filters in the PCEF/TDF and therefore are used as part of the logic to detect traffic generated by an application. The ASP may remove or modify some or all of the PFDs which have been provisioned previously for one or more application identifiers. When a removed/modified PFD was used to detect application traffic related to an application identifier in a PCC/ADC Rule of an IP-CAN/TDF session and the PCEF/TDF has reported the application start as described in clause 4.5 to the PCRF for the application instance corresponding to this PFD, the PCEF/TDF shall report the application stop to the PCRF for the corresponding application instance identifier if the removed/modified PFD in PCEF/TDF results in that the stop of the application instance is not being able to be detected.
NOTE 1: The management of Packet Flow Descriptions is optional and is only used if the PFDF is deployed and the PCEF or the TDF supports this feature.
Each PFD may be identified by a PFD id. A PFD id is unique in the scope of a particular application identifier. There may be different PFD types associated to an application identifier, see TS 23.682 [42] for the definition of PFD.
The PFDs may be retrieved by PCEF/TDF from PFDF in "pull" mode or may be provisioned from PFDF to the PCEF/TDF in "push" mode.
When the "push" mode is used, the PFDF distributes PFDs for each application identifier to those PCEFs/TDFs that enable access to those applications. The PFDF may be configured with the list of PCEFs/TDFs where PFDs should be distributed. There are three methods to provision PFDs from the PFDF to the PCEF/TDF, as described in clause 7.12.2:
a) Push of whole PFDF state according to operator configuration in PFDF (e.g. provision per day according to operator configuration);
b) Selective push of an ASP change in the PFD set (i.e. ASP changes the PFD set while operator configuration defines when to push);
c) Selective push of an ASP change in the PFD set according to ASP request (i.e. ASP indicates to push changes in a PFD set within the time interval indicated by the Allowed Delay as described in TS 23.682 [42]).
NOTE 2: In all cases listed above, how to protect the PCEF/TDF from overload during the procedure to provision PFDs is up to Stage 3.
The SCEF may be configured with a minimum allowed delay based on SLA to authorize the allowed delay provided by the ASP, as defined in TS 23.682 [42].
When the "pull" mode is used, at the time a PCC/ADC Rule with an application identifier for which PFDs provisioned by the PFDF are not available is activated or provisioned, the PCEF/TDF requests all PFDs for that application identifier from the PFDF. The PFDs retrieved for an application identifier from the PFDF are cached in the PCEF/TDF with an associated caching timer to control how long the PFDs are valid. When the caching timer elapses, if there are still active PCC/ADC rules that refer to the corresponding application identifier, the PCEF/TDF reloads the PFD(s) from the PFDF. When the PCEF/TDF removes the last PCC/ADC rule that refers to the corresponding application identifier, or when the caching timer expires and no PCC/ADC rule refers to the application identifier, the PCEF/TDF may remove the PFD(s) related with the application identifier.
NOTE 3: It is assumed that all PCEF(s)/TDF(s) and PFDF(s) in an operator network are configured with the same default caching time value to be applied for all application identifiers.
Within one PLMN, "push" mode only, "pull" mode only, or a combination of "pull" and "push" mode may be supported if the feature is supported.
When the "pull" mode is used, the PFDF may provide to the PCEF/TDF a caching time value per application identifier. The PCEF/TDF receives the caching time value together with the PFD(s) from the PFDF over Gw/Gwn and applies this value for the application identifier instead of the configured default caching time value. In case no caching time value is received from PFDF, the PCEF/TDF uses the configured default caching time value.
NOTE 4: The configuration of a caching time value per application identifier PFDF is based on the SLA between the operator and the ASP.
When only "pull" mode is supported in one PLMN, if the Allowed Delay is shorter than the caching time value stored for this application identifier, or shorter than the default caching time if no application-specific caching time is stored, the PFDF sends a response to SCEF with an indication that the Allowed Delay cannot be met. The PFDF may still store the PFD(s) and if so, indicate this to the SCEF. The PFDF shall also include the caching time value in the response to the SCEF. The SCEF shall forward the indication that the PFDF stored the PFD(s) (if available) and the caching time value to the ASP when informing that the Allowed Delay could not be met.
If the PFDs are managed by local O&M procedures, PFD retrieval is not used; otherwise, the PFDs retrieved from PFDF overrides any PFDs pre-configured in the PCEF/TDF. If all PFDs retrieved from the PFDF are removed for an application identifier, the pre-configured PFDs shall be applied again for the application identifier. The PCEF/TDF may differentiate the need for PFD retrieval based on operator configuration in the PCEF/TDF.
The AF requests including an application identifier may trigger the activation or provisioning of a PCC/ADC Rule in the PCEF/TDF by the PCRF based on operator policies. |
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 the Serving GW but get dropped in the PDN GW. If this happens, it's not possible to verify accounting information collected at the Serving GW for inter-operator charging. However, the subscriber may not be charged for those packets.
The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 22.011 [49], that are the only allowed services in downlink direction when the 3GPP PS Data Off feature has been activated by the user.
When PCRF is deployed, it shall be configured with the list of 3GPP PS Data Off Exempt Services and the event trigger of 3GPP PS Data Off status change is used to inform the PCRF about every change of the 3GPP PS Data Off status.
NOTE 2: The PCRF can be configured with a list of 3GPP PS Data Off Exempt Services per APN. The list of 3GPP PS Data Off Exempt Services for an APN can also be empty, or can allow for any service within that APN, according to operator policy.
NOTE 3: The PCRF can be configured with up to two lists of 3GPP PS Data Off Exempt Services for UEs in HPLMN and for UEs camping in any VPLMNs using mechanism as specified in clause 6.2.1.1.
NOTE 4: For the PDN connection used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS domain as specified TS 23.228 [39]. Policies configured in the PCRF need to ensure that IMS services are allowed when the 3GPP Data Off status of the UE is set to "activated", e.g. by treating any service within a well-known IMS APN as 3GPP PS Data Off Exempt Services.
When the PCRF is informed about the activation of 3GPP PS Data Off, it shall update the PCC rules in such a way that only packets for services belonging to the list of 3GPP PS Data Off Exempt Services are forwarded while all other packets are discarded.
NOTE 5: In order for the PCEF to prevent the services that do not belong to the list of 3GPP PS Data Off Exempted Services, if the services are controlled by dynamic PCC rules, the PCRF could modify the PCC rules by setting the gate status to "closed" for the downlink and optionally uplink directions in all active dynamic PCC rules or remove those dynamic PCC rules. If the services are controlled by predefined PCC rules, the PCRF can deactivate those predefined PCC rules. PCC rule with wild-carded service data flow filters can be among the PCC rules that are modified, removed or deactivated in that manner. In this case, it can be necessary that the PCRF at the same time installs or activates PCC rules for data-off exempt services.
NOTE 6: For example, four PCC rules (A, B, C, D) are active for a PDN connection with PCC rule A representing a 3GPP PS Data Off Exempt Service. When 3GPP PS Data Off is activated, the PCRF could either modify PCC rules B, C and D if they are dynamic PCC rules by closing the gate in downlink and optionally in uplink direction or remove/deactivate PCC rules B, C and D if they are predefined PCC rules. PCC rule A does not need to be changed as it represents 3GPP PS Data Off Exempt Service. Assuming that PCC rule B contained wild-carded service data flow filters which has enabled some 3GPP PS Data Off Exempt Service is removed or deactivated, an additional PCC rule E can be installed or activated as well to enable the downlink traffic for that 3GPP PS Data Off Exempt Service.
NOTE 7: The network configuration can ensure that at least one PCC Rule is bound to the default bearer when Data Off is activated in order to avoid deletion of an existing PDN connection or in order not to fail a PDN connection establishment.
When the PCRF receives service information from the AF, in addition to what is specified in clause 6.2.1.0, PCRF shall check if the requested service information belongs to the 3GPP PS Data Off Exempt Services. If the requested service belongs to 3GPP PS Data Off Exempt Services, PCRF shall continue as specified in clause 6.2.1.0. If the requested service doesn't belong to the 3GPP PS Data Off Exempt Services, PCRF shall reject the service request.
When the PCRF is informed about the deactivation of 3GPP PS Data Off, it shall perform policy control decision as specified in clause 6.2.1.0 and perform PCC rule operations as specified in clause 6.3.2 2 to make sure that the services are allowed according to user's subscription and operator policy (irrespective of whether they belong to the list of 3GPP PS Data Off Exempt Services).
When PCRF is not deployed, predefined PCC rules, as example, can be configured in the PCEF to ensure the following:
- when the PCEF is informed about activation of 3GPP PS Data Off, only packets for services belonging to the list of 3GPP PS Data Off Exempt Services are forwarded while all other packets are discarded. The list of 3GPP PS Data Off Exempt Services for UEs camping in HPLMN and the list of 3GPP PS Data Off Exempt Services for UEs camping in VPLMN can be different and
- When PCEF is informed about deactivation of 3GPP PS Data Off, downlink packets are forwarded according to the operator policy for the subscriber.
NOTE 8: For example, the PCEF can be configured with three sets of predefined PCC rules: one set for UEs with 3GPP PS Data Off status "inactive", the second set for UE camping in the HPLMN with 3GPP PS Data Off status "active" and the third set for UEs camping in the VPLMN with 3GPP PS Data Off status "active". The set of predefined PCC rules for UE 3GPP PS Data Off status "active" can be equivalent to the set of predefined PCC rules for UE 3GPP PS Data Off status "inactive" with the following two differences: All services belonging to the list of 3GPP PS Data Off Exempt Services can be represented by PCC rule(s) which allows the traffic to pass while in all other PCC rules (not belonging to the list of 3GPP PS Data Off Exempt Services) the gate status can be "closed" for the downlink direction. When the PCEF is informed about the change of UE 3GPP PS Data Off status, it can replace the currently active set of predefined PCC rules with the other set of predefined PCC rules.
When the UE 3GPP PS Data Off status is "active" and a handover from one access-system to another occurs, the PCRF performs the above operations so that the downlink traffic for services not belonging to the list of 3GPP PS Data Off Exempt Services is only prevented via the 3GPP access.
When NBIFOM applies for the IP-CAN session, the PCRF shall not modify PCC rules associated to the IP-CAN type "Non 3GPP EPS". |
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 application detection, gating, QoS and application based charging (except credit management) towards the TDF and the PCEF enhanced with ADC.
The PCRF shall apply the security procedures, as required by the operator, before accepting service information from the AF.
The PCRF shall decide whether application traffic detection is applicable, as per operator policies, based on user profile configuration, received within subscription information.
The PCRF shall decide how certain service/application traffic shall be treated in the PCEF and in the TDF, if applicable and ensure that the PCEF user plane traffic mapping and treatment is in accordance with the user's subscription profile.
If Gxx applies, the PCRF shall provide QoS rules with identical service data flow templates as provided to the PCEF in the PCC rules. If the service data flow is tunnelled at the BBERF, the PCRF shall provide the BBERF with information received from the PCEF to enable the service data flow detection in the mobility tunnel at the BBERF. In case 2a, defined in clause 7.1, the PCRF may also provide to the BBERF the charging ID information received from the PCEF. If IP flow mobility as specified in TS 23.261 [23] applies, the PCRF shall, based on IP flow mobility routing rules received from the PCEF, provide the authorized QoS rules to the applicable BBERF as specified in clause 6.1.1.3.
The PCRF should for an IP‑CAN session derive, from IP‑CAN specific restrictions, operator policy and SPR data, the list of permitted QoS class identifiers and associated GBR and MBR limits for the IP‑CAN session.
The PCRF may check that the service information provided by the AF is consistent with both the operator defined policy rules and the related subscription information as received from the SPR during IP‑CAN session establishment before storing the service information. The service information shall be used to derive the QoS for the service. The PCRF may reject the request received from the AF when the service information is not consistent with either the related subscription information or the operator defined policy rules and as a result the PCRF shall indicate that this service information is not covered by the subscription information or by operator defined policy rules and may indicate, in the response to the AF, the service information that can be accepted by the PCRF (e.g. the acceptable bandwidth). In the absence of other policy control mechanisms outside the scope of PCC, it is recommended that the PCRF include this information in the response.
When receiving service information from the AF, the PCRF may temporarily reject the AF request (e.g. if the service information is not consistent with the operator defined policy rules for the congestion status of the user). To temporarily reject the AF request the PCRF shall indicate a re-try interval to the AF. When receiving a re-try interval from the PCRF the AF shall not send the same service information to the PCRF again (for the same IP‑CAN session) until the re-try interval has elapsed.
NOTE 1: How the PCRF derives the re-try interval is up to implementation.
In this Release, the PCRF supports only a single Rx reference point, i.e. there is one AF for each AF session.
The PCRF authorizes QoS resources. The PCRF uses the service information received from the AF (e.g. SDP information or other available application information) and/or the subscription information received from the SPR to calculate the proper QoS authorization (QoS class identifier, bitrates). The PCRF may also take into account the requested QoS received from the PCEF via Gx interface.
NOTE 2: The PCRF provides always the maximum values for the authorized QoS even if the requested QoS is lower than what can be authorized.
The Authorization of QoS resources shall be based on complete service information unless the PCRF is required to perform the authorization of QoS resources based on incomplete service information. The PCRF shall after receiving the complete service information, update the affected PCC rules accordingly.
The PCRF may use the subscription information as basis for the policy and charging control decisions. The subscription information may apply for both session based and non-session based services.
The PCRF determines whether a Gx session from the PCEF is to be linked with a Gateway Control Session from the BBERF by matching the IPv4 address and/or IPv6 network prefix and conditionally the UE Identity, PDN Connection ID and PDN ID towards open Gateway Control Sessions. When IP flow mobility as specified in TS 23.261 [23] applies, one Gx session may be linked with multiple Gateway Control Sessions.
If the BBERF does not provide any PDN ID at the Gateway Control Session Establishment, then the PCRF maintains Gateway Control Session to Gx session linking to the Gx sessions where the assigned CoA and UE Identity (if available over Gxx) are equal. The PCRF and BBERF shall be capable of separating information for each IP‑CAN session within the common Gateway Control Session.
If the BBERF provides a PDN ID at the Gateway Control Session Establishment, then the PCRF maintains Gateway Control Session to Gx session linking where the UE identity and PDN ID are equal. If the BBERF provides a PDN ID at Gateway Control Session establishment, it may also indicate in the Gateway Control Session establishment that the PCRF shall not attempt linking the new Gateway Control Session with an existing Gx session immediately. If the PCRF receives such an indication, it keeps the new Gateway Control Session pending and defers linking until an IP-CAN session establishment or an IP-CAN session modification with matching UE Identity, PDN ID and IP-CAN type arrives via Gx.
If the BBERF provides a PDN ID and a PDN Connection ID at the Gateway Control Session establishment, then the PCRF maintains Gateway Control Session to Gx session linking where the UE identity, PDN Connection ID and PDN ID are equal.
When a BBERF establishes multiple Gateway Control Sessions for the same PDN ID and the IP‑CAN type changes, the PCRF assumes that this constitutes inter-system BBERF relocations of existing Gateway Control Sessions. The BBERF may supply UE IPv4 address and/or IPv6 network prefix (if known) that can be used for linking the new Gateway Control Session to the existing Gx session. If the UE IPv4 address and/or IPv6 network prefix is/are not provided in the new Gateway Control Session establishment, the PCRF shall defer the linking with existing Gx session until receiving an IP-CAN Session modification with matching UE Identity, IP‑CAN type, PDN Connection ID and PDN ID.
The PCRF determines which case applies as described on clause 7.1.
If an AF requests the PCRF to report on the signalling path status, for the AF session, the PCRF shall, upon indication of loss of resources from the PCEF, for PCC rules corresponding to the signalling traffic notify the AF on changes to the signalling path status. The PCRF needs to have the knowledge of which PCC rules identify signalling traffic.
Negotiation of IP‑CAN bearer establishment mode takes place via Gx for 3GPP IP‑CANs. For non-3GPP IP‑CANs specified in TS 23.402 [18] negotiation of bearer establishment mode takes place via Gx when GTP is used and via Gxx for the rest of the cases. For other accesses supporting multiple IP‑CAN bearer establishment modes, if Gxx applies, the negotiation takes place via Gxx, otherwise via Gx. To support the different IP‑CAN bearer establishment modes (UE-only or UE/NW) the PCRF shall:
- shall set the IP‑CAN bearer establishment mode for the IP‑CAN session based on operator configuration, network and UE capabilities;
- shall, if the bearer establishment mode is UE/NW, decide what mode (UE or NW) shall apply for a PCC rule and resolve race conditions between for requests between UE-initiated and NW-initiated requests;
NOTE 3: For an operator-controlled service, the UE and the PCRF may be provisioned with information indicating which mode is to be used.
- may reject a UE request that is already served by a NW-initiated procedure in progress. When rejecting a UE-initiated request by sending a reject indication, the PCRF shall use an appropriate cause value which shall be delivered to the UE.
NOTE 4: This situation may e.g. occur if the PCRF has already triggered a NW-initiated procedure that corresponds to the UE request.
- guarantee the precedence of dynamic PCC rules with SDF template containing SDF filter(s) (and optionally also for SDF templates consisting of an application identifier) for network controlled services in the service data flow detection process at the PCEF by setting the PCC rule precedence information to appropriate values.
If an AF requests the PCRF to report on the change of type of IP‑CAN, the PCRF shall provide to the AF the information about the IP‑CAN type the user is currently using and upon indication of change of IP‑CAN type, notify the AF on changes of the type of IP‑CAN. In the case of 3GPP IP‑CAN, the information of the Radio Access Technology Type (e.g. UTRAN) shall be also reported to the AF. If IP flow mobility as specified in TS 23.161 [43] or in TS 23.261 [23] applies, the PCRF shall provide to the AF the new IP-CAN type information together with the affected service information. When IP flow mobility is allowed within an IP‑CAN session, the PCRF shall only report to an AF the IP‑CAN type change when the IP flow mobility applies to the service information provided by this AF.
NOTE 5: The PCRF can also use the dynamic or pre-defined PCC Rules related to the IMS signalling to request Access Network Information reporting. This can be used to support e.g. regulatory requirements for SMS over IP, where the IMS network (i.e. P‑CSCF) needs to retrieve the user location and/or UE Time Zone information. Note that due to regulatory requirements, the Access Network Information can be requested for SMS over IP, impacting a large number of PDN Connections, that can lead to significant increase in signalling load when the Access Network Information is requested from the Access Node (e.g. MME).
If an AF requests the PCRF to report Access Network Information, the PCRF shall set the Access Network Information report parameters in the corresponding PCC rule(s) or QoS rule(s) and provision them together with the corresponding event trigger to the PCEF or BBERF as per procedure in clause 7.4.2. For those PCC rule(s) or QoS rule(s) based on preliminary service information the PCRF may assign the QCI and ARP of the default bearer to avoid signalling to the UE. In addition the SDF filter(s) shall not be marked as to be used for signalling to the UE as traffic mapping information.
If an AF requests the PCRF to report Access Network Information, The PCRF shall also set the corresponding event trigger to the PCEF or BBERF as per procedure in clause 7.4.2. The PCRF shall, upon receiving the subsequent Access Network Information report corresponding to the AF session from the PCEF or BBERF, forward the Access Network Information as requested by the AF.
If an AF requests the PCRF to report the PLMN identifier where the UE is currently located, then the PCRF shall provide the PLMN identifier to the AF if available.Otherwise, the PCRF shall provision both the corresponding PCC rules and QoS Rules if applicable and the event trigger to report PLMN change to the PCEF. The PCRF shall, upon receiving of the PLMN identifier from the PCEF forward this information to the AF as defined in the procedures in clause 6.1.4.
If an AF requests the PCRF to report Access Network Charging Correlation Information, the PCRF shall provide to the AF the Access Network Charging Correlation Information, which will identify the usage reports that include measurement for the flows, once the Access Network Charging Correlation Information is known at the PCRF. If not known in advance, the PCRF subscribes for the Access Network Charging Correlation Information event for the applicable PCC rule(s), unless a single charging identifier per IP-CAN session is used as described below.
The PCEF provides at IP‑CAN session establishment both a charging identifier and an optional indication that the charging identifier is the only one for that IP‑CAN session, as defined in clause 5.1.3 of TS 32.251 [9]. In absence of the indication there is a separate charging identifier for each IP‑CAN bearer to identify usage reports that include measurements for flows served by each individual bearer. When the PCEF indicates that a single charging identifier is used for the IP‑CAN session, the PCRF uses the charging identifier received at IP‑CAN session establishment to provide Access Charging Correlation information to the AF for all flows, instead of subscribing to the Access Network Charging Correlation Information event trigger for the applicable PCC Rule(s) as described above.
If Gxx applies and the PCEF provided information about required event triggers, the PCRF shall provide these event triggers to the BBERF and notify the PCEF of the outcome of the provisioning procedure by using the PCRF initiated IP‑CAN Session Modification procedure, as defined in clause 7.4.2. The PCRF shall include the parameter values received in the response from the BBERF in the notification to the PCEF. When multiple BBERFs exist (e.g. in IP flow mobility case), the PCEF may subscribe to different or common set of event triggers at different BBERFs; when the PCRF receives event notification from any BBERF, the PCRF shall include both the parameters values received from the BBERF and also the information for identifying the BBERF in the notification to the PCEF.
If Sd applies and the TDF provided information about required event triggers, the PCRF shall provide these event triggers to the PCEF or BBERF, if Gxx applies and notify the TDF of the outcome of the provisioning procedure within the PCEF initiated IP‑CAN Session Modification procedure, as defined in clause 7.4.1. The PCRF shall include the parameter values, received in the response from the PCEF/BBERF, in the notification to the TDF. The relevant Event Triggers are: PLMN change, Location change, Change in type of IP‑CAN, RAT type change, SGSN change, Serving GW change, User CSG Information change in CSG cell, User CSG Information change in subscribed hybrid cell, User CSG Information change in un-subscribed hybrid cell, Change of UE presence in Presence Reporting Area.
NOTE 6: For IP flow mobility feature enabled, the TDF doesn't have accurate information about the location and the type of RAT the user is attached to.
When the PCRF gets an event report from the BBERF that is required by the PCEF, the PCRF shall forward this event report to the PCEF.
When the PCRF gets an Event Report from the PCEF/BBERF that is required by the TDF, the PCRF shall forward this Event Report to the TDF.
The PCRF may support usage monitoring control. Usage is defined as either volume or time of user plane traffic.
The PCRF may receive information about total allowed usage per PDN and UE from the SPR, i.e. the overall amount of allowed resources (based either on traffic volume and/or traffic time) that are to be monitored for the PDN connections of a user. In addition information about total allowed usage for Monitoring key(s) per PDN and UE may also be received from the SPR. For the purpose of usage monitoring per access type , the PCRF receives an individual Monitoring key per access type from SPR.
For the purpose of usage monitoring control the PCRF shall request the Usage report trigger and provide the necessary usage threshold(s), either volume threshold, time threshold, or both volume threshold and time threshold, upon which the requested node (PCEF or TDF) shall report to the PCRF. The PCRF shall decide if and when to activate usage monitoring to the PCEF and TDF.
The PCRF may provide a Monitoring time to the PCEF/TDF for the Monitoring keys(s) and optionally specify a subsequent threshold value for the usage after the Monitoring time.
If the PCEF reports usage before the Monitoring time is reached, the Monitoring time is not retained by the PCEF. Therefore the PCRF may again provide a Monitoring time and optionally the subsequent threshold value for the usage after the Monitoring time in the response.
It shall be possible for the PCRF to request a usage report from the requested node (PCEF or TDF).
NOTE 7: The PCRF ensures that the number of requests/following policy decisions provided over Gx/Sd reference point do not cause excessive signalling load by e.g. assigning the same time for the report only for a preconfigured number of IP-CAN/TDF sessions.
Once the PCRF receives a usage report from the requested node (PCEF or TDF) the PCRF shall deduct the value of the usage report from the totally allowed usage for that PDN and UE (in case usage per IP-CAN session is reported). If usage is reported from the TDF or the PCEF, the PCRF shall deduct the value of the usage report from the totally allowed usage for individual Monitoring key(s) for that PDN and UE (in case of usage for one or several Monitoring keys is reported).
NOTE 8: The PCRF maintains usage thresholds for each Monitoring key and IP‑CAN session that is active for a certain PDN and UE. Updating the total allowanced usage after the PCEF reporting, minimizes the risk of exceeding the usage allowance.
If the PCEF or TDF reports usage for a certain Monitoring key and if monitoring shall continue for that Monitoring key then the PCRF shall provide new threshold value(s) in the response to the PCEF or TDF respectively. If Monitoring time and subsequent threshold value are used then the PCRF provides them to the PCEF or TDF as well.
The PCRF may provide a new volume threshold and/or a new time threshold to the PCEF or TDF, the new threshold values overrides the existing threshold values in the PCEF or TDF.
If monitoring shall no longer continue for that Monitoring key, then the PCRF shall not provide a new threshold in the response to the PCEF / TDF.
NOTE 9: If the PCRF decides to deactivate all PCC rules or ADC rules associated with a certain Monitoring key, then the conditions defined in clause 6.6.2 for continued Monitoring will no longer be fulfilled for that Monitoring key.
If all IP-CAN session of a user to the same APN is terminated, the PCRF shall store the remaining allowed usage, i.e. the information about the remaining overall amount of resources, in the SPR.
The PCRF may authorise an application service provider to request specific PCC decisions (e.g. authorisation to request sponsored IP flows, authorisation to request QoS resources). For sponsored data connectivity (see Annex N), the PCRF may receive a usage threshold from the AF.
If the AF specifies a usage threshold, the PCRF shall use the Sponsor Identity to construct a Monitoring key for monitoring the volume, time, or both volume and time of user plane traffic and invoke usage monitoring on the PCEF/TDF. The PCRF shall notify the AF when the PCEF/TDF reports that a usage threshold for the Monitoring key is reached provided that the AF requests to be notified for this event. If the usage threshold is reached, the AF may terminate the AF session or provide a new usage threshold to the PCRF. Alternatively, the AF may allow the session to continue without specifying a usage threshold. If the AF decides to allow the session to continue without specifying a usage threshold, then monitoring in the PCEF/TDF shall be discontinued for that monitoring key by the PCRF, unless there are other reasons for continuing the monitoring.
If the AF revokes the service information and the AF has notified previously a usage threshold to the PCRF, the PCRF shall report the usage up to the time of the revocation of service authorization.
If the IP-CAN session terminates and the AF has specified a usage threshold then the PCRF shall notify the AF of the accumulated usage (i.e. either volume, or time, or both volume and time) of user plane traffic since the last usage report.
The PCRF performs authorizations based on sponsored data connectivity profiles stored in the SPR. If the AF is in the operator's network and is based on the OSA/Parlay-X GW (TS 23.198 [24]), the PCRF is not required to verify that a trust relationship exists between the operator and the sponsors.
If the H-PCRF detects that the UE is accessing the sponsored data connectivity in the roaming scenario with home routed access, it may allow the sponsored data connectivity in the service authorization request, reject the service authorization request, or initiate the AF session termination based on home operator policy.
NOTE 10: Sponsored data connectivity is not supported in the roaming with visited access scenario in this Release.
If the AF request includes an AF application identifier then, based on the operator policies the PCRF may trigger the activation of a predefined PCC/ADC Rule or provide a dynamic PCC/ADC rule with an appropriate application identifier in the PCEF/TDF.
For the solicited application reporting, it is PCRF's responsibility to coordinate the PCC rules and QoS rules, if applicable, with ADC rules in order to ensure consistent service delivery.
The PCRF uses the information relating to subscriber spending available in the OCS as input for policy decisions related to e.g. QoS control, gating or charging conditions.
The PCRF uses the RUCI received from the RCAF as input for policy decisions.
If the AF contacts the PCRF via the SCEF (and the Nt interface) to request a time window and related conditions for future background data transfer, the PCRF shall determine possible transfer policies (as described in clause 6.1.16) and send them to the AF together with a reference ID. If the AF received more than one transfer policy, the AF selects one of them and informs the PCRF about the selected transfer policy. The PCRF shall store the selected transfer policy in the SPR together with the reference ID and the network area information. Whenever the PCRF receives a reference ID from the AF during a subsequent transfer of AF session information (via the Rx interface), the PCRF shall retrieve the corresponding transfer policy from the SPR and apply it as one of the inputs for policy decisions for this IP-CAN session.
The PCRF uses one or more pieces of information defined in the clause 6.2.1.1 as input for the selection of traffic steering policies used to control the steering of the subscriber's traffic to appropriate (S)Gi-LAN service functions.
NOTE 11: In order to allow the PCRF to select and provision an application based traffic steering policy, the reporting of detected applications to the PCRF or any other information such as the RAT type, the RUCI etc. defined in clause 6.2.1.1 can be used.
At reception of the IMS service information from the P-CSCF, if configured through policy, the PCRF determines the Maximum Packet Loss Rate for UL and DL based on the IMS service information and taking into account information defined in TS 26.114 [45] and sends it to PCEF along with the PCC rule for the voice media.
NOTE 12: Based on local configuration, the PCRF sets the Maximum Packet Loss Rate (UL, DL) corresponding to either the most robust codec configuration (e.g. codec, mode, redundancy) or the least robust codec configuration of the negotiated set in each direction. |
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 information below describes examples of the information provided. Depending on the particular scenario all the information may not be available or is already provided to the PCRF.
The PCEF and/or BBERF may provide the following information:
- Subscriber Identifier;
- The IMEI(SV) of the UE;
- IPv4 address of the UE;
- IPv6 network prefix assigned to the UE;
- NBIFOM Routing Rules (when NBIFOM as specified in TS 23.161 [43] applies);
- IP flow routing information (when IP flow mobility as specified in TS 23.261 [23] applies);
NOTE 1: IP flow routing information and NBIFOM Routing Rules are provided only by the PCEF.
- Change of usability of an Access (when NBIFOM as specified in TS 23.161 [43] applies);
- IP‑CAN bearer attributes;
NOTE 2: If IP flow mobility as specified in TS 23.161 [43] or in TS 23.261 [23] applies, an IP-CAN session may be active over multiple accesses and thus some IP‑CAN bearer attributes may have a different value depending on the access type;
- Request type (initial, modification, etc.);
- Type of IP‑CAN (e.g. GPRS, etc.);
NOTE 3: The Type of IP‑CAN parameter should allow extension to include new types of accesses.
- Location of the subscriber;
NOTE 4: See clause 6.1.4 for the description of this location information.
NOTE 5: Depending on the type of IP‑CAN, the limited update rate for the location information at the PCEF may lead to a UE moving outside the area indicated in the detailed location information without notifying the PCEF.
- A PDN ID;
- A PLMN identifier;
- IP‑CAN bearer establishment mode;
- 3GPP PS Data Off status.
The PCEF enhanced with ADC or the TDF may provide the following information:
- Detected application identifier;
- Allocated application instance identifier;
- Detected service data flow descriptions.
The SPR may provide the following information for a subscriber, connecting to a specific PDN:
- Subscriber's allowed services, i.e. list of Service IDs;
- For each allowed service, a pre-emption priority;
- Information on subscriber's allowed QoS, including:
- the Subscribed Guaranteed Bandwidth QoS;
- a list of QoS class identifiers together with the MBR limit and, for real-time QoS class identifiers, GBR limit.
- Subscriber's charging related information;
- Spending limits profile containing an indication that policy decisions depend on policy counters available at the OCS that has a spending limit associated with it and optionally the list of relevant policy counters.
- Subscriber category;
- Subscriber's usage monitoring related information;
- Subscriber's profile configuration;
- Sponsored data connectivity profiles;
- MPS EPS Priority, MPS Priority Level (See TS 23.401 [17] for more detail on MPS Subscription);
- IMS Signalling Priority.
NOTE 6: The MPS Priority Level represents user priority.
NOTE 7: The MPS Priority Level is one among other input data such as operator policy for the PCRF to set the ARP value. The MPS EPS Priority and MPS Priority Level are consistent with the corresponding parameters defined in the HSS.
The SPR may provide the following policy information related to an ASP (see clause 6.1.16):
- The ASP identifier;
- A transfer policy together with a reference ID, the volume of data to be transferred per UE, the expected amount of UEs and the network area information.
The AF, if involved, may provide the following application session related information, e.g. based on SIP and SDP:
- Subscriber Identifier;
- IP address of the UE;
- Media Type;
- Media Format, e.g. media format sub-field of the media announcement and all other parameter information (a= lines) associated with the media format;
- Bandwidth;
- Sponsored data connectivity information (see clause 5.2.1);
- Flow description, e.g. source and destination IP address and port numbers and the protocol;
- AF application identifier;
- AF Communication Service Identifier (e.g. IMS Communication Service Identifier), UE provided via AF;
- AF Application Event Identifier;
- AF Record Information;
- Flow status (for gating decision);
- Priority indicator, which may be used by the PCRF to guarantee service for an application session of a higher relative priority;
NOTE 8: The AF Priority information represents session/application priority and is separate from the MPS EPS Priority indicator.
- Emergency indicator;
- Indicator for Restricted Local Operator Services;
- Application service provider.
NOTE 9: The application service provider may be identified in numerous forms e.g. the AF application identifier or the host realm at Diameter level.
The OCS, if involved, may provide the following information for a subscriber:
- Policy counter status for each relevant policy counter.
The RCAF, if involved, may provide the following information for a subscriber:
- Subscriber Identifier.
- Identifier of the eNB, E-UTRAN cell or Service Area serving the subscriber.
NOTE 10: Whether in case of E-UTRAN the eNB identifier or the ECGI are included in the RUCI is up to operator configuration in the RCAF.
NOTE 11: Depending on the RUCI reporting interval configured in the RCAF, a UE may move outside the area indicated without the RCAF immediately notifying the PCRF. The PCRF can avoid receiving information about the cell currently serving a UE from multiple sources (i.e. via the Np and the Gx interface) by deactivating reporting of the congested cell's identifier over Np. In case PCRF receives information about the cell currently serving a UE via Np and Gx, then the information received via Gx is expected to take precedence.
- APNs.
- Congestion level or an indication of the "no congestion" state.
In addition, the predefined information in the PCRF may contain additional rules based on charging policies in the network, whether the subscriber is in its home network or roaming, depending on the IP‑CAN bearer attributes.
The QoS Class Identifier (see clause 6.3.1) in the PCC rule is derived by the PCRF from AF or SPR interaction if available. The input can be SDP information or other available application information, in line with operator policy.
The Allocation/Retention Priority in the PCC Rule is derived by the PCRF from AF or SPR interaction if available, in line with operator policy. |
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 subscriber ID and, if available, the PDN identifier in the request. The PCRF should retain the subscription information that is relevant for PCC decisions until the IP‑CAN session termination and the gateway control session termination.
The PCRF may request notifications from the SPR on changes in the subscription information. Upon reception of a notification, the PCRF shall make the PCC decisions necessary to accommodate the change in the subscription and updates the PCEF and/or the BBERF and/or the TDF by providing the new PCC and/or QoS and/or ADC decisions if needed. The PCRF shall send a cancellation notification request to the SPR when the related subscription information has been deleted. |
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 if a request is for a roaming user.
A Gateway Control Session request received over the Gxx reference point may trigger a request over the S9 reference point from the V‑PCRF to the H‑PCRF.
If a Gateway Control Session establishment request is received that can not be bound to an existing Gx session then the associated IP‑CAN session is either home routed or it is visited access but the IP‑CAN session establishment request has not yet been received over Gx.
For this case the V-PCRF may determine based on PDN-Id carried in the GW control session and roaming agreements if the request shall be proxied to the H‑PCRF over S9 or not. The V-PCRF may choose not to proxy the Gateway Control Session Establishment only if the PDN-Id indicates the request is for visited access.
The Gateway Control Session Establishment request should only be proxied to the H‑PCRF over S9 in case the V‑PCRF is configured to do so e.g. based on roaming agreement.
NOTE: Proxying the Gateway Control Session Establishment makes the H‑PCRF aware of the Gateway Control Session and enables binding in case a subsequent IP‑CAN Session is established with home routed access or visited access.
If the V‑PCRF determines that a Gateway Control Session Establishment shall be proxied to the H‑PCRF over S9 then the reply from the H‑PCRF shall also be communicated back to the GW (BBERF) over Gxx.
In case the V‑PCRF determines that a Gateway Control Session Establishment request shall not be proxied, then the V‑PCRF shall respond to the request made by the GW (BBERF) without notifying the H‑PCRF.
If an IP‑CAN session establishment request is received for a roaming user over the Gx reference point, then the V‑PCRF shall conclude that the IP‑CAN session use visited access and act as described in clause 6.2.1.3.3.
NOTE 2: Through roaming agreement, the HPLMN operator may allow the VPLMN operator to operate the V‑PCRF without using the capabilities described in clause 6.2.1.3.3 (i.e. no S9 is used). In such case, the PCRF in the VPLMN has no access to subscriber policy information from the HPLMN, only static policies will apply based on roaming agreements. The VPCRF may also interact with the AF in the VPLMN in order to generate PCC Rules for services delivered via the VPLMN. V-PCRF uses locally configured policies according to the roaming agreement with the HPLMN operator as input for PCC Rule generation.
If a Gateway Control and QoS rules provision is received by the V‑PCRF over the S9 reference point for a Gateway Control session which is not associated, at the V-PCRF, with an existing Gx session, the V‑PCRF shall conclude that the IP‑CAN session associated with the Gateway Control session is home routed and act as described in clause 6.2.1.3.2. |
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 regarding QoS authorization requested by the home operator 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.
Within an IP‑CAN session, a different V-PCRF may be selected when a new Gateway Control Session is established. |
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 service.
- When Gxx interaction is terminated locally at the V-PCRF, perform Gx to Gateway Control Session linking.
‑ When Gxx interaction is terminated locally at the V-PCRF, extract QoS rules (defined in clause 6.5) from PCC rules (defined in clause 6.3) provided by the H‑PCRF over the S9 reference point. The V‑PCRF provides updated PCC rules to the PCEF and QoS rules to the BBERF, if appropriate.
‑ For the case of AF in the VPLMN:
‑ Proxy Rx authorizations over the S9 reference point to the H‑PCRF;
‑ Relay event subscriptions and notifications between the H‑PCRF and V‑AF
When Gx interactions are proxied between the PCEF and the H-PCRF, the V-PCRF proxies:
- Indication of IP‑CAN Session Establishment and Termination;
- Policy and Charging Rule Provisioning;
- Request Policy and Charging Rules.
If a Gateway Control Session is used and if during the IP‑CAN Session Establishment the Gateway Control Session Establishment procedure was proxied to the H‑PCRF (according to the logic in clause 6.2.1.3.1), then the V‑PCRF shall also proxy all other Gateway Control Session procedures to the H‑PCRF.
If the Gateway Control Session was not proxied to the H‑PCRF then the V‑PCRF shall handle all Gateway Control Session procedures locally and not proxy them to the H‑PCRF. This has the following implications:
‑ An IP‑CAN Session modification may trigger the V‑PCRF to update the Gateway Control Session if required in order to maintain the alignment of PCC and QoS Rules.
‑ An IP‑CAN Session termination procedure may trigger the V‑PCRF to terminate the Gateway Control Session if the Gateway Control Session was established for the purpose of a single IP‑CAN session. Otherwise a Gateway Control and QoS Rules Provision procedure may be initiated to remove the QoS Rules associated with the IP‑CAN session.
‑ On receiving a Gateway Control and QoS Rules Request message from the BBERF, the V-PCRF performs the procedure described in clause 7.7.3.2 for the event reporting for PCEF in visited network and locally terminated Gxx interaction.
NOTE 1: The V-PCRF has to set the event triggers at the PCEF in a way that the PCEF would trigger a PCEF initiated IP‑CAN Session Modification Procedure if an interaction with the H-PCRF is required.
When Rx components are proxied between an AF in the VPLMN and the H‑PCRF, the V‑PCRF shall proxy service session information between the AF and the H‑PCRF.
The V-PCRF shall support functionality to generate ADC rules from the PCC rules providing application detection and control as instructed by the H‑PCRF over S9. The V‑PCRF shall provide updated PCC Rules to the PCEF and generated ADC rules to the TDF, as appropriate in the VPLMN configuration.
NOTE 2: There may be situations where the TDF or PCEF enhanced with ADC is not able to detect the traffic requested by the H-PCRF. Prior agreements could be arranged to ensure that there is a common understanding of the meaning of application identifiers transferred between PLMNs.
The V‑PCRF shall install the event triggers in the PCEF, in the TDF and in the BBERF that were provided for the IP‑CAN session and install additional event triggers in the BBERF that are relevant only to the PCEF (i.e. such event triggers are typically set by the OCS) or the TDF. On receiving an Event report from the PCEF/BBERF, the V-PCRF forwards it to the TDF, if TDF has previously subscribed for it.
NOTE 3: Event reports over Gxx that are relevant only to the PCEF will not trigger a PCEF initiated IP‑CAN session modification procedure.
For UEs in a local breakout scenario, the RCAF may contact the V-PCRF with the RUCI information. Congestion information shall not be exposed via the S9 interface.
Within an IP‑CAN session the same V-PCRF remains for the whole lifetime of the IP‑CAN session. |
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 Gateway Control Session Establishment is indicated over S9, then one or more of the following cases applies:
1. One (or several) home routed IP‑CAN sessions are known to the H‑PCRF that can be bound to the Gateway Control session. For such IP‑CAN sessions, the H‑PCRF shall act as described in clause 6.2.1.4.2.
2. No IP‑CAN session is known to the H‑PCRF that can be bound to the Gateway Control session. This is the case when an IP‑CAN session establishment process has not yet been initiated over Gx or S9.
If an IP‑CAN Session Establishment is received over Gx then the H‑PCRF shall conclude that the IP‑CAN session is home routed and act as described in clause 6.2.1.4.2.
If an IP‑CAN Session Establishment is received over S9 then the H‑PCRF shall conclude that the IP‑CAN session use visited access and act as described in clause 6.2.1.4.3. |
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 received over the Gx reference point, then the H‑PCRF shall initiate a Gateway Control Session Termination procedure over S9 if the Gateway Control Session was established for the purpose of a single IP‑CAN session. Otherwise a Gateway Control and QoS Rules Provision procedure may be initiated over S9 to remove the QoS Rules in the BBERF associated with the IP‑CAN session. |
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 Termination messages;
- Policy and Charging Rule Provisioning messages;
- Request Policy and Charging Rules messages.
When the Gateway Control Session is proxied to the H-PCRF, 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:
- Indication of Gateway Control Session Establishment and Termination messages;
- QoS Rules Provisioning messages;
- Request QoS Rules messages.
The H-PCRF shall generate PCC rules for application traffic detection, notification and policy control when the TDF is located in the VPLMN.
The H‑PCRF should generate PCC rules for both of the cases when the AF is located in the VPLMN and when the AF is located in the HPLMN. The H‑PCRF provides the PCC rules to the V‑PCRF over the S9 reference point. |
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 PCRF handles the multiple BBFs as follows:
- The PCRF classifies the BBERF which reports the same IP‑CAN type as that reported by the PCEF as the primary BBERF and a BBERF that reports an IP‑CAN type different from that reported by the PCEF as non-primary BBERF. If there are more than one BBERFs that report the same IP‑CAN type as that reported by the PCEF, the BBERF that last created the GW Control Session with the PCRF is classified as the primary BBERF and other BBERF(s) are classified as non-primary BBERF(s).
NOTE 1: During handover where the BBF moves from a BBERF to the PCEF (e.g. handover from PMIP to GTP), when the PCEF reports a new IP-CAN type, the BBERF is classified as a non-primary BBERF. There is no primary BBERF but the active BBF is in the PCEF.
NOTE 2: During handover where the BBF moves from the PCEF to a BBERF (e.g. handover from GTP to PMIP), when the BBERF creates a Gateway Control Session, it is classified as a non-primary BBERF. This BBERF subsequently gets classified as the primary BBERF when the PCEF reports an IP‑CAN type which is the same as that reported by the BBERF.
- When a new (primary/non-primary) BBERF supporting NW/UE bearer establishment mode creates a GW Control session, the PCRF provides to the new BBERF QoS rules corresponding to SDFs. For a change of IP‑CAN type, the QoS parameters of some of the QoS rules may be changed or some QoS rules may not be provided to the new BBERF, e.g. depending of the capability of the target RAT. When a new (primary/non-primary) BBERF supporting only UE bearer establishment mode creates a GW Control session, the PCRF authorizes the setup of the default bearer and only pushes down QoS rules in response to specific requests from the BBERF.
NOTE 3: After completion of the handover procedure to the new BBERF, the UE can still initiate the access specific procedures to modify or release the resources that were originally allocated based on UE-initiated resource allocation. Such operations and the associated changes to QoS rules are handled following the normal UE-initiated resource management procedures.
NOTE 4: To facilitate the UE's determination of QoS resources in the target access allocated to pre-existing IP flows the access system is required to provide packet filters with the same content as that in the SDF template filters received over the Gx/Gxx interface (see clause 6.1.9).
- If the BBF is located in any of the BBERF, the PCRF keeps track of QoS rules activation by all the BBERFs. The PCRF updates PCC rules to the PCEF based on activation status of QoS rules in the primary BBERF.
- If the primary-BBERF reports failure to activate a QoS rule, the PCRF also removes the same QoS rule from the non-primary BBERFs, if any are already installed and the corresponding PCC rule from the PCEF. If a non-primary BBERF reports failure to install a QoS rule, the PCRF updates the status for that particular BBERF in its record but does not perform any further action.
- When path-switch occurs and the PCEF informs the PCRF of a new IP‑CAN type, if a BBERF is re-classified as a primary BBERF, the PCRF may update QoS rules in the BBERF corresponding to the PCC rules in the PCEF.
- For the case of UE initiated resource reservation through the non-primary BBERF: If a non-primary BBERF request results in a change of the QoS rules active in the primary-BBERF, e.g. creation of a new QoS rule or results in modification of an existing QoS rule, then the PCRF shall reject the request. |
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 more than one BBF associated with the same IP‑CAN session due to flow mobility, the PCRF handles the multiple BBFs as follows:
- The default route may be associated with one of the BBFs. The PCRF does not differentiate between primary and secondary BBF.
- If, based on routing information received from the PCEF, the PCRF determines that the bearer binding for a service data flow is located in a BBERF, the PCRF provides QoS rules for bearer binding to the appropriate BBERF/BBF. Each service data flow is associated with one BBF based on the routing information. If no explicit routing information for a service data flow is available from the PCEF, the PCRF provides PCC/QoS rules for the service data flow based on the default route.
- When the route of a service data flow changes from one source BBF to another target BBF, the PCRF removes the QoS rules related to the service data flow from the source BBF (if the source BBF is located in a BBERF) and provisions the QoS rules related to the service data flow to the target BBF (if the target BBF is located in a BBERF).
- The PCRF may select different bearer establishment mode for different BBFs. Provision of PCC/QoS rules to a specific BBF follows the rule provision procedures based on the bearer establishment mode selected for that BBF. |
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 management (where the IP‑CAN permits), QoS handling and service data flow measurement as well as online and offline charging interactions.
A PCEF shall ensure that an IP packet, which is discarded at the PCEF as a result from PCC rule enforcement or flow based charging, is neither reported for offline charging nor cause credit consumption for online charging.
NOTE 1: For certain cases e.g. suspected fraud an operator shall be able to block the service data flow but still be able to account for any packets associated with any blocked service data flow.
The PCEF is enforcing the Policy Control as indicated by the PCRF in two different ways:
- Gate enforcement. The PCEF shall allow a service data flow, which is subject to policy control, to pass through the PCEF if and only if the corresponding gate is open;
- QoS enforcement:
- QoS class identifier correspondence with IP‑CAN specific QoS attributes. The PCEF shall be able to convert a QoS class identifier value to IP‑CAN specific QoS attribute values and determine the QoS class identifier value from a set of IP‑CAN specific QoS attribute values.
- PCC rule QoS enforcement. The PCEF shall enforce the authorized QoS of a service data flow according to the active PCC rule (e.g. to enforce uplink DSCP marking).
- IP‑CAN bearer QoS enforcement. The PCEF controls the QoS that is provided to a combined set of service data flows. The policy enforcement function ensures that the resources which can be used by an authorized set of service data flows are within the "authorized resources" specified via the Gx interface by "authorized QoS". The authorized QoS provides an upper bound on the resources that can be reserved (GBR) or allocated (MBR) for the IP‑CAN bearer. The authorized QoS information is mapped by the PCEF to IP‑CAN specific QoS attributes. During IP-CAN bearer QoS enforcement, if packet filters are provided to the UE, the PCEF shall provide packet filters with the same content as that in the SDF template filters received over the Gx interface.
The PCEF is enforcing the charging control in the following way:
- For a service data flow (defined by an active PCC rule) that is subject to charging control, the PCEF shall allow the service data flow to pass through the PCEF if and only if there is a corresponding active PCC rule with and, for online charging, the OCS has authorized credit for the charging key. The PCEF may let a service data flow pass through the PCEF during the course of the credit re-authorization procedure.
For a service data flow (defined by an active PCC rule) that is subject to both Policy Control and Charging Control, the PCEF shall allow the service data flow to pass through the PCEF if and only if the right conditions from both policy control and charging control happen. I.e. the corresponding gate is open and in case of online charging the OCS has authorized credit for its charging key.
For a service data flow (defined by an active PCC rule) that is subject to policy control only and not charging control, the PCEF shall allow the service data flow to pass through the PCEF if and only if the conditions for policy control are met.
A PCEF may be served by one or more PCRF nodes. The PCEF shall contact the appropriate PCRF based on the packet data network (PDN) connected to, together with, a UE identity information (if available and which may be IP‑CAN specific). It shall be possible to ensure that the same PCRF is contacted for a specific UE irrespective of the IP‑CAN used.
The operator may configure an indicator in HSS which is delivered to the PCEF within the Charging Characteristics and used by the PCEF to not establish the Gx session during the IP-CAN session establishment procedure.
NOTE 2: The decision to not establish the Gx session applies for the life time of the IP-CAN session.
NOTE 3: The indicator in the HSS is operator specific, therefore its value is understood within the HPLMN and can be used in both non-roaming or home routed roaming cases.
The PCEF shall, on request from the PCRF, modify a PCC rule, using the equivalent PCEF behaviour as the removal of the old and the activation of the new (modified) PCC rule. The PCEF shall modify a PCC rule as an atomic operation. The PCEF shall not modify a predefined PCC rule on request from the PCRF.
The PCEF should support predefined PCC rules.
For online charging, the PCEF shall manage credit as defined in clause 6.1.3.
The operator may apply different PCC rules depending on different PLMN. The PCEF shall be able to provide identifier of serving network to the PCRF, which may be used by the PCRF in order to select the PCC rule to be applied.
The operator may configure whether Policy and Charging Control is to be applied based on different access point.
The PCEF shall gather and report IP‑CAN bearer usage information according to clause 6.1.2. The PCEF may have a pre-configured Default charging method. Upon the initial interaction with the PCRF, the PCEF shall provide pre-configured Default charging method if available.
At IP‑CAN session establishment the PCEF shall initiate the IP‑CAN Session Establishment procedure, as defined in clause 7.2. In case the SDF is tunnelled at the BBERF, the PCEF shall inform the PCRF about the mobility protocol tunnelling header of the service data flows. In case 2a, defined in clause 7.1, the PCEF may provide charging ID information to the PCRF. The PCEF shall inform the PCRF on whether it is enhanced with ADC, or provide the TDF address, if one is configured at the PCEF. If no PCC rule was activated for the IP‑CAN session, the PCEF shall reject the IP‑CAN session establishment.
If there is no PCC rule active for a successfully established IP‑CAN session at any later point in time, e.g. through a PCRF initiated IP‑CAN session modification, the PCEF shall initiate an IP‑CAN session termination procedure, as defined in clause 7.3.2. If the PCRF terminates the Gx session, the PCEF shall initiate an IP‑CAN session termination procedure, as defined in clause 7.3.2.
If there is no PCC rule active for a successfully established IP‑CAN bearer at any later point in time, e.g. through a PCRF initiated IP‑CAN session modification, the PCEF shall initiate an IP‑CAN bearer termination procedure, as defined in clause 7.4.1.
If the IP‑CAN session is modified, e.g. by changing the characteristics for an IP‑CAN bearer, the PCEF shall first use the event trigger to determine whether to request the PCC rules for the modified IP‑CAN session from the PCRF; afterwards, the PCEF shall use the re-authorisation triggers, if available, in order to determine whether to require re-authorisation for the PCC rules that were either unaffected or modified. If the PCEF receives an unsolicited update of the PCC rules from the PCRF (IP‑CAN session modification, clause 7.4.2), the PCC rules shall be activated, modified or removed as indicated by the PCRF.
The PCEF shall inform the PCRF about the outcome of a PCC rule operation. If network initiated procedures apply to the PCC rule and the corresponding IP‑CAN bearer can not be established or modified to satisfy the bearer binding, then the PCEF shall reject the activation of a PCC rule.
The PCEF shall inform the PCRF about any removal of a PCC rule, that the PCRF has activated, that occurs without explicit instruction from the PCRF.
When IP-CAN bearer resources are released, i.e. at IP-CAN session termination or PCEF-initiated IP-CAN session modification notifying that PCC Rules are removed, the PCEF shall also provide, if available, the reason why resources are released, i.e. RAN/NAS Release Cause, TWAN Release Cause or UWAN Release Cause.
NOTE 4: In case of a rejection of a PCC rule activation the PCRF may e.g. modify the attempted PCC rule, de-activate or modify other PCC rules and retry activation or abort the activation attempt and, if applicable, inform the AF that transmission resources are not available.
If network initiated procedures for IP‑CAN bearer establishment apply this also includes provisioning the UE with traffic mapping information. See clause 6.1.9, Annex A and Annex D for details.
If another IP‑CAN session is established by the same user, this is treated independently from the existing IP‑CAN session.
To support the different IP‑CAN bearer establishment modes (UE-only or UE/NW) the PCEF shall:
- forward the network and UE capabilities to the PCRF;
- apply the IP‑CAN bearer establishment mode for the IP‑CAN session set by the PCRF.
During an IP‑CAN session modification, the PCEF shall provide information (belonging to the IP‑CAN bearer established or modified) to the PCRF as follows:
- in UE-only bearer establishment mode, the PCEF shall send the full QoS and traffic mapping information;
- in UE/NW bearer establishment mode, the PCEF shall:
- at UE-initiated bearer establishment, send the full QoS and traffic mapping information;
- at UE-initiated bearer modification, send information on the requested change to QoS bitrates and changes to the traffic mapping information;
- at NW-initiated bearer establishment or modification, the PCEF shall not send any QoS or traffic mapping information.
When flow mobility as specified in TS 23.261 [23] applies, the PCEF shall provide IP flow mobility routing information to the PCRF as follows:
- the default route to be used if no explicit routing information for a service data flow is provided;
- the route for an IP flow.
The PCEF shall derive the routing information from the IP flow mobility flow bindings installed in the PCEF, as defined in TS 23.261 [23].
If there are events which can not be monitored in the PCEF, the PCEF shall provide the information about the required event triggers to the PCRF using the PCEF initiated IP‑CAN Session Modification procedure, as defined in clause 7.4.1, or in the response to a PCRF initiated IP‑CAN Session Modification, as defined in clause 7.4.3. If the triggers were provided by the OCS at credit authorization, it is an implementation option whether a successful confirmation is required from the PCRF in order for the PCEF to consider the credit (re-)authorization procedure to be successful.
IP‑CAN-specific parameters may be sent by the PCRF to the PCEF or the PCEF to the PCRF. The IP‑CAN Session Modification procedure may be used to deliver these parameters to allow interaction between the BBERF and the PCEF by way of the PCRF. This is required in accesses that require these parameters to be sent indirectly.
The PCEF shall support usage monitoring as specified in clause 4.4.
The PCEF enhanced with ADC shall handle application traffic detection as per request from PCRF as well as report about the detected application traffic along with service data flow descriptions, if deducible, to the PCRF, if requested by the PCRF.
The PCEF shall support traffic steering as specified in clause 6.1.17.
The PCEF shall support 3GPP PS Data Off as specified in clause 6.1.21.
The PCEF forwards the Maximum Packet Loss Rate for UL and DL, if received from PCRF for the PCC rule bound to a QCI=1 bearer. In the case multiple PCC Rules share one QCI=1 bearer and the PCEF received multiple Maximum Packet Loss Rates, the PCEF chooses the lowest value per direction related to these PCC rules.
When the PCRF provides updated PCC rules for the IP-CAN session to the PCEF and the PCC rules were not enforced due to that the UE is in suspend state, e.g. due to SRVCC to GERAN without DTM support as specified in clause 6.2.2.1 in the TS 23.216 [28] or CSFB to UTRAN without PS Handover as specified in clause 6.5 in the TS 23.272 [52], the PCEF shall indicate to the PCRF that the PCC Rules were not enforced with the reason that the UE is in suspend state. Upon reception of the failure indication, the PCRF may subscribe to UE resumed from suspend state event trigger. |
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 detection filter.
For PCC rules that contain an application identifier (i.e. that refer to an application detection filter), the order and the details of the detection are implementation specific. The application detection filter may be extended with the PFDs provided by the PFDF as described in clause 6.1.20. The new PFDs provided by the PFDF replace the existing ones in the PCEF. When multiple PFDs are associated with application identifier, the application is detected when any of the PFDs associated with the application identifier is matched. In addition, if a PFD contains multiple attributes, the PFD is only matched when every attribute contained in the PFD has a matching value.
Once an application has been detected, enforcement and charging shall however be applied under consideration of the PCC rule precedence, i.e. when multiple PCC rules overlap, only the enforcement and charging actions of the PCC rule with the highest precedence shall be applied.
For PCC Rules that contain an application identifier (i.e. that refer to an application detection filter) the detection of the uplink part of the service data flow may be active in parallel on other bearers with non-GBR QCI (e.g. the default bearer) in addition to the bearer where the PCC rule is bound to.
NOTE 1: When PCC rules with application detection filters cannot be used to generate traffic mapping information for the UE, the application detection may need to inspect traffic on multiple bearers. The PCEF uses implementation specific logic to determine for what bearers the up-link service data flow detection applies. The uplink traffic will get the QoS of the bearer carrying the traffic. The QCI of the bearer may therefore be different than the QCI of the PCC rule detecting the service data flow. The charging and other enforcement functions performed by the PCEF will still be carried out based on parameters of the PCC rule detecting the service data flow. If the PCC rule contains a GBR QCI, the GBR resource reservation will only apply on the bearer where the PCC rule is bound to. The PCRF can prevent that uplink GBR resources are reserved by providing an uplink GBR value of zero in the PCC rule.
The PCEF shall discard a packet in the case that there is no service data flow template of the same direction (i.e. of the IP‑CAN session for the downlink or of the IP‑CAN bearer for the uplink) detecting the packet.
NOTE 2: For the uplink direction, discarding packets due to no matching service data flow template is also referred to as uplink bearer binding verification. For the case a BBERF is present, uplink bearer binding verification is done by the BBERF.
NOTE 3: If PCC Rule containing an Application Identifier inspects traffic on multiple bearers in the uplink, such detected traffic counts as detection by that PCC rule.
The remainder of this clause describes the detection of service data flows identified by a service data flow filter (i.e. does not apply to PCC rules containing an application identifier):
- Each service data flow template may contain any number of service data flow filters;
- Each service data flow filter is applicable uplink, downlink or both uplink and downlink;
- Service data flow filters are applied for each direction, so that the detection is applied independently for the downlink and uplink directions;
NOTE 4: Service data flow filters that apply in both uplink and downlink should be used whenever the underlying IP‑CAN and access type supports this.
NOTE 5: A service data flow template may include service data flow filters for one direction, or for both directions.
- Each service data flow filter may contain information about whether the explicit signalling of the corresponding traffic mapping information to the UE is required.
NOTE 6: This information enables e.g. the generation/removal of traffic mapping information for a default IP‑CAN bearer as well as the usage of PCC rules with specific service data flow filters on a default IP‑CAN bearer without the need to generate traffic mapping information.
Figure 6.3: Relationship of service data flow, packet flow, service data flow template and service data flow filter
Service data flow filters identifying the service data flow may:
- be a pattern for matching the IP 5 tuple (source IP address or IPv6 network prefix, destination IP address or IPv6 network prefix, source port number, destination port number, protocol ID of the protocol above IP). In the pattern:
- a value left unspecified in a filter matches any value of the corresponding information in a packet;
- an IP address may be combined with a prefix mask;
- port numbers may be specified as port ranges.
- the pattern can be extended by the Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask;
- consist of the destination IP address and optional mask, protocol ID of the protocol above IP, the Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask and the IPSec Security Parameter Index (SPI);
- consist of the destination IP address and optional mask, the Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask and the Flow Label (IPv6).
NOTE 7: The details about the IPSec Security Parameter Index (SPI), the Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask and the Flow Label (IPv6) are defined in clause 15.3 of TS 23.060 [12].
- extend the packet inspection beyond the possibilities described above and look further into the packet and/or define other operations (e.g. maintaining state). Such service data flow filters must be predefined in the PCEF.
NOTE 8: Such filters may be used to support filtering with respect to a service data flow based on the transport and application protocols used above IP. This shall be possible for HTTP and WAP. This includes the ability to differentiate between TCP, Wireless-TCP according to WAP 2.0, WDP, etc, in addition to differentiation at the application level. Filtering for further application protocols and services may also be supported.
For downlink traffic, the downlink parts of all the service data flow templates associated with the IP‑CAN session for the destination address are candidates for matching in the detection process.
Figure 6.4: The service data flow template role in detecting the downlink part of a service data flow and mapping to IP‑CAN bearers
For uplink traffic, the uplink parts of all the service data flow templates associated with the IP‑CAN bearer (details according to clause A), are candidates for matching in the detection process.
Figure 6.5: The service data flow template role in detecting the uplink part of a service data flow
NOTE 9: To avoid the PCEF discarding packets due to no matching service data flow template, the operator may apply open PCC rules (with wild-carded service data flow filters) to allow for the passage of packets that do not match any other candidate service data flow template.
Service data flow templates shall be applied in the order of their precedence. |
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 filter (i.e. with an application identifier).
The PCEF measurement measures all the user plane traffic, except traffic that PCC causes to be discarded.
The PCEF shall maintain a measurement per IP‑CAN bearer (IP‑CAN specific details according to Annex A and Annex D) and Charging Key combination.
If Service identifier level reporting is mandated in a PCC rule, the PCEF shall maintain a measurement for that Charging Key and Service Identifier combination, for the IP‑CAN bearer (IP‑CAN specific details according to Annex A and Annex D).
NOTE 2: In addition, the GW may maintain IP‑CAN bearer level measurement if required by the operator.
For usage monitoring, the PCEF shall support volume and time measurement for an IP-CAN session and maintain a measurement for each IP-CAN session for which the PCRF has requested the Usage report trigger and provided threshold values on an IP‑CAN session level. The PCEF shall be able to support volume and time measurements simultaneously for a given IP-CAN session.
The PCEF shall support volume and time measurement per Monitoring key and maintain a measurement for each Monitoring key if the PCRF has requested the Usage report trigger and provided threshold values on Monitoring key level. The PCEF shall be able to support volume and time measurements simultaneously for a given Monitoring Key.
The PCEF shall support simultaneous volume and time measurement for usage monitoring on IP‑CAN session level and Monitoring key level for the same IP‑CAN session.
Volume and time measurements for usage monitoring purposes on IP‑CAN session level and on Monitoring key level shall be performed independently of each other. If the PCC rule is associated with an indication of exclusion from session level monitoring, the PCEF shall not consider the corresponding service data flow for the volume and time measurement on IP-CAN session level.
If the Usage report reached event trigger is set and a volume or a time threshold is reached, the PCEF shall report this event to the PCRF. The PCEF shall continue to perform volume or time measurement after the threshold is reached and before a new threshold is provided by the PCRF. At IP-CAN session termination or if the conditions defined in clause 6.6.2 for continued monitoring are no longer met, or if the PCRF explicitly requests a usage report, the PCEF shall inform the PCRF about the resources that have been consumed by the user since the last usage report for the affected Monitoring keys, including the resources consumed before and after the Monitoring time was reached, if provided according to clause 6.2.1.0.
If combined volume and time measurements are requested by the PCRF, then the reporting shall be done for both together. For example, if the volume threshold is reached, the consumed time shall be reported as well and, in order to continue combined volume and time measurements, the PCRF shall provide a new time threshold along with a new volume threshold. The PCEF shall continue to perform volume and time measurement after the threshold is reached and before a new threshold is provided by the PCRF. If new threshold is provided only for time or volume, then the measurements shall continue only for that provided type and the accumulated usage for the non provided type shall be discarded by the PCEF.
When the PCRF requests to report usage, the PCEF shall report the accumulated usage to the PCRF according to the provided usage threshold, i.e. the PCEF reports accumulated volume when the volume threshold was provided by the PCRF, accumulated time when the time threshold was provided by the PCRF and both accumulated volume and accumulated time when volume threshold and time threshold were provided by the PCRF.
If the Usage thresholds for a Monitoring key are not provided to the PCEF in the acknowledgement of an IP-CAN Session modification where its usage was reported, then the usage monitoring shall not continue in the PCEF for that Monitoring key.
When the Monitoring time occurs, the accumulated volume and/or time usage shall be recorded by the PCEF and:
- If the subsequent usage threshold value is provided, the usage threshold shall be reset to this value by the PCEF.
- Otherwise, the usage threshold shall be set by the PCEF to the remaining value of the threshold previously sent by the PCRF (i.e. excluding the accumulated usage).
The first usage report after the Monitoring Time was reached shall indicate the usage up to the Monitoring time and usage after the Monitoring time.
In order to support time based usage monitoring, the PCRF may optionally indicate to the PCEF, along with other usage monitoring information provided, the Inactivity Detection Time. This value represents the time interval after which the time measurement shall stop for the Monitoring key, if no packets are received belonging to the corresponding Monitoring Key during that time period. Time measurement shall resume on receipt of a further packet belonging to the Monitoring key.
Time measurement for a Monitoring key shall also be stopped when time based usage monitoring is disabled, if this happens before the Inactivity Detection Time is reached.
If an Inactivity Detection Time value of zero is provided, or if no Inactivity Detection Time is present within the usage monitoring information provided by the PCRF, the time measurement shall be performed continuously from the point at which it was started until time based usage monitoring is disabled. |
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.
For a UE-initiated IP‑CAN bearer establishment or modification the PCEF receives the authorized QoS (QCI, ARP, GBR, MBR) for a bearer that the PCEF has identified for the PCRF. The PCEF shall enforce it which may lead to a downgrading or upgrading of the requested bearer QoS.
NOTE 1: The MBR is an average value, which is measured over some time period. Services may generate media with variable bitrate. For example, TS 26.114 [45] describes the bitrate variations that may be generated for real-time conversational media in the MTSI service. The policing function in the PCEF should take such bitrate variations into account.
For a network initiated IP‑CAN bearer establishment or modification the PCEF receives the authorized QoS per PCC rule (QCI, ARP, GBR, MBR). For GBR bearers the PCEF should set the bearer's GBR to the sum of the GBRs of all PCC rules that are active and bound to that GBR bearer. If a set of PCC Rules is subject to resource sharing as specified in clause 6.1.14 the PCEF should use, for each applicable direction, the highest GBR from the set of PCC Rules sharing resources as input for calculating the bearer´s GBR. For GBR bearers the PCEF should set the bearer's MBR to the sum of the MBRs of all PCC rules that are active and bound to that GBR bearer. If a set of PCC Rules is subject to resource sharing as specified in clause 6.1.14 the PCEF may, for each applicable direction, use the highest MBR from the set of PCC Rules as input for calculating the bearer´s MBR.
NOTE 2: Since the PCRF controls the GBR value in the PCC rule, the PCRF can prevent that uplink GBR resources are reserved by providing an uplink GBR value of zero for that PCC rule, This may be useful e.g. for a PCC rule with application identifier as the uplink traffic can be received in other bearers than the one the PCC rule is bound to.
For an IP‑CAN that supports non-GBR bearers that have a separate MBR (e.g. GPRS) the PCEF may, before or in connection with activation of the first PCC rule with a certain QCI, receive the authorized QoS (QCI, MBR) for that QCI. The authorized MBR per QCI only applies to non-GBR bearers and it sets an upper limit for the MBR that the PCEF assigns to a non-GBR bearer with that QCI. In case multiple IP‑CAN bearers within the same IP‑CAN session are assigned the same QCI, the authorized MBR per QCI applies independently to each of those IP‑CAN bearers. The PCRF may change the authorized MBR per QCI at any time. An authorized GBR per QCI shall not be signalled on Gx.
NOTE 3: The intention of the authorized MBR per QCI is to avoid frequent IP‑CAN bearer modifications as PCC rules are dynamically activated and deactivated. That is, the PCEF may choose to assign the authorized MBR per QCI to a non-GBR bearer with that QCI. |
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 PCRF:
- For the Start of application event trigger: the application identifier and, when service data flow descriptions are deducible, the application instance identifier and the service data flow descriptions to use for detecting that application traffic with a dynamic PCC rule as defined in clause 6.1.4.
- For the Stop of application event trigger: the application identifier and if the application instance identifier was reported for the Start, also the application instance identifier as defined in the clause 6.1.4. |
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 policy, the PCEF performs deployment specific actions as configured for that traffic steering policy. The PCEF may for example perform packet marking where, for the traffic identified by the service data flow template (defined by an active PCC rule), the PCEF provides information for traffic steering, as part of the packets, to the (S)Gi-LAN. This information for traffic steering identifies, explicitly or implicitly, a specific set of service functions and their order via which the traffic needs to be steered in the (S)Gi-LAN. |
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 notifications about IP‑CAN bearer level events. One example of an AF is the P‑CSCF of the IM CN subsystem.
The AF may receive an indication that the service information is not accepted by the PCRF together with service information that the PCRF would accept. In that case, the AF rejects the service establishment towards the UE. If possible the AF forwards the service information to the UE that the PCRF would accept.
An AF may communicate with multiple PCRFs. The AF shall contact the appropriate PCRF based on either:
- the end user IP Address; and/or
- a UE identity that the AF is aware of.
NOTE 1: By using the end user IP address, an AF is not required to acquire any UE identity in order to provide information, for a specific user, to the PCRF.
In case of private IP address being used for the end user, the AF may send additional PDN information (e.g. PDN ID) over the Rx interface. This PDN information is used by the PCRF for session binding and it is also used to help selecting the correct PCRF.
For certain events related to policy control, the AF shall be able to give instructions to the PCRF to act on its own, i.e. based on the service information currently available as described in clause 6.1.5.
The AF may use the IP‑CAN bearer level information in the AF session signalling or to adjust the IP‑CAN bearer level event reporting.
The AF may request the PCRF to report on IP‑CAN bearer level events (e.g. the signalling path status for the AF session). The AF shall cancel the request when the AF ceases handling the user.
NOTE 2: The QoS authorization based on incomplete service information is required for e.g. IMS session setup scenarios with available resources on originating side and a need for resource reservation on terminating side.
The AF may request the PCRF to report on the change of type of IP‑CAN. The PCRF shall report the IP-CAN type and subsequent changes to the AF together with the information of the Radio Access Technology Type (e.g. UTRAN) as defined in access specific annexes. The change of the Radio Access Technology Type (e.g. UTRAN) shall be also reported to the AF, even if the IP‑CAN type is unchanged.
The AF may request the PCRF to report any combination of the user location and/or UE Timezone at AF session establishment, modification or termination. For AF session termination the communication between the AF and the PCRF shall be kept alive until the PCRF report is received.
The AF may request the PCRF to report changes of the PLMN identifier where the UE is currently located at AF session establishment. The PLMN identifier reporting remains until the AF session is terminated.
If IP-CAN bearer resources corresponding to the AF session are released, the PCRF reports to the AF, if available, the reason why IP-CAN bearer resources are released i.e. RAN/NAS Release Cause, TWAN Release Cause or UWAN Release Cause.
If IP-CAN bearer resources corresponding to the AF session are released, the PCRF reports to the AF, if available, the User Location Information and/or the UE Timezone.
NOTE 3: The H-PCRF informs the AF of event triggers that cannot be reported. For detail see Annex L.
To support sponsored data connectivity (see Annex N), the AF may provide the PCRF with the sponsored data connectivity information, including optionally a usage threshold, as specified in clause 5.2.1. The AF may request the PCRF to report events related to sponsored data connectivity.
If the user plane traffic traverses the AF, the AF may handle the usage monitoring and therefore it is not required to provide a usage threshold to the PCRF as part of the sponsored data connectivity information.
In order to mitigate RAN user plane congestion, the Rx reference point enables transport of the following information from the PCRF to the AF:
- Re-try interval, which indicates when service delivery may be retried on Rx.
NOTE 4: Additionally, existing bandwidth limitation parameters on Rx interface during the Rx session establishment are available in order to mitigate RAN user plane congestion.
When receiving service information from the AF, the PCRF may temporarily reject the AF request (e.g. if the service information is not consistent with the operator defined policy rules for the congestion status of the user). To temporarily reject the AF request the PCRF shall indicate a re-try interval to the AF. When receiving a re-try interval from the PCRF the AF shall not send the same service information to the PCRF again (for the same IP‑CAN session) until the re-try interval has elapsed.
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 (as described in clause 6.1.16). If the PCRF replies with more than one transfer policy, the AF shall select one of them and inform the PCRF about the selected transfer policy. The reference ID provided by the PCRF shall be used by the AF during every subsequent transfer of AF session information related to this background data transfer (via the Rx interface). |
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 SPR are out of scope of this document.
NOTE 1: The SPR's relation to existing subscriber databases is not specified in this Release.
The SPR may provide the following subscription profile information (per PDN, which is identified by the PDN identifier):
- Subscriber's allowed services;
- For each allowed service, a pre-emption priority;
- Information on subscriber's allowed QoS, including the Subscribed Guaranteed Bandwidth QoS;
- Subscriber's charging related information (e.g. location information relevant for charging);
- Subscriber's User CSG Information reporting rules;
- List of Presence Reporting Area identifiers and optionally the elements for one or more of the Presence Reporting Areas;
- Subscriber category;
- Subscriber's usage monitoring related information;
- MPS EPS Priority and MPS Priority Level;
- IMS Signalling Priority;
- Subscriber's profile configuration indicating whether application detection and control can be enabled.
- Spending limits profile containing an indication that policy decisions are based on policy counters available at OCS that has a spending limit associated with it and optionally the list of policy counters.
The SPR may provide the following sponsored data connectivity profile information:
- A list of Application Service Providers and their applications per sponsor identity.
NOTE 2: The sponsored data connectivity profile may be locally configured at the PCRF.
If the IMS Signalling Priority is set, it indicates that the IMS Signalling Bearer and the Default Bearer are assigned ARP appropriate for MPS at the time of the establishment of the PDN connection for IMS, i.e. EPS Attach or PDN Connectivity Request.
The SPR may provide the following policy information related to an ASP (see clause 6.1.16):
- The ASP identifier;
- A transfer policy together with a reference ID, the volume of data to be transferred per UE, the expected amount of UEs and the network area information.
NOTE 3: The information related to an ASP is only available in the SPR after being stored by the PCRF as described in clauses 6.1.16 and 7.11.1.
NOTE 4: A transfer policy is only valid until the end of its time window. The removal of outdated transfer policies from the SPR is up to implementation. |
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 about the existence of any specific service/application), it is recommended to use different charging keys for any service/application that shall not be unintentionally interrupted.
There may be several OCSs in a PLMN. The default OCS addresses (i.e. the primary address and secondary address) shall be locally pre-configured within the PCEF and TDF. OCS addresses may also be passed once per IP‑CAN session or TDF session from the PCRF to the PCEF or TDF. The OCS addresses provided by the PCRF shall have a higher priority than the pre-configured ones. |
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 the PCEF or TDF. The addresses provided by the PCRF shall have a higher priority than the pre-configured ones. |
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 the uplink direction, the BBERF applies QoS rules with a bearer binding to the bearer that the packet arrived on. The uplink bearer binding verification is successful if there is a QoS rule with a matching uplink SDF filter. The BBERF shall discard packets for which the uplink bearer binding verification fails. |
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 identifier value from a set of QoS attribute values used in the access network.
NOTE: The definition of the mapping between QCI and Non 3GPP access specific QoS is outside of scope for 3GPP.
The BBERF controls the QoS that is provided to a combined set of service data flows. BBERF ensures that the resources which can be used by an authorized set of service data flows are within the "authorized resources" specified via the Gxx interface by "authorized QoS". The authorized QoS provides an upper bound on the resources that can be reserved (GBR) or allocated (MBR) for the service data flows.
In order to support the different IP‑CAN bearer establishment modes (UE-only or UE/NW), the BBERF shall support the same procedures for handling different IP‑CAN bearer establishment modes as specified for the PCEF in clauses 6.2.2.1 and 6.2.2.4. |
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/subscription data. This reference point is named Ud. More information on the UDR can be found in TS 23.335 [25].
The SPR data listed in clause 6.2.4 are stored in the UDR, the information model remains unspecified. |
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 by the PFDF as described in clause 6.1.20. The new PFDs provided by the PFDF replace the existing ones in the PCEF.
The TDF shall detect Start and Stop of the application traffic for the ADC rules that the PCRF has activated at the TDF (solicited application reporting) or which are pre-provisioned at the TDF (unsolicited application reporting). The TDF shall report, unless the notification is muted for the specific ADC Rule in case of solicited application reporting, to the PCRF:
- For the Start of application event trigger: the application identifier and, when service data flow descriptions are deducible, the application instance identifier and the service data flow descriptions to use for detecting that application traffic with a dynamic PCC rule as defined in clause 6.1.4.
- For the Stop of application event trigger: the application identifier and if the application instance identifier was reported for the Start, also the application instance identifier as defined in the clause 6.1.4.
For solicited application reporting, the PCRF can request the TDF to also perform enforcement actions, charging and usage monitoring.
For those cases where service data flow description is not possible to be provided by the TDF to the PCRF, the TDF performs:
- Gating;
- Redirection;
- Bandwidth limitation;
- Charging.
for the detected applications.
For those cases where service data flow description is provided by the TDF to the PCRF the actions resulting of application detection may be performed by the PCEF as part of the charging and policy enforcement per service data flow as defined in this document or may be performed by the TDF.
NOTE: The PCEF can be enhanced with application detection and control feature as specified in clause 6.2.2.5.
The TDF shall support usage monitoring as specified in clause 4.4 and the usage reporting functions as specified in clause 6.2.2.3 for the PCEF.
The TDF shall support data volume, duration, combined volume/duration and event based measurement for charging. The Measurement method indicates what measurement type is applicable for the ADC rule.
NOTE 1: Events to be charged are predefined in the TDF.
The TDF measurement measures all the user plane traffic, except packets discarded by ADC-rule enforcement or due to MBR-enforcement.
The TDF shall maintain a measurement per TDF session and Charging Key combination.
If Service identifier level reporting is mandated in an ADC rule, the TDF shall maintain a measurement for that Charging Key and Service identifier combination, for the TDF session.
If there are required events which cannot be monitored in the TDF (e.g. related to the location changes), the TDF shall request the information about these Event Triggers from the PCRF using either:
- The IP-CAN Session Establishment procedure, as defined in clause 7.2, or
- The PCEF initiated IP-CAN Session Modification procedure, as defined in clause 7.4.1, or
- In the response to a PCRF initiated IP-CAN Session Modification, as defined in clause 7.4.2, or
- Within the Update of the subscription information in the PCRF procedure, as defined in clause 7.5.
For unsolicited application reporting, the TDF performs only application detection and reporting functionality but neither enforcement actions nor usage monitoring. The TDF should handle each IPv4 address and IPv6 prefix, assuming the max prefix length used in the access network, within a separate TDF session. The PCRF shall, if needed, correlate TDF sessions that correspond to the same IP-CAN session.
The TDF shall support traffic steering as specified in clause 6.1.17. |
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, the TDF performs deployment specific actions as configured for that traffic steering policy. The TDF may for example perform packet marking where, for the traffic identified by the Application Identifier or by the service data flow filter list (defined by an active ADC rule), the TDF provides information for traffic steering, as part of the packets, to the (S)Gi-LAN. This information for traffic steering identifies, explicitly or implicitly, a specific set of service functions and their order via which the traffic needs to be steered in the (S)Gi-LAN. |
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 follows:
- For a PDN connection in a non-roaming scenario the RCAF reports the RUCI to the PCRF.
- For a PDN connection in a local breakout scenario, based on operator configuration, the RCAF reports the RUCI to the V-PCRF.
- For a PDN connection in a home routed scenario, based on the roaming agreement with the HPLMN and operator configuration, the RCAF reports the RUCI to the H-PCRF.
NOTE 1: Reporting of congestion information to the HPLMN may be used e.g. in case of a group of PLMNs which belong to a single business entity.
The RCAF determines whether a given PDN connection is served in a local breakout or a home routed roaming scenario based on the APN operator identifier received as part of the APN information from the MME or the S4-SGSN as documented in TS 23.401 [17] and TS 23.060 [12], respectively.
NOTE 2: Operator configuration can be used to limit RUCI reporting on the Np interface to certain APNs only.
In addition if the RCAF detects that a UE is no longer subject to congestion (i.e. the UE is no longer detected in any of the congested cells that the RCAF is monitoring) then the RCAF shall indicate the no congestion state to the PCRFs serving the UE.
Any RUCI changes shall be reported by RCAF unless reporting restrictions apply.
The RCAF maintains a context on per UE and per APN basis. The context is identified by the IMSI and the APN. It contains the following information:
- The previously reported congestion level over the Np reference point.
- The reporting restrictions received from the PCRF. The reporting restrictions are stored by the RCAF until the PCRF explicitly signals to remove the reporting restrictions.
- The logical PCRF id received from the PCRF to identify the PCRF that is the Np destination for the RCAF when sending aggregate messages. |
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 steering policy is enforced, the TSSF performs deployment specific actions as configured for that traffic steering policy. For example, the TSSF may configure traffic detection and forwarding entities in the (S)Gi-LAN to fulfil the traffic steering policy. |
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 identifier from the SCEF as defined in TS 23.682 [42]. |
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 PCC rules exist: Dynamic rules and predefined rules. The dynamic PCC rules are provisioned by the PCRF via the Gx reference point, while the predefined PCC rules are directly provisioned into the PCEF and only referenced by the PCRF. The usage of predefined PCC rules for QoS control is possible if the BBF remains in the PCEF during the lifetime of an IP-CAN session. In addition, predefined PCC rules may be used in a non-roaming situation and if it can be guaranteed that corresponding predefined QoS rules are configured in the BBF and activated along with the predefined PCC rules.
NOTE 1: The procedure for provisioning predefined PCC rules is out of scope for this specification.
NOTE 2: There may be another type of predefined rules that are not explicitly known in the PCRF and not under the control of the PCRF. The operator may define such predefined PCC rules, to be activated by the PCEF on one IP‑CAN bearer within the IP‑CAN session. The PCEF may only activate such predefined PCC rules if there is no UE provided traffic mapping information related to that IP‑CAN bearer. The IP‑CAN session termination procedure deactivates such predefined PCC rules.
There are defined procedures for activation, modification and deactivation of PCC rules (as described in clause 6.3.2). The PCRF may activate, modify and deactivate a PCC rule at any time, over the Gx reference point. However, the modification procedure is applicable to dynamic PCC rules only.
Each PCC rule shall be installed for a single IP‑CAN bearer only (for further details about predefined PCC rules see clause 6.3.2).
The operator defines the PCC rules.
Table 6.3 lists the information contained in a PCC rule, including the information name, the description and whether the PCRF may modify this information in a dynamic PCC rule which is active in the PCEF. The Category field indicates if a certain piece of information is mandatory or not for the construction of a PCC rule, i.e. if it is possible to construct a PCC rule without it.
Table 6.3: The PCC rule information
Information name
Description
Category
PCRF permitted to modify for a dynamic PCC rule in the PCEF
Rule identifier
Uniquely identifies the PCC rule, within an IP‑CAN session.
It is used between PCRF and PCEF for referencing PCC rules.
Mandatory
no
Service data flow detection
This part defines the method for detecting packets belonging to a service data flow.
Precedence
Determines the order, in which the service data flow templates are applied at service data flow detection, enforcement and charging. (NOTE 9).
Conditional (NOTE 13)
yes
Service data flow template
Either a list of service data flow filters or an application identifier that references the corresponding application detection filter for the detection of the service data flow.
Mandatory (NOTE 7)
Conditional (NOTE 12)
Mute for notification
Defines whether application's start or stop notification is to be muted.
Conditional (NOTE 8)
No
Charging
This part defines identities and instructions for charging and accounting that is required for an access point where flow based charging is configured
Charging key
The charging system (OCS or OFCS) uses the charging key to determine the tariff to apply to the service data flow.
yes
Service identifier
The identity of the service or service component the service data flow in a rule relates to.
yes
Sponsor Identifier
An identifier, provided from the AF which identifies the Sponsor, used for sponsored flows to correlate measurements from different users for accounting purposes.
Conditional
(NOTE 6)
yes
Application Service Provider Identifier
An identifier, provided from the AF which identifies the Application Service Provider, used for sponsored flows to correlate measurements from different users for accounting purposes.
Conditional
(NOTE 6)
yes
Charging method
Indicates the required charging method for the PCC rule.
Values: online, offline or neither.
Conditional
(NOTE 4)
no
Measurement method
Indicates whether the service data flow data volume, duration, combined volume/duration or event shall be measured.
This is applicable to reporting, if the charging method is online or offline.
Note: Event based charging is only applicable to predefined PCC rules and PCC rules used for application detection filter (i.e. with an application identifier).
yes
Application Function Record Information
An identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports.
no
Service identifier level reporting
Indicates that separate usage reports shall be generated for this Service identifier.
Values: mandated or not required
Yes
Policy control
This part defines how the PCEF shall apply policy control for the service data flow.
Gate status
The gate status indicates whether the service data flow, detected by the service data flow template, may pass (Gate is open) or shall be discarded (Gate is closed) at the PCEF.
Yes
QoS class identifier
Identifier for the authorized QoS parameters for the service data flow.
Values: see NOTE 1.
Conditional
(NOTE 2)
Yes
UL-maximum bitrate
The uplink maximum bitrate authorized for the service data flow
Conditional
(NOTE 3)
Yes
DL-maximum bitrate
The downlink maximum bitrate authorized for the service data flow
Conditional
(NOTE 3)
Yes
UL-guaranteed bitrate
The uplink guaranteed bitrate authorized for the service data flow
Yes
DL-guaranteed bitrate
The downlink guaranteed bitrate authorized for the service data flow
Yes
UL sharing indication
Indicates resource sharing in uplink direction with service data flows having the same value in their PCC rule
No
DL sharing indication
Indicates resource sharing in downlink direction with service data flows having the same value in their PCC rule
No
Redirect
Redirect state of the service data flow (enabled/disabled)
Conditional (NOTE 10)
Yes
Redirect Destination
Controlled Address to which the service data flow is redirected when redirect is enabled
Conditional
(NOTE 11)
Yes
ARP
The Allocation and Retention Priority for the service data flow consisting of the priority level, the pre-emption capability and the pre-emption vulnerability
Conditional
(NOTE 5)
Yes
Bind to Default Bearer
Indicates that the dynamic PCC rule shall always have its bearer binding with the default bearer.
Conditional
(NOTE 15)
Yes
PS to CS session continuity
Indicates whether the service data flow is a candidate for vSRVCC.
Conditional
No
Access Network Information Reporting
This part describes access network information to be reported for the PCC rule when the corresponding bearer is established, modified or terminated.
User Location Report
The serving cell of the UE is to be reported. When the corresponding bearer is deactivated and if available, information on when the UE was last known to be in that location is also to be reported.
Yes
UE Timezone Report
The time zone of the UE is to be reported.
Yes
Usage Monitoring Control
This part describes identities required for Usage Monitoring Control.
Monitoring key
The PCRF uses the monitoring key to group services that share a common allowed usage.
Yes
Indication of exclusion from session level monitoring
Indicates that the service data flow shall be excluded from the IP-CAN session usage monitoring
Yes
Traffic Steering Enforcement Control
This part describes identities required for Traffic Steering Enforcement Control.
Traffic steering policy identifier(s)
Reference to a pre-configured traffic steering policy at the PCEF (NOTE 14).
Yes
NBIFOM related control Information
This part describes PCC rule information related with NBIFOM (defined in TS 23.161 [43]. Refer also to clause 6.1.18.
Allowed Access Type
The access to be used for traffic identified by the PCC rule
Yes
Routing Rule Identifier
The Routing Rule identifier to be used in NBIFOM routing rule
No
RAN support information
This part defines information supporting the RAN for e.g. handover threshold decision.
UL Maximum Packet Loss Rate
The maximum rate for lost packets that can be tolerated in the uplink direction for service data flow. It is defined in clause 5.4.1 of TS 23.401 [17].
Conditional (NOTE 16)
Yes
DL Maximum Packet Loss Rate
The maximum rate for lost packets that can be tolerated in the downlink direction for service data flow. It is defined in clause 5.4.1 of TS 23.401 [17].
Conditional (NOTE 16)
Yes
NOTE 1: The QoS class identifier is scalar and accommodates the need for differentiating QoS in all types of 3GPP IP‑CAN. The value range is expandable to accommodate additional types of IP‑CAN.
NOTE 2: The QoS class identifier is mandatory when the bearer binding is allocated to the PCEF.
NOTE 3: Mandatory when the QoS class identifier is of Resource Type GBR. Used to activate policy control on SDF level at the PCEF.
NOTE 4: Mandatory if there is no default charging method for the IP‑CAN session.
NOTE 5: Mandatory when policy control on SDF level applies unless otherwise stated in an access-specific Annex.
NOTE 6: Applicable to sponsored data connectivity.
NOTE 7: Either service data flow filter(s) or application identifier shall be defined per each rule. application identifier can only be used for PCEF enhanced with ADC.
NOTE 8: Optional and applicable only if application identifier exists within the rule.
NOTE 9: For PCC rules based on an application detection filter, the precedence is only relevant for the enforcement, i.e. when multiple PCC rules overlap, only the enforcement, reporting of application starts and stops, monitoring and charging actions of the PCC rule with the highest precedence shall be applied.
NOTE 10: Optional and applicable only if application identifier exists within the rule.
NOTE 11: If Redirect is enabled.
NOTE 12: YES, in case the service data flow template consists of a set of service data flow filters. NO in case the service data flow template consists of an application identifier.
NOTE 13: The Precedence is mandatory for PCC rules with SDF template containing SDF filter(s). For dynamic PCC rules with SDF template containing an application identifier, the precedence is either preconfigured in PCEF or provided in the PCC rule from PCRF.
NOTE 14: The Traffic steering policy identifier can be different for uplink and downlink direction. If two Traffic steering policy identifiers are provided, then one is for uplink direction, while the other one is for downlink direction.
NOTE 15: The presence of this attribute causes the QCI/ARP of the rule to be ignored. This attribute is defined for selected accesses as specified in the access specific Annexes.
NOTE 16: Optional and applicable only for voice service data flow in this Release.
The Rule identifier shall be unique for a PCC rule within an IP‑CAN session. A dynamically provided PCC rule that has the same Rule identifier value as a predefined PCC rule shall replace the predefined rule within the same IP‑CAN session.
The Service data flow template may comprise any number of Service data flow filters. A Service data flow filter contains information for matching user plane packets. A Service data flow filter, provided from the PCRF, contains information elements as described in clause 6.2.2.2. The Service data flow template filtering information within an activated PCC rule is applied at the PCEF to identify the packets belonging to a particular service data flow.
NOTE 3: Predefined PCC rules may include service data flow filters, which support extended capabilities, including enhanced capabilities to identify events associated with application protocols.
Alternatively, the Service data flow template consists of an application identifier that references an application detection filter that is used for matching user plane packets. The application identifier is also identifying the application, for which the rule applies. The same application identifier value can occur in more than one PCC rule with the following restrictions:
- The same application identifier value can be used for a dynamic PCC rule and one or multiple predefined PCC rules. If so, the PCRF shall ensure that there is at most one PCC rule active per application identifier value at any time.
NOTE 4: The configuration of the Application Identifier in the PCEF can include the set of information required for encrypted traffic detection as defined in Annex X.
The Mute for notification defines whether notification to the PCRF of application's starts or stops shall be muted. Absence of this parameter means that start/stop notifications shall be sent.
The Precedence defines in what order the activated PCC rules within the same IP‑CAN session shall be applied at the PCEF for service data flow detection. When a dynamic PCC rule and a predefined PCC rule have the same precedence, the dynamic PCC rule takes precedence. For dynamic PCC rules that contain an application identifier, the Precedence shall be either preconfigured at the PCEF or provided dynamically by the PCRF within the PCC Rules.
NOTE 5: The operator shall ensure that overlap between the predefined PCC rules can be resolved based on precedence of each predefined PCC rule in the PCEF. The PCRF shall ensure that overlap between the dynamically allocated PCC rules can be resolved based on precedence of each dynamically allocated PCC rule. Further information about the configuration of the PCC rule precedence is described in Annex G.
NOTE 6: Whether precedence for dynamic PCC rules that contain an application identifier is preconfigured in PCEF or provided in the PCC rule from the PCRF depends on network configuration.
For downlink packets all the service data flow templates, activated for the IP‑CAN session shall be applied for service data flow detection and for the mapping to the correct IP‑CAN bearer. For uplink packets the service data flow templates activated on their IP‑CAN bearer shall be applied for service data flow detection (further details provided in clause 6.2.2.2 and the IP-CAN specific annexes).
The Charging key is the reference to the tariff for the service data flow. Any number of PCC Rules may share the same charging key value. The charging key values for each service shall be operator configurable.
NOTE 7: Assigning the same Charging key for several service data flows implies that the charging does not require the credit management to be handled separately.
NOTE 8: If the IP flow mobility is supported and the tariff depends on what access network is in use for the service data flow, then a separate Charging key can be allocated for each access network and the PCRF can set the Charging key in accordance with the access network in use.
The Service identifier identifies the service. PCC Rules may share the same service identifier value. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow.
NOTE 9: The PCC rule service identifier need not have any relationship to service identifiers used on the AF level, i.e. is an operator policy option.
The Sponsor Identifier indicates the (3rd) party organization willing to pay for the operator's charge for connectivity required to deliver a service to the end user.
The Application Service Provider Identifier indicates the (3rd) party organization delivering a service to the end user.
The Charging method indicates whether online charging, offline charging, or both are required or the service data flow is not subject to any end user charging. If the charging method identifies that the service data flow is not subject to any end user charging, a Charging key shall not be included in the PCC rule for that service data flow, along with other charging related parameters. If the charging method is omitted the PCEF shall apply the default charging method as determined at IP‑CAN session establishment (see clause 6.4). The Charging method is mandatory if there is no default charging method for the IP‑CAN session.
The Measurement method indicates what measurements apply to charging for PCC rule.
The Service Identifier Level Reporting indicates whether the PCEF shall generate reports per Service Identifier. The PCEF shall accumulate the measurements from all PCC rules with the same combination of Charging key/Service identifier values in a single report.
The Application function record information identifies an instance of service usage. A subsequently generated usage report, generated as a result of the PCC rule, may include the Application function record information, if available. The Application Function Record Information may contain the AF Charging Identifier and/or the Flow identifiers. The report is however not restricted to include only usage related to the Application function record information reported, as the report accumulates the usage for all PCC rules with the same combination of Charging key/Service identifier values. If exclusive charging information related to the Application function record information is required, the PCRF shall provide a service identifier, not used by any other PCC rule of the IP‑CAN session at this point in time, for the AF session.
NOTE 10: For example, the PCRF may be configured to maintain a range of service identifier values for each service which require exclusive per instance charging information. Whenever a separate counting or credit management for an AF session is required, the PCRF shall select a value, which is not used at this point in time, within that range. The uniqueness of the service identifier in the PCEF ensures a separate accounting/credit management while the AF record information identifies the instance of the service.
The Gate indicates whether the PCEF shall let a packet identified by the PCC rule pass through (gate is open) the PCEF, or the PCEF shall discard (gate is closed) the packet.
NOTE 11: A packet, matching a PCC Rule with an open gate, may be discarded due to credit management reasons.
The QoS Class Identifier for the service data flow. The QoS class identifier represents the QoS parameters for the service data flow. The PCEF maintains the mapping between QoS class identifier and the QoS concept applied within the specific IP‑CAN. The bitrate information is separate from the QoS class identifier value.
The bitrates indicate the authorized bitrates at the IP packet level of the SDF, i.e. the bitrates of the IP packets before any IP‑CAN specific compression or encapsulation.
The UL maximum-bitrate indicates the authorized maximum bitrate for the uplink component of the service data flow.
The DL maximum-bitrate indicates the authorized maximum bitrate for the downlink component of the service data flow.
The UL guaranteed-bitrate indicates the authorized guaranteed bitrate for the uplink component of the service data flow.
The DL guaranteed-bitrate indicates the authorized guaranteed bitrate for the downlink component of the service data flow.
The 'Maximum bitrate' is used for enforcement of the maximum bit rate that the SDF may consume, while the 'Guaranteed bitrate' is used by the PCEF to determine resource allocation.
The UL sharing indication indicates that resource sharing in uplink direction for service data flows with the same value in their PCC rule shall be applied by the PCEF as described in clauses 6.1.14 and 6.2.2.4.
The DL sharing indication indicates that resource sharing in downlink direction for service data flows with the same value in their PCC rule shall be applied by the PCEF as described in clauses 6.1.14 and 6.2.2.4.
The Redirect indicates whether the uplink part of the service data flow should be redirected to a controlled address.
The Redirect Destination indicates the target redirect address when Redirect is enabled.
The Allocation and Retention Priority indicates the allocation, retention and priority of the service data flow. The ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. The Allocation and Retention Priority resolves conflicts of demands for network resources.
The Bind to Default Bearer indicates that the dynamic PCC rule shall be bound to the default bearer.
The PS to CS session continuity is present if the service data flow is a candidate for vSRVCC according to TS 23.216 [28].
The access network information reporting parameters (User Location Report, UE Timezone Report) instruct the PCEF about what information to forward to the PCRF when the PCC rule is activated, modified or removed.
The Monitoring Key is the reference to a resource threshold. Any number of PCC Rules may share the same monitoring key value. The monitoring key values for each service shall be operator configurable.
The Indication of exclusion from session level monitoring indicates that the service data flow shall be excluded from the IP-CAN session usage monitoring.
The Traffic Steering Policy Identifier(s) is a reference to a pre-configured traffic steering policy at the PCEF as defined in clause 6.11.1.
The Allowed Access Type applies only in case of NBIFOM. The Allowed Access Type indicates the IP-CAN type that is to be used for the transfer of traffic identified by the PCC rule. The PCEF uses the Allowed Access Type as input for the bearer binding. When network-initiated NBIFOM mode applies, the PCEF shall also create / modify / delete a corresponding Routing Rule for such a PCC rule at the UE as described in clause 6.1.18.2. When the Allowed Access Type is not provided within a PCC rule, the traffic identified by the PCC rule is to be transferred on the default NBIFOM access.
The Routing Rule Identifier applies only in case of NBIFOM. The PCRF provides it to the PCEF only when network-initiated NBIFOM mode applies.
The UL Maximum Packet Loss Rate indicates the maximum rate for lost packets that can be tolerated in the uplink direction.
The DL Maximum Packet Loss Rate indicates the maximum rate for lost packets that can be tolerated in the downlink direction. |
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 the Gx reference point.
Activation of a predefined PCC rule, not known in the PCRF, may be done by the PCEF based on operator policy. The PCEF may only activate such predefined PCC rule if there are no UE provided traffic mapping information related to the IP‑CAN bearer. Further restrictions regarding the usage of predefined PCC rules are described in clause 6.3.1.
An active PCC rule means that:
- the service data flow template shall be used for service data flow detection;
- the service data flow template shall be used for mapping of downlink packets to the IP‑CAN bearer determined by the bearer binding;
- the service data flow template shall be used for service data flow detection of uplink packets on the IP‑CAN bearer determined by the bearer binding;
- usage data for the service data flow shall be recorded (further details can be found in clause 6.1.2 Reporting and clause 6.1.3 Credit Management);
- policies associated with the PCC rule, if any, shall be invoked.
- for service data flow detection with an application detection filter, the start or the stop of the application traffic is reported to the PCRF, if applicable and requested by the PCRF. In that case, the notification for Start may include service data flow filters, (if possible to provide) and the application instance identifier associated with the service data flow filters.
A predefined PCC rule is known at least, within the scope of one access point.
NOTE 1: The same predefined PCC rule can be activated for multiple IP‑CAN bearers in multiple IP‑CAN sessions.
A predefined PCC rule is bound to one and only one IP-CAN bearer per IP‑CAN session. For a predefined PCC rule whose service data flow cannot be fully reflected for the uplink direction in terms of traffic mapping information sent to the UE, the PCEF may apply the uplink service data flow detection at additional IP‑CAN bearers with non-GBR QCI of the same IP‑CAN session. The deactivation of such a predefined PCC rule ceases its service data flow detection for the whole IP‑CAN session.
The PCRF may, at any time, modify an active, dynamic PCC rule.
The PCRF may, at any time, deactivate an active PCC rule in the PCEF via the Gx reference point. At IP‑CAN bearer termination all active PCC rules on that bearer are deactivated without explicit instructions from the PCRF to do so.
Policy and charging control rule operations can be also performed in a deferred mode. A PCC rule may have either a single deferred activation time, or a single deferred deactivation time or both.
A PCC rule with only a deferred activation time shall be inactive until that time. A PCC rule with only a deferred deactivation time shall be active until that time. When the rule activation time occurs prior to the rule deactivation time, the rule is inactive until the activation and remains active until the deactivation time occurs. When the rule deactivation time occurs prior to the rule activation time, the rule is initially active until the deactivation time, then remains inactive until the activation time and then becomes active again. An inactive PCC rule, that has not been activated yet, is still considered to be installed and may be removed by the PCRF.
The PCRF may modify a currently installed PCC rule, including setting, modifying or clearing its deferred activation and/or deactivation time. When modifying a dynamic PCC rule with a prior and/or new deferred activation and/or deactivation time, the PCRF shall provide all attributes of that rule, including attributes that have not changed.
NOTE 2: In this case, the PCRF omission of an attribute that has a prior value will erase that attribute from the rule.
Deferred activation and deactivation of PCC rules can only be used for PCC rules that belong to the IP‑CAN bearer without traffic mapping information.
NOTE 3: This limitation prevents dependencies on the signalling of changed traffic mapping information towards the UE.
Deferred modification of PCC rules shall not be applied for changes of the QoS or service data flow filter information of PCC rules. |
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 PCEF and BBERF (if applicable) using the PCC rule and QoS rule (if applicable) provision procedure. The IP‑CAN bearer related policy information may be provided together with rules or separately.
Table 6.4 lists the PCC related IP‑CAN bearer and IP‑CAN session related policy information.
Table 6.4: PCC related IP‑CAN bearer and IP‑CAN session related policy information
Attribute
Description
PCRF permitted to modify the attribute
Scope
Charging information
(NOTE 2)
Defines the containing OFCS and/or OCS addresses.
No
IP‑CAN session
Default charging method
(NOTE 2)
Defines the default charging method for the IP‑CAN session.
No
IP‑CAN session
Event trigger
Defines the event(s) that shall cause a re-request of PCC rules for the IP‑CAN bearer.
Yes
IP‑CAN session
Authorized QoS per bearer (UE-initiated IP‑CAN bearer activation/modification)
(NOTE 1)
Defines the authorised QoS for the IP‑CAN bearer (QCI, GBR, MBR).
Yes
IP‑CAN bearer
Authorized MBR per QCI (network initiated IP‑CAN bearer activation/modification)
(NOTE 1)
(NOTE 3)
Defines the authorised MBR per QCI.
Yes
IP‑CAN session
Revalidation time limit
Defines the time period within which the PCEF shall perform a PCC rules request.
Yes
IP‑CAN session
PRA Identifier(s)
Defines the Presence Reporting Area(s) to monitor for the UE with respect to entering/leaving
Yes
IP-CAN session
List(s) of Presence Reporting Area elements (NOTE 4)
Defines the elements of the Presence Reporting Area(s)
Yes
IP-CAN session
Default NBIFOM access
The access to be used for all traffic that does not match any existing Routing Rule
Yes (only at the addition of an access to the IP-CAN session)
IP-CAN session
NOTE 1: Depending on the bearer establishment mode; only one Authorized QoS information has to be used.
NOTE 2: These attributes should not be provided to BBERF.
NOTE 3: This attribute is only applicable when the IP‑CAN supports non-GBR bearers that have a separate MBR (e.g. for GPRS).
NOTE 4: The list of PRA elements shall be a short list of elements.
Upon the initial interaction with the PCEF, the PCRF may provide Charging information containing OFCS and/or OCS addresses to the PCEF defining the offline and online charging system addresses respectively. These shall override any possible predefined addresses at the PCEF. If received by the PCEF, it supersedes the Primary OFCS/OCS address and Secondary OFCS/OCS address in the charging characteristics profile.
Upon the initial interaction with the PCEF, the PCRF may provide Default charging method indicating what charging method shall be used in the IP‑CAN session for every PCC rule where the charging method identifier is omitted, including predefined PCC rules that are activated by the PCEF. If received by the PCEF, it supersedes the Default charging method in the charging characteristics profile.
Upon every interaction with the ERF, the PCRF may provide event triggers for the IP‑CAN session. Event triggers are used to determine which IP‑CAN bearer modification causes the ERF to re-request PCC rules. The triggers are listed in clause 6.1.4.
The semantics of the authorized QoS per bearer (UE-initiated IP‑CAN bearer activation/modification) and the authorized MBR per QCI (network initiated IP‑CAN bearer activation/modification) are captured in clause 6.2.2.4.
The Revalidation time limit defines the time period within which the PCEF shall trigger a request for PCC rules for an established IP‑CAN session.
Upon every interaction with the PCEF, the PCRF and the OCS may activate / deactivate reporting changes of UE presence in Presence Reporting Area by setting / unsetting the corresponding event trigger or credit reauthorization trigger by providing the PRA Identifier(s) and additionally the list(s) of elements comprising the Presence Reporting Area for UE-dedicated Presence Reporting Area(s), as described in clauses 6.1.4 and 6.1.3, respectively.
The PCEF shall combine the requests from PCRF and the OCS.
When the Change of UE presence in Presence Reporting Area is armed, i.e. when the PCRF or the OCS subscribes to reporting change of UE presence in a particular Presence Reporting Area and the reporting change of UE presence in this Presence Reporting Area was not activated before, the PCEF shall activate the relevant IP‑CAN specific procedure which reports when the UE enters or leaves a Presence Reporting Area (an initial report is received when the IP‑CAN specific procedure is activated). The PCEF reports the PRA Identifier(s) and indication(s) whether the UE is inside or outside the Presence Reporting Area(s) and indication(s) if the corresponding Presence Reporting Area(s) is set to inactive by the serving node to the PCRF and/or the OCS.
NOTE: The serving node can activate the reporting for the PRAs which are inactive as described in the TS 23.401 [17].
When neither the PCRF nor the OCS are subscribed to change of UE presence in Presence Reporting Area for a particular Presence Reporting Area, the PCEF shall deactivate the relevant IP‑CAN specific procedure which reports when the UE enters or leaves a Presence Reporting Area.
The PCEF stores PCRF or OCS subscription to reporting for changes of UE presence in Presence Reporting Area and forwards the PRA Identifier(s) and indication(s) whether the UE is inside or outside the Presence Reporting Area(s) received from the serving node according to the corresponding subscription.
When a PRA set identified by a PRA Identifier was subscribed to report changes of UE presence in Presence Reporting Area by the PCRF and/or OCS, the PCEF additionally receives the PRA Identifier of the PRA set from the serving node, along with the individual PRA Identifier(s) belonging to the PRA set and indication(s) of whether the UE is inside or outside the individual Presence Reporting Area(s), as described in TS 23.401 [17].
6.4a TDF session related policy information
The purpose of the TDF session related information is to provide information that is applicable to the whole TDF session. The PCRF provides the TDF session related information to the TDF (if applicable) using ADC rule provision procedure.
Table 6.4a lists the TDF session related policy information.
Table 6.4a: TDF session related policy information
Attribute
Description
PCRF permitted to modify the attribute
Charging Characteristics
Defines how to control TDF behaviour regarding online and offline charging.
No
Charging information
Defines the containing OFCS and/or OCS addresses.
No
Default charging method
Defines the default charging method for the TDF session.
No
Event trigger
Defines the event(s) that shall cause a re-request of ADC rules for the TDF session.
Yes
Maximum downlink bit rate
Defines the maximum downlink bit rate per TDF session.
Yes
Maximum uplink bit rate
Defines the maximum uplink bit rate per TDF session.
Yes
ADC Revalidation time limit
Defines the time period within which the TDF shall perform an ADC rules request.
Yes
Upon the initial interaction with the TDF, the PCRF may provide Charging Characteristics to the TDF, if received from the PCEF, defining how to control TDF behaviour regarding online and offline charging.
Upon the initial interaction with the TDF, the PCRF may provide Charging information containing OFCS and/or OCS addresses to the TDF defining the offline and online charging system addresses respectively. These shall override any possible predefined addresses at the TDF. If received by the TDF, it supersedes the Primary OFCS/OCS address and Secondary OFCS/OCS address predefined at the TDF.
Upon the initial interaction with the TDF, the PCRF may provide Default charging method indicating what charging method shall be used in the TDF session for every ADC rule where the charging method identifier is omitted. If received by the TDF, it supersedes the defined Default charging method.
If Charging Characteristics are received by the PCRF from the PCEF, the PCRF may take them into account when providing Charging information and Default charging method to the TDF. In case the TDF receives both Charging Characteristics and Charging information and Default charging method parameters, the Charging Information and Default charging method shall supersede the values received in Charging Characteristics.
Upon every interaction with the TDF, the PCRF may provide Maximum downlink bit rate and/or Maximum uplink bit rate for the TDF session.
NOTE: To avoid down-link packets being discarded in PCEF when TDF performs charging, the PCRF should set the Maximum downlink bit rate to the DL APN-AMBR.
Upon every interaction with the TDF, the PCRF may provide event triggers for the TDF session. Event triggers are used to determine which event causes the TDF to re-request ADC rules. The triggers applicable for the TDF are listed in clause 6.1.4.
The ADC Revalidation time limit defines the time period within which the TDF shall trigger a request for ADC rules for an established TDF session.
6.4b APN related policy information
The purpose of the APN related policy information is to provide policy and charging control related information that is applicable to all IP‑CAN sessions of a UE to the same APN. The PCRF provides APN related policy information to the PCEF using the PCC provision procedure together with PCC rules or separately.
Table 6.4b-1 lists the applicable PCC specific APN related policy information.
Table 6.4b-1: PCC specific APN related policy information
Attribute
Description
PCRF permitted to modify the attribute
Scope
Authorized APN-AMBR
Defines the APN-AMBR for the total bandwidth usage of non-GBR QCI traffic at the APN.
Yes
All IP‑CAN sessions for the same UE within the same APN
Subsequent APN-AMBR (NOTE 1)
Defines the APN-AMBR for the total bandwidth usage of non-GBR QCI traffic at the APN to be applied by the PCEF when the APN-AMBR change time is reached.
No
(NOTE 2)
All IP‑CAN sessions for the same UE within the same APN
APN-AMBR change time (NOTE 1)
Defines the time at which the PCEF shall apply the Subsequent APN-AMBR for the total bandwidth usage of non-GBR QCI traffic at the APN.
No
(NOTE 2)
All IP‑CAN sessions for the same UE within the same APN
NOTE 1: Both parameters shall be provided together. The PCRF may provide up to four instances of them. If multiple instances are provided, the values of the APN-AMBR change time have to be different and should not be too close to each other in order to reduce the risk for signalling overload.
NOTE 2: The PCRF may replace all instances that have been provided previously with a new instruction. A previously provided Subsequent APN-AMBR or APN-AMBR change time cannot be individually modified.
The PCRF may provide the (unconditional) Authorized APN-AMBR in every interaction with the PCEF. The PCEF shall apply the Authorized APN-AMBR as APN-AMBR for all IP‑CAN sessions of the UE to the same APN and shall communicate the changed APN-AMBR to the UE.
NOTE 1: There is always an unconditional value for the APN-AM BR available at the PCEF. The initial value is received as Subscribed APN-AMBR in an access specific manner and the PCRF can overwrite it by providing an Authorized APN-AMBR.
NOTE 2: In order to reduce the risk for signalling overload, the PCRF should avoid simultaneous provisioning of Authorized APN-AMBR for many UEs (e.g. by spreading over time).
The Authorized APN-AMBR may be provided together with conditions, i.e. a list of RAT types and/or a list of IP-CAN types. One or multiple instances of conditional APN-AMBR, with different conditions, may be provided by the PCRF. The PCEF shall apply a conditional Authorized APN-AMBR as APN-AMBR only if the current RAT type and IP-CAN type match one of the RAT types and IP-CAN types specified in the conditions, respectively. Otherwise the PCEF shall apply the unconditional Authorized APN-AMBR as APN-AMBR. A changed APN-AMBR shall be communicated to the UE.
NOTE 3: Guidance what conditional Authorized APN-AMBR value to use in case the current RAT type and IP-CAN type match multiple conditional Authorized APN-AMBRs is specified in stage 3.
Conditional Authorized APN-AMBR(s) are not applied for a PDN connection supporting NBIFOM.
Upon PCRF changing the unconditional Authorized APN-AMBR or providing a conditional Authorized APN-AMBR, the PCEF shall discard any previously received conditional Authorized APN-AMBR.
The PCRF may provide the unconditional and/or one or multiple instances of conditional Authorized APN-AMBR together with an APN-AMBR change time, referred to as Subsequent APN-AMBR. When the APN-AMBR change time is reached, the PCEF shall apply the unconditional and/or conditional Subsequent APN-AMBR as unconditional and/or conditional Authorized APN-AMBR and discard any previously applied conditional Authorized APN-AMBRs.
NOTE 4: The modification is made in the same way as if the PCRF had modified the Authorized APN-AMBR at that point in time.
Up to four instances of Subsequent APN-AMBR may be provided by the PCRF. The PCEF shall discard any previously received Subsequent APN-AMBR instances on explicit instruction as well as whenever the PCRF provides a new instruction for one or more subsequent changes to the APN-AMBR or any other subsequent parameter.
NOTE 5: In order to provide further Subsequent APN-AMBRs in a timely fashion the PCRF can use its own clock to issue the desired changes or use the Revalidation time limit parameter (clause 6.4) to trigger a PCEF request for a policy decision. |
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 supports service data flow templates consisting of a set of service data flow filters.
The PCRF shall ensure that each PCC rule in the PCEF has a corresponding active QoS rule in the BBERF. The QoS rule shall contain the same service data flow template, precedence and the QoS information as the corresponding PCC rule.
NOTE 2: During the course of a BBERF change procedure the BBERF might not be able to maintain the correspondence throughout the procedure. The post-condition for the procedure shall however be that corresponding PCC and QoS rules are active at the PCEF and BBERF.
There are defined procedures for activation, modification and deactivation of QoS rules (as described in clause 6.5.2). The PCRF may activate, modify and deactivate a QoS rule over the Gxx reference point.
The QoS rules are derived from the PCC rules.
Table 6.5 lists the information contained in a QoS rule, including the information name and whether the PCRF may modify this information in a QoS rule which is active in the BBERF. For the IE description, refer to clause 6.3.1. The Category field indicates if a certain piece of information is mandatory or not for the construction of a QoS rule, i.e. if it is possible to construct a QoS rule without it.
Table 6.5: The QoS rule information
Information name
Category
PCRF permitted to modify for an active QoS rule in the BBERF
Rule identifier
(NOTE 1)
Mandatory
No
Service data flow detection
Precedence
Mandatory
Yes
Service data flow template
Mandatory
Yes
QoS control
QoS class identifier
(NOTE 2)
Mandatory
Yes
UL-maximum bitrate
Conditional
(NOTE 3)
Yes
DL-maximum bitrate
Conditional
(NOTE 3)
Yes
UL-guaranteed bitrate
Conditional
(NOTE 3)
Yes
DL-guaranteed bitrate
Conditional
(NOTE 3)
Yes
UL sharing indication
No
DL sharing indication
No
ARP
Conditional
(NOTE 3)
Yes
PS to CS session continuity
Conditional
No
Access Network Information Reporting
User Location Report
Conditional
Yes
UE Timezone Report
Conditional
Yes
NOTE 1: The Rule-Identifier uniquely defines an active QoS rule for a certain BBERF within the scope of a UE.
NOTE 2: The QoS class identifier is scalar and accommodates the need for differentiating QoS in all types of IP‑CAN. The value range is expandable to accommodate operator specific policies.
NOTE 3: If present in the corresponding PCC rule. |
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;
- the service data flow template shall be used for mapping of downlink packets to the IP‑CAN bearer determined by the bearer binding;
- the service data flow template shall be used for service data flow detection of uplink packets on the IP‑CAN bearer determined by the bearer binding;
- QoS procedures associated with the QoS rule, if any, shall be invoked.
The PCRF may, at any time, modify an active QoS rule.
The PCRF may, at any time, deactivate an active QoS rule in the BBERF via the Gxx reference point. At IP‑CAN bearer termination all active QoS rules on that bearer are deactivated without explicit instructions from the PCRF to do so. |
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
Description
Category
Scope
Monitoring key
The PCRF uses the monitoring key to group services that share a common allowed usage.
Mandatory
IP-CAN session,
TDF session
Volume threshold
(NOTE 1)
Defines the traffic volume value after which the PCEF or the TDF shall report usage to the PCRF for this monitoring key.
Optional
Monitoring key
Time threshold
(NOTE 1)
Defines the resource time usage after which the PCEF or the TDF shall report usage to the PCRF.
Optional
Monitoring key
Monitoring time
Defines the time at which the PCEF or the TDF shall reapply the Volume and/or Time Threshold.
Optional
Monitoring Key
Subsequent Volume threshold
Defines the traffic volume value after which the PCEF or the TDF shall report usage to the PCRF for this Monitoring key for the period after the Monitoring time.
Optional, Conditional
(NOTE 2)
Monitoring Key
Subsequent Time threshold
Defines resource time usage after which the PCEF or the TDF shall report usage to the PCRF for this Monitoring key for the period after the Monitoring time.
Optional, Conditional
(NOTE 2)
Monitoring Key
Inactivity Detection Time
Defines the period of time after which the time measurement shall stop, if no packets are received.
Optional, Conditional
(NOTE 3)
Monitoring Key
NOTE 1: This attribute is also used by the PCEF/TDF, e.g. during IP-CAN/TDF session termination, to inform the PCRF about the resources that have been consumed by the UE.
NOTE 2: This attribute is applicable in presence of Monitoring Time only.
NOTE 3: This attribute is applicable in presence of Time threshold only.
The Monitoring Key is the reference to a resource threshold. Any number of PCC/ADC Rules may share the same monitoring key value. The monitoring key values for each service shall be operator configurable.
It shall also be possible for an operator to use the Monitoring Key parameter to indicate usage monitoring on an IP‑CAN session level at the PCEF or on a TDF session level at the TDF.
The Volume threshold indicates the overall user traffic volume value after which the PCEF or the TDF shall report the Usage threshold reached trigger to the PCRF.
The Time threshold indicates the overall resource time usage after which the PCEF or the TDF shall report the Usage threshold reached trigger to the PCRF.
The Monitoring time indicates the time at which the PCEF or the TDF shall store the accumulated usage information.
The Subsequent Volume threshold indicates the overall user traffic volume value measured after Monitoring time, after which the PCEF or the TDF shall report the Usage threshold reached trigger to the PCRF.
The Subsequent Time threshold indicates the overall resource time usage measured after Monitoring time, after which the PCEF or the TDF shall report the Usage threshold reached trigger to the PCRF.
The Inactivity Detection Time indicates the period of time after which the time measurement shall stop, if no packets are received during that time period. |
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 value for the IP‑CAN session has been provided.
- For TDF session level monitoring at the TDF, a TDF session is active and a volume and/or time threshold value has been provided.
For usage monitoring on Monitoring key level at the PCEF or the TDF the following conditions are applicable:
- A volume and/or time threshold has been provided for a Monitoring key to the PCEF and there is at least one PCC rule activated for the IP-CAN session that is associated with that Monitoring key.
- A volume and/or time threshold has been provided for a Monitoring key to the TDF and there is at least one ADC rule at the TDF activated for the TDF session that is associated with that Monitoring key.
NOTE: The PCRF is recommended to use monitoring so that the same traffic is not monitored by both PCC rules and ADC rules. This avoids double counting. |
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 contained in the IP flow mobility routing rule to the applicable BBERF for each PCC/QoS rule. The IP flow mobility routing rules are provided by the PCEF to the PCRF during IP‑CAN session establishment or modification.
The PCEF derives IP flow mobility routing rules based on flow binding information received from the UE as described in TS 23.261 [23].
Table 6.7 lists the information contained in a routing rule, including the information name, the description and whether the PCEF may modify this information in an updated version of the rule. The Category field indicates if a certain piece of information is mandatory or not.
Table 6.7: The routing rule information
Information name
Description
Category
PCEF permitted to modify in an update
Rule identifier
Uniquely identifies the routing rule within an IP‑CAN session. It is assigned by the PCEF.
Mandatory
No
Routing information
This clause defines the method for detecting packets belonging to a flow and the route for the flow.
Precedence
Determines the order, in which the routing filters are applied.
Mandatory
Yes
Packet filter
A list of packet filters for the detection of IP flows.
Mandatory
Yes
IP flow mobility Routing Address
The IP flow mobility Routing Address that the matching IP flows use.
Mandatory
Yes
The Rule identifier shall be unique for a routing rule within an IP-CAN session. It is assigned by the PCEF.
The Precedence defines in what order the routing rules is used by the PCRF to determine where to route a service data flow. The Precedence is derived from the priority included in the Binding Update as specified in TS 23.261 [23].
The Packet filter may comprise any number of packet filters, containing information for matching service data flows. The format of the packet filters is the same as the service data flow filter described in clause 6.2.2.2. A default packet filter can be specified by using wild card filter.
The IP flow mobility Routing Address identifies the IP address to be used for all service data flows matching the packet filters specified for this routing rule. The IP flow mobility Routing Address can be equal to the care-of address, or to the UE IP address (home address) in case of home link operations. |
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 BBERF for any service data flow related for that IP-CAN Session.
The PCEF may, at any time, modify or remove an installed routing rule based on updated flow binding information received from the UE as described in TS 23.261 [23]. |
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 application traffic detected by the rule.
ADC rules are applicable over the Sd reference point. Over the Sd reference point, the ADC rules are used to support application detection and control as defined in clause 4.5 including traffic steering control as defined in clause 4.8.
ADC Rules are also applicable over the St reference point. Over the St reference point, the ADC rules are used to transfer traffic steering control information as defined in clause 6.11.1.
ADC rules definitions are assumed to be directly provisioned into the TDF or TSSF and referenced by the PCRF with the ADC Rule identifier.
NOTE 1: The method to perform the detection, in particular for the Start and Stop, may extend beyond the IP header and is out of scope for this document.
Two types of ADC rules exist: Predefined and dynamic ADC rules. A predefined ADC rule is constant and shall not be changed. For a dynamic ADC rule, some parameters can be provided and modified by the PCRF as defined in Table 6.8.
There are defined procedures for activation, modification and deactivation of ADC rules (as described in clause 6.8.2). The PCRF may activate, modify and deactivate an ADC rule at any time. The modification procedure is applicable to dynamic ADC rules only.
The operator defines the ADC rules.
Table 6.8 lists the information contained in an ADC rule that can be exchanged over the Sd and St reference point, including the information element name, the description, whether the PCRF may modify this information in a dynamic ADC rule which is active in the TDF and the applicable reference point (i.e. Sd and/or St) for the corresponding information element. The Category field indicates if a certain piece of information is mandatory or not for the construction of an ADC rule, i.e. if it is possible to construct an ADC rule without it.
Table 6.8: The Application Detection and Control rule information
Information name
Description
Category
PCRF permitted to modify for a dynamic ADC rule
Applicable reference point
ADC Rule identifier
Uniquely identifies the ADC rule within a TDF/TSSF session.
It is used between PCRF and TDF/TSSF for referencing ADC rules.
Mandatory
No
Sd, St
Application detection
This clause defines the detection and the application name.
Sd, St
Precedence
For ADC, the precedence is only relevant for the enforcement, i.e. when multiple ADC rules overlap, only the enforcement, reporting of application starts and stops, monitoring and charging actions of the ADC rule with the highest precedence shall be applied.
Optional
Yes
Sd, St
Application identifier
(NOTE 2)
References the corresponding application detection filter for the detection of the service data flow. References the corresponding application, for which the rule applies.
Conditional
(NOTE 5)
No
Sd, St
Service data flow filter list
A list of service data flow filters for the detection of the traffic.
Conditional
(NOTE 5)
No
Sd, St
Mute for notification
Defines whether application's start or stop notification is to be muted.
Optional
No
Sd
Usage Monitoring Control
This clause describes identities required for Usage Monitoring Control.
Sd
Monitoring key
The PCRF uses the monitoring key to group applications that share a common allowed usage.
Optional
Yes
Sd
Indication of exclusion from session level monitoring
Indicates that the application shall be excluded from the TDF session usage monitoring.
Optional
Yes
Sd
Enforcement control
This clause defines how the TDF shall apply enforcement actions for the detected application traffic.
Sd
Gate status
The gate status indicates whether the detected application may pass (Gate is open) or shall be discarded (Gate is closed) at the TDF.
Optional
Yes
Sd
UL-maximum bit rate
The uplink maximum bit rate authorized for the application traffic
Optional
Yes
Sd
DL-maximum bit rate
The downlink maximum bit rate authorized for the application traffic
Optional
Yes
Sd
Redirect
Redirect state of detected application traffic (enabled/disabled)
Optional
Yes
Sd
Redirect Destination
Controlled Address to which detected application traffic should be redirected when redirect is enabled
Conditional
(NOTE 1)
Yes
Sd
DSCP value
Downlink packets of detected application traffic shall be marked with this DSCP value.
Optional
(NOTE 4)
Yes
Sd
Charging
This clause defines identities and instructions for charging and accounting that is required for an access point where application usage charging is configured
Sd
Charging key
The charging system (OCS or OFCS) uses the charging key to determine the tariff to apply for the application.
Optional
Yes
Sd
Service identifier
Identifies one or more applications to the charging system.
Optional
Yes
Sd
Sponsor Identifier
An identifier, provided from the AF which identifies the Sponsor, used for sponsored flows to correlate measurements from different users for accounting purposes.
Conditional
(NOTE 7)
Yes
Application Service Provider Identifier
An identifier, provided from the AF which identifies the Application Service Provider, used for sponsored flows to correlate measurements from different users for accounting purposes.
Conditional
(NOTE 7)
Yes
Sd
Charging method
Indicates the required charging method for the ADC rule.
Values: online, offline or neither.
Conditional
(NOTE 3)
No
Sd
Measurement method
Indicates whether the application data volume, duration, combined volume/duration or event shall be measured.
This is applicable for reporting, if the charging method is online or offline.
Optional
Yes
Sd
Service identifier level reporting
Indicates that separate usage reports shall be generated for this Service identifier.
Values: mandated or not required.
Optional
Yes
Sd
Traffic Steering Enforcement Control
This part describes identities required for Traffic Steering Enforcement Control.
Sd, St
Traffic steering policy identifier(s)
Reference to a pre-configured traffic steering policy at the TDF/TSSF (NOTE 6).
Optional
Yes
Sd, St
NOTE 1: If Redirect is enabled.
NOTE 2: For every ADC rule this information is pre-configured in the TDF.
NOTE 3: Mandatory if there is no default charging method for the TDF session. It is possible to activate both online and offline charging for the same ADC Rule.
NOTE 4: See Annex U for details regarding how to apply policy and charging control for an application detected and marked by the TDF in the downlink direction (typically application with non-deducible service data flows).
NOTE 5: Either Application identifier or Service data flow filter list shall be included.
NOTE 6: The Traffic steering policy identifier can be different for uplink and downlink direction. If two Traffic steering policy identifiers are provided, then one is for uplink direction, while the other one is for downlink direction.
NOTE 7: Applicable to sponsored data connectivity.
The ADC Rule identifier shall be unique for an ADC rule within a TDF/TSSF session.
NOTE 2: The PCRF has to ensure that there is no dynamically provided ADC rule that has the same Rule identifier value as any of the predefined ADC rules.
The Precedence defines, if multiple ADC rules overlap, which ADC Rule shall be applied for the purpose of enforcement, reporting of application start and stop, monitoring and charging. When a dynamic ADC rule and a predefined ADC rule have the same precedence, the dynamic ADC rule takes precedence. For dynamic ADC rules, the Precedence shall be either preconfigured at the TDF/TSSF or provided dynamically by the PCRF within the ADC Rules.
NOTE 3: The operator shall ensure that overlap between the predefined ADC rules can be resolved based on precedence of each predefined ADC rule in the TDF. For dynamic ADC rules, if precedence is not preconfigured in the TDF, the PCRF shall ensure that overlap between the dynamic ADC rules can be resolved based on precedence of each dynamic ADC rule.
The Application identifier references the corresponding application detection filter that is used for matching user plane packets. It is also used for identifying the application, for which the rule applies, during reporting to the PCRF. The same application identifier value can occur in more than one ADC rule. If so, the PCRF shall ensure that there is at most one ADC rule active per application identifier value at any time.
NOTE 4: The same application identifier value could be used for a dynamic ADC rule and a predefined ADC rule or for multiple predefined ADC rules.
NOTE 5: The configuration of the Application Identifier in the TDF can include the set of information required for encrypted traffic detection as defined in Annex X.
Instead of Application identifier, the Service data flow filter list may be provided which comprises one or more Service data flow filters and is used by the TDF or TSSF to identify the packets belonging to a detected traffic. The format of the Service data flow filter is described in clause 6.2.2.2, except the filters extending the inspection to look further into the packet and/or define other operations as those are identified by Application Identifier.
The Mute for notification defines whether notification of application's start or stop shall be muted to the PCRF. Absence of this parameter means that start/stop notifications shall be sent.
The Monitoring Key is the reference to a resource threshold. Any number of ADC Rules may share the same monitoring key value. The monitoring key values for each application shall be operator configurable.
The Indication of exclusion from session level monitoring indicates that the application shall be excluded from the TDF session usage monitoring.
The Gate status indicates whether the TDF shall let detected application traffic pass through (gate is open) the TDF or the TDF shall discard (gate is closed) the application traffic.
The UL maximum-bitrate indicates the authorized maximum bitrate for the uplink component of the detected application traffic.
The DL maximum-bitrate indicates the authorized maximum bitrate for the downlink component of the detected application traffic.
NOTE 6: The maximum bit rate is an average value, which is measured over some time period. Services may generate media with variable bitrate. The policing function should take such bitrate variations into account.
The Redirect indicates whether the uplink part of the detected application traffic should be redirected to a controlled address.
The Redirect Destination indicates the target redirect address when Redirect is enabled.
The DSCP value indicates the value with which a TDF marks downlink application traffic identified by an ADC rule.
The Charging key is the reference to the tariff for the application. Any number of ADC Rules may share the same charging key value. The charging key values for each application shall be operator configurable.
NOTE 7: Assigning the same Charging key for several applications implies that the charging does not require the credit management to be handled separately.
The Service identifier identifies one or more applications to the charging system. ADC Rules may share the same Service identifier value. The service identifier provides the most detailed identification specified for application based charging.
NOTE 8: The Service Identifier need not have any relationship to service identifiers used on the AF level, i.e. is an operator policy option.
The Sponsor Identifier indicates the (3rd) party organization willing to pay for the operator's charge for connectivity required to deliver a service to the end user.
The Application Service Provider Identifier indicates the (3rd) party organization delivering a service to the end user.
The Charging method indicates whether online charging, offline charging, or both are required or the application is not subject to any end user charging. If the charging method identifies that the application is not subject to any end user charging, a Charging key shall not be included in the ADC rule for that application, along with other charging related parameters. If the charging method is omitted, the TDF shall apply the default charging method as determined at TDF session establishment (see clause 6.4a). The Charging method is mandatory if there is no default charging method for the TDF session.
The Measurement method indicates what measurements apply for charging for ADC rule.
The Service Identifier Level Reporting indicates whether the TDF shall generate reports per Service Identifier. The TDF shall accumulate the measurements from all ADC rules with the same combination of Charging key/Service Identifier values in a single report.
The Traffic Steering Policy Identifier(s) is a reference to a pre-configured traffic steering policy at the TDF/TSSF as defined in clause 6.11.1. |
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 ADC rule means that:
- The application traffic, matching the corresponding application, can be detected; and
- Start or stop of application traffic is reported to the PCRF, if applicable and requested by the PCRF; the notification for Start may include service data flow filters, if possible to provide; and the application instance identifier associated with the service data flow filter; and
- Monitoring and enforcement, as specified within the rule, is applied.
The PCRF may, at any time, modify an active, dynamic ADC rule.
The PCRF may, at any time, deactivate an active ADC rule. The TDF session termination shall deactivate all ADC rules for that IP‑CAN session.
Application Detection and Control rule activation/deactivation operations can also be performed in a deferred mode. An ADC rule may have either a single deferred activation time, or a single deferred deactivation time or both.
An ADC rule with only a deferred activation time shall be inactive until that time. An ADC rule with only a deferred deactivation time shall be active until that time. When the rule activation time occurs prior to the rule deactivation time, the rule is inactive until the activation and remains active until the deactivation time occurs. When the rule deactivation time occurs prior to the rule activation time, the rule is initially active until the deactivation time, then remains inactive until the activation time and then becomes active again. An inactive ADC rule, that has not been activated yet, is still considered to be installed and may be removed by the PCRF.
The PCRF may modify a currently installed dynamic ADC rule, including setting, modifying or clearing its deferred activation and/or deactivation time.
When modifying a dynamic ADC rule with a prior and/or new deferred activation and/or deactivation time, the PCRF shall provide all attributes of that rule, including attributes that have not changed.
NOTE: In this case, the PCRF omission of an attribute that has a prior value will erase that attribute from the rule. |
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 with the actions associated with the policy counter status that is received from OCS.
The PCRF may request the status of policy counters in the OCS using the Initial or Intermediate Spending Limit Report Request Procedure. The OCS provides the current status of the requested policy counters to the PCRF. The OCS may in addition provide one or more pending statuses for a requested policy counter together with the time they have to be applied. The PCRF shall immediately apply the current status of a policy counter. A pending status of a policy counter shall autonomously become the current status of a policy counter at the PCRF when the indicated corresponding time is reached. Subsequently provided information for pending statuses of a policy counter shall overwrite the previously received information.
The PCRF may subscribe to spending limit reporting for policy counters from the OCS using the Initial or Intermediate Spending Limit Report Request procedure. If spending limit reporting for a policy counter is enabled, the OCS shall notify the PCRF of changes in the status of this policy counter (e.g. daily spending limit of $2 reached) and optionally pending statuses of this policy counter together with their activation time (e.g. due to a billing period that will expire at midnight). The PCRF may cancel spending limit reporting for specific policy counter(s) using the Intermediate Spending Limit Report Request procedure, or for all policy counter(s) using the Final Spending Limit Report Request procedure.
The PCRF uses the status of each relevant policy counter and optional pending policy counter statuses if known, as input to its policy decision to apply operator defined actions, e.g. change the QoS (e.g. downgrade APN-AMBR), modify the PCC/QoS/ADC Rules to apply gating or change charging conditions.
NOTE: The relationship between a policy counter identifier and the Charging Key could be 1-1. However it could also be assumed that services that share the same Charging Key can be associated with different policy counters i.e. although they are rated in the same way they are subject to different actions regarding (e.g. QoS and gating) and are therefore counted separately. Likewise services that share the same policy counters can be associated with different Charging Key. |
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 ADC rules over Sd reference point;
- From the PCRF to the TSSF within ADC rules over St reference point.
NOTE 1: In this release of the specification, traffic steering control information does not contain the IP-CAN specific parameters such as e.g. RAT type, which may be needed by the (S)Gi-LAN service functions.
Table 6.11 lists the components of traffic steering control information and their corresponding information names in PCC/ADC rule.
Table 6.11: Traffic steering control information
Component of traffic steering control information
Corresponding information name in ADC rule (NOTE 1)
Corresponding information name in PCC rule (NOTE 2)
Rule Name
ADC Rule Identifier
Rule identifier
Description of Traffic
Application Identifier
or Service data flow filter list
Service Data Flow Template
Traffic steering policy identifier(s) (NOTE 3)
Traffic steering policy identifier(s)
(NOTE 3)
Traffic steering policy identifier(s)
(NOTE 3)
Precedence
Precedence
Precedence
NOTE 1: The information definition refers to Table 6.8.
NOTE 2: The information definition refers to Table 6.3.
NOTE 3: The Traffic steering policy identifier can be different for uplink and downlink direction. If two Traffic steering policy identifiers are provided, then one is for uplink direction, while the other one is for downlink direction.
The Traffic Steering Policy Identifier is a reference to traffic steering policy locally configured at the PCEF/TDF/TSSF. The traffic steering policy identifies, explicitly or implicitly, a specific set of service functions and their order via which the traffic, identified by the description of traffic included in the traffic steering control information, needs to be steered in the (S)Gi-LAN.
For traffic steering control at the PCEF, the PCC Rule operations described in the clause 6.3.2 apply.
For traffic steering control at the TDF, the ADC Rule operations over Sd described in the clause 6.8.2 apply.
For traffic steering control at the TSSF, the Traffic Steering Control operations over St described in the clause 6.11.2 apply.
NOTE 2: In order for PCEF/TDF to measure the user plane traffic that is sent to a specific set of service functions, identified by a Traffic Steering Policy Identifier, a specific Charging Key or generic Charging Key and a specific Service Identifier is assigned to the PCC/ADC rule per each Traffic Steering Policy Identifier for which separate measurements are needed and the applicable measurement type as required. In case of Service Identifier usage, the PCC/ADC Rule also includes service identifier level reporting. |
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 filter list or the application identifier can be steered in the SGi-LAN according to the information associated with the traffic steering policy identifier. The PCRF provides the UE IP address and the associated APN when provisioning of traffic steering control information to the TSSF. The TSSF uses the APN to determine the PDN.
NOTE: The APN is provided from PCRF to the TSSF for the cases when the PCEF supports multiple APNs with overlapping IP addresses. In that case, the same UE IP address can be allocated to different UEs when they access different PDNs, each APN provides access to a different PDN.
When using ADC Rules, the following applies:
- For pre-defined ADC rules in TSSF, the PCRF provides the ADC Rule identifier(s) to the TSSF;
- For dynamic ADC Rules, the PCRF provides traffic steering control information within the ADC rules to the TSSF.
Modification: The PCRF may modify traffic steering control information to change the traffic steering policy identifier(s), the precedence, the service data flow filters or application identifier.
When using ADC Rules, the PCRF may modify a dynamic ADC rule.
Removal: The PCRF may, at any time, remove traffic steering control information.
When using ADC Rules, the PCRF may remove ADC Rule(s). |
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 from the UE (when UE-initiated NBIFOM mode applies) or based on requests from the UE to have the network create / modify / delete Routing Rules (when Network-initiated NBIFOM mode applies), as described in TS 23.161 [43].
Table 6.12 lists the information contained in an NBIFOM routing rule, including the information name, the description and whether the PCEF may modify this information in an updated version of the rule. The Category field indicates if a certain piece of information is mandatory or not.
Table 6.12: The NBIFOM routing rule information
Information name
Description
Category
PCEF permitted to modify in an update
Routing Rule identifier
Uniquely identifies the routing rule within an IP‑CAN session.
Mandatory
No
Routing information
This clause defines the method for detecting packets belonging to a flow and the route for the flow.
Routing Rule Priority
Determines the order, in which the routing filters are applied.
Mandatory
Yes
Routing Filter
A packet filter for the detection of IP flows.
Mandatory
Yes
Routing Access Information
The access type that the matching IP flows intend to use.
Mandatory
Yes
The Routing Rule identifier shall be unique for a NBIFOM routing rule within an IP-CAN session. It is set to the Routing Rule identifier assigned by the UE when UE-initiated NBIFOM mode applies as specified in TS 23.161 [43] or by the PCRF when Network-initiated NBIFOM mode applies.
The Routing Rule Priority defines in what order the NBIFOM routing rules are used by the PCRF to determine where to route a service data flow. The Routing Rule Priority is set according to the information provided by the UE as specified in TS 23.161 [43].
The Routing Filter comprises a single packet filter, containing information for matching IP flows. The format of the routing filter is the same as the service data flow filter described in clause 6.2.2.2. The Routing Filter is set according to the information provided by the UE as specified in TS 23.161 [43].
The Routing Access Information indicates the IP-CAN type that the IP flows matching the Routing Filter of this NBIFOM routing rule intend to use. |
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 it is so, the PCRF updates the Allowed Access Type in this PCC Rule according to the Routing Access Information. Otherwise a new PCC Rules is created with a service data flow filter equal to the Routing Filter, a precedence according to the Routing Rule Priority and the Allowed Access Type set to the Routing Access Information and then installed in the PCEF.
NOTE: If the Routing Filter is partially overlapping with a service data flow template of an installed PCC rule, it is up to the operator policy whether to reject the NBIFOM routing rule or whether to create a new PCC rule for this NBIFOM routing rule. In the latter case, this new PCC rule shall have the same parameters (except the rule name and the SDF template) and a higher precedence. The PCRF shall also ensure that relevant PCC rule modifications are applied for both PCC rules.
The PCRF shall store the relation between the Routing Rule identifier and the corresponding PCC rule. The PCRF may also reject a NBIFOM routing rule according to operator policy.
The modification of a NBIFOM routing rule to change the Routing Filter or the Routing Rule Priority triggers the PCRF to modify the service data flow filter or precedence in the corresponding installed PCC Rule accordingly.
The modification of a NBIFOM routing rule to change the Routing Access Information triggers the PCRF to change the Allowed Access Type in the corresponding installed PCC Rule accordingly.
The removal of a NBIFOM routing rule triggers the PCRF to remove the corresponding PCC Rule if the PCC rule creation was triggered by this NBIFOM routing rule. Otherwise, the PCRF removes only the Allowed Access Type in this PCC Rule. |
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 bearer establishment, modification, termination, as well as unsolicited PCC decisions.
There are three distinct network scenarios for an IP‑CAN Session:
Case 1: No Gateway Control Session is required, no Gateway Control Establishment occurs at all (e.g. 3GPP Access where GTP-based S5/S8 are employed, as described in TS 23.401 [17] and the IP‑CAN specific Annexes and non-3GPP accesses where GTP-based S2a or GTP-based S2b is employed, as described in TS 23.402 [18]).
Case 2: A Gateway Control Session is required. The BBERF establishes a Gateway Control Session prior to any IP‑CAN session establishment. There are two sub-cases:
2a) The UE acquires a care of address (CoA) that is used for the S2c reference point. The same Gateway Control session applies for all IP‑CAN sessions using that CoA.
2b) A Gateway Control Session is required, as described in TS 23.402 [18] and the IP‑CAN specific Annexes, Gateway Control Session Establishment, as defined in clause 7.7.1.
Each IP‑CAN session is handled in a separate Gateway Control Session.
The PCRF determines at Gx and Gxx session establishment what case applies initially as follows:
1. If the BBERF, at establishment of the Gateway Controls Session, provides an APN, then case 2b applies for the IP‑CAN session.
2. If the BBERF, at establishment of the Gateway Controls Session, does not provide any APN, then case 2a applies for the UE. For this case, the PCRF expects tunnelling header information for each IP‑CAN session to be provided by the applicable PCEF.
3. If there is no Gateway Control Session for the UE with the same IP‑CAN type as indicated over Gx, case 1 applies.
In a handover procedure the applicable case may change for an IP‑CAN session. The PCRF determines the new case in the same manner as described above. Details are defined in each such procedure.
The procedures cover non-roaming, roaming with home routed access and roaming with access to a visited PDN.
For the non-roaming case, the H‑PCRF plays the full role of PCRF. The V‑PCRF is not applicable in this case.
For the roaming case with home routed access, the H‑PCRF interacts with the PCEF and, if the Gxx applies, the V‑PCRF interacts with the BBERF.
For the roaming case with visited access (a.k.a. local breakout in TS 23.401 [17] and TS 23.402 [18]), the V‑PCRF interacts with the PCEF and, if Gxx applies, the BBERF and, if Sd applies, the TDF.
NOTE: The roaming scenario (figure 5.1-4) with visited access is not applicable for traffic steering control.
Procedures defined in this clause cover the traffic cases where the TDF is located on Gi/SGi interface.
Procedures defined in clause 7 cover all the traffic cases where roaming partners both operate PCC. For limited PCC deployment scenarios, Annex K and Annex L specify the impacts to these procedures.
In the text describing the steps in each sequence diagram, the designation PCRF, without specifying V‑ or H‑, refers to the PCRF in non-roaming case and refers to either the V‑PCRF or the H‑PCRF in the roaming cases. The interpretation of the text "PCRF" is thus dependent on the network scenario.
When NBIFOM (defined in TS 23.161 [43]) applies, the description of the flows in this clause 7 is complemented by the description of NBIFOM dedicated behaviours documented in clause 6.1.18. |
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 Session is used, the V-PCRF should proxy the Gateway Control Session Establishment information between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
For the Local Breakout scenario (Figure 5.1-4) the V-PCRF shall proxy the Indication and Acknowledge of IP‑CAN Session Establishment over S9 between the PCEF in the VPLMN and the H-PCRF. For TDF and solicited application reporting, the V-PCRF shall generate ADC rules from PCC Rules containing application detection and control information as instructed by the H-PCRF over S9. Then, the V-PCRF shall install PCC Rules to the PCEF and ADC Rules to the TDF, if applicable.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The BBERF initiates a Gateway Control Session Establishment procedure as defined in clause 7.7.1 (applicable to case 2a during initial attach and case 2b, as defined in clause 7.1).
2. The GW (PCEF) receives a request for IP‑CAN Bearer establishment. A PDN Connection Identifier may be included in the request. The GW (PCEF) accepts the request and assigns an IP address and (if requested) network prefix for the user.
3. The PCEF determines that the PCC authorization is required, requests the authorization of allowed service(s) and PCC Rules information. The PCEF includes the following information: UE Identity (e.g. MN NAI), a PDN identifier (e.g. APN), the IP‑CAN type and the IPv4 address and IPv6 network prefix, if available, the PDN Connection Identifier received for IP‑CAN Bearer establishment if multiple PDN connections to the same APN are supported and, if available, the default charging method and the IP‑CAN bearer establishment modes supported and information on whether PCEF is enhanced with ADC. It may also include the TDF IP address, in case of solicited application reporting, if applicable. If the UE has declared support for the extended TFT filter format and the PCEF does not prevent the use thereof, then the PCEF shall indicate that support to the PCRF. The PDN identifier, IP address(es) and UE identity enables identification of the IP‑CAN session. The IP‑CAN Type identifies the type of access from which the IP‑CAN session is established. If the service data flow is tunnelled at the BBERF, the PCEF shall provide information about the mobility protocol tunnelling encapsulation header. The PCEF may also include the Default Bearer QoS and APN-AMBR (applicable to case 1 and case 2a, as defined in clause 7.1). In case 2a the PCEF may also include charging ID information. If the GW/PCEF allocates a shorter IPv6 prefix for use with IPv6 Prefix Delegation, the GW/PCEF provides this shorter prefix as the IPv6 network prefix. If Charging Characteristics were received by GW/PCEF according to TS 23.401 [17] and TS 23.402 [18], the GW/PCEF also forwards Charging Characteristics to the PCRF. Based on local configuration the GW/PCEF may also include the following information: its control plane IPv4 and/or IPv6 address(es), an indication on how the APN was selected, indications on whether IP address(es) where statically or dynamically allocated and the charging identifier of the default bearer to identify different records belonging to the same PDN connection, indication on whether the charging identifier is the only one for the IP‑CAN session. When the PCEF has received the IMEI(SV) in the request for IP‑CAN Bearer establishment received at step 2, the PCEF shall transfer this information to the PCRF.
NOTE 1: In case of TDF and solicited application reporting, either PCEF informs PCRF with TDF IP address, or PCRF has it preconfigured per each one of PCEFs.
4. If the PCRF does not have the subscriber's subscription related information, it sends a request to the SPR in order to receive the information related to the IP‑CAN session. The PCRF provides the subscriber ID and, if applicable, the PDN identifier to the SPR. The PCRF may request notifications from the SPR on changes in the subscription information.
5. The PCRF stores the subscription related information containing the information about the allowed service(s) and PCC Rules information and may include MPS EPS Priority, MPS Priority Level and IMS Signalling Priority for establishing a PS session with priority and may also include user profile configuration indicating whether application detection and control should be enabled for the IP-CAN session.
6. If the PCRF determines that the policy decision depends on the status of the policy counters available at the OCS and such reporting is not established for the subscriber, the PCRF sends an Initial Spending Limit Report Request as defined in clause 7.9.1. If policy counter status reporting is already established for the subscriber and the PCRF determines that the status of additional policy counters are required, the PCRF sends an Intermediate Spending Limit Report Request as defined in clause 7.9.2.
7. The PCRF makes the authorization and policy decision. If MPS EPS Priority, MPS Priority Level and IMS Signalling Priority are present for the user, the PCRF takes the information into account.
8. For the solicited application reporting, the PCRF requests the TDF to establish the relevant session towards PCRF and provides ADC Rules to the TDF, as per user profile configuration, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. The PCRF shall include the following information: a PDN identifier (e.g. APN), the IPv4 address and/or IPv6 network prefix, if available and may also include the UE Identity Information and the location/access network information, if available. If Charging Characteristics were received by the PCRF according to step 3 and charging is applicable for the TDF, the PCRF shall also forward received Charging Characteristics to the TDF. Additionally, if received from the PCEF and if charging is applicable for the TDF, the PCRF shall also forward the following parameters to the TDF: the GW/PCEF control plane IPv4 and/or IPv6 address (es), an indication on how the APN was selected, indications on whether IP address (es) where statically or dynamically allocated and the PDN charging identifier of the default bearer. The PCRF may also subscribe to the Event Triggers applicable for the TDF, according to table 6.2.
NOTE 2: If Charging Characteristics are received by the PCRF from the PCEF, PCRF may take them into account when providing Charging information and Default charging method to the TDF.
9. If online charging is applicable for the TDF and at least one ADC rule with charging parameters was activated, the TDF activates the online charging session and provides relevant input information for the OCS decision. Depending on operator configuration, the TDF may request credit from the OCS for each charging key of the activated ADC rules.
10. If online charging is applicable for the TDF, the OCS provides the possible credit information to the TDF and may provide re-authorisation triggers for each of the credits.
11. The TDF sends an Ack (accept or reject of the ADC rule operation(s)) to inform the PCRF about the outcome of the actions related to the decision(s) received in step 8. The Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
12. If traffic steering control over St applies, the PCRF determines the traffic steering control information needed for the IP-CAN session; the PCRF provides the UE IPv4 address and/or UE IPv6 prefix and one or more sets of traffic steering control information to the TSSF. The TSSF identifier is pre-configured on the PCRF per e.g. PCEF.
13. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 12.
14. The PCRF sends the decision(s) including the chosen IP‑CAN bearer establishment mode and indicates whether the use of the extended TFT filter format is allowed in the IP-CAN session, to the PCEF. The GW (PCEF) enforces the decision. The PCRF may provide the default charging method and may include the following information: the PCC Rules to activate and the Event Triggers to report. If PCEF is enhanced with ADC, the applicable PCC rules are provided, according to the user profile configuration, if traffic steering control over Gx applies, PCC Rules may contain traffic steering control information. The Policy and Charging Rules allow the enforcement of policy associated with the IP‑CAN session. The Event Triggers indicate to the PCEF what events must be reported to the PCRF. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
15. If online charging is applicable and at least one PCC rule with charging parameters was activated, the PCEF activates the online charging session and provides relevant input information for the OCS decision. Depending on operator configuration, the PCEF may request credit from the OCS for each charging key of the activated PCC rules.
16. If online charging is applicable, the OCS provides the possible credit information to the PCEF and may provide re-authorisation triggers for each of the credits.
In cases 2a and 2b, if the OCS provides any re-authorisation trigger, which cannot be monitored at the PCEF, the PCEF shall request PCRF to arrange those to be reported by the BBERF via the PCRF.
17. If at least one PCC rule was successfully activated and if online charging is applicable and credit was not denied by the OCS, the GW (PCEF) acknowledges the IP‑CAN Bearer Establishment Request.
18. If network control applies the GW may initiate the establishment of additional IP-‑CAN bearers. See Annex A and Annex D for details.
19. If the PCRF in step 12 has requested an acknowledgement based on PCC rule operations, the GW (PCEF) sends the IP‑CAN Session Establishment Acknowledgement to the PCRF in order to inform the PCRF of the activated PCC rules result. |
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 Session Termination or the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H‑PCRF. For those cases it is also the H-PCRF that initiates the PCRF initiated Gateway Control Session Termination procedure or the Gateway Control and QoS Rules Provision procedure and proxy the information over S9 to the BBERF through the V‑PCRF.
For the Local breakout scenario (figure 5.1-4) the V-PCRF shall proxy Indication and Acknowledge of IP‑CAN Session Termination over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF resides in the VPLMN, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
For the same scenario if either case 1 or case 2b applies (as defined in clause 7.1), the V-PCRF may respond to/initiate the Gateway Control Session procedures locally without notifying the H‑PCRF.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. If case 2b applies, the GW (BBERF) receives a request to remove the IP‑CAN session. In case 2a, the request goes transparently through the GW (BBERF). In all cases, the GW (PCEF) receives a request to remove the IP‑CAN session.
2. If case 2b applies, the GW (BBERF)-initiated GW Control Session Termination procedure as defined in clause 7.7.2.1 is initiated.
3. The GW (PCEF) indicates that the IP‑CAN Session is being removed and provides relevant information to the PCRF.
NOTE 2: The GW (PCEF) may proceed to step 11 in parallel with the indication of IP‑CAN Session termination.
4. The PCRF finds the PCC Rules that require an AF to be notified and removes PCC Rules for the IP‑CAN session.
5. The GW (PCEF) removes all PCC Rules associated with the IP‑CAN session.
6. The PCRF notifies the AF that there are no transmission resources for the service if this is requested by the AF.
7. The AF acknowledges the notification of the loss of transmission resources.
8. If this is the last IP-CAN session for this subscriber requiring policy counter status reporting, the Final Spending Limit Report Request as defined in clause 7.9.3 is sent. If any existing IP-CAN sessions for this subscriber require policy counter status reporting, the Intermediate Spending Limit Report Request as defined in clause 7.9.2 may be sent to alter the list of subscribed policy counters.
9. If there is an active Sd session between TDF and PCRF, the PCRF terminates it.
10. For the solicited application reporting, the TDF deactivates all the ADC Rules associated with the TDF session. The TDF acknowledges the termination request from the PCRF.
11. If online charging is applicable for the TDF, the TDF issues the final reports and returns the remaining credit to the OCS.
12. The OCS acknowledges the credit report and terminates the online charging session with the TDF.
13. The PCRF removes the information related to the terminated IP‑CAN Session (subscription information etc.) and acknowledges to the GW (PCEF) that the PCRF handling of the IP‑CAN session has terminated. This interaction is the response to the GW (PCEF) request in step 3.
NOTE 3: Step 13 may be initiated any time after step 7.
14. The GW (PCEF) continues the IP‑CAN Session removal procedure.
15. If case 2a applies, the GW Control and QoS Rules Provision procedure as defined in clause 7.7.4 may be initiated to remove the QoS rules associated with the IP‑CAN session being terminated. This applies e.g. in case the Gateway Control Session shall remain to serve other IP‑CAN sessions.
Alternatively, if case 2a applies and the PCRF determines that all QoS rules are to be removed and the Gateway Control Session shall be terminated, the PCRF-initiated GW Control Session Termination procedure as defined in clause 7.7.2.2 is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP‑CAN session.
16. If online charging is applicable for the PCEF, the PCEF issues the final reports and returns the remaining credit to the OCS.
NOTE 4: Step 16 may be initiated any time after step 13.
17. The OCS acknowledges that credit report and terminates the online charging session with the PCEF.
18. The PCRF sends a cancellation notification request to the SPR if it has subscribed such notification. If all IP-CAN sessions of the user to the same APN are terminated, the PCRF stores the remaining usage allowance in the SPR.
NOTE 5: Step 18 may be initiated any time after step 13.
19. The SPR sends a response to the PCRF.
20. If RUCI reporting from RCAF to PCRF is used, the PCRF sends a Release context request message to the RCAF using the previously stored identity of the RCAF.
21. RCAF acknowledges this by sending the Release context response message to the PCRF. The RCAF releases the context corresponding to the given UE for the given APN, including any reporting restrictions. This also implies that the RCAF does not indicate to the PCRF that the congestion state is over. In case of multiple PCRFs being in simultaneous use for a given UE, a Release context request message from a PCRF applies to the UE context specific to the given Np connection only, identified by the APN. The RCAF can completely release all context information for a given UE when it has released the context for each Np connection of the given UE.
NOTE 6: The IP‑CAN Session removal procedure may proceed in parallel with the indication of IP‑CAN Session termination.
22. If the PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the PCRF sends a request to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix for the terminated IP-CAN session.
NOTE 7: Step 22 may be initiated any time after step 13.
23. The TSSF acknowledges the removal of the traffic steering control information. |
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) initiated Gateway Control Session Termination or the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H‑PCRF. For those cases it is also the H-PCRF that initiates the PCRF initiated Gateway Control Session Termination procedure or the Gateway Control and QoS Rules Provision procedure and proxy the information over S9 to the BBERF through the V‑PCRF.
For the Local breakout scenario (figure 5.1-4) the V-PCRF shall proxy Indication and Acknowledge of IP‑CAN Session Termination over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF relies in the VPLMN, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
For the same scenario if either case 1 or case 2b applies (as defined in clause 7.1), the V‑PCRF may respond to/initiate the Gateway Control Session procedures locally without notifying the H‑PCRF.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. The GW (PCEF) detects that IP‑CAN Session termination is required.
2. The GW (PCEF) sends a request to remove the IP‑CAN session.
3. If case 2b applies, the GW (BBERF)-initiated GW Control Session Termination procedure as defined in clause 7.7.2.1 is initiated.
4. The GW (PCEF) receives the response for the IP‑CAN session removal.
5. The GW (PCEF) indicates the IP‑CAN Session termination and provides the relevant information to the PCRF.
6. The PCRF finds the PCC Rules that require an AF to be notified.
7. The PCRF notifies the AF that there are no transmission resources for the service if this is requested by the AF.
8. The AF acknowledges the notification on the loss of transmission resources.
9. If this is the last IP-CAN session for this subscriber requiring policy counter status reporting, the Final Spending Limit Report Request as defined in clause 7.9.3 is sent. If any existing IP-CAN sessions for this subscriber require policy counter status reporting, the Intermediate Spending Limit Report Request as defined in clause 7.9.2 may be sent to alter the list of subscribed policy counters.
10. The GW (PCEF) removes all the PCC Rules associated with the IP‑CAN session.
11. If there is an active Sd session between TDF and PCRF, the PCRF informs TDF about IP-CAN session termination.
12. For the solicited application reporting, the TDF deactivates all the ADC Rules associated with the TDF session. The TDF acknowledges the termination request from the PCRF.
13. If online charging is applicable for the TDF, the TDF issues the final reports and returns the remaining credit to the OCS.
14. The OCS acknowledges the credit report and terminates the online charging session with the TDF.
15. The PCRF removes the information related to the terminated IP‑CAN Session (subscription information etc.) and acknowledges the IP‑CAN Session termination.
NOTE 2: Step 15 may be initiated any time after step 6.
16. If case 2a applies, the GW Control and QoS Rules Provision procedure as defined in clause 7.7.4 may be initiated to remove the QoS rules associated with the IP‑CAN session being terminated. This applies e.g. in case the Gateway Control Session shall remain to serve other IP‑CAN sessions.
Alternatively, if case 2a applies and the PCRF determines that the Gateway Control session shall be terminated, the PCRF-initiated GW Control Session Termination procedure as defined in clause 7.7.2.2 is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP‑CAN session.
17. If online charging is applicable for the PCEF, the PCEF issues final reports and returns the remaining credit to the OCS.
NOTE 3: Step 17 may be initiated any time after step 15.
18. The OCS acknowledges the credit report and terminates the online charging session.
19. The PCRF sends a cancellation notification request to the SPR if it has subscribed such notification. If all IP-CAN sessions of the user to the same APN are terminated, the PCRF stores the remaining usage allowance in the SPR.
NOTE 4: Step 19 may be initiated any time after step 8.
20. The SPR sends a response to the PCRF.
21. If RUCI reporting from RCAF to PCRF is used, the PCRF sends a Release context request message to the RCAF using the previously stored identity of the RCAF.
22. RCAF acknowledges this by sending the Release context response message to the PCRF. The RCAF releases the context corresponding to the given UE for the given APN, including any reporting restrictions. This also implies that the RCAF does not indicate to the PCRF that the congestion state is over. In case of multiple PCRFs being in simultaneous use for a given UE, a Release context request message from a PCRF applies to the UE context specific to the given Np connection only, identified by the APN. The RCAF can completely release all context information for a given UE when it has released the context for each Np connection of the given UE.
23. If the PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the PCRF sends a request to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or the UE IPv6 prefix for the terminated IP-CAN session.
NOTE 5: Step 23 may be initiated any time after step 6.
24. The TSSF acknowledges the removal of the traffic steering control information. |
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 modification may be that a start or stop of application traffic that matches with one of the activated PCC Rules is detected.
The AF may be involved. An example of the scenario is authorization of a session-based service for which an IP‑CAN Session is also modified.
Figure 7.4: IP‑CAN Session Modification; GW (PCEF) initiated
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access applies (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), when a Gateway Control Session is used, the H‑PCRF may initiate a Gateway Control and QoS Rules Provisioning procedure towards the BBERF and proxy the information through the V‑PCRF over S9.
For case 2b in the Local Breakout scenario (figure 5.1-4) and if the Gateway Control Session is terminated locally at the V‑PCRF, the V‑PCRF shall initiate the Gateway Control and QoS Rules Provisioning procedure locally without notifying the H‑PCRF. For this case the V-PCRF shall proxy the Indication and Acknowledge of IP‑CAN Session Modification over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF is located in the VPLMN for this scenario, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not shown in the figure.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. Optionally, the AF provides/revokes service information to the PCRF due to AF session signalling. The AF may subscribe at this point to notification of bearer level events related to the service information.
NOTE 2: For the PCRF to generate the applicable events, the PCRF instructs the PCEF to report events related to the corresponding PCC rules. Such events are not shown in this sequence diagram.
2. The PCRF stores the service information and responds with the Acknowledgement to the AF.
3. The GW (PCEF) may receive IP‑CAN session signalling for IP‑CAN Session modification. PDN Connection Identifier may be included in the IP‑CAN session signalling.
4. The GW (PCEF) makes a decision to trigger IP‑CAN Session modification either caused by the previous step or based on an internal decision or, e.g. if the GW (PCEF) enhanced with ADC, has detected the start/ stop of application traffic, requested by one of the activated PCC Rules.
5. The GW (PCEF) determines that the PCC interaction is required and sends an Indication of IP‑CAN Session modification (Event Report, affected PCC Rules, if available, the PDN Connection Identifier) to the PCRF together with, if available, User Location Information and/or UE Time Zone and RAN/NAS Release Cause and, if changed, the new IP‑CAN bearer establishment modes supported. If there is a limitation or termination of the transmission resources for a PCC Rule, the GW (PCEF) reports this to the PCRF. If flow mobility applies, the GW (PCEF) may include updated IP flow mobility routing information for any IP flows; the GW (PCEF) also provides an indication if default route for the IP‑CAN session is changed.
6. The PCRF correlates the request for PCC Rules with the IP‑CAN session and service information available at the GW (PCEF).
7. The PCRF may need to report to the AF an event related to the transmission resources if the AF requested it at initial authorisation.
8. The AF acknowledges the event report and/or responds with the requested information.
9. If the PCRF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Request procedures as defined in clauses 7.9.1, 7.9.2 and 7.9.3.
10. The PCRF makes the authorization and policy decision.
11. For the TDF solicited application reporting, the steps 11-14 take place. The PCRF provides all new ADC decisions to the TDF. This may include ADC Rules activation, deactivation and modification, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. This may also include the list of Event triggers and also Event Report for the Event triggers, if reported by the PCEF/BBERF to the PCRF, if the TDF has previously subscribed for such an Event Report. In case of local breakout, the V-PCRF shall provide ADC rules generated from PCC Rules providing application detection and control as instructed by the H‑PCRF over S9.
For unsolicited application reporting and if the PCRF has recorded the release of an IPv4 address in step 5, the PCRF terminates the related Sd session.
12. If online charging is applicable for the TDF, the TDF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
13. If OCS was contacted by the TDF, the OCS provides the credit information to the TDF and/or acknowledges the credit report.
14. The TDF sends an Ack (accept or reject of the ADC rule operation(s)) to inform the PCRF about the outcome of the actions related to the decision(s) received in step 11. The Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
15. If traffic steering control over St applies, the PCRF determines if traffic steering control information needs to be modified/provisioned for the IP-CAN session; the PCRF provides to the TSSF the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix.
16. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 15.
17. The PCRF sends an Acknowledge of IP‑CAN Session modification (PCC Rules, Event Triggers and, if changed, the chosen IP‑CAN bearer establishment mode) to the GW (PCEF). If traffic steering control over Gx applies, PCC Rules may contain traffic steering control information. The GW (PCEF) enforces the decision. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
18. If online charging is applicable for the PCEF, the GW (PCEF) may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
19. If OCS was contacted by the PCEF, the OCS provides the credit information to the GW (PCEF) and/or acknowledges the credit report.
20 The GW (PCEF) acknowledges or rejects any IP‑CAN Session signalling received in step 3.
An IP‑CAN bearer establishment is accepted if at least one PCC rule is active for the IP‑CAN bearer and in case of online charging credit was not denied by the OCS. Otherwise, the IP‑CAN bearer establishment is rejected.
An IP‑CAN bearer termination is always acknowledged by the GW (PCEF).
An IP‑CAN bearer modification not upgrading the QoS and not providing traffic mapping information is always acknowledged by the GW (PCEF). An IP‑CAN bearer modification is accepted if the provided traffic mapping information is accepted by the PCRF. Otherwise, the IP‑CAN bearer modification is rejected.
In case of a GW (PCEF) internal decision the GW (PCEF) initiates any additional IP‑CAN Session signalling required for completion of the IP‑CAN Session modification (applicable to case 1).
In case the IP‑CAN session modification is due to the BBF transitioning from a BBERF in the source access-network to the PCEF, the PCEF initiates IP‑CAN bearer signalling to activate bearers in the target access network (applicable to case 1).
21. The GW (PCEF) receives the response for the IP‑CAN Session signalling request (applicable to case 1).
22. The GW (PCEF) sends a Provision Ack (accept or reject of the PCC rule operation(s)) to inform the PCRF about the outcome of the GW (PCEF) actions related to the decision(s) received in step 15.
NOTE 3: For Cases 2a and 2b, the rejection of PCC rule operation can only occur as a result of online charging interaction.
23. Based on the result of PCC rule operations, the PCRF decides whether to initiate a Gateway Control and QoS Rules provision procedure as defined in clause 7.7.4, if required to keep the PCC and QoS rules aligned (applicable to cases 2a and 2b, as defined in clause 7.1).
If there are multiple BBERFs associated with the IP‑CAN session, this step is performed with all the affected BBERFs.
24. If the AF requested it, the PCRF notifies the AF of related bearer level events (e.g. transmission resources are established/released/lost).
NOTE 4: Based on the outcome reported in this step the AF performs the appropriate action, e.g. starting charging or terminating the AF session.
25. The AF acknowledges the notification from the PCRF. |
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.
- A change in the status of a policy counter.
IP‑CAN Session handling and handling of PCC rules for non-session based services and also general handling of PCC rules that are not subject to AF-interaction or TDF-interaction is also applicable here.
Figure 7.5: IP‑CAN Session Modification; PCRF initiated
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access applies (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), when a Gateway Control Session is used, the V‑PCRF shall proxy Gateway Control and QoS Rules Request between the BBERF in the VPLMN and the H‑PCRF over S9. For this case the H‑PCRF may also initiate a Gateway Control and QoS Rules Provisioning procedure towards the BBERF in the VPLMN and proxy the information via the V‑PCRF over S9.
For case 2b in the Local Breakout scenario (figure 5.1-4) and if the Gateway Control Session is terminated locally at the V‑PCRF, the V-PCRF shall reply to/initiate Gateway Control Session and QoS Rules Request/Provisioning procedures locally without notifying the H‑PCRF. For this case the V‑PCRF shall proxy the Policy and Charging Rules Provisioning and Acknowledge over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF is located in the VPLMN for this scenario, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1a. Optionally, the AF provides/revokes service information to the PCRF due to AF session signalling. The AF may subscribe at this point to notification of bearer level events related to the service information. The AF may also provide a reference ID to a transfer policy that the AF previously negotiated with the PCRF (as described in clauses 6.1.16 and 7.11.1).
NOTE 2: For the PCRF to generate the applicable events, the PCRF instructs the PCEF to report events related to the corresponding PCC rules. Such events are not shown in this sequence diagram.
1b. Alternatively, optionally, for TDF, e.g. the TDF detects the start/stop of an application traffic that matches with one of the active ADC Rules.
For solicited application reporting, if the start/stop of application traffic detection Event Trigger was received from the PCRF and the reporting is not muted for the ADC rule, the TDF shall provide application information to the PCRF, including the application identifier, start or stop of application traffic detection event trigger and, for the start of application's traffic detection, the service data flow descriptions, if deducible. Additionally, the application instance identifier should be included in the report both for Start and for Stop of application traffic detection, when the service data flow descriptions are provided.
For unsolicited application reporting, the Sd reports the same application information to the PCRF unconditionally. The TDF establishes a new Sd session if it detects an application for an IPv4 address or IPv6 address for which no corresponding Sd session exists.
1c. Alternatively, optionally, the OCS provides a Spending Limit Report to the PCRF as described in clause 7.9.4.
1d. Alternatively, optionally, the RCAF provides a Congestion Report to the PCRF as described in clause 7.10.1.
NOTE 3: This step is not shown on the diagram.
2a. The PCRF stores the service information if available and responds with the Acknowledgement to the AF. This is applicable to 1a case.
NOTE 4: Without AF interaction, a trigger event in the PCRF may cause the PCRF to determine that the PCC rules require updating at the PCEF, e.g. change to configured policy.
NOTE 5: This procedure could also be triggered by the Gateway Control and QoS Rules Request procedure as described in clause 7.7.3.
3. If the PCRF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Request procedures as defined in clauses 7.9.1, 7.9.2 and 7.9.3.
4. The PCRF makes the authorization and policy decision. If the AF provided a reference ID to a transfer policy in step 1a, the PCRF shall retrieve the corresponding transfer policy from the SPR before making any decisions.
5. The PCRF may store the application information if provided and responds with an Acknowledgement to the TDF (for unsolicited application reporting) or a Sd session modification (for solicited application reporting). For the TDF solicited application reporting, the PCRF may provide a new ADC decision to the TDF. If the last ADC rule is deactivated, the PCRF requests the TDF to terminate the Sd session towards the PCRF. If there is no active Sd session yet between the TDF and the PCRF, the PCRF requests the TDF to establish the Sd session towards PCRF and provides an ADC decision to the TDF, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. In case of local breakout, the V-PCRF shall provide ADC rules generated from PCC Rules providing application detection and control as instructed by the H‑PCRF over S9.
6. If online charging is applicable for the TDF, the TDF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
7. If OCS was contacted by the TDF, the OCS provides the credit information to the TDF and/or acknowledges the credit report.
8. For the TDF solicited application reporting, in the case of an existing on-going session, if requested by the PCRF the TDF sends a Provision Ack (accept or reject of the ADC Rule operation(s)). For a new session, the TDF sends an Ack. This is to inform the PCRF about the outcome of the actions related to the received ADC decision(s). The Provision Ack / Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
9. If traffic steering control over St applies, the PCRF determines if traffic steering control information needs to be modified/provisioned for the IP-CAN session; the PCRF provides to the TSSF the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix.
10. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 9.
11. If there is no Gateway Control and QoS Rules Reply pending and there is a need to provision QoS rules, the PCRF initiates a Gateway Control and QoS Rules Provision Procedure as defined in 7.7.4 (applicable to cases 2a and 2b, as defined in clause 7.1).
If there are multiple BBERFs associated with the IP‑CAN session, Step 9 is performed with the BBERFs that support UE/NW bearer establishment mode.
NOTE 6: If there is a Gateway Control and QoS Rules Reply pending, e.g. this procedure was invoked from the Gateway Control and QoS Rules Request procedure as defined in clause 7.7.3, the PCRF shall use that opportunity for provisioning the applicable QoS rules. If there are multiple BBERFs associated with the IP‑CAN session and the procedure was invoked by a Gateway Control and QoS Rules Request procedure from the primary BBERF, the PCRF may receive a Gateway Control and QoS Rules Request from the non-primary BBERFs.
12. The PCRF sends the Policy and Charging Rules Provision (PCC Rules, Event Trigger, Event Report) to the PCEF. If traffic steering control over Gx applies, the PCC Rules may contain traffic steering control information. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
13. The PCEF enforces the decision.
14. If online charging is applicable for the PCEF, the PCEF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may return the remaining credit for charging keys no longer active to the OCS.
15. If OCS was contacted by the PCEF, the OCS provides the credit information to the PCEF and/or acknowledges the credit report.
16. The GW (PCEF) may send an IP‑CAN Bearer establishment, modification or termination request (applicable to case 1, as defined in clause 7.1).
An IP‑CAN bearer modification is sent by the GW (PCEF) if the QoS of the IP‑CAN bearer exceeds the authorized QoS provided by the PCRF in step 4.
An IP‑CAN bearer termination request is sent by the GW (PCEF) if all PCC rules for an IP‑CAN bearer have been removed.
17. The GW (PCEF) receives the response for the IP‑CAN Bearer modification or termination request (applicable to case 1).
18. The PCEF sends Acknowledge Policy and Charging Rules Provisioning (accept or reject of the PCC rule operation(s)) to the PCRF.
19. If the AF requested it, the PCRF notifies the AF related bearer level events (e.g. transmission resources are established/released/lost).
20. The AF acknowledges the notification from the PCRF. |
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 profile.
5 If the updated subscriber profile requires the status of new policy counters available at the OCS then an Initial/Intermediate Spending Limit Report Request is sent from PCRF as defined in clauses 7.9.1 and 7.9.2. If the updated subscriber profile implies that no policy counter status is needed an Intermediate Spending Limit Report Request is sent from PCRF, if this is the last policy counter status Final Spending Limit Report Request is sent from PCRF as specified in clause 7.9.3.
6. PCRF makes an authorization and policy decision.
7. The PCRF provides all new PCC decisions to the PCEF and BBERF (if applicable), using the PCRF initiated IP‑CAN session modification procedure in clause 7.4.2. The PCRF also provides all new ADC decisions to the TDF, if applicable. |
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 binding).
- The PCRF must be able to associate sessions established over the different reference points (Gx, Rx, S9, Gxa/Gxc, Sd, Np), for the same UE's IP‑CAN session. The actual reference points that need to be correlated depend on the scenario (e.g. roaming, LBO etc.).
- It shall be possible to deploy a network so that a PCRF may serve only specific PDN(s). For example, PCC may be enabled on a per APN basis.
For the case 2a (as defined in clause 7.1), the same PCRF shall support all the PDNs for which PCC is enabled and for which there are potential users accessing by means of case 2a (as defined in clause 7.1).
It shall also be possible to deploy a network so that the same PCRF can be allocated for all PDN connections for a UE.
- A standardized procedure for contacting the PCRF is preferred to ensure interoperability between PCRFs from different vendors. The procedure may be specific for each reference point. The procedure shall enable the PCRF(s) to coordinate Gx, Rx and, when applicable, Gxa/Gxc, S9, Sd and Np interactions.
- It shall allow that entities contacting the PCRF may be able to provide different sets of information about the UE and PDN connections. For example:
- The AF has information about UE IP address and PDN but may not have user identity information.
- The PDN GW has information about user identity (UE NAI), the APN and the UE IP address(es) for a certain PDN connection.
- For case 2b as defined in clause 7.1, the S‑GW and trusted non-3GPP access has information about the user identity (UE NAI) and, the APN(s) but may not know the UE IP address(es).
- For case 2a as defined in clause 7.1, the trusted non-3GPP access has information about the user identity (UE NAI) and the local IP address (CoA) but may not know the APN or UE IP address(es) (HoA).
- The TDF (when the unsolicited application reporting applies) has the information about UE IP address, but may not have the UE identity.
- The RCAF has the information about the user identity (IMSI) and the APN.
- The DRA has information about the user identity (UE NAI), the APN, the UE IP address(es) and the selected PCRF address for a certain IP‑CAN Session.
When the DRA first receives a request for a certain IP‑CAN Session (e.g. from the PDN GW), the DRA selects a suitable PCRF for the IP‑CAN Session and stores the PCRF address. Subsequently, the DRA can retrieve the selected PCRF address according to the information carried by the incoming requests from other entities (e.g. the AF or the BBERF).
When the IP‑CAN Session terminates, the DRA shall remove the information about the IP‑CAN Session. In case of the PCRF realm change, the information about the IP‑CAN session stored in the old DRA shall be removed.
- All PCRFs in a PLMN belong to one or more Diameter realms. Routing of PCC messages for a UE towards the right Diameter realm in a PLMN is based on standard Diameter routing, as specified in RFC 3588, i.e. based on UE-NAI domain part. A Diameter realm shall provide the ability of routing PCC messages for the same UE and PDN connection to the same PCRF based on the available information supplied by the entities contacting the PCRF.
- A PLMN may be separated into multiple Diameter realms based on the PDN ID information or IP address range. In this case, the relevant information (PDN ID, IP address, etc) shall be used to assist routing PCC message to the appropriate Diameter realm.
- Unique identification of an IP‑CAN session in the PCRF shall be possible based on the (UE ID, PDN ID)-tuple , the (UE IP Address(es), PDN ID)-tuple and the (UE ID, UE IP Address(es), PDN ID).
- Standard IETF RFC 3588 mechanisms and components, e.g. Diameter agents, should be applied to deploy a network where the PCRF implementation specifics are invisible for Diameter clients. The use of Diameter agents, including Diameter redirect agents, shall be permitted, but the use of agents in a certain deployment shall be optional.
NOTE: For the use of private UE IPv4 address TS 29.213 [22] provides guidance. |
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)" function is enabled. This resolution mechanism is not required in networks that utilise a single PCRF per Diameter realm. The DRA has the following roles:
- When deployed, DRA needs to be contacted at first interaction point for a given GW and IP‑CAN session.
NOTE: How subsequent interactions work is described in TS 29.213 [22].
- When deployed, the DRA is on the Diameter routing path when initiating a session with a PCRF over Gx, Rx, Gxa/Gxc, S9 and Sd.
- The DRA is involved at IP‑CAN session establishment by the PDN GW.
- The DRA selects the PCRF at initial attach (IP‑CAN session or Gateway Control session establishment).
- The DRA is involved at Gateway Control session establishment by the S‑GW and trusted non-3GPP access.
- The DRA selects the PCRF at unsolicited service reporting over Sd.
- After IP‑CAN session or Gateway Control Session establishment, the DRA ensures that the same PCRF is contacted for Rx, Gxa/Gxc, Gx, S9, Sd and Np.
- The DRA keeps status of assigned PCRF for a certain UE and IP‑CAN session.
- It is assumed that there is a single logical DRA serving a Diameter realm.
- In roaming scenarios, there is only a single VPCRF for all the PCC sessions (IP‑CAN session, GW control sessions, AF session, etc.) belonging to a single PDN connection of the UE. The VPCRF shall be selected by a DRA in the visited PLMN.
Figure 7.6-1: PCRF selection and discovery using DRA
The DRA functionality should be transparent to the Diameter applications used on the Gx, Gxa/Gxc, S9, Rx, Sd or Np reference points.
In roaming scenario, home routed or local breakout, if the DRA is deployed, the vPCRF is selected by the DRA located in the visited PLMN and the hPCRF is selected by the DRA located in the home PLMN.
The parameters available for the DRA to be able to determine the already allocated PCRF depend on the reference point over which the DRA is contacted, as described in clause 7.6.1. |
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 Session corresponding to the Gateway Control Session being established. This happens when the BBERF changes, i.e. during BBERF relocation and handovers from and to GTP based EPC. |
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 on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The GW (BBERF) receives an indication that it must establish a Gateway Control Session.
2. The GW (BBERF) sends the PCRF a Gateway Control Session Establishment. The BBERF includes the following information: IP‑CAN Type, UE Identity, PDN Identifier (if known), IP address(es) (if known), an indication that leg linking shall be deferred (applicable for case 2b, as defined in clause 7.1), if available, the PDN Connection Identifier and if available, the IP‑CAN bearer establishment modes supported and the indication of BBERF support for the extended TFT filter format. The IP‑CAN Type identifies the type of access used by the UE. The UE's identity and PDN Identifier requested are used to identify the subscriber and in PCRF selection to locate the PCRF function with the corresponding IP‑CAN session established by the PDN GW. The BBERF may also include the Default Bearer QoS and APN-AMBR (applicable for case 2b, as defined in clause 7.1). An indication that leg linking shall be deferred is included to inform the PCRF that linking the Gateway Control Session to a Gx session shall occur when a matching Gx message is received as described clause 6.2.1.0. Further information is supplied on an access specific basis, as described in the IP‑CAN specific Annexes.
NOTE: The BBERF support is a prerequisite for the PCRF enabling the possibility for usage of the extended TFT filter format in the IP-CAN session(s).
3. For GERAN/UTRAN accesses, if the PCRF is required to interact with the GW (PCEF), the PCRF waits until it gets informed about the establishment of the corresponding IP‑CAN session (step 7 of the IP‑CAN session establishment procedure) and performs a PCRF initiated IP‑CAN session modification procedure with the GW (PCEF).
4. The PCRF sends an Acknowledge Gateway Control Session Establishment to the GW (BBERF). The PCRF may include the following information: the chosen IP‑CAN bearer establishment mode, QoS Rules and Event Triggers. In case 2a a charging ID may be provided together with QoS rules. The QoS policy rules are employed by the GW (BBERF) to perform Bearer Binding. The Event Triggers indicate events that require the GW (BBERF) to report to the PCRF.
5. The QoS Rules and Event Triggers received by the GW (BBERF) are deployed. This will result in bearer binding being performed, according to the rules. This step may trigger IP‑CAN bearer establishment procedures. The details of bearer establishment are IP‑CAN specific.
6. An indication of Gateway Control Session Established is sent to the entity that triggered the initiation of the session. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.1.2 Gateway Control Session Establishment during BBERF Relocation | Figure 7.7.1.2-1: Gateway Control Session Establishment during BBERF Relocation
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 on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The target GW (BBERF) receives an indication that it must establish a Gateway Control Session.
2. The target GW (BBERF) sends the PCRF a Gateway Control Session Establishment. The BBERF includes the following information: IP‑CAN Type, UE Identity, PDN Identifier (if known), IP address(es) (if known), PDN Connection Identifier if available and, if available, the IP‑CAN bearer establishment modes supported. The IP‑CAN Type identifies the type of access used by the UE. The UE's identity and PDN Identifier requested are used to identify the subscriber and in PCRF selection to locate the PCRF function with the corresponding IP‑CAN session established by the PDN GW. The BBERF may also include the Default Bearer QoS and APN-AMBR (applicable for case 2b, as defined in clause 7.1). If the handover state is unknown to the GW (BBERF), as described in TS 23.402 [18], the GW (BBERF) includes an indication to inform the PCRF that linking the Gateway Control Session to a Gx session shall be deferred as described clause 6.2.1.0 (applicable for case 2b, as defined in clause 7.1). Further information is supplied on an access specific basis, as described in the IP‑CAN specific Annexes.
3. If case 2b of clause 7.1 applies and the PCRF correlates the Gateway Control Session with an existing IP‑CAN session, it sends an Acknowledge Gateway Control Session Establishment to the target GW (BBERF). The PCRF may include the following information: QoS Rules and Event Triggers. The QoS policy rules are employed by the GW (BBERF) to perform Bearer Binding. The Event Triggers indicate events that require the GW (BBERF) to report to the PCRF. If the BBERF supports NW/UE bearer establishment mode, the PCRF provides to the new BBERF QoS rules corresponding to existing SDFs. For a change of IP‑CAN type, the QoS parameters of some of the QoS rules may be changed or some QoS rules may not be provided to the new BBERF, e.g. depending of the capability of the target RAT.
If case 2a of clause 7.1 applies, the PCRF sends an Acknowledge Gateway Control Session Establishment to the target GW (BBERF). The PCRF includes packet filters and QoS information for the CoA in order to establish the initial bearer, e.g. for the DSMIPv6 signalling. The PCRF may also include Event Triggers.
NOTE: The packet filters and QoS information provided at this step conceptually are not QoS rules as they are not associated with any IP-CAN session. However, it is a stage 3 issue if the packet filters and QoS information are communicated to the BBERF with the same information elements by which QoS rules are communicated.
4. The QoS Rules and Event Triggers received by the target GW (BBERF) are deployed. This will result in bearer binding being performed, according to the rules. This step may trigger IP‑CAN bearer establishment procedures. The details of bearer establishment are IP‑CAN specific.
5. An indication of Gateway Control Session Established is sent to the entity that triggered the initiation of the session.
6. The target GW (BBERF) initiates the IP‑CAN Bearer signalling if required for the QoS Rules and Event Triggers deployed in step 4.
7. The target GW (BBERF) receives the response for the IP‑CAN Bearer signalling.
8. The target GW (BBERF) sends the result of the QoS rule activation to the PCRF, indicating whether the resources requested have been successfully allocated.
9. If case 2b applies the source GW (BBERF) initiates the Gateway Control Session Termination procedure as defined in clause 7.7.2.1, if appropriate.
10. If the PCC rules previously provided to the GW (PCEF) need to be removed due to the result of the QoS rule activation as received in step 8, the PCRF updates the GW (PCEF). The PCRF first waits for the PCEF initiated IP‑CAN session modification procedure to provide the updates. If the IP‑CAN session modification procedure already occurred, the PCRF performs an IP‑CAN session modification procedure with the GW (PCEF).
11. If case 2a applies the PCRF initiates a Gateway Control and QoS Rules Provision procedure towards the target GW (BBERF) as defined in clause 7.7.4, if appropriate, in order to provide any QoS Rules based on the IP‑CAN session modification of step 10. In case 2a a charging ID may be provided together with QoS rules.
12. If case 2a applies the PCRF initiates a Gateway Control and QoS Rules Provision procedure towards the source GW (BBERF) as defined in clause 7.7.4, if appropriate, in order to remove any QoS Rules affected by the GW (BBERF) re-location. If there is no other IP‑CAN session established at the source GW (BBERF), the PCRF instead initiates the Gateway Control Session Termination procedure as defined in clause 7.7.2.2. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2 Gateway Control Session Termination | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2.1 GW (BBERF)-Initiated Gateway Control Session Termination | Figure 7.7.2-1: BBERF-Initiated Gateway Control Session Termination
1. The GW (BBERF) is requested to terminate its Gateway Control Session.
2. The GW (BBERF) initiates a Gateway Control Session Termination towards the H-PCRF. If the GW (BBERF) is deployed in a visited network, this procedure is initiated by the GW (BBERF) to the V-PCRF. The V-PCRF forwards the information to the H-PCRF.
3. The H-PCRF replies to the GW (BBERF) with an Ack Gateway Control Session Termination. If the GW (BBERF) is deployed in a visited network, this information is sent by the H-PCRF to the V-PCRF. The V-PCRF forwards the information to the GW (BBERF).
4. The GW (BBERF) removes the QoS rules and Event triggers associated with the Gateway Control Session. This means the GW (BBERF) ceases its bearer binding and other Gateway Control functions associated with the QoS rules and Event Triggers.
5. The GW (BBERF) has completed terminating the session and can continue with the activity that prompted this procedure. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2.2 PCRF-Initiated Gateway Control Session Termination | Figure 7.7.2-2: PCRF-Initiated Gateway Control Session Termination
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 Termination between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The PCRF is requested to terminate its Gateway Control Session.
2. The PCRF sends a PCRF-Initiated Gateway Control Session Termination to the GW (BBERF).
3. The GW (BBERF) removes the QoS rules and Event triggers associated with the Gateway Control Session. This means the GW (BBERF) ceases its bearer binding and other Gateway Control functions associated with the QoS rules and Event Triggers.
4. If the bearer(s) corresponding to the removed QoS rules are still established, the GW (BBERF) initiates an IP‑CAN specific bearer removal procedure.
5. The GW (BBERF) receives the response for the IP‑CAN specific bearer removal procedure.
6. The GW (BBERF) replies to the PCRF with an PCRF-Initiated Gateway Control Session Termination acknowledgement. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.