Anda di halaman 1dari 88

Messages Reference

MF001002 BSS ISSUE1.0

Content
Chapter 1 A-Interface Key Messages...........................................................................................4 1.1 Message Contents.............................................................................................................4 1.1.1 ASSIGNMENT REQUEST.......................................................................................4 1.1.2 ASSIGNMENT COMPLETE....................................................................................5 1.1.3 ASSIGNMENT FAILURE.........................................................................................6 1.1.4 HANDOVER REQUEST..........................................................................................7 1.1.5 HANDOVER REQUEST ACKNOWLEDGE.............................................................9 1.1.6 HANDOVER REQUIRED.......................................................................................10 1.1.7 HANDOVER REQUIRED REJECT........................................................................11 1.1.8 HANDOVER COMMAND.......................................................................................11 1.1.9 HANDOVER COMPLETE......................................................................................11 1.1.10 HANDOVER FAILURE .......................................................................................12 1.1.11 HANDOVER PERFORMED.................................................................................13 1.1.12 PAGING..............................................................................................................13 1.1.13 CLEAR REQUEST..............................................................................................14 1.1.14 CLEAR COMMAND.............................................................................................14 1.1.15 CLASSMARK REQUEST....................................................................................15 1.1.16 CLASSMARK UPDATE.......................................................................................15 1.1.17 CIPHER MODE COMMAND................................................................................16 1.1.18 CIPHER MODE COMPLETE...............................................................................16 1.1.19 CIPHER MODE REJECT.....................................................................................16 1.1.20 COMPLETE LAYER 3 INFORMATION................................................................17 1.2 Signaling element coding.................................................................................................17 1.3 Message Type.................................................................................................................19 1.3.1 Channel Type........................................................................................................21 1.3.2 Layer 3 Header Information...................................................................................28 1.3.3 Priority...................................................................................................................29 1.3.4 Circuit Identity Code..............................................................................................30 1.3.5 Downlink DTX Flag................................................................................................31 1.3.6 Interference Band To Be Used...............................................................................31 1.3.7 Classmark Information Type 2...............................................................................31 1.3.8 Group Call Reference............................................................................................32 1.3.9 Talker Flag............................................................................................................32 1.3.10 LSA Access Control Suppression........................................................................32 1.3.11 RR Cause............................................................................................................33 1.3.12 Cell Identifier.......................................................................................................33 1.3.13 Chosen Channel..................................................................................................35

MF001002 BSS ISSUE1.0

1.3.14 Chosen Encryption Algorithm...............................................................................36 1.3.15 Circuit Pool..........................................................................................................36 1.3.16 Speech Version...................................................................................................40 1.3.17 LSA Identifier.......................................................................................................40 1.3.18 Cause..................................................................................................................41 1.3.19 Circuit Pool List....................................................................................................43 1.3.20 Encryption Information.........................................................................................44 1.3.21 Classmark Information Type 1.............................................................................45 1.3.22 Classmark Information Type 3.............................................................................45 1.3.23 Current Channel Type 1.......................................................................................45 1.3.24 LSA Information...................................................................................................46 1.3.25 Old BSS to New BSS information........................................................................48 1.3.26 Configuration Evolution Indication........................................................................48 1.3.27 Response Request..............................................................................................49 1.3.28 Cell Identifier List.................................................................................................49 1.3.29 Queuing Indicator................................................................................................53 1.3.30 Layer 3 Information..............................................................................................53 1.3.31 IMSI.....................................................................................................................53 1.3.32 TMSI ...................................................................................................................54 1.3.33 Channel Needed..................................................................................................54 1.3.34 eMLPP Priority.....................................................................................................54 1.3.35 Cipher Response Mode.......................................................................................55 1.3.36 Layer 3 Message Contents..................................................................................55 1.3.37 LSA Identifier List................................................................................................55 1.3.38 APDU..................................................................................................................56 Chapter 2 Abis-Interface Key Messages....................................................................................57 2.1 Message Contents...........................................................................................................57 2.1.1 CHANNEL REQUIRED..........................................................................................57 2.1.2 PAGING COMMAND.............................................................................................58 2.1.3 CHANNEL ACTIVATION.......................................................................................58 2.1.4 CHANNEL ACTIVATION ACKNOWLEDGE...........................................................60 2.1.5 CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE........................................60 2.1.6 IMMEDIATE ASSIGN COMMAND.........................................................................61 2.1.7 CONNECTION FAILURE INDICATION.................................................................61 2.1.8 ERROR INDICATION............................................................................................61 2.1.9 ENCRYPTION COMMAND...................................................................................62 2.1.10 HANDOVER DETECTION...................................................................................62 2.1.11 MODE MODIFY...................................................................................................62 2.1.12 MODE MODIFY ACKNOWLEDGE......................................................................63 2.1.13 MODE MODIFY NEGATIVE ACKNOWLEDGE....................................................63 2.1.14 ESTABLISH INDICATION...................................................................................64 2.2 Signaling element coding.................................................................................................65

ii

MF001002 BSS ISSUE1.0

2.2.1 Message discriminator...........................................................................................65 2.2.2 MESSAGE TYPE..................................................................................................66 2.2.3 Channel Number...................................................................................................67 2.2.4 Request Reference................................................................................................68 2.2.5 Access Delay.........................................................................................................68 2.2.6 Physical Context....................................................................................................68 2.2.7 Paging Group........................................................................................................69 2.2.8 MS Identity............................................................................................................69 2.2.9 Channel Needed....................................................................................................69 2.2.10 eMLPP Priority.....................................................................................................70 2.2.11 Activation Type....................................................................................................70 2.2.12 Channel Mode.....................................................................................................71 2.2.13 Channel Identification..........................................................................................73 2.2.14 Encryption information.........................................................................................73 2.2.15 Handover reference.............................................................................................74 2.2.16 BS Power............................................................................................................74 2.2.17 MS Power............................................................................................................75 2.2.18 Timing Advance...................................................................................................75 2.2.19 MS Power Parameters.........................................................................................76 2.2.20 BS Power Parameters.........................................................................................76 2.2.21 SACCH Information.............................................................................................76 2.2.22 UIC......................................................................................................................77 2.2.23 Main channel reference.......................................................................................78 2.2.24 MultiRate configuration........................................................................................78 2.2.25 MultiRate Control.................................................................................................78 2.2.26 Supported Code Types........................................................................................79 2.2.27 Frame Number....................................................................................................81 2.2.28 Cause.................................................................................................................81 2.2.29 Full Immediate Assign Info...................................................................................84 2.2.30 Link Identifier.......................................................................................................85 2.2.31 RLM Cause.........................................................................................................85 2.2.32 L3 Information (message name)..........................................................................86

iii

Messages Reference

Chapter 2 Abis-Interface Key Messages

Chapter 1 A-Interface Key Messages


There is no general rule for the order of signaling elements: it happens that the same elements appear in various orders depending on the message. The messages of Ainterface described here are based on Phase 2+ GSM 0808 version 7.6.0 Release 1998. The key BSSMAP messages are listed in the following table:
Message name ASSIGNMENT REQUEST ASSIGNMENT COMPLETE ASSIGNMENT FAILURE HANDOVER REQUEST HANDOVER REQUEST ACKNOWLEDGE HANDOVER REQUIRED HANDOVER REQUIRED REJECT HANDOVER COMMAND HANDOVER COMPLETE HANDOVER FAILURE HANDOVER PERFORMED PAGING CLEAR REQUEST CLEAR COMMAND CLASSMARK REQUEST CLASSMARK UPDATE CIPHER MODE COMMAND CIPHER MODE COMPLETE CIPHER MODE REJECT COMPLETE LAYER 3 INFORMATION Reference 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9 1.1.10 1.1.11 1.1.12 1.1.13 1.1.14 1.1.15 1.1.16 1.1.17 1.1.18 1.1.19 1.1.20

1.1 Message Contents


1.1.1 ASSIGNMENT REQUEST
This message is sent from the MSC to the BSS via the relevant SCCP connection in order to request the BSS to assign radio resource(s), the attributes of which are defined within the message. The message may also include the terrestrial circuit to be used.
INFORMATION ELEMENT Message Type Channel Type Layer 3 Header Information Priority Circuit Identity Code REFERENCE DIRECTION 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS TYPE M M O (3) O O (1) LEN 1 5-10 4 3 3

Messages Reference

Chapter 2 Abis-Interface Key Messages

INFORMATION ELEMENT Downlink DTX Flag Interference Band To Be Used Classmark Information 2 Group Call Reference Talker Flag LSA Access Control Suppression

REFERENCE DIRECTION 1.2.6 1.2.7 1.2.8 1.2.9 1.2.10 1.2.11 MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS

TYPE O O O O O O (2) (4) (5) (6) (8) 2 2 4-5 3-8 1 2

LEN

1. This element is included when the MSC allocates the A-interface circuits and the channel type Information Element indicates speech or data, and only in those cases. 2. This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS. 3. This information element doesnt serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message. 4. These elements may be included if the information is known by the MSC. 5. This may be included by the MSC for either a talking or listening subscriber in a group call. 6. This information element is included for group calls, when this is included it indicates that the mobile is a talker in the call else the mobile is a listener. 7. The information is indicated by the MSC if known. 8. This information element is included if LSA access control function shall be suppressed in the BSS.

1.1.2 ASSIGNMENT COMPLETE


The ASSIGNMENT COMPLETE message is sent from the BSS to the MSC and indicates that the requested assignment has been completed correctly. The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT Message Type RR Cause Circuit Identity Code Cell Identifier Chosen Channel Chosen Encryption Algorithm Circuit Pool Speech Version (Chosen) LSA Identifier REFERENCE DIRECTION 1.2.1 1.2.12 1.2.5 1.2.13 1.2.14 1.2.15 1.2.16 1.2.17 1.2.18 BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M O O (4) O (1) O (3) O (5) O (2) O (6) O (7) LEN 1 2 3 3-10 2 2 2 2 5

Messages Reference

Chapter 2 Abis-Interface Key Messages

1. The cell identifier is used to indicate a new cell, if during the assignment the serving cell has changed. 2. Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the ASSIGNMENT REQUEST message. 3. Included at least when the channel rate/type choice was done by the BSS. 4. The Circuit Identity Code information element is included mandatory by the BSS if the BSS allocates the A-interface circuits and a circuit is needed. 5. Included at least when the encryption algorithm has been changed by the BSS. 6. Included at least when the speech version choice was done by the BSS. 7. Shall be included if current LSA in the serving cell has been identified (see GSM 03.73). Not included means that there is no current LSA in the serving cell.

1.1.3 ASSIGNMENT FAILURE


The ASSIGNMENT FAILURE message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that there has been a failure in the assignment process at the BSS and that the assignment procedure has been aborted.
INFORMATION ELEMENT Message Type Cause RR Cause Circuit Pool Circuit Pool List REFERENCE 1.2.1 1.2.19 1.2.12 1.2.16 1.2.20 DIRECTIO TYPE N BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC M M O O (1) O (2) 1 3-4 2 2 V LEN

1. Shall be included when several circuit pools are present on the BSS MSC interface. 2. May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences. Typical Cause values are: - radio interface message failure, - O and M intervention, - equipment failure, - no radio resource available, - requested terrestrial resource unavailable,

Messages Reference

Chapter 2 Abis-Interface Key Messages

- requested transcoding/rate adaption unavailable, - terrestrial resource already allocated, - invalid message contents, - radio interface failure - reversion to old channel, - directed retry, - circuit pool mismatch, - switch circuit pool. requested speech version unavailable.

1.1.4 HANDOVER REQUEST


This message is sent from the MSC to the BSS via the relevant SCCP connection to indicate that the MS is to be handed over to that BSS.
INFORMATION ELEMENT Message Type Channel Type Encryption Information Classmark Information 1 Or Classmark Information 2 Cell Identifier (Serving) Priority Circuit Identity Code Downlink DTX Flag Cell Identifier (Target) Interference Band To Be Used Cause Classmark Information 3 Current Channel type 1 Speech Version (Used) Group Call Reference Talker Flag Configuration Evolution Indication Chosen Encryption Algorithm (Serving) Old BSS to New BSS Information LSA Information LSA Access Control Suppression REFERENCE DIRECTIO N 1.2.1 1.2.2 1.2.21 1.2.22 1.2.8 1.2.13 1.2.4 1.2.5 1.2.6 1.2.13 1.2.7 1.2.19 1.2.23 1.2.24 1.2.17 1.2.9 1.2.10 1.2.27 1.2.15 1.2.26 1.2.25 1.2.11 MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS TYPE M M M (1) M# M (6) M O O (7) O (3) M O O (9) O (4) O (8) O (10) O (5) O (11) O (12) O (2) LEN 1 5-10 3-n 2 4-5 5-10 3 3 2 3-10 2 3-4 3-14 2 2 3-8 1 2 2

O(13) 2-n O(14) 3+4n O (15) 2

1. If the MSC has not sent a CIPHER MODE COMMAND for this RR connection (or has had all such CIPHER MODE COMMANDs rejected with CIPHER MODE REJECT messages) then the MSC shall indicate that the only permitted algorithm is no encryption. 2. If this information element is included, it shall be equal to the last received Chosen
7

Messages Reference

Chapter 2 Abis-Interface Key Messages

Encryption Algorithm information element. 3. This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS. 4. This element is included if the MSC has received such information. 5. This element is included if the MS is in a voice broadcast or voice group call. 6. One of these two elements is sent. 7. This element is included when the channel type Information Element indicates speech or data, and only in those cases. 8. This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a Current channel type 1 information element. In this case it shall be equal to the received element. 9. This information element should always be included. Its cause value should be the same as indicated in the corresponding Handover Required message. 10. This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a Speech version (used) information element. In this case it shall be equal to the received element. 11. This information element is included for voice group call, when this is included it indicates that the mobile is a talker in the call else the mobile is a listener. 12. The information is indicated by the MSC if known 13. This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing an old BSS to new BSS information information element. Its contents shall be equal to the received element. 14. This information element is included when the subscriber has localized service area support. 15. This information element is included if LSA access control function shall be suppressed in the BSS. Typical Cause values are: - uplink quality, - uplink strength, - downlink quality, - downlink strength - distance,

Messages Reference

