11 List of system parameters

04.183GPPMobile radio interface Layer 3 specificationRadio Resource Control (RRC) protocolRelease 1999TS

The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions.

11.1 Timers and counters for radio resource management

11.1.1 Timers on the mobile station side

T3122: This timer is used during random access, after the receipt of an IMMEDIATE ASSIGN REJECT message.

Its value is given by the network in the IMMEDIATE ASSIGN REJECT message.

T3124: This timer is used in the seizure procedure during a hand-over, when the two cells are not synchronized.

Its purpose is to detect the lack of answer from the network to the special signal.

Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms.

T3126: This timer is started either:

after sending the maximum allowed number of CHANNEL REQUEST messages during an immediate assignment procedure; or

on receipt of an IMMEDIATE ASSIGNMENT REJECT message;

whichever occurs first.

It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message.

At its expiry, the immediate assignment procedure is aborted.

The minimum value of this timer is equal to the time taken by T+2S slots of the mobile station’s RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds.

T3128: This timer is started when the mobile station starts the uplink investigation procedure and the uplink is busy.

It is stopped at receipt of the first UPLINK FREE message.

At its expiry, the uplink investigation procedure is aborted.

The value of this timer is set to 1 second.

T3130: This timer is started after sending the first UPLINK ACCESS message during a VGCS uplink access procedure.

It is stopped at receipt of a VGCS ACCESS GRANT message.

At its expiry, the uplink access procedure is aborted.

The value of this timer is set to 5 seconds.

T3110: This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL RELEASE. Its purpose is to let some time for disconnection of the main signalling link.

Its value is set to such that the DISC frame is sent twice in case of no answer from the network. (It should be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of the channel release procedure.)

T3134 This timer is used in the seizure procedure during an RR network controlled cell change order procedure. Its purpose is to detect the lack of answer from the network or the lack of availability of the target cell.

Its value is set to 5 s.

T3142: The timer is used during packet access on CCCH and during packet access while in dedicated mode. It is started after the receipt of an IMMEDIATE ASSIGNMENT REJECT or a DTM REJECT message.

Its value is given by the network in the IMMEDIATE ASSIGNMENT REJECT or DTM REJECT message.

T3148: This timer is used during DTM establishment in dedicated mode.

It is started after sending a DTM REQUEST message during a packet access procedure while in dedicated mode.

It is stopped at the receipt of one of the following messages:

– DTM ASSIGNMENT COMMAND.

– PACKET ASSIGNMENT.

– DTM REJECT.

– ASSIGNMENT COMMAND.

– HANDOVER COMMAND.

At its expiry, the packet access procedure is aborted.

Its value is 4 seconds.

T3146: This timer is started either

after sending the maximum allowed number of CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages during a packet access procedure; or

on receipt of an IMMEDIATE ASSIGNMENT REJECT message during a packet access procedure;

whichever occurs first.

It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message.

At its expiry, the packet access procedure is aborted.

The minimum value of this timer is equal to the time taken by T+2S slots of the mobile station’s RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds.

T3164: This timer is used during packet access using CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message.

It is stopped at the transmission of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 04.60.

At expire, the mobile station returns to the packet idle mode.

The value of the timer is 5 s.

T3190: The timer is used during packet downlink assignment on CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message or of an PDCH ASSIGNMENT COMMAND message when in dedicated mode.

It is stopped at the receipt of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 04.60.

At expiry, the mobile station returns to the packet idle mode.

The value of the timer is 5 s.

T3204: This timer is used by a mobile station with non-GSM capabilities. The timer is started after sending the first CHANNEL REQUEST during a packet access procedure. The CHANNEL REQUEST was sent requesting a single block packet access and the purpose of the packet access procedure is to send a PACKET PAUSE message.

It is stopped at the receipt of an IMMEDIATE ASSIGNMENT message granting a single block period on an assigned packet uplink resource.

At expiry, the packet access procedure is aborted.

The value of the timer is 1 second.

11.1.2 Timers on the network side

T3101: This timer is started when a channel is allocated with an IMMEDIATE ASSIGNMENT message. It is stopped when the MS has correctly seized the channels.

Its value is network dependent.

NOTE 1: It could be higher than the maximum time for a L2 establishment attempt.

T3103: This timer is started by the sending of a HANDOVER message and is normally stopped when the MS has correctly seized the new channel. Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 2: It could be higher than the maximum transmission time of the HANDOVER COMMAND, plus the value of T3124, plus the maximum duration of an attempt to establish a data link in multiframe mode.)

T3105: This timer is used for the repetition of the PHYSICAL INFORMATION message during the hand-over procedure.

Its value is network dependent.

NOTE 3: This timer may be set to such a low value that the message is in fact continuously transmitted.

T3107: This timer is started by the sending of an ASSIGNMENT COMMAND or a DTM ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly seized the new RR channels.

Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 4: It could be higher than the maximum transmission time of the ASSIGNMENT COMMAND message plus twice the maximum duration of an attempt to establish a data link multiframe mode.

T3109: This timer is started when a lower layer failure is detected by the network, when it is not engaged in a RF procedure. It is also used in the channel release procedure.

Its purpose is to release the channels in case of loss of communication.

Its value is network dependent.

NOTE 5: Its value should be large enough to ensure that the MS detects a radio link failure.

T3111: This timer is used to delay the channel deactivation after disconnection of the main signalling link. Its purpose is to let some time for possible repetition of the disconnection.

Its value is equal to the value of T3110.

T3113: This timer is started when the network has sent a PAGING REQUEST message and is stopped when the network has received the PAGING RESPONSE message.

Its value is network dependent.

NOTE 6: The value could allow for repetitions of the Channel Request message and the requirements associated with T3101.

T3115: This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink access procedure.

Its value is network dependent.

NOTE 7: This timer may be set to such a low value that the message is in fact continuously transmitted.

