3.2.2 Signalling element coding

08.083GPPMobile-services Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 SpecificationRelease 1999TS

This paragraph contains the CODING of the signalling 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.

Table: Signalling elements used and their CODING

Element Identifier Coding

Element name

Reference

0000 0001

Circuit Identity Code

3.2.2.2

0000 0010

Reserved

*

0000 0011

Resource Available

3.2.2.4

0000 0100

Cause

3.2.2.5

0000 0101

Cell Identifier

3.2.2.17

0000 0110

Priority

3.2.2.18

0000 0111

Layer 3 Header Information

3.2.2.9

0000 1000

IMSI

3.2.2.6

0000 1001

TMSI

3.2.2.7

0000 1010

Encryption Information

3.2.2.10

0000 1011

Channel Type

3.2.2.11

0000 1100

Periodicity

3.2.2.12

0000 1101

Extended Resource Indicator

3.2.2.13

0000 1110

Number Of MSs

3.2.2.8

0000 1111

Reserved

*

0001 0000

Reserved

*

0001 0001

Reserved

*

0001 0010

Classmark Information Type 2

3.2.2.19

0001 0011

Classmark Information Type 3

3.2.2.20

0001 0100

Interference Band To Be Used

3.2.2.21

0001 0101

RR Cause

3.2.2.22

0001 0110

Reserved

*

0001 0111

Layer 3 Information

3.2.2.24

0001 1000

DLCI

3.2.2.25

0001 1001

Downlink DTX Flag

3.2.2.26

0001 1010

Cell Identifier List

3.2.2.27

0001 1011

Response Request

3.2.2.28

0001 1100

Resource Indication Method

3.2.2.29

0001 1101

Classmark Information Type 1

3.2.2.30

0001 1110

Circuit Identity Code List

3.2.2.31

0001 1111

Diagnostic

3.2.2.32

0010 0000

Layer 3 Message Contents

3.2.2.35

0010 0001

Chosen Channel

3.2.2.33

0010 0010

Total Resource Accessible

3.2.2.14

0010 0011

Cipher Response Mode

3.2.2.34

0010 0100

Channel Needed

3.2.2.36

0010 0101

Trace Type

3.2.2.37

0010 0110

Triggerid

3.2.2.38

0010 0111

Trace Reference

3.2.2.39

0010 1000

Transactionid

3.2.2.40

0010 1001

Mobile Identity

3.2.2.41

0010 1010

OMCId

3.2.2.42

0010 1011

Forward Indicator

3.2.2.43

0010 1100

Chosen Encryption Algorithm

3.2.2.44

0010 1101

Circuit Pool

3.2.2.45

0010 1110

Circuit Pool List

3.2.2.46

0010 1111

Time Indication

3.2.2.47

0011 0000

Resource Situation

3.2.2.48

0011 0001

Current Channel type 1

3.2.2.49

0011 0010

Queueing Indicator

3.2.2.50

0100 0000

Speech Version

3.2.2.51

0011 0011

Assignment Requirement

3.2.2.52

0011 0101

Talker Flag

3.2.2.54

0011 0110

Connection Release Requested

3.2.2.3

0011 0111

Group Call Reference

3.2.2.55

0011 1000

eMLPP Priority

3.2.2.56

0011 1001

Configuration Evolution Indication

3.2.2.57

0011 1010

Old BSS to New BSS Information

3.2.2.58

0011 1011

LSA Identifier

3.2.2.15

0011 1100

LSA Identifier List

3.2.2.16

0011 1101

LSA Information

3.2.2.23

0011 1110

LCS QoS

3.2.2.60

0011 1111

LSA access control suppression

3.2.2.61

0100 0011

LCS Priority

3.2.2.62

0100 0100

Location Type

3.2.2.63

0100 0101

Location Estimate

3.2.2.64

0100 0110

Positioning Data

3.2.2.65

0100 0111

LCS Cause

3.2.2.66

0100 1000

LCS Client Type

3.2.2.67

0100 1001

APDU

3.2.2.68

0100 1010

Network Element Identity

3.2.2.69

0100 1011

GPS Assistance Data

3.2.2.70

0100 1100

Deciphering Keys

3.2.2.71

0100 1101

Return Error Request

3.2.2.72

0100 1110

Return Error Cause

3.2.2.73

0100 1111

Segmentation

3.2.2.74

0101 0000

Service Handover

3.2.2.75

0101 0001 (NOTE)

Source RNC to target RNC transparent information (UMTS)

3.2.2.76

0101 0010 (NOTE)

Source RNC to target RNC transparent information (cdma2000)

3.2.2.77

0100 0001

Reserved

#

0100 0010

Reserved

#

NOTE. This encoding aligns with the RANAP specified tagging.The coding is defined in relevant RANAP specification TS 25.413.

* Information Element codes marked as "reserved" are reserved for use by previous versions of this interface specification

# Information Element codes marked as "reserved" are reserved for use by ANSI version of this interface specification

3.2.2.1 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.

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0

Reserved.

ASSIGNMENT MESSAGES

0 0 0 0 0 0 0 1

ASSIGNMENT REQUEST

0 0 0 0 0 0 1 0

ASSIGNMENT COMPLETE

0 0 0 0 0 0 1 1

ASSIGNMENT FAILURE

HANDOVER MESSAGES

0 0 0 1 0 0 0 0

HANDOVER REQUEST

0 0 0 1 0 0 0 1

HANDOVER REQUIRED

0 0 0 1 0 0 1 0

HANDOVER REQUEST ACKNOWLEDGE

0 0 0 1 0 0 1 1

HANDOVER COMMAND

0 0 0 1 0 1 0 0

HANDOVER COMPLETE

0 0 0 1 0 1 0 1

HANDOVER SUCCEEDED

0 0 0 1 0 1 1 0

HANDOVER FAILURE

0 0 0 1 0 1 1 1

HANDOVER PERFORMED

0 0 0 1 1 0 0 0

HANDOVER CANDIDATE ENQUIRE

0 0 0 1 1 0 0 1

HANDOVER CANDIDATE RESPONSE

0 0 0 1 1 0 1 0

HANDOVER REQUIRED REJECT

0 0 0 1 1 0 1 1

HANDOVER DETECT

RELEASE MESSAGES

0 0 1 0 0 0 0 0

CLEAR COMMAND

0 0 1 0 0 0 0 1

CLEAR COMPLETE

0 0 1 0 0 0 1 0

CLEAR REQUEST

0 0 1 0 0 0 1 1

RESERVED

0 0 1 0 0 1 0 0

RESERVED

0 0 1 0 0 1 0 1

SAPI "N" REJECT

0 0 1 0 0 1 1 0

CONFUSION

OTHER CONNECTION RELATED MESSAGES

0 0 1 0 1 0 0 0

SUSPEND

0 0 1 0 1 0 0 1

RESUME

0 0 1 0 1 0 1 0

CONNECTION ORIENTED INFORMATION

0 0 1 0 1 0 1 1

PERFORM LOCATION REQUEST

0 0 1 0 1 1 0 0

LSA INFORMATION

0 0 1 0 1 1 0 1

PERFORM LOCATION RESPONSE

0 0 1 0 1 1 1 0

PERFORM LOCATION ABORT

0 0 1 0 1 1 1 1

COMMON ID

GENERAL MESSAGES

0 0 1 1 0 0 0 0

RESET

0 0 1 1 0 0 0 1

RESET ACKNOWLEDGE