Chapter 2 Abis-Interface Key Messages

- better cell, - response to MSC invocation - O and M intervention, - directed retry, - switch circuit pool, - traffic, - preemption.

1.1.5 HANDOVER REQUEST ACKNOWLEDGE


This message is sent from the BSS to the MSC and indicates that the request to support a handover at the target BSS can be supported by the BSS, and also to which radio channel(s) the MS should be directed. The message is sent via the BSSAP SCCP connection associated with the dedicated resource.
INFORMATION ELEMENT Message Type Layer 3 Information Chosen Channel Chosen Encryption Algorithm Circuit Pool Speech Version (Chosen) Circuit Identity Code LSA Identifier REFERENCE 12.1 1.2.3 1.2.14 1.2.15 1.2.16 1.2.17 1.2.5 1.2.18 DIRECTION BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M 1 M (1) 11-n O (4) 2 O (5) 2 O O O O (2) (6) (3) (7) 2 2 3 5 LEN

1. This information field carries a radio interface HANDOVER COMMAND message. 2. Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the HANDOVER REQUEST message. 3. The Circuit identity code information element is included mandatory by the BSS if the BSS allocates the A-interface circuits and a circuit is needed. 4. Included at least when the channel rate/type choice was done by the BSS. 5. Included at least when the encryption algorithm has been selected by the BSS. 6. Included at least when the speech version choice was done by the BSS. 7. Shall be included if a new potential current LSA in the target cell has been identified (see GSM 03.73). Not included means that there is no potential current LSA in the target cell.
9

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.1.6 HANDOVER REQUIRED


This message is sent from the BSS to the MSC to indicate that for a given MS which already has dedicated radio resource(s) assigned, a handover is required for the reason given by the cause element. The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT Message Type Cause Response Request Cell Identifier List (Preferred) Circuit Pool List Current Channel Type 1 Speech Version (Used) Queuing Indicator Old BSS to New BSS Information REFERENCE 1.2.1 1.2.19 1.2.28 1.2.29 DIRECTION BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M M O M LEN 1 3-4 1 2n+3 to 7n+3 V 2 2 2 2-n

1.2.20 1.2.24 1.2.17 1.2.30 1.2.26

BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC

O (1) O (2) O (3) O O

1. Shall be included when cause "switch circuit pool" and the MSC allocates the Ainterface circuit. 2. This information element should always be included. 3. This information element should always be included when the channel mode is speech, and only in this case. Typical Cause values are: - uplink quality, - uplink strength, - downlink quality, - downlink strength, - distance, - better cell, - response to MSC invocation, - O&M intervention, - directed retry, - switch circuit pool, - traffic,

10

Messages Reference

Chapter 2 Abis-Interface Key Messages

- preemption.

1.1.7 HANDOVER REQUIRED REJECT


This message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the BSS that the HANDOVER REQUIRED message has not resulted in handover.
INFORMATION ELEMENT Message Type Cause REFERENCE 1.2.1 1.2.19 DIRECTIO N MSC-BSS MSC-BSS TYPE M M 1 3-4 LEN

Typical Cause values are: - equipment failure, - no radio resource available, - requested terrestrial resource unavailable, - invalid message contents, - requested transcoding/rate adaptation unavailable, - O and M intervention.

1.1.8 HANDOVER COMMAND


This message is sent from the MSC to the BSS via the relevant SCCP connection and contains the target channel to which the MS should retune.
INFORMATION ELEMENT Message Type Layer 3 Information Cell Identifier REFERENCE 1.2.1 1.2.31 1.2.13 DIRECTION MSC-BSS MSC-BSS MSC-BSS TYPE M M (1) O LEN 1 11-n 3-10

This information field carries a radio interface HANDOVER COMMAND message.

1.1.9 HANDOVER COMPLETE


This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that the correct MS has successfully accessed the target cell.
INFORMATION ELEMENT Message Type REFERENCE 1.2.1 DIRECTION BSS-MSC TYPE M 1 LEN

11

Messages Reference RR Cause 1.2.12

Chapter 2 Abis-Interface Key Messages BSS-MSC O 2

1.1.10 HANDOVER FAILURE


This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates to the MSC that there has been a failure in the resource allocation process on handover, and that the handover has been aborted.
INFORMATION ELEMENT Message Type Cause RR Cause Circuit Pool Circuit Pool List REFERENC DIRECTION E 1.2.1 1.2.19 1.2.12 1.2.16 1.2.20 BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M M O O (1) O (2) LEN 1 3-4 2 2 V

1. Shall be included when several circuit pools are present on the BSS MSC interface. 2. May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences. Typical Cause values are: - radio interface message failure; - O and M intervention; - Equipment failure; - no radio resource available; - requested terrestrial resource unavailable; - requested transcoding/rate adaption unavailable; - terrestrial resource already allocated; - invalid message contents; - radio interface failure - reversion to old channel; - ciphering algorithm not supported; - circuit pool mismatch; - switch circuit pool; - requested speech version unavailable.

12

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.1.11 HANDOVER PERFORMED


This message is sent from the BSS to the MSC in order to indicate that the BSS has performed an internal handover. The cell identifier and (if required for O and M reasons) optionally the new channel identity is included. The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT Message Type Cause Cell Identifier Chosen Channel Chosen Encryption Algorithm Speech Version (Chosen) LSA Identifier REFERENCE 1.2.1 1.2.19 1.2.13 1.2.14 1.2.15 1.2.17 1.2.18 DIRECTION BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M M M O (1) O (2) O (3) O (4) LEN 1 3-4 3-10 2 2 2 5

1. Included at least when the channel rate/type has changed during the handover. 2. Included at least when the encryption algorithm has been changed by the BSS. 3. Included at least when the speech version has been changed by the BSS. 4. Shall be included if current LSA in the new serving cell has been identified (see GSM 03.73). Not included means that there is no current LSA in the new serving cell. Typical Cause values: as for the handover required message, except response to MSC invocation.

1.1.12 PAGING
This message is sent from the MSC to the BSS and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. This message is sent as a connectionless SCCP message.
INFORMATION ELEMENT Message Type IMSI TMSI Cell Identifier List Channel Needed eMLPP Priority REFERENCE DIRECTION 1.2.1 1.2.32 1.2.33 1.2.29 1.2.34 1.2.35 MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS MSC-BSS TYPE M M O (1) M O (2) O (3) LEN 1 3-10 6 3 to 3+7n 2 2

1. This element is omitted in the exceptional case where the IMSI is used instead of the

13

Messages Reference

Chapter 2 Abis-Interface Key Messages

TMSI as a paging address at the radio interface. 2. If the channel needed element is not present, the default value is assumed to be 00 (any channel). 3. If the BSS implements the eMLPP feature it should use this information element to build the radio interface Paging request messages, otherwise the information may be considered as an unrecognisable information element.

1.1.13 CLEAR REQUEST


This message is sent from the BSS to the MSC to indicate to the MSC that the BSS wishes to release the associated dedicated resource(s). The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT Message Type Cause REFERENCE 1.2.1 1.2.19 DIRECTION BSS-MSC BSS-MSC TYPE M M LEN 1 3-4

Typical Cause values are: - radio interface message failure, - O and M intervention, - equipment failure, - Joined group call channel, - protocol error between BSS and MSC, - preemption.

1.1.14 CLEAR COMMAND


This message is sent from the MSC to the BSS to instruct the BSS to release the associated dedicated resource(s). The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT Message Type Layer 3 Header Information Cause REFERENCE 1.2.1 1.2.3 1.2.19 DIRECTION MSC-BSS MSC-BSS MSC-BSS TYPE M O (1) M LEN 1 4 3-4

14

Messages Reference

Chapter 2 Abis-Interface Key Messages

This information element doesnt serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message. Typical Cause values are: - call control, - O and M intervention, - equipment failure, - handover successful, - protocol error between BSS and MSC.

1.1.15 CLASSMARK REQUEST


This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It requests an update of the classmark parameters for the concerned MS.
INFORMATION ELEMENT Message Type REFERENCE 1.2.1 DIRECTIO TYPE N MSC-BSS M 1 LEN

1.1.16 CLASSMARK UPDATE


This message is sent from the BSS to the MSC or from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the classmark parameters for the concerned MS.
INFORMATION ELEMENT Message Type Classmark Information Type 2 Classmark Information Type 3 REFERENCE 1.2.1 1.2.8 1.2.23 DIRECTION Both Both Both M M O (1) TYPE LEN 1 4-5 3-14

This element shall be included by the BSS if it was received from the MS. It shall be included by the MSC if this information element has previously been received by the MSC.

15

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.1.17 CIPHER MODE COMMAND


This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the encryption parameters for the concerned MS.
INFORMATION ELEMENT Message Type Layer 3 Header Information Encryption Information Cipher Response Mode REFERENCE 1.2.1 1.2.3 1.2.21 1.2.36 DIRECTION MSC-BSS MSC-BSS MSC-BSS MSC-BSS TYPE M O (1) M O 1 4 3-n 2 LEN

This information element doesnt serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of 08.08, this information element will be deleted from this message.

1.1.18 CIPHER MODE COMPLETE


This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that a successful cipher synchronisation has been achieved across the radio interface.
INFORMATION ELEMENT REFERENCE DIRECTION BSS-MSC BSS-MSC BSS-MSC TYPE M O O (1) LEN 1 2-n 2

Message Type 1.2.1 Layer 3 Message Contents 1.2.37 Chosen Encryption Algorithm 1.2.15

Included at least when the encryption algorithm has been selected by the BSS.

1.1.19 CIPHER MODE REJECT


This message is sent from the BSS to the MSC via the relevant SCCP connection associated with that MS transaction. It indicates that the BSS is unable to perform the requested ciphering.
INFORMATION ELEMENT Message Type Cause REFERENCE DIRECTIO TYPE N 1.2.1 1.2.19 BSS-MSC BSS-MSC M M LEN 1 3-4

Typical Cause values are: - Ciphering algorithm not supported, - Invalid message contents
16

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.1.20 COMPLETE LAYER 3 INFORMATION


The message is sent from the BSS to the MSC via the BSSAP SCCP connection established for the associated dedicated resource(s).
INFORMATION ELEMENT Message Type Cell Identifier Layer 3 Information Chosen Channel LSA Identifier List APDU REFERENCE DIRECTIO N 1.2.1 1.2.13 1.2.31 1.2.14 1.2.38 3.2.2.68 BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC BSS-MSC TYPE M M M O (1) O (2) O (3) LEN 1 3-10 3-n 2 3+3n 3-n

This element is optionally used by the BSS to give the MSC a description of the channel rate/type on which the initial layer 3 message was received. This element shall be included at least when the current cell belongs to one or more LSAs. This element is optionally used by the BSS to provide Location Services related information to MSC.

1.2 Signaling element coding


This paragraph contains the CODING of the signaling elements used. The following conventions are assumed for the sequence of transmission of bits and bytes:

Each bit position is marked as 1 to 8. Bit 1 is the least significant bit and is transmitted first. In an element octets are identified by number, octet 1 is transmitted first, then octet 2 etc.

When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field.

For variable length elements a length indicator is included, this indicates the number of octets following in the element. All fields within Information Elements are mandatory unless otherwise specified. The Information Element Identifier shall always be included. All spare bits are set to 0.

The elements used and their CODING are:


Element Identifier Coding 0000 0001 0000 0010 Element name Circuit Identity Code Reserved

17

Messages Reference

Chapter 2 Abis-Interface Key Messages

Element Identifier Coding 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0011 0011 0011 0100 0011 0011 0011 0011 0011 0011 0011 0011 0011 0011 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 0000 0001 0010 0000 0011 0101 0110 0111 1000 1001 1010 1011 1100 1101

Element name Resource Available Cause Cell Identifier Priority Layer 3 Header Information IMSI TMSI Encryption Information Channel Type Periodicity Extended Resource Indicator Number Of MSs Reserved Reserved Reserved Classmark Information Type 2 Classmark Information Type 3 Interference Band To Be Used RR Cause Reserved Layer 3 Information DLCI Downlink DTX Flag Cell Identifier List Response Request Resource Indication Method Classmark Information Type 1 Circuit Identity Code List Diagnostic Layer 3 Message Contents Chosen Channel Total Resource Accessible Cipher Response Mode Channel Needed Trace Type Trigger id Trace Reference Transaction id Mobile Identity OMC Id Forward Indicator Chosen Encryption Algorithm Circuit Pool Circuit Pool List Time Indication Resource Situation Current Channel type 1 Queuing Indicator Speech Version Assignment Requirement Talker Flag Connection Release Requested Group Call Reference eMLPP Priority Configuration Evolution Indication Old BSS to New BSS Information LSA Identifier LSA Identifier List LSA Information 18

Messages Reference

Chapter 2 Abis-Interface Key Messages

Element Identifier Coding 0011 0011 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 1110 1111 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111

Element name LCS QoS LSA access control suppression LCS Priority Location Type Location Estimate Positioning Data LCS Cause LCS Client Type APDU Network Element Identity GPS Assistance Data Deciphering Keys Return Error Request Return Error Cause Segmentation

1.3 Message Type


Message Type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. Bit 8 is reserved for future extension of the code set. All unassigned codes are spare.
87654321 00000000 Reserved. ASSIGNMENT MESSAGES 00000001 ASSIGNMENT REQUEST 00000010 ASSIGNMENT COMPLETE 00000011 ASSIGNMENT FAILURE HANDOVER MESSAGES 00010000 HANDOVER REQUEST 00010001 HANDOVER REQUIRED 00010010 HANDOVER REQUEST ACKNOWLEDGE 00010011 HANDOVER COMMAND 00010100 HANDOVER COMPLETE 00010101 HANDOVER SUCCEEDED 00010110 HANDOVER FAILURE 00010111 HANDOVER PERFORMED 00011000 HANDOVER CANDIDATE ENQUIRE 00011001 HANDOVER CANDIDATE RESPONSE 00011010 HANDOVER REQUIRED REJECT 00011011 HANDOVER DETECT RELEASE MESSAGES 00100000 CLEAR COMMAND 00100001 CLEAR COMPLETE 00100010 CLEAR REQUEST 00100011 RESERVED 00100100 RESERVED 00100101 SAPI N REJECT 00100110 CONFUSION OTHER CONNECTION RELATED MESSAGES 00101000 SUSPEND 00101001 RESUME 00101010 CONNECTION ORIENTED INFORMATION

