Cisco Policy Suite Mobile Configuration Guide

Transcription

1 Cisco Policy Suite Mobile Configuration Guide Version November 27, 2013 Cisco Systems, Inc. Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at Text Part Number:

2 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved.

3 CONTENTS Getting Started vii Audience vii Additional Support vii Terms and Definitions vii Version Control Software viii CHAPTER 1 Concepts 1-1 Overview 1-1 Cisco Policy Builder Services and Use Cases 1-1 Service Model 1-1 Use Cases 1-3 Service Options 1-3 Services 1-6 Use Cases 1-6 Use Case Configuration 1-6 Use Case Initiators 1-7 Use Case Configuration Options 1-8 Policy Rules 1-9 Reference Data 1-10 Basic Configuration Steps 1-11 Using the Screens 1-11 Creating a New Service Option 1-13 Services Screen 1-13 Creating a New Service 1-14 Services and Service Options in Detail 1-14 CHAPTER 2 Required Service Configuration 2-1 Overview of Steps 2-1 Before You Begin 2-1 Configuring the Diameter Stack 2-2 Full Environment Verify 2-2 All in One verify 2-3 Setting the Diameter Client 2-6 iii

4 Contents Setting Diameter Defaults 2-7 Rx Profiles 2-7 Sd Push Rules Configuration 2-8 Configuring Use Case Template, Service Option, and Service 2-9 Selecting a Domain 2-9 Publishing the Configuration 2-10 Creating a Subscriber Account 2-10 CHAPTER 3 Domain Configurations 3-1 Defining a Default Domain 3-2 Testing Your Work 3-4 CHAPTER 4 Elective Service Configurations 4-1 Elective Use Cases 4-1 Configuring Basic QoS 4-2 Define a Use Case Template for Basic QoS 4-3 Create a Service Option for Basic QoS 4-7 Create the Basic QoS Service 4-8 VoLTE 4-10 Use Case Template 4-10 Service Option 4-11 Service 4-11 Default Bearer 4-12 Use Case Template 4-12 Service Option 4-15 Service 4-18 Account Balance Template 4-20 Use Case Template 4-21 Service 4-24 Default Bearer with Usage Monitoring 4-28 Services 4-28 Account Balance Template 4-30 Use Case Templates 4-30 Use Case Initiator 4-31 Service Option 4-32 Service 4-32 Use Case Template 4-33 Service Option 4-34 Service 4-35 iv

5 Contents Bandwidth Monitoring 4-35 Use Case Initiators Explained 4-42 Final Steps for Elective Configuration 4-44 CHAPTER 5 Test the Configuration 5-1 Validate Configuration 5-1 Cisco Policy Builder GUI 5-1 Subscriber Services Portal GUI 5-4 Services Validation 5-5 Zabbix/SNMP 5-5 LB01/ CPS0x 5-6 SessionMgr0x 5-6 PortalLB01/ Portal0x 5-6 ControlCenter01/ Checking Access 5-7 Testing Subscriber Access with 00.testAccessRequest.sh 5-7 Testing Subscriber Access with soapui 5-8 Testing for ISG Functionality and Connectivity with test aaa Scripts 5-12 v

6 Contents vi

7 Getting Started Welcome to the. This document describes configuration tasks using the Cisco Policy Builder The document assists installers, network operators, and network engineers to tune and configure the Cisco Policy Builder client interface. Audience This guide is best used by these readers: Network administrators Network engineers Network operators System administrators This document assumes a general understanding of network architecture, configuration, and operations. Additional Support For further documentation and support: Contact your Cisco Systems, Inc. technical representative. Call the Cisco Systems, Inc. technical support number. Write to Cisco Systems, Inc. at support@cisco.com Visit the Cisco self-service portal at > Services > Customer Support > Online Support Ticket Refer to support matrix at and to other documents related to Cisco Policy Suite Terms and Definitions This document uses certain terms and definitions specific to the CPS software application. Please refer to our common Glossary of Terms vii

8 Version Control Software Cisco Policy Builder uses version control software to manage its various data repositories. The default installed version control software is Subversion, which is provided in your installation package. viii

9 CHAPTER 1 Concepts Revised: November 27, 2013, Overview Policies translate a Service Provider s business rules into actionable, logical processing methods. The Cisco Policy Suite provides the Cisco Policy Builder as an interface to policy management. Log in to the Cisco Policy Builder to see the most frequently used policies set up for you. You can customize the standard policies to suite your own business rules. Additionally, you can create your own policy structures for special case situations. Cisco Policy Builder Services and Use Cases The Cisco Policy Builder is the web-based client interface for the configuration of policies to the Cisco Policy Suite. Cisco Policy Builder supports two levels of expertise: Service Model, administrator level Policy Rules, advanced administrator level Service Model The service model prepackages common capabilities into reusable components. The foundation of the service model is Use Cases. Use case templates are the building blocks of the Cisco Policy Builder Service Model architecture and provides the basic construct a service scenario. Using a use case template, you construct various use case modifications, referred to as service options. For example, with the Basic QoS Service, you can configure a 512 Mbps, 1 Gbps downlink service options. One or more Service Options are subsequently combined to create Services. The following figure shows how a use case template is modified into a service option, and finally into a subscriber service. 1-1

10 Cisco Policy Builder Services and Use Cases Chapter 1 Concepts 1-2

11 Chapter 1 Concepts Cisco Policy Builder Services and Use Cases Use Cases A use case contains two parts: a service configuration and an optional initiator, which activates the use case. Some example use cases might be these: Default Bearer QoS Fair Use Usage Monitoring/Quota Control Shared Quota Bandwidth On Demand (Turbo boost) Voice over LTE (VoLTE) Tethering Detection Multi-PCEF Coordination For mobile subscribers, this use case sets up the subscriber s default bearer QoS, i.e., QoS Class Indicator, Uplink and Downlink Bit Rates. This use case defines a fair use scenario that limits a subscriber, e.g. to 2GB of usage per month. If this volume is exceeded, it then throttles the user to a lower bandwidth. Real-time usage control/quota monitoring of user sessions, e.g. for usage caps, fair use, with breach options including notifications, bandwidth downgrade and blocking/redirect. Share Quota across multiple devices and/or users, e.g. a family plan. Sharing based on a common subscriber account with subaccounts and/or a shared external charging identifier. Bandwidth on demand provides additional capacity as necessary to accommodate bursts in data traffic, or a sudden heavy use of bandwidth that is unusual, for example. BoD use case allows the subscriber to only pay for services as they are needed rather than overpay for bandwidth that may go under used part of the time. Authorization of VoLTE/IMS signaling bearer and real-time voice bearer control for voice calls over LTE. This use case is used to detect when the subscriber is using their mobile device as a modem to tether to additional device. Tethering detection depends on PCEF capability. Coordinate policy actions across multiple policy control enforcement points, for example a PDN-Gateway/GGSN and an external DPI. Service Options A service option is a specific instance of a use case template. For instance, service options created using the Bearer QoS use case could be these: QCI 7, 14Mbps (option) QCI 9, 5Mbps (option) 1-3

12 Cisco Policy Builder Services and Use Cases Chapter 1 Concepts This figure shows the basic use case values for a default bearer quality of service: 1-4

13 Chapter 1 Concepts Cisco Policy Builder Services and Use Cases This figure shows the use case template further configured as a service option, with customized values: 1-5

