01-OWR571101 UPCC System Overview and Networking Introduction ISSUE1.00.pdf

UPCC System Overview and Networking Introduction www.huawei.com

Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.

Foreword 

This course mainly introduces the UPCC system overview, including UPCC Product Description, Product structure, Application Scenario.


Page2

References 

UPCC Product Documentation


Page3

Objectives 

Upon completion of this course, you will be able to: 

Understand the position of UPCC in the network



Grasp the service flow and principle



Grasp the hardware and software structure and the specifications


Page4

Contents 1. Product Orientation and Application Scenario 2. Interfaces and Protocols 3. System Structure 4. Services and Functions Introduction 5. UPCC Message Flow 6. Performance Specifications


Page5

Product Orientation 

By leveraging various solutions such as quality of service (QoS) and charging solutions, the Unified Policy and Charging Controller (UPCC) allows flexible policy configuration for fixedline, mobile, and IP Multimedia Subsystem (IMS) services.



UPCC provides the functions of policy management, service management, subscription management, quota management.


Page6

Product Orientation (Cont.) Expands telecom services, cuts down Total Cost of Operation (TCO), and enhances user experience. Leverages network resources and services in a flexible way to free the network from evolving to an "information pipeline". The UPCC also effectively addresses the changing demands of various business modes on the resource and policy control. Advantage of UPCC

Works with the broadband remote access server (BRAS) to implement policy control on fixed-line services. Works with the gateway GPRS support node (GGSN), Service Awareness (SA), PDN Gateway (P-GW) to implement policy control on mobile services such as roaming quota notification and fair usage policy (FUP). Works with the proxy-call session control function (P-CSCF) to implement policy control on IMS services.


Page7

Mobile Network Solution 

The Unified Policy and Charging Controller (UPCC) provides rich and flexible policy control functions, helping carriers make proper use of network resources and maximizes returns for carriers from their investments by enhancing service quality and user experience of very important person (VIP) subscribers.



The mobile network solution can be classified into the following two networking: Networking Type Direct connection with the Gateway GPRS support node (GGSN)/PDN gateway (P-GW) Direct connection with the DPI

Description 

The Service Awareness (SA) is embedded in the GGSN/P-GW



The DPI is independently deployed.


Introduction The UPCC works with Deep Packet Inspection (DPI) to implement service-specific policy control.

Page8

Position of UPCC in Mobile Network Networking topology of direct connection with the GGSN/P-GW


Page9

Position of UPCC in Mobile Network

Networking topology of direct connection with the DPI


Page10

SmartPCC Solution


Page11

VoLTE Solution





Voice over Long Term Evolution (VoLTE) is an IMS-based solution and is defined by 3GPP. IMS networks help carriers not only seamlessly deploy traditional voice services and short message service (SMS) but also integrate voice services with enhanced services, providing more services to subscribers. The UPCC communicates with the Proxy-Call Session Control Function (PCSCF) over the Diameter-based Rx/Gx interfaces, provides applicationspecific policy control, and ensure the QoS of networks.


Page12

Contents 1. Product Orientation and Application Scenario 2. Interfaces a nd P rotocols 3. System Structure 4. Services and Functions Introduction 5. UPCC Message Flow 6. Performance Specifications


Page13

UPCC Protocol Interfaces


Page14

UPCC Protocol Interfaces (Cont.) Interface

Interworking Device

Signaling Protocol 

LDAP （Lightweig ht Directory Access Protocol） SOAP （Simple Object Access Protocol）

Sp

External SPR

Gx

PCEF (functioning as the GGSN, DPI,

Diameter/RADIUS （Remote Authentication

P-GW, BRAS, or PDSN)

Dial-In User Service）



Usage









LDAP Enables communication with the external SPRof tosubscribers. obtain subscription information SOAP Enables communication with the external SPR to send subscription notification over the SOAP interface to the UPCC. Diameter Enables communication with the PCEF to provide policy control. RADIUS Enables communication with the PCEF to provide policy control.


Page15


Interworking Device

Signaling Protocol

Usage 

Rx

RESTfulbased Rx

Gpt

EDR

AF

Diameter 

AF

Portal Server

EDR server

