V v Business Process AMTV Streaming TV Streaming

v

v

Business ProcessAMTV Streaming

TV Streaming

General Architecture

DB

(SMS)Subscriber

Management System

CMS Gateway CMS

WEB Gateway

WEB

Payment Gateway

Payment System

Finance Gateway

Accounting

12

3

4

5

DescriptionCore SMS: Subscriber database, packaging, payment processing, invoicingGateway: As interface between core SMS and external system

Web Admin Web Interface : Admin dashboard, Analytics, Monitoring (message REST-JSON)

Payment provider Payment Gateway: Process online payment: credit card or paypal (message: SOAP, XMLRPC, ISO8583)

CMS CMS Gateway: Subscriber state, packages (as a client and as a server, message: depend on CMS)

Accounting Finance Gateway : Subscriber payment state, Payment reporting

1

2

3

4

5

Data Flow Diagram (DFD)

Admin Subscriber

Payment

System Management

Service(SMS)

DB

CMS

1. Conf. Setting

5. L

ogin

3. Payment

4. Pay

8. A

cces

s Con

tent

11. C

onte

nt Li

st/sh

ow st

ream

7. V

alid

ation

6. Login/passwordForward to CMS

2. Register

9. A

utho

rista

ion

chec

k

10. A

utho

rista

ion

FRANCK DUMORTIER

Some updates on the flow with explanation in the comments section at the bottom of the page.

Updated DFD Description1. Configuration Setting

Admin DashboardAnalyticsMonitoring

2. Register: from subscriber to SMS3. Subscriber submit payment to SMS

Payment Methode (Credit card or Paypall)4. SMS submit Pay to Payment System

Payment Processing5. Login from subscriber’s app to CMS6. Login from CMS to SMS7. Authentication from SMS to CMS8. Access Content from app to CMS9. CMS checsks Subscriber State10.Validation

CMS get information about Subscriber State11.Content List

Streaming

FRANCK DUMORTIER

Modified slide

Sequence Diagram

Admin Subscriber SMS CMS Payment

Tim

e

Monitoring & Management

Login

Response

Payment process

Login & Data Editing

Session

Notification

Register

subs

crip

tion

At e

ach

logi

n

FRANCK DUMORTIER

modified slide

Registration Process

Personal info

FRANCK DUMORTIER

modified slide

Login Process

Payment Inquiry

Payment

Database Table

1. User/subscriber2. Payment3. Product List4. Package List5. Device Type & Device List6. Transaction History

Database Table Mapping

FRANCK DUMORTIER

For simplification, we advice to use as "username" the unique subscriber "ID". This subscriber ID should be link to mobile phone number, or email address to be remembered easily.

FRANCK DUMORTIER

When connecting from APP through the Facebook connect SDK, this will be the facebook account that will identify the customer.

FRANCK DUMORTIER

This may be used as the main login and authentication process OR require the user to log in the app then to log in via Facebook

Database – User Table

1. ID User identity registration number (Primary)2. Name Name of user3. Email User email address (Primary Key)4. Birth Date 5. Address6. User Name User name used for login7. Password

FRANCK DUMORTIER

For simplification, we advice to use as "username" the unique subscriber "ID". This subscriber ID should be link to mobile phone number, or email address to be remembered easily.

FRANCK DUMORTIER

For security reason, password should not be stored in clear in database but using at least a hash function for passwords such as SHA512crypt or bcrypt, preventing bruteforce attack if the site SMS is cracked and the table compromised.

Database – Payment Table

1. Payment ID2. ID User identity registration number2. Name Name of user3. Product ID4. Package ID5. Device ID6. Payment Methods Paypall / Credit Card7. Payment Status Pay or Not Pay

FRANCK DUMORTIER

Shouldn't other payments method be considered?- cash via agents- mobile money- reseller...

Database – Product List Table

1. Product ID2. Product Name3. Product Category Adult / Family Content4. Product prize

Database – Package List Table

1. Package ID2. Package Name3. Package Category Product list in package4. Package Prize

FRANCK DUMORTIER

Name is confusing. If package category is the list of product in package, it should not be called Category

Database – Device Type Table

1. Device ID2. Device List3. Device Type

Database – User History Table

1. Name2. Product Name3. Package Name4. Device Type5. Login Date & Time6. Logout Date & Time7. Purchase History

CMS/SMS API Classification

1. Register2. Login3. Profile :

Change emailChange Password

4. Payment :Payment MethodePayment Schedule

5. Class6. Device Management

1. Login2. Authentication3. Authorization4. Sessions

management (to limit the number of simultaneous session with the same account)

5. Device Management

FRANCK DUMORTIER

These are SMS APIs classification

FRANCK DUMORTIER

What is the Class API?

WEB Classification

1. Admin2. Monitoring3. Reporting4. Maintenance5. Register6. Profile :

Change emailChange Password

7. Payment :Payment MethodePayment Schedule

FRANCK DUMORTIER

Those actions should be available through a web selfcare portal for the customer. The portal can be integrated as part of the AMTV website or as a webapp inside the AMTV mobile apps

Documents

V v Business Process AMTV Streaming TV Streaming