l3 Message 2g

Information

System

PM:SBS Message Flows

A30808-X3247-M41-3-7618

2 A30808-X3247-M41-3-7618

PM:SBS Message Flows InformationSystem

f Important Notice on Product Safety

DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system mustcomply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components mayalso have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injuryor property damage.Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenenGeräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefährlicher Spannung. Einige Komponentenkönnen auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Körperverletzungen oderSachschäden führen.Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in tableA30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for aClass A digital device, pursuant to part 15 of the FCC Rules.These limits are designed to provide reasonable protection against harmful interference when the equipment isoperated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual “Guide to Documentation”, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments concerning construction rules and static load capacities of buildings and roofs.For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagneticfield / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for their own purposescould violate the rights of their owners.

Copyright (C) Siemens AG 2005.

Issued by the Communications GroupHofmannstraße 51D-81359 München

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

A30808-X3247-M41-3-7618 3

InformationSystem


Reason for UpdateSummary:

Third Edition for Release BR 8.0

Details:

Chapter / Section Reason for Update

All Minor changes

Issue HistoryIssue Date of Issue Reason for Update

1 01/2005 First Edition for New Release BR 8.0

2 04/2005 Second Edition for Release BR 8.0

3 07/2005 Third Edition for Release BR 8.0

4 A30808-X3247-M41-3-7618


A30808-X3247-M41-3-7618 5

InformationSystem


This document consists of a total of 236 pages. All pages are issue 3.

Contents

1 Performance Measurement Message Flows . . . . . . . . . . . . . . . . . . . . . . . 111.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.1 Call Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.1.1 Successful Mobile Originating Call (MOC), FR Call . . . . . . . . . . . . . . . . . . 121.2.1.2 Successful Mobile Terminating Call (MTC), FR Call. . . . . . . . . . . . . . . . . . 151.2.1.3 Successful Mobile Originating Call (MOC) with Direct Traffic Channel Assign-

ment, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.1.4 Successful (MOC) Using Early Classmark Sending, FR Call . . . . . . . . . . 201.2.1.5 Successful Mobile Terminating Call (MTC), Using Early Classmark, Sending,

FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.2.1.6 Successful Mobile Terminating Call (MTC) in busy mode, new waiting call

(feature “Call waiting”) is accepted by called subscriber. . . . . . . . . . . . . . . 261.2.1.7 Unsuccessful Mobile Originating Call (MOC), Subscriber B Busy, FR Call 281.2.1.8 Unsuccessful Mobile Originating Call (MOC), No TCH Available, FR Call . 291.2.1.9 Successful Mobile Originated Call (MOC) in a Concentric Cell (inner area), FR

Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.2.1.10 Successful Mobile Emergency Call (MEC), FR Call . . . . . . . . . . . . . . . . . . 321.2.2 Unsuccessful Assignment Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.2.2.1 Unsuccessful TCH Assignment Procedure with Reversion to SDCCH, FR Call

331.2.2.2 Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COM-

MAND (T10 < T_MSRFPCI), FR Call (T10 Expiry). . . . . . . . . . . . . . . . . . . 341.2.2.3 Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COM-

MAND (T10 > T_MSRFPCI), FR Call (T_MSRFPCI Expiry). . . . . . . . . . . . 351.2.2.4 Unsuccessful TCH Assignment Procedure LAPDm I-Frame with

ASSIGNMENT COMMAND not acknowledged by MS (T200 Expiry), FR Call36

1.2.3 Call Release Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371.2.3.1 Normal Call Release (Originated by MS), FR Call . . . . . . . . . . . . . . . . . . . 371.2.3.2 Normal Call Release (Originated by Network), FR Call . . . . . . . . . . . . . . . 381.2.3.3 Abnormal Call Release Procedure; Call drop: BTS sends CONNECTION

FAILURE INDICATION to the BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391.2.3.4 Abnormal Call Release Procedure; Call drop: BTS sends ERROR

INDICATION to the BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.2.3.5 Abnormal Call Release; BTS sends RELEASE INDICATION during a stable

call phase to the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441.2.4 Inter-Cell Handover, Intra-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451.2.4.1 Successful Inter-Cell Handover, Intra-BSC, FR Call. . . . . . . . . . . . . . . . . . 451.2.4.2 Unsuccessful Inter-Cell Handover Attempt, Intra-BSC, No TCH Available in

Target Cell, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471.2.4.3 Unsuccessful Inter-Cell Handover, Intra-BSC, with Reversion to Old TCH

(T3124 Expiry), FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481.2.4.4 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS (Loss of HO

CMD, T8<TTRAU), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6 A30808-X3247-M41-3-7618


