GSM PROTOCOL

skgochhayat@gmail.com

Functions Of Protocols

Session establishment and termination between users. Orderly exchange of Data messages. Coding of the information. Routing and Sequencing Flow control and Congestion control. Error checking and recovery. Efficient network resource utilization

Example Of Some Functions

Code conversion to facilitate understanding of the meaning. Routing of the messages through Network. Error control to counteract effect of disturbances. Transmission of Electrical Signals.

OSI Layers

The OSI model is built of seven ordered layers:

Layer-7: Application Layer-6: Presentation Layer-5: Session Layer-4: Transport Layer-3: Network Layer-2: Data Link Layer-1: Physical

Application Presentation Session

Transport
Network Data Link Physical

OSI Layers

The seven layers can be thought of as belonging to three sub groups

Network Support Layers (Layers 1-3) User Support Layers (Layers 5-7)
systems
one device to another

Deal with the physical aspects of moving data from

Allow interoperability among unrelated software

Layer-4 ensures end to end reliable data

transmission

OSI Layers
End System Application Presentation User Support Layers Session Network Support Layers Transport Network Network Network Network Data Link Data Link Data Link Data Link Physical Physical Physical Physical
PSPDN

PSTN

Dedicated

CSPDN

Hierarchical communication.

Within a single machine, each layer calls upon the services of the layer just below it The passing of data and network information is made possible by an interface between each pair of adjacent layers The messages exchanged between the adjacent layers, to obtain the required services, are called Interface Control

Peer-to-Peer communication

Between machines, layer-n on one machine communicates with layer-n on another machine This communication is governed by an agreedupon series of rules and conventions called protocols The processes on each machine that communicates at a given layer are called peerto-peer processes At the physical layer, communication is direct At higher layers, communication moves down

Hierarchical & Peer-to-Peer Communications

Hierarchical

N+1-Layer
Interface

PCI

N+1-Layer
Interface

N-Layer
ICI

Peer-to-Peer

N-Layer

Control Information (ICI) Protocol Control Information (PCI)

Interface

Data Units in the OSI Model

(N+1)-PDU (N+1)-PCI
(N+1)-Layer (N)-Layer (N+1)-PCI (N+1)-SDU

(N+1)-SDU
(N)-ICI (N)-IDU (N)-ICI (N)-ICI (N)-SDU

(N+1)-PCI

(N+1)-SDU (N)-PDU

(N)-PCI (N)-PCI (N+1)-PCI (N+1)-SDU

Data Units

Protocol Control Information (PCI)

(N)-PCI is the protocol control information

exchanged between the (N)-entities to coordinate their functions

Service Data Units (SDU)

(N)-SDU is the data unit transferred between

the ends of a (N)-connection whose identity is preserved during the transfer

Protocol Data Unit (PDU)

(N)-SDU

(N)-PDU is the combination of (N)-PCI and

Data Units

Interface Control Information (ICI)

(N)-ICI is the information exchanged between

(N+1)-entity and (N)-entity to coordinate their functions

Interface Data Unit (IDU)

(N)-IDU is the total data unit transferred across

the SAP between (N+1)-entity and (N)-entity

OSI Layers
7-Application
7-6 Interface Link Intermediate Node Link

7-Application
7-6 Interface

6-Presentation
6-5 Interface

6-Presentation
6-5 Interface

5-Session
5-4 Interface

5-Session
5-4 Interface

4-Transport
4-3 Interface

4-Transport
4-3 Interface

3-Network
3-2 Interface

3-Network
3-2 Interface

3-Network
3-2 Interface

2-Data Link
2-1 Interface

2-Data Link
2-1 Interface

2-Data Link
2-1 Interface

1-Physical

1-Physical

1-Physical

Summary of OSI Layers Functions

Application Translate, encrypt and compress data
7-6 Interface

Allow access to network resources

Presentation
6-5 Interface

Session
5-4 Interface

Establish, manage and terminate sessions

Reliable end to end delivery & error recovery

Transport
4-3 Interface

Network Organise bits into streams; Node to node delivery

3-2 Interface

Movement of packets; Provide internetworking

Data Link
2-1 Interface

Physical

Transmit bits; Mechanical and electrical specifications

Summary of OSI Layers Functions

Application Translate, encrypt and compress data
7-6 Interface

Allow access to network resources

Presentation
6-5 Interface