14 Use Cases Chapter 1 Concepts Services Services are created by combining one or more use case service options together into a service plan. This figure shows a service that incorporates the Default Bearer QoS service option along with other service options: Services may be conceptualized in several ways. One way is to create one service with one service option in it, and then bundle services to sell to a subscriber. Another way is to create a service that has several service options in it, and so create one service for a customized, specific subscriber need. Use Cases Use case templates are the building blocks of the Cisco Policy Builder Service Manager architecture. They are the basic constructs upon which you create service options. The software Cisco Policy Builder provides the following uses cases for you to adapt or use as is. Recall that you do not use the provided use case templates. Rather, you copy them, calling them service options, and then make any changes you need in the parameter values. Use Case Configuration A use case template consists of two parts Use Case Initiators/Triggers defines the conditions on which the use case is invoked Use Case Configuration options define the criteria which to evaluate a given use case, and the applicable policy actions to apply. 1-6

15 Chapter 1 Concepts Use Cases Use Case Initiators There is an extensive list of input variables provided. Any field available from an SPR, PCEF, session, or calculated at runtime may be used as an input variable and so used to evaluate the condition. The initiators for a specific use case trigger the execution of a given use case. Condition(s) Select from an extensive library of condition phrases that are evaluated as Boolean logic. Input Variable Any field available from SPR, PCEF session(s) or calculated in runtime may be referenced. Operator 1-7

16 Use Cases Chapter 1 Concepts Single values that are not Boolean. For example, : =, isnull,!isnull (Not Null), matches (java regex matching),!matches, in (provide a comma delimited list),!in, <> (Not equals) are all Boolean values. Boolean single values: =, <>, isnull, null Use Case Configuration Options The options or actions of a use case is use to authorize the QoS, install PCC rules, or monitor usage, for example. 1-8

17 Chapter 1 Concepts Policy Rules If a use case requires evaluation of various criteria to determine the resulting action, decision table all for intuitive and flexible execution based on the evaluation of multiple conditions. This way, no scripting is required. Policy Rules For those policies that have no use definitions, Cisco Policy Builder supports an expert or advanced level user capacity. For the advanced administrator, these capabilities, advantages, and considerations are available. Policies tab on the Cisco Policy Builder can be used to define policy rules. Capabilities: IF / THEN support, defined as condition / action Decision tables Can trigger actions from extensive catalog of condition initiators (100+) Can reference sessions, messages, and OSS/BSS data to evaluate conditions Advantages No coding required Supports custom or unusual business rules, such as Turn off Gold service every other Thursday for customer s with the first name of John. Easy to add capabilities that are normally hard coded or scripted, such as Make this DB query for these specific realms with these options Considerations Building policies requires a deeper understanding of the call flow and underlying platform. Due to the flexibility of Cisco Policy Builder, it is possible to create conflicting policies 1-9

18 Reference Data Chapter 1 Concepts Reference Data In the Cisco Policy Builder interface, the Reference Data tab organizes mostly static data about your network. It is not directly related to policy, services, or use cases, but does define the reference points for the following type of information: Systems, cluster, and instance data Policy enforcement points, or network devices Jdbc query string definitions Balance and quota values Diameter client information Query strings Look up tables Notification addresses and text strings Reporting criteria Subscriber data repositories Tariff switch times For mobile configurations, these reference data screens must be configured to configure the Diameter stack: Systems Diameter clients Diameter defaults Account balances boundaries 1-10

19 Chapter 1 Concepts Basic Configuration Steps Note the various plug-ins available to set up a mobile configuration. Basic Configuration Steps Fundamentally, the steps for configuring your services are: Step 1 Step 2 Step 3 Step 4 Configure the use cases one time. Create a service option by copying a use case template. Adapt that service option to meet your business rules. Combine one or more service options and create a service. Using the Screens To perform your configuration tasks, you use two main screens: Services Screen Service Options Screen This example shows how to customize a service option for VoLTE. 1-11

20 Basic Configuration Steps Chapter 1 Concepts Step 1 Step 2 Open up a browser window and display the Cisco Policy Builder interface. Click Service tab > Services node > Service Options folder. In the tree on the left, the service option VoLTE uses the Standard service option, which has the four configurations listed. Step 3 In the Service option main screen, select one of the service configurations, click in the value field for upload UL or download DL, and set an upload or download rate. Name Use Case Template Service Configurations A unique and descriptive name for the service option. Informs you which use case template this service option is derived from. Part of the use case template. Service Configurations can be added or removed. Change the value of the Service Configuration in the table to the right. Add or remove Service Configurations to get the desired combination of parameters. 1-12

21 Chapter 1 Concepts Basic Configuration Steps Value Add / Remove button The value or parameter of the Service Configuration. Click to add or remove service configurations to the service option. After adding, you can change the default value of the Service Configuration to meet your definition of the Service Option. Our example shows an upload rate of and a download rate of , which is a change from the default value in the original use case template. Creating a New Service Option In summary the basic steps used to create a new service option, based on an available use case are these. Step 1 Step 2 Step 3 Step 4 Step 5 Click Services tab > Services node > Service options folder > base service option. Select the Service Option link on the right. Click OK to display an empty Service Option screen. Select the Service Configuration on the left to display the parameters. Click in the table on the right and change the parameters. After modifying the parameters click Save to save the modified parameters. If you do not see the service option you want in the tree, notify your software technical representative. The representative can construct a use case template for you. Services Screen In the example below, the tree on the left shows a variety of mobile services available to offer subscribers. 1-13

22 Basic Configuration Steps Chapter 1 Concepts The GOLD service uses these service options: Gold 2 GB-Month (2 GB per month) User Alerts The 2GB-Month service option is used in the GOLD service as shown here, but may be used in other service offers as well. To augment or restrict the GOLD service, use the Add and Remove buttons to add and remove service options. For example, if you want to reduce the bearer QoS, add the DowngradeQoS service option as well. Creating a New Service In summary, to create a new service, select one or several previously created service options: Step 1 Step 2 Step 3 Click Services tab > Services node > Service folder > Service link on the right. Fill in the Service screen, with a Code and Name. Use the Add and Remove buttons to add and remove service options. If you do not see the service option you want for your service, create one with the Service Options folder. Services and Service Options in Detail Now that you understand the basic concepts for configuring your services, Perform the required configuration tasks described in Required Service Configuration. Create any elective services as described in Elective Service Configurations. 1-14

23 CHAPTER 2 Required Service Configuration Revised: November 27, 2013, Overview of Steps These configuration steps are required. Read and complete all these sections. Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Configuring the Diameter Stack Setting the Diameter Client Setting Diameter Defaults Configuring Use Case Template, Service Option, and Service Selecting a Domain Publishing the Configuration Creating a Subscriber Account When you have completed the required configuration steps above: Examine Elective Service Configurations and configure your own service options and services. Test your configuration. See Test the Configuration. Before You Begin Before you perform the required configurations tasks discussed here, be sure that you have these tasks completed: Install Cisco Policy Suite and have it process test traffic. Have the proper licenses enabled. Have access to the Cisco Policy Builder web page. Have access to the Control Center virtual machine (VM). Have your NAS or PEP installed and configured. Begin all procedures from the Cisco Policy Builder interface for most procedures. Know what your basic service consists of. 2-1

