2. If case 2b applies (as defined in clause 4.0), the BBERF-initiated Gateway Control Session Termination procedure as defined in clause 4.4.4 (BBERF-Initiated Gateway Control Session Termination) is initiated.

M

NC

3. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the PCEF sends a CCR to the H-PCRF, indicating the IP-CAN Session termination. The PCEF requests the termination of the Gx session using the CC-Request-Type AVP set to the value TERMINATION_REQUEST. If the usage monitoring is enabled, the PCEF informs the H-PCRF about the resources that have been consumed by the user since the last report.

M

C

If the Required-Access-Info AVP is included in any PCC Rule, the PCEF informs the H-PCRF about the access network information.

M

C

If RAN-NAS-Cause feature is supported, the PCEF informs the H-PCRF about the access network information and the failure cause(s), if available.

C

NC

For the case when the UE is roaming in a Visited Access scenario, steps 3a~3b are executed instead of step 3:

3a. The PCEF sends a CCR to the V-PCRF, indicating the IP-CAN Session termination. The PCEF requests the termination of the Gx session using the CC-Request-Type AVP set to the value TERMINATION_REQUEST. If the usage monitoring is enabled, the PCEF informs the V-PCRF about the resources that have been consumed by the user since the last report. If the Required-Access-Info AVP is included in any PCC Rule, the PCEF informs the V-PCRF about access network information.

3b. If there is an active TDF session between the TDF and the V-PCRF, for roaming UE with visited access, the TDF Session termination is initiated as defined in Section 4.6.2. For this case, the PCRF described in Section 4.6.2 acts as a V-PCRF.

3c. If congestion reporting is active for the user id and PDN id, for roaming UE with visited access, the V-PCRF initiates a UE context removal as defined in clause 4.8.5.

3d. The V-PCRF sends the CCR to the H-PCRF. If case 2b or case 1 applies and this is the last subsession associated with the S9 session, the V-PCRF sends a CCR to the H-PCRF to request the termination of the S9 session using the CC-Request-Type AVP set to the value TERMINATION_REQUEST. Otherwise, the VPCRF sends a CCR to the H-PCRF with a CC-Request-Type AVP set to the value UPDATE_REQUEST and a Subsession-Enforcement-Info within which the Subsession-Operation AVP set to value TERMINATION to request the termination of the conresponding S9 subsession.

Op

PC

S9 interface is not supported.

4. The H-PCRF identifies AF sessions that are bound to IP flows of the removed IP-CAN Session.

M

C

When the SAPC receives a CCR Termination from the PCEF, the SAPC removes the IP-CAN session and also the associated AF sessions.

5. The PCRF acknowledges the session termination by sending a Diameter CCA message.

M

C

7. If there is an active TDF session between the TDF and the H-PCRF, for non-roaming UE/roaming UE with home routed access, the TDF Session termination is initiated as defined in Section 4.6.2.

Op

C

8.If congestion reporting is active for the user id and PDN id, for non-roaming UE or UE is roaming in home routed case, the H-PCRF initiates a UE context removal as defined in clause 4.8.5.

Op

NC

9. The H-PCRF indicates the session abort to the H-AF by sending a Diameter ASR message to the H-AF.

M

C

10. The H-AF responds by sending an ASA to the H-PCRF.

M

C

11. The H-AF sends an STR to the H-PCRF to indicate that the session has been terminated.

M

C

12. The H-PCRF responds by sending a Diameter STA message to the AF.

M

C

If the provided PCC rules are related to an AF session associated with a sponsor, usage thresholds were provided by the H-AF earlier, and the H-PCRF has usage data that has not yet been reported to the H-AF, the H-PCRF informs the H-AF about the resources that have been consumed by the user since the last report. If the BBERF in step 2 or PCEF in step 3 reports the access network information and if the AF requested the H-PCRF to report access network information in step 10 previously and/or the RAN-NAS-Cause feature is supported, the H-PCRF informs the H-AF about the access network information and/or RAN/NAS release cause(s) if available.

M

PC

The SAPC does not support sponsor service and RAN-NAS-Cause feature.

13. If this is the last IP-CAN session for this subscriber the Final Spending Limit Report Request as defined in clause 4.7.3 is sent.

M

C