HTTP/HTTPS

Enables communication with the AF to receive requests from application systems. Enables communication with the AF to receive RESTful requests from the AF.



Enables communication with the Portal server to receive requests from application systems.



Enables the UPCC to send the EDRs compressed in the comma-separated value (CSV) format to the EDR server.

SOAP

FTP/SFTP


Page16


Short Message Peer to Peer

Interworking Device

Signaling Protocol

Usage 

SMC

SMPP

(SMPP) 

Sy

OCS

Diameter

SOAP/MML

Provisioning system

SOAP/MML

CLI

CLI Client

MML

TDF

subscribers. Enables communication with the OCS to obtain quota information about subscribers.



Enables communication with the provisioning system to provide services to subscribers.



Enables communication with the CLI client to configure policy data.



Sd

Enables communication with the SMC to send notifications by sending short messages to

Diameter


Enables the communication with the TDF to provide application detection and policy control. Page17


Interworking Device

Signaling Protocol

Usage 



Simple Network Management Protocol (SNMP)/MML/S OAP/Network Time Protocol (NTP)



M2000

SNMP/MML /SOAP/NTP 

SNMP Enables the UPCC to report alarms to the M2000. MML Enables the UPCC to receive MML commands from the M2000. SOAP Enables the UPCC to receive SOAP commands from the M2000. NTP Enables communication with the M2000 to ensure time synchronization between the M2000 and the O&M subsystem of the UPCC and time synchronization among all the NEs on the network.


Page18

Contents 3. System Structure 3.1 Software Architecture 3.1.1 ME Software 3.1.2 VNFM 3.1.3 OMU 3.1.4 Platform Application 3.1.5 Virtualization software 3.2 System Architecture


Page19

Software Architecture


Page20

Software Architecture 

ME Software 

The UPCC software layer is logically divided into the front end (FE) and the back end (BE):



FE, that is, the UPCC, processes protocol messages and service requests and manages policy data.



BE, that is, the USCDB, stores and manages the subscriber data and provides open interfaces for data access.


Page21


ME Software


Page22


VNFM 

Virtual Network Function Manager (VNFM), the virtual machine management software of the network functions virtualization (NFV) architecture. The VNFM deploys MEs running applications, manages lifecycles, scale-up, and scale-down, and reports alarms and key performance indicators (KPIs) of the virtualization layer and hardware layer.



The VNFM connects to the OMU to operate and maintain MEs, forwards the commands issued by the VOMU to the FusionSphere or Vmware.


Page23


VNFM


Page24


OMU 

The U2000 and VNFM connect to the operation & maintenance unit (OMU) to operate and maintain managed elements (MEs).


Page25


Platform Application 

The platform application layer consists of high-availability PMUs on the virtual machines (VMs) running applications. Each VM runs one PMU.


Page26


Virtualization software 

FusionSphere


Page27


Virtualization software 

VMware software


Page28

Contents 3. System Structure 3.1 Software Architecture 3.2 System Architecture 3.2.1 Service Processing Subsystem 3.2.2 Policy Enabler Subsystem 3.2.3 Policy Data Management Subsystem 3.2.4 Subscriber Data Management Subsystem 3.2.5 Data Service Subsystem 3.2.6 Data Storage Subsystem 3.2.7 Virtualization Subsystem Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved.

Page29


Page30


Page31

Service Processing Subsystem 

The service processing subsystem processes protocol stack messages. Based on the received messages, it obtains subscriber data from the back end (BE), makes policy decision accordingly, and returns the result to the peer end.


Page32

Service Processing Subsystem Module

Function 



NPU 



PPU

Provides floating IP addresses for the peer end, distributes the service requests to the PPU based on the protocol and links, and forwards the responses sent from the PPU to the peer end. Forwards the messages sent from the PPU to the peer end and the responses from the peer end to the PPU. Obtains subscriber data and subscription data from the external subscription profile repository (SPR) over the Lightweight Directory Access Protocol (LDAP) interface when the subscriber sets up an IP Connectivity Access Network (IP-CAN) session. The PPU encodes and decodes the TCP/SCTP/Diameter/RADIUS/Simple Object Access Protocol (SOAP)/LDAP/DS call interface (DCI) protocol messages, converts the messages to internal messages, and forwards the messages to the SPU.