19

Messages Reference

Chapter 2 Abis-Interface Key Messages

87654321 00101011 PERFORM LOCATION REQUEST 00101100 LSA INFORMATION 00101101 PERFORM LOCATION RESPONSE 00101110 PERFORM LOCATION ABORT GENERAL MESSAGES 00110000 RESET 00110001 RESET ACKNOWLEDGE 00110010 OVERLOAD 00110011 RESERVED 00110100 RESET CIRCUIT 00110101 RESET CIRCUIT ACKNOWLEDGE 00110110 MSC INVOKE TRACE 00110111 BSS INVOKE TRACE 00111010 CONNECTIONLESS INFORMATION TERRESTRIAL RESOURCE MESSAGES 01000000 BLOCK 01000001 BLOCKING ACKNOWLEDGE 01000010 UNBLOCK 01000011 UNBLOCKING ACKNOWLEDGE 01000100 CIRCUIT GROUP BLOCK 01000101 CIRCUIT GROUP BLOCKING ACKNOWLEDGE 01000110 CIRCUIT GROUP UNBLOCK 01000111 CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE 01001000 UNEQUIPPED CIRCUIT 01001110 CHANGE CIRCUIT 01001111 CHANGE CIRCUIT ACKNOWLEDGE RADIO RESOURCE MESSAGES 01010000 RESOURCE REQUEST 01010001 RESOURCE INDICATION 01010010 PAGING 01010011 CIPHER MODE COMMAND 01010100 CLASSMARK UPDATE 01010101 CIPHER MODE COMPLETE 01010110 QUEUING INDICATION 01010111 COMPLETE LAYER 3 INFORMATION 01011000 CLASSMARK REQUEST 01011001 CIPHER MODE REJECT 01011010 LOAD INDICATION VGCS/V BS 00000100 VGCS/VBS SETUP 00000101 VGCS/VBS SETUP ACK 00000110 VGCS/VBS SETUP REFUSE 00000111 VGCS/VBS ASSIGNMENT REQUEST 00011100 VGCS/VBS ASSIGNMENT RESULT 00011101 VGCS/VBS ASSIGNMENT FAILURE 00011110 VGCS/VBS QUEUING INDICATION 00011111 UPLINK REQUEST 00100111 UPLINK REQUEST ACKNOWLEDGE 01001001 UPLINK REQUEST CONFIRMATION 01001010 UPLINK RELEASE INDICATION 01001011 UPLINK REJECT COMMAND 01001100 UPLINK RELEASE COMMAND 01001101 UPLINK SEIZED COMMAND

20

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.1 Channel Type


This element contains all of the information that the BSS requires to determine the required radio resource(s). The channel type information element has a minimum length of 5 octets and a maximum length of 10 octets. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3 octet 4 octet 5 or octet 5 with extension*

Element identifier Length Spare Speech/data indicator Channel rate and type Permitted speech version indication / data rate + transparency indicator

* If the speech / data indicator (octet 3) indicates "speech" or data, octet 5 may

optionally be extended. Otherwise octet 5 shall not be extended. The "speech / data indicator" field is coded as follows: 0001 Speech 0010 Data 0011 Signaling All other values are reserved. For values 0001 and 0010 a dedicated terrestrial resource is also required. The "channel rate and type" is coded as follows: If octet 3 indicates data then octet 4 shall be coded as: 0000 1000 Full rate TCH channel Bm 0000 1001 Half rate TCH channel Lm 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request.

21

Messages Reference

Chapter 2 Abis-Interface Key Messages

0010 0xxx Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs and if applicable the used radio interface rate per channel allowed after first channel allocation as a result of the request. 0011 0xxx Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs or the used radio interface rate per channel not allowed after first channel allocation as a result of the request. xxx (bits 3-1) indicates maximum number of traffic channels; 321 000 001 010 011 100 101 110 111 1 TCHs 2 TCHs 3 TCHs 4 TCHs 5 TCHs 6 TCHs 7 TCHs 8 TCHs

All other values are reserved. If octet 3 indicates speech then octet 4 shall be coded as: 0000 1000 Full rate TCH channel Bm. Preference between the permitted speech versions for full rate TCH as indicated in octet 5, 5a etc.. 0000 1001 Half rate TCH channel Lm. Preference between the permitted speech versions for half rate TCH as indicated in octet 5, 5a etc.. 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as

22

Messages Reference

Chapter 2 Abis-Interface Key Messages

indicated in octet 5, 5a etc. 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. 0000 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate allowed also after first channel allocation as a result of the request 0001 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate not allowed after first channel allocation as a result of the request All other values are reserved. If octet 3 indicates signaling then octet 4 shall be coded as: 0000 0000 SDCCH or Full rate TCH channel Bm or Half rate TCH channel Lm 0000 0001 SDCCH 0000 0010 SDCCH or Full rate TCH channel Bm 0000 0011 SDCCH or Half rate TCH channel Lm 0000 1000 Full rate TCH channel Bm 0000 1001 Half rate TCH channel Lm 0000 1010 Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. 0000 1011 Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. 0001 1010 Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request.
23

Messages Reference

Chapter 2 Abis-Interface Key Messages

0001 1011 Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. All other values are reserved. The " permitted speech version indication / data rate + transparency indicator" octet is coded as follows: If octet 3 indicates speech then octet 5 shall be coded as follows:
8 ext ext ext ext ext 0 7 6 5 speech speech speech speech speech speech 4 version version version version version version 3 2 1 octet octet octet octet octet octet 5 5a 5b 5c 5d 5e

permitted permitted permitted permitted permitted permitted

identifier identifier identifier identifier identifier identifier

Bit 8 indicates extension of octet 5. 0 no extension, i.e. value "0" indicates that this octet is the last octet. 1 extension, i.e. value "1" indicates that at least one additional octet is included. If more than one permitted speech version is indicated by octet 5 (with extension), then the speech version choice is left to the BSS. Bits 7-1 indicate the permitted speech version identifier; 765 4321 000 0001 GSM speech full rate version 1 001 0001 GSM speech full rate version 2 010 0001 GSM speech full rate version 3 000 0101 GSM speech half rate version 1 001 0101 GSM speech half rate version 2 010 0101 GSM speech half rate version 3 NOTE: Bits 7-1 indicate six speech versions.

The GSM speech full rate version 3 is also referred as the adaptive multi-rate full rate speech version 1 The GSM speech half rate version 3 is also referred as the adaptive multi-rate half rate speech version 1

24

Messages Reference

Chapter 2 Abis-Interface Key Messages

All other values of permitted speech version identifiers are for future use. If an unknown value is received and more than one octet 5 is received the sender expects the receiver to behave as if it has made a choice of speech version. The rules for coding preferences in octet 5, 5a - 5e are the following: - In those cases when one specific channel rate is indicated in octet 4, the non-empty set of permitted speech versions is included. Within this set the permitted speech versions are included in order of speech version preferences. - In those cases when a preference for a channel rate is indicated in octet 4, the nonempty sets of permitted speech versions for the respective channel rate are included in order of the channel rate preferences indicated in octet 4. Within a set of permitted speech versions for a channel rate, the permitted speech versions are included in order of speech version preferences. - In those cases when no preference or specific channel rate is indicated in octet 4, the permitted speech versions are included in order of speech version preferences. Always octet 5 has the highest preference followed by octet 5a and so on. For each channel rate allowed by octet 4 at least one speech version shall be present. If octet 5 indicates no extension and bits 7-1 is coded "000 0001", then the preference is interpreted based upon the octet 4 value as follows: -in those cases when octet 4 indicates one specific channel rate, then speech version 1 for the indicated channel rate is permitted. -in those cases when octet 4 indicates a preference for a channel rate, then speech version 1 for any of the allowed channel rates is permitted. - in those cases when octet 4 does neither indicate a preference for a channel rate nor a specific channel rate, then speech version 1 for any of the allowed channel rates is permitted and speech full rate version 1 is preferred. If octet 3 indicates data, and octet 4 does not indicate multislot configuration, then octet 5 shall be coded as follows:
8 ext ext 7 T/NT spare 6 Rate allowed radio interface rates 5 4 3 2 1 octet 5 octet 5a

Bit 8 indicates extension of octet 5. 0 no extension, i.e. value "0" indicates that this octet is the last octet. 1 extension, i.e. value "1" indicates that at least one additional octet is included.

25

Messages Reference

Chapter 2 Abis-Interface Key Messages

Bit 7: 0 Transparent service 1 Non-transparent service. For non-transparent service bits 6-1 indicate the radio interface data rate; 65 4321 00 0000 12 kbit/s if the channel is a full rate TCH, or

6 kbit/s if the channel is a half rate TCH 01 1000 01 0000 01 0001 14.5 kbit/s 12 kbit/s 6 kbit/s

If bit 7 in octet 5 indicates non-transparent service and octet 5a is included the rate in octet 5 indicates the wanted air interface data rate and the allowed r i/f rates indicates the other possible data rates allowed. All other values are reserved. For transparent service bits 6-1 indicate the data rate; 65 4321 01 1000 01 0000 01 0001 01 0010 01 0011 01 0100 01 0101 14.4 kbit/s 9.6 kbit/s 4.8 kbit/s 2.4 kbit/s 1.2 kbit/s 600 bit/s 1200/75 bit/s (1200 network-to-MS / 75 MS-to-network)

If bit 7 in octet 5 indicates transparent service octet 5 shall not be extended. All other values are reserved. Octet 5a shall be coded as follows: Bit 8 reserved for extension. A coding of 0 indicates no extension Bits 4 to 1 indicate allowed radio interface data rate, per channel:

26

Messages Reference

Chapter 2 Abis-Interface Key Messages

Bit 4: 0 1

14.5 kbit/s (TCH/F14.4) not allowed 14.5 kbit/s (TCH/F14.4) allowed

Bit 3: Spare Bit 2: 0 1 Bit 1: 0 1 12.0 kbit/s (TCH/F9.6) not allowed 12.0 kbit/s (TCH/F9.6) allowed 6.0 kbit/s (TCH/F4.8) not allowed 6.0 kbit/s (TCH/F4.8) allowed

If octet 3 indicates data and octet 4 indicates Full rate TCH channels in a multislot configuration, octet 5 and 5a shall be coded as follows;
8 ext ext 7 T/NT spare 6 Rate allowed radio interface rates 5 4 3 2 1 octet 5 octet 5a

Octet 5 shall be coded as follows; Bit 8 : extension bit 0 indicates no extension 1 indicates that at least one additional octet is included Bit 7 : 0 1 Transparent service Non-transparent service.

For non-transparent service bits 6-1 indicates wanted total radio interface data rate; 65 4321 01 0110 01 0100 01 0011 01 0010 01 0001 01 0000 58 kbit/s (4x14.5 kbit/s) 48.0 / 43.5 kbit/s (4x12 kbit/s or 3x14.5 kbit/s) 36.0 / 29.0 kbit/s (3x12 kbit/s or 2x14.5 kbit/s) 24.0 / 24.0 (4x6 kbit/s or 2x12 kbit/s) 18.0 / 14.5 kbit/s (3x6 kbit/s or 1x14.5 kbit/s) 12.0 / 12.0 kbit/s (2x6 kbit/s or 1x12 kbit/s)

All other values are reserved. For transparent service bits 6-1 indicates requested air interface user rate;

27

Messages Reference

Chapter 2 Abis-Interface Key Messages

65 4321 01 1111 01 1110 01 1101 01 1100 01 1011 01 1010 01 1001 01 1000 01 0000 64 kbit/s, bit transparent 56 kbit/s, bit transparent 56 kbit/s 48 kbit/s 38.4 kbit/s 28.8 kbit/s 19.2 kbit/s 14.4 kbit/s 9.6 kbit/s

All other values are reserved. Octet 5a shall be coded as follows; Bit 8 reserved for extension. A coding of 0 indicates no extension Bits 4 to 1 indicates allowed radio interface data rate, per channel; Bit 4: 0 1 Bit 3: Bit 2: 0 1 Bit 1: 0 1 14.5/14.4 kbit/s (TCH/F14.4) not allowed 14.5/14.4 kbit/s (TCH/F14.4) allowed Spare 12.0/9.6 kbit/s (TCH F/9.6) not allowed 12.0/9.6 kbit/s (TCH F/9.6) allowed 6.0/4.8 kbit/s (TCH F/4.8) not allowed 6.0/4.8 kbit/s (TCH F/4.8) allowed

If octet 5a is not included, allowance of radio interface data rates of 12.0 and 6.0 shall be presumed. NOTE: For data services, the information in the channel type Information Element

is used to set the "E-bits" and map the "D-bits" (as described in GSM 04.21 and 08.20) and to select the correct channel coding. If octet 3 indicates signaling then octet 5 is spare.

1.3.2 Layer 3 Header Information


This element is used to supply the BSS with information that needs to be included in
28

Messages Reference

Chapter 2 Abis-Interface Key Messages

the header of layer 3 messages over the radio interface.


8 7 6 5 4 3 2 1 octet octet octet octet 1 2 3 4

Element identifier Length Protocol discriminator Transaction identifier

The length indicator is a binary indication of the number of octets following in the element. The transaction identifier and protocol discriminator fields are coded as defined in GSM 04.08. The protocol discriminator occupies bit 1 to 4 in octet 3 of Layer 3 header information, the Transaction identifier occupies bit 1 to 4 in octet 4 of the Layer 3 header information.

1.3.3 Priority
This element indicates the priority of the request. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3

Element identifier Length Priority

Octet 2 is a binary indication of the length of the rest of the element. Octet 3 is coded as follows:
8 spare 7 pci 6 5 4 3 qa 2 1 pvi octet 1

priority level

Bit 8 is spare, set to 0 pci = Preemption Capability indicator (see note)

0 this allocation request shall not preempt an existing connection 1 this allocation request may preempt an existing connection priority level: 6543 0000 0001 0010 1110 spare priority level 1 = highest priority priority level 2 = second highest priority priority level 14 = lowest priority

29

Messages Reference

Chapter 2 Abis-Interface Key Messages

1111

priority not used

