Some Protocols used in GPRS.

GPRS Tunnelling Protocol (GTP) is a group of IP-based communications protocols used to carry General Packet Radio Service (GPRS) within GSM and UMTS networks. GTP can be decomposed into separate protocols, GTP-C, GTP-U and GTP'. GTP-C is used within the GPRS core network for signaling between Gateway GPRS Support Nodes (GGSN) and Serving GPRS Support Nodes (SGSN). This allows the SGSN to activate a session on a user's behalf (PDP context activation), to deactivate the same session, to adjust quality of service parameters, or to update a session for a subscriber who has just arrived from another SGSN. GTP-U is used for carrying user data within the GPRS Core Network and between the Radio Access Network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats. GTP' (GTP prime) uses the same message structure as GTP-C and GTP-U, but has an independent function. It can be used for carrying charging data from the Charging Data Function (CDF) of the GSM or UMTS network to the Charging Gateway Function (CGF). In most cases, this should mean from many individual network elements such as the GGSNs to a centralized computer that delivers the charging data more conveniently to the network operator's billing center. Different GTP variants are implemented by RNCs, SGSNs, GGSNs and CGFs within 3GPP networks. GPRS mobile stations (MSs) are connected to a SGSN without being aware of GTP. GTP can be used with UDP or TCP. GTP version one is used only on UDP. GTP is the primary protocol used in the GPRS core network. It is the protocol which allows end users of a GSM or UMTS network to move from place to place whilst continuing to connect to the Internet as if from one location at the GGSN. It does this by carrying the subscriber's data from the subscriber's current SGSN to the GGSN which is handling the subscriber's session. Three forms of GTP are used by the GPRS core network.

GTP-U for transfer of user data in separated tunnels for each PDP context GTP-C for control reasons including: o setup and deletion of PDP contexts o verification of GSN reachability o updates; e.g., as subscribers move from one SGSN to another. GTP' for transfer of charging data from GSNs to the charging function.

RANAP (Radio Access Network Application Part)[1] protocol is used in UMTS signaling between the Core Network, which can be a MSC or SGSN, and the UTRAN. RANAP is carried over Iu-interface. RANAP signalling protocol resides in the control plane of Radio network layer of Iu interface in the UMTS (Universal Mobile Telecommunication System) protocol stack. Iu interface is the interface between RNC (Radio Network Controller) and CN (Core Network). RANAP is used for the following tasks:

Relocation Radio Access Bearer Management Paging Transport of signalling between a UE and the Core Network (non-access stratum signalling)

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.

Facilities provided
The primary facilities provided by MAP are:

Mobility Services: location management (roaming), authentication, managing service subscription information, fault recovery, Operation and Maintenance: subscriber tracing, retrieving a subscriber's IMSI Call Handling: routing, managing calls whilst roaming, checking that a subscriber is available to receive calls Supplementary Services Short Message Service Packet Data Protocol (PDP) services for GPRS: providing routing information for GPRS connections Location Service Management Services: obtaining the location of subscribers

Transaction Capabilities Application Part, from ITU-T recommendations Q.771Q.775 or ANSI T1.114 is a protocol for Signalling 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 in Intelligent Networks and MAP in mobile phone networks. TCAP messages are sent over the wire between machines. TCAP primitives are sent between the application and the local TCAP stack, all TCAP messages are primitives but there are primitives that are not messages, i.e. some are only transferred inside the local machine. A TCAP primitive is made up of one or more TCAP components.

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.

Decoded TCAP Message

This is a MO-SMS sent by a MAP layer and the hex stream is taken from TCAP layer. 62744804000200306b1a2818060700118605010101a00d600ba109060704000001001902 6c50a14e02010102012e3046800570314244448406a1709192555504352f090070979262 230400902011800124002743507a0ea2a3cb2071794e07b1c3ee733d7c2e83d22074d85e0 695ed6539685e2ebb0100 According to tag length values, this can be decoded as below.
| '--> 62|74 <- Start of Tcap begin message | '--> 48|04:00 02 00 30 <- Transaction ID | '--> 6B|1A <- Start of Dialog portion | '--> 28|18 | '--> 06|07:00 11 86 05 01 01 01 | '--> A0|0D | '--> 60|0B | '--> A1|09 | '--> 06|07:04 00 00 01 00 19 02 <- Application context | '--> 6C|50 <- Start of component portion | '--> A1|4E | '--> 02|01:01 <- Component Id (invoke id) | '--> 02|01:2E <- Operation Code | '--> 30|46 <- Start of parameter buffer | '--> 80|05:70 31 42 44 44 <SM-RP-DA(BCD) | '--> 84|06:A1 70 91 92 55 55 <SM-RP-OA(BCD) | '--> 04|35:2F 09 00 70 97 92 62 23 04 00 90 20 11 80 01 24 00 27 4