0 0 1 1 0 0 1 0

OVERLOAD

0 0 1 1 0 0 1 1

RESERVED

0 0 1 1 0 1 0 0

RESET CIRCUIT

0 0 1 1 0 1 0 1

RESET CIRCUIT ACKNOWLEDGE

0 0 1 1 0 1 1 0

MSC INVOKE TRACE

0 0 1 1 0 1 1 1

BSS INVOKE TRACE

0 0 1 1 1 0 1 0

CONNECTIONLESS INFORMATION

TERRESTRIAL RESOURCE MESSAGES

0 1 0 0 0 0 0 0

BLOCK

0 1 0 0 0 0 0 1

BLOCKING ACKNOWLEDGE

0 1 0 0 0 0 1 0

UNBLOCK

0 1 0 0 0 0 1 1

UNBLOCKING ACKNOWLEDGE

0 1 0 0 0 1 0 0

CIRCUIT GROUP BLOCK

0 1 0 0 0 1 0 1

CIRCUIT GROUP BLOCKING ACKNOWLEDGE

0 1 0 0 0 1 1 0

CIRCUIT GROUP UNBLOCK

0 1 0 0 0 1 1 1

CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE

0 1 0 0 1 0 0 0

UNEQUIPPED CIRCUIT

0 1 0 0 1 1 1 0

CHANGE CIRCUIT

0 1 0 0 1 1 1 1

CHANGE CIRCUIT ACKNOWLEDGE

RADIO RESOURCE MESSAGES

0 1 0 1 0 0 0 0

RESOURCE REQUEST

0 1 0 1 0 0 0 1

RESOURCE INDICATION

0 1 0 1 0 0 1 0

PAGING

0 1 0 1 0 0 1 1

CIPHER MODE COMMAND

0 1 0 1 0 1 0 0

CLASSMARK UPDATE

0 1 0 1 0 1 0 1

CIPHER MODE COMPLETE

0 1 0 1 0 1 1 0

QUEUING INDICATION

0 1 0 1 0 1 1 1

COMPLETE LAYER 3 INFORMATION

0 1 0 1 1 0 0 0

CLASSMARK REQUEST

0 1 0 1 1 0 0 1

CIPHER MODE REJECT

0 1 0 1 1 0 1 0

LOAD INDICATION

VGCS/VBS

0 0 0 0 0 1 0 0

VGCS/VBS SETUP

0 0 0 0 0 1 0 1

VGCS/VBS SETUP ACK

0 0 0 0 0 1 1 0

VGCS/VBS SETUP REFUSE

0 0 0 0 0 1 1 1

VGCS/VBS ASSIGNMENT REQUEST

0 0 0 1 1 1 0 0

VGCS/VBS ASSIGNMENT RESULT

0 0 0 1 1 1 0 1

VGCS/VBS ASSIGNMENT FAILURE

0 0 0 1 1 1 1 0

VGCS/VBS QUEUING INDICATION

0 0 0 1 1 1 1 1

UPLINK REQUEST

0 0 1 0 0 1 1 1

UPLINK REQUEST ACKNOWLEDGE

0 1 0 0 1 0 0 1

UPLINK REQUEST CONFIRMATION

0 1 0 0 1 0 1 0

UPLINK RELEASE INDICATION

0 1 0 0 1 0 1 1

UPLINK REJECT COMMAND

0 1 0 0 1 1 0 0

UPLINK RELEASE COMMAND

0 1 0 0 1 1 0 1

UPLINK SEIZED COMMAND

3.2.2.2 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

7

6

5

4

3

2

1

Element identifier

octet 1

a

b

c

d

e

f

g

h

octet 2

i

j

k

X

X

X

X

X

octet 3

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:

8

7

6

5

4

3

2

1

Element identifie

octet 1

CIC (least significant bits)

octet 2

CIC (most significant bits)

octet 3

3.2.2.3 Connection Release Requested

The element has a fixed length of one octet

8

7

6

5

4

3

2

1

Element identifier

octet 1

3.2.2.4 Resource Available

This element gives the number of full and half rate channels available on any given cell at the time of construction of the message.

It defines these parameters in terms of the number of channels available in five interference bands, the boundaries of these bands being set by O and M as follows:

Interference level: 0 —————————

Band 1

X1 —————————

Band 2

X2 —————————

Band 3

X3 —————————

Band 4

X4 —————————

Band 5

X5 —————————

The element is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Number of full rate

octet 2

channels available in band 1

octet 3

Number of half rate

octet 4

channels available in band 1

octet 5

Number of full rate

octet 18

channels available in band 5

octet 19

Number of half rate

octet 20

channels available in band 5

octet 21

Octets (2,3,4,5,) are then repeated for each of the other interference bands giving a total message length of 21 octets.

Octets 2 and 3 give a 16 bit binary representation of the number of full rate channels available for service but not currently assigned.

Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels available for service but not currently assigned. This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels.

(e.g. If there is a spare half rate channel and a spare full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3).

Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit.

3.2.2.5 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

Element identifier

octet 1

Length

octet 2

0/1 ext

Cause Value

octet 3

(octet 4)

The length indicator is a binary representation of the length of the following element.

Cause Value:

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 (eg parameter out of range)

Class (110) : protocol error

Class (111) : interworking

In the following table, "reserved for international use" means that this codepoint should not be used until a meaning has been assigned to it following the process of international standardisation. "Reserved for national use" indicates codepoints that may be used by operators without the need for international standardisation.

Cause value

Cause

Class

Value

Number

7

6

5

4

3

2

1

0

0

0

0

0

0

0

Radio interface message failure

0

0

0

0

0

0

1

Radio interface failure

0

0

0

0

0

1

0

Uplink quality

0

0

0

0

0

1

1

Uplink strength

0

0

0

0

1

0

0

Downlink quality

0

0

0

0

1

0

1

Downlink strength

0

0

0

0

1

1

0

Distance

0

0

0

0

1

1

1

O and M intervention

0

0

0

1

0

0

0

Response to MSC invocation

0

0

0

1

0

0

1

Call control

0

0

0

1

0

1

0

Radio interface failure, reversion to old channel

0

0

0

1

0

1

1

Handover successful

0

0

0

1

1

0

0

Better Cell

0

0

0

1

1

0

1

Directed Retry

0

0

0

1

1

1

0

Joined group call channel

0

0

0

1

1

1

1

Traffic

0

0

1

0

0

0

0

}

to

} Reserved for international use

0

0

1

0

1

1

1

}

0

0

1

1

0

0

0

}

to

} Reserved for national use

0

0

1

1

1

1

1

}

0

1

0

0

0

0

0

Equipment failure

0

1

0

0

0

0

1

No radio resource available

0

1

0

0

0

1

0

Requested terrestrial resource unavailable

0

1

0

0

0

1

1

CCCH overload

0

1

0

0

1

0

0

Processor overload

0

1

0

0

1

0

1

BSS not equipped

0

1

0

0

1

1

0

MS not equipped

0

1

0

0

1

1

1

Invalid cell

0

1

0

1

0

0

0

Traffic Load

0

1

0

1

0

0

1

Preemption

0

1

0

1

0

1

0

}

to

} Reserved for national use

0

1

0

1

1

1

1

}

0

1

1

0

0

0

0

Requested transcoding/rate adaption unavailable

0

1

1

0

0

0

1

Circuit pool mismatch

0

1

1

0

0

1

0

Switch circuit pool

0

1

1

0

0

1

1