Session
5-4 Interface

Establish, manage and terminate sessions

Reliable end to end delivery & error recovery

Transport
4-3 Interface

Network Organise bits into streams; Node to node delivery

3-2 Interface

Movement of packets; Provide internetworking

Data Link
2-1 Interface

Physical

Transmit bits; Mechanical and electrical specifications

GSM System Architecture

BSS 16Kb/s
TRAU BSC

NSS GSTN
64Kb/s

R A D I O MS

MSC ISDN

VLR
BTS

SS7

HLR

NSS

BSS : Base Station Sub-system BSC : Base Station Controller BTS : Base Transceiver Station TRAU : Transcoder / Rate Adapter Unit

NSS : Network and Switching Sub-system MSC: Mobile service Switching Center HLR : Home Location Register VLR : Visitors Location Register

GSM protocol layers for signaling U A

m bis

A MSC
CM

MS
CM MM RR RR LAPDm radio LAPDm radio

BTS

BSC

MM
BSSAP

BSSAP

BTSM LAPD PCM

RR BTSM LAPD PCM

SS7
PCM

SS7
PCM

16/64 kbit/s

64 kbit/s / 2.048 Mbit/s

ISDN Protocol

Two types of ISDN Interfaces : Basic Rate Interface (BRI), and Primary rate interface (PRI), provide multiple digital bearer channels over which temporary connections can be made and data can be sent. The result is digital dial access to multiple site concurrently. Type of Interface Number of Bearer Channels (B channels) 2 23 30 Number of Signaling Channels (D Channels) 1 (16 Kbps) 1 (64 Kbps) 1 (64 Kbps)

BRI PRI(T/1) PRI(E/1)

ISDN Channels

B Channels : Bearer channels (B channels) are used to transport data. B Channels are called bearer channels because they bear the burden of transporting the data. B channels operate up to 64 Kbps, although the speed might be lower depending on the service provider. D Channels are used for signaling. LAPD is used to deliver signaling message to the ISDN switch

LAPD and PPP on D and B Channels

BRI B0 B1 D LAPD Call Setup Flows SS7 BRI

Call Setup Flows ISDN Network

B0 B1 D LAPD Call Setup Flows

BRI B0 B1 D LAPD

PPP

BRI B0 B1 D LAPD

ISDN Network

LAPD and PPP on D and B Channels

The call is established through the service provider network; PPP is used as the data link protocol on the B channel from end to end. LAPD is used between the router and the ISDN switch at each local central office (CO) and remains up so that new signaling messages can be sent and received. Because the signals are sent outside the channel used for data, this is called out-of-band signaling. The BRI encodes bits at 192 kbps, out of which 144 Kbps is used by B and D Channels rest is used for framing.

Use of ISDN as WAN Protocol

Dial on Demand Routing Logic is configured in the routers to trigger the dial when that traffic needs to get to another site is sent by user. Telecommuting Environment Backup to leased lines When leased line fails, an ISDN call is established between two routers.

ISDN as WAN Link

Dial on Demand Routing ISDN Network Telecommuting

NT1

ISDN Network Leased Line Backup Leased Line

Computer with ISDN Inerface

BRI

BRI

ISDN Network

Layer 2 LAPDM Protocol

Establishment and release of signalling layer 2 connections. Multiplexing and de multiplexing of several signalling layer 2 connection on a dedicated control channel and discrimination between them by including different Service Access Point Identifiers (SAPI). Mapping of signalling layer 2 service data units on protocol data unit (in case of acknowledged operation service data units may be segmented and reassembled at destination). Detection and recovery of errors due to loss, duplication, and disorder. Flow control.

LAPDM Protocol

The establishment and release of layer 2 connection coincides with the allocation release, and change of dedication radio channels. Signaling layer 2 connections are frequently established and released, and thus an average lifetime of a connection is short. Multiplexing and demultiplexing deals with arranging different user (eight channels per frame) in a frame format. LAPDm uses on the two modes of operation for the transmission of layer 3 message; unacknowledged operation of multiple frame operation.

LAPDM Protocol

On the DCCH both unacknowledged and acknowledged operations are used, DCCHs (SDCCH, SACCH and FACCH) whereas on the CCCHs only unacknowledged operation is applied. Thus, both modes are applicable for transmission over on of the in contrast top information transfer over CCCHs (BCCH, PCH and AGCH)