Page33


Function 



SPU 

The SPU receives service requests sent from the PPU, processes the requests based on the subscriber data cached in the local memory, and returns the result to the PPU. When processing messages from subscribers, the SPU generates event data records and sends the records to the EDR server by using the main processing unit (MPU). The SPU performs the policy decisions based on the subscription and session information, and delivers the generated policies to the peer end.



The SDU stores the IP address, session ID, and subscriber ID based on which the messages are distributed. It ensures that the messages in a session srcinated by a subscriber are sent to the same SPU.



Collects the data access requests from the SPU and policy data management subsystem, and forwards the requests to the data service subsystem.



Receives the data access responses from the data service subsystem, and forwards the responses to the SPU and policy data management subsystem.

SDU

DSG


Page34


Function 

Provides service interfaces for the BE and aggregates ports.



Forwards the received IP packets to the DSG module based on the quintuple (source IP address, source port number,

DPU

destination IP address, destination port number, and protocol type) contained in the received packets. 

Forwards the IP packets from the DSG module to the peer NE.


Page35

Service Processing Subsystem Interfaces


Page36

Service Processing Subsystem Interfaces Interface

Function

Protocol

Signaling interface

Enables the UPCC to communicate with the peer NEs.

Diameter，RADIUS， SOAP

Data access interface (DCI)

Enables the FE to communicate with the data routing unit (DRU) to query and modify the data stored in the data service subsystem.

DCI

Data access interface (LDAP)

When the subscriber sets up an IP Connectivity Access Network (IP-CAN) session, it obtains subscriber data and subscription data from the external subscription profile repository (SPR) over the Lightweight Directory Access Protocol (LDAP) interface.

LDAP

OM interface

Internal Enables each module to report module status and alarms to the OMU for monitoring purpose. communication mechanism provided by the CGP platform


Page37

Policy Enabler Subsystem



The policy enabler subsystem provides the protocol conversion function that converts RESTful requests sent from the application function (AF) to standard Diameter messages through internal encoding and decoding.


Page38

Policy Enabler Subsystem Module

Function 

DPU 



PEU  

NPU

Receives RESTful requests from the application function (AF) and distributes the requests to available PEU modules. Sends responses to the AF. Converts RESTful requests forwarded by the DPU module to standard Diameter messages. Converts standard Diameter messages to RESTful messages. The NPU provides floating IP addresses to the external subsystems. It distributes received service requests to the NPU modules of the service processing subsystem based on the protocol and link configurations.


Page39

Policy Enabler Subsystem Interfaces


Page40

Policy Enabler Subsystem Interfaces Interface

Function

Protocol

Receives RESTful requests from the application function (AF) and returns responses to the AF.

Hypertext Transfer Protocol (HTTP) Hypertext Transfer Protocol Secure (HTTPS)

Rx interface

Sends converted Rx resource management messages to the service processing subsystem and receives responses (such as RAR messages) from the service processing subsystem.

Diameter

OM interface

Enables each module to report module status and alarms to the OMU for monitoring purpose.

RESTful-based Rx interface


Internal communication mechanism provided by the CGP platform

Page41

Policy Data Management Subsystem



The Policy data management subsystem is mainly used for the management of the policy data (such as condition and action data).


Page42

Policy Data Management Subsystem Module

Function 



NPU



  

PAU 

Provides floating IP addresses for UPCC Web UI, and distributes service requests to the PMS modules based on the protocol types and links. Forwards messages sent from the internal modules to the external NEs. Receives the srcinal and updated data from the external subscription profile repository (SPR) over the subscription notification interface over Simple Object Access Protocol (SOAP) when subscriber data on the external SPR changes. Provides the command-line interface (CLI) to communicate with the CLI client to maintain, and import the policy data. Forwards short message notifications sent from the signaling processing unit (SPU) to the PMS. Forwards policy data update notifications sent from the PMS to the SPU. Communicates with the data service gateway (DSG) of the service processing subsystem to interact with the data service subsystem.


Page43

Policy Data Management Subsystem Module

Function 



PMS

 



MPU 

