Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.203  Word version:  17.2.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.1.4…   6.1.7…   6.1.10…   6.1.17…   6.2…   6.2.2…   6.2.3…   6.3   6.4…   6.8…   7…   7.3…   7.4…   7.7…   7.7.3…   7.8…   A…   A.4…   D…   P…   P.4.2.4…   P.7…   P.7.5…   P.8   Q…   S…   S.7…   S.8.8   T…

 

6.4  IP CAN bearer and IP CAN session related policy informationp. 111

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.
Attribute Description PCRF permitted to modify the attribute Scope
Charging information (NOTE 2)Defines the containing OFCS and/or OCS addresses.NoIP-CAN session
Default charging method (NOTE 2)Defines the default charging method for the IP-CAN session.NoIP-CAN session
Event triggerDefines the event(s) that shall cause a re-request of PCC rules for the IP-CAN bearer.YesIP-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).YesIP-CAN bearer
Authorized MBR per QCI (network initiated IP-CAN bearer activation/modification) (NOTE 1) (NOTE 3)Defines the authorised MBR per QCI.YesIP-CAN session
Revalidation time limitDefines the time period within which the PCEF shall perform a PCC rules request.YesIP-CAN session
PRA Identifier(s)Defines the Presence Reporting Area(s) to monitor for the UE with respect to entering/leavingYesIP-CAN session
List(s) of Presence Reporting Area elements (NOTE 4)Defines the elements of the Presence Reporting Area(s)YesIP-CAN session
Default NBIFOM accessThe access to be used for all traffic that does not match any existing Routing RuleYes (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.
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.
Up

6.4a  TDF session related policy information |R11|p. 113

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.
Attribute Description PCRF permitted to modify the attribute
Charging CharacteristicsDefines how to control TDF behaviour regarding online and offline charging.No
Charging informationDefines the containing OFCS and/or OCS addresses.No
Default charging methodDefines the default charging method for the TDF session.No
Event triggerDefines the event(s) that shall cause a re-request of ADC rules for the TDF session.Yes
Maximum downlink bit rateDefines the maximum downlink bit rate per TDF session.Yes
Maximum uplink bit rateDefines the maximum uplink bit rate per TDF session.Yes
ADC Revalidation time limitDefines 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.
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.
Up

6.4b  APN related policy information |R13|p. 114

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.
Attribute Description PCRF permitted to modify the attribute Scope
Authorized APN-AMBRDefines the APN-AMBR for the total bandwidth usage of non-GBR QCI traffic at the APN.YesAll 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.
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.
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.
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.
Up

6.5  Quality of Service Control rule |R8|p. 116

6.5.1  Generalp. 116

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.
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.
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.
Information name Category PCRF permitted to modify for an active QoS rule in the BBERF
Rule identifier (NOTE 1)MandatoryNo
Service data flow detection
PrecedenceMandatoryYes
Service data flow templateMandatoryYes
QoS control
QoS class identifier (NOTE 2)MandatoryYes
UL-maximum bitrateConditional (NOTE 3)Yes
DL-maximum bitrateConditional (NOTE 3)Yes
UL-guaranteed bitrateConditional (NOTE 3)Yes
DL-guaranteed bitrateConditional (NOTE 3)Yes
UL sharing indicationNo
DL sharing indicationNo
ARPConditional (NOTE 3)Yes
PS to CS session continuityConditionalNo
Access Network Information Reporting
User Location ReportConditionalYes
UE Timezone ReportConditionalYes
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.
Up

6.5.2  Quality of Service control rule operationsp. 117

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.
Up

6.6  Usage Monitoring Control specific information |R9|p. 118

6.6.1  Generalp. 118

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.
Information name Description Category Scope
Monitoring keyThe PCRF uses the monitoring key to group services that share a common allowed usage.MandatoryIP-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.OptionalMonitoring key
Time threshold (NOTE 1)Defines the resource time usage after which the PCEF or the TDF shall report usage to the PCRF.OptionalMonitoring key
Monitoring timeDefines the time at which the PCEF or the TDF shall reapply the Volume and/or Time Threshold.OptionalMonitoring Key
Subsequent Volume thresholdDefines 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 thresholdDefines 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 TimeDefines 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.
Up

6.6.2  Usage Monitoring Control operationsp. 119

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.
Up

6.7  S2c based IP flow mobility Routing rule |R10|p. 119

6.7.1  Generalp. 119

The clause 6.7 refers to UE based IP flow mobility as described in TS 23.261.
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.
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.
Information name Description Category PCEF permitted to modify in an update
Rule identifierUniquely identifies the routing rule within an IP-CAN session. It is assigned by the PCEF.MandatoryNo
Routing informationThis clause defines the method for detecting packets belonging to a flow and the route for the flow.
PrecedenceDetermines the order, in which the routing filters are applied.MandatoryYes
Packet filterA list of packet filters for the detection of IP flows.MandatoryYes
IP flow mobility Routing AddressThe IP flow mobility Routing Address that the matching IP flows use.MandatoryYes
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.
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.
Up

6.7.2  Routing rule operationsp. 120

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.
Up

Up   Top   ToC