98259163 guide to gsm and wcdma protocols

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

HUAWEI Confidential

Security Level: 内部公开

Guide to GSM and

WCDMA Protocols

ISSUE1.0

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

Upon completion of this course, you will be

able to:

Learn basic concepts in telecom

protocols

Learn general knowledge of GSM

protocols

Learn general knowledge of WCDMA

protocols


Chapter 1 Basic Concepts in Telecom Protocols

Chapter 2 Guide to GSM Protocols

Chapter 3 Guide to WCDMA Protocols


International Organizations for Standardization

ITU International Telecommunications Union Telecommunication standards

ISO International Standard Organization Common standards

ETSI European Telecommunications Standards

Institute European standards

IETF Internet Engineering Task Force Internet standards

UMTS Universal Mobile Telecommunications

System

GSM Global System for Mobile Communications GSM standards

3GPP 3rd Generation Partnership Project 3GPP standards

IEEE Institute of Electrical and Electronics

Engineers


Open System Interconnection Model

Facilitating communication

between applications

Processing data format and

performing data encryption

Establishing, maintaining and

managing a session

Setting up end-to-end connection

between hosts

Performing routing

Providing media interaction and

link management

Managing bit stream transmission

Application

Layer

Presentation

Layer

Session Layer

Transport

Layer

Network Layer

Data Link

Layer

Physical Layer 1

2

3

4

5

6

7

Bottom layer: managing

network data transmission

Upper layer: managing

host data transmission


SAP and Primitives Service access point (SAP) is a point at which the N layer provides services for N+1 layer.

Primitives are categorized into the following types:

•REQUEST primitive: used when a higher layer is requesting a service from the next lower

layer

•INDICATION primitive: used by a layer providing a service to notify the next higher layer of

activities related to the primitive type REQUEST

•RESPONSE primitive: used by a layer to acknowledge receipt, from a lower layer, of the

primitive type INDICATION

•CONFIRM primitive: used by the layer providing the requested service to confirm that the

activity has been completed

N+1 layer N+1 layer

N layer N layer

RequestConfirm ResponseIndcation

Entity of

N+1 layer

Entity of N

layer

*SAP


Protocol Stack


Protocol Structure

In general, a protocol consists of the following sections:

Introduction (scope, references and abbreviations)

Background knowledge (protocol significance and relation with

other protocols)

Detailed description (related processes, such as the objective,

operation, and result)

Related messages

Information element codes in messages

Appendix (supplementary description of key points in the

protocol)


The Way to Read Protocols

To read protocols effectively, follow the principles below:

Read a protocol from the general introduction to the detailed

description step by step, that is, from the easy to the difficult.

Read the outline first to get a general knowledge of the

contents, and then browse the whole context.

Analyze the introduction section to find out the source and

objective of the protocol.

Focus on the basic processing flow, and combine the

message (and message codes if necessary) learning with the

protocol learning.


Questions

Can you recall any international organization for standardization?

What is the OSI model?

What is the basic structure of a protocol?



Chapter 2 Guide to GSM protocols

Chapter 3 Guide to WCDMA protocols


Development of GSM

Mobile communication has gone through the development from analog communication to

digital communication. The digital mobile communication mechanism at present consists

of GSM (Pan-Europe), ADC (the US) and JDC (PDC now, Japan). Following are the

milestones in the GSM development.

In 1982, Conference of European Postal and Telecommunications Administrations

(CEPT) set up the GSM, targeting at developing the second generation of mobile

communication system.

In 1986, the eight systems proposed after numerous researches and experiments were

tested on site in Paris.

In 1987, the GSM member states achieved an agreement on adopting the technologies

such as the TDMA, RPE-LTP, and GMSK after the on-site tests and demonstrations.

In 1988, 18 European countries signed the GSM memorandum of understanding.

In 1989, the GSM recommendations took effect.

In 1991, the GSM technology and network were formally adopted in Europe. The

second generation of mobile communication came into being.

The GSM experienced the updating from V5, V6 to V7. The GPRS was introduced at

the V6 stage.

The 3GPP was established. In 1999 and 2000, the 3G 1999 and 3G 2000 were put

forward respectively.


GSM Recommendations (1) GSM network description: GSM 01.02

GSM protocol abbreviations: GSM 01.04

Cheating-proof system: GSM 01.31 and GSM 02.31

Lawful interception: GSM 01.48、GSM 02.33

GPRS: GSM 01.60, GSM 01.61, GSM 02.60, GSM 04.60, GSM 04.64 and GSM 04.65

