Signaling System No.

7 (SS)
Signaling System No. 7 (SS7) is a set of Telephone signaling protocols which are used to set up most of the world's public switched telephone network telephone calls. The main purpose is to set up and tear down telephone calls. Other uses include number translation, local number portability , prepaid billing mechanisms, short message service (SMS), and a variety of other mass market services. It is usually referenced as signaling System No. 7 or signaling System #7, or simply abbreviated to SS7.

SS7, being a high-speed and high-performance packet-based communications protocol, can communicate significant amounts of information when setting up a call, during the call, and at the end of the call.
This permits rich call-related services to be developed. Some of the first such services were call management related, Call forwarding (busy and no answer) voice mail, call waiting, conference calling , calling name and number display, call screening, malicious caller identification, Busy call back, The earliest deployed upper layer protocols in the SS7 signaling suite were dedicated to the setup, maintenance, and release of telephone calls.

Due to its richness and the need for an out-of-band channel for its operation, SS7 signaling is mostly used for signaling between telephone switch and not for signaling between local exchange and customer- premises equipment (CPE).
It is also possible with SS7 is Non-Call-Associated Signaling, which is signaling that is not directly related to the establishment of a telephone call. An example of this is the exchange of the registration information used between a mobile telephone and a home location register (HLR) database: a database that tracks the location of the mobile. Other examples include Intelligent Network and local number portability databases.

Signaling modes SS7 is designed to operate in two modes:

associated mode and quasi-associated mode.

When operating in the associated mode, SS7 signaling progresses from switch to switch through the PSTN following the same path as the associated facilities that carry the telephone call. This mode is more economical for small networks.

When operating in the quasi-associated mode, SS7 signaling progresses from the originating switch to the terminating switch, following a path through a separate SS7 signaling network composed of signaling transfer points. This mode is more economical for large networks with lightly loaded signaling links.

Physical network SS7 separates signaling from the voice circuits. An SS7 network must be made up of SS7-capable equipment from end to end in order to provide its full functionality. The network can be made up of several link types (A, B, C, D, E, and F) and three signaling nodes

Service Switching Point (SSPs). Signaling Transfer Point (STPs) Service control Point (SCPs). Each node is identified on the network by a number, a signaling point code. Extended services are provided by a database interface at the SCP level using the SS7 network.

The links between nodes are full-duplex 56, 64, 1,536, or 1,984 Kbit/s graded communications channels. One or more signaling links can be connected to the same two endpoints that together form a signaling link set. Signaling links are added to link sets to increase the signaling capacity of the link set.

In Europe, SS7 links normally are directly connected between switching exchanges using F-links. This direct connection is called associated signaling. In North America, SS7 links are normally indirectly connected between switching exchanges using an intervening network of STPs. This indirect connection is called quasi-associated signaling. Quasi-associated signaling reduces the number of SS7 links necessary to interconnect all switching exchanges and SCPs in an SS7 signaling network.
SS7 links at higher signaling capacity (1.536 and 1.984 Mbit/s, simply referred to as the 1.5 Mbit/s and 2.0 Mbit/s rates) are called High Speed Links (HSL) in contrast to the low speed (56 and 64 Kbit/s) links.

There are differences between the specifications for the 1.5 Mbit/s rate. High speed links utilize the entire bandwidth of a T1 (1.536 Mbit/s) or E1 (1.984 Mbit/s) transmission facility for the transport of SS7 signaling messages.
SIGTRAN provides signaling using SCTP associations over the Internet Protocol.

The SS7 protocol stack borrows partially from the OSI Model of a packetized digital protocol stack. OSI layers 1 to 3 are provided by the Message Transfer Part (MTP) and the Signaling Connection Control Part (SCCP) of the SS7 protocol (together referred to as the Network Service Part (NSP)); for circuit related signaling, such as the Telephone User Part (TUP) or the ISDN User Part(ISUP), the User Part provides layer 7. Currently there are no protocol components that provide OSI layers 4 through 6.

The Transaction Capabilities Application Part (TCAP) is the primary SCCP User in the Core Network, using SCCP in connectionless mode.
SCCP in connection oriented mode provides the transport layer for air interface protocols such as BSSAP and RANAP. TCAP provides transaction capabilities to its Users (TC-Users), such as The Mobile Application Part. The Intelligent network Application part. The CAMEL Application Part.

