The SAPC supporting ADC function instructs the PCEF to detect and report application start and stop events. Based on this report, the SAPC makes policy decisions and sends enforcement actions to the PCEF.

This function enables the operator to have real-time control over the services of the users. The operator can take the following immediate actions based on application status:

• Change of service authorization

• QoS modification

• Bandwidth management

• Service charging control

• User notifications

This function also supports redirecting the detected applications to another destination, or muting notifications to the SAPC for specific applications.

• For details on application redirection, see ADC Redirection Control.

• For details on mute notification, see ADC Mute Notification Control.

This functionality is provided through the Gx interface. The SAPC can enable PCEFs for ADC support. The PCEF detects the application traffic using static or preconfigured PCC rules enhanced with ADC.

• A static PCC rule enhanced with ADC is a PCC rule locally configured in the PCEF and dynamically activated or deactivated by the SAPC. Its Traffic Detection Function (TDF) application identifier (used to reference an application detection filter, which is predefined in the PCEF), redirection, and mute notification information are locally configured in the PCEF.

• A preconfigured PCC rule enhanced with ADC is a PCC rule predefined in the SAPC. Apart from rest of data of a PCC rule, it includes TDF application identifier, redirection and mute notification information configured in the SAPC, but does not include Service Data Flow Filters.

Figure 1 illustrates an example of QoS upgrade based on application detection. The SAPC makes QoS decisions depending on application events reported by the PCEF.

Figure 1   QoS upgrade based on Application Detection start

1. The default bearer is established with negotiated QoS.

2. The UE starts the application traffic.

3. The GGSN (PGW) detects and reports an application start event together with the flow information to the SAPC.

4. The SAPC evaluates the QoS and sends new QoS to the GGSN (PGW).

5. The dedicated bearer with new QoS is established.

6. The End-to-End application traffic is established.

The SAPC authorizes PCC rules enhanced with ADC together with other PCC rules by evaluating Access and Charging Control, as described in Access and Charging Control (Gx), including:

• Service Selection

• Service Authorization

• Service Qualification

The SAPC can instruct the PCEF to redirect the uplink traffic of specific applications to another destination based on conditions such as Time of Day (ToD). The SAPC can also disable the redirection of these applications.

The SAPC sends redirection information for preconfigured PCC rules enhanced with ADC including type and address of a redirection server and an indication to enable or disable redirection. The type of server address can be IPv4 address, IPv6 address, URL, or SIP URI.

If the redirection server address is not provided by the SAPC, the server address preconfigured in the PCEF for this PCC rule is used instead.

The SAPC selects the redirection profile for a PCC rule enhanced with ADC by evaluating ADC Redirection policies according to the following precedence allocation:

1. Subject policy locator.

2. Subject group policy locator. All the active subscriber groups are considered.

   Therefore configure Dynamic Group Selection policies to evaluate only the desired subscriber group policies.

3. Global policy locator.

In case there are conflicts among the rules within a policy, the result for the policy depends on the rule combining algorithm configured. See Solving Policies Conflicts section in Subscription and Policy Management for further information.

If there are no configured policies or the policies are not fulfilled, the SAPC obtains the ADC Redirection information provisioned statically for the service.

If ADC Redirection cannot be selected either dynamically or statically, the SAPC does not request to redirect the traffic.

The SAPC can instruct the PCEF to mute application notifications associated with preconfigured PCC rules enhanced with ADC. It can be used if the enforcement action to be applied for the application is access control or bandwidth limitation to save event notifications.

ADC Mute Notification can only be set at PCC rule installation and it cannot be updated during the lifetime of the PCC rule.

The SAPC selects the mute status for PCC rules enhanced with ADC by evaluating ADC Mute Notification policies according to the following precedence allocation:

1. Subject policy locator.

2. Subject group policy locator. All the active subscriber groups are considered.

   Therefore configure Dynamic Group Selection policies to evaluate only the desired subscriber group policies.

3. Global policy locator.

In case there are conflicts among the rules within a policy, the result for the policy depends on the rule combining algorithm configured. See Solving Policies Conflicts section in Subscription and Policy Management for further information.

If there are no configured policies or the policies are not fulfilled, the SAPC obtains the mute status provisioned statically for the service.

If ADC Mute Notification cannot be selected either dynamically or statically, the SAPC does not request the PCEF to mute the application notifications.

The PCEF enhanced with ADC performs the application reporting if the following conditions are met:

• The SAPC subscribes to application start and application stop event triggers, which indicate the start and stop of the application traffic.

• The SAPC activates a static PCC rule with ADC configured in the PCEF, or the SAPC installs a preconfigured PCC rule with ADC to the PCEF.

• The PCC rule enhanced with ADC has not ADC Mute Notification information enabled.

The PCEF reports the application status at application level or service data flow level, by sending the application start and stop events and application detection information to the SAPC.

• If the reporting is at application level, the application detection information only includes a TDF application identifier used to reference the corresponding application.

• If the reporting is at service data flow level, besides the TDF application identifier, the application detection information includes flow information along with the TDF application instance identifier. Each application may have several service data flows, and each TDF application instance identifier maps to an individual flow or a group of flows.

During the lifetime of a PCC rule enhanced with ADC, the SAPC expects that the application start and stop events are reported at the same level (application level or service data flow level). The SAPC uses the TDF application identifier and TDF application instance identifiers received in the start and stop notifications reported by the PCEF to keep track of application traffic status. The SAPC does not handle flow information for PCC rules enhanced with ADC. It is the PCEF which knows about the flow information corresponding to the application or service traffic reported.

This traffic case shows an example of QoS control based on application traffic detection for PCC rules enhanced with ADC in an EPS deployment.

In this example, the QoS profile of the default bearer is upgraded/downgraded when PCEF detects and reports the application traffic start/stop of a previously installed PCC rule enhanced with ADC.

Figure 2   QoS Control based on Application Traffic Detection

IP-CAN session establishment

• 2. The UE attaches to the network, and the PCEF receives a notification about this situation.

• 3. The PCEF sends a CCR-Initial to the SAPC with the ADC bit set in the Supported-Features AVP, notifying that it supports ADC.

• 4. The SAPC performs session authorization including evaluation of Access and Charging Control, ADC Redirection Control, and ADC Mute Notification Control.

  The SAPC decides to install preconfigured PCC rules enhanced with ADC and to activate static PCC rules with ADC to the PCEF.

  Note:

  For the PCC rule precedence calculation, the SAPC does not increment the dynamic part of the precedence of the PCC rules enhanced with ADC as flow information is implicit in the TDF application identifier of the PCC rule with ADC. For more information regarding precedence calculation, refer to Access and Charging Control (Gx).

• 5. The SAPC answers with a CCA-Initial message to the PCEF including the following AVPs:

  • Supported-Features AVP with the ADC bit (6) set.

    Note:

    If the ADC bit is not received in the Supported-Features AVP, the ADC license is not active or ADC support is not configured for the PCEF, the SAPC answers back with the ADC bit unset, meaning ADC function is not enabled for the session.

  • Charging-Rule-Install AVP including the Charging-Rule-Name or Charging-Rule-Base-Name AVPs for static PCC rules enhanced with ADC, and the Charging-Rule-Definition AVP with the following additional AVPs for preconfigured PCC rules enhanced with ADC:

    • The TDF-Application-Identifier AVP that identifies the application for traffic detection.

      Note:

      If TDF-Application-Identifier AVP is included, then no Flow-Information AVP shall be included under the same Charging-Rule-Definition AVP. For static PCC rules, the TDF-Application-Identifier AVP is never downloaded to the PCEF.

    • The Redirect-Information AVP if any ADC Redirection profile is statically or dynamically provisioned for the service.

    • The Mute-Notification AVP if ADC Mute Notification "muted" value is statically or dynamically provisioned for the service.

  • The Event-Triggers AVP including the APPLICATION_START and APPLICATION_STOP events.

  • The Default-EPS-Bearer-QoS AVP with the QoS to apply to the default bearer.

• 6. The PCEF applies the downloaded QoS parameters to the default bearer and starts detecting traffic.

Upgrade default bearer QoS at application start detected

• 8. The subscriber starts application traffic that is to be detected by the PCC rule enhanced with ADC.

• 9. The PCEF reports the application traffic start event by sending a CCR-Update message with:

  • The Event-Triggers AVP including the APPLICATION_START event.

  • The Application-Detection-Information AVP including the TDF-Application-Identifier AVP.

    Note:

    When the service data flow descriptions are deducible, Application-Detection-Information AVP includes also the Flow-Information AVP for the detected application. If the Flow-Information AVP is included, the TDF-Application-Instance-Identifier AVP is also included. In any other case, the SAPC returns an error as described in Application Reporting Error Handling.

• 10. The SAPC reauthorizes the session and as result the QoS for the default bearer is upgraded.

• 11. The SAPC answers with a CCA-Update message to the PCEF, with the Default-EPS-Bearer-QoS AVP containing the upgraded QCI or ARP.

Downgrade default bearer QoS at application stop detected

• 13. The subscriber stops the application traffic detected by the PCC rule enhanced with ADC.

• 14. The PCEF reports the application stop event using a CCR-Update with:

  • The Event-Triggers AVP including the APPLICATION_STOP event.

  • The Application-Detection-Information AVP including the TDF-Application-Identifier AVP.

    Note:

    If an application start event was received with the TDF-Application-Instance-Identifier AVP, the corresponding stop event should also include the TDF-Application-Instance-Identifier AVP. In any other case, the SAPC returns an error as described in Application Reporting Error Handling.

• 15. The SAPC reevaluates the data to be applied to the subscriber and as result the QoS for the default bearer is downgraded.

• 16. The SAPC answers with a CCA-Update message to the PCEF, with the Default-EPS-Bearer-QoS AVP with the downgraded QCI or ARP.

This traffic case shows an example of ADC Redirection Control based on a ToD condition where the SAPC controls time.

In this example ADC Redirection Control is dynamically selected only during a specific range of time. The SAPC triggers the reauthorization of the session when ADC Redirection is to be applied.

Figure 3   ADC Redirection Control based on ToD conditions

IP-CAN session establishment

• 1-6. The steps are the same to steps 1–6 in QoS Control Based on Application Traffic Detection except step 5:

  In this case, the Charging-Rule-Definition AVP does not include the Redirect-Information AVP, as the time of day condition for ADC Redirection is not fulfilled at ADC Redirection policy evaluation.

Traffic is detected but not redirected

• 8. The subscriber starts service traffic that is detected by the PCC rules enhanced with ADC.

  The application traffic is not redirected, because ADC Redirection profile is not applicable at that time of day, but PCEF may report application traffic start and application traffic stop independently of application traffic being redirected or not.

ToD event. ADC Redirect profile downloaded

• 10. The time at which the ToD event is to be triggered arrives.

• 11. The SAPC reauthorizes the session and determines to apply an ADC Redirection profile to the previously installed PCC rule enhanced with ADC.

• 12. The SAPC sends a RAR message to the PCEF with the Charging-Rule-Definition AVP containing the applicable Charging-Rule-Name, TDF-Application-Identifier, and Redirect-Information AVP including:

  • Redirect-Support AVP set to REDIRECTION_ENABLED value.

  • Redirect-Address-Type AVP.

  • Redirect-Server-Address AVP.

  Note:

  When the Redirect-Server-Address AVP is not sent, the Redirect-Server-Address value configured in the PCEF is used. In case the Redirect-Server-Address value is neither configured in the PCEF, the PCEF reports an error to the SAPC. For further details, see PCC Rule Error Handling.

Subscriber traffic is redirected to the Redirect Server

• 13. From now on, the service traffic of PCC rule enhanced with ADC is redirected to the destination server where information about the accessed service may be offered.

This traffic case shows how ADC Mute Notification Control can be used when it is not needed to report traffic start/stop towards the SAPC, for example if it is only needed to perform bandwidth enforcement for the application.

In this example, the preconfigured PCC rule enhanced with ADC is downloaded with MUTE_REQUIRED value, so the PCEF does not report any service traffic start or stop for the PCC rule enhanced with ADC.

Figure 4   ADC Mute Notification Control

IP-CAN session establishment

• 1-5. The steps are the same to steps 1–5 in QoS Control Based on Application Traffic Detection except step 5:

  The Charging-Rule-Definition AVP includes the Mute-Notification AVP with MUTE_REQUIRED value as ADC Mute Notification profile is static or dynamic configured with "muted" value for the service.

Application traffic start is detected

• 7. The subscriber starts service traffic detected by the PCC rule enhanced with ADC.

• 8. The PCEF does not report the corresponding application traffic start to the SAPC as mute notification was requested.

Application traffic stop is detected

• 10. The subscriber stops service traffic detected by the PCC rule enhanced with ADC.

• 11. The PCEF does not report application stop to the SAPC as mute notification was requested.