Trial SPU 

Functions as the Web server to provide the UPCC Web UI, and encodes and decodes messages sent from the UPCC Web UI. Processes the service logic for policy management. Provides interfaces to the short message center (SMC), email server or SOAP server for sending notifications to subscribers. Encodes and sends Java Messaging Service (JMS), Short Message Peer to Peer (SMPP), Simple Mail Transfer Protocol (SMTP) and Simple Object Access Protocol (SOAP) notifications. The primary main processing unit (MPU) sends the received messages to auxiliary MPUs based on the load balancing principle. The trial SPU performs the following functions: Loads submitted global data of test subscribers. Sends the test subscriber list to the SDU.


Page44

Policy Data Management Subsystem Interfaces


Page45

Policy Data Management Subsystem Interfaces Interface Operator interface Notification interface

Function

Protocol

Hypertext Transfer Enables the UPCC to receive operation Protocol Secure (HTTPS) commands from the UPCC Web UI and for communicating with return operation results to the UPCC Web UI. the UPCC Web UI It allows the UPCC to send notifications by SMPP/SMTP/CMPP/JMS/S short messages or E-mails. OAP

OM interface

Enables each module to report module status and alarms to the OMU for monitoring purpose.

Internal communication mechanism provided by the CGP platform

command-line interface (CLI)

Receives commands from the CLI client and returns operation results.

Telnet

Receives the srcinal and updated data from the external subscription profile repository Data access (SPR) over the subscription notification interface (SOAP) interface over SOAP when subscriber data on the external SPR changes.

SOAP


Page46

Subscriber Data Management Subsystem



The subscriber data management subsystem mainly manages subscriber data such as subscriber IDs and services.


Page47

Subscriber Data Management Subsystem Module

DPU

Function 

Provides service interfaces for the provisioning system and PGW Web LMT and acts as a portal for incoming and outgoing IP datagrams.



Forwards the received IP packets to the PGW module for processing based on the quintuples (source IP address, source port number, destination IP address, destination port number, and protocol type) contained in the received packets. Forwards the IP packets processed by the PGW module to the provisioning system or PGW Web LMT. Provides the Pre-Sy interface for communicating with the OCS and implements modification of information such as the quota status and reset time. Provides the SOAP interface for communicating with the SPG to define and delete Voice over Long Term Evolution (VoLTE) subscribers and provide and withdraw services in a centralized way.

 




Page48

Subscriber Data Management Subsystem Module

Function 

DTL  

PGW

 



Receives the subscriber data exported by the SDMT tool, imports the subscriber data to the in-memory database through the DS call interface (DCI), and export global data. Processes the messages sent from the provisioning system and PGW Web LMT. Transfers synchronization files between the active and redundancy USCDBs and runs the synchronization files. Interacts with the FE to process subscription notification messages. Interacts with the data service gateway (DSG), which then interacts with the data routing unit (DRU) and data service unit (DSU), to update the subscriber data, global data, and common data. Interacts with the physical database to store operation logs.


Page49

Subscriber Data Management Subsystem Interfaces


Page50

Subscriber Data Management Subsystem Interfaces Interface

Function

Protocol

Interfaces to the Enables the provisioning subscriber data

The subscriber data management subsystem communicates with the PGW

system, PGW Web LMT and SPG

Web LMT by using the MML protocol.

management subsystem to receive subscriber operation commands and return operation results.

The subscriber data management subsystem communicates with the SPG by using the SOAP protocol. The subscriber data management subsystem communicates with the provisioning system by using the MML and Simple Object Access Protocol (SOAP). SOAP is used in the IMS-HSS, UPCC, and ENS. MML is used in the other FEs.


Page51


Function

Protocol

Subscription notification

Enables the Provisioning gateway (PGW) to The PGW communicate with the FE using message call communicates

interface

interface (MCI) or SOAP. After modifying the global data, the PGW sends a notification to all the FEs of this application type. After modifying the subscriber data, the PGW sends a notification to the FE that have subscribed to notifications.


Page52

with the FEs by using the MCI protocol.


Function

Enables the PGW to communicate with the data service subsystem and the data storage subsystem. The PGW accesses the data service subsystem to store subscriber data, global data, and common data. Data access interface