T3117: This timer is started by the sending of a PDCH ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly accessed the target TBF.

Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 8: It could be higher than the maximum transmission time of the PDCH ASSIGNMENT COMMAND message plus T3132 plus the maximum duration of an attempt to establish a data link in multiframe mode.

T3119: This timer is started by the sending of a RR-CELL CHANGE ORDER message and is normally stopped when the MS has correctly accessed the new cell. Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

NOTE 9: It could be higher than the maximum transmission time of the RR_CELL CHANGE ORDER, plus T3134, plus the maximum duration of an attempt to establish a data link in multiframe mode.

T3121: This timer is started by the sending of an INTER SYSTEM TO UTRAN HANDOVER message and is normally stopped when the MS has correctly seized the UTRAN channel(s). Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

T3123: This timer is started by the sending of an INTER SYSTEM TO CDMA2000 HANDOVER message and is normally stopped when the MS has correctly seized the CDMA2000 channel(s). Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.

Its value is network dependent.

T3141: This timer is started when a temporary block flow is allocated with an IMMEDIATE ASSIGNMENT message during a packet access procedure. It is stopped when the mobile station has correctly seized the temporary block flow.

Its value is network dependent.

11.1.3 Other parameters

Ny1: The maximum number of repetitions for the PHYSICAL INFORMATION message during a handover (see sub-clause 3.4.4.2.2). The value is network dependent.

Ny2: The maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink access procedure (see sub-clause 3.3.1.2.2). The value is network dependent.

11.2 Timers of mobility management

See 3GPP TS 24.008.

11.3 Timers of circuit-switched call control

See 3GPP TS 24.008.

Annex A (informative):
Example of subaddress information element coding

See 3GPP TS 24.008.

Annex B (normative):
Compatibility checking

See 3GPP TS 24.008.

Annex C (normative):
Low layer information coding principles

See 3GPP TS 24.008.

Annex D (informative):
Examples of bearer capability information element coding

See 3GPP TS 24.008.

Annex E (informative):
Comparison between call control procedures specified in 3GPP TS 24.008 and CCITT Recommendation Q.931

See 3GPP TS 24.008.

Annex F (informative):
GSM specific cause values for radio resource management

This annex is informative.

Cause value = 0 Normal event;

indicates that the channel is released because of a normal event or that an assignment or handover is successfully, and normally, completed.

Cause value = 1 Abnormal release, unspecified;

indicates that the channel is released because of an abnormal event without specifying further reasons.

Cause value = 2 Abnormal release, channel unacceptable;

indicates that the channel type or channel characteristics are not acceptable.

Cause value = 3 Abnormal release, timer expired;

indicates that the release is caused by a timer expiry.

Cause value = 4 Abnormal release, no activity on the radio path;

indicates that some supervisory function has detected that the channel is not active.

Cause value = 5 Pre-emptive release;

indicates that the channel is released in order to be allocated to a call with priority (e.g. an emergency call).

Cause value = 6 UTRAN configuration unknown;

indicates that the MS does not know the UTRAN predefined configuration (i.e. was not read from UTRAN Channels) or that the MS does not have the capability to handle the requested default configuration.

Cause value = 8 Handover impossible, timing advance out of range;

indicates that a handover is unsuccessful because the target BTS is beyond the normal range and the target BTS would not accept an out of range timing advance.

Cause value = 9 Channel mode unacceptable

indicates that the MS does not have the capability to handle the requested mode or type of channel.

Cause value = 10 Frequency not implemented

indicates that the MS does not have the capability to operate on (at least one of) the requested frequency(ies).

Cause value = 12 Lower layer failure

indicates that a lower layer failed to establish a connection on the new channel.

Cause value = 65 Call already cleared;

indicates that a handover is unsuccessful because the connection has been released by the network or the remote user.

Cause value = 95 Semantically incorrect message;

See annex H, sub-clause H5.10.

Cause value = 96 Invalid mandatory information;

See annex H, sub-clause H6.1.

Cause value = 97 Message type non-existent or not implemented;

See annex H, sub-clause H6.2.

Cause value = 98 Message type not compatible with protocol state;

See annex H, sub-clause H6.3

Cause value = 100 Conditional IE error;

See annex H, sub-clause H6.5

Cause value = 101 No cell allocation available;

indicates that an assignment or handover is unsuccessful because the MS has no current CA.

Cause value = 111 Protocol error unspecified;

See annex H, sub-clause H6.8.

Annex G (informative):
GSM specific cause values for mobility management

See 3GPP TS 24.008.

Annex H (informative):
GSM specific cause values for call control

See 3GPP TS 24.008.

Annex I (informative):
GSM specific cause values for session management

See 3GPP TS 24.008.

Annex J (informative):
Algorithm to encode frequency list information elements

J.1 Introduction

Some information elements encode frequency lists with a special method. The main specification specifies the meaning of the fields and hence the way to decode them, but the corresponding encoding algorithm is difficult to infer from the decoding algorithm. This annex is intended as an aid for implementers of the encoding algorithm.

It could be shown that any set of frequency with less or the same number of frequencies as the number of words can be encoded with a careful choice of F1, F2, and so on, i.e. that a set of Wi can be found so that the decoding algorithm given in the main sub-clause will give back the frequency set. The right order is not the order of the frequency values.

J.2 General principle

The encoding algorithm is based on a recursive dichotomy of both the range (i.e. the set of values that are possible) and the subset (the values to encode).

The dichotomy is best understood if the range is seen as a circle. For instance, for the 1023 range:

Figure J.1: Circular arrangement of 0..1023

The dichotomy consists in finding a value in the subset such that the diameter determined by this value splits the subset in two equal or nearly equal subsets. In the following case, we see that value 290 is acceptable (the two subsets have 3 elements), when value 250 is not acceptable (the two subsets have 4 and 2 elements):

