Introduction

Purpose and scope

This document is aimed to specify B/OSS (PortaBilling) to ZXUN USPP HSS/SPR (ZTE EPC solutions) provisioning in details enough to implement the same by interoperability parties. This document will be the base for interoperability test (IOT) afterwards.

The document includes the description of protocols used at reference points:

  • Transport and application layer protocols used
  • Methods to interact
  • Data structure to use within methods

The document is designed to cover typical user scenarios encouraging going through use cases one by one from description level to API design level.

The other than “B/OSS to HSS/SPR provisioning” reference points (like Gy, Ga, etc) are out of scope.

 

Ticket NumberTT#487910
Target Build
MR54-0
AreaPortaAdmin

Collaborators

Business Department

Development Department

Testing and Support Departments

Definitions, acronyms and abbreviation

B/OSSBusiness and Operations support systems combined
LTE

Long Term Evolution, a standard for wireless communication of high-speed data for mobile phones and data terminals

EPCEvolved Packet Core, the latest evolution of the 3GPP core network architecture.
HSSHome Subscriber Server, the concatenation of the HLR (Home Location Register - user identification, addressing and profile) and the AuC (Authentication Center)
SPRSubscription Profile Repository, contains
  • Subscriber's allowed services
  • Information on subscriber's allowed QoS (MBR and GBR)
  • Subscriber's charging related information
  • Subscriber category
The Sp reference point resides between SPR and PCRF. It allows the PCRF to request subscription information related to a subscriber's service/session.
PCRFPolicy and Charging Rules Function, PCRF server manages the service policy and sends QoS setting information for each user session and accounting rule information.

References

  1. ZXUN USPP V4.14.10_Interface Specification of XML (general).pdf
  2. ZXUN USPP V4.14.10_interface specification of XML(HLR&EPC-HSS fascicule).pdf
  3. ZXUN USPP V4.14.10_interface specification of XML(SPR fascicule).pdf
  4. 3GPP TS 23.008, 3GPP TS 33.401
  5. Similar project in the past with Huawei equipment
  6. Similar project in the past with Greenisis equipment

Architecture Overview

LTE (Long Term Evolution) is becoming the new standard for building wireless networks. Numerous benefits in terms of radio technology (which are beyond the scope of this document) allow service providers to deploy the LTE network rapidly and at reduced cost.

PortaBilling can serve as the B/OSS system for LTE services, i.e. it manages customer data (including unified balance), service configuration details, product/rate tables, and so on for LTE just like for other services (VoIP or DSL Internet access).

PortaBilling can also provision customer data into HSS (to allow centralized user authentication across the network) and SPR (to allocate the correct package with quotas/policy/QoS parameters to the customer).

The main quota control function in this project is SPR (but not B/OSS via Gy). Gy is expected to provide usage details only in later stages of the project.

On PortaBilling side a standard Event Scripts Framework is used (triggered upon creation of a new account, product or service feature change, etc.). The data are provisioned into HSS and SPR using SOAP as a provisioning protocol.

This document is the step forward to make PortaBilling provisioning customer data to ZXUN EPC platform by ZTE.

Business Model Overview

Prepaid

The end-users will access the portal to top-up their balance and purchase plans:
a) 1 day, 3 days, 7 days of LTE internet
b) 1G, 2G, 5G, 10G of LTE internet
Once the time or volume allotment expires the end-user is redirected back to the portal to purchase another allotment.

Postpaid

The end-users will use LTE internet based on assigned subsription plan - reccuring charges will apply. Once there's no available funds, the user will be redirected to the portal for payment collection.

Specifiations

Create "Business requirements" Create "Software requirements" Create "Design requirements"

Use Cases - ZTE EPC LTE provisioning

Testing plan

Prepared by QA. The main goal  is to check Business and Software Requirements. This chapter should be prepared as separate document.

Feature integration guide

It is auxiliary maintenance description which carries information about how to deploy and configure developed solution, its limitation and usage particularities. This chapter should be prepared as separate document.