Requested speech version unavailable

0

1

1

0

1

0

0

LSA not allowed

0

1

1

0

1

0

1

}

to

} Reserved for international use

0

1

1

1

1

1

1

}

1

0

0

0

0

0

0

Ciphering algorithm not supported

1

0

0

0

0

0

1

}

to

} Reserved for international use

1

0

0

0

1

1

1

}

1

0

0

0

1

1

1

}

to

} Reserved for national use

1

0

0

1

1

1

1

}

1

0

1

0

0

0

0

Terrestrial circuit already allocated

1

0

1

0

0

0

1

Invalid message contents

1

0

1

0

0

1

0

Information element or field missing

1

0

1

0

0

1

1

Incorrect value

1

0

1

0

1

0

0

Unknown Message type

1

0

1

0

1

0

1

Unknown Information Element

1

0

1

0

1

1

0

}

to

} Reserved for international use

1

0

1

0

1

1

1

}

1

0

1

1

0

0

0

}

to

} Reserved for national use

1

0

1

1

1

1

1

}

1

1

0

0

0

0

0

Protocol Error between BSS and MSC

1

1

0

0

0

0

1

VGCS/VBS call non existent

1

1

0

0

0

1

0

}

to

} Reserved for international use

1

1

0

0

1

1

1

}

1

1

0

1

0

0

0

}

to

} Reserved for national use

1

1

0

1

1

1

1

}

1

1

1

0

0

0

0

}

to

} Reserved for international use

1

1

1

0

1

1

1

}

1

1

1

1

0

0

0

}

to

} Reserved for national use

1

1

1

1

1

1

1

}

3.2.2.6 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 3GPP TS 04.08.

The element coding is:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Rest of element coded as in 3GPP TS 04.08, not including 3GPP TS 04.08 element identifier or 3GPP TS 04.08 octet length value

octet 3 – n

3.2.2.7 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

Element identifier

octet 1

Length

octet 2

TMSI

octet 3 – 6

The TMSI field is unstructured.

3.2.2.8 Number Of MSs

This is a fixed length element which indicates the number of handover candidates that have been sent to the MSC.

The coding is:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Number of handover candidates

octet 2

Octet 2 is a binary indication of the number of handover candidates. Bit 1 is the least significant bit.

3.2.2.9 Layer 3 Header Information

This element is used to supply the BSS with information that needs to be included in the header of layer 3 messages over the radio interface.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Protocol discriminator

octet 3

Transaction identifier

octet 4

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 3GPP TS 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.

3.2.2.10 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

Element identifier

octet 1

Length

octet 2

Permitted algorithms

octet 3

Key

octet 4 – n

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 meaning

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 repesented 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. Over MAP/E interface to 3G_MSC-B the key shall be present if available. When present, the key shall be 8 octets long.

3.2.2.11 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

Element identifier

octet 1

Length

octet 2

Spare

Speech / data indicator

octet 3

Channel rate and type

octet 4

Permitted speech version indication /

data rate + transparency indicator

octet 5

or

octet 5 with

extension *

* 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:

code meaning

0001 Speech

0010 Data

0011 Signalling

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:

code meaning

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.

0010 0xxx Full rate TCH channels in a multislot configuration, changes by the BSS of the 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;

bits

321 meaning

000 1 TCHs

001 2 TCHs

010 3 TCHs

011 4 TCHs

100 5 TCHs

101 6 TCHs

110 7 TCHs

111 8 TCHs

All other values are reserved.

If octet 3 indicates speech then octet 4 shall be coded as:

code meaning

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 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 signalling then octet 4 shall be coded as:

code meaning

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.

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

7

6

5

4

3

2

1

ext

permitted speech version identifier

octet 5

ext

permitted speech version identifier

octet 5a

ext

permitted speech version identifier

octet 5b

ext

permitted speech version identifier

octet 5c

ext

permitted speech version identifier

octet 5d

0

permitted speech version identifier

octet 5e

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;

bits

765 4321 meaning

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

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 non-empty 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

7

6

5

4

3

2

1

ext

T/NT

Rate

octet 5

ext

allowed

r i/f rates

octet 5a

ext

asymmetry

indication

spare

octet 5b

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.

Bit 7 :

0 Transparent service

1 Non-transparent service.

For non-transparent service bits 6-1 indicate the radio interface data rate;

65 4321 meaning

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

11 0100 43.5 kbit/s

11 0001 29 kbit/s

01 1000 14.5 kbit/s

01 0000 12 kbits/s

01 0001 6 kbits/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 meaning

11 1010 32.0 kbit/s

11 1001 28.8 kbit/s

01 1000 14.4 kbit/s

01 0000 9.6kbit/s

01 0001 4.8kbit/s

01 0010 2.4kbit/s

01 0011 1.2Kbit/s

01 0100 600 bit/s

01 0101 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 7 to 1 indicate allowed radio interface data rate, per channel;

Bit 7: 0 43.5 kbit/s (TCH/F43.2) not allowed

1 43.5 kbit/s (TCH/F43.2) allowed

Bit 6: 0 32.0 kbit/s (TCH/F32.0) not allowed
1 32.0 kbit/s (TCH/F32.0) allowed

Bit 5: 0 29.0 kbit/s (TCH/F28.8) not allowed

1 29.0 kbit/s (TCH/F28.8) allowed

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

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

Bit 3: Spare

Bit 2: 0 12.0 kbit/s (TCH/F9.6) not allowed

1 12.0 kbit/s (TCH/F9.6) allowed

Bit 1: 0 6.0 kbit/s (TCH/F4.8) not allowed

1 6.0 kbit/s (TCH/F4.8) allowed

Octet 5b shall be coded as follows:

Bit 8 reserved for extension.

A coding of 0 indicates no extension

Bits 7 and 6 indicate the asymmerty preference:

Bit 76

00 Not applicable

10 Downlink biased asymmetry is preferred

01 Uplink biased asymmetry is preferred

11 Spare

Bits 5 to 1 are spare

NOTE: "Not applicable" means that a symmetric service is preferred

If octet 5b is not included, symmetry shall be presumed.

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

7

6

5

4

3

2

1

ext

T/NT

Rate

octet 5

ext

allowed r i/f rates

octet 5a

ext

asymmetry
indication

spare

octet 5b

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 Transparent service

1 Non-transparent service.

For non-transparent service bits 6-1 indicates wanted total radio interface data rate;

65 4321 meaning

01 0110 58 / 58 kbit/s (4×14.5 kbit/s or 2 x29.0 kbit/s)

01 0100 48.0 / 43.5 / 43.5 kbit/s (4×12 kbit/s or 3×14.5 kbit/s or 1×43.5 kbit/s)

01 0011 36.0 / 29.0 / 29.0 kbit/s (3×12 kbit/s or 2×14.5 kbit/s or 1 x 29.0 kbit/s)

01 0010 24.0 / 24.0 (4×6 kbit/s or 2×12 kbit/s)

01 0001 18.0 / 14.5 kbit/s (3×6 kbit/s or 1×14.5 kbit/s)

01 0000 12.0 / 12.0 kbit/s (2×6 kbit/s or 1×12 kbit/s)

All other values are reserved.

For transparent service bits 6-1 indicates requested air interface user rate;

65 4321 meaning

01 1111 64 kbit/s, bit transparent

01 1110 56 kbit/s, bit transparent

01 1101 56 kbit/s

01 1100 48 kbit/s

01 1011 38.4 kbit/s