LAPDM Protocol

For an unacknowledged information transfer, the use of layer 3 service implies that the information transfer is not acknowledged by the data link layer, and thus error check facilities are not provided. The transmission and reception of messages here use data link service primitives, that is, DL-DATA-REQUEST and DL-DATA-INDICATION.

LAPD and LAPDm

The main distinction between LAPD and LAPDm is the absence of address and control fields. Thus, the protocol is only used for the unacknowledged mode of operation, which applies to BCCHs and CCCHs only. Both FCCH and SCH under BCCH do not require unacknowledged. Similarity, no acknowledgement is needed for PCH and AGCH. The LAPD frame is used internal to BSS, namely, between BTS and BSC.

MTP3, SCCP, and TCAP Protocols.

SS7 Signaling

The Telephone Network [1/2]

ISUP Messages INAP/TCAP Messages Signal Transfer Point Intelligent Peripheral Service Service + Control Data Point Point Control Layer

Transport Layer

Class 4 Tandem Switch

Class 5 End Office Switch

Circuit Switched Network

The Telephone Network [2/2]

5 Basic Components in Intelligent Networks SSP/Service Switching Point switching, service invocation STP/Service Transfer Point signal routing TCAP messages SCP/Service Control Point IP service logic execution SDP/Service Data Point subscriber data storage, access SSP IP/Intelligent Peripheral resources such as customized voice announcement, voice recognition, DTMF digit collection

SCP

SDP

STP

STP

ISUP messages Voice

SSP

Signalling example
BBSR Exch Exch KOLKOTA Database A typical scenario: User A calls mobile user B. The call is routed to a specific gateway exchange (GMSC) that must contact a database (HLR) to find out under which exchange (MSC) the mobile user is located. The call is then routed to this exchange. Exch CUTTACK

User A (calling user)

User B (called user)

SS7 Protocol Suite

OSI Layers Transaction Capabilities Applications Part Signaling Connection Control Part Application

INAP

MAP

Presentation Session
Transport

TCAP

ISUP

IN Application Part Mobile Application Part ISDN User Part

SCCP MTP Level 3

MTP Level 2

Network
Data Link

Physical

MTP Level 1

MTP Levels 1 & 2

Message Transfer Part Level 1 Handling the issues related to the signals on the physical links between one signaling node and another Closely to layer 1 of the OSI stack Level 2 Dealing with the transfer of messages on a given link from one node to another Providing error detection/correction and sequenced delivery of the SS7 messages signalling network supervision and maintenance functions

MTP Level 3

Signaling message handling

Providing message routing between signaling points

in the SS7 network May pass a number of intermediate nodes (STP, Signal Transfer Point) MTP level 3 users are ISUP and SCCP

Signaling network management

Rerouting traffic to other SS7 signaling links in the

case of link failure, congestion or node failure Load-sharing

Services

Provides a number of services to the protocol

layer above it

The transfer of messages Indicating availability of resources MTP-Transfer request, MTP-Transfer indication,
MTP_Pause indication, MTP-Resume indication, and MTP-Status indication

ISUP

ISDN User Part Used as the protocol for setting up and tearing down phone calls between switches Initial Address Message (IAM) To initiate a call between two switches Answer Message (ANM) To indicate that a call has been accepted by the called party Release Message (REL) To initiate call disconnection

Connection-Oriented Protocol

A connection-oriented protocol

Related to the establishment of connections

between users The path of messages and the path of the bearer might be different

SCCP

Signaling Connection Control Part Used as the transport layer for TCAP-based services

Free phone (800/888), calling card, wireless roaming

Mostly connectionless signaling

Both connection-oriented and connectionless

Global title translation (GTT) capabilities

number is determined from the global title

The destination signaling point and subsystem

TCAP, MAP and INAP

TCAP (Transaction Capabilities Applications Part)

Supporting the exchange of non-circuit related

information between signaling points Queries and responses sent between SSPs and SCPs are carried in TCAP messages

Provides services to

INAP (IN Application Part) MAP (Mobile Application Part)

SS7 Network Architecture

Figure 7-4 depicts a typical SS7 network arrangement. This configuration serves several purposes.

No direct signaling links A fully meshed signaling network is not required. The quad arrangement ensures great robustness.

Signaling Point (SP)

Each node in an SS7 network is an SP. The signaling address of the SP is known as a signaling point code (SPC). Linkset