qa = queuing allowed indicator 0 queuing not allowed 1 queuing allowed pvi = Preemption Vulnerability indicator (see note) 0 this connection shall not be preempted by another allocation request 1 this connection might be preempted by another allocation request NOTE: Preemption Capability indicator applies to the allocation of resources for an

event and as such it provides the trigger to the preemption procedures/processes of the BSS. Preemption Vulnerability indicator applies for the entire duration of a connection and as such indicates whether the connection is a target of the preemption procedures/processes of the BSS.

1.3.4 Circuit Identity Code


This element defines the terrestrial channel over which the call will pass. If a 2048Kbits/s digital path is used then the circuit identification code contains in the 5 least significant bits a binary representation of the actual number of the timeslot which is assigned to the circuit. The remaining bits in the CIC are used where necessary, to identify one among several systems interconnecting an originating and destination point. The element is 2 octets in length:
8 a i b j 7 6 5 4 f X 3 g X 2 h X 1 octet 1 octet 2 octet 3

Element identifier c d e k X X

a-k defines the PCM multiplex in use. XXXXX define the actual timeslot in use. The circuit identity code defines the PCM multiplex and timeslot in use at the MSC. In cases where remultiplexing takes place between the MSC and BSS a translation may be necessary at the BSS. If a 1544 kbit/s digital path is used, then the format of the circuit identity code (CIC) shall be as shown below: The element is 2 octets in length:

30

Messages Reference

Chapter 2 Abis-Interface Key Messages

1 octet 1 octet 2 octet 3

Element identifier CIC (least significant bits) CIC (most significant bits)

1.3.5 Downlink DTX Flag


A fixed length element indicating whether the DTX function in the BSS is to be disabled on a particular radio channel.
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Downlink DTX flag

The Downlink DTX Flag is coded as follows: - bits 8 to 2 are spare; - bit 1 is set to one if the MSC forbids the BSS to activate DTX in the downlink

direction; it is set to 0 otherwise.

1.3.6 Interference Band To Be Used


This fixed length element is coded as follows:
8 7 6 Element identifier Band to be used 5 4 3 2 1 octet 1 octet 2

Octet 2 is coded as: Bits 876 Spare

Bits 54321 A bit map indicating which interference bands are acceptable, the LSB represents the least level of interference.

1.3.7 Classmark Information Type 2


The classmark information type 2 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Length

31

Messages Reference Classmark

Chapter 2 Abis-Interface Key Messages octet 3 5

Octet 2 is a binary indication of the length of the remainder of the element in octets. The length shall be determined by the length of the Mobile Station Classmark 2 element of GSM 04.08. The classmark octets 3, 4 and 5 are coded in the same way as the equivalent octets in the Mobile station classmark 2 element of GSM 04.08.

1.3.8 Group Call Reference


It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3 8

Element identifier Length Descriptive group or broadcast call reference

Octet 2 is a binary indication of the length of the remainder of the element in octets. The octets 3 to 8 are coded in the same way as the octets 2-6 in the Descriptive group or broadcast call reference information element as defined in GSM 04.08.

1.3.9 Talker Flag


8 7 6 5 4 3 2 1 octet 1

Element identifier

1.3.10 LSA Access Control Suppression


This information element is included if LSA access control function shall be suppressed in the BSS. It is coded as follows:
8 7 6 5 4 3 2 1 EM octet 1 octet 2

Element identifier spare

If the connection is an emergency call the MSC shall set the emergency field (bit 1 of octet 2) to 1. If the emergency field is set to 1, the BSS shall suppress exclusive access, LSA only access and preferential access functionality.

32

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.11 RR Cause
This fixed length element is passed from the radio interface to the MSC transparently, when received in a GSM 04.08 message.
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier RR cause

Octet 2 is coded as the equivalent field from GSM 04.08.

1.3.12 Cell Identifier


This element uniquely identifies a cell within a BSS and is of variable length containing the following fields:
8 7 6 5 4 3 2 1 octet octet octet octet n 1 2 3 4

Element identifier Length Spare Cell identification

Cell identification discriminator

The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the Cell identification discriminator (octet 3). The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole or a part of Cell Global Identification, CGI, according to GSM 03.03 is used for cell identification in octet 4-n. The "Cell identification discriminator" is coded as follows: 0000 The whole Cell Global Identification, CGI, is used to identify the cell. 0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell. 0010 Cell Identity, CI, is used to identify the cell. 0011 No cell is associated with the transaction. All other values are reserved. The coding of octet 4-n depends on the Cell identification discriminator (octet 3). Below the coding is shown for each Cell identification discriminator: Note that no coding is specified for a Cell identification discriminator value of "0011" as no additional information is required. Coding of Cell Identification for Cell identification discriminator = 0000

33

Messages Reference

Chapter 2 Abis-Interface Key Messages

For GSM 900 and DCS 1800:


8 7 1 6 1 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet octet octet 4 5 6 7 8 9 10

MCC dig 2 1 1 MNC dig 2 LAC LAC cont. CI value CI value cont

The octets 4-8 are coded as shown in GSM 04.08, Table Location Area Identification information element . The octets 9-10 are coded as shown in GSM 04.08, Table Cell Identity information element. For PCS 1900 for NA:
8 7 6 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet octet octet 4 5 6 7 8 9 10

MCC dig 2 MNC dig 3 MNC dig 2 LAC LAC cont. CI value CI value cont

The octets 4-8 are coded as shown in GSM 04.08, Table Location Area Identification information element. The octets 9-10 are coded as shown in GSM 04.08, Table Cell Identity information element. Coding of Cell Identification for Cell identification discriminator = 0001
8 7 6 5 4 3 2 1 octet octet octet octet 4 5 6 7

LAC LAC cont. CI value CI value cont

Coding of Cell Identification for Cell identification discriminator = 0010


8 7 6 5 4 3 2 1 octet 4 octet 5

CI value CI value cont

The octets 4-5 are coded as shown in GSM 04.08, Table Cell Identity information

34

Messages Reference

Chapter 2 Abis-Interface Key Messages

element

1.3.13 Chosen Channel


This Information Element contains a description of the channel allocated to the MS. For VGCS/VBS calls this Information Element contains a description of the channel allocated for the call in the cell. It is coded as follows:
8 7 6 5 4 Channel 3 2 1 octet 1 octet 2

Element identifier Channel mode

The channel mode field is coded as follows: Bit 8765 no channel mode indication speech (full rate or half rate)

0000 1001

1110data, 14.5 kbit/s radio interface rate 1011data, 12.0 kbit/s radio interface rate 1100data, 6.0 kbit/s radio interface rate 1101data, 3.6 kbit/s radio interface rate 1000 signaling only

All other values are reserved. The channel field is coded as follows: Bit 4321 None (Note *) SDCCH 1 Full rate TCH 1 Half rate TCH 2 Full Rate TCHs

0000 0001 1000 1001 1010

10113 Full Rate TCHs 11004 Full Rate TCHs

35

Messages Reference

Chapter 2 Abis-Interface Key Messages

11015 Full Rate TCHs 11106 Full Rate TCHs 1111 7 Full Rate TCHs 0100 8 Full Rate TCHs

All other values are reserved. NOTE *: This value may be returned in the chosen channel information for

VGCS/VBS calls in the case where the BSS has decided to de-allocate resources or allocate no resources for the call.

1.3.14 Chosen Encryption Algorithm


This element indicates the encryption algorithm being used by the BSS. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Algorithm identifier

The algorithm identifier caters for the possible future introduction of different user data encryption algorithms. It is coded as; 0000 0001 No encryption used 0000 0010 GSM user data encryption version 1(A5/1). 0000 0011 GSM A5/2 0000 0100 GSM A5/3 0000 0101 GSM A5/4 0000 0110 GSM A5/5 0000 0111 GSM A5/6 0000 1000 GSM A5/7 All other values are Reserved for future international use.

1.3.15 Circuit Pool


This element indicates the circuit pool of a circuit or group of circuits. It is coded as follows:

36

Messages Reference

Chapter 2 Abis-Interface Key Messages

1 octet 1 octet 2

Element identifier Circuit pool number

Predefined circuit pools are currently Circuit pool number 1 to Circuit pool number 32. The circuit pool element is coded as follows (along with the definition of the predefined circuit pools):
Coding 0000 0001 0000 0010 0000 0011 Pool Circuit pool number 1 Circuit pool number 2 Circuit pool number 3 Supported channels and speech coding algorithms FR speech version 1 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) FR speech version 1 FR data (12, 6, 3.6 kbit/s) HR speech version 1 0000 0100 0000 0101 Circuit pool number 4 Circuit pool number 5 Circuit pool number 6 HR data (6, 3.6 kbit/s) FR speech version 2 FR data (12, 6, 3.6 kbit/s) FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 0000 0111 Circuit pool number 7 HR data (6, 3.6 kbit/s) FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 0000 1000 0000 1001 Circuit pool number 8 Circuit pool number 9 Circuit pool number 10 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (12, 6 kbit/s) FR data (12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (12, 6 kbit/s) FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) 0000 1011 0000 1100 Circuit pool number 11 Circuit pool number 12 HSCSD max 2 x FR data (12, 6 kbit/s) HSCSD max 4 x FR data (12, 6 kbit/s) FR data (12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s)

0000 0110

0000 1010

37

Messages Reference

Chapter 2 Abis-Interface Key Messages

Coding

Pool

Supported channels and speech coding algorithms HSCSD max 4 x FR data (12, 6 kbit/s) FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (12, 6 kbit/s) HSCSD max 6 x FR data (12, 6 kbit/s) FR data (14.5 kbit/s) HSCSD max 2 x FR data (14.5 kbit/s) HSCSD max 4 x FR data (14.5 kbit/s) FR data (14.5, 12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12, 6 kbit/s) FR data (14.5, 12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12, 6 kbit/s) FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12, 6 kbit/s) FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12, 6 kbit/s) FR speech version 3 HR speech version 3 FR speech version 3 FR data (12, 6, 3.6 kbit/s) HR speech version 3 FR speech version 1 FR speech version 2 FR speech version 3

0000 1101

Circuit pool number 13

0000 1110 0000 1111 0001 0000 0001 0001 0001 0010

Circuit pool number 14 Circuit pool number 15 Circuit pool number 16 Circuit pool number 17 Circuit pool number 18 Circuit pool number 19 Circuit pool number 20

0001 0011

0001 0100

0001 0101

Circuit pool number 21

0001 0110

Circuit pool number 22

0001 0111 0001 1000

Circuit pool number 23 Circuit pool number 24 Circuit pool number 25

0001 1001

38

Messages Reference

Chapter 2 Abis-Interface Key Messages

Coding

Pool

Supported channels and speech coding algorithms FR data (12, 6, 3.6 kbit/s)

0001 1010

Circuit pool number 26

HR speech version 3 FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 3 FR speech version 1 FR speech version 2 FR speech version 3 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR speech version 3 HR data (6, 3.6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR speech version 3 HR data (6, 3.6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR speech version 3 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (12, 6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR speech version 3 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12, 6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (12, 6, 3.6 kbit/s) HR speech version 1

0001 1011

Circuit pool number 27

0001 1100

Circuit pool number 28

0001 1101

Circuit pool number 29

0001 1110

Circuit pool number 30

0001 1111

Circuit pool number 31

39

Messages Reference

Chapter 2 Abis-Interface Key Messages

Coding

Pool

Supported channels and speech coding algorithms HR speech version 3 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (12, 6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR speech version 3 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)

0010 0000

Circuit pool number 32

1000 xxxx

For national/local use All other values are Reserved for future international use

1.3.16 Speech Version


This element indicates the speech version being used by the BSS. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier spare Circuit pool number

The bits 7-1 of octet 2 are coded in the same way as the permitted speech version identifier in the Channel type information element.

1.3.17 LSA Identifier


This element uniquely identifies a LSA and is of fixed length containing the following fields:
8 7 6 5 4 3 2 1 octet octet octet octet octet 1 2 3 4 5

Element identifier Length LSA ID LSA ID cont. LSA ID cont.

40

Messages Reference

Chapter 2 Abis-Interface Key Messages

The octets 3-5 are coded as specified in GSM 03.03, Identification of Localized Service Area. Bit 8 of octet 3 is the MSB.

1.3.18 Cause
The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below. The cause value is a single octet element if the extension bit (bit 8) is set to 0. If it is set to 1 then the cause value is a 2 octet field. If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national applications, (XXX will still indicate the class).
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3 (octet 4)

0/1 ext

Element identifier Length Cause Value

The length indicator is a binary representation of the length of the following element. Cause Value: Class (000) : Class (001) : Class (010) : Class (011) : Class (100) : Class (101) : Class (110) : Class (111) : Normal event Normal event Resource unavailable Service or option not available Service or option not implemented invalid message (eg parameter out of range) protocol error interworking

In the following table, "reserved for international use" means that this code point should not be used until a meaning has been assigned to it following the process of international standardisation. "Reserved for national use" indicates code points that may be used by operators without the need for international standardisation.
Cause value Class 765 000 Value 4321 0000 Radio interface message failure Cause Number

41

Messages Reference

Chapter 2 Abis-Interface Key Messages

Cause value Class 765 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 Value 4321 0 0 0 1 1 1 1 0 0 0 0 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0

Cause Number

000 000 000 000 000 001 ::: 001 001 ::: 001 010 010 010 010 010 010 010 010 010 010 010 ::: 010 011 011 011 011 011 011 011 011 100 100 100 100 100 100

101 110 110 111 111 000 :::: 011 100 :::: 111 000 000 001 001 010 010 011 011 100 100 101 :::: 111 000

0001 0010 0011 0100 0101 :::: 1111 0000 0001 :::: 0111 1000 :::: 42

Radio interface failure Uplink quality Uplink strength Downlink quality Downlink strength Distance O and M intervention Response to MSC invocation Call control Radio interface failure, reversion to old channel Handover successful Better Cell Directed Retry Joined group call channel Traffic } } Reserved for international use } } } Reserved for national use } Equipment failure No radio resource available Requested terrestrial resource unavailable CCCH overload Processor overload BSS not equipped MS not equipped Invalid cell Traffic Load Preemption } } Reserved for national use } Requested transcoding/rate adaption unavailable Circuit pool mismatch Switch circuit pool Requested speech version unavailable LSA not allowed } } Reserved for international use } Ciphering algorithm not supported } } Reserved for international use } } } Reserved for national use