14. If case 2a applies (as defined in clause 4.0), the Gateway Control and QoS Rules Provision procedure as defined in clause 4.4.3 (Gateway Control and QoS Rules Provision) may be initiated to remove the QoS rules associated with the IP-CAN session being terminated. This applies e.g. in case the Gateway Control Session remains to serve other IP-CAN sessions. Alternatively, if UE acquires a care of address (CoA) that is used for the S2c reference point and the H-PCRF determines that all QoS rules are to be removed and the Gateway Control Session to be terminated, the PCRF initiated Gateway Control Session Termination procedure as defined in clause 4.4.4 (PCRF-Initiated Gateway Control Session Termination) is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP-CAN session.

M

NC

15. The H-PCRF sends a cancellation notification request to the SPR if it has subscribed such notification.

The H-PCRF stores the remaining usage allowance in the SPR if all IP-CAN sessions of the user to the same APN are terminated. Step 14 may be initiated any time after step 5 or 5a (as applicable).

C

NC

17. If the H-PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the H-PCRF initiates the St session termination procedure to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix for the terminated IP-CAN session according to the subclause 4.9.3.

NOTE 5: Step 17 can be initiated any time after step 5.

C

NC

5 - 7. Same as Steps 3~5 in figure 4.2.1.1.1.

See steps 2-5 in Table 3

8 - 14. Same as Steps 7~15 in figure 4.2.1.1.1.

See steps 7-15 in Table 3

1. The H-PCRF detects that the termination of an IP-CAN Session is required.

M

C

2. The H-PCRF sends a Diameter RAR including the Session-Release-Cause AVP to request that the PCEF terminates the IP CAN session.

M

C

For the case when the UE is roaming in a Visited Access scenario, steps 2a~2b are executed instead of step 2:

2a. If case 2b or case 1 applies and the subsession being terminated is the last subsession over S9, the H-PCRF sends a RAR including the Session-Release-Cause AVP to the V-PCRF to indicate the termination of the S9 session. Otherwise, the H-PCRF sends a RAR to the V-PCRF including the Subsession-Decision-Info AVP with the Session-Release-Cause AVP to indicate the request for terminating the S9 subsession corresponding to the IP-CAN session.

2b. The V-PCRF sends a RAR including the Session-Release-Cause AVP to the PCEF.

M

NC

4. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the PCEF sends a RAA to acknowledge the RAR. For the case when the UE is roaming in a Visited Access scenario, steps 4a~4b are executed instead of step 4:

4a. The PCEF sends a RAA to the V-PCRF.

4b. The V-PCRF sends a RAA to the H-PCRF and acknowledges the request for terminating the S9 session or the S9 subsession corresponding to the IP-CAN session.

M

C

S9 is not supported

1. The H-PCRF receives an internal or external trigger to re-evaluate PCC Rules and policy decision for an IP-CAN Session. Possible external trigger events are described in clause 4.3.1.2.

In addition, this procedure is triggered by:

- PCEF subscribed event

- SPR subscription data modification (e.g. change in MPS EPS Priority, MPS Priority Level and/or IMS Signalling Priority).

- OCS status of a policy counter identifier(s) has changed and the PCRF requested notification for spending limits apply.

- Application detection information report from TDF.

M

C

2. The H-PCRF selects the PCC Rule(s) to be installed, modified or removed for the IP-CAN Session. In case of PCEF supporting Application Detection and Control feature, some of those PCC rules may be used for application detection and control. The HPCRF may also update the policy decision by defining an authorized QoS and enable or disable the service flow(s) of PCC Rules. If the BBERF/PCEF controls the binding of IP-CAN bearers, the H-PCRF may add or change QoS information per QCI applicable to that IP-CAN session. In case of TDF, the H-PCRF selects the applicable ADC rules for the solicited application reporting with a TDF.

M

PC

The SAPC does not support BBERF interaction.

If NBIFOM applies to the IP-CAN session and Network-initiated mode is selected, the H-PCRF determines the access that is to be used for the transfer of traffic and include the allowed access type in the PCC rules. If NBIFOM applies to the IP-CAN session, the H-PCRF determines one access is to be removed from multi access IP-CAN session.

C

NC

3. The H-PCRF stores the updated PCC Rules and ADC rules if available.

M

C

4. Step 4 is only applicable if the Bearer Control Mode (BCM) selected is UE-only or, for UE/NW the PCRF determines that UE mode applies for the affected PCC Rules, and the PCRF receives an external trigger from the AF.