Figure J.2: Example of dichotomy

The pivot value is part of the information field, then the two subsets are renumbered and the same algorithm is applied again on each of them. Because the range is halved at each step, the number of bits needed to encode a pivot value is 1 bit less than the number of bits needed to encode the parent pivot value.

The convention is that if the number of values is even, the left subset (that is to say the values that can be expressed as the pivot value minus some integer between 1 and half the range) will have 1 element more than the right subset.

At each step the subset is numbered from 0 to the range minus 1. The coding in the information field of the pivot value is its value as renumbered, plus 1. Value 0 is reserved to indicate no element.

The order of appearance in the information field of the successive pivot values is particular. If we present the values as organized as a tree, with the left child being the pivot of the left subset and the right child the pivot of the right subset, the order of appearance is given by the following tree.

Figure J.3

This order has been chosen so that:

a) whatever the number N of elements in the set, the meaningful nodes are the first N and the value for all nodes from N+1 on are null (if sent);

b) the tree and all subtrees are balanced.

Important properties of these trees are used in the algorithms (with generation 1 corresponding to the root):

– Generation g contains 2g-1 nodes, and their indices are 2g-1 to 2g-1;

– For generation g, nodes 2g-1 to 2g-1+2g-2-1 are left children, the others are right children;

– If node k belongs to generation g, its left child is node k + 2g-1 , and its right child is k + 2g;

– Reciprocally, if k is a left child from generation g, its parent node is node k – 2g-2, and if k is a right child of generation g, its parent is node k – 2g-1.

J.3 Performances

The number of bits needed to encode a given set of values depends on the number of values and on the range they can span.

For the application on the BCCH and the SACCH (CA and BA information ) 16 octets are available, and the number of frequencies that can be encoded in one information element is the following:

Range

Number of frequencies

513 to 1 024

2 to 16 (17 if frequency 0 is in)

257 to 512

2 to 18

129 to 256

2 to 22

113 to 128

2 to 29

up to 112

any

With two messages (for the BA) the number of frequencies that can be encoded is the following:

Range

Number of frequencies

513 to 1 024

2 to 36 (note 1)

257 to 512

2 to 40 (note 2)

225 to 256

2 to 51 (note 3)

up to 224

any

NOTE 1: A 1024 range can be split cyclically in to two 512 ranges each with less than 18 frequencies; each subset is coded in one message with 512 range format.

NOTE 2: A 512 range can be split in to two consecutive 256 ranges. If both sub-ranges contain 22 frequencies or less, it is possible to code each of these in a messages using the 256 range format. Otherwise one of the two ranges contains 23 frequencies or more: 22 of them can be coded in one message using the 256 range format and the remaining frequencies (numbering less than or equal to 18) can be coded in the other message using the 512 range format.

NOTE 3: The principles described in notes 1 and 2, above apply in this case.

The frequency short list information element allows the following:

Range

Number of frequencies

513 to 1 024

2 to 7 (8 if frequency 0 is in)

257 to 512

2 to 8

129 to 256

2 to 9

57 to 128

2 to 12

up to 56

any

The number of frequencies as a function of the range and the length in octets of the variable length frequency list information element (including the message type and length fields) is given in table J.1.

Table J.1: Performance of the variable length frequency list information element

Range
(octets)

513 to 1 024

257 to 512

129 to 256

up to 128

variable bit map

5

1

1

1

1

8

6

2

2

3

3

16

7

3

3

4

4

24

8

4

4

5

6

32

9

5

6

6

8

40

10

6

7

8

10

48

11

7

8

9

12

56

12

9

9

11

14

64

13

10

11

13

16

72

14

11

12

14

18

80

15

12

13

16

21

88

16

13

15

18

24

96

17

14

16

20

26

104

18

16

18

22

29

112

19

17

19

24

32

120

20

18

21

26

‑‑

128

21

20

22

28

136

22

21

24

30

144

23

22

26

32

152

24

24

27

34

160

25

25

29

37

168

26

26

30

40

176

27

28

32

42

184

28

29

34

45

192

29

30

36

48

200

30

32

38

50

208

31

33

40

53

216

32

35

42

56

224

J.4 Encoding algorithm

The choice is done recursively as given by the following programs, written in ADA:

Let us define the recursive procedure:

procedure ENCODE_SUBTREE(in INDEX : INTEGER;

in SET : SET_OF_VALUE;

in RANGE : INTEGER);

This procedure is given a set of integer values and an index. It chooses one of those values and computes the corresponding W(INDEX) (considered as a global variable), it splits the set less the value in two equal or nearly equal subsets, and calls itself recursively for each of those subsets, with suitable INDEX.

Assumption: all values in SET lie (inclusively) between 0 and RANGE-1, and they are all distinct.

As written, the program does not assume special values for the range. With a range such as 2k-1, some expressions can be simplified.

Declarative part:

INDEX_IN_SET : INTEGER;

begin

First the program tests the leaf conditions :

if SET’SIZE=0 then

W(INDEX) := 0;

return;

elsif SET’SIZE=1 then

W(INDEX) := 1 + SET(1);

return;

end if;

The following program finds a value in the set such that exactly (SET’SIZE-1)/2 values from the set are between this value plus 1 and this value plus half the range:

declare

N : INTEGER;

J : INTEGER;

begin

for I in 1..SET’SIZE loop

N:=0;

for J in 1..SET’SIZE loop

if (SET(J)-SET(I)) mod RANGE  (RANGE-1)/2 then

N := N+1;

end if;

end loop;

The test compares N-1 because the possible pivot value is counted.

if N-1 = (SET’SIZE-1)/2 then

INDEX_IN_SET := I;

exit;

end if;

end loop;

end;

INDEX_IN_SET is then the index in the list of the pivot value.

The following sets W(INDEX)

W(INDEX) := SET(INDEX_IN_SET) + 1;