24 Configuring the Diameter Stack Chapter 2 Required Service Configuration Plan what your additional services will look like. Decide on the names and levels of tiered service. Be familiar with any AV pairs you will use. Know what speeds will define your uploads and downloads Specify the domain Default. No special settings are required. Understand what limitations and augmentations each service will have. Configuring the Diameter Stack Full Environment Verify Verify that the diameter feature is installed in full environment. If not installed follow these instructions to install the feature. Step 1 Step 2 Step 3 Step 4 Take backup of directory /etc/broadhop/license/. From directory /opt/broadhop/installer run script set_config.sh. It initializes default mobile setup (i.e., initializes the /etc/broadhop directory to a default configuration). If no arguments are provided the system will echo the valid choices of configurations. It is recommended for mobile to select general_mobile. Restore the license backup taken above to /etc/broadhop/license/ directory. Verify that the Diameter plug-in configuration is installed on the Cisco Policy Server and Cisco Policy Builder. a. Add the following feature to /etc/broadhop/iomanager01/features and /etc/broadhop/iomanager02/features on pcrfclient01 com.broadhop.diameter2.service.feature b. Add the following feature to /etc/broadhop/pcrf/features on pcrfclient01. com.broadhop.diameter2.local.feature c. Add the following feature to /etc/broadhop/pb/features com.broadhop.client.feature.diameter2 d. Change directory with the following command. cd /opt/broadhop/control e. Run./syncconfig.sh f. Change directory with the following command. cd /opt/broadhop/installer g. Run "su qns -c "./update_qns.sh -f" 2-2

25 Chapter 2 Required Service Configuration Configuring the Diameter Stack All in One verify If the feature is missing, add the feature as shown below. These instructions are applicable to only All-In-One solutions: a. Add the following features to /etc/broadhop/pcrf/features file: com.broadhop.diameter2.service.feature com.broadhop.diameter2.local.feature b. Add the following feature to /etc/broadhop/pb/features file: com.broadhop.client.feature.diameter2 c. Change directory with the command cd /opt/broadhop/installer or type installer. d. Run./update_qns.sh Step 5 Add the plug-in Diameter Configuration in Cisco Policy Builder. Click Systems > your_system_name > Plugin Configurations > Diameter Configuration. Figure 2-1 Systems > Diameter Configuration Plug-in Step 6 Step 7 In the tree, select Diameter Configuration, the configuration you just added. In the main window on the right, notice the Next Hop Routing check box. Do not select Next Hop Routing. 2-3

26 Configuring the Diameter Stack Chapter 2 Required Service Configuration Figure 2-2 Diameter Configuration Screen > Next Hop Routing Step 8 Create a Diameter Stack, in the tree click system-1 > Plugin Configurations > Diameter Configuration > stack-1 as shown in the figure below. Make sure the check box Accept Undefined Peer, at the top, is checked. Especially notice the values in the Realm table and in the Local End Points table. The minimum configuration requires these fields: Stack name Realm Inbound Peers -> Realms with Processing Protocols Local End Points Note Be sure to update /etc/hosts with the IP address of your Diameter end point. 2-4

27 Chapter 2 Required Service Configuration Configuring the Diameter Stack Figure 2-3 Systems > Plug-ins > Diameter > stack-1 Example Step 9 Step 10 Add the Diameter Host Name defined in Fqdn Mapping to the /etc/hosts file of the host with the end point network interface IP address. For example: pcrf In the Realms table in the figure above: The Name column is the realm name of the PCEF device. Processing Protocol column is the protocol used to interface with the PCEF device. Either use a IP address or leave this blank. 2-5

28 Setting the Diameter Client Chapter 2 Required Service Configuration Setting the Diameter Client This procedure is optional. The client configuration is used to apply different policies based on PCEF type. This is optional. Only one client can control a session life cycle. The client controlling the session life cycle is responsible for network session management. This section shows how to configure tow types of Diameter Gx clients, PGW for Cisco realm and L7GX for Openwave. Step 1 Step 2 Step 3 Click Reference Data > Diameter Clients > Gx Clients. Select Gx Client in the right pane. Set the Name field, add the pgw.cisco.com realm, and select the check box Control Session Lifecycle. Figure 2-4 GX / PGW Client Settings An Openwave Example Step 1 Step 2 Step 3 Click Reference Data > Diameter Clients > Gx Clients. Select Gx Client in the right pane. Provide a Name, add the realm openwave.com, and select the check box Load By Framed IP. 2-6

29 Chapter 2 Required Service Configuration Setting Diameter Defaults Figure 2-5 Openwave Client Settings Setting Diameter Defaults This section shows typical screens and values used when configuring Diameter. Rx Profiles This configuration is applicable when CPS interfaces with AF over an Rx interface. These values are used as specified in 3GPP TS Step 1 Step 2 Click Reference Data > Diameter Defaults node > Rx Profiles. The only required values for an Rx client are the maximum requested upload and download bandwidth. Application QoS Policy values and Codec QoS Policy values are usually left blank unless specifically needed. These values can be configured for the Rx interface if needed. Our example shows values of for both upload and download MBR. These default values are applicable if the Rx service configuration object is not defined. 2-7

30 Setting Diameter Defaults Chapter 2 Required Service Configuration Figure 2-6 Rx Profile Settings Sd Push Rules Configuration This configuration is required when CPS interfaces with TDF of an Sd interface. The values here define a TDF realm corresponding to a Gx realm. Step 1 Click Reference Data > Diameter Defaults > Sd Push Rules. Figure 2-7 SD Push Rule Settings 2-8

31 Chapter 2 Required Service Configuration Configuring Use Case Template, Service Option, and Service Configuring Use Case Template, Service Option, and Service A required step in configuring you system is to set up at least one service. Services are built from service options, and service options are built upon copies of use case templates and may be modified or not. See Elective Service Configurations for procedures on how to configure services, service options, and use case templates for specific business purposes. Selecting a Domain Setting a domain is a required step. A domain controls how a subscriber is authorized. Each subscriber accesses the network through a single domain authorization process upon log on. A subscriber's domain is determined by their physical location. If a subscriber does not qualify for any of the established domains, he is considered to be part of the domain named 'default'. Note Recall that for mobile configurations, only a simple Default domain is needed. Set the default domain values as described below: Step 1 Step 2 Step 3 Step 4 Click Services tab -> Domains node. If a Default domain is already present in the tree on the left, Make sure the Is Default check box is selected. Check that Authorization shows Allow All Users. A domain prefix is optional, but helpful in a mobile configuration. Figure 2-8 Select a Domain Screen 2-9

32 Publishing the Configuration Chapter 2 Required Service Configuration To create a Default domain, select the Summary node in the tree and define the Name field and check the Is Default box. No other settings are required. If you need more help, see Defining a Default Domain. Publishing the Configuration Step 1 Step 2 Step 3 Click File > Save to client repository and select a repository to save to. If the repository is local, reload the configuration on CPS servers. If the repository is version controlled, click File > Publish to Runtime Environment. Creating a Subscriber Account Subscriber accounts are handled by Cisco Control Center. For testing purpose, create a test subscriber account with that interface. Step 1 Log in to the Cisco Control Center interface. You will need a username and password for this site. Figure 2-9 Create a Subscriber Screen Step 2 Step 3 Step 4 Click Create Subscriber. Specify credential and a full or partial name of the subscriber. To check, click Find Subscriber and put in the credential name you just made. 2-10

33 Chapter 2 Required Service Configuration Creating a Subscriber Account Step 5 Click search and it should display. Figure 2-10 Find a Subscriber Screen Step 6 Step 7 Open the subscriber with the link on the right. In the Services table click edit. Step 8 In the Service Code list click add. 2-11