Messages Reference

Chapter 2 Abis-Interface Key Messages

Cause value Class 765 100 101 101 101 101 101 101 101 101 1 1 1 1 0 0 0 1 1 1 1 0 Value 4321 1111 0000 0001 0010 0011 0100 0101 0110 0111 1000 :::: 1111 0000 0001 0010 :::: 011 100 :::: 111 000 :::: 1 0 1 0

Cause Number

110 110 110 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1

0111 1000 :::: 1111

} Terrestrial circuit already allocated Invalid message contents Information element or field missing Incorrect value Unknown Message type Unknown Information Element } } Reserved for international use } }Reserved for national use } Protocol Error between BSS and MSC VGCS/VBS call non existent } } Reserved for international use } } } Reserved for national use } } } Reserved for international use } } } Reserved for national use }

1.3.19 Circuit Pool List


This element defines a list of BSS preferred circuit pools in order of preference. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3 octet n+2

Element identifier Length Circuit pool number (1st preferred) : Circuit pool number (nth preferred)

The Circuit pool number is coded as specified in 1.2.16.

43

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.20 Encryption Information


This element contains the user data encryption information used to control any encryption equipment at the BSS. It is a variable length element. It is coded as follows:
8 7 6 5 4 3 2 1 octet octet octet octet n 1 2 3 4-

Element identifier Length Permitted algorithms Key

The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. The permitted algorithms octet is a bit map indicating the A5 encryption algorithms and no encryption. From this bit map the BSS may select an A5 algorithm or no encryption to be used. Bit No 1 No encryption 2 GSM A5/1 3 GSM A5/2 4 GSM A5/3 5 GSM A5/4 6 GSM A5/5 7 GSM A5/6 8 GSM A5/7 A bit position encoded as 1 indicates that the BSS may use the option represented by that bit position. A bit position encoded as 0 indicates that the BSS shall not use the option represented by that bit position. A permitted algorithms octet containing all bits encoded as 0 shall not be used. The key shall be present if at least one of the A5 encryption algorithms is permitted. When present, the key shall be 8 octets long.

44

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.21 Classmark Information Type 1


The classmark information type 1 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Classmark

The classmark octet 2 is coded in the same way as the equivalent octet in the classmark 1 element of 04.08.

1.3.22 Classmark Information Type 3


The classmark information type 3 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 314

Element identifier Length Classmark

Octet 2 is a binary indication of the length of the remainder of the element in octets. The length octet has a minimum value of 1 and a maximum of 12. The length shall be determined by the length of the Mobile Station Classmark 3 element of GSM 04.08. The classmark octets 3 to 14 are coded in the same way as the equivalent octets in the Mobile station classmark 3 element of GSM 04.08.

1.3.23 Current Channel Type 1


This Information Element contains a description of the channel allocated to the MS. It is coded as follows:
8 7 6 5 4 Channel 3 2 1 octet 1 octet 2

Element identifier Channel mode

The channel mode field is coded as follows:

45

Messages Reference

Chapter 2 Abis-Interface Key Messages

Bit

8765

0000 signaling only 0001 speech (full rate or half rate) 0110 data, 14.5 kbit/s radio interface rate 0011 data, 12.0 kbit/s radio interface rate 0100 data, 6.0 kbit/s radio interface rate 0101 data, 3.6 kbit/s radio interface rate 1111 is reserved All other values are for future use. If the receiver receives an unknown channel mode it shall not be rejected but the receiver shall assume that the channel mode is to be changed. The channel field is coded as follows: Bit 4321 Full Half Full Full Full Full Full Full rate rate Rate Rate Rate Rate Rate Rate TCH TCH TCHs TCHs TCHs TCHs TCHs TCHs

0001 SDCCH 1000 1 1001 1 1010 2 1011 3 1100 4 1101 5 1110 6 1111 7 0100 8 Full Rate TCHs 0000 is reserved All other values are for future use. If the receiver receives a unknown channel field it shall not be rejected but the receiver shall assume that the channel is to be changed. Consistencies between channel fields and channel modes shall not be checked.

1.3.24 LSA Information


This element uniquely identifies LSAs, the priority, the preferential access indicator and the active mode support indicator of each LSA. The access right outside these LSAs is also defined. The element is of variable length containing the following fields:

46

Messages Reference

Chapter 2 Abis-Interface Key Messages

1 octet octet LSA only octet octet 1 2 3 4-7

Element identifier Length spare LSA identification and attributes 1 : LSA identification and attributes n

to 3+4n

The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the number of LSAs to be identified. If the LSA only access indicator (bit 1 of octet 3) is set to 1 the subscriber has only access to the LSAs that are defined by the LSA Information element. The LSA only access indicator is set to 0 for allowing an emergency call. Coding of the i-th LSA identification with attributes:
8 spare LSA ID LSA ID cont. LSA ID cont. 7 act 6 5 pref 4 priority 3 2 1 octet x+1 octet x+2 octet x+3 octet x+4

Where x = 3 + 4(i-1) Bits 1 to 4 of octet (x+1) define the priority of the LSA identification. Bit 4321 0000 priority 1 = lowest priority 0001 priority 2 = second lowest priority :::: priority 16 = highest priority If the preferential access indicator (bit 5 of octet (x+1)) is set to 1 the subscriber has preferential access in the LSA. If the active mode support indicator (bit 6 of octet (x+1)) is set to 1 the subscriber has active mode support in the LSA. The octets (x+2)-(x+4) are coded as specified in GSM 03.03, Identification of Localized Service Area. Bit 8 of octet (x+2) is the MSB.

47

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.25 Old BSS to New BSS information


This information element is defined as a general container for passing Field Elements transparently between BSSs via the MSC. These Field Elements are passed in the Old BSS to New BSS information elements octets field.
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3-n

Element identifier Length


Old BSS to New BSS information elements

The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet and may be set to zero. The Old BSS to New BSS information elements field is made up of 0 or more Field Elements listed in the table shown below. Field elements may occur in any order in the Old BSS to New BSS information elements field. The construction of the Field Elements allows the receiver to ignore unknown Field Elements. Due to backward compatibility issues Field Elements in the Old BSS to New BSS information may duplicate Information Elements in the HANDOVER REQUEST, when this occurs and the new BSS detects an inconsistency between this information then the information contained in the Old BSS to New BSS information shall take precedence as long as the coding is understood by the new BSS. Reception of an erroneous Old BSS to New BSS information shall not cause a rejection of the HANDOVER REQUEST message; the Old BSS to New BSS information information element shall be discarded and the handover resource allocation procedure shall continue.
FIELD ELEMENT Extra information Current Channel Type 2 Target cell radio information GPRS Suspend information MultiRate configuration information REFERENCE 3.2.3.1 3.2.3.2 3.2.3.3 3.2.3.4 3.2.3.5 LEN 3 4 3 19 3-8

1.3.26 Configuration Evolution Indication


This information element indicates whether subsequent assignment requests should be expected and the limitation for these subsequent assignments.
48

Messages Reference

Chapter 2 Abis-Interface Key Messages

4 SMI

1 octet 1 octet 2

Element identifier spare

SMI: Subsequent Modification Indication. This indicates the maximum number of TCH/F that could be requested in subsequent assignments. The SMI field is coded as follows: Bit 4321

0000 No Modification is allowed 0001 Modification is allowed and maximum number of TCH/F is 1 0010 Modification is allowed and maximum number of TCH/F is 2 0011 Modification is allowed and maximum number of TCH/F is 3 0100 Modification is allowed and maximum number of TCH/F is 4 All other values are reserved.

1.3.27 Response Request


The presence of this element indicates that a Handover Required Reject message is required by the BSS, if the Handover Required message does not result in a handover. The element has a fixed length of one octet:
8 7 6 5 4 3 2 1 octet 1

Element identifier

1.3.28 Cell Identifier List


This element uniquely identifies cells and is of variable length containing the following fields:

1 octet octet octet octet 4+m 1 2 3 4-

Element identifier Length


spare Cell identification discriminator

Cell identification 1
:

Cell identification n

to 4+nm

49

Messages Reference

Chapter 2 Abis-Interface Key Messages

The coding of octet 2 is a binary number indicating the Length of the remaining element. The Length depends on the Cell identification discriminator (bits 1 to 4 of octet 3) as well as the number of cells to be identified. The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to GSM 03.03 is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: 0000 The whole Cell Global Identification, CGI, is used to identify the cells. 0001 Location Area Code, LAC, and Cell Identify, CI, is used to identify the cells. 0010 Cell Identity, CI, is used to identify the cells. 0011 No cell is associated with the transaction. 0100 Location Area Identification, LAI, is used to identify all cells within a Location Area. 0101 Location Area Code, LAC, is used to identify all cells within a location area. 0110 All cells on the BSS are identified. All other values are reserved. Values 0100, 0101 and 0110 are only applicable for page message. The coding of the Cell Identifications 1 to n (octets 4 to 4+nm) depends on the Cell identification discriminator (octet 3). Below the coding of the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): Note that no coding is specified for Cell identification discriminator values of "0011" and "0110" as no additional information is required. Coding of the i-th Cell Identification for Cell identification discriminator = 0000 For GSM 900 and DCS 1800:
8 7 1 6 1 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet octet octet 4 5 6 7 8 9 10

MCC dig 2 1 1 MNC dig 2 LAC LAC cont. CI value CI value cont

Where x = 3 + 7(i-1).

50

Messages Reference

Chapter 2 Abis-Interface Key Messages

The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table Location Area Identification information element. The octets (x+6)-(x+7) are coded as shown in GSM 04.08, Table Cell Identity information element. For PCS 1900 for NA:
8 7 6 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet octet octet x+1 x+2 x+3 x+4 x+5 x+6 x+7

MCC dig 2 MNC dig 3 MNC dig 2 LAC LAC cont. CI value CI value cont

Where x = 3 + 7(i-1). The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table Location Area Identification information element. The octets (x+6)-(x+7) are coded as shown in GSM 04.08, Table Cell Identity information element . Coding of i-th Cell Identification for Cell identification discriminator = 0001
8 7 6 5 4 3 2 1 octet octet octet octet x+1 x+2 x+3 x+4

LAC LAC cont. CI value CI value cont