Then the program does the same thing for the two halves of the range delimited by W(INDEX) and W(INDEX)+RANGE/2. First the left subset:

declare

SUBSET : SET_OF_VALUE(1..SET’SIZE/2);

SUBSET_INDEX : INTEGER;

ORIGIN_VALUE : INTEGER;

begin

ORIGIN_VALUE := (SET(INDEX_IN_SET] + (RANGE-1)/2

+ 1) mod RANGE;

SUBSET_INDEX:=1;

for I in 1..SET’SIZE loop

if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then

SUBSET(SUBSET_INDEX) :=

(SET(I) – ORIGIN_VALUE) mod RANGE;

SUBSET_INDEX := SUBSET_INDEX + 1;

end if;

end loop;

ENCODE_SUBTREE(

INDEX := INDEX +

GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX),

SET := SUBSET,

RANGE := RANGE/2);

end;

Then the right subset:

declare

SUBSET : SET_OF_VALUE(1..(SET’SIZE-1)/2);

SUBSET_INDEX : INTEGER;

ORIGIN_VALUE : INTEGER;

begin

ORIGIN_VALUE := (SET(INDEX_IN_SET] + 1) mod RANGE;

SUBSET_INDEX:=1;

for I in 1..SET’SIZE loop

if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then

SUBSET(SUBSET_INDEX) :=

(SET(I) – ORIGIN_VALUE) mod RANGE;

SUBSET_INDEX := SUBSET_INDEX + 1;

end if;

end loop;

ENCODE_SUBTREE(

INDEX := INDEX +

2*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX),

SET := SUBSET,

RANGE := (RANGE-1)/2);

end;

end ENCODE_SUBTREE;

The initial call of the procedure depends on the format. Given some set to encode, the first problem is to verify that it can be encoded, and by so doing to choose the format.

First the encoding process must find the minimum range of the set, that is to say the minimum value R such that there exists one frequency F0 in the set such that all frequencies in the set can be written (F0 + N) mod 1024, with some N, 0  N  R‑1. The choice of the format depends on R and the number of frequencies : the 512 range format can be chosen only if R512, the 256 range format can be chosen only if R256, the 128 range format can be chosen only if R128.

If the chosen format is "1024 range", then the program must first check if frequency 0 is in the set. If so the F0 subfield is set to 1, and frequency 0 is removed from the set. Otherwise, the F0 subfield is set to 0. Then ENCODE_SUBTREE is called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies minus 1, and RANGE := 1023.

If the chosen format is "512 range", "256 range" or "128 range", F0 is chosen as ORIG-ARFCN and ENCODE_SUBTREE is called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies except F0, minus F0+1, and RANGE set respectively to 511, 255 or 127.

J.5 Decoding

The decoding algorithm, as given below, is the inverse transform of the program given in the previous sub-clause, for the specific case where the original range is a power of 2 minus 1. It is given a set of integer values W(i), and an original range R, and it builds a set of values from 0..R-1.

The program is here written so that the fact that it is the inverse of the encoding program needs no more proof.

procedure DECODE(in W : array <> of INTEGER;

out SET : SET_OF_VALUE;

in ORIGINAL_RANGE : INTEGER);

— local variables

INDEX : 1..W’SIZE; RANGE : INTEGER;

N : INTEGER;

begin

for K in 1..W’SIZE loop

The next loop follows the tree from child to parent, from the node of index K to the root (index 1). For each iteration the node of index INDEX is tackled. The corresponding range is RANGE, and N is the value of the element in the range defined by the node.

The data are set to their initial values :

INDEX := K;

RANGE := ORIGINAL_RANGE / GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX);

N := W(INDEX) – 1;

while INDEX>1 loop

Due to the assumption that the original range is a power of two minus one, the range for the parent node can be easily computed, and does not depend upon whether the current node is a left or right child :

RANGE := 2*RANGE + 1;

Let us note J := 2g-1, g being the generation of node INDEX. We have J = GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX).

The numbering used in the tree is such that the nodes of index J to J + J/2 – 1 are left children, and the nodes of index J/2 to J+J-1 are right children. Hence an easy test to distinguish left and right children:

if 2*INDEX <

3*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX)

then — left child

The next computation gives the index of the parent node of the node of index INDEX, for a left child :

INDEX := INDEX –

GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX)/2;

The next formula is the inverse of the renumbering appearing in the encoding for a left child. It gives the value of the parent node in the range defined by the grand-parent node:

N := (N + W(INDEX) – 1 + (RANGE-1)/2 + 1)

mod RANGE;

else — right child

The next computation gives the index of the parent node of the node of index INDEX, for a right child :

INDEX := INDEX – GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX);

The next formula is the inverse of the renumbering appearing in the encoding for a right child:

N := (N + W(INDEX) – 1 + 1) mod RANGE;

end if;

end loop;

F(K) := N;

end loop;

end;

A careful study will show that the programs given in the main part of the Technical Specification are equivalent to the one presented here. The main difference is the use of different remnant variables to remove most of the calls to the function giving the greatest power of 2 less than or equal to some integer.

The decoding must be terminated by the correction specific to the format.

J.6 A detailed example

Let us take the following subset of 16 elements of the set [0..1023] : [13, 71, 122, 191, 251, 321, 402, 476, 521, 575, 635, 701, 765, 831, 906, 981]

Range 1024 format will be used. Frequency 0 is not in the set, thus field F0 is set to 0. The set is renumbered, so as to give a subset of 0..1022 : [12, 70, 121, 190, 250, 320, 401, 475, 520, 574, 634, 700, 764, 830, 905, 980].

For the first node (corresponding to W(1)), the value 121 satisfies the requirements. The opposite value is 121 + 511 = 632. There are 8 values between 633 and 120 (namely the left-hand subset 634, 700, 764, 830, 905, 980, 12 and 70), and 7 values between 122 and 632 (namely the right-hand subset 190, 250, 320, 401, 475, 520 and 574).