1.2.4.5 Unsuccessful Inter-Cell Handover, Intra-BSC with Loss of MS (Loss of HOCMD, T8>TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . 52

1.2.4.6 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS, Handover Ac-cess Failure (No SABM after Transmission of PHYSICAL INFO, [(NY1+1) *T3105]<<T8<TTRAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

1.2.4.7 Successful Inter-Cell Handover (Intra-BSC) between Colocated ConcentricCells, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1.2.4.8 Successful Inter-Cell Handover, Intra-BTSE, Between Synchronized Cells, FRCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

1.2.4.9 Successful Inter-Cell Handover, Intra-BSC, MSC Controlled, FR Call . . . . 601.2.4.10 Successful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC . . . . . . . . . . . 621.2.4.11 Unsuccessful SDCCH-SDCCH Inter-Cell Handover Attempt, Intra-BSC, No

SDCCH Available in Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641.2.4.12 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC, with Loss of

MS (Loss of HO CMD, T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.2.5 Inter-Cell Handover, Inter-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671.2.5.1 Successful Inter-Cell Handover, Inter-BSC, FR Call . . . . . . . . . . . . . . . . . . 671.2.5.2 Unsuccsessful Inter-Cell Handover, Inter-BSC, No TCH Available in Target

Cell, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691.2.5.3 Unsuccessful Inter-Cell Handover, Inter-BSC, with Reversion to Old TCH, FR

Call (T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701.2.5.4 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO

CMD, T8<Trr7), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721.2.5.5 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO

CMD, T8>Trr7), FR Call (Trr7 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741.2.5.6 Unsuccessful Inter-Cell Handover, Inter-BSC, with Loss of MS, Handover Ac-

cess Failure (No SABM received after Transmission) of PHYSICAL INFO,[(NY1+1) * T3105]<<T8<TTRAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

1.2.5.7 Successful Inter-Cell Handover, Inter-BSC, No TCH Available in First (exter-nal) Cell, Second Target Cell Belongs to Originating BSC, FR Call . . . . . . 79

1.2.5.8 Successful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC . . . . . . . . . . . 811.2.5.9 Unsuccsessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC, No SDCCH

Available in Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831.2.5.10 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC with Loss of

MS (Loss of HO CMD, T8<Trr7, T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . 841.2.6 Intra-Cell Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861.2.6.1 Successful Intra-Cell Handover, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . 861.2.6.2 Unsuccessful Intra-Cell Handover Due to Quality, No TCH Available,

FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881.2.6.3 Unsuccessful Intra-Cell Handover Due to Quality with Reversion to Old TCH,

FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891.2.6.4 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD, T10 <

TTRAU), FR Call (T10 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911.2.6.5 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD,

T10>TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931.2.6.6 Successful Intra-Cell Handover Due to Quality, MSC Controlled, FR Call . 951.2.6.7 Successful SDCCH-SDCCH Intra-Cell Handover . . . . . . . . . . . . . . . . . . . . 971.2.7 Directed Retry, Intra-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991.2.7.1 Successful Directed Retry, Intra-BSC, FR Call . . . . . . . . . . . . . . . . . . . . . . 99

A30808-X3247-M41-3-7618 7

InformationSystem


1.2.7.2 Unsuccessful Directed Retry, Intra-BSC, No Target Cell Available, FR Call .101

1.2.7.3 Unsuccessful Directed Retry, Intra-BSC, 1 Target Cell Available, Target CellCongested, FR Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

1.2.7.4 Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH, FR Call(T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

1.2.7.5 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD,T8 < TTRAU), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

1.2.7.6 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD,T8 > TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . 107

1.2.8 Directed Retry, Inter-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091.2.8.1 Successful Directed Retry, Inter-BSC, FR Call . . . . . . . . . . . . . . . . . . . . . 1091.2.8.2 Unsuccessful Directed Retry, Inter-BSC, FR Call, no Radio Resource avail-

able in Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121.2.8.3 Unsuccessful Directed Retry, Inter-BSC, with Reversion to SDCCH, FR Call

(T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131.2.8.4 Unsuccessful Derected Entry, Inter-BSC, with Loss of MS (Loss of HO CMD,

T8 < Trr7), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161.2.8.5 Unsuccessful Directed Retry, Inter-BSC, with Loss of MS (Loss of HO CMD,

T8 > Trr7), FR Call (Trr7 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181.2.9 Forced Handover Due to O & M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201.2.9.1 Successful Forced Handover Due to O & M . . . . . . . . . . . . . . . . . . . . . . . 1201.2.9.2 Successful Forced Handover Due to O & M, Inter-BSC, FR Call . . . . . . . 1221.2.9.3 Successful Forced Intra-Cell Handover Due to O & M, FR Call . . . . . . . . 1241.2.10 Handover due to BSS Resource Management Criteria (Traffic Handover) 1251.2.10.1 Successful Handover due to BSS Resource Management Criteria (Traffic

Handover), FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251.2.10.2 Unsuccessful Inter-Cell Handover due to BSS Resource Management Criteria

(Traffic Handover), traffic load in Target Cell exceeds the threshold TRFLTH128

1.2.11 Queuing & Preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301.2.11.1 Queuing: Queued Assignment Request for FR TCH Is Served Before

T11 Expiry, Directed Retry Enabled But No Target Cell Available, PreemptionDisabled or Not Allowed for the Requesting Call . . . . . . . . . . . . . . . . . . . 130

1.2.11.2 Queuing: Queued Assignment Request for FR TCH is Discarded from theQueue Before T11 Expiry Due to an Incoming FR Assignment Request withHigher Priority Directed Retry Enabled But No Target Cell Available, Preemp-tion Disabled or Not Allowed for the Requesting Call . . . . . . . . . . . . . . . . 132

1.2.11.3 Queuing: Queued Assignment Request for FR TCH Is Discarded from QueueDue to T11 Expiry, Directed Retry Enabled But No Target Cell Available, Pre-emption Disabled or Not Allowed for the Requesting Call . . . . . . . . . . . . 134

1.2.11.4 Queuing: Queued Handover Request for FR TCH Is Served Before TQHO Ex-piry, Preemption Disabled or Not Allowed for the Requesting Call . . . . . . 135

1.2.11.5 Queuing: Queued Handover Request for FR TCH Is Discarded from theQueue Before TQHO Expiry Due to an Incoming FR Call with Higher Priority,Preemption Disabled or Not Allowed for the Requesting Calls. . . . . . . . . 137

1.2.11.6 Queuing: Queued Handover Request for FR TCH Is Discarded from theQueue Due to TQHO Expiry, Preemption Disabled or Not Allowed for the Re-questing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

1.2.11.7 Preemption: Successful Forced Inter-Cell Handover Due to Preemption, Pre-empted Assignment Request and Preempting Call Are Both FR . . . . . . . 140

8 A30808-X3247-M41-3-7618


1.2.11.8 Preemption: Forced Release of Preempted Call Due to Lack of Target Cell forForced Inter-Cell Handover Procedure, Preempted and Preempting Call AreBoth FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

1.2.11.9 Preemption: Successful Forced Inter-BSC Handover Due to Preemption, Pre-empting Handover Request and Preempted Call Are Both FR, OriginatingBSC of the Preempting Handover Request and Target BSC for the ForcedHandover Are the Same. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

1.2.12 HSCSD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451.2.12.1 Successful HSCSD Call, Mobile Originating, 3 TCHs Used . . . . . . . . . . . 1451.2.12.2 Successful Inter-cell Handover of an HSCSD Call (3 TCHs Used), Intra-BSC

1481.2.12.3 Forced Intra-cell Handover During HSCSD Assignment Procedure . . . . . 1511.2.13 Signalling Transactions without TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531.2.13.1 Successful Location Update (Phase 2 MS) . . . . . . . . . . . . . . . . . . . . . . . . 1531.2.13.2 Successful Location Update (2G/3G (GSM/UMTS) Multirat MS) . . . . . . . 1551.2.13.3 Successful IMSI Detach (Phase 2 MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571.2.13.4 Successful Supplementary Service (SS) Management Procedure via Sub-

scriber-Controlled Input (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581.2.13.5 Successful USSD (Unstructured Supplementary Service Data) Management

Procedure via (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601.2.13.6 Unsuccessful Immediate Assignment Procedure, No SDCCH Available. . 1621.2.13.7 Unsuccessful Immediate Assignment Procedure, No AGCH Available (AGCH

Overload) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631.2.13.8 Unsuccessful Immediate Assignment Procedure, assigned SDCCH is not

seized by the MS (Phantom RACH Scenario) . . . . . . . . . . . . . . . . . . . . . . 1641.2.13.9 BTS Discards Invalid RACH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651.2.13.10Immediate Assignment Procedure for Abis Link Configured via Satellite Link.

1661.2.13.11Paging Overload - BTS discards a PAGING REQUEST Message . . . . . . 1671.2.14 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681.2.14.1 Successful SMS Mobile Originating in Idle Mode (Phase 2 MS) . . . . . . . . 1681.2.14.2 Successful SMS Mobile Terminating in Idle Mode (Phase 2 MS) . . . . . . . 1701.2.14.3 Successful SMS Mobile Originating in Connected Mode (FR Call Ongoing). .

1721.2.14.4 Successful SMS Mobile Terminating in Connected Mode . . . . . . . . . . . . . 1731.2.15 Advanced Speech Call Items (ASCI) Procedures . . . . . . . . . . . . . . . . . . . 1751.2.15.1 VBS/VGCS Setup Initiated by fixed Dispatcher and Release . . . . . . . . . . 1751.2.15.2 Succesful Uplink Allocation Procedure (1) . . . . . . . . . . . . . . . . . . . . . . . . . 1771.2.15.3 FREE Uplink Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791.2.15.4 VGCS Setup initiated by Service Subscriber and Release . . . . . . . . . . . . 1801.2.15.5 VGCS SETUP initiated by Service Subscriber (FAST CALL SETUP) . . . . 1831.2.15.6 MTC During Ongoing VBS/VGCS Connection. . . . . . . . . . . . . . . . . . . . . . 1841.2.15.7 VBS/VGCS Call during Ongoing Speech Call . . . . . . . . . . . . . . . . . . . . . . 1851.2.16 Inter System Handover (2G <--> 3G), circuit switched (CS) . . . . . . . . . . . 1861.2.16.1 Successful Inter System Handover (2G --> 3G) . . . . . . . . . . . . . . . . . . . . 1861.2.16.2 Unsuccessful Inter System Handover (2G --> 3G),

loss of MS (loss of HOCMD), T3121 expiry . . . . . . . . . . . . . . . . . . . . . . . . 1881.2.16.3 Unsuccessful Inter System Handover (2G --> 3G),

No TCH available in Target UMTS Cell (3G) . . . . . . . . . . . . . . . . . . . . . . . 190

A30808-X3247-M41-3-7618 9

InformationSystem


1.2.16.4 Unsuccessful Inter System Handover (2G --> 3G), Revision to old TCH, T3124expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

1.2.16.5 Successful Inter System Handover (3G --> 2G) . . . . . . . . . . . . . . . . . . . 1921.2.16.6 Unsuccessful Inter System Handover (3G --> 2G), No TCH available in Target

GSM Cell (2G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941.2.17 Inter System Cell Reselection Procedure (2G <--> 3G), packet oriented (PO),

intra SGSN inter system change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951.2.17.1 Successful Inter System Cell Reselection Procedure (2G --> 3G) . . . . . . 1951.2.17.2 Successful Inter System Cell Reselection Procedure (3G --> 2G) . . . . . . 1981.2.18 Other Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2021.2.18.1 Idle Traffic Channel Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2021.2.18.2 Uplink and Downlink Measurement Reports on Abis . . . . . . . . . . . . . . . . 2031.2.18.3 IMSI Trace Invocation for Normal Call Setup . . . . . . . . . . . . . . . . . . . . . . 2041.2.18.4 IMSI Trace Invocation for Incoming Inter-BSC Handover. . . . . . . . . . . . . 2051.3 GPRS Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2061.3.1 GPRS Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2061.3.1.1 GPRS Mobility Management: Attach Procedure. . . . . . . . . . . . . . . . . . . . 2061.3.1.2 GPRS Mobility Management: Detach Procedure . . . . . . . . . . . . . . . . . . . 2071.3.1.3 GPRS Session Management: Activate PDP Context . . . . . . . . . . . . . . . . 2081.3.1.4 GPRS Session Management: Deactivate PDP Context . . . . . . . . . . . . . . 2091.3.1.5 GPRS: Paging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2091.3.1.6 GPRS Mobility Management: Routing Area Update . . . . . . . . . . . . . . . . . 2101.3.1.7 GPRS Mobility Management: Cell Update . . . . . . . . . . . . . . . . . . . . . . . . 2121.3.1.8 GPRS: Suspend / Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2131.3.2 LC/MAC Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2151.3.2.1 Uplink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2161.3.2.2 Downlink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2201.3.2.3 Concurrent UL TBF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2231.3.2.4 Concurrent DL TBF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

2 Counter / Message Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

3 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

10 A30808-X3247-M41-3-7618


A30808-X3247-M41-3-7618 11

InformationSystem


1 Performance Measurement Message Flows

1.1 IntroductionThe following sections show the SBS-specific message flows of call- and signalling-transactions on the interfaces Um, Abis and A.

The messages between the network elements (MS, BTS, BSC and MSC) are abbrevi-ated in the same way as the most common protocol analyzers (e.g. K1103, K1205, etc.)do. For the mapping of the used abbreviations to the complete message names definedby GSM and the Siemens Abis specifications please refer to Chapter 2 “Abbreviations”.

In addition to the messages, the implemented SBS performance measurement countersare embedded into the message flows in such a way that the association of the countersto their triggering events becomes clear. As a general rule, the appearance of a counterwithin a message flow means that its value is increased by ’1’. Deviations from this ruleare explicitely mentioned in the message flows.

To indicate also the subcounters of the specific measurements, the following method isused: <measurement shortname>(<subcounter no.>.).

Example:“ATINHIRC (2.)” means that the second subcounter of the measurement ATINHIRC(’downlink quality’) is increased by the marked event.For the long names of the measurements, please refer to the document “PM:SBSCounter”.

iNote: The message flows have to be considered as typical examples for the affectedsignalling transactions. Depending on specific settings in the involved network elements(MSC, BSC), flow traces taken from ’real live’ networks can deviate from the shownmessage flows (especially for the optional sub-procedures Authentication, Ciphering,Early Classmark Sending and TMSI Reallocation).

iNote: If not otherwise defined the blue colour generally indicates the events on the han-dover target resources.In 1.2.11.2 the blue colour indicates the events related to the second (high priority) call.In 1.2.11.5 the blue colour indicates the events related to the high priority call.In 1.2.11.7, 1.2.11.8 and 1.2.11.9 the blue colour indicates the events related to pre-empting call.In 1.2.5.7 the red colour indicates the BSC serving the first (really external) target cell inthe target cell list of the HANDOVER REQUIRED message.

iSMLC-Specific Message Flows:In order to guarantee an SBS release-independent documenation delivery, the SMLC-related message flows are provided in a separate documentation set. The manualPM:SBS Message Flows is intended for the SBS-specific message flows, whereas themanual PM:SMLC Message Flows is intended for the SMLC-specific message flows.Both manuals may be used together, if applicable.

12 A30808-X3247-M41-3-7618


1.2 Message Flows

1.2.1 Call Setup Procedures

1.2.1.1 Successful Mobile Originating Call (MOC), FR Call

BTS BSCMS MSC

CHNRD

NSUCCHPC (4.)NASUSDPE

CHNREQ

UI (IMASS)

SABM (CMSREQ)

UA

ESTIN (CMSREQ)

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)

TACCBPRO (2.)SUIMASCA (4.)NACSUCPR (2.)

RACH

AGCH

SDCCH

SDCCH

DT1 (CICMP)

I (CIMCMD)

I (CIMCMP)

ENCRY (CIMCMD)

MRPCI

DATIN (CIMCMP)

DT1 (CICMD)

SDCCH

SDCCH

DT1 (AUTREP)

I (AUTREQ)

I (AUTREP)

DATRQ (AUTREQ)

DATIN (AUTREP)

CC (AUTREQ)

SDCCH

SDCCH

CR (CL3I; CMSREQ)

NATTSDPENACSUCPR (3.)ATIMASCA (4.)If last SDCCH startASDCALTI

Start T_MSRFPCI

Start T3101

Stop T_MSRFPCI

Start T3101

NTDMAGCH (1.)

A30808-X3247-M41-3-7618 13

InformationSystem


BTS BSCMS MSC

I (ASS CMD)

PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

MTCHBUTI (1.) (start)

DT1 (ASS REQ)

SDCCH

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

I (ASS CMP)

SABM

UAESTIN

SUCTCHSE (1.)TASSSUCC (2.)

TNTCHCL (1.)

DATIN (ASS CMP)

MRPCI

DT1 (ASS COM)

FACCH

FACCH

FACCH

Stop T_MSRFPCI

DATIN (SETUP)SETUP

DT1 (SETUP)

DT1 (CPROC)

SDCCH

I (CPROC) DATRQ (CPROC)SDCCH

ATTCHSEI (1.)TASSATT (2.)If last TCH startAALTCHTI (1.)

RELCN

RCHRL (SDCCH)

RCHRA

ASDCALTI(stop)MBUSYSSP (1.)(accumulation)

RELRQ

Start T10

Stop T10

14 A30808-X3247-M41-3-7618


BTS BSCMS MSC

I (CONACK)

DT1 (ALERT)

I (ALERT) DATRQ (ALERT)

DATIN (CONACK) DT1 (CONACK)

DT1 (CONNECT)DATRQ (CONNECT)I (CONNECT)

FACCH

FACCH

FACCH

Conversation phase ...

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done ontransmission of the ASSIGNMENT COMMAND.

(**)

called party isreachableandidle (’ringing’)

called party hasaccepted the call

A30808-X3247-M41-3-7618 15

InformationSystem


1.2.1.2 Successful Mobile Terminating Call (MTC), FR Call

BTS BSCMS MSCPGCMD

CHNAV (SDCCH)

TACCBPRO (1.)



NATTSDPENACSUCPR (1.), (3.)ATIMASCA (1.)If last SDCCH startASDCALTI

UDT (PAGIN)

CHNRD

CHNAK

IACMD (IMASS)

UA

ESTIN (PAGRES)

(CL3L; PAGRES)

UI (IMASS)

SABM (PAGRES)

AGCH

SDCCH

UI (PAGREQ)PCH

SDCCH

CHNREQ

RACH

DATRQ (TRCMD)I (TRCMD)

I SETUP

I (TRCMP)

DT1 (SETUP)DATIN (SETUP)

DATIN (TRCMP) DT1 (TRCMP)

I (CCONF)DATRQ (CCONF)

DT1 (CCONF)

SDCCH

SDCCH

SDCCH

SDCCH

Start T_MSRFPCI

Start T3101

Stop T3101

MRPCI

Stop T_MSRFPCI

DT1 (TRCMD)

Optional: Authentication & Ciphering Procedure... (see 1.2.1.1)

NTDMPCH (1.)

NTDMAGCH (1.)

16 A30808-X3247-M41-3-7618


BTS BSCMS MSC

PHCRQ

PHCCN


DT1 (ASREQ)

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

I (ASS CMD)

SABMESTIN

DATIN (ASS CMP)

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

TNTCHCL (1.)

SDCCH

FACCH

DT1 (ASS COM)


I (ASS CMP)FACCH

UAFACCH

MRPCI

Stop T_MSRFPCI


Start T10

Stop T10

RELRQ

RCHRL (SDCCH)

RCHRA

RELCN


A30808-X3247-M41-3-7618 17

InformationSystem


BTS BSCMS MSC

I (CONACK)

DT1 (ALERT)

I (ALERT)DATIN (ALERT)

DATRQ (CONACK)DT1 (CONACK)

DT1 (CONNECT)DATIN (CONNECT)

I (CONNECT)

FACCH

FACCH

FACCH



(**)

called MS isready (’ringing’)

called MS hasaccepted the call

18 A30808-X3247-M41-3-7618


1.2.1.3 Successful Mobile Originating Call (MOC) with Direct TrafficChannel Assignment, FR Call

BTS BSCMS MSC

CHNAV (TCH)

CHNAK

ATTCHSEI (1.)ATIMASCA (4.)NASCUCPR (3.)If last TCH startAALTCHTI (1.)

NSUCCHPC (10.)SUCTCHSE (1.)TNTCHCL (1.)

CHNRD

IACMD (IMASS)

ESTIN (CMSREQ)

MRPCI

UI (IMASS)

SABM (CMSREQ)

AGCH

FACCH

CHNREQRACH

MTCHBUTI (1.) (start)Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

Stop T_MSRFPCI

I (SETUP) DATIN (SETUP)DT1 (SETUP)FACCH

UAFACCH

Optional: Authentication & Ciphering Procedure...(see 1.2.1.1)

DATRQ (CPROC)I (CPROC)

DT1 (CPROC)

FACCH

CR (CL3I;CMSREQ)


Start T3101

Stop T3101

NTDMAGCH (1.)

A30808-X3247-M41-3-7618 19

InformationSystem


BTS BSCMS MSC

MOMRQ

DT1 (ASS COM)

TASSSUCC (2.)

I (CHMM)

I (CHMMACK)

MOMAK

DATRQ (CHMM)

DATIN (CHMMACK)

DT1 (ASS REQ)

DT1 (CONNECT)DATRQ (CONNECT)

I (CONNECT)

I (CONACK)DATIN (CONACK)

DT1 (CONACK)

DT1 (ALERT)DATRQ (ALERT)

I (ALERT)

FACCH

FACCH

FACCH

FACCH

FACCH



(**)

TASSATT (2.)

(***)

In case of direct TCH assignment the timer T10 is not used. Two not-administrable system internaltimers are used, one for the control of the MOMRQ procedure, one for the control of the CHMMprocedure. In case of expiry of one of these timers, the BSC sends an ASS FAI with cause ’equipmentfailure’ to the MSC.

(***)



20 A30808-X3247-M41-3-7618


1.2.1.4 Successful (MOC) Using Early Classmark Sending, FR Call

BTS BSCMS MSC

CHNAV (SDCCH)

CHNAK




CHNRD

IACMD (IMASS)

ESTIN (CMSREQ)

MRPCI

I (CLAMCH)

CC (CICMD)ENCRY (CIMCMD)

DATIN (CLAMCH)DT1 (CLUPD)

I (CIMCMP)DATIN (CIMCMP) DT1 (CICMP)

I (TRCMD)DT1 (TRCMD)

UI (IMASS)

I (CMSREQ)

AGCH

SDCCH

CHNREQRACH

SDCCH

I (CIMCMD)

SDCCH

SDCCH

SDCCH

CR (CL3I; CMSREQ)

I (CPROC) DATRQ (CPROC)

DATIN (SETUP)I (SETUP)DT1 (SETUP)

DT1 (CPROC)

SDCCH

SDCCH

Start T3101

Stop T3101

Stop T_MSRFPCI

Start T_MSRFPCI

MRPCI

DATRQ (TRCMD)

NTDMAGCH (1.)

A30808-X3247-M41-3-7618 21

InformationSystem


BTS BSCMS MSC

DT1 (ASREQ)

PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

ESTIN

I (ASS CMD)

I (ASS CMP)DATIN (ASS CMP)

DT1 (TRCMP)

I (TRCMP)DATIN (TRCMP)

DT1 (ASS COM)

MRPCI


Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

FACCH

Stop T_MSRFPCI

SDCCH

SDCCH

SABM

FACCH

UAFACCH

ATTCHSEITASSATT (5.)If last TCH startAALTCHTI (1.)


TNTCHCL (1.)

Start T10

Stop T10

RELRQ

RELCN

RCHRL (SDCCH)

RCHRA


22 A30808-X3247-M41-3-7618


BTS BSCMS MSC

DT1 (ALERT)

Call setup continuation...


(**)

DATRQ (ALERT)I (ALERT)

FACCH


A30808-X3247-M41-3-7618 23

InformationSystem


1.2.1.5 Successful Mobile Terminating Call (MTC), Using Early Classmark,Sending, FR Call

BTS BSCMS MSCPGCMD

CHNAV (SDCCH)

TACCBPRO (1.)




UDT (PAGIN)

CHNRD

CHNAK

IACMD (IMASS)

UA

ESTIN (PAGRES)

UI (IMASS)

SABM (PAGRES)

AGCH

SDCCH

UI (PAGREQ)PCH

SDCCH

CHNREQRACH

DT1 (CICMP)

Start T_MSRFPCI

Start T3101

Stop T3101

ENCRY (CIMCMD)I (CIMCMD)SDCCH

I (CLAMCH)SDCCH

I (CIMCMP)SDCCH

DATIN (CLAMCH) DT1 (CLUPD)

MRPCI

Stop T_MSRFPCI

DATIN (CIMCMP)

CR (CL3I; PAGRES)

CC (CIMCMD)

NTDMAGCH (1.)

24 A30808-X3247-M41-3-7618


BTS BSCMS MSC

PHCRQ

PHCCN


DT1 (ASREQ)

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

I (ASS CMD)

SABMESTIN

DATIN (ASS CMP)

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

TNTCHCL (1.)

SDCCH

FACCH

DT1 (ASS COM)


I (ASS CMP)FACCH

UAFACCH

MRPCI

Stop T_MSRFPCI


Start T10

Stop T10

DATRQ (TRCMD)I (TRCMD)

I SETUP

I (TRCMP)

DT1 (SETUP)DATIN (SETUP)

DATIN (TRCMP) DT1 (TRCMP)

I CCONF DATRQ (CCONF) DT1 (CCONF)

SDCCH

SDCCH

SDCCH

SDCCH

DT1 (TRCMD)

A30808-X3247-M41-3-7618 25

InformationSystem


FACCHI (ALERT)

BSCMS BTS MSC

DATRO (ALERT)DT1 (ALERT)

Call setup continuation...


(**)

RELRQ

RCHRL (SDCCH)

RCHRA

RELCN


26 A30808-X3247-M41-3-7618


1.2.1.6 Successful Mobile Terminating Call (MTC) in busy mode, new wait-ing call (feature “Call waiting”) is accepted by called subscriber

called subscriber acceptsnew cell and releases theold one by the pressingthe appropriate keys onthe MS

DATIN (SPDACK)

DATIN (STDACK)

DATRQ (SPDTMF)

DATRQ (STDTMF) DT1 (STDTMF)

DT1 (STDACK)

DT1 (SPDTMF)

DT1 (SPDACK)

FACCH

BTS MSCMS BSC

(cause: user busy

I (SPDACK) FACCH

I (SPDTMF)

I (STDACK)FACCH

I (STDTMF)FACCH

SDCCH

SDCCH

new call for a busysubscriber arrives atMS

DT1 (ALERT)

DATIN (SETUP)

DATRQ (CONNECT)

I (ALERT)


DATRQ (ALERT)


FACCH

I (CONNECT)FACCH

FACCH

DATRQ (ALERT)*

FACCH


I (ALERT)*

I (CCONF)*

I SETUP)*DT1 (SETUP)*

DT1 (ALERT)*

DT1 (CCONF)*

I (CONACK)

DT1 (CONNECT)

DATRQ (CCONF)*


A30808-X3247-M41-3-7618 27

InformationSystem


BTS BSCMS MSC

I (DISC)FACCH (cause: normal call clearing)

I (RELEAS)FACCH

I (RELCMP)FACCH

I (CONNECT)*FACCH

I (CONACK)*FACCH

DATIN (DISC)

DATIN (RELEAS)

DATIN (REL CMP)

DATIN (CONNECT)*

DATIN (CONACK)*

DT1 (DISC)

DT1 (RELEAS)

DT1 (REL CMP)

DT1 (CONNECT)*

DT1 (CONACK)*

(cause: normal call clearing)

Conversation phase of new accepted call...

Messages related to new waiting and accepted call.(*)

28 A30808-X3247-M41-3-7618


1.2.1.7 Unsuccessful Mobile Originating Call (MOC), Subscriber B Busy, FRCall

BTS BSCMS MSC

DT1 (ASS COM)



MRPCI

RELRQ

Call setup ... (see Successful MOC)

Call release... (see ‚normal call release, originated by network‘)

RCHRL (SDCCH)

RELCN

DT1 (DISC)

RCHRA

(cause: user busy)

FACCH

I (DISC)SDCCH

DATRQ (DISC)

Stop T_MSRFPCI

Stop T10


A30808-X3247-M41-3-7618 29

InformationSystem


1.2.1.8 Unsuccessful Mobile Originating Call (MOC), No TCH Available, FRCall

BTS BSCMS MSC

I (SETUP)DATIN (SETUP)

TASSFAIL (8.)

ATTCHSEI (1.)ATCHSMBS (1.)TASSATT (2.)

DT1 (SETUP)

DT1 (CPROC)DATRQ (CPROC)

I (CPROC) DT1 (ASS REQ)

DT1 (ASS FAI)

(cause: no radio resource available)

Call release ... (see ‚Normal call release, originated by network‘)

DT1 (DISC)(cause: no circuit/channel available)I (DISC)

FACCH

DATRQ (DISC)

SDCCH

SDCCH

Call setup ...

30 A30808-X3247-M41-3-7618


1.2.1.9 Successful Mobile Originated Call (MOC) in a Concentric Cell (innerarea), FR Call

BTS BSCMS MSC

I (CPROC)DATRQ (CPROC)



DATIN (SETUP)I (SETUP)

DT1 (SETUP)

DT1 (CPROC)

DT1 (ASS REQ)

PAREQ

PAREA

PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

Call setup ...

SDCCH

SDCCH

(preferred area type: inner area)

Start TTRAU

Start T_MSRFPCI

I (ASS CMD)SDCCH

DATRQ (ASS CMD)

Stop TTRAU (**)

FACCHSABM

UAFACCH

I (ASS CMP)DATIN (ASS CMP)FACCH

TNTCHCL (1.) (for concentric cells)

ESTIN


DT1 (ASS COM)

Start T10

Stop T10

A30808-X3247-M41-3-7618 31

InformationSystem


BTS BSCMS MSC

RELCN

AALTCHTI (1.) (stop)MTCHBUTI (1.)(stop)MBUSYSSP (1.)(accumulation)

DT1 (ALERT)

MRPCI

RELRQ

RCHRL (SDCCH)

RCHRA

Call setup continuation ...


(**)

Stop T_MSRFPCI

DATRQ (ALERT)I (ALERT)

FACCH

32 A30808-X3247-M41-3-7618


1.2.1.10 Successful Mobile Emergency Call (MEC), FR Call

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

CR (CL3I; CMSREQ)


TACCBPRO () (2.)SUIMASCA (2.)NACSUCPR (2.)


CHNRD

IACMD (IMASS)UI (IMASS)

SABM (CMSREQ)ESTIN (CMSREQ)

MRPCI

RACH (request reference: emergencycall)

AGCH

SDCCH (CM service type: emergencycall establishment)

I (EMSETUP)DATIN (EMSETUP)

DT1 (EMSETUP)

DT1 (CPROC)

SDCCH

Optional: Authentication & Ciphering Procedure (see 1.2.1.1)

DATRQ (CPROC)I (CPROC)

SDCCH

UASDCCH


DT1 (ASREQ)

Call setup continuation ...

Stop T_MSRFPCI

Start T_MSRFPCI

Start T3101

Stop T3101

NTDMAGCH (1.)

A30808-X3247-M41-3-7618 33

InformationSystem


1.2.2 Unsuccessful Assignment Procedures

1.2.2.1 Unsuccessful TCH Assignment Procedure with Reversion toSDCCH, FR Call

BTS BSCMS MSC

DT1 (ASS REQ)

Start T_MSRFPCI

DT1 (ASS FAIL)

TASSFAIL (7.)

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)I (ASS CMD)

(cause: radio interface failure,

DT1 (DISC)

Call setup ...

SDCCH

Start TTRAU


(cause: normal, unspecified)

I (ASS FAIL)SDCCH

FACCHSABM

ESTIN

PHCRQ

ATTCHSEI (1.)TASSATT (2.)If last TCH startAALTCHTI

Access to targetchannel fails...

SABMSDCCH

UA

(Cause: protocolerror unspecified)

DATIN (ASS FAIL)

reversion to old channel)

Start T10

Stop T10

Call release ...

DATRQ (DISC)I (DISC)

SDCCH

FACCHSABM

FACCHSABM

....

SDCCH

34 A30808-X3247-M41-3-7618


1.2.2.2 Unsuccessful TCH Assignment Procedure with Loss ofASSIGNMENT COMMAND (T10 < T_MSRFPCI), FR Call (T10 Expiry)

BTS BSCMS MSC

DT1 (ASS REQ)

Start T10

Start T_MSRFPCI

Expiry T10 DT1 (ASS FAI)


TASSFAIL (6.)

PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

I (ASS CMD)

(cause: radio interface msg failure)

DT1 (CL CMD)(cause: call control)

Call setup ...

SDCCH

Start TTRAU

Stop TTRAU (**)

Release of resources ...


(**)


ASS CMD islost ...

A30808-X3247-M41-3-7618 35

InformationSystem


1.2.2.3 Unsuccessful TCH Assignment Procedure with Loss ofASSIGNMENT COMMAND (T10 > T_MSRFPCI), FR Call (T_MSRFPCIExpiry)

BTS BSCMS MSC

DT1 (ASS REQ)

Start T10

Start T_MSRFPCI

DT1 (CL REQ)


NRFLTCH (4.)

PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

I (ASS CMD)


DT1 (CL CMD)


Call setup ...

SDCCH

Start TTRAU

Stop TTRAU (**)


ASS CMD islost ...

Expiry T_MSRFPCICONFL


(cause: T_MSRFPCI expired)

(**) TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done ontransmission of the ASSIGNMENT COMMAND.

36 A30808-X3247-M41-3-7618


1.2.2.4 Unsuccessful TCH Assignment Procedure LAPDm I-Frame withASSIGNMENT COMMAND not acknowledged by MS (T200 Expiry),FR Call

BTS BSCMS MSC

DT1 (ASS REQ)

Start T10

Start T_MSRFPCI


PHCRQ

PHCCN

CHNAV (TCH)

CHNAK

DATRQ (ASS CMD)

Call setup ...

Start TTRAU

Stop TTRAU (**)



I (ASS CMD)SDCCH

DT1 (CL REQ)(cause: radio interface msg failure)

DT1 (CL CMD)(cause: radio interface msg failure)

ERRIN

(cause: timer T200 expiredN200+1 times))


(**)

NRFLSDCC (1.)

I (ASS CMD)

I (ASS CMD)

I (ASS CMD)

SDCCH

SDCCH

SDCCH

T200 expiredN200+1 times))

T200

T200

T200

NRCLRCMD (1.)

NRCLRREQ (3.)

A30808-X3247-M41-3-7618 37

InformationSystem


1.2.3 Call Release Procedures

1.2.3.1 Normal Call Release (Originated by MS), FR Call

BTS BSCMS MSC

I (DISC)

DATRQ (RELEAS)

DATIN (REL CMP)

MTCHBUTI (1.) (stop)AALTCHTI (1.) (stop)

DATIN (DISC)DT1 (DISC)

DT1 (RELEAS)

I (RELEAS)

I (RELCMP)DT1 (REL CMP)

DATRQ (CHREL)

DT1 (CL CMD)

I (CHREL)

DESACDT1 (CL CMP)

RLSD

RLC

RELIN

RCHRL (TCH)

RCHRA


(cause: normal call clearing)FACCH

FACCH

FACCH

FACCH

DISCFACCH

UAFACCH


(cause: call control)

(cause: end user originated)

Start T3110

Stop T3110

Start T3109

Stop T3109

Start T3111

Expiry T3111

NRCLRCMD (2.)

38 A30808-X3247-M41-3-7618


1.2.3.2 Normal Call Release (Originated by Network), FR Call

BTS BSCMS MSC

I (DISC)

DATRQ (RELEAS)

DATIN (REL CMP)


DATIN (DISC)DT1 (DISC)

DT1 (RELEAS)I (RELEAS)

I (RELCMP)DT1 (REL CMP)

DATRQ (CHREL)

DT1 (CL CMD)

I (CHREL)

DESAC

DT1 (CL CMP)

RLSD

RLC

RELIN

RCHRL (TCH)

RCHRA


FACCH

FACCH

FACCH

FACCH

DISCFACCH

UAFACCH



(cause: end user originated)


Start T3110

Stop T3110

Start T3109

Stop T3109

Start T3111

Expiry T3111

NRCLRCMD (2.)

A30808-X3247-M41-3-7618 39

InformationSystem


1.2.3.3 Abnormal Call Release Procedure; Call drop: BTS sendsCONNECTION FAILURE INDICATION to the BSC

BTS BSCMS MSC

CONFL

TTRAU expiry***orTSYNC/TSYNCDL**** expiry

NRFLTCH (7.)or *

NRFLSDCC (7.)

(cause: radio link failure)

Radio link counterin the BTS (RDLNKTBS**)reaches “0”

CONFL

Call or dedicated connection (SDCCH or FACCH) established...

or...

(cause: remote transcoder failure)

NRFLTCH (8.)or *

NRFLSDCC (8.)

T_MSRFPCI expiry*****

CONFL(cause: T_MSRFPCI expired)

NRFLTCH (4.)or *

NRFLSDCC (4.)

or...

40 A30808-X3247-M41-3-7618


BTS BSCMS MSC

DT1 (CL REQ)

RELCN

RCHRA

DT1 (CL CMD)

(cause: radio interface

DT1 (CL CMP)RELRQ

message failure******)

Reset T_MSRFPCI

RCHRL (New TCH)

MTCHBUTI (1.) (stop)

MS-BTS distanceexceeds the thresholdEXCDIST

CONFL(cause: distance limit exceeded******)

NRFLTCH (5.)or *

NRFLSDCC (5.)

or...

NRCLRCMD (1.)

NRCLRREQ (3.)

NRCLRREQ (3.)or

NRCLRREQ (6.)******

A30808-X3247-M41-3-7618 41

InformationSystem


If the CONNECTION FAILURE INDICATION is received a TCH, NRFLTCH is triggered; if it is receivedfor an SDCCH, NRFLSDCC is triggered.

RDLNKTBS is the initial value of the 'S' Counter. This counter in the BTS is decreased by '1' if the BTScannot decode a SACCH frame correctly. When the BTs can decode a SACCH frame again,RDLNKTBS is increased by '2'. If the counter reaches '0', the Um connection is regarded as lost.

TTRAU is started in the BTS on receipt of the CHANNEL ACTIVATION message for a TCH. Its purposeis to observe the receipt of TRAU frames from the TRAU after the activation of the TCH, i.e. it is stoppedwhen TRAU frames are received.

TSYNC is started in the BTS when the BTS does not receive valid TRAU frames for an activated TCHanymore. Its purpose is to observe the re-appearance of TRAU frames from the TRAU, i.e. it is stoppedagain when TRAU frames are received. TSYNC is used for FR, HR and EFR speech calls and forstandard dataservices (up to 9,6 kbit/s). For AMR calls and 14,4 kbit/s dataservices TSYNC is replacedby TSYNCDL.

T_MSRFPCI is started in the BTS on receipt of the CHANNEL ACTIVATION ACKNOWLEDGEmessage for a TCH. Its purpose is to observe the receipt of the MPRCI message, i.e. it is stopped whenthe MRPCI message is received. The BSC sends this message when the MS has successfully sent thefirst layer 3 message on a new channel during call setup (CM SERVICE REQUEST (for the SDCCH)and ASSIGNMENT COMPLETE) and handover (ASSIGNMENT COMPLETE (intracell HO) andHANDOVER COMPLETE (inter-cell handover)). As T_MSRFPCI is hardcoded to a very long value(20s), this timer should never expire under normal conditions and reasonable timer settings.

When the BSC receives a CONNECTION FAILURE INDICATION with cause ’distance limit exceeded’,the cause value contained in the CLEAR REQUEST message will not be ’radio interface messagefailure’ but ’distance’. Consequently also the corresponding NRCLRREQ subcounter (6.) is triggeredinstead of subcounter (3.).

(*)

(***)

(****)

(*****)

(**)

(******)

42 A30808-X3247-M41-3-7618


1.2.3.4 Abnormal Call Release Procedure; Call drop: BTS sends ERRORINDICATION to the BSC

BTS BSCMS MSC

ERRIN

NRFLTCH (1.)or *

NRFLSDCC (1.)

(cause: timer T200 expiredN200+1 times)

BTS has sent a Um layer 2 (LAPDm)message in ’acknowledged mode’N200+1 times to the MS withoutreceiving an appropriate layer 2acknowledgement.

Call or dedicated connection (SDCCH or FACCH) established...

NRFLTCH (2.)or *

NRFLSDCC (2.)

MS has sent a Um layer 2 (LAPDm)message DM (Mode) to the BTS whilethe BTS-MS communication is in’multiple frame stablished state’

ERRIN

(cause: unsolicited DM response,multiple frame established state)

DMFACCH or SDCCH

or...

RELIN**

RELIN**

A30808-X3247-M41-3-7618 43

InformationSystem


BTS BSCMS MSC

DT1 (CL REQ)

RCHRA

DT1 (CL CMD)

(cause: radio interface

DT1 (CL CMP)

message failure)

Reset T_MSRFPCI

RCHRL (New TCH)


NRFLTCH (3.)or *

NRFLSDCC (3.)

If the ERROR INDICATION is received for a TCH, NRFLTCH is triggered; if it is received for a SDCCH,NRFLSDCC is triggered.

(*)

ERRIN(cause: sequence error)

BTS has detected irregularitiesin the Um layer 2 (LAPDm) flowcontrol functions (wrongmessage sequence) useds in’acknowledged mode’

or...

NRCLRCMD (1.)

NRCLRREQ (3.)

RELIN**

The RELEASE INDICATION is always sent directly after the ERROR INDICATION to indicate that thelayer 2 context on the Um interface has already been cleared by the BTS.

(**)

44 A30808-X3247-M41-3-7618


1.2.3.5 Abnormal Call Release; BTS sends RELEASE INDICATION during astable call phase to the BSC

BTS BSCMS MSC

DT1 (CL REQ)

DT1 (CL CMD)

(cause: radiointerface failure)

RELIN

Due to MS-internalirregularities, the MSdisconnects the layer 2on the Um interface.

Call or dedicated TCH connection in a stable phase...

NRCLRCMD (1.)

NRCLRREQ (2.)

DISC

RELCN

RCHRA

RELRQ

Reset T_MSRFPCI

RCHRL (New TCH)


A30808-X3247-M41-3-7618 45

InformationSystem


1.2.4 Inter-Cell Handover, Intra-BSC

1.2.4.1 Successful Inter-Cell Handover, Intra-BSC, FR Call

BTSold BTSnew BSCMS MSC

CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8

HANDO

Start T3124

Stop T3124Start T3105

ATTCHSEI (1.)ATINHIRC (*)If last TCH startAALTCHTI (1.)

Start THORQST

Start TTRAU

Stop TTRAU (**)

Start T_MSRFPCI

UI (MEAS REP)

HO ACCESS

UI (PHYS INFO)

SACCH

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

FACCH

FACCH

FACCH

(with HO cause)

BWHCI

DATRQ (HO CMD)

AININIRH (*)AOUINIRH (*)

Stop T3105ESTIN

SABM

UA

FACCH

FACCHTNTCHCL (1.)

Call in progress...

46 A30808-X3247-M41-3-7618



MRPCI


Stop T8

DATIN (HO CMP)

SUCTCHSE (1.)

DT1 (HOPER)

SINTHINT (*)SININIRH (*)SOUINIRH (*)SINHOBSC (*)

Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITIONINDICATION.

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is doneafter receipt of the HANDOVER DETECT message.

(**)

(*)

Stop T_MSRFPCI (with HO cause)

RELRQ

RELCN

RCHRL (Old TCH)

RCHRA

I (HO CMP)FACCH

Call continuation ...

A30808-X3247-M41-3-7618 47

InformationSystem


1.2.4.2 Unsuccessful Inter-Cell Handover Attempt, Intra-BSC, No TCHAvailable in Target Cell, FR Call


......

......

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITONINDICATION.When the BSC receives an INTERCELL HANDOVER CONDITION INDICATION for a TCH with a validtarget cell, it first checks the administrative state (locked/unlocked/shutting down) and the availabilitystate (enabled/disabled) of the target BTS objects. Moreover, if the INTERCELL HANDOVER CON-DITION INDICATION contains the cause "traffic", it checks the TCH load situation with respect to thethreshold TRFLTH.Only if the BSC finds one target BTS in state "unlocked/enabled" and (in case of traffic handover)with a TCH load below the TRFLTH threshold, the BSC starts to search for an available TCH in the"idle list" of the target cell. Only in this case the measurements ATINHIRC (for the originating BTS)and ATTCHSEI (for the target BTS) are triggered. If no TCH can be found due to TCH congestion,"locked" state of the TRXs or/and "locked" state of the CHAN objects in the target BTS, ATCHSMBSis triggered for the target BTS in addition and the next target cell is analyzed.If no target BTS in state "unlocked/enabled" or (in case of traffic handover) no target cell with the TCHload below the threshold TRFLTH can be found, NHOINRHA is triggered. In this case neither ATIN-HIRC nor ATTCHSEI nor ATCHSMBS are increased.

(*)

BWHCI

(with HO cause)

ATTCHSEI (1.)(**)ATCHSMBS (1.)(**)ATINHIRC (*)(**)NHOINRHA (3.)(**)

BWHCI

(with HO cause)

Start THORQST

Expiry THORQST

Call in progress...


(**)

ATTCHSEI (1.)(**)ATCHSMBS (1.)(**)ATINHIRC (*)(**)NHOINRHA (3.)(**)

48 A30808-X3247-M41-3-7618


1.2.4.3 Unsuccessful Inter-Cell Handover, Intra-BSC, with Reversion to OldTCH (T3124 Expiry), FR Call


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8


Start T3124

Expiry T3124


Start THORQST

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)

HO ACCESS

SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

FACCH

FACCH

HO ACCESSdoes not getthrough***

SABM

UAFACCH

FACCH

ESTIN

HO ACCESSFACCH

Stop T8

HOFITABSUNINHOIE (*)

I (HO FAIL)FACCH DATIN (HO FAIL)

(cause: protocol error, unspecified**)

Call in progress...

A30808-X3247-M41-3-7618 49

InformationSystem



RCHRL (New TCH)



(*)

Reset T_MSRFPCI

RCHRA

Reset TTRAU


(**) The actual cause value used by the MS might differ from the one indicated in the message flow -other cause values such as "abnormal release, timer expired" or "abnormal release, unspecified" etc.might be used.

The handover might not only fail due to the fact that no PHYSICAL INFORMATION is received aftertransmission of the HANDOVER ACCESS on the target channel. The MS can still return to the oldchannel after it has received the PHYSICAL INFORMATION from the BTS. This happens when thelayer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmissionof the SABM on the target channel.

(****)

50 A30808-X3247-M41-3-7618


1.2.4.4 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS (Lossof HO CMD, T8<TTRAU), FR Call (T8 Expiry)


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8



Start THORQST

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

Expiry T8

UNIHIRLC

HO CMD islost ...

DT1 (CL REQ)(cause: radiointerface messagefailure)

DT1 (CL CMD)

DT1 (CL CMP)

RELCN

RELRQ

RCHRL (Old TCH)

RCHRA

Call in progress...

NRCLRCMD (1.)

NRCLRREQ (3.)

A30808-X3247-M41-3-7618 51

InformationSystem





(*)

Reset T_MSRFPCI

Reset TTRAU

RCHRA

RLSD

RCHRL (New TCH)

RLC

Call release ...

52 A30808-X3247-M41-3-7618


1.2.4.5 Unsuccessful Inter-Cell Handover, Intra-BSC with Loss of MS (Lossof HO CMD, T8>TTRAU), FR Call (TTRAU Expiry)


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8



Start THORQST

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

NRFLTCH (8.)

HO CMD islost ...

DT1 (CL REQ)(cause: radio interfacemessage failure)

DT1 (CL CMD)

Expiry TTRAU CONFL(Cause: remotetranscoder failure)

DT1 (CL CMP)

Call in progress...

NRCLRCMD (1.)

NRCLRREQ (3.)

A30808-X3247-M41-3-7618 53

InformationSystem





(*)

RELRQ

RELCN

RCHRA

RCHRL (New TCH)

RCHRL (Old TCH)

RCHRA

RLSD

RLC

Reset T_MSRFPCI

54 A30808-X3247-M41-3-7618


1.2.4.6 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS,Handover Access Failure (No SABM after Transmission ofPHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU)


CHNAK

CHNAV (New TCH)

I (HO CMD) Start T8


HANDO

Start T3124

Start T3105


Start THORQST

Start TTRAU

Stop TTRAU (**)

Start T_MSRFPCI

UI (MEAS REP)

UI (PHYS INFO)

SACCH

DATRQ (HO CMD)

BWHCI

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

FACCH

Expiry T3105

Start T3105

UI (PHYS INFO)

(with HO cause)

FACCH

MTCHBUTI (1.) start

Call in progress...

MS does not reactto PHYS INFO, noSABM is receivedat the BTS.


FACCH

A30808-X3247-M41-3-7618 55

InformationSystem



MTCHBUTI (1.)(stop)AALTCHTI (1.)(stop)


(*)

RELRQ

RELCN

RCHRA

RCHRL (New TCH)

RCHRL (Old TCH)

RCHRA

RLSD

RLC

NRFLTCH (6.)

DT1 (CL REQ)

(cause: radio interfacemessage failure)

DT1 (CL CMD)

CONFL(cause: HO accessfailure)

DT1 (CL CMP)

Start T3105

FACCH

UI (PHYS INFO)

Note: T3105 expires (NY1+1) times.(***)


Expiry T3105 (***)

Expiry T3105

NRCLRCMD (1.)

NRCLRREQ (3.)

56 A30808-X3247-M41-3-7618


1.2.4.7 Successful Inter-Cell Handover (Intra-BSC) between ColocatedConcentric Cells, FR Call


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8


HANDOStart T3124


Start TTRAU

Stop TTRAU (**)

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

FACCH


UI (PHYS INFO)FACCH

Stop T3105ESTIN

TNTCHCL (1. forconcentric cells)

SABM

UA

FACCH

FACCH

Call in progress...

PAREA

PAREQ

A30808-X3247-M41-3-7618 57

InformationSystem



MRPCI


Stop T8

DATIN (HO CMP)

SUCTCHSE (1.)

DT1 (HOPER)




(**)

(*)


RELRQ

RELCN

RCHRL (Old TCH)

RCHRA

I (HO CMP)FACCH


58 A30808-X3247-M41-3-7618


1.2.4.8 Successful Inter-Cell Handover, Intra-BTSE, Between SynchronizedCells, FR Call


CHNAK

CHNAV (New TCH)

I (HO CMD)

MTCHBUTI (1.)(start)

Start T8


HANDO


Start THORQST

Start TTRAU

Stop TTRAU (**)

Start T_MSRFPCI

UI (MEAS REP)

HO ACCESS (***)

SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

HO ACCESS (***)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

FACCH

FACCH

(Activation type: related tosynchronous handover)

(Synchronization Indicator: synchronized)

HO ACCESS (***)FACCH

HO ACCESS (***)FACCH

ESTINSABM

UAFACCH

FACCH TNTCHCL (1.)

Stop T8

DATIN (HO CMP)


I (HO CMP)FACCH

Call in progress...

A30808-X3247-M41-3-7618 59

InformationSystem



MRPCI


SUCTCHSE (1.)

DT1 (HOPER)

Note: Subcounter depends on the handover cause value contained in the BWHCI.


(**)

(*)

Stop T_MSRFPCI

(with HO cause)

RELRQ

RELCN

RCHRL (Old TCH)

RCHRA


HO ACCESS is transmitted exactly 4 times, the MS does not wait for any response from the BTS butdirectly sets up the layer 2 connection (using the SABM) after the last HO ACCESS.

(***)

60 A30808-X3247-M41-3-7618


1.2.4.9 Successful Inter-Cell Handover, Intra-BSC, MSC Controlled, FR Call

CHNAK

DT1 (HO RQD)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

CR (HO REQ)

I (HO CMD)

FACCH

CHNAV (New TCH)

HANDO


Call in progress...

Start THORQST

BWHCI

(with HO cause)

Start T7

MTCHBUTI (1.) (start)Start TTRAU (**)

Start T_MSRFPCI CC (HO RAC; HO CMD)

AOUINIRH (*)AININIRH (*)

Stop T7

DATRQ (HO CMD)

Start T8

HO ACCESS

Stop TTRAU (**)

Start T3124

DT1 (HO CMD; HO CMD) (***)

ATTCHSEI (1.)if last TCH startAALTCHTI (1.)

FACCH

A30808-X3247-M41-3-7618 61

InformationSystem


ESTIN

DATIN (HO CMP)

MRPCI

DT1 (HO CMP)

DT1 (CL CMP)

DT1 (CL CMD)

Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITIONINDICATION.TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of MSC-controlled handover this isdone on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.

(**)

(*)

FACCH

FACCH

(cause: handoversuccessful)

HANDOVER COMMAND contains the BCCH and BSIC frequency of an internal neighbour cell.(***)


Stop T3124

PHYS INFO

Start T3105

Stop T3105

SABM

TNTCHCL (1.)

I (HO CMP)

UA

SUCTCHSE (1.)

Stop T8

SOUINIRH (*)SININIRH (*)NRCLRCMD (3.)

RELRQ

RELCN

RCHRL (Old TCH)

RCHRA

MTCHBUTI (stop)AALTCHTI (stop)

Stop T_MSRFPCI

FACCH

FACCH

62 A30808-X3247-M41-3-7618


1.2.4.10 Successful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC


CHNAK

CHNAV (New SDCCH)

I (HO CMD)Start T8

HANDO

Start T3124


NATTSDPEATINHIRC (*)If last SDCCH startASDCALTI

Start THORQST

Start T_MSRFPCI

UI (MEAS REP)

HO ACCESS

UI (PHYS INFO)

SACCH

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SDCCH

SDCCH

SDCCH

SDCCH

(with HO cause)

BWHCI

DATRQ (HO CMD)

AININIRH (*)AOUINIRH (*)AISHINTE

Stop T3105ESTIN

SABM

UA

SDCCH

SDCCH

SDCCH transaction or call in SDCCH phase in progress ...

Stop T8

DATIN (HO CMP)

SINTHINT (*)SININIRH (*)SOUINIRH (*)SISHINTESINHOBSC (*)

I (HO CMP)FACCH

A30808-X3247-M41-3-7618 63

InformationSystem



MRPCI

ASDCALTI (stop)

NASUSDPE

DT1 (HOPER)


(*)


RELRQ

RELCN

RCHRL (Old SDCCH)

RCHRA


64 A30808-X3247-M41-3-7618


1.2.4.11 Unsuccessful SDCCH-SDCCH Inter-Cell Handover Attempt, Intra-BSC, No SDCCH Available in Target Cell


......

......

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITONINDICATION.When the BSC receives an INTERCELL HANDOVER CONDITION INDICATION for andSDCCH-SDCCH handover with a valid target cell, it first checks the administrative state(locked/unlocked/shutting down) and the availability state (enabled/disabled) of the target BTS objects.Only if the BSC finds one target BTS in state "unlocked/enabled", the BSC starts to search for anavailable SDCCH in the "idle list" of the target cell. Only in this case the measurements ATINHIRC(for the originating BTS) and NATTSDPE (for the target BTS) are triggered. If no SDCCH can be founddue to SDCCH congestion, "locked" state of the TRXs or/and "locked" state of the CHAN objects in thetarget BTS, ATSDCMBS is triggered for the target BTS in addition and the next target cell is analyzed.If no target BTS in state "unlocked/enabled" can be found, NHOINRHA is triggered. In this case neitherATINHIRC nor NATTSDPE nor ATSDCMBS are increased.

(*)

BWHCI

(with HO cause)

NATTSDPE (**)ATSDCMBS (**)ATINHIRC (*)(**)NHOINRHA (3.)(**)

BWHCI

(with HO cause)

Start THORQST

Expiry THORQST

Call in progress...


(**)

NATTSDPE (**)ATSDCMBS (**)ATINHIRC (*)(**)NHOINRHA (3.)(**)

A30808-X3247-M41-3-7618 65

InformationSystem


1.2.4.12 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC, withLoss of MS (Loss of HO CMD, T8 Expiry)


CHNAK

CHNAV (New SDCCH)

I (HO CMD)Start T8

AININIRH (*)AOUINIRH (*)AISHINTE

NATTSDPEATINHIRC (*)If last SDCCH startASDCALTI

Start THORQST

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

BWHCI

(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SDCCH

Expiry T8

UNIHIRLCUISHIRLC

HO CMD islost ...


DT1 (CL CMD)

DT1 (CL CMP)RELCN

RELRQ

RCHRL (Old SDCCH)

RCHRA

Call in progress...

NRCLRCMD (13.)

NRCLRREQ (21.)

66 A30808-X3247-M41-3-7618



ASDCALTI (stop)


(*)

Reset T_MSRFPCI

RCHRA

RLSD

RCHRL (New SDCCH)

RLC

Call release ...

A30808-X3247-M41-3-7618 67

InformationSystem


1.2.5 Inter-Cell Handover, Inter-BSC

1.2.5.1 Successful Inter-Cell Handover, Inter-BSC, FR Call

BTSold BTSnewMS

CHNAK

Start T7

Start T3124

HO ACCESS

DT1 (HO DET)

I (HO CMD)

HANDO

Stop T7

BSCnewBSCold MSC

ATINBHDO (*)

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH

BWHCI(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

Start T_MSRFPCI


ATTCHSEI (1.)If last TCH startAALTCHTI (1.)

Stop TTRAU (**)

CC (HO RAC; HO CMD)DT1 (HO CMD; HO CMD)

Start T8FACCH

FACCH

HO ACCESSFACCH

Start Trr7 (***)

CHNAV (New TCH)

UI (PHYS INFO)


FACCH

Call in progress...

68 A30808-X3247-M41-3-7618


BTSold BTSnewMS

I (HO CMP)

DATIN (HO CMP)

MRPCI

DT1 (HO CMP)

RELRQ

DT1 (CL CMD)

Stop T8

SUINBHDO (*)NRCLRCMD (3.)

BSCnewBSCold MSC

DT1 (CL CMP)RELCN

RCHRA

RLSD

SUCTCHSE (1.)



TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC handover this is done onthe CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.

(**)

(*)


FACCH

Stop T_MSRFPCI

SABM

Stop T3105

TNTCHCL (1.)

ESTIN

UAFACCH

FACCH

Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.(***)

Stop Trr7 (***)

RLC

RCHRL (Old TCH)


A30808-X3247-M41-3-7618 69

InformationSystem


1.2.5.2 Unsuccsessful Inter-Cell Handover, Inter-BSC, No TCH Available inTarget Cell, FR Call

BTSold BTSnewMS BSCnewBSCold MSC

ATTCHSEI (1.)**ATCHSMBS (1.)**

Start T7

DT1 (HO RQD)

CR (HO REQ)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

(cause: no radioresource available)

CREF (HO FAI)

DT1 (HO RRJ)

Expiry T7

Call in progress...


NHOINRHA (2.)*

NRINHDFL


Note: Subcounter (2.) of the measurement NHOINRHA is triggered when the administrable BSSMAPtimer T7 (database parameter name BSCT7) expires; with suitable settings of BSCT7 this happensafter the receipt of a HANDOVER REQUIRED REJECT message from the MSC. This means that thetimer T7 must be set appropriately (e.g. BSCT7=HLFSEC-6) to ensure that NHOINRHA (2.) countscorrectly in case of Inter-BSC handover.If - by chance - the call is released before T7 expires, NHOINRHA (2.) is not triggered.

(*)

(**) ATTCHSEI and ATCHSMBS are only triggered if the target BTS indicated in the HO REQ message isin state unlocked/enabled.

70 A30808-X3247-M41-3-7618


1.2.5.3 Unsuccessful Inter-Cell Handover, Inter-BSC, with Reversion to OldTCH, FR Call (T3124 Expiry)


CHNAK

Start T7

Start T3124

HO ACCESS

I (HO CMD)

Stop T7

ATINBHDO (*)

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST



CC (HO RAC; HO CMD)

DT1 (HO CMD; HO CMD)

Start T8FACCH

FACCH

HO ACCESSFACCH

HO ACCESSdoes not getthrough*****

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)Start Trr7 (***)

CHNAV (New TCH)

SABMESTINFACCH

Expiry T3124

Call in progress...

A30808-X3247-M41-3-7618 71

InformationSystem




DT1 (HO FAI)

NRUNINHD

DT1 (CL CMD)

RLSD

RCHRA

RLC



(**)

(*)

UA

I (HO FAIL)DATIN (HO FAIL)

Stop T8

FACCH

FACCH (cause:protocol errorunspecified****)

(cause: equipmentfailure)


RCHRL (New TCH)


Reset T_MSRFPCI

Stop Trr7 (***)

(cause: radiointerface fail-ure, reversionto old channel)

(****) The actual cause value used by the MS might differ from the one indicated in the message flow - othercause values such as "abnormal release, timer expired" or "abnormal release, unspecified" etc. mightbe used.The handover might not only fail due to the fact that no PHYSICAL INFORMATION is received aftertransmission of the HANDOVER ACCESS on the target channel. The MS can still return to the oldchannel after it has received the PHYSICAL INFORMATION from the BTS. This happens when thelayer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmissionof the SABM on the target channel.

(*****)

NRCLRCMD (4.)

DT1 (CL CMP)

72 A30808-X3247-M41-3-7618


1.2.5.4 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Lossof HO CMD, T8<Trr7), FR Call (T8 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

I (HO CMD)

Stop T7

BSCnewBSCold MSC

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

Start T_MSRFPCI



Stop TTRAU (**)

CC (HO RAC; HO CMD)

DT1 (HO CMD)

Start T8FACCHHO CMD islost ...

Start Trr7 (***)

Expiry T8

NRFLTCH (9.)


CHNAV (New TCH)

ATINBHDO (*)

Call in progress...

NRCLRREQ (3.)

A30808-X3247-M41-3-7618 73

InformationSystem


BTSold BTSnewMS

DT1 (CL CMD)

BSCnewBSCold MSC

DT1 (CL CMP)

RLSD

RLC



(**)

DATRQ (CHREL)

DESAC

RELIN

RCHRA

Expiry Trr7 (***)

DT1 (CL CMD)

DT1 (CL CMP)

RLSD

RCHRA

RLC


Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.Its value is hardcoded to 15 sec..

(***)


(*)

RCHRL (New TCH)

RCHRL (Old TCH)

Reset T_MSRFPCI

NRCLRCMD (1.)

74 A30808-X3247-M41-3-7618


1.2.5.5 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Lossof HO CMD, T8>Trr7), FR Call (Trr7 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

Stop T7

BSCnewBSCold MSC

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

Start T_MSRFPCI



Stop TTRAU (**)

CC (HO RAC; HO CMD)

DT1 (HO CMD)

Start T8

HO CMD islost ...

Start Trr7 (***)

Reset T8

DT1 (CL CMD)(cause: call control)

Expiry Trr7

DT1 (CL CMP)

DT1 (CL CMD)

DT1 (CL CMP)


ATINBHDO (*)

I (HO CMD)FACCH

CHNAV (New TCH)

Call in progress...

NRCLRCMD (4.)NRCLRCMD (2.)

A30808-X3247-M41-3-7618 75

InformationSystem



RLSD

RLC



(**)

DATRQ (CHREL)

DESAC

RELIN

RCHRA

RLSD

RCHRA

RLC


(***)


(*)

RCHRL (New TCH)

RCHRL (Old TCH)

Reset T_MSRFPCI

76 A30808-X3247-M41-3-7618


1.2.5.6 Unsuccessful Inter-Cell Handover, Inter-BSC, with Loss of MS,Handover Access Failure (No SABM received after Transmission) ofPHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU)

BTSold BTSnewMS

CHNAK

Start T7

I (HO CMD)

Stop T7

BSCnewBSCold MSC

ATINBHDO (*)

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

Start T_MSRFPCI



Stop TTRAU (**)


Start T8FACCH

Start Trr7 (***)

CHNAV (New TCH)

Call in progress...

HO ACCESSFACCH

HO ACCESSFACCH

Start T3124

A30808-X3247-M41-3-7618 77

InformationSystem



DT1 (HO DET)HANDO

UI (PHYS INFO)

Start T3105

FACCH

MS does not react toPHYS INFO, noSABM is received atthe BTS.

Expiry T3105UI (PHYS INFO)

Start T3105

FACCH

Expiry T3105UI (PHYS INFO)

Start T3105

FACCH


Expiry T3105 (****)

CONFL

DT1 (CL REQ)(cause: radiointerfacemessagefailure)

DT1 (CL CMD)


(cause: handoveraccess failure)

DT1 (CL CMD)

NRCLRCMD (1.)

NRCLRREQ (3.)

78 A30808-X3247-M41-3-7618





(**)

(*)


RCHRL

RELIN

RCHRA

MTCHBUTI (1.)(Stop)AALTCHTI (1.)(Stop)

Expiry T8

NRFLTCH (9.)

DT1 (CL REQ)

(Cause:radio interfacemessage failure)

DT1 (CL CMD)

DT1 (CL CMP)

RLSD

RLC

DATRQ (CHREL)

DESAC

RELIN

RCHRA

RCHRL (Old TCH)

When T3105 has expired NY1+1 times, the BTS sends the CONNECTION FAILURE INDICATIONwith cause “handover access failure”.

(****)

NRCLRCMD (1.)

NRCLRREQ (3.)

A30808-X3247-M41-3-7618 79

InformationSystem


1.2.5.7 Successful Inter-Cell Handover, Inter-BSC, No TCH Available inFirst (external) Cell, Second Target Cell Belongs to Originating BSC,FR Call

iThe red colour indicates the BSC serving the first (really external) target cell in the targetcell list of the HANDOVER REQUIRED message.

BTSold BSC BMS

CHNAK

BSC ABTSnew MSC

NRINHDFL

Start T7

DT1 (HO RQD)CR (HO REQ)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

ATTCHSEI (1.)ATCHSMBS (1.)

CREF (HO FAI)(cause: no radioresource available)

CR (HO REQ)

CC (HO RAC; HO CMD)Start T_MSRFPCI

Stop TTRAU (**)

Stop T7

AOUINIRH (*)AININIRH (*)

Start T8

Start TTRAU (**)

I (HO CMD)

FACCH

CHNAV (New TCH)

Call in progress...

(belongs to BSC A) (belongs to BSC A)

Start T3124HANDOFACCH


ATTCHSEI (1.)if last TCH startAALTCHTI (1.)

DT1 (HO CMD; HO CMD) (***)

DATRQ (HO CMD)


HO ACCESS

80 A30808-X3247-M41-3-7618


ESTIN

DATIN (HO CMP)

MRPCI

DT1 (HO CMP)

DT1 (CL CMP)

SUCTCHSE (1.)

DT1 (CL CMD)


Stop T3105

Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITIONINDICATION.TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is doneafter receipt of the HANDOVER DETECT message.

(**)

(*)

FACCH

FACCH

FACCH

FACCH

Stop T_MSRFPCI

Stop T8


RCHRL (Old TCH)

BTSold BSC BMS BSC ABTSnew MSC(belongs to BSC A) (belongs to BSC A)

HANDOVER COMMAND contains the BCCH and BSIC frequency of an internal neighbour cell.(***)

PHYS INFO

SABM

UA

I (HO CMP)

RELRQ

RELCN

RCHRA

MTCHBUTI (stop)AALTCHTI (stop)

SOUINIRH (*)SININIRH (*)NRCLRCMD (3.)

TNTCHCL (1.)

A30808-X3247-M41-3-7618 81

InformationSystem


1.2.5.8 Successful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC

BTSold BTSnewMS

CHNAK

Start T7

Start T3124

HO ACCESS

DT1 (HO DET)

I (HO CMD)

HANDO

Stop T7

BSCnewBSCold MSC

ATINBHDO (*)AOINTESH

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start T_MSRFPCI

NATTSDPEIf last SDCCH startASDCALTI


Start T8SDCCH

SDCCH

HO ACCESSSDCCH

Start Trr7 (***)

CHNAV (New SDCCH)

UI (PHYS INFO)


SDCCH

Call in progress...

(channel type:SDCCH)

82 A30808-X3247-M41-3-7618


BTSold BTSnewMS

I (HO CMP)

DATIN (HO CMP)

MRPCI

DT1 (HO CMP)

RELRQ

DT1 (CL CMD)

Stop T8

SUINBHDO (*)SOINTESHNRCLRCMD (3.)

BSCnewBSCold MSC

DT1 (CL CMP)RELCN

RCHRA

RLSD

NASUSDPE

ASDCALTIMBUSYSSP (n.) (**)(accumulation)


(*)


SDCCH

Stop T_MSRFPCI

SABM

Stop T3105

ESTIN

UASDCCH

SDCCH


Stop Trr7 (***)

RLC

RCHRL (Old SDCCH)


Note: Subcounter of MBUSYSSP depends on type of original SCDDH transaction(**)

A30808-X3247-M41-3-7618 83

InformationSystem


1.2.5.9 Unsuccsessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC, NoSDCCH Available in Target Cell

BTSold BTSnewMS

NRINHDFL

BSCnewBSCold MSC

NATTSDPEATSDCMBS

Start T7

DT1 (HO RQD)

CR (HO REQ)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST


CREF (HO FAI)

DT1 (HO RRJ)

Expiry T7

Call in progress...



Note: If the handover condition persists and another INTERCELL HANDOVER CONDITION INDICATIONis received from the BTS after expiry of T7, the same procedure is repeated in exactly the same way.

NHOINRHA (2.)

84 A30808-X3247-M41-3-7618


1.2.5.10 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC withLoss of MS (Loss of HO CMD, T8<Trr7, T8 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

I (HO CMD)

Stop T7

BSCnewBSCold MSC

DT1 (HO RQD)

CR (HO REQ)

DATRQ (HO CMD)

UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start T_MSRFPCI

NATTSDPEIf last SDCCH startASDCALTI

CC (HO RAC; HO CMD)

DT1 (HO CMD)

Start T8SDCCH

HO CMD islost ...

Start Trr7 (***)

Expiry T8

NRFLSDCCUMCSHLC

DT1 (CL REQ)(cause:radio interfacemessage failure)

CHNAV (New SDCCH)

ATINBHDO (*)AOINTESH

Call in progress...


NRCLRREQ (21.)

A30808-X3247-M41-3-7618 85

InformationSystem


BTSold BTSnewMS

DT1 (CL CMD)

BSCnewBSCold MSC

DT1 (CL CMP)

RLSD

RLC

ASDCALTI

DATRQ (CHREL)

DESAC

RELIN

RCHRA

Expiry Trr7 (***)

DT1 (CL CMD)

DT1 (CL CMP)

RLSD

RCHRA

RLC



(***)


(*)

RCHRL (New SDCCH)

RCHRL (Old SDCCH)

Reset T_MSRFPCI

NRCLRCMD (4.)

ASDCALTIMBUSYSSP (n.) (**)(accumulation)

Note: Subcounter of MBUSYSSP depends on type of original SCDDH transaction(**)

86 A30808-X3247-M41-3-7618


1.2.6 Intra-Cell Handover

1.2.6.1 Successful Intra-Cell Handover, FR Call

iNote: This message flow is valid for intra-cell handover due to quality,intra-cell handover complete <--> inner in concentric cells andintra-cell handover far <--> near in extended cells.The difference just consists in the handover cause.

BTS BSCMS MSC

WIHCI

CHNAK


SABM

Start T10

ESTIN



UA

TNTCHCL (1.)

Start TTRAU

UI (MEAS REP)SACCH

(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start T_MSRFPCI

Old FACCH

New FACCH

New FACCH

Stop TTRAU (**)

CHNAV (New TCH)

ATINHIAC (*)

SINTHITA (*)SINHOBSC (*)

DATIN (ASS CMP)I (ASS CMP)

New FACCH

Call in progress...

Stop T10

A30808-X3247-M41-3-7618 87

InformationSystem


BTS BSCMS MSC


RELRQ

RELCN

RCHRA

SUCTCHSE (1.)


(*)

(with HO cause)

MRPCI

Stop T_MSRFPCI

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-cell handover this is done afterreceipt of the ESTABLISH INDICATION for the target TCH.

(**)

DT1 (HOPER)

RCHRL (Old TCH)


88 A30808-X3247-M41-3-7618


1.2.6.2 Unsuccessful Intra-Cell Handover Due to Quality, No TCH Available,FR Call


WIHCI

ATTCHSEI (1.)ATCHSMBS (1.)NHOINRHA (4.)

ATTCHSEI (1.)(BTS new)ATINHIRC (*)If last TCH startAALTCHTI (1.)

BWHCI (**)

UI (MEAS REP)SACCH

(cause:downlink/uplink

quality)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH


quality)


(*)

Only for intra-cell handover due to quality. An inter-cell handover due to quality is triggered, if thehandover conditions persist and the call is still on the old TCH when the next HANDOVER CONDITIONINDICATION is sent after expiry of THORQST.

(**)

Start THORQST

Expiry THORQST

Call in progress...

Call continuation with inter-cell handover attempt...

A30808-X3247-M41-3-7618 89

InformationSystem


1.2.6.3 Unsuccessful Intra-Cell Handover Due to Quality with Reversion toOld TCH, FR Call

BTS BSCMS MSC

WIHCI

CHNAK


I (ASS FAIL)

Start T10

ESTIN


UNINHOIA (*)

Start TTRAU

UI (MEAS REP)SACCH

(cause:downlink/uplinkquality)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start T_MSRFPCI

(cause: protocolerror unspecified)

DATIN (ASS FAIL)

Stop T10

Old FACCH

Old FACCH

SABMOld FACCH

SABMNew FACCH

Access to targetchannel fails ...

UA


ATINHIAC (*)

CHNAV (New TCH)

Reset TTRAU

Reset T_MSRFPCI

RCHRL (New TCH)

Call in progress...

90 A30808-X3247-M41-3-7618


BTS BSCMS MSC

UI (MEAS REP)SACCH

BWHCI (**)(cause:downlink/uplink quality)

Only for intra-cell handover due to quality. An inter-cell handover due to quality is triggered, if thehandover conditions persist and the call is still on the old TCH when the next HANDOVER CONDITIONINDICATION is sent after expiry of THORQST.

(**)

RCHRA

UI (MEAS REP)SACCH



(*)

Expiry THORQST

Call continuation with inter-cell handover attempt ...

A30808-X3247-M41-3-7618 91

InformationSystem


1.2.6.4 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASSCMD, T10 < TTRAU), FR Call (T10 Expiry)

BTS BSCMS MSC

WIHCI

CHNAK

DATRQ (ASS CMD)I (ASS CMD)Start T10



DT1 (CL REQ)

RELCN

RCHRA

DT1 (CL CMD)

UNIHIALC

DT1 (CL CMP)

RELRQ RLSD

RLC

Old FACCH


ATINHIAC (*)

UI (MEAS REP)SACCH

(with HO cause)

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

ASS CMDis lost ...

Start T_MSRFPCI

Reset TTRAU

Reset T_MSRFPCI

Expiry T10

CHNAV (New TCH)

RCHRL (New TCH)

Call in progress...

(cause, radio interfacemessage failure)NRCLRREQ (3.)

NRCLRCMD (1.)

92 A30808-X3247-M41-3-7618


BTS BSCMS MSC

RCHRA


(*)


RCHRL (Old TCH)

A30808-X3247-M41-3-7618 93

InformationSystem


1.2.6.5 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASSCMD, T10>TTRAU), FR Call (TTRAU Expiry)

BTS BSCMS MSC

WIHCI

CHNAK

DATRQ (ASS CMD)I (ASS CMD)Start T10



DT1 (CL REQ)

RELCN

RCHRA

DT1 (CL CMD)

Expiry TTRAU

NRFLTCH

DT1 (CL CMP)RELRQ

Old FACCH

ATINHIAC (*)

UI (MEAS REP)SACCH

(with HO cause)

UI (MEAS REP)SACCH

Start THORQST

Start TTRAU

ASS CMDis lost ...

Start T_MSRFPCI

CONFL(cause: remote

transcoder failure)

Reset T_MSRFPCI

CHNAV (New TCH)

RCHRL (New TCH)


Call in progress...

(cause, radio interfacemessage failure)NRCLRREQ (3.)

NRCLRCMD (1.)

94 A30808-X3247-M41-3-7618


BTS BSCMS MSC

RCHRA


(*)

RCHRL (Old TCH)

RLSD

RLC


A30808-X3247-M41-3-7618 95

InformationSystem


1.2.6.6 Successful Intra-Cell Handover Due to Quality, MSC Controlled, FRCall

BTS BSCMS MSC

DT1 (HO RQD)

Start T7

HANDO


CR (HO REQ)

CHNAKCC (HO RAC; HO CMD)


I (HO CMD)

HO ACCESS

Start T3124

HO ACCESS

DATRQ (HO CMD)

DT1 (HO DET)

WIHCI

CHNAV (New TCH)


UI (MEAS REP)SACCH


quality)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start T_MSRFPCI

Stop T7

Start T8

Stop TTRAU (**)

Old FACCH

New FACCH

New FACCH

Stop T3124

UI (PHYS INFO)

Start T3105

New FACCH

ESTIN

TNTCHCL (1.)

SABM

UA

Stop T3105New FACCH

New FACCH

Call in progress...

96 A30808-X3247-M41-3-7618


BTS BSCMS MSC

I (HO CMP)

MRPCI

DATIN (HO CMP)

DT1 (HO CMP)

DT1 (CL CMD)

DT1 (CL CMP)RELRQ

RLSD

RLC

RELCN

RCHRL (Old TCH)

RCHRA

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of MSC controlled handover this isdone on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.

(**)


New FACCH

(cause: handover successful)

Stop T_MSRFPCI


Stop T8

NRCLRCMD (3.)

A30808-X3247-M41-3-7618 97

InformationSystem


1.2.6.7 Successful SDCCH-SDCCH Intra-Cell Handover

BTS BSCMS MSC

WIHCI

CHNAK


SABM

ESTIN

NATTSDPEASDCALTI (start)

UA

UI (MEAS REP)SACCH

(with HO cause)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start THORQST

Start T_MSRFPCI

Old SDCCH

New SDCCH

New SDCCH

CHNAV (New SDCCH)

ATINHIAC (*)AISHINTR

SINTHITA (*)SISHINTRSINHOBSC (*)


New SDCCH

Call in progress...

Stop T10

NASUSDPE(with HO cause)

MRPCI

Stop T_MSRFPCI

DT1 (HOPER)

Start T10

98 A30808-X3247-M41-3-7618


BTS BSCMS MSC

RELRQ

RELCN

RCHRA


(*)

RCHRL (Old SDCCH)


ASDCALTI (stop)MBUSYSSP (n.)(accumulation)

A30808-X3247-M41-3-7618 99

InformationSystem


1.2.7 Directed Retry, Intra-BSC

1.2.7.1 Successful Directed Retry, Intra-BSC, FR Call


CHNAK

CHNAV (New TCH)

I (HO CMD)

MTCHBUTI (1.)

Start T8

AOUINIRH (7.)AININIRH (7.)

(HANDO)

Start T3124

ATINHIRC (7.)ATTCHSEI (1.)If last TCH startAALTCHTI (1.) (**)

Start TTRAU

Stop TTRAU (***)

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

FHREQ

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SDCCH

FACCH

Start T3105

UI (PHYS INFO)FACCH

DT1 (ASS REQ)

BWHCI

(cause: ’forced’, target cell list)

ATTCHSEI (1.) (*)ATCHSMBS (1.) (*)TASSATT (2.)

Start TIMERFHO

FACCH

(contains CGI of BTS0and GSM08.08 cause

’forced’)

Stop T3124

Stop T3105

SABM

UA

FACCH

FACCH

ESTIN

TNTCHCL (1.)

Call setup ...

HO ACCESS

100 A30808-X3247-M41-3-7618



MRPCI

Stop T8

DATIN (HO CMP)


DT1 (ASS COM)

SOUINIRH (7.)SININIRH (7.)SINHOBSC (7.)SINTHINT (7.)

Stop T_MSRFPCI

RELRQ

RELCN

RCHRL (SDCCH)

RCHRA

I (HO CMP)FACCH

DATRQ (CHMM)I (CHMM)

FACCH

I (CHMMACK)FACCH

DATIN (CHMMACK)

I (ALERT)FACCH

DT1 (ALERT)

DT1 (CONNECT)DATRQ (ALERT)

I (CONNECT)FACCH

DATRQ (CONNECT)

DT1 (CONACK)

I (CONACK)FACCH DATIN (CONACK)

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC directed retry this is doneon receipt of the HANDOVER DETECT message.

(***)


Event is counted for the target cell.(**)Event is counted for the serving cell.(*)

ASDCALTI (stop)MBUSYSSP (1.)(accumulation)

A30808-X3247-M41-3-7618 101

InformationSystem


1.2.7.2 Unsuccessful Directed Retry, Intra-BSC, No Target Cell Available,FR Call

BTS BSCMS MSC

FHREQ

BWHCI

DT1 (DISC)

DATRQ (DISC)

I (DISC)

TASSFAIL (8.)

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SDCCH

DT1 (ASS REQ)


DT1 (ASS FAI)(cause: no radio resource

available)

(cause: ’forced’,emptytarget cell list)

UI (MEAS REP)SACCH

Call setup ...

Call release ...

NHOINRHA (1.)

102 A30808-X3247-M41-3-7618


1.2.7.3 Unsuccessful Directed Retry, Intra-BSC, 1 Target Cell Available,Target Cell Congested, FR Call


I (DISC)

TASSFAIL (8.)

ATINHIRC (7.)ATTCHSEI (1.) (**)ATCHSMBS (1.) (**)

UI (MEAS REP)SACCH FHREQ

UI (MEAS REP)SACCH

SDCCH

DT1 (ASS REQ)

BWHCI

(cause: ’forced’, one target cell included)


DT1 (ASS FAI)(cause: no radio

resource available)

DT1 (DISC)(cause: normal,

unspecified)DATRQ (DISC)


UI (MEAS REP)SACCH

Call setup ...

Call release ...

A30808-X3247-M41-3-7618 103

InformationSystem


1.2.7.4 Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH,FR Call (T3124 Expiry)


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8


Start T3124

ATINHIRC (7.)ATTCHSEI (1.) (**)If last TCH startAALTCHTI (1.) (**)

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

FHREQUI (MEAS REP)

SACCH

UI (MEAS REP)SACCH

SDCCH

DT1 (ASS REQ)

BWHCI



Start TIMERFHO

HO ACCESSFACCH


’forced’)

HO ACCESSFACCH

Expiry T3124

HO ACCESSdoes notget through****

ESTINSABM

SDCCH

UASDCCH

Call setup ...

104 A30808-X3247-M41-3-7618



RCHRL (New TCH)

Stop T8

HOFITABSUNINHOIE (7.)

RCHRA

I (HO FAIL)

Reset TTRAU

SDCCH DATIN (HO FAIL)

(cause: protocol error, unspecified***)

DT1 (ASS FAI)

(cause: radio interfacefailure - reversion to old

channel)

TASSFAIL (7.)

Reset T_MSRFPCI


DT1 (DISC)

SDCCH

DATRQ (DISC)I (DISC)(cause: normal,

unspecified)


Call release ...

(****) The actual cause value used by the MS might differ from the one indicated in the message flow - othercause values such as "abnormal release, timer expired" or "abnormal release, unspecified" etc. mightbe used.The handover might not only fail due to the fact that no PHYSICAL INFORMATION is received aftertransmission of the HANDOVER ACCESS on the target channel.Possible problem scenarios are:- HO ACCESS not correctly received at BTS- PHYS INFO not correctly received at MSThe MS can still return to the old channel after it has received the PHYSICAL INFORMATION fromthe BTS. This happens when the layer 2 connection setup fails, i.e. when the MS does not receive anyUA after repeated transmission of the SABM on the target channel.

(*****)

A30808-X3247-M41-3-7618 105

InformationSystem


1.2.7.5 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss ofHO CMD, T8 < TTRAU), FR Call (T8 Expiry)


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8



Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