Group of signaling links directly connecting

two SPCs For capability and security reasons

Service Switching Point (SSP)

Signal Transfer Point (STP)

To transfer messages from one SPC to another

Service Control Point (SCP)

A network entity that contains additional logic and that can be used to offer advanced services The switch sends a message to the SCP asking for instructions.

The SCP, based upon data and service logic

that is available, will tell the switch which actions need to be taken.

An good example toll-free 800 number

 An example

A subscriber dials a toll-free 800 number The SSP knows that it needs to query the SCP The SCP contains the translation information The SCP responds to the SSP with a routable
number The SSP routes the call Connectionless signaling The application use the services of TCAP, which in turn uses the services of SCCP

 The messages sent in Units the SS7 network Message Signal (MSUs)
Backward Sequence Number BSN Indicator Bit Forward Sequence Number Length Indicator

Message Signal Units (MSUs)

The messages sent in the SS7 network The format of an MSU

SIO Service Information Octet

Indicate the upper-level protocol (e.g., SCCP or

ISUP) A sub-service field indicating the signaling numbering plan

SIF Signaling Information Field

The actual user information The ANSI version and the ITU-T version The routing label

 Signaling Link Selection (SLS)

The particular signaling link to be used

SS7 addressing The ANSI version, 24 bits Member, cluster, network codes An operator has a network code The ITU-T version, 14 bits International Signaling Gateway Use sub-service field National, Nation Spare, International, International Spare An international gateway has one national point code and one international code

International Signaling

Same SPCs can be reused at different network levels

International SPC = 277

National

SPC = 277

SPC = 277 means different signalling points (network elements) at different network levels. The Service Information Octet (SIO) indicates whether the DPC and OPC are international or national signalling point codes.
F CK SIF SIO LI Control F

ISDN User Part (ISUP)

ISUP is a signalling application protocol that is used for establishing and releasing circuit-switched connections (calls).

Only for signalling between exchanges (ISUP can never be used between an exchange and a stand-alone database)
Not only for ISDN (=> ISUP is generally used in the PSTN)

Structure of ISUP message:

SIO (one octet) Routing label (four octets) CIC (two octets) Message type (one octet) Mandatory fixed part Mandatory variable part Optional part Must always be included in ISUP message E.g., IAM message E.g., contains called (user B) number in IAM message

The ISDN User Part (ISUP) ISUP

calls IAM

The most-used SS7 application The establishment and release of telephone

Called number, calling number, transmission

requirement, type of caller,

ACM

The call is through-connected to the destination A one-way-audio path is opened for ring-back tone Optional
If not returned, no ring-back tone at all

 CPG, Call Progress

ANM, Answer Message

Optional; provide information to the calling switch

REL, Release RLC, Release Complete

Open the transmission path in both directions Instigate charging for the call

CIC, circuit identification Code

Indicates the specific trunk between two

switches OPC, DPC, and CIC

Difference between SLS and CIC

The four-bit signalling link selection (SLS) field in the routing label defines the signalling link which is used for transfer of the signalling information. The 16-bit circuit identification code (CIC) contained in the ISUP message defines the TDM time slot or circuit with which the ISUP message is associated. Signalling link STP Exchange Circuit Exchange

ISUP Call Establishment and Release

A given circuit between two switches is identified by OPC, DPC and CIC.

Signalling using IAM message

STP SL 4 SL 7 SPC = 82 Circuit 14 Exchange Outgoing message: OPC = 82 CIC = 14 DPC = 22 SLS = 4 Exchange SPC = 22 Circuit 20 SPC = 60

STP

Exchange

Processing in (transit) exchange(s): Received IAM message contains B-number. Exchange performs number analysis (not part of ISUP) and selects new DPC (60) and CIC (20).

Setup of a call using ISUP

User A LE A Transit exchange LE B User B

Setup

IAM
Number analysis

IAM

DSS1 signalling assumed

Setup Alert

Alert

ACM

ACM

Connect

ANM
Charging of call starts now

ANM

Connect

ISUP message format

Signalling Connection Control Part (SCCP)

SCCP is required when signalling information is carried between exchanges and databases in the network. An important task of SCCP is global title translation (GTT): Exchange STP
STP with GTT capability

Database

1. Exchange knows the global title (e.g. 0800 number or IMSI number in a mobile network) but does not know the DPC of the database related to this global title.

