MGW_intro_U15_v1-3

© NOKIA MGW_intro_U15.PPT / 3.7.2001 /BKe page: 1

Introduction to

Multimedia Gateway(MGW)

U1.5 7.77.7.2001.2001


3G MGW, Introduction to Multimedia 3G MGW, Introduction to Multimedia GateWay (ATM Module) GateWay (ATM Module)

• Target Group: Personnel working in the Customer Service center who need information about the ATM module in 3G network

• Prerequisite Knowledge: Knowledge of GSM network functioning and Nokia 2G network. General knowledge of IPA 2800 platform. Basics of ATM. General knowledge of functioning of datacom networks.

• Objectives: Personnel who have participated in the course are able to describe how ATM module is located in the 3G network and know the main functionalities of it. They also know what can be found from the ATM module documentation and where the documentation can be found.


Objectives and contentObjectives and content

• The objective of this presentation is to cover basic MGW functionality

• Viewpoint is U1.5 sw release

• Presentation consists of:

• General information about MGW

• Signalling Bearer (Control Plane)

• Data Transport & Transport Signalling (User Plane)

• Statistics

• Capacity & Overload

• NEMU

• Future evolution


General information about General information about MGWMGW


Nokia 3G MSC = Nokia 3G MSC = 2G 2G MSC + MSC + MGWMGW

Co-sited GSM + UMTSBase Station Subsystem

Mobile Switching CentreHome Location Register

(GSM + UMTS)

HLR

MSC

MGW

Network Subsystem(GSM + UMTS)

IN Service Control Point

BSC

RNC

Radio NetworkController (UMTS)

UMTS (WCDMA)Base Station

UMTSmobile

GSMmobile

GSM/UMTS mobile

Landline NW(PSTN/ISDN)

GSM Base Station

Base StationController (GSM)

A

Iu


Nokia 3G MSCNokia 3G MSC

Based on the standards defined by 3GPP

Overall CS CN architecture will be almost unchanged as a result of evolution from GSM to 3GPP Release '99

The only architectural change: ATM based Iu interface will replace A interface for connection of the MSC to the 3G Radio Access Network

The Iu interface will be implemented by a HW upgrade to the MSC

A interface towards BSS remains

Evolving in phases of flexible upgrades from existing GSM MSC's towards the 3G core networkSolution is based on the use of the GSM core network

A smooth evolution from GSM to integrated GSM/3G networks, while supporting all the existing GSM services together with the new 3G services

Fast roll out

The 3G MSC supports (in addition to GSM MSC)Iu interface using ATM transmission towards the WCDMA RAN

User plane adaptation for circuit switched data services

Transcoding of speech services


3G MSC Schedule - 3GPP Rel 993G MSC Schedule - 3GPP Rel 99

TRIAL U1

04/2001M10

11/2000

Phased approachTRIAL- 3G functionalities readyLAUNCH- Rel99 compliant & support for multiple RNCsCOMMERCIAL- More capacity

MGWU-releases

MSC & HLRM-releases

20002000 20012001 20022002

LAUNCH

U1+08/2001

M1108/2001

COMMERCIAL U1.5

12/2001M11

08/2001


3G Core Trials 3G Core Trials M10 + U1.0; Available 5/01M10 + U1.0; Available 5/01

• For subscribers using GSM SIM cardRoaming

ATM Module

• Basic speech • Limited data service capabilityBasics

• All Intra MSC handovers• 3G -> 2G Inter MSC Handovers• 2G -> 2G Inter MSC Handovers

Handovers

• GSM level authentication (SIM card) based on A3/A8 algorithms Authentication

• 56/64 kbit/s transparent (no IWF); Circuit Switched multimedia - video call

Data speeds


3G Core - R99 compliancy3G Core - R99 compliancyM11 + U1+; Available 9/01M11 + U1+; Available 9/01

• For subscribers using GSM SIM card• For subscribers using 3G USIM card

Roaming

ATM Module

• Speech and data calls possible• multiple RNC feature to MGW • Basically 3GMSC supports the same features than 2GMSC

Basics

• All HO on previous slide added with • 2G -> 3G Inter MSC Handovers• 3G -> 3G Inter MSC Handovers• data Handover for 56/64 kbit/s transparent

Handovers

• UMTS authentication (USIM card); new algorithms (f1…f5) used in HLR/AuC and USIM • Mutual authentication

Authentication

• 56/64 kbit/s transparent (no IWF); Circuit Switched multimedia - video callData speeds


3G Core - More capacity3G Core - More capacityM11 + U1.5; Available 1/02M11 + U1.5; Available 1/02

• For subscribers using GSM SIM card• For subscribers using 3G USIM card

Roaming

ATM Module

• Speech and data calls possible• MGW can support 8-20 RNCs• Basically 3GMSC supports the same features than 2GMSC• support for multicall

Basics

• All HO on previous slide added with • 14.4, 28.8 and 57.6 kbit/s Non-Transparent and 28.8 kbit/s Transparent Handovers

Handovers

• UMTS authentication (USIM card); new algorithms (f1…f5) used in HLR/AuC and USIM • Mutual authentication

Authentication

• 14.4, 28.8 and 57.6kbit/s Non Transp.• 28.8 kbit/s Transparent • Circuit Switched multimedia (64/56 kbit/s transparent, no IWF) video call

Data speeds


First to market with Nokia WCDMA 3G First to market with Nokia WCDMA 3G systemsystem

Network deliveriesstart

Mar2001

World's first 3GPP WCDMA network

deliveries

Precommercial networksoperational

Multivendor integration

Jun2001

Commercial launch

Sep2001

Volume roll-out Invoiceable end user

services

3GPP compliant WCDMA network operational

Apr2001

Network verification start

Feb2001

CS core network elements MSC, HLR, and preMGW ready for 3G pilots. GSM equipment has upgraded to 3G. Open Iu-Cs interface supported.


Functionality of Functionality of MGWMGW

• Main function of the MGW is to provide transcoding and interworking between 3G RAN and MSC

Key functions:

• At user plane: • Signal processing for speech coding (transcoding) and circuit switched data

adaptation

• ATM/TDM conversion

• At control plane: • Iu-A' interface signaling conversion meaning narrowband and broadband SS7

mapping

• L3 protocols (MM, CM) based on GSM and carried transparently over to UTRAN

MGWRNC MSCIu A'


Architecture of Architecture of MGWMGW

Interface Functions

Switching Functions

Control Functions

Signal Processing

System Functions

SFU

MXU

MXU

MXU

NIP1

NIWU

TCU

A2SU

TBU

NIS1

OMU

SPMU

ISU

WDU

E1/T1/J1IMA/ATM

E1/T1TDM

