@vantage UMTS/GSM

Mobile Communication System Sales Feature Description Switching Subsystem SR7 IN: USSD based Callback
SF075186

The information in this document is subject to change without notice and describes only the functionality of the product defined in the introduction of this documentation. This document is intended for the use of SIEMENS customers only for the purpose of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted by any means without prior permission of SIEMENS. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. SIEMENS welcomes customer comments as part of the process of continuous improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software cannot be considered binding but shall be defined in the agreement made between SIEMENS and the customer. However, SIEMENS has made reasonable efforts to ensure that the content of the documentation is adequate and free of editorial errors or omissions. SIEMENS will, if necessary, explain issues, which may not be covered by the document. SIEMENS liability for any errors in the document is limited to the documentary correction of errors. SIEMENS will not be responsible in any event for errors in this document or for any damages, incidental or consequential, that might arise from the use of this document. This document and the product described in it are considered protected by copyright according to the applicable laws. For detailed information regarding compliance to relevant standardization specifications, please refer to separate SIEMENS Statements of Compliance (SoCs). Copyright SIEMENS AG 2006. All rights reserved.

SF075186

2 / 11

Contents
1. 1.1. 1.2. 1.3. 1.4. 2. 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. Short Description ............................................................................... 4 Functionality ....................................................................................... 4 Customer Benefits (Operator)............................................................ 4 Customer Benefits (Subscriber)......................................................... 4 Possible Applications ......................................................................... 5 Short Technical Description ............................................................... 6 Realization ........................................................................................ 6 Network Compatibility ...................................................................... 10 Performance..................................................................................... 10 Prerequisites .................................................................................... 10 Recommendations ........................................................................... 10 Man Machine Interface (Operator)................................................... 11 Man Machine Interface (User) ......................................................... 11

SF075186

3 / 11

1. Short Description
1.1. Functionality
CAMEL (Customized Application for Mobile network Enhanced Logic) is a standard, which has been defined to migrate proprietary IN- and OSS- (Operator Specific Services) solutions towards standardized GSM network solutions, e.g. international roaming for credit and prepaid subscriber. Currently there are some networks that do not provide the CAMEL functionality. A consequence is that international roaming can not be offered to prepaid subscribers roaming in these PLMNs. Prepaid is a service that is offered to many target segments, e.g. young people, students, temporary (vacation) users, business customers (e.g. supervision of telephone accounts of employees), fluctuating mobile subscribers or subscribers who want independence. As these prepaid subscribers are a high-growth group of customers a proprietary solution is absolutely necessary. This Sales Feature allows prepaid mobile subscribers to use USSD initiated Callback Service (UCB) provided by the SCP by means of the USSD mechanism, roaming outside of the HPLMN and CAMEL is not supported by that VPLMN. Mobile prepaid subscribers are only allowed to initiate USSD requests and to receive mobile terminated calls in those networks. Its not possible to setup mobile originating calls or to send short messages. This Sales Feature describes the necessary software for the MSC/SSP and the USSD relay function in the HLR. The UCB service needs to be supported also in the SCP.

1.2.

Customer Benefits (Operator)

The motivation for offering UCB is due to differentiating from competitors while increasing the traffic in the network. With this Sales Feature the operator can offer his prepaid subscribers the possibility to set up calls even in (foreign) networks not supporting CAMEL. This innovation will attract a large amount of new mobile prepaid subscribers, especially often travelling business customers. This will enable the operator to compete successfully with competitors by generating additional business as well as additional revenue by traffic increase. Furthermore this feature provides a smooth and fast introduction of CAMEL.

1.3.

Customer Benefits (Subscriber)

At last, this feature enables prepaid subscribers to set up calls if roaming in networks not supporting CAMEL. They are now in the comparable situation as credit subscribers. Prepaid subscribers are not longer discriminated from credit users concerning the possibility to set up calls from abroad. The benefits of a prepaid card (no minimum monthly turnover, no basic fee, independence, and

SF075186

4 / 11

anonymity) are still valid. The convenience of prepaid mobile subscribers will be enhanced in general.

1.4.

