R4 Network and Key Technology

（内部资料 )

ASB/MSD/BU1/Product Management2004/12

UMTS R4 network and key technology

All rights reserved © 2004, Alcatel Shanghai Bell

（内部资料）

Outline

• NGN architecture• NGN concept• NGN in mobile world

• UMTS R4 architecture• Network architecture and logical interface• Protocol stack• Operator benefits

• UMTS R4 key technology• TrFO vs TFO• Bearer control signaling • Nc and Mc interface: BICC and H.248• Signaling transport


（内部资料）

NGN concept － from standard point of view

ITU-T (SG 13) has finally given the following definition of an NGN (Geneva, 3-12 Feb 2004):

“A Next Generation Network (NGN) is a packet-based network able to provide services including Telecommunication Services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies. It offers unrestricted access by users to different service providers. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users.”

NGN : Next Generation NetworkNGN : Next Generation Network


（内部资料）

NGN concept － list of NGN Characteristics

The NGN can be defined by the following key characteristics: Packet-based transfer Separation of control functions among bearer capabilities, call/session, and

application/ service Decoupling of service provision from network, and provision of open interfaces Support for a wide range of services, applications and mechanisms based on service

building blocks (including real time/ streaming/ non-real time services and multi-media)

Broadband capabilities with end-to-end QoS and transparency Interworking with legacy networks via open interfaces Generalized mobility Converged services between Fixed/Mobile

…


（内部资料）

NGN concept － brief view> Layer Separation architecture. Control and transport split

clearly.

> With same Packet Transport for voice and data.

UMTS R4 is an example of this concept:

Service

Control+

Transport

Service

Control

Transport

Access

SwitchISUP

MAP for mobile

Subscriber Data base

E1/SDH

Application Server

Subscriber Data base

Application Server

Access

H.248

ATM or IP

transport

Call Server Call ServerBICC or SIP-T

MAP for mobile

MGW MGW

Switch

non NGN NGN

H.248

Q.2630 (ATM)IPBCP (IP)


（内部资料）

NGN concept － from application point of view

NGN is not only about call control and user-plane split. NGN is two folds:

One is NGN for narrowband service / access The other one is NGN for Broadband service /access

NB-NGN: for fixed : class 4 (off-load) or class 5 replacement for mobile : 3GPP R4 architecture

BB-NGN: SIP based architecture (may also applies to H.323 protocol) for fixed : SIP signaling (or H.323) for mobile : standardized by 3GPP - R5 and R6 IMS architectures aims at providing enhanced multimedia services

UMTS R4 is narrowband NGN in mobile network CS domain.


（内部资料）

Current mobile network topology － Not NGN minded

R99: is not NGN architecture Largely derived from GSM TDM transport Features content functionally frozen 12/2000

HLR

Node B

RNC

Packet Data

NetworkSGSN

GGSN

MSC MSC

GPRSnetwork

PSTN andFPLMN

TDM Network

BTSBSC

2G RAN3G RAN


（内部资料）

NGN in mobile world – R4

UMTS R4: belongs to "NB-NGN" family NGN in Cs Domain with Separation of Control and User layers

Introduction of MSC Server & MGW Introduction of ATM and IP transport instead of TDM

BTSBSC

HLR

Packet Data

NetworkSGSN

GGSN

MGW

MSC Server

MSC Server

BICC

MGW

H.248 H.248

IP or ATMnetwork

PSTN andFPLMN

Node B

RNC

2G RAN3G RAN

2G CS can use R4 architecture also.

Therefore, 2G CS can get benefits from it also, except for some special functions of R4, eg. TrFO…


（内部资料）

NGN in mobile world – the Ultimate Target R5&R6: Full NGN with IP Multimedia Sub-system (IMS)

Circuit SwitchNetwork still

present HLR/HSS

SGSN GGSN

Packet

DataNetwork

Packet

DataNetwork

IP or ATMnetwork

MGW

SGW

IMS

Node B

RNC

MRF

MGCF

CSCF

BTSBSC

2G RAN

3G RAN

PSTN andFPLMN


（内部资料）