FHREQUI (MEAS REP)

SACCH

UI (MEAS REP)SACCH

SDCCH

DT1 (ASS REQ)

BWHCI



Start TIMERFHO


’forced’)

HO CMDis lost ...

Expiry T8

UNIHIRLC

DT1 (CL REQ)(cause: radiointerface messagefailure)

DT1 (CL CMD)

Call setup ...

NRCLRCMD (1.)

NRCLRREQ (3.)

106 A30808-X3247-M41-3-7618



RCHRL (New TCH)

RCHRA

Reset TTRAU

Reset T_MSRFPCI


DT1 (CLCMP)

RELRQ

RELCN

RCHRL (SDCCH)

RCHRA

Reset TIMERFHO

RLSD

RLC



A30808-X3247-M41-3-7618 107

InformationSystem


1.2.7.6 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss ofHO CMD, T8 > TTRAU), FR Call (TTRAU Expiry)


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8


Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

FHREQUI (MEAS REP)

SACCH

UI (MEAS REP)SACCH

SDCCH

DT1 (ASS REQ)

BWHCI

(cause: ’forced’)


Start TIMERFHO


’forced’)

HO CMD islost ...

DT1 (CL REQ)(cause: radiointerfacemessage failure)

DT1 (CL CMD)

Expiry TTRAU CONFL(cause: remote

transcoder failure) NRFLTCH (8.)