2. SCCP performs global title translation in the STP (0800 or IMSI number => DPC) and the SCCP message can now be routed to the database.

Example: SCCP usage in mobile call

Mobile switching center (MSC) needs to contact the home location register (HLR) of a mobile user identified by his/her International Mobile Subscriber Identity (IMSI) number.
SCCP/GTT functionality STP SCCP SPC = 32 SCCP

MSC located in Espoo

SPC = 82 Outgoing message: OPC = 82 DPC = 32 SCCP: IMSI global title

HLR located in Oslo

SPC = 99 Processing in STP: Received message is given to SCCP for GTT. SCCP finds the DPC of the HLR: DPC = 99

To sum it up with an example

Part B, Section 3.3 in Understanding Telecommunications 2 Typical operation of a local exchange PSTN Transmission (PDH, SDH)

Subscriber signalling (analog or ISDN=DSS1)

Networkinternal signalling (SS7)

Databases in the network (HLR)

Basic local exchange (LE) architecture

Modern trend: Switching and control functions are separated into different network elements (separation of user and control plane).
Subscriber stage LIC LIC Time switch Tone Rx

Switching system
Group switch ETC ETC Sign. TDM links to other network elements Exchange terminal circuit

Tone generator Line interface circuit

Switch control E.164 number analysis Charging User databases O&M functions

SS7 Signalling equipment

Control system

Setup of a call (1)

Phase 1. User A lifts handset and receives dial tone.
Local exchange of user A

4. Tone Rx is connected
1. Off hook LIC LIC 5. Dial tone is sent (indicating network is alive) Time switch Tone Rx

Switching system
Group switch ETC ETC Sign.

Tone generator

2. Check user database. For instance, is user A barred for outgoing calls? 3. Reserve memory for user B number

Control system

Setup of a call (2)

Phase 2. Exchange receives and analyzes user B number.
Local exchange of user A

Switching system
LIC LIC 1. User A dials user B number Time switch Tone Rx Group switch ETC ETC Sign.

2. Number (DTMF signal) received 3. Number analysis

4. IN triggering actions? Should an external database (e.g. SCP, HLR) be contacted?

Control system

Setup of a call (3)

Phase 3. Outgoing circuit is reserved. ISUP Initial address message (IAM) is sent to next exchange.
Local exchange of user A

Switching system
LIC LIC 1. Tone receiver is disconnected 2. Outgoing circuit is reserved 3. Outgoing signalling message (ISUP IAM) contains user B number Time switch Tone Rx Group switch ETC ETC Sign.

E.g., CIC = 24

IAM (contains information CIC = 24)

Control system

Setup of a call (4)

Phase 4. ACM received => ringback or busy tone generated. ANM received => charging starts.
Local exchange of user A

Switching system
LIC LIC 2. Ringback or busy tone is locally generated 4. Call continues Tone generator Time switch Group switch ETC ETC Sign.

ACM, ANM

1. ISUP ACM message indicates free or busy user B 3. Charging starts when ISUP ANM message is received

Control system

Performance Requirements for SS7

Bellcore spec. GR-246-Core

MTP

A given route set should not be out of service for

more than 10 minutes per year < 1*10-7 messages should be lost < 1*10-10 messages should be delivered out of sequence

ISUP

Numerous timing requirements

A VoIP network that uses SS7

Must meet the stringent requirements

Long-distance VoIP network A given route set should not be out of service for more than 10 minutes per year. No more than 1x10-7 messages should be lost. No more than 1x10-10 messages should be delivered out of sequence. In ISUP, numerous timing requirements must be met. How to make sure that VoIP networks can emulate the signaling performance of SS7. SIGTRAN (Signaling Transport) group of IETF

Performance Requirements for SS7

Softswitch Architecture

SS7 Network
SCP STP

Signaling (SS7) Gateway SIGTRAN

Internet
Call Agent
MGCP/ MEGACO

MGCP/ MEGACO Trunking Trunking Gateway Trunking Gateway Gateway

CO Switch

RTP

Residential Residential Gateway Residential Gateway Gateway

Signaling Transport (SIGTRAN) Addressing the issues regarding the transport of signaling within IP networks

The issues related to signaling performance

within IP networks and the interworking with PSTN

SIP/MEGACO/ISUP Interworking

