HTTPinterface_debitcredit

download HTTPinterface_debitcredit

of 25

  • date post

    25-Oct-2014
  • Category

    Documents

  • view

    35
  • download

    0

Embed Size (px)

Transcript of HTTPinterface_debitcredit

INTELLIGENT NETWORK

GENERIC PPS PPS 4.3.2 / RTDC - DEBIT CREDIT INTERFACE PART

HTTP INTERFACE DESCRIPTION

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

1/25

PREFACE

This document describes the HTTP interfaces allowing an external entity to debit/credit a subscriber that is hosted on the SDP/DBRES of the PPS 4.3.2 service. In the PPS 4.3.2 deployment, pure prepaid accounts are held in SDP 1.4 whereas post-paid and regular prepaid accounts are held in DBRES 1.8.

HISTORYEdition(yy-mm-dd)

Date

Comments

Ed 04 Ed 03 Ed 02 Ed 01

05-10-27 05-06-29 05-04-07 04-09-08

Modification Type of the prices Type of the prices was int instead of real Update for FR VELin32219 (DBRES Currency Precision handling) Creation of document

TRADEMARKS

None

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

2/25

CONVENTIONS

The table below shows the typing conventions used in this document. These conventions denote a special type of information. Typing convention bold-face text menu options dialog box fields commands buttons file names italics document titles document references Information type

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

3/25

TABLE OF CONTENTS

1. INTRODUCTION ............................................................................................................ 7

2. NETWORK ENVIRONMENT............................................................................................ 9

3. INFORMATION FLOW.................................................................................................. 10 3.1 3.2 3.3 3.4INTRODUCTION ............................................................................................................. IMMEDIATE DEBIT ........................................................................................................... TWO-STEP DEBIT ............................................................................................................ IMMEDIATE CREDIT .........................................................................................................

10 10 12 14

4. EXTERNAL INTERFACES DESCRIPTION ........................................................................ 15 4.1 CONTENT PROVIDER REQUEST .......................................................................................... 15 4.2 CONTENT PROVIDER REPLY............................................................................................... 20 5. ANNEX A: VALUES FOR THE PARAMETER RESULT..................................................... 22

6. ANNEX B: DTD XML .....................................................................................................23

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

4/25

TABLE OF ILLUSTRATIONS

Figure 1: Immediate Debit Scenario Fee Example when Debiting an Amount of Money................. 11 Figure 2: Immediate Debit Scenario Example of a Debit on a Sub-account / Regular Prepaid or Postpaid Case ............................................................................................................................ 11 Figure 3: Two-step Debit Scenario One Example when Debiting an Amount of Money.................. 12 Figure 4: CP Aborts the Two-step Debit Example of a Debit on a Sub-account / Regular Prepaid or Post-paid Case ..................................................................................................................... 13 Figure 5: Credit Request - Post-paid/Regular Prepaid .................................................................... 14 Figure 6: Credit Request - Prepaid................................................................................................ 14

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

5/25

REFERENCE DOCUMENTS

N1 2 3

Reference3BL 45120 BAAA DTZZA 3BL 45011 EAAA DSZZA 3BL 45180 BAAA DTZZA

Ed01 01 01

TitleGeneric PPS - PPS 4.3.2 / RTDC Functional Specifications Generic PPS - PPS 4.3.2 Pure Prepaid DBRES1.4 General Design Service Description Generic PPS - PPS 4.3.2 / DBRES 1.8 Functional Specifications

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

6/25

1.

INTRODUCTION

The aim of this document is to describe the Debit-Credit HTTP interface that enables an external entity to perform following operations on users accounts identified by their MSISDN: For prepaid users: Debit an amount of money on the main account Credit all the sub-accounts1 of the user and modify the activity and inactivity periods of the main account, the activity period of the promotional sub-account and the validity period of the refill bonus SMS. Each amount is given in the unit of the targeted sub-account. For post-paid and regular prepaid users: Debit an amount associated with a content code. The determination of the targeted sub-account(s)2 follows the following logic: Through RTDC service population, this content code refers to an operator service and, through the commercial offer subscribed by the user, this service is linked to a rating tree that enables the selection of the sub-account(s) to debit. Credit all the sub-accounts of the user. Each amount is given in the unit of the targeted sub-account. Note that if the external entity does not know the type of user (prepaid or not), it can only debit an amount of money (and the RTDC service will use a default value (65535) of content code in case the user is post-paid or regular prepaid). For debit transactions, two different scenarios may take place: Immediate Debit: Charging is done at the reception of the request, Two- Step Transaction: there is a first message to authorise the transaction and book the given amount in case of pure prepaid and regular prepaid accounts and a second message is sent when the transaction has been successfully completed. The subscribers account is charged at the reception of the confirmation request (second message). In case that the second message is not received, the booked amount (pure and regular prepaid) will be credited again to the account after a given timer. In all cases, the external entity has always the possibility to cancel the previous booking by sending an ABORT request.

The sub-account expression includes the main account, the promotional sub-account, the MMS sub-account, the data sub-account, the content sub-account and the refill bonus SMS counter. The sub-account expression includes the balance, the general money sub-accounts (money1 and money2) and the specialised sub-accounts (time/voice, SMS, MMS, data, content).Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization2

1

7/25

Furthermore, for any transaction Call Detail Records (CDR) will be generated including information such as date and time, subscriber MSISDN, debited amount, identity of the external entity originating the request.

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

8/25

2.

NETWORK ENVIRONMENT

The interface described in this document relies between the External Entity and the OSP where the prepaid, post-paid and regular prepaid accounts are held. This interface may be used within the operator Intranet (between two network-nodes managed by the operator, as well as for a node lying outside in the Internet). For the later, this interface provides a secure transport by using https and digital certificates. However it must be pointed out that this securitylayer will obviously decrease the overall solution performance. Next figure depicts both possible configurations.

Firewall

CP

Internet

HTTP(S) Interface

Debit / credit serviceOSP

MMS-C

Operator IP network

Generic PPS PPS 4.3.2 / RTDC - Debit Credit Interface Part HTTP INTERFACE DESCRIPTION 3BL 45121 BAAA NSZZA Ed 04 Validated All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

9/25

3. 3.1 INTRODUCTION