Escolar Documentos
Profissional Documentos
Cultura Documentos
Information 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 angeschlossenen Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen. In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponenten knnen auch eine hohe Betriebstemperatur aufweisen. Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder Sachschden fhren. 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 table A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a Class 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 is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful interference to radio communications. For system installations it is strictly required to choose all installation sites according to national and local requirements 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 electromagnetic field / 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 purposes could violate the rights of their owners.
A30808-X3247-M41-4-7618
Information System
Issue History
Issue 1 2 3 4 Date of Issue 01/2005 04/2005 07/2005 03/2006 Reason for Update First Edition for New Release BR 8.0 Second Edition for Release BR 8.0 Third Edition for Release BR 8.0 Fourth Edition for Release BR 8.0
A30808-X3247-M41-4-7618
Information System
A30808-X3247-M41-4-7618
Information System
This document consists of a total of 236 pages. All pages are issue 4.
Contents
Performance Measurement Message Flows . . . . . . . . . . . . . . . . . . . . . . . 11 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Call Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Successful Mobile Originating Call (MOC), FR Call . . . . . . . . . . . . . . . . . . 12 Successful Mobile Terminating Call (MTC), FR Call. . . . . . . . . . . . . . . . . . 15 Successful Mobile Originating Call (MOC) with Direct Traffic Channel Assignment, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1.2.1.4 Successful (MOC) Using Early Classmark Sending, FR Call . . . . . . . . . . 20 1.2.1.5 Successful Mobile Terminating Call (MTC), Using Early Classmark, Sending, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1.2.1.6 Successful Mobile Terminating Call (MTC) in busy mode, new waiting call (feature Call waiting) is accepted by called subscriber. . . . . . . . . . . . . . . 26 1.2.1.7 Unsuccessful Mobile Originating Call (MOC), Subscriber B Busy, FR Call 28 1.2.1.8 Unsuccessful Mobile Originating Call (MOC), No TCH Available, FR Call . 29 1.2.1.9 Successful Mobile Originated Call (MOC) in a Concentric Cell (inner area), FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 1.2.1.10 Successful Mobile Emergency Call (MEC), FR Call . . . . . . . . . . . . . . . . . . 32 1.2.2 Unsuccessful Assignment Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 1.2.2.1 Unsuccessful TCH Assignment Procedure with Reversion to SDCCH, FR Call 33 1.2.2.2 Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 < T_MSRFPCI), FR Call (T10 Expiry). . . . . . . . . . . . . . . . . . . 34 1.2.2.3 Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 > T_MSRFPCI), FR Call (T_MSRFPCI Expiry). . . . . . . . . . . . 35 1.2.2.4 Unsuccessful TCH Assignment Procedure LAPDm I-Frame with ASSIGNMENT COMMAND not acknowledged by MS (T200 Expiry), FR Call 36 1.2.3 Call Release Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 1.2.3.1 Normal Call Release (Originated by MS), FR Call . . . . . . . . . . . . . . . . . . . 37 1.2.3.2 Normal Call Release (Originated by Network), FR Call . . . . . . . . . . . . . . . 38 1.2.3.3 Abnormal Call Release Procedure; Call drop: BTS sends CONNECTION FAILURE INDICATION to the BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 1.2.3.4 Abnormal Call Release Procedure; Call drop: BTS sends ERROR INDICATION to the BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 1.2.3.5 Abnormal Call Release; BTS sends RELEASE INDICATION during a stable call phase to the BSC, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 1.2.4 Inter-Cell Handover, Intra-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 1.2.4.1 Successful Inter-Cell Handover, Intra-BSC, FR Call. . . . . . . . . . . . . . . . . . 45 1.2.4.2 Unsuccessful Inter-Cell Handover Attempt, Intra-BSC, No TCH Available in Target Cell, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 1.2.4.3 Unsuccessful Inter-Cell Handover, Intra-BSC, with Reversion to Old TCH (T3124 Expiry), FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 1.2.4.4 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS (Loss of HO CMD, T8<TTRAU), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 1 1.1 1.2 1.2.1 1.2.1.1 1.2.1.2 1.2.1.3
A30808-X3247-M41-4-7618
Information System
1.2.4.5 1.2.4.6
1.2.4.7 1.2.4.8 1.2.4.9 1.2.4.10 1.2.4.11 1.2.4.12 1.2.5 1.2.5.1 1.2.5.2 1.2.5.3 1.2.5.4 1.2.5.5 1.2.5.6
1.2.5.7 1.2.5.8 1.2.5.9 1.2.5.10 1.2.6 1.2.6.1 1.2.6.2 1.2.6.3 1.2.6.4 1.2.6.5 1.2.6.6 1.2.6.7 1.2.7 1.2.7.1
Unsuccessful Inter-Cell Handover, Intra-BSC with Loss of MS (Loss of HO CMD, T8>TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . 52 Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS, Handover Access Failure (No SABM after Transmission of PHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Successful Inter-Cell Handover (Intra-BSC) between Colocated Concentric Cells, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Successful Inter-Cell Handover, Intra-BTSE, Between Synchronized Cells, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Successful Inter-Cell Handover, Intra-BSC, MSC Controlled, FR Call . . . . 60 Successful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC . . . . . . . . . . . 62 Unsuccessful SDCCH-SDCCH Inter-Cell Handover Attempt, Intra-BSC, No SDCCH Available in Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Inter-Cell Handover, Inter-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Successful Inter-Cell Handover, Inter-BSC, FR Call . . . . . . . . . . . . . . . . . . 67 Unsuccsessful Inter-Cell Handover, Inter-BSC, No TCH Available in Target Cell, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Unsuccessful Inter-Cell Handover, Inter-BSC, with Reversion to Old TCH, FR Call (T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8<Trr7), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8>Trr7), FR Call (Trr7 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Unsuccessful Inter-Cell Handover, Inter-BSC, with Loss of MS, Handover Access Failure (No SABM received after Transmission) of PHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Successful Inter-Cell Handover, Inter-BSC, No TCH Available in First (external) Cell, Second Target Cell Belongs to Originating BSC, FR Call . . . . . . 79 Successful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC . . . . . . . . . . . 81 Unsuccsessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC, No SDCCH Available in Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8<Trr7, T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . 84 Intra-Cell Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Successful Intra-Cell Handover, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Unsuccessful Intra-Cell Handover Due to Quality, No TCH Available, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Unsuccessful Intra-Cell Handover Due to Quality with Reversion to Old TCH, FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD, T10 < TTRAU), FR Call (T10 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD, T10>TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Successful Intra-Cell Handover Due to Quality, MSC Controlled, FR Call . 95 Successful SDCCH-SDCCH Intra-Cell Handover . . . . . . . . . . . . . . . . . . . . 97 Directed Retry, Intra-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Successful Directed Retry, Intra-BSC, FR Call . . . . . . . . . . . . . . . . . . . . . . 99
A30808-X3247-M41-4-7618
Information System
1.2.7.2 1.2.7.3 1.2.7.4 1.2.7.5 1.2.7.6 1.2.8 1.2.8.1 1.2.8.2 1.2.8.3 1.2.8.4 1.2.8.5 1.2.9 1.2.9.1 1.2.9.2 1.2.9.3 1.2.10 1.2.10.1 1.2.10.2
1.2.11 1.2.11.1
1.2.11.2
1.2.11.3
1.2.11.4
1.2.11.5
Unsuccessful Directed Retry, Intra-BSC, No Target Cell Available, FR Call . 101 Unsuccessful Directed Retry, Intra-BSC, 1 Target Cell Available, Target Cell Congested, FR Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH, FR Call (T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 < TTRAU), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 > TTRAU), FR Call (TTRAU Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Directed Retry, Inter-BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Successful Directed Retry, Inter-BSC, FR Call . . . . . . . . . . . . . . . . . . . . . 109 Unsuccessful Directed Retry, Inter-BSC, FR Call, no Radio Resource available in Target Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Unsuccessful Directed Retry, Inter-BSC, with Reversion to SDCCH, FR Call (T3124 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Unsuccessful Derected Entry, Inter-BSC, with Loss of MS (Loss of HO CMD, T8 < Trr7), FR Call (T8 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Unsuccessful Directed Retry, Inter-BSC, with Loss of MS (Loss of HO CMD, T8 > Trr7), FR Call (Trr7 Expiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Forced Handover Due to O & M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Successful Forced Handover Due to O & M . . . . . . . . . . . . . . . . . . . . . . . 120 Successful Forced Handover Due to O & M, Inter-BSC, FR Call . . . . . . . 122 Successful Forced Intra-Cell Handover Due to O & M, FR Call . . . . . . . . 124 Handover due to BSS Resource Management Criteria (Traffic Handover) 125 Successful Handover due to BSS Resource Management Criteria (Traffic Handover), FR Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Unsuccessful Inter-Cell Handover due to BSS Resource Management Criteria (Traffic Handover), traffic load in Target Cell exceeds the threshold TRFLTH 128 Queuing & Preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Queuing: Queued Assignment Request for FR TCH Is Served Before T11PUB or T11WPS Expiry, Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call . . . . . 130 Queuing: Queued Assignment Request for FR TCH is Discarded from the Queue Before T11PUB or T11WPS Expiry Due to an Incoming FR Assignment Request with Higher Priority Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Queuing: Queued Assignment Request for FR TCH Is Discarded from Queue Due to T11PUB or T11WPS Expiry, Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call . 134 Queuing: Queued Handover Request for FR TCH Is Served Before TQHOPUB or TQHOWPS Expiry, Preemption Disabled or Not Allowed for the Requesting Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Queuing: Queued Handover Request for FR TCH Is Discarded from the Queue Before TQHOPUB or TQHOWPS Expiry Due to an Incoming FR Call with Higher Priority, Preemption Disabled or Not Allowed for the Requesting Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
A30808-X3247-M41-4-7618
Information System
1.2.11.6 Queuing: Queued Handover Request for FR TCH Is Discarded from the Queue Due to TQHOPUB or TQHOWPS Expiry, Preemption Disabled or Not Allowed for the Requesting Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 1.2.11.7 Preemption: Successful Forced Inter-Cell Handover Due to Preemption, Preempted Assignment Request and Preempting Call Are Both FR. . . . . . . . 140 1.2.11.8 Preemption: Forced Release of Preempted Call Due to Lack of Target Cell for Forced Inter-Cell Handover Procedure, Preempted and Preempting Call Are Both FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 1.2.11.9 Preemption: Successful Forced Inter-BSC Handover Due to Preemption, Preempting Handover Request and Preempted Call Are Both FR, Originating BSC of the Preempting Handover Request and Target BSC for the Forced Handover Are the Same. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 1.2.12 HSCSD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 1.2.12.1 Successful HSCSD Call, Mobile Originating, 3 TCHs Used . . . . . . . . . . . 145 1.2.12.2 Successful Inter-cell Handover of an HSCSD Call (3 TCHs Used), Intra-BSC 148 1.2.12.3 Forced Intra-cell Handover During HSCSD Assignment Procedure . . . . . 151 1.2.13 Signalling Transactions without TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 1.2.13.1 Successful Location Update (Phase 2 MS) . . . . . . . . . . . . . . . . . . . . . . . . 153 1.2.13.2 Successful Location Update (2G/3G (GSM/UMTS) Multirat MS) . . . . . . . 155 1.2.13.3 Successful IMSI Detach (Phase 2 MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 1.2.13.4 Successful Supplementary Service (SS) Management Procedure via Subscriber-Controlled Input (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 1.2.13.5 Successful USSD (Unstructured Supplementary Service Data) Management Procedure via (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 1.2.13.6 Unsuccessful Immediate Assignment Procedure, No SDCCH Available. . 162 1.2.13.7 Unsuccessful Immediate Assignment Procedure with DELETE INDICATION (no AGCH available or AGCH message timeout) . . . . . . . . . . . . . . . . . . . 163 1.2.13.8 Unsuccessful Immediate Assignment Procedure, assigned SDCCH is not seized by the MS (Phantom RACH Scenario) . . . . . . . . . . . . . . . . . . . . . . 164 1.2.13.9 BTS Discards Invalid RACH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 1.2.13.10Immediate Assignment Procedure for Abis Link Configured via Satellite Link. 166 1.2.13.11Paging Overload - BTS discards a PAGING REQUEST Message . . . . . . 167 1.2.14 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 1.2.14.1 Successful SMS Mobile Originating in Idle Mode (Phase 2 MS) . . . . . . . . 168 1.2.14.2 Successful SMS Mobile Terminating in Idle Mode (Phase 2 MS) . . . . . . . 170 1.2.14.3 Successful SMS Mobile Originating in Connected Mode (FR Call Ongoing). . 172 1.2.14.4 Successful SMS Mobile Terminating in Connected Mode . . . . . . . . . . . . . 173 1.2.15 Advanced Speech Call Items (ASCI) Procedures . . . . . . . . . . . . . . . . . . . 174 1.2.15.1 VBS/VGCS Setup Initiated by fixed Dispatcher and Release . . . . . . . . . . 174 1.2.15.2 Succesful Uplink Allocation Procedure (1) . . . . . . . . . . . . . . . . . . . . . . . . . 176 1.2.15.3 FREE Uplink Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 1.2.15.4 VGCS Setup initiated by Service Subscriber and Release . . . . . . . . . . . . 179 1.2.15.5 VGCS SETUP initiated by Service Subscriber (FAST CALL SETUP) . . . . 182 1.2.15.6 MTC During Ongoing VBS/VGCS Connection. . . . . . . . . . . . . . . . . . . . . . 183 1.2.15.7 VBS/VGCS Call during Ongoing Speech Call . . . . . . . . . . . . . . . . . . . . . . 184 1.2.16 Inter System Handover (2G <--> 3G), circuit switched (CS) . . . . . . . . . . . 185
A30808-X3247-M41-4-7618
Information System
1.2.16.1 Successful Inter System Handover (2G --> 3G) . . . . . . . . . . . . . . . . . . . 185 1.2.16.2 Unsuccessful Inter System Handover (2G --> 3G), loss of MS (loss of HOCMD), T3121 expiry . . . . . . . . . . . . . . . . . . . . . . . 187 1.2.16.3 Unsuccessful Inter System Handover (2G --> 3G), No TCH available in Target UMTS Cell (3G) . . . . . . . . . . . . . . . . . . . . . . 189 1.2.16.4 Unsuccessful Inter System Handover (2G --> 3G), Reversion to old TCH, T3124 expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 1.2.16.5 Successful Inter System Handover (3G --> 2G) . . . . . . . . . . . . . . . . . . . 191 1.2.16.6 Unsuccessful Inter System Handover (3G --> 2G), No TCH available in Target GSM Cell (2G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 1.2.17 Other Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 1.2.17.1 Idle Traffic Channel Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 1.2.17.2 Uplink and Downlink Measurement Reports on Abis . . . . . . . . . . . . . . . . 195 1.2.17.3 IMSI Trace Invocation for Normal Call Setup . . . . . . . . . . . . . . . . . . . . . . 196 1.2.17.4 IMSI Trace Invocation for Incoming Inter-BSC Handover . . . . . . . . . . . . . 197 1.3 GPRS Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 1.3.1 GPRS Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 1.3.1.1 GPRS Mobility Management: Attach Procedure. . . . . . . . . . . . . . . . . . . . 198 1.3.1.2 GPRS Mobility Management: Detach Procedure . . . . . . . . . . . . . . . . . . . 199 1.3.1.3 GPRS Session Management: Activate PDP Context . . . . . . . . . . . . . . . . 200 1.3.1.4 GPRS Session Management: Deactivate PDP Context . . . . . . . . . . . . . . 201 1.3.1.5 GPRS: Paging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 1.3.1.6 GPRS Mobility Management: Routing Area Update . . . . . . . . . . . . . . . . . 202 1.3.1.7 GPRS Mobility Management: Cell Update . . . . . . . . . . . . . . . . . . . . . . . . 204 1.3.1.8 GPRS: Suspend / Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 1.3.2 Inter System Cell Reselection Procedure (2G <--> 3G), packet oriented (PO), intra SGSN inter system change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 1.3.2.1 Successful Inter System Cell Reselection Procedure (2G --> 3G) . . . . . . 207 1.3.2.2 Successful Inter System Cell Reselection Procedure (3G --> 2G) . . . . . . 210 1.3.3 RLC/MAC Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 1.3.3.1 Uplink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 1.3.3.2 Downlink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 1.3.3.3 Concurrent UL TBF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 1.3.3.4 Concurrent DL TBF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 2 3 Counter / Message Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
A30808-X3247-M41-4-7618
Information System
10
A30808-X3247-M41-4-7618
Information System
Note: The message flows have to be considered as typical examples for the affected signalling transactions. Depending on specific settings in the involved network elements (MSC, BSC), flow traces taken from real live networks can deviate from the shown message flows (especially for the optional sub-procedures Authentication, Ciphering, Early Classmark Sending and TMSI Reallocation). The messages between the network elements (MS, BTS, BSC and MSC) are abbreviated 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 defined by GSM and the Siemens Abis specifications please refer to Chapter 2 Abbreviations. In addition to the messages, the implemented SBS performance measurement counters are embedded into the message flows in such a way that the association of the counters to their triggering events becomes clear. As a general rule, the appearance of a counter within a message flow means that its value is increased by 1. Deviations from this rule are explicitely mentioned in the message flows. To indicate also the subcounters of the specific measurements, the following method is used: <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:SBS Counter.
Note: If not otherwise defined the blue colour generally indicates the events on the handover 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 preempting call. In 1.2.5.7 the red colour indicates the BSC serving the first (really external) target cell in the target cell list of the HANDOVER REQUIRED message. SMLC-Specific Message Flows: In order to guarantee an SBS release-independent documenation delivery, the SMLCrelated message flows are provided in a separate documentation set. The manual PM:SBS Message Flows is intended for the SBS-specific message flows, whereas the manual PM:SMLC Message Flows is intended for the SMLC-specific message flows. Both manuals may be used together, if applicable.
A30808-X3247-M41-4-7618
11
Information System
1.2
1.2.1 1.2.1.1
Message Flows
Call Setup Procedures Successful Mobile Originating Call (MOC), FR Call
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE NACSUCPR (3.) ATIMASCA (4.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
UI (IMASS)
AGCH
IACMD (IMASS) Stop T3101 TACCBPRO (2.) SUIMASCA (4.) NACSUCPR (2.)
NTDMAGCH (1.)
SABM (CMSREQ)
SDCCH
UA
SDCCH
CR (CL3I; CMSREQ)
DATRQ (AUTREQ)
CC (AUTREQ)
I (AUTREP)
SDCCH
I (CIMCMD) I (CIMCMP)
SDCCH
DATIN (CIMCMP)
DT1 (CICMP)
12
A30808-X3247-M41-4-7618
Information System
MS
SETUP
SDCCH
BTS
DATIN (SETUP) DATRQ (CPROC)
SDCCH
BSC
MSC
DT1 (SETUP) DT1 (CPROC) DT1 (ASS REQ) ATTCHSEI (1.) TASSATT (2.) If last TCH start AALTCHTI (1.) CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
I (CPROC)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] PHCRQ PHCCN
CHNAV (TCH) Start TTRAU Start T_MSRFPCI DATRQ (ASS CMD) I (ASS CMD) SABM
FACCH
CHNAK
Start T10
ESTIN UA
FACCH
I (ASS CMP)
FACCH
TNTCHCL (1.) SUCTCHSE (1.) TASSSUCC (2.) DATIN (ASS CMP) Stop T10 DT1 (ASS COM) MRPCI
Stop T_MSRFPCI RELRQ RELCN RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-)
A30808-X3247-M41-4-7618
13
Information System
MS
BTS
BSC
MSC
called party is reachable and idle (ringing) DT1 (ALERT)
I (ALERT)
FACCH
DATRQ (ALERT) called party has accepted the call DT1 (CONNECT) DATRQ (CONNECT)
FACCH
I (CONNECT) I (CONACK)
FACCH
DATIN (CONACK)
DT1 (CONACK)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
14
A30808-X3247-M41-4-7618
Information System
1.2.1.2
MS
UI (PAGREQ)
BTS
PGCMD
PCH
BSC
UDT (PAGIN)
TACCBPRO (1.)
MSC
CHNREQ
RACH
NTDMPCH (1.)
CHNRD
NATTSDPE NACSUCPR (1.), (3.) ATIMASCA (1.) If last SDCCH start ASDCALTI CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
UI (IMASS)
AGCH
IACMD (IMASS)
Start T3101 TACCBPRO (2.) SUIMASCA (1.) NACSUCPR (2.)
NTDMAGCH (1.)
SABM (PAGRES)
SDCCH
ESTIN (PAGRES)
Stop T3101
UA
SDCCH
(CL3L; PAGRES)
MRPCI
Stop T_MSRFPCI
I (TRCMD)
SDCCH
I SETUP I (TRCMP)
SDCCH
I (CCONF)
SDCCH
A30808-X3247-M41-4-7618
15
Information System
MS
BTS
BSC
DT1 (ASREQ)
MSC
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] PHCRQ PHCCN
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]t
CHNAV (TCH) Start TTRAU Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (**) I (ASS CMD)
SDCCH
CHNAK
Start T10
SABM
FACCH
ESTIN
FACCH
UA I (ASS CMP) TNTCHCL (1.) SUCTCHSE (1.) TASSSUCC (2.) DATIN (ASS CMP) Stop T10 MRPCI Stop T_MSRFPCI RELRQ RELCN RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-) DT1 (ASS COM)
FACCH
16
A30808-X3247-M41-4-7618
Information System
MS
called MS is ready (ringing) I (ALERT)
FACCH
BTS
BSC
MSC
DATIN (ALERT)
DT1 (ALERT)
DATIN (CONNECT)
I (CONACK)
FACCH
DATRQ (CONACK)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
A30808-X3247-M41-4-7618
17
Information System
1.2.1.3
Successful Mobile Originating Call (MOC) with Direct Traffic Channel Assignment, FR Call
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
ATTCHSEI (1.) ATIMASCA (4.) NASCUCPR (3.) If last TCH start AALTCHTI (1.) CHNAV (TCH)
MEBUSTCH-1 MEBUSTLY
Start T3101 TACCBPRO (2.) SUIMASCA (4.) NACSUCPR (2.) ESTIN (CMSREQ) Stop T3101
NTDMAGCH (1.)
SABM (CMSREQ)
FACCH
UA
Stop T_MSRFPCI
I (CPROC)
FACCH
18
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
DT1 (ASS REQ) TASSATT (2.) MOMRQ MOMAK MBTCHCHT CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one also CHALNHLY [2 or 3] (***) DATIN (CHMMACK) DT1 (ASS COM) TASSSUCC (2.) DT1 (ALERT)
MSC
I (CHMM)
FACCH
DATRQ (CHMM)
I (CHMMACK)
FACCH
I (ALERT)
FACCH
DATRQ (ALERT)
called party has accepted the call DATRQ (CONNECT) DT1 (CONNECT)
I (CONNECT) I (CONACK)
FACCH FACCH
DATIN (CONACK)
DT1 (CONACK)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND. In case of direct TCH assignment the timer T10 is not used. Two not-administrable system internal timers are used, one for the control of the MOMRQ procedure, one for the control of the CHMM procedure. In case of expiry of one of these timers, the BSC sends an ASS FAI with cause equipment failure to the MSC.
(***)
A30808-X3247-M41-4-7618
19
Information System
1.2.1.4
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
NATTSDPE NACSUCPR (3.) ATIMASCA (4.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI IACMD (IMASS) UI (IMASS)
AGCH
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
ESTIN (CMSREQ) Stop T3101 NSUCCHPC (4.) NASUSDPE MRPCI CR (CL3I; CMSREQ)
I (CIMCMD)
SDCCH
ENCRY (CIMCMD)
CC (CICMD)
I (CLAMCH)
SDCCH
I (CIMCMP)
SDCCH
I (TRCMD) I (SETUP)
SDCCH
DATIN (SETUP)
I (CPROC)
SDCCH
DATRQ (CPROC)
20
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
DT1 (ASREQ)
MSC
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] PHCRQ PHCCN
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAV (TCH) Start TTRAU Start T_MSRFPCI DATRQ (ASS CMD) I (ASS CMD) I (TRCMP)
SDCCH
CHNAK
Start T10
DT1 (TRCMP)
SABM
FACCH
UA I (ASS CMP)
FACCH
TNTCHCL (1.) SUCTCHSE (1.) TASSSUCC (2.) DATIN (ASS CMP) Stop T10 MRPCI DT1 (ASS COM)
Stop T_MSRFPCI RELRQ RELCN RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-)
A30808-X3247-M41-4-7618
21
Information System
MS
BTS
BSC
MSC
called party is reachable and idle (ringing) DT1 (ALERT)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
22
A30808-X3247-M41-4-7618
Information System
1.2.1.5
Successful Mobile Terminating Call (MTC), Using Early Classmark, Sending, FR Call
MS
UI (PAGREQ)
BTS
PGCMD
PCH
BSC
UDT (PAGIN)
TACCBPRO (1.)
MSC
CHNREQ
RACH
CHNRD
NATTSDPE NACSUCPR (1.), (3.) ATIMASCA (1.) If last SDCCH start ASDCALTI CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
UI (IMASS)
AGCH
IACMD (IMASS)
Start T3101 TACCBPRO (2.) SUIMASCA (1.) NACSUCPR (2.)
NTDMAGCH (1.)
SABM (PAGRES)
SDCCH
ESTIN (PAGRES)
Stop T3101
UA
SDCCH
CR (CL3I; PAGRES)
I (CIMCMD) I (CLAMCH)
SDCCH SDCCH
CC (CIMCMD)
DT1 (CLUPD)
I (CIMCMP)
SDCCH
DATIN (CIMCMP)
DT1 (CICMP)
A30808-X3247-M41-4-7618
23
Information System
MS
BTS
BSC
MSC
I (TRCMD)
SDCCH
I SETUP
SDCCH
I (TRCMP)
SDCCH SDCCH
I CCONF
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
PHCRQ PHCCN CHNAV (TCH) Start TTRAU Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (**) I (ASS CMD)
SDCCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAK
Start T10
SABM
FACCH
ESTIN
FACCH
UA I (ASS CMP) TNTCHCL (1.) SUCTCHSE (1.) TASSSUCC (2.) DATIN (ASS CMP) Stop T10 MRPCI Stop T_MSRFPCI DT1 (ASS COM)
FACCH
24
A30808-X3247-M41-4-7618
Information System
MS
BTS
RELRQ RELCN RCHRL (SDCCH) RCHRA
BSC
MSC
DT1 (ALERT)
I (ALERT)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
A30808-X3247-M41-4-7618
25
Information System
1.2.1.6
Successful Mobile Terminating Call (MTC) in busy mode, new waiting call (feature Call waiting) is accepted by called subscriber
MS
BTS
BSC
MSC
called party is reachable and idle (ringing) DT1 (ALERT)
I (ALERT)
FACCH
DATRQ (ALERT) called party has accepted the call DATRQ (CONNECT)
FACCH
DT1 (CONNECT)
I (CONNECT) I (CONACK)
FACCH
DATIN (CONACK)
DT1 (CONACK)
DT1 (SETUP)*
I (CCONF)*
SDCCH (cause: user busy
I (ALERT)*
FACCH
DATRQ (ALERT)*
called subscriber accepts new cell and releases the old one by the pressing the appropriate keys on the MS I (STDTMF)
FACCH
I (STDACK)
FACCH
I (SPDTMF)
FACCH
I (SPDACK)
FACCH
DATIN (SPDACK)
26
A30808-X3247-M41-4-7618
Information System
MS
I (DISC)
FACCH (cause: normal call clearing)
BTS
DATIN (DISC)
BSC
DT1 (DISC) DT1 (RELEAS)
(cause: normal call clearing)
MSC
I (RELCMP)
FACCH
FACCH
DATIN (CONNECT)*
(*)
A30808-X3247-M41-4-7618
27
Information System
1.2.1.7
MS
BTS
BSC
MSC
DATIN (ASS CMP) Stop T10 SUCTCHSE (1.) TASSSUCC (2.) DT1 (ASS COM)
RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) DATRQ (DISC)
SDCCH
DT1 (DISC)
(cause: user busy)
I (DISC)
28
A30808-X3247-M41-4-7618
Information System
1.2.1.8
MS
BTS
BSC
MSC
SDCCH
SDCCH
DT1 (DISC)
DATRQ (DISC)
A30808-X3247-M41-4-7618
29
Information System
1.2.1.9
Successful Mobile Originated Call (MOC) in a Concentric Cell (inner area), FR Call
MS
BTS
BSC
MSC
DATIN (SETUP)
I (CPROC)
SDCCH
DATRQ (CPROC)
PAREQ
(preferred area type: inner area)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6]
PAREA ATTCHSEI (1.) If last TCH start AALTCHTI (1.) MTCHBUTI (1.) (start)
Start TTRAU CHNAK Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (**) I (ASS CMD)
SDCCH
Start T10
SABM
FACCH
ESTIN UA
FACCH
I (ASS CMP)
FACCH
TNTCHCL (1.) SUCTCHSE (1.) TASSSUCC (2.) Stop T10 DT1 (ASS COM)
30
A30808-X3247-M41-4-7618
Information System
MS
BTS
MRPCI Stop T_MSRFPCI RELRQ RELCN RCHRL (SDCCH) RCHRA
BSC
MSC
DATRQ (ALERT)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
A30808-X3247-M41-4-7618
31
Information System
1.2.1.10
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
NATTSDPE NACSUCPR (3.) ATIMASCA (2.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI UI (IMASS)
AGCH
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
IACMD (IMASS) Start T3101 TACCBPRO () (2.) SUIMASCA (2.) NACSUCPR (2.)
NTDMAGCH (1.)
SABM (CMSREQ)
SDCCH (CM service type: emergency call establishment)
UA
SDCCH
Stop T_MSRFPCI
DATIN (EMSETUP)
I (CPROC)
SDCCH
DATRQ (CPROC)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
32
A30808-X3247-M41-4-7618
Information System
1.2.2 1.2.2.1
Unsuccessful Assignment Procedures Unsuccessful TCH Assignment Procedure with Reversion to SDCCH, FR Call
MS
BTS
Call setup ...
BSC
MSC
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
DT1 (ASS REQ) ATTCHSEI (1.) TASSATT (2.) If last TCH start AALTCHTI PHCRQ PHCCN CHNAV (TCH) CHALNHLYCHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAK
Start T10
SABM
FACCH
SABM
FACCH
SABM
FACCH
.... SABM
SDCCH
UA I (ASS FAIL)
SDCCH (Cause: protocol error unspecified)
DATIN (ASS FAIL) Stop T10 TASSFAIL (7.) DT1 (ASS FAIL)
(cause: radio interface failure, reversion to old channel)
I (DISC)
SDCCH
DATRQ (DISC)
DT1 (DISC)
(cause: normal, unspecified)
A30808-X3247-M41-4-7618
33
Information System
1.2.2.2
Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 < T_MSRFPCI), FR Call (T10 Expiry)
MS
BTS
Call setup ...
BSC
MSC
DT1 (ASS REQ) MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] ATTCHSEI (1.) TASSATT (2.) If last TCH start AALTCHTI PHCRQ PHCCN MTCHBUTI (1.) (start) CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAV (TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (ASS CMD) I (ASS CMD) ASS CMD is lost ... Expiry T10 TASSFAIL (6.) DT1 (CL CMD)
(cause: call control)
Start T10
NRCLRCHD [14]
34
A30808-X3247-M41-4-7618
Information System
1.2.2.3
Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 > T_MSRFPCI), FR Call (T_MSRFPCI Expiry)
MS
BTS
Call setup ...
BSC
MSC
DT1 (ASS REQ) ATTCHSEI (1.) TASSATT (2.) If last TCH start AALTCHTI PHCRQ PHCCN MTCHBUTI (1.) (start)
CHNAV (TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (ASS CMD) I (ASS CMD) ASS CMD is lost ... Stop TTRAU (**)
SDCCH
Start T10
Expiry T_MSRFPCI
NRCLRCMD [1]
A30808-X3247-M41-4-7618
35
Information System
1.2.2.4
Unsuccessful TCH Assignment Procedure LAPDm I-Frame with ASSIGNMENT COMMAND not acknowledged by MS (T200 Expiry), FR Call
MS
BTS
Call setup ...
BSC
MSC
DT1 (ASS REQ) ATTCHSEI (1.) TASSATT (2.) If last TCH start AALTCHTI (1.) MTCHBUTI (1.) (start)
PHCRQ PHCCN
CHNAV (TCH) Start TTRAU Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (**) I (ASS CMD) I (ASS CMD) I (ASS CMD)
SDCCH SDCCH SDCCH T200 T200 T200 expired N200+1 times))
CHNAK
Start T10
I (ASS CMD)
SDCCH T200
ERRIN
(cause: timer T200 expired N200+1 times))
NRCLRREQ (1S)
NRCLRCMD (13)
36
A30808-X3247-M41-4-7618
Information System
1.2.3 1.2.3.1
MS
BTS
BSC
MSC
DATIN (DISC)
DT1 (DISC)
DT1 (RELEAS)
(cause: normal call clearing)
I (RELCMP)
FACCH
UA Stop T3110
Stop T3109 Start T3111 RLC RCHRL (TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS Expiry T3111
A30808-X3247-M41-4-7618
37
Information System
1.2.3.2
MS
BTS
BSC
MSC
DT1 (DISC)
(cause: normal call clearing)
I (DISC)
I (RELEAS)
FACCH (cause: normal call clearing)
DATRQ (RELEAS)
I (RELCMP)
FACCH
NRCLRCMD (2.)
RLSD
(cause: end user originated)
UA Stop T3110
FACCH
38
A30808-X3247-M41-4-7618
Information System
1.2.3.3
Abnormal Call Release Procedure; Call drop: BTS sends CONNECTION FAILURE INDICATION to the BSC
MS
BTS
BSC
MSC
or...
TTRAU expiry*** or TSYNC/TSYNCDL**** expiry
CONFL
(cause: remote transcoder failure)
or...
T_MSRFPCI expiry*****
CONFL
(cause: T_MSRFPCI expired)
A30808-X3247-M41-4-7618
39
Information System
MS
BTS
or...
MS-BTS distance exceeds the threshold EXCDIST
BSC
MSC
CONFL
(cause: distance limit exceeded******)
DT1 (CL CMD) B RELRQ RELCN RCHRL (New TCH) or SDCCH Reset T_MSRFPCI RCHRA If TCH MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS If SDCCH MBUSYSDC ASDCALTI (stop, if previously started) NRCLRCMD (1.) DT1 (CL CMP)
40
A30808-X3247-M41-4-7618
Information System
(*)
If the CONNECTION FAILURE INDICATION is received a TCH, NRFLTCH is triggered; if it is received for 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 BTS cannot 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 purpose is to observe the receipt of TRAU frames from the TRAU after the activation of the TCH, i.e. it is stopped when TRAU frames are received. TSYNC is started in the BTS when the BTS does not receive valid TRAU frames for an activated TCH anymore. Its purpose is to observe the re-appearance of TRAU frames from the TRAU, i.e. it is stopped again when TRAU frames are received. TSYNC is used for FR, HR and EFR speech calls and for standard dataservices (up to 9,6 kbit/s). For AMR calls and 14,4 kbit/s dataservices TSYNC is replaced by TSYNCDL.
(**)
(***)
(****)
(*****) T_MSRFPCI is started in the BTS on receipt of the CHANNEL ACTIVATION ACKNOWLEDGE message for a TCH. Its purpose is to observe the receipt of the MPRCI message, i.e. it is stopped when the MRPCI message is received. The BSC sends this message when the MS has successfully sent the first 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) and HANDOVER 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 message failure but distance. Consequently also the corresponding NRCLRREQ subcounter (6.) is triggered instead of subcounter (3.). A If the CONN_FAIL is received on TCH, the corresponding subcounter is NRCLRREQ 3 or 6 (see note above); on the contrary if it is received on SDCCH, the corresponding subcounter is NRCLRREQ 21 or 24. NRCLRCMD (1) if CONN_FAIL is received on TCH NRCLRCMD (13) if CONN_FAIL is received on SDCCH
A30808-X3247-M41-4-7618
41
Information System
1.2.3.4
Abnormal Call Release Procedure; Call drop: BTS sends ERROR INDICATION to the BSC
MS
BTS
BSC
MSC
RELIN**
or...
MS has sent a Um layer 2 (LAPDm) message DM (Mode) to the BTS while the BTS-MS communication is in multiple frame stablished state
DM
FACCH or SDCCH
ERRIN
(cause: unsolicited DM response, multiple frame established state)
RELIN**
42
A30808-X3247-M41-4-7618
Information System
MS
BTS
or...
BSC
MSC
BTS has detected irregularities in the Um layer 2 (LAPDm) flow control functions (wrong message sequence) useds in acknowledged mode ERRIN
(cause: sequence error)
NRFLTCH (3.) or * NRFLSDCC (3.) RELIN** DT1 (CL REQ) 3 if TCH 21 if SDCCH NRCLRREQ (3.)
(cause: radio interface message failure)
DT1 (CL CMD) NRCLRCMD (1.) RCHRL (New TCH) Reset T_MSRFPCI RCHRA If TCH MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS If SDCCH MBUSYSDC ASDCALTI (stop, if previously started) 1 if TCH 13 if SDCCH DT1 (CL CMP)
(*)
If the ERROR INDICATION is received for a TCH, NRFLTCH is triggered; if it is received for a SDCCH, NRFLSDCC is triggered. The RELEASE INDICATION is always sent directly after the ERROR INDICATION to indicate that the layer 2 context on the Um interface has already been cleared by the BTS.
(**)
A30808-X3247-M41-4-7618
43
Information System
1.2.3.5
Abnormal Call Release; BTS sends RELEASE INDICATION during a stable call phase to the BSC, FR Call
MS
BTS
BSC
MSC
DT1 (CL CMD) NRCLRCMD (1.) RELRQ RELCN RCHRL (New TCH) Reset T_MSRFPCI RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
44
A30808-X3247-M41-4-7618
Information System
1.2.4 1.2.4.1
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) BWHCI
(with HO cause)
UI (MEAS REP)
SACCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
Start THORQST
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD) MTCHBUTI (1.) (start)
I (HO CMD)
FACCH
HO ACCESS (***)
FACCH
Start T3124
FACCH
Stop T3105 UA
FACCH
A30808-X3247-M41-4-7618
45
Information System
MS
BTSold
I (HO CMP)
BTSnew
DATIN (HO CMP)
BSC
MSC
FACCH
Stop T8 SINTHINT (*) SININIRH (*) SOUINIRH (*) SINHOBSC (*) MRPCI DT1 (HOPER) Stop T_MSRFPCI RELRQ RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS (with HO cause)
SUCTCHSE (1.)
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message. HO ACCESS is transmitted exactly 4 times, the MS does not wait for any response from the BTS but directly sets up the layer 2 connection (using the SABM) after the last HO ACCESS.
(***)
46
A30808-X3247-M41-4-7618
Information System
1.2.4.2
Unsuccessful Inter-Cell Handover Attempt, Intra-BSC, No TCH Available in Target Cell, FR Call
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
. . . . .
.
(with HO cause)
. . . . .
.
Expiry THORQST
BWHCI
(with HO cause)
(***)
A30808-X3247-M41-4-7618
47
Information System
1.2.4.3
Unsuccessful Inter-Cell Handover, Intra-BSC, with Reversion to Old TCH (T3124 Expiry), FR Call
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
HO ACCESS
FACCH
HO ACCESS
Expiry T3124
FACCH
I (HO FAIL)
FACCH
48
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
MSC
RCHRL (New TCH) RCHRA Reset TTRAU Reset T_MSRFPCI MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. 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 after transmission of the HANDOVER ACCESS on the target channel. The MS can still return to the old channel after it has received the PHYSICAL INFORMATION from the BTS. This happens when the layer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmission of the SABM on the target channel.
(****)
A30808-X3247-M41-4-7618
49
Information System
1.2.4.4
Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS (Loss of HO CMD, T8<TTRAU), FR Call (T8 Expiry)
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
ATTCHSEI (1.) ATINHIRC (*) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
I (HO CMD)
FACCH
Start T8 AININIRH (*) AOUINIRH (*) Expiry T8 UNIHIRLC DT1 (CL REQ) NRCLRREQ (3.)
(cause: radio interface message failure)
DT1 (CL CMD) NRCLRCMD (1.) RELRQ RELCN RCHRL (Old TCH) RCHRA DT1 (CL CMP)
50
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
RLSD RLC
MSC
RCHRL (New TCH) RCHRA Reset TTRAU Reset T_MSRFPCI MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop)
(*) A
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. Note: These subcounters are triggered both for the new and old channel's release.
A30808-X3247-M41-4-7618
51
Information System
1.2.4.5
Unsuccessful Inter-Cell Handover, Intra-BSC with Loss of MS (Loss of HO CMD, T8>TTRAU), FR Call (TTRAU Expiry)
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
I (HO CMD)
FACCH
Expiry TTRAU
52
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
RCHRL (New TCH) A
MSC
RELRQ RLC
(*) A
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. Note: These subcounters are triggered both for the new and old channel's release.
A30808-X3247-M41-4-7618
53
Information System
1.2.4.6
Unsuccessful Inter-Cell Handover, Intra-BSC, with Loss of MS, Handover Access Failure (No SABM after Transmission of PHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU)
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
Start THORQST MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
ATTCHSEI (1.) ATINHIRC (*) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
I (HO CMD)
FACCH
HO ACCESS
FACCH
Start T3124
MS does not react to PHYS INFO, no SABM is received at the BTS. UI (PHYS INFO) MS does not react to PHYS INFO, no SABM is received at the BTS.
Start T3105
Expiry T3105
FACCH
Start T3105
54
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
MSC
UI (PHYS INFO) MS does not react to PHYS INFO, no SABM is received at the BTS.
Expiry T3105
FACCH
Start T3105
NRCLRREQ (3.)
DT1 (CL CMD) NRCLRCMD (1.) RCHRL (New TCH) RCHRA DT1 (CL CMP)
RLSD RELRQ RLC RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop) A MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
A (*)
Note: These subcounters are triggered both for the new and old channel's release. Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION.
A30808-X3247-M41-4-7618
55
Information System
1.2.4.7
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
PAREQ PAREA CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8 HO ACCESS AININIRH (*) AOUINIRH (*) HANDO Stop TTRAU (**)
FACCH
Start T3124
UI (PHYS INFO)
FACCH
Start T3105
Stop T3105 UA
FACCH
56
A30808-X3247-M41-4-7618
Information System
MS
BTSold
I (HO CMP)
BTSnew
BSC
MSC
FACCH
DATIN (HO CMP) Stop T8 SINTHINT (*) SININIRH (*) SOUINIRH (*) SINHOBSC (*) MRPCI DT1 (HOPER) Stop T_MSRFPCI RELRQ RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS SUCTCHSE (1.)
(with HO cause)
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message.
A30808-X3247-M41-4-7618
57
Information System
1.2.4.8
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) BWHCI
(with HO cause)
UI (MEAS REP)
SACCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
Start THORQST
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH)
(Activation type: related to synchronous handover)
Start TTRAU CHNAK Start T_MSRFPCI DATRQ (HO CMD) I (HO CMD)
FACCH (Synchronization Indicator: synchronized)
HO ACCESS (***)
FACCH FACCH
FACCH FACCH
HANDO
FACCH
UA
FACCH
ESTIN (new TCH) TNTCHCL (1.) DATIN (HO CMP) Stop T8 SINTHINT (*) SININIRH (*) SOUINIRH (*) SINHOBSC (*)
I (HO CMP)
FACCH
58
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
MRPCI Stop T_MSRFPCI RELRQ RELCN
BSC
MSC
DT1 (HOPER)
(with HO cause)
SUCTCHSE (1.) RCHRL (Old TCH) RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(*) (**)
Note: Subcounter depends on the handover cause value contained in the BWHCI. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message. HO ACCESS is transmitted exactly 4 times, the MS does not wait for any response from the BTS but directly sets up the layer 2 connection (using the SABM) after the last HO ACCESS.
(***)
A30808-X3247-M41-4-7618
59
Information System
1.2.4.9
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3] CHNAV (New TCH)
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) (***) Stop T7 AOUINIRH (*) AININIRH (*) Start T8
HO ACCESS
FACCH
HANDO
Start T3124
60
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
MSC
PHYS INFO
FACCH
TNTCHCL (1.) DATIN (HO CMP) DT1 (HO CMP) SUCTCHSE (1.) MRPCI
I (HO CMP)
FACCH
Stop T_MSRFPCI
SOUINIRH (*) SININIRH (*) NRCLRCMD (3.) Stop T8 RELRQ DT1 (CL CMP) RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(***)
A30808-X3247-M41-4-7618
61
Information System
1.2.4.10
MS
BTSold
BTSnew
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+) NATTSDPE ATINHIRC (*) If last SDCCH start ASDCALTI
Start THORQST
CHNAV (New SDCCH) CHNAK Start T_MSRFPCI DATRQ (HO CMD) I (HO CMD)
SDCCH
HO ACCESS
SDCCH
Start T3124
SDCCH
UA
SDCCH
I (HO CMP)
FACCH
DATIN (HO CMP) Stop T8 SINTHINT (*) SININIRH (*) SOUINIRH (*) SISHINTE SINHOBSC (*)
62
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
MRPCI
BSC
MSC
DT1 (HOPER) Stop T_MSRFPCI NASUSDPE RELRQ RELCN RCHRL (Old SDCCH) RCHRA ASDCALTI (stop) MBUSYSD MBUSYSSP [4] (accumulation) (**)
(with HO cause)
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. Note: Subcounter of MBUSYSSP depends on type of original SDCCH transaction at call setup.
A30808-X3247-M41-4-7618
63
Information System
1.2.4.11
Unsuccessful SDCCH-SDCCH Inter-Cell Handover Attempt, IntraBSC, No SDCCH Available in Target Cell
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
Start THORQST
. . . . .
.
(with HO cause)
. . . . .
.
NATTSDPE (**) (***) ATSDCMBS (**) (***) ATINHIRC (*)(**) (***) NHOINRHA (3.)(**)
Expiry THORQST
BWHCI
(with HO cause)
NATTSDPE (**) (***) ATSDCMBS (**) (***) ATINHIRC (*)(**) (***) NHOINRHA (3.)(**)
(*) (**)
(***)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITON INDICATION. When the BSC receives an INTERCELL HANDOVER CONDITION INDICATION for and SDCCH-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 an available 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 found due to SDCCH congestion, "locked" state of the TRXs or/and "locked" state of the CHAN objects in the target 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 neither ATINHIRC nor NATTSDPE nor ATSDCMBS are increased. CHALNHLY [19] total request CHALNHLY [1] not served
64
A30808-X3247-M41-4-7618
Information System
1.2.4.12
Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 Expiry)
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+) NATTSDPE ATINHIRC (*) If last SDCCH start ASDCALTI
RELRQ
RELCN
A30808-X3247-M41-4-7618
65
Information System
MS
BTSold
BTSnew
BSC
RLSD RLC
MSC
RCHRL (New SDCCH) RCHRA Reset T_MSRFPCI ASDCALTI (stop) (*) MBUSYSD - dec for 2 sdcch
(*)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION.
66
A30808-X3247-M41-4-7618
Information System
1.2.5 1.2.5.1
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) BWHCI
(with HO cause)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
DT1 (HO RQD) CR (HO REQ) ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) MTCHBUTI (1.) (start) Start TTRAU
Start THORQST
Start T7
CHNAK CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (*) DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8 HO ACCESS
FACCH
Start T3124
FACCH
Stop T3124
FACCH
Start T3105
A30808-X3247-M41-4-7618
67
Information System
MS
BTSold
BSCold
SABM
MSC
BSCnew
BTSnew
FACCH
TNTCHCL (1.)
FACCH
DATIN (HO CMP) DT1 (HO CMP) Stop Trr7 (***) DT1 (CL CMD) Stop T8
(cause: handover successful)
SUINBHDO (*) NRCLRCMD (3.) RELRQ RELCN DT1 (CL CMP) RLSD RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) RLC MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC handover this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
(***)
68
A30808-X3247-M41-4-7618
Information System
1.2.5.2
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
DT1 (HO RQD) CR (HO REQ) ATTCHSEI (1.)(**)(***) ATCHSMBS (1.)(**)(***) ATINHIRC (*)(**)(***) NHOINRHA (3.)(**) CREF (HO FAI)
(cause: no radio resource available)
Start THORQST
Start T7
NRINHDFL
(*)
(**)
Note: Subcounter (2.) of the measurement NHOINRHA is triggered when the administrable BSSMAP timer T7 (database parameter name BSCT7) expires; with suitable settings of BSCT7 this happens after the receipt of a HANDOVER REQUIRED REJECT message from the MSC. This means that the timer T7 must be set appropriately (e.g. BSCT7=HLFSEC-6) to ensure that NHOINRHA (2.) counts correctly 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 is in state unlocked/enabled. Also CHALHNLY is triggered: 20 [if full V1/V2] and 11. Also 21 [if AMR] and 12.
(***)
A30808-X3247-M41-4-7618
69
Information System
1.2.5.3
Unsuccessful Inter-Cell Handover, Inter-BSC, with Reversion to Old TCH, FR Call (T3124 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) BWHCI
(with HO cause)
UI (MEAS REP)
SACCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
DT1 (HO RQD) CR (HO REQ) ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) MTCHBUTI (1.) (start) CC (HO RAC; HO CMD) Start TTRAU
Start THORQST
Start T7
CHNAK DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (*) I (HO CMD)
FACCH
FACCH
Start T3124
FACCH
HO ACCESS
ESTIN
70
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
UA
FACCH
I (HO FAIL)
FACCH (cause: DATIN protocol error unspecified****)
(HO FAIL)
Stop T8
RLSD RLC
(***) (****)
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 after transmission of the HANDOVER ACCESS on the target channel. The MS can still return to the old channel after it has received the PHYSICAL INFORMATION from the BTS. This happens when the layer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmission of the SABM on the target channel.
A30808-X3247-M41-4-7618
71
Information System
1.2.5.4
Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8<Trr7), FR Call (T8 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) BWHCI
(with HO cause)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
DT1 (HO RQD) CR (HO REQ) ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) MTCHBUTI (1.) (start) CC (HO RAC; HO CMD) DT1 (HO CMD) Start TTRAU CHNAK Start T_MSRFPCI Stop TTRAU (**)
Start THORQST
Start T7
NRCLRREQ (3.)
72
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
DT1 (CL CMD) NRCLRCMD (1.) DT1 (CL CMP) DATRQ (CHREL) DESAC RLSD RLC
RELIN
RCHRL (Old TCH) MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, RCHRA if previously started)
RCHRA
MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
RLSD RLC
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC handover this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. 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..
(***)
A30808-X3247-M41-4-7618
73
Information System
1.2.5.5
Unsuccessful Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8>Trr7), FR Call (Trr7 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
DT1 (HO RQD) CR (HO REQ) CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3] ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU
Start THORQST
Start T7
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
MTCHBUTI (1.) (start) CC (HO RAC; HO CMD) DT1 (HO CMD) Stop T7 ATINBHDO (*) DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8
HO CMD is lost ... Expiry Trr7 DT1 (CL CMD) NRCLRCMD (2.) Reset T8 DT1 (CL CMP)
74
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
RCHRA
DATRQ (CHREL) DESAC RLSD RLC RELIN MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop)
RLSD RLC
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC handover this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. 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..
(***)
A30808-X3247-M41-4-7618
75
Information System
1.2.5.6
Unsuccessful Inter-Cell Handover, Inter-BSC, with Loss of MS, Handover Access Failure (No SABM received after Transmission) of PHYSICAL INFO, [(NY1+1) * T3105]<<T8<TTRAU)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
DT1 (HO RQD) CR (HO REQ) CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3] ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU
Start THORQST
Start T7
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
MTCHBUTI (1.) (start) CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (*) DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8 HO ACCESS
FACCH
Start T3124
FACCH
HO ACCESS
76
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
MS does not react to PHYS INFO, no SABM is received at the BTS. UI (PHYS INFO) MS does not react to PHYS INFO, no SABM is received at the BTS. UI (PHYS INFO) MS does not react to PHYS INFO, no SABM is received at the BTS.
Start T3105
Expiry T3105
FACCH
Start T3105
Expiry T3105
FACCH
Start T3105
A30808-X3247-M41-4-7618
77
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
RCHRL RELIN RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started)
DT1 (CL CMD) NRCLRCMD (1.) DT1 (CL CMP) DATRQ (CHREL) DESAC RLSD RLC
(***) (****)
78
A30808-X3247-M41-4-7618
Information System
1.2.5.7
Successful Inter-Cell Handover, Inter-BSC, No TCH Available in First (external) Cell, Second Target Cell Belongs to Originating BSC, FR Call
The red colour indicates the BSC serving the first (really external) target cell in the target cell list of the HANDOVER REQUIRED message.
i
MS
BSC A
MSC
BSC B
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
DT1 (HO RQD) Start T7 CR (HO REQ) ATTCHSEI (1.) ATCHSMBS (1.) CREF (HO FAI) CR (HO REQ) ATTCHSEI (1.) if last TCH start AALTCHTI (1.)
(cause: no radio resource available)
Start THORQST
NRINHDFL
CHNAV (New TCH) Start TTRAU (**) MTCHBUTI (1.) (start) CHNAK Start T_MSRFPCI CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) (***) Stop T7 AOUINIRH (*) AININIRH (*) DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8
HO ACCESS
FACCH
Start T3124
A30808-X3247-M41-4-7618
79
Information System
MS
BSC A
MSC
BSC B
TNTCHCL (1.) DATIN (HO CMP) DT1 (HO CMP) SUCTCHSE (1.) MRPCI
I (HO CMP)
FACCH
Stop T_MSRFPCI
SOUINIRH (*) SININIRH (*) NRCLRCMD (3.) Stop T8 DT1 (CL CMP) RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (stop) AALTCHTI (stop)
RELRQ
(*) (**)
(***)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message. HANDOVER COMMAND contains the BCCH and BSIC frequency of an internal neighbour cell.
80
A30808-X3247-M41-4-7618
Information System
1.2.5.8
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
Start THORQST
Start T7
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (*) AOINTESH Start Trr7 (***)
Start T_MSRFPCI
Start T8 HO ACCESS
SDCCH
Start T3124
SDCCH
Stop T3124
SDCCH
Start T3105
A30808-X3247-M41-4-7618
81
Information System
MS
BTSold
BSCold
SABM
MSC
BSCnew
BTSnew
SDCCH
I (HO CMP)
SDCCH
DATIN (HO CMP) DT1 (HO CMP) Stop Trr7 (***) NASUSDPE MRPCI DT1 (CL CMD) Stop T8
(cause: handover successful)
Stop T_MSRFPCI
SUINBHDO (*) SOINTESH NRCLRCMD (15.) RELRQ RELCN DT1 (CL CMP) RLSD RCHRL (Old SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (n.) (**) (accumulation) MBUSYSD - (decr.)
RLC
(*)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. Note: Subcounter of MBUSYSSP depends on type of original SDCCH transaction at call setup. Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
(**) (***)
82
A30808-X3247-M41-4-7618
Information System
1.2.5.9
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
Start THORQST
Start T7
NATTSDPE ATSDCMBS CHALNHLY [19] If layer is not the preferred one CHALNHLY [1]
NRINHDFL
Note: If the handover condition persists and another INTERCELL HANDOVER CONDITION INDICATION is received from the BTS after expiry of T7, the same procedure is repeated in exactly the same way.
A30808-X3247-M41-4-7618
83
Information System
1.2.5.10
Unsuccessful SDCCH-SDCCH Inter-Cell Handover, Inter-BSC with Loss of MS (Loss of HO CMD, T8<Trr7, T8 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
Start THORQST
Start T7
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
CC (HO RAC; HO CMD) DT1 (HO CMD) Stop T7 ATINBHDO (*) AOINTESH I (HO CMD)
SDCCH
Start T_MSRFPCI
84
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
DT1 (CL CMD) NRCLRCMD (13.) DT1 (CL CMP) DATRQ (CHREL) DESAC RLSD RLC
RELIN
NRCLRCMD (16.)
RCHRA
ASDCALTI MBUSYSD - (decr.)
RLSD RLC
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. Note: Subcounter of MBUSYSSP depends on type of original SCDDH transaction 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..
A30808-X3247-M41-4-7618
85
Information System
1.2.6 1.2.6.1
MS
BTS
Call in progress...
UI (MEAS REP)
BSC
MSC
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] WIHCI
(with HO cause)
Start THORQST
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI I (ASS CMD)
Old FACCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
DATRQ (ASS CMD) Start T10 ESTIN Stop TTRAU (**) ATINHIAC (*) TNTCHCL (1.)
SABM
New FACCH
UA
New FACCH
I (ASS CMP)
New FACCH
86
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
DT1 (HOPER) SUCTCHSE (1.) MRPCI
(with HO cause)
MSC
Stop T_MSRFPCI RELRQ RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-cell handover this is done after receipt of the ESTABLISH INDICATION for the target TCH.
A30808-X3247-M41-4-7618
87
Information System
1.2.6.2
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
Expiry THORQST
BWHCI (**)
(cause: downlink/uplink quality)
ATTCHSEI (1.)(BTS new) ATINHIRC (*) If last TCH start AALTCHTI (1.)
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. The inter-cell handover is sent after n intra-cell handover. Only for intra-cell handover due to quality. An inter-cell handover due to quality is triggered, if the handover conditions persist and the call is still on the old TCH when the next HANDOVER CONDITION INDICATION is sent after expiry of THORQST.
88
A30808-X3247-M41-4-7618
Information System
1.2.6.3
Unsuccessful Intra-Cell Handover Due to Quality with Reversion to Old TCH, FR Call
MS
BTS
Call in progress...
UI (MEAS REP)
BSC
MSC
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5] WIHCI
(cause: downlink/uplink quality)
Start THORQST
CHNAV (New TCH) Start TTRAU CHNAK Start T_MSRFPCI I (ASS CMD)
Old FACCH
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
SABM
New FACCH
UA I (ASS FAIL)
Old FACCH (cause: protocol error unspecified)
DATIN (ASS FAIL) Stop T10 UNINHOIA (*) RCHRL (New TCH) Reset TTRAU
Reset T_MSRFPCI
A30808-X3247-M41-4-7618
89
Information System
MS
BTS
RCHRA
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. The inter-cell handover is sent after n intra-cell handover. Only for intra-cell handover due to quality. An inter-cell handover due to quality is triggered, if the handover conditions persist and the call is still on the old TCH when the next HANDOVER CONDITION INDICATION is sent after expiry of THORQST.
90
A30808-X3247-M41-4-7618
Information System
1.2.6.4
Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD, T10 < TTRAU), FR Call (T10 Expiry)
MS
BTS
Call in progress...
UI (MEAS REP)
BSC
MSC
SACCH SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] UI (MEAS REP) MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 WIHCI ATINHIRC (*) (with HO cause) Start THORQST CHALNHLY[20 (Full ATTCHSEI (1.) V1/V2) or 21(AMR)] If last TCH start If layer is not the preAALTCHTI (1.) CHNAV (New TCH) ferred one CHALNHLY[2 or 3] Start TTRAU MTCHBUTI (1.) (start) CHNAK Start T_MSRFPCI I (ASS CMD)
Old FACCH
DT1 (CL CMD) NRCLRCMD (1.) DT1 (CL CMP) RELRQ RELCN RCHRL (New TCH) Reset TTRAU Reset T_MSRFPCI RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS RLSD RLC
A30808-X3247-M41-4-7618
91
Information System
MS
BTS
RCHRL (Old TCH) RCHRA
BSC
MSC
(*)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION.
92
A30808-X3247-M41-4-7618
Information System
1.2.6.5
Unsuccessful Intra-Cell Handover with Loss of MS (Loss of ASS CMD, T10>TTRAU), FR Call (TTRAU Expiry)
MS
BTS
Call in progress...
UI (MEAS REP)
BSC
MSC
SACCH
UI (MEAS REP)
SACCH
WIHCI
(with HO cause)
Start THORQST
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) CHNAV (New TCH) CHALNHLY[20 (Full V1/V2) or 21(AMR)] Start TTRAU MTCHBUTI (1.) (start) If layer is not the preCHNAK ferred one Start T_MSRFPCI CHALNHLY[2 or 3] DATRQ (ASS CMD) Start T10 ATINHIAC (*)
I (ASS CMD)
Old FACCH
Expiry TTRAU
CONFL
(cause: remote transcoder failure)
DT1 (CL CMD) NRCLRCMD (1.) RELRQ RELCN RCHRL (New TCH) Reset T_MSRFPCI RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS DT1 (CL CMP)
A30808-X3247-M41-4-7618
93
Information System
MS
BTS
BSC
RLSD RCHRL (Old TCH) RLC RCHRA MTCHBUTI (1.) (stop)
MSC
(*)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION.
94
A30808-X3247-M41-4-7618
Information System
1.2.6.6
MS
BTS
BSC
MSC
Call in progress...
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
WIHCI
(cause: downlink/uplink quality)
DT1 (HO RQD) Start T7 CR (HO REQ) CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
MEBUSTCH [1] ATTCHSEI (1.) MEBUTSLY [FR & LY] If last TCH start MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 AALTCHTI (1.) ATINHIRC (*) CHNAV (New TCH) Start TTRAU MTCHBUTI (1.) (start) CHNAK Start T_MSRFPCI Stop TTRAU (**) Stop T7 I (HO CMD)
Old FACCH
HO ACCESS
New FACCH
TNTCHCL (1.)
A30808-X3247-M41-4-7618
95
Information System
MS
I (HO CMP)
New FACCH
BTS
BSC
MSC
SOUINIRH SININIRH NRCLRCMD (3.) DT1 (CL CMP) RELRQ RELCN RLSD RLC
RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop)
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of MSC controlled handover this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS.
96
A30808-X3247-M41-4-7618
Information System
1.2.6.7
MS
BTS
Call in progress...
UI (MEAS REP)
BSC
MSC
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] CHNAV (New SDCCH) MBUSYSD (+) CHNAK
DATRQ (ASS CMD) Start T10 ATINHIAC (*) AISHINTR ESTIN (New SDCCH)
SABM
New SDCCH
UA
New SDCCH
I (ASS CMP)
New SDCCH
DATIN (ASS CMP) Stop T10 SINTHITA (*) SISHINTR SINHOBSC (*) DT1 (HOPER) NASUSDPE MRPCI Stop T_MSRFPCI
(with HO cause)
A30808-X3247-M41-4-7618
97
Information System
MS
BTS
RELRQ RELCN RCHRL (Old SDCCH) RCHRA
BSC
MSC
(*)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION.
98
A30808-X3247-M41-4-7618
Information System
1.2.7 1.2.7.1
MS
BTSold
BTSnew
Call setup ...
BSC
MSC
UI (MEAS REP)
SACCH
DT1 (ASS REQ) ATTCHSEI (1.) (*) ATCHSMBS (1.) (*) TASSATT (2.)(*)
UI (MEAS REP)
SACCH
FHREQ BWHCI
(cause: forced, target cell list)
UI (MEAS REP)
SACCH
ATINHIRC (7.)(*) MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATTCHSEI (1.)(**) If last TCH start AALTCHTI (1.) (**) CHNAV (New TCH)
(contains CGI of BTS0 and GSM08.08 cause forced)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
MTCHBUTI (1.)
HO ACCESS
FACCH
FACCH
TNTCHCL (1.)
A30808-X3247-M41-4-7618
99
Information System
MS
FACCH
BTSold
I (HO CMP)
BTSnew
DATIN (HO CMP)
BSC
MSC
Stop T8 SOUINIRH (7.) SININIRH (7.) SINHOBSC (7.) SINTHINT (7.) DT1 (ASS COM) SUCTCHSE (1.) TASSSUCC (4.) MRPCI Stop T_MSRFPCI RELRQ RELCN RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-)
I (CHMM)
FACCH
DATRQ (CHMM)
I (CHMMACK)
FACCH
I (ALERT)
FACCH
I (CONNECT)
FACCH
I (CONACK)
FACCH
100
A30808-X3247-M41-4-7618
Information System
1.2.7.2
MS
BTS
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(cause: forced,empty target cell list)
A30808-X3247-M41-4-7618
101
Information System
1.2.7.3
Unsuccessful Directed Retry, Intra-BSC, 1 Target Cell Available, Target Cell Congested, FR Call
MS
BTSold
BTSnew
Call setup ...
BSC
MSC
UI (MEAS REP)
SACCH
ATTCHSEI (1.) (*) ATCHSMBS (1.) (*) TASSATT (2.) (*) FHREQ BWHCI
(cause: forced, one target cell included)
UI (MEAS REP)
SACCH
ATINHIRC (7.) ATTCHSEI (1.) (**) ATCHSMBS (1.) (**) DT1 (ASS FAI)
(*) (**)
Event is counted for the serving cell. Event is counted for the target cell.
102
A30808-X3247-M41-4-7618
Information System
1.2.7.4
Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH, FR Call (T3124 Expiry)
MS
BTSold
BTSnew
Call setup ...
BSC
MSC
DT1 (ASS REQ) ATTCHSEI (1.) (*) ATCHSMBS (1.) (*) TASSATT (2.)
UI (MEAS REP)
SACCH
FHREQ BWHCI
(cause: forced, target cell list)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) Start TIMERFHO Start TTRAU
ATINHIRC (7.) ATTCHSEI (1.) (**) If last TCH start AALTCHTI (1.) (**) CHNAV (New TCH)
(contains CGI of BTS0 and GSM08.08 cause forced)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
HO ACCESS
FACCH
Expiry T3124
SDCCH
SABM UA
SDCCH
A30808-X3247-M41-4-7618
103
Information System
MS
I (HO FAIL)
SDCCH
BTSold
BTSnew
BSC
MSC
TASSFAIL (7.) RCHRL (New TCH) Reset TTRAU Reset T_MSRFPCI RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS I (DISC)
SDCCH
MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) DT1 (DISC)
DATRQ (DISC)
Event is counted for the serving cell. Event is counted for the target cell.
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 after transmission 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 MS The MS can still return to the old channel after it has received the PHYSICAL INFORMATION from the BTS. This happens when the layer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmission of the SABM on the target channel.
104
A30808-X3247-M41-4-7618
Information System
1.2.7.5
Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 < TTRAU), FR Call (T8 Expiry)
MS
BTSold
BTSnew
Call setup ...
BSC
MSC
DT1 (ASS REQ) ATTCHSEI (1.) (*) ATCHSMBS (1.) (*) TASSATT (2.) FHREQ BWHCI
(cause: forced, target cell list)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) Start TTRAU Start TIMERFHO
ATINHIRC (7.) ATTCHSEI (1.) (**) If last TCH start AALTCHTI (1.) (**) CHNAV (New TCH)
(contains CGI of BTS0 and GSM08.08 cause forced)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAK
On old Channel
A30808-X3247-M41-4-7618
105
Information System
MS
BTSold
BTSnew
BSC
DT1 (CLCMP)
MSC
RCHRL (New TCH) Reset TTRAU Reset T_MSRFPCI Reset TIMERFHO RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started)
RLSD RLC
(*) (**)
Event is counted for the serving cell. Event is counted for the target cell.
106
A30808-X3247-M41-4-7618
Information System
1.2.7.6
Unsuccessful Directed Retry, Intra-BSC, with Loss of MS (Loss of HO CMD, T8 > TTRAU), FR Call (TTRAU Expiry)
MS
BTSold
BTSnew
Call setup ...
BSC
MSC
DT1 (ASS REQ) ATTCHSEI (1.) (*) ATCHSMBS (1.) (*) TASSATT (2.)
UI (MEAS REP)
SACCH
FHREQ BWHCI
(cause: forced)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) Start TTRAU Start TIMERFHO
ATINHIRC (7.) ATTCHSEI (1.) (**) If last TCH start AALTCHTI (1.) (**) CHNAV (New TCH)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CHNAK
Expiry TTRAU
CONFL (On TCH) NRFLTCH (8.) DT1 (CL REQ) NRCLRREQ (3.)
(cause: radio interface message failure)
A30808-X3247-M41-4-7618
107
Information System
MS
BTSold
BTSnew
BSC
MSC
RCHRL (New TCH) Reset T_MSRFPCI RCHRA MBTCHCH MTCHBUTI (1.) (stop) MEBUSTCH = AALTCHTI (1.) (stop, MEBUTSLY if previously started) ABSPDIS -
RELRQ RELCN RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-) RLSD RLC
(*) (**)
Event is counted for the serving cell. Event is counted for the target cell.
108
A30808-X3247-M41-4-7618
Information System
1.2.8 1.2.8.1
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
FHREQ BWHCI
(cause: forced)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CR (HO REQ)
(cause: directed retry)
Start T7 CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU Start TIMERFHO CHNAK Start T_MSRFPCI
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (7.) I (HO CMD)
SDCCH
A30808-X3247-M41-4-7618
109
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
HO ACCESS
FACCH
HANDO
FACCH
Start T3105
I (HO CMP)
FACCH
DATIN (HO CMP) DT1 (HO CMP) DT1 (CL CMD) Stop T8
(cause: handover successful)
SUINBHDO (7.)
Release of resources...
DATRQ (CHMM) I (CHMM)
FACCH
I (CHMMACK)
FACCH
DATIN (CHMMACK)
DATRQ (ALERT)
FACCH
110
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
I (CONACK)
FACCH
DT1 (CONACK)
DATIN (CONACK)
(**)
(***)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC directed retry this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
A30808-X3247-M41-4-7618
111
Information System
1.2.8.2
Unsuccessful Directed Retry, Inter-BSC, FR Call, no Radio Resource available in Target Cell
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
FHREQ BWHCI
(cause: forced)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CR (HO REQ)
(cause: directed retry)
Start T7
NRINHDFL
NRCLRCMD [14]
(*)
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 HANDOVER REQUIRED REJECT, it will immediately release the resources by sending a CLEAR COMMAND to the BSC. 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).
112
A30808-X3247-M41-4-7618
Information System
1.2.8.3
Unsuccessful Directed Retry, Inter-BSC, with Reversion to SDCCH, FR Call (T3124 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CR (HO REQ)
(cause: directed retry)
Start T7 CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3] MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*) ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU
Start TIMERFHO CHNAK CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (7.) I (HO CMD)
SDCCH
Start T_MSRFPCI
A30808-X3247-M41-4-7618
113
Information System
MS
BTSold
BSCold
HO ACCESS
MSC
BSCnew
BTSnew
FACCH
HO ACCESS
FACCH
ESTIN (SDCCH)
UA
SDCCH
I (HO FAIL)
SDCCH
RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) RLSD RLC CL CMD
114
A30808-X3247-M41-4-7618
Information System
(***) (****)
Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD. 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 after transmission of the HANDOVER ACCESS on the target channel. The MS can still return to the old channel after it has received the PHYSICAL INFORMATION from the BTS. This happens when the layer 2 connection setup fails, i.e. when the MS does not receive any UA after repeated transmission of the SABM on the target channel.
A30808-X3247-M41-4-7618
115
Information System
1.2.8.4
Unsuccessful Derected Entry, Inter-BSC, with Loss of MS (Loss of HO CMD, T8 < Trr7), FR Call (T8 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
CR (HO REQ)
(cause: directed retry)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
Start T7
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU Start TIMERFHO CHNAK Start T_MSRFPCI
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (7.) DATRQ (HO CMD) I (HO CMD)
SDCCH
Start T8
116
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
Expiry T8 NRSLSDCC DT1 (CLREQ)
MSC
BSCnew
BTSnew
NCLRREQ [21]
NCLRCMD [13]
DESAC RELIN RCHRL (SDCCH) RLC RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-) RLSD
NRCLRCMD (4.) RCHRL new TCH Reset TIMERFHO Reset T_MSRFPCI RCHRA new TCH
MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) DT1 (CL CMP) RLSD RLC
(***)
Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
A30808-X3247-M41-4-7618
117
Information System
1.2.8.5
Unsuccessful Directed Retry, Inter-BSC, with Loss of MS (Loss of HO CMD, T8 > Trr7), FR Call (Trr7 Expiry)
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
FHREQ
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(cause: forced)
CR (HO REQ)
(cause: directed retry)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
Start T7
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) Start TTRAU
118
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
Reset T8 RELRQ DT1 (CL CMP) RELCN RLSD RCHRL (SDCCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop) RLC DT1 (CL CMP) RLSD RLC
Reset TIMERFHO Reset T_MSRFPCI RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS -
(***)
Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
A30808-X3247-M41-4-7618
119
Information System
1.2.9 1.2.9.1
MS
BTSold
BTSnew
BSC
MSC
UI (MEAS REP)
SACCH
FHREQ BWHCI
(cause: forced, target cell list)
UI (MEAS REP)
SACCH
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATINHIRC (8.) (*) ATTCHSEI (1.)(**) If last TCH start AALTCHTI (1.) (**)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
MTCHBUTI (1.)
HO ACCESS
FACCH
TNTCHCL (1.)
120
A30808-X3247-M41-4-7618
Information System
MS
BTSold
I (HO CMP)
BTSnew
DATIN (HO CMP)
BSC
MSC
FACCH
Stop T8 SOUINIRH (8.) SININIRH (8.) SINHOBSC (16.) SINTHINT (8.) DT1 (HO PER) MRPCI
(cause: O & M intervention)
Event is counted for the serving cell. Event is counted for the target cell. TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC directed retry this is done on receipt of the HANDOVER DETECT message.
A30808-X3247-M41-4-7618
121
Information System
1.2.9.2
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
FHREQ BWHCI
(cause: forced)
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
Start T7 CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
CR (HO REQ)
(cause: O & M intervention)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
ATTCHSEI (1.) (***) If last TCH start AALTCHTI (1.) (***) CHNAV (New TCH) Start TTRAU Start TIMERFHO CHNAK Start T_MSRFPCI
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (8.) I (HO CMD)
SDCCH
FACCH
HANDO
FACCH
Start T3105
Stop T3105
122
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BSCold
MSC
BSCnew
ESTIN TNTCHCL (1.)
BTSnew
UA
FACCH
I (HO CMP)
FACCH
DATIN (HO CMP) DT1 (HO CMP) NCLRCMD [3] Stop T8 SUINBHDO (8.) DT1 (CL CMD)
(cause: handover successful)
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 when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC directed retry this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. Events triggered in target BTS.
(***)
A30808-X3247-M41-4-7618
123
Information System
1.2.9.3
MS
BTS
BSC
MSC
DATRQ (ASS CMD) Start T10 ESTIN Stop TTRAU (**) ATINHIAC (7.) TNTCHCL (1.)
SABM
New FACCH
UA
New FACCH
I (ASS CMP)
New FACCH
DATIN (ASS CMP) Stop T10 SINTHITA (7.) SINHOBSC (16.) DT1 (HOPER) SUCTCHSE (1.) MRPCI Stop T_MSRFPCI RELRQ RELCN RCHRL (Old TCH) RCHRA MTCHBUTI (1.) (stop) AALTCHTI (1.) (stop, if previously started) MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS (cause: O & M intervention)
124
A30808-X3247-M41-4-7618
Information System
1.2.10
Handover due to BSS Resource Management Criteria (Traffic Handover) Successful Handover due to BSS Resource Management Criteria (Traffic Handover), FR Call
1.2.10.1
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
Expiry TRFCT* BSC detects that the traffic load in the BTS old exceeds the threshold TRFHITH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
SET ATTRIBUTE **
(Traffic Handover enabled)
UI (MEAS REP)
SACCH
CHALNHLY[20 (Full SET ATTRIBUTE ACK or 21(AMR)] V1/V2) Start TRFHOT Traffic Handover enabled in the BTS (m=1) *** BWHCI
(cause: traffic)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (9.) (*) Start TTRAU
ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV (New TCH) MTCHBUTI (1.) (start) CHNAK
A30808-X3247-M41-4-7618
125
Information System
MS
BTSold
BTSnew
BSC
MSC
HO ACCESS
FACCH
Start T3124
FACCH
UA
FACCH
ESTIN TNTCHCL (1.) DATIN (HO CMP) Stop T8 SINTHINT (9.) SININIRH (9.) SOUINIRH (9.) SINHOBSC (12.) MRPCI DT1 (HOPER) Stop T_MSRFPCI SUCTCHSE (1.) RELRQ RELCN RCHRL (Old TCH) RCHRA MBTCHCH MEBUSTCH = MEBUTSLY ABSPDIS (cause: distance)
I (HO CMP)
FACCH
126
A30808-X3247-M41-4-7618
Information System
(*) (**)
(***)
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 the traffic handover for the whole BTS. This means that the BTS makes the traffic handover decision for all calls currently busy in the cell and starts the timer TRFHOT (when it expires, the BTS makes the next handover decision for all calls that are busy at that point of time). This message flow just shows one single 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 value m=1. m is an internal counter which is used in the calculation process of the traffic handover decision and which supports a mechanism for a dynamic decrease of the traffic handover margin for subsequent traffic handover decisions. For further details, please refer to the associated feature description for traffic handover!
A30808-X3247-M41-4-7618
127
Information System
1.2.10.2
Unsuccessful Inter-Cell Handover due to BSS Resource Management Criteria (Traffic Handover), traffic load in Target Cell exceeds the threshold TRFLTH
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
Expiry TRFCT* BSC detects that the traffic load in the BTS old exceeds the threshold TRFHITH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
SET ATTRIBUTE **
(Traffic Handover enabled)
UI (MEAS REP)
SACCH
SET ATTRIBUTE ACK Start TRFHOT Traffic Handover enabled in the BTS (m=1) ***
BWHCI***
. . . . .
. Expiry TRFHOT Next Traffic Handover decision (m=2)
(cause: traffic)
. . . . .
.
BSC detects that the traffic load in the target cell is above the threshold (TRFLTH) NHOINRHA (3.)
BWHCI****
(cause: traffic)
BSC detects that the traffic load in the target cell is above the threshold (TRFLTH) NHOINRHA (3.)
Call in continuation...
128
A30808-X3247-M41-4-7618
Information System
(*) (**)
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 the traffic handover for the whole BTS. This means that the BTS makes the traffic handover decision for all calls currently busy in the cell and starts the timer TRFHOT (when it expires, the BTS makes the next handover decision for all calls that are busy at that point of time). This message flow just shows one single 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 value m=1. m is an internal counter which is used in the calculation process of the traffic handover decision and which supports a mechanism for a dynamic decrease of the traffic handover margin for subsequent traffic 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!
A30808-X3247-M41-4-7618
129
Information System
1.2.11 1.2.11.1
Queuing & Preemption Queuing: Queued Assignment Request for FR TCH Is Served Before T11PUB or T11WPS Expiry, Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call
MS
BTS
BSC
MSC
FHREQ BWHCI
(cause: forced, no target cell included)
Start T11PUB or T11WPS MTCHQLEN (1) (incr.) (*) DT1 (PROGRES) I (PROGRES)
SDCCH
DATRQ (PROGRES)
BTS congestion ends during runtime of T11PUB or T11WPS, 1 TCH becomes idle again...
Stop T11PUB or T11WPS MDURTCRQ (1.) (accumulation) MTCHQLEN (1) (decr.) (***) PHCRQ MTCHBUTI (1.) (start) PHCCN CHNAV Start TTRAU CHNAK Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (**) I (ASS CMD)
SDCCH
130
A30808-X3247-M41-4-7618
Information System
MS
SABM
FACCH
BTS
ESTIN UA
FACCH
BSC
MSC
I (ASS CMP)
FACCH
(* )
If the queued call is a WPS one, also the subcounter WPSSUPV [2] is incremented.
(**)
TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message. If the queued call is a WPS one, also the subcounters WPSSUPV [10] and [7] are incremented.
(***)
A30808-X3247-M41-4-7618
131
Information System
1.2.11.2
Queuing: Queued Assignment Request for FR TCH is Discarded from the Queue Before T11PUB or T11WPS Expiry Due to an Incoming FR Assignment Request with Higher Priority Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call
The blue colour indicates the events related to the second (high priority) call.
i
MS
BTS
BSC
MSC
NHOINRHA (1.)
DT1 (QUIND)
Start T11PUB or T11WPS (low prio call) MTCHQLEN (1) (incr.) (**) I (PROGRES)
SDCCH
DATRQ (PROGRES)
DT1 (PROGRES)
All places in the queue are occupied after the first call...
DT1 (ASS REQ)* ATTCHSEI (1.)* ATCHSMBS (1.)* TASSATT (2.)*
Stop T11PUB or T11WPS (low prio call) NMSGDISQ (1.) (***) MDURTCRQ (1.) (stop) NHOINRHA (1.)
132
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
DT1 (QUIND)* DT1 (ASS FAI)
MSC
Events related to second (high priority) call If the queued call is a WPS one, also the subcounter WPSSUPV [2] is incremented. If the queued call is a WPS one, also the subcounter WPSSUPV [4] is incremented.
A30808-X3247-M41-4-7618
133
Information System
1.2.11.3
Queuing: Queued Assignment Request for FR TCH Is Discarded from Queue Due to T11PUB or T11WPS Expiry, Directed Retry Enabled But No Target Cell Available, Preemption Disabled or Not Allowed for the Requesting Call
MS
BTS
BSC
MSC
FHREQ BWHCI
(cause: forced, no target cell included)
Start T11PUB or T11WPS MDURTCRQ (1.) (start) DT1 (PROGRES) DATRQ (PROGRES) I (PROGRES)
SDCCH
Expiry T11PUB or T11WPS NMSGDISQ (1.) MDURTCRQ (1.) (stop) If WPS WPSSUP [3] DT1 (CL REQ) NRCLRREQ (22.)
(cause: no radio resource available)
134
A30808-X3247-M41-4-7618
Information System
1.2.11.4
Queuing: Queued Handover Request for FR TCH Is Served Before TQHOPUB or TQHOWPS Expiry, Preemption Disabled or Not Allowed for the Requesting Call
MS
BTS
BSCnew
All TCHs in the BTS are busy...
MSC
BSC old
ATTCHSEI (1.) ATCHSMBS (1.) CC (QUIND) Start TQHOPUB or TQHOWPS If WPS WPSSUP [2]
BTS congestion ends during runtime of TQHOPUB or TQHOWPS, 1 TCH becomes idle again...
Stop TQHOPUB or TQHOWPS MDURTCRQ (3.) (accum.) CHNAV Start TTRAU CHNAK Start T_MSRFPCI DT1 (HO RAC; HO CMD) WPSSUP [7] DT1 (HO CMD; HO CMD) WPSSUP [11]
A30808-X3247-M41-4-7618
135
Information System
(*)
In case of MSC-controlled handover the MSC cyclically attempts the HANDOVER REQUEST procedure towards all target cells previously received in the HANDOVER REQUIRED message from the originating 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 SIEMENS MSC 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 queuing mechanism as the very last measure to rescue a call.
136
A30808-X3247-M41-4-7618
Information System
1.2.11.5
Queuing: Queued Handover Request for FR TCH Is Discarded from the Queue Before TQHOPUB or TQHOWPS Expiry Due to an Incoming FR Call with Higher Priority, Preemption Disabled or Not Allowed for the Requesting Calls
The blue colour indicates the events related to the high priority call.
i
MS
BTS
BSCnew
All TCHs in the BTS are busy...
CR (HO REQ)
(queuing allowed indicator=allowed)
MSC
BSC old
ATTCHSEI (1.) ATCHSMBS (1.) CC (QUIND) Start TQHOPUB or TQHOWPS MDURTCRQ (3.) (start)
All places in the queue are occupied after the handover request...
DT1 (ASS REQ)* ATTCHSEI (1.)* ATCHSMBS (1.)* TASSATT (2.)* FHREQ* High priority call BWHCI*
(cause: forced, no target cell included)
Stop TQHOPUB or TQHOWPS (low prio call) NMSGDISQ (3.) MDURTCRQ (3.) (stop) NHOINRHA (1.) WPSSUP [4]
Start T11PUB or T11WPS* (high prio call) MDURTCRQ (1.) (start)* DT1 (QUIND)* RLSD (HO FAI) NRINHDFL
(cause: no radio resource available)
A30808-X3247-M41-4-7618
137
Information System
MS
BTS
BSC new
RLC
MSC
BSC old
(*)
138
A30808-X3247-M41-4-7618
Information System
1.2.11.6
Queuing: Queued Handover Request for FR TCH Is Discarded from the Queue Due to TQHOPUB or TQHOWPS Expiry, Preemption Disabled or Not Allowed for the Requesting Calls
MS
BTS
BSCnew
All TCHs in the BTS are busy...
MSC
BSC old
Expiry TQHOPUB or TQHOWPS NMSGDISQ (3.) MDURTCRQ (3.) (stop) WPSSUP [4]
RLC
A30808-X3247-M41-4-7618
139
Information System
1.2.11.7
Preemption: Successful Forced Inter-Cell Handover Due to Preemption, Preempted Assignment Request and Preempting Call Are Both FR
The blue colour indicates the events related to preempting call.
i
MS
BTSold
BTSnew
BSC
MSC
FHREQ BWHCI
(cause: forced, BTSnew included)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3
ATTCHSEI (1.) ATINHIRC (11.) If last TCH start AALTCHTI (1.) CHNAV
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
DATIN (HO CMP) Stop T8 SININIRH (11.) SINTHINT (11.) SOUINIRH (11.) SINHOBSC (16.)
140
A30808-X3247-M41-4-7618
Information System
MS
BTSold
BTSnew
BSC
HOPER
MSC
(cause: Preemption)
PHCCN* CHNAV* preempted channel Start TTRAU* Start T_MSRFPCI* DATRQ (ASS CMD)* I (ASS CMD)*
SDCCH
CHNAK*
Start T10*
(*)
A30808-X3247-M41-4-7618
141
Information System
1.2.11.8
Preemption: Forced Release of Preempted Call Due to Lack of Target Cell for Forced Inter-Cell Handover Procedure, Preempted and Preempting Call Are Both FR
The blue colour indicates the events related to preempting call.
i
MS
BTSold
BTSnew
BSC
MSC
FHREQ BWHCI
(cause: forced, no target cell)
NRCLRCMD (1.)
Start T10*
142
A30808-X3247-M41-4-7618
Information System
1.2.11.9
Preemption: Successful Forced Inter-BSC Handover Due to Preemption, Preempting Handover Request and Preempted Call Are Both FR, Originating BSC of the Preempting Handover Request and Target BSC for the Forced Handover Are the Same
The blue colour indicates the events related to preempting call.
i
MS
BTSold
BSC old
MSC
BSCnew
BTSnew
CR (HO REQ)
(cause: Preemption)
Start T7 CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3] ATTCHSEI (1.) If last TCH start AALTCHTI (1.) CHNAV CHNAK Start T_MSRFPCI
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ATINHIRC (*)
CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) Stop T7 ATINBHDO (10.) DATRQ (HO CMD) I (HO CMD)
FACCH
Start T8
SUCTCHSE (1.)
A30808-X3247-M41-4-7618
143
Information System
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
DT1 (HO CMP) Stop Trr7 (***) DT1 (CL CMD) Stop T8
(cause: handover successful)
RELCN
DT1 (CL CMP) RCHRL RLSD RCHRA MTCHBUTI (1.)* RLC CHNAV* Start TTRAU* CHNAK* Start T_MSRFPCI* Stop TTRAU* CC (HO RAC; HO CMD)* DT1 (HO CMD; HO CMD)* Start Trr7 (***) Start T8 ATINBHDO (*) I (HO CMD)*
FACCH
(*) (**)
Events related to preempting call TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of inter-BSC handover this is done on the CHANNEL ACTIVATION ACKNOWLEDGE for the TCH in the target BTS. Trr7 is an MSC timer which supervises the receipt of a HO CMP after transmission of a HO CMD.
(***)
144
A30808-X3247-M41-4-7618
Information System
1.2.12 1.2.12.1
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE NACSUCPR (3.) ATIMASCA (4.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK CHALNHLY [19] If layer is not the preferred one CHALNHLY [1] MBUSYSD (+)
UI (IMASS)
AGCH
ESTIN (CMSREQ)
SDCCH
ENCRY (CIMCMD)
I (CLAMCH)
SDCCH SDCCH
SDCCH
I (CPROC)
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3 ABISPDIS [1], ABISPSUP [6] If last abis, start ABISPSUP [5]
ATTCHSEI (1.) (*) TASSATT (2.) If last TCH start AALTCHTI (1.)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
A30808-X3247-M41-4-7618
145
Information System
MS
BTS
BSC
MSC
CHNAK (mCH) (**) Start T_MSRFPCI CHNAK (sCH1) (**) Start T_MSRFPCI CHNAK (sCH2) (**) Start T_MSRFPCI DATRQ (ASS CMD) Stop TTRAU (***) I (ASS CMD)
SDCCH
SABM
FACCH
ESTIN on mCH UA
FACCH
TNTCHCL (1.) TNMSCNCL (3.) DATIN (ASS CMP) DT1 (ASS CMP)
I (ASS CMP)
FACCH
146
A30808-X3247-M41-4-7618
Information System
MS
BTS
MRPCI (mCH) (**) Stop T_MSRFPCI MRPCI (sCH1) (**) Stop T_MSRFPCI MRPCI (sCH2) (**) Stop T_MSRFPCI RELRQ RELCN RELCHRL RCHRA ASDCALTI (stop) MBUSYSSP (1.) (accumulation) MBUSYSD (-) I (ALERT)
FACCH
BSC
MSC
I (CONNECT) I (CONACK)
FACCH
DATIN (CONACK)
DT1 (CONACK)
(*) (**)
Note: This counter counts as many events as TCHs are used for the HSCSD call. mCH = main channel sCH1 = 1. secondary channel sCH2 = 2. secondary channel TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND.
(***)
A30808-X3247-M41-4-7618
147
Information System
1.2.12.2
MS
BTSold
BTSnew
Call in progress...
BSC
MSC
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
UI (MEAS REP)
SACCH
BWHCI
(with HO cause)
Start THORQST
MEBUSTCH [1] MEBUTSLY [FR & LY] MBTCHCHT 1 if FV1, 2 if FV2, 3 if FV3
ATTCHSEI (1.) (****) ATINHIRC (*) If last TCH start AALTCHTI (1.) CHNAV (mCH) (**)
CHALNHLY[20 (Full V1/V2) or 21(AMR)] If layer is not the preferred one CHALNHLY[2 or 3]
Start TTRAU
CHNAK (mCH) (**) Start T_MSRFPCI CHNAK (sCH1) (**) Start T_MSRFPCI CHNAK (sCH2) (**) Start T_MSRFPCI DATRQ (HO CMD) I (HO CMD)
FACCH
HO ACCESS
FACCH
148
A30808-X3247-M41-4-7618
Information System
MS
BTSold
UI (PHYS INFO)
BTSnew
BSC
MSC
FACCH
Start T3105
Stop T3105 UA
FACCH
ESTIN New in mCH TNTCHCL (1.) TNMSCNCL (3.) DATIN (HO CMP) Stop T8 SINTHINT (*) SININIRH (*) SOUINIRH (*) SINHOBSC (*) DT1 (HOPER) SUCTCHSE (1.) (****)
(with HO cause)
I (HO CMP)
FACCH
MRPCI (mCH) (**) Stop T_MSRFPCI MRPCI (sCH1) (**) Stop T_MSRFPCI MRPCI (sCH2) (**) Stop T_MSRFPCI
RELRQ RELCN
A30808-X3247-M41-4-7618
149
Information System
MS
BTSold
BTSnew
RCHRL RCHRL RCHRL RCHRA
BSC
MSC
(*) (**)
Note: Subcounter depends on the handover cause value contained in the HANDOVER CONDITION INDICATION. mCH = main channel sCH1 = 1. secondary channel sCH2 = 2. secondary channel TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of intra-BSC handover this is done after receipt of the HANDOVER DETECT message. 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 used for the HSCSD call in the old cell (the number of TCHs used can change during the handover procedure, depending on the number of channels available).
150
A30808-X3247-M41-4-7618
Information System
1.2.12.3
MS
BTS
BSC
MSC
SABM
New FACCH
TNTCHCL (1.)
I (ASS CMP)
New FACCH
DATIN (ASS CMP) Stop T10 SINTHITA (12.) SINHOBSC (16.) MRPCI Stop T_MSRFPCI RELRQ DT1 (HOPER) RELCN RELCHRL
(cause: O & M intervention)
SUCTCHSE (1.)
(*****)
A30808-X3247-M41-4-7618
151
Information System
MS
BTS
PHCRQ (****)
BSC
MSC
MTCHBUTI (1.) (start) (*) (****) PHCCN (****) CHNAV (mCH) (**) (****) Start TTRAU
(activation type: related to normal assignment procedure)
(*) (**)
Note: This counter counts as many events as TCHs are used for the HSCSD call. mCH = main channel sCH1 = 1. secondary channel sCH2 = 2. secondary channel TTRAU is stopped when the BTS receives the (idle) TRAU frames from the TRAU. This happens when the BSC throughconnects the Asub-TCH to the Abis-TCH. In case of TCH Assignment this is done on transmission of the ASSIGNMENT COMMAND. Events related to HSCSD TCH request.
(***)
(****)
(*****) The channel released with the Forced HO is reused in HSCSD call.
152
A30808-X3247-M41-4-7618
Information System
1.2.13 1.2.13.1
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE NACSUCPR (3.) ATIMASCA (5.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI
UI (IMASS)
AGCH
IACMD (IMASS) TACCBPRO (2.) SUIMASCA (5.) NACSUCPR (2.) ESTIN (LUREQ) NSUCCHPC (5.) NASUSDPE MRPCI Stop T_MSRFPCI CR (CL3I; LUREQ) CC
UA
SDCCH
DT1 (LUACC)
I (LUACC) I (TRCMP)
SDCCH
DATIN (TRCMP)
A30808-X3247-M41-4-7618
153
Information System
MS
BTS
DESAC
BSC
MSC
RLSD DISC
SDCCH
RLC RELIN
UA
SDCCH
154
A30808-X3247-M41-4-7618
Information System
1.2.13.2
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE NACSUCPR (3.) ATIMASCA (5.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI
UI (IMASS)
AGCH
IACMD (IMASS) TACCBPRO (2.) SUIMASCA (5.) NACSUCPR (2.) ESTIN (LUREQ) NSUCCHPC (5.) NASUSDPE MRPCI Stop T_MSRFPCI CR (CL3I; LUREQ) CC
UA
SDCCH
CLCH UTRANCC
A30808-X3247-M41-4-7618
155
Information System
MS
BTS
BSC
DT1 (LUACC)
MSC
I (LUACC)
SDCCH
DATRQ (LUACC)
I (TRCMP)
SDCCH
DATIN (TRCMP)
RLC RELIN
UA
SDCCH
156
A30808-X3247-M41-4-7618
Information System
1.2.13.3
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE NACSUCPR (3.) ATIMASCA (6.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI
UI (IMASS)
AGCH
IACMD (IMASS) TACCBPRO (2.) SUIMASCA (6.) NACSUCPR (2.) ESTIN (IMDETIN) NSUCCHPC (6.) NASUSDPE MRPCI Stop T_MSRFPCI CR (CL3I; IMDETIN)
UA
SDCCH
DATRQ (CHREL)
CREF
DESAC DISC
SDCCH
RELIN UA
SDCCH
A30808-X3247-M41-4-7618
157
Information System
1.2.13.4
Successful Supplementary Service (SS) Management Procedure via Subscriber-Controlled Input (SCI)
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
NATTSDPE NACSUCPR (3.) ATIMASCA (4.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI IACMD (IMASS) UI (IMASS)
AGCH
ESTIN (CMSREQ)
(CM Service type: Supplementary Service Activation)
MRPCI
I (CIMCMD)
SDCCH
ENCRY (CIMCMD)
CC (CICMD)
I (CLAMCH)
SDCCH
DATIN (CLAMCH) DT1 (CLUPD) MRPCI Stop T_MSRFPCI I (CIMCMP) DATIN (CIMCMP)
SDCCH
DT1 (CICMP)
158
A30808-X3247-M41-4-7618
Information System
MS
I (REGISTER)
SDCCH (SS code, operation code, service)
BTS
DATIN (REGISTER)
(SS code, operation code, service)
BSC
MSC
DT1 (REGISTER)
(SS code, operation code, service)
I (REL CMP)
SDCCH
I (CHREL)
DISC
SDCCH
RELIN
SDCCH
A30808-X3247-M41-4-7618
159
Information System
1.2.13.5
Successful USSD (Unstructured Supplementary Service Data) Management Procedure via (SCI)
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
NATTSDPE NACSUCPR (3.) ATIMASCA (4.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI IACMD (IMASS) UI (IMASS)
AGCH
ESTIN (CMSREQ)
(CM Service type: Supplementary Service Activation)
MRPCI
I (CIMCMD)
SDCCH
ENCRY (CIMCMD)
CC (CICMD)
I (CLAMCH)
SDCCH
DATIN (CLAMCH) DT1 (CLUPD) MRPCI Stop T_MSRFPCI I (CIMCMP) DATIN (CIMCMP)
SDCCH
DT1 (CICMP)
160
A30808-X3247-M41-4-7618
Information System
MS
I (REGISTER)
SDCCH (SS code, operation code, service)
BTS
DATIN (REGISTER)
(SS code, operation code, service)
BSC
MSC
NSUSDSUS (*)
DT1 (REGISTER)
(SS code, operation code, service)
DT1 (CL CMD) Call control DATRQ (REL CMP) I (REL CMP)
SDCCH
I (CHREL)
DISC
SDCCH
RELIN
SDCCH
(*)
NSUSDSUS and MBUSYSSP subcounter 3 are only triggered if the database flag TRANSPM (BSC object) is set to TRUE. If this flag is set to FALSE, NSUSDSUS is not triggered at all and MBUSYSSP is triggered for subcounter 4.
A30808-X3247-M41-4-7618
161
Information System
1.2.13.6
MS
CHNREQ
RACH
BTS
BSC
MSC
UI (IMASSRJ)
AGCH
Start T3122
NTDMAGCH (1.)
. . . . .
Expiry 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, the MS attempts another access to the cell.
162
A30808-X3247-M41-4-7618
Information System
1.2.13.7
Unsuccessful Immediate Assignment Procedure with DELETE INDICATION (no AGCH available or AGCH message timeout)
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE, NACSUCPR (3.), (1.) (**) ATIMASCA (*) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI
IACMD (IMASS) Start T3101 TACCBPRO (2.) SUIMASCA (*) NACSUCPR (2.)
NTDMAGCH (3.) DELIN (***) Stop T3101 NACSUCPR (2.) decreased by 1 ASDCALTI (stop)
Subcounter depends on the access cause. Subcounter (1.) is only increased if the access cause is answer to paging. The IMMEDIATE ASSIGNMENT message can be discarded due to 3 different events: 1. AGCH queue is full when IMASS is received 2. IMM ASS was received with a high delay (time between CHANNEL REQUEST and receipt of the IMASS has already exceeded the timeout period) 3. IMASS was enqueued in AGCH queue, but timeout was detected prior to transmission on Um. In cases (1) and (2) the DELETE INDICATION will contain the IMASS messages as received from the BSC. In case (3) the DELIN may contain an IMMEDIATE ASSIGNMENT EXTENDED message. This happens, if the BTS has combined two IMASS messages to one IMASS EXT in the AGCH queue and discarded it due to timeout. In this case the counter NTDMAGCH(3.) is increased by 1 (not by 2 although two IMMEDIATE ASSIGNMENT procedures are affected)
A30808-X3247-M41-4-7618
163
Information System
1.2.13.8
Unsuccessful Immediate Assignment Procedure, assigned SDCCH is not seized by the MS (Phantom RACH Scenario)
MS
CHNREQ
RACH
BTS
BSC
MSC
CHNRD NATTSDPE, NACSUCPR (3.), (1.) (**) ATIMASCA (*) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI
UI (IMASS)
AGGH
IACMD (IMASS) Start T3101 TACCBPRO (2.) SUIMASCA (6.) NACSUCPR (2.)
Expiry T3101 RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (n.) (accumulation)
(*) (**)
Subcounter depends on the access cause. Subcounter (1.) is only increased if the access cause is answer to paging.
164
A30808-X3247-M41-4-7618
Information System
1.2.13.9
MS
BTS
BSC
CHNREQ
RACH
Level of received CHANNEL REQUEST is below the threshold RACHBT NINVRACH (1.)
MS
BTS
Timing advance value determined from the received CHANNEL REQUEST exceeds the threshold EXCDIST NINVRACH (2.)
BSC
CHNREQ
RACH
A30808-X3247-M41-4-7618
165
Information System
1.2.13.10
Immediate Assignment Procedure for Abis Link Configured via Satellite Link
Abis link with high propagation delay
MS
CHNREQ
RACH
BTS
BSC
MSC
CH
NR
A HN
V(
C SD
CH
C IA
MD
(IM
S AS
) (*
Start T3101
CH
NA
(*)
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 after the transmission of the CHANNEL ACTIVATION message without waiting for the CHANNEL ACTIVATION ACKNOWLEDGE. This is done to avoid additional Immediate Assignment signaling delay and, as a consequence. unnecessary RACH retransmissions from the mobile stations.
166
A30808-X3247-M41-4-7618
Information System
1.2.13.11
MS
BTS
BSC
UDT (PAGIN) PGCMD TCMSGREC TACCBPRO (1.)
MSC
No place in any paging queue available - the BTS discards the PAGING REQUEST * NTDMPCH (3.) OVERLOAD
(cause: CCCH overload)
Start T17 **
**
Each paging queue place in the BTS can be seized by one PAGING REQUEST message (PAGREQ) which itself can contain the mobile identities (IMSI or TMSI) of up to 3 mobile subscribers simultaneously. This means that the PAGING REQUEST message can contain the mobile identities of up to 3 PAGING COMMANDS (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 increased by as many counts as mobile identities (IMSI or TMSIs) were contained in the discarded PAGING REQUEST message! 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 is enabled in the BSC (BTSOVLH=TRUE). The PAGING COMMANDS to the BTS are discarded as long as T17 runs.
A30808-X3247-M41-4-7618
167
Information System
1.2.14 1.2.14.1
Short Message Service Successful SMS Mobile Originating in Idle Mode (Phase 2 MS)
MS
CHNREQ
RACH
BTS
CHNRD
BSC
MSC
NATTSDPE NACSUCPR (3.) ATIMASCA (6.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK Start T_MSRFPCI IACMD (IMASS) UI (IMASS)
AGCH
SABM (CMSREQ)
SDCCH
ESTIN (CMSREQ) UA
SDCCH
Stop T3101 NSUCCHPC (6.) NASUSDPE MRPCI Stop T_MSRFPCI CR (CL3I; CMSREQ) CC
DATRQ (TRCMD)
DT1 (TRCMD)
SABM (SAPI 3)
SDCCH
ESTIN (SAPI 3)
SDCCH
UA (SAPI 3) I (TRCMP)
SDCCH
168
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
MSC
I (CPDAT; RPDA)
SDCCH
I (CPACK)
SDCCH
I (CPDAT;RPAC) I (CPACK)
SDCCH
DATIN (CPACK)
I (CHREL)
SDCCH
NRCLRCMD (14.)
DISC
SDCCH
RELIN
SDCCH
UA
RELRQ RELCN RLSD RLC RCHRL (SDCCH) RCHRA ASDCALTI (stop) MBUSYSSP (2.) (accumulation) MBUSYSD (-)
A30808-X3247-M41-4-7618
169
Information System
1.2.14.2
MS
BTS
PGCMD
PCH
BSC
UDT (PAGIN) TACCBPRO (1.) CHNRD NATTSDPE NACSUCPR (1.), (3.) ATIMASCA (1.) If last SDCCH start ASDCALTI CHNAV (SDCCH) CHNAK
MSC
CHNREQ
RACH
IACMD (IMASS) Start T3101 TACCBPRO (2.) SUIMASCA (6.) NACSUCPR (2.) ESTIN (PAGRES) Stop T3101 NSUCCHPC (1.) NASUSDPE MRPCI Stop T_MSRFPCI CR (CL3I; PAGRES) CC
SABM (PAGRES)
SDCCH
UA
SDCCH
DT1 (TRCMP)
UA (SAPI 3)
SDCCH
170
A30808-X3247-M41-4-7618
Information System
MS
I (CPACK)
SDCCH
BTS
BSC
MSC
DT1 (CPACK) DT1 (CPDAT; RPAC) DT1 (CPACK) DT1 (CL CMD) NRCLRCMD (14.)
I (CPDAT; RPAC)
SDCCH
I (CPACK)
SDCCH
DATRQ (CPACK)
I (CHREL)
SDCCH
DATRQ (CHREL)
DESAC DISC
SDCCH
RELIN
UA
SDCCH
RELRQ
RLC
A30808-X3247-M41-4-7618
171
Information System
1.2.14.3
MS
BTS
Call in progress...
I (CMSREQ)
BSC
MSC
FACCH
SABM (SAPI 3)
SACCH
NSUCCHPC (15.) DATIN (CPDAT; RPDA) DT1 (CPDAT; RPDA) DT1 (CPACK) DT1 (CPDAT; RPAC)
I (CPDAT; RPDA)
SACCH
I (CPDAT; RPAC)
SACCH
DT1 (CPACK)
SACCH
DATIN (CPACK)
DT1 (CPACK)
172
A30808-X3247-M41-4-7618
Information System
1.2.14.4
MS
BTS
Call in progress...
BSC
MSC
UA (SAPI 3)
SACCH
ESTCN (SAPI 3) TCH NSUCCHPC (16.) DATRQ (CPDAT; RPDA) I (CPDAT; RPDA)
SACCH
I (CPACK)
SACCH
DATIN (CPACK) I (CPDAT; RPAC) DT1 (CPACK) DATIN (CPDAT; RPAC) DT1 (CPDAT; RPAC) DT1 (CPACK) DATRQ (CPACK) I (CPACK)
SACCH
SACCH
A30808-X3247-M41-4-7618
173
Information System
1.2.15 1.2.15.1
Advanced Speech Call Items (ASCI) Procedures 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 Flow below GCA contains bts1 and bts2 in BSC1 and bts1 and bts2 in the BSC2.
MS
bts1/bts2
BSC1
bts1/bts2
BSC2
CR (VBST) CR (VBST) CC (VBSA)
MSC
CR (VARQ)
cell identifier: bts 1 TASSATVS +1 in each cell incl. in GCA
CR (VARQ)
cell identifier: bts 2
One SCCP connection for each VBS/VGCS TCH i.e.for each call
CR (VARQ)
cell identifier: bts 2
ULFREE
VBS/VGCS TCH
ULFREE Notif/NCH
ULFREE NOTCMD
command indicator start
NNNOTNCH Notif/NCH
NCH
NNNOTNCH NOTCMD
command indicator start
NOTCMD
command indicator start
174
A30808-X3247-M41-4-7618
Information System
MS
bts1/bts2
Notif/NCH
NCH
BSC1
bts1/bts2
BSC2
MSC
Notif/NCH
NCH
CC (VARE)
cell identifier: bts 1
CC (VARE)
cell identifier: bts 1
CC (VARE)
cell identifier: bts 2
Release all res. DT1 (CLCMD) control SCCP connetion and associated VGCS/VBS TCH
NOTCMD
command indicator stop
CHREL DISC UA
UDTRQ(CHREL)
DT1 (CLCMP)
NOTCMD UDTRQ(CHREL) DT1 (CLCMP) DESAC RCHRL RLSD RLSD RLC RLC RCHRA RCHRA DT1 (CLCMD) DT1 (CLCMP) RLSD RLC
DESAC DESAC
DT1 (CLCMP)
RLSD RLSD
RCHRA RCHRA
RLSD RLSD DT1 (CLCMD) DT1 (CLCMD) RLSD RLC Release SCCP connetion (Gr.. Call Control
A30808-X3247-M41-4-7618
175
Information System
1.2.15.2
MS
BTS
ULFREE (2) ULFREE ULFREE
VGRULF (3)
FACCH
BSC1
MSC
BSC2
BTS
UPLINK ACCESS
uplink voice group TCH
ULBUSY
FACCH
UPBUS (ULBUSY)
ESTIN (TALKIND)
DT1(URC) [TALKIND])
DATIN (CLCH) MRPCI DT1 (CLUPD) CR(ASREQ) CHNAV CHNAK DATRQ (ASCMD) ESTIN DATIN (ACOM) MRPCI UP_REL (6) CC (ASCMP) SETPAR (7)
Conversation Phase...
176
A30808-X3247-M41-4-7618
Information System
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 dedicated channel (TCH) becomes the new talking subscriber.This is the typical talking subscriber change procedure. 2. The BSC sends this message to the BTS to indicate that the uplink of the VGCS channels becomes or is free. 3. vgcsULFreeTimer (VGRULF in BSC DB Object BTS [TIMER]). If no ASCI call is active the network provides an UPLINK FREE message on the main signalling channel periodically. The timer vgcsULFree Timer denes the repetition rate of sending this message. The timer will be stopped if an Uplink Access of a Mobile Station (MS) or an UPLINK Busy of the BSC was received. 4. Tgrant is a timer to dene the repetition rate of sending the VGCS UPLINK GRANT message. In case of an ASCI call the network grants the uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station. After having sent this message the BTS starts TGRANT to repeat this message for as long as a counter has not reached the value of NRPGRANT. 5. With DT1 USC (Uplink Seize Cmd) the MSC informs a BSC that a MS belonging to another BSC area has successfully seized the uplink common VGCS channel. Then the BSS noties its MSs that the channel is busy. 6. UPLINK RELEASE (BSC->BTS) sent on VGCS common channel to inform the BTS that the BSC has assigned a dedicated TCH to the talker in the same call during talker change procedure. 7. SET PARAMETER messages are sent from MSC where the MS is told that Uplink/Downlink is connected.
A30808-X3247-M41-4-7618
177
Information System
1.2.15.3
MS
BTS
BSC1
MSC
BSC2
BTS
DATIN(ULREL) ULFREE
ULFREE
FACCH
DT1 (UPRI) cause: call control DATRQ(CHREL) CHEL DESAC DISC UA RELIN RCHRL RCHRA The other MSs may attempt to seize the uplink common VGCS channel, in order to talk. RLSD RLC DT1 (CLCMD) cause: call control DT1 (CLCMD)
178
A30808-X3247-M41-4-7618
Information System
1.2.15.4
MS
CHNREQ
BTS
CHNRD CHNAV CHNAK IAS CMSREQ IACMD (IAS)
BSC
MSC
CR(CL3I[CMSREQ]) CC (CICMD)
ENCRY (CI CM) CICM CLCH DATIN (CLCH) MRPCI DATIN (CICP) DT1 (CICMP) SETUP PHCRQ PHCCN CHNAV CHNAK DATRQ (ASCMD) ASCMD UA ESTIN DATIN (ACOM) ACOM MRPCI RELRQ RELCN RCHRL RCHRA DT1 (ASCMP) DT1 (ASREQ) DT1 (CLUPD)
CICP
(1)
A30808-X3247-M41-4-7618
179
Information System
MS
BTS
BSC
CR (VBST) CC (VBSA) CR (VARQ) CHNAV CHNAK
MSC
SCCP connetion (Group Call Control) One SCCP connection (Res. Controlling) for each VGCS TCH, i.e. for each cell
ULBUSY
FACCH
UPBUS (ULBUSY)
NOTCMD Notification/NCH command indicator: start SSI10 (SIT10) CONNECT DATIN (ULREL) ULFREE
FACCH
CC (VARE) (2)
UPFRE (ULFREE)
DT1 (UPRI) DT1 (CLCMD) Release SCCP connection (Res.Controlling) and associated TCH
DATRQ (CREL)
DESAC
UA
RLC
Calling subscriber terminates VGCS call Calling Subcriber Performs Talker Change Procedure... (see 1.2.15.2)
TERMREQ TERM (4)
Release of the Talker TCH ... (see 1.2.15.3) Release all res. controlling SCCP connection and asociated VGCS THCs Release SCCP connections (Group Call Control)
180
A30808-X3247-M41-4-7618
Information System
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 do this the mobile station must have access to the uplink.
A30808-X3247-M41-4-7618
181
Information System
1.2.15.5
MS
CHREQ
BTS
BSC
CHNRD CHNAV CHNAK IACMD (IAS)
MSC
ESTIN (ISETUP) CR (CL3I [ISETUP]) CC (CMSACC) DATRQ (CMSACC) DT1 (ASSREQ) CR (VBST)
CMSACC
(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.
182
A30808-X3247-M41-4-7618
Information System
1.2.15.6
MS
BTS
BSC
MSC
Notif/FACCH
PGCMD
If the PAGING message towards the BSC contains the emLPP priority level IE and if the emLPP priority level is 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 channel active. If the paged MS is a listener of any ongoing ASCI call in the BSC then it should receive the Notification/FACCH message and switch to the incoming MTC call.
A30808-X3247-M41-4-7618
183
Information System
1.2.15.7
MS
BTS
BSC
MSC
Notif/FACCH
FACCH
DISC
cause value: pre-emption
DISC
DT1 (DISC)
cause value: pre-emption
If the VBS/VGCS Assignment Request message contains the emLPP priority level IE and if the emLPP Priority 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 dedicated TCH occupied by speech call (MOC originated by ASCI subscriber, member of the incoming group call). If the originator of the ongoing MOC is a member of the incoming group call it should receive the Notification/FACCH message and switch the incoming group call. The MOC should be released.
184
A30808-X3247-M41-4-7618
Information System
1.2.16 1.2.16.1
Inter System Handover (2G <--> 3G), circuit switched (CS) Successful Inter System Handover (2G --> 3G)
MS/ UE
UI (MEAS REP)
BTS
BSC
2G+3G MSC
RNC
NodeB
DT1 (HOCMD)
T7 stop ATOISHDO
HO ACCESS
T3124 start
HO ACCESS
RRC HO Detect lu Relocation Detect
T3124 stop
HO COMPLETE
RRC HO Complete lu Relocation Complete
A30808-X3247-M41-4-7618
185
Information System
MS/ UE
BTS
BSC
2G+3G MSC
DT1 (CLCMD)
RNC
NodeB
186
A30808-X3247-M41-4-7618
Information System
1.2.16.2
Unsuccessful Inter System Handover (2G --> 3G), loss of MS (loss of HOCMD), T3121 expiry
MS/ UE
UI (MEAS REP)
BTS
BSC
2G+3G MSC
RNC
NodeB
DT1 (HOCMD)
ATOISHDO
[9]
[3]
DT1 (CLCMD)
NRCLRCMD
[1]
DT1 (CLCMP)
A30808-X3247-M41-4-7618
187
Information System
MS/ UE
BTS
BSC
2G+3G MSC
RNC
NodeB
188
A30808-X3247-M41-4-7618
Information System
1.2.16.3
Unsuccessful Inter System Handover (2G --> 3G), No TCH available in Target UMTS Cell (3G)
MS/ UE
UI (MEAS REP)
BTS
BSC
2G+3G MSC
RNC
NodeB
DT1 (HORRJ)
T7 expiry NHOINRHA
A30808-X3247-M41-4-7618
189
Information System
1.2.16.4
Unsuccessful Inter System Handover (2G --> 3G), Reversion to old TCH, T3124 expiry
MS/ UE
UI (MEAS REP)
BTS
BSC
2G+3G MSC
RNC
NodeB
DT1 (HOCMD)
ATOISHDO
T3124 start
HO ACCESS
T3124 expiry
DT1 (HOFAI)
lu Clear Command lu Clear Complete Release new channels on UTRAN (3G) side
190
A30808-X3247-M41-4-7618
Information System
1.2.16.5
MS/ UE
NodeB
RNC
2G+3G MSC
BSC
BTS
Event 2d: Meas Report [2d] Event 3a: Meas Report [3a] lu Relocation Required
CR (HOREQ)
RQIISHDO
A30808-X3247-M41-4-7618
191
Information System
MS/ UE
NodeB
RNC
2G+3G MSC
BSC
BTS
(*)
192
A30808-X3247-M41-4-7618
Information System
1.2.16.6
Unsuccessful Inter System Handover (3G --> 2G), No TCH available in Target GSM Cell (2G)
MS/ UE
NodeB
RNC
2G+3G MSC
BSC
BTS
Event 2d: Meas Report [2d] Event 3a: Meas Report [3a] lu Relocation Required
CR (HOREQ)
RQIISHDO No TCHs available on GSM (2G) side
CREF (HOFAI)
UNIISHDO
A30808-X3247-M41-4-7618
193
Information System
1.2.17 1.2.17.1
MS
BTS
BSC
MSC
. . . . .
RESIN (*) ILUPLKIC
. . . . .
MEITCHIB
(*)
Contains the idle TCH measurements for all TCHs of the TRX currently not used for a call.
194
A30808-X3247-M41-4-7618
Information System
1.2.17.2
MS
BTS
BSC
MSC
MEAS REP MESRS (MEAS REP) (*) PWRUPDW CRXLVQUU CRXLVQUD CRXLVTAU CRXLVTAD CFERRXQU
. . . . .
MEAS REP
. . . . .
. . . . .
. . . . .
MESRS (MEAS REP) (*) PWRUPDW CRXLVQUU CRXLVQUD CRXLVTAU CRXLVTAD CFERRXQU
(*)
Measurement Reports are transmitted for each TCH of the TRX currently seized by a call only if the feature Measurements on Abis (SET TRX: RADIOMR = TRUE) is enabled in the BSC database.
A30808-X3247-M41-4-7618
195
Information System
1.2.17.3
MS
BTS
BSC
MSC
I (CMSREQ)
SDCCH
I (CLAMCH)
SDCCH
I (CIMCMP)
SDCCH
TMEASRES (MEASREP)
196
A30808-X3247-M41-4-7618
Information System
1.2.17.4
MS
BTSold
BSCold
MSC
BSCnew
BTSnew
CR (HO REQ) CHNAV (New TCH) CHNAK CC (HO RAC; HO CMD) DT1 (HO CMD; HO CMD) DT1 (MSIT) DATRQ (HO CMD) I (HO CMD)
FACCH
I (HO CMP)
FACCH
DATIN (HO CMP) DT1 (HO CMP) MRPCI DT1 (CL CMD)
(cause: handover successful)
STRAC STRACACK
RELRQ RELCN DT1 (CL CMP) RLSD RCHRL (Old TCH) RCHRA RLC
A30808-X3247-M41-4-7618
197
Information System
1.3
1.3.1
1.3.1.1
1 2
DL-TBF UL-TBF
4 5
DL-TBF UL-TBF
The Attach procedure is used by the mobile to register for GPRS services. 1. 2. The mobile sends Attach Request containing information about its mobile capabilities, its mutual class and its IMSI or P-TMSI for identification. If the MS identifies itself with its P-TMSI but the P-TMSI is unknown in SGSN, the SGSN sends an Identity Request to the MS. The MS responds with Identity Response including its IMSI. In contrast to ciphering in existing GSM (between BTS and MS) GPRS ciphering is a function of the LLC layer in the SGSN and in the mobiles. If enabled in the SGSN it initiates the authentication and ciphering procedure. The network informs the MS that the Attach was accepted. The network may include a new P-TMSI in the Attach Accept message. If the Attach Accept contained a new P-TMSI, the MS confirms the reception with Attach Complete.
3.
4. 5.
198
A30808-X3247-M41-4-7618
Information System
1.3.1.2
(Mobile initiated) MS UL-TBF DL-TBF BSC DTRQ detach type DTAC SGSN
1 2
The detach procedure is used by the mobile to deregister from GPRS services. 1. 2. The mobile initiated detach might be triggered by user command from mobile menu or when the mobile is switched off. If the detach Type indicates that the detach is not due to power switch off, the SGSN sends a Detach Accept to the MS.
1 2
DL-TBF UL-TBF
The network may initiate the GPRS detach when GPRS services are no longer accepted for a subscriber (e.g. the subscriber is cancelled from the HLR database). 1. 2. The SGSN informs the MS that it has been detached by sending detach Request to the MS. The mobile confirms the detach with detach accept.
A30808-X3247-M41-4-7618
199
Information System
1.3.1.3
1 2
DL-TBF
A PDP context represents a logical connection between a mobile and the network with a specific PDP address for data routing (e.g. fixed or dynamic local IP address) and a specific Quality of Service profile (QoS). The Activate PDP Context procedure is used to establish the connection. If supported by the mobile several PDP Contexts with different QoS profiles might be active handling different applications. 1 In the Activate PDP Context Request the mobile includes a requested QoS. The MS . shall use the PDP Address Information Element to indicate whether it requires the use of a static PDP Address or whether it requires the use of a dynamic PDP address. The MS leaves the PDP Address IE empty to request a dynamic PDP address. 2 The network verifies if it can support the requested QoS and if it is allowed for this . subscriber. Depending on the result, the SGSN may accept the Activate PDP Context Request with the requested or another QoS, or the SGSN rejects the Activate PDP Context Request. If requested by the mobile, the SGSN assigns a dynamic PDP-address. The MS either accepts the negotiated QoS profile, or deactivates the PDP context. 3 In the XID messages, parameters of the LLC and SNDCP layer are negotiated be. tween the mobile and the SGSN.
200
A30808-X3247-M41-4-7618
Information System
1.3.1.4
UL-TBF DL-TBF
DPRQ DPAC
cause
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 attached. Network initiated PDP Context Deactivation is done with reverse message directions.
1.3.1.5
GPRS: Paging
BSC PAPS
SGSN
IMSI, Paging Area, opt. P-TMSI
1 2
In GMM STANDBY status a mobile performs routing area updates but it doesnt inform the network about cell changes. A MS in STANDBY state must be paged by the SGSN before a downlink transfer to that MS is possible. The Paging procedure is used by the network to determine the cell where the mobile is located and moves the GMM state to READY. 1. The SGSN includes the IMSI, information about the area in which the mobile shall be paged and if available a P-TMSI. If included, the BSC shall use the P-TMSI instead of IMSI in the PAGING message on the Um-interface. 2. In response to a GPRS page, the mobile usually sends an unnumbered Information frame (UI). However any other uplink data from the MS can be a valid paging response. The BSC adds the Cell Global Identity (CGI) including RAC and LAC of the cell where the message was received before passing the message to the SGSN.
A30808-X3247-M41-4-7618
201
Information System
1.3.1.6
MS
UL/DL-TBFs (Data)
DTGR UL/DL-Data
UL-TBF
DL-TBF
FLUSH-ACK TLLI
RACO
DTGR UL/DL-Data
A routing area update takes place when a GPRS attached MS detects that it has entered a new RA, when the periodic RA update timer has expired, or when a suspended MS is not resumed by the BSS. 1. In the new cell the mobile sends a Routing Area Update Request including the old Routing Area Identication and the reason for the routing area update. The BSC adds the new Cell Global Identity including RAC and LAC of the cell where the message 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 the old 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.
202
A30808-X3247-M41-4-7618
Information System
3. The SGSN validates the presence of the MS in the new RA. If the MS is not allowed to be attached in the RA due to regional subscription restrictions, or if subscription checking fails, then the SGSN rejects the routing area update with an appropriate cause. If all checks are successful, then the SGSN updates the GMM context for the MS. A new P-TMSI may be allocated. A Routing Area Update Accept (RAAC) is returned to the MS. 4. The MS acknowledges the new P-TMSI by returning a Routing Area Update Complete (RACO). 5. Data transfer is continued in the new routing area.
A30808-X3247-M41-4-7618
203
Information System
1.3.1.7
MS
UL/DL-TBFs (Data)
DTGR UL/DL-Data
UL-TBF (UI)
FLUSH-ACK TLLI
UL/DL-TBFs (Data)
DTGR UL/DL-Data
1. A cell update takes place when the MS enters a new cell inside the current RA and the MS is in READY state. The MS performs the cell update procedure by sending an uplink LLC frame of any type containing the MS identity to the SGSN. Towards the 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 BVC to 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 the SGSN 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.
204
A30808-X3247-M41-4-7618
Information System
1.3.1.8
MS
BSS
SGSN
UL/DL-TBFs (Data)
Circuit switched traffic, e.g. Mobile Originated Call, answer to paging, Location Update
DTGR
UL/DL-Data
CHNREQ
RACH
DTGR
DL-TBF 3
DL-Data
4 SDCCH
DISC
5
RES RESA
CHNREL (Resume) T4
6
UL/DL-TBF
DTGR
UL/DL-Data
A30808-X3247-M41-4-7618
205
Information System
The Suspend / Resume procedure is used to interrupt GPRS data traffic temporarily to allow circuit switched services, e.g. answer to Paging for an incoming call, a periodic Location Update or in our example a Mobile Originating Call. 1. The mobile is transferring data. 2. The mobile leaves the Packet data trafc channels and switches to the BCCH. It requests a signalling channel (SDCCH) by sending CHNREQ on the Random Access Channel. 3. If a downlink TBF is active during this time, it will fail because the mobile is no longer monitoring the PDTCHs. The BSC reports this lost downlink TBF with a Radio Status (RSTA) and the number of not transferred with a LLC-discarded (LLCD) towards the SGSN. 4. The mobile sends a GPRS Suspend Request on the SDCCH. The BSC forwards the Suspend to the SGSN. The call set-up continues. 5. The call ends and the circuit switched resources are released. The BSC includes the resume command towards the mobile in the channel release message and sends in parallel a resume message towards SGSN. 6. Whether data transfer is continued or not depends on the recovery mechanism and time out of the suspended application.
206
A30808-X3247-M41-4-7618
Information System
1.3.2
Inter System Cell Reselection Procedure (2G <--> 3G), packet oriented (PO), intra SGSN inter system change Successful Inter System Cell Reselection Procedure (2G --> 3G)
The inter system change from A/Gb mode to Iu mode takes place when a GPRSattached MS changes from A/Gb mode to GERAN or UTRAN IU mode. Depending on the GPRS mobility management state before the inter system change and whether the Routing Area (RA) is changed or not, one of the following procedures is initiated by the MS: 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 afterwards initiate the Radio Access Bearers (RABs) by the Service Request procedure. The RA update procedure is either combined RA / LA update or only RA update. If the network operated in mode I, an MS that is both PS-attached and CS-attached shall perform the Combined RA / LA Update procedure. This concerns only idle mode (see 3GPP TS 23.122), as no combined RA / LA updates are performed during a CS connection. In the context of this specification, the terms RNS (or RNC) refer also to a GERAN BSS (or BSC) when serving an MS in Iu mode.
1.3.2.1
A30808-X3247-M41-4-7618
207
Information System
MS/ UE
BSC
RNC
2. RARQ 3. ACRQ 3. ACRE 4. Security mode control (command) 4. Security mode control (complete) 5. RAAC 6. RACO 7. MPCR 8. SREQ 8. SACC 9. MPCA 10. RAB assignment (request) 11. RB setup request 11. RB setup complete 12. RAB assignment (response)
208
A30808-X3247-M41-4-7618
Information System
1. The MS or the RAN decides to perform an inter system change which makes the MS switch to a new cell where Iu mode has to be used, and stops transmission to the network. 2. The MS initiates an RRC connection establishment and sends a Routing Area Update (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 or combined 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 a follow on request, i.e. if there is pending uplink trafc (signalling or data). As an implementation option, the SGSN may use the follow-on request indication to release or keep the Iu connection after the completion of the RA update procedure. The SRNS shall add an identier of the area where the message was received before passing the message to the 2G+3G-SGSN. The 2G+3G-SGSN stops transmission of 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 roaming restrictions the MS is not allowed to be attached in the RA, or if subscription checking fails, the 2G+3G-SGSN rejects the RAU with an appropriate cause. If all checks are successful, the 2G+3G-SGSN updates MM and PDP contexts for the MS. 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 derives the corresponding PDCP sequence numbers from the N-PDU sequence numbers stored in the SGSN PDP contexts by adding eight most signicant 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 to the 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 species the requested service. Service Type shall indicate one of the following: Data or Signalling. 9. The MS/UE responds with a Modify PDP context accept to the 2G+3G-SGSN MS -> N. 10. - 12. The 2G+3G-SGSN requests the SRNS to establish a radio access bearer by sending an RAB Assignment Request (RAB ID(s), QoS Prole(s), GTP-SNDs, GTPSNUs, PDCP-SNUs) message to the SRNS. The PDCP sequence numbers are derived 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 the MS. The MS responds with a Radio Bearer Setup Complete (PDCP-SNDs) message. The SRNS responds with a RAB Assignment Response message. Note: The NSAPI value is carried in the RAB ID IE.
A30808-X3247-M41-4-7618
209
Information System
1.3.2.2
210
A30808-X3247-M41-4-7618
Information System
MS/ UE
BSC
RNC
2. RARQ 3. SRNS context request 3. SRNS context response 5. ACRQ 5. ACRE 6. SRNS Data forward command 7. Forward packets 8. Iu Release command 8. Iu Release complete 9. RAAC 10. RACO 11. MPCR 11. MPCA
A30808-X3247-M41-4-7618
211
Information System
1. The MS or the RAN decides to perform an inter system change which makes the MS switch to a new cell where A/Gb mode has to be used, and stops transmission to the network. 2. The MS sends a RAU Request (old RAI, old P-TMSI Signature, Update Type) message to the 2G+3G-SGSN. Update Type shall indicate RAU or combined RA / LA update 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 attach. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the 2G+3GSGSN. 3. If the MS is PMM-CONNECTED state, the 2G+3G-SGSN sends an SRNS Context Request (IMSI) message to the SRNS. 4. Upon reception of the SRNS Context Request message, the SRNS starts buffering and stops sending downlink PDUs to the MS. The SRNS responds with an SRNS Context Response (GTP-SNDs, GTP-SNUs, PDCP-SNDs, PDCP-SNUs) message. The GTP sequence numbers are included for each PDP context indicating the next in-sequence downlink GTP-PDU to be sent to the MS and the next in-sequence GTP PDU to be tunnelled to the GGSN. For each active PDP context which uses lossless PDCP, the SRNS also includes the uplink PDCP sequence number (PDCP-SNU) and the downlink PDCP sequence number (PDCP-SND). PDCP-SNU is the PDCP sequence number for the next expected in-sequence uplink packet to be received from the MS. PDCP-SND is the PDCP sequence number of the rst downlink packet for which successful transmission has not been conrmed. The 2G+3G-SGSN shall take off the eight most signicant bits of the passed PDCP sequence numbers, thus converting them to SNDCP N-PDU numbers of the respective 2G GPRS PDP contexts. 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 to the SRNS. This message informs the SRNS that the 2G+3G-SGSN is ready to receive data packets. Upon reception of SRNS Data Forward Command message from 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 duplicating and tunnelling the buffered GTP-PDUs back to the 2G+3G-SGSN. For each radio bearer which uses lossless PDCP, the GTP-PDUs related to transmitted but not yet acknowledged PDCP-PDUs are duplicated and tunnelled back to the 2G+3G-SGSN. Their related downlink PDCP sequence numbers are sent with them. The 2G+3G-SGSN converts the PDCP sequence numbers to SNDCP sequence numbers by taking off the eight most signicant bits of the PDCP sequence numbers. 8. The 2G+3G-SGSN sends an Iu Release Command message to the SRNS. When the RNC data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message. 9. The 2G+3G-SGSN validates the presence of the MS in the new RA. If due to roaming restrictions the MS is not allowed to be attached in the RA, or if subscription checking fails, the 2G+3G-SGSN rejects the RAU with an appropriate cause. If all checks are successful, the 2G+3G-SGSN updates MM and PDP contexts for the MS. A new P-TMSI may be allocated. A logical link is established between the new 2G+3G-SGSN and the MS. 2G+3G-SGSN initiates the establishment procedure. A RAU Accept (P-TMSI, P-TMSI Signature, Receive N-PDU Number) message is returned to the MS. The Receive N-PDU Number is equal to the converted PDCP-
212
A30808-X3247-M41-4-7618
Information System
SNU. It contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure. All mobile-originated N-PDUs which were successfully transferred before the start of the update procedure are thereby conrmed. If the Receive N-PDU Number conrms the reception of N-PDUs, these NPDUs shall be discarded by the MS. 10. The MS acknowledges the new P-TMSI by returning a RAU Complete (Receive NPDU Number) message to the SGSN. The Receive N-PDU Number is equal to the converted PDCP-SND. It contains the acknowledgements for each NSAPI which used lossless PDCP before the start of the update procedure. All mobile-terminated N-PDUs which were successfully transferred before the start of the update procedure are thereby conrmed. If the Receive N-PDU Number conrms the reception of N-PDUs, these N-PDUs shall be discarded by the 2G+3G-SGSN. The MS deducts Receive N-PDU Number from PDCP-SND by taking off the eight most significant bits. PDCP-SND is the PDCP sequence number for the next expected insequence downlink packet which is received in the MS per radio bearer and which used lossless PDCP. The new 2G-SGSN negotiates the use of acknowledged or unacknowledged SNDCP with the MS for each NSAPI, regardless whether the SRNS used lossless PDCP or not. 11. A Modify PDP context request N -> MS is sent from 2G+3G-SGSN to the MS. The MS responds with a Modify PDP context accept to the 2G+3G-SGSN MS -> N.
1.3.3
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 multislot classes.
A30808-X3247-M41-4-7618
213
Information System
1.3.3.1
Uplink TBF
MS
UL-LLC-Data in MS
BTS
BSC
1
RACH
PCU-UL (PUDCB)
6
PDTCH
RMAC-DL
PCU-DL (PUAN)
(...)
214
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
PCU-UL (PUAN)
PCU-UL (DATA)
BSN=y+1; CV=15
(...)
(...)
RMAC-UL (DATA)
PDTCH
BSN=z; CV=15
PCU-UL (DATA)
BSN=z; CV=15
PCU-UL (DATA)
BSN=z+1; CV=14
(...)
(...)
10
RMAC-UL (PUDCB)
PDTCH
UL Data Repetition
(...)
11 12
RMAC-DL
PCU-UL (PCA)
A30808-X3247-M41-4-7618
215
Information System
Uplink TBF / One Phase Access on CCCH The purpose of the packet access procedure is to establish an uplink TBF to transfer LLC PDUs in the direction from the mobile station to the network. The scenario describes the packet access procedure on CCCH (no PBCCH is configured in the cell). For a GPRS data transfer with a MS not supporting UL Extended TBF or UL Extended TBF not enabled at BSC side. With the one phase access, only a single PDCH can be allocated in the uplink direction, otherwise a two phase access is required. 1. The MS sends a Channel Request message with the establishment cause. For One phase packet access with request for single timeslot uplink transmission; one PDCH is needed (011110xx, 01111x0x, 01111xx0). 2. If no PDCH has been activated, a single timeslot will be congured as PDCH and the Time Alignment procedure is performed. 3. The BSC sends an Immediate Assignment towards the MS. A set of GPRS related parameters is included indicating e.g. the Temporary Flow Identier (TFI), the Uplink State Flag (USF) and the Coding Scheme (CS). 4. Packet Downlink Dummy Control Blocks (PDDCB) with the USF value previously assigned to the MS are transmitted in the allocated PDCH. The MS monitors the USF of all downlink blocks on this timeslot to send its uplink data blocks as response to the occurence of its assigned USF. The PDDCBs continue during the whole uplink TBF - only the rst one is drawn in the message ow! 5. A Mobile might send a Packet Uplink Dummy Control Block (PUDCB) as rst block of an uplink TBF. This is probably because the uplink user data is not yet ready for transmission 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 completed (rst PUAN with TLLI). The data blocks are counted up with the Block Sequence Number BSN (modulo 128). The Countdown Value CV remains at its maximum value as long as more than 15 RLC/MAC data blocks remain to be send. 7. The BSC acknowledges the rst received uplink data block with a Packet Uplink Ack/Nack message (PUAN). As soon as the MS receives this rst PUAN message including its TLLI, the Contention Resolution is completed and the MS continues sending its uplink data blocks without its TLLI inserted. The MS is now clearly identied - concurrent TBF handling according to its multislot capabilities is possible. 8. The BSC acknowledges every single uplink data block received from the mobile with a moving window mechanism. For this purpose the BSC sends every N-th block (N=NRLCMAX; BSS database parameter) a PUAN message indicating which blocks were correctly received or not. Missing blocks will be repeated by the mobile and acknowledged in the next scheduled PUAN message. 9. If the MS has sent most of its uplink data, the Countdown Value CV starts counting down towards the nal block. This allows the network to calculate the remaining blocks of the running uplink TBF. 10. As soon as CV=0 is reached, the MS has transferred all uplink data. The uplink TBF however remains open until the last sent blocks were acknowledged by the BSS. The MS repeats uplink blocks that have been sent already before the nal PUAN is received. 11. The BSC conrms the remaining uplink blocks with the nal PUAN the Final Ack Indication is set. Additionally the MS is polled with the RRBP-bit set to conrm the reception of this nal PUAN.
216
A30808-X3247-M41-4-7618
Information System
12. The Packet Control Ack (PCA) conrms the reception of the previous nal PUAN. Now the uplink TBF is complete and the MS returns to monitor the BCCH.
A30808-X3247-M41-4-7618
217
Information System
1.3.3.2
Downlink TBF
MS
BTS
BSC
DL-LLC-Data on Gb
I (IMASS)
4 5
TS2
PCU-UL (PCA)
TS2
6 7
RMAC-DL (PPCTA) TFI; TA value; TS2 RMAC-DL (DATA) TFI; BSN=1; TS3
PDTCH
PCU-DL (DATA) TFI; BSN=1; TS3 PCU-DL (DATA) TFI; BSN=2; TS1
PDTCH
(...)
PCU-DL (DATA) TFI; BSN=19; TS2; RRBP=1 PCU-DL (DATA) TFI; BSN=20; TS3
(...)
(...)
(...)
218
A30808-X3247-M41-4-7618
Information System
MS
BTS
BSC
RMAC-DL (DATA)
TFI; BSN=z-1
10
RMAC-DL (DATA)
11
RMAC-UL (PDAN)
PACCH
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 GSN must be transferred towards the mobile. This scenario assumes the MS is in GMM ready state, therefore no paging is required or it was already performed including the paging response. For a GPRS data transfer with a MS not supporting UL Extended TBF or UL Extended TBF not enabled at BSC side. 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 congured as PDCH. The actually activated number of timeslots basically depends on the MS capabilities (which are known to the BSC since its GPRS attach), however less timeslots are possible under various circumstances (e.g. trafc load). For each timeslot a separate CHNAV/CHNAK message is required - the timeslot numbers indicated in the message ow are regarded as relative numbers! 3. The BSC sends an Immediate Assignment for a downlink TBF towards the MS. A set of GPRS related parameters is included, indicating e.g. the Temporary Logical Link Identity (TLLI) of the MS and the Temporary Flow Identier (TFI) of the TBF. The IA message is either sent on the AGCH or the PCH - depending if the MS is still in Non-DRX Mode or not. Only a single timeslot can be allocated with the Immediate Assignment message. 4. The MS moves to the allocated PDCH timeslot (according the IA) where it receives the Packet Downlink Assignment (PDAS). This message now allocates all intended downlink 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 conrmation from the MS about the correct reception of the PDAS message.
A30808-X3247-M41-4-7618
219
Information System
5. The MS responds to the polling with a Packet Control Ack (PCA) - the PCA format is 4 access bursts. These access bursts are used by the BSC to calculate the initial timing advance value for the mobile. 6. Downlink data transfer starts on timeslot 1. The MS listens on the assigned 3 timeslots to all downlink blocks with its own TFI, the RLC/MAC blocks are counted up with the Block Sequence Number (BSN). 7. The initial timing advance value is sent to the MS with a Packet Power Control/Timing Advance message (PPCTA). This allows the mobile to transmit (e.g. PDAN) before a continuous timing advance value is available. 8. Every N-th downlink data block (N=NRLCMAX, the default value NRLCMAX=20 is used in case the MS is not the only on the timeslots, otherwise the default value is 15) 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 for uplink 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 received by the MS until the transmission of this PDAN are acknowledged. A moving window mechanism is used. If blocks were not correctly received by the mobile, the BSC will repeat them soon after the reception of the PDAN. The repeated 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 Final Block Indicator bit (FBI) in this last block and polls the MS for a nal PDAN (RRBP=1). 11. The MS conrms the remaining downlink blocks with a PDAN. The Final Ack Indication is set, the downlink TBF is complete and no retransmissions are required. The MS remains on the PDCH and listens for new assignments until the timer T3192 expires. Afterwards it returns to listen to the BCCH. In the example shown above, the DELAyed DL TBF is disabled.
220
A30808-X3247-M41-4-7618
Information System
1.3.3.3
Concurrent UL TBF
MS
BTS
PCU-DL (DATA) TFI; BSN
PDTCH
BSC
(...)
(...) 3
PCU-DL (PDDCB)
(...)
USF; TS2
(...)
PCU-DL (DATA) TFI; BSN; TS1 PCU-DL (DATA) TFI; BSN TS2; USF
PDTCH
RMAC-DL (DATA) TFI; BSN TS2; USF RMAC-DL (DATA) TFI; BSN; TS3
PDTCH (...)
PCU-UL (PDDCB)
TLLI; TS2
A30808-X3247-M41-4-7618
221
Information System
MS
BTS
BSC
PCU-DL (DATA) BSN=0; CV=2; TS2 PCU-DL (DATA) BSN=1; CV=1; TS2 PCU-UL (DATA) PCU-UL (DATA)
(...) PCU-DL (DATA) TFI; BSN; TS1
PDTCH
8 9
(...)
10
PCU-DL (PUAN)
(...)
11
TS2
PCU-UL (PCA)
TS2
12
(...)
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 all applicable blocks can be shown in this message flow.
222
A30808-X3247-M41-4-7618
Information System
Concurrent UL TBF while a DL TBF is actice / Example with a 3+1 Mobile / CCCH only If a downlink TBF is already active and the MS needs to transmit data in uplink direction additionally, a concurrent uplink TBF is initiated. The described scenario occurs frequently for instance in case of a downlink FTP transfer. For a GPRS data transfer with a MS not supporting UL Extended TBF or UL Extended TBF not enabled at BSC side. While the downlink data is transported in a continuously running DL TBF (in our example 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+1 Mobile / CCCH only CAUTION: As the downlink transfer is continuously active during the whole uplink assignment (or even UL TBF), the usual DL message flow continues respectively. Please be aware that not all DL TBF related messages can be inserted in the message flow (please refer to DL TBF only description). 1. 2. LLC data is ready for uplink transmission towards the network. The downlink TBF is running. The MS requests resources for an uplink TBF within the next scheduled Packet Downlink Ack/Nack (PDAN) of the running downlink TBF. For this purpose it adds a Channel Request Description element inside the PDAN message. The BSC sends a Packet Uplink Assignment (PUAS) towards the MS. The Temporary Flow Identifier (TFI), the Uplink State Flag (USF) and the Coding Scheme (CS) are specified. The PUAS is sent on relative timeslot 2 which is used as uplink timeslot in case of a 3+1 MS. The BSC sets the assigned USF in downlink blocks on timeslot 2. 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 for transmission inside the MS. The MS starts sending the uplink user data. The Contention Resolution procedure is not necessary as the MS is aIready clearly identified by the running DL TBF. In our 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. The last uplink block is sent with the Countdown Value (CV) = 0. This indicates the complete transmission of the uplink data and triggers the final Packet Uplink Ack/Nack (PUAN) message. The MS repeats the uplink blocks until the final PUAN has been received by the MS. The BSC sends the final Packet Uplink Ack/Nack (PUAN) and polls the MS to confirm its reception (RRBP=1). A Packet Control Ack (PCA) is sent by the MS as response to the previous polling. The downlink TBF continues solely.
3.
4./5 6.
7.
8.
A30808-X3247-M41-4-7618
223
Information System
1.3.3.4
Concurrent DL TBF
MS
RMAC-DL (PDDCB) USF;TS2
BTS
PCU-DL (PDDCB) USF;TS2
PDTCH
BSC
(...)
(...)
2 3
USF; TS2
RMAC-DL (PDAS)
PCU-DL (PDAS)
RMAC-UL (DATA)
PDTCH
(...) 6
TS2
PCU-UL (PCA)
TS2
(...)
224
A30808-X3247-M41-4-7618
Information System
MS
RMAC-DL (DATA) TFI; BSN=0; TS1
BTS
PCU-DL (DATA)
PDTCH
BSC
TFI; BSN=0; TS1
PCU-DL (DATA)
PCU-DL (DATA)
(...)
(...)
RMAC-DL (DATA)
8
PCU-UL (DATA)
BSN; CV=15
PCU-DL (DATA)
(...)
PCU-UL (PDAN)
(...)
(...) 10
RMAC-DL (DATA)
TFI; BSN=33;...
PDTCH
PCU-DL (DATA)
(...)
RMAC-UL (PDAN)
11
PACCH
PCU-UL (PDAN)
(...)
(...)
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 applicable blocks can be shown in this message flow.
A30808-X3247-M41-4-7618
225
Information System
Concurrent DL TBF while a UL TBF is active / Example with a 3+1 Mobile / CCCH only If an uplink TBF is already running and the MS needs to send data in downlink direction additionally, 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 1 timeslot), the FTP ACKs need to be sent in downlink direction. CAUTION: As the uplink transfer is continuously active during the whole downlink assignment (or even DL TBF), the usual UL message flow continues respectively. Please be 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 relative timeslot 2 is already used for the uplink transfer because an uplink FTP is already running for a longer time. In case the uplink TBF was just opened on the relative timeslot 1 and a first concurrent downlink TBF is required, the system will send a Packet Timeslot Reconfigure message (PTR) instead of the PDAS (see below). This because the position of the running uplink TBF must be moved to the relative timeslot 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 Identifier (TFI) to the MS (TLLI). Additionally the poll bit is set (RRBP=1) - the BSC requests a confirmation from the MS about the correct reception of the PDAS message. 6. The MS responds to the polling with a Packet Control ACK (PCA) in the reserved uplink block. The uplink TBF is meanwhile ongoing. 7. The BSC starts sending the downlink data blocks of the new TBF. The DL data blocks 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 Downlink ACK/NACK message (PDAN). (N=NRLCMAX,the default value NRLCMAX=20 is used in case the MS is not the only on the timeslots, otherwise the default value is 15, therefore the downlink data block with BSN=19 polls the MS). Due to the polling this block must be sent on TS 2 even if a different NRLCMAX value suggests another timeslot. UL allocation is meant as to avoid also DL function, so PUAS can be sent. Instead, if MS request in UL creates a final allocation with impacts on DL, the message sent to MS on TS2 is a PTR (Packet Timeslot Reconfigure). 9. The PDAN message from the MS is received in the reserved uplink radio block. All RLC/MAC data blocks successfully received by the MS until the transmission of this 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 previous sequence. 11. The final PDAN confirms all remaining RLC/MAC blocks of the downlink TBF.
226
A30808-X3247-M41-4-7618
Information System
A30808-X3247-M41-4-7618
227
Information System
228
A30808-X3247-M41-4-7618
Information System
-CCC CCONF CHMM CHMMACK CHNAK CHNAV CHNRD CHNREQ CHREL CICMD CICMP CIMCMD CIMCMP CLAMCH CLCH CL CMD CONNECTION CONFIRM CALL CONFIRMED CHANNEL MODE MODIFY CHANNEL MODE MODIFY ACKNOWLEDGE CHANNEL ACTIVATION ACKNOWLEDGE CHANNEL ACTIVATION CHANNEL REQUIRED CHANNEL REQUEST CHANNEL RELEASE CIPHER MODE COMMAND CIPHER MODE COMPLETE CIPHERING MODE COMMAND CIPHERING MODE COMPLETE CLASSMARK CHANGE CLASSMARK CHANGE CLEAR COMMAND SCCP Message DTAP Message DTAP Message DTAP Message Abis RSL Message Abis RSL Message Abis RSL Message Um Message DTAP Message BSSMAP Message BSSMAP Message DTAP Message DTAP Message DTAP Message Abis RSL Message BSSMAP Message
A30808-X3247-M41-4-7618
229
Information System
Abbreviation CL CMP CLUPD CL REQ CL3I CMSACC CMSREQ COIN (BSC->SMLC) CONACK CONNECT CPACK CPDAT CPROC CR CREF -DDATIN DATRQ DELIN DESAC DISC DISC DM DTAP
Long Name CLEAR COMPLETE CLASSMARK UPDATE CLEAR REQUEST COMPLETE LAYER 3 INFORMATION CM SERVICE ACCEPT CM SERVICE REQUEST CONNECTION ORIENTED INFORMATION CONNECT ACKNOWLEDGE CONNECT SHORT MESSAGE CP-ACK SHORT MESSAGE CP-DATA CALL PROCEEDING CONNECTION REQUEST CONNECTION REFUSED
Type BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message DTAP Message DTAP Message BSSMAP-LE Message DTAP Message DTAP Message DTAP Message DTAP Message DTAP Message SCCP Message SCCP Message
DATA INDICATION DATA REQUEST DELETE INDICATION DEACTIVATE SACCH DISCONNECT DISCONNECT DISCONNECT MODE DIRECT TRANSFER APPLICATION PART
DT1 -EEMSETUP ENCRY ERIN ESTCN ESTIN ESTRQ E-TA_REQ (SMLC->BSC) E-TA_RES (BSC->SMLC)
DATA FORM 1
Abis RSL Message Abis RSL Message Abis RSL Message Abis RSL Message DTAP Message Um layer 2 Message Um layer 2 Message Protocol (MS<->BSC, MS<->MSC) SCCP Message
EMERGENCY SETUP ENCRYPTION COMMAND ERROR INDICATION ESTABLISH CONFIRM ESTABLISH INDICATION ESTABLISH REQUEST TIMING ADVANCE REQUEST TIMING ADVANCE RESPONSE
DTAP Message Abis RSL Message Abis RSC Message Abis RSL Message Abis RSL Message Abis RSL Message BSSLAP Message BSSLAP Message
230
A30808-X3247-M41-4-7618
Information System
Long Name
Type
-HHANDO HO CMD HO CMP HO DET HO FAIL HO FAI HO PER HO RAC HO REQ HO RQD HO RRJ HR -II IACMD IMASS IMASSRJ IMDETIN IMSETUP ISHUTRAN -JINFORMATION IMMEDIATE ASSIGN COMMAND IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT REJECT IMSI DETACH INDICATION IMMEDIATE SETUP MESSAGE INTER SYSTEM HANDOVER TO UTRAN Um layer2 Message Abis RSL Message DTAP Message DTAP Message DTAP Message BSSMAP Message DTAP-RR Message HANDOVER DETECTION HANDOVER COMMAND HANDOVER COMPLETE HANDOVER DETECT HANDOVER FAILURE HANDOVER FAILURE HANDOVER PERFORMED HANDOVER REQUEST ACKNOWLEDGE HANDOVER REQUEST HANDOVER REQUIRED HANDOVER REQUIRED REJECT HALF RATE Abis RSL Message DTAP Message DTAP Message BSSMAP Message DTAP Message BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message Speech Version
-K-
A30808-X3247-M41-4-7618
231
Information System
Abbreviation -LLCSREQ (BSC->BTS) LCSRRES (BTS->BSC) LUACC LUREQ -MMEAS REP MESRS MOMAK MOMRQ MPCA MPCR MRPCI MSIT -NNCH NOTCMD -OOVERLOAD -PPAGIN PAGREQ PAGRES PAREA PAREQ PCH PGCMD PHCCN PHCRQ PLRQ (MSC->BSC) PLRQ (BSC->SMLC) PLRS (BSC->MSC) PLRS (SMLC->BSC) PROGRES OVERLOAD
Long Name
Type
LOCATION BASED SERVICES REQUEST LOCATION BASED SERVICES RESPONSE LOCATION UPDATING ACCEPT LOCATION UPDATING REQUEST
MEASUREMENT REPORT MEASUREMENT RESULT MODE MODIFY ACKNOWLEDGE MODE MODIFY REQUEST MODIFY PDP CONTEXT ACCEPT MS -> N MODFY PCP CONTEXT REQUEST N -> MS MS RF POWER CAPABILITY INDICATION MSC INVOKE TRACE
Um Message Abis RSL Message Abis RSL Message Abis RSL Message GMM (GPRS MM/SM) Message GMM (GPRS MM/SM) Message Abis RSL Message BSSMAP Message
UM Channel SRSL
PAGING PAGING REQUEST PAGING RESPONSE PREFERRED AREA PREFERRED AREA REQUEST PAGING CHANNEL PAGING COMMAND PHYSICAL CONTEXT CONFIRM PHYSICAL CONTEXT REQUEST PERFORM LOCATION REQUEST PERFORM LOCATION REQUEST PERFORM LOCATION RESPONSE PERFORM LOCATION RESPONSE PROGRESS
BSSMAP Message Um Message DTAP Message Abis RSL Message Abis RSL Message Um Channel Abis RSL Message Abis RSL Message Abis RSL Message BSSMAP Message BSSMAP-LE Message BSSMAP Message BSSMAP-LE Message DTAP Message
232
A30808-X3247-M41-4-7618
Information System
Abbreviation -QQUIND -RRAAC RACH RACO RARQ RCHRA RCHRL RELCMP RELCN RELEAS RELIN RELRQ RESET RESIN RETRACK RETRV RLC RLSD RPAC RPDA RSL -SSABM SACC SACFL SACCH SAPI SBCCM SCCP SDCCH SETUP SPDACK SPDTMF SREQ STDACK STDTMF STRAC
Long Name
Type
QUEUING INDICATION
BSSMAP Message
ROUTING AREA UPDATE ACCEPT RANDOM ACCESS CHANNEL ROUTING AREA UPDATE COMPLETE ROUTING AREA UPDATE REQUEST RF CHANNEL RELEASE ACKNOWLEDGE RF CHANNEL RELEASE RELEASE COMPLETE RELEASE CONFIRM RELEASE RELEASED INDICATION RELEASE REQUEST RESET RF RESOURCE INDICATION RETRIEVE ACKNOWLEDGE RETRIEVE RELEASE COMPLETE RELEASED RP-ACK RP-DATA RADIO SIGNALLING LINK
GMM (GPRS MM/SM) Message Um Channel GMM (GPRS MM/SM) Message GMM (GPRS MM/SM) Message Abis RSL Message Abis RSL Message DTAP Message Abis RSL Message DTAP Message Abis RSL Message Abis RSL Message BSSLAP Message Abis RSL Message DTAP Message DTAP Message SCCP Message SCCP Message SMRP Message SMRP Message Abis-Protocol
SET ASYNCHRONOUS BALANCED MODE SERVICE ACCEPT SACCH FILLING SLOW ASSOCIATED CONTROL CHANNEL SERVICE ACCESS POINT IDENTIFIER SMS BROADCAST COMMAND SIGNALLING CONNECTION CONTROL PART STAND ALONE DEDICTED CONTROL CHANNEL SETUP STOP DTMF ACKNOWLEDGE STOP DTMF SERVICE REQUEST START DTMF ACKNOWLEDGE START DTMF START TRACE
Um layer2 Message GMM (GPRS MM/SM) Message Abis RSL Message Um Channel LAPD Addressing ID Abis RSL Message CCS7 User Part Um Channel DTAP Message DTAP Message DTAP Message GMM (GPRS MM/SM) Message DTAP Message DTAP Message Abis RSL Message
A30808-X3247-M41-4-7618
233
Information System
Abbreviation STRACACK -TTALKDET TALKIND TAREQ (SMLC->BSC) TARSP (BSC->SMLC) TCH TMEASRES TRCMD TRCMP -UUA UDT UI UPCF UPLACC UPLGRT UPLINKBUSY UPLINKFREE UPLREL UPRA UPRC UPRI UPRQ UPSC UTRANCC -VVVAR VVRQ VVS VVSA -WWIHCI
TALKER DETECT MESSAGE TALKER INDICATION MESSAGE TIMING ADVANCE REQUEST TIMING ADVANCE RESPONSE TRAFFIC CHANNEL TRACE MEASUREMENT RESULTS TMSI REALLOCATION COMMAND TMSI REALLOCATION COMPLETE
DTAP Message DTAP Message BSSLAP Message BSSLAP Message Um Channel Abis RSL Message DTAP Message DTAP Message
UNNUMBERED ACKNOWLEDGEMENT UNIT DATA UNNUMBERED INFORMATION UPLINK REQUEST CONFIRM MESSAGE UPLINK ACCESS UPLINK GRANT MESSAGE UPLINK BUSY MESSAGE UPLINK FREE MESSAGE UPLINK RELEASE UPLINK REQUEST ACKNOWLEDGE UPLINK RELEASE COMMAND UPLINK RELEASE INDICATION UPLINK REQUEST MESSAGE UPLINK SEIZED COMMAND UTRAN CLASSMARK CHANGE
Um layer2 Message SCCP Message Um layer2 Message BSSMAP Message DTAP DTAP DTAP DTAP DTAP BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message BSSMAP Message Abis RSL Message
VGCS ASSIGNMENT RESULT VGCS ASSIGNMENT REQUEST MESSAGE VGCS SETUP MESSAGE VGCS SETUP ACKNOWLEDGE
234
A30808-X3247-M41-4-7618
Information System
3
BSC BSIC
Abbreviations
Base Station Controller Base Station Identity Code BSS LCS Assistance Protocol BSS Management Application Part Base Transceiver Station Cell Identifier This BSC DB parameter represents the flag to enable the transmission of the Cell Identifier (CI) and Timing Advance (TA) to MSC. enhanced Multi-Level Procedure and Preemption General Packet Radio Services This BSC DB enables LCS NSS centric solution. For LCS BSS centric solution it must be always set to FALSE. Mobile Station Mobile-Services Switching Center Mobile Terminating Location Request Network Induced Location Request Siemens Base Station System SET PARAMETER Set Information Type 10 Serving Mobile Location Center Set System Info 10 Timing Advance TERMINATION TERMINATION REQUEST Temporary Mobile Subscriber Identity Unit Data Request Uplink Request Confirm Uplink Request CMD Uplink Seized Command
MS MSC MT-LR NI-LR SBS SETPAR SIT10 SMLC SSI10 TA TERM TERMREQ TMSI UDTRQ URC URLC USC
A30808-X3247-M41-4-7618
235
Information System
236
A30808-X3247-M41-4-7618