We will use above picture as refference.

For example, Subscriber A(MS A) want to send Short message to subscriber B(MS B) Then subscriber A will type the message on the phone and select subscriber B as the destination address. After subsriber A, hit send button, MS terminal will request channel assignment to the BTS and BSC and then forward the MS A Information to MSC A MSC A will check MS A(subscriber A) data from VLR, if the telecommunication operator has many SMSC, it will identified which SMSC this MS A belong to. After that MS A will transfer the short message to MSC A, at this point on MS A phone will display sending notification

MSC A routes the message to the interworking MSC(IW MSC), beside use IW MSC usually it can use STP IW MSC will route the short message to the SMSC. SMSC Send a notification report to IW MSC and then to MSC A, MSC B and come to subscriber. At this point MS A phone will display Message Sent but not yet delivered to MS B All Above step called MO(Message Originating), we will come on MT(Message Terminating) on the next step SMSC Transfer the short message to the Gateway MSC(GW MSC) The GW MSC ask information from the HLR for routing the short message GW MSC will forward the message to MSC B, and MSC B will check MS B data from VLR MSC B Transfer the short message to MS B through BSC and BTS MSC B Send delivery report to GW MSC, and GW MSC will forward to HLR and SMSC. At this point MS B receive the message and can read it. Delivery report will send by SMSC to MS A after MS B receive the message.

Unstructured Supplementary Service Data

From Wikipedia, the free encyclopedia (Redirected from USSD) Unstructured Supplementary Service Data (USSD) is a protocol used by GSM cellular

telephones to communicate with the service provider's computers. USSD can be used for WAP browsing, prepaid callback service, mobile-money services, location-based content services, menu-based information services, and as part of configuring the phone on the network.[1] USSD messages are up to 182 alphanumeric characters in length. Unlike Short Message Service (SMS) messages, USSD messages create a real-time connection during a USSD session. The connection remains open, allowing a two-way exchange of a sequence of data. This makes USSD more responsive than services that use SMS.[1

Use
The user composes some messageusually rather crypticon the phone keyboard. The phone sends it to the phone company network, where it is received by a computer dedicated to USSD. The answer from this computer is sent back to the phone. The answer could be seen on the phone screen, but it is usually with a very basic presentation. The messages sent over USSD are not defined by any standardization body, so each network operator can implement whatever it finds suitable for its customers. USSD can be used to provide independent calling services such as a callback service (e.g. cheaper phone charges while roaming) or interactive data service (e.g. stock quotes, sports results). USSD is commonly used by pre-paid GSM cellular phones to query the available balance. The vendor's "check balance" application hides the details of the USSD protocol from the user. Some payment methods, such as SharEpay, SWAP Mobile in South Africa, Mobipay in Spain, M-Pesa in Tanzania (but not in Kenya, where M-Pesa menus are provided by STK rather than USSD), and mPay in Poland use USSD. Some examples of very simple but effective USSD based services in Papua New Guinea include BuyPower, InetMobile, SaveBal and TextBal. These services run on the Digicel PNG mobile network and were all developed by leading mobile payment technology vendor mHITs Limited.

Technical details
All GSM phones have USSD capability. It is generally associated with real-time or instant messaging services. There is no store-and-forward capability, as is typical of other shortmessage protocols like SMSin other words, an SMSC is not present in the processing path.

USSD Phase 1, specified in GSM 02.90, only supports mobile-initiated ("pull") operation. In the core network, the message is delivered over MAP. USSD Phase 2, specified in GSM 03.90, supports network-initiated ("push") operation as well.