STM-1ATM

CACU

CM

Iu

A'

Ethernet100Base-

TX

NEMU

WDU


Configuration of Configuration of MGWMGW

TB

UF

TS

S3

PD

20P

D20

TS

S3

TB

UF

MX

622-

AM

XU

MX

622-

AM

XU

SF

05-A

SF

U 0

CC

PC

2C

M 0

HD

S9

WD

U 0

HD

S9

WD

U 1

CC

PC

2O

MU

0C

CP

C2

OM

U 1

MO

DF

DU

MC

PC

2N

EM

UE

HB

NI4

S1

NIU

NI4

S1

NIU

CC

PC

2C

AC

U 0

CC

PC

2S

PM

U 0

CC

PC

2C

M 1

CC

PC

2C

AC

U 1

CC

PC

2S

PM

U 1

SF

05-A

SF

U 1

HD

S9

C:

HD

S9

C:

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

MX

622-

AM

XU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

U

CD

SP

TC

U

AL

2SA

2SU

CC

PC

2IS

U

IW1

6P1

NIW

UIW

16P

1N

IWU

CC

PC

2IS

U (

SP

)A

L2S

A2S

U (

SP

)

++

++

++

++

++

++

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

MX

622-

AM

XU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

U

CD

SP

TC

U

AL

2SA

2SU

CC

PC

2IS

U

IW1

6P1

NIW

UIW

16P

1N

IWU

++

++

IW1

6P1

NIW

U+

+

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

U

CD

SP

TC

U

AL

2SA

2SU

CC

PC

2IS

U

IW1

6P1

NIW

UIW

16P

1N

IWU

++

++

++

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

++

++

++

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

MX

622-

AM

XU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

U

CD

SP

TC

U

AL

2SA

2SU

CC

PC

2IS

U

IW1

6P1

NIW

UIW

16P

1N

IWU

++

++

++

TB

UF

TB

UF

PD

20

MX

622-

AM

XU

MX

622-

AM

XU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

UC

DS

PT

CU

CD

SP

TC

U

CD

SP

TC

U

AL

2SA

2SU

CC

PC

2IS

U

IW1

6P1

NIW

UIW

16P

1N

IWU

++

++

++

++

++

++

++

++

++

++

++

++

++

++

++

++

++

111

222

333

444

555

• Physical size one or two cabinets

• Modular expansion: capacity can be increased even plug-in-unit by plug-in-unit

• Expansion steps expressed as number of transcoding channels:

1 = 1024 ch (8 TCUs)+2 = 2048 ch (16 TCUs)+3 = 3072 ch (24 TCUs)+4 = 4096 ch (32 TCUs)+5 = 5120 ch (40 TCUs)


General information about Iu General information about Iu Interface Interface


Iu Interface ConceptIu Interface Concept

UTRAN

USIM

RNC

Iub Iur

CN

Uu

UE

ME

Cu

RNS

RNS

Node B

Iu

RNC

Node B

Node B

Node B

SGSN

Iu-CS

Iu-PS

MSC/VLR

CBC

Iu-BC

Access Nodefor CS-domain

Access Nodefor PS-domain

Access Nodefor BC-domain


Iu is in the Access StratumIu is in the Access Stratum

UTRANUE CN

Access Stratum

Non-Access Stratum

Radio(Uu)

Iu

Radioprotocols

Radioprotocols

Iuprotocols

(2)

Iuprotocols

(2)

CM, MM CM, MM

Iuprotocols

Iuprotocols


Protocol PrinciplesProtocol Principles• Elementary Procedures

• Three classes:

Class 1: request and response (failure or success)

Class 2: request without response

Class 3: request and possibility for many responses

• Independent of each other (interactions specified in special cases)

• Backwards and Forwards Compatibility

• So called "Comprehension Required" principle applied

• Allows IEs from different standard versions in one message

• Client - Server model

Clientno questions why

Serverdetailed service

Request


Protocol structure for IProtocol structure for Iuu-CS-CS

Q.2150.1

Q.2630.1

RANAP Iu UP ProtocolLayer

TransportNetwork

Layer

Physical Layer

TransportUser

NetworkPlane

Control Plane User Plane

TransportUser

NetworkPlane

Transport NetworkControl Plane

RadioNetwork

Layer

ATM

SSCOP

AAL5

SSCOP

SSCF-NNI

AAL2AAL5

MTP3bMTP3b

SCCP

SSCF-NNI

• Control Plane: Signalling Bearer for Circuit Switched Domain

• User Plane: Data Transport & Transport Signalling

• Transport Network Control Plane• Transport Network User Plane


Functions of RANAPFunctions of RANAP

• Relocating serving RNC

• This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another.

• Overall RAB management

• This function is responsible for setting up, modifying and releasing RABs.

• Queuing the setup of RAB

• The purpose of this function is to allow placing some requested RABs into a queue, and indicate the peer entity about the queuing.

• Requesting RAB release

• While the overall RAB management is a function of the CN, the RNC has the capability to request the release of RAB.

• Release of all Iu connection resources

• This function is used to explicitly release all resources related to one Iu connection.


• Requesting the release of all Iu connection resources

• While the Iu release is managed from the CN, the RNC has the capability to request the release of all Iu connection resources from the corresponding Iu connection.

• Controlling overload in the Iu interface

• This function allows adjusting the load in the Iu interface.

• Resetting the Iu

• Sending the UE Common ID (permanent NAS UE identity) to the RNC

• Paging the user

• Controlling the tracing of the UE activity.

• This function allows setting the trace mode for a given UE. This function also allows the deactivation of a previously established trace.


• Transport of NAS information between UE and CN

• Transport of the initial NAS signalling message from the UE to CN, Transport of NAS signalling messages between UE and CN.

• Controlling the security mode in the UTRAN

• This function is used to send the security keys (ciphering and integrity protection) to the UTRAN, and setting the operation mode for security functions.

• Controlling location reporting

• This function allows the CN to operate the mode in which the UTRAN reports the location of the UE.

• Location reporting

• This function is used for transferring the actual location information from RNC to the CN.

• Reporting general error situations

• This function allows reporting of general error situations, for which function specific error messages have not been defined.


Control PlaneControl Plane


Overview Overview

• In the MGW ATM based Iu interface and TDM based A' interface are connected together. This requires:

• control plane level interworking between interfaces

• interworking of ATM and PCM resources at user plane

• Feature 1031 Circuit Switched Services covers environment of circuit switched services and conversions required from control plane point of view

• Since all A' interface signalling is not directly applicable at Iu interface and vice versa, conversion of procedures, signalling messages and parameters is needed in MGW.

• The feature also describes changes in MSC

• MM/CM level modifications according to 3G TS 24.008 (Release 99)