GSM service principles: GSM 02.01

GSM bearer service: GSM 02.02

GSM telephony service: GSM 02.03

GSM supplementary service: GSM 02.04, GSM 03.11 and GSM 09.11

Mobile station: GSM 02.06，GSM 02.07，GSM 02.30，GSM 02.40 and GSM 03.22

IMEI: GSM 02.16

ODB: GSM 02.41 and GSM 03.15

Network indicator and time zone: GSM 02.42

SoLSA: GSM 02.43 and 3G 23073

PDS: GSM 02.63 and GSM 04.63、

MNP: GSM 02.66

eMLPP: GSM 02.67 and GSM 04.67

VGCS: GSM 02.68

VBS: GSM 02.69

LCS: 3G 22071

CD: GSM 02.72、GSM 04.72


GSM Recommendations (2) CAMEL: GSM 02.78, GSM 03.78 and GSM 09.78

SOR: GSM 02.79 and GSM 03.79

Calling line identification service: GSM 02.81, GSM 03.81, and GSM 04.81

Call forwarding service: GSM 02.82, GSM 03.82 and GSM 04.82

Call waiting and call holding: GSM 02.83, GSM 03.83 and GSM 04.83

MPTY: GSM 02.84、GSM 03.84 and GSM 04.84

CUG: GSM 02.85、GSM 03.85 and GSM 04.85

Aoc and CAI: GSM 02.86, GSM 02.24, GSM 03.86 and GSM 04.86

Call Barring: GSM 02.88, GSM 03.88 and GSM 04.88

Network capability and structure: 03.xx

User data recovery: GSM 03.07

User data management: GSM 03.08 and GSM 03.16

Switchover: GSM 03.09

Location update: GSM 03.12

DTMF support: GSM 03.14

Basic call processing: GSM 03.18

Network safety: GSM 02.09 and GSM 03.20

SMS: GSM 03.40 and GSM 04.11

SMSCB: GSM 03.41 and GSM 04.12

Videotex and fax: GSM 03.43, GSM 03.44, GSM 03.45 and GSM 03.46

Interaction between GSM and other networks: GSM 03.47, GSM 03.49, GSM 03.50,

GSM 03.70 and GSM 09.01


GSM Recommendations (3)

UUS: GSM 03.87 and GSM 04.87

USSD: GSM 03.90 and GSM 04.90

ECT: GSM 03.91 and GSM 04.91

CCBS: GSM 03.93 and GSM 04.93

CNAP: GSM 03.96 and GSM 04.96

MSP: GSM 03.97

MS-BS-BSS-A interface: GSM 04.01, GSM 04.02, GSM 04.03, GSM 04.04, GSM 04.05, GSM

04.07, GSM 04.08, GSM 04.10, GSM 04.11, GSM 04.12, GSM 04.13, GSM 04.14, GSM 04.18,

GSM 04.21, GSM 04.22, GSM 04.80 and GSM 08.xx

CTS: GSM 04.56 and GSM 04.57

GCC: GSM 04.68

BCC: GSM 04.69

BSS physical layer: GSM 05.xx

Full rate and half rate: GSM 06.xx

Terminal: GSM 07.xx

MAP: GSM 09.02

Interaction with PSTN/ISUP: GSM 09.03, GSM 09.04, GSM 09.05, GSM 09.06, GSM 09.07 and

09.12

E interface BSSAP: GSM 09.08

BSS-NSS information mapping: GSM 09.10

SIM-ME interface: GSM 09.91

FIGS: GSM 02.31


GSM System Structure and Interfaces

The GSM system structure

is defined in the 03.02

recommendation.

GSM supports the following

interfaces in the CS domain

of the core network:

A: BSC<->MSC

B: MSC<->VLR

C: MSC<-HLR

D: VLR<->HLR

E: MSC<->MSC

F: MSC<->EIR

G: VLR<->VLR

H: HLR<->AuC


A interface Protocol Stack

Radio resource management (RR)

Mobility management (MM)

Call control (CC)

Message transfer part (MTP)

Signalling connection control part (SCCP)

BSS operation and maintenance application part (BSSOMAP)

Base station subsystem application part (BSSAP)

BSS management application part (BSSMAP)

Direct transfer application part (DTAP)

Layer3-CC

Layer3-MM

Layer3-RR

Data link layer

Physical layer

SCCP ITU-T Q712/713/714

MTP3 ITU-T Q704

MTP2 ITU-T Q703