The Message Transfer Part (MTP) is part of the Signaling System 7 (SS7) used for communication in Public Switched Telephone Networks. MTP is responsible for reliable, unduplicated and in-sequence transport of SS7 messages between communication partners. MTP is formally defined primarily in ITU-T Recommendations Q.701, Q.702, Q.703, Q.704 and Q.705. Tests for the MTP are specified in the ITU-T Recommendations Q.781 for MTP2 and in Q.782 for MTP3. These tests are used to validate the correct implementation of the MTP protocol. Different countries use different variants of the MTP protocols. In North America, the formal standard followed is ANSI T1.111. Regional Bell Operating Companies The SS7 stack can be separated into four functional levels:[1]

Level 1 is the Signalling Data Link Functional Level (Data Link Level). Level 2 is the Signalling Link Functional Level (Link Level). Level 3 is the Signalling Network Functional Level (Network Level). Level 4 is the MTP User and consists of SCCP, ISDN, 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.[2] MTP and SCCP are together referred to as the Network Service Part (NSP).[3] There is no one-to-one mapping of MTP Levels 1 through 3 onto the OSI model.[4] Instead, MTP provides the functionality of Layers 1, 2 and part of Layer 3 in the OSI model.[5] 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).[6][7]

[edit] Signalling Data Link Functional Level

MTP Level 1 is described in ITU-T Recommendation Q.702, and provides the Signalling Data Link functional level for narrowband signalling links. For broadband signalling links, ITU-T Recommendation Q.2110 or Q.2111 describe the signalling data link function. 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.

[edit] Signalling Link Functional Level

MTP Level 2 is described in ITU-T Recommendation Q.703, and provides the Signalling Link functional level for narrowband signalling links. For broadband signalling links, ITU-T Recommendation Q.2140 and Q.2210 describe the signalling link function referred to as MTP3b. The signalling link functional level may also be provided using the SIGTRAN protocol M2PA described in RFC 4165. MTP2 provides 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 signalling 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.

[edit] Signalling Network Functional Level

MTP Level 3 is described in ITU-T Recommendation Q.704, and provides the Signalling Network functional level for narrowband signalling links and, with only minor modifications described in ITU-T Recommendation Q.2210, for broadband signalling links. The functions of MTP Level 3 may also be replaced with the Generic Signalling 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; when the availability of MTP2 data links changes, MTP3 establishes alternative links as required and propagates information about route availability through the network. Access to the signalling 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.

[edit] 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.[7] The services provided to MTP Level 4 by the MTP (that is, MTP to MTP Users) is described in ITU-T Recommendation Q.701.

The Signalling Connection Control Part (SCCP) is a network layer[1] 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. 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

The connectionless protocol classes provide the capabilities needed to transfer one Network Service Data Unit (NSDU) in the "data" field of an XUDT, LUDT or UDT message. When one connectionless message is not sufficient to convey the user data contained in one NSDU, a segmenting/reassembly function for protocol classes 0 and 1 is provided. In this case, the SCCP at the originating node or in a relay node provides segmentation of the information into multiple segments prior to transfer in the "data" field of XUDT (or as a network option LUDT) messages. At the destination node, the NSDU is reassembled. The connection-oriented protocol classes (protocol classes 2 and 3) provide the means to set up signalling connections in order to exchange a number of related NSDUs. The connection-oriented protocol classes also provide a segmenting and reassembling capability. If an NSDU is longer than 255 octets, it is split into multiple segments at the originating node, prior to transfer in the "data" field of DT messages. Each segment is less than or equal to 255 octets. At the destination node, the NSDU is reassembled.[3]

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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 Signalling Transport service specified in Q.2150.0, the signalling transport converter for SCTP specified in Q.2150.3 and a specialized Transport-Independent Signalling Connection Control Part (TI-SCCP) specified in T-REC-Q.2220. TI-SCCP can also be used with the Generic Signalling Transport adapted for MTP3 and MTP3b as described in Q.2150.1, or adapted for SSCOP or SSCOPMCE as described in Q.2150.2.

BSSAP+ protocol : Gs: Interface between the SGSN and the MSC (VLR). Uses the BSSAP+ protocol. This interface allows paging and station availability when it performs data transfer. When the station is attached to the GPRS network, the

SGSN keeps track of which routing area (RA) the station is attached to. An RA is a part of a larger location area (LA). When a station is paged this information is used to conserve network resources. When the station performs a PDP context, the SGSN has the exact BTS the station is using. GMM : Protocols to manage and support the transmission of voice, data and video over wireless networks. GPRS Mobility Management (GMM) is a GPRS signaling protocol that handles mobility issues such as roaming, authentication, and selection of encryption algorithms. GPRS Mobility Management, together with Session Management (GMM/SM) protocol support the mobility of user terminal so that the SGSN can know the location of a mobile station (MS) at any time and to activate, modify and deactivate the PDP sessions required by the MS for the user data transfer. IuPS interface This is the interface in UMTS which links the RNC (Radio Network Controller) with a 3G SGSN (3G Serving GPRS Support Node). GTP-U is used on the IuPS between the GPRS core network and the RAN, however the GTP-C protocol is not used. In this case, RANAP is used as a control protocol and establishes GTP-U tunnels between the SGSN and the radio network controller (RNC). Iu-CS Interface (Circuit Switched) This is the interface in UMTS which links the RNC with a 3G MSC (3G Mobile Switching Centre). (Radio Network Controller)

------------------------------------------xxx------------------------------------------------------