Possible Applications
The main application will be to offer the international roaming and the possibility to set up calls for mobile prepaid subscribers. Additionally the UCB feature can also be offered to mobile subscribers without a CAMEL subscription information of their own. Based on an IN/CAMEL service table entry with a fixed service name or UG-CSI data respectively (SR8.0) the HLR is able to address the SCP in order to relay the USSD-message. Basically this feature is not restricted to the initiation of the UCB feature. Any other service provided by a SCP can be triggered by this way. Its transparent for the HLR which service will be finally executed by a SCP. An application could be to use the favorable fees of the VPLMN by changing the MOC of a roaming subscriber into a MTC. In this case, the roaming subscriber initiates an USSD. The HPLMN calls back the roaming subscriber and connects him to the B-Party.

SF075186

5 / 11

2. Short Technical Description

2.1. Realization
The USSD relay to a SCP function allows mobile subscribers to make use of the USSD initiated Callback service (UCB) provided by the SCP. Because of this a mobile subscriber can establish prepaid calls, especially when roaming outside of the HPLMN and CAMEL is not supported by that VPLMN. SR7: In SR7 the USSD relay to a SCP function is realized by a proprietary solution. For this the HLR function named Follow Me was adapted. Siemens realizes this proprietary solution to enable the operator to offer the UCB service to his customers as soon as possible. SR8: With SR8 the proprietary USSD relay functionality is replaced by Sales Feature SF075211, CAMEL phase 2: USSD phase 1, which provides an extended functionality, e.g. new counters which are defined in the HLR for the measurement of the handling of USSD for CAMEL services. Furthermore the Man Machine Interface (User) can de defined more flexible. For the detailed description of the enhancements delivered with SF075211 please see the appropriate Sales Feature Description. In any case, SF075211 is mandatory from SR8. The UCB service is triggered by a mobile subscriber by entering an USSD string containing a service code, which identifies the UCB feature in the HLR and a certain application in the SCP. Furthermore it contains the B-number (international format starting with international prefix, e.g. 004903098765432). The USSD string is sent from an MS via MSC/VLR towards the HLR. Here the USSD string is analyzed. If the service code identifies the national supplementary service UCB the O-CSI of the originating subscriber is taken in order to determine the address of the corresponding SCP (address of gsmSCF). If there is no O-CSI available it is tried to get the SCP address from the IN/CAMEL service table specified by a hardcoded service name. The address is used to relay the USSD string towards the SCP, if possible (see figure 1). The application triggered at the SCP site is out of the scope of this document. It has to return an USSD response string, normally indicating the successful reception of the USSD request. This string is transparently relayed by the HLR. For SR8 please refer to SF075211.

SF075186

6 / 11

MAP Dialogue
2 3 3

HLR
2

VLR
4 4 5 4

SSP MSC
1 3

CSE (SCP)

SINAP Dialogue

Visited PLMN
roaming subscriber

SSP GMSC
5

Home PLMN

HLR

USSDHandler

USSD relay function

adapted functionality

Figure 1: Overview: USSD based Callback

1.) MS sends an USSD string (entered by the mobile subscriber) to MSC/VLR, for example: **11*00491715000102#, where 11 specifies the service code to identify the UCB service within the HLR and 00491715000102 represents the MSISDN of the mobile subscriber B. 2.) MSC/VLR relays USSD string towards HLR (in HPLMN), HLR receives USSD string and relays it to SCP, if possible 3.) SCP returns response to HLR, HLR returns that response to MSC/VLR, MSC/VLR returns response to MS 4.) Call setup to A-Party 5.) Connect to B-Party

Detailed description concerning the USSD relay to SCP function (SR7): Only operation ** of UCB is supported; other operations such as ## or *# are rejected with UnexpectedDataValue

SF075186

7 / 11

 the barring of supplementary service management (BASSM) is checked the address of the SCP is determined from the O-CSI of MSUB-A. If no O-CSI is assigned to the mobile subscriber the fixed service name UCBSERV is used to find that entry within the IN/CAMEL service table containing the address of the SCP. If this service has not been entered by means of MMLcommand CR SUBRSERV, then the USSD request is rejected with UnexpectedDataValue. If both O-CSI and the IN/CAMEL service table entry are available the SCP address of the O-CSI takes precedence. the MSISDN of MSUB-A is inserted into parameter OriginatingEntityNumber of the BeginSubscriberActivity operation The subsystem number 147 (to be created by means of MML-command CR SCUSER) should be used for addressing of the SCP together with the global title digits the USSD string received from VLR is taken unchanged and will be sent to the SCP USSD strings or errors received from the SCP are transparently returned to the MSC/VLR

Detailed description concerning the USSD relay to SCP function (SR8): please refer to SF075211.

SF075186