MTP1 ITU-T Q702

ITU-T G711

DTAP GSM 04.08 08.06

BSSMAP GSM 08.06 08.08BSSAP

BSS

OMA

P

DTAP

BSSMAP

SCCP

MTP3

MTP2

MTP1

PCM-A


Questions

Can you recall any main recommendation of GSM?

Can you recall any main interface of GSM?



Chapter 2 Guide to GSM protocols

Chapter 3 Guide to WCDMA Protocol


3GPP Specification Description

Same to the naming convention of GSM specifications, 3GPP

specifications are named in the format of 2X.XXX. The 21-series

requirements specifications put forward requirements for certain

specifications to be standardized. After the specifications are

standardized, the 21-series requirements specifications are not

used or used to describe the system performance.

Among them, the 21.101 specifications are important references

to query the specifications from the 21 series to the 35 series.

Specifications recommended:

21.101 3rd Generation mobile system Release 1999

Specifications

21.102 3rd Generation mobile system Release 4 Specifications

21.905 3G Vocabulary


Mobile Service Specifications

• Telecom service (3GPP TS 22.003)

TS11 Telephony

TS12 Emergency Calls

TS21 Short message MT/PP 3GPP TS 23.040

TS22 Short message MO/PP 3GPP TS 23.040

TS23 Cell Broadcast Service 3GPP TS 23.041

TS61 Alternate speech and facsimile group 3 ITU-T T.30

TS62 Automatic Facsimile group 3 ITU-T T.30

TS91 Voice Group Call Service 3GPP TS42.068

TS92 Voice Broadcast Service 3GPP TS42.069

• Bearer service (3GPP TS 22.002/29.007)

BS2X Asynchronous General Bearer Service

BS3X Synchronous General Bearer Service


Mobile Service Specifications • Supplementary service (3GPP TS 22.003)

22.004 General on supplementary services

23.011 Technical realization of supplementary services

24.010 Mobile radio interface layer 3-supplementary services specification-

general aspects

24.080 Mobile radio layer 3 supplementary service specification; Formats

and coding

29.011 Signaling interworking for supplementary services


Mobility Management Specifications

23.007 Restoration procedures

23.016 Subscriber data management

23.012 Location management procedures

24.008 Mobile radio interface layer 3 specification

29.002 Mobile application part (MAP) specification

23.122 Non-Access-Stratum functions related to mobile station (MS) in idle mode

25.304 UE procedures in idle mode and procedures for cell reselection in

connected mode


ISUP Recommendations (1)

Entry Source Description

ISDN User Part functional

description Q.761 This recommendation describes the ISDN user part function.

ISDN user part general

functions of messages and

signals

Q.762

This recommendation describes the messages, parameters and

the signaling information contained within parameters used by

the ISDN user part protocol, and their functions.

ISDN user part formats and

codes Q.763

This recommendation specifies the formats and codes of the

ISDN user part messages and parameters required to support

basic bearer services and supplementary services.

ISDN user part signaling

procedures Q.764

This recommendation describes the ISDN user part signaling

procedures of the set-up and clear down of national and

international ISDN connections used for "ISUP'97". Actions

common for all types of exchanges are described only once.

Different or additional actions required in an exchange are

specified in a separate sub clause applicable to that type of

exchange. The procedures specified in clause 2 relate to basic

calls (for example, calls not involving supplementary services

and IN).

performance objectives Q.766

Signaling availability

Signaling dependability

Signaling delay

Signaling system limitations


ISUP Recommendations (2)


ISDN supplementary services Q.730

This recommendation provides general information for

ISDN supplementary services. It describes generic

procedures, network specific facilities and end-to-end

signaling methods. It also contains the generic format for

the supplementary service descriptions contained in

Recommendations Q.731 to Q.737, to be used in

conjunction with the ISDN User Part (ISUP) defined in

Recommendations Q.761 to Q.764 and Recommendation

Q.767 "Application of the ISDN user part of CCITT

Signaling System No. 7 for international ISDN

connections". A listing of the currently defined

supplementary services is included as well.

Numbering plan

CCITT

Recommend

ation E.164

It is assumed that the ISDN follows the international

numbering plan defined for the ISDN and provides a basic

circuit switched service between ISDN terminals or

between ISDN terminals and terminals being connected to

the existing international telephone network.

Test specification Q.784-

Q.785

ISUP basic call test specification.

ISUP protocol test specification for supplementary

services


TUP Recommendations (1)