34 Creating a Subscriber Account Chapter 2 Required Service Configuration Step 9 Add any of the services displayed, just to get started. You will create your own services later. Step 10 Go on to Elective Service Configurations. All of your required configuration procedures are complete, although you may want to use the Reference Data tab again to make small changes. 2-12

35 CHAPTER 3 Domain Configurations Revised: November 27, 2013, This section contains procedures for configuring a mobile domain. Defining a Default Domain Testing Your Work Open a browser and log on to the Cisco Policy Builder interface to perform domain configuration tasks. Domain screens are at Services -> Domains -> Summary. A domain is a way to partition subscribers based on an attribute of the triggering session creation message with a set of authorization, auto provisioning, secondary profile load, locations, and various advanced domain options. This list provides a detailed explanation of these concepts: The Authorization section defines the method that can be used for authorizing session creation. The following methods are appropriate for mobile use cases: USuM Authorization performs a lookup in the Cisco Unified SuM SPR for the subscriber s profile. This method requires a username (network identifier) and optionally a password. A password is not common in mobile scenarios. Common username fields are MSISDN or IMSI. Allow All Users performs no validation and always allows session creation. This method is commonly used if a secondary subscriber data source is the sole source of subscriber data or if auto provisioning is defined. The Provisioning section defines whether auto provisioning of subscribers within the SPR should occur. This method is generally used in scenarios where the system is configured to auto-learn subscribers and assign a default service profile. For example, the Authorization section would be configured with Allow All Users and the Provisioning section would be configured to provision users with a key of the MSISDN. The Additional Profile Data section defines if an LDAP search or other search method (Sh) should be utilized to retrieve profile data that is not stored in the local SPR. This is often used to integrate an external profile repository. The Locations section defines the rules used to guide the requests to a non-default domain. The rules supported that are relevant to mobile include: Framed IP Mask, in CIDR format Realm Mask, defined as realm/abc.madeup.com The Advanced Rules determines if unknown subscribers can come into the system and defines the unknown service. This is often used if subscribers self-provision and so are initially unknown. An example of this scenario is: 3-1

36 Defining a Default Domain Chapter 3 Domain Configurations Cisco Unified SuM authorization, IMSI Authorization No Auto Provisioning Unknown Subscribers Allowed Unknown Package - Portal Self-service Defining a Default Domain This procedure shows you how to create a default domain for all subscribers in the system. At any one time, there must be one domain defined in the system and that domain is assigned to a session if the location rules do not resolve to another domain. In general, you should not have rules for a default domain. This domain specifies that any time a request is received, the Cisco Unified SuM SPR profile is loaded using the MSISDN. No provisioning is triggered, and no additional profile data is retrieved. All advanced options are set to default. Domain Screen Top Enter a Name and review the Is Default check box. General Subtab Set Authorization to USuM Authorization. Your subscriber will be checked against Cisco Unified SuM. Set the User Id Field to Session MSISDN. 3-2

37 Chapter 3 Domain Configurations Defining a Default Domain Provisioning Subtab No changes are needed. Additional Profile Data Subtab No changes are needed. 3-3

38 Testing Your Work Chapter 3 Domain Configurations Locations Subtab No changes are needed. Advanced Rules Subtab No changes are needed. Testing Your Work Test your configuration with these steps: Step 1 Step 2 Step 3 Check for correct access and log on using a test subscriber logon. Verify correct portal redirection, On the portal, validate the subscriber and that they are registered in Cisco Unified SuM. Go on to configure the use cases needed for your company s deployment. See the chapter Elective Service Configurations. 3-4

39 CHAPTER 4 Elective Service Configurations Revised: November 27, 2013, This chapter shows how to configure your software for your specific service configurations. Elective service configurations are ones that you choose to implement and are shown in the list below. You can use one, many, or all of the elective service configurations to serve your subscribers. Open a browser window and log on to the Cisco Policy Builder interface for all tasks. Before you configure thecps elective configurations, make sure that you have these tasks completed: Complete the required use cases as described in Required Service Configuration. You must have all of the required service configurations complete before you can implement any of the elective service configurations. For the examples here, you will need the required service configurations for Diameter Clients, of pcef.com/pcef Client and dpi.com/dpi clients. Choose the use cases you want from this chapter and work through them. Set up a Default domain as described at Domain Configurations. When you are all done, perform the tasks described in Elective Service Configurations. Elective Use Cases Configure one, many, or all of these use cases to enable the services you want to provide to your subscribers. Before you work through any of these use cases, you must have completed all of the required use cases. Procedures are provided for these use cases: Configuring Basic QoS Work through this use case example in full. You will always want to have a basic level of QoS and this procedure has more detail. VoLTE Voice over LTE is a global mobile industry movement toward a standard way of delivering voice and messaging services for Long-Term Evolution (LTE). Using IP Multimedia Subsystem specifications, VoLTE focuses on roaming and Interconnect interfaces, in addition the interface between customer and network. LTE is a 4G wireless broadband technology that facilitates high-speed communication and data transfer, as well as increased bandwidth capacity. LTE is a radio platform technology with higher peak throughputs than HSPA+ in higher spectrum bandwidth. LTE is faster than 3G and utilizes an all-ip architecture, everything is handled as data. 4-1

40 Elective Use Cases Chapter 4 Elective Service Configurations Default Bearer This example configures separate MBR for UTRAN and E-UTRAN based on rattype initiator. These steps create a use case template, service option and service that provides Usage Monitoring. That is, if a subscriber exceeds their quota or time balance, the quality of service is degraded. And, usually the subscriber is provided with an opportunity to buy more quota with another mechanism. This use case provides Usage Monitoring. That is, if a subscriber exceeds their quota or time balance, the quality of service is degraded. An application monitoring use case monitors apps for a quota amount and then degrades QoS if that quota is exhausted. An application monitoring use case checks subscriber use of a specific application, perhaps Facebook, against a set quota amount and then degrades QoS if that quota is exhausted. Turbo boost means to up sell subscriber to a faster service for a predetermined amount of time in the event that they exhaust quota amount or time. With a Turbo boost use case you can configure a service to up sell the subscriber to a faster service for a predetermined amount of time in the event that they exhaust their regular quota amount or time amount. Bandwidth Monitoring This feature is based on usage monitoring key being installed in order to have the usage reported by the PCEF. Configuring Basic QoS Back to Elective Use Cases. This procedure sets the bandwidth for an authenticated client as a basic service option that can then be included in many other services. Briefly, the steps are these: Basic QoS Use Case Template Set up a template with a Default Bearer QoS and Pre Defined Rule Service Configurations. The basic service configurations you add to a use case template are provided and you select them from a list. You do not configure these yourself. Allow values to be overridden with new speeds or new value if desired Basic QoS Service Option Speed Tier 1 Set up the subscriber with 512kb upstream / 680kb downstream Pass a predefined rule to the Policy Enforcement Point 4-2

41 Chapter 4 Elective Service Configurations Elective Use Cases Define a Use Case Template for Basic QoS Step 1 Click Services tab > Use Case Templates node > Summary > Summary > Use Case Template link and view the Use Case Template screen. Step 2 Change the Name field to Base QoS. Note Step 3 Step 4 Step 5 This procedure uses only the Use Case Template tab. Set up a template with a Default Bearer QoS and PreDefinedRule service configurations. Click Add, choose an object and open it. Then choose DefaultBearerQos. 4-3