UMTS R5 : belongs to BB-NGN family : Frozen by 3GPP in June 2003 Introduction of MM Call Server (CSCF) and "SIP" Session Control Protocol Introduction of enhanced MM services External interfaces with Application Servers (AS) through SIP, CAMEL, OSA Security : authentication (AKA based) and cyphering IPSEC SIP Compression

UMTS R6 : belongs to BB-NGN family (like R5) : will be frozen not before mid 2004, likely end 2004 PSTN interworking Interworking with external IPv4 IMS "Ut" interface : direct interaction between user and AS Optimisation of Radio resources

Header compression (ROHC) RTCP/RTP handling over radio

NGN in mobile world – the Ultimate Target R5&R6: Full NGN with IP Multimedia Sub-system (IMS)

Introduction of VoIP on radio

New multimedia services

Success of SIP based services on fixed BB access

Fixe-Mobile convergence through IMS

Mobility with other wireless access as WLAN,…


（内部资料）

> It focus on Opex reduction in CS domain:

• Better flexibility• Long distance by-pass• Transport saving• Network simplification• Better Time to market

> It increase network reliability with standby media gateway which can handle traffic in case of failure

NGN in mobile world － operator benefits from R4 architecture

> It focus also on CAPEX reductionin CS domain :

• Technology improvements• Network simplification :

simplify transit network, simplify signalling network …

• No need of transcoder for 3G calls

> Convergence of CS and PS domain on the same data backbone

> Voice quality improvement

2G CS can use R4 architecture also. Therefore, 2G CS can get benefits from it also, except for some special

functions of R4, eg. TrFO…


（内部资料）

Outline





（内部资料）

UMTS R4 concept － brief view

> Layer separation architecture.

H248

Iu -CS

CONTROL

SERVICE

H248

BICC

SCP/ SCE

PSTN

MAP INAP/CAP

MeXe SAT PORTAL

IP/ATM

A

ISUP

V-MSC Server

MGW

BSS UTRAN

G-MSC Server

MGW

HLR

TRANSPORT

ACCESS


（内部资料）

UMTS R4 logical interface

User Plane Signaling Plane

Circuit Domain

UTRAN

BSS Nc: BICC

Mc: H248

Relay of RANAP BSSMAP

BSSMAP

RANAP ALCAP

G711/AAL2/ATM G711/RTP/IP AMR/AAL2/ATM AMR/ RTP/IP

G711/TDM or G711/AAL2/

Relay of ISUP or BICC

MSC Call

Server

MGW

BSC

RNC

MSC Call

Server

MGW

PSTN Q2630 for AAL2 IPBCP for IP

Mc: H248

Nb


（内部资料）

Functional split

VLR

Call Control

SS7 Signaling

Bearer Setup

Bearer Path Management

Mobility Management

Echo cancellation

Call Processing

FCAPS

Call Features

IP

MEGACO/H.248MEGACO/H.248

MGC

Context Management

Conference BridgeCodec

Silence Suppression

Tone and announcement

Lawful interception


（内部资料）

In narrowband NGN, the 2 important protocoles are:

BICC (MSC to MSC) H.248 (MSC to MGW)

In broadband NGN, the important protocol is:

SIP (MS to CSCF)

TDM

ATM

IP

DTAP

BSSAP

RANAP

MGW

TDM

ATM

IP

H.248 Signalling Relay

MAP 1, 2 ,3

CAP 1, 2, 3, 4

INCS1, 2

ISUP

National ISUP

BICC CS1, 2

SIP (IMS IWF)

MSC Server

NNI

Application and services

UNI

Bearer control

Network architecture: protocol interface


（内部资料）

Network architecture: Signalling

V_MSCserver

MGW

G_MSCserver

MGW

BSC

RNCNb

Nc

Iu_cs

A

Mc Mc

HLRHLR

AUcAUc

FD C

H

gsmSCFgsmSCF

gsmSRFgsmSRF

TRANSPORT

CONTROL

APPLICATIONS &SERVICES

V_MSC G_MSC

E/G

N_ISUP N_ISUPCAP/IN

CAP/IN