The encoded value W(1) is 121 + 1, i.e. 122.

The second node (corresponding to W(2)) is the left-hand child of the first node. The corresponding subtree has to encode for the left-hand subset, renumbered beginning at 633. This gives the following 8 element subset of 0..510, ordered as resulting from the example of algorithm : [402, 460, 1, 67, 131, 197, 272, 347]. Out of these values, 1 splits the set in 4 and 3, and the encoded value W(2) is 2.

Similarly, the third node (W(3)) is the right-hand child of the first node and then the corresponding subtree encodes for the right-hand subset, renumbered starting at 122. This gives the following set of 0..510 : [68, 128, 198, 279, 353, 398, 452]. Out of these values, 68 splits the set into 3 and 3, and the encoded value W(3) is 69.

The same method is applied for all nodes, giving the following encoded values per node.

Node

Value

1

122

2

2

3

69

4

204

5

75

6

66

7

60

8

70

9

83

10

3

11

24

12

67

13

54

14

64

15

70

16

9

The encoding then consists in formatting, in that order:

122 on 10 bits, then 2 and 69 on 9 bits each, then 204, 75, 66 and 60 on 8 bits each, then 70, 83, 3, 24, 67, 54, 64 and 70 on 7 bits each, and finally 9 on 6 bits.

Conversely the decoding can be done easily. For instance for node 2, the original value is:

(122 – 512 + 2) smod 1023 = 635

For node 14, we have as original value:

(122 – 512 + (2 + (66 + 64)smod 255)smod 511)smod 1023 = 765

Annex K (informative):
Default Codings of Information Elements

The information in this annex does NOT define the value of any IEI for any particular message. This annex exists to aid the design of new messages, in particular with regard to backward compatibility with phase 1 mobile stations.

K.1 Common information elements

For the common information elements see 3GPP TS 24.008 annex K.

K.2 Radio Resource management information elements

For the Radio Resource management information elements listed below, the default coding of the information element identifier bits is summarized in table K.2.

Table K.2 (page 1 of 2): Default information element identifier coding
for Radio Resource management information elements

8

7

6

5

4

3

2

1

Reference sub-clause

1

:

:

:

Type 1 info elements

1

0

0

1

Cipher Mode Setting

10.5.2.9

1

0

1

0

Cipher Response

10.5.2.10

1

0

1

1

Note

1

1

0

1

Synchronization Indication

10.5.2.39

1

1

1

0

Channel Needed

10.5.2.8

0

:

:

:

:

:

:

:

Type 3 & 4 info elements

0

0

0

0

0

0

1

0

Frequency Short List

10.5.2.14

0

0

0

0

0

1

0

1

Frequency List

10.5.2.13

0

1

1

0

0

0

0

1

Note

0

1

1

0

0

0

1

0

Cell Channel Description

10.5.2.1b

0

1

1

0

0

0

1

1

Channel Mode

10.5.2.6

0

1

1

0

0

1

0

0

Channel Description

10.5.2.5

0

1

1

0

0

1

1

0

Channel Mode 2

10.5.2.7

0

1

1

0

1

0

0

0

Note

0

1

1

0

1

0

0

1

Frequency Channel Sequence

10.5.2.12

0

1

1

0

1

0

1

0

Note

0

1

1

0

1

0

1

1

Note

0

1

1

0

1

1

0

0

Note

0

1

1

1

0

0

0

1

Note

0

1

1

1

0

0

1

0

Mobile Allocation

10.5.2.21

0

1

1

1

0

0

1

1

BA range

10.5.2.1

0

1

1

1

0

1

0

0

Note

0

1

1

1

0

1

0

1

Note

0

1

1

1

0

1

1

0

Note

0

1

1

1

0

1

1

1

Mobile Time difference

10.5.2.21a

0

1

1

1

1

0

0

0

Note

0

1

1

1

1

0

0

1

Note

0

1

1

1

1

0

1

0

Note

0

1

1

1

1

0

1

1

Time Difference

10.5.2.41

0

1

1

1

1

1

0

0

Starting Time

10.5.2.38

0

1

1

1

1

1

0

1

Timing Advance

10.5.2.40

0

1

1

1

1

1

1

0

TMSI

10.5.2.42

0

1

1

1

1

1

1

1

Note

NOTE: These values were allocated but never used in earlier phases of the protocol.

Annex L (normative):
Additional Requirements for backward compatibility with PCS 1900 for NA revision 0 ME

See 3GPP TS 24.008.

Annex M (informative):
Change history

Meeting

CR

Rev

Subject

New

SMG#29

A371

2

BCIE modifications due to EDGE

8.0.0

SMG#29

A515

1

Split of 04.08 in RR and CN parts (Sub-clause 7, "L3 stage2")

8.0.0

SMG#29

A562

CR to 04.08 due to EDGE SMG2 EDGE WS

8.0.0

SMG#29

A567

1

Split of 04.08 in RR and CN parts

8.0.0

SMG#29

A592

1

GSM 400 and Mobile Station Classmark

8.0.0

SMG#29

A611

1

Split of 04.08 in RR and CN parts

8.0.0

SMG#29

A613

1

Split of 04.08 in RR and CN parts

8.0.0

SMG#29

A621

2

IE Daylight saving time

8.0.0

SMG#29

A687

Transfer of the LSA Information to the MS

8.0.0

SMG#30

A002

Correction of Mobile Station Classmark 2 in the Talker Indication message

8.1.0

SMG#30

A004

Modification due to ECSD Asymmetry

8.1.0

SMG#30

A005

Fast power control

8.1.0

SMG#30

A006

1

Compact Cell Reselection

8.1.0

SMG#30

A008

1

EGPRS support on 04.18 Immediate Assignment & PDCH assignment.

8.1.0