TUP function description Q.721 This recommendation describes the TUP function.

TUP general functions of

messages and signals Q.722

This recommendation describes the general function of telephone

signaling messages and the telephone signals and other

information components contained in those messages.

Formats and codes Q.723

Basic format characteristics

Label

Telephone signal message formats and codes




Signaling procedures

Q.724

Normal call set-up

Dual seizure with both-way operation

Automatic repeat attempt

Speed of switching and signal transfer in international exchanges

Blocking and unblocking of circuits and circuit groups

Release of international connections and associated equipment

Continuity-check for 4-wire speech circuits

Continuity-check for 2-wire speech circuits

Interruption control for multiplex systems

Supplementary services

Echo suppressor control

Congestion control

Telephone User Part outage

State transition diagrams




Signaling Performance

Q.725

Signaling performance in the telephone application

Test specification

Q.783

This recommendation contains a set of detailed tests for the

Signaling system No. 7 telephony user part (TUP).


UMTS System Structure and Interfaces

BSS

BSC

RNS

RNC

CN

Node B Node B

IuPS

Iur

Iub

USIM

ME

MS

Cu

Uu

MSC server

SGSN Gs

GGSN GMSC

server

Gn HLR

Gr

Gc C

D

Nc

H

EIR

F Gf

Gi PSTN

IuCS

VLR B

Gp

VLR

G

BTS BTS

Um

RNC

Abis

SIM

SIM-ME i/f or

MSC server

B

PSTN

cell

CS-MGW CS-MGW

CS-

MGW

AuC

Nb

Mc Mc

Nb

PSTN PSTN

Nc

Mc

Mh

A Gb

E

The UMTS system structure is

defined in the 23.002

recommendation.

UMTS supports the following

interfaces in the CS domain of

the core network:

A: BSC<->MSC

B: MSC<->VLR

C: MSC<-HLR

D: VLR<->HLR

E: MSC<->MSC

F: MSC<->EIR

G: VLR<->VLR

H: HLR<->AuC

IuCS: MSC<->RNC

Mc: MSC<->MGW

Nc: MSC<->MSC

Nb: MGW<->MGW

Gs: VLR<-SGSN


IU-CS Interface Protocol Stacks

Q.2150.1

Q.2630.2

RANAP Iu UP Protocol Layer

Transport Network

Layer

Physical Layer

Transport User

Network Plane

Control Plane User Plane

Transport User

Network Plane

Transport Network Control Plane

Radio Network

Layer

ATM

SSCOP

AAL5

SSCOP

SSCF-NNI

AAL2 AAL5

MTP3b MTP3b

SCCP

SSCF-NNI


Description of IU-CS Interface Protocol Stack

Based on the vertical plane structure of the Iu-CS protocol, the Iu-CS interface protocol can be

described in the following aspects:

• Control plane: The RANAP (TS25.413) and signaling bearer (TS25.412) recommendations are

used on this plane.

• User plane: The IuUP (TS25.415) and data bearer (TS25.414) recommendations are used on

this plane.

• Transport network control plane: The ALCAP (ITU-T Q.2630.1 and ITU-T Q.2630.2) and

signalling bearer (TS25.414) recommendations are used on this plane.

List of recommendations:

23.930 Iu principles

23.110 UMTS access layer services and functions

25.410 UTRAN Iu interface: Introduction and principles

25.411 UTRAN Iu interface: UTRAN Iu layer interface 1

25.412 UTRAN Iu interface: Signaling transport

25.413 UTRAN Iu interface: RANAP signaling

25.414 UTRAN Iu interface: Data transport and transport signaling

25.415 UTRAN Iu interface: User plane recommendation

25.419 UTRAN Iu interface: Service area broadcast protocol (SABP)

ITU-T Recommendation Q.2210 MTP3-B


Structure of RANAP Protocol Stack

The structure of RANAP protocol stack is based on the following signaling bearer systems:

• ATM-based broadband SS7 (SAAL-NNI, MTP3b and SCCP)

• IP-based signaling transmission system (IP, SCTP and M3UA)

The RANAP protocol stack consists of the following parts:

• Radio access network application part (RANAP) (TS25.413) on radio network layer

• Signaling bearer part on transport network layer

RNC

(b)

Iu - CS RNC

(a) ATM-based

MSC Server (MSOFTX3000)

Iu - CS

RANAP

SCCP

M3UA

SCTP

IP

RANAP

SCCP

MTP3B

STC

SAAL

AAL5

ATM

PL

RANAP

SCCP