01 0001 32 kbit/s

01 1010 28.8 kbit/s

01 1001 19.2 kbit/s

01 1000 14.4 kbit/s

01 0000 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 7 to 1 indicates allowed radio interface data rate, per channel;

Bit 7: 0 43.5 kbit/s (TCH/F43.2) not allowed

1 43.5 kbit/s (TCH/F43.2) allowed

Bit 6: 0 32.0 kbit/s (TCH/F32.0) not allowed

1 32.0 kbit/s (TCH/F32.0) allowed

Bit 5: 0 29.0 kbit/s (TCH/F28.8) not allowed

1 29.0 kbit/s (TCH/F28.8) allowed

Bit 4: 0 14.5/14.4 kbit/s (TCH/F14.4) not allowed

1 14.5/14.4 kbit/s (TCH/F14.4) allowed

Bit 3: Spare

Bit 2: 0 12.0/9.6 kbit/s (TCH F/9.6) not allowed

1 12.0/9.6 kbit/s (TCH F/9.6) allowed

Bit 1: 0 6.0/4.8 kbit/s (TCH F/4.8) not allowed

1 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 3GPP TS 04.21 and 08.20) and to select the correct channel coding.

NOTE: 43.5 kbit/s is used only for nontransparent services.

Octet 5b is coded as follows:

Bit 8 reserved for extension.

A coding of 0 indicates no extension

Bits 7 and 6 indicate the asymmerty preference:

Bit

76 meaning

00 Not applicable

10 Downlink biased asymmetry is preferred

01 Uplink biased asymmetry is preferred

11 Spare

Bits 5 to 1 are spare

NOTE: "Not applicable" means that a symmetric service is preferred

If octet 5b is not included, symmetry shall be presumed.

If octet 3 indicates signalling then octet 5 is spare.

3.2.2.12 Periodicity

This element defines the periodicity of a particular procedure. It is fixed length, 2 octets.

The coding is as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Periodicity

octet 2

When the Resource Indication Method IE is set to either "method i) of sub-clause 3.1.3.1" or "method iii) of sub-clause 3.1.3.1" and the periodicity parameter is not 0000 0000 then the coding of the periodicity parameter is:

0000 0001 Period

1111 1111 –

where the period is the binary value of octet 2 * 100 ms (ie 100 ms to 25,500 ms).

When the Resource Indication Method IE is set to "method i) of sub-clause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall ignore this IE.

When the Resource Indication Method IE is set to "method iii) of sub-clause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall treat the message according to sub-clause 3.1.19.4, case 2.

When the Resource Indication Method IE is set to either "method ii) of sub-clause 3.1.3.1" or "method iv) of sub-clause 3.1.3.1" then the Periodicity IE shall be ignored.

3.2.2.13 Extended Resource Indicator

This element defines which additional resource information related to a given cell the BSS shall transfer to the MSC. It may also indicate the subsequent reporting mode for that cell.

The coding is as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

spare

SM

TARR

octet 2

SM = Subsequent mode

TARR = Total Accessible Resource Requested

The coding of the Total Accessible Resource Requested field is as follows:

0 no extra Resource Information is requested

1 The total number of accessible channels is requested

If the Resource Indication Method is not set to "method ii of sub-clause 3.1.3.1" then the Subsequent Mode field is ignored.

If the Resource Indication Method is set to "method ii of sub-clause 3.1.3.1" then the Subsequent Mode field is decoded as follows:

0 method iv) of sub-clause 3.1.3.1.

1 if the reporting mode prior to receipt of this IE was i) or iii) of sub-clause 3.1.3.1 then the subsequent mode shall be respectively i) or iii); otherwise the subsequent mode shall be method iv) of sub-clause 3.1.3.1.

3.2.2.14 Total Resource Accessible

This element gives the total number of full and half rate channels accessible on any given cell at the time of construction of the message.

It defines these parameters in terms of the number of channels which are accessible or in use. No separation between the defined interference bands is made.

The element is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Total number of accessible full rate channels

octet 2
octet 3

Total number of accessible half rate channels

octet 4
octet 5

Octets 2 and 3 give a 16 bit binary representation of the total number of full rate channels accessible (i.e. available for service or currently assigned).

Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels accessible (i.e. available for service or currently assigned). This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels.

(eg. If there is an accessible half rate channel and an accessible full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3).

Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit.

3.2.2.15 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

Element identifier

octet 1

Length

octet 2

LSA ID

octet 3

LSA ID cont.

octet 4

LSA ID cont.

octet 5

The octets 3-5 are coded as specified in 3GPP TS 03.03, ‘Identification of Localised Service Area’. Bit 8 of octet 3 is the MSB.

3.2.2.16 LSA Identifier List

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

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Spare

EP

octet 3

LSA identification 1

octet 4-6

LSA identification n

.. to 3+3n

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 3GPP TS 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

LSA ID

octet x+1

LSA ID cont.

octet x+2

LSA ID cont.

octet x+3

Where x = 3 + 3(i-1)

The octets (x+1)-(x+3) are coded as shown in 3GPP TS 03.03, ‘Identification of Localised Service Area’. Bit 8 of octet (x+1) is the MSB.

3.2.2.17 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

Element identifier

octet 1

Length

octet 2

Spare

Cell identification

discriminator

octet 3

Cell identification

octet 4 – n

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 3GPP TS 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.

1000 Intersystem Handover to UTRAN or cdma2000.PLMN-ID, LAC and RNC-ID, is used to identify the target RNC.

1001 Intersystem Handover to UTRAN or cdma2000. The RNC-ID is coded to identify the target RNC.

1010 Intersystem Handover to UTRAN or cdma2000. LAC and RNC-ID are encoded to identify the target RNC.

1011 Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000.

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

For GSM 900 and DCS 1800:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet 4

1

1

1

1

MCC dig 3

octet 5

MNC dig 2

MNC dig 1

octet 6

LAC

octet 7

LAC cont.

octet 8

CI value

octet 9

CI value cont

octet 10

The octets 4-8 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’ .

The octets 9-10 are coded as shown in 3GPP TS 04.08, Table ‘Cell Identity information element’.

For PCS 1900 for NA:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet 4

MNC dig 3

MCC dig 3

octet 5

MNC dig 2

MNC dig 1

octet 6

LAC

octet 7

LAC cont.

octet 8

CI value

octet 9

CI value cont

octet 10

The octets 4-8 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets 9-10 are coded as shown in 3GPP TS 04.08, Table ‘Cell Identity information element’.

Coding of Cell Identification for Cell identification discriminator = 0001

8

7

6

5

4

3

2

1

LAC

octet 4

LAC cont.

octet 5

CI value

octet 6

CI value cont

octet 7

Coding of Cell Identification for Cell identification discriminator = 0010

8

7

6

5

4

3

2

1

CI value

octet 4

CI value cont

octet 5

The octets 4-5 are coded as shown in 3GPP TS 04.08, Table ‘Cell Identity information element’

Cell identification discriminator = 1000

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet 4

MNC dig 3

MCC dig 3

octet 5

MNC dig 2

MNC dig 1

octet 6

LAC

octet 7

LAC cont.

octet 8

RNC-ID

octet 9

RNC-ID cont.

octet 10

The octets 4 – 8 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octet 5 bits 5-8 are filled by ‘1111’ if 2 digit MNC is used.

The octets 9 – 10 are coded as the RNC-ID specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are filled by ‘0000’.

Cell identification discriminator = 1001

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