SMG#30

A009

1

Alignment on 04.60 of information elements RR Packet Uplink and Downlink Assignment

8.1.0

SMG#30

A010

1

Clarification of MCC and MNC in SI 4/16/17 rest octets

8.1.0

SMG#30

A011

Length of BA List Pref IE in the Channel Release message

8.1.0

SMG#30

A013

1

Alignment of RLC_OCTET_COUNT in 04.08 with 04.60

8.1.0

SMG#30

A014

System information type 14 and 15

8.1.0

SMG#30

A015

EDGE Compact and support for EGPRS in ANSI-136 networks

8.1.0

SMG#30

A016

1

Introduction of short LSA ID.

8.1.0

SMG#30

A018

1

New coding of SI 4/7/8 Rest Octets.

8.1.0

SMG#30

A019

Correction to handling of GPRS suspension cause

8.1.0

SMG#30

A022

2

Alignment between 04.08 & 04.60 on the packet access procedure attempt following T3142 or T3172 attempt

8.1.0

SMG#30

A023

Addition of 3rd MNC digit in Routing Area Identification and correction of LAI

8.1.0

SMG#30

A024

Addition of new SI type in SI 9 Rest Octets.

8.1.0

SMG#30

A025

Addition of PR mode in ASSIGNMENT message in 04.08

8.1.0

SMG#30bis

A007

2

Definition of extended TA layer 3 information

8.2.0

SMG#30bis

A028

Applicability of "Uplink Reply"

8.2.0

SMG#30bis

A029

Removal of old message types

8.2.0

SMG#30bis

A030

Corrections in Uplink management procedures

8.2.0

SMG#30bis

A031

NCH parameters & combined CCCH

8.2.0

SMG#30bis

A037

Editorial (misleading reference) (R99)

8.2.0

SMG#30bis

A041

Handover execution in cells that support extended TA IE

8.2.0

SMG#30bis

A042

Introduction of two ‘Release Indication’ bits in the BCCH

8.2.0

SMG#30bis

A051

Multiband on early classmark sending

8.2.0

SMG#30bis

A052

1

Packet extended timing advance

8.2.0

SMG#30bis

A053

Correction to Packet Access Reject procedure

8.2.0

SMG#31

A003

3

Non-GSM Broadcast Information

8.3.0

SMG#31

A038

2

EGPRS COMPACT Cell Selection, Cell Bar Qualify 2

8.2.0

SMG#31

A063

1

Alignment of 04.18 with 04.60 for EGPRS Downlink Assignments

8.3.0

SMG#31

A064

Support for packet pause procedure for mobile stations capable of non-GSM circuit operation

8.3.0

SMG#31

A065

COMPACT Cell Selection, Cell Bar Qualify 2 removal

8.3.0

SMG#31

A068

Emergency Call Handling in COMPACT

8.3.0

SMG#31

A001

3

Immediate assignment

8.3.0

SMG#31

A033

5

PR_MODE field in assignment message

8.3.0

SMG#31

A040

2

Channel Request Description IE length and Packet Channel Description IE coding

8.3.0

SMG#31

A054

Clarification of the RLC/MAC segmentation in single block allocation

8.3.0

SMG#31

A073

Suspension Cause IE

8.3.0

SMG#31

A075

Clarification of starting timer T3134

8.3.0

SMG#31

A043

1

Uplink L3 Message Sequencing

8.3.0

SMG#31

A035

2

Intorduction of LCS into 3GPP TS 04.08

7.2.0

SMG#31bis

none

First some purely editorial changes have been made implementing ETSIs stylesheet in a noticebly better way, and figures in LD (linedraw) format have been corrected to table format which is also readable in Windows 2000. Corroded bullit styles in sub-clause 3.4.17 which consistently crashed the PCs have been corrected. All those framed CSN.1 parts have been corrected to ‘real’ tables, which is much more stable and easier to maintain.

8.4.0

SMG#31bis

A082

Addition of CSCH description

8.4.0

SMG#31bis

A084

Inconsistent Rest Octet length indication

8.4.0

SMG#31bis

A091