• Non standard additions to BSSAP R99 signalling in order to provide all necessary information to MGW for supporting open Iu interface towards the RNC


Control plane protocol stacks of Control plane protocol stacks of networknetwork elements elements

UE

MGWRNC

MSC

64 kbit/s PHY

MTP2

MTP3

SCCP

BSSMAP+

MM

64 kbit/s PHY

MTP2

Generic MTP3

BSSMAP+RANAP

SAAL-NNI

ATM

SCCP

MTP3-b

RANAP

SAAL-NNI

ATM

RRC

CM (CC, SS, SMS)

MM

CM (CC, SS, SMS)

Iu A'

RLC/MAC/Physical Layer

Generic SCCP

BSSMAP+ to RANAP conversion

BSSMAP+:non-standard additions to BSSAP

3G TS 25.413

GSM 08.08 + additions

TS 24.008

SSCF/SSCOP/AAL5


Handling of BSSAP'/RANAP Handling of BSSAP'/RANAP procedures between A' and Iu procedures between A' and Iu

interfacesinterfaces

• Procedures can be divided to following types:• Procedures converted between interfaces

Majority of procedures belong to this group, e.g. assignment and handover

• Procedures used only at A' interface

Circuit handling procedures and such procedures that are not defined at Iu but can be used for interworking over A' interface, e.g blocking and handover performed

• Procedures used only at Iu interface

These procedures have no corresponding procedure at A' interface, e.g. relocation cancel

• Procedures that cause interaction at the interface(s) (e.g. reset)

• Procedures that are not supported with ATM Module/MSC

MGWMGWRNCRNCMSCMSCIu interface A' interface

3G TS 25.413 (RANAP) BSSAP'


Iu interface messagesIu interface messages

Iu interface message Action

RAB ASSIGNMENT REQUEST ConvertedRAB ASSIGNMENT RESPONSE ConvertedRAB RELEASE REQUEST ConvertedIU RELEASE REQUEST ConvertedIU RELEASE COMMAND ConvertedIU RELEASE COMPLETE ConvertedRELOCATION REQUIRED ConvertedRELOCATION REQUEST ConvertedRELOCATION REQUEST ACKNOWLEDGE ConvertedRELOCATION COMMAND ConvertedRELOCATION DETECT ConvertedRELOCATION COMPLETE ConvertedRELOCATION PREPARATION FAILURE ConvertedRELOCATION FAILURE ConvertedRELOCATION CANCEL Iu only - causes actions over A'RELOCATION CANCEL ACKNOWLEDGE Iu only - causes actions over A'SRNS CONTEXT REQUEST Not relevant for CS CNSRNS CONTEXT RESPONSE Not relevant for CS CNSRNS DATA FORWARD COMMAND Not relevant for CS CNFORWARD SRNS CONTEXT Not relevant for CS CNPAGING Converted

Iu interface message Action

COMMON ID ConvertedCN INVOKE TRACE ConvertedSECURITY MODE COMMAND ConvertedSECURITY MODE COMPLETE ConvertedSECURITY MODE REJECT ConvertedLOCATION REPORTING CONTROL Iu only - causes actions over A'LOCATION REPORT Iu only - causes actions over A'DATA VOLUME REPORT REQUEST Not relevant for CS CNDATA VOLUME REPORT Not relevant for CS CNINITIAL UE MESSAGE ConvertedDIRECT TRANSFER Converted

OVERLOAD ConvertedRESET Iu only - causes actions over A'RESET ACKNOWLEDGE Iu only - causes actions over A'ERROR INDICATION Iu onlyCN DEACTIVATE TRACE Not supportedRANAP RELOCATION INFORMATION Not relevant for CS CNRESET RESOURCE Iu only - causes actions over A'RESET RESOURCE ACKNOWLEDGE Iu only - causes actions over A'


A' interface messagesA' interface messagesA' interface message Action

ASSIGNMENT REQUEST ConvertedASSIGNMENT COMPLETE ConvertedASSIGNMENT FAILURE ConvertedBLOCK A' onlyBLOCKING ACKNOWLEDGE A' onlyCIRCUIT GROUP BLOCK Not supportedCIRCUIT GROUP BLOCKING ACKNOWLEDGE Not supportedCIRCUIT GROUP UNBLOCK Not supportedCIRCUIT GROUP UNBLOCKING ACKNOWLEDGE Not supportedCLEAR COMMAND ConvertedCLEAR COMPLETE ConvertedCLEAR REQUEST ConvertedUNBLOCK A' onlyUNBLOCKING ACK A' onlyHANDOVER CANDIDATE ENQUIRE Not supportedHANDOVER CANDIDATE RESPONSE Not supportedHANDOVER REQUEST ConvertedHANDOVER REQUIRED ConvertedHANDOVER REQUIRED REJECT ConvertedHANDOVER REQUEST ACKNOWLEDGE ConvertedHANDOVER COMMAND ConvertedHANDOVER COMPLETE ConvertedHANDOVER SUCCEEDED Not supportedHANDOVER FAILURE ConvertedHANDOVER PERFORMED A' only - caused by Iu actionHANDOVER DETECT ConvertedRESOURCE REQUEST Not supportedRESET A' only - causes actions over IuRESET ACK A' only - causes actions over IuRESOURCE INDICATION Not supportedPAGING ConvertedOVERLOAD ConvertedMSC INVOKE TRACE ConvertedBSS INVOKE TRACE Not supportedCLASSMARK UPDATE A' only - caused by Iu actionCLASSMARK REQUEST Not supported

CIPHER MODE COMMAND ConvertedCIPHER MODE COMPLETE ConvertedCIPHER MODE REJECT ConvertedCOMPLETE LAYER 3 INFORMATION ConvertedQUEUING INDICATION A' only - caused by Iu actionSAPI "N" REJECT Not supportedRESET CIRCUIT A' only - causes actions over IuRESET CIRCUIT ACKNOWLEDGE A' only - causes actions over IuCONFUSION A' onlyUNEQUIPPED CIRCUIT A' onlyLOAD INDICATION Not supportedVGCS/VBS SETUP Not supportedVGCS/VBS SETUP ACK Not supportedVGCS/VBS SETUP REFUSE Not supportedVGCS/VBS ASSIGNMENT REQUEST Not supportedVGCS/VBS ASSIGNMENT RESULT Not supportedVGCS/VBS ASSIGNMENT FAILURE Not supportedVGCS/VBS QUEUING INDICATION Not supportedUPLINK REQUEST Not supportedUPLINK REQUEST ACKNOWLEDGE Not supportedUPLINK REQUEST CONFIRMATION Not supportedUPLINK RELEASE INDICATION Not supportedUPLINK REJECT COMMAND Not supportedUPLINK RELEASE COMMAND Not supportedUPLINK SEIZED COMMAND Not supportedSUSPEND Not supportedRESUME Not supportedCHANGE CIRCUIT Not supportedCHANGE CIRCUIT ACKNOWLEDGE Not supportedLSA INFORMATION Not supportedCONNECTION ORIENTED INFORMATION Not supportedPERFORM LOCATION REQUEST Supported U1+ onwardsPERFORM LOCATION RESPONSE Supported U1+ onwardsPERFORM LOCATION ABORT Supported U1+ onwardsCONNECTIONLESS INFORMATION Not supportedCOMMON ID Converted