RNC-ID

octet 4

RNC-ID cont.

octet 5

The octets 4 – 5 are coded as the RNC-ID, specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 4.In the octet 4 bits 5-8 are filled by ‘0000’.

Cell identification discriminator = 1010

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

LAC

octet 4

LAC cont.

octet 5

RNC-ID

octet 6

RNC-ID cont.

octet 7

The octets 4 – 5 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets 6-7 are coded as the RNC-ID, specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 4. In the octet 6 bits 5-8 are filled by ‘0000’.

Coding of the SAI for
Cell identification discriminator = 1011

The coding of SAI is defined in 3GPP TS 25.413 " UTRAN Iu Interface RANAP Signalling ", without the protocol extension container.

3.2.2.18 Priority

This element indicates the priority of the request. It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Priority

octet 3

Octet 2 is a binary indication of the length of the rest of the element.

Octet 3 is coded as follows:

8

7

6

5

4

3

2

1

spare

pci

priority level

qa

pvi

octet 3

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:

6 5 4 3

0 0 0 0 spare

0 0 0 1 priority level 1 = highest priority

0 0 1 0 priority level 2 = second highest priority

: : : :

1 1 1 0 priority level 14 = lowest priority

1 1 1 1 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.

3.2.2.19 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

Element identifier

octet 1

Length

octet 2

Classmark

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 3GPP TS 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 3GPP TS 04.08.

3.2.2.20 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

Element identifier

octet 1

Length

octet 2

Classmark

octet 3 – 14

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 3GPP TS 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 3GPP TS 04.08.

3.2.2.21 Interference Band To Be Used

This fixed length element is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Band to be used

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.

3.2.2.22 RR Cause

This fixed length element is passed from the radio interface to the MSC transparently, when received in a 3GPP TS 04.08 message.

8

7

6

5

4

3

2

1

Element identifier

octet 1

RR cause

octet 2

Octet 2 is coded as the equivalent field from 3GPP TS 04.08.

3.2.2.23 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:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Spare

LSA only

octet 3

LSA identification and attributes 1

octet 4-7

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

7

6

5

4

3

2

1

spare

act

pref

priority

octet x+1

LSA ID

octet x+2

LSA ID cont.

octet x+3

LSA ID cont.

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

: : : :

1111 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 3GPP TS 03.03, ‘Identification of Localised Service Area’. Bit 8 of octet (x+2) is the MSB.

3.2.2.24 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

Element identifier

octet 1

Length

octet 2

Layer 3 information

octet 3 – n

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 either:

– a radio interface layer 3 message as defined in 3GPP TS 04.18, or

– Handover To UTRAN Command as defined in UMTS 25.331, where n-2 is equal to the length of that radio interface layer 3 message.

3.2.2.25 DLCI

This is a fixed length element indicating the radio interface SAPI.

8

7

6

5

4

3

2

1

Element identifier

octet 1

DLCI

octet 2

Octet 2 is coded as the DLCI octet described in 08.06.

3.2.2.26 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

Element identifier

octet 1

Downlink DTX flag

octet 2

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.

3.2.2.27 Cell Identifier List

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

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Spare

Cell identification

discriminator

octet 3

Cell identification 1

octet 4-4+m

Cell identification n

.. to 4+nm

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 3GPP TS 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.

1000 Intersystem Handover to UTRAN or cdma2000. PLMN-ID, LAC, and RNC-ID, are encoded to identify the target RNC.

1001 Intersystem Handover to UTRAN or cdma2000. The RNC-ID is coded to identify the target RNC.

1010 Intersystem Handover to UTRAN or cdma2000. LAC and RNC-ID are encoded to identify the target RNC.

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

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet x+1

1

1

1

1

MCC dig 3

octet x+2

MNC dig 2

MNC dig 1

octet x+3

LAC

octet x+4

LAC cont.

octet x+5

CI value

octet x+6

CI value cont

octet x+7

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

The octets (x+1)-(x+5) are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets (x+6)-(x+7) are coded as shown in 3GPP TS 04.08, Table ‘Cell Identity information element’.

For PCS 1900 for NA:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet x+1

MCC dig 3

MCC dig 3

octet x+2

MNC dig 2

MNC dig 1

octet x+3

LAC

octet x+4

LAC cont.

octet x+5

CI value

octet x+6

CI value cont

octet x+7

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

The octets (x+1)-(x+5) are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets (x+6)-(x+7) are coded as shown in 3GPP TS 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

LAC

octet x+1

LAC cont.

octet x+2

CI value

octet x+3

CI value cont

octet x+4

Where x = 3 + 4(i-1)

The octets (x+1)-(x+2) are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets (x+3)-(x+4) are coded as shown in 3GPP TS 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

CI value

octet x+1

CI value cont

octet x+2

Where x = 3 + 2(i-1)

The octets (x+1)-(x+2) are coded as shown in 3GPP TS 04.08, Table ‘Cell Identity information element’ .

Coding of i-th Cell Identification for Cell identification discriminator = 0100

For GSM 900 and DCS 1800:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet x+1

1

1

1

1

MCC dig 3

octet x+2

MNC dig 2

MNC dig 1

octet x+3

LAC

octet x+4

LAC cont.

octet x+5

Where x = 3 + 5(i-1)

The octets (x+1)-(x+5) are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

For PCS 1900 for NA:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet x+1

MCC dig 3

MCC dig 3

octet x+2

MNC dig 2

MNC dig 1

octet x+3

LAC

octet x+4

LAC cont.

octet x+5

Where x = 3 + 5(i-1)

The octets (x+1)-(x+5) are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

Coding of i-th Cell Identification for Cell identification discriminator = 0101

8

7

6

5

4

3

2

1

LAC

octet x+1

LAC cont.

octet x+2

Where x = 3 + 2(i-1)

The octets (x+1)-(x+2) are coded as shown in 3GPP TS 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.

Coding of the Target ID for Cell identification discriminator = 1000

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

MCC dig 2

MCC dig 1

octet 4

MNC dig 3

MCC dig 3

octet 5

MNC dig 2

MNC dig 1

octet 6

LAC

octet 7

LAC cont.

octet 8

RNC-ID

octet 9

RNC-ID cont.

octet 10

The octets 4 – 8 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octet 5 bits 5-8 are filled by ‘1111’ if 2 digit MNC is used.

The octets 9-10 are coded as the RNC-ID, specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are filled by ‘0000’.

Coding of the Target ID for Cell identification discriminator = 1001

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

RNC-ID

octet 4

RNC-ID cont.

octet 5

The octets 4 – 5 are coded as the RNC-ID, specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 4. In the octet 4 bits 5-8 are filled by ‘0000’.

Coding of the Target ID for Cell identification discriminator = 1010

For intersystem handover from GSM to UMTS or cdma2000:

8

7

6

5

4

3

2

1

LAC

octet 4

LAC cont.

octet 5

RNC-ID

octet 6

RNC-ID cont.

octet 7

The octets 4 – 5 are coded as shown in 3GPP TS 04.08, Table ‘Location Area Identification information element’.

The octets 6-7 are coded as the RNC-ID, specified in UMTS 25.413 in sub-clause 9.2.1.25 in the Table "Target ID". The least significant bit of RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 4. In the octet 6 bits 5-8 are filled by ‘0000’.

3.2.2.28 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

Element identifier

octet 1

3.2.2.29 Resource Indication Method