The Message Transfer Part (MTP) covers a portion of the functions of the OSI network layer including: network interface, information transfer, message handling and routing to the higher levels. Signaling Connection Control Part (SCCP) is at functional Level 4. Together with MTP Level 3 it is called the Network Service Part (NSP). SCCP completes the functions of the OSI network layer: end-toend addressing and routing, connectionless messages (UDTs), and management services for users of the Network Service Part (NSP).

Telephone User Part (TUP) is a link-by-link signaling system used to connect calls. ISDN User Part (ISUP) is the key user part, providing a circuit-based protocol to establish, maintain, and end the connections for calls. Transaction Capabilities Application Part (TCAP) is used to create database queries and invoke advanced network functionality, or links to Intelligent Network Application Part (INAP) for intelligent networks, or Mobile Application Part (MAP) for mobile services.

Message Transfer Part (MTP)

Message Transfer Part (MTP)

The Message Transfer Part (MTP) is part of the Signaling System no 7 (SS7) used for communication in Public Switch Telephone network. MTP is responsible for reliable, unduplicated and in-sequence transport of SS7 messages between communication partners.

Functional levels
The SS7 stack can be separated into four functional levels:

Level 1 is the Signaling Data Link Functional Level (Data Link Level).
Level 2 is the Signaling Link Functional Level (Link Level). Level 3 is the Signaling Network Functional Level (Network Level).

Level 4 is the MTP User and consists of SCCP, ISUP, TUP, or any other MTP User.

Level 1 through Level 3 comprise the MTP, and Level 4 the MTP user. MTP Level 3 is sometimes abbreviated MTP3; MTP Level 2, MTP2.
MTP and SCCP are together referred to as the Network Service Part (NSP). There is no one-to-one mapping of MTP Levels 1 through 3 onto the OSI Model . Instead, MTP provides the functionality of layer 1, 2 and part of layer 3 in the OSI model. The part of layer 3 of the OSI model that MTP does not provide, is provided by SCCP or other Level 4 parts (MTP users).

Signaling Data Link Functional Level

MTP1
MTP1 represents the physical layer. That is, the layer that is responsible for the connection of SS7 Signaling Points into the transmission network over which they communicate with each other. Primarily, this involves the conversion of messaging into electrical signal and the maintenance of the physical links through which these pass. In this way, it is analogous to the Layer 1 of ISDN or other, perhaps more familiar, protocols. MTP1 normally uses a timeslot in an E-Carrier or T- Carrier. The Physical interfaces defined include E-1 (2048 kb/s; 32 64 kb/s channels), DS-1 (1544 kb/s; 24 64kb/s channels), V.35 (64 kb/s), DS-0 (64 kb/s), and DS-0A (56 kb/s).

Signaling Link Functional Level MTP Level 2 is described in ITU-T Recommendation Q.703, and provides the Signaling Link functional level for narrowband signaling links. For broadband signaling links, ITU-T Recommendation Q.2140 and Q. 2210 describe the signaling link function referred to asMTP3b. The signaling link functional level may also be provided using the SIGTRAN protocol M2PA described in RFC 4165. MTP Level 2 ensures accurate end-to-end transmission of a message across a signaling link. r and test specifications described in Q.755, Q.755.1, Q.780 and Q.781.

MTP2 provides flow control, error detection and sequence checking, and retransmits unacknowledged messages. MTP2 uses packets called signal units to transmit SS7 messages. There are three types of signal units: Fill-in Signal Unit (FISU), Link Status Signal Unit (LSSU), Message Signal Unit (MSU). Access to the signaling link functional level's service interface can be provided over SCTP by the SIGTRAN protocol M2UA, described in RFC 3331. MTP Level 2 is tested using the protocol tester and test specifications described in Q.755, Q.755.1, Q.780 and Q.781.

Signaling Network Functional Level

MTP Level 3 is described in ITU-T Recommendation Q.704, and provides the Signaling Network functional level for narrowband signaling links and, with only minor modifications described in ITU-T Recommendation Q.2210, for broadband signaling links.

The functions of MTP Level 3 may also be replaced with the Generic Signaling Transport Service described in ITU-T Recommendation Q.2150.0 as provided by MTP3b (Q.2150.1), SSCOP or SSCOPMCE (Q.2150.2) or SCTP (Q.2150.3).
MTP Level 3 functions can also be provided by using the IETF SIGTRAN M3UA protocol, described in RFC 4666, in IPSP mode.