42 Elective Use Cases Chapter 4 Elective Service Configurations Leave the check boxes as they are. When checked, these field names appear on subsequent screens. Step 6 DefaultBearerQoS is now listed as a service configuration for this use case template. Use the check boxes and allow changes to only the Qci, upload bandwidth, download bandwidth, and the Arp values. 4-4

43 Chapter 4 Elective Service Configurations Elective Use Cases Any other values will be unchangeable, but allowing a value to be edited lets this use case be used in other services with variations to these values. Note The tabs Use Case Initiator and Documentation are not required. Now add the PreDefinedRule service configuration. Step 1 Step 2 Click the Add button and choose an interface object and open it. Be sure to use the same interface you used above. Then choose the PreDefinedRule object. 4-5

44 Elective Use Cases Chapter 4 Elective Service Configurations Leave the check boxes selected so that the field names appear on the next screen. Step 3 Step 4 Use the check boxes and allow changes to only The Rule Name. Any other values will be unchangeable, but allowing a value to be edited lets this use case be used in other services with variations to these values. Click the Value column for that row and enter the value Basic-Rule. 4-6

45 Chapter 4 Elective Service Configurations Elective Use Cases The use case template Basic QoS is now defined. You can use it as is or change the values where override is permitted. The next procedure shows how to use this use case template in a service option. Create a Service Option for Basic QoS Create a service option that uses the use case template Basic QoS. If you need to, go back and check that procedure at Define a Use Case Template for Basic QoS. When a Use Case Template is created, a corresponding empty Service Option folder is also created. Each Service Option created underneath the Service Option folder takes the Service Configuration parameters set in the original Use Case Template These steps create a child Service Option under Basic QoS service option named Speed Tier 1. Step 1 Step 2 Click Services tab > Services node > Service Options folder. Open the folder and then click the Service Option link on the right. Step 3 Review the Select Service Configuration screen and click OK. Step 4 Define the Name field as Speed Tier 1. Step 5 Make sure the use case template shows the Basic QoS link. Note Step 6 Notice that you can view only the parameters you left check marked when you created the use case template Basic QoS. If you want to set a parameter, and it is not displayed, go back and look at the use case template. Set the Default Bearer QoS values for the Service Configuration. Redefine the Upload and Download bandwidths to Kb and 76000Kb. These are the UL and DL rates the subscriber will experience. You can override these values now because you checked Allow Override in the Use Case Template. 4-7

46 Elective Use Cases Chapter 4 Elective Service Configurations No fields need to be marked as required. Step 7 Click the PreDefined Rule configuration to check its parameters. Step 8 Redefine the value for Rule Name if your business case requires it. Our example above shows a slight change to the Rule Name when it is displayed. The Service Option Speed Tier 1 is now set up as a complete Service Option under the Basic QoS Use Case Template. This service option can be used to define a subscriber service. Create the Basic QoS Service When the Service Option is complete, create the new service by adding the new Basic QoS option to the service. 4-8

47 Chapter 4 Elective Service Configurations Elective Use Cases Step 1 Click Services tab > Services node > Services folder > Service link on the right. Step 2 Click the Add button and add the service option Speed Tier 1. Notice the changed UL and DL values and the edited name of the Rule Name parameter. Step 3 Step 4 Change the Code field and the Name field. No other changes are necessary, but notice the check boxes at the top. Enabled mean the service is available now and may be purchased by the subscriber. Suppress In Portal means that if the subscriber logs in through a custom portal, the portal will not show this service yet. Balance Service means this service requires an account balance template to be associated to measure quotas of volume or time. 4-9

48 Elective Use Cases Chapter 4 Elective Service Configurations Add to Subaccounts means that this service is provided to related users under a subscriber by default. Your final Service screen should look like this one. Go back to Elective Use Cases.list if you would like to see another example of configuring Use Case Template, Service Option, Service. VoLTE This use case shows how to offer subscribers a VoLTE service. Rx is the interface protocol. Use Case Template Configure a use case template with the service configuration RxAppQoSInformation. Click the Add button to select this from a list. 4-10

49 Chapter 4 Elective Service Configurations Elective Use Cases You might want to review the parameters that appear on the right. Service Option In the Service Options folder, VoLTE is now available to either use as is or modify to a special need. Check the parameters on the right to see if any changes are necessary. Usually changes are not necessary. Service Create a service that uses the VoLTE service option. Below, the VoLTE Service Option is the only option in the VoLTE service. However, a subscriber can purchase the VoLTE service bundled with other services. 4-11

50 Elective Use Cases Chapter 4 Elective Service Configurations Back to Elective Use Cases. Default Bearer Use Case Template This example of Use Case Template, Service Option, Service separates MBR for UTRAN vs E-UTRAN based on rattype initiator. Briefly the steps are these: Default Bearer Use Case Template set up a template with a Default Bearer QoS and Pre Defined Rule Service Configurations Include Use Case Initiators to determine the rattype 2 Default Bearer Service Options for differentiated services Silver and Gold options use different QoS values Pass predefined rules to the Policy Enforcement Point (PCEF) per service option This type of use case requires an understanding of use case initiators, which is discussed Different QoS are possible with this use case and depend on whether or not the rattype is UTRAN or E-UTRAN. These steps create a Default Bearer use case template. Step 1 Step 2 Click Services > Services > Services > Use Case Templates and provide the Name field with Default Bearer. Create E-UTRAN Bearer and UTRAN Bearer children. 4-12

51 Chapter 4 Elective Service Configurations Elective Use Cases Step 3 Edit the children, providing different QoS depending on whether or not the rattype is UTRAN or E-UTRAN. Step 4 Step 5 Add a PreDefinedRuleBase service configuration object to the Default Bearer Use Case Option Do this for both the UTRAN and E-UTRAN children. Step 6 Add a default bearer QoS for E-UTRAN. 4-13

52 Elective Use Cases Chapter 4 Elective Service Configurations No need to add values yet, that is added in the Service Option configuration. Step 7 Configure an E-UTRAN Use Case Initiator (rattype 1004) Step 8 Then Add a default bearer QoS for UTRAN 4-14

53 Chapter 4 Elective Service Configurations Elective Use Cases Step 9 Configure a UTRAN Use Case Initiator (rattype 1000) Service Option Step 1 Create two Service Options, one named Silver and one named Gold. These service options will contribute to the services created in the next section. 4-15

54 Elective Use Cases Chapter 4 Elective Service Configurations Step 2 For the Silver service option, set the PreDefinedRuleBase in the Service Configurations list. Make sure the Rule Name is Silver, like the Service Option name. Step 3 Set the QCI and MBR for the UTRAN Bearer QoS for the Silver service option. Our example shows QCI 7, upload UL 3,000,000, download DL 60,000,000, Bit rate UL , bit rate DL 60,000,

55 Chapter 4 Elective Service Configurations Elective Use Cases Step 4 Likewise, set the QCI and MBR for the E-UTRAN Bearer QoS for the Silver service option. Our example shows QCI 7, upload UL 3,000,001, download DL 60,000,001, Bit rate UL , bit rate DL 60,000,001. Step 5 Step 6 Now do the Gold service option. Select it in the tree. Set the PreDefinedRuleBase. Make sure the Rule Name is Gold. Step 7 Set the QCI and MBR for the UTRAN Bearer QoS for Gold. 4-17

