Content for  TS 23.203  Word version:  19.0.0

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.

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.

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.

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.

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.

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.