Inter System Handover Command (scls 10.5.2.48 in CR is added as scls 10.5.2.51

8.4.0

SMG#31bis

A094

Correction of SI 4 Rest Octets

8.4.0

SMG#31bis

A080

Moving NOTIFICATION RESPONSE from MM to GSM RR

8.4.0

SMG#31bis

A101

1

Downlink and Uplink information for Measurement Reporting and Enhanced Measurement Reporting on 3G Cells. Note that scls 9.1.53 and 54 in the CR has been added as 9.1.54 and 9.1.55.

8.4.0

SMG#31bis

A081

1

COMPACT : impact of new block ordering on SI19

8.4.0

SMG#31bis

A097

1

EGPRS and IA Rest Octets IE

8.4.0

SMG#31bis

A098

2

DTM: definition of new procedures while in dedicated mode

8.4.0

SMG#31bis

A092

2

Support of Handover from GSM to cdma2000

8.4.0

SMG#31bis

A056

4

EGPRS mode TBF establishment on CCCH

8.4.0

SMG#31bis

A086

2

Clarification of power control requirements during TBF establishment

8.4.0

SMG#31bis

A085

2

Incomplete Rest Octet information

8.4.0

SMG#31bis

A090

2

New measurement order – Idle mode

8.4.0

SMG#31bis

A099

2

DTM: definition of new messages

8.4.0

SMG#31bis

A057

5

Blind search Idle Mode – SI2ter

8.4.0

SMG#31bis

A062

3

RR UTRAN Classmark Change

8.4.0

SMG#31bis

A089

1

RR Pre-configuration Command

8.4.0

SMG#31bis

A095

3

Distributing UMTS frequencies to the mobiles

8.4.0

SMG#31bis

A104

2

UE Classmark Enquiry

8.4.0

SMG#32

A105

2

DTM: Replacement of Channel Request Description 2 IE

8.5.0

SMG#32

A106

DTM: Removal of DTM Reject Information

8.5.0

SMG#32

A107

DTM: Editorial Corrections

8.5.0

SMG#32

A108

1

Maximum size of fixed ALLOCATION_BITMAP

8.5.0

SMG#32

A110

2

DTM: Alignment of normal release procedure

8.5.0

SMG#32

A113

DTM: Alignment of the assignment procedure

8.5.0

SMG#32

A117

2

GSM to 3G Handovers: Various Corrections and Clarifications

8.5.0

SMG#32

A119

Clarification of Channel Mode Modify and Configuration Change procedures ( RSB )

8.5.0

SMG#32

A124

Definition of the SCALE parameter

8.5.0

GP-01

A137

DTM: GPRS information for DTM operation – TBF re-establishment

8.6.0

GP-01

A139

Interpretation addition of CELL_BAR_QUALIFY_2 value

8.6.0

GP-01

A140

DTM and EGPRS

8.6.0

GP-01

A141

Correction on Measurement Info message

8.6.0

GP-01

A143

SI2quater updates to allow GPRS -> UMTS Cell Reselection.

8.6.0

GP-01

A146

1

Handover to UMTS description procedure including "blind handover" to UMTS.

8.6.0

GP-01

A147

1

Correction on UTRAN classmark change procedure

8.6.0

GP-01

A136

1

Support of 11 bits request reference in IA and IAR messages

8.6.0

GP-01

A152

AMR Noise Suppressor Control

8.6.0

GP-01

A142

1

SI2ter bit map correction.

8.6.0

GP-01

A150

1

Editorial correction on RR Packet Uplink/Downlink Assignment

8.6.0

GP-01

A127

DTM: Removal of polling from DTM assignment

8.6.0

GP-01

A144

2

Detailed coding modifications for the Pre-configurations.

8.6.0

GP-01

A135

DTM: definition

8.6.0

GP-01

A126

1

Extended measurement report (MAFA)

8.6.0

GP-01

A128

1

DTM: Correction of timers T3148 and T3107

8.6.0

GP-01

A129

DTM: tunnelling of GPRS information on the main DCCH

8.6.0

GP-01

A130

1

DTM: provision of GPRS information for correct DTM behaviour

8.6.0

GP-01

A131

1

DTM: reuse of the GPRS Suspension procedure in cells with no DTM capabilities

8.6.0

GP-01

A132

DTM: alignment of the handover procedure

8.6.0

GP-01

A133

DTM: clarification of Radio Link Failure and RR connection abortion while in DTM

8.6.0

GP-01

A134

1

DTM: removal of the Main DCCH Assignment message

8.6.0

GP-01

A125

Handling of Power-Control-Parameter alpha

8.6.0

GP-01

none

Implementation comments (in addition to the CRs):

Tables formatting improved. Strange pagebreaks removed. Change History table tightned up. Defect and unused textstyle crashing PCs and persistent to earlier removal attempts now removed. Format updated to 3GPP style.

8.6.0

GP-02

A162

Inclusion of Cell Bar Quality 2 in the neighbour cell descriptions in SI19

8.7.0

GP-02

A180

Support for interworking with 1.28 Mcps TDD cells

8.7.0

GP-02

A177

1

Deletion of the UE RAB pre-configuration message

8.7.0

GP-02

A174

Cipher mode setting in HO command

8.7.0

GP-02

A173

Editorial corrections

8.7.0

GP-02

A171

Indication of notifications and paging information

8.7.0

GP-02

A169

1

Indication of availability of UTRAN pre-configurations from the GSM BCCH.

8.7.0

GP-02

A168

1

Handover to UMTS procedure, abnormal cases : MS behaviour.

8.7.0

GP-02

A167

1

3G Cell Reselection list.

8.7.0

GP-02

A153

Clarification of downlink bit

8.7.0

GP-02

A163

2

Editorials and corrections to GSM-UTRAN interworking

8.7.0

GP-02

A161

Enable several instances of SI18 and SI20

8.7.0

GP-02

A160

2

DTM: RR reallocation during packet access (R99)

8.7.0

GP-02

A159

2

DTM: Corrections to the abnormal cases (R99)

8.7.0

GP-02

A158

DTM: DTM Reject with wait indication (R99)

8.7.0

GP-02

A157

DTM: RR interaction with the datalink layer (R99)

8.7.0

GP-02

A155

Second Part Packet Assignment in IA Rest octet

8.7.0

GP-02

A175

DTM: Alignment of the intersystem handover procedure

8.7.0

GP-02

A154

Correction of send sequence number handling

8.7.0

GP-02

A164

UTRAN Classmark Change : CSN1 corrections.

8.7.0

Removal of unused references. Formatting alignment with 44.018. Table and Figure numbers corrected.

8.7.0

GP-03

A181

1

BSICs in idle mode and default preconfigurations: procedure and terminology alignments.

8.8.0

GP-03

A182

1

Correction of SI19 Rest Octets

8.8.0

GP-03

A183

Removal of Anonymous Access

8.8.0

GP-03

A185

DTM: Replacement of ‘padding bits’ in RR messages

8.8.0

GP-03

A186

1

Precision about Blind Handover 2G > 3G (R99)

8.8.0

GP-03

A187

1

Blind HandOver 2G > 2G (R99)

8.8.0

GP-03

A188

1

Control of ARFCN channel numbering for 1800 and 1900.

8.8.0

GP-04

A194

1

The use of UTRAN Central frequencies by "Class C GPRS" (&UTRAN) mobiles

8.9.0

GP-04

A195

GERAN to UTRAN RR-Network Controlled Cell Change Order: abnormal case

8.9.0

GP-04

A196

1

Editorial alignments and clarifications

8.9.0

GP-04

A190

1

MEASUREMENT_STARTING_TIME field in RR Packet Downlink Assignment IE

8.9.0

GP-04

A191

1

Introduction of a presence bit indicator for SI2quater

8.9.0

GP-04

A192

2

Clarifications on Solsa requirements

8.9.0

GP-05

A199

Invalid BSICs : Terminology alignment.

8.10.0

GP-05

A189

2

This structure contains the report of cells with invalid BSIC.

8.10.0

GP-05

A207

Handling of starting time in the case of intersystem handover to GSM and in the case of blind handover

8.10.0

GP-05

A201

Transfer of the N(SD) duplication avoidance protocol from 3GPP TS 04.18

8.10.0

GP-05

A203

Coding Corrections to Measurement information and SI2quater

8.10.0

GP-05

A200

2

Introduction of the GSM to CDMA2000 handover procedure.

8.10.0

GP-05

A204

3

Clarification of predefined configuration status report

8.10.0

GP-06

A216

1

Alignments and Clarifications (e.g. for equivalent PLMNs) (R99)

8.11.0

GP-06

A215

Removal of IEI explicit value in the UTRAN Frequency list information element description (R99)

8.11.0

GP-06

A212

Error in the introduction of CR A199 (R99)

8.11.0

GP-06

A208

2

Introduction of UTRAN blind search from the SI2 quater (R99)

8.11.0

GP-06

A225

Introduction of the band indicator field in SI6 (R99)

8.11.0

GP-06

A220

2

Clarification of the Index_Start_3G parameter (R99)

8.11.0

GP-06

A223

Removal of IEI explicit value in the BA List Pref information element description (R99)

8.11.0

GP-06

A224

Clarification of "inconsistent" MultiRate configuration IE (R99)

8.11.0

GP-07

A238

Correction on GSM400 measurement parameter coding

8.12.0

GP-07

A236

1

Support of Early Classmark Sending by an PBCCH capable cell

8.12.0

GP-07

A230

Clarification of the term primary scrambling code.

8.12.0

GP-07

A233

1

Alignment of ASSIGNMENT CMD, HO CMD and CH MOD MOD for AMR

8.12.0

GP-07

A226

1

Backward compatibility problem in SI2ter Rest octets

8.12.0

GP-07

A237

Restoration of the SI 3 Rest Octets IE description

8.12.0

GP-07

A229

1

Transparent UMTS specific information in Classmark Change

8.12.0

GP-07

A234

1

Correction on Ciphering Mode Setting IE in HANDOVER COMMAND

8.12.0

GP-08

A239

2

Correction about BSIC and RTD for neighbour cells

8.13.0

GP-08

A241

Number of cells and frequencies in the 3G Neighbour cell list.

8.13.0

GP-09

A242

Correction of DTM message type values

8.14.0

GP-09

A245

1

Backwards compatibility of R99 extensions in IA Rest octets

8.14.0

GP-09

A246

1

Backwards compatibility of R99 extensions in RR Packet Downlink Assignment IE

8.14.0

GP-09

A247

2

Backwards compatibility of R99 extensions in RR Packet Uplink Assignment IE

8.14.0

GP-09

A254

Alignment of "resegment" information description

8.14.0

GP-09

A252

Initial 3G Neighbour cell reporting in dedicated mode

8.14.0

GP-09

A249

1

PFC for DTM

8.14.0

GP-10

A253

2

Correction to indexing mechanism for UTRAN frequencies

8.15.0

GP-10

A257

2

Removal of CBQ2

8.15.0

GP-10

A256

3

Removal of UTRAN Frequency List

8.15.0

GP-11

A259

Correction to DTM Failure Cases

8.16.0

GP-11

A260

1

Correction to abnormal cases of establishment of TBFs whilst in dedicated mode

8.16.0

GP-11

A261

1

MS behaviour in case of a failed authentication of the network

8.16.0

GP-11

A267

2

Consistent behaviour in an EGPRS cell in case of uplink signalling causing downlink user data transfer

8.16.0

GP-12

A271

Two-message packet downlink assignment on CCCH

8.17.0

GP-13

A272

1

Wrong CR incorporation "Removal of CBQ2" in SI19 rest octets

8.18.0

GP-15

A275

Correction of erroneous mathematical expressions

8.19.0

GP-17

A277

1

Correction on Dedicated Mode or TBF Information Element format (Recover from v8.16.0)

8.20.0

GP-17

Added reference to 3GPP TS 05.03. Corrected reference to 3GPP TS 03.22 and 3GPP TS 03.71. Eased the reference style used for tables and figures.

8.20.0

GP-18

A278

2

Addition of Multi Rate Config IE to the message DTM ASSIGNMENT COMMAND

8.21.0

GP-18

A280

3

Lack of FH parameters during VGCS handover

8.21.0

GP-18

A282

1

Correction of incomplete information element descriptions

8.21.0

GP-19

A284

Short access removal

8.22.0

GP-20

A285

Correction of the CSN.1 coding of the SI10 Rest Octets to be used for ASCI

8.23.0

GP-20

A287

1

Ambiguous definition of SI2ter Rest Octets

8.23.0

GP-20

A289

Correction of DTM output power control

8.23.0

GP-21

A293

2

Starting Time in DTM ASSIGMENT COMMAND and in PACKET ASSIGNMENT message

8.24.0

GP-21

A291

Correction to Group Channel Description IE

8.24.0

GP-21

A290

VGCS Target Mode Indication IEI

8.24.0

GP-23

A294

2

Missing cell identity in DTM Information message

8.25.0

GP-24

A295

1

Inconsistent coding of FORMAT ID in variable bitmap format of Cell Channel Description

8.26.0

GP-29

A296

DTM establishment with full duplex PS resources

8.27.0

GP-29

A298

1

TBF handling upon reception of a DTM ASSIGNMENT COMMAND

8.27.0