MAP MAP

MAPBICC

H248

ATM : Q2630.2 (AAL2) Q2931 (ATM SVC)

IP : IPBCP/IPBCTPALCAP (transport)

RANAP (Radio control)

BSSAP

MAP

H248

MAP

IN_CSx

SIGrelay

TDM/SDH

N_ISUP (1)

ATM PLMN

BICC(1)

ATM/SDH

ISDN/PSTN/ NB PLMN

(1) : In case of associated signalling ( same physical transport as user plane) :- signalling gateway function needed in MGW

SIGrelay

J

To user plane :- TDMGMLCGMLCSMSCSMSC

EIREIR

MAPMAP

GsBSSAP+

Lg


（内部资料）

Protocol stack

> Nc: > Mc: 4 options

H.248MTP3bSSCF SSCOPAAL5 ATM

H.248

M3UA

SCTP

IP

H.248

SCTP

IP

H.248

UDP

IP


（内部资料）

Protocol stack

Signaling: to RNC RNC <-> MGW: IuSignaling: to BSC A interface User Plane : G711/ TDMSignaling: to BSC A interface Control Plane : BSSMAP/ TDMSignaling: backbone Proprietary interface User Plane : VoATMSignaling: backbone Proprietary interface User Plane : VoIPSignaling: backbone Nb interface User Plane : ATM. AMR/Iu/AAL2 I366.1/ATMSignaling: backbone Nb interface User Plane : IP. AMR/Iu/RTP/UDP/IPSignaling: backbone Nb interface User Plane : ATM. G711/Iu/AAL2 I366.1/ATMSignaling: backbone Nb interface User Plane : IP. G711/Iu/RTP/UDP/IPSignaling: backbone Nb Control Plane: Q2630.2/MTP3B/SCCF/ SSCOP NNI/AAL5/ATMSignaling: backbone Nb interface Control Plane: RTCP/UDP/IP


（内部资料）

Protocol stack

Signaling interface: MAP C: MAP/TCAP/SCCP/MTP3/MTP2Signaling interface: MAP D: MAP/TCAP/SCCP/MTP3/MTP2Signaling interface: MAP E: MAP/TCAP/SCCP/MTP3/MTP2Signaling interface: MAP G: MAP/TCAP/SCCP/MTP3/MTP2Signaling interface: MAP C: MAP/TCAP/SCCP/M3UA/SCTP/IPSignaling interface: MAP D: MAP/TCAP/SCCP/M3UA/SCTP/IPSignaling interface: MAP E: MAP/TCAP/SCCP/M3UA/SCTP/IPSignaling interface: MAP G: MAP/TCAP/SCCP/M3UA/SCTP/IPSignaling interface: IN IN-CS1/TCAP/SCCP/MTP3/MTP2 Signaling interface: IN IN-CS1/TCAP/SCCP/M3UA/SCTP/IP Signaling interface: IN CAP/TCAP/SCCP/MTP3/MTP2 Signaling interface: IN CAP/TCAP/SCCP/M3UA/SCTP/IP


（内部资料）

R4 Major objectives

> Evolution towards a NGN Network• Separation of control and transport parts• Migration towards an ATM or IP CS backbone• Common backbone with the PS domain• First step towards a full IP network (R5)

> Resource optimisation :• Transcoder function : suppression for 3G/3G calls• Transport resource : compressed voice in the CS Core

> Voice quality improvement :• Tandem free operation (TFO)• Transcoder free operation (TrFO)


（内部资料）

OPEX and CAPEX reductionSeparation of control and transport layer

> Independent Call server & MGW locations• Optimisation of local traffic transport

> Operation and dimensioning simplification • Independent dimensioning of Call Server & MGW• Adding a new MGW on an existing MSC server with no impact on the

network

Transport saving Network

simplification

MSC

RNCBSC RNC

BSC

MSC Server

MGW

Site 1

RNCBSC

PSTNPLMN

RNCBSC

RNCBSC

Site 1

RNCBSC

Site 2

PSTNPLMN

Transportnetwork

MGW

Site 3

RNCBSC

Site 2

MGW RNCBSC