MTP3 provides routing functionality to transport signaling messages through the SS7 network to the requested endpoint.

Each network element in the SS7 network has a unique address, the Point Code (PC). Message routing is performed according to this address. A distinction is made between a Signaling Transfer Point (STP) which only performs MTP message routing functionalities and a Signaling End Point (SEP) which uses MTP to communicate with other SEPs (that is, telecom switches). MTP3 is also responsible for network management;

MTP3 establishes alternative links and re-routes traffic away from failed links and signaling points and propagates information about route availability through the network. Also controls traffic when congestion occurs.
MTP3 is equivalent to the OSI Network Layer. Access to the signaling network functional level's service interface (as described in Q.701) can be provided over SCTP by the SIGTRAN protocol M3UA, described in RFC 4666. MTP Level 3 is tested using the protocol tester and test specifications described in Q.755, Q.755.1, Q.780 and Q.782.

MTP Users
Level 4 consists of MTP Users. The remaining components of the SS7 stack are all directly, or indirectly, MTP Users. Some examples of parts at Level 4 are SCCP, ISUP and TUP. The services provided to MTP Level 4 by the MTP (that is, MTP to MTP Users) is described in ITU-T Recommendation Q.701.

Signaling Connection Control Part (SCCP)

Signaling Connection Control Part The Signaling Connection Control Part (SCCP) is a network layer protocol that provides extended routing, flow control, segmentation, connection-orientation, and error correction facilities in Signaling System 7 telecommunications networks. SCCP relies on the services of MTP for basic routing and error detection.

Routing facilities beyond MTP

Although MTP provides routing capabilities based upon the Point Code, SCCP allows routing using a Point Code and Subsystem number or a Global Title. A Point Code is used to address a particular node on the network, whereas a Subsystem number addresses a specific application available on that node. SCCP employs a process called Global Title Translation to determine Point Codes from Global Titles so as to instruct MTP on where to route messages. SCCP messages contain parameters which describe the type of addressing used, and how the message should be routed:

Address Indicator Routing indicator Route on Global Title Route on Point Code/Subsystem Number Global title indicator No Global Title Global Title includes Translation Type (TT), Numbering Plan Indicator (NPI) and Type of Number (TON) Global Title includes Translation Type only Subsystem indicator Subsystem Number present Subsystem Number not present Point Code indicator Point Code present Point Code not present Global Title Address Indicator Coding Address Indicator coded as national (the Address Indicator is treated as international if not specified)

Protocol classes
SCCP provides 5 classes of protocol to its applications: Class 0: Basic connectionless. Class 1: Sequenced connectionless. Class 2: Basic connection-oriented. Class 3: Flow control connection oriented. Class 4: Error recovery and flow control connection oriented.

Class 0: Basic connectionless

The SCCP Class 0 protocol class is the most basic of the SCCP protocol classes. Network Service Data Units passed by higher layers to the SCCP in the originating node are delivered by the SCCP to higher layers in the destination node. They are transferred independently of each other. Therefore, they may be delivered to the SCCP user out-ofsequence. Thus, this protocol class corresponds to a pure connectionless network service. As a connectionless protocol, no network connection is established between the sender and the receiver.

Class 1: Sequenced connectionless SCCP Class 1 builds on the capabilities of Class 0, with the addition of a sequence control parameter in the NSDU which allows the SCCP User to instruct the SCCP that a given stream of messages should be delivered in sequence. Therefore, Protocol Class 1 corresponds to an enhanced connectionless protocol with assurances of in-sequence delivery.

Class 2: Basic connection-oriented

SCCP Class 2 provides the facilities of Class 1, but also allows for an entity to establish a two-way dialog with another entity using SCCP.

Class 3: Flow control connection oriented

Class 3 service builds upon Class 2, but also allows for expedited (urgent) messages to be sent and received, and for errors in sequencing (segment re-assembly) to be detected and for SCCP to restart a connection should this occur.

Transport over IP Networks