Where x = 3 + 4(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table Location Area Identification information element. The octets (x+3)-(x+4) are coded as shown in GSM 04.08, Table Cell Identity information element. Coding of i-th Cell Identification for Cell identification discriminator = 0010
8 7 6 5 4 3 2 1 octet x+1 octet x+2

CI value CI value cont

Where x = 3 + 2(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table Cell Identity

51

Messages Reference

Chapter 2 Abis-Interface Key Messages

information element . Coding of i-th Cell Identification for Cell identification discriminator = 0100 For GSM 900 and DCS 1800:
8 7 1 6 1 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet octet octet x+1 x+2 x+3 x+4 x+5 x+6 x+7

MCC dig 2 1 1 MNC dig 2 LAC LAC cont. CI value CI value cont

Where x = 3 + 5(i-1) The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table Location Area Identification information element. For PCS 1900 for NA:
8 MCC dig 2 MNC dig 3 MNC dig 2 LAC LAC cont. 7 6 5 4 MCC dig 1 MCC dig 3 MNC dig 1 3 2 1 octet octet octet octet octet x+1 x+2 x+3 x+4 x+5

Where x = 3 + 5(i-1) The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table Location Area Identification information element. Coding of i-th Cell Identification for Cell identification discriminator = 0101
8 LAC LAC cont. 7 6 5 4 3 2 1 octet x+1 octet x+2

Where x = 3 + 2(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table Location Area Identification information element . The appropriate coding for not identified cells is "0" for all bits of LAC and CI for all possible Cell Identification Discriminator values.

52

Messages Reference

Chapter 2 Abis-Interface Key Messages

1.3.29 Queuing Indicator


This element contains a recommendation of the BSS concerning application of queuing. The element has a fixed length of two octets.
8 7 6 5 4 3 qri 2 1 spare octet 1 octet 2

Element identifier spare

Octet 2 is coded as follows: qri = queuing recommendation indicator 0 it is recommended not to allow queuing 1 it is recommended to allow queuing

1.3.30 Layer 3 Information


This is a variable length element used to pass radio interface messages from one network entity to another.
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3-n

Element identifier Length Layer 3 information

Octet 1 identifies the element. Octet 2 gives the length of the following layer 3 information. Octet j (j = 3, 4, ..., n) is the unchanged octet j-2 of a radio interface layer 3 message as defined in GSM 04.08, n-2 is equal to the length of that radio interface layer 3 message.

1.3.31 IMSI
The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and includes a length indicator. The remainder of this element is coded as defined in GSM 04.08. The element coding is:
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Length

53

Messages Reference

Chapter 2 Abis-Interface Key Messages Rest of element coded as in GSM 04.08, not including GSM 04.08 element identifier or GSM 04.08 octet length value octet 3-n

1.3.32 TMSI
The TMSI is a fixed length element. The TMSI is an unstructured number of 4 octets in length. The coding is:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3-n

Element identifier Length TMSI

The TMSI field is unstructured.

1.3.33 Channel Needed


This information element contains an indication for the mobile station of which channel is needed for the transaction linked to the paging procedure. It is coded as follows:
8 7 6 5 4 3 2 Channel 1 octet 1 octet 2

Element identifier spare

The Channel field is coded as follows: Bit 00 01 10 11 21 Any channel SDCCH TCH/F (Full rate) TCH/H or TCH/F (Dual rate)

1.3.34 eMLPP Priority


This Information Element contains the eMLPP priority of the call. It is coded as follows:

54

Messages Reference

Chapter 2 Abis-Interface Key Messages

3 Call priority

1 octet 1 octet 2

Element identifier spare

The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in the Descriptive group or broadcast call reference information element as defined in GSM 04.08.

1.3.35 Cipher Response Mode


This information element is used by the MSC to indicate whether the IMEI is to be included in the CIPHERING MODE COMPLETE message to be sent by the Mobile Station.
8 7 6 5 4 3 2 1 octet 1 octet 2

Element identifier Cipher response mode

Octet 2 is coded as:Bits 8,7,6,5,4,3,2 - Spare Bit 1 = 0 - IMEISV must not be included by the Mobile Station Bit 1 = 1 - IMEISV must be included by the Mobile Station

1.3.36 Layer 3 Message Contents


This is a variable length element used to pass the contents (from octet 3 up to the last octet) of radio interface messages from one network entity to another.
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3-n

Element identifier Length Layer 3 message contents

The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. Octet j (j = 3, 4, ..., n) is the unchanged octet j of a radio interface layer 3 message as defined in GSM 04.08, n is equal to the length of that radio interface layer 3 message.

1.3.37 LSA Identifier List


This element uniquely identifies LSAs and is of variable length containing the following

55

Messages Reference

Chapter 2 Abis-Interface Key Messages

fields:
8 7 6 5 4 3 2 1 octet 1 octet 2 octet 3 octet 4-6 : to 3+3n

Element identifier Length spare LSA identification 1 : LSA identification 2

EP

The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the number of LSAs to be identified. If the escape PLMN (see GSM 03.73) is broadcast the EP bit (bit 1 of octet 3) is set to 1, otherwise it is set to 0.
8 7 6 5 4 3 2 1 octet x+1 octet x+2 octet x+3

LSA ID LSA ID cont. LSA ID cont.

Where x = 3 + 3(i-1) The octets (x+1)-(x+3) are coded as shown in GSM 03.03, Identification of Localized Service Area. Bit 8 of octet (x+1) is the MSB.

1.3.38 APDU
This information element is defined as a general container for passing information transparently between BSSs or between BSS and SMLC via the MSC. It is coded as follows:
8 7 6 5 4 3 2 1 octet 1 octet 2-3 octet 4-n

Element identifier Length APDU

The length indicator is a binary indication of the number of octets following in the element. The APDU octets 4 to n are coded in the same way as the equivalent octet in the APDU element of GSM 09.31.

56

Messages Reference

Chapter 2 Abis-Interface Key Messages

Chapter 2 Abis-Interface Key Messages1


There is no general rule for the order of signaling elements: it happens that the same elements appear in various orders depending on the message. The key BSSMAP messages are listed in the following table:
Message name CHANNEL REQUIRED PAGING COMMAND CHANNEL ACTIVATION CHANNEL ACTIVATION ACKNOWLEDGE CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE IMMEDIATE ASSIGN COMMAND CONNECTION FAILURE INDICATION ERROR INDICATION ENCRYPTION COMMAND HANDOVER DETECTION MODE MODIFY MODE MODIFY ACKNOWLEDGE MODE MODIFY NEGATIVE ACKNOWLEDGE ESTABLISH INDICATION Reference 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.1.11 2.1.12 2.1.13 2.1.14

2.1 Message Contents


2.1.1 CHANNEL REQUIRED
This message is sent from BTS to BSC to indicate the reception of a CHANnel REQuest message (special access burst message) from an MS.
INFORMATION ELEMENT Message discriminator Message type Channel number Request Reference Access Delay Physical Context REFEREN CE 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 PRESENC E M M M M M O 1) FORM AT V V TV TV TV TLV LENGT H 1 1 2 4 2 >=2

Optional element for additional physical channel information. The Request Reference element contains the random access reference value sent by MS in the CHANnel REQuest message and some low order bits of the absolute frame
The messages of Abis-interface described here are based on Phase 2+ GSM 0858 version 7.4.1 Release 1998.
1

57

Messages Reference

Chapter 2 Abis-Interface Key Messages

number for the reception of the access burst.

2.1.2 PAGING COMMAND


This message is sent from BSC to BTS to request the paging of an MS.
INFORMATION ELEMENT Message discriminator Message type Channel number Paging Group MS Identity Channel Needed eMLPP Priority REFEREN CE 2.2.1 2.2.2 2.2.3 2.2.7 2.2.8 2.2.9 2.2.10 PRESEN CE M M M M M O 1) O 2) FORMA T V V TV TV TLV TV TV LENGT H 1 1 2 2 2-10 2 3

If the Channel Needed element is not present, the default value is assumed to be 00 (any channel). If the eMLPP Priority is not present then the BTS does not include the eMLPP priority in the radio interface message. The Paging Group element is used by BTS to calculate the correct DRX paging block to be used for the transmission of the PAGing REQuest message as defined in GSM 05.02.

2.1.3 CHANNEL ACTIVATION


This message is sent from BSC to BTS in order to activate a radio channel. The attributes of the channel are defined in the message.
INFORMATION ELEMENT Message discriminator Message type Channel number Activation Type Channel Mode Channel Identification Encryption information Handover Reference BS Power MS Power Timing Advance BS Power Parameters MS Power Parameters Physical Context SACCH Information REFEREN CE 2.2.1 2.2.2 2.2.3 2.2.11 2.2.12 2.2.13 2.2.14 2.2.15 2.2.16 2.2.17 2.2.18 2.2.20 2.2.19 2.2.6 2.2.21 PRESENC E M M M M M O 7) O 1) C 2) O 3) O 3) C 3) 4) O 5) O 5) O 6) O 8) FORM AT V V TV TV TLV TLV TLV TV TV TV TV TLV TLV TLV TLV LENGT H 1 1 2 2 8-9 8 >=3 2 2 2 2 >=2 >=2 >=2 >=3

58

Messages Reference UIC Main channel reference MultiRate configuration MultiRate Control Supported Code Types 2.2.22 2.2.23 2.2.24 2.2.25 2.2.26

Chapter 2 Abis-Interface Key Messages O O O O O 9) 10) 11) 12) 12) TLV TV TLV TV TLV 3 2 >=4 2 >=5

1) 2) 3) 4) 5)

The Encryption Information element is only included if ciphering is to be applied. The Handover Reference element is only included if activation type is handover. If BS Power, MS Power and/or Timing Advance elements are present, they are to be used to set the initial transmission power and the initial L1-header. The Timing Advance element must be included if activation type is intra cell channel change. The BS and MS Power Parameters elements are included to indicate that BS and/or MS power control is to be performed by BTS. The maximum power to be used is indicated in the BS and MS Power elements respectively.

6) 7) 8)

Optional element for additional physical channel information. Included if compatibility with phase1 is required. Optional element for setting the SACCH filling information individually for this channel. If this element is present, the SACCH filling information as given by this element shall be used for this channel (replacing any SACCH filling information as given by the SACCH FILLING message(s)) until the channel is released or the information is changed by a SACCH INFO MODIFY message. (If this element is not present, the SACCH filling as given by the SACCH FILLING message(s) shall be used.)

9)

The UIC element may be included for voice group calls. It is used in the same way as the BSIC for decoding the random access bursts when decoding uplink access bursts. If not included, the BSIC shall be used for decoding uplink access bursts.

10) Optional element for multislot operation, it may be used in case of power control in the BTS. 11) Included if the Channel Mode indicates that a multi-rate speech code is used. 12) Optionally included if the Channel Mode indicates that a multi-rate speech code is used and TFO control is required or to give to the BTS the possibility to change autonomously the multi-rate code configuration.

59

Messages Reference

Chapter 2 Abis-Interface Key Messages

2.1.4 CHANNEL ACTIVATION ACKNOWLEDGE


This message is sent from BSC to BTS to acknowledge that the requested channel activation has been completed correctly.
INFORMATION ELEMENT Message discriminator Message type Channel number Frame number REFEREN CE 2.2.1 2.2.2 2.2.3 2.2.27 PRESENCE M M M M FORM AT V V TV TV LENGT H 1 1 2 3

The Frame Number element is used by BSC to calculate the Starting Time parameter when required.

2.1.5 CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE


This message is sent from BTS to BSC to indicate that the channel activation could not be performed as requested.

60

Messages Reference

Chapter 2 Abis-Interface Key Messages

INFORMATION ELEMENT Message discriminator Message type Channel number Cause

REFERENC E 2.2.1 2.2.2 2.2.3 2.2.28

PRESENC E M M M M

FORM AT V V TV TLV

LENGT H 1 1 2 >=3

If the Channel Activation message was received with an erroneous Channel number information element, the Channel Activation Negative Acknowledge message is returned with the Channel Number information element equal to the received (and erroneous) Channel number and the Cause value "Mandatory Information Element Error" with Diagnostics equal to the Channel number element identifier value.

2.1.6 IMMEDIATE ASSIGN COMMAND


This message is sent from BSC to BTS to request the transmission of an immediate assignment message.
INFORMATION ELEMENT Message discriminator Message type Channel number Full Imm. Assign Info REFERENCE 2.2.1 2.2.2 2.2.3 2.2.29 PRESENC E M M M M FORM AT V V TV TLV LENGT H 1 1 2 25

The Full Imm. Assign Info element contains the relevant immediate assignment message as defined in GSM 04.08 (IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT) with the "Page Mode" element set to the value "no change".

2.1.7 CONNECTION FAILURE INDICATION


This message is sent from BTS to BSC to indicate that an active connection has been broken for some reason.
INFORMATION ELEMENT Message discriminator Message type Channel number Cause REFERENC E 2.2.1 2.2.2 2.2.3 2.2.28 PRESENC E M M M M FORM AT V V TV TLV LENGT H 1 1 2 >=3

2.1.8 ERROR INDICATION


This message is sent from BTS to BSC to indicate an abnormal case for a radio link

61

Messages Reference

Chapter 2 Abis-Interface Key Messages

layer connection.
INFORMATION ELEMENT Message discriminator Message type Channel number Link Identifier RLM Cause REFERENC E 2.2.1 2.2.2 2.2.3 2.2.30 2.2.31 PRESENC E M M M M M FORM AT V V TV TV TLV LENGT H 1 1 2 2 2-4

2.1.9 ENCRYPTION COMMAND


This message is sent from BSC to BTS to start ciphering mode operation.
INFORMATION ELEMENT Message discriminator Message type Channel number Encryption information Link Identifier L3 Info (CIPH MOD CMD) REFEREN CE 2.2.1 2.2.2 2.2.3 2.2.14 2.2.30 2.2.32 PRESENC E M M M M M M FORM AT V V TV TLV TV TLV LENGT H 1 1 2 >=3 2 6

The L3 Info element contains the complete Ciphering Mode Command message as defined in GSM 04.08.

2.1.10 HANDOVER DETECTION


This message is sent from BTS to BSC when BTS correctly receives information from an MS on the handover activated channel.
INFORMATION ELEMENT Message discriminator Message type Channel number Access Delay REFERENC E 2.2.1 2.2.2 2.2.3 2.2.5 PRESENC E M M M O 1) FORM AT V V TV TV LENGT H 1 1 2 2

The Access Delay element is included if the sending of the handover detection message was triggered by the reception of a handover access burst with the correct handover reference.

2.1.11 MODE MODIFY


This message is sent from BSC to BTS to request a change of channel mode of an active channel.

62

Messages Reference

Chapter 2 Abis-Interface Key Messages

INFORMATION ELEMENT Message discriminator Message type Channel number Channel Mode Encryption information Main channel reference MultiRate configuration Multirate Control Supported Code Types

REFERENC E 2.2.1 2.2.2 2.2.3 2.2.12 2.2.14 2.2.23 2.2.24 2.2.25 2.2.26

PRESENC E M M M M O O O O O

FORM AT V V TV TLV TLV TV TLV TV TLV

LENGT H 1 1 2 8-9 >=3 2 >=3 2 >=5

1) 2) 3) 4) 4)

(1)

The Encryption Information element is only included if ciphering is to be applied.

13) Optional element for multislot operation, it may be used in case of power control in the BTS. 14) Included if the Channel Mode indicates that a multi-rate speech code is used. 15) Optionally included if the Channel Mode indicates that a multi-rate speech code is used and TFO control is required or to give to the BTS the possibility to change autonomously the multi-rate code configuration.

2.1.12 MODE MODIFY ACKNOWLEDGE


This message is sent from BTS to BSC to confirm the change of channel mode of an active channel.
INFORMATION ELEMENT Message discriminator Message type Channel number REFERENC E 2.2.1 2.2.2 2.2.3 PRESENC E M M M FORM AT V V TV LENGT H 1 1 2

2.1.13 MODE MODIFY NEGATIVE ACKNOWLEDGE


This message is sent from BTS to BSC to indicate that the channel mode modification could not be performed as requested.
INFORMATION ELEMENT Message discriminator Message type Channel number Cause REFERENC E 2.2.1 2.2.2 2.2.3 2.2.28 PRESENC E M M M M FORM AT V V TV TLV LENGT H 1 1 2 >=3

63

Messages Reference

Chapter 2 Abis-Interface Key Messages

2.1.14 ESTABLISH INDICATION


This message is sent from BTS to BSC to indicate the establishment of a radio link layer connection in multi-frame mode, initiated by an MS.

64

Messages Reference

Chapter 2 Abis-Interface Key Messages

INFORMATION ELEMENT Message discriminator Message type Channel number Link Identifier L3 Information

REFERENC E 2.2.1 2.2.2 2.2.3 2.2.30 2.2.32

PRESENC E M M M M O 1)

FORM AT V V TV TV TLV

LENGT H 1 1 2 2 3-23

The L3 Information field is present only if the SABM frame contained a non-empty information field. NOTE: The "establish mode" parameter appearing in GSM 04.06 is used only on

the MS side.

2.2 Signaling element coding


2.2.1 Message discriminator
A 1 octet field is used in all messages to discriminate between Transparent and NonTransparent messages and also between Radio Link Layer Management, Dedicated Channel Management, Common Channel Management and TRX Management messages.
8 G7 7 G6 6 G5 5 G4 4 G3 3 G2 2 G1 T 1

The T-bit is set to 1 to indicate that the message is to be/was considered transparent by BTS. All other messages shall have the T-bit set to 0. The G-bits are used to group the messages as follows:

G7 0 0 0 0 0 0 All

G6 G5 G4 G3 G2 G1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0

Message Group

reserved Radio Link Layer Management messages Dedicated Channel Management messages 0 0 0 1 1 0 Common Channel Management messages 0 0 1 0 0 0 TRX Management messages 0 1 0 0 0 0 Location Services messages other values are reserved for future use

65

Messages Reference

Chapter 2 Abis-Interface Key Messages

2.2.2 MESSAGE TYPE