Site 3

Local call inter BSC Local call intra BSC NGN Local call inter BSCNGN Local call intra BSC

Operator benefits from R4 architecture


（内部资料）

OPEX and CAPEX reduction

Simplified operation and better time to market > Complex in integrated MSC and MSC server

> Very simple operation in Media Gateway

> By minimising MSC server in few locations• Less operations (backup, upgrades, network design…)• Faster network upgrades

Better time to market

Network simplification

Transportnetwork

MGW

MGW

MGW

MSC Server

MSC Server

MGWMGWMGW

MGW

Transit MSC

Access MSC



（内部资料）


Simplification of the transit switch layer

> No extension in case of traffic growth

> No more operation and maintenance

> Less unused transport resources

Transportnetwork

Node B

/BTS

Node B

/BTS

Node B

/BTS

Node B

/BTS

Node B

/BTS

Node B

/BTS

MSC MSCMSC

Transit MSC

RNCBSC

RNCBSC

RNCBSC

RNCBSC

Node B/BTS

MGW

RNC

BSC

RNC

BSC

RNC

BSC

RNC

BSC

MGWMGW

MSC Server MSC Server

Long distance by-pass

Transport saving Network

simplification



（内部资料）

> With SS7 over IP, less need for dedicated signalling network

• simplification of transport network• removal of STP elements

SS7 Network

Transportnetwork

MGW

MGW

MGW

SCP

HLR

HLR

MSC

Server

MSC Server

#7 over NB (TDM)#7 over IP (Sigtran)

Transportnetwork

MGWMGW

MGW

HLR

MSC ServerHL

RMSC Server

SCP

Network simplification



（内部资料）

> AMR over packet is 2 to 4 times more efficient in term of bandwidth compared to voice over TDM

> 2G bandwidth efficiency can be improved by using silence suppression and/or voice compression techniques

TDM (reference)

kb/s per AMR voice channel

kb/s per 64kb data or G711 ch.

ATM AAL2 POS IP V4 POS IP V6 GE IP V4 GE IP V6 IP V4 over ATM AAL5

IP V6 over ATM AAL5

64 15 34 44 49 59 51 51

64 85 121 141 151 171 153 204

transport type

kb/s per channel


Bandwidth efficiency



（内部资料）

Existing Networks: 108 MSCs, 22 Transit switches, 36 HLRs on 37 sites HLR

1 MSC 150 Ksubs = 6 racks

Transit switches

Exampled network: 8 MSCs, 29 MGWs, 6 HLRs on 18 sites

If MSC server2MSubs in one rack

HLR

If MGW500KSubsin one rack

Operator benefits from R4 architecture － example


（内部资料）

R4 architecture － Circuit Switched NGN : a optimum solution to smoothly evolve toward target network

Target network :an all IP network

> Voice services over the packet is about 20-25% less efficient in RAN

> Voice services hand-over between Circuit switched and Packet Switched is technically impossible

> IMS performance lower than TDM

> Alternative solutions to fast introduction of multimedia services are possible

> Circuit Switched NGN is a good solution for real time services to:

• reduce operating expenses and optimise infrastructure investments

• Prepare networks for coming evolution

• Minimise technical risks

But Today

Circuit SwitchNetwork still

present HLR/HSS

SGSN GGSN

PacketData

Network

PacketData

Network

IP or ATMnetwork

MGW

SGW

IMS

Node B

RNC

MRF

MGCF

CSCF

BTSBSC

2G RAN

3G RAN

PSTN andFPLMN


（内部资料）

Outline





（内部资料）

TrFO vs TFO

> TFO : Tandem Free Operation

• Objectives : – Improvement of voice

quality for calls between 2 mobile subscribers.

– but no resource optimisation as transcoder functions are always present in the path

> TrFO : Transcoder Free Operation• Objectives

– Improvement of voice quality for calls between 2 mobile subscribers

– Resources optimisation in the core Network by skipping the transcoder functions.

– Bandwidth optimisation– Delay optimisation


（内部资料）

TrFO principles

• Codec negotiation at call set-up• Insert TC on demand• Framing protocol initialisation :

