1. Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext LT Medium Font to be used by customers and partners : Arial HUAWEI TECHNOLOGIES CO., LTD. www.huawei.com PCRF Information Gateway2013 ISSUE 11 Improvements on PCRF Documentation

2. How Many Types of UPCC Documents Are There? How Do I Obtain Them? Marketing and Sales Documentation Marketing Documentation Sales Documentation Technical Service Documentation HLD, LLD Release Documentation Testing Documentation Patch Documentation Maintenance Cases Training Documentation CPI Documentation CPI (HedEx Documentation) Customer Sales engineer Technical support engineer Support website Training center

3. Feature Document Software Parameter Feature Guide(Integrated Service) SOAP Interface Quota Reset Parameters Performance Entity Signaling Analysis QoS Data Backup and Restoration Result Code Delta (Version Changes) PCRF Top N Documentation Improvement Roadmap 2013 Before 2013

4. Feature Documentation: makes an E2E understanding on features (Phase 1) Your VoicesOur Actions (1) How to obtain end-to-end feature documentations? Use the same feature name in the function list, feature description, and feature guide for each feature, which facilitate your search. (2) What is the value and impact of a feature? Provide detailed information on the Benefits, Impact on System, Interaction with Other Features, and Principles sections. (3) How to configure a feature?Take a typical scenario as an example to explain how to configure data for the feature. Your Suggestions: Does the preceding feature introduction meet your requirements? Do you have any other suggestions? Would you like to keep a long-term communication with us during the documentation application? Obtain Documentation: UPCC V300R005C01 UPCC V300R003C01

5. Feature Document: makes features more clearer (Phase 2) Does the feature description and guide meet your requirements? Do you have any other suggestions? Would you like to keep a long-term communication with us during the documentation application? Your Suggestions: Your VoicesOur Actions (1) The background information and network architecture related to service implementation are not provided. Provide the background information and network architecture in the Definition section to present the service implementation from the point of customers' view. (2) The application scenario of a feature is not provided.Provide the typical application scenario of a feature to help you to use the feature easily and quickly. (3) The feature principle shown in the message flow is not network- wide. In addition, the meanings of VAPs, commands, and software parameters involved in a message flow are unavailable. (a) Provide the specific message diagram to present key message flows. (b) Provide links for VAPs, commands, and software parameters involved in a message flow. (1) (2) (3)

6. Software Parameter Document: provides detailed information for easy use Your VoicesOur Actions (1) The function and background information about a software parameter needs to be provided. Provide detailed background information to help your learn the function of a software parameter. (2) The configuration suggestion is required for the live network application. Provide a typical application scenario and recommended configuration based on site requirements. (3) The impact on the system needs to be clarified if a software parameter is set to a too large or small value. Provide the impact on the system if a software parameter is set to a too larger or small value to help you evaluate the configuration impact and reduce the configuration risk. (4) The relationship between a software parameter and its related software parameter needs to be provided. Provide all related software parameters to help your learn the relationship between the software parameter and its related software parameters. (5) How does a software parameter take effect after being modified? Clarify the modification effective time to clear your doubts. (6) Are there any common troubleshooting cases related to a software parameter? Add related troubleshooting cases to help you rectify faults rapidly. Obtain Documentation: V300R005C01 V300R005C12V300R005C01V300R005C12V300R005C13 V300R005C15V300R005C13V300R005C15 (1) (2) (3) (4) (5) (6)

7. Signaling Analysis: Provides Detailed Message Flow, Message Description, and AVP Description (1) Your VoicesOur Actions (1) How to handle complaints from subscribers ？ Provide the Signaling Analysis manual to tell you how to create a message tracing task, understand traced messages, and locate the fault. (2) Details on the message flow, messages, and AVPs are required. Provide standard compliance, and message and AVP description to help you understand what the messages and AVPs are. (1) Customer service center receives complaints from subscribers. Maintenance center receives fault reports. Create a user interface tracing task. Locate error signaling messages. Find error codes and AVPs contained in messages. Search for AVPs or error codes, and rectify faults step by step. AVP name: Max-Requested-Bandwidth-DL