Translating the MTP-based SS7 message (e.g.,

IAM) to IP-based message (e.g., IP IAM) Just a simple translation from point code to IP address ???

SIGTRAN Issues discussed in SIGTRAN

Address translation How can we deploy an SS7 application (e.g.,

ISUP) that expects certain services from lower layers such as MTP when lower layers do not exist in the IP network? For transport layer, the ISUP message must be carried in the IP network with the same speed and reliability as in the SS7.

UDP x TCP x

RFC 2719, Framework Architecture for Signaling Transport

SIGTRAN Architecture Signaling over standard IP uses a common

transport protocol that ensures reliable signaling delivery.

Error-free and in-sequence Stream Control Transmission Protocol (SCTP)

An adaptation layer is used to support specific primitives as required by a particular signaling application.

The standard SS7 applications (e.g., ISUP) do not realize that the underlying transport is IP.

ISUP Transport to MGC

NIF (Nodal Interworking Function) is responsible for interworking between the SS7 and IP networks

SCTP: fast delivery of messages (error-free, in sequence delivery), network-level fault tolerance

SIGTRAN Protocol Stack

Adaptation Layer [1/3] M2UA (MTP-2 User Adaptation

Layer)

Adaptation [2/3] M2PA (MTP-2 Layer Peer-to-Peer Adaptation Layer) An SG that utilizes M2PA is a signaling node for the
MGC.

It is effectively an IP-based STP.

SG can processing higher-layer signaling functions, such as SCCP GTT.

Adaptation Layer [3/3]

M3UA (MTP3-User Adaptation Layer) SUA (SCCP-User Adaptation Layer)

Applications such as TCAP use the services of SUA.

IUA (ISDN Q.921-User Adaptation Layer) V5UA (V5.2-User Adaptation Layer)

SCTP

To offer the fast transmission and reliability required for signaling carrying. SCTP provides a number of functions that are critical for telephony signaling transport.

It can potentially benefit other applications

needing transport with additional performance and reliability.

SCTP must meet the Functional Requirements of SIGTRAN.

Why not use TCP? TCP provides both reliable data transfer
and strict order-of-transmission, but SS7 may not need ordering.

TCP will cause delay for supporting order-oftransmission.

The limited scope of TCP sockets complicates the task of data transmission using multi-homed hosts. TCP is relatively vulnerable to DoS attack, such as SYN attacks.

What Supported By Using SCTP?

To ensure reliable, error-free, insequence delivery of user messages (optional). To support fast delivery of messages and avoid head-of-line blocking. To support network-level fault tolerance that is critical for carrier-grade network performance by using multi-home hosts. To provide protection against DoS attack by using 4-way handshake and cookie.

SCTP Endpoint & Association

Endpoint The logical sender/receiver of SCTP packets. Transport address = IP address + SCTP port number An endpoint may have multiple transport addresses (for multi-homed host, all transport addresses must use the same port number.) Association A protocol relationship between SCTP endpoints. Two SCTP endpoints MUST NOT have more than one SCTP association.

Multi-Homed Host

Host A

Host B

SCTP User SCTP One IP address

SCTP User SCTP One IP address One IP address

One SCTP association with multi-homed redundant

SCTP Streams

A stream is a one-way logical channel between SCTP endpoints.

The number of streams supported in an

association is specified during the establishment of the association.

To avoid head-of-line blocking and to ensure in-sequence delivery

stream.

In-sequence delivery is ensured within a single

SCTP Functional View

SCTP User Application
Association startup and takedown Sequenced delivery within streams User Data Fragmentation Acknowledgement and Congestion Avoidance Chunk Bundling Packet Validation Path Management

SCTP Packets & Chunks

A SCTP packet can comprise several chunks. Chunk Data or control

0
Common Header

. . .
Source Port Number

15 16
Verification Tag Checksum

. . .
Destination Port Number

31

Chunk Type

Chunk Flags Chunk Value

Chunk Length

Chunk 1

Chunk N

. . .

 ID Value Chunk Type

-------0 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Chunk Type --------------- Payload Data (DATA) - Initiation (INIT) - Initiation Acknowledgement (INIT ACK) - Selective Acknowledgement (SACK) - Heartbeat Request (HEARTBEAT) - Heartbeat Acknowledgement (HEARTBEAT ACK) - Abort (ABORT) - Shutdown (SHUTDOWN) - Shutdown Acknowledgement (SHUTDOWN ACK) - Operation Error (ERROR) - State Cookie (COOKIE ECHO) - Cookie Acknowledgement (COOKIE ACK) - Reserved for Explicit Congestion Notification Echo (ECNE) - Reserved for Congestion Window Reduced (CWR) - Shutdown Complete (SHUTDOWN COMPLETE) - Reserved for IETF

