Contents

1   Configure Bearer QoS Control and BandwidthManagement Overview

Next figure, shows the main parts related to configuration and provisioning in the SAPC.

The purpose of this document is to provide guidelines to configure the SAPC node for QoS control and bandwidth management by providing configuration examples.

This document is not intended as an exhaustive guide to configure the SAPC for every possible scenario.

The complete parameter list and details of all configured options of the SAPC are included in separate documents, refer to Managed Object Model (MOM) and Provisioning REST API.

Examples on this document cover the case of data configured in the SAPC internal repository. In case an external repository is used, refer to Database Access.

1.1   Other Conventions

This document refers to some configuration and provisioning data.

To clarify which detailed data is managed by COM or by the REST API, this document uses the following conventions:

• Configuration: whenever referring to Managed Object Class (MOC).

  The detailed description for the object and attributes can be found in Managed Object Model (MOM).

  Example: set enableReauthsOnSubsChange attribute in class AppConfig.

  The tools or interfaces to manage these data in the SAPC are:

  1. NETCONF interface, refer to Ericsson NETCONF Interface.

     The configuration examples show the NETCONF file contents, using the following syntax:

     <edit-config>
       ...
       <config>
       <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
       <managedElementId>1</managedElementId>
            ...
       </ManagedElement>
       </config>
     </edit-config>

  2. Or COM CLI, refer to Ericsson Command-Line Interface.
• Provisioning: mainly subscribers, subscriber groups (dataplans), services (contents), profiles, and policy-related data. The SAPC provides a REST API for them, see Provisioning REST API.

  This document uses the following terminology for them: <resource-name> URI in the provisioning REST API.

  Example: To provision subscriber groups, use the dataplan URI in the provisioning REST API.

  And provisioning examples show HTTP operations on REST resources with the following syntax:

  HTTP-Operation /resource-URI 
      {json content}

  where /resource-URI is the relative URI from the SAPC provisioning base URI detailed in Provisioning REST API.

  Example:

  PUT /dataplans/Gold   
  { "dataplanName" : "Gold",
    "subscribedContents" : [{"contentName" : "HTTP_Streaming",
                             "redirect" : false}]
  }

  Note:  

  To ease provisioning operations, the SAPC provides an HTTPS CLI client named resty, refer to Provisioning Tools.

  
  

2   Configuration Prerequisites

Before configuring the SAPC in an operational network, assure that:

• CBA Components are installed.
• The SAPC product software is installed.
• To have a detailed understanding of the function.

3   Configure QoS Control for the Default Bearer and the APN

To configure QoS Control for the default bearer and the APN, do the following:

• Configure the following bearer events related to QoS Control to be notified in the Gx interface:
  • For authorized Bearer QoS:
    • For GPRS access: QOS_CHANGE
    • For EPS access:
      • DEFAULT_EPS_BEARER_QOS_CHANGE.

  For details on how to configure event triggers, refer to Configuration Guide for Access and Charging Control (Gx).

  Note:  

  The following events need no configuration in the SAPC because the PCEF always notifies about them without need of subscription:

  • DEFAULT_EPS_BEARER_QOS_MODIFICATION_FAILURE, applying to Bearer QoS for EPS access.
  • APN_AMBR_MODIFICATION_FAILURE, applying for QoS per APN.
  • QOS_CHANGE, when applicable at APN level, this event needs no subscription.

  
  
• Configure QoS Control for the corresponding PCEF (see Section 3.1)
• Provision QoS profiles for the default bearer/APN (see Section 3.2)
• Provision the maximum and minimum bearer QoS profiles applicable to the subscribers or subscriber groups, either unconditionally or conditionally (see Section 3.3)
• In case of integration with an external database, reconfigure the corresponding Entity Data Source, refer to Database Access.

  Note:  

  All objects and attributes in this document refer to the default configuration provided at installation time in the SAPC: Entity Data Source pointing to data in the SAPC internal database.

  
  

3.1   Diameter Node Control for QoS Control for the Default Bearer and the APN

To execute this function in the SAPC, include the "BEARER_QOS" value in the controls attribute of the DiameterNode object class.

For more information on the PCEF node configuration, refer to Configuration Guide for Access and Charging Control.

3.2   Provision QoS Profiles for Default Bearer/APN

A QoS Profile contains QoS characteristics for the default bearer or APN-AMBR. To provision a Bearer/APN QoS Profile, use the /profiles/ip-can-session-qos/<profileId> URI in the provisioning REST API.

3.2.1   Configuration of Bearer/APN QoS Profiles for GPRS

The applicable attributes are:

• profileId
• qci (QoS Class Identifier)
• mbrDownlink
• mbrUplink
• arpPriorityLevel

The following example shows a possible configuration of bearer QoS profiles:

PUT /profiles/ip-can-session-qos/QosProfile_Default
{
	"arpPriorityLevel" : 7,
	"mbrDownlink" : 1024,
	"mbrUplink" : 512,
	"profileId" : "QosProfile_Default",
	"qci" : 5
}

PUT /profiles/ip-can-session-qos/QosProfile_General_Max
{
	"arpPriorityLevel" : 7,
	"mbrDownlink" : 2560,
	"mbrUplink" : 1024,
	"profileId" : "QosProfile_General_Max",
	"qci" : 5
}

The previous example configures the following bearer QoS profiles:

• A maximum interactive bearer QoS profile with QCI=5 and MBR set to 2560 Kbps and 1024 Kbps for downlink and uplink traffic, respectively.
• A default interactive bearer QoS profile sets MBR for downlink to 1024 Kbps and uplink 512 Kbps, respectively.

Note:  

Depending on the deployment, the PCEF can use MBR or APN-AMBR. Therefore, the values set in mbrUplink and mbrDownlink attributes correspond to:

• Either Max-Requested-Bandwith-UL AVP and Max-Requested-Bandwith-DL AVP
• Or APN-Aggregate-Max-Bitrate-UL AVP and APN-Aggregate-Max-Bitrate-UL AVP

3.2.2   Configuration of Bearer/APN QoS Profiles for EPS

The applicable attributes are:

• profileId
• qci (QoS Class Identifier)
• mbrDownlink
• mbrUplink
• arpPriorityLevel
• arpPci
• arpPvi

The following example presents a Bearer QoS profile for EPS access:

PUT /profiles/ip-can-session-qos/MinGBearerQos
{
	"arpPci" : true,
	"arpPriorityLevel" : 3,
	"arpPvi" : false,
	"mbrDownlink" : 5120,
	"mbrUplink" : 512,
	"profileId" : "MinGBearerQos",
	"qci" : 6
}

Note:  

In this case, the values configured within mbrDownLink and mbrUplink attributes always correspond to:

• APN-Aggregate-Max-Bitrate-UL AVP and APN-Aggregate-Max-Bitrate-UL AVP

3.3   Provision QoS Control for Default Bearer/APN selection

1. To unconditionally associate a QoS Control for the default bearer/APN depending to a subscriber or subscriber group:

   Provision the corresponding subscribers or dataplans URI in the provisioning REST API as explained in Configuration Guide for Subscription and Policies, and set maxBearerQosProfile and minBearerQosProfile attributes to a value that matches the profileId attribute of any bearer QoS profile previously provisioned in the SAPC (see Section 3.2).

   The Example 3 configures maximum and minimum bearer QoS profiles for group "Bronze":

2. To configure QoS Control for the default bearer/APN depending on Conditions, create the needed policies using:
   • For Global policy locator:

     /locators/resources/ip-can-session/contexts/qos

   • For Subscriber group locator

     /dataplans/<dataplanName>/locators/resources/ip-can-session/contexts/qos

   • For Subscriber locator

     /subscribers/<subscriberId>/locators/resources/ip-can-session/contexts/qos

   • Within the outputAttributes object in the rule set:
     • attrName attribute to max-qos or min-qos.
     • attrValue to an expression returning a valid bearer QoS profile id (ip-can-session-qos).

       Note:  

       To assign a fixed QoS profile (for example "Qos1") to the default bearer or APN, set the same expression as max-qos or min-qos.

       
       

Example 4 shows how to assign a QoS for Default Bearer using conditions.

PUT /dataplans/Bronze
{
	"dataplanName" : "Bronze",
	"staticQualification" : 
	{
		"maxBearerQosProfileId" : "QosProfile_General_Max",
		"minBearerQosProfileId" : "QosProfile_Default"
	}
}

PUT /rules/QoS_General
{
	"condition" : "AccessData.bearer.ipCanType==0",
	"outputAttributes" : 
	[
		{
			"attrName" : "max-qos",
			"attrValue" : "(BearerQosProfile[\"QosProfile_General_Max\"]+sumQosProfile)",
			"result" : "permit"
		},
		{
			"attrName" : "min-qos",
			"attrValue" : "maxQosProfile",
			"result" : "permit"
		}
	],
	"ruleName" : "QoS_General"
}

PUT /policies/QoS_General
{
	"policyName" : "QoS_General",
	"ruleCombiningAlgorithm" : "permit-overrides",
	"rules" : [ "QoS_General" ]
}

PUT /dataplans/Bronze/locators/resources/ip-can-session/contexts/qos
{
	"policies" : [ "QoS_General" ]
}

The configuration in this example applies the following range of QoS profiles to "Bronze" subscribers when establishing the bearer for GPRS access (IP-CAN-Type is GPRS):