8. Signaling Analysis: Provides Detailed Message Flow, Message Description, and AVP Description (2) Obtain Documentation: UPCC V300R005C01 UPCC V300R005C01 UPCC V300R005C12UPCC V300R005C12 UPCC V300R005C13UPCC V300R005C15 Your VoicesOur Actions (1) How to handle complaints from subscribers ？ Provide the Signaling Analysis manual to tell you how to create a message tracing task, understand traced messages, and locate the fault. (2) Details on the message flow, messages, and AVPs are required. Provide standard compliance, and message and AVP description to help you understand what the messages and AVPs are. (2)

9. Integrated Service Sample: a good helper for advanced features Your VoicesOur Actions (1) How do the UPCC, GGSN, and OCS work together to implement PCC services? Provide the complete PCC architecture, message flow, and collaboration principles for these NEs. (2) How are various features used on the live network?Select high-frequency service scenarios based on the requirement research to help you start learning from the most typical features. (3) How to obtain parameter configurations from the original requirement analysis? Provide the detailed service analysis flow and methods for service design. (4) Which configurations are required on the UPCC and GGSN?Provide the configuration procedures to be performed on the UPCC and GGSN to help you implement end-to-end service deployment. (1) (2) (4) (3) Does the improvement direction and effectiveness meet your expectations? Which service scenarios are commonly used in your work? Do you have any other better service analysis flow or methods? Your Suggestions: Obtain Documentation: UPCCV300R003C01 UPCCV300R005C01 UPCCV300R005C15

10. Quota Reset Parameters: enable you to learn quota reset principles in the round Your VoicesOur Actions (1) What is the flexibility of the UPCC quota reset?Provide detailed parameter meanings to help you learn the flexible charging period feature of the UPCC. (2) Which processing logic is used for different reset modes? Provide a clear diagram of quota reset logic to clear your doubts. (3) How to flexibly set parameters according to my requirements? Provide typical application examples to tell you how to set parameters rapidly. Does the improvement direction and effectiveness meet your expectations? Does the Quota Reset Parameters manual provide all information you desired? Your Suggestions: Obtain Documentation: V300R006C01 (1) (2) (3) Provides the detailed meaning and background information of a parameter. Provides the detailed associated relationship between parameters. Provides details on internal processing logics of a parameter.

11. Result Code Description of the Gx Interface Makes Your Troubleshooting Work Easier Documentation Version: UPCC V300R006C01 (1)(2) Message flows for complicated causes Common possible causes (3) Related performance counters (a), alarms (b), and software parameters (c) a b c (1)How to handle error result codes found in messages during commissioning? (2) What possible causes are there for a result code? When and where is the result code generated? (3) After knowing the fault related to a result code, how to fix the fault? Your Voices: Our Actions: Signaling Analysis and Result Code documents are provided to describe result codes. Common causes are provided. Message flows are provided to describe when and where result codes are generated. Step-by-step procedures are provided for users to fix related faults.

12. SOAP Interface: makes service provisioning simple and easy Does the improvement direction and effectiveness meet your expectations? Which error codes are commonly used during your work? Is the recommendation of these return codes doing enough to support your work? Your Suggestions: Your VoicesOur Actions (1) The parameters are too unclear to configure during adaptation development of commands. Add detailed information to parameter description and configuration principles to help you easily complete adaptation development of commands. (2) How to deal with it if a SOAP request fails to be initialed during service provisioning? Provide commonly used return codes to help you rectify such a failure in a fast way. (3) How to deal with it if an interworking fault occurs? Provide descriptions on common interworking faults to help you troubleshoot the interworking fault. (3) (1) (2)

13. QoS Manual: a quick start for the QoS Your VoicesOur Actions (1) What is QoS? How it defined in the SGPP specifications?Provide detailed information to help you understand QoS basic concepts. (2) How to negotiate the QoS in the PCC architecture?Provide clear negotiation principles to clear your doubts. (3) What are typical applications and configurations for QoS guarantee? Provide typical applications and configuration to help you use the QoS services rapidly. (4) How to locate a QoS fault?Provide common problem analysis and troubleshooting to help you rectify faults rapidly. Does the improvement direction and effectiveness meet your expectations? Does the QoS manual provide all information you desired? Your Questions:Obtain Documentation: UPCC V300R006C01 Describes basic concepts and parameters related to the QoS. Overview Describes the evolution of the QoS solution and the end-to-end QoS negotiation among Nes on the UMTS and EPS networks. QoS in UMTS and EPS Networks Describes typical QoS application scenarios. Typical QoS Applications and Configuration Describes how to troubleshoot the QoS-related fault. Common Problem Analysis and Troubleshooting