MM/CM level conversionMM/CM level conversion

• The MM/CM specification (24.008) in R99 is common for GSM and UMTS

• MM/CM messages are transparent for MGW

• DTAP messaging over A' interface

• Piggypacked in Direct Transfer messages over Iu interface

• MSC is required to support R99 MM/CM!

MGWMGWRNCRNCMSCMSCIu interface A' interface

3G TS 24.008 (MM/CM)


Changes in MSCChanges in MSC

• Requirements for MSC due to MGW• Release 99 MM/CM:

The MSC connected to MGW is required to support release 99 MM/CM protocols.

• Release 99 BSSAP

The MSC connected to MGW is required to support release 99 BSSAP protocol.

• Non-standard BSSAP

The standard A-interface is not able to support all functionalities that are needed between MGW and MSC in order to support open Iu interface towards RNC.

• Control of the functionality in the MSC

New BSSAP version, PRFILE parameters, MML commands etc.

• Features in MSC

SUPPORT OF ENHANCED CIRCUIT SWITCHED DATA (ECSD) is required for 56/64kbits bit transparent data calls


Non standard BSSAP (U1)Non standard BSSAP (U1)

• Non standard BSSAP (= BSSAP') contains changes compared with standard GSM 08.08 BSSAP

• Affected messages and new information elements (Fn 1031):

- Handover Request: UMTS security information

- Handover Request Acknowledge: Chosen UMTS security information

- Handover Performed: SAI

- Cipher Mode Command: UMTS security information, Key status

- Cipher Mode Complete: Chosen UMTS security information

- Complete layer 3 Information: Global RNC-ID


Non standard BSSAP (U1_top & Non standard BSSAP (U1_top & U1.5)U1.5)

• Affected messages and new information elements (Fn 1260):

- Handover Required: RANAP cause

- Handover Failure: RANAP cause

- Handover Required Reject: RANAP cause

- Assignment Request: RAB parameters list (RAB parameters, User Plane Mode, UP Mode Versions), CIC list (RAB Id, CIC)

- Assignment Complete: RAB Id list, RAB Id list with causes, RAB Ids to be queued

- Assignment Failure: not used, instead Assignment Complete with RAB Id list with causes (RAB Id, RANAP cause, BSSAP cause)


- Clear Request: RANAP cause, RAB id list with causes

- Clear Command: RANAP cause, RAB id list with causes

- Clear Complete: RANAP cause, RAB id list with causes

- Handover Request (A): Contains only the message type

- Handover Request (B): RANAP cause, UMTS security information, RAB parameters list, CIC list

- Handover Request Acknowledge: Chosen UMTS security information, RAB Id list, RAB Id list with causes

- Handover Command: RAB Id list with causes

- Handover Performed: SAI

- Cipher Mode Command: UMTS security information, Key status

- Cipher Mode Complete: Chosen UMTS security information

- Complete layer 3 Information: Global RNC-ID

- Paging: CM Service Type (Paging Cause)


Connection EstablishmentConnection Establishment

RNC MGW MSC

1. RANAP: Initial UE messages

2. RANAP

3.BSSAP

4. Conversion

5. BSSMAP: Complete L3 Information (CM service request)

6. CC level signalling: security procedures and setup (transparent to MGW)


Connection Establishment Connection Establishment (continues)(continues)

RNC MGW MSC

7. BSSMAP: Assignment Request8.BSSAP

11&13RANAP

14. RANAP:RAB Assignment Request

15. User plane setup: AAL2 signalling

12.Binding Id

9. Conversion

10. Resource reservation

16.TC/DSP



RNC MGW MSC

23. CC level signalling continues

19.BSSAP

17. RANAP: RAB Assignment Response

18.RANAP

22. BSSMAP: Assignment Complete

21.TC/DSP

20. Conversion


Signalling conversion: operating Signalling conversion: operating principles principles

• Conversion functionality of MGW is controlled via files with MML's

• MGW-specific default parameters (WE)

MML commands for create, modify, interrogate, delete

network element specific default parameters, e.g. address type of information

Output of erroneous messages from the cyclic buffer with the commands of this command group

• Radio network controller-specific parameters (E1)

RNC-specific parameters have to be added in the MGW before traffic can be started, e.g. RNC-id, LAC

MML commands for create, modify, interrogate, delete RNC-specific parameters, also to restart the RNC or mobile services switching centre (MSC) connected to the MGW.


Signalling conversion: operating Signalling conversion: operating principlesprinciples

• MGW also contains

• PRB default parameters

Changes to default values (e.g. timers)

No MML's, modifications via UTPFIL

• Fixed data files (in U1)

Conversion specific information (cause code conversion ID3FIL, information element conversion paramters ID2FIL)

Changes in coordinated manner - e.g. change note type of procedure

-> in U1_top MML's for both files


MGWMGW Integration and Configuration Integration and Configuration Management Management


MGWMGW Integration Integration

• The main steps for integrating an IPA2800 network element to the mobile network:

• Configure PDH and SDH interfaces.

• Create ATM resources for signalling, user data and for DCN network .

• Create TCP/IP and IP over ATM configuration for DCN network

• Connect to Network Management System.

• Set external time source.

• Create SS7 signalling configuration.

• Create routing objects.

• Create synchronisation inputs.

• Creating MGW-specific default parameters

• Adding RNC-specific parameters

• Restarting RNC and MSC Interface

U1 related manuals and instructions can be found from

intranet: http://wwwdoc


MGWMGW configuration management configuration management

• Handling MGW-specific default parameters (WE)

• MGW-specific default parameters

• Output of erroneous messages from the cyclic buffer

• Handling radio network controller-specific parameters (E1)

• RNC-specific parameters

• Restart the RNC or MSC interface

U1 related manuals and instructions can be found from

intranet: http://wwwdoc


Exceptions to normal Radio network configuration in MSC

• These exceptions are described as part of MGW Configuration Management quide. For further information, refer to the MSC-specific commands in the Cellular Radio Network Administration command class.

• The MGW is connected to the MSC via A' interface and it has a specific signalling point code (SPC). Therefore, you need to create normal MTP/SCCP/BSSAP connections to this signalling point in MSC.

• Checking the extensions required by MGW: ATM_MODULE_EXT_IN_USE

• Creating MGW:

• Create MGW using the BSC creation commands. The BSC number is the RNC-ID of the RNC connected to MGW.

• Creating BSSAP version (parameter set)• MSC does not contain a default BSSAP version that corresponds the MGW A-interface version

(parameter set). You need to create one using an existing free BSSAP version as a basis.

• Creating service areas• From the radio network definitions' view point RNC is not visible, but you need to create MGW the same

way as BSC.

• The Service Area Codes (SAC) must be created to the MSC the same way as BTSs (cells).

• BSs are not visible in MSC.


Multiple RNC connections in one Multiple RNC connections in one MGWMGW

MSC

MGW

RNC

MGW MGW

RNC

RNCRNC

RNC RNC RNCRNC

RNC

Iu (+ Iur)

A'

Iur Iur

Physically MGWs are located on the MSC site

GSM A-interface improved with RANAP extensions

Iur connection between RNCs through MGW will be included to U1.5 Functionality

Max number of RNCs connectedto one MGW depends on network design.

Iur

UMTS interface between radio access network and circuit switched core network


Multiple RNC connections in one Multiple RNC connections in one MGWMGW

• More than one RNC can be configured into MGW• Changes to MGW control files

• Message routing from MSC to the correct RNC• Paging: Target RNC is selected according to LAC• Handover Request: Target RNC is selected according to RNC-ID

• Reset Resource procedure support for multiple RNC configuration• Separate Iu signaling connection identity table for each RNC

• Location reporting procedure conversions between Iu- and A'-interfaces


Further information sourcesFurther information sources

• IS 1031 Circuit Switched Services, r8 (in TDE and MSC&HLR/feature directory)

• R99 Specifications:

• UMTS 25.413 UTRAN Iu Interface RANAP Signalling, ver 3.5.0

• GSM 08.08 MSC - BSS interface; layer 3 specification, ver. 8.8.0

• UMTS 24.008 Core Network Protocols ver. 3.6.0

• Other MGW feature specifications:

• IS 1030 ATM User Plane connections (Risto Kauppinen)

• IS 1034, Circuit Switched Data User Service (Mika Heinola)

• IS 1077, ATM Module Effects on Statistics (András Pfening)

• Speech transcoding for ATM Module (SWP 52004) (Henrik Lepänaho)


User PlaneUser Plane


Iu User Plane ProtocolIu User Plane Protocol

• Transparent Mode

• For RABs requiring no special handling from Iu

• Only transport of the user data without framing

• Usage Example: Transparent CS data

• Support Mode for predefined SDU size

• Provides special services for handling RABs

• Uses framing of user data

• 3 PDU Types:

control data (PDU Type 14)

user data with error detection scheme (PDU Type 0),

user data without error detection scheme (PDU Type 1)

• Usage Example: AMR speech PDUs, Non-transparent CS data


Support Mode FunctionsSupport Mode FunctionsCN

Iu UP layer in support

mode

TNL-SAPTNL-SAP

Proce-dure

Controlfunc-tions

Proce-dure

Controlfunc-tions

Frame Handler function

Frame Handler function

NAS Data Streams specific functions

NAS Data Streams specific functions

RNL-SAP

Non Access Stratum

Access Stratum

Rad

io I

nte

rfac

e P

roto

cols

Iu UP layer in support

mode

RNCIu


• Transfer of User Data• Procedure that is used from either side of the Iu whenever there is data to be sent

• Frame Quality Classification

• Initialisation Procedure• Set the parameters (RFCIs, SDU sizes) in both end points of the U-Plane protocol.

• Iu Rate Control Procedure• Select a subset of RFCIs from those initialised.

• Time Alignment Procedure• Either delay or advance sending frames at the far end. The aim is to minimize the need for

buffering.

• Handling of Error Event Procedure• Report of error situations.


Transport Network Control Plane: Transport Network Control Plane: User Plane Connections in User Plane Connections in MGWMGW


OverviewOverview

• At Iu interface the radio access signalling protocols (control plane and user plane signalling protocols) are separated from each other

• support for different physical resources (ATM,IP,TDM) is needed

• maintenance procedures are taken away from the control plane signalling

• Feature 1030 ATM User Plane Connections covers interaction between control and user plane signalling


User Plane set-up

Speech call setup example in Speech call setup example in MGWMGWMGW MSCRNC

Assignment_request(CIC)

AAL2 SETUP(Binding Id, VPI/VCI/CID)

AAL2 CONNECT

Radio_access_bearer_assignment_complete

Assignment_complete

Radio_access_bearer_assignment_request(Binding Id)

CC Procedures continue

CC Procedures


Connection EstablishmentConnection Establishment

RNC ATM Module MSC

1. BSSMAP: Assignment RequestBSSAP

RANAP

4. RANAP:RAB Assignment Request

Res. man

2. Reserve resource

Binding Id

3. Reserve identifier

6. Associate identifier

7. Reserve resource

5. AAL2 SETUP (Binding Id, VPI/VCI/CID)AAL2 sig

9. AAL2 CONNECT

8. Indicate UP connection



RNC ATM Module MSC

16. Alerting.

12.BSSAP

10. RANAP: RAB Assignment Response

11.RANAP

15. BSSMAP: Assignment Complete

13. Conversion

14.Res. Man


Transport Network User PlaneTransport Network User Plane


Circuit Switched DataCircuit Switched Data


Operating principlesOperating principles

• MGW offers in first phase:

• bit transparent 56/64 kbit/s CS data connection

• important for multimedia applications

• This is achieved by using transparent mode functionality of the Iu UP protocol (3GPP TS 25.415)

• Actually MGW transfers raw data from Iu ta A'-interface and backwards because no framing is used.

Terminal RNC

Iu UP

MGW

Physical Physical Physical

2G MSC

Raw data Raw data Iu UP

Internal interface Iu Uu

Relay Relay

64 kbit/s 64 kbit/s


Implementation ArchitectureImplementation Architecture

Rawdata

buffer

Iu protocolhandling

A'protocol handling

IDPPRB

Setup from BSSAP' application

Iu 64 kbit/sA' 64 kbit/s


AMR SpeechAMR Speech


AMRAMR• UMTS AMR (Adative Multi Rate) codec is the default codec

• UMTS AMR codec has 8 source rates from 4.75 kbit/s to 12.2 kbit/s, a low rate background noise encoding mode (SID) and no_data -> therefore up to 10 different bearers are required to support it.

• The speech coder is capable of switching its bit-rate every 20 ms speech frame upon command.

• AMR speech utilises the support mode for predefined SDU size of the Iu UP protocol (3GPP TS 25.415)

Codec mode Source codec bit-rate

AMR_12.20 12.20 kbit/s (GSM EFR)

AMR_10.20 10.20 kbit/s

AMR_7.95 7.95 kbit/s

AMR_7.40 7.40 kbit/s (IS-641)

AMR_6.70 6.70 kbit/s (PDC-EFR)




AMR_SID 1.80 kbit/s * (*) Assuming SID frames are continously transmitted


• The output bits from the AMR speech codec are divided into 3 classes based on their sensitivity to errors.

• Class A bits are the most sensitive, and require the strongest error protection. Errors in other classes are not that likely to be audible.

• For an optimised speech service, the different classes of AMR codec output bits are transported within different RAB sub-flows.

• RAB sub-flows are coordinated, i.e. the frames are still received as whole in the UE/TC.

• Each RAB sub-flow can have different QoS parameters, e.g.

• Bit-error ratio of 10^-6 for class A bits,

• Bit-error ratio of 10^-3 for class B bits, and

• Bit-error ratio of 5*10^-3 for class C bits.

• Even though AMR is a multi-rate codec, changes in radio conditions are handled by RNC power control.

• However, AMR modes may be useful e.g. for RAN load balancing


StatisticsStatistics


• Cyclic buffer for erroneous messages

• Up to 200 erroneous messages with additional information about the event

• MML command (group WE) for output of erroneous messages

• Specially for testing and fault solving purposes

• Tracing per IMSI basis

• Triggered in the MSC

• MGW stores all connection oriented messages after CN Invoke Trace message has been received

• Described also in Statistics

• Counters

• Counter / message or event

• Values can be reported to the operator

• Described more detailed in Statistics

Fault monitoring in Fault monitoring in MGWMGW


Measurement - purposeMeasurement - purpose

• This short presentation is intended to tell you how operators can see MGW at work.

• Measurement in MGW

• Trace in MGW

• Inform operator that MGW is working

• Allow problem detection


Measurement - contentMeasurement - content

Operator gets figures telling the

• number of protocol messages (both A-if and Iu-if)

• binding id allocations

• overflow cases

• cause codes

incoming cause codes from A-if

incoming cause codes from Iu-if

MGW internal cause codes

Measurement is controlled by MML commands, group T2


Measurement report - fictiveMeasurement report - fictiveFICTIVE IWU REPORT MODEL START TIME: 1999-12-31 24:00 STOP TIME: 2000-01-01 01:00…BSSAP MESSAGE CASESASSIGNMENT REQUEST 255…RANAP MESSAGE CASESRADIO ACCESS BEARER ASSIGNMENT COMPLETE 254RADIO ACCESS BEARER ASSIGNMENT FAILURE 1…BINDING CASESBINDING ID ALLOCATIONS 234BINDING ID ALLOCATION FAILURES 1…CAUSE CODES FROM MSCcause code 1 112cause code 2 1…CAUSE CODES FROM RNCcause code 1 132cause code 2 11…IWU INTERNAL CAUSE CODEScause code 1 100cause code 2 0…END OF FICTIVE REPORT


Measurement - data and control flowMeasurement - data and control flow

IAFPRB

IUFPRB

ISU counter

fileRDRPRB

ISU-x

MGW counter

file

OMU

NEMU

DatabaseNMS/GUI

SHGHAN

SCMPRB

MML

AMNPRB

data flow control flow


Trace - purposeTrace - purpose

Monitor protocol conversion process for the purpose of

• testing

• allocating faults /RNC-MGW-MSC/

• proving correctness in multivendor environment


Trace - contentTrace - content

• DX messages that are sent to or received from IAFPRB and IUFPRB are monitored.

• It is possible to get only the message identity (number, name) or full content for detailed analysis.

• User can select which messages to monitor.

• Trace is triggered by MSC - fits into GSM trace

• Trace is controlled by MML commands (group T3)


Trace - data and control flowTrace - data and control flow

IAFPRB

IUFPRB

RRRPRB

ISU-x

NEMU

DatabaseNMS/GUI

OMUSDKPRB

resourcemanager

TOKAJI

Trace datafile

NEMU supportin later releases SHGHANRCQLIB

RCQLIB

data flow control flow

Tra

ce in

voca

tion

from

MS

C


MGWMGW Capacity issues Capacity issues and Overload controland Overload control


MGWMGW HW in U1 HW in U1.5.5 (A (A33))

• SFU: 10 Gbit/s

• 8 SFU ports:

• 2 of which for STM-1 connections and

• 6 for MXUs of which:

• 1 for centralized units

• 5 possible for "expansion steps"

• MXU interface towards SFU: 622 Mbit/s

• 13 tributary units behind one MXU, each at 155 Mbit/s

• Units behind the MXUs in the "expansion steps" are: ISU, A2SU, TCU, NIWU


MGWMGW expansion in U1 expansion in U1.5.5

• There are 8 TCUs behind each MXU

• one TCU can handle (theoretically…) 128 speech channels, 8*128=1024

• Thus the MGW capacity of SPEECH channels can be expanded in steps of 1024 channels, from 1024 to 5120.


MGWMGW bottlenecks in U1 bottlenecks in U1.5.5

• The obvious bottleneck is the A'-interface signalling link capacity

• Sixteen 64 kbit/s links at 0,2 Erl would not be nearly enough

• This bottleneck can be solved with high capacity links (available up to 1 Mbit/s or 2Mbit/s in A2?) but on the MSC side they are supported only in MSCi


MGWMGW and CS data in U1 and CS data in U1

• Even one STM-1 connection (155 Mbit/s) should be enough with speech calls

• The STM-1 becomes a bottleneck when the number of CS data calls increases -> payload bitrate of speech=16 kbit/s and of CS data=64 kbit/s!


Max. number of RNCs connected to Max. number of RNCs connected to the the MGWMGW

• SW required for Support of multiple RNC's in MGW

• MGW already U1_top

• MSC M11 (Fn 1260)

• MGW SW supports up to 20 RNC's / MGW

• HW limitation comes from the number of possible STM-1 connections

• In case each RNC is connected to MGW directly with own STM-1 connection

• In A2 absolute max number of RNC's was 4

• In A3 max number of RNC's is 8

• In case ATM Cross Connect (AXC) for STM-1 connections is used, the limiting factor is the SW support -> maximum number of RNC's is 20


MGWMGW Overload control Overload control

• Based on same WAC Window Access Service method as in B-series

• In every signaling unit ticket service program block TISERO • handles fixed amount tickets

• IAF checks the message in question and fetches a ticket based on message priority

• Two phase overload mechanism• access phase: controls initial messages for connection establishment i.e. ISU load

• assignment phase: controls resource reservation phase of the call, i.e. centralized unit load

• Second phase ticket reserving priority is higher than the first phase• If centralized part of system is overloaded meaning that the second phase reserves

most of the tickets, first phase can not get access

• Paging is not restricted by overload control

• In U1_top: Monitoring of incoming load from each RNC separately


NEMU in NEMU in MGWMGW


NEMU NEMU (=Network Element Management Unit)(=Network Element Management Unit)

• Adaptation between NE and NMS/SMP (compatibility)

• Collect all the NT applications into one manageable enviroment

• Offer great platform for NT designers and let them to concentrate on business logic

• Make it easier to bring value added services faster to market

• Open APIs also for 3rd parties to develop O&M applications

• Enables commercial products and sub contracting

NEMU Services

All applications arelocated here

NEMU SW Platform

NE

MU

3rd p

arty SW

NE

MU

3rd p

arty SW

GUIClients


Hardware: Compact NEMUHardware: Compact NEMU

Integrated in DX rackWindows NT operating systemIntel 600 MHz Pentium Pro CPU2 x Hard disc (9/18 GB)External management console (KB, mouse, monitor)HW management softwareCan be used with 3G and 2G Network ElementsSize: Compact PCI standard (high 6U)Connection to NE 10/100 Mbit/s TCP/IP Ethernet

CPU HDD

ManagementConsole


NEMU Applications in NEMU Applications in MGWMGW

• PM (Performance Management)• Performance monitoring, XML based

• FM (Fault Management) • Transferring alarms to NMS

• CM (Configuration Management)• Not in MGW, is done via MML commands

• CD Remote Management• Centralized CD activation & monitoring

• Remote SW Upgrade• Centralized, multiple clients, monitoring in real time

• NEMU in MGW does NOT have NE Backup Server and Network Element Data mediator


New features in U1.5New features in U1.5


CS Data User Plane Protocol Support CS Data User Plane Protocol Support for UMTS (FN1265)for UMTS (FN1265)

• New datarates in addition to 64/56 kbit/s transparent provided in U1

• 32 kbit/s transparent (no IWF used in MSC)

• 28.8 kbit/s transparent

• 14.4, 28.8, 57.6 kbit/s non transparent

• Changes also in the MSC


• The AAL2 nodal function has two main functions, which are:

• operation and maintenance procedures (already in the A2 platform)

• the AAL2 connection control function

• The task of the AAL2 connection control function is to route the AAL2 signalling according to the received Service Endpoint Address

• AAL type 2 transit paths can be formed between two Service End Point via the MGW.

• This feature enables connecting the AAL2 based Iur interface between two adjacent RNCs via MGW

• When the Iur interface is routed via MGW, direct connections between RNCs are not needed.

• This makes the implementation of the signaling network easier and cheaper for the operator – the same ATM resources can be utilized both for the Iu and the Iur interfaces.

• In the future this functionality can also be used for other AAL2 transit signaling cases e.g. for connecting the Iu traffic through a Media Gateway to another.

Feature AAL2 Nodal FunctionFeature AAL2 Nodal Function(FN 1302)(FN 1302)

RNC

ATM

Module

RNC RNC RNC

RNC

RNC

RNC

RNC

RNC

ATM

Module

NF

IurIur

=ATM connection

. . . . . . .. . . . .

MSC

RNC

MGW MGW

MSC


• This feature is an UMTS feature (CS domain only), it is not applicable to GSM system

• The Multicall supplementary service enables a mobile subscriber to have several simultaneous CS calls, each call using its own dedicated bearer.

• One CS Speech call and n*CS data/fax calls

• According to the specifications, only one active CS speech call is allowed simultaneously with CS data and fax calls.

• Multicall differs from GSM supplementary services in that in Multicall, one separate bearer (channel) is allocated for each speech or data call.

• MSC part is included in Fn 1264 Call Hold SS

ActiveCALL1

HoldCALL2

BEARER

ActiveCALL1

ActiveCALL2

BEARER1 BEARER2

ActiveCALL1

HoldCALL2

BEARER1

ActiveCALL3

BEARER2

Multicall Multicall with Call Hold

Feature Support for Multicall in Feature Support for Multicall in MGW MGW

(FN 1311)(FN 1311)


ATM Module traceability improvement(FN 1324)

Feature describes following improvements to fault tracing in MGW:

Tracing per IMSI basis

• Improvements for collection of RANAP/BSSMAP messages (RANAP trace)

• Trace can be activated for certain IMSI also from the MGW.

• MML command (group WE) for trace handling.

• Functionality is described more detailed in Statistics (FN1077: RANAP trace)

• Collection of error codes from user plane application

• Trace can be activated for certain IMSI locally in the MGW.

• Error codes are stored to a cyclic buffer.

• Trace is controlled by MML commands (group WE)

Cyclic buffer for erroneous A’ and Iu interface messages

• The stored additional information contains more exact diagnostic of the failure.


Future Future


Two Paths Two Paths of MGWof MGW

MGW needs:SW: upgradeHW: 100% reuse(add IP HW)

MSC Serverpath

All-IP path

MGW needs:SW: upgradeHW: ~90% reuse(add IP HW &remove ATM HW)

3G MSC

DX 200 MSC

MGW

H.248

Iu

ATM orIP backbone

PSTNMGWMGW

H.248

PSTNIP backbone MGWMGW

MSCServer

CPS


MSC Server in Rel4 networkMSC Server in Rel4 network

SGSN

RNCRNC

IN/SCE APSE

GSM

BSCBSC

WCDMA

MGWMGW

ExternalIP networks

IP/ATMBackbone

MGW

PSTN/ISDN

Other PLMN

HLR/

HSS

MSC ServerMSC ServerMSC ServerMSC Server

GGSN

A

A

Iu-CS

Iu-PS

H.248 H.248

BICC CS-2, SIP-T


Nokia/Cisco 3G Backbone- 2 technical options for R'99 deployment

-

IP + ATM backbone

• ATM and cell based MPLS

• initially core and RNC sites

• RAN ATM transport (2G and 3G)- E1/STM-1 (ATM, TDM) or - extend IP + ATM to RAN

• For multiservice ATM-based access technologies (e.g. BWA, xDSL)

• For multi-service technologies (e.g. IP, ATM, FR, CES)

IP/MPLS backboneframe based MPLSinitially core sites RAN transport (2G and 3G) E1/STM-1 (ATM, TDM)

For dedicated 3G networkFor evolving 2G/3G mobile network with ISP services

Both solutions ready for R5. Real-time IP flows are supported!


IP+ATMIP+ATMR'99 deploymentR'99 deployment

Nokia_Cisco_Tech_Message_12/07.03.2001 page 21 Cisco/Nokia Confidential - draft

RNC Site

2G & 3G Radio Access

BTS

BTS

BTS

RNCBTS

BSC

IP networks/access

MSC

HLR

Core Site

GGSNSGSN

IP networks/access

IP+ATM Backbone- MPLS support- Cisco MGX 8850- Catalyst 6509 (core sites)- STM-4 to STM-64 transport

BTS

RNC Site

RNC

BTS

BTS

BSC

IP networks/access

RNC + Core Site

RNCIP networks/access

PSTN

MSC SGSNGGSN

BTS

BTS

PSTN


IP+ATMIP+ATMR4/R5 deploymentR4/R5 deployment


BTS

BTS

BTS

RNC Site

RNCBTS

BSC

IP networks/access

Core Site

GGSNSGSN

IP networks/access

BTS

RNC Site

RNC

BTS

BTS

BSC

IP networks/access

RNC + Core Site


PSTN

MGWSGSN

BTS

BTS

PSTN

MGW

MSCserver

HSSCPS

GGSN

IP+ATM Backbone- MPLS support- MGX 8850- 7600 OSR (core sites)- STM-4 to STM-64 transport


IP/MPLSIP/MPLSR'99 deploymentR'99 deployment

Nokia_Ci sco_Tech_M essage_12/07.03.2001 page 19 Cisco/Nokia Confidential - draft

- Cisco GSR 12000 (core sites)- Catalyst 6509 (core sites)- STM-4 to STM-64- Iu & A-traffic with STM-1/E1


BTS

BTS

BTS

RNC Site

RNCBTS

BSC

IP ne tworks/access

MSC

HLR

Core Site

GGSNSGSN

IP ne tworks/access

BTS

RNC Site

RNC

BTS

BTS

BSC

RNC + Core Site

RNCIP ne tworks/access

PSTN

MSC SGSNGGSN

BTS

BTS

PSTN


IP/MPLSIP/MPLS R4/R5 deploymentR4/R5 deployment


BTS

BTS

BTS

RNC SiteBTS

BSC

IP networks/access

Core Site

GGSNSGSN

IP networks/access

BTS

RNC Site

BTS

BTS

BSC

RNC Site


MGWSGSN

BTS

BTS

IP/MPLS Backbone- 12000 GSR- 7600 OSR - STM-4 to STM-64- Iur/IP

MGWSGSN

MGW

MSCserver

HSSCPS

PSTN

PSTN

MGWSGSN

PSTN

RNC

RNC


Mobility Connection& Control

Servers

HLR/HSS

CPS MSS/CGS

Application Platforms and Servers

Service infrastructure

Horizontal enabling applications (location, presence, messaging etc.)

Consumer appsBusiness apps.

Service Domain

Incl. SIP ApplicationServer

All IP Network Architecture VisionAll IP Network Architecture Vision

BroadbandConnection and Control

Servers

NetAct Operation Support System

Internet

PSTNISDN

Intelligent Edge

IP/ATM/MPLS Backbone

IPv6

Media Gateway

Broadband Gateway

Mobility Gateway

MGW

2G SGSN3G SGSN

MGW

Wideband Wide-areaMultiradio Access

TripleModeBTS

WCDMABTS

EDGEBTS

BroadbandLocal-Area Access


Nokia/Cisco = Enablers for Mobile Nokia/Cisco = Enablers for Mobile InternetInternet

IP Mobility Layer

Access Layer

CiscoIP Backbone

Corporate Servers

NokiaSGSN

NokiaSGSN

NokiaGGSN

NokiaGGSN

PSTN

NokiaMedia

GW

NokiaHSS

NokiaCPS

Intranet

WDM,Dark Fiber

Network andService Mgmt

WCDMA

GSM/EDGE

TDMA/EDGE

Cisco ERCisco ER

Cisco ER

Cisco CR

Cisco CR

Cisco ER

Cisco CR

Gateway

Application Servers

IPv6


Example 3G Network deployment Example 3G Network deployment

Core site

RNC

RNC

RNC

RNC

RNC

RNC

RNC

RNC

RNCRNC

RNC

RNC

RNC

RNC

RNC

- up to n x 1000 BTS- 120 hub sites- 20 RNC sites- 2 core network sites

STM-4, STM-1, E3

STM-16

RNC

RNCSTM-4STM-16

STM-16

Core site

RNC

RNC

STM-1

Hub Site

nx2M

SDH

SGSN

GGSN

HSS CPS MSCServer

Core Site

Servers

GW

SDH

RNC

Inter-connects

RNCRNC

RNC Site

SDH


Control Plane Terminology & Control Plane Terminology & Abbreviations Abbreviations

• CS CN = Circuit Switched Core Network• Nokia solution consists of Mobile Switching Centre (MSC) and MGW

• RAN = Radio Access Network• Radio Network Controller and Node B's (or BS's) comprise the radio access network (RAN)