In the SIGTRAN suite of protocols, there are two primary methods of transporting SCCP applications across Internet Protocol networks: SCCP can be transported indirectly using the MTP level 3 User Adaptation protocol (M3UA), a protocol which provides support for users of MTP-3including SCCP. Alternatively, SCCP applications can operate directly over the SCCP User Adaptation protocol (SUA) which is a form of modified SCCP designed specifically for use in IP networking. ITU-T also provides for the transport of SCCP users over Internet Protocol using the Generic Signaling Transport service specified inQ.2150.0, the signaling transport converter for SCTP specified in Q.2150.3 and a specialized Transport-Independent Signaling Connection Control Part (TI-SCCP) specified in T-REC-Q.2220. TI-SCCP can also be used with the Generic Signaling Transport adapted for MTP3 and MTP3b as described in Q.2150.1, or adapted for SSCOP or SSCOPMCE as described in Q.2150.2.

Transaction Capabilities Application Part

Transaction Capabilities Application Part, from ITUT recommendations Q.771-Q.775 or ANSI T1.114 is a protocol for Signaling System 7 networks. Its primary purpose is to facilitate multiple concurrent dialogs between the same sub-systems on the same machines, using Transaction IDs to differentiate these, similar to the way TCP ports facilitate multiplexing connections between the same IP addresses on the Internet.

TCAP is used to transport INAP Networks and MAP in mobile phone networks.

in

Intelligent

Unidirectiona A single primitive with no subsequent primitives. l Sometimes referred to as a Notice. Begin Continue Start a dialog, further primitives will follow. Send a subsequent primitive on an existing dialog, further primitives will follow. The last primitive on an existing dialog, Close an existing dialog. An error has caused the dialog to close.

End Abort

Cancel

The invoke timer has expired without a response being received (this is a primitive but not a message)

A Begin primitive has an Originating Transaction ID (up to 4 bytes). Continues have an Originating Transaction ID and a Destination Transaction ID. Ends and Aborts only have a Destination Transaction ID. Each primitive has both an optional component and (required) dialogue portions. The component portion for the unidirectional primitive is mandatory.

The dialogue portion carries dialogue or undialogue control PDUs. For MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives. Following primitives are defined for the dialogue PDU:

AARQ

Dialogue request. For MAP and INAP, AARQ is sent in the Begin primitive with the Invoke component in general, with the application context of MAP/INAP operation's package.

AARE

Dialogue response. Sent in response to AARQ in either Continue or End primitives.

ABRT

Dialogue abort.

Each ITU-T TCAP component may be one of the following types: Invoke components have a signed 7 bit Invoke ID which is present in all the other components to identify which invoke they relate to.

TCAP is based on the OSI defined ROSE, Remote Operations Services Element protocol.

Invoke

A new operation is being requested, this may or may not solicit a response

Return Result Last

A final response to an Invoke

Return Result Not Last

A response to an Invoke, further responses will be sent

Return Error

An error occurred

Reject

Component is rejected for some reason like duplicate invocation, unrecognized linked id, unrecognized operation or mistyped argument

Transaction ID The transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog. When machine A starts a TCAP dialog with another machine B, the machine A sends a Begin message to machine B. This Begin message contains an Originating Transaction ID, which is the Transaction ID reference for A. When the machine B replies to A with a Continue message it includes A's Transaction ID as the Destination Transaction ID. Furthermore B includes its own Transaction ID as the Originating Transaction ID.

As the TCAP dialog goes on each Continue message includes the Transaction ID of the destination machine as the Destination Transaction ID and the Transaction ID of the originating machine as the Originating Transaction ID.
When any of the machines wants to close the dialog it sends an End message or an Abort message to the other machine. This message contains the Destination Transaction ID only.

Invoke ID
Invoke ID is a TCAP reference for a specific TCAP operation.

Decoded TCAP Message

This is a MO-SMS sent by a MAP layer and the hex stream is taken from TCAP layer. 62 11 00 2E 92 90 20 74 74 86 00 30 55 20 71 D8 48 05 01 46 55 11 79 5E 04 01 00 80 04 80 4E 06 00 01 19 05 35 01 07 95 02 01 02 70 2F 24 B1 ED 00 A0 6C 31 09 00 C3 65 30 0D 50 42 00 27 EE 39 6B 60 A1 44 70 43 73 68 1A 0B 4E 44 97 50 3D 5E 28 A1 02 84 92 7A 7C 2E 18 09 01 06 62 0E 2E BB 06 06 01 A1 23 A2 83 01 07 07 02 70 04 A3 D2 00 00 04 01 91 00 CB 20

According to tag length values, this can be decoded as below.

CAMEL Application Part

The CAMEL Application Part (CAP) is a signaling 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 Free phone 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 INAPCS-2 protocol.

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 four 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).

