Technical Overview 09 - API
Technical Overview 09 - API
API Overview
Care
Elastic Charging Engine
Business
Operations
Center Elastic charging servers
Persistence
Database
HTTP/2 Diameter RADIUS
Gateway Gateway Gateway
C/C++
Standard BC REST Framework
(CM parent handle
BRM application
BRM RSM (TMF) process)
Client connections
or CM ip@
WSM SOAP
PCM API
CM port
Custom
Java
BRM JCA/J2EE
FMs
Client Customer FM
Activity FM
Application Billing & Rating FM
Perl
request Policy FM & Custom FM
…
CMs provide an interface between clients and the rest of the system
All client application connect to the BRM system through a Connection Manager (CM)
Data sent by the application is processed first by the FMs that are included in the CM
PCM API
Activity FM
Billing & Rating FM
• Basic object manipulation: Policy FM and Custom FM
create, search for, delete, and modify objects in the database …
Base Opcodes
• FM object manipulation: Context Management
implement business policies and processes Opcodes
C/C++
• Web Service Manager (WSM SOAP) BC REST Framework
• Billing Care REST Framework (BC REST)
PCM API
BRM RSM (TMF)
REST Service Manager (TMF Open API aligned)
Java
• BRM REST Services Manager (BRM RSM) API
WSM SOAP
Perl
JCA/J2EE
PCM API
for converting data between request BRM
Resource
Billing Care and BRM formats (Ex: Account Resource) CM
Or REST
Module
• The PCM tier manages the Client
(Ex: PCMAccountModule)
connections between Billing Care (Postman…)
and the BRM Connection Manager Worker
(Ex: AccountWorker)
The BRM REST Services Manager API supports the following TMF APIs: Adapters
• TMF 666: Account Management API • TMF 654: Prepay Balance BC REST Framework
Retrieves billing cycle specifications (bill Management API
units and bill unit infos in BRM). Retrieves bucket, accumulated,
disputed, and adjusted balances. BRM RSM (TMF)
Also, creates adjusted and disputed
• TMF 635: Usage Management API balances.
Retrieves usage information.
WSM SOAP
• TMF 678: Customer Bill
• TMF 676: Payment Management API Management API
Creates payments, retrieves payment Retrieves customer bills (customer
information, and allocates payments to invoices in BRM). JCA/J2EE
a bill. Creates refunds and retrieves
refund information.
PCM API
• Customer Bill Management request BRM RSM
BRM
• Payment Management CM
Or REST BRM RSM Extension
• Prepay Balance Management Client
• Usage Management (Postman…)
• Use the Apache Axis framework to support SOAP Web services and is
packaged as an integration pack.
BRM RSM (TMF)
PCM API
request (WebLogic/TomCat)
BRM JCA/J2EE
CM
Or SOAP Deployed WSM App
Client
(Postman…)
PCM API
compliant Validation and BRM
Application Transformation: CM JCA/J2EE
XML / BRM Flist
request
JCA Resource Adapter
BRM JCA Resource Adapter
Documentation
Weblogic Server
Web Service
WS Client PDC DB BRM DB
(SOAP)
PDC Import /
EJB T3
Export Utility
The Product Catalog Master publishes the product offering objects to registered billing-spoke systems using
TMF620 Notification. Then, PDC REST Services Manager synchronizes this data and then transforms it to charge
offers, discount offers, bundles, and packages in the PDC-BRM system.
1 2 3 4 5
Product Manager DX4C Launch PDC REST Services
Upon design PDC pushes
designs Project and publishes Project to Manager transforms
approval, Product pricing/billing attributes
Product Offerings and Fabric. Fabric routes Product Offerings and
Manager submits to BRM/ECE for testing
their pricing/billing publish Project to their pricing/billing
Project Publish in and/or commercial
attributes in DX4C registered billing spoke attributes and provisions
DX4C Launch consumption
Launch (PDC/BRM) PDC
Fabric Routing
Fabric Routing
from notification event)
2 3 Publish Event
REST
projectPublishEvent POST Oracle
Server
(Listener)
Service
9
success/failure info
4
Product Offering Integration Service
1 5 Product
Product Catalog
API (TMF620) Launch Catalog
Service
PDC T3
7 T3
PDC
Service Client Server
launch-publish
8
Fabric Routing
10 Fabric Routing 9
Publish Tracker Publishing Notification Publish Ack OAuth2 protected endpoints;
Acknowledgement Client Service OAuth2 servers and flows not
shown