– RFCI storage/RFCI value correction

• TrFO break– TrFO connection must be interrupted for :

– Hand-over – Insertion of announcements and tones– Insertion of DTMF– Invocation of supplementary services (Explicit call transfer, Call

waiting , call hold , call forwarding , ....)– Lawful interception– Conference

– These functions could lead to insert a TC function in the path and possibly to re-negotiate the codec

• TFO/TrFO :– Cohabitation 2G/3G– Hand-over/relocation


（内部资料）

TrFO Benefits : resource optimisation/voice quality improvement

MSC-OTDM backbone

MSC-T

RNC_ORNC-T

TC TC

AMR G711 (64 Kbits/s) AMR

R99

MSC-OCS backbone

MSC-T

RNC_ORNC-T

AMR (15 Kbits/s with ATM transport)

R4 NGN

: AAL2 switching or IP routing


（内部资料）

AMR G711 (64 K bits/s per channel) AMR

R99

AMR (down to 15 K bits/s with ATM AAL2 per channel)

NGN

OPEX and CAPEX reductionTRFO function (3G)

> End to End AMR voice transport (3G/3G Call)

Node B

RNC

TCRNC

MSC server

MGW

MSC server

MGW

TC RNC

RNC

Bandwidth optimisationTranscoder savingVoice quality improvement

PacketNetwork

TDM Network


（内部资料）

> Transcoder located on the edge of the network for 3G to PSTN or 3G to 2G PLMN Voice Call

G711 (64 K bits/s per channel)

R99

AMR (down to 15 K bits/s with ATM AAL2 per channel)

NGN

PSTN/2G PLMN

TC

PSTN/2G PLMN

TC

G711 (64 K bits/s per ch.)

OPEX and CAPEX reductionTranscoder at the edge (3G)

AMR

TCRNC

Node B

RNC

MSC server

MGW

MSC server

MGW

Node B

TC

Bandwidth optimisation

PacketNetwork

TDM Network


（内部资料）

MSC

MSC

MSC

MSC

3G

3G

3G

2G

3G

2G

PSTN

Transcoding function

Transport adaptation 2G

2G

PSTNCS Core backbone

AAL2 switching or IP routing

AMR

G711 (with or without silence suppression) or other codec (i.e ADPCM32)

G711

TrFO Benefits : resource optimisation/voice quality improvement


（内部资料）

TrFO: break equipment

MSC-OCS

backbone

Iu user protocol

TrFO and UMTS : Establishment

Compressed

Iu user protocol Iu framing protocol

TrFO and UMTS : Established

MSC-T

: TrFO break equipment

RNC_ORNC-T

MSC-OCS

backbone

MSC-T

RNC_ORNC-T

: AAL2 switching or IP routing


（内部资料）

TrFO functions (examples)

RNC

MGW

> Hand-over

RNC

MGWRNC

TBE

MGWRNC

> DTMF

RNC

MGW

RNC

MGWTC

AAL2switch

AAL2switc

h

AAL2switc

h

AAL2switc

h

AAL2switc

h

> Announcement and tones

RNC

MGW

RNC

MGW

TC

AAL2switc

h

AAL2switc

h

A

D


（内部资料）

Transcoding :ATM CS Core

3G UE PSTN or PLMN(SCN)

2G MS PSTN orPLMN(SCN)

AMR/Iu/AAL2(I366.1)

G711/Iu/AAL2(I366.1)VoATM*trunking

G711/TDM

AAL2 switch

G711/TDM

3G UE 2G MSAMR/Iu/AAL2(I366.1)

G711/TDM

3G UE 3G UE.AMR/Iu/AAL2(I366.1)AAL2 switch

AAL2 switch

2G MS 2G MSG711/Iu/AAL2(I366.1)

VoATM*trunking

G711/TDMG711/TDM

G711/TDM

AMR/Iu/AAL2/I366.1AMR/Iu /AAL2(I366.1)

AMR/Iu /AAL2(I366.1)

AMR/Iu/AAL2(I366.1)

VoATM*Trunking

+EC

TC+EC