• MGW• Interworking network element located between MSC and RAN

• Based on IPA2800 platform

• Main function is to convert signalling and user data between A' and Iu interfaces

• A' interface• Internal interface between MSC and MGW.

• Based on GSM 08.08 BSSAP specification, but contains also additions -> This is not a standard interface!

• Iu interface• Standardised and open interface between MGW and RAN network.

MGW MGW RNCRNC

MSCMSCIu interface A' interface

RAN

CS CN

3G TS 24.008 (MM/CM)

3G TS 25.413 (RANAP) BSSAP'


• BSSAP'• Based on BSSAP (Base Station Subsystem Application Part) signalling for control of GSM services but contains additions

compared with normal BSSAP in order to provide open Iu interface towards RNC

• The BSSAP protocol is described in GSM 08.08: MSC-BSS Interface; Layer 3 Specification (Release 99) and the additions to this are defined within Fn 1031 (U1) and Fn 1260 (U1_top and U1.5)

• RANAP• Radio Access Network Application Part (RANAP) is used on the Iu interface for control of UMTS services

• The RANAP protocol is decribed in UMTS 25.413: UTRAN Iu Interface RANAP signalling (Release 99)

• Control plane• RANAP signalling in 3rd generation and BSSAP signalling in 2nd generation on top of transport layers.

• User plane• User data and transport layers that are based on ATM in 3rd generation and PCM concept in 2nd generation.

Terminology & Abbreviations Terminology & Abbreviations

MGW_intro_U15_v1-3

Documents

core sitesgsn ggsn

radio network controller

previous slide added

u1 related manuals

predefined sdu size

circuit switched multimedia

circuit switched data

error detection scheme