14. Performance Counters: assists in your performance maintenance Your VoicesOur Actions (1) The description on measurement entities is too simple to understand their functions. Add the application scenario and measurement information to help you understand the usage of a measurement entity. (2) The measurement point is unclear.Provide details on the condition at which the measurement entity is triggered. The combination of contents and figures makes a clear understanding on the measurement point. (3) How to deal with it if an measurement entity is abnormal?Add reference information for abnormalities, which makes the measurement entities much instructive. (1) (2) (3) Does the improvement direction and effectiveness meet your expectations? Which measurement entities are required during your work? Is the Performance Metric Reference document doing enough to support your work? Your Suggestions: Obtain Documentation: UPCC V300R006C01

15. Delta Information: helps you easily learn differences between versions (1) Your VoicesOur Actions (1) How to rapidly learn about the differences between two adjacent versions?Build a complete Delta document system, including general impact (global view), feature impact (service view), and Delta information (professional view) to solve different problems for different objects in different scenarios. (2) The Delta information document based on the actual upgrade path must be provided to support customized upgrade schemes. Provide Delta descriptions for each upgrade path, which helps you learn version differences in an efficient way. (3) How to learn about the impact on existing features after a version upgrade?Provide changes and network impact after a version upgrade from various aspects, including capacity and performance, hardware, configuration, performance, alarms, performance entities, and Inter-NE interfaces. (4) How to learn about detailed information about changes to software parameters, commands, interfaces, and alarms? Provide Delta information in the excel format to describe change description and change impact, which help you adapt to third-party development. Provides an overview of the impact that the new version has on the network, including the system Hardware, performance, capacity, license, and FCAPS. General Impact Describes the impact that feature changes between two adjacent versions have on the network. The Feature changes include changes to the alarms, configuration, and CDRs. Feature Impact Describes detailed changes to the alarms, MML commands, software parameters, timers, License, and CDRs in tables and provide impact analysis on these changes. Delta Information Providing Delta descriptions for each upgrade path (1) (2)

16. Delta: Helps You Better Understand Version Differences (2) Your VoicesOur Actions 1. How should I know the version differences more quickly?Divided the Delta document into three parts: general impact (in terms of the whole system), impact of features (in terms of services), and delta records (from a professional perspective). 2. The delta description based on actual upgrade path is not provided.Provided delta description based on actual upgrade path, which helps you understand the version differences more efficiently. 3. The manual does not provide the impacts on features after the upgrade. Provided the impacts from the perspective of capacity and performance, hardware, configuration, performance management, alarm, license and so on. 4. The manual does not provide changes in software parameters, commands, alarms, which could be used for third-party software development. Provided delta records in.xls format, which facilitates third-party software development. Do the improvements we have made fit in with your expectations? Does the Delta manual helps you to perform the evaluation before the upgrade more efficiently? Questions: Obtain Documentation: 34 V300R005C15 - V300R005C12

17. Data Backup and Restoration: A Useful Tool for System Reliability Your VoicesOur Actions 1. The manual does not provide details about the principles of data backup and restoration. Added detailed description about principles of data backup and restoration and optimized the structure according to a specific template. 2. The given operations cannot guide on-site engineers to back up and recover data. Provided command examples, required time, check criteria for your reference. 3. The manual does not provide the configuration procedure for a concrete scenario. Offered configuration procedures for a concrete scenario to facilitate data configuration. 1 2 3 Do the provided principles of data backup and restoration satisfy your requirement? Do the given application scenarios include all the specific scenarios you have met? Questions: Obtain Documentation: UPCC V300R005C13 UPCC V300R006C01

18. How Do I Download and Update CPI? Downloading CPIs from the support website Downloading and updating CPIs using HedEx Lite 1 2 2 1 Use the online query function provided by HedEx Lite to download and update the desired CPI. Enable the automatic upgrade function provided by HedEx Lite to update the desired CPI. Note: The file name extension of a CPI is.hdx. You need to download and run HedEx Lite before you can view the CPI. HedEx Lite Support website: Documentation > Core Network > Core Network Unified Subscriber Center-USC > UPCCUPCC

19. THANK YOU www.huawei.com Copyright©2013 Huawei Technologies Co., Ltd. All Rights Reserved. The information contained in this document is for reference purpose only, and is subject to change or withdrawal according to specific customer requirements and conditions.