Protocol

The PGW communicates with the data service subsystem by using the DS call interface (DCI) protocol.

The PGW and DTL communicate with the The PGW accesses the data storage data storage subsystem subsystem to store PGW operation logs. by using the DB API protocol. Data tool (DTL) imports subscriber data to the in-memory database through the Data access interface and exports global data from the in-memory database.


Page53

Data Service Subsystem



The data service subsystem provides data services which are distributed data storage and data caching in the memory.


Page54

Data Service Subsystem Module

Function



Provides service interfaces for other NEs and acts as a portal for incoming and outgoing IP datagrams. Forwards the received IP packets to the DSG module for processing



based on the quintuples (source IP address, source port number, destination IP address, destination port number, and protocol type) contained in the received packets. Forwards the IP packets processed by the DSG module to related NEs.



DPU





DSG 

Collects and maintains the state of each node in the DRU and DSU clusters of the BE. The nodes are externally shielded so that the external entities communicate only with the DSG. Dispatches the received data access requests to the nodes in the clusters based on the operation type (query or update), and forwards data access responses to the peer end. Broadcasts the status information of the DRU clusters to the DSG of the FE or other BEs. The status information does not include the status information of the nodes in the DRU clusters.


Page55

Data Service Subsystem Module

Function  

DRU  

DSU 

Provides the data routing function and stores the global data and routing data. Locates the DSU cluster in which the required subscriber data is stored and chooses a DSU node from the DSU cluster based on the load-balancing strategy to provide the data query service or the master DSU node to provide the data update service. Multiple DRU clusters can be configured. You can set the DRU clusters used for storing routing data and global data. Stores subscriber data and provides the DRU with data services such as querying, adding, deleting, and updating the subscriber data. Multiple DSU clusters can be configured. The subscriber data is distributed among the DSU clusters.


Page56

Data Service Subsystem Interfaces


Page57

Data Service Subsystem Interfaces Interface

Data access interface

Function

Protocol

Enables other subsystems to query, modify, delete, and update the data stored in the data service subsystem.

DS call interface (DCI)

Enables the data service subsystem to synchronize updated data to the physical database, load data from the physical database, and perform data consistency check between the data service subsystem and the physical database.

DB API


Page58

Data Storage Subsystem



The data storage subsystem stores all the data managed by the Unified Subscriber Center Database (USCDB).


Page59

Data Storage Subsystem Module

Function 

DBG

 

NDF





PT

Serves as the access point to connect to all the data routing unit (DRU) and data service unit (DSU) nodes. Converts the format of the messages between the physical database and the DRU or DSU nodes. Physical database management: The NDF provides the backup and restoration, upgrade and rollback, and password modification functions. Platform resource monitoring: The NDF monitors the status of the platform resources, including the database, cluster, and disk partition. In addition, it reports alarms when a fault is detected. The PROTON database, serving as the database management system (DBMS), backs up the data stored in other modules. It is independent of service processing.


Page60

Data Storage Subsystem Interfaces


Page61

Data Storage Subsystem Interfaces Interface

Data access interface

Function

Protocol

Enables the data storage DB API subsystem to communicate with the data service subsystem and the subscriber data management subsystem.

Enables each module to report Internal communication OM interface module status and alarms to the mechanism provided by OMU for monitoring purpose. the CGP platform


Page62

Virtualization Subsystem


Page63



Page64

VM Features


Page65



Page66



Page67

Functions of UPCC Functions

Description 

Policy Control over the Gx Interface Using Diameter

Multi-Signaling Connections with a Peer Device

The Policy Control over the Gx Interface Using Diameter feature allows the Unified Policy and Charging Controller (UPCC) to exert dynamic policy control over the policy and charging enforcement function (PCEF). In thethe case of IPCAN session establishment or event trigger, UPCC makes a policy decision according to the information reported by the PCEF, subscription data, and status information, and delivers the policy and charging control (PCC) rule to the PCEF for enforcement.



The Unified Policy and Charging Controller (UPCC) can establish multiple signaling links over Diameter, RADIUS, or Simple Object Access Protocol (SOAP) with an NE to improve reliability and exchange a large number of messages with the NE.