The definition of the protocol may be considered to be split into three sections:
the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol, defined within the prose of the specification; the definition of the operations transferred between entities, defined using Abstract Syntax Notation One (ASN.1); the definition of the actions taken at each entity, defined by means of state transition diagrams.

ISDN User Part

The ISDN User Part or ISUP is part of the Signaling System No. 7 (SS7) which is used to set up telephone calls in the public switched telephone network (PSTN). It is specified by the ITU-T as part of the Q.76x series.
When a telephone call is set up from one subscriber to another, several telephone exchanges could be involved, possibly across international boundaries. To allow a call to be set up correctly, where ISUP is supported, a switch will signal call-related information like called party number to the next switch in the network using ISUP messages.

The telephone exchanges may be connected via E1 or T1 trunks which transport the speech from the calls. These trunks are divided into 64 Kbit/s timeslots, and one timeslot can carry exactly one call.

Regardless of what facilities are used to interconnect switches, each circuit between two switches is uniquely identified by a circuit identification code (CIC) that is included in the ISUP messages.

The exchange uses this information along with the received signaling information (especially the called party number) to determine which inbound and outbound circuits should be connected together to provide an end to end speech path.

In addition to call related information, ISUP is also used to exchange status information for, and permit management of, the available circuits. In the case of no outbound circuit being available on a particular exchange, a release message is sent back to the preceding switches in the chain.

ISUP variants
Different ISUP variants exist. ITU-T specifies the variant used in the international network. In Europe ETSI releases its own ISUP specification which is close that of the ITU-T. ITU-T ISUP is used for international connections and is the base for some national ISUP variants.

Most countries have their own variation of ISUP to cover national requirements. ANSI specifies variations of ISUP utilized under the North American Numbering Plan; however, some countries under the NANP differ in their support of some procedures (for example, LATA is meaningless within Canada.

Also, RBOCs support Telcordia procedures not fully specified by ANSI.) Some countries outside the NANP support ANSIbased variants (e.g. Mexico). While these variations of ISUP differ in subtle ways, the vast majority of ISUP message type, parameter type, and parameter field code-points, and related fundamental call processing procedures, agree across all variants.

ITU-T specification versions 1984 ISUP Red Book 1988 ISUP Blue Book 1991 ISUP Q.767 1992 ISUP'92 White Book (segmentation, compatibility, new supplementary services) 1997 ISUP'97 (new procedures, IN CS1, new supplementary services) According to ITU-T Q.761 section 2.4.1 ISUP interworking ISUP'92 is backwards compatible with ISUP Blue Book and Q.767 for basic call procedures and supplementary services except for some procedures (e.g. number portability). Additionally the compatibility features introduced in this version ensure forward compatibility with newer versions.

Message types
An ISUP message contains a fixed header containing the circuit identification code and the ISUP message type, followed by a mandatory fixed-length parameter part, a mandatory variablelength parameter part, and an optional parameter part that are dependent on the type of message being sent. ISUP messages can be sent using the services of the Message Transfer Part, or, less often, the Signaling Connection Control Part. These messages are transmitted in various stages of call setup and release. The most common messages are:

 Initial address message (IAM) First message sent to inform the partner switch that a call has to be established on the CIC contained in the message. Contains the called number, type of service (speech or data) and optional parameters.

Subsequent address message (SAM) For networks that support overlap dialing procedures, and then in the case that the IAM did not contain the full called number, one or more SAMs follow containing additional digits. This message is not supported by networks that only support en bloc dialing procedures.

 Address complete message (ACM) Message returned from the terminating switch when the subscriber is reached and the phone starts ringing, or when the call traverses an interworking point and the intermediate trunk is seized.
Call progress (CPG) Contains additional information about the progress of a call. Normally sent after the ACM when the status of the call changes from that reported in the

ACM.

Answer message (ANM) Sent when the subscriber picks up the phone, a resource is connected or answer supervision is returned by an interworking point. Normally charging starts at this moment. It is required that the call be cut through in both directions by this point. Connect (CON) Sent when the call is answered by an automatic terminal. This message replaces the ACM, CPG and ANM for calls that are answered by automatic terminals.
Release (REL) Sent to clear the call when a subscriber goes on hook. This is also sent (in direct response to an IAM) if the terminating switch determines that the call cannot be completed. In either case, the terminating switch provides a cause value in the message to explain the reason for the release, e.g., "User busy". Release complete (RLC) Acknowledgment of the release the circuit is idle afterward and can be used again.