C

NC

The PCRF may start a timer to wait for a UE requested bearer resource initiation, modification or removal procedure initiated by the UE, as depicted in figure 4.3.2.1.1 or figure 4.3.2.2.1.

If a UE requested bearer resource initiation, modification or termination procedure initiated by the terminal is received for the affected PCC rules while the timer is running, all subsequent steps in the present figure shall not be executed and, for case 1, the steps in figure 4.3.2.1.1 (on provisioning based on PULL procedure at PCEF –initiated IP-CAN session modification when the AF is located in the HPLMN), 4.3.2.2.1 (on provisioning based on PULL procedure at PCEF-initiated IP-CAN session modification when the AF is located in the VPLMN) and for cases 2a and 2b, the steps in figure 4.4.2.1.1 (Home Routed case) or 4.4.2.2.1 (Visited Access case) shall be executed instead.

Otherwise, the PCRF shall proceed with the subsequent steps (provisioning based on PUSH procedure) in the present figure after timer expiry.

NOTE 1: For IMS Emergency session step 4 is not applicable.

Op

NC

5. For case 2a and 2b, if Gxx applies for the IP-CAN session and the user is not roaming, or the user is roaming in a Home Routed scenario or a Visited Access scenario for case 2a when the available QoS rule are not related to any IP-CAN session, the H-PCRF may initiate Gateway Control and QoS rules provisioning procedures described in clause 4.4.3.

NOTE 2: This step is not executed if this procedure is triggered by PCEF subscribed events and/or credit re-authorisation triggers reported by the BBERF.

Op

NC

6. The H-PCRF sends a Diameter RAR to request that the PCEF installs, modifies or removes PCC Rules and updates the policy decision, or to report PCEF subscribed events and/or credit re-authorisation triggers reported by the BBERF. The report includes the User Location Information and the User CSG Information (If received from the BBERF)

M

PC

The SAPC does not support BBERF interaction.

If the provided PCC rules are related to an AF session associated with a sponsor, the H-PCRF includes, in the Charging-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that it received from the AF if the Reporting-Level AVP is set to the value SPONSORED_CONNECTIVITY_LEVEL and, if AF provided the application usage thresholds, the Usage-Monitoring-Information AVP.

M

NC

If the AF requests the access network information, the H-PCRF includes Required-Access-Info AVP in the Charging-Rule-Definition AVP and/or Charging-Rule-Remove AVP. In addition, the H-PCRF includes the Event-Trigger set to the value "ACCESS_NETWORK_INFO_REPORT" if not provided yet.

Op

NC

If the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP are provided within the Media-Component-Description AVP, the PCRF may apply the mechanisms for resource sharing as specified at 3GPP TS 29.212 [9]. The PCRF includes the Removal-Of-Access AVP set to the value REMOVAL_OF_ACCESS (0) and the IP-CAN-Type AVP set to the value of removed access to remove one access from the multi access IP-CAN session.

Op

NC

If the H-PCRF subscribes the change of UE presence in Presence Reporting Area, the H-PCRF may provide the Presence Reporting Area Information to the PCEF.

Op

C

6a. The H-PCRF sends a Diameter RAR to the V-PCRF to request that the PCEF installs, modifies or removes PCC Rules and updates the policy decision. In the case of VPLMN supporting Application Detection and Control feature for solicited application reporting, some of those PCC Rules may be used for application detection and control. If the provided PCC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the Charging-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that it received from the AF if the Reporting-Level AVP is set to the value SPONSORED_CONNECTIVITY_LEVEL and, if AF provided the application usage thresholds, the Usage-Monitoring-Information AVP.

If the AF requests the access network information, the H-PCRF includes Required-Access-Info AVP in the Charging-Rule-Definition AVP and/or Charging-Rule-Remove AVP. In addition, the H-PCRF includes the Event-Trigger set to the value "ACCESS_NETWORK_INFO_REPORT" if not provided yet.

6b. The V-PCRF enforces visited operator policies regarding PCC rules requested by the H-PCRF based on roaming agreements or locally configured policy. In case of TDF, V-PCRF extracts the ADC rules from the PCC Rules received from the H-PCRF and stores them. NOTE: If the V-PCRF rejects provisioned PCC rules received from the H-PCRF, the remaining steps in this call flow are not followed. Instead, the V-PCRF shall notify the H-PCRF by sending a Diameter RAA, including the Experimental-Result-Code AVP set to the value PCC_RULE_EVENT, identify the failed PCC rules as specified in TS 29.212 , and additionally may provide the acceptable QoS Information for the service.