DT1 (CLCMP)


Call setup ...

NRCLRCMD (1.)

NRCLRREQ (3.)

108 A30808-X3247-M41-3-7618



RCHRL (New TCH)

RCHRA

Reset T_MSRFPCI


RELRQ

RELCN

RCHRL (SDCCH)

RCHRA

RLSD

RLC



A30808-X3247-M41-3-7618 109

InformationSystem


1.2.8 Directed Retry, Inter-BSC

1.2.8.1 Successful Directed Retry, Inter-BSC, FR Call

BTSold BTSnewMS

CHNAK

Start T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH

BWHCIUI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start TTRAU

Start T_MSRFPCI


Stop TTRAU (**)

DT1 (ASS REQ)

(cause: ’forced’) DT1 (ASS FAI)

(cause: directed retry)

TASSFAIL (9.)





FHREQ

Start TIMERFHO

CHNAV (New TCH)

I (HO CMD)SDCCH

ATINBHDO (7.)

DATRQ (HO CMD)

Start T8

Stop T7

CC (HO RAC; HO CMD)


Start Trr7 (***)

Call setup ...

110 A30808-X3247-M41-3-7618


BTSold BTSnewMS

Start T3124

HO ACCESS

DT1 (HO DET) HANDO

BSCnewBSCold MSC

FACCH

I (HO CMP)

DATIN (HO CMP)FACCH

SABM

UI (PHYS INFO)


Stop T3105

TNTCHCL (1.)

ESTIN

UAFACCH

FACCH

FACCH

DT1 (HO CMP)DT1 (CL CMD)

Stop T8

SUINBHDO (7.)

SUCTCHSE (1.)(cause: handover

successful) MRPCI

Stop T_MSRFPCI

DATRQ (CHMM)

DATIN (CHMMACK)

I (CHMM)FACCH

I (CHMMACK)FACCH

Release of resources...

DT1 (ALERT)DATRQ (ALERT)

I (ALERT)FACCH

DT1 (CONNECT)DATRQ (CONNECT)

I (CONNECT)FACCH

A30808-X3247-M41-3-7618 111

InformationSystem




TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC directed retry this is doneon the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.

(**)

DATIN (CONACK)DT1 (CONACK)

I (CONACK)FACCH


112 A30808-X3247-M41-3-7618


1.2.8.2 Unsuccessful Directed Retry, Inter-BSC, FR Call, no Radio Re-source available in Target Cell

BTSold BTSnewMS

Start T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH


UI (MEAS REP)SACCH


DT1 (ASS REQ)



TASSFAIL (9.)




NRINHDFL

FHREQ

CREF (HO FAI)

DT1 (HO RRJ)

Call setup ...



DT1 (CLCMD)(cause: call control)

Call release ...

Expiry T7*

NHOINRHA (2.)*

Note: NHOINRHA (2.) might not count in case of Inter-BSC directed retry due to the following reasons:If the MSC has rejected the inter-BSC directed retry handover attempt by sending a HANDOVERREQUIRED REJECT, it will immediately release the resources by sending a CLEAR COMMAND to theBSC. If the CLEAR COMMAND arrives before T7 expires, NHOINRHA (2.) is not triggered.This will happen with normal settings of BSCT7 (e.g. BSCT7=HLFSEC-6).

(*)

A30808-X3247-M41-3-7618 113

InformationSystem


1.2.8.3 Unsuccessful Directed Retry, Inter-BSC, with Reversion to SDCCH,FR Call (T3124 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

Stop T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH

BWHCI

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start TTRAU

Start T_MSRFPCICC (HO RAC; HO CMD)


FHREQ

DT1 (ASS REQ)

(cause: ’forced’)DT1 (ASS FAI)


TASSFAIL (9.)

(cause: directed retry)(cause: directed retry)


Start Trr7 (***)


I (HO CMD)SDCCH

ATINBHDO (7.)

DATRQ (HO CMD)

Start T8

Start TIMERFHO

Call setup ...


CHNAV (New TCH)

114 A30808-X3247-M41-3-7618


BTSold BTSnewMS

HO ACCESS

BSCnewBSCold MSC

FACCH

SABMESTIN

UASDCCH

SDCCH

Stop T8

NRUNINHD

DT1 (HO FAIL)

RCHRA

RLSD


RLC

HO ACCESSFACCH

HO ACCESSdoes not getthrough****

Expiry T3124

I (HO FAIL)SDCCH

DATIN (HO FAIL)

(cause: radio interfacefailure, reversion to oldchannel)

DT1 (CL CMD)(cause: equipmentfailure)

DT1 (CL CMP)

Reset TIMERFHO

Reset T_MSRFPCI

RCHRL (New TCH)

Call release ...

CL CMD

(cause: abnormalrelease, timer ex-pired****)


NRCLRCMD (4.)

A30808-X3247-M41-3-7618 115

InformationSystem



(****) The actual cause value used by the MS might differ from the one indicated in the message flow - othercause values such as "abnormal release, timer expired" or "abnormal release, unspecified" etc. mightbe used.

The handover might not only fail due to the fact that no PHYSICAL INFORMATION is received aftertransmission of the HANDOVER ACCESS on the target channel. The MS can still return to the oldchannel after it has received the PHYSICAL INFORMATION from the BTS. This happens when thelayer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmissionof the SABM on the target channel.

(*****)

116 A30808-X3247-M41-3-7618


1.2.8.4 Unsuccessful Derected Entry, Inter-BSC, with Loss of MS (Loss ofHO CMD, T8 < Trr7), FR Call (T8 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

Stop T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH

BWHCI

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)CC (HO RAC; HO CMD)DT1 (HO CMD; HO CMD)

DT1 (ASS REQ)

(cause: ’forced’)DT1 (ASS FAI)


TASSFAIL (9.)

(cause: directed retry)(cause: directed retry)


Start Trr7 (***)


I (HO CMD)SDCCH

ATINBHDO (7.)

DATRQ (HO CMD)

Start T8

HO CMD islost ...

Start TIMERFHO

FHREQ

CHNAV (New TCH)

Call setup ...


A30808-X3247-M41-3-7618 117

InformationSystem



DT1 (CLREQ)

Expiry T8

(cause: radio interfacemsg. failure)

DESAC

DT1 (CL CMD)

RELIN

RCHRA

RLSD


RLC

NRSLSDCC

DATRQ (CHREL)

(cause: abnormal re-lease, unspecified)

DT1 (CL CMP)

Expiry Trr7

RCHRL

RCHRA


DT1 (CL CMD)(cause: equipmentfailure)

Reset TIMERFHO

Reset T_MSRFPCI

RLSD

RLC

DT1 (CL CMP)


RCHRL (New TCH)

NRCLRCMD (4.)

118 A30808-X3247-M41-3-7618


1.2.8.5 Unsuccessful Directed Retry, Inter-BSC, with Loss of MS (Loss ofHO CMD, T8 > Trr7), FR Call (Trr7 Expiry)

BTSold BTSnewMS

CHNAK

Start T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH

BWHCI

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

Start TIMERFHO

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

FHREQ

DT1 (ASS REQ)



TASSFAIL (9.)





CHNAV (New TCH)

Call setup ...


A30808-X3247-M41-3-7618 119

InformationSystem


BTSold BTSnewMS

I (HO CMD)

BSCnewBSCold MSC

SDCCH

Reset T8

(cause:equipment failure)

RELRQ

DT1 (CL CMD)

RELCN

RCHRA

RLSD


RLC

ATINBHDO (7.)

DATRQ (HO CMD)

Start T8HO CMD islost ...

DT1 (CL CMP)RCHRA


Reset TIMERFHO

Reset T_MSRFPCI

Expiry Trr7

(cause:call control)

DT1 (CL CMD)

DT1 (CL CMP)


Stop T7

CC (HO RAC; HO CMD)


Start Trr7 (***)

RLSD

RLC

RCHRL (New TCH)

RCHRL (SDCCH)

NCLRCMD (2.) NCLRCMD (4.)

120 A30808-X3247-M41-3-7618


1.2.9 Forced Handover Due to O & M

1.2.9.1 Successful Forced Handover Due to O & M


CHNAK

CHNAV (New TCH)

I (HO CMD)

MTCHBUTI (1.)

Start T8

(HANDO)

Start T3124

ATINHIRC (8.)ATTCHSEI (1.)If last TCH startAALTCHTI (1.) (**)

Start TTRAU

Stop TTRAU (***)

Start T_MSRFPCI

UI (MEAS REP)SACCH

DATRQ (HO CMD)

FHREQ

HO ACCESS

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SDCCH

FACCH

Start T3105

UI (PHYS INFO)FACCH

BWHCI


Start TIMERFHO

HO ACCESSFACCH


’forced’)

Stop T3124

Stop T3105

SABM

UA

FACCH

FACCH

ESTIN

Call in progress, operator initiated shutdown of a BTS, TRX or TCH...


TNTCHCL (1.)

A30808-X3247-M41-3-7618 121

InformationSystem



MRPCI

Stop T8

DATIN (HO CMP)

DT1 (HO PER)

SOUINIRH (8.)SININIRH (8.)SINHOBSC (16.)SINTHINT (8.)

I (HO CMP)FACCH

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC directed retry this is doneon receipt of the HANDOVER DETECT message.

(***)



(cause: O & M intervention)

122 A30808-X3247-M41-3-7618


1.2.9.2 Successful Forced Handover Due to O & M, Inter-BSC, FR Call

BTSold BTSnewMS

CHNAK

Start T7

BSCnewBSCold MSC


UI (MEAS REP)SACCH


UI (MEAS REP)SACCH

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (**)

(cause: ’forced’)

(cause: O & Mintervention)

(cause: O & Mintervention) ATTCHSEI (1.)

If last TCH startAALTCHTI (1.)


FHREQ

Start TIMERFHO

CHNAV (New TCH)

I (HO CMD)SDCCH

ATINBHDO (8.)

DATRQ (HO CMD)

Start T8

Stop T7

CC (HO RAC; HO CMD)


Start Trr7 (***)

Call in progress, operator initiated shutdown of a BTS, TRX or TCH...

Start T3124

HO ACCESS

DT1 (HO DET) HANDOFACCH

SABM

UI (PHYS INFO)


Stop T3105FACCH

FACCH

A30808-X3247-M41-3-7618 123

InformationSystem



I (HO CMP)

DATIN (HO CMP)FACCH

TNTCHCL (1.)

ESTIN

UAFACCH

DT1 (HO CMP)DT1 (CL CMD)

Stop T8

SUINBHDO (8.)

SUCTCHSE (1.)(cause: handover

successful) MRPCI

Stop T_MSRFPCI

Release of resources in originating cell and call continuation in target cell ...

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC directed retry this is doneon the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.

(**)

124 A30808-X3247-M41-3-7618


1.2.9.3 Successful Forced Intra-Cell Handover Due to O & M, FR Call

BTS BSCMS MSC

CHNAK


SABM

Start T10

ESTIN


UATNTCHCL (1.)

Start TTRAU

Start T_MSRFPCI

Old FACCH

New FACCH

New FACCH

Stop TTRAU (**)

CHNAV (New TCH)

ATINHIAC (7.)

SINTHITA (7.)SINHOBSC (16.)


New FACCH

Call in progress, operator initiated shutdown of a TRX or TCH...

Stop T10

TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens whenthe BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-cell handover this is done afterreceipt of the ESTABLISH INDICATION for the target TCH.

(**)



RELRQ

RELCN

RCHRA

SUCTCHSE (1.)(cause: O & Mintervention)

MRPCI

Stop T_MSRFPCI

DT1 (HOPER)

RCHRL (Old TCH)

A30808-X3247-M41-3-7618 125

InformationSystem


1.2.10 Handover due to BSS Resource Management Criteria (TrafficHandover)

1.2.10.1 Successful Handover due to BSS Resource Management Criteria(Traffic Handover), FR Call


CHNAK

CHNAV (New TCH)

I (HO CMD)


Start T8

ATTCHSEI (1.)ATINHIRC (9.)If last TCH startAALTCHTI (1.)

Start TRFHOT

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

FACCH

(cause: traffic)

BWHCI

DATRQ (HO CMD)

Call in progress...

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SET ATTRIBUTE **(Traffic Handover enabled)

SET ATTRIBUTE ACK

Traffic Handover enabledin the BTS (m=1) ***

AININIRH (9.)AOUINIRH (9.)

BSC detects that thetraffic load in the BTS oldexceeds the thresholdTRFHITH

Expiry TRFCT*

126 A30808-X3247-M41-3-7618



HANDO

Start T3124


Stop TTRAU

HO ACCESS

UI (PHYS INFO)

HO ACCESSFACCH

FACCH

FACCH

Stop T3105ESTIN

SABM

UA

FACCH

FACCHTNTCHCL (1.)

MRPCI


Stop T8

DATIN (HO CMP)

SUCTCHSE (1.)

DT1 (HOPER)

SINTHINT (9.)SININIRH (9.)SOUINIRH (9.)SINHOBSC (12.)

Stop T_MSRFPCI (cause: distance)

RELRQ

RELCN

RCHRL (Old TCH)

RCHRA

I (HO CMP)FACCH


A30808-X3247-M41-3-7618 127

InformationSystem


Note: TRFCT represents a periodic cycle in which the BSC checks the traffic load in all its cells.

The message SET ATTRIBUTE is sent via the Abis O&M channel (LPDLM, SAPI 62) and enables thetraffic handover for the whole BTS . This means that the BTS makes the traffic handover decision forall calls currently busy in the cell and starts the timer TRFHOT (when it expires, the BTS makes the nexthandover decision for all calls that are busy at that point of time). This message flow just shows onesingle call for which the traffic handover was triggered and succesfully completed.

(**)(*)

The first traffic handover decision after the enabling of traffic handover in the BTS is based on the valuem=1. m is an internal counter which is used in the calculation process of the traffic handover decisionand which supports a mechanism for a dynamic decrease of the traffic handover margin for subsequenttraffic handover decisions.For further details, please refer to the associated feature description for traffic handover!

(***)

128 A30808-X3247-M41-3-7618


1.2.10.2 Unsuccessful Inter-Cell Handover due to BSS ResourceManagement Criteria (Traffic Handover), traffic load in Target Cellexceeds the threshold TRFLTH


NHOINRHA (3.)

Start TRFHOT

Expiry TRFHOT

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

(cause: traffic)

BWHCI***

Call in progress...

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

SET ATTRIBUTE ACK

(Traffic Handover enabled)

SET ATTRIBUTE **

Traffic Handover enabledin the BTS (m=1) ***

BSC detects that thetraffic load in the BTS oldexceeds the thresholdTRFHITH

Expiry TRFCT*

......

......

BWHCI****

BSC detects that thetraffic load in the targetcell is above thethreshold (TRFLTH)

BSC detects that the trafficload in the target cell is abovethe threshold (TRFLTH)

NHOINRHA (3.)

Call in continuation...

(cause: traffic)

Next Traffic Handoverdecisson (m=2)

A30808-X3247-M41-3-7618 129

InformationSystem


Note: TRFCT represents a periodic cycle in which the BSC checks the traffic load in all its cells.

The message SETATTRIBUTE is sent via the Abis O&M channel (LDDLM, SAPI 62) and enables thetraffic handover for the whole BTS . This means that the BTS makes the traffic handover decision forall calls currently busy in the cell and starts the timer TRFHOT (when it expires, the BTS makes the nexthandover decision for all calls that are busy at that point of time). This message flow just shows onesingle call for which triggered and succesfully completed.

(**)

(*)

The first traffic handover decision after the enabling of traffic handover in the BTS is based on the valuem=1. m is an internal counter which is used in the calculation process of the traffic handover decisionand which supports a mechanism for a dynamic decrease of the traffic handover margin for subsequenttraffic handover decisions.For further details, please refer to the associated feature description for traffic handover!

(***)

The traffic handover decision after the first expiry of TRFHOT is based on the value m=2.This margin is dynamically decreased with every expiry of TRFHOT.For further details, please refer to the associated feature description for traffic handover!

(****)

130 A30808-X3247-M41-3-7618


1.2.11 Queuing & Preemption

1.2.11.1 Queuing: Queued Assignment Request for FR TCH Is Served BeforeT11 Expiry, Directed Retry Enabled But No Target Cell Available,Preemption Disabled or Not Allowed for the Requesting Call

BTS BSCMS MSC

DT1 (ASS REQ)

Start T11

Start T_MSRFPCI

Stop T11

DT1 (QUIND)

BWHCI

PHCRQ

CHNAK

DATRQ (PROGRES)

I (PROGRES)

DT1 (PROGRES)

All TCHs in the BTS are busy...

SDCCH

Start TTRAU

Stop TTRAU (**)

MDURTCRQ (1.) (start)

PHCCN

FHREQ


(queuing allowedindicator=allowed)

(cause: forced,no target cell included)

BTS congestion ends during runtime of T11, 1 TCH becomes idle again...

MDURTCRQ (1.) (stop)

CHNAV


DATRQ (ASS CMD)

I (ASS CMD)SDCCH

NHOINRHA (1.)

A30808-X3247-M41-3-7618 131

InformationSystem


BTS BSCMS MSC

Stop T_MSRFPCI

FACCH

FACCH

SABM

UATNTCHCL (1.)

ESTIN

MRPCI

FACCH


DT1 (ASS COM)


Call setup completion ...


(**)

132 A30808-X3247-M41-3-7618


1.2.11.2 Queuing: Queued Assignment Request for FR TCH is Discardedfrom the Queue Before T11 Expiry Due to an Incoming FRAssignment Request with Higher Priority Directed Retry EnabledBut No Target Cell Available, Preemption Disabled or Not Allowedfor the Requesting Call

iThe blue colour indicates the events related to the second (high priority) call.

BTS BSCMS MSC

DT1 (ASS REQ)

Start T11 (low prio call)

DT1 (QUIND)

BWHCI

DATRQ (PROGRES)I (PROGRES)DT1 (PROGRES)


SDCCH


FHREQ




All places in the queue are occupied after the first call...

First call:low priority

DT1 (ASS REQ)*

Stop T11 (low prio call)

BWHCI*

MDURTCRQ (1.) (start)*

FHREQ*

ATTCHSEI (1.)*ATCHSMBS (1.)*TASSATT (2.)*

(Cause: forced,no target cell included)

Second call:high priority

NMSGDISQ (1.)MDURTCRQ (1.)(stop)NHOINRHA (1.)

Start T11* (high prio call)

NHOINRHA (1.)

A30808-X3247-M41-3-7618 133

InformationSystem


BTS BSCMS MSC

High priority call remains queued...*

DATRQ (PROGRES)*

I (PROGRES)*

DT1 (PROGRES)*

SDCCH

(Cause: no radio resource available)

Events related to second (high priority) call(*)

DT1 (ASS FAI)