AAL2 switch

TC

VoATM*trunking

When EC (echo cancellation) function is mentioned, it only applies to interfaces towards the PSTN.


（内部资料）

Transcoding : IP CS Core

3G UE PSTN or PLMN(SCN)

2G MS PSTN orPLMN(SCN)

AMR/Iu/RTP/UDP/IP)

G711/Iu /RTP/UDP/IP)VoIP*trunking

G711/TDM

ATM <-> IP

G711/TDM

3G UE 2G MSAMR/Iu//RTP/UDP/IP)

G711/TDM

3G UE 3G UE.AMR/Iu/RTP/UDP/IPATM <-> IP

ATM <-> IP

2G MS 2G MSG711/Iu /RTP/UDP/IP

VoIP*trunking

G711/TDMG711/TDM

G711/TDM

AMR/Iu/AAL2/I366.1AMR/Iu /AAL2(I366.1)

AMR/Iu /AAL2(I366.1)

AMR/Iu/AAL2(I366.1)

VoIP*Trunking

+EC

TC+EC

IP <-> ATM

TC

VoIP*trunking

When EC (echo cancellation) function is mentioned, it only applies to interfaces towards the PSTN.


（内部资料）

G711 (64 K bits/s per channel)

GSM

NGN

PSTN/2G PLMN

TC

PSTN/2G PLMN

TC


AMR/EFR/HR/FR

BSC

BSC MGW

BTSTC

AMR/EFR/HR/FR BTS

TCMGW


TC

G711/G72x (from 16 to 171Kb/s per ch.)

Local traffic will decrease

bandwidth requirements

TC

OPEX and CAPEX reduction2G network

> MGW must be located near BSC to favour local traffic

> Transcoder can be added to improve bandwidth efficiency Transport

saving

PacketNetwork

TDM Network

Voice compression and silence suppression can

be added to reduce bandwidth

requirements


（内部资料）

Outline



• UMTS R4 key technology• TrFO vs TFO• Bearer control signaling • Nc and Mc interface: BICC, H.248• Signaling transport


（内部资料）

Architecture - ATM backbone

MSCServer

(G)MSCServer

BICC CS-2

MGW MGW

AAL2 CS-2

ATM/AAL2/Iu UP

H.248/Megacowith BICC,

3GPP Packages

- TFO- 3G UP- CS Data- 3G Call Progress


（内部资料）

Nb interface: ATM backbone

AAL2 connection signaling(Q.2630.2)

AAL2 Signaling Transport Converterfor MTP3b (Q.2150.1)

MTP3bSSCF-NNISSCOPAAL5ATM

AAL-2 SAR SSCS (I.366.1)AAL2 (I.363.2)

ATM

User plane:

Control plane:AAL2 bearer establishment signaling


（内部资料）

Architecture - IP backbone

MSCServer

(G)MSCServer

IPBCP

MGW MGW

IP/UDP/RTP/Iu UPF

H.248/Megacowith 3GPP Packages

- TFO- 3G UP- CS Data- 3G Call Progress

Tunnel

APM/BICC


（内部资料）

Protocol stack for IP technology

MGW MGW

MSC-Server MSC-ServerNc

Mc

Nb

Mc

TS 29.232

BICC: Q.765.5

Tunnel: Q.1990

IPBCP: Q.1970

Nb:User plane and control plane for user plane:

Control plane:for IP bearer establishment

RTP/RTCP UDP IPv4 or IPv6

IPBCP is used for the exchange of media stream characteristics, port numbers and IP addressesof the source and sink of a media stream to establish and allow the modification of IP bearers


（内部资料）

Outline





（内部资料）

Nc interface:NGN architecture elements

CSF CSFCall Control Signalling

Connection

Call

BIWF = Bearer Inter-working FunctionCSF = Call Service FunctionBCF = Bearer Control FunctionMCF = Media Control FunctionMMSF = Media Mapping/Switching Function

Bearer Control Signalling

Connection

BIWF

MMSF

MCF

BCF

BIWF

MMSF

MCF

BCF

BIWF

MMSF

MCF

BCF

BIWF