• Maximum - Fixed QoS profile ("QosProfile_General_Max") plus the addition of the QoS Profiles assigned to the dynamic services running on that bearer.
• Minimum - Maximum QoS Profile among the ones assigned to the dynamic services running on that bearer.

4   Configure Bandwidth Management for Services

4.1   Configure Static Services

To select different bandwidth limits for services (PCC Rules) in a standard PCEF or the SASN, the SAPC allows to activate/deactivate different Charging-Rule-Name values. To configure so, it is possible to do it with the following options:

• Unconditionally: using static services, by setting the PCC Rule name in pccRuleName attribute of a contents URI in the provisioning REST API.
• Conditionally: using policies for static access, see Configuration Guide for Access and Charging Control.

4.2   Preconfigured and Dynamic Services

To assign bandwidth management to services in the SAPC, there are the following options:

• Unconditionally, assigning QoS Profiles to Services, detailed in Section 4.4.
• Conditionally, using policies, detailed in Section 4.4.

For those fields not configured in a QoS profile, values are obtained from QoS-Information AVP.

4.3   Provision Service QoS Profiles

A service QoS profile contains a set of QoS related attributes values shared by services with the same QoS requirements. To provision a Service QoS Profile, use the /profiles/content-qos/<profileId> URI in the provisioning REST API.

4.3.1   Configuration for GPRS

The applicable attributes are:

• profileId
• qci (QoS Class Identifier)
• mbrDownlink
• mbrUplink
• gbrDownlink
• gbrUplink
• arpPriorityLevel
• resourceType

The following example configures several service QoS profiles:

PUT /profiles/content-qos/QosProfile_Streaming_OTHER
{
	"gbrDownlink" : 2048,
	"gbrUplink" : 1024,
	"mbrDownlink" : 4096,
	"mbrUplink" : 2048,
	"profileId" : "QosProfile_Streaming_OTHER",
	"qci" : 3
}

PUT /profiles/content-qos/QosProfile_Streaming_UTRAN
{
	"gbrDownlink" : 3072,
	"gbrUplink" : 1536,
	"mbrDownlink" : 4096,
	"mbrUplink" : 2048,
	"profileId" : "QosProfile_Streaming_UTRAN",
	"qci" : 3
}

PUT /profiles/content-qos/QosProfile_VoIP
{
	"gbrDownlink" : 4096,
	"gbrUplink" : 4096,
	"mbrDownlink" : 6144,
	"mbrUplink" : 6080,
	"profileId" : "QosProfile_VoIP",
	"qci" : 1
}

PUT /profiles/content-qos/QosProfile_MMS
{
	"gbrDownlink" : 4096,
	"gbrUplink" : 4096,
	"mbrDownlink" : 6144,
	"mbrUplink" : 6080,
	"profileId" : "QosProfile_MMS",
	"qci" : 201,
	"resourceType" : "GBR"
}

The previous example configures the following QoS profiles:

• Two QoS profiles for streaming service with QCI= "3" (streaming) and high requirements on Maximum Bit Rate (MBR) and Guaranteed Bit Rate (GBR).
• A QoS profile for VoIP service with QCI= "1" (conversational) and higher requirements on MBR and GBR.
• A QoS profile for MMS service with QCI= "201" (defined by operator) and with resourceType= "GBR", meaning that dedicated network resources are permanently allocated.

4.3.2   Configuration for EPS

The applicable attributes are:

• profileId
• qci (QoS Class Identifier)
• mbrDownlink
• mbrUplink
• gbrDownlink
• gbrUplink
• arpPriorityLevel
• arpPci
• arpPvi
• resourceType

The following example presents a QoS profile for EPS access:

PUT /profiles/content-qos/MinGBearerQos
{
	"arpPci" : true,
	"arpPriorityLevel" : 3,
	"arpPvi" : false,
	"mbrDownlink" : 5120,
	"mbrUplink" : 512,
	"profileId" : "MinGBearerQos",
	"qci" : 6
}

4.4   Provision QoS Control for Services

1. To unconditionally associate a QoS Control to a service:

   Create a contents URI in the provisioning REST API (according to Configuration Guide for Access and Charging Control (Gx)) and set the qosProfileId attribute to a value that matches the profileId attribute of a previously provisioned content-qos profile (see Section 4.3).

   The example provisions a streaming service with a Service QoS Profile:

2. To configure QoS Control for services depending on Conditions, create the needed policies using:
   • For Global policy locator:

     /locators/resources/<contentName>/contexts/qos

   • For Subscriber group locator

     /dataplans/<dataplanName>/locators/resources/<contentName>/contexts/qos

   • For Subscriber locator

     /subscribers/<subscriberId>/locators/resources/<contentName>/contexts/qos

   • Within the outputAttributes object in the rule set:
     • attrName attribute to qos.
     • attrValue to an expression returning a valid service QoS profile id (content-qos).