SCTP control chunks

INIT chunk

Initiate an SCTP association between two

endpoints Cannot share an SCTP packet with any other chunk

INIT ACK

Acknowledge the initiation Must not share a packet with any other chunk Acknowledge the receipt of Data chunks Inform the sender of any gaps

SACK

HEARTBEAT

When no chunks need to be sent Send periodic HEARTBEAT messages Contain sender-specific information
Containing heartbeat information copied form
HEARTBEAT

HEARTBEAT ACK ABORT

End an association abruptly Cause information Can be multiplexed with other SCTP control
chunks

SHUTDOWN

A graceful termination of an association Stop sending any new data Wait until all data sent has been

acknowledged Send a SHUTDOWN to the far end

Upon receipt of a SHUTDOWN

Indicate the chunk received

Retransmit data that are not acknowledged Send a SHUTDOWN ACK

SHUTDOWN ACK SHUTDOWN COMPLETE

ERROR

Some error condition detected

E.g., a chunk for a non-existent stream

COOKIE ECHO
Used only during the initiation of an association An INIT ACK includes a cookie parameter Information specific to the endpoint, a timestamp, a cookie lifetime Upon receipt of an INIT ACK

Return the cookie information in COOKIE ECHO Can be multiplexed; must be the first chunk

COOKIE ACK

INIT Chunk
0 Type = 1 . . . Chunk Flags Initial Tag Advertised Receiver Window Credit (a_rwnd) Number of Outbound Streams Number of Inbound Streams 15 16 . . . Chunk Length 31

Initial TSN (Transmission Sequence Number) Optional / Variable-Length Parameter . . .

Association Establishment
INIT [I-Tag=Tag_A] INIT ACK [V-Tag=Tag_A, I-Tag=Tag_Z, Cookie_Z]

COOKIE [Cookie_Z] COOKIE ACK

allocating resources

User Data Transfer

SCTP user User Messages

SCTP DATA Chunks

SCTP Control Chunks

SCTP packets

SCTP

Connectionless Packet Transfer Service (e.g. IP)

DATA Chunk
0
Type = 0

. . .
Reserved

15 16
UB E TSN

. . .
Chunk Length

31

Stream ID = S

Stream Sequence Number = n Payload Protocol ID

User Data (Sequence n of Stream S)

. . .

U : unordered B : begin E : end

Payload data chunk

Carry information to and from the ULP U: unordered bit B and E: beginning and end bits
without regard to sequencing

The information should be passed to the ULP

Segment a
given user message

TSN: Transmission Sequence Number (32-bit)

Independent of any streams Assigned by SCTP An INIT has the same TSN as the first DATA chunk

 S: Stream Identifier (16-bit) n: stream sequence number (16-bit)

Payload protocol identifier
Begins at zero Increments for each new message For the users to pass further information about the
chunk but is not examined by the SCTP

SACK Chunk
0
Type = 3

. . .
Chunk Flags

15 16
Cumulative TSN Ack

. . .
Chunk Length

31

Advertised Receiver Window Credit (a_rwnd) Number of Gap Ack Blocks = n Gap Ack Block #1 Start Number of Duplicate TSNs = x Gap Ack Block #1 End

. . .
Duplicate TSN #1

. . .

Transferring data

Reliable transfer SACK chunk

Cumulative TSN

The number of Gap Ack Blocks The number of duplicate TSNs

2

unbroken sequence 2

The highest TSN value received without any gaps 4

The number of fragments received after the

 Gap Ack Block number 1 start Gap Ack Block number 1 end a_rwnd

sequence 8 (8-4)

The offset of the first segment from the unbroken

sequence 3 (7-4)

The offset of the first segment from the unbroken

The updated buffer space of the sender

SCTP Robustness Robustness is a key characteristic of any

carrier-grade network.

To handle a certain amount of failure in the network without a significant reduction in quality

INIT and INIT ACK chunks may optionally include one or more IP addresses (a primary address + several secondary addresses).

Multi-homes hosts