Page68

Functions of UPCC (Cont.) Functions

Description 

The User Plane IPv6 feature allows the Unified Policy and Charging Controller (UPCC) to analyze the IPv6 address contained in a Credit Control Request (CCR) message sent by the policy and charging enforcement function (PCEF).



A service package is a combination of services. An administrator can combine multiple services into a service package. After subscribing to a service package, a subscriber is provided with all the services in the service package.



This feature allows carriers to classify subscribers into different groups based on subscriber attributes such as category or location area. Carriers can define and implement policies by groups, which allows the subscribers in different groups to be provided with different QoS. This feature also allows carriers to specify charging server groups based on subscriber groups. The UPCC randomly selects a charging server from the charging server group associated with a subscriber group. The PCEF interworks with the selected charging server to perform charging management.

User Plane IPv6

Service Package Management

Subscriber Group Management




Page69

UPCC Services Services

Description 

PCRF Geographic Redundancy

The PCRF Geographic Redundancy feature allows the PCRFs that are deployed in different places to work as the backup for each other. The active PCRF provides services, and the redundancy PCRF synchronizes data with the active PCRF in real time. If the active PCRF fails, the redundancy PCRF takes over services from the active PCRF.



If the Unified Policy and Charging Controller (UPCC) connects to multiple policy and charging enforcement functions (PCEFs) of different types, each policy and charging enforcement function (PCEF) may request the UPCC to establish a Gx session after a subscriber initiates an IP connectivity access network (IPCAN) session establishment request.



The Default Quota feature allows carriers to correlate certain default services with default quotas and provide these default

Multi-PCEF

Default Quota

services for subscribers. The Unified Policy and Charging Controller (UPCC) performs policy control based on the status of the default quotas.


Page70

UPCC Services (Cont.) Services

Description 

Multi-Quota

The Multi-Quota feature allows the Unified Policy and Charging Controller (UPCC) to associate a subscriber with multiple quotas and perform policy control based on the status of these quotas. The policy update includes updating quality of service (QoS) or charging rates, redirecting access, sending notifications, switching services, and blocking services.

Enhancement to Subscriber Notification with Customized Threshold

Cell Congestion Control



A notification is sent to a subscriber if the quota or account usage of the subscriber reaches a specified threshold. The Enhancement to Subscriber Notification with Customized Threshold feature allows subscribers to customize the thresholds on the Portal provided by carriers.



The Cell Congestion Control feature allows the Unified Policy and Charging Controller (UPCC) to dynamically update bandwidth control policies based on the congestion status of cells and the cell congestion level reported by the policy and charging enforcement function (PCEF). This feature also allows the UPCC to perform different policies for the subscribers in a congested cell based on the subscriber priority.


Page71

UPCC Services (Cont.) Services Enhancement to Usagebased Dynamic Policy Control with Top-up Quota

Description 

The Enhancement to Usage-based Dynamic Policy Control with Top-up Quota feature allows subscribers to purchase additional quota when needed.



The Usage-based Dynamic Policy Control feature allows the Unified Policy and Charging Controller (UPCC) to update policies (for example, adjust the access bandwidth) based on the data volume used by subscribers within a specified period.



The Duration-based Dynamic Policy Control feature allows the Unified Policy and Charging Controller (UPCC) to update policies based on the duration of a subscriber within a specified period (for example, in a day, week, or month) or a session. If the duration reaches a specified threshold, the UPCC may reduce the access rate, update the charging rate, send notifications, switch services, or block services to ensure fair usage of the network among subscribers.

Usage-based Dynamic Policy Control

Duration-based Dynamic Policy Control


Page72

UPCC Services (Cont.) Services

Description 

The Enhancement to Usage-based Dynamic Policy Control with Customizable Quota Reset Date feature is developed based on the Usage-based Dynamic Policy Control feature. It allows carriers to set the quota reset cycle flexibly. By default, options of the billing cycle are by day, by week, and by month. This feature allows the Unified Policy and Charging Controller (UPCC) to reset the quota of a subscriber on the billing



The Enhancement to Usage-based Dynamic Policy Control with Top-up Quota feature allows subscribers to purchase additional quota when