56 Elective Use Cases Chapter 4 Elective Service Configurations Our example shows QCI 7, upload UL 5,000,000, download DL 10,000,000, Bit rate UL 5,000,000, bit rate DL 10,000,000. Step 8 Set the QCI and MBR for the E-UTRAN Bearer QoS for Gold. Our example shows QCI 7, upload UL 5,000,001, download DL 10,000,001, Bit rate UL 5,000,001, bit rate DL 10,000,001. Service With a Silver and Gold Default Bearer service option, they are available as options within any service. 4-18

57 Chapter 4 Elective Service Configurations Elective Use Cases Click Services tab > Services node > Service Options > Default Bearer and create a Silver level service and a Gold level service that use those service options. Go back to Elective Use Cases.list if you would like to see another example of configuring Use Case Template, Service Option, Service. These steps create a use case template, service option and service that provides Usage Monitoring. That is, if a subscriber exceeds their quota or time balance, the quality of service is degraded. And, usually the subscriber is provided with an opportunity to buy more quota with another mechanism. Briefly: Create an Account Balance from the template. Track usage against the account balance, changing QoS when the balance is depleted. Create a Usage Monitoring Service Option with Use Case Initiators. Track a specific Application Key. Create a Silver service that has the Usage Monitoring service option. Add Automatic Balance Provisioning to the service When the service is added to a subscriber or user account in Cisco Unified SuM, the balance automatically adds to the account as well. 4-19

58 Elective Use Cases Chapter 4 Elective Service Configurations Account Balance Template Step 1 Click Reference Data tab, Account Balance Templates > Summary > Account Balance Template on the right. Step 2 Change: Name field to 100MB_MONTHLY Set the units to Megabytes Change the Name field to DATA. This automatically creates a folder in the tree with three folders under it. Step 3 Step 4 Step 5 Step 6 In the tree, select the DATA folder you just created and open it. Select Recurring Quota Templates > Recurring Quota Template on the right. Name this template 100MB_MONTHLY Set: 4-20