For some examples about how QoS profiles are conditionally assigned to services using policies, see Example 8.

Note:  

The values configured using policies prevail over the static QoS profiles provisioned in the service. These statically provisioned Service QoS Profiles are only considered when no policies apply, or if the applicable policies do not return any Service QoS Profile.

Example 8 shows how to qualify a service by with conditions:

PUT /contents/Streaming
{
	"contentName" : "Streaming",
	"flows" : 
	[
		{
			"destIpAddr" : "any",
			"destPort" : "",
			"direction" : "dl",
			"flowName" : "1",
			"protocol" : "ip",
			"sourceIpAddr" : "192.168.1.2",
			"sourcePort" : "5001-5050"
		},
		{
			"destIpAddr" : "any",
			"destPort" : "",
			"direction" : "dl",
			"flowName" : "2",
			"protocol" : "ip",
			"sourceIpAddr" : "192.168.1.2",
			"sourcePort" : "5101-5150"
		}
	],
	"pccRuleName" : "4033",
	"pccRuleType" : 2,
	"staticQualification" : 
	{
		"contentQosProfileId" : "QosProfile_VoIP"
	}
}

PUT /rules/QoS_Streaming_OTHER
{
	"condition" : "AccessData.bearer.accessType!=1000",
	"outputAttributes" : 
	[
		{
			"attrName" : "qos",
			"attrValue" : "ServiceQosProfile[\"QosProfile_Streaming_OTHER\"]",
			"result" : "permit"
		}
	],
	"ruleName" : "QoS_Streaming_OTHER"
}

PUT /rules/QoS_Streaming_UTRAN
{
	"condition" : "AccessData.bearer.accessType==1000",
	"outputAttributes" : 
	[
		{
			"attrName" : "qos",
			"attrValue" : "ServiceQosProfile[\"QosProfile_Streaming_UTRAN\"]",
			"result" : "permit"
		}
	],
	"ruleName" : "QoS_Streaming_UTRAN"
}

PUT /policies/QoS_Streaming
{
	"policyName" : "QoS_Streaming",
	"ruleCombiningAlgorithm" : "permit-overrides",
	"rules" : [ "QoS_Streaming_UTRAN", "QoS_Streaming_OTHER" ]
}

PUT /dataplans/Gold/locators/resources/Streaming/contexts/qos
{
	"policies" : [ "QoS_Streaming" ]
}

PUT /dataplans/Gold
{
	"dataplanName" : "Gold",
	"subscribedContents" : 
	[
		{
			"contentName" : "Streaming",
			"redirect" : false
		}
	]
}

The Service Profile "QosProfile_Streaming_UTRAN" is selected for a "Gold" subscriber group if the subscriber is using UMTS Radio Access. Otherwise, the Service Profile " QosProfile_Streaming_OTHER" is selected.

5   Appendix A. QoS Policy Types

Figure 2 shows the different policy types applicable to QoS Control that can be used and configured in the SAPC.

6   Appendix B. QoS Policy Tags

The following tags related to conditional information about IP-CAN session can be used in the condition formula of rules for QoS Control.

For the policy tags obtained from AVPs received in CCR messages (see Comments column), their values are kept during the session lifetime, unless new values of the AVPs are received in subsequent CCR-U/CCR-T messages.

(1)  Ericsson recommends not using this value if charging characteristics for the subscriber has been provisioned.

Also, the following tags related to dynamic information about QoS can be used in the condition formula of rules:

Note:  

AccessData.requestedQos.xx tags refer to the values sent by the PCEF in CCR messages (QoS-Information AVP or Default-EPS-Bearer-QoS AVP, depending on the access type). When the SAPC performs Bearer QoS Control, it is not recommended to use AccessData.requestedQos.xx tags, as such requested QoS can be modified in upgrades or downgrades.

7   Appendix C. QoS Selection Tags for Output Attributes Used in Policies

The following set of tags can be used in an output attribute (attrValue item of outputAttributes attribute) to make mathematical operations to calculate the QoS for default bearer or APNs.

(1)   Do not use this function in network scenarios that support dedicated bearers. Use instead QoS for services.

(2)  This function selects the highest value for every field of the service QoS profiles. For priority-related parameters like QCI, it is the lowest numeric value.

(3)   Related to QoS for APN (as APN-AMBR are the aggregation of MBRs of non-GBR bearers for an APN), do not use this function in network scenarios having services running in GBR-bearers.

(4)  Adding the individual throughput parameters (MBRs) of the QoS profiles, and selecting the highest value in the rest of the QoS parameters.

8   Appendix D Configuration Summary

The next table summarizes the configuration possibilities grouped by the SAPC functions.

Reference List