E.5 PCC procedures

29.2123GPPPolicy and Charging Control (PCC)Reference pointsRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

E.5.1 PCC procedures over Gx reference point

The PCC procedures over Gx reference point defined in clause 4.5 shall apply. In addition, to support interworking with Fixed Broadband Access networks, during the IP-CAN session establishment or modification, the PCEF may include

– In WLAN scenario, when GTP-based S2b and trusted S2c is used, the UE Local IP Address within the UE-Local-IP-Address AVP, and the UDP source port number of IPSec tunnel or the UDP source port number of DSMIPv6 binding update signalling within the UDP-Source-Port AVP if available for case 1 and the PDN-GW address used as the endpoint of the DSMIPv6 Ipv4 user plane tunnel with the UE within the 3GPP-GGSN-Address (Ipv4 address) or the PDN-GW address used as the endpoint of the DSMIPv6 Ipv6 user plane tunnel with the UE within the 3GPP-GGSN-Ipv6-Address (Ipv6 address) for trusted S2c access or the ePDG IP address derived from the ePDG IP address IE as defined in clause 7.2.1 of 3GPP TS 29.274 [22] within the AN-GW-Address for GTP-based S2b. The event trigger set to the value UE_LOCAL_IP_ADDRESS_CHANGE shall be included when the UE local IP address and/or UDP source port number are changed. The IP-CAN-Type is set to the value "Non-3GPP-EPS".

– In H(e)NB scenario, when GTP-based S5/S8 is used, the H(e)NB local IP Address within the HeNB-Local-IP-Address and UDP source port number of IPSec tunnel within UDP-Source-Port AVP if available for case 1 in H(e)NB scenario when GTP-base S5/S8 is used. The event trigger set to the value H(E)NB_LOCAL_IP_ADDRESS_CHANGE shall be included when the H(e)NB local IP address and/or UDP source port number are changed. The IP-CAN-Type is set to the value "3GPP-EPS".

E.5.2 PCC procedures over Gxx reference point

E.5.2.1 Gateway Control Session Establishment

For the case 2a and case 2b of WLAN scenario, the BBERF (ePDG) may initiate a Gateway Control Session Establishment with the PCRF if it is aware that a 3GPP UE has attached via the BBF access and also learns the IMSI of the subscriber.

The BBERF(ePDG) shall send a CCR command with the CC-Request-Type AVP set to the value "INITIAL_REQUEST", the CCR command shall include the IMSI within the Subscription-Id AVP, the type of IP-CAN within the IP-CAN-Type AVP set to the value "Non-3GPP-EPS", the PDN information within the Called-Station-ID AVP if available, the UE Local IP Address within the UE-Local-IP-Address AVP, the UDP source port number of IPSec tunnel within the UDP-Source-Port AVP if available and the ePDG IP address used as IPSec tunnel endpoint with the UE within the AN-GW-Address AVP.

For the case 2b of H(e)NB scenario, the procedure defined in clause 4a.5.1 applies. In addition, to support interworking with Fixed Broadband Access networks, during the Gateway Control session establishment, the BBERF(S-GW) may include the H(e)NB local IP Address within the HeNB-Local-IP-Address and UDP source port number of IPSec tunnel within UDP-Source-Port AVP if available.

E.5.2.2 Gateway Control Session Modification

For the case 2a and case 2b of WLAN scenario, the BBERF(ePDG) may initiate a Gateway Control session modification with the PCRF if the Local UE IP address and/or the UDP source port number if available are changed.

The BBERF(ePDG) shall send a CCR command with the CC-Request-Type AVP set to the value "UPDATE_REQUEST", the CCR command shall include the UE Local IP Address within the UE-Local-IP-Address AVP and/or the UDP source port number of Ipsec tunnel within the UDP-Source-Port AVP, and the event trigger set to the value UE_LOCAL_IP_ADDRESS_CHANGE.

For the case 2b of H(e)NB scenario, the procedure defined in clause 4a.5.1 applies. In addition, to support interworking with Fixed Broadband Access networks, during the Gateway Control session modification, the BBERF(S-GW) may include the H(e)NB local IP Address within the HeNB-Local-IP-Address and/or UDP source port number of IPSec tunnel within UDP-Source-Port AVP if available, and the event trigger set to the value H(E)NB_LOCAL_IP_ADDRESS_CHANGE.

E.5.2.3 Gateway Control Session Termination

Procedure defined in clause 4a.5.3 shall apply.

E.5.2.4 Request of Gateway Control Session Termination

Procedure defined in clause 4a.5.4 shall apply.

NOTE: BBERF(ePDG) does not need to remove/deactivate the QoS rule because the QoS rule are not applicable to the BBERF(ePDG).

E.5.3 S15 Procedures

E.5.3.1 S15 Session Establishment

The HNB GW initiates an S15 Session Establishment with the PCRF if the HNB registers to the HNB GW.

The HNB GW shall send a CC-Request with the CC-Request-Type AVP set to the value "INITIAL_REQUEST", The CCR command shall include the HNB Local IP address within the HeNB-Local-IP-Address AVP and the UDP source port number of IPSec tunnel within the UDP-Source-Port AVP if available.

When the PCRF receives the CC-Request, it shall acknowledge this message by sending a CC-Answer to the HNB GW.

E.5.3.2 S15 Session Modification

E.5.3.2.1 S15 Session Modification initiated by the HNB GW