59 Chapter 4 Elective Service Configurations Elective Use Cases Recurrence Frequency to Months Amount to 100 (by default it refers to Megabytes as this account balance template was defined as MB The completed template provides 100MB monthly after it becomes associated with a service. Use Case Template Next, set up the use case template for usage monitoring. You will set up the correct use case initiators to track data use by the subscriber. Step 1 Step 2 Step 3 Click Services > Use Case Templates > Use case Template on the right. In the first tab, Use Case Option, change the Name field to Usage Monitoring. Add two service configuration objects: Usage Monitoring Trigger and Usage Monitoring Key. Note Step 4 Remember, all our example use the Gx interface. Select the new Use Case Template in the tree, click on Use Case Option on the right. 4-21

60 Elective Use Cases Chapter 4 Elective Service Configurations This adds a child Use Case Option that monitors quota depletion. Step 5 Step 6 Step 7 Name the child Quota Exhaustion and add the Service Configuration Quota Exhaustion QoS. In the tree select Quota Exhaustion. In the second tab Use Case Initiators, click the green plus. 4-22

61 Chapter 4 Elective Service Configurations Elective Use Cases Step 8 Change the name for the initiator in the field under that table. Step 9 Step 10 Click the Add button to display the condition phrases available. Select A MSBM AccountStatus exists. 4-23

62 Elective Use Cases Chapter 4 Elective Service Configurations Step 11 Then Click on the new condition in the condition table and display the variables. Our example uses only the variables accountbalancecode, a literal equal to the string DATA. and amountremaining, a literal equal to zero. That is, if the balance code is DATA, and the amount Remaining is 0, this condition will evaluate to TRUE. The use case option Quota Exhaustion under the use case template Usage Monitoring has its service configurations defined and its use case initiator defined. Service Step 1 Select Services > Silver service, > Automatic Balance Provisioning on the right. 4-24

63 Chapter 4 Elective Service Configurations Elective Use Cases Step 2 Configure Automatic Balance Provisioning to add an account balance to the service as a default. Step 3 Select Services > Service on the right. 4-25

64 Elective Use Cases Chapter 4 Elective Service Configurations Step 4 Add the Silver Default Bearer and Basic Usage Monitoring Service Options. Step 5 Select the Silver service in the tree and select Automatic Balance Provisioning. 4-26

65 Chapter 4 Elective Service Configurations Elective Use Cases Step 6 Name the new Automatic Balance Provisioning BILL_PERIOD. Step 7 Step 8 Step 9 Scroll down to add the 100MB_MONTHLY to the Recurring Balance Rules table. Select an Account Type of Subscriber. Click in the Quota Template field and click the three dots on the right of the column. Step 10 Select the 100MB_MONTHLY quota you created earlier. Go back to Elective Use Cases.list if you would like to see another example of configuring Use Case Template, Service Option, Service. 4-27

66 Elective Use Cases Chapter 4 Elective Service Configurations Default Bearer with Usage Monitoring Briefly: A use case template with two service configuration objects Usage Monitoring and Default Bearer and Two service options, Gold for E-UTRAN and Silver for UTRAN. See Default Bearer and the section on page 19. This procedure builds from the default bearer use case and the Usage Monitoring use case. This allows you to quickly create two subscriber services, Gold and Silver. Procedures for those two use cases are not repeated here, but the service configuration is provided. Note No use case initiators are needed. The proper service is rendered when the subscriber logs in. Services With the Gold and Silver service options in place you can quickly create services that use them. Recall that Default bearer use case E-UTRAN has a RAT type of Default bearer use case UTRAN has a RAT type of Service option Default Bearer Gold has UL and DL speeds in the and ranges for example. Service option Default Bearer Silver has UL and DL speeds in the and ranges for example. Select Services in the tree on the left. Configure the Gold service to use the Gold Default Bearer service option and the Basic Usage Monitoring service option. 4-28

67 Chapter 4 Elective Service Configurations Elective Use Cases Gold service option specifies the slower UL and DL speeds and operates on the condition RAT type = 1004 as specified in the use case initiator. Configure the Silver service to use the Silver Default Bearer service option and the Basic Usage Monitoring service option. Silver service option specifies the slower UL and DL speeds and operates on the condition RAT type = You can add any other service option you like at this point. Perhaps the Gold subscriber would also like the Social service option to prevent any shock when over-using an application. A Silver user might like to have Turbo Boost in the service so that he can get higher speeds than normally configured for him. Go back to Elective Use Cases list if you would like to see another example of configuring Use Case Template, Service Option, Service. An application monitoring use case monitors apps for a quota amount and then degrades QoS if that quota is exhausted. Briefly: Create a Social daily account balance. Create Use Case Initiators to provide Application Monitoring Tracking a specific Application Key Create an Account Balance Tracking usage against a Social Data account balance and changing QoS when the balance is depleted Create a Social service with an auto-provisioned balance of 10 MB/Day. When a subscriber buys the Social service assigned, that quota is debited first. 4-29

68 Elective Use Cases Chapter 4 Elective Service Configurations Account Balance Template Step 1 Select Reference Data > Account Balance Templates > Summary > Account Balance Template on the right. Step 2 Step 3 As with the 100MB_MONTHLY template, select the type MB. Provide the name it SOCIAL. Create a recurring quota of 10MB day under the SOCIAL template. Use Case Templates Use Case Templates can be set up for Application Monitoring with the appropriate Use Case Initiators. Step 1 Create a new use case template and name it Application Monitoring. 4-30

69 Chapter 4 Elective Service Configurations Elective Use Cases Step 2 Add three service configurations, Usage Monitoring Trigger, Usage Monitoring Key, and PreDefinedRule. Use Case Initiator Step 1 Select the use case Application Monitoring and click the second tab, Use Case Initiators. Note Step 2 Step 3 If you need more detailed help to work through these screens, see the section on Use Case Initiators Explained. Add the Service Initiator naming it Not Depleted. Click the Add button and select the condition phrase A MSBM AccountStatus exists. 4-31

70 Elective Use Cases Chapter 4 Elective Service Configurations Step 4 Click on that condition when it is in the table. This condition uses only the variables accountbalancecode, a Literal value equaling SOCIAL and the amountremaining variable, a Literal greater than zero. That is, if the service shows a balance code of SOCIAL, and the amount available is more than 0, this condition evaluates as true, and provides the answer TRUE to the MSBMAccountStatus as output. Service Option A matching Application Monitoring service option is available in the Service Options folder. Service Add the Application Monitoring service option to any service you create. It must be used in a service that has an account balance template to monitor usage. Go back to Elective Use Cases list if you would like to see another example of configuring Use Case Template, Service Option, Service. Turbo boost means to up sell subscriber to a faster service for a predetermined amount of time in the event that they exhaust quota amount or time. Briefly: Assign a Priority to a use case template so when the service option is invoked, it will take precedence over any other conflicting service assigned to the customer account. Create a time based Account Balance for the Turbo Boost and track usage against the balance. Use a Use Case Initiator to remove the Turbo Boost once the Account Balance is depleted. 4-32

71 Chapter 4 Elective Service Configurations Elective Use Cases Use Case Template Step 1 Create a Turbo Boost use case template with the Turbo QoS service configuration Step 2 Set your initiator name and condition. 4-33

72 Elective Use Cases Chapter 4 Elective Service Configurations Step 3 Set your condition parameters like this. This policy will only take effect when the account balance amount remaining greater than or = to zero, that is, when it is exhausted. Service Option A matching Turbo Boost service option is available in the Service Options folder. The example below show a boost of and ranges for example. 4-34

73 Chapter 4 Elective Service Configurations Elective Use Cases Service Add the Turbo Boost option to any service you create. It must be used in a service that has an account balance template to monitor usage. Go back to Elective Use Cases list if you would like to see another example of configuring Use Case Template, Service Options, and Services. Bandwidth Monitoring This feature is based on usage monitoring key being installed in order to have the usage reported by the PCEF. Using the feature, the service provider can install a monitoring key and the different thresholds that will be used to flag the subscriber. This feature works in parallel with the usage monitoring feature but the usage monitoring feature has a higher priority since that one is about charging traffic. In this context 'higher priority' means that usage monitoring feature installs any usage monitoring keys it needs to do its job. Bandwidth monitoring installs any additional monitoring keys it needs while reusing any monitoring keys that were already installed. In order to reuse a monitoring key the same monitoring key name should be used in both BandwidthMonitor and UsageMonitoringKey objects. ReportingTimeout value is in minutes and is used to set the Revalidation-Time AVP so that the subscriber has a chance to get unthrottled before the allocated dosage is used. The BandwidthThreshold Lower Value is in kbps and when the computed bandwidth used is over that value the corresponding Label is set to the subscriber for the particular application identified by Name attribute. Step 1 Create a subscriber having a regular service (e.g. IP_128KBPS) and the Bandwidth Monitoring service that only the heavy users get (e.g. OPTUS Bandwidth Monitoring). 4-35

74 Elective Use Cases Chapter 4 Elective Service Configurations Step 2 The IP_128KBPS service has the "Upsell 1" service option. For example, let us consider it includes a PreDefinedRule object, an EventTrigger object and a DefaultBearerQoS object. The DefaultBearerQoS object is overridden when the initiator is evaluated to true. The Failure use case template is not used in this scenario. 4-36

75 Chapter 4 Elective Service Configurations Elective Use Cases Step 3 The Bandwidth Monitoring service option includes the UsageMonitoringKey object that enables Gx usage monitoring for this subscriber. Note Monitoring Level attribute is set to zero (SESSION_LEVEL). 4-37

76 Elective Use Cases Chapter 4 Elective Service Configurations Step 4 This service option also includes BandwidthMonitor object. It associates a list of threshold value-threshold label pairs to a monitoring key. When the average bandwidth usage as calculated using the Gx usage report and the time span between the last quota granted and the current quota report for this monitoring key is higher than the 'Lower value', the corresponding Label is associated to the subscriber. 4-38

77 Chapter 4 Elective Service Configurations Elective Use Cases Step 5 The use-case template that overrides the DefaultBearerQoS object when the High label is associated to the subscriber service is depicted below. 4-39

78 Elective Use Cases Chapter 4 Elective Service Configurations Step 6 Create the Use Case Initiator. The configured Use Case Initiator is given below: 4-40

79 Chapter 4 Elective Service Configurations Elective Use Cases The final configured Bandwidth Monitoring is shown below. 4-41

80 Use Case Initiators Explained Chapter 4 Elective Service Configurations Use Case Initiators Explained Use case initiator values: Define the triggers for the execution of a use case Condition(s) that will be evaluated as true or false Select from an extensive library of condition phrases Conditions can bind to any data that the engine has received or is known by the PCRF Input Variable Any field available from SPR, PCEF session(s) or calculated in runtime may be referenced 4-42

81 Chapter 4 Elective Service Configurations Use Case Initiators Explained Type Literal, Output Operator Single values that aren't Boolean values: =, isnull,!isnull (Not Null), matches (Java regex matching),!matches, in (provide a comma delimited list),!in, <> (Not equals) Boolean single values: =, <>, isnull, null Lists of values: contains,!contains (Not Contains) which means the list contains or does not contain, respectfully) the value or values (if comma separated list) specified 4-43

82 Final Steps for Elective Configuration Chapter 4 Elective Service Configurations And then this: This condition uses only two variables: accountbalancecode, a Literal string. A Literal string is data, as opposed to output from some other condition. The accountbalancecode variable must be equal to FAIR_USE. The second variable is amountremaining, a Literal long number that must be less than or equal to 100,000,000. That seems quite fair. So, if this condition evaluates as true, it provides the answer TRUE as output to some other function. Final Steps for Elective Configuration The next step is to try some test traffic and test your configurations before going into production. Contact your Cisco technical representative if you have questions or need any assistance. 4-44

83 CHAPTER 5 Test the Configuration Revised: November 27, 2013, This section shows you how to validate that your configuration tasks are complete. Validation of the configuration and services involves looking at different components from both a visual level as well as using the command line interface. Because of the complexity of the system, it is necessary to start at the high level view of the system and then pursue the task at a more detailed level. Validate Configuration For configuration validation, the main configuration tools are used to check what is actually configured. Two GUI tools and the command line is available for this task. Cisco Policy Builder GUI Cisco Subscriber Services Portal GUI The command line interface (CLI) tools are all located on Control Center 01 and Control Center 02 and are accessed via the CPS user over SSH. Cisco Policy Builder GUI Cisco Policy Builder is the main configuration tool used for the policy engine. Open a browser and enter the correct URL to the Cisco Policy Builder. <IP_address>:7070/pb 5-1

84 Validate Configuration Chapter 5 Test the Configuration Display the main page by clicking OK on the Choose Policy Builder data repository page. Step 1 First, page through this interface and look for any red Xs in any of the Services, Policies, or Reference Data tabs. The figure shows two examples of error screens, one for the tree and one in a screen: Any errors denoted with a red X typically cause the polices not to load and so not allow any of the new configuration changes to be deployed. Step 2 If there are no errors in the configuration, confirm that the changes have been applied by going to the Control Center CLI, and running this command: svn log --limit 1 It may prompt you for a username and password. Enter the same user and password that is used for Publishing from the Cisco Policy Builder. It will then tell you the last time a configuration change has been made to the Cisco Policy Builder. Here is an example. r283 broadhop :03: (Thu, 10 May 2012) 1 line Added new IPs for new ISG in region and

85 Chapter 5 Test the Configuration Validate Configuration Step 3 If the configurations are published properly, check that they loaded in to the CPS Policy Engine (processing node). a. In the Control Center CLI, go to /var/log/broadhop/ and run grep "Policies successfully configured" consolidated-qns.log You should see a message like this upon the last time the policies were published, or if the CPS processing node was restarted: :04:27,769 [pool-9-thread-1] INFO c.b.policy.impl.policyconfiguration :Policies successfully configured If not found, check when the configuration change was made using the svn command above to determine what log it should be in. In some cases, the logs may have already rolled over and this message will not be found. In that case, every 5 minutes these type of messages should be printed out in the consolidated-qns.log as well. These show the state of the system :04:27,785 [pool-9-thread-1] INFO c.b.s.w.u.usumconfigurationmanager - successfully initialized the usum portal :05:00,066 [pool-10-thread-1] DEBUG c.b.d.impl.diagnosticcontroller - Starting diagnostics :05:00,067 [pool-10-thread-1] DEBUG c.b.radius.impl.radiusdiagnostics - Running radius diagnositics :05:00,158 [pool-10-thread-1] DEBUG c.b.d.impl.diagnosticcontroller - Ending diagnostics :05:00,158 [pool-10-thread-1] INFO c.b.d.impl.diagnosticcontroller - Diagnostic test passed --> Policy: 6:Last policy configuration was successful :05:00,159 [pool-10-thread-1] INFO c.b.d.impl.diagnosticcontroller - Diagnostic test passed --> Expiration Manager: 8:Current node is expiration manager :05:00,159 [pool-10-thread-1] INFO c.b.d.impl.diagnosticcontroller - Diagnostic test passed --> Session Datastore: 7:lab:27017 session management node is enabled :05:00,159 [pool-10-thread-1] INFO c.b.d.impl.diagnosticcontroller - Diagnostic test passed --> Common Services: 1:QNS server is alive :05:00,159 [pool-10-thread-1] WARN c.b.d.impl.diagnosticcontroller - Diagnostic is abnormal. A problem may exist with the system --> Common Services: 4:Session creation allowed % used 5-3

86 Validate Configuration Chapter 5 Test the Configuration :05:00,160 [pool-10-thread-1] INFO c.b.d.impl.diagnosticcontroller - Diagnostic test passed --> Common Services: 2:Memcached server is operational The "Policy: 6:Last policy configuration was successful" section shows that the last time changes were made to the configuration, they were successful. If this is not found then the system may not be running properly and will need to be diagnosed with help from your Cisco technical representative. Subscriber Services Portal GUI To access the administrator-facing screens for the portal at admin user level, open a browser and use this URL: replace with the IP address of lbvip01 from /etc/host. Enter a username and password to log in as admin. The SSP GUI is the main tool to configure the functionality of the subscriber services portal. This includes setting up locations, the text content, and the behavior of the portal. Note Step 4 Because the SSP GUI immediately posts the information into the policy engine, these configuration changes become effective as soon as you save them from this GUI. To determine your configuration, select your location and make sure it has the proper information on the Behavior tab and the Network tab. Note Be sure that there are no overlapping network mappings in the Network tabs for each Location. 5-4

87 Chapter 5 Test the Configuration Validate Configuration Services Validation Zabbix/SNMP Validating services consists of using either the Zabbix or SNMP system to determine that all of the services on all of the components are running properly. If there is an issue, then you can access the individual components to determine if the application services are running properly or not. This section uses command lines as qns user with an SSH session. Open Zabbix in a browser window and log in. <IP_Address>/zabbix Make sure all the backgrounds are green. Any red areas mean that a service may not be running. Note Zabbix runs on ControlCenter01 and 02 so if Zabbix is not running, use the checks for the services in that section below. SNMP should provide something similar as a dashboard, but that is operator specific. LB01/02 Heartbeat, memcached, and CPS (IOMgr) must be running on both load balancers, always. ps -ef grep java 5-5

88 Validate Configuration Chapter 5 Test the Configuration ps -ef grep memcached ps -ef grep heartbeat The one that is the active node (has the VIPs), must have Proxy. ps -ef grep haproxy CPS0x Java must be running for the Policy Engine to run. ps -ef grep java SessionMgr0x The sessionmgr database must be running. Depending upon the solution, there will be between 1 and 6 sessionmgr databases running. ps -ef grep mongo One is for Sessions on port and is mandatory. One is for Balance on port Two are for SPR (USuM) on port and One is for portal on port PortalLB01/02 Heartbeat must be running. ps -ef grep heartbeat The active node (which has the VIPs), must have stunnel and HAProxy running. ps -ef grep stunnel ps -ef grep haproxy Portal0x Apache and Tomcat must be running. ps -ef grep httpd ps -ef grep java ControlCenter01/02 Apache, Cisco Policy Builder, CPS, and MySQL must be running. ps -ef grep httpd 5-6

89 Chapter 5 Test the Configuration Checking Access ps -ef grep java grep pb ps -ef grep java grep pcrf ps -ef grep mysql Checking Access When you are confident that the installation and configuration tasks are complete and processing properly, try running a small amount of test traffic, following it through the system. Here are three ways to ascertain correct process of access from a subscriber perspective. Testing Subscriber Access with 00.testAccessRequest.sh Step 5 00.testAccessReqest.sh is a test script used to test subscriber access to the ISG and CPS system. You cna find the 00.testAccessReqest.sh in /opt/broadhop/installer/isg/troubleshooting directory on the CPS server. To configure the subscriber used, edit /opt/broadhop/installer/isg/troubleshooting/config.ini file. In the config.ini file, change the User-Name and Password fields. Note Step 6 You may need to change some of the other parameters in order to match your configuration. The other main attributes to change will be the NAS-IP-Address and Framed-IP-Address. Run the script from a command line. No arguments are necessary: 00.testAccessRequest.sh 5-7

90 Checking Access Chapter 5 Test the Configuration Upon success, this output displays: Testing Subscriber Access with soapui This procedure tests end subscriber access to your system. Step 1 Step 2 Step 3 Download soapui from here: You only need the freeware version (not soapui Pro). Launch soapui. Right click on projects, select New soapuiproject from the drop-down menu. 5-8

91 Chapter 5 Test the Configuration Checking Access Step 4 Name your project and enter into Initial WSDL/WADL the appropriate WSDL URL (you may have to replace the IP in display with your own IP) and select OK: 5-9

92 Checking Access Chapter 5 Test the Configuration Step 5 In the tree click Demo > SubscriberBinding > GetSubscriber > Request 1, as shown in the figure on the right. Step 6 Edit the End Point by selecting from the drop down: [edit current...]. Enter the appropriate IP. Step 7 In the XML file: Replace the? in <typ:networkid>?</typ:networkid> with the appropriate credential or network Id. Replace the? in <typ:returnsessions>?</typ:returnsessions> with "True". 5-10

93 Chapter 5 Test the Configuration Checking Access Replace the? in <typ:returnbalance>?</typ:returnbalance> with "True". Step 8 Click on the green arrow (underneath Request 1"). 5-11