8 / 11

Detailed description concerning the call setup to the A- and B-subscriber (4. +5.):

HPLMN HLR SCP

2. SRI 6. ERB 3. SRI, MSRN 1. ICA* 7.Connect*

PPS
8. IDP* 9. Connect*

SSP
4. IAM, MSRN

GMSC

MSC/VLR

5. Answear

VPLMN
A-party: Roaming prepaid subscriber B-party

*
1. ICA (CdPA = A, CgPA = xyz RRB, CUE) 7. CON (CdPA = yyyB, CgPA = add_CgPA=VLR#) 8. IPD (CgPA = yyyB, CdPA = yyy B, add_CgPA=VLR#) 9. CON (CdPA = B, , add_CgPA=A)

1.) UCB-service initiates a connection to the A-party using the operation InitiateCallAttempt ICA to the GMSC-SSP.. Simultaneously RequestReportBCSMEvent RRB activates all Event Detection Points EDP and proceeds with Continue CUE. 2., 3.) The GMSC interrogates according to the received MSISDN the appropriate HLR with SendRoutingInformation SRI. With the help of the special Calling Party Number and SDDPFC (Subscriber Dependent Digit Processing and Feature Control), the HLR is interrogated with the information element 'Suppress T-CSI'. By evaluation of this information element the HLR suppresses the sending of the T-CSI and the HLR suppresses the CFU handling in case the A-party has activated Call Forwarding Unconditional. This is necessary, in order to set up the MTC to the A-party. 4.) Via the message IAM the connection is established to the A-party. 5., 6.) With EventReportBCSM ERB the UCB service gets the information, whether the A-party has answered the call, is busy, does not answer, or is not reachable. 7.) In case of answer, the UCB reacts with Connect CON that finishes the UCB IN dialogue. CgPA is the A-party's MSISDN, CdPA is the originally dialled CdPA (BParty), which has to be extended by a prefix of an administrable number of

SF075186

9 / 11

administrable digits YYY (possibly hexadecimal). YYY is IN service specific, as it has to initiate the desired IN service at the appropriate SCP. If the A-location was retrieved, the VLR# is conveyed to the following IN service via the additionalCallingPartyAddress. In all other events (busy, no_answer, route_select_failure) the IN dialogue is terminated via the operation ReleaseCall RL. 8., 9.) The special prefix digits YYY are used in the GMSC-SSP to trigger the Prepaid Service (PPS). If the triggering is done by SDDPFC it is possible to remove the prefix YYY in the operation InitialDP. Otherwise the SCP has to remove the prefix YYY.

2.2.

Network Compatibility
The affected HLRs, SSPs and GMSCs have to be Siemens products. Overlay structures are supported. USSD according to MAP Version 1 has to be supported.

2.3.

Performance
Related to the USSD triggering there is no essential performance impact expected.

2.4.

Prerequisites
HPLMN: SR7 CAMEL Phase 1 (SF075103), MAP V3, SINAP5M+. This feature requires the provision of the UCB service at the SCP site, which is not part of this Sales Feature. IN: Leg Management (SF075168) support in GMSC. According to this feature additional LTG's are necessary. From SR8 Sales Feature SF075211, CAMEL phase2: USSD phase 1 is mandatory. For full functionality the feature needs to be supported also in the SCP.

VPLMN: MAP V2 is sufficient, CAMEL not needed

2.5.

Recommendations
Relevant GSM-Recommendation: GSM-Nr. Implementation acc. GSM Ph1 No Ph2 No Ph2+ No Not applicable

SF075186

10 / 11

2.6.

Man Machine Interface (Operator)

There are no modification of the operator interface related to SR7. Concerning SR8, please refer to SF075211..

2.7.

Man Machine Interface (User)

SR7: Basically this interface is not modified with regard to Follow Me. That is, in principal the MMI as specified in GSM 02.30 and GSM 02.90 applies. The mobile subscriber has to enter an USSD string for example as follows **149*B-Number# where 149 represents the service code entered for Follow Me at the SSS site (HLR). The B-Number specifies the destination to which the mobile subscriber A tries to establish a call (USSD Callback service). The B-Number B is not verified by the HLR, but has to start with the international prefix.. It is not allowed to start with +. SR8: USSD strings of the same format as specified above (SR7) are supported. In addition with SR8 more flexibility with regard to the operation codes, service codes and further optional parameters are offered. Please refer to SF075211.

SF075186

11 / 11