This element defines the way the BSS shall transfer the resource information related to a cell to the MSC. The coding is as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Spare

Resource indication

method

octet 2

The coding of the Resource Indication parameter is:

0000 the method i) of sub-clause 3.1.3.1 is selected,

0001 the method ii) of sub-clause 3.1.3.1 is selected,

0010 the method iii) of sub-clause 3.1.3.1 is selected,

0011 the method iv) of sub-clause 3.1.3.1 is selected.

All other values are reserved.

3.2.2.30 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

Element identifier

octet 1

Classmark

octet 2

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

3.2.2.31 Circuit Identity Code List

This element defines in conjunction with a Circuit Identity Code (3.2.2.2.) a list of terrestrial channels.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Range

octet 3

Status

octet 4-35

The following codes are used in the range and status fields:

Range:

A number in pure binary representation ranging from 0 to 255. The number represented by the range code +1 indicates the range of circuits affected by the message.

Status:

The Status subfield contains up to 256 Status bits numbered from 0 up to 255. Status bit 0 is located in bit position 1 of the first Status subfield octet and refers to the circuit indicated in the CIC subfield{should be "associated Circuit Identity Code Information Element" not "CIC subfield"} itself. Other Status bits follow in numerical order.

Each Status bit is associated with a circuit identification code such that Status bit n is associated with CIC m+n, where m is the CIC contained in the message.{"where m is the CIC identified in the asociated Circuit Identity Code Information Element in the message"}

Status bit n is located in bit position nb of the no-th octet of the Status subfield with:

nb = (n mod 8) + 1
and
no = (n div 8) + 1.

The number of relevant Status bits in a given Status subfield is equal to the range value +1.

The Status bits are coded as follows:

– in the CIRCUIT GROUP BLOCK message

0 no indication

1 block

– in the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message

0 no indication

1 blocking acknowledgement

– in the CIRCUIT GROUP UNBLOCK message

0 no indication

1 unblock

– in the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message

0 no indication

1 unblocking acknowledgement

– in the UNEQUIPPED CIRCUIT message

0 no indication

1 unequipped

3.2.2.32 Diagnostics

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Error pointer

octet 3-4

Message received

octet 5-n

The coding of the error pointer field is as follows:

Octet 3 gives the number of octets between octet 4 (not included) and the first octet (included) of the part of the message received which provoked the error. Thus:

0000 0000 Error location not determined

0000 0001 The first octet of the message received (i.e. the message type) was found erroneous (unknown)

0000 0010 The second octet of the message received was found erroneous

0000 0011 The third octet of the message received was found erroneous

etc.

The last three values are reserved for the BSSAP header:

1111 1101 The first octet of the BSSAP header (Discrimination) was found erroneous

1111 1110 (DTAP only) The DLCI (second) octet of the BSSAP header was found erroneous

1111 1111 The last octet of the BSSAP header (length indicator) was found erroneous

Octet 4 is coded as follows:

bit

8

7

6

5

4

3

2

1

0

0

0

0

spare

bit pointer

The bit pointer field is coded as follows:

bits 4321
0000 No particular part of the octet is indicated
0001 An error was provoked by the field whose most significant bit is in bit position 1
0010 An error was provided by the field whose most significant bit is in bit position 2
0011 An error was provided by the field whose most significant bit is in bit position 3
0100 An error was provided by the field whose most significant bit is in bit position 4
0101 An error was provided by the field whose most significant bit is in bit position 5
0110 An error was provided by the field whose most significant bit is in bit position 6
0111 An error was provided by the field whose most significant bit is in bit position 7
1000 An error was provided by the field whose most significant bit is in bit position 8

All other values are reserved.

The "message received" field should be the contents, as far as can be determined, of the received message which provoked the error.

3.2.2.33 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

3

2

1

Element identifier

octet 1

Channel mode

Channel

octet 2

The channel mode field is coded as follows:

Bit

8765 meaning

0000 no channel mode indication

1001 speech (full rate or half rate)

1110 data, 14.5 kbit/s radio interface rate

1011 data, 12.0 kbit/s radio interface rate

1100 data, 6.0 kbit/s radio interface rate

1101 data, 3.6 kbit/s radio interface rate

1000 signalling only

0001 data, 29.0 kbit/s radio interface rate

0010 data, 32.0 kbit/s radio interface rate

0011 data, 43.5 kbit/s radio interface rate

0100 data, 43.5 kbit/s downlink and 14.5 kbit/s uplink

0101 data, 29.0 kbit/s downlink and 14.5 kbit/s uplink

0110 data, 43.5 kbit/s downlink and 29.0 kbit/s uplink

0111 data, 14.5 kbit/s downlink and 43.5 kbit/s uplink

1010 data, 14.5 kbit/s downlink and 29.0 kbit/s uplink

1111 data, 29.0 kbit/s downlink and 43.5 kbit/s uplink

All other values are reserved.

The channel field is coded as follows:

Bit

4321 meaning

0000 None (Note *)

0001 SDCCH

1000 1 Full rate TCH

1001 1 Half rate TCH

1010 2 Full Rate TCHs

1011 3 Full Rate TCHs

1100 4 Full Rate TCHs

1101 5 Full Rate TCHs

1110 6 Full Rate TCHs

1111 7 Full Rate TCHs

0100 8 Full Rate TCHs

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.

All other values are reserved.

3.2.2.34 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

Element identifier

octet 1

Cipher response mode

octet 2

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

3.2.2.35 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

Element identifier

octet 1

Length

octet 2

Layer 3 message contents

octet 3 – n

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 3GPP TS 04.08, n is equal to the length of that radio interface layer 3 message.

3.2.2.36 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

1

Element identifier

octet 1

Spare

Channel

octet 2

The Channel field is coded as follows:

Bit 2 1

0 0 Any channel

0 1 SDCCH

1 0 TCH/F (Full rate)

1 1 TCH/H or TCH/F (Dual rate)

3.2.2.37 Trace Type

A fixed length element indicating the type of trace information to be recorded.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Trace type

octet 2

Octet 2 contains the trace type.

Octet 2 is coded as the MSC/BSS Trace Type specified in 3GPP TS 12.08.

3.2.2.38 TriggerID

A variable length element indicating the identity of the entity which initiated the trace.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Entity identity

octets 3-22

Octets 3-22 may be typically an OMC identity.

3.2.2.39 Trace Reference

A fixed length element providing a trace reference number allocated by the triggering entity

8

7

6

5

4

3

2

1

Element identifier

octet 1

TraceReference

octet 2-3

3.2.2.40 TransactionID

A potentially variable length element indicating a particular transaction within a trace.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Transaction number

octet 3-4

3.2.2.41 Mobile Identity

A variable length element.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Mobile identity

octet 3-n

Octet 3-n contain either the IMSI, IMEISV or IMEI as coded in 3GPP TS 04.08, not including 3GPP TS 04.08 element identifier or 3GPP TS 04.08 octet length value.

3.2.2.42 OMCID

A variable length element indicating the destination OMC to which trace information is to be sent.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

OMC identity

octets 3-22

For the OMC identity, see TS 12.20

3.2.2.43 Forward Indicator

A fixed length element indicating whether the trace is to be continued in a BSS to which the call has been handed over.

8

7

6

5

4

3

2

1

Element identifier

octet 1

spare

Forward indicator

octet 2

Octet 2 is coded as follows:

bit 4 3 2 1

0 0 0 1 forward to subsequent BSS, no trace at MSC