Release codes
Release codes are used to identify and debug any events occurring in ISDN User Part signaling. Every event in ISUP signaling generates a release code number. Even for a normal ISUP call, a release code is generated. There are lot of applications developed based on the release code from ISUP signaling. Similarly Telecom operators trace for Release codes to debug any call failures.
Following are the list of releases codes used. Release codes only defined by number are effectively undefined, and may be used for proprietary solutions.

Message format

The Signaling Information Field (SIF) for all ISUP Message Signal Units (MSU) contain the following components: Routing Label Circuit Identification Code Message Type Mandatory Fixed Part Mandatory Variable Part Optional Part

The Routing Label indicates the Point Codes of the originating and destination nodes in the network; it also includes the Signaling Link Selection field that is used to select between the multiple routes an MSU could take between two nodes. The Circuit Identification Code is used to specify which trunk between two switches is used to carry a particular call. Note that some versions of ANSI ISUP permit a CIC with 14 significant bits instead of the 12 that are shown.

1. The Message Type indicates the ISUP message type. The presence and form of the remaining 3 components are determined by this message type. 2. The Mandatory fixed part, when present, contains the mandatory, fixed-length parameters associated with the message type. 3. The Mandatory variable part, when present, contains the mandatory, variable-length parameters associated with the message type. 4. The Optional part, when present, contains the optional parameters permitted to be included in the message type.

When sent using the services of the Signaling Connection Control Part, ISUP messages passed to SCCP in the User Data parameter (NSDU) consist of only the last 4 components (Message Type, Mandatory fixed part, Mandatory variable part, Optional part). The routing label and circuit identification code are not included in the user data passed to SCCP.

Mobile Application Part

The Mobile Application Part (MAP) is an SS7 protocol which provides an application layer for the various nodes in GSM and UMTS mobile core networks and GPRS core networks to communicate with each other in order to provide services to mobile phone users. The Mobile Application Part is the application-layer protocol used to access the Home Location Register, Visitor Location Register, Mobile Switching Center, Equipment Identity Register, Authentication Centre, Short message service center and Serving GPRS Support Node (SGSN)

Facilities provided
The primary facilities provided by MAP are: 1. Mobility Services: location management (to support roaming), authentication, managing service subscription information, fault recovery, 2. Operation and Maintenance: subscriber tracing, retrieving a subscriber's IMSI 3. Call Handling: routing, managing calls whilst roaming, checking that a subscriber is available to receive calls 4. Supplementary Services 5. Short Message Service Packet Data Protocol (PDP) services for GPRS: providing routing information for GPRS connections 6. Location Service Management Services: obtaining the location of subscribers

Published specification
The Mobile Application Part specifications were originally defined by the GSM Association, but are now controlled by ETSI/3GPP. MAP is defined by two different standards, depending upon the mobile network type: 1. MAP for GSM (prior to Release 4) is specified by 3GPP TS 09.02 2. MAP for UMTS ("3G") and GSM (Release 99 and later) is specified by 3GPP TS 29.002 3. Also there is Mobile Application Part specification for CDMA 3GPP2 network type: MAP for CDMA is specified by 3GPP2 X.S0004-000-E v9.0

Implementation
MAP is a Transaction Capabilities Application Part (TCAP) user, and as such can be transported using 'traditional' SS7 protocols or over IP using Transport Independent Signaling Connection Control Part (TI-SCCP); or using SIGTRAN.

MAP Signaling
In mobile cellular telephony networks like GSM and UMTS the SS7 application MAP is used. Voice connections are Circuit Switched(CS) and data connections are Packet Switched (PS) applications.

Some of the GSM/UMTS Circuit Switched interfaces in the Mobile Switching Center (MSC) transported over SS7 include the following:

1.

B -> VLR (uses MAP/B). Most MSCs are associated with a Visitor Location Register (VLR), making the B interface "internal". C -> HLR (uses MAP/C) Messages between MSC to HLR handled by C Interface

2.

3.

D -> HLR (uses MAP/D) for attaching to the CS network and location update
E -> MSC (uses MAP/E) for inter-MSC handover F -> EIR (uses MAP/F) for equipment identity check H -> SMS-G (uses MAP/H) for Short Message Service (SMS) over CS

4. 5. 6.