6c. In case of TDF, solicited application reporting, for roaming UE with visited access, the V-PCRF initiates the TDF session establishment, modification, or termination. If the provided ADC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the ADC-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that are received from the AF if the Reporting-Level AVP is set to the value SPONSORED_CONNECTIVITY_LEVEL. Additionally, if the AF provided the application usage thresholds, the H-PCRF includes the Usage-Monitoring-Information AVP. If the last ADC rule is deactivated, the V-PCRF requests the TDF to terminate the TDF session toward the V-PCRF as defined in clause 4.6.2. If there is no active TDF session between the TDF and the V-PCRF, the V-PCRF requests the TDF to establish the TDF session towards V-PCRF and provides ADC Rules to the TDF as defined in clause 4.6.1. If there is already an active TDF session between the TDF and the V-PCRF, the V-PCRF provides the ADC rules to the TDF as defined in clause 4.6.3.2.

6d. For case 2a and 2b, if Gxx applies for the IP-CAN session and the user is roaming in a Visited Access scenario when Gxx is hidden, V-PCRF will derive the QoS rules from the PCC rules. The V-PCRF will initiate a Gateway Control and QoS Rule procedure as described in clause 4.4.3 to install, modify or remove QoS rules and optionally subscribe to new events in the BBERF.

6e. The BBERF installs, modifies or removes the identified QoS Rules. The BBERF also enforces the authorized QoS of the corresponding QoS Rules.

6f. The V-PCRF sends a Diameter RAR to request that the PCEF installs, modifies or removes PCC Rules.

M

PC

The SAPC does not support BBERF interaction.

8. The PCEF sends a Diameter RAA to acknowledge the RAR. The PCEF informs the H-PCRF about the outcome of the PCC rule operation

M

C

When the UE is roaming, steps a ~ d are executed instead of step 8:

a. The BBERF informs the V-PCRF about the outcome of the operation by sending a Diameter RAA command. b. The PCEF informs the V-PCRF about the outcome of the PCC rule operation by sending a Diameter RAA command. c. The V-PCRF stores the received information. d. The V-PCRF informs the H-PCRF about the outcome of the operation by sending a Diameter RAA command.

M

NC

9. In case of TDF, solicited application reporting, for non-roaming UE/roaming UE with home routed access, HPCRF initiates the TDF session establishment, modification, or termination. If the provided ADC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the ADC-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that are received from the AF if the Reporting-Level AVP is set to the value SPONSORED_CONNECTIVITY_LEVEL. Additionally, if the AF provided the application usage thresholds, the H-PCRF includes the Usage-Monitoring-Information AVP. If the last ADC rule is deactivated, the H-PCRF requests the TDF to terminate the TDF session toward the H-PCRF as defined in clause 4.6.2. If there is no active TDF session between the TDF and the H-PCRF, the H-PCRF requests the TDF to establish the TDF session towards H-PCRF and provides ADC Rules to the TDF as defined in clause 4.6.1. If there is already an active TDF session between the TDF and the H-PCRF, H-PCRF provides the ADC rules to the TDF as defined in clause 4.6.3.2.

Op

PC

Only predefined ADC rules supported.

TDF session termination is only requested when IP-CAN session is finished.

10. If traffic steering control over St applies, if the PCRF determines that the traffic steering control information needs to be provisioned for the IP-CAN session; the PCRF initiates the St session establishment procedure according to the subclause 4.9.1. If the PCRF determines that the traffic steering control information provisioned to the TSSF needs to be updated, the PCRF initiates the St session modification procedure according to the subclause 4.9.2. If the PCRF determines that the traffic steering control information is not needed for the IP-CAN session any more, the PCRF initiates the St session termination procedure according to the subclause 4.9.3.

C

NC

11. In case of spending limits, for non-roaming/roaming UE with both home routed and visited access, HPCRF initiates Initial/ Intermediate/ Final Spending Limit Report Request. The H-PCRF sends an Initial Spending Limit Report Request if this is the first time a status notification of policy counter is requested for the user as defined in clause 4.7.1. If the H-PCRF decides to modify the list of subscribed policy counters the HPCRF sends an Intermediate Spending Limit Report Request as defined in clause 4.7.2. If the H-PCRF decides to unsubscribe any future status notification of policy counters, it sends a Final Spending Limit Report Request to cancels the request for reporting the change of the status of the policy counters available at the OCS as defined in clause 4.7.3.