The Message Type uniquely identifies the function of the message being sent. It is a single octet and coded in the following way:
8 EM 7 6 5 4 3 2 1

Message type

Bit 8 is the extension bit and is reserved for future use. The following message types are used (all other values are reserved):
87654321 0000---0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 0001---0001 0010 0011 0100 0101 0110 0111 1001 1010 1011 1100 1101 1110 1111 001----00001 00010 00011 00100 00101 00110 00111 01000 01001 01010 01011 01100 01101 Message Radio Link Layer Management messages DATA REQuest DATA INDication ERROR INDication ESTablish REQuest ESTablish CONFirm ESTablish INDication RELease REQuest RELease CONFirm RELease INDication UNIT DATA REQuest UNIT DATA INDication Common Channel Management/TRX Management messages BCCH INFOrmation CCCH LOAD INDication CHANnel ReQuireD DELETE INDication PAGING CoMmanD IMMEDIATE ASSIGN COMMAND SMS BroadCast REQuest RF RESource INDication SACCH FILLing OVERLOAD ERROR REPORT SMS BroadCast CoMmanD CBCH LOAD INDication NOTification CoMmanD Dedicated Channel Management messages CHANnel ACTIVation CHANnel ACTIVation ACKnowledge CHANnel ACTIVation Negative ACK CONNection FAILure DEACTIVATE SACCH ENCRyption CoMmanD HANDOver DETection MEASurement RESult MODE MODIFY REQuest MODE MODIFY ACKnowledge MODE MODIFY Negative ACKnowledge PHYsical CONTEXT REQuest PHYsical CONTEXT CONFirm

66

Messages Reference

Chapter 2 Abis-Interface Key Messages

87654321 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0

Message RF CHANnel RELease MS POWER CONTROL BS POWER CONTROL PREPROCess CONFIGure PREPROCessed MEASurement RESult RF CHANnel RELease ACKnowledge SACCH INFO MODIFY TALKER DETection LISTENER DETection REMOTE CODE CONFiguration REPort Round Trip Delay REPort PRE-HANDOver NOTIFication MultiRate CODE MODification REQest MultiRate CODE MOD ACKnowledge MultiRate CODE MOD Negative ACKnowledge MultiRate CODE MOD PERformed TFO REPort TFO MODification REQuest Location Service messages Location Information

11101 11110 11111 01-----000001

2.2.3 Channel Number


In the direction BSC to BTS the Channel Number parameter is used to indicate on which physical channel/subchannel the message is to be sent. In the direction BTS to BSC the Channel Number indicates on which physical channel/subchannel the message was received. It is coded in two octets as follows:
8 7 6 5 4 3 2 1

Element identifier C5 C4 C3 C2 C1 TN

The C-bits describe the channel as follows:


C5 C4 C3 C2 C1 0 0 0 1 0 0 0 T 0 0 1 T 0 1 T T 1 0 0 0 1 0 0 1 1 0 0 0

0 Bm + ACCH's 1 Lm + ACCH's T SDCCH/4 + ACCH T SDCCH/8 + ACCH

0 BCCH 0 Uplink CCCH (RACH) 1 Downlink CCCH (PCH + AGCH)

67

Messages Reference

Chapter 2 Abis-Interface Key Messages

The T-bits indicate, coded in binary, GSM 05.02.

the sub-channel number as specified in

TN is time slot number, binary represented as in GSM 05.02.

2.2.4 Request Reference


This element carries the Request Reference parameters used for contention resolution on RACH.
8 7 6 5 4 3 2 1 1 2 3 4

Element identifier RA T1' T3 (low)

T3 (high) T2

Octets 2-4 are coded as the corresponding fields of the Request Reference element of GSM 04.08. (Octet 2, RA, is the Random Access Information field set by MS in the CHANnel REQuest message. Octets 3-4 contain the absolute frame number modulo 42432 for the frame number when the access burst was received, see Starting Time information element of GSM 04.08).

2.2.5 Access Delay


This element contains the delay of the access burst as measured by BTS at random access or at handover access.
8 7 6 5 4 3 2 1 1 2

Element identifier Access Delay

The Access Delay field contains the delay of the access burst as measured by BTS. The delay is expressed as defined for the Timing Advance TA in GSM 05.10 but with the range extended to 8 bits, i.e. the six least significant bits of the field correspond to the Timing Advance.

2.2.6 Physical Context


This element contains supplementary information on the transmission/reception process. It is a variable length element.
8 7 6 5 4 3 2 1 1 2 3

Element identifier Length Physical Context

68

Messages Reference Information

Chapter 2 Abis-Interface Key Messages N

The Physical Context Information field is not specified. This information should not be analyzed by BSC, but merely forwarded from one TRX/channel to another.

2.2.7 Paging Group


This element carries the paging population of an MS to be paged.
8 7 6 5 4 3 2 1 1 2

Element identifier Paging Group

The Paging Group field (octet 2) contains the binary representation of the paging group as defined in GSM 05.02.

2.2.8 MS Identity
This element carries the identity of an MS (TMSI or IMSI). It is a variable length element.
8 7 6 5 4 3 2 1 1 2 3 : N

Element identifier Length MS Identity

The MS Identity field (octets 3-N) is coded as specified for the Mobile Identity information element of GSM 04.08, octets 3-N.

2.2.9 Channel Needed


This information element is used to indicate to the mobile station which channel will be needed for the transaction linked to the paging procedure.
8 7 6 5 4 3 2 Channel 1 1 2

Element identifier Reserved for future use

The Channel Field (bits 1-2 of octet 2) indicates the further combination of channel which will be needed. It is coded as follows: Value Channel Needed.
69

Messages Reference

Chapter 2 Abis-Interface Key Messages

00 01 10 11

Any Channel. SDCCH. TCH/F (Full rate). TCH/F or TCH/H (Dual rate).

2.2.10 eMLPP Priority


This Information Element contains the eMLPP priority of the call. It is coded as follows:
8 7 6 5 4 3 2 1 1 2

Element identifier spare

call priority

The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in the Descriptive group or broadcast call reference information element as defined in GSM 04.08.

2.2.11 Activation Type


This element is used to indicate the type of activation requested in the CHANnel ACTIVation message. It is coded in two octets as follows:
8 7 6 5 4 3 A3 2 A2 1 A1 1 2

Element identifier R Reserved

The R bit indicates if the procedure is an initial activation or a reactivation. R 0 1 Initial activation Reactivation

The A-bits indicate the type of activation, which defines the access procedure and the operation of the data link layer, as follows: A3 A2 A1 0 0 - Activation related to intra-cell channel change 0 1 - related to immediate assignment procedure - related to normal assignment procedure

70

Messages Reference

Chapter 2 Abis-Interface Key Messages

0 1 - Activation related to inter-cell channel change (handover) 0 1 - related to asynchronous handover procedure - related to synchronous handover procedure

1 0 - Activation related to secondary channels 0 1 - related to additional assignment procedure - related to multislot configuration

All other values reserved for future use. NOTE: For the main TCH channel in a Multislot configuration activation types for

intra-cell and inter-cell channel change are used.

2.2.12 Channel Mode


This element gives information on the mode of coding/decoding and transcoding/rate adaption of a channel.
8 7 6 5 4 3 2 1 1 2 3 4 5 6

Element identifier Length Reserved for future use Speech or data indicator Channel rate and type Speech coding algor./data rate + transp ind

DTXd

DTXu

The DTX bits of octet 3 indicate whether DTX is applied: 1 DTX is applied 0 DTX is not applied. DTXd indicates use of DTX in the downlink direction (BTS to MS) and DTXu indicates use of DTX in the uplink direction (MS to BTS). The "Speech or data indicator" field (octet 4) is coded as follows: 0000 0001 Speech 0000 0010 Data 0000 0011 Signaling All other values are reserved. The "Channel rate and type" field (octet 5) is coded as follows: 0000 0001 SDCCH

71

Messages Reference

Chapter 2 Abis-Interface Key Messages

0000 1000 Full rate TCH channel Bm 0000 1001 Half rate TCH channel Lm 0000 1010 Full rate TCH channel bi-directional Bm, Multislot configuration 0001 1010 Full rate TCH channel uni-directional downlink Bm, Multislot configuration 0001 1000 Full rate TCH channel Bm Group call channel 0001 1001 Half rate TCH channel Lm Group call channel 0010 1000 Full rate TCH channel Bm Broadcast call channel 0010 1001 Half rate TCH channel Lm Broadcast call channel All other values are reserved. The "speech coding algorithm/data rate + transparency indicator" field (octet 6) is coded as follows: If octet 4 indicates speech, then octet 6 is coded as follows: 0000 0001 GSM speech coding algorithm version 1 0001 0001 GSM speech coding algorithm version 2 0010 0001 GSM speech coding algorithm version 3 All other values are reserved. If octet 4 indicates signaling then octet 6 is coded as follows: 0000 0000 No resources required All other values are reserved. NOTE: GSM speech coding algorithm version 3 is also referred as GSM adaptive multirate speech coding algorithm version 1. If octet 4 indicates data, then octet 6 is coded as follows:
8 ext 7 T/NT 6 Rate 5 4 3 2 1 octet 6

Bit 8: Reserved for extension Bit 7: 0 Transparent service 1 Non-transparent service. For the non-transparent service, bits 6 to 1 indicate the radio interface data rate: 65 4321

72

Messages Reference

Chapter 2 Abis-Interface Key Messages

01 1000 14.5 kbit/s 01 0000 12 kbit/s 01 0001 6 kbit/s all other values are reserved. For the transparent service, bits 6-1 indicate the data rate: 65 4321 01 1000 14.4 kbit/s 01 0000 9.6 kbit/s 01 0001 4.8 kbit/s 01 0010 2.4 kbit/s 01 0011 1.2 kbit/s 01 0100 600 bit/s 01 0101 1 200/75 bit/s (1 200 network-to-MS, 75 MS-to-network) All other values are reserved.

2.2.13 Channel Identification


This information element describes some aspects of a channel together with its SACCH.
8 7 6 5 4 3 2 1 1 2 * *

Element identifier Length 04.08 "Channel Description" 04.08 "Mobile Allocation"

A * denotes that the whole of the 04.08 element including the element identifier and length should be included. The 04.08 "Mobile Allocation" shall for compatibility reasons be included but empty, i.e. the length shall be zero.

2.2.14 Encryption information


This element is a variable length element. It contains necessary information to control encryption devices.
8 7 6 5 4 3 2 1 1 2

Element identifier Length

73

Messages Reference Algorithm identifier Key

Chapter 2 Abis-Interface Key Messages 3 4

The Algorithm Identifier field (octet 3) indicates the relevant ciphering algorithm. It is coded as: 0000 0000 Reserved 0000 0001 No encryption shall be used. 0000 0010 GSM encryption algorithm version 1 (A5/1) 0000 0011 GSM A5/2 0000 0100 GSM A5/3 0000 0101 GSM A5/4 0000 0110 GSM A5/5 0000 0111 GSM A5/6 0000 1000 GSM A5/7 All other values are reserved The Key field (octets 4-n) indicates the ciphering key. It shall be an integral number of octets and the length is given as the value of the Length field minus 1.

2.2.15 Handover reference


The information is coded in two octets and contains the handover reference value.
8 7 6 5 4 3 2 1 1 2

Element identifier Handover reference

The Handover Reference octet contains the handover reference value as defined in GSM 04.08.

2.2.16 BS Power
This information element indicates the TRX transmission power level on a particular channel.

74

Messages Reference 8 7 6 5 4 3 2

Chapter 2 Abis-Interface Key Messages 1 1 2

Element identifier Reserved Power Level

The Power Level field (octet 2) indicates the number of 2 dB steps by which the power shall be reduced from its nominal value, Pn, set by the network operator to adjust the coverage. Thus the Power Level values correspond to the following powers (relative to Pn): Value 00000 00001 00010 01110 01111 Power level Pn Pn - 2 dB Pn - 4 dB Pn - 28 dB Pn - 30 dB

All other values are reserved for future use. See also GSM 05.05, subclass 4.1.2 and GSM 05.08, subclass 4.5.

2.2.17 MS Power
This element carries the power level of MS.
8 7 6 5 4 3 2 1 1 2

Element identifier Reserved

Power Level

The coding and meaning of the Power Level field is as defined in GSM 05.05 and GSM 05.08. See also GSM 04.04.

2.2.18 Timing Advance


This element contains the timing advance to be used by MS in subsequent communications. It is calculated by BTS at the reception of a CHANnel REQuest message (random access burst) or a handover access burst.
8 7 6 5 4 3 2 1 1 2

Element identifier Reserved Timing Advance

The Timing Advance field contains the timing advance TA as specified in GSM 05.10.
75

Messages Reference

Chapter 2 Abis-Interface Key Messages

Bits 7-8 of octet 2 are reserved for future use.

2.2.19 MS Power Parameters


This element carries the parameters required by TRX for MS power control.
8 7 6 5 4 3 2 1 1 2 3

Element identifier Length MS Power Control Parameters

The MS Power Control Parameters field contains the parameters and limits required when MS power control is to be performed by BTS. The coding is operator dependant. Examples of possible parameters and algorithms can be found in GSM 05.08 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance) etc.).

2.2.20 BS Power Parameters


This element carries the parameters required by TRX for control of its own transmission power.
8 7 6 5 4 3 2 1 1 2 3 : N

Element identifier Length BS Power Control Parameters

The BS Power Control Parameters field contains the parameters and limits required when TRX transmission power control is to be performed by BTS. The coding is operator dependant. Examples of possible parameters and algorithms can be found in GSM 05.08 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance) etc.).

2.2.21 SACCH Information


This element is used to carry the SACCH filling information (System Information messages, or EXTENDED MEASUREMENT ORDER message) that is to be used on a specific channel.
8 7 6 5 4 3 2 1 1

Element identifier

76

Messages Reference Length Number of messages Type of 1st message Length of 1st message 1st message

Chapter 2 Abis-Interface Key Messages 2 3 4 5 : j l l+1 N

Type of n'th message Length of n'th message n'th message