The HNB GW initiates an S15 session modification with the PCRF if the HNB GW receives the RAB assignment message to request, modify and cancel the resource for the CS service.

The HNB GW shall send a CCR command with the CC-Request-Type AVP set to the value "UPDATE_REQUEST".

When the RAB assignment requests to allocate new resources, the HNB GW shall include the requested QoS information which is derived from the RAB message within the QoS-Information AVP, and the QoS request identifier assigned by the HNB GW within CS-Service-QoS-Request-Identifier AVP in the CCR command.

When the RAB assignment requests to modify existing resources, the HNB GW shall set the CS-Service-QoS-Request-Operation AVP to "MODIFICATION", the HNB GW shall also include the requested QoS information which is derived from the RAB message within the QoS-Information AVP and the QoS request identifier assigned by the HNB GW within CS-Service-QoS-Request-Identifier AVP in the CCR command.

When the RAB assignment requests to delete resources the HNB GW shall set the CS-Service-QoS-Request-Operation AVP to "DELETION", and shall also include the QoS request identifier assigned by the HNB GW within CS-Service-QoS-Request-Identifier AVP in the CCR command.

E.5.3.2.2 S15 Session Modification initiated by the PCRF

The PCRF initiates an S15 session modification with the HNB GW if the PCRF receives the QoS rule failure report with the PCC-Rule-Status AVP set to the value "INACTIVE" from the BPCF.

The PCRF shall include the CS-Service-Resource-Report AVP in the RAR command with the CS-Service-Resource-Result-Operation AVP set to the value "DELETION", the CS-Service-QoS-Request-Identifier AVP containing the QoS request identifier corresponding to the QoS rule reported by the BPCF and the CS-Service-Resource-Failure-Cause AVP indicating the reason why the resource is released.

The HNB GW shall initiate RAB modification or RAB release procedure to release the corresponding resource allocated in the 3GPP network as defined in 3GPP TS 23.060 [17].

E.5.3.3 S15 Session Termination

The HNB GW initiates the S15 session termination with the PCRF if the HNB GW initiates deregistration for the HNB or receives the deregistration request from the HNB.

The HNB GW shall send a CC-Request with CC-Request-Type AVP set to the value "TERMINATION_REQUEST".

If the HNB GW needs to send an S15 Session termination request towards a PCRF which is known to have restarted since the S15 Session establishment, the HNB GW should not send CC-Request to inform the PCRF.

When the PCRF receives the CC-Request, it shall acknowledge this message by sending a CC-Answer to the HNB GW.

E.5.4 ADC procedures over Sd reference point for solicited application reporting

E.5.4.1 TDF session establishment

If PCRF decides, based on subscriber’s profile configuration, that the TDF session should be established with the TDF per corresponding IP-CAN session, during the IP-CAN session establishment or at any point of time when the PCRF decides that the session with TDF is to be established (e.g. subscriber profile changes), the PCRF shall indicate via the Sd reference point, the ADC rules to be applied at the TDF. The TDF-Information AVP shall be either received over S9a within initial CC-Request received from BPCF or pre-provisioned at PCRF.

NOTE: In case the TDF-Information is pre-provisioned in the PCRF and also the value is received in CC-Request from the BPCF, the value received in CC-Request takes precedence over the pre-provisioned value.

When establishing the session with the TDF, the PCRF shall send a TS-Request with the PDN information (NSWO-APN), if available, within the Called-Station-Id AVP, the UE Local IP address within the Framed-IP-Address AVP and/or the Framed-Ipv6-Prefix AVP.

E.5.5 ADC procedures over Sd reference point for unsolicited application reporting

E.5.5.1 General

For provisioning of ADC Rules and Application Detection Information reporting the procedures described in clauses 4b.5a.1 and 4b.5a.2 apply respectively.

For the request of TDF Session Termination, the procedure described in clause 4b.5a.3 applies, with the exemption that the release of Ipv4 address in a dual stack scenario is notified with the S9a* Session Termination for that Ipv4 address.

E.5.5.2 TDF session to S9a* session linking

When the PCRF receives the CCR command with the CC-Request-Type set to the value "INITIAL_REQUEST" over Sd reference point, the PCRF links the TDF session to an S9a* session, if the Ipv4 address or Ipv6 address of the TDF session matches the UE local IP address of the S9a* session. The PDN information (i.e NSWO-APN) if available in the Called-Station-Id AVP may also be used for this session linking.

When the PCRF checks if APNs within Called-Station-Id AVPs match each other, the PCRF shall apply the APN matching procedures in Annex H of 3GPP TS 29.213 [8].

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.

NOTE 1: In a dual-stack scenario where a 3GPP UE in the Broadband Fixed Access Network is allocated an Ipv6 address/prefix and an Ipv4 address, this would result in two S9a* sessions. The PCRF would link the Ipv4 address related TDF session and Ipv6 address related TDF session for the same UE to the different S9a* sessions.

NOTE 2: In the scenario where the TDF performs initial Application Detection on multiple simultaneous traffic flows for the same Ipv6 prefix (i.e. two or more traffic flows from Ipv6 addresses of the same IP-CAN session) the TDF could not be aware that those flows belong to the same IP-CAN session until a response is received from the PCRF, containing the Ipv6 prefix. This leads to using separate TDF sessions for the Ipv6 addresses for the same IP-CAN session. The TDF reports new application detection information related to that Ipv6 prefix via any of the TDF sessions at a later stage.