tedpmmf

transcript

Performance Measurement Message Flows

UMTS Terrestrial Radio Access Network

TED:PMMF

A50016-G5000-F201-1-7618 ND-57172-704 (E)-01

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties

for their own purposes could violate the rights of their owners.

Copyright (C) Siemens AG / NEC Corporation 2005.

Issued by: Siemens AG, Communications, Hofmannstraße 51, 81359 München, Germany and NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo, Japan

Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Preface

PR-11 Page

PREFACE

This document is prepared as a standard edition that may include descriptions not applying to your system.

This document shows basic and typical message sequence(s) per call processing. In the sequences, measurement types required for performance measurements are represented by “mtype n”, and radio channel names are accompanied with radio protocol messages (within parentheses).

The following sequences comprise this document:

• Location Registration

• MOC CS Related (Call Origination from CS)

• MTC CS Related (Call Termination to CS)

• CS Call Release

• MOC PS Related (Call Origination from PS)

• MTC PS Related (Call Termination to PS)

• PS Call Release

• Intra-Node B Handover

• Inter-Node B Handover

• Inter-RNC Handover

• Inter-Frequency Handover

• Relocation

• Inter-System Handover

• Inter-Node Connection (CS semi-normal sequence)

• Cell Update

• URA Update

• Common Measurement Report Reception

• Abbreviation List

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

Reason for Update

Summary:

First edition

Details:

Issue History:

Chapter/Section Reason for Update

All First edition

Issue Number

Date of issue Reason for Update

1 5/2004 First edition

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Contents

CONTENTS TITLE PAGE

1. Location Registration.................................................... 1-1

2. MOC CS Related (Call Origination from CS) ........................................... 2-1

3. MTC CS Related (Call Termination to CS) ................................................3-1

4. CS Call Release................................................................ 4-1

4.1 UE-Initiated Call Release ................................................. 4-1

4.2 Network-Initiated Call Release........................................ 4-4

5. MOC PS Related (Call Origination from PS).............................................5-1

6. MTC PS Related (Call Termination to PS) ................................................6-1

7. PS Call Release................................................................ 7-1

7.1 UE-Initiated Call Release ................................................. 7-1

7.2 RNC-Initiated Call Release .............................................. 7-4

8. Intra-Node B Handover ................................................. 8-1

8.1 Radio Link Addition ......................................................... 8-1

8.2 Radio Link Deletion.......................................................... 8-4

8.3 Radio Link Addition - Failure .......................................... 8-6

9. Inter-Node B Handover ................................................. 9-1

9.1 Radio Link Addition ......................................................... 9-1

9.2 Radio Link Deletion.......................................................... 9-3

9.3 Radio Link Addition - Failure .......................................... 9-5

10. Inter-RNC Handover ..................................................... 10-1

10.1 Radio Link Addition ....................................................... 10-1

10.2 Radio Link Deletion........................................................ 10-5

11. Inter-Frequency Handover......................................... 11-1

12. Relocation ........................................................................ 12-1

A50016-G5000-E201-1-7618ND-57172-703 (E)-01 Contents

CL-22 Pages

TITLE PAGE

13. Inter-System Handover ............................................... 13-1

13.1 From UMTS to GSM ....................................................... 13-1

13.2 From UMTS to GPRS ..................................................... 13-4

13.3 From UMTS to GPRS(PS) .............................................. 13-6

13.4 From GSM to UMTS ....................................................... 13-8

14. Inter-Node Connection................................................ 14-1

14.1 NG Occurrence after Receiving RANAP: RAB Assignment Request at RAB Establishment ...... 14-1

14.2 Racing of NBAP_RLFailureInd Reception for Waiting for ALCAP Establish Confirm .................... 14-6

14.3 Racing of RRC_SigConnRelInd Reception after RRC_RRCConnSetupComp ................................. 14-8

14.4 NG Occurrence after Receiving ALCAP: Establish Confirm (Iub) at RAB Establishment ......... 14-11

14.5 RRC ConnectionSetupComplete Wait Time-out ....... 14-13

15. Cell Update....................................................................... 15-1

16. URA Update ..................................................................... 16-1

17. Common Measurement Report Reception ......... 17-1

18. Abbreviation List ........................................................... 18-1

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 1Location Registration

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Location Registration

1. Location Registration

Fig. 1-1 shows the location registration procedure for Circuit Switched (CS) and Packet Switched (PS) systems together.

The following measurement types are used in the sequence:

• mtype 1Number of attempted RRC connection establishments per establishment cause

• mtype 2Number of successful RRC connection establishments per establishment cause

• mtype 82Number of used codes per spreading factor

• mtype 102Number of attempted code requests per spreading factor

• mtype 103Number of attempted radio link establishments per SF

• mtype 104Number of successful radio link establishments per SF

• mtype 159Number of attempted RRC connection releases on DCCH per release cause

• mtype 161Number of attempted signaling connection establishments

• mtype 163Number of signaling connection releases

• mtype 186Number of Iu release commands per release cause

• mtype 221Number of successful code requests per spreading factor

Node B MSCUE RNC

Fig. 1-1 Location Registration (1/5)

mtype 2

RRC: MEASUREMENT CONTROL(DCH: DCCH)

RRC: RRC CONNECTION SETUPCOMPLETE(DCH: DCCH)

RRC: RRC CONNECTION SETUP(FACH:CCCH)

RRC: INITIAL DIRECT TRANSFER[CS domain](MM: LOCATION UPDATING REQUEST(DCH:DCCH))

RRC: RRC CONNECTIONREQUEST(RACH: CCCH)

NBAP: RADIO LINKSETUP REQUEST

NBAP: RADIO LINKSETUP RESPONSE

mtype 82, 102, 103, 221

mtype 1

QAAL2 (Iub):ESTABLISH REQUEST

QAAL2 (Iub):ESTABLISH CONFIRM

NBAP: DEDICATED MEASUREMENTINITIATION REQUEST

NBAP: DEDICATED MEASUREMENTINITIATION RESPONSE

NBAP: RADIO LINKRESTORE INDICATION

mtype 104

Node B MSCUE RNC

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION REQUEST))]

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION AND CIPHERING REQUEST))]

RRC: DOWNLINK DIRECT TRANSFER(GMM: AUTHENTICATION AND CIPHERING REQUEST(DCH: DCCH))

SCCP(CO): CR[RANAP(INITIAL UE MESSAGE(ATTACH REQUEST))]

mtype 161

SCCP(CO): CC[RANAP(none)]

RRC: DOWNLINK DIRECT TRANSFER(MM: AUTHENTICATION REQUEST(DCH: DCCH))

RRC: UPLINK DIRECT TRANSFER(MM: AUTHENTICATION RESPONSE(DCH: DCCH))

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION RESPONSE))]

mtype 161

RRC: INITIAL DIRECT TRANSFER[PS domain](GMM: ATTACH REQUEST(DCH:DCCH))

SCCP(CO): CR[RANAP(INITIAL UE MESSAGE(LOCATION UPDATING REQUEST))]

Node B MSCUE RNC SGSN

SCCP (CO): DT1[RANAP(SECURITY MODE COMMAND)]

SCCP (CO): DT1[RANAP(SECURITY MODE COMPLETE)]

RRC: SECURITY MODECOMMAND(DCH: DCCH)

RRC: SECURITY MODECOMPLETE(DCH: DCCH)

RRC: UPLINK DIRECT TRANSFER(GMM: AUTHENTICATION AND CIPHERING RESPONSE(DCH: DCCH))

SCCP (CO): DT1[RANAP(COMMON ID)]

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION AND CIPHERING RESPONSE))]

SCCP(CO): DT1[RANAP (IU RELEASE COMMAND)]

RRC: SIGNALING CONNECTION RELEASE(DCH: DCCH)

SCCP(CO): DT1[RANAP

RRC: DOWNLINK DIRECT TRANSFER(GMM: ATTACH ACCEPT(DCH: DCCH))

SCCP(CO): DT1[RANAP(IU RELEASE COMMAND)]

RRC: RRC CONNECTIONRELEASE(DCH: DCCH)

mtype 159

RRC: RRC CONNECTION RELEASECOMPLETE(DCH: DCCH)

mtype 186

RRC: UPLINK DIRECT TRANSFER(GMM: ATTACH COMPLETE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(ATTACH COMPLETE))]

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(LOCATION UPDATING ACCEPT))]

RRC: DOWNLINK DIRECT TRANSFER(MM: LOCATION UPDATING ACCEPT(DCH: DCCH))

RRC: UPLINK DIRECT TRANSFER(MM: TMSI REALLOCATION COMPLETE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(TMSI REALLOCATION COMPLETE))]

(DIRECT TRANSFER(ATTACH ACCEPT))]

mtype 163

1-66 Pages

SCCP(CO): DT1[RANAP(IU RELEASE COMPLETE)]

NBAP: RADIO LINKDELETION REQUEST

NBAP: RADIO LINKDELETION RESPONSE

QAAL2(Iub):RELEASE REQUEST

QAAL2(Iub):RELEASE CONFIRM

SCCP(CO): RLSD

SCCP(CO): RLC

SCCP(CO): RLSD

SCCP(CO): RLC

mtype 82

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 2MOC CS Related

(Call Origination from CS)

A50016-G5000-F201-1-7618 MOC CS RelatedND-57172-704 (E)-01 (Call Origination from CS)

2. MOC CS Related (Call Origination from CS)

Fig. 2-1 shows a message sequence of the call origination from Circuit Switched (CS) network.

• mtype 5Number of attempted RAB establishments per RAB type

• mtype 6Number of successful RAB establishments per RAB type

• mtype 115Number of CN initiated RAB releases per release cause

Node B MSCUE RNC

Fig. 2-1 Call Origination from CS (1/4)

RRC: RRC CONNECTION SETUPCOMPLETE (DCH:DCCH)

RRC: RRC CONNECTIONREQUEST (RACH: CCCH)

mtype 2

RRC: MEASUREMENT CONTROL (DCH: DCCH)

RRC: INITIAL DIRECT TRANSFER(MM: CM SERVICE REQUEST (DCH:DCCH))

mtype 103

mtype 104

Node B MSCUE RNC

Fig.2-1 Call Origination from CS (2/4)

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(TMSI REALLOCATION COMMAND))]

RRC: DOWNLINK DIRECT TRANSFER(MM: TMSI REALLOCATION COMMAND(DCH: DCCH))

mtype 161

SCCP(CO): CC [RANAP (none)]

SCCP(CO): CR [RANAP (INITIAL UE MESSAGE(CM SERVICE REQUEST))]

RRC: UPLINK DIRECT TRANFER(MM: AUTHENTICATION RESPONSE(DCH: DCCH))

RRC: DOWNLINK DIRECT TRANFER(MM: AUTHENTICATION REQUEST(DCH: DCCH))

Node B MSCUE RNC

mtype82, 102, 221

NBAP: RADIO LINKRECONFIGURATION READY

QAAL2(Iub):ESTABLISH REQUEST

QAAL2(Iub):ESTABLISH CONFIRM

SCCP(CO): DT1[RANAP(RAB ASSIGNMENT REQUEST)]mtype 5, 115

QAAL2(Iu): ESTABLISH REQUEST

QAAL2(Iu): ESTABLISH CONFIRM

NBAP: RADIO LINKRECONFIGURATION PREPARE

NBAP: RADIO LINKRECONFIGURATION COMMIT

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(SETUP))]

RRC: UPLINK DIRECT TRANSFER(CC: SETUP(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CALL PROCEEDING))]

RRC: DOWNLINK DIRECT TRANSFER(CC: CALL PROCEEDING(DCH: DCCH))

SCCP (CO): DT1[RANAP(DIRECT TRANSFER(TMSI REALLOCATION COMMPLETE))]

RRC: UPLINK DIRECT TRANSFER(MM: TMSI REALLOCATION COMPLETE(DCH: DCCH))

Fig.2-1 Call Origination from CS (3/4)

2-55 Pages

Fig. 2-1 Call Origination from CS (4/4)

Node B MSCUE RNC

RRC: RADIO BEARER SETUPCOMPLETE(DCH: DCCH)

RRC: RADIO BEARERSETUP(DCH: DCCH)

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(ALERTING))]

mtype 6,81SCCP(CO): DT1[RANAP(RAB ASSIGNMENT RESPONSE)]

RRC: DOWNLINK DIRECT TRANSFER(CC: ALERTING(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CONNECT))]

RRC: DOWNLINK DIRECT TRANSFER(CC: CONNECT(DCH: DCCH))

RRC: UPLINK DIRECT TRANSFER(CC: CONNECT ACKNOWLEDGE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CONNECT ACKNOWLEDGE))]

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 3MTC CS Related

(Call Termination to CS)

A50016-G5000-F201-1-7618 MTC CS RelatedND-57172-704 (E)-01 (Call Termination to CS)

3. MTC CS Related (Call Termination to CS)

Fig. 3-1 shows a message sequence of the call termination to Circuit Switched (CS) network.

• mtype 111Number of CN originated pagings type 1 per paging cause (IDLE/PCH)

Node B MSCUE RNC

Fig. 3-1 Call Termination to CS (1/4)

mtype 1

mtype82, 102, 103, 221

SCCP(CL): UDT [RANAP (PAGING)]

RRC: RRC PAGING TYPE1 (PCH: PCCH)

The following is the same sequence as callorigination except for DIRECT TRANSFER (CC:)messages, basically.

mtype 111

mtype 104

Node B MSCUE RNC

RRC: UPLINK DIRECT TRANFER(MM: AUTHENTICATION RESPONSE(DCH: DCCH))

RRC: DOWNLINK DIRECT TRANFER(MM: AUTHENTICATION REQUEST(DCH: DCCH))

mtype 2

RRC: INITIAL DIRECT TRANSFER(MM: PAGING RESPONSE (DCH:DCCH))

mtype 161

SCCP(CO): CR [RANAP(INITIAL UE MESSAGE(PAGING RESPONSE))]

RRC: RRC CONNECTIONSETUPCOMPLETE(DCH:DCCH)

RRC: RADIO BEARER SETUP(DCH: DCCH)

Node B MSCUE RNC

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(SETUP))]

RRC: DOWNLINK DIRECT TRANSFER(CC: SETUP(DCH: DCCH))

RRC: UPLINK DIRECT TRANSFER(CC: CALL CONFIRM(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CALL CONFIRM))]

SCCP(CO): DT1[RANAP(RAB ASSIGNMENT REQUEST)]mtype 5, 115

QAAL2(Iu): ESTABLISH RESPONSE

mtype82, 102, 221

3-55 Pages

Node B MSCUE RNC

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(ALERTING))]

mtype 6,81SCCP(CO): DT1[RANAP(RAB ASSIGNMENT RESPONSE)]

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CONNECT))]

RRC: UPLINK DIRECT TRANSFER(CC: CONNECT(DCH: DCCH))

RRC: DOWNLINK DIRECT TRANSFER(CC: CONNECT ACKNOWLEDGE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(CONNECT ACKNOWLEDGE))]

RRC: UPLINK DIRECT TRANSFER(CC: ALERTING(DCH: DCCH))

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 4CS Call Release

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 CS Call Release

4. CS Call Release

4.1 UE-Initiated Call Release

Fig. 4-1 shows a message sequence of the UE-initiated call release.

• mtype 31Number of successful outgoing hard handovers per handover type (Intra-Node B)Number of successful outgoing hard handovers per handover type (Inter-Node B/Intra-RNC)Number of successful outgoing hard handovers per handover type (Inter-RNC)Number of successful outgoing hard handovers per handover type (Inter-RAT)

• mtype 177Number of successful outgoing inter-system handovers per adjacent cell pair

Node B MSCUE RNC

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(RELEASE))]

RRC: DOWNLINK DIRECT TRANFER(CC: RELEASE(DCH: DCCH))

RRC: UPLINK DIRECT TRANFER(CC: RELEASE COMPLETE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(RELEASE COMPLETE))]

RRC: UPLINK DIRECT TRANFER(CC: DISCONNECT(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(DISCONNECT))]

mtype31, 115, 177, 186

mtype 159

mtype 82

For DCCHQAAL2(Iub):RELEASE CONFIRM

For DTCH

Fig. 4-1 UE-Initiated Call Release (1/2)

Node B MSCUE RNC

QAAL2(Iu): RELEASE REQUEST

QAAL2(Iu): RELEASE CONFIRM

SCCP(CO): RLSD

SCCP(CO): RLC

4.2 Network-Initiated Call Release

Fig. 4-2 shows a message sequence of the network-initiated call release.

Node B MSCUE RNC

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(RELEASE))]

RRC: UPLINK DIRECT TRANFER(CC: RELEASE)(DCH: DCCH))

RRC: UPLINK DIRECT TRANFER(CC: RELEASE COMPLETE(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(RELEASE COMPLETE))]

RRC: DOWNLINK DIRECT TRANFER(CC: DISCONNECT(DCH: DCCH))

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(DISCONNECT))]

mtype31, 115, 177, 186

mtype 159

mtype 82

For DCCHQAAL2(Iub):RELEASE CONFIRM

For DTCH

Fig. 4-2 Network-Initiated Call Release (1/2)

4-66 Pages

Fig. 4-2 Network-Initiated Call Release (2/2)

Node B MSCUE RNC

SCCP(CO): RLSD

SCCP(CO): RLC

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 5MOC PS Related

(Call Origination from PS)

A50016-G5000-F201-1-7618 MOC PS RelatedND-57172-704 (E)-01 (Call Origination from PS)

5. MOC PS Related (Call Origination from PS)

Fig. 5-1 shows a message sequence of the call origination from Packet Switched (PS) network.

Node BUE RNC

Fig. 5-1 Call Origination from PS (1/3)

RRC: RRC CONNECTIONSETUP (FACH:CCCH)

mtype 1

mtype82, 102, 103, 221

mtype 2

RRC: MEASUREMENTCONTROL (DCH: DCCH)

mtype 104

Node BUE RNC

SCCP(CO): CR [RANAP (INITIAL UE MESSAGE(SERVICE REQUEST(TYPE=SIGNALING)))]

mtype 161

RRC: INITIAL DIRECT TRANSFER(GMM: SERVICE REQUEST(TYPE=SIGNALING)(DCH:DCCH))

RRC: DOWNLINK DIRECT TRANFER(GMM: AUTHENTICATION AND CIPHERING REQUEST(DCH: DCCH))

RRC: UPLINK DIRECT TRANFER(GMM: AUTHENTICATION AND CIPHERING RESPONSE(DCH: DCCH))

5-44 Pages

Node BUE RNC SGSN

mtype 82

SCCP(CO): DT1[RANAP(DIRECT TRANSFER)ACTIVATE PDP CONTEXT ACCEPT))]

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(ACTIVATE PDP CONTEXT REQUEST))]

SCCP(CO): DT1[RANAP(RAB ASSIGNMENT REQUEST)]

mtype 5

mtype 102,221,82

SCCP(CO): DT1[RANAP(RAB ASSIGNMENT RESPONSE)]

mtype 6, 81

RRC: MEASUREMENT CONTROL(DCH: DCCH)For Traffic Volume

RRC: UPLINK DIRECT TRANFER(SM: ACTIVATE PDP CONTEXT REQUEST(DCH: DCCH))

RRC: DOWNLINK DIRECT TRANSFER(SM: ACTIVATE PDP CONTEXT ACCEPT(DCH: DCCH))

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 6MTC PS Related

(Call Termination to PS)

A50016-G5000-F201-1-7618 MTC PS RelatedND-57172-704 (E)-01 (Call Termination to PS)

6. MTC PS Related (Call Termination to PS)

Fig. 6-1 shows a message sequence of the call termination to Packet Switched (PS) network.

• mtype 111Number of CN originated pagings type 1 per paging cause (IDLE/PCH)

Node BUE RNC

Fig. 6-1 Call Termination to PS (1/4)

RRC: RRC CONNECTIONSETUP (FACH:CCCH)

mtype 1

mtype82, 102, 103, 221

mtype 2

RRC: MEASUREMENT CONTROL (DCH: DCCH)

The following is the same sequence ascall origination except the DIRECTTRANSFER(CC:) messages, basically.

mtype 111RRC: PAGING TYPE1 (PCH: PCCH)

SCCP(CL): UDT[RANAP(PAGING)]

mtype 104

Node BUE RNC

SCCP(CO): CR [RANAP (INITIAL UE MESSAGE(SERVICE REQUEST(TYPE=SIGNALING)))]

mtype 161

RRC: INITIAL DIRECT TRANSFER (GMM: SERVICE REQUEST(TYPE=SIGNALING)(DCH:DCCH))

RRC: DOWNLINK DIRECT TRANFER(GMM: AUTHENTICATION AND CIPHERING REQUEST(DCH: DCCH))

RRC: UPLINK DIRECT TRANFER(GMM: AUTHENTICATION AND CIPHERING RESPONSE(DCH: DCCH))

Node BUE RNC SGSN

mtype82

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(ACTIVATE PDP CONTEXT REQUEST))]

SCCP(CO): DT1[RANAP(RAB ASSIGNMENT REQUEST)]

mtype 5

mtype 102,221,82

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(REQUEST PDP CONTEXT ACTIVATION))]

RRC: DOWNLINK DIRECT TRANFER(SM: REQUEST PDP CONTEXT ACTIVATION(DCH: DCCH))

RRC: UPLINK DIRECT TRANFER(SM: ACTIVATE PDP CONTEXT REQUEST(DCH: DCCH))

6-55 Pages

Node BUE RNC SGSN

SCCP(CO): DT1[RANAP(DIRECT TRANSFER)ACTIVATE PDP CONTEXT ACCEPT))]

mtype 6, 81

RRC: MEASUREMENT CONTROL(DCH: DCCH)For Traffic Volume

RRC: DOWNLINK DIRECT TRANSFER(SM: ACTIVE PDP CONTEXT ACCEPT(DCH: DCCH))

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 7PS Call Release

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 PS Call Release

7. PS Call Release

7.1 UE-Initiated Call Release

Fig. 7-1 shows a message sequence (on Cell_DCH) of the UE-initiated call release.

Node BUE RNC SGSN

mtype 82

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(DEACTIVATE PDP CONTEXT REQUEST))]

SCCP(CO): DT1[RANAP(IU RELEASE COMMAND)]mtype 31, 115,

177, 186

mtype 159

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(DEACTIVATE PDP CONTEXT ACCEPT))]

RRC: UPLINK DIRECT TRANFER(SM: DEACTIVATE PDP CONTEXT REQUEST(DCH: DCCH))

RRC: DOWNLINK DIRECT TRANFER(SM: DEACTIVATE PDP CONTEXT ACCEPT(DCH: DCCH))

Node BUE RNC SGSN

SCCP(CO): RLSD

SCCP(CO): RLC

For DCCH

For DTCH

7.2 RNC-Initiated Call Release

Fig. 7-2 shows a message sequence (on Cell_DCH) of the RNC-initiated call release.

• mtype 112Number of UTRAN originated pagings type 1 in CELL_PCH per paging cause

• mtype 114Number of UTRAN initiated RAB releases per release cause

• mtype 160Number of attempted RRC connection releases on CCCH per release cause

• mtype 167Number of cell updates per update cause

• mtype 168Number of incoming cell updates per update cause per adjacent cell pair

• mtype 185Number of Iu release requests per release cause

7-55 Pages

Fig. 7-2 RNC-Initiated Call Release

Node BUE RNC SGSN

mtype 112

mtype167, 168

RRC: RRC CONNECTIONRELEASE (FACH: CCCH)

mtype 160

SCCP(CO): RLSD

SCCP(CO): RLC

SCCP(CO): DT1[RANAP(IU RELEASE REQUEST)]

RRC: PAGING TYPE 1(PCH: PCCH)

RRC: CELL UPDATE(RACH: CCCH)

mtype 31, 115,177, 186

mtype 114

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 8Intra-Node B Handover

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Intra-Node B Handover

8. Intra-Node B Handover

8.1 Radio Link Addition

Fig. 8-1 shows a message sequence of the radio link addition in the intra-Node B handover procedure.

• mtype 17Number of drifting UEs (adjacent RNC)

• mtype 34Number of attempted intra Node B branch additions per addition cause

• mtype 36Number of successful intra Node B branch additions per addition cause

• mtype 46Number of attempted intra RNC branch additions per addition cause

• mtype 48Number of successful intra RNC branch additions per addition cause

• mtype 170Number of attempted outgoing radio link addition movements per adjacent cell

• mtype 171Number of successful outgoing radio link addition movements

per adjacent cell

• mtype 205Number of UEs per active link set size

Fig. 8-1 Radio Link Addition

RRC: ACTIVE SET UPDATE(DCH: DCCH)

NBAP: RADIO LINKADDITION RESPONSE

NBAP: RADIO LINKADDITION REQUEST

Node BUE RNC

mtype46, 34, 170

RRC: ACTIVE SET UPDATECOMPLETE(DCH: DCCH) mtype

17, 36, 48, 171

mtype82, 102, 103, 221

RRC: MEASUREMENT REPORT(DCH: DCCH)

mtype 205

mtype 104

8.2 Radio Link Deletion

Fig. 8-2 shows a message sequence of the radio link deletion in the intra-Node B handover procedure.

• mtype 38Number of attempted branch deletions per deletion cause

• mtype 50Number of successful branch deletions per deletion cause

Fig. 8-2 Radio Link Deletion

Node BUE RNC

mtype 38

RRC: ACTIVE SET UPDATECOMPLETE(DCH: DCCH)

mtype 82

mtype 17, 50

mtype 205

8.3 Radio Link Addition - Failure

Fig. 8-3 shows a failed message sequence of the radio link addition -failure in the intra-Node B handover procedure.

• mtype 34Number of attempted intra Node B branch additions per addition cause

• mtype 35Number of unsuccessful intra Node B branch additions per failure cause

• mtype 47Number of unsuccessful intra RNC branch additions per failure cause

• mtype 172Number of failed outgoing radio link addition movements per failure cause per adjacent cell

Node BUE RNC

RRC: ACTIVE SET UPDATEFAILURE(DCH: DCCH) mtype

35, 47, 172

RRC: CONNECTION RELEASE (DCH:DCCH)

RRC: CONNECTION COMPLETE (DCH:DCCH)

mtype 159

mtype 82

CS, UDI

mtype 185

mtype 186, 81

SCCP (CO): DT1[RANAP(IU RELEASE REQUEST)]

SCCP (CO): DT1[RANAP(IU RELEASE COMMAND)]

mtype 185

mtype 186, 81

mtype34, 46, 170

mtype82, 102, 103, 221

mtype 82(For 2nd RL Deletion)

Fig. 8-3 Radio Link Addition - Failure (1/2)

mtype 104

8-99 Pages

Node BUE RNC SGSN MSC

QAAL2 (Iu): RELEASE REQUEST

QAAL2 (Iu): RELEASE CONFIRM

SCCP (CO): DT1[RANAP(IU RELEASE COMPLETE)]

SCCP (CO): RLSD

SCCP (CO): RLC

SCCP (CO): RLSD

SCCP (CO): RLC

CS, UDI

QAAL2 (Iub):RELEASE REQUEST

QAAL2 (Iub):RELEASE CONFIRM

For DCCH

For DTCH

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 9Inter-Node B Handover

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Inter-Node B Handover

9. Inter-Node B Handover

Fig. 9-1 shows a message sequence of the radio link addition in the inter-Node B handover procedure.

• mtype 171Number of successful outgoing radio link addition movements per adjacent cell

Fig. 9-1 Radio Link Addition

Node BUE RNC

mtype46, 170

RRC: ACTIVE SET UPDATECOMPLETE(DCH: DCCH) mtype

17, 48, 171

mtype82, 102, 103, 221

mtype 104

Fig. 9-2 shows a message sequence of the radio link deletion in the inter-Node B handover procedure.

Node BUE RNC

mtype 38

mtype 82

mtype 17, 50

9.3 Radio Link Addition - Failure

Fig. 9-3 shows a failed message sequence of the radio link addition -failure in the inter-Node B handover procedure.

• mtype 47Number of unsuccessful intra RNC branch additions per failure cause

• mtype 172Number of failed outgoing radio link addition movements per failure cause per adjacent cell

UE RNC

mtype46, 170

mtype 47 (172)

Node B112

CS, UDI

mtype 185

mtype186(81)

mtype 185

mtype186(81)

QAAL2(Iub):

mtype82, 102, 103, 221

SGSN MSCNode B111

mtype 104

ESTABLISH REQUEST

ESTABLISH CONFIRM

RRC: ACTIVE SET UPDATEFAILURE(DCH: DCCH)

9-77 Pages

UE RNCNode B111

QAAL2 (Iu): RELEASE REQUEST

QAAL2 (Iu): RELEASE CONFIRM

SCCP (CO): RLSD

SCCP (CO): RLC

SCCP (CO): RLSD

SCCP (CO): RLC

SGSN MSC

CS, UDI

mtype 159

RRC: RRC CONNECTIONRELEASE (DCH: DCCH)

RRC: RRC CONNECTIONCOMPLETE (DCH: DCCH)

mtype 82

Node B112

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 10Inter-RNC Handover

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Inter-RNC Handover

10. Inter-RNC Handover

Fig. 10-1 shows a message sequence of the radio link addition in the inter-RNC handover procedure.

• mtype 58Number of attempted inter RNC branch additions per addition cause

• mtype 59Number of successful inter RNC branch additions per addition cause

• mtype 171Number of successful outgoing radio link addition movements per adjacent cell

SCCP(CO): CR[RNSAP(none)]

Node B111

UE RNC11 RNC12

SCCP(CO): CR[RNSAP(none)]

Node B112

SCCP(CO): DT1[RNSAP(RADIO LINK SETUP REQUEST)]

QAAL2(Iur):ESTABLISH CONFIRM

QAAL2(Iur):ESTABLISH REQUEST

For Outer LoopPower Control

mtype82, 102, 103, 221

SCCP(CO): DT1[RNSAP(RADIO LINK SETUP RESPONSE)]

SCCP(CO): DT1[RNSAP(DEDICATED MEASUREMENT INITIATION REQUEST)]

Fig. 10-1 Radio Link Addition (1/2)

mtype46, 58, 170

mtype 104

Fig. 10-1 Radio Link Addition (2/2)

Node B111

UE RNC11 RNC12Node B112

SCCP(CO): DT1[RNSAP(RADIO LINK RESTORE INDICATION)]

SCCP(CO): DT1[RNSAP

mtype17, 48, 59, 171

(DEDICATED MEASUREMENT INITIATION RESPONSE)]

Fig. 10-2 shows a message sequence of the radio link deletion in the inter-RNC handover procedure.

10-66 Pages

Node B111

UE RNC11

QAAL2(Iub): RELEASE CONFIRM

QAAL2(Iub): RELEASE REQUEST

SCCP(CO): RLSD

SCCP(CO): RLC

RRC: ACTIVE SET UPDATE(DCH: DCCH)mtype 38

mtype17, 50

mtype 82

Node B112

SCCP(CO): DT1[RNSAP(RADIO LINK DELETION REQUEST)]

SCCP(CO): DT1[RNSAP(RADIO LINK DELETION RESPONSE)]

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 11Inter-Frequency Handover

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Inter-Frequency Handover

11. Inter-Frequency Handover

Fig. 11-1 shows a message sequence of the inter-frequency handover procedure.

• mtype 27Number of attempted outgoing hard handovers per adjacent cell pair

• mtype 28Number of successful outgoing hard handovers per adjacent cell pair

• mtype 29Number of unsuccessful outgoing hard handovers per adjacent cell per failure cause

• mtype 30Number of attempted outgoing hard handovers per handover type (Intra-Node B)Number of attempted outgoing hard handovers per handover type (Inter-Node B/Intra-RNC)Number of attempted outgoing hard handovers per handover type (Inter-RNC)Number of attempted outgoing hard handovers per handover type (Inter-RAT)

• mtype 32Number of unsuccessful outgoing hard handovers per handover type per failure cause (Intra-Node B)Number of unsuccessful outgoing hard handovers per handover type per failure cause (Inter-Node B/Intra-RNC)Number of unsuccessful outgoing hard handovers per handover type per failure cause (Inter-RNC)

Number of unsuccessful outgoing hard handovers per handover type per failure cause (Inter-RAT)

• mtype 105Number of radio link failures per failure cause

• mtype 164Number of attempted physical channel reconfigurations

• mtype 165Number of successful physical channel reconfigurations

mtype27, 30, 164

RRC: PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE(DCH: DCCH)

RRC: PHYSICAL CHANNELRECONFIGURATION(DCH: DCCH)

NBAP: RADIO LINKFAILURE INDICATION

RNSAP: RADIO LINKFAILURE INDICATION

mtype28, 29, 31, 32, 165

Fig. 11-1 Inter-Frequency Handover (1/2)

UENode B111

Node B112

RNC11Node B121

mtype82, 102, 103, 221

mtype 105

mtype 82

end ofcoverage

Node B111

Node B112

RNC12(DRNC)

Node B121

RNC11(SRNC)

freq 2

freq 1

UEsame

antennaend of

coverage

Node B111

Node B112

Node B121

freq 2

freq 1

UEsameantenna

RNC12RNC11(SRNC)

mtype 104

11-44 Pages

Fig. 11-1 Inter-Frequency Handover (2/2)

end ofcoverage

SCCP(CO): RLSD

SCCP(CO): RLC

Node B111

Node B112

RNC12(DRNC)

Node B121

RNC11(SRNC)

freq 2

freq 1

UEsame

antenna

Node B111

Node B112

Node B121

RNC11(SRNC)

freq 2

freq 1

UEsame

antenna

QAAL2(Iur): RELEASE REQUEST

QAAL2(Iur): RELEASE CONFIRM

mtype 205

mtype 82

UENode B112

Node B121

end ofcoverage

SCCP(CO): DT1[RNSAP(RADIO LINK DELETION REQUEST)]

SCCP(CO): DT1[RNSAP(RADIO LINK DELETION RESPONSE)]

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 12Relocation

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Relocation

12. Relocation

Fig. 12-1 shows a message sequence of the relocation.

• mtype 180Number of attempted outgoing relocation preparations per relocation cause per relocation type (per intra/inter PLMN)

• mtype 182Number of successful outgoing relocation preparations per relocation cause per relocation type (per intra/inter PLMN)

• mtype 183Number of attempted incoming relocations per relocation cause

• mtype 184Number of successful incoming relocations per relocation cause

Fig. 12-1 Relocation (1/2)

UE RNC11

mtype 180

(GTP-C: FORWARDRELOCATION REQUEST)

SCCP(CO): DT1[RANAP(RELOCATION REQUIRED)]

SGSN2 RNC21

mtype 167

SCCP(CO):CR[RANAP(none)]

SCCP(CO):CC[RANAP(none)]

SCCP(CO): DT1[RANAP(RELOCATION REQUEST)]

mtype 183

SCCP(CO): DT1[RANAP(RELOCATION REQUEST ACKNOWLEDGE)]

mtype 184

(GTP-C: FORWARDRELOCATION RESPONSE)

SCCP(CO): DT1[RANAP(RELOCATION COMMAND)]

mtype 182This is counted uponreceiving theRELOCATON COMMAND.

SCCP(CL): UDT[RNSAP(RELOCATION COMMIT)]

FORWARDING OF DATA

SCCP(CO): DT1[RANAP(RELOCATION DETECT)]

SCCP(CL): UDT[RNSAP(UPLINK SIGNALING TRANSFER INDICATION)]

12-33 Pages

Fig. 12-1 Relocation (2/2)

UE SGSN1

mtype186, 81

(GTP-C: FORWARDRELOCATION COMPLETE)

SGSN2 RNC21

RRC: DOWNLINK DIRECT TRANSFER(FACH: DCCH)

(GTP-C: FORWARD RELOCATIONCOMPLETE ACKNOWLEDGE)

SCCP(CO): RLSD

SCCP(CO): RLC

(UPDATE PDPCONTEXT REQUEST)

(UPDATE PDP CONTEXTRESPONSE)

RRC: RADIO BEARER RECONFIGURATION(RACH: DCCH)

SCCP(CO): DT1[RANAP(RELOCATION COMPLETE)]

RRC: CELL UPDATE CONFIRM(FACH: CCCH)

RRC: MEASUREMENT CONTROL(FACH: DCCH)

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 13Inter-System Handover

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Inter-System Handover

13. Inter-System Handover

13.1 From UMTS to GSM

Fig. 13-1 shows a message sequence of the inter-system handover (from UMTS to GSM).

• mtype 30Number of attempted outgoing hard handovers per handover type (Inter-RAT)

• mtype 31Number of successful outgoing hard handovers per handover type (Inter-RAT)

• mtype 173Number of attempted relocation preparations for outgoing inter-system handovers per adjacent cell pair

• mtype 175Number of attempted outgoing inter-system handovers per adjacent cell pair

• mtype 180Number of attempted outgoing relocation preparations per relocation cause per relocation type (per intra/inter PLMN)

• mtype 182Number of successful outgoing relocation preparations per relocation cause per relocation type (per intra/inter PLMN)

Fig. 13-1 From-UMTS-to-GSM Handover

Node B

UE MSC

mtype 82

SCCP(CO): RLSD

SCCP(CO): DT1[RANAP(RELOCATION REQUIRED)]

mtype173, 180

mtype30, 175

RRC: HANDOVER FROM UTRANCOMMAND(DCH: DCCH)

SCCP(CO): RLC

SCCP(CO): DT1[RANAP(RELOCATION COMMAND)]

mtype 182

mtype31, 115, 177

13.2 From UMTS to GPRS

Fig. 13-2 shows a message sequence of the inter-System handover (from UMTS to GPRS).

Fig. 13-2 From-UMTS-to-GPRS Handover

Node BUE MSC

SCCP(CO): RLSD

SCCP(CO): DT1[RANAP(SRNS CONTEXT REQUEST)]

SCCP(CO): RLC

SCCP(CO): DT1[RANAP(SRNS CONTEXT RESPONSE)]

mtype31, 115, 177

CELL_FACH,CELL_PCH,or URA_PCH

13.3 From UMTS to GPRS(PS)

Fig. 13-3 shows a message sequence of the inter-System handover (from UMTS to GPRS) of PS call on Cell_DCH.

• mtype 175Number of attempted outgoing inter-system handovers per adjacent cell pair

Fig. 13-3 From-UMTS-to-GPRS(PS) Handover

Node BUE SGSN

SCCP(CO): RLSD

SCCP(CO): DT1[RANAP(SRNS CONTEXT REQUEST)]

SCCP(CO): RLC

SCCP(CO): DT1[RANAP(SRNS CONTEXT RESPONSE)]

mtype31, 115, 177

PS CELL_DCH Single Call

RRC: MEASUREMENT REPORT

(DCH:DCCH AM) (Event:3A)

RRC: CELL CHARGE ORDER

FROM UTRAN (DCH:DCCH AM)

mtype 175

mtype 82

13.4 From GSM to UMTS

Fig. 13-4 shows a message sequence of the inter-System handover (from GSM to UMTS).

• mtype 179Number of successful incoming CS inter RAT handovers

13-88 Pages

Fig. 13-4 From-GSM-to-UMTS Handover

Node B MSCUE RNC

mtype 179

RRC: HANDOVER TO UTRANCOMPLETE(DCH: DCCH AM)

SCCP(CO): CR [RANAP(none)]

mtype 82, 102, 103, 221

mtype 104

SCCP(CO): CC [RANAP(none)]

SCCP(CO): DT1 [RANAP(RELOCATION REQUEST)]

QAAL2(Iu): ESTABLISH CONFIRM

SCCP(CO): DT1 [RANAP(RELOCATION ACKNOWLEDGE)]

SCCP(CO): DT1 [RANAP(RELOCATION DETECT)]

SCCP(CO): DT1 [RANAP(RELOCATION COMPLETE)]

RRC: UTRAN MOBILITY INFORMATION(DCH: DCCH UM)

RRC: UTRAN MOBILITY INFORMATIONCONFIRM(DCH: DCCH AM)

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 14Inter-Node Connection

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Inter-Node Connection

14. Inter-Node Connection

14.1 NG Occurrence after Receiving RANAP: RAB Assignment Request at RAB Establishment

Fig. 14-1 shows a CS semi-normal message sequence of the NG occurrence after receiving RANAP: RAB assignment request at RAB establishment in the inter-node connection.

• mtype 109Number of unsuccessful RAB establishments per failure cause

• mtype 186

Number of Iu release commands per release cause

Node B MSCUE RNC

mtype 1

mtype82, 102, 103, 221

mtype 2

Fig. 14-1 NG Occurrence after Receiving RANAP: RAB Assignment Request (1/3)

INITIATION RESPONSE

INITIATION REQUEST

INITIATION RESPONSE

INITIATION REQUEST

mtype 104

NBAP: DEDICATED MEASUREMENT

RRC: INITIAL DIRECT TRANSFER(MM: CM SERVICE REQUEST(DCH:DCCH))

Node B MSCUE RNC

RRC: SECURITY MODECOMMAND (DCH: DCCH)

RRC: UPLINK DIRECT TRANSFER(CC: SETUP (DCH: DCCH))

SCCP (CO): DT1 [RANAP (SECURITY MODE COMPLETE)]

RRC: SECURITY MODECOMPLETE (DCH: DCCH)

SCCP (CO): DT1 [RANAP (DIRECT TRANSFER (SETUP))]

SCCP (CO): DT1 [RANAP (DIRECT TRANSFER(CALL PROCEEDING))]

RRC: DOWNLINK DIRECT TRANSFER(CC: CALL PROCEEDING(DCH: DCCH))

SCCP (CO): DT1 [RANAP (RAB ASSIGNMENT REQUEST)]NG occurrencepoint:due toabnormal messagereception orinternal resourceshortage

mtype 161

SCCP(CO): CR[RANAP(INITIAL UE MESSAGE(CM SERVICE REQUEST))]

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION REQUEST))]

SCCP(CO): DT1[RANAP(DIRECT TRANSFER(AUTHENTICATION RESPONSE))]

SCCP(CO): DT1[RANAP(COMMAND ID)]

SCCP(CO): DT1[RANAP(SECURITY MODE COMMAND)]

RRC: DOWNLINK DIRECT TRANSFER(MM: AUTHENTICATION REQUEST (DCH: DCCH))

RRC: UPLINK DIRECT TRANSFER(MM: AUTHENTICATION RESPONSE (DCH: DCCH))

Node B MSCUE RNC

mtype 185SCCP (CO): DT1 [RANAP (IU RELEASE REQUEST)]

SCCP (CO): DT1 [RANAP (IU RELEASE COMMAND)]mtype186, 81

RRC: RRC CONNECTIONRELEASE (DCH: DCCH)

mtype 159

RRC: RRC CONNECTIONCOMPLETE (DCH: DCCH)

mtype 82

SCCP (CO): DT1 [RANAP (IU RELEASE COMPLETE)]

SCCP (CO): DT1 [RANAP (RAB ASSIGNMENT RESPONSE)]mtype 109

14.2 Racing of NBAP_RLFailureInd Reception for Waiting for ALCAP Establish Confirm

Fig. 14-2 shows a CS semi-normal message sequence of the racing of NBAP_RLFailureInd reception for waiting for ALCAP Establish Confirm in the inter-node connection.

• mtype 105Number of radio link failures per failure cause

• mtype 107Number of failed RRC connection establishments per failure cause

Fig. 14-2 Racing of NBAP_RLFailureInd Reception

Node BUE RNC

mtype 1

mtype82, 102, 103, 221

NBAP: RADIO LINKFAILURE INDICATION

mtype 105

RRC: RRC CONNECTIONREJECT(PACT: CCCH)

mtype 107

QAAL2 (Iub):RESET REQUEST

mtype 82

QAAL2 (Iub):RESET CONFIRM

mtype 104

14.3 Racing of RRC_SigConnRelInd Reception after RRC_RRCConnSetupComp

Fig. 14-3 shows a CS semi-normal message sequence of the racing of RRC_SigConnRelInd reception after RRC_RRConnSetupComp in the inter-node connection.

• mtype 162Number of signaling connection release requests

Node BUE RNC

mtype 1

mtype82, 102, 103, 221

mtype 2

INITIATION RESPONSE

INITIATION REQUEST

INITIATION RESPONSE

mtype 162

INITIATION REQUEST

Fig. 14-3 Racing of RRC_SigConnRelInd Reception (1/2)

mtype 104

NBAP: DEDICATED MEASUREMENT

RRC: SIGNALING CONNECTION RELEASEINDICATION (DCH:DCCH)

Fig. 14-3 Racing of RRC_SigConnRelInd Reception (2/2)

Node BUE RNC

mtype 159

QAAL2 (Iub):RESET REQUEST

mtype 82

QAAL2 (Iub):RESET CONFIRM

14.4 NG Occurrence after Receiving ALCAP: Establish Confirm (Iub) at RAB Establishment

Fig. 14-4 shows a CS semi-normal message sequence of the NG occurrence after Receiving ALCAP: Establish Confirm (Iub) at RAB Establishment in the inter-node connection.

The following measurement type is used in the sequence:

• mtype 109Number of unsuccessful RAB establishments per failure cause

• mtype 114Number of UTRAN initiated RAB releases per release cause

Fig. 14-4 NG Occurrence after Receiving ALCAP: Establish Confirm (Iub)

Node B MSCUE RNC

mtype 109

SCCP(CO): DT1[RANAP(IU RELEASE REQUEST)]

For DCCH

For DTCH

SCCP(CO): RLSD

SCCP(CO): RLC

mtype 114

mtype31, 115, 177

RRC: RRC CONNECTION RELEASE(DCH:DCCH)

RRC: RRC CONNECTION RELEASECOMPLETE(DCH:DCCH)

14.5 RRC ConnectionSetupComplete Wait Time-out

Fig. 14-5 shows a PS semi-normal message sequence of the RRC ConnectionSetupComplete Wait Time-out in the inter-node connection.

• mtype 107Number of failed RRC connection establishments per failure cause

14-1414 Pages

Fig. 14-5 RRC ConnectionSetupComplete Wait Time-out

Node BUE RNC

RRC: RRC CONNECTIONREJECT (FACH:CCCH)

mtype 107

RRC: RRC CONNECTION SETUP COMPLETE Wait Time-out

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 15Cell Update

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Cell Update

15. Cell Update

Fig. 15-1 shows a message sequence of the cell update.

• mtype 168Number of incoming cell updates per update cause per adjacent cell pair

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Cell Update

15-22 Pages

Fig. 15-1 Cell Update

Node BUE RNC SGSN

mtype167, 168

RRC: CELL UPDATE CONFIRM(FACH: CCCH)

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 16URA Update

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 URA Update

16. URA Update

Fig. 16-1 shows a message sequence of the URA update.

• mtype 169Number of URA updates per update cause

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 URA Update

16-22 Pages

Fig. 16-1 URA Update

Node BUE RNC SGSN

mtype 169

RRC: URA UPDATE(RACH: CCCH)

RRC: URA UPDATE CONFIRM(FACH: CCCH)

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 17Common Measurement

Report Reception

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Common Measurement Report Reception

17. Common Measurement Report Reception

Fig. 17-1 shows a message sequence of the common measurement report reception.

• mtype 99Transmitted carrier power

• mtype 206Received total wide band power

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Common Measurement Report Reception

17-22 Pages

Fig. 17-1 Common Measurement Report Reception

Node BUE RNC SGSN

NBAP: COMMONMEASUREMENT REPORT mtype

206, 99

A50016-G5000-F201-1-7618ND-57172-704 (E)-01

SECTION 18Abbreviation List

A50016-G5000-F201-1-7618ND-57172-704 (E)-01 Abbreviation List

18. Abbreviation List

Abbreviation Meaning

ALCAP Access Link Control Application Part

CC Connection Confirm

CCCH Common Control Channel

CE Channel Element

CGI Cell Global ID

CL Connectionless

CM Configuration Management

CO Connection Oriented

CR Connection Request

CS Circuit Switched

DCCH Dedicated Control Channel

DCH Dedicated Channel

DHT Diversity Handover Trunk

DL Downlink

DRNC Drift Radio Network Controller

DT1 Data Type 1

DTCH Dedicated Traffic Channel

EDGE Enhanced Data Rates for GSM Evolution

FACH Forward Link Access Channel

GERAN GSM/EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GMM GPRS Mobility Management

GPRS General Packet Radio Service

GSM Global System for Mobile Communications

GTP-C GPRS Tunneling Protocol - Control Plane

HHO Hard Handover

IU Interface Between an RNC and a Core Network

MEID managedElementId

MM Mobility Management

MOC Managed Object Class Mobile Originated Call

MSC Mobile-services Switching Center

MTC Mobile Terminated Call

mtype Measurement Type

NBAP Node B Application Part

PCCH Paging Control Channel

PCH Paging Channel

PDP Packet Data Protocol

PF Platform

PRACH Physical Random Access Channel

PRLC Packet for Radio Link Control

PS Packet Switched

PTI Protocol Type Identifier

QAAL2 ATM Adaptation Layer Type Signaling Protocol 2

QoS Quality of Service

RAB Radio Access Bearer

RACH Random Access Channel

RANAP Radio Access Network Application Part

RL Radio Link

RLC Release Complete

RLSD Released

RNC Radio Network Controller

RNS Radio Network System

RNSAP Radio Network Subsystem Application Part

RRC Radio Resource Control

18-33 Pages

RC Radio Commander

SCCP Signalling Connection Control Part

SCCPCH Secondary Common Control Physical Channel

SF Spreading Factor

SHO Soft Handover

SGSN Serving GPRS Support Node

SM Session Management

SRNC Source RNC

SRNS Serving Radio Network Subsystem

TMSI Temporary Mobile Subscriber Identity

UDI Unrestricted Digital Information

UDT User Data Transfer

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunications System

URA UTRAN Registration Area

UTRAN UMTS Terrestrial Radio Access Network

VC Virtual Channel

VCI Virtual Channel Identifier

VP Virtual Path

tedpmmf

Documents