DT1 (QUIND)*

TASSFAIL (8.)

134 A30808-X3247-M41-3-7618


1.2.11.3 Queuing: Queued Assignment Request for FR TCH Is Discardedfrom Queue Due to T11 Expiry, Directed Retry Enabled But NoTarget Cell Available, Preemption Disabled or Not Allowed for theRequesting Call

BTS BSCMS MSC

DT1 (ASS REQ)

Start T11

Expiry T11

DT1 (QUIND)

BWHCI

DATRQ (PROGRES)

I (PROGRES)

DT1 (PROGRES)


SDCCH


FHREQ




NMSGDISQ (1.)MDURTCRQ (1.)(stop)

DT1 (CL REQ)(cause: no radioresource available)

DT1 (CL CMD)


Release of the queued context...

NHOINRHA (1.)

NRCLRREQ (22.)

NRCLRCMD (1.)

A30808-X3247-M41-3-7618 135

InformationSystem


1.2.11.4 Queuing: Queued Handover Request for FR TCH Is Served BeforeTQHO Expiry, Preemption Disabled or Not Allowed for theRequesting Call

BTS oldBSCnew MSCMS BSC

CR (HO REQ)

Start TQHO


CC (QUIND)


(queuing allowedindicator=not allowed )*

(cause: no radio resourceavailable)

CREF (HO FAI)

NRINHDFL

CR (HO REQ)(queuing allowedindicator=allowed )*



BTS congestion ends during runtime of TQHO, 1 TCH becomes idle again...

Stop TQHO

MDURTCRQ (3.) (stop)

CHNAV

Start TTRAUCHNAK

Start T_MSRFPCI

DT1 (HO RAC; HO CMD)


Completion of Handover procedure...

DT1 (HO RQD)

136 A30808-X3247-M41-3-7618


In case of MSC-controlled handover the MSC cyclically attempts the HANDOVER REQUEST proce-dure towards all target cells previously received in the HANDOVER REQUIRED message from theoriginating BSC. For the first cycle, the SIEMENS MSC generally sets the ‚queuing allowed indicator‘to ‚not allowed‘. If in this first cycle the request for radio resoucres fails for all target cells, the SIEMENSMSC repeats the cycle again, this time, however, with the ‚queuing allowed indicator‘ set to ‚allowed‘.This is done to avoid an unnecessary delay in the handover execution and in order to use the queuingmechanism as the very last measure to rescue a call.

(*)

A30808-X3247-M41-3-7618 137

InformationSystem


1.2.11.5 Queuing: Queued Handover Request for FR TCH Is Discarded fromthe Queue Before TQHO Expiry Due to an Incoming FR Call withHigher Priority, Preemption Disabled or Not Allowed for theRequesting Calls

iThe blue colour indicates the events related to the high priority call.


CR (HO REQ)

Start TQHO


DT1 (QUIND)*



CC (QUIND)



All places in the queue are occupied after the handover request...

Stop TQHO (low prio call)

NMSGDISQ (3.)MDURTCRQ (3.) (stop)NHOINRHA (1.)

FHREQ*

BWHCI*

DT1 (ASS REQ)*


High prioritycall

RLSD (HO FAI)(cause: no radioresource available)

MDURTCRQ (1.) (start)*

Start T11* (high prio call)

NRINHDFL

138 A30808-X3247-M41-3-7618



RLC

DATRQ (PROGRES)*

High priority call remains queued...*

DT1 (PROGRES)*

I (PROGRES)*SDCCH

Events related to high priority call(*)

A30808-X3247-M41-3-7618 139

InformationSystem


1.2.11.6 Queuing: Queued Handover Request for FR TCH Is Discarded fromthe Queue Due to TQHO Expiry, Preemption Disabled or NotAllowed for the Requesting Calls


CR (HO REQ)

Start TQHO




CC (QUIND)


Release of the queued context...

NMSGDISQ (3.)MDURTCRQ (3.) (stop)

Expiry TQHO

RLSD (HO FAI)

RLC

(cause: no radioresource available)NRINHDFL

140 A30808-X3247-M41-3-7618


1.2.11.7 Preemption: Successful Forced Inter-Cell Handover Due toPreemption, Preempted Assignment Request and Preempting CallAre Both FR

iThe blue colour indicates the events related to preempting call.


CHNAK

CHNAV

I (HO CMD)


AININIRH (11.)AOUINIRH (11.)

ATTCHSEI (1.)ATINHIRC (11.)If last TCH startAALTCHTI (1.)

DATRQ (HO CMD)

BWHCI

(cause: forced, BTSnew included)

FACCH

DT1 (ASS REQ)*

All TCHs in the old BTS are busy...

(preemption allowedindicator=allowed)

FHREQ


SININIRH (11.)SINTHINT (11.)SOUINIRH (11.)SINHOBSC (16.)

Continuation of inter-cell handover procedure for preempted call...

FACCH

I (HO CMP)DATIN (HO CMP)

Start T8

Stop T8

A30808-X3247-M41-3-7618 141

InformationSystem



MRPCI

I (ASS CMD)*

MTCHBUTI (start)*

DATRQ (ASS CMD)*

SDCCH

Completion of Assignment procedure for preempting call...

RELRQ

RELCN

RCHRL

RCHRA

MTCHBUTI (stop)PHCRQ*

PHCCN*

CHNAV*

CHNAK*Start TTRAU*

Start T_MSRFPCI*

Events related to preempting call(*)

Start T10*

HOPER(cause: Preemption)

142 A30808-X3247-M41-3-7618


1.2.11.8 Preemption: Forced Release of Preempted Call Due to Lack ofTarget Cell for Forced Inter-Cell Handover Procedure, Preemptedand Preempting Call Are Both FR



BWHCI

(cause: forced, no target cell)

DT1 (ASS REQ)*


(preemption allowedindicator=allowed)

FHREQ


DT1 (CL REQ)(cause: preemption)

DT1 (CL CMD)(cause: preemption)

Completion of assignment procedure for preempting call...

I (ASS CMD)*

MTCHBUTI (start)*

DATRQ (ASS CMD)*

SDCCH

PHCCN*

CHNAV*

Start T_MSRFPCI*


Start T10*

Start T10*

NHOINRHA (1.)

PHCRQ*

CHNAK*

Release of preempted call...

NRCLRCMD (1.)

NRCLRREQ (7.)

A30808-X3247-M41-3-7618 143

InformationSystem


1.2.11.9 Preemption: Successful Forced Inter-BSC Handover Due toPreemption, Preempting Handover Request and Preempted CallAre Both FR, Originating BSC of the Preempting Handover Requestand Target BSC for the Forced Handover Are the Same


BTSold BTSnewMS

CHNAK

Start T7

BSCnewBSCold MSC

CR (HO REQ)*

DT1 (HO RQD)*

DATRQ (HO CMD)

BWHCI(cause: forced,external targetcell included)

I (HO CMD)FACCH

Start T_MSRFPCI

ATTCHSEI (1.)*ATCHSMBS (1.)*

CC (HO RAC; HO CMD)

DT1 (HO RQD)

Start Trr7 (***)

ATINBHDO (10.)

CHNAV


FHREQ


(preemptionindicator=allowed)

(cause: Preemption CR (HO REQ)

(cause: Preemption)


Stop T7

Continuation of inter-BSC handover procedures for preempted call...

I (HO CMP)FACCH

SUCTCHSE (1.)

Start T8

144 A30808-X3247-M41-3-7618



RLSD

DT1 (CL CMP)

RELRQ

RCHRL

CHNAK*

RCHRA

RELCN

Continuation of preempting incoming MSC-controlled handover procedure...


(**)



Start TTRAU*

Stop TTRAU*Start Trr7 (***)

Start T_MSRFPCI*

MTCHBUTI (1.)*

Start T8

RLCCHNAV*

CC (HO RAC; HO CMD)*

DT1 (HO CMD; HO CMD)*

ATINBHDO (*)

I (HO CMD)*FACCH

SUINBHDO (10.)NRCLRCMD (3.)

DT1 (CL CMD)

(cause: handoversuccessful)Stop T8

DT1 (HO CMP)

Stop Trr7 (***)

A30808-X3247-M41-3-7618 145

InformationSystem


1.2.12 HSCSD

1.2.12.1 Successful HSCSD Call, Mobile Originating, 3 TCHs Used

BTS BSCMS MSC

CHNRD


NSUCCHPC (4.)

CHNREQ

UI (IMASS)

SABM (CMSREQ)

UAESTIN (CMSREQ)

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)


RACH

AGCH

SDCCH

SDCCH

DT1 (CLUPD)

I (CIMCMD)

I (CLAMCH)

ENCRY (CIMCMD)

MRPCI

DATIN (CLAMCH)

CR (CL3I; CMSREQ)

CC (CICMD)

SDCCH

SDCCH

DATIN (SETUP)SETUP

DT1 (SETUP)

DT1 (CPROC)

SDCCH

I (CPROC)DATRQ (CPROC)

SDCCH

DT1 (CICMP)DATIN (CIMCMP)SDCCH

I (CIMCMP)

ATTCHSEI (1.) (*)TASSATT (2.)If last TCH startAALTCHTI (1.)

DT1 (ASREQ)

NTDMAGCH (1.)

146 A30808-X3247-M41-3-7618


BTS BSCMS MSC

I (ASS CMD)

PHCRQ

PHCCN

CHNAV (mCH) (**)

DATRQ (ASS CMD)

MTCHBUTI (1.) (start) (*)

SDCCH

Start TTRAU

Start T_MSRFPCI

Stop TTRAU (***)

SABM

UA

ESTIN

TNTCHCL (1.)TNMSCNCL (3.)

FACCH

FACCH

(activation type: relatedto normal assignmentprocedure)

CHNAV (sCH1) (**)

Start TTRAU(activation type: relatedto multislot configuration)

CHNAV (sCH2) (**)

Start TTRAU(activation type: related tomultislot configuration)

CHNAK (mCH) (**)

CHNAK (sCH1) (**)

CHNAK (sCH2) (**)

Start T_MSRFPCI

Start T_MSRFPCI

I (ASS CMP)

SUCTCHSE (1.) (*)TASSSUCC (2.)

DATIN (ASS CMP)DT1 (ASS CMP)FACCH

A30808-X3247-M41-3-7618 147

InformationSystem


BTS BSCMS MSC

I (CONACK)

RELCN

DT1 (ALERT)

I (ALERT)

RELCHRL

RCHRA

DATRQ (ALERT)


ASDCALTI(stop)

DT1 (CONNECT)DATRQ (CONNECT)I (CONNECT)

RELRQ

FACCH

FACCH

FACCH

Call phase ...

Note: This counter counts as many events as TCHs are used for the HSCSD call.(*)

mCH = main channelsCH1 = 1. secondary channelsCH2 = 2. secondary channel

(**)


(***)

MRPCI (mCH) (**)

Stop T_MSRFPCI

MRPCI (sCH1) (**)

Stop T_MSRFPCI

MRPCI (sCH2) (**)

Stop T_MSRFPCI

148 A30808-X3247-M41-3-7618


1.2.12.2 Successful Inter-cell Handover of an HSCSD Call (3 TCHs Used),Intra-BSC


CHNAK (mCH) (**)

CHNAV (mCH) (**)


ATTCHSEI (1.) (****)ATINHIRC (*)If last TCH startAALTCHTI (1.)

Start THORQST

Start TTRAU

Start T_MSRFPCI

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

UI (MEAS REP)SACCH

(with HO cause)

BWHCI

CHNAV (sCH)1 (**)


CHNAV (sCH2) (**)


CHNAK (sCH1) (**)

Start T_MSRFPCI

CHNAK (sCH2) (**)

Start T_MSRFPCI

I (HO CMD)Start T8


FACCH

DATRQ (HO CMD)

HANDO

Start T3124

Stop TTRAU (**)

HO ACCESS

HO ACCESSFACCH

FACCH

Call in progress...

A30808-X3247-M41-3-7618 149

InformationSystem



MRPCI (mCH) (**)

Stop T8

DATIN (HO CMP)

SUCTCHSE (1.) (****)

DT1 (HOPER)


Stop T3105ESTIN

Stop T_MSRFPCI

(with HO cause)

I (HO CMP)

SABM

UA

FACCH

FACCH

FACCH


UI (PHYS INFO)FACCH

MRPCI (sCH1) (**)

Stop T_MSRFPCI

MRPCI (sCH2) (**)

Stop T_MSRFPCI

RELRQ

RELCN

TNTCHCL (1.)TNMSCNCL (3.)

150 A30808-X3247-M41-3-7618






(***)

(*)


(**)

Note: This counter counts as many events as TCHs are used for the HSCSD call.(****)

Note: The number of the channels to be released in the old cell depends on the number of TCHs usedfor the HSCSD call in the old cell (the number of TCHs used can change during the handover proce-dure, depending on the number of channels available).

(*****)

(*****)

RCHRL

RCHRA

RCHRL


RCHRL

RCHRA


RCHRA


A30808-X3247-M41-3-7618 151

InformationSystem


1.2.12.3 Forced Intra-cell Handover During HSCSD Assignment Procedure

BTS BSCMS MSC

HSCSD call setup... (see 1.2.12.1)

ATTCHSEI (1.) (*)TASSATT (2.)If last TCH startAALTCHTI (1.)

DT1 (ASREQ) (****)

CHNAV (new TCH)

Start TTRAUCHNAK

Start T_MSRFPCI

I (ASS CMD)DATRQ (ASS CMD)

Old FACCH

Stop TTRAU (***)

SABM

UA

ESTIN

TNTCHCL (1.)New FACCH

New FACCH

I (ASS CMP)DATIN (ASS CMP)New FACCH

SINTHITA (12.)SINHOBSC (16.)

Not enoughadjacentTCHs

MRPCI

Stop T_MSRFPCI

DT1 (HOPER)

SUCTCHSE (1.)(cause: O & Mintervention)

RELCN

RELCHRL

RCHRA

RELRQ


ATINHIAC (12.)

Start T10

Stop T10

152 A30808-X3247-M41-3-7618


PHCRQ (****)

PHCCN (****)

MTCHBUTI (1.) (start) (*) (****)

CHNAV (sCH1) (**) (****)


CHNAV (sCH2) (**) (****)


CHNAV (mCH) (**) (****)

Start TTRAU(activation type: relatedto normal assignmentprocedure)

Note: This counter counts as many events as TCHs are used for the HSCSD call.(*)


(**)


(***)

HSCSD call setup continuation... (see 1.2.12.1)

BTS BSCMS MSC

Events related to HSCSD TCH request.(****)

A30808-X3247-M41-3-7618 153

InformationSystem


1.2.13 Signalling Transactions without TCH

1.2.13.1 Successful Location Update (Phase 2 MS)

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)

SABM (LUREQ)

UI (IMASS)

UA

MRPCI CR (CL3I; LUREQ)




CHNRD

CC

ESTIN (LUREQ)SDCCH

RACH

AGCH

SDCCH


DT1 (LUACC)DATRQ (LUACC)

I (LUACC)


DT1 (TRCMP)

SDCCH

SDCCH

DT1 (CL CMD)

DT1 (CL CMP)DATRQ (CHREL)I (CHREL)

SDCCH

Start T_MSRFPCI

Stop T_MSRFPCI

NTDMAGCH (1.)

NRCLRCMD (2.)

154 A30808-X3247-M41-3-7618


BTS BSCMS MSC

DESACRLSD

RLC

RELIN

RCHRL (SDCCH)

RCHRA

DISC

UA

SDCCH

SDCCH


A30808-X3247-M41-3-7618 155

InformationSystem


1.2.13.2 Successful Location Update (2G/3G (GSM/UMTS) Multirat MS)

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)

SABM (LUREQ)

UI (IMASS)

UA

MRPCI CR (CL3I; LUREQ)




CHNRD

CC

ESTIN (LUREQ)SDCCH

RACH

AGCH

SDCCH


Start T_MSRFPCI

Stop T_MSRFPCI

NTDMAGCH (1.)

CLCH

UTRANCC

DATIN (CLCH)

DATIN (UTRANCC)

DT1 (CLUPD)

156 A30808-X3247-M41-3-7618


BTS BSCMS MSC

DESACRLSD

RLC

RELIN

RCHRL (SDCCH)

RCHRA

DISC

UA

SDCCH

SDCCH

DATRQ (LUACC)I (LUACC)


DT1 (TRCMP)

SDCCH

SDCCH

DT1 (CL CMD)

DT1 (CL CMP)DATRQ (CHREL)I (CHREL)

SDCCH

NRCLRCMD (2.)

DT1 (LUACC)


A30808-X3247-M41-3-7618 157

InformationSystem


1.2.13.3 Successful IMSI Detach (Phase 2 MS)

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)

SABM (IMDETIN)

UI (IMASS)

ESTIN (IMDETIN)

UA

MRPCI CR (CL3I; IMDETIN)




CHNRD

SDCCH

RACH

AGCH

SDCCH

SDCCH

SDCCH

SDCCH


Start T_MSRFPCI

Stop T_MSRFPCI

I (CHREL)

DISC

UA

RCHRA

RCHRL (SDCCH)

RELIN

DESAC

DATRQ (CHREL)CREF

NTDMAGCH (1.)


158 A30808-X3247-M41-3-7618


1.2.13.4 Successful Supplementary Service (SS) Management Procedurevia Subscriber-Controlled Input (SCI)

BTS BSCMS MSC

CHNAV (SDCCH)

CHNAK




CHNRD

IACMD (IMASS)

ESTIN (CMSREQ)

MRPCI

I (CLAMCH)



I (CIMCMP)DATIN (CIMCMP)

DT1 (CICMP)

UI (IMASS)

I (CMSREQ)

AGCH

SDCCH

CHNREQRACH

SDCCH

I (CIMCMD)

SDCCH

SDCCH

CR (CL3I; CMSREQ)

Start T3101

Stop T3101

Stop T_MSRFPCI

Start T_MSRFPCI

MRPCI

NTDMAGCH (1.)

(CM Service type:Supplementary ServiceActivation)


A30808-X3247-M41-3-7618 159

InformationSystem


BTS BSCMS MSC

DISCSDCCH RELIN

RCHRL (SDCCH)

RCHRA


I (CHREL)

DT1 (CL CMD)

SDCCH

DATRQ (CHREL)

NRCLRCMD (2.)

DESACRLSD

RLC

UASDCCH

DT1 (CL CMP)

I (REGISTER)DATIN (REGISTER) DT1 (REGISTER)SDCCH (SS code, operation

code, service)(SS code, operationcode, service) (SS code, operation

code, service)

DT1 (REL CMP)DATRQ (REL CMP)

SDCCH

I (REL CMP)

160 A30808-X3247-M41-3-7618


1.2.13.5 Successful USSD (Unstructured Supplementary Service Data)Management Procedure via (SCI)

BTS BSCMS MSC

CHNAV (SDCCH)

CHNAK




CHNRD

IACMD (IMASS)

ESTIN (CMSREQ)

MRPCI

I (CLAMCH)




DT1 (CICMP)

UI (IMASS)

I (CMSREQ)

AGCH

SDCCH

CHNREQRACH

SDCCH

I (CIMCMD)

SDCCH

SDCCH

CR (CL3I; CMSREQ)

Start T3101

Stop T3101

Stop T_MSRFPCI

Start T_MSRFPCI

MRPCI

NTDMAGCH (1.)



A30808-X3247-M41-3-7618 161

InformationSystem


BTS BSCMS MSC

DISCSDCCH RELIN

RCHRL (SDCCH)

RCHRA

ASDCALTI (stop)MBUSYSSP (3.) (*)(accumulation)

I (CHREL)

DT1 (CL CMD)

SDCCH

DATRQ (CHREL)

NRCLRCMD (2.)

DESACRLSD

RLC

UASDCCH

DT1 (CL CMP)

I (REGISTER)DATIN (REGISTER)

DT1 (REGISTER)

SDCCH (SS code, operationcode, service)

(SS code, operationcode, service)

(SS code, operationcode, service)

DT1 (REL CMP)DATRQ (REL CMP)

SDCCH

I (REL CMP)

NSUSDSUS (*)

NSUSDSUS and MBUSYSSP subcounter 3 are only triggered if the database flag TRANSPM (BSCobject) is set to TRUE. If this flag is set to FALSE, NSUSDSUS is not triggered at all and MBUSYSSPis triggered for subcounter 4.

(*)

162 A30808-X3247-M41-3-7618


1.2.13.6 Unsuccessful Immediate Assignment Procedure, No SDCCHAvailable

BTS BSCMS MSC

CHNREQ

IACMD (IMASSRJ)

CHNRD

TACCBPRO (2.)NACSUCPR (2.)

NATTSDPEATSDCMBSNACSUCPR (3.), (1.) (**)ATIMASCA (*)

UI (IMASSRJ)

RACH

AGCH

Expiry T3122

Start T3122

CHNREQ (***)RACH

Subcounter depends on the access cause(*)

.....

Subcounter (1.) is only increased if the access cause is ’answer to paging’.(**)T3122 is started in the MS on receipt of an IMMEDIATE ASSIGNMENT REJECT. When it expires, theMS attempts another access to the cell.

(***)

NTDMAGCH (1.)

A30808-X3247-M41-3-7618 163

InformationSystem


1.2.13.7 Unsuccessful Immediate Assignment Procedure, No AGCHAvailable (AGCH Overload)

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

NATTSDPE,NACSUCPR (3.), (1.) (**)ATIMASCA (*)If last SDCCH startASDCALTI

NACSUCPR (2.) decreased by 1ASDCALTI (stop)

CHNRDRACH

Subcounter depends on the access cause.(*)

Subcounter (1.) is only increased if the access cause is ’answer to paging’.(**)

Stop T3101

IACMD (IMASS)

DELIN (*)

TACCBPRO (2.)SUIMASCA (*)NACSUCPR (2.)

Start T_MSRFPCI

Start T3101

NTDMAGCH (3.)

No AGCHavailable,IMASS discarded

164 A30808-X3247-M41-3-7618


1.2.13.8 Unsuccessful Immediate Assignment Procedure, assigned SDCCHis not seized by the MS (Phantom RACH Scenario)

BTS BSCMS MSC

CHNREQ

CHNAV (SDCCH)

CHNAK

IACMD (IMASS)

NATTSDPE,NACSUCPR (3.), (1.) (**)ATIMASCA (*)If last SDCCH startASDCALTI


CHNRDRACH

Subcounter depends on the access cause.(*)

Start T_MSRFPCI

Start T3101UI (IMASS)

AGGH

Expiry T3101

RCHRL (SDCCH)

RCHRA

Subcounter (1.) is only increased if the access cause is ’answer to paging’.(**)

ASDCALTI (stop)MBUSYSSP (n.)(accumulation)

A30808-X3247-M41-3-7618 165

InformationSystem


1.2.13.9 BTS Discards Invalid RACH Messages

MS BTS BSC

CHNREQRACH

RACH

CHNREQ

NINVRACH (1.)

NINVRACH (2.)

Level of receivedCHANNEL REQUESTis below the thresholdRACHBT

Timing advance valuedetermined from thereceived CHANNELREQUEST exceeds thethreshold EXCDIST

MS BTS BSC

166 A30808-X3247-M41-3-7618


1.2.13.10 Immediate Assignment Procedure for Abis Link Configured viaSatellite Link

BTS BSCMS MSC

CHNAV (SDCCH)



CHNRD

IACMD (IMASS) (*

)

CHNAKUI (IMASS)

AGCH

CHNREQRACH

Start T3101

Abis link with highpropagation delay

When for the BTSM object subordinate to the serving BTS, the parameter LPDLMSAT (BTSM object)is set to TRUE, the BSC sends the IMMEDIATE ASSIGNMENT message to the BTS immediately afterthe transmission of the CHANNEL ACTIVATION message without waiting for the CHANNELACTIVATION ACKNOWLEDGE. This is done to avoid additional Immediate Assignment signalingdelay and, as a consequence. unnecessary RACH retransmissions from the mobile stations.

(*)

Call / Transaction Setup Continuation ...

Start

A30808-X3247-M41-3-7618 167

InformationSystem


1.2.13.11 Paging Overload - BTS discards a PAGING REQUEST Message

BTS BSCMS MSC

PGCMD

UDT (PAGIN)

NTDMPCH (3.)

OVERLOAD

No place in any pagingqueue available - theBTS discards thePAGING REQUEST *

(cause: CCCH overload)Start T17 **

BSC starts todiscard allpagings towardsthis BTS **

TACCBPRO (1.)

TCMSGREC

* Each paging queue place in the BTS can be seized by one PAGING REQUEST message (PAGREQ) whichitself can contain the mobile identities (IMSI or TMSI) of up to 3 mobile subscribers simultaneously. Thismeans that the PAGING REQUEST message can contain the mobile identities of up to 3 PAGINGCOMMANDS (PGCMD) that were received from the BSC before.If the BTS discards a PAGING REQUEST due to lack of paging queue places, NTDMPCH (3.) is increasedby as many counts as mobile identities (IMSI or TMSIs) were contained in the discarded PAGING REQUESTmessage! In other words, if the discarded PAGING REQUEST contains e.g. 3 TMSIs, then NTDMPCH (3.)is increased by 3.

** The BSC starts T17 and discards all new PAGING COMMANDS to the BTS only if BTS overload handling isenabled in the BSC (BTSOVLH=TRUE). The PAGING COMMANDS to the BTS are discarded as long as T17runs.

168 A30808-X3247-M41-3-7618


1.2.14 Short Message Service

1.2.14.1 Successful SMS Mobile Originating in Idle Mode (Phase 2 MS)

BTS BSCMS MSC

CHNAV (SDCCH)

CHNAK



TACCBPRO (2.)SUIMASCANACSUCPR (2.)

CHNRD


SABM (CMSREQ)ESTIN (CMSREQ)

MRPCI

I (TRCMD)DT1 (TRCMD)DATRQ (TRCMD)

ESTIN (SAPI 3)

SDCCH

AGCH

CHNREQRACH

UASDCCH

SDCCH

SABM (SAPI 3)SDCCH

UA (SAPI 3)SDCCH


CC

CR (CL3I; CMSREQ)

I (TRCMP) DATIN (TRCMP)DT1 (TRCMP)SDCCH

Start T_MSRFPCI

Stop T_MSRFPCI

Start T3101

Stop T3101

NSUCCHPC (7.)

A30808-X3247-M41-3-7618 169

InformationSystem


BTS BSCMS MSC

I (CPDAT; RPDA)DATIN (CPDAT; RPDA)

DT1 (CPDAT; RPDA)

I (CPACK)

DT1 (CPACK)DATRQ (CPACK)

I (CPDAT;RPAC)DT1 (CPDAT; RPAC)

DATRQ (CPDAT; RPAC)

I (CHREL)

DT1 (CL CMD)

DATRQ (CHREL)

DESAC

RELIN

RELRQ

RELCN

RCHRL (SDCCH)

RCHRA

RLSD

DT1 (CL CMP)

RLC

SDCCH

SDCCH

SDCCH

SDCCH

DISCSDCCH

UASDCCH

I (CPACK)SDCCH

DATIN (CPACK) DT1 (CPACK)

NRCLRCMD (2.)


170 A30808-X3247-M41-3-7618


1.2.14.2 Successful SMS Mobile Terminating in Idle Mode (Phase 2 MS)

BTS BSCMS MSC