0 0 1 0 forward to subsequent BSS, and trace at MSC

All other values are reserved.

Bits 5-8 are spare.

3.2.2.44 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

Element identifier

octet 1

Algorithm identifier

octet 2

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.

3.2.2.45 Circuit Pool

This element indicates the circuit pool of a circuit or group of circuits.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Circuit pool number

octet 2

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

Pool

Supported channels and speech coding algorithms

0000 0001

Circuit pool number 1

FR speech version 1
FR data (12, 6, 3.6 kbit/s)

0000 0010

Circuit pool number 2

HR speech version 1
HR data (6, 3.6 kbit/s)

0000 0011

Circuit pool number 3

FR speech version 1
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)

0000 0100

Circuit pool number 4

FR speech version 2
FR data (12, 6, 3.6 kbit/s)

0000 0101

Circuit pool number 5

FR speech version 1
FR speech version 2
FR data (12, 6, 3.6 kbit/s)

0000 0110

Circuit pool number 6

FR speech version 2
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)

0000 0111

Circuit pool number 7

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 1000

Circuit pool number 8

HSCSD max 2 x FR data (12, 6 kbit/s)

0000 1001

Circuit pool number 9

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)

0000 1010

Circuit pool number 10

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 2 x FR data (12, 6 kbit/s)

0000 1011

Circuit pool number 11

HSCSD max 4 x FR data (12, 6 kbit/s)

0000 1100

Circuit pool number 12

FR data (12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (12, 6 kbit/s)

0000 1101

Circuit pool number 13

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)

0000 1110

Circuit pool number 14

HSCSD max 6 x FR data (12, 6 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s)

0000 1111

Circuit pool number 15

FR data (14.5 kbit/s)

0001 0000

Circuit pool number 16

HSCSD max 2 x FR data (14.5 kbit/s)
EDGE FR data (29.0 kbit/s)

0001 0001

Circuit pool number 17

HSCSD max 4 x FR data (14.5 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)

0001 0010

Circuit pool number 18

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)
EDGE FR data (29.0 kbit/s)

0001 0011

Circuit pool number 19

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)

0001 0100

Circuit pool number 20

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)

0001 0101

Circuit pool number 21

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)
EDGE FR data (29.0 kbit/s)

0001 0110

Circuit pool number 22

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)

0001 0111

Circuit pool number 23

FR speech version 3
HR speech version 3

0001 1000

Circuit pool number 24

FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 3

0001 1001

Circuit pool number 25

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

0001 1010

Circuit pool number 26

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

0001 1011

Circuit pool number 27

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)

0001 1100

Circuit pool number 28

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)

0001 1101

Circuit pool number 29

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)

0001 1110

Circuit pool number 30

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)
EDGE FR data (29.0 kbit/s)

0001 1111

Circuit pool number 31

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 4 x FR data (12, 6 kbit/s)

0010 0000

Circuit pool number 32

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)

0010 0001

Circuit pool number 33

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s)

0010 0010

Circuit pool number 34

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s)

0010 0011

Circuit pool number 35

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)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s)

1000 xxxx

For national/local use

All other values are Reserved for future international use

3.2.2.46 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

Element identifier

octet 1

Length

octet 2

Circuit pool number (1st preferred)

octet 3

Circuit pool number (nth preferred)

octet n+2

The Circuit pool number is coded as specified in 3.2.2.45.

3.2.2.47 Time Indication

This element defines the period where the information shall be valid. It is fixed length, 2 octets.

The coding is as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Time

octet 2

The Time field of this Information Element message in octet 2 is coded as follows:

0000 0000 (note)

0000 0001

: :

1111 1110 Time,

where the time is the binary value of octet 2 * 10s (ie 10s to 2540s).

If the Time field contains the value 255 (1111 1111), the receiving entity shall consider the time as infinite.

NOTE: The value 0 has a special meaning in the Load indication procedure (refer to sub-clause 3.1.20).

3.2.2.48 Resource Situation

This element gives, for respective indicated channel type, the total number of channels accessible and the number of channels available on any given cell at the time of construction of the message.

The number of channels available may be defined in up to five interference bands, the boundaries of these bands being set by O and M as follows:

Interference level:

0 —————————
Band 1
X1 —————————
Band 2
X2 —————————
Band 3
X3 —————————
Band 4
X4 —————————
Band 5
X5 —————————

The element is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Resource and interference band indicator

Channel type

octet 3

7/15 ind.

Number of channels

octet 4

octet 4a

Resource and interference band indicator

Channel type

octet 5

7/15 ind.

Number of channels

octet 6

octet 6a

Resource and interference band indicator

Channel type

octet N-1

7/15 ind.

Number of channels

octet N

octet Na

The length indicator is a binary representation of the length of the following element.

The Resource type octet (octets 3, 5, etc.) is coded as follows:

The Channel type field (bits 1-4 of octets 3, 5, etc.) is coded as follows:

Bit

4 3 2 1 meaning

0 0 0 1 SDCCH

1 0 0 0 Full Rate TCH

1 0 0 1 Half Rate TCH

All other values are reserved.

The Resource and interference band indicator field (bits 5-8 of octets 3, 5, etc.) is coded as follows:

Bit

8 7 6 5 meaning

0 0 0 0 Total number of channels accessible (i.e. available for service or currently assigned)

0 0 0 1 Number of channels available in interference band 1

0 0 1 0 Number of channels available in interference band 2

0 0 1 1 Number of channels available in interference band 3

0 1 0 0 Number of channels available in interference band 4

0 1 0 1 Number of channels available in interference band 5

1 1 1 0 Number of channels available without supplied interference band classification

All other values are reserved.

The Number of channels octets (octets 4, 6, etc.) is coded as follows:

The Number of channels is a single octet element if the 7/15 indication bit (bit 8 of octets 4, 6, etc.) is set to 0. If the 7/15 indication bit is set to 1 then it is a 2 octet field. It give a 7 (or 15) bit binary representation of the number of channels with resource type as indicated in the nearest preceding resource type octet. The coding convention used when a field extends over more than one octet is defined in sub-clause 3.2.2.

The number of half rate channels will include half rate channels counted as full rate channels, if these correspond to full rate channels that can be used as half rate channels.

(e.g. If there is one idle half rate channel and one idle full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3).

The Resource type octet and the Number of channels octet(s) are repeated for each of the resource type reported.

For each of the channel type reported, the total number of channels accessible and at least one indication of available channels shall be included.

The number of channels available without supplied interference band classification is included only in case the interference band definition is not available for the reported channel type.

3.2.2.49 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

3

2

1

Element identifier

octet 1

Channel mode

Channel

octet 2

The channel mode field is coded as follows:

Bit

8765 meaning

0000 signalling 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

0111 data, 29 kbit/s radio interface rate

1000 data, 32 kbit/s radio interface rate

1001 data, 43.5 kbit/s radio interface rate

0010 data, 43.5 kbit/s downlink and 14.5 kbit/s uplink

1010 data, 29.0 kbit/s downlink and 14.5 kbit/s uplink

1011 data, 43.5 kbit/s downlink and 29.0 kbit/s uplink

1100 data, 14.5 kbit/s downlink and 43.5 kbit/s uplink

1101 data, 14.5 kbit/s downlink and 29.0 kbit/s uplink

1110 data, 29.0 kbit/s downlink and 43.5 kbit/s uplink

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 meaning

0001 SDCCH

1000 1 Full rate TCH

1001 1 Half rate TCH