MTP3B

STC

SAAL

AAL5

ATM

PL


MAC

RANAP

SCCP

M3UA

SCTP

IP

MAC

RNC

(b) IP-based

Iu - CS RNC

(a)


Iu - CS

RANAP

SCCP

M3UA

SCTP

IP

RANAP

SCCP

MTP3B

STC

SAAL

AAL5

ATM

PL

RANAP

SCCP

MTP3B

STC

SAAL

AAL5

ATM

PL


MAC

RANAP

SCCP

M3UA

SCTP

IP

MAC


Structure of MAP Protocol Stack

SCCP ITU-T Q712/713/714

MTP3 ITU-T Q704

MTP2 ITU-T Q703

MTP1 ITU-T Q702

ITU-T G711

TCAP ITU-T Q771/772/773TCAP

SCCP

MTP3

MTP2

MTP1

PCM-A

MAP GSM 29.002

The mobile application part (MAP) protocol defines how messages are exchanged between CDMA

network entities for the purpose of realizing the MS roaming function. The involved network entities

include the MSC Server, VLR, SGSN, HLR, SMC and GMLC.

In the UMTS network, the C, D, E, G, Lg and L interfaces can all transfer MAP messages.

The MAP protocol at the C and D interfaces implements signaling interaction of the following services:

• Location registration

• Authentication

• Subscriber management

• Fault recovery (user data recovery during PRN)

• Call handling (routing information and roaming number retrieval)

• Supplementary service

• PSI (provide subscriber information)


Structure of E Interface Protocol Stack

When related mobile signaling is transferred on the E interface, the MAP protocol

stack is adopted. The MAP protocol implements signaling interaction of the

following services:

• Inter-office handover

• SMS transfer

When traffic data is transferred on the E interface, the TUP/ISUP protocol

stack is adopted.

MTP3 ITU-T Q704

MTP2 ITU-T Q703

MTP1 ITU-T Q702

ITU-T G711

ISUP Q.76XISUP

MTP3

MTP2

MTP1

PCM-A

TUP TUP Q.72X


E Interface Protocol Stack

MS/BSS-A

MSC-A MSC-B

MAP-Prep-Handover req. MAP-Allocate-Handover-Number req.

A-HO-REQUEST

A-HO-REQUIRED

BSS-B/MS

VLR-B

A-HO-REQUEST-ACK

MAP-Send-Handover-Report req. MAP-Prep-Handover resp.

IAM

MAP-Send-Handover-Report resp. (1)

ACM A-HO-COMMAND

A-HO-DETECT

A-HO-COMPLETE

MAP-Process-Access-Sig req. MAP-Send-End-Signal req. A-CLR-CMD/COM

ANSWER

RELEASE End of call

MAP-Send-End-Signal resp.

NOTE 1: Can be sent at any time after the reception of IAM


F Interface Protocol Stack

The F interface protocol stack also belongs to the MAP protocol stack.

The F interface protocol stack implements the signaling interaction of the CheckImei

service to check the international mobile station equipment identity (IMEI).

SCCP ITU-T Q712/713/714

MTP3 ITU-T Q704

MTP2 ITU-T Q703

MTP1 ITU-T Q702

ITU-T G711


SCCP

MTP3

MTP2

MTP1

PCM-A

MAP GSM 29.002


Mc Interface Protocol Stack

H.248

SCTP

IP

MAC

L1

(G)MSC Server Mc

MGW

(a)

Mc MGW

(b) ATM-based

(G)MSC Server

H.248 H.248

SCTP

IP

MAC

L1

STC

SAAL

AAL5

MTP3B

ATM

PL

H.248

STC

SAAL

AAL5

MTP3B

ATM

PL

H.248

SCTP

IP

MAC

L1

(G)MSC Server Mc

MGW Mc

MGW

(b)

(G)MSC Server

H.248 H.248

SCTP

IP

MAC

L1

STC

SAAL

AAL5

MTP3B

ATM

PL

H.248

STC

SAAL

AAL5

MTP3B

ATM

PL

IP-based


Nc Interface Protocol Stack

BICC

SCTP

IP

MAC

L1

(G)MSC Server Nc

MSC Server

(c) SCTP/IP-based

Nc MSC Server

(d) ATM-based

(G)MSC Server

BICC BICC

SCTP

IP

MAC

L1

STC

SAAL

AAL5

MTP3B

ATM

PL

BICC

STC

SAAL

AAL5

MTP3B

ATM

PL

BICC

MTP3