Enhancement to Usagebased Dynamic Policy Control with Customizable Quota Reset Date

Enhancement to Usagebased Dynamic Policy Control with Top-up Quota

needed.


Page73

Contents 5. UPCC Message Flow


Page74

IP-CAN Session Establishment 

An IP-CAN session is established after a primary Packet Data Protocol (PDP) context initiated by the UE is activated.


Page75

UE-Initiated IP-CAN Session Modification 

The figure shows the message flow IPCAN session update triggered by UEinitiated Packet Data Protocol (PDP)



modification. The UE-initiated IP-CAN session operations include: 

UE-initiated IP-CAN bearer establishment





UE-initiated IP-CAN bearer modification



UE-initiated IP-CAN bearer termination

The processing flows of these operations on the UPCC are similar.


Page76

PCRF-Initiated IP-CAN Session Modification 

When the subscriber attribute or subscription data on a PCRF changes, the PCRF indicates a reauthorization request to update an IP-connectivity access network (IP-CAN) session.


Page77

UE-Initiated IP-CAN Session Termination 

After a Packet Data Protocol (PDP) context is deactivated, the associated IP connectivity access network (IP-CAN) bearer will be released. If the deactivated PDP context is the last one in an IP-CAN session, the IP-CAN session will be deleted.


Page78

PCRF-Initiated IP-CAN Session Termination 

The PCRF-initiated IP connectivity access network (IP-CAN) session termination operations include: 

Subscriber deletion



Subscriber account frozen



Delivery of rules with Operation Type set to Term IP-CAN Session


Page79

PCRF-Initiated IP-CAN Session Termination (Cont.)


Page80



Page81

Performance Specifications 

VM specifications

VM Type

CPU (Core)

Memory (MB)

Remote Disk (GB)

VM Type

CPU (Core)

Memory (MB)

Remote Disk (GB)

VM-S

2

12288

4/100

VM-M

4

24576

4/200

VM-L

6 (in the FusionSphare and Sigma-based deployment scenario) 8 (in the VMWare and COTS-based deployment scenario)

30720 (for a 6-core CPU) 49152 (for a 8—core CPU)

4/300/1000


Page82


VM application types used by the FE

Application Type VM Type

Performance

UPIRU

VM-M: 0.8 million IP-CAN concurrent sessions 4-core VCPU (in the VMWare-based deployment 24,576 MB memory scenario) 4 GB hard disk 1 million IP-CAN concurrent sessions (in the FusionSphare-based deployment scenario)

UPPDU

VM-M: 4-core VCPU 24,576 MB memory 200 GB hard disk

•

• • •

•

• • •

VM-M: UPPEU

2400 transactions per second (TPS) (in

•

•

4-core VCPU the VMWare-based deployment scenario) 24,576 MB memory 3000 TPS (in the FusionSphare-based 200 GB hard disk deployment scenario)

•

•

•


Page83


VM application types used by the BE

Application Type

VM Type

Performance

VM-M:

0.4 million IP-CAN sessions and 1.8 million static subscribers (in the VMware-based deployment scenario)

• •

•

USRSU

4-core VCPU 24,576 MB memory 200 GB hard disk

VM-L: • •

•


1 million IP-CAN concurrent sessions (When the UPCC is deployed based on the FusionSphere platform, USRSU VMs of the VM-M type are deployed.) 1.2 million IP-CAN sessions and 5 million static subscribers (When the UPCC is deployed based on the FusionSphere platform, USRSU VMs of the VM-L type are deployed.)


Page84

Performance Specifications Application Type

VM Type

Performance

USPID3

VM-M:

-

• • •


VM-L: • • •

USPGW

6-core VCPU/8-core VCPU 30,720 MB memory 300 GB or 1000 GB hard disk

VM-M: • • •


VM-L: • • •



Page85

Configuration Example


Page86

Summary 

This course introduces the UPCC system and networking which include product orientation and application scenario, interfaces and protocols, system structure, services and functions, UPCC message flows and performance specifications.


Page87

Thank you www.huawei.com

01-OWR571101 UPCC System Overview and Networking Introduction ISSUE1.00.pdf

Recommend Documents