MMSF

MCF

BCF

3GPP Nc

3GPP Nb

3GPP McH.248


（内部资料）

Nc interface

> BICC Bearer Independent Call control• support of narrow-band ISDN services independent of

the bearer technology and signalling message transport technology used.

• Mainly adds the Binding reference, BNC charact, BIWF@ field to be exchanged + Codec negotiation

CSF

BCF

CSF

BCFBCF BCF BCF

MMSF MMSF MMSF MMSF MMSF

BICC

Connection

Call

MCF MCF MCF MCF MCF

Signalling

Bearer


（内部资料）

Forward bearer setup and backward bearer setup


（内部资料）

Mc interface

> H.248• Server instructs MGW to establish bearers

CSF

BCF

CSF

BCFBCF BCF BCF

MMSF MMSF MMSF MMSF MMSF

BICC

Connection

Call

MCF MCF MCF MCF MCF

Signalling

Bearer

Mc Mc


（内部资料）

Mc introduction

> Mc protocol is based on H248. > Termination : A “Termination” is a logical entity on a MG,

that sources and/or sinks media and/or control streams. A Termination is described by a number of characterizing Properties

> Context : A “Context” is an association between a number of Terminations. The Context describes the topology (who hears/sees whom) and the media mixing and/or switching parameters when two or more Terminations are involved. The null-context is a specific context that contains all terminations that are not associated to another termination.


（内部资料）

Properties

> Most important properties are :• mux : describes how media of a session are multiplexed• media : describes media type• events : describes events to be listened for by the MG and what

to do when an event is detected (ex digit collection)• signals : describes signals and/or actions to be applied (e.g. rin

gback signal)


（内部资料）

Mc commands

> “Only” 8 commands are defined. But they can largely be modulated by packages

– ADD– MODIFY– SUBSTRACT– MOVE AUDIT VALUES– AUDIT CAPABILITIES– NOTIFY– SERVICE CHANGE


（内部资料）

Mc - MGW

> MGC and MGW have a client/server relationship. Thus all commands flow from MGC toward MG except :• NOTIFY” command (from MGW to MGC) • SERVICE CHANGE (both way)


（内部资料）

Call establishment principles> Three new steps :

• Codec negotiation • Transport establishment • Codec modes identification

> Codec negotiation :

MSCserver

MSC server

BICC : IAM (codec list,...)

BICC : APM (selected codec,available codec list,....)

RANAP( Set_up, codec list)

N_ISUP : IAM RANAP(Rab asgt req.

, selected codec)

MGW MGW


（内部资料）

Call establishment principles

MSCserver

MSCserver

RANAP (Setup ,codec list)

> Transport establishment (forward mode)

BICC : IAM (codec list, BNC Charac., ...) N_ISUP (IAM; ..)

H248:Add (TDM resource, ..)

H248 :Add (BNC charac.)

H248:Add resp(BIWF_ad,BNC_id,...)

BICC : APM (selected codec, available codec listBIWF_ad,BNC_id,...)

H248 :Add (BIWF_ad,BNC_id,...)

Q2630.2:Bearer establishment

Q2630.2:Bearer established

Bearer establishment withRNC not represented

(same as R3)

RANAP(RAB asgt req., selected codec)

MGW MGW


（内部资料）

Call establishment principles

> Codec mode identification :• In band protocol : Iu framing protocol (Iu user protocol(R3))• Launched when the bearer is fully established end to end (RNC/RNC ,

RNC/transcoder point)• Objective : declaration of the identification of the codec mode (RFCI) :

RNC dependant • TrFO break equipment : TBE

MGW

RNCIuFP : init

IuFP : ack

MGW

RNC

TBE : Store RFCIAcknowledge Iu FP

forward control PDU

TBE : Store RFCIAcknowledge Iu FPTerminated IuFP

RNCAAL2switch

AAL2switch RNC

Iu FP+ user data

Establishment phase

Established phase

IuFP : init

IuFP : ack

IuFP : init

IuFP : ack


（内部资料）

Outline



• UMTS R4 key technology• TrFO vs TFO• Bearer control signaling • Nc and Mc interface: BICC, H.248• Signaling transport