1010 2 Full Rate TCHs

1011 3 Full Rate TCHs

1100 4 Full Rate TCHs

1101 5 Full Rate TCHs

1110 6 Full Rate TCHs

1111 7 Full Rate TCHs

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.

3.2.2.50 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

2

1

Element identifier

octet 1

spare

qri

spare

octet 2

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

3.2.2.51 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

Element identifier

octet 1

spare

Speech version identifier

octet 2

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.

3.2.2.52 Assignment Requirement

8

7

6

5

4

3

2

1

Element identifier

octet 1

Assignment requirement

octet 2

Octet 2

00000000 Delay allowed

00000001 Immediate and the resources shall not be de-allocated until the end of the call

00000010 Immediate and the resources may further be de-allocated by the BSS

all other values are reserved

3.2.2.53 (void)

3.2.2.54 Talker Flag

8

7

6

5

4

3

2

1

Element identifier

octet 1

3.2.2.55 Group Call Reference

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Descriptive group or broadcast call reference

octets 3-7

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 3GPP TS 04.08.

3.2.2.56 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

Element identifier

octet 1

spare

call priority

octet 2

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 3GPP TS 04.08.

3.2.2.57 Configuration Evolution Indication

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

8

7

6

5

4

3

2

1

Element identifier

octet 1

spare

SMI

octet 2

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.

3.2.2.58 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. The error handling performed by the receiving entity for the "Old BSS to New BSS information elements" field is that specified in sub-clause 3.1.19.7.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Old BSS to New BSS information elements

octet 3-n

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

REFERENCE

LEN

Extra information

3.2.3.1

3

Current Channel Type 2

3.2.3.2

4

Target cell radio information

3.2.3.3

3

GPRS Suspend information

3.2.3.4

19

MultiRate configuration information

3.2.3.5

3-8

Dual Transfer Mode information

3.2.3.6

3

Inter RAT Handover Info

3.2.3.7

3-n

cdma2000 Capability Information

3.2.3.8

n

3.2.2.59 (void)

3.2.2.60 LCS QoS

This element indicates the Quality of Service requirements for the location request.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

QoS

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The QoS octets 3 to n are coded in the same way as the equivalent octets in the LCS QoS element of 3GPP TS 09.31.

3.2.2.61 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

Element identifier

octet 1

spare

EM

octet 2

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.

3.2.2.62 LCS Priority

The LCS Priority defines the priority of the location request.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Priority

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Priority octets 3 to n are coded in the same way as the equivalent octets in the LCS Priority element of 3GPP TS 09.31.

3.2.2.63 Location Type

The Location Type information element indicates the type of location request.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Location Type

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Location Type octets 3 to n are coded in the same way as the equivalent octets in the Location Type element of 3GPP TS 09.31.

3.2.2.64 Location Estimate

This is a variable length information element providing an estimate of a geographic location of a target MS.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Location estimate

octet 3-n

The length indicator is a binary indication of the number of octets following in the element.

The Location Estimate field is composed of 1 or more octets with an internal structure according to 3GPP TS 03.32.

3.2.2.65 Positioning Data

This element indicates the data on the positioning process for possible use in billing in location method evaluation.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Positioning data

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Positioning Data octets 3 to n are coded in the same way as the equivalent octets in the Positioning Data element of 3GPP TS 09.31.

3.2.2.66 LCS Cause

This element indicates the data on the positioning process for possible use in billing in location method evaluation.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

LCS Cause

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The LCS Cause octets 3 to n are coded in the same way as the equivalent octets in the LCS Cause element of 3GPP TS 09.31.

3.2.2.67 LCS Client Type

This element identifies the type of LCS Client.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

LCS Client Type

octet 3-n

The LCS Client Type octets 3 to n are coded in the same way as the equivalent octet in the LCS Client Type element of 3GPP TS 09.31.

3.2.2.68 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

Element identifier

octet 1

Length

octet 2-3

APDU

octet 4-n

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 3GPP TS 09.31.

3.2.2.69 Network Element Identity

This is a variable length information element identifying a network element. by association with either a designated cell site or a designated location area.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Network Element Identity

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Network Element Identity octets 3 to n are coded in the same way as the equivalent octets in the Network Element Identity element of 3GPP TS 09.31.

3.2.2.70 GPS Assistance Data

This is a variable length information element indicating the requested GPS assistance data.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

GPS Assistance Data

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The GPS Assistance Data octets 3 to n are coded in the same way as the equivalent octets in the Requested GPS Data element of 3GPP TS 09.31.

3.2.2.71 Deciphering Keys

This is a variable length information element indicating the requested GPS assistance data.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Deciphering Keys

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Deciphering Key octets 3 to n are coded in the same way as the equivalent octets in the Deciphering Key element of 3GPP TS 09.31.

3.2.2.72 Return Error Request

This is a variable length information element indicating a request from the source for an error response if the message cannot be delivered to its final destination.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Return Error Type

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Return Error Type octets from 3 to n are coded in the same way as the equivalent octets in the Return Error Request element of 3GPP TS 09.31.

3.2.2.73 Return Error Cause

This is a variable length information element indicating the reason for unsuccessful delivery of a message to its final destination.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Cause Value

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Cause Value octets from 3 to n are coded in the same way as the equivalent octets in the Return Error Cause element of 3GPP TS 09.31.

3.2.2.74 Segmentation

This is a variable length information element containing segmentation and message information for a segmented APDU.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Segmentation and Message Information

octet 3-n

The coding of octet 2 is a binary number indicating the length of the remaining element.

The Segmentation and Message information octets from 3 to n are coded in the same way as the equivalent octets in the Segmentation element of 3GPP TS 09.31.

3.2.2.75 Service Handover

The Service Handover defines information to use for handover to UTRAN or cdma2000.

It is coded as follows:

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Service Handover information

octet 3

Octet 2 is a binary indication of the length of the remainder of the element in octets.

Service Handover information is coded as follows:

Bits 4-8: Spare.

Bits 1-3:

3 2 1

0 0 0 Handover to UTRAN or cdma2000 should be performed
Handover to UTRAN or cdma2000 is preferred. The handover evaluation of the target cell for handovers
shall take into account the preference for UTRAN or cdma2000.

0 0 1 Handover to UTRAN or cdma2000 should not be performed
Handover to GSM is preferred. The handover evaluation of the target cell for handovers
shall take into account the preference for GSM.

0 1 0 Handover to UTRAN or cdma2000 shall not be performed
Handover to UTRAN or cdma2000 is not allowed.

All other values are interpreted as no information available for service based handover.

3.2.2.76 Source RNC to target RNC transparent information (UMTS)

This information element is defined as a general container for passing (e.g. UE Capability Information, Target Cell ID) RNC specific information transparently through the core network from BSS to RNC.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Source RNC to target RNC information container

octet 3-n

The Source RNC to Target RNC Information container structure and encoding is defined in relevant RANAP specification TS 25.413, excluding RANAP tag.

3.2.2.77 Source RNC to target RNC transparent information (cdma2000)

This information element is defined as a general container for passing (e.g. cdma2000 Capability Information, Target Cell ID) RNC specific information transparently through the core network from BSS to RNC.

8

7

6

5

4

3

2

1

Element identifier

octet 1

Length

octet 2

Source RNC to target RNC information container

octet 3-n

The Source RNC to Target RNC Information container structure and encoding is defined in relevant RANAP specification TS 25.413, excluding RANAP tag.