MTP2

MTP1

(G)MSC Server Nc

MSC Server

(a) TDM-based

(G)MSC Server Nc

MSC Server

(b) M3UA-based

BICC

L1

BICC

M3UA

IP

MAC

L1

BICC

MTP3

MTP2

MTP1

SCTP

M3UA

IP

MAC

SCTP

BICC

SCTP

IP

MAC

L1

(G)MSC Server Nc

MSC Server

(c)

Nc MSC Server

(d)

(G)MSC Server

BICC BICC

SCTP

IP

MAC

L1

STC

SAAL

AAL5

MTP3B

ATM

PL

BICC

STC

SAAL

AAL5

MTP3B

ATM

PL

BICC

MTP3

MTP2

MTP1

BICC

MTP3

MTP2

MTP1

(G)MSC Server Nc

MSC Server

(a)

(G)MSC Server Nc

MSC Server

(b)

BICC

L1

BICC

M3UA

IP

MAC

L1

BICC

MTP3

MTP2

MTP1

BICC

MTP3

MTP2

MTP1

SCTP

M3UA

IP

MAC

SCTP


BICC Protocol

The bearer independent call control protocol (BICC) is a bearer-unspecific call control

protocol used in the backbone network. It is used in data networks including the ATM

network and IP network to bear the PSTN/ISDN service comprehensively. Therefore,

BICC is considered as an important tool to facilitate the change from the traditional

telecommunication network to the multi-service integration platform.

The control part and bearer part are separated in BICC. That is, BICC does not directly

control the media resources (ATM and IP), but controls them through standard bearer

control protocol (H.248 protocol).

BICC is developed based on the narrowband ISUP protocol. It can be considered as a

version that comes out of narrowband ISUP protocol with the detailed circuit control

part deleted. However, it can never be compatible with the ISUP protocol.

Theoretically, BICC can be used in all types of signal transport protocol stack to

provide bearer-unspecific call control.

The BICC protocol includes the ITU-T recommendations Q.1902, Q.2150 and Q.765.


BICC Protocols

The bearer-unspecific BICC protocol proposed by the ITU-T has three different versions.

They are CS1, CS2 and CS3.

Protocol model, coding and decoding, and call flow

Q.1902.1: BICC CS2 Function description (functionality and protocol model)

Q.1902.2: BICC CS2 Common functions of messages and parameters

Q.1902.3: BICC CS2 Format and coding/decoding of messages and parameters

Q.1902.4: BICC CS2 Call flow and supplementary abnormity processing flow

APM

Q.1950: Call bearer control protocol

Q.1970: IP bearer control protocol

Q.1990: BICC bear Control Tunnel Protocol

Q.765: Application transport mechanism

Q.765.5: APM coding type

Signaling bearer

Q.2150.0: Common signaling transport service

Q.2150.1: STC on MTP3 and MTP3b

Q.2150.2: STC on SSCOP and SSCOPMCE

Q.2150.3: STC on SCTP


Nb Interface Protocol Stack

MGWMGW

NbIu

Transport

Layer

SRNC

Radio

Protocols

Iu UP Iu UPNb

UP

Nb

UP

Nb UP

AAL-2 SAR SSCS (I.366.1)

AAL2 (I.363.2)

ATM

Nb UP

RTP

UDP

IPv4 or IPv6


CAP Interface Protocol Stack

SCCP ITU-T Q712/713/714

MTP3 ITU-T Q704

MTP2 ITU-T Q703

MTP1 ITU-T Q702

ITU-T G711


SCCP

MTP3

MTP2

MTP1

PCM-A

CAP GSM 23.078 29.078

The CAMEL application part (CAP) is developed based on the INAP protocol used in the wired

intelligent network. CAP supports the CAMEL service by enabling the signaling interaction between

functional entities (GSM SSF, GSM SRF and GSM SCF) of the wireless intelligent network (WIN).

CAP is part of the SS7, belonging to the user part of the transaction capability application part

(TCAP). It uses the structured/unstructured conversation capability provided by the TCAP to realize

the signaling interaction between different entities.

Recommendations:

• ETSI /3GPP CAMEL Phase1, Phase2, Phase 3 and Phase 4

• TS 23.078 (SSF/SCF)

• TS 23.018(Call flow)

• TS 29.078 (CAP)


Questions

Can you recall any main interface in WCDMA?

Can you explain the relation between GSM and WCDMA?

谢谢

www.huawei.com

98259163 guide to gsm and wcdma protocols

Documents