M

PC

The SAPC does not support Intermediate Spending Limit Report Request or Roaming Scenarios.

12. If usage monitoring is enabled and the H-PCRF either removed the last PCC rule applicable for certain monitoring key , disabled usage monitoring or requested usage report, the PCEF shall initiate an IP-CAN session modification procedure.

M

C

1. For case 2a and 2b, the BBERF may initiate Gateway Control and QoS rules request procedure described in subclause 4.4.2.

M

NC

3. The PCEF informs the H-PCRF about the IP-CAN session modification for non-roaming case and Home Routed roaming scenario. The PCEF sends a CCR command to the H-PCRF including the CC-Request-Type AVP set to the value “UPDATE_REQUEST”. For an IP-CAN Session modification where an existing IP-CAN bearer is modified, the PCEF supplies the specific event that caused the IP-CAN Session modification within the Event-Trigger AVP and the PCC rule name(s) and their status within the Charging-Rule-Report AVP.

M

C

For an IP-CAN Session modification where an existing IP-CAN bearer is terminated, the PCEF supplies the affected PCC rule name(s), their status set to inactive, the rule failure code and, if available, the RAN/NAS/TWAN/Untrusted WLAN cause(s) within the Charging-Rule-Report AVP.

M

PC

RAN/NAS/TWAN/Untrusted WLAN cause(s) are not supported by SAPC.

In the case where the UE initiates a resource modification request procedure, the PCEF includes the Packet-Filter-Information AVP, Packet-Filter-Operation AVP and QoS-Information AVP, if applicable.

M

NC

In the case of PCEF supporting Application Detection and Control feature, when the start or stop of the application’s traffic, identified by TDF-Application-Identifier, is detected, if PCRF has previously subscribed to the APPLICATION_START/APPLICATION_STOP Event-Triggers, the PCEF shall report the information regarding the detected application’s traffic in the Application-Detection-Information AVP in the CCR command.

M

C

3c. The V-PCRF sends a CCR command with the CC-Request-Type AVP set to “UPDATE_REQUEST” to the H-PCRF. The V-PCRF includes the Subsession-Enforcement-Info AVP and the assigned S9 subsession identifier within Subsession-Id AVP. The Subsession-Operation AVP is set to the value “MODIFICATION”.

M

NC

4. If the H-PCRF requires subscription-related information and does not have it, the PCRF sends a request to the SPR in order to receive the information.

M

C

5. The SPR replies with the subscription related information containing the information about the allowed service(s) and PCC Rules information.

M

C

The SAPC stores the PCC rules information in its internal database.

6. If the AF requested a notification of the corresponding event, the H-PCRF sends a Diameter RAR with the Specific-Action AVP set to indicate the event that caused the request.

M

C

If the session modification affected a sponsored data flow and the H-PCRF detects that the usage threshold provided by the AF has been reached, this message includes the accumulated usage in the Used-Service-Unit AVP within the Sponsored-Connectivity-Data AVP and the Specific-Action AVP set to the value USAGE_REPORT.

M

NC