CHNAV (SDCCH)

CHNAK



PGCMD


SABM (PAGRES)

ESTIN (PAGRES)

MRPCI


TACCBPRO (1.)

UDT (PAGIN)

CHNRD

CC

UI (PAGREQ)PCH

AGCH

SDCCH

UASDCCH

RACH

CHNREQ


CR (CL3I; PAGRES)

I (TRCMD)DT1 (TRCMD)DATIN (TRCMD)

ESTRQ (SAPI 3)

I (TRCMP) DATIN (TRCMP) DT1 (TRCMP)

DT1 (CPDAT; RPDA)SDCCH

SDCCH

SABM (SAPI 3)SDCCH

ESTCN (SAPI 3)

DATRQ (CPDAT; RPDA)I (CPDAT; RPDA)SDCCH

UA (SAPI 3)SDCCH

Start T_MSRFPCI

Stop T_MSRFPCI

Start T3101

Stop T3101

NTDPMAIN (1.)

NSUCCHPC (8.)

A30808-X3247-M41-3-7618 171

InformationSystem


I (CPACK)DATIN (CPACK) DT1 (CPACK)

I (CPDAT; RPAC)DATIN (CPDAT; RPAC)

DT1 (CPDAT; RPAC)

I (CPACK)DT1 (CPACK)

DATRQ (CPACK)

I (CHREL)

DT1 (CL CMD)

DATRQ (CHREL)

DT1 (CL CMP)

DESAC

RELIN

RELRQ

RELCN

RCHRL (SDCCH)

RCHRA

RLSD

RLC

SDCCH

SDCCH

SDCCH

SDCCH

DISCSDCCH

UASDCCH

BTS BSCMS MSC

NRCLRCMD (2.)


172 A30808-X3247-M41-3-7618


1.2.14.3 Successful SMS Mobile Originating in Connected Mode (FR CallOngoing)

BTS BSCMS MSC

I (CMSREQ)DATIN (CMSREQ)

DT1 (CMSREQ)

DT1 (CMSACC)DATRQ (CMSACC)

I (CMSACC)

I (CPDAT; RPDA)DATIN (CPDAT; RPDA)

DT1 (CPDAT; RPDA)


I (CPACK) DT1 (CPDAT; RPAC)DATRQ (CPDAT; RPAC)

I (CPDAT; RPAC)

UA (SAPI 3)SACCH

FACCH

FACCH

SABM (SAPI 3)SACCH ESTIN (SAPI 3)

SACCH

SACCH

SACCH

Call in progress...


DT1 (CPACK) DATIN (CPACK)DT1 (CPACK)SACCH

NSUCCHPC (15.)

A30808-X3247-M41-3-7618 173

InformationSystem


1.2.14.4 Successful SMS Mobile Terminating in Connected Mode

174 A30808-X3247-M41-3-7618


BTS BSCMS MSC

DT1 (CPDAT; RPDA)ESTRQ (SAPI 3)

ESTCN (SAPI 3)

DATRQ (CPDAT; RPDA)


DT1 (CPACK)DATIN (CPACK)

DT1 (CPDAT; RPAC)DATIN (CPDAT; RPAC)

I (CPDAT; RPDA)

I (CPACK)

I (CPDAT; RPAC)

UA (SAPI 3)SACCH

SABM (SAPI 3)SACCH

SACCH

SACCH

SACCH

I (CPACK)SACCH

Call in progress...


NSUCCHPC (16.)

A30808-X3247-M41-3-7618 175

InformationSystem


1.2.15 Advanced Speech Call Items (ASCI) Procedures

1.2.15.1 VBS/VGCS Setup Initiated by fixed Dispatcher and Release

By means of this procedure, performed for every cell involved in the Group Call Area(GCA), the BSC activates in the cell the common VBS/VGCH TCH. In the Message Flowbelow GCA contains bts1 and bts2 in BSC1 and bts1 and bts2 in the BSC2.

MS BSC1 bts 1/bts 2

CR (VBST)

SCCP connectionGroup Call Control

CC (VBSA)

cell identifier: bts 1

CR (VBST)

CC (VBSA)

DT1 (URLC)

DT1 (URLC)

CR (VARQ)

CR (VARQ)cell identifier: bts 2

One SCCPconnection foreach VBS/VGCSTCH i.e.for eachcall



CHNAV

CHNAV

CHNAV

CHNAV

CHNAK

CHNAK CHNAK

CHNAK

ULFREE

ULFREE

VBS/VGCS TCH

NOTCMDcommandindicator ’start’


ULFREE

ULFREE



FACCH

ULFREE

ULFREE

Notif/NCH

Notif/NCHNCH

bts 1/bts 2 MSCBSC2

TASSATVS +1 in each

cell incl. in GCA

TASSATVS +1 in each

cell incl. in GCA

NNNOTNCH NNNOTNCH

176 A30808-X3247-M41-3-7618


MS BSC1 bts 1/bts 2

CC (VARE)

CC (VARE)

DT1 (CLCMD)

DT1 (CLCMD)DT1 (CLCMD)

UDTRQ(CHREL)

DESAC

UDTRQ(CHREL)

DESAC

RCHRL

NOTCMD

NOTCMD

REHRL

RCHRL

DESAC

DESACUDTRQ (CHREL)

RCHRA

UA

CHREL

Notif/NCHNCH

Notif/NCHNCH

cell identifier: bts 1

CC (VARE)cell identifier: bts 2

cell identifier: bts 1CC (VARE)

cell identifier: bts 2SSI 10 (SIT 10)

SSI 10 (SIT 10)

RELEASE initiated by fixed dispatcher...

Release all res.controlSCCP connetionand associatedVGCS/VBS TCHDT1 (CLCMD)

NOTCMDcommandindicator ’stop’

NOTCMDcommand indicator ’stop’

DISC

CHREL DT1 (CLCMP)DT1 (CLCMP)

UA

UDTRQ(CHREL)

DISCDESAC

DT1 (CLCMP)

DT1 (CLCMP)

RLSDRLSD

RLSD

RLSDRLCRLC

CHRELDISCUA

RCHRARCHRA

CHRELDISCUA

RLSDRLSD

RCHRA DT1 (CLCMD)

DT1 (CLCMD)DT1 (CLCMD)

Release SCCPconnetion (Gr..Call Control

DT1 (CLCMP)RLSDRLSD

RLCRLC

bts 1/bts 2 MSCBSC2

SSI10 (SIT10)

SSI10 (SIT10)

A30808-X3247-M41-3-7618 177

InformationSystem


1.2.15.2 Succesful Uplink Allocation Procedure (1)

ULFREE (2)

ULFREEFACCH

ULFREE

UPLINK ACCESS

TALDC

DT1 (UPRQ)

DT1 (URA)

VGCS UPLINK GRANT

UPBUS (ULBUSY)ULBUSY

FACCH

DT1 (USC) (5)UPBUS (ULBUSY)

SABM (TALKIND)

UA (TALKIND)

ESTIN (TALKIND)DT1(URC)[TALKIND])

DATIN (CLCH)

MRPCIDT1 (CLUPD)

CR(ASREQ)

CHNAK

CHNAV

DATRQ (ASCMD)

ESTIN

DATIN (ACOM)

MRPCI

UP_REL (6)CC (ASCMP)

Conversation Phase...

MS BTS BSC1 BSC2MSC BTS

SETPAR (7)

downlink voicegroup TCH

uplink voice group TCH

VGRULF (3)

178 A30808-X3247-M41-3-7618


1. The listening subscriber may attempt to seize the Uplink common VGCS (TCH).When the MS is informed about the successful seizure it then moves on a dedicatedchannel (TCH) becomes the new talking subscriber.This is the typical talking sub-scriber change procedure.

2. The BSC sends this message to the BTS to indicate that the uplink of the VGCSchannels becomes or is free.

3. vgcsULFreeTimer (VGRULF in BSC DB Object BTS [TIMER]). If no ASCI call is ac-tive the network provides an UPLINK FREE message on the main signalling channelperiodically. The timer vgcsULFree Timer defines the repetition rate of sending thismessage. The timer will be stopped if an Uplink Access of a Mobile Station (MS) oran UPLINK Busy of the BSC was received.

4. Tgrant is a timer to define the repetition rate of sending the VGCS UPLINK GRANTmessage. In case of an ASCI call the network grants the uplink to one mobile stationby sending a VGCS UPLINK GRANT message to the mobile station. After havingsent this message the BTS starts TGRANT to repeat this message for as long as acounter has not reached the value of NRPGRANT.

5. With DT1 USC (Uplink Seize Cmd) the MSC informs a BSC that a MS belonging toanother BSC area has successfully seized the uplink common VGCS channel. Thenthe BSS notifies its MSs that the channel is busy.

6. UPLINK RELEASE (BSC->BTS) sent on VGCS common channel to inform the BTSthat the BSC has assigned a dedicated TCH to the talker in the same call during talk-er change procedure.

7. SET PARAMETER messages are sent from MSC where the MS is told that Up-link/Downlink is connected.

A30808-X3247-M41-3-7618 179

InformationSystem


1.2.15.3 FREE Uplink ProcedureMS releases the dedicated channel (TCH). This happens when the talking subscriberwants to stop speaking. After this procedure, other MSs may attempt to seize the uplinkcommon VGCS channel.

Current talking subscriberreleases its dedicatedchannel

ULRELFACCH DATIN(ULREL)

RELIN

RCHRA

RCHRL

ULFREE

DT1 (UPRI)DT1 (URLC)

ULFREEDT1 (CLCMD)

DT1 (CLCMD)

RLSD

RLC

FACCHULFREE

DATRQ(CHREL)

CHEL

DESAC

DISC

UA

The other MSs mayattempt to seize the uplinkcommon VGCS channel,in order to talk.

MS BTS BSC1 BSC2MSC BTS

cause: call controlcause: call control

cause: call control

180 A30808-X3247-M41-3-7618


1.2.15.4 VGCS Setup initiated by Service Subscriber and Release

CHNREQCHNRD

CHNAV

CHNAK

IACMD (IAS)IAS

CMSREQESTIN (CMSREQ)

CR(CL3I[CMSREQ])

CC (CICMD)MRPCI

ENCRY (CI CM)CICM

CLCH

CICP

DATIN (CLCH)

MRPCIDT1 (CLUPD)

DATIN (CICP)DT1 (CICMP)

SETUP(1)

DT1 (ASREQ)PHCRQ

PHCCN

CHNAV

DATRQ (ASCMD)

CHNAK

ASCMD

UA ESTIN

DATIN (ACOM)ACOM DT1 (ASCMP)

MRPCI

RELRQ

RELCN

RCHRL

RCHRA

SCCP connetion(res. controllingdedicated to thecalling subscriber)

MS BTS BSC MSC

A30808-X3247-M41-3-7618 181

InformationSystem


CR (VBST)

CC (VBSA)

CR (VARQ)

SCCP connetion(Group Call Control)

One SCCPconnection (Res.Controlling) for eachVGCS TCH, i.e. foreach cell

CHNAV

NOTCMD

CHNAK

UPBUS (ULBUSY)

SSI10 (SIT10)

ULBUSYFACCH

Notification/NCH

CONNECT (2)DATIN (ULREL)

UPFRE (ULFREE)

DATRQ (CREL)

RELIN

RCHRL

RCHRA

ULFREEFACCH

CREL

DT1 (UPRI)

DT1 (CLCMD)Release SCCPconnection(Res.Controlling) andassociated TCHDISC

DT1 (CLMP)DESAC

UARLC

Calling subscriber terminates VGCS call

Calling Subcriber Performs Talker Change Procedure... (see 1.2.15.2)

Release of the Talker TCH ... (see 1.2.15.3)

(4)

Release all res. controlling SCCP connection and asociated VGCS THCs

Release SCCP connections (Group Call Control)

MS BTS BSC MSC

RLSD

(TCH call.subscr.)

command indicator:’start’

TERM

TERMREQ

CC (VARE)

182 A30808-X3247-M41-3-7618


1. SETUP: The MSC is provided with details about the Voice Group Call.2. CONNECT: Information to the mobile station of the calling subscriber that the VGCS

is established with the related group call reference as the connected number.3. The calling subscriber can terminate the call only if the calling subscriber has access

to the uplink.4. TERMINATION REQUEST: An authorized mobile station can send a

TERMINATION REQUEST message to clear down the entire voice group call. To dothis the mobile station must have access to the uplink.

A30808-X3247-M41-3-7618 183

InformationSystem


1.2.15.5 VGCS SETUP initiated by Service Subscriber (FAST CALL SETUP)

... (see 1.2.15.4)

CHREQ

IAS

SABM (ISETUP) (1)

CMSACC

CHNRD

CHNAV

CHNAK

ESTIN (ISETUP)CR (CL3I [ISETUP])

CC (CMSACC)

DATRQ (CMSACC)DT1 (ASSREQ)

CR (VBST)

(1) This message is sent by the MS to the network in order to setup a group call immediately.No encryption and ciphering are performed to speed up the call setup procedure.

MS BTS BSC MSC

IACMD (IAS)

184 A30808-X3247-M41-3-7618


1.2.15.6 MTC During Ongoing VBS/VGCS Connection

Ongoing VBS/VGCS call, called party is a listening subscriber

UDTRQ(Notification FACCH)

PAGIN

PGCMD

Notif/FACCH

If the PAGING message towards the BSC contains the emLPP priority level IE and if the emLPP priority levelis greater or equal to the evalue set by the operator for an appropriate threshold (NOTFACCH in SET BSC)then a Notification / FACCH with paging information included is sent for each Voice Group Call channelactive. If the paged MS is a listener of any ongoing ASCI call in the BSC then it should receive theNotification/FACCH message and switch to the incoming MTC call.

MS BTS BSC MSC

Succesful MTC SETUP ... (see 1.2.1.2)

IE call priority level

IE paging info is included

FACCH groupcall TCH

A30808-X3247-M41-3-7618 185

InformationSystem


1.2.15.7 VBS/VGCS Call during Ongoing Speech Call

Ongoing MOC from ASCI service subscriber

Release of speech call

UDTRQ(Notification FACCH)

DISC

Notif/FACCH

If the VBS/VGCS Assignment Request message contains the emLPP priority level IE and if the emLPPPriority level is greater than or equal to the value set by the operator for an appropriate threshold(NOTFACCH in SET BSC) then a Notification/FACCH with group call information included is sent a dedicatedTCH occupied by speech call (MOC originated by ASCI subscriber, member of the incoming group call). Ifthe originator of the ongoing MOC is a member of the incoming group call it should receive theNotification/FACCH message and switch the incoming group call. The MOC should be released.

Incoming VBS/VGCS call

FACCH

DISCDT1 (DISC)

DT1 (RELEAS)DATRQ (RELEAS)

DATRQ (RELEAS)

MS BTS BSC MSC

cause value: pre-emption

cause value: pre-emption

IE Group call informationis included

FACCH TCHfor speech call

186 A30808-X3247-M41-3-7618


1.2.16 Inter System Handover (2G <--> 3G), circuit switched (CS)

1.2.16.1 Successful Inter System Handover (2G --> 3G)

NodeB

DT1 (HOCMD)

MS/UE

BTS BSC RNC2G+3GMSC

UI (MEAS REP)

BWHCI

DT1 (HORQD)

lu RelocationRequest

lu RelocationRequest ack

Activate newchannels onUTRAN (3G) side

DATRQ (ISHUTRAN)

I (HOCMD) T3121 start

T7 start

T7 stop

ATOISHDO

HO ACCESS

T3124 start HO ACCESS

lu RelocationDetect

RRC HO Detect

T3124 stopHO COMPLETE

lu RelocationComplete

RRC HO Complete

A30808-X3247-M41-3-7618 187

InformationSystem


NodeBMS/UE

BTS BSC RNC2G+3GMSC

DT1 (CLCMD)

DT1 (CLCMP)

T3121 stop

SUOISHDO

RLSD

RLC

RELRQ

RELCN

RCHRL

RCHRA

188 A30808-X3247-M41-3-7618


1.2.16.2 Unsuccessful Inter System Handover (2G --> 3G),loss of MS (loss of HOCMD), T3121 expiry

DT1 (HOCMD)

MS/UE

BTS BSC RNC2G+3GMSC

NodeB

UI (MEAS REP)

BWHCI

DT1 (HORQD)

lu RelocationRequest



DATRQ (ISHUTRAN)

I (HOCMD)T3121 start

ATOISHDO

DT1 (CLCMD)

DT1 (CLCMP)

T3121 expiry

NRFLTCH

DT1 (CLREQ)

NRCLRREQ

NRCLRCMD

A30808-X3247-M41-3-7618 189

InformationSystem


MS/UE

BTS BSC RNC2G+3GMSC

NodeB

RLSD

RLC

DATRQ (CREL)

RELIN

RCHRL

RCHRA

DESAC

Release newchannels onUTRAN (3G) side

190 A30808-X3247-M41-3-7618


1.2.16.3 Unsuccessful Inter System Handover (2G --> 3G),No TCH available in Target UMTS Cell (3G)

DT1 (HORRJ)

MS/UE

BTS BSC RNC2G+3GMSC

NodeB

UI (MEAS REP)

BWHCI

DT1 (HORQD)lu RelocationRequest

lu RelocationFailure

No TCHsavailable onUTRAN (3G) side

T7 start

NHOINRHA

T7 expiry

A30808-X3247-M41-3-7618 191

InformationSystem


1.2.16.4 Unsuccessful Inter System Handover (2G --> 3G), Revision to oldTCH, T3124 expiry

DT1 (HOCMD)

MS/UE

BTS BSC RNC2G+3GMSC

NodeB

UI (MEAS REP)

BWHCI

DT1 (HORQD) lu RelocationRequest



DATRQ (ISHUTRAN)

I (HOCMD)

ATOISHDO

HO ACCESS

T3124 start HO ACCESS

T3124 expiry

DT1 (HOFAI)

UNOISHDO

HO ACCESSdoes not getthrough

SABM

ESTIN

UA

I (HOFAIL)

DATIN (HOFAIL)

lu ClearCommand

lu ClearComplete

Release newchannels onUTRAN (3G) side

192 A30808-X3247-M41-3-7618


1.2.16.5 Successful Inter System Handover (3G --> 2G)

BTSMS/UE

NodeB RNC BSC2G+3GMSC

Event 2d: Meas Report [2d]

CC (HORAC,HCOM)

RQIISHDO

HO ACCESS

HO ACCESS

DT1 (HODET)

Event 3a: Meas Report [3a]

lu RelocationRequired

CR (HOREQ)

CHNAV

CHNAK

lu RelocationCommand

HandoverCommand

RRC HandoverCommand

HANDO

HO COMPLETE

DATIN (HOCMP)

ESTIN

A30808-X3247-M41-3-7618 193

InformationSystem


BTSMS/UE


SUIISHDO

DT1 (HOCMP)

MRPCI

DATIN (UTRANCC)

lu ReleaseCommand

MRPCI

DATRQ (CLEQ)

lu ReleaseComplete

DATIN (CLCH)

DT1 (CLUPD)

MRPCI

Release oldchannels onUTRAN (3G) side

194 A30808-X3247-M41-3-7618


1.2.16.6 Unsuccessful Inter System Handover (3G --> 2G), No TCH availablein Target GSM Cell (2G)

BTSMS/UE


Event 2d: Meas Report [2d]

CREF (HOFAI)

RQIISHDO

Event 3a: Meas Report [3a]

lu RelocationRequired

CR (HOREQ)

lu RelocationRequired Reject

No TCHsavailable on GSM(2G) side

UNIISHDO

A30808-X3247-M41-3-7618 195

InformationSystem


1.2.17 Inter System Cell Reselection Procedure (2G <--> 3G), packetoriented (PO), intra SGSN inter system change

1.2.17.1 Successful Inter System Cell Reselection Procedure (2G --> 3G)The inter system change from A/Gb mode to Iu mode takes place when a GPRS-attached MS changes from A/Gb mode to GERAN or UTRAN IU mode. Depending onthe GPRS mobility management state before the inter system change and whether theRouting Area (RA) is changed or not, one of the following procedures is initiated by theMS:– When an MS in STANDBY state changes to Iu mode inside the current RA, the MS

shall follow the selective RA update procedures.– When an MS in STANDBY state changes to Iu mode and the RA changes, the MS

shall initiate the Iu mode RA update procedure.– When an MS in READY state changes to Iu mode independent of whether the RA

has changed or not, the MS shall initiate the Iu mode RA update procedure and af-terwards initiate the Radio Access Bearers (RABs) by the Service Request proce-dure. The RA update procedure is either combined RA / LA update or only RAupdate.

If the network operated in mode I, an MS that is both PS-attached and CS-attached shallperform the Combined RA / LA Update procedure. This concerns only idle mode (see3GPP TS 23.122), as no combined RA / LA updates are performed during a CS connec-tion. In the context of this specification, the terms RNS (or RNC) refer also to a GERANBSS (or BSC) when serving an MS in Iu mode.

196 A30808-X3247-M41-3-7618


BSC RNCMS/ 2G+3GUE SGSN (lu)

1. Inter system change decision

2. RARQ

6. RACO

5. RAAC

4. Security mode control (complete)

7. MPCR

3. ACRQ

8. SREQ

3. ACRE

4. Security mode control (command)

9. MPCA

8. SACC

11. RB setup complete

11. RB setup request

10. RAB assignment (request)

12. RAB assignment (response)

13. Packet data transfer

A30808-X3247-M41-3-7618 197

InformationSystem


1. The MS or the RAN decides to perform an inter system change which makes the MSswitch to a new cell where Iu mode has to be used, and stops transmission to thenetwork.

2. The MS initiates an RRC connection establishment and sends a Routing Area Up-date (RAU) Request (P-TMSI, Old RA, Old P-TMSI Signature, Update Type, CM)message to the combined 2G+3G-SGSN. Update Type shall indicate RA update orcombined RA / LA update or combined RA / LA update with IMSI attach requested.A combined RA / LA update with IMSI attach requested occurs also if the MS has afollow on request, i.e. if there is pending uplink traffic (signalling or data). As an im-plementation option, the SGSN may use the follow-on request indication to releaseor keep the Iu connection after the completion of the RA update procedure. TheSRNS shall add an identifier of the area where the message was received beforepassing the message to the 2G+3G-SGSN. The 2G+3G-SGSN stops transmissionof N-PDUs to the MS.

3. Authentication/Ciphering functions may be executed.4. Security functions may be executed.5. The 2G+3G-SGSN validates the presence of the MS in the new RA. If due to roam-

ing restrictions the MS is not allowed to be attached in the RA, or if subscriptionchecking fails, the 2G+3G-SGSN rejects the RAU with an appropriate cause. If allchecks are successful, the 2G+3G-SGSN updates MM and PDP contexts for theMS. A new P-TMSI may be allocated. A RAU Accept (P-TMSI, P-TMSI Signature)message is returned to the MS. For this inter system change, the 2G+3-SGSN de-rives the corresponding PDCP sequence numbers from the N-PDU sequence num-bers stored in the SGSN PDP contexts by adding eight most significant bits “1”.These PDCP sequence numbers are stored in the SGSN PDP contexts.

6. The MS acknowledges the new P-TMSI by returning a RAU Complete message tothe SGSN.

7. A Modify PDP context request N -> MS is sent from 2G+3G-SGSN to the MS.8. If the MS has pending uplink data or signalling, it shall send a Service Request

(P-TMSI, RAI, CKSN, Service Type) message to the SGSN. Service Type specifiesthe requested service. Service Type shall indicate one of the following: Data or Sig-nalling.

9. The MS/UE responds with a Modify PDP context accept to the 2G+3G-SGSNMS -> N.

10. - 12. The 2G+3G-SGSN requests the SRNS to establish a radio access bearer bysending an RAB Assignment Request (RAB ID(s), QoS Profile(s), GTP-SNDs, GTP-SNUs, PDCP-SNUs) message to the SRNS. The PDCP sequence numbers are de-rived from the N-PDU sequence numbers and stored in the PDP contexts in step 5.The SRNS sends a Radio Bearer Setup Request (PCDP-SNUs) message to theMS. The MS responds with a Radio Bearer Setup Complete (PDCP-SNDs) mes-sage. The SRNS responds with a RAB Assignment Response message.

Note: The NSAPI value is carried in the RAB ID IE.

198 A30808-X3247-M41-3-7618


1.2.17.2 Successful Inter System Cell Reselection Procedure (3G --> 2G)The inter system change from Iu mode to A/Gb mode takes place when an MS changesfrom UTRAN or GERAN Iu mode to A/Gb mode. Depending on the PMM state beforethe inter system change and whether the RA is changed or not, one of the following pro-cedures is initiated by the MS:– When an MS in PMM-IDLE state changes to A/Gb mode without changing the RA,

the MS shall follow the selective Routing Area Update (RAU) procedure.– When an MS in PMM-IDLE state changes to A/Gb mode and the RA changes, the

MS shall initiate the GPRS RAU procedures.– When an MS in PMM-CONNECTED state changes to the A/Gb mode, the MS shall

initiate the GPRS RAU procedure independent of whether the RA has changed ornot. The RAU procedure is either combined RA / LA update or only RAU.

A combined RA / LA update takes place in network operation mode I when the MSenters a new RA or when a GPRS-attached MS performs IMSI attach. The MS sends aRAU Request message indicating that an LA update may also need to be performed. Inthis case the SGSN forwards the LA update to the VLR. This concerns only idle mode(see 3GPP TS 23.122), as no combined RA / LA updates are performed during a CSconnection. In the context of this specification, the terms RNS (or RNC) refer also to aGERAN BSS (or BSC) when serving an MS in Iu mode.

A30808-X3247-M41-3-7618 199

InformationSystem


BSC RNCMS/ 2G+3GUE SGSN

1. Inter system change decision

2. RARQ

7. Forward packets

6. SRNS Data forward command

5. ACRE

8. Iu Release command

3. SRNS context request

3. SRNS context response

5. ACRQ

10. RACO

9. RAAC

11. MPCA

11. MPCR

12. Packet data transfer

(Gb) (lu)

8. Iu Release complete

200 A30808-X3247-M41-3-7618


1. The MS or the RAN decides to perform an inter system change which makes the MSswitch to a new cell where A/Gb mode has to be used, and stops transmission to thenetwork.

2. The MS sends a RAU Request (old RAI, old P-TMSI Signature, Update Type) mes-sage to the 2G+3G-SGSN. Update Type shall indicate RAU or combined RA / LAupdate or combined RA / LA update with IMSI attach requested. A combined RA /LA update with IMSI attach requested occurs if the MS wants to perform an IMSI at-tach. The BSS shall add the Cell Global Identity including the RAC and LAC of thecell where the message was received before passing the message to the 2G+3G-SGSN.

3. If the MS is PMM-CONNECTED state, the 2G+3G-SGSN sends an SRNS ContextRequest (IMSI) message to the SRNS.