（内部资料）

Signalling> Network Control signalling :

• MAP/CAP/IN/ISUP/BICC, 2 options :– NB SS7 (MTP3/MTP2/MTP1)– IP transport (M3UA/SCTP/IP)

> Access control signalling :• RANAP/ALCAP : BB SS7 (MTP3B/SSCF/SSCOP/AAL5/ATM)• BSSMAP : NB SS7 (MTP3/MTP2/MTP1)

> Transport signalling :• ATM :

– Q2630.2 : BB SS7 (MTP3B/SSCF/SSCOP/AAL5/ATM)– Q2931 : UNI stack (SSCF/SSCOP/AAL5/ATM)

• IP : IPBCP/IPBCTP (tunnelling via H248 & BICC)

> Call bearer control signalling :• H248 : IP transport (H248/SCTP/IP)


（内部资料）

SIGTRAN

> M3UA is specified by 3GPP R4.

SCCP/ISUP

MTP-3

MTP-2

Data

MTP-1

M2PA

SCTP

TCAP / MAP / INAP Q.931Q.921

IUASUAISUP / SCCP

M2UA

MTP-3M3UA

IP

IETF Protocols Aligned to SS7 Stack SS7 Stack


（内部资料）

SIGTRAN

SIGTRAN (for Signaling Transport) is used to transport SS7 over the Internet (SCCP, ISUP)

The SIGTRAN protocol is actually made up of several components:

standard IP; SCTP: used to ensure that

the data required for signaling is delivered properly;

M3UA: transport of any SS7 MTP3-User signaling (e.g., SCCP, ISUP) over the IP Network.

MSC server with SGW embedded

Legacy HLR

Dedicated SGW

SIGTRAN domain

SS7 domain

MGW with SGW

embedded

SIGTRAN HLR

(1)

(2)

(3)


（内部资料）

Signalling : NB SS7 and ATM backbone

Transmission level

TDM levelATM level

IP levelNB SS7 Network

MAP CAP ISUP BICCBSSMAP

BB SS7 Network

RANAP

Control

ALCAP Q2630.2 H248

Transport

Q2931

UNIstack


（内部资料）

Signalling : IP transport

Transmission level

ATM level

IP level

MAP CAP ISUP BICCBSSMAP

BB SS7 Network

RANAP

Control

ALCAP H248

Transport

SCTP

IP levelSCTP

M3UA


（内部资料）

Signalling over IP : M3UA

> Network organisation

IP

SS7MSC

MSC

SG

MSCSigtranServer

MSC server

MGC

SigtranServer

External signalling gateway function

External signalling gateway function

Equipment with native M3UA stack

SG

: IP

: NB SS7

SERVICE & HOME ENVIRONMENTSERVICE & HOME ENVIRONMENT

HLR SCP

GMLC

SMSCEIR

SCCPGW/RELSTP

MNP,FLR,..

MSC server


（内部资料）

IP signalling transport

MGW

BSSAP/MTP3

BSC

IP backbone

BSC

MSC server

Sigtranserver

RNC RANAP/MTP3BBSSAP or RANAP or BICC or ISUP/M3UA

DS0grooming

MGW

Sigtranserver

DS0grooming

RNC

VCCC

VCCC

ISUP/MTP3MGW

Sigtranserver

DS0grooming

Native M3UA


（内部资料）

IP signalling transport Control plane and management plane

SERVICE & HOME ENVIRONMENTSERVICE & HOME ENVIRONMENT

GMLC

SMSCEIR

HLR SCP

Billing Center (option)

CDR collector

OMC_CS

H248

SS7 orSIGTRAN

MSC Server

IP IP

IP

IP(NGN only)

Localmanagement

(1 standard PC)

BTSBSC

NB SS7

BB SS7

Node BRNC

NB SS7 orSIGTRAN

SGSN

IP

IP

To other MSC server :SS7 or SIGTRAN

（内部资料）

`

www.alcatel-sbell.com.cn

R4 Network and Key Technology

Documents

Transcript of R4 Network and Key Technology