SCTP ensures that endpoint is aware of the reachability of another endpoint through the following mechanisms.

SACK chunks if DATA chunk have been sent HEARTBEAT chunks if an association is idle

M3UA Operation

M3UA over SCTP Application Server

A logical entity handling signaling for a scope A CA handles ISUP signaling for a SS7
DPC/OPC/CIC-range An AS contains a set of Application Server Processes (ASPs)

ASP

A process instance of an AS Can be spread across multiple IP addresses Active ASPs and standby ASPs

Routing Key

A set of SS7 parameters that identifies the

signaling for a given AS OPC/DPC/CIC-range

Network Appearance

A mechanism for separating signaling traffic

between an SG and an ASP E.g., international signaling gateway

Signaling Network Architecture

No single point of failure

SGs should be set up at least in pairs ASPs

A redundant or load-sharing configuration Spread over different hosts

Point code
same PC

All ASPs and the connected SG share the

All ASPs share a PC != that of the SG
ASPs: a signaling endpoint; SG: an STP A single SS7 signaling endpoint

Robust Signaling Architecture

Services Provided by M3UA

Offer the same primitives as offered by MTP3

MTP-Transfer request MTP-Transfer indication MTP-Pause indication

suspended

Signaling to a particular destination should be Signaling to a particular destination can resume

MTP-Resume indication MTP-Status indication

Some change in the SS7 network

Transferring application message

A CA sends an ISUP message MTP-Transfer request A SCTP DATA chunk Transmitted to a SG M3UA MTP3 To the SS7 network

M3UA Messages

Messages between peer M3UA entities A header + the M3UA message content The entities can communicate information
regarding the SS7 network

If a remote destination becomes unavailable The SG becomes aware of this through SS7
signaling-network management messages The SG pass M3UA messages to the CA The ISUP application at the CA is made aware

MTP-Pause indication

Signaling Network Management MSGs

S7ISO SS7 Network Isolation

lost

When all links to the SS7 network have been Sent from the SG to all connected ASPs Destination(s) within the SS7 network is not
available

DUNA Destination Unavailable

DUNA is generated at the SG

message

Allocate 24 bits for each DPC

It determines from MTP3 network management

DAVA - Destination Available

Sent from SG to all concerned ASPs Mapped to the MTP-Resume indication Sent from an ASP to an SG To query the status of one or more destination The SG responds with DAVA, DUNA, or
SCON

DAUD Destination State Audit

SCON SS7 Network Congestion

Sent from the SG to ASPs The route to an SS7 destination is congested

DUPU Destination User Part Unavailable

Sent from the SG to ASPs A given user part at a destination is not

available The DPC and the user part in question Mapped to MTP-Status indication Cause codes

DRST Destination Restricted

Sent from the SG to ASPs

ASP management

ASPUP ASP Up

Used between M3UA peers The adaptation layer is ready to receive traffic
or maintenance messages

ASPDN ASP Down

An ASP is not ready

UP ACK ASP Up Ack DOWN ACK ASP Down Ack

ASPAC ASP Active

Sent by an ASP Indicate that it is ready to be used To receive all messages or in a load-sharing
mode Routing context

DPC/OPC/CIC-range ASPIA ASP Inactive ACTIVE ACK ASP Active Ack

Indicate the scope is applicable to the ASP

BEAT Heartbeat

Between M3UA peers Still available to each other When M3UA use the services of SCTP
level

The BEAT message is not required at the M3UA

SCTP includes functions for reachability information ERR Error message

A received message with invalid contents

NFTY Notify

Between M3UA peers

Routing Key Management Messages

Registration Request (REG REQ)

An ASP = a DPC/OPC/CIC range

Registration Response Deregistration Request Deregistration Response

M2UA Operation

MTP3/M2UA/SCTP The CA has more visibility of the SS7 network

More tightly coupled to the SG

MTP3

Routing and distribution capabilities ASPUP, ASPDN, ASPAC, ASPIA and ERR

M2UA uses similar concepts to those used by M3UA

M2UA-specific messages

DATA

ESTABLISH REQUEST

Carry an MTP2-user Protocol Data Unit To establish a link to the SG

ESTABLISH CONFIRMATION RELEASE REQUEST RELEASE CONFIRM RELEASE INDICATION

out of service

Request the SG to take a particular signaling link

The SG autonomously take a link out of service