[edit] Format
A typical USSD message starts with an asterisk (*) followed by digits that comprise commands or data. Groups of digits may be separated by additional asterisks. The message is terminated with a number sign (#).[1] Example USSD codes: *101# *109*72348937857623# After entering a USSD code on your GSM handset, the reply from the GSM operator is displayed within a few seconds

Intelligent Network CAMEL & INAP

The Intelligent Network is network architecture intended both for fixed as well as mobile telecom networks. It allows operators to differentiate themselves by providing value-added services in addition to the standard telecom services such as PSTN, ISDN and GSM services on mobile phones.
In IN, the intelligence is provided by network nodes owned by telecom operators mostly called as SCP -Service Control Point.IN is based on the Signaling System #7 (SS7) protocol between telephone network switching centers and other network nodes owned by network operators. Looking at the History, The IN concepts, architecture and protocols were originally developed as standards by the ITU-T which is the standardization committee of the International Telecommunication Union; prior to this a number of telecommunications providers had proprietary IN solutions. The primary aim of the IN was to enhance the core telephony services offered by traditional telecommunications networks. A complete description of the IN emerged in a set of ITU-T standards named Q.1210 to Q.1219, or Capability Set One (CS-1).The major driver behind the development of the IN system was the need for a more flexible way of adding sophisticated services to the existing network. Before IN was developed, all new feature and/or services that were to be added had to be implemented directly in the core switch systems. i.e., intelligence is taken out of the switch and placed in computer nodes that are distributed throughout the network. This provides the network operator with the means to develop and control services more efficiently..This made for very long release cycles as the bug hunting and testing had to be extensive and thorough to prevent the network from failing. With the advent of IN, most of these services (such as toll free numbers and geographical number portability) were moved out of the core switch systems and into self serving nodes (IN) .The initial use of IN technology was for number translation services. But much more complex services have since been built on IN, such as prepaid telephone calls.

Technical Terms

For any further discussions we would need to use some technical terms. They are discussed in this section. Interrogating PLMN (IPLMN): The PLMN that interrogates the Home PLMN (HPLMN) for information to handle mobile terminating call. CAMEL Service Environment (CSE): A CSE is a logical entity which processes activities related to Operator Specific Services (OSS). CAMEL Subscription Information (CSI): Identifies that CAMEL support is required for the subscriber and the identities of the CSEs to be used for that support. Service Control Function (SCF): SCF contains the actual independent service logic to apply to the call. Basic Call State Model (BCSM): BSCM represents an abstract view of call processing, seen from the perspective of service feature control performed by the SCF. The BCSM consists of two sets of call processing logic, Originating BCSM (O-BCSM) and Terminating BCSM (T-BCSM). Points in Call (PIC): PIC are defined by standards to represent those points in which action might be taken. They provide a view of a state or event in which call processing logic may initiate an action, such as suspension of call processing while a database is queried. Detection Points (DP): DP represent transitional events that occur between some PICs. Triggers: A trigger is the term used to define specific call-processing logic associated with a given point in call. Triggers are nothing more than software logic that is loaded in a network element to carry out instructions to initiate an intelligent network process based on analysis of conditions at a detection point. Events: Unlike a trigger, which depends on some form of input criteria, an event is simply a call occurrence such as no answer, busy signal or call termination. Arming of detection points: Detection points have two classifications: Trigger Detection Points (TDP) and Event Detection Point (EDP). A detection point is armed if control logic is established to initiate service control based on a trigger or event. GSM Service Control Function (gsmSCF): functional entity that contains the CAMEL service logic to implement OSS. It interfaces with the gsmSSF, the gsmSRF, the GMLC and the HLR. GSM Service Switching Function (gsmSSF): functional entity that interfaces the MSC or GMSC to the gsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network. GSM Specialised Resource Function (gsmSRF): functional entity which provides

various specialized resources. It interfaces with the gsmSCF and with the MSC. Applicability of CAMEL procedures The CAMEL feature is applicable to Mobile Originated and Mobile Terminated Call Related Activities. CAMEL procedures are applicable to all circuit switched basic services without distinction (except Emergency calls). The CAMEL feature is applicable to Supplementary Services Invocation CAMEL procedures are applicable to GPRS sessions and PDP contexts CAMEL procedures are applicable to Mobile Originating/Terminating short message service through both circuit switched and packet switched serving network entities CAMEL procedures are applicable to IP multimedia services (except Emergency calls) to support legacy services CAMEL shall support IPMM sessions which are based on the same charging paradigm as CS/PS calls. This applies most probably to VoIP and Video over IP. CAMEL procedures are applicable to IP multimedia sessions addressed by either E.164 numbers or SIP URLs. Camel Application Part Wikipedia Apture View Table of ContentsBackNextWikipedia Summary Show Quick Facts The CAMEL Application Part (CAP) is a signalling protocol used in the Intelligent Network (IN) architecture. CAP is a Remote Operations Service Element (ROSE) user protocol, and as such is layered on top of the Transaction Capabilities Application Part (TCAP) of the SS#7 protocol suite. CAP is based on a subset of the ETSI Core and allows for the implementation of carrier-grade, value added services such as unified messaging, prepaid, fraud control and Freephone in both the GSM voice and GPRS data networks. CAMEL is a means of adding intelligent applications to mobile (rather than fixed) networks. It builds upon established practices in the fixed line telephony business that are generally classed under the heading of (Intelligent Network Application Part) or INAP CS2 protocol.[1]

Protocol specification

The CAMEL Application Part (CAP) portable software provides mechanisms to support operator services beyond the standard GSM services for subscribers roaming within or outside the Home PLMN (HPLMN). The CAP product extends the IN framework to GSM/3G networks for implementing IN-based services within GSM/3G networks. CAMEL is used when the subscriber is roaming between networks, allowing the home network to monitor and control calls made by the subscriber. CAMEL provides services such as prepaid roaming services, fraud control, special numbers (e.g., 123 for voicemail that works everywhere) and closed user groups (e.g., office extension numbers that work everywhere). As with CAMEL, CAP has been defined in 4 phases, each of which has an accompanying specification that builds upon the previous phase. Each CAP phase provides the message set and procedures needed to support the corresponding CAMEL phase requirements, as defined in 3GPP TS 22.078 (service aspects) and 3GPP TS 23.078 (technical realization).