3

rd
party/CP integration with SDP solution
Contents
SDP overview
Changes @CP end
Connectivity with SDP
Interfaces exposed by SDP
Process/Message Flows
API CP need to provide
Brief on API specs
2 February 11, 2014
Overview of SDP
(Service Delivery Platform)
manage product offerings for all type of products
and services as well as cross-product bundles
Product Management
end to end management of subscription life-cycle
including renewal
Subscription Management
creation and management of CP profile with
required role based access management.
Partner/CP management
encapsulates the core capabilities and expose
those via simple and standard API
Integration with core-
telco capabilities
responsible for charging both prepaid and
postpaid subscribers for purchasing product &
services
Unified billing
capable to maintain and enforce SLA on network
capabilities(SMS, MMS, USSD, etc) that are
exposed to CP.
SLA & policy control
3 February 11, 2014
What needs to be adopted by CP
Connectivity with SAG instead with service enablers(e.g. SMSC,
MMSC, USSD, etc)
SAG will be single point of integration for CP thus CP need to adopt to
parley X APIs exposed by SDP. This will remove silo based integration
with individual service enablers/gateways
Subscription & charging logic will reside @SDP
SDP will manage the complete lifecycle of subscription whereas CP
needs to provide service/content only. This will ease the management
of the subscription logic in a centralized & organized manner.
4 February 11, 2014
3
rd
party connectivity with SDP
5 February 11, 2014
SAG will be the
only point of
integration
replacing silo
based
integration
requirement
with individual
service
enablers(SMSC,
MMSC, LBS,
USSD, billing
systems, etc.)
API exposed by SDP
No. API Group Protocol Compliance
1 SMS API
Parlay X 2.1
Parlay REST 1.0
2 MMS API
Parlay X 2.1
Parlay REST 1.0
3 USSD API Huawei-customized SOAP
4 WAP Push API Huawei-customized SOAP
5 Subscription API SOAP
6 February 11, 2014
*For detail, please refer to API specs
Service/Message Flows
7 February 11, 2014
P2A flow(SMS/MMS)
8 February 11, 2014
A2P flow(SMS/MMS)
9 February 11, 2014
Subscriber initiated USSD transaction
10 February 11, 2014
CP initiated USSD transaction
11 February 11, 2014
Subscription flow(SMS, USSD)
12 February 11, 2014
Subscription flow(IVR)
13 February 11, 2014
Subscription Renewal flow
14 February 11, 2014
Un-Subscription flow(SMS, USSD)
15 February 11, 2014
Un-Subscription flow(IVR)
16 February 11, 2014
API that CP needs to deliver
Get Delivery Receipt for submitted sms(MT)
Get MO sms
SMS
Get MO USSD request
Get session abort notification
USSD
Get Delivery Receipt for submitted MMS(MT)
Get MO mms
MMS
Sync subscription relationship with CP Subscription
Get Delivery Receipt for WAP push WAP push
17 February 11, 2014
For detail on API, please refer to API specs
CP need to deliver only those API that are required for service/content delivery.
API must be delivered in compliance with mentioned specs
Thank you