7. If step 6 takes place, the AF may take the application specific procedure (e.g. for IMS refer to 3GPP TS 23.228 [59], replies with a Diameter RAA and may provide updated service information within. Additionally, the AF may terminate the Rx session as per subclause 4.3.1.2.3

Op

C

8-11. If all service data flows for an AF session are deleted, the AF session is terminated.

M

C

If the session modification affected a sponsored data flow and the H-PCRF detects the UE is roaming with home routed case, the H-PCRF initiates the AF session termination. If the IP-CAN session is associated with a sponsor, usage thresholds were provided by the AF earlier, and the H-PCRF has usage data that has not yet been reported to the AF, the H-PCRF informs the AF, in step 11, about the resources that have been consumed by the user since the last report.

M

NC

If RAN-NAS-Cause feature is supported and RAN/NAS/TWAN/Untrusted WLAN cause(s) and/or access network information were received in step 3, the H-PCRF sends this information to the AF in step 11.

M

NC

NOTE 2: Initial/intermediate/Final Spending Limit Report Request can be triggered at any time after this if PCRF, based on policy decisions, find the need to initialize, modify, or deactivate spending limit reporting for the subscriber according to subclause 4.7.1/2/3 respectively.

Op

PC

The SAPC does not support Intermediate Spending Limit Report Request or Roaming Scenarios.

12. The H-PCRF selects or generates PCC Rule(s) to be installed. The H-PCRF may also identify existing PCC rules that need to be modified or removed. In the case of VPLMN supporting Application Detection and Control feature for solicited application reporting, some of those PCC Rules may be used for application detection and control. The PCC Rules may relate to any of the matching AF sessions or may exist in the PCRF without matching to any AF session. The H-PCRF may also make a policy decision by deriving an authorized QoS and by deciding whether service data flows described in the PCC Rules are to be enabled or disabled. The H-PCRF may also update the ADC decisions and select the ADC rules to be installed, modified or removed for the IP-CAN session in the non-roaming case.

M

PC

Only predefined ADC rules supported.)

If the NBIFOM applies to the IP-CAN session, the PCRF can also make a decision of NBIFOM as defined in subclause 4.5.25.2 of 3GPP TS 29.212 [9].

C

NC

13. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the H-PCRF provisions the PCC Rules to the PCEF using CCA command. The H-PCRF also provides the selected Bearer Control Mode, if changed and applicable for the IP-CAN type. The PCRF may also provide a new list of event triggers for which the PCRF requires to be notified. The PCRF may provide QoS information within the APN-AMBR AVP and the Default-EPS-Bearer-QoS AVP. In the case of PCEF supporting Application Detection and Control feature, the H-PCRF may provision the PCC rules for application detection and control to the PCEF.

M

C

13a. The H-PCRF sends a Diameter CCA to the V-PCRF including the PCC Rules to be provisioned within the Subsession-Decision AVP, along with the S9 subsession identifier as received in step 3b within the Subsession-Id AVP. Other parameters listed in step 9 are also applicable here.

M

NC

13b. The V-PCRF validates the QoS parameters requested within the PCC Rules and enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. In case of TDF, the V-PCRF extracts and validates the ADC rules from the PCC rules received from the H-PCRF according to the local policy and roaming agreements if provided by the H-PCRF.

M

NC

NOTE: If the V-PCRF rejects provisioned PCC rules received from the H-PCRF, the remaining steps in this call flow are not followed. Instead, the V-PCRF shall notify the H-PCRF by sending a Diameter CCR, including the Experimental-Result-Code AVP set to the value PCC_RULE_EVENT, identify the failed PCC rules as specified in TS 29.215 [22], and additionally may provide the acceptable QoS Information for the service.

M

NC

13c. The V-PCRF provisions PCC rules to the PCEF by using CCA command. The parameters listed in step 13a are applicable here.

M

NC

13d. In case of TDF, solicited application reporting, the H-PCRF provisions the ADC rules to the TDF as defined in subclause 4.6.3.2. In case of TDF, unsolicited application reporting, the H-PCRF initiates the TDF session termination as defined in subclause 4.6.2 if the PCEF reported the UE_IP_ADDRESS_RELEASE to the H-PCRF and there is an active IPv4 address related TDF session for that IP-CAN session.

M

PC

Unsolicited application reporting not supported.

14. In case of TDF, solicited application reporting, the H-PCRF provisions the ADC rules to the TDF as defined in subclause 4.6.3.2. In case of TDF, unsolicited application reporting, the H-PCRF initiates the TDF session termination as defined in subclause 4.6.2 if the PCEF reported the UE_IP_ADDRESS_RELEASE to the H-PCRF and there is an active Ipv4 address related TDF session for that IP-CAN session.

M

PC

Unsolicited application reporting not supported

16. If traffic steering control over St applies, if the PCRF determines that the traffic steering control information needs to be provisioned for the IP-CAN session; the PCRF initiates the St session establishment procedure according to the subclause 4.9.2. If the PCRF determines that the traffic steering control information provisioned to the TSSF needs to be updated, the PCRF initiates the St session modification procedure according to the subclause 4.9.3. If the PCRF determines that the traffic steering control information is not needed for the IP-CAN session any more, the PCRF initiates the St session termination procedure according to the subclause 4.9.2.

C

NC