There are also several GSM/UMTS PS interfaces in the Serving GPRS Support Node (SGSN) transported over SS7: 1. Gr -> HLR for attaching to the PS network and location update 2. 3. Gd -> SMS-C for SMS over PS

Gs -> MSC for combined CS+PS signaling over PS 4. Ge -> Charging for Customized Applications for Mobile networks Enhanced Logic (CAMEL) prepaid charging

5.

Gf -> EIR for equipment identity check

INAP
The Intelligent Network Application Protocol (INAP) is a signaling protocol used in the intelligent network architecture. It is part of the SS7 protocol suite, typically layered on top of TCAP. It can also be termed as logic for controlling telecommunication services migrated from traditional switching points to computer based service independent platform The ITU defines several "capability levels" for this protocol, starting with Capability Set 1 (CS-1). A typical application for the IN is a Number Translation service. For example, in the United Kingdom, 0800 numbers are free phone numbers and are translated to a geographic number using an IN platform. The Telephone exchanges decode the 0800 numbers to an IN trigger and the exchange connects to the IN.

The Telephone exchange uses TCAP, SCCP and INAP and in IN terms is a Service Switching Point. It sends an INAP Initial Detection Point (IDP) message to the Service Control Point (SCP). The SCP returns an INAP Connect message, which contains a geographic number to forward the call to.

INAP messages are defined using ASN.1 encoding. SCCP is used for the routing. Extended form of INAP is Customized Applications for Mobile Enhanced Logic (CAMEL). TCAP is used to separate the transactions into discrete units.

IS-41
IS-41, also known as ANSI-41, is a mobile, cellular telecommunications system standard to support mobility management by enabling the networking of switches. ANSI41 is the standard now approved for use as the network-side companion to the wireless-side AMPS(analog), IS-136 (Digital AMPS), cdma One, and CDMA2000 networks. It competes with GSM MAP, but the two will eventually merge to support worldwide roaming.

IS-41 facilitates inter-switch operations like handoff and roaming authentication. IS-41 evolved through revisions 0, A, B, C, and D with increasingly robust and distributed call processing between switches and their roamer databases.
To describe IS-41 messaging requires special terminology to designate the telephone call's originating and terminating switch, called an MSC (anchor-MSC, candidate-MSC, homing-MSC, serving MSC and target MSC) and databases called VLR and HLR. For handoffs the messaging is between switches.

For roaming and authentication, the messaging would include an HLR and a VLR. In both cases, the PSTN may be needed to carry messaging.

 Signaling Connection Control Part (SCCP), a routing

protocol in SS7 protocol suite in layer 4, provides end-toend routing for TCAP messages to their proper database. SCCP provides connectionless and connection-oriented network services above MTP Level 3. While MTP Level 3 provides point codes to allow messages to be addressed to specific signaling points, SCCP provides subsystem numbers to allow messages to be addressed to specific applications or subsystems at these signaling points. SCCP is used as the transport layer for TCAP-based services such as freephone (800/888), calling card, local number portability, wireless roaming, and personal communications services (PCS).

 SCCP also provides the means by which an STP can

perform global title translation (GTT), a procedure by which the destination signaling point and subsystem number (SSN) is determined from digits (i.e., the global title) present in the signaling message. The global title digits may be any sequence of digits, such as 800/888 number, pertinent to the service requested.

 Protocol Structure - SCCP: SS7 Signalling

Connection Control PartSCCP messages are contained within the Signaling Information Field (SIF) of an MSU. There are two formats for the SCCP messages: one is defined by ANSI and the other is defined by ITU-T. Routing label Message type Mandatory fixed part Mandatory variable part Optional part

 Routing label - A standard routing label - see the

picture regarding the ANSI and ITU SCCP message for more information. Message type code - A one octet code which is mandatory for all messages. The message type code uniquely defines the function and format of each SCCP message. Mandatory fixed part - The parts that are mandatory and of fixed length for a particular message type will be contained in the mandatory fixed part.

 Mandatory variable part - Mandatory parameters of

variable length will be included in the mandatory variable part. The name of each parameter and the order in which the pointers are sent is implicit in the message type. Optional part - The optional part consists of parameters that may or may not occur in any particular message type. Both fixed length and variable length parameters may be included. Optional parameters may be transmitted in any order. Each optional parameter will include the parameter name (one octet) and the length indicator (one octet) followed by the parameter contents.