4. Upon reception of the SRNS Context Request message, the SRNS starts bufferingand stops sending downlink PDUs to the MS. The SRNS responds with an SRNSContext Response (GTP-SNDs, GTP-SNUs, PDCP-SNDs, PDCP-SNUs) message.The GTP sequence numbers are included for each PDP context indicating the nextin-sequence downlink GTP-PDU to be sent to the MS and the next in-sequence GTPPDU to be tunnelled to the GGSN. For each active PDP context which uses losslessPDCP, the SRNS also includes the uplink PDCP sequence number (PDCP-SNU)and the downlink PDCP sequence number (PDCP-SND). PDCP-SNU is the PDCPsequence number for the next expected in-sequence uplink packet to be receivedfrom the MS. PDCP-SND is the PDCP sequence number of the first downlink packetfor which successful transmission has not been confirmed. The 2G+3G-SGSN shalltake off the eight most significant bits of the passed PDCP sequence numbers, thusconverting them to SNDCP N-PDU numbers of the respective 2G GPRS PDP con-texts.

5. Authentication/Ciphering functions may be executed.6. If the MS is PMM-CONNTECTED, the 2G+3G-SGSN sends an SRNS Data Forward

Command (RAB ID, Transport Layer Address, Iu Transport Association) message tothe SRNS. This message informs the SRNS that the 2G+3G-SGSN is ready to re-ceive data packets. Upon reception of SRNS Data Forward Command messagefrom the 2G+3G-SGSN, the SRNS shall start the data-forwarding timer.

7. For each RAB indicated by the SRNS Data Forward Command, the SRNS starts du-plicating and tunnelling the buffered GTP-PDUs back to the 2G+3G-SGSN. Foreach radio bearer which uses lossless PDCP, the GTP-PDUs related to transmittedbut not yet acknowledged PDCP-PDUs are duplicated and tunnelled back to the2G+3G-SGSN. Their related downlink PDCP sequence numbers are sent withthem. The 2G+3G-SGSN converts the PDCP sequence numbers to SNDCP se-quence numbers by taking off the eight most significant bits of the PDCP sequencenumbers.

8. The 2G+3G-SGSN sends an Iu Release Command message to the SRNS. Whenthe RNC data-forwarding timer has expired, the SRNS responds with an Iu ReleaseComplete message.

9. The 2G+3G-SGSN validates the presence of the MS in the new RA. If due to roam-ing restrictions the MS is not allowed to be attached in the RA, or if subscriptionchecking fails, the 2G+3G-SGSN rejects the RAU with an appropriate cause. If allchecks are successful, the 2G+3G-SGSN updates MM and PDP contexts for theMS. A new P-TMSI may be allocated. A logical link is established between the new2G+3G-SGSN and the MS. 2G+3G-SGSN initiates the establishment procedure. ARAU Accept (P-TMSI, P-TMSI Signature, Receive N-PDU Number) message is re-turned to the MS. The Receive N-PDU Number is equal to the converted PDCP-

A30808-X3247-M41-3-7618 201

InformationSystem


SNU. It contains the acknowledgements for each NSAPI which used lossless PDCPbefore the start of the update procedure. All mobile-originated N-PDUs which weresuccessfully transferred before the start of the update procedure are thereby con-firmed. If the Receive N-PDU Number confirms the reception of N-PDUs, these N-PDUs shall be discarded by the MS.

10. The MS acknowledges the new P-TMSI by returning a RAU Complete (Receive N-PDU Number) message to the SGSN. The Receive N-PDU Number is equal to theconverted PDCP-SND. It contains the acknowledgements for each NSAPI whichused lossless PDCP before the start of the update procedure. All mobile-terminatedN-PDUs which were successfully transferred before the start of the update proce-dure are thereby confirmed. If the Receive N-PDU Number confirms the receptionof N-PDUs, these N-PDUs shall be discarded by the 2G+3G-SGSN. The MS de-ducts Receive N-PDU Number from PDCP-SND by taking off the eight most signif-icant bits. PDCP-SND is the PDCP sequence number for the next expected in-sequence downlink packet which is received in the MS per radio bearer and whichused lossless PDCP. The new 2G-SGSN negotiates the use of acknowledged or un-acknowledged SNDCP with the MS for each NSAPI, regardless whether the SRNSused lossless PDCP or not.

11. A Modify PDP context request N -> MS is sent from 2G+3G-SGSN to the MS. TheMS responds with a Modify PDP context accept to the 2G+3G-SGSN MS -> N.

202 A30808-X3247-M41-3-7618


1.2.18 Other Procedures

1.2.18.1 Idle Traffic Channel Supervision

BTS BSCMS MSC

RESIN (*)

MEITCHIB

RESIN (*)

Contains the idle TCH measurements for all TCHs of the TRX currently not used for a call.(*)

ILUPLKIC

MEITCHIBILUPLKIC

.....

.....

A30808-X3247-M41-3-7618 203

InformationSystem


1.2.18.2 Uplink and Downlink Measurement Reports on Abis

BTS BSCMS MSC

MEAS REP

PWRUPDWCRXLVQUUCRXLVQUDCRXLVTAUCRXLVTADCFERRXQU

MESRS (MEAS REP) (*)

MEAS REPMESRS (MEAS REP) (*)

Measurement Reports are transmitted for each TCH of the TRX currently seized by a call only if thefeature ’Measurements on Abis’ (SET TRX: RADIOMR = TRUE) is enabled in the BSC database.

(*)

.....

..........

.....

PWRUPDWCRXLVQUUCRXLVQUDCRXLVTAUCRXLVTADCFERRXQU

204 A30808-X3247-M41-3-7618


1.2.18.3 IMSI Trace Invocation for Normal Call Setup

BTS BSCMS MSC

ESTIN (CMSREQ)

MRPCI

I (CLAMCH)

DT1 (CICMD)ENCRY (CIMCMD)



DT1 (CICMP)

I (TRCMD)

DT1 (TRCMD)DATRQ (TRCMD)

I (CMSREQ)SDCCH

SDCCH

I (CIMCMD)

SDCCH

SDCCH

SDCCH

CR (CL3I; CMSREQ)

Call setup ...

CC (MSIT)STRAC

STRACACK

Call setup continuation and completion...

TMEASRES (MEASREP)


TMEASRES (MEASREP)

TMEASRES (MEASREP)

A30808-X3247-M41-3-7618 205

InformationSystem


1.2.18.4 IMSI Trace Invocation for Incoming Inter-BSC Handover

BTSold BTSnewMS

CHNAK

I (HO CMD)

BSCnewBSCold MSC

CR (HO REQ)

DATRQ (HO CMD)

CC (HO RAC; HO CMD)


FACCH

CHNAV (New TCH)

Continuation of handover procedure ...

DT1 (MSIT)

I (HO CMP)

DATIN (HO CMP)

MRPCIDT1 (HO CMP)

RELRQ

DT1 (CL CMD)

DT1 (CL CMP)RELCN

RCHRA

RLSD


FACCH

RLC

RCHRL (Old TCH)


STRAC

STRACACK

TMEASRES (MEASREP)

TMEASRES (MEASREP)

206 A30808-X3247-M41-3-7618


1.3 GPRS Message Flows

1.3.1 GPRS ProceduresThis chapter describes the general procedures for GPRS Mobility Management andGPRS Session Management. The temporary block flows (TBF) which are used to trans-port signalling messages and user data between mobile and BSS are described in chap-ter 1.3.2.

1.3.1.1 GPRS Mobility Management: Attach Procedure

The Attach procedure is used by the mobile to register for GPRS services.

UL-TBF

DL-TBF

DL-TBF

UL-TBF

DL-TBF

UL-TBF

UL-TBF

2

1

3

4

5

MS BSC SGSN

IMSI or P-TMSI, MScapability, multislot classATRQ

IDRQ

IDRE

ACRQ

ACRE

ATAC

ACOM

IMSI

new P-TMSI

1. The mobile sends Attach Request containing information about its mobilecapabilities, its mutual class and its IMSI or P-TMSI for identification.

2. If the MS identifies itself with its P-TMSI but the P-TMSI is unknown in SGSN, theSGSN sends an Identity Request to the MS. The MS responds with IdentityResponse including its IMSI.

3. In contrast to ciphering in existing GSM (between BTS and MS) GPRS cipheringis a function of the LLC layer in the SGSN and in the mobiles. If enabled in theSGSN it initiates the authentication and ciphering procedure.

4. The network informs the MS that the Attach was accepted. The network mayinclude a new P-TMSI in the Attach Accept message.

5. If the Attach Accept contained a new P-TMSI, the MS confirms the reception withAttach Complete.

A30808-X3247-M41-3-7618 207

InformationSystem


1.3.1.2 GPRS Mobility Management: Detach Procedure

The detach procedure is used by the mobile to deregister from GPRS services.

The network may initiate the GPRS detach when GPRS services are no longer acceptedfor a subscriber (e.g. the subscriber is cancelled from the HLR database).

DL-TBF

UL-TBF1

MS BSC SGSN

detach typeDTRQ

DTAC2

(Mobile initiated)

1. The mobile initiated detach might be triggered by user command from mobilemenu or when the mobile is switched off.

2. If the detach Type indicates that the detach is not due to power switch off, theSGSN sends a Detach Accept to the MS.

UL-TBF

DL-TBF1

MS BSC SGSN

detach type, causeDTRQ

DTAC2

(Network initiated)

1. The SGSN informs the MS that it has been detached by sending detach Requestto the MS.

2. The mobile confirms the detach with detach accept.

208 A30808-X3247-M41-3-7618


1.3.1.3 GPRS Session Management: Activate PDP Context

A PDP context represents a logical connection between a mobile and the network witha specific PDP address for data routing (e.g. fixed or dynamic local IP address) and aspecific Quality of Service profile (QoS). The Activate PDP Context procedure is usedto establish the connection. If supported by the mobile several PDP Contexts with differ-ent QoS profiles might be active handling different applications.

DL-TBF

DL-TBF

UL-TBF

UL-TBF

2

1

3

MS BSC SGSN

QoS, opt. PDP-addressAPCR

APAC

XID

XID

QoS, opt. dyn. PDP-address

1.

In the Activate PDP Context Request the mobile includes a requested QoS. The MSshall use the PDP Address Information Element to indicate whether it requires theuse of a static PDP Address or whether it requires the use of a dynamic PDP ad-dress. The MS leaves the PDP Address IE empty to request a dynamic PDP ad-dress.

2.

The network verifies if it can support the requested QoS and if it is allowed for thissubscriber. Depending on the result, the SGSN may accept the Activate PDP Con-text Request with the requested or another QoS, or the SGSN rejects the ActivatePDP Context Request. If requested by the mobile, the SGSN assigns a dynamicPDP-address. The MS either accepts the negotiated QoS profile, or deactivates thePDP context.

3.

In the XID messages, parameters of the LLC and SNDCP layer are negotiated be-tween the mobile and the SGSN.

A30808-X3247-M41-3-7618 209

InformationSystem


1.3.1.4 GPRS Session Management: Deactivate PDP Context

The deactivate PDP Context procedure is used to deactivate a specific PDP Context.E.g. the related dial up connection is disconnected. The mobile remains GPRS at-tached. Network initiated PDP Context Deactivation is done with reverse message di-rections.

1.3.1.5 GPRS: Paging

In GMM STANDBY status a mobile performs routing area updates but it doesn’t informthe network about cell changes. A MS in STANDBY state must be paged by the SGSNbefore a downlink transfer to that MS is possible. The Paging procedure is used by thenetwork to determine the cell where the mobile is located and moves the GMM state toREADY.

DL-TBF

UL-TBF

MS BSC SGSN

causeDPRQ

DPAC

(Mobile initiated)

UL-TBF

P-TMSI or IMSI1

MS BSC SGSN

IMSI, Paging Area, opt. P-TMSIPAPS

UI2

PAGING

DL-TBF DTGR DL-Data

TLLI; CGI

1. The SGSN includes the IMSI, information about the area in which the mobile shallbe paged and if available a P-TMSI. If included, the BSC shall use the P-TMSI in-stead of IMSI in the PAGING message on the Um-interface.

2. In response to a GPRS page, the mobile usually sends an unnumbered Informationframe (UI). However any other uplink data from the MS can be a valid paging re-sponse. The BSC adds the Cell Global Identity (CGI) including RAC and LAC of thecell where the message was received before passing the message to the SGSN.

210 A30808-X3247-M41-3-7618


1.3.1.6 GPRS Mobility Management: Routing Area Update

A routing area update takes place when a GPRS attached MS detects that it has entereda new RA, when the periodic RA update timer has expired, or when a suspended MS isnot resumed by the BSS.

1. In the new cell the mobile sends a Routing Area Update Request including the oldRouting Area Identification and the reason for the routing area update. The BSCadds the new Cell Global Identity including RAC and LAC of the cell where the mes-sage was received before passing the message to the SGSN.

2. When the SGSN detects the routing area update, it sends a FLUSH-LL PDU to theold BVC to initiate the following procedure:- at a cell change between two NSEIs or between two routing areas, LLC-PDU(s)

stored at the "old" BVCI for the TLLI are deleted.- in response to a FLUSH-LL PDU the BSS shall send a FLUSH-LL-ACK PDU to

the SGSN containing: -the TLLI received in the FLUSH-LL PDU.

4

MS old BTS new BTS BSC SGSN

UL/DL-TBFs (Data)

UL-TBF

DL-TBF

UL-TBF

UL/DL-TBFs (Data)

2

5

3

2

1

UL/DL-Data

UL/DL-Data

new CGI, old RAI

DTGR

RARQ

RAAC

FLUSH-ACK

RACO

DTGR

FLUSH

TLLI

RAI; opt. new P-TMSI

TLLI, old BVCI, opt.new BVCI

A30808-X3247-M41-3-7618 211

InformationSystem


3. The SGSN validates the presence of the MS in the new RA. If the MS is not allowedto be attached in the RA due to regional subscription restrictions, or if subscriptionchecking fails, then the SGSN rejects the routing area update with an appropriatecause. If all checks are successful, then the SGSN updates the GMM context for theMS. A new P-TMSI may be allocated. A Routing Area Update Accept (RAAC) is re-turned to the MS.

4. The MS acknowledges the new P-TMSI by returning a Routing Area Update Com-plete (RACO).

5. Data transfer is continued in the new routing area.

212 A30808-X3247-M41-3-7618


1.3.1.7 GPRS Mobility Management: Cell Update

1. A cell update takes place when the MS enters a new cell inside the current RA andthe MS is in READY state. The MS performs the cell update procedure by sendingan uplink LLC frame of any type containing the MS identity to the SGSN. Towardsthe SGSN, the BSS adds the BVCI and Cell Global Identity including RAC and LAC.

2. When the SGSN detects the cell change, it sends a FLUSH-LL PDU to the old BVCto initiate the following procedure:- at a cell change within one NSEI (e.g. one PCU represents one NSEI) and

within one routing area, LLC-PDU(s) for a given TLLI stored at an "old" BVCI(corresponding to the old cell) are either deleted or transferred to a "new" BVCI(corresponding to the new cell) with which the TLLI is currently associated.

3. In response to a FLUSH-LL PDU the BSS shall send a FLUSH-LL-ACK PDU to theSGSN containing:- the TLLI received in the FLUSH-LL PDU and- an indication of whether the LLC-PDU(s) were "transferred" or "deleted". In case

the SDUs were "transferred" the BVCI (new) IE shall be included.4. Data transfer is continued in the new cell.

MS new BTS BSC SGSN

UL/DL-TBFs (Data)

UL/DL-TBFs (Data)

1

2

4

UL-TBF (UI)

old BTS

3

DTGR

UI

FLUSH

FLUSH-ACK

DTGR

UL/DL-Data

TLLI, new BVCI

TLLI, old BVCI, opt.new BVCI

TLLI

UL/DL-Data

A30808-X3247-M41-3-7618 213

InformationSystem


1.3.1.8 GPRS: Suspend / Resume

Circuit switched traffic, e.g. Mobile OriginatedCall, answer to paging, Location Update

MS BSS SGSN

UL/DL-TBFs (Data)

CHNREQ

DL-TBF

GPRSSU TLLI Cause

DISC

CHNREL (Resume)

UL/DL-TBF

DTGR UL/DL-Data

DTGR DL-Data

SUS TLLI

RSTA TLLI

LLCD TLLI

DTGR UL/DL-Data

3

4

3

5

6

1

2

SDCCH

RACH

SUSA

RES

RESA

214 A30808-X3247-M41-3-7618


The Suspend / Resume procedure is used to interrupt GPRS data traffic temporarily toallow circuit switched services, e.g. answer to Paging for an incoming call, a periodicLocation Update or in our example a Mobile Originating Call.

1. The mobile is transferring data.2. The mobile leaves the Packet data traffic channels and switches to the BCCH. It re-

quests a signalling channel (SDCCH) by sending CHNREQ on the Random AccessChannel.

3. If a downlink TBF is active during this time, it will fail because the mobile is no longermonitoring the PDTCHs. The BSC reports this lost downlink TBF with a Radio Sta-tus (RSTA) and the number of not transferred with a LLC-discarded (LLCD) towardsthe SGSN.

4. The mobile sends a GPRS Suspend Request on the SDCCH. The BSC forwards theSuspend to the SGSN. The call set-up continues.

5. The call ends and the circuit switched resources are released. The BSC includes theresume command towards the mobile in the channel release message and sends inparallel a resume message towards SGSN.

6. Whether data transfer is continued or not depends on the recovery mechanism andtime out of the suspended application.

A30808-X3247-M41-3-7618 215

InformationSystem


1.3.2 LC/MAC Message FlowsAll afore mentioned GPRS Mobility Management and Data Transfer procedures use theRLC/MAC message flows described below.

Data and GMM messages are transferred in Temporary Block Flows (TBF). Each TBFconsists of the resource allocation, the transfer of RLC/MAC data blocks itself, the re-spective acknowledgements if required and the release of the resources. Four basicTBF types exist:

– Uplink TBF– Downlink TBF– Concurrent Uplink TBF– Concurrent Downlink TBF

This document decribes the RLC/MAC implementation of the BSS releases BR55/10 toBR55/14. As GPRS is constantly improved, slight changes will apply for the loads fromBR55/15 onwards.

PBCCH issues are not yet included in the message flows. This is the PBCCH feature isnot officially released within BR55 and only a single type of phone is available for testing.

In case more detailed information is required, please refer to the GSM specifications(RLC/MAC: GSM 04.60).

Timeslot allocation of various multislot classes:

Up- and downlink resources are allocated to the mobiles depending on their multislotclasses.

This is important to understand the resource allocation for different mobiles on theRLC/MAC layer.

Multislot Class # of TS Relative Timeslot Allocation

1 1+1 DL: 1 - UL: 12 2+1 DL: 1,2 - UL: 24 3 +1 DL: 1,2,3 - UL: 28 4+1 DL: 1,2,3,4 - UL: 3

216 A30808-X3247-M41-3-7618


1.3.2.1 Uplink TBF

MS BTS BSCUL-LLC-Datain MS

(...)

(...)

(...)

(...)

(...)

(...)

1

7

6

5

4

2

3

TLLI;Contention Resolut.;Ack BSN=0; USF

Ack BSN=0; USFTLLI;Contention Resolution;

CHNREQ (Uplink TBF)

I (IMASS) Packet UL Ass.: TFI; USF; CS

RMAC-DL (PDDCB) USF

RMAC-UL (PUDCB)

RMAC-UL (DATA) TLLI; BSN=0; CV=15

RMAC-UL (DATA) TLLI; BSN=x; CV=15

RMAC-DL (PUAN)

RMAC-UL (DATA) TLLI; BSN=x+1; CV=15

CHNRD (Uplink TBF)

CHNAV PDCH

CHNAK

IACMD (IMASS) Packet UL Ass.: TFI; USF; CS

PCU-DL (PDDCB) USF

PCU-UL (PUDCB)

PCU-UL (DATA) TLLI; BSN=0; CV015

PCU-UL (DATA) TLLI; BSN=x; CV=15

PCU-DL (PUAN)

PCU-UL (DATA) TLLI; BSN=0; CV=15

PACCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

AGCH

RACH

A30808-X3247-M41-3-7618 217

InformationSystem


MS BTS BSC

(...)

(...)

(...) (...)

8

(...)

(...)

9

10

11

12

Ack for NRLCMAX; USFAck for BSN=NRLCMAX; USF

BSN=y+1; CV=15BSN=y+1; CV=15

BSN=z; CV=15 BSN=z; CV=15

BSN=z+1; CV=14 BSN=z+1; CV=14

BSN=z+15; CV=0BSN=z+15; CV=0

UL Data Repetition UL Data Repetition

Ack BSN=z+15; RRBP=1

Final Ack for BSN=z+15;RRBP=1

RMAC-UL (DATA) BSN=y; CV=15

RMAC-DL (PUAN)

RMAC-UL (DATA)

RMAC-UL (DATA)

PCU-UL (DATA) BSN=y; CV=15

PCU-UL (PUAN)

PCU-UL (DATA)

PCU-UL (DATA)

RMAC -UL (DATA) PCU-UL (DATA)

RMAC-UL (DATA) PCU-UL (DATA)

RMAC-UL (PUDCB) PCU-UL (PUDCB)

RMAC-UL (DATA) PCU-UL (DATA)

RMAC-DL (PUAN) PCU-DL (PUAN)

4 ACCESS BURST (PCA) PCU-UL (PCA)

PACCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

PDTCH

PACCH

218 A30808-X3247-M41-3-7618


Uplink TBF / One Phase Access on CCCH

The purpose of the packet access procedure is to establish an uplink TBF to transferLLC PDUs in the direction from the mobile station to the network.

The scenario describes the packet access procedure on CCCH (no PBCCH is config-ured in the cell). With the one phase access, only a single PDCH can be allocated in theuplink direction, otherwise a two phase access is required.

1. The MS sends a Channel Request message with the establishment cause. For Onephase packet access with request for single timeslot uplink transmission; one PDCHis needed (011110xx, 01111x0x, 01111xx0).

2. If no PDCH has been activated, a single timeslot will be configured as PDCH andthe Time Alignment procedure is performed.

3. The BSC sends an Immediate Assignment towards the MS. A set of GPRS relatedparameters is included indicating e.g. the Temporary Flow Identifier (TFI), the UplinkState Flag (USF) and the Coding Scheme (CS).

4. Packet Downlink Dummy Control Blocks (PDDCB) with the USF value previously as-signed to the MS are transmitted in the allocated PDCH. The MS monitors the USFof all downlink blocks on this timeslot to send its uplink data blocks as response tothe occurence of its assigned USF.The PDDCBs continue during the whole uplink TBF - only the first one is drawn inthe message flow!

5. A Mobile might send a Packet Uplink Dummy Control Block (PUDCB) as first blockof an uplink TBF. This is probably because the uplink user data is not yet ready fortransmission inside the MS.

6. The MS starts to send user data (LLC-frames) inside the uplink RLC/MAC blocks.The TLLI of the MS is included until the Contention Resolution procedure is complet-ed (first PUAN with TLLI). The data blocks are counted up with the Block SequenceNumber BSN (modulo 128). The Countdown Value CV remains at its maximum val-ue as long as more than 15 RLC/MAC data blocks remain to be send.

7. The BSC acknowledges the first received uplink data block with a Packet UplinkAck/Nack message (PUAN).As soon as the MS receives this first PUAN message including its TLLI, the Conten-tion Resolution is completed and the MS continues sending its uplink data blockswithout its TLLI inserted. The MS is now clearly identified - concurrent TBF handlingaccording to its multislot capabilities is possible.

8. The BSC acknowledges every single uplink data block received from the mobile witha moving window mechanism. For this purpose the BSC sends every N-th block(N=NRLCMAX; BSS database parameter) a PUAN message indicating whichblocks were correctly received or not. Missing blocks will be repeated by the mobileand acknowledged in the next scheduled PUAN message.

9. If the MS has sent most of its uplink data, the Countdown Value CV starts countingdown towards the final block. This allows the network to calculate the remainingblocks of the running uplink TBF.

10. As soon as CV=0 is reached, the MS has transferred all uplink data. The uplink TBFhowever remains open until the last sent blocks were acknowledged by the BSS.The MS repeats uplink blocks that have been sent already before the final PUAN isreceived.

11. The BSC confirms the remaining uplink blocks with the final PUAN – the Final AckIndication is set. Additionally the MS is polled with the RRBP-bit set to confirm thereception of this final PUAN.

A30808-X3247-M41-3-7618 219

InformationSystem


12. The Packet Control Ack (PCA) confirms the reception of the previous final PUAN.Now the uplink TBF is complete and the MS returns to monitor the BCCH.

220 A30808-X3247-M41-3-7618


1.3.2.2 Downlink TBF

MS BTS BSC

(...)

(...)(...)

(...)

9

(...)

(...)

DL-LLC-Dataon Gb

4

8

7

6

5

1

3

2

Packet DL Ass.; TLLI; TFI; TS2Packet DL Ass.; TLLI; TFI; TS=2

TLLI; TFI; RRBP=1;TS2 TLLI; TFI; RRBP=1send on TS2

(PDCH: TS 1,2,3 if necessary)

TS2TS2

TFI; BSN=0; TS 1

TFI; TA value; TS2TFI; TA value; TS2

TFI; BSN=1; TS3 TFI; BSN=1; TS3

TFI; BSN=2; TS1

TFI; BSN=0; TS 1

TFI; BSN=19; TS2; RRBP=1 TFI; BSN=19; TS2; RRBP=1

TFI; BSN=20; TS3 TFI; BSN=20; TS3

TFI;Ack/Nack Description;TS2TFI;Ack/Nack Description;TS2

TFI; BSN=yTFI; BSN=y

I (IMASS)

RMAC-DL (PDAS)

4 ACCESS BURST (PCA)

CHNAV

CHNAK

IACMD (IMASS)

PCU-DL (PDAS)

PCU-UL (PCA)

RMAC-DL (DATA)

RMAC-DL (PPCTA)

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (PPCTA)

PCU-DL (DATA)

PCU-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

TFI; BSN=2; TS1

RMAC-UL (PDAN)

RMAC-DL (DATA)

PCU-UL (PDAN)

PCU-DL (DATA)

PACCH

PACCH

PDTCH

PDTCH

PACCH

AGCH/PCH

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

A30808-X3247-M41-3-7618 221

InformationSystem


Downlink TBF / Example with a 3+1 Mobile / CCCH only

A downlink TBF is initiated by the network as soon as LLC data coming from the GSNmust be transferred towards the mobile. This scenario assumes the MS is in GMM readystate, therefore no paging is required or it was already performed including the pagingresponse.

1. Downlink data (LLC-frame) arrives on the Gb-interface from the SGSN.2. If no PDCH has been activated, the required number of timeslots will be configured

as PDCH. The actually activated number of timeslots basically depends on the MScapabilities (which are known to the BSC since its GPRS attach), however lesstimeslots are possible under various circumstances (e.g. traffic load). For eachtimeslot a separate CHNAV/CHNAK message is required - the timeslot numbers in-dicated in the message flow are regarded as relative numbers!

3. The BSC sends an Immediate Assignment for a downlink TBF towards the MS. Aset of GPRS related parameters is included, indicating e.g. the Temporary LogicalLink Identity (TLLI) of the MS and the Temporary Flow Identifier (TFI) of the TBF.The IA message is either sent on the AGCH or the PCH - depending if the MS isstill in Non-DRX Mode or not. Only a single timeslot can be allocated with the Imme-diate Assignment message.

4. The MS moves to the allocated PDCH timeslot (according the IA) where it receivesthe Packet Downlink Assignment (PDAS). This message now allocates all intendeddownlink timeslots (in our case three) and includes e.g. the TLLI as well as the TFI.Additionally the poll bit is set (RRBP=1) - the BSC requests a confirmation from theMS about the correct reception of the PDAS message.