18. If the PCRF requested to confirm that the resources associated to a PCC Rule have been successfully allocated or the resource release procedure has concluded, the PCEF-initiated IP-CAN session modification procedure is performed again starting from step 3.

M

C

19. For case 2a and 2b, the BBERF may initiate Gateway Control and QoS rules Provision procedure described in subclause 4.4.3.

Op

NC

1. TDF is triggered to report an event(s) (e.g. The TDF detects the start/stop of an application traffic that matches with one or more activated ADC rules that do not contain the Mute-Notification AVP) for a TDF session. For the start of traffic detection, in case the enforcement actions were provided as a part of ADC rules, the TDF enforces corresponding actions for solicited application reporting.

M

C

2. The TDF sends a Diameter CCR to the PCRF with the CC-Request-Type AVP set to the value UPDATE_REQUEST to report an event. For the start of traffic detection, if PCRF has previously subscribed to the APPLICATION_START/APPLICATION_STOP Event-Triggers, the TDF includes TDF-Application-Identifier AVP, the Flow-Information AVP of the detected application when service data flow descriptions are deducible, within the Application-Detection-Information AVP and sets the event trigger value with APPLICATION_START. If Flow-Information AVP is included, the TDF-Application-Instance-Identifier shall also be included within the Application-Detection-Information AVP in order to allow correlation of APPLICATION_START. For the stop of traffic detection, if PCRF has previously subscribed to the APPLICATION_START/APPLICATION_STOP Event-Triggers, the TDF includes TDF-Application-Identifier AVP, the TDF-Application-Instance-Identifier AVP, if provided in the report of the start of application traffic detection within the Application-Detection-Information AVP and sets the event trigger value with APPLICATION_STOP. For the solicited application reporting, if usage monitoring is enabled and the usage threshold is reached or the PCRF removes the last ADC rule applicable for certain monitoring key or disables usage monitoring or requests usage report, the TDF may inform the PCRF about the corresponding usage that have been consumed by the user since the last report.

M

PC

Usage monitoring not supported in TDF interactions

3. The PCRF stores the information, received in the Diameter CCR and makes the PCC/QoS and – in the solicited reporting case – ADC decisions.

M

C

4. The PCRF acknowledges to the TDF by sending a Diameter CCA. For the solicited application reporting, the PCRF may provide a new ADC decisions by including the ADC-Rule-Install AVP and/or ADC-Rule-Remove AVP to the TDF within this acknowledge.

M

C

5. For the solicited application reporting, the TDF installs, modifies and removes the ADC rules according the new ADC decisions provided in step 4.

M

PC

Only predefined ADC rules supported (not possible to be modified by SAPC)

NOTE: If the installation or modification of one or more ADC rules fails, the TDF reports the failure to the PCRF as defined in clause 4b.5.5 of 3GPP TS 29.212 [9].

M

NC

1. The PCRF receives an internal or external trigger (e.g. the subscriber’s profile configuration is changed) to update the ADC rule or notify the event occurred at the PCEF/BBERF for a TDF session.

M

PC

BBERF is not supported by the SAPC.

Event-Report-Indication not supported

2. The PCRF sends a Diameter RAR to provide a new ADC decision by including the ADC-Rule-Install AVP and/or ADC-Rule-Remove AVP or notify the event occurred at the PCEF/BBERF by including the Event-Report-Indication AVP.

M

PC

BBERF is not supported by the SAPC.

Event-Report-Indication AVP not supported

3. The TDF stores the information, received in the Diameter RAR. The TDF installs, modifies and removes the ADC rules according the new ADC decisions provided in step 2.

NR

Only predefined ADC rules supported (not possible to be modified by SAPC)

4. The TDF acknowledges to the PCRF by sending a Diameter RAA to inform the PCRF about the outcome of the actions related to the decision(s).

NR

If the timer in step 4 expires and the PCRF still requires additional filter information coming from the UE in order to decide on bearer binding for new PCC rules to be installed, all subsequent steps in figure 4.3.1.1.1 shall not be executed, and further reactions of the PCRF are left unspecified. As a possible option, the PCRF could abort the AF session.

When the PCRF performs the bearer binding, once the PCC rules are selected, the PCRF identifies the IP-CAN bearer for each of the PCC rules and the authorized QoS.

The PCRF may provision PCC Rules and authorized QoS for several IP-CAN Bearers within the same RAR command

Op

NC