The Length field (octet 2) indicates in binary the total remaining length of the element (octets 3 - N). The Number of SI messages field (octet 3) indicates in binary the number of messages contained in the element. The coding of each of these messages consists of a type field (Type of nth msg), a length field (Length of nth message) and a message field (nth message). The "Type of nth msg" field indicates the type of SYSTEM INFORMATION, or an EXTENDED MEASUREMENT ORDER message that follows in the "nth message" field. It is coded as follows: Value 0000 0101 0000 0110 0000 1101 0000 1110 0100 0111 Message SYSTEM INFORMATION 5 SYSTEM INFORMATION 6 SYSTEM INFORMATION 5bis SYSTEM INFORMATION 5ter EXTENDED MEASUREMENT ORDER

All other values are reserved. The "Length of nth SI message" field indicates in binary the length of the "nth message" field that follows. The "nth message" field contains a complete SACCH message as defended in GSM 04.08.

2.2.22 UIC
It is coded as follows:

77

Messages Reference 8 7 6 5 4

Chapter 2 Abis-Interface Key Messages 3 2 1 1 2 3

Element identifier Length UIC information

Octet 3 bits 1 to 6 contain the radio interface octet 2 bits 3 to 8 of the UIC information element as defined in GSM 04.08. Octet 3 bits 7 and 8 are spare and set to zero.

2.2.23 Main channel reference


This element contains the main channel reference of a multislot connection. It is coded in two octets as follows:
8 7 6 5 4 3 TN 2 1 1 2

Element identifier Reserved for future use

TN is time slot number, binary represented as in GSM 05.02.

2.2.24 MultiRate configuration


This element gives the description of the multirate speech code configuration to be applied.
8 7 6 5 4 3 2 1 1 2 3-n

Element identifier Length Rest of element coded as in GSM 04.08 not including GSM 04.08 element identifier or GSM 04.08 octet length value

2.2.25 MultiRate Control


This element indicates whether TFO is enabled or not and whether the BSC authorises the BTS to perform autonomously multi-rate code changes and whether an handover is to be expected. It is coded in two octets as follows:
8 7 6 5 4 PRE 3 RAE 2 1 TFO 1 3

Element identifier Spare

78

Messages Reference

Chapter 2 Abis-Interface Key Messages

The TFO field (bit 1 of octet 3) indicates if TFO is enabled or not. It is coded as follows: Value 0 1 TFO

Tandem Free Operation is enabled Tandem Free Operation is disabled

The RAE field (bits 2-3, octet 3) defines whether the RATSCCH mechanism is enabled or not. It is coded as follows: Value RAE

0 0 RATSCCH mechanism is generally enabled, the BTS may change the AMR configuration within the given SCS and MACS constraints and within the given radio and Abis channel. 0 1 RATSCCH mechanism will potentially be enabled for one exchange. The BSC will use a MultiRate CODE MOD REQ message for that purpose 1 0 reserved 1 1 RATSCCH mechanism is generally disabled The PRE field (bit 4 of octet 3) indicates if an handover is to be expected soon or not. It is coded as follows: Value 0 1 PRE

Handover is not expected, respectively has failed Handover is expected soon

2.2.26 Supported Code Types


This element indicates the code types supported by the BSS or remote BSS. It is coded as follows:
8 7 6 5 4 3 2 1 1 2 3 4-n n+1

Element identifier Length Sys-ID ext Code List Preferred Code Type

The Sys-ID field (octet 3) identifies the system that sends or has sent the configuration. It should be set to 0000 0000 for GSM. The Code List field (octet 4) lists the code types that are supported by the BSS and Transcoder, and are therefore potential candidates for TFO establishment. If the

79

Messages Reference

Chapter 2 Abis-Interface Key Messages

Preferred Code Type is not present (this field is set to 1111.1111), then the Code List belongs to the remote BSS, otherwise it is the list of alternative Preferred Code Types. It is coded as follows: Bit 1: Set to 1 if the GSM FR Speech Code is supported. Bit 2: Set to 1 if the GSM HR Speech Code is supported. Bit 3: Set to 1 if the GSM EFR Speech Code is supported. Bit 4: Set to 1 if the GSM FR AMR Speech Code is supported. Bit 5: Set to 1 if the GSM HR AMR Speech Code is supported Bit 6-7: Reserved, set to 0. Bit 8: Reserved for extension, set to 0. If bit 4 of the Code List field (octet 4) indicates that FR AMR is supported or if bit 5 of the Code List field (octet 4) indicates that HR AMR is supported, the following two octets (octets 5-6) should be coded as follows:
8 Spare SCS 7 6 5 4 TFO_VER 3 2 MACS 1 5 6

If both FR AMR and HR AMR are supported, the octets 5-6 shall be sent twice. The first occurrence shall correspond to FR AMR configuration, the second one shall correspond to HR AMR configuration. The MACS field (bits 1-2 of octet 5, if present) indicates the Maximum number of AMR Code ModeS the BSS can support in the Active Code Set. It should be coded as follows: 0 0: A maximum of four code modes can be supported in the Active Code Set 0.1: A maximum of one code mode can be supported in the Active Code Set 1.0: A maximum of two code modes can be supported in the Active Code Set 1.1: A maximum of three code modes can be supported in the Active Code Set The TFO_VER field (bits 3-4 of octet 5, if present) indicates the TFO_VERSION. 0 0 : Version 0 of TFO All other values reserved for future used The SCS field (octet 6 if present) indicates the Set of AMR Code modes Supported by the BSS. It should be coded as follows: Bit 8: Set to 1 if the AMR 12.2 Code Mode is supported.
80

Messages Reference

Chapter 2 Abis-Interface Key Messages

Bit 7: Set to 1 if the AMR 10.2 Code Mode is supported. Bit 6: Set to 1 if the AMR 7.95 Code Mode is supported. Bit 5: Set to 1 if the AMR 7.40 Code Mode is supported. Bit 4: Set to 1 if the AMR 6.70 Code Mode is supported. Bit 3: Set to 1 if the AMR 5.90 Code Mode is supported. Bit 2: Set to 1 if the AMR 5.15 Code Mode is supported. Bit 1: Set to 1 if the AMR 4.75 Code Mode is supported. The Preferred Code Field (bits 1-8, octet n+1) indicates the preferred code type for TFO establishment. It is coded as follows; 0 0 0 0 . 0 0 0 0: Full Rate Code is preferred 0 0 0 0 . 0.0 0 1: Half Rate Code is preferred 0 0 0 0 . 0 0 1.0: Enhanced Full Rate Code is preferred 0 0 0 0 . 0 0 1.1: FR Adaptive Multi-Rate Code is preferred 0 0 0 0 . 0 1 0 0: HR Adaptive Multi-Rate Code is preferred 1 1 1 1 . 1 1 1 1: No preferred code type All other values reserved for future used

2.2.27 Frame Number


This element contains the absolute frame number (FN) modulo 42432. It is used to carry the current timing in BTS to BSC for calculation of the Starting Time parameter required in some messages.
8 7 6 5 4 3 T3 (high) T2 2 1 1 2 3

Element identifier T1' T3 (low)

Octets 2-3 are coded as defined for octets 2-3 of the Starting Time information element of GSM 04.08.

2.2.28

Cause

The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below.

81

Messages Reference 8 7 6 5 4

Chapter 2 Abis-Interface Key Messages 3 2 1 1 2 3 3a 4 N

Element identifier Length E Cause Value Cause Extension Diagnostic(s) if any

The Length field indicates in binary the remaining length of the element (octets 3-N). The Cause Value is a single octet field (octet 3) if the extension bit E (bit 8) is set to 0. If it is set to 1 then the cause value is a 2 octet field (octets 3 and 3a). The Cause Value is divided into two fields: a class (bits 5-7 of octet 3) and a value within the class (bits 1-4 of octet 3). If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national applications (XXX will still indicate the class). Diagnostic information is not available for every cause, see the table below. When available, it is coded in the same way as the corresponding information element in clause 9. Inclusion of diagnostics is optional. Classes: Class (000): Normal event Class (001): Normal event Class (010): Resource unavailable Class (011): Service or option not available Class (100): Service or option not implemented Class (101): Invalid message (e.g. parameter out of range) Class (110): Protocol error Class (111): Interworking CAUSE VALUES:
Class 000 000 000 000 000 000 000 Value - - - 0000 0001 0010 0011 0100 0101 Cause Normal Event radio interface failure radio link failure handover access failure talker access failure reserved for international use reserved for international use Diagnostics Channel Channel Channel Channel Number Number Number Number

82

Messages Reference

Chapter 2 Abis-Interface Key Messages

Class 000 000 000 000 000 000 001 001 001 001 001 001 001 010 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0

Value 0110 0111 1000 1 : : : 1110 1111 - - - 0000 0 : : : 0111 1000 1 : : : 1111 - - - 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0

Cause reserved for international use O&M intervention reserved for international use normal event, unspecified Normal Event reserved for international use reserved for national use Resource unavailable equipment failure radio resource not available terrestrial channel failure CCCH overload ACCH overload processor overload reserved for international use BTS not equipped remote transcoder failure notification overflow reserved for international use reserved for international use reserved for national use reserved for national use reserved for national use resource not available, unspecified Service or Option Not Available requested transcoding/rate adaption not available reserved for international use service or option not available, unspecified Service or Option Not Implemented encryption algorithm not implemented reserved for international use reserved for national use service or option not implemented, unspecified

Diagnostics

Channel Channel Channel Channel

Number Number Number Number

Channel Number Channel Number

010 0 0 0 0 1 1 1 1 0 0 0 0

1011 1 1 1 1 1 1 1 1 0 0 1 1 0 1 0 1

011 011 011 011 011 011 100 100 100 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0

- - - 0000 0001 : : : : 1110 1111 - - - 0000 0001 0 0 1 1 1 1 : : : 111 000 : : : 110 111

Channel Number

Channel Number

83

Messages Reference

Chapter 2 Abis-Interface Key Messages

Class 101 101 101 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1

Value - - - 0000 0001 0 0 1 1 1 1 : : : 111 000 : : : 110 111

Cause Invalid Message radio channel already activated/allocated reserved for international use reserved for national use invalid message, unspecified Protocol Error message discriminator error message type error message sequence error general information element error mandatory information element error optional information element error information element nonexistent information element length error invalid information element contents reserved for international use reserved for international use reserved for international use reserved for national use reserved for national use reserved for national use protocol error, unspecified Interworking reserved for international use reserved for national use interworking, unspecified

Diagnostics Channel Number

110 110 110 110 110 110 110 110 110 110 110 110 110 110 110 110 110 111 111 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

- - - 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 - - - 0000 0 0 1 1 1 1 : : : 111 000 : : : 110 111

Message Discrim Message Type Message Type Element Identif Element Identif Element Identif Element Identif Inform. Element

2.2.29 Full Immediate Assign Info


This element is used to convey a full L3 immediate assign message (3 types).
8 7 6 5 4 3 2 1 1 2 3

Element identifier Length Indicator Full Immediate

84

Messages Reference Assign Info

Chapter 2 Abis-Interface Key Messages

25

The Length Indicator field (octet 2) indicates in binary the remaining length of the element (octets 3-25). The Full Immediate Assign Info field (octets 3-25) contains a complete immediate assign message (IMMEDIATE ASSIGN or IMMEDIATE ASSIGN EXTENDED or IMMEDIATE ASSIGN REJECT) as defined in GSM 04.08.

2.2.30 Link Identifier


This element identifies the signaling channel and SAPI of the radio data link.
8 7 6 5 4 3 SAPI 2 1 1 2

Element identifier C2 C1 NA priority

The NA bit (bit 6 in octet 2) is set to 1 to indicate that the Link Identifier is not applicable for this message. In all other cases it is set to 0. The C-bits indicate the channel type as follows: C2 C1 0 0 main signaling channel (FACCH or SDCCH) 0 1 SACCH All other values are reserved for future use. The SAPI field contains the SAPI value as defined in GSM 04.05. The priority field contains the message priority for SAPI 0, as defined in GSM 04.06, as follows: 00 01 10 normal priority high priority low priority

All other values for SAPI 0 and all values for other SAPIs are reserved for future use.

2.2.31 RLM Cause


This element is used to indicate the precise protocol error or the reason for a release on the radio link layer.

85

Messages Reference 8 7 6 5 4

Chapter 2 Abis-Interface Key Messages 3 2 1 1 2 3

Element identifier Length E Cause Value

The Cause Value is a one octet field if the extension bit is set to 0. If the extension bit is set to 1, the Cause Value is a two octet field. The Cause Value field is coded as follows: 87654321 0 0 0 0 0 0 0 0 reserved 0 0 0 0 0 0 0 1 timer T200 expired (N200+1) times 0 0 0 0 0 0 1 0 re-establishment request 0 0 0 0 0 0 1 1 unsolicited UA response 0 0 0 0 0 1 0 0 unsolicited DM response 0 0 0 0 0 1 0 1 unsolicated DM response, multiple frame established state 0 0 0 0 0 1 1 0 unsolicited supervisory response 0 0 0 0 0 1 1 1 sequence error 0 0 0 0 1 0 0 0 U-frame with incorrect parameters 0 0 0 0 1 0 0 1 S-frame with incorrect parameters 0 0 0 0 1 0 1 0 I-frame with incorrect use of M bit 0 0 0 0 1 0 1 1 I-frame with incorrect length 0 0 0 0 1 1 0 0 frame not implemented 0 0 0 0 1 1 0 1 SABM command, multiple frame established state 0 0 0 0 1 1 1 0 SABM frame with information not allowed in this state All other values are reserved for future use.

2.2.32 L3 Information (message name)


This element contains a link layer service data unit (L3 message). It is used to forward a complete L3 message as specified in GSM 04.08 between BTS and BSC.
8 7 6 5 4 3 2 1 1 2

Element identifier Length

86

Messages Reference Indicator Link Layer Service Data Unit (i.e. a layer 3 message as defined in GSM 04.08)

Chapter 2 Abis-Interface Key Messages 3 4 n

The Length Indicator field (octets 2-3) indicates in binary the remaining length of the element (octets 4-n). The most significant bit is bit 8 of octet 2 and the least significant bit is bit 1 of octet 3. Octets 4-n contain the complete L3 message as defined in GSM 04.08. In the message format section, the 04.08 message name to be included is indicated within brackets.

87

Anda mungkin juga menyukai