6.4 IP‑CAN bearer and IP‑CAN session related policy information

23.2033GPPPolicy and charging control architectureRelease 17TS

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