For EPS the credit re-authorisation triggers in Table A.4.3-1 shall apply in addition to the ones in Table 6.1. They are applicable both in case of PCEF and in case of TDF.

If the Location change trigger for GERAN/UTRAN or E-UTRAN is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 or TS 23.401. The OCS determines at credit management session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the OCS may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the credit management session. If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (the SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 or TS 23.401. If the User CSG Information change in CSG cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required.

For EPS the event triggers in Table A.4.3-2 shall apply in addition to the ones in Table 6.2 at the PCEF upon the request of the PCRF.

If the Location change trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 or TS 23.401. The PCRF determines at IP-CAN session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the PCRF may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the IP-CAN session. If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 or TS 23.401. The User Location Report in the Access Network Information Reporting contains the ECGI and when the bearer is deactivated, information on when the UE was last known to be in that location. If the User CSG Information change in CSG cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required.

As explained in clause 6.1.1, the binding mechanism is performed in three steps: Session Binding, PCC Rule authorization and Bearer Binding. Session Binding has no 3GPP Access (GTP-based) specifics. For the authorization of a PCC rule with a GBR QCI the PCRF shall assign a GBR value within the limit supported by the serving network. For the 3GPP Access (GTP-based) the Bearer Binding is performed by the PCEF. For GERAN/UTRAN in UE-only mode the Bearer Binding mechanism is restricted by the UE provided binding between a SDF and a bearer for UE initiated resource requests. A PCEF supporting the Bind to Default Bearer PCC rule attribute shall bind a dynamic PCC rule with this attribute to the default bearer instead of using the bearer binding mechanism defined in clause 6.1.1.4 and keep the binding as long as this attribute remains set. When the PCRF removes the Bind to Default Bearer PCC rule attribute, the bearer binding mechanism as defined in clause 6.1.1.4 shall be applied by using the QoS Class Identifier and ARP values of the dynamic PCC rule. The PCEF support for the Bind to Default Bearer PCC rule attribute is optional, and shall be indicated to the PCRF. The bearer binding mechanism associates the PCC Rule with the EPS bearer to carry the service data flow. The association shall:

• cause the downlink part of the service data flow to be directed to the EPS bearer in the association; and
• assume that the UE directs the uplink part of the service data flow to the EPS bearer in the association.

Thus, the detection of the uplink part of a service data flow shall be performed on the EPS bearer over which the downlink packets of the same service data flow is directed to. When the PDN GW is connected to an SGSN via Gn/Gp (and thus a handover from UTRAN/GERAN to E-UTRAN is possible), the bearer binding in the PCEF shall not combine PCC rules with different ARP values onto the same PDP context. For the UE-only mode (which is based on a UE provided binding) PCC rules with different ARP values shall not be authorized for the same PDP context.

For 3GPP Access (GTP based) the policy control functionalities should include the following functionality for QoS control (in addition to the functionalities listed in clause 6.1.5):

• Authorization and enforcement of the maximum QoS that is authorized for the total bandwidth usage of non-GBR QCIs at an APN.
• Authorization and enforcement of the maximum QoS allocated to the Default EPS bearer. The Default EPS bearer shall have a non-GBR QCI as defined in clause 4.7.2.1 of TS 23.401.

The following information represents 3GPP EPS specific values of the ones listed in clause 6.2.1.1:

• Subscriber Identifier in the form of IMSI, MSISDN;
• Type of IP-CAN is set to 3GPP-EPS.

The PCEF may provide the following information (in addition to the information in clause 6.2.1.1):

• Subscribed APN-AMBR;
• Default EPS Bearer QoS.

The SPR may provide the following information for a subscriber (in addition to the information in clause 6.2.1.1) connecting to a specific PDN:

• Authorized APN-AMBR for 3GPP Access;
• Authorized Default EPS Bearer QoS.

The Authorized APN-AMBR and the Authorized Default EPS Bearer QoS are derived by the PCRF from SPR interaction, according to operator policy. The PCRF shall upon indication of PCC rule removal due to PS to CS handover notify the AF that the associated flows are no longer served by the PS-domain due to PS to CS handover. If vSRVCC is supported in the serving network, the PCRF (V-PCRF if roaming) provides an indicator via Gx to the PCEF to indicate that vSRVCC is allowed for the flow corresponding to the video component of the voice/video call. The PCRF shall provide SDF filters in the PCC rule as received in the packet filter information from the PCEF. If the PCRF receives a request for addition of service data flow(s) with a reference to existing SDF filter identities (and by that to existing PCC rule(s)), the PCRF shall use the QCI or ARP of the existing PCC rule for the new service data flow(s).

In the 3GPP Access (GTP-based) architecture the PCEF enforce QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.2.1 with the following additions:

• Authorized APN-AMBR enforcement. The PCEF shall enforce the authorized APN-AMBR received via the Gx interface for the total bandwidth usage of non-GBR QCI for the APN.
• Authorized Default EPS Bearer QoS Enforcement. The PCEF receives the authorized QoS for the default bearer over Gx interface. The PCEF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The PCEF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any PCC Rule operation requested by the PCRF.

When the PDN GW is connected via Gn/Gp (and thus handover from UTRAN/GERAN to E-UTRAN is possible), the PDN-GW shall map QoS parameters of EPS bearers and APN-AMBR (if not received via Gn/Gp) to/from Release 99 and Release 97/Release 98 QoS parameter values of PDP-contexts as specified in Annex E of TS 23.401. The PDN GW shall mediate Gn/Gp procedures so that PCRF experiences no difference compared to S5/S8 procedures. Only the GBR per bearer is used for resource reservation (e.g. admission control in the RAN). The MBR (per PCC rule / per bearer) and the authorized APN-AMBR are used for rate policing.

The AF instructions to report loss of transmission resources will result in a notification from the PCRF that may include an indication that the transmission resources are lost due to PS to CS handover.

For IP-CAN session modification (described in clause 7.4.1) the PCEF includes the modification of any of the 3GPP specific information listed in clause A.4.4.2. If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the PCEF reports termination of transmission resources for associated PCC Rules due to PS to CS handover. The PCRF may provide the following parameters in the Acknowledgement of the IP-CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN-AMBR, Authorized Default EPS Bearer QoS.

The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN-AMBR, Authorized Default EPS Bearer QoS. Whenever the PCRF modifies the Authorized Default EPS Bearer QoS, the PCRF shall simultaneously modify the QCI and ARP of all PCC Rules that, according to the operator policy, shall have the same QoS as the default bearer. A modification of the Authorized Default EPS Bearer QoS requires that at least one PCC Rule with a matching QoS can be bound to the default bearer as defined in clause 6.1.1.4.

The same considerations as in clause A.4.3.1.3 apply with the following modifications:

• For the 3GPP Access (PMIP-based) the Bearer binding is performed by the BBERF.

For 3GPP Access (PMIP-based EPC) the same credit re-authorisation triggers as defined in Table A.4.3-1 apply.

For 3GPP Access (PMIP-based EPC) the same event triggers as defined in Table A.4.3-2 apply. However, they apply at the BBERF (and not at the PCEF) upon the request from the PCRF.

For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.1 apply with the following modification:

• Default EPS Bearer QoS and Subscribed APN-AMBR are provided by the BBERF.

For 3GPP Access (PMIP based), the PCRF receives information about supported bearer establishment modes from the PCEF and provides the bearer establishment mode to be used to the PCEF, i.e. in the same way as for 3GPP Access (GTP based).

For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.2 apply with the following modification:

• For the 3GPP Access (PMIP-based) the enforcement of the Authorized Default EPS Bearer QoS is not performed by the PCEF.

In the 3GPP Access (PMIP-based) the BBERF enforces QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.7.3 with the following additions:

• Authorized Default EPS Bearer QoS Enforcement. The BBERF receives the authorized QoS for the default bearer over Gxx interface. The BBERF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The BBERF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any QoS Rule operation requested by the PCRF.

The PCRF may provide the following parameters in the Acknowledgement of the IP-CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN AMBR.

The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN AMBR, User Location Information (if received from the BBERF), user GSG information (if received from the BBERF).