5. The MS responds to the polling with a Packet Control Ack (PCA) - the PCA formatis 4 access bursts. These access bursts are used by the BSC to calculate the initialtiming advance value for the mobile.

BTS BSC

11

10

MS

TFI; BSN=z-1TFI; BSN=z-1

TFI; BSN=z; TS2;FBI=1; RRBP=1 FBI=1; RRBP=1

TFI; BSN=z; TS2;

TFI; Final/ACK/NACK; TS2 TFI; Final/ACK/NACK; TS2

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-UL (PDAN)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-UL (PDAN)

PACCH

PDTCH

PACCH

222 A30808-X3247-M41-3-7618


6. Downlink data transfer starts on timeslot 1. The MS listens on the assigned 3timeslots to all downlink blocks with its own TFI, the RLC/MAC blocks are countedup with the Block Sequence Number (BSN).

7. The initial timing advance value is sent to the MS with a Packet Power Control/Tim-ing Advance message (PPCTA). This allows the mobile to transmit (e.g. PDAN) be-fore a continuous timing advance value is available.

8. Every N-th downlink data block (N=NRLCMAX, in this case the default value NRL-CMAX=20 is used) the BSC polls the MS for a Packet Downlink Ack/Nack message(PDAN). This polling can only be sent on the timeslot of the TBF which is used foruplink signalling purpose - in case of a 3+1 MS timeslot #2 is used.

9. The MS answers the polling with a PDAN message. All RLC/MAC data blocks re-ceived by the MS until the transmission of this PDAN are acknowledged.A moving window mechanism is used. If blocks were not correctly received by themobile, the BSC will repeat them soon after the reception of the PDAN. The repeat-ed blocks will then be acknowledged in the next PDAN message.

10. If the end of the downlink transfer is reached (last BSN=z), the BSC sets the FinalBlock Indicator bit (FBI) in this last block and polls the MS for a final PDAN(RRBP=1).

11. The MS confirms the remaining downlink blocks with a PDAN. The Final Ack Indica-tion is set, the downlink TBF is complete and no retransmissions are required. TheMS remains on the PDCH and listens for new assignments until the timer T3192 ex-pires. Afterwards it returns to listen to the BCCH.

A30808-X3247-M41-3-7618 223

InformationSystem


1.3.2.3 Concurrent UL TBF

BTS BSC

2

1

MS

(...) (...)

(...)(...)

(...)

(...)

(...)

5

3

4

6

(...)

UL-LLC-DATAin MS

TFI; Ch.Req.; TS2 TFI; Channel Request Des.; TS2

RMAC-DL (PUAS) TFI; USF; CS

RMAC-DL (PDDCB) USF; TS2

PCU-DL (PUAS) TFI; USF; CS; TS2

PCU-DL (PDDCB) USF; TS2

RMAC-UL (PUDCB) TLLI; TS2TLLI; TS2PCU-UL (PDDCB)

TFI; BSN

TFI; BSN

TFI; BSN

TFI; BSN

TFI; BSN

TFI; BSN

TFI; BSN; TS2; RRBP=1

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-DL (PDAN)

TFI; BSN

RMAC-UL (PDAN)

RMAC-DL (DATA)

PCU-UL (PDAN)

PCU-DL (DATA)

RMAC-DL (DATA)PCU-DL (DATA)

TFI; BSN

TFI; BSNTFI; BSN; TS3

TFI; BSN

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

TFI; BSN; TS1TFI; BSN; TS1


TFI; BSN TS2; USFTFI; BSN TS2; USF

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

PACCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

224 A30808-X3247-M41-3-7618


All uplink transfer related messages / parameters are in blue colour and italics.

The downlink TBF is ongoing similar to the DL-only description, however not allapplicable blocks can be shown in this message flow.

BTS BSC

9

7

MS

(...) (...)

(...)

12

10

11

(...)

(...)

8

(...)

RMAC-UL (DATA)

RMAC-UL (DATA)

RMAC-UL (DATA)

RMAC-UL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-UL (DATA)

PCU-UL (DATA)

RMAC-DL (PUAN) PCU-DL (PUAN)

4 ACCESS BURST (PCA) PCU-UL (PCA)

BSN=0; CV=2; TS2

BSN=1; CV=1; TS2

BSN=2; CV=0; TS2

UL Data Repetition; TS2

BSN=0; CV=2; TS2

BSN=1; CV=1; TS2

BSN=2; CV=0; TS2

UL Data Repetition; TS2

Final Ack; RRBP=1; TS2

TS2TS2



TFI; BSNTFI; BSN

TFI; BSN

TFI; BSNTFI; BSN

TFI; BSN

Final Ack; RRBP=1; TS2

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

PDTCH

A30808-X3247-M41-3-7618 225

InformationSystem


Concurrent UL TBF while a DL TBF is actice / Example with a 3+1Mobile / CCCH only

If a downlink TBF is already active and the MS needs to transmit data in uplink directionadditionally, a concurrent uplink TBF is initiated.

The described scenario occurs frequently for instance in case of a downlink FTP trans-fer: While the downlink data is transported in a continuously running DL TBF (in our ex-ample 3 timeslots), the FTP Acks need to be sent in uplink direction.

Concurrent DL TBF while a UL TBF is active / Example with a 3+1Mobile / CCCH only

CAUTION: As the downlink transfer is continuously active during the whole uplink as-signment (or even UL TBF), the usual DL message flow continues respectively. Pleasebe aware that not all DL TBF related messages can be inserted in the message flow(please refer to DL TBF only description).

1. LLC data is ready for uplink transmission towards the network. The downlink TBFis running.

2. The MS requests resources for an uplink TBF within the next scheduled PacketDownlink Ack/Nack (PDAN) of the running downlink TBF. For this purpose it addsa Channel Request Description element inside the PDAN message.

3. The BSC sends a Packet Uplink Assignment (PUAS) towards the MS.The Temporary Flow Identifier (TFI), the Uplink State Flag (USF) and the CodingScheme (CS) are specified.The PUAS is sent on relative timeslot 2 which is used as uplink timeslot in case ofa 3+1 MS.

4./5 The BSC sets the assigned USF in downlink blocks on timeslot 2.6. The MS might send a Packet Uplink Dummy Control Block (PUDCB) as first block

of the new UL TBF. This probably because the uplink user data is not yet ready fortransmission inside the MS.

7. The MS starts sending the uplink user data. The Contention Resolution procedureis not necessary as the MS is aIready clearly identified by the running DL TBF. Inour example the complete uplink transfer consists of only 3 RLC/MAC blocks,which is a typical scenario for FTP uplink Acks in a downlink FTP.

8. The last uplink block is sent with the Countdown Value (CV) = 0. This indicates thecomplete transmission of the uplink data and triggers the final Packet UplinkAck/Nack (PUAN) message.

9. The MS repeats the uplink blocks until the final PUAN has been received by theMS.

10. The BSC sends the final Packet Uplink Ack/Nack (PUAN) and polls the MS toconfirm its reception (RRBP=1).

11. A Packet Control Ack (PCA) is sent by the MS as response to the previouspolling.

12. The downlink TBF continues solely.

226 A30808-X3247-M41-3-7618


1.3.2.4 Concurrent DL TBF

BTS BSC

1

MS

(...) (...)

(...)

4

2

3

(...)

(...)

5

6

(...)

(...)

CHNAV

CHNAK

DL-LLC-Dataon Gb

PDCH; TS 1,3; please refer to text

RMAC-DL (PDAS)

PCU-UL (PCA)

TLLI; TFI; RRBP=1; TS2TLLI; TFI; RRBP=1; TS2PCU-DL (PDAS)

TS2TS2

USF;TS2USF;TS2

RMAC-UL (DATA)

RMAC-DL (PUAN)

RMAC-UL (DATA)

BSN; CV=15; TS2BSN; CV=15

Ack BSN#; USF; TS2Ack BSN#; USF; TS2

BSN; CV=15; TS2BSN; CV=15; TS2

RMAC-DL (PDDCB)

RMAC-UL (DATA)

RMAC-DL (PDDCB)

RMAC-UL (DATA)

USF; TS2USF; TS2


PCU-DL (PDDCB)

PCU-UL (DATA)

PCU-DL (PDDCB)

PCU-UL (DATA)

USF; TS2USF; TS2


BSN; CV=15; TS2RMAC-UL (DATA) BSN; CV=15; TS2

4 ACCESS BURST (PCA)

PCU-DL (PDDCB)

PCU-UL (DATA)

PCU-UL (DATA)

RMAC-DL (PDDCB)

PCU-DL (PUAN)

PCU-UL (DATA)

PDTCH

PDTCH

PDTCH

PACCH

PDTCH

PDTCH

PACCH

PDTCH

PACCH

PDTCH

PDTCH

A30808-X3247-M41-3-7618 227

InformationSystem


All downlink transfer related messages / parameters are in blue colour and italics.

The uplink TBF is ongoing similar to the UL-only description, however not all applicableblocks can be shown in this message flow.

BTS BSC

7

MS

(...) (...)

(...)

10

8

9

(...)

(...)

11

(...)

(...)

(...) (...)

(...)

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-UL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-UL (DATA)

PCU-DL (DATA)TFI; BSN=2; TS3 TFI; BSN=2; TS3

RMAC-DL (DATA)

RMAC-DL (DATA)

RMAC-UL (DATA)

RMAC-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

PCU-DL (DATA)

RMAC-UL (PDAN)

RMAC-DL (DATA)

PCU-UL (PDAN)

PCU-DL (DATA)

RMAC-UL (PDAN) PCU-UL (PDAN)

TFI; BSN=18; TS1TFI; BSN=18; TS1

TFI; BSN=1; TS2; USF TFI; BSN=1; TS2; USF

TFI; BSN=0; TS1

TFI; BSN=19;... TFI; BSN=19; TS2; RRBP=1; USF

TFI; BSN=20; TS3TFI; BSN=20; TS3

TFI; Ack/Nack Des.; TS2TFI; Ack/Nack Des.; TS2

TFI; BSN=33;...

TFI; BSN=33; TS2;FBI=1; RRBP=1; USF

TFI; Final Ack/Nack Des.; TS2TFI; Final Ack/Nack Des.; TS2

TFI; BSN=0; TS1

BSN; CV=15BSN; CV=15

BSN; CV=15BSN; CV=15PCU-UL (DATA)

BSN; CV=15BSN; CV=15

RMAC-UL (DATA)PCU-UL (DATA)

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PDTCH

PACCH

PACCH

228 A30808-X3247-M41-3-7618


Concurrent DL TBF while a UL TBF is active / Example with a 3+1Mobile / CCCH only

If an uplink TBF is already running and the MS needs to send data in downlink directionadditionally, a concurrent downlink TBF is initiated.

The described scenario occurs frequently for instance in case of an uplink FTP transfer:While the uplink data is transported in a continuously running UL TBF (in our example 1timeslot), the FTP ACKs need to be sent in downlink direction.

CAUTION: As the uplink transfer is continuously active during the whole downlink as-signment (or even DL TBF), the usual UL message flow continues respectively. Pleasebe aware that not all UL TBF related messages can be inserted in the message flow(please refer to UL TBF only description).

1. An uplink transfer between the MS and the BSS is ongoing. We assume the rela-tive timeslot 2 is already used for the uplink transfer because an uplink FTP is al-ready running for a longer time.In case the uplink TBF was just opened on the relative timeslot 1 and a first con-current downlink TBF is required, the system will send a Packet Timeslot Recon-figure message (PTR) instead of the PDAS (see below).This because the position of the running uplink TBF must be moved to the relativetimeslot 2 during a 3 timeslot downlink TBF.

2. Downlink data (LLC-frame) arrives on the Gb-interface from the GSN.3. If only a single PDCH is activated yet, two more timeslots will be configured as

PDCH and the Time Alignment procedure is performed on these new timeslots.4. The uplink TBF continues - PDDCBs indicate the assigned USF towards the MS,

the MS sends its data in the next uplink block.5. The BSC sends a Packet Downlink Assignment (PDAS) towards the MS. This

message assignes the used downlink TBF timeslots and the Temporary Flow Iden-tifier (TFI) to the MS (TLLI).Additionally the poll bit is set (RRBP=1) - the BSC requests a confirmation from theMS about the correct reception of the PDAS message.

6. The MS responds to the polling with a Packet Control ACK (PCA) in the reserveduplink block. The uplink TBF is meanwhile ongoing.

7. The BSC starts sending the downlink data blocks of the new TBF. The DL datablocks on TS 2 continue setting the USF bit for the ongoing uplink TBF.

8. After NRLCMAX blocks are sent, the BSC polls the MS for a Packet DownlinkACK/NACK message (PDAN). (In our case NRLCMAX=20, therefore the downlinkdata block with BSN=19 polls the MS).Due to the polling this block must be sent on TS 2 even if a different NRLCMAXvalue suggests another timeslot.

9. The PDAN message from the MS is received in the reserved uplink radio block. AllRLC/MAC data blocks successfully received by the MS until the transmission ofthis message are acknowledged.

10. The final downlink data block is sent from the BSC. The Final Block Indicator Bit(FBI) is set and the BSC polls for a final Packet Downlink ACK/NACK (RRBP=1).Due to the polling, also this block must be sent on TS 2 independent of the previoussequence.

11. The final PDAN confirms all remaining RLC/MAC blocks of the downlink TBF.

A30808-X3247-M41-3-7618 229

InformationSystem


2 Counter / Message Abbreviations

Abbreviation Long Name Type

-A-

ABORT ABORT BSSLAP MessageACRE AUTHENTICATION & CIPHERING RESPONSE GMM (GPRS MM/SM) MessageACRQ AUTHENTICATION & CIPHERING REQUEST GMM (GPRS MM/SM) MessageAGCH ACCESS GRANT CHANNEL Um ChannelALERT ALERTING DTAP MessageASS CMD ASSIGNMENT COMMAND DTAP MessageASS CMP ASSIGNMENT COMPLETE DTAP MessageASS COM ASSIGNMENT COMPLETE BSSMAP MessageASS FAIL ASSIGNMENT FAILURE DTAP MessageASS FAI ASSIGNMENT FAILURE BSSMAP MessageASS REQ ASSIGNMENT REQUEST BSSMAP MessageAUTREP AUTHENTICATION RESPONSE DTAP MessageAUTREQ AUTHENTICATION REQUEST DTAP Message

-B-

BCCH BROADCAST CONROL CHANNEL Um ChannelBCINF BCCH INFORMATION Um MessageBWHCI INTERCELL HANDOVER CONDITION INDICA-

TIONAbis RSL Message

BSSMAP BASE STATION MANAGEMENT APPLICATIONPART

A-Protocol

-C-

CC CONNECTION CONFIRM SCCP MessageCCONF CALL CONFIRMED DTAP MessageCHMM CHANNEL MODE MODIFY DTAP MessageCHMMACK CHANNEL MODE MODIFY ACKNOWLEDGE DTAP MessageCHNAK CHANNEL ACTIVATION ACKNOWLEDGE Abis RSL MessageCHNAV CHANNEL ACTIVATION Abis RSL MessageCHNRD CHANNEL REQUIRED Abis RSL MessageCHNREQ CHANNEL REQUEST Um MessageCHREL CHANNEL RELEASE DTAP MessageCICMD CIPHER MODE COMMAND BSSMAP MessageCICMP CIPHER MODE COMPLETE BSSMAP MessageCIMCMD CIPHERING MODE COMMAND DTAP MessageCIMCMP CIPHERING MODE COMPLETE DTAP MessageCLAMCH CLASSMARK CHANGE DTAP MessageCLCH CLASSMARK CHANGE Abis RSL MessageCL CMD CLEAR COMMAND BSSMAP Message

230 A30808-X3247-M41-3-7618


CL CMP CLEAR COMPLETE BSSMAP MessageCLUPD CLASSMARK UPDATE BSSMAP MessageCL REQ CLEAR REQUEST BSSMAP MessageCL3I COMPLETE LAYER 3 INFORMATION BSSMAP MessageCMSACC CM SERVICE ACCEPT DTAP MessageCMSREQ CM SERVICE REQUEST DTAP MessageCOIN (BSC->SMLC) CONNECTION ORIENTED INFORMATION BSSMAP-LE MessageCONACK CONNECT ACKNOWLEDGE DTAP MessageCONNECT CONNECT DTAP MessageCPACK SHORT MESSAGE CP-ACK DTAP MessageCPDAT SHORT MESSAGE CP-DATA DTAP MessageCPROC CALL PROCEEDING DTAP MessageCR CONNECTION REQUEST SCCP MessageCREF CONNECTION REFUSED SCCP Message

-D-

DATIN DATA INDICATION Abis RSL MessageDATRQ DATA REQUEST Abis RSL MessageDELIN DELETE INDICATION Abis RSL MessageDESAC DEACTIVATE SACCH Abis RSL MessageDISC DISCONNECT DTAP MessageDISC DISCONNECT Um layer 2 MessageDM DISCONNECT MODE Um layer 2 MessageDTAP DIRECT TRANSFER APPLICATION PART Protocol

(MS<->BSC,MS<->MSC)

DT1 DATA FORM 1 SCCP Message

-E-

EMSETUP EMERGENCY SETUP DTAP MessageENCRY ENCRYPTION COMMAND Abis RSL MessageERIN ERROR INDICATION Abis RSC MessageESTCN ESTABLISH CONFIRM Abis RSL MessageESTIN ESTABLISH INDICATION Abis RSL MessageESTRQ ESTABLISH REQUEST Abis RSL MessageE-TA_REQ (SMLC->BSC) TIMING ADVANCE REQUEST BSSLAP MessageE-TA_RES (BSC->SMLC) TIMING ADVANCE RESPONSE BSSLAP Message


A30808-X3247-M41-3-7618 231

InformationSystem


-F-

FACCH FAST ASSOCIATED CONTROL CHANNEL Um ChannelFACIL FACILITY DTAP MessageFHREQ FORCED HO REQUEST Abis RSL MessageFR FULL RATE Speech Version

-G-

-H-

HANDO HANDOVER DETECTION Abis RSL MessageHO CMD HANDOVER COMMAND DTAP MessageHO CMP HANDOVER COMPLETE DTAP MessageHO DET HANDOVER DETECT BSSMAP MessageHO FAIL HANDOVER FAILURE DTAP MessageHO FAI HANDOVER FAILURE BSSMAP MessageHO PER HANDOVER PERFORMED BSSMAP MessageHO RAC HANDOVER REQUEST ACKNOWLEDGE BSSMAP MessageHO REQ HANDOVER REQUEST BSSMAP MessageHO RQD HANDOVER REQUIRED BSSMAP MessageHO RRJ HANDOVER REQUIRED REJECT BSSMAP MessageHR HALF RATE Speech Version

-I-

I INFORMATION Um layer2 MessageIACMD IMMEDIATE ASSIGN COMMAND Abis RSL MessageIMASS IMMEDIATE ASSIGNMENT DTAP MessageIMASSRJ IMMEDIATE ASSIGNMENT REJECT DTAP MessageIMDETIN IMSI DETACH INDICATION DTAP MessageIMSETUP IMMEDIATE SETUP MESSAGE BSSMAP MessageISHUTRAN INTER SYSTEM HANDOVER TO UTRAN DTAP-RR Message

-J-

-K-


232 A30808-X3247-M41-3-7618


-L-

LCSREQ (BSC->BTS) LOCATION BASED SERVICES REQUESTLCSRRES (BTS->BSC) LOCATION BASED SERVICES RESPONSELUACC LOCATION UPDATING ACCEPT DTAP MessageLUREQ LOCATION UPDATING REQUEST DTAP Message

-M-

MEAS REP MEASUREMENT REPORT Um MessageMESRS MEASUREMENT RESULT Abis RSL MessageMOMAK MODE MODIFY ACKNOWLEDGE Abis RSL MessageMOMRQ MODE MODIFY REQUEST Abis RSL MessageMPCA MODIFY PDP CONTEXT ACCEPT MS -> N GMM (GPRS MM/SM) MessageMPCR MODFY PCP CONTEXT REQUEST N -> MS GMM (GPRS MM/SM) MessageMRPCI MS RF POWER CAPABILITY INDICATION Abis RSL MessageMSIT MSC INVOKE TRACE BSSMAP Message

-N-

NCH NOTIFICATION CHANNEL UM ChannelNOTCMD NOTIFICATION COMMAND SRSL

-O-

OVERLOAD OVERLOAD Abis RSL Message

-P-

PAGIN PAGING BSSMAP MessagePAGREQ PAGING REQUEST Um MessagePAGRES PAGING RESPONSE DTAP MessagePAREA PREFERRED AREA Abis RSL MessagePAREQ PREFERRED AREA REQUEST Abis RSL MessagePCH PAGING CHANNEL Um ChannelPGCMD PAGING COMMAND Abis RSL MessagePHCCN PHYSICAL CONTEXT CONFIRM Abis RSL MessagePHCRQ PHYSICAL CONTEXT REQUEST Abis RSL MessagePLRQ (MSC->BSC) PERFORM LOCATION REQUEST BSSMAP MessagePLRQ (BSC->SMLC) PERFORM LOCATION REQUEST BSSMAP-LE MessagePLRS (BSC->MSC) PERFORM LOCATION RESPONSE BSSMAP MessagePLRS (SMLC->BSC) PERFORM LOCATION RESPONSE BSSMAP-LE MessagePROGRES PROGRESS DTAP Message


A30808-X3247-M41-3-7618 233

InformationSystem


-Q-

QUIND QUEUING INDICATION BSSMAP Message

-R-

RAAC ROUTING AREA UPDATE ACCEPT GMM (GPRS MM/SM) MessageRACH RANDOM ACCESS CHANNEL Um ChannelRACO ROUTING AREA UPDATE COMPLETE GMM (GPRS MM/SM) MessageRARQ ROUTING AREA UPDATE REQUEST GMM (GPRS MM/SM) MessageRCHRA RF CHANNEL RELEASE ACKNOWLEDGE Abis RSL MessageRCHRL RF CHANNEL RELEASE Abis RSL MessageRELCMP RELEASE COMPLETE DTAP MessageRELCN RELEASE CONFIRM Abis RSL MessageRELEAS RELEASE DTAP MessageRELIN RELEASED INDICATION Abis RSL MessageRELRQ RELEASE REQUEST Abis RSL MessageRESET RESET BSSLAP MessageRESIN RF RESOURCE INDICATION Abis RSL MessageRETRACK RETRIEVE ACKNOWLEDGE DTAP MessageRETRV RETRIEVE DTAP MessageRLC RELEASE COMPLETE SCCP MessageRLSD RELEASED SCCP MessageRPAC RP-ACK SMRP MessageRPDA RP-DATA SMRP MessageRSL RADIO SIGNALLING LINK Abis-Protocol

-S-

SABM SET ASYNCHRONOUS BALANCED MODE Um layer2 MessageSACC SERVICE ACCEPT GMM (GPRS MM/SM) MessageSACFL SACCH FILLING Abis RSL MessageSACCH SLOW ASSOCIATED CONTROL CHANNEL Um ChannelSAPI SERVICE ACCESS POINT IDENTIFIER LAPD Addressing IDSBCCM SMS BROADCAST COMMAND Abis RSL MessageSCCP SIGNALLING CONNECTION CONTROL PART CCS7 User PartSDCCH STAND ALONE DEDICTED CONTROL CHANNEL Um ChannelSETUP SETUP DTAP MessageSPDACK STOP DTMF ACKNOWLEDGE DTAP MessageSPDTMF STOP DTMF DTAP MessageSREQ SERVICE REQUEST GMM (GPRS MM/SM) MessageSTDACK START DTMF ACKNOWLEDGE DTAP MessageSTDTMF START DTMF DTAP MessageSTRAC START TRACE Abis RSL Message


234 A30808-X3247-M41-3-7618


STRACACK START TRACE ACKNOWLEDGE Abis RSL Message

-T-

TALKDET TALKER DETECT MESSAGE DTAP MessageTALKIND TALKER INDICATION MESSAGE DTAP MessageTAREQ (SMLC->BSC) TIMING ADVANCE REQUEST BSSLAP MessageTARSP (BSC->SMLC) TIMING ADVANCE RESPONSE BSSLAP MessageTCH TRAFFIC CHANNEL Um ChannelTMEASRES TRACE MEASUREMENT RESULTS Abis RSL MessageTRCMD TMSI REALLOCATION COMMAND DTAP MessageTRCMP TMSI REALLOCATION COMPLETE DTAP Message

-U-

UA UNNUMBERED ACKNOWLEDGEMENT Um layer2 MessageUDT UNIT DATA SCCP MessageUI UNNUMBERED INFORMATION Um layer2 MessageUPCF UPLINK REQUEST CONFIRM MESSAGE BSSMAP MessageUPLACC UPLINK ACCESS DTAPUPLGRT UPLINK GRANT MESSAGE DTAPUPLINKBUSY UPLINK BUSY MESSAGE DTAPUPLINKFREE UPLINK FREE MESSAGE DTAPUPLREL UPLINK RELEASE DTAPUPRA UPLINK REQUEST ACKNOWLEDGE BSSMAP MessageUPRC UPLINK RELEASE COMMAND BSSMAP MessageUPRI UPLINK RELEASE INDICATION BSSMAP MessageUPRQ UPLINK REQUEST MESSAGE BSSMAP MessageUPSC UPLINK SEIZED COMMAND BSSMAP MessageUTRANCC UTRAN CLASSMARK CHANGE Abis RSL Message

-V-

VVAR VGCS ASSIGNMENT RESULT BSSMAP MessageVVRQ VGCS ASSIGNMENT REQUEST MESSAGE BSSMAP MessageVVS VGCS SETUP MESSAGE BSSMAP MessageVVSA VGCS SETUP ACKNOWLEDGE BSSMAP Message

-W-

WIHCI INTRACELL HANDOVER CONDITION INDICA-TION

Abis RSL Message


A30808-X3247-M41-3-7618 235

InformationSystem


3 AbbreviationsBSC Base Station Controller

BSIC Base Station Identity Code

BSSLAP BSS LCS Assistance Protocol

BSSMAP BSS Management Application Part

BSSMAP-LE BSSMAP LCS Extension

BTS Base Transceiver Station

CI Cell Identifier

CITASUP This BSC DB parameter represents the flagto enable the transmission of the Cell Iden-tifier (CI) and Timing Advance (TA) to MSC.

emLPP enhanced Multi-Level Procedure and Pre-emption

GPRS General Packet Radio Services

LCSNSSC This BSC DB enables LCS NSS centric so-lution. For LCS BSS centric solution it mustbe always set to FALSE.

MS Mobile Station

MSC Mobile-Services Switching Center

MT-LR Mobile Terminating Location Request

NI-LR Network Induced Location Request

SBS Siemens Base Station System

SETPAR SET PARAMETER

SIT10 Set Information Type 10

SMLC Serving Mobile Location Center

SSI10 Set System Info 10

TA Timing Advance

TERM TERMINATION

TERMREQ TERMINATION REQUEST

TMSI Temporary Mobile Subscriber Identity

UDTRQ Unit Data Request

URC Uplink Request Confirm

URLC Uplink Request CMD

USC Uplink Seized Command

236 A30808-X3247-M41-3-7618


Documents

l3 Message 2g