nobill ussd callbacak camel description 1 01

Calling Party MSC HLR Nobill SCP/PPS Called Party ProcessUnstructuredSS-Request 1 ProcessUnstructuredSS-RequestResp 8 SendRoutingInfoRequest 2 SendRoutingInfoCnf 3 InitiateCallAttempt 9

Trang 1

Nobill USSD Callback (Camel)

- Signalling

Trang 2

Contents

Contents 2

Revision history 3

1 Description 3

2 Signalling sequences 4

2.1 Normal Call 4

2.2 Call released due to low balance 6

2.3 Call rejected with low balance announcement 8

Trang 3

Revision history

R1.00 2005-06-13 BABT This is the first revision of the document

R1.01 2005-10-17 BABT Invocation of SCP is done before

IntitalCallAttempt

1 Description

The purpose of this document is to describe the detailed network signalling for the

Nobill USSD callback service when interworking with an external prepaid system

over CAMEL (CAPv2)

Nobill communicates with the HLR using MAP (version 2) and with the MSC using

INAP/CS1

Trang 4

2 Signalling sequences

The sequence below describes the signalling carried out during a normal USSD

callback call, i.e when the initiating user has enough balance on the prepaid account

Calling Party MSC HLR Nobill SCP/PPS Called Party

ProcessUnstructuredSS-Request (1)

ProcessUnstructuredSS-RequestResp (8)

SendRoutingInfoRequest (2) SendRoutingInfoCnf (3)

InitiateCallAttempt (9)

RequestReportBCSMEvent (10)

Continue (11)

"Ringing" (12)

"Off-hook" (13)

ReportBCSMEvent Answer (14)

InitialDP (4)

ApplyCharging (6)

Continue (7)

Connect (16)

"Ringing" (17)

"Off-hook" (18) ReportBCSMEvent Answer (19)

ReportBCSMEvent Answer (20)

"On-hook" (21)

ReportBCSMEvent Disconnect (22)

ReportBCSMEvent Disconnect (23)

ApplyChargingReport (24)

Normal call

1 An USSD request is received by Nobill from the HLR The USSD string is on

the format *nnn*xxxxxxxx#, where nnn is a configurable service code and

xxxxxxxx is the MSISDN of the called party The MSISDN shall be given in

international dialling format, e.g +46702692431 or 0046702692431

Trang 5

3 The HLR responds with roaming number The O-CSI parameter in the HLR

response contains information about the SCP address and the service key

Nobill uses this information when invoking the SCP

4 Nobill sends an InitialDP request to the PrePaid System (SCP/PPS), i.e to the

SCP The request is sent over INAP/CAPv2

5 The PPS sends a RequestReportBSCMEvent request to arm events needed to

monitor the call

6 The PPS sends an ApplyCharging request

Note: Nobill will start a timer supervision and send an ApplyChargingReport

when the max call duration specified in the ApplyCharging request has

elapsed or when the call is disconnected

7 The PPS sends a Continue request

8 An USSD response is sent back to the initiating party displaying a message

that the request was received This USSD session is closed

9 Nobill sends an InitiateCallAttempt request to the MSC over INAP/CS1

10 Nobill sends a RequestReportBSCMEvent request to the MSC to arm events

needed to monitor the call setup

11 Nobill sends a Continue request to the MSC to order the MSC to continue with

the call setup

12 The MSC setup the call to the initiating party

13 The initiating party answers the call

14 The MSC reports the Answer event to Nobill

15 Nobill sends a Connect request to the MSC to order to connect the called

party

16 The MSC connects the called party

17 The called party answers

18 The Answer event is reported by the MSC to Nobill

19 Nobill relays the Answer event to the PPS

20 Eventually, some of the parties go on-hook

21 The Disconnect event is reported by the MSC to Nobill

22 Nobill relays the Disconnect event to the PPS

Trang 6

23 Nobill sends an ApplyChargingReport to the PPS

2.2 Call released due to low balance

The sequence below describes the signalling carried out when the initiating party runs

out of balance during an active call

xxxxxxxx is the MSISDN of the called party

2 Nobill sends a SendRoutingInfoRequest to the HLR in order to retrieve the

roaming number of the initiating party

Trang 7

4 Nobill sends an InitialDP request to the PrePaid System (PPS), i.e to the SCP

The request is sent over INAP/CAPv2

5 The PPS sends a RequestReportBSCMEvent request to arm events needed to

monitor the call

6 The PPS sends an ApplyCharging request

Note: Nobill will start a timer supervision and send an ApplyChargingReport

when the max call duration specified in the ApplyCharging request has

elapsed or when the call is disconnected

7 The PPS sends a Continue request

that the request was received

9 Nobill sends an InitiateCallAttempt request to the MSC over INAP/CS1

needed to monitor the call setup

11 Nobill sends a Continue request to the MSC to order the MSC to continue with

the call setup

12 The MSC setup the call to the initiating party

13 The initiating party answers the call

14 The MSC reports the Answer event to Nobill

needed to monitor the call setup to the called party

16 Nobill sends a Connect request to the MSC to order to connect the called

party

17 The MSC connects the called party

18 The called party answers

19 The Answer event is reported by the MSC to Nobill

20 Nobill relays the Answer event to the PPS

21 The max call duration, specified in the ApplyCharging request above, has

elapsed and Nobill sends an ApplyChargingReport to the PPS

22 The PPS send a ReleaseCall request

23 Nobill relays the ReleaseCall request to the MSC

Trang 8

2.3 Call setup rejected due to low balance

xxxxxxxx is the MSISDN of the called party

2 Nobill sends a SendRoutingInfoRequest to the HLR in order to retrieve the

roaming number of the initiating party

3 The HLR responds with roaming number

4 Nobill sends an InitialDP request to the PrePaid System (PPS), i.e to the SCP

The request is sent over INAP/CAPv2

5 The PPS detects that the initiating user does not have enough balance and

sends a ReleaseCall request

that the request was rejected

Định dạng
Số trang	8
Dung lượng	114,4 KB