1 Mobility Based Policy Control for Overlay Deployments (Smp) Function
1.1 Mobility Based Policy Control for Overlay Deployments (Smp) Overview
The Mobility Based Policy Control for Overlay Deployments function provides direct communication between the SAPC and the SGSN-MME by using the Smp interface. The SAPC works in Smp only mode and only serves the Smp traffic and other PCRFs in the network serve Gx, Rx, and Sy traffic.
This function enables the SGSN-MME to get the following policy decisions from the SAPC:
The function enables new innovative use cases, for example:
The following figure shows an overview of Network Elements providing Mobility Based Policy Control for Overlay Deployments function:
An Smp session is based on the PDN connection and established between the SGSN-MME and the SAPC.
The life cycle of an Smp session includes its establishment and termination. The SAPC does not support currently session modification nor reauthorization.
The SGSN-MME establishes an Smp session when:
| Note: |
In the case of inter SGSN-MME TAU or Handover session establishment,
the SGSN-MME sends only the International Mobile Subscriber Identity
(IMSI) to the SAPC. |
The SGSN-MME terminates an Smp session when:
1.2 Smp Session Access Control
Smp session Access Control is used to allow or reject Smp session establishment. Even if Smp session is rejected, SGSN-MME can continue with the IP-CAN session establishment towards the PGW.
Smp session Access Control policies are evaluated according to the following precedence allocation and applying permit overrides algorithm among them (that is, if any policy evaluates to true, the Smp session is authorized):
Subject policy locator.
Subject group policy locator. All the active subscriber groups are considered.
Therefore, it is recommended to configure Dynamic Group Selection policies to evaluate only the desired subscriber group policies.
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.
In case there are no Smp Session Access Control policies configured, the Smp session is authorized.
1.3 PDN-GW Selection
With the PDN-GW selection function, the SAPC can select the IP address (IPv4 and/or IPv6) and/or FQDN of a list of PDN-GWs for a UE when the UE attaches to the network.
| Note: |
The maximum number of PDN-GWs in a list is 32. |
The SAPC allows to select the list of PDN-GWs based on the following information:
The SAPC selects the list of PDN-GWs applying the mechanism for controls using both Policies and Qualification Data explained in Selection of Data to apply to the Subscriber section in Subscription and Policy Management.
The PDN-GW selection is performed only in the Smp session establishment procedure in the UE Attach or PDN connectivity scenario. During the Smp session lifetime, the selected list of PDN-GWs cannot be changed.
The following figure shows how to perform the PDN-GW selection:
1.4 SPID Selection
The SPID selection function enables the SAPC to control the camp priorities in Idle mode and inter-RAT/inter-frequency handover in Active mode for subscribers. This index is mapped by the eNodeB (E-UTRAN), RNC (UTRAN), or BSC (GERAN) to locally defined configuration. For more information, see 1 and 2. This increases the flexibility and service awareness for radio optimizations.
The SAPC allows to select the SPID based on the following information:
The SAPC selects the SPID applying the mechanism for controls using both Policies and Qualification Data explained in Selection of Data to apply to the Subscriber section in Subscription and Policy Management.
The following figure shows how to perform the SPID selection based on user information provided during the Smp session establishment:
1.5 Subscriber Profile Handling
The subscriber and subscriber group data can be stored in the SAPC internal or external database.
The SAPC uses the International Mobile Subscriber Identity (IMSI) to obtain the subscriber ID. This subscriber ID is used to access to the subscriber profile.
The subscriber can be associated with subscriber groups, having the possibility to specify the date and time, and the subscriber group priority.
Also, the SAPC supports dynamic selection of the subscribed groups by using Dynamic Group Selection policies.
The autoprovisioning and subscriber unknown functions are also applicable to Smp session procedures.
When any subscriber data is updated, the SAPC does not perform Smp reauthorization to check whether any data need to be added or removed, so updated subscriber data will be applied at next Smp session establishment.
When a subscriber is removed, the SAPC does not indicate the SGSN-MME to terminate the associated Smp sessions.
For more information, refer to Subscription and Policy Management.
2 Network Deployments
The SAPC supports the Mobility Based Policy Control for Overlay Deployments function in the following Network Elements:
3 Traffic Cases
This section describes traffic cases for Smp sessions.
The preconditions to all traffic cases are as follows:
Only the significant attributes for these traffic cases are described in the following sections. For more information on the supported interfaces, refer to the corresponding interface description documents.
| Note: |
The Session-Id AVP is mandatory
for all the messages in the Smp protocol. The Session-Id AVP is globally unique and used to identify
an Smp session. |
3.1 Smp Session Lifecycle at UE Attach or PDN Connectivity
This traffic case shows the Smp session lifecycle at the UE Attach or PDN connectivity scenario. The Smp session lifecycle includes Smp session establishment and termination.
The following figure shows the Diameter messages exchanged between the SAPC and the SGSN-MME.
Smp Session Establishment
Report Subscriber IP Address
Smp Session Termination
3.2 Smp Session Lifecycle at Inter SGSN-MME TAU or Handover
The traffic case shows the Smp session lifecycle at the Inter SGSN-MME TAU or Handover scenario. The Smp session lifecycle includes Smp session establishment and termination.
The following figure shows the Diameter messages exchanged between the SAPC and the SGSN-MME.
Smp Session Establishment
Old Smp Session Termination
For the subsequent signalling flows, see Smp Session Lifecycle at UE Attach or PDN Connectivity from Smp Session Termination.
3.3 Error Handling
|
Error Condition |
Action |
Code |
|---|---|---|
|
The SAPC determines that the SGSN-MME must continue the IP-CAN session and drop the Smp session. |
DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE = 4011 |
|
|
A request is received with an AVP with an invalid value in its data portion. |
The SAPC returns a CCA indicating an error, including a Failed-AVP AVP containing the AVPs that caused the failure. |
DIAMETER_INVALID_AVP_VALUE = 5004 |
|
When a request is received including an AVP that is not required to process that request, that AVP is ignored and the request is processed as usual. On the contrary, when a request does not include an AVP that is required to process such request, the SAPC returns a response including Result-Code DIAMETER_MISSING_AVP and the Failed-AVP AVP. |
DIAMETER_MISSING_AVP = 5005 |
|
|
This error is returned when the SAPC receives a request and detects an internal error which does not allow to continue processing a request, or the license is not active. |
DIAMETER_UNABLE_TO_COMPLY =5012 |
|
|
This error is returned when the subscriber specified in Subscription-Id AVP is not known in the SAPC at session activation or modification. |
DIAMETER_USER_UNKNOWN = 5030 |
5 Reference List
-
General Packet Radio Service (GPRS); Service Description; Stage 2, 3GPP TS 23.060
-
General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access, 3GPP TS 23.401

Contents