11 General message format and information elements coding
3GPP44.318Generic Access Network (GAN)Mobile GAN interface layer 3 specificationRelease 17TS
11.1 Message coding principles
Five different message headers are defined in this specification:
– Message header for the GA-RC and GA-CSR messages (defined in sub-clause 11.1.1)
– Message header for the GA-PSR messages sent over the TCP-based signalling channel (defined in sub-clause 11.1.2)
– Message header for the GA-PSR messages sent over the UDP-based GA-PSR Transport Channel (defined in sub-clause 11.1.3)
– Message header for the GA-RRC messages sent over the TCP-based signalling channel (defined in sub-clause 11.1.3a)
– Message header for the GA-RRC messages sent over the UDP-based GA-RRC Packet Transport Channel (defined in sub-clause 11.1.3b)
The principles for information element coding are described in sub-clause 11.1.4.
11.1.1 GA-RC and GA-CSR message header information elements
Each GA-RC and GA-CSR message begins with a 4-octet message header, as shown in Table 11.1.1.1. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator and Message Type. These IEs are described in the following sub-clauses.
Note that these information elements are also present in both the GA-PSR message header and the GA-RRC message header defined in sub-clauses 11.1.2 and 11.1.3a, respectively. However, the GA-PSR and GA-RRC message headers include additional information elements.
Table 11.1.1.1: GA-RC and GA-CSR message header contents
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Value |
Notes |
Length Indicator |
Length Indicator |
M |
V |
2 |
|||
GA-RC and GA-CSR Protocol Discriminator |
Protocol Discriminator |
M |
V |
½ |
0001 |
||
Skip Indicator |
Skip Indicator |
M |
V |
½ |
0000 |
||
GA-RC and GA-CSR Message Type |
Message Type |
M |
V |
1 |
|||
Here continues the list of IE’s using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. |
11.1.1.1 Length Indicator (LI)
The first two octets of the message header contains the Length Indicator (LI) information element. The LI is needed as each message is transported using TCP, which provides a ‘stream-of-bytes’ transmission i.e. no message concept, or message length concept is provided by TCP and this has to be handled in the application layer.
This field specifies the total length of the message excluding the 2 octets for Length Indicator.
Minimum value for LI is 2 and maximum value is defined as 2048.
For example: For a message of total length of 20 octets, this field is coded with the decimal value of 18. Then there follows 18 octets of message (i.e. total length of TCP-data is 20 octets).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
LI MSB |
octet 1 |
|||||||||
LI LSB |
octet 2 |
Figure 11.1.1.1.1. Length Indicator message header field
Table 11.1.1.1.1: Length Indicator message header field
LI value, Length Indicator value (octet 1 and 2) In the LI value field bit 8 of octet 1 is the most significant bit and bit 1of octet 2 the least significant bit. The Length Indicator consists of 2 octets. |
11.1.1.2 Protocol Discriminator (PD)
Bits 1 to 4 of the third octet in the message header contain the Protocol Discriminator (PD) information element. The PD identifies the upper layer protocol to which the message belongs.
The following Protocol Discriminator values are defined:
Table 11.1.1.2.1: Protocol Discriminator Values
Protocol |
PD Value |
GA-RC |
0 |
GA-CSR |
1 |
GA-PSR |
2 |
GA-RRC |
3 |
11.1.1.3 Skip Indicator
Bits 5 to 8 of the third octet in the message header contain the Skip Indicator information element. A message received with Skip Indicator different from 0000 shall be ignored. A message received with Skip Indicator encoded as 0000 shall not be ignored (unless it is ignored for other reasons). A protocol entity sending any message shall encode the Skip Indicator as 0000.
11.1.1.4 Message Type
The Message Type IE is the fourth octet in the message header. Bit 8 of the Message Type value is the most significant bit and bit 1 is the least significant bit.
The following message types are defined for GA-RC and GA-CSR:
Table 11.1.1.4.1: Message Type values for GA-RC
GA-RC message name |
Message Type value (decimal) |
Message Type value (hex) |
GA-RC DISCOVERY REQUEST |
1 |
H’01 |
GA-RC DISCOVERY ACCEPT |
2 |
H’02 |
GA-RC DISCOVERY REJECT |
3 |
H’03 |
GA-RC REGISTER REQUEST |
16 |
H’10 |
GA-RC REGISTER ACCEPT |
17 |
H’11 |
GA-RC REGISTER REDIRECT |
18 |
H’12 |
GA-RC REGISTER REJECT |
19 |
H’13 |
GA-RC DEREGISTER |
20 |
H’14 |
GA-RC REGISTER UPDATE UPLINK |
21 |
H’15 |
GA-RC REGISTER UPDATE DOWNLINK |
22 |
H’16 |
GA-RC CELL BROADCAST INFO |
23 |
H’17 |
GA-RC KEEP ALIVE |
116 |
H’74 |
GA-RC SYNCHRONIZATION INFORMATION |
120 |
H’78 |
Table 11.1.1.4.2: Message Type values for GA-CSR
GA-CSR message name |
Message Type value (decimal) |
Message Type value (hex) |
GA-CSR CIPHERING MODE COMMAND |
32 |
H’20 |
GA-CSR CIPHERING MODE COMPLETE |
33 |
H’21 |
GA-CSR ACTIVATE CHANNEL |
48 |
H’30 |
GA-CSR ACTIVATE CHANNEL ACK |
49 |
H’31 |
GA-CSR ACTIVATE CHANNEL COMPLETE |
50 |
H’32 |
GA-CSR ACTIVATE CHANNEL FAILURE |
51 |
H’33 |
GA-CSR CHANNEL MODE MODIFY |
52 |
H’34 |
GA-CSR CHANNEL MODE MODIFY |
53 |
H’35 |
GA-CSR RELEASE |
64 |
H’40 |
GA-CSR RELEASE COMPLETE |
65 |
H’41 |
GA-CSR CLEAR REQUEST |
66 |
H’42 |
GA-CSR HANDOVER ACCESS |
80 |
H’50 |
GA-CSR HANDOVER COMPLETE |
81 |
H’51 |
GA-CSR UPLINK QUALITY INDICATION |
82 |
H’52 |
GA-CSR HANDOVER INFORMATION |
83 |
H’53 |
GA-CSR HANDOVER COMMAND |
84 |
H’54 |
GA-CSR HANDOVER FAILURE |
85 |
H’55 |
GA-CSR PAGING REQUEST |
96 |
H’60 |
GA-CSR PAGING RESPONSE |
97 |
H’61 |
GA-CSR UPLINK DIRECT TRANSFER |
112 |
H’70 |
GA-CSR DOWNLINK DIRECT TRANSFER |
114 |
H’72 |
GA-CSR STATUS |
115 |
H’73 |
GA-CSR CLASSMARK ENQUIRY |
117 |
H’75 |
GA-CSR CLASSMARK CHANGE |
118 |
H’76 |
GA-CSR GPRS SUSPENSION REQUEST |
119 |
H’77 |
GA-CSR UTRAN CLASSMARK CHANGE |
121 |
H’79 |
GA-CSR REQUEST |
128 |
H’80 |
GA-CSR REQUEST ACCEPT |
129 |
H’81 |
GA-CSR REQUEST REJECT |
130 |
H’82 |
11.1.2 GA-PSR message header information elements over TCP
Each GA-PSR message sent over the TCP-based signalling channel begins with an 8-octet message header. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator, Message Type and TLLI. These IEs are described in the following sub-clauses.
Table 11.1.2.1: GA-PSR (TCP) message header contents
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Value |
Notes |
Length Indicator |
Length Indicator |
M |
V |
2 |
|||
GA-PSR Protocol Discriminator |
Protocol Discriminator |
M |
V |
½ |
0010 |
||
Skip Indicator |
Skip Indicator |
M |
V |
½ |
0000 |
||
GA-PSR Message Type |
GA-PSR Message Type |
M |
V |
1 |
|||
TLLI |
TLLI |
M |
V |
4 |
|||
Here continues the list of IE’s using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. |
11.1.2.1 GA-PSR Message Type
The GA-PSR Message Type IE is the fourth octet in the GA-PSR (TCP) message header. Bit 8 of the GA-PSR Message Type value is the most significant bit and bit 1 is the least significant bit.
The following GA-PSR Message Type values are defined:
Table 11.1.2.1.1: GA-PSR Message Type values (TCP)
GA-PSR message name |
GA-PSR Message Type value (decimal) |
GA-PSR-DATA |
1 |
GA-PSR-PS-PAGE |
3 |
GA-PSR-ACTIVATE-UTC-REQ |
8 |
GA-PSR-ACTIVATE-UTC-ACK |
9 |
GA-PSR-DEACTIVATE-UTC-REQ |
10 |
GA-PSR-DEACTIVATE-UTC-ACK |
11 |
GA-PSR STATUS |
12 |
GA-PSR HANDOVER COMPLETE |
13 |
GA-PSR UPLINK QUALITY INDICATION |
14 |
GA-PSR HANDOVER INFORMATION |
15 |
GA-PSR HANDOVER COMMAND |
16 |
GA-PSR HANDOVER CONTINUE |
17 |
GA-PSR HANDOVER FAILURE |
18 |
11.1.2.2 Temporary Logical Link Identity (TLLI)
Octets 5 to 8 of the GA-PSR (TCP) message header contain the Temporary Logical Link Identity (TLLI) information element. The TLLI identifies the MS this message was sent by or sent to.
11.1.3 GA-PSR message header information elements over UDP
Each GA-PSR message sent over the UDP-based GA-PSR Transport Channel begins with a 7-octet message header. This message header consists of the following information elements: GA-PSR Message Type, TLLI, and Sequence Number. These IEs are described in the following sub-clauses.
Table 11.1.3.1: GA-PSR (UDP) message header contents
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Value |
Notes |
GA-PSR Message Type |
GA-PSR Message Type |
M |
V |
1 |
|||
TLLI |
TLLI |
M |
V |
4 |
|||
Sequence Number |
Sequence Number |
M |
V |
2 |
|||
Here continues the list of IE’s using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. |
11.1.3.1 GA-PSR Message Type
The GA-PSR Message Type IE is the first octet in the GA-PSR (UDP) message header. Bit 8 of the GA-PSR Message Type value is the most significant bit and bit 1 is the least significant bit.
The following GA-PSR Message Type values are defined:
Table 11.1.3.1.1: GA-PSR Message Type values (UDP)
GA-PSR message name |
GA-PSR Message Type value (decimal) |
GA-PSR UNITDATA |
2 |
GA-PSR-UFC-REQ |
6 |
GA-PSR-DFC-REQ |
7 |
11.1.3.2 Temporary Logical Link Identity (TLLI)
Octets 2 to 5 of the GA-PSR (UDP) message header contain the Temporary Logical Link Identity (TLLI) information element. The TLLI identifies the MS this message was sent by or sent to.
11.1.3.3 Sequence Number
Octets 6 to 7 of the GA-PSR (UDP) message header contain the Sequence Number information element with value in the range of 0 to 65535.
11.1.3a GA-RRC message header information elements over TCP
Each GA-RRC message sent over the TCP-based signalling channel begins with a 4-octet message header. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator, and GA-RRC Message Type. These IEs are described in the following sub-clauses.
Table 11.1.3a.1: GA-RRC (TCP) message header contents
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Value |
Notes |
Length Indicator |
Length Indicator |
M |
V |
2 |
|||
GA-RRC Protocol Discriminator |
Protocol Discriminator |
M |
V |
½ |
0011 |
||
Skip Indicator |
Skip Indicator |
M |
V |
½ |
0000 |
||
GA-RRC Message Type |
GA-RRC Message Type |
M |
V |
1 |
|||
Other IEs as defined in sub-clause 10.3. |
11.1.3a.1 GA-RRC Message Type
The GA-RRC Message Type IE is the fourth octet in the GA-RRC (TCP) message header. Bit 8 of the GA-RRC Message Type value is the most significant bit and bit 1 is the least significant bit.
The following GA-RRC (TCP) Message Type values are defined:
Table 11.1.3a.1.1: GA-RRC Message Type values (TCP)
GA-RRC message name |
GA-RRC Message Type value |
GA-RRC REQUEST |
1 |
GA-RRC REQUEST ACCEPT |
2 |
GA-RRC REQUEST REJECT |
3 |
GA-RRC RELEASE REQUEST |
4 |
GA-RRC RELEASE |
5 |
GA-RRC RELEASE COMPLETE |
6 |
GA-RRC PAGING REQUEST |
7 |
GA-RRC ACTIVATE CHANNEL |
8 |
GA-RRC ACTIVATE CHANNEL ACK |
9 |
GA-RRC ACTIVATE CHANNEL COMPLETE |
10 |
GA-RRC MODIFY CHANNEL |
11 |
GA-RRC MODIFY CHANNEL ACK |
12 |
GA-RRC DEACTIVATE CHANNEL REQUEST |
13 |
GA-RRC DEACTIVATE CHANNEL |
14 |
GA-RRC DEACTIVATE CHANNEL COMPLETE |
15 |
GA-RRC SECURITY MODE COMMAND |
16 |
GA-RRC SECURITY MODE COMPLETE |
17 |
GA-RRC INITIAL DIRECT TRANSFER |
18 |
GA-RRC UPLINK DIRECT TRANSFER |
19 |
GA-RRC DOWNLINK DIRECT TRANSFER |
20 |
GA-RRC RELOCATION INFORMATION |
21 |
GA-RRC RELOCATION COMMAND |
22 |
GA-RRC RELOCATION ACCESS |
23 |
GA-RRC RELOCATION COMPLETE |
24 |
GA-RRC RELOCATION FAILURE |
25 |
GA-RRC RELOCATION REQUEST |
26 |
GA-RRC RELOCATION REQUEST ACK |
27 |
GA-RRC UPLINK QUALITY INDICATION |
28 |
GA-RRC STATUS |
29 |
11.1.3b GA-RRC message header over UDP
Each GA-RRC message sent over the UDP-based Packet Transport Channel begins with a message header that is as defined for the G-PDU message in the GTP-U protocol in [53]. The message header is shown below for information. See [53] for a description of each field.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Version |
PT |
spare |
E |
S |
PN |
octet 1 |
||
Message Type |
octet 2 |
|||||||
Length |
octet 3-4 |
|||||||
TEID |
octet 5-8 |
|||||||
Sequence Number |
octet 9-10 |
|||||||
N-PDU Number |
octet 11 |
|||||||
Next Extension Header Type |
octet 12 |
Figure 11.1.3b.1: GA-RRC (PTC) message header contents
Table 11.1.3b.1: GA-RRC (PTC) message header description
Version (octet 1) The Version field shall be set to value ‘001’. PT, Payload Type (octet 1) The Payload Type field shall be set to value ‘1’. E, Extensions Header Flag (octet 1) The use of the Extensions Header Flag is described in [53]. The MS shall set the E field to value ‘0’ for all messages sent to the GANC and disregard all extension fields if present in messages received from the GANC. S, Sequence Number Flag (octet 1) Bit 2 0 The Sequence Number field is not present or is present but not meaningful 1 The Sequence Number field is present See sub-clause 11.1.3b.2 for the handling of this field. PN, N-PDU Number Flag (octet 1) Bit 1 0 The N-PDU Number field is not present or is present but not meaningful 1 The N-PDU Number field is present The MS shall set PN to value ‘0’ for all messages sent to the GANC. Message Type (octet 2) The GTP-U Message Type field carries the GA-RRC PTC Message Type value as defined in sub-clause 11.1.3b.1. Length (octet 3-4) This field indicates the length in octets of the payload; i.e., the rest of the message following the mandatory part of the header (that is the first 8 octets). The MSB is octet 3 and the LSB is octet 4. TEID, Tunnel Endpoint ID (octet 5-8) This field contains the TEID value that has been assigned to the MS (for downlink messages) or the GANC (for uplink messages) for the PTC to which this message belongs. The format is as defined in sub-clause 11.2.110, "TEID" but with no IEI and no length fields. Sequence Number (octet 9-10) This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the Sequence Number Flag is set to 1. The handling of this field is specified in sub-clause 11.1.3b.2. N-PDU Number (octet 11) This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the N-PDU Number Flag is set to 1. If the Sequence Number field shall be included in messages sent to the GANC, the MS shall fill the N-PDU Number field with the value ‘00000000’ for all messages sent to the GANC and disregard all N-PDU Number fields if present in messages received from the GANC. Next Extension Header Type (octet 11) This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the Extensions Header Flag is set to 1. If the Sequence Number field shall be included in messages sent to the GANC, the MS shall fill the Next Extensions Header Type field with the value ‘00000000’ for all messages sent to the GANC and disregard all extension fields if present in messages received from the GANC. |
11.1.3b.1 GA-RRC PTC Message Type
The GA-RRC PTC Message Type field is the second octet in the GA-RRC (PTC) message header. Bit 8 of the GA-RRC PTC Message Type value is the most significant bit and bit 1 is the least significant bit.
The following GA-RRC PTC message types are defined:
Table 11.1.3a.1.1: Message types for GA-RRC (UDP)
GA-RRC PTC message name |
GA-RRC PTC Message Type value |
GA-RRC PDU |
255 |
11.1.3b.2 GA-RRC Sequence Number Handling
The following describes the use of GA-RRC PDU message sequence numbering assuming sequencing has been activated for the PTC (i.e., Delivery Order is requested in the IE "RAB Configuration" associated with the PTC).
The sending MS shall use 0 for the value of the Sequence Number of the first GA-RRC PDU message in a tunnel, only during the PDP context activation, and shall increment the Sequence Number for each following GA-RRC PDU message. The value shall wrap to zero after 65535.
The receiving MS shall set the content of a counter to zero, only during the PDP context activation. When the receiving MS receives a valid GA-RRC PDU message, it shall increment this counter by one. This counter shall wrap to zero after 65535. It defines the ‘Expected Sequence Number’.
Based on the received and Expected Sequence Number values, the receiving MS may decide whether or not to discard the received GA-RRC PDU message.
The receiving MS shall reorder the incoming T-PDUs in sequence if the Reordering Required flag in the PDP context is set. In this case, if needed, the receiving MS shall take into account a maximum number of valid received frames and a maximum elapsed time to assume that a GA-RRC PDU message was lost.
The sequence numbers allocated by the CN (down-link) and MS (uplink) are kept unchanged irrespective of the number of GA-RRC and GTP tunnels the PDU is transferred over. Therefore, GANC shall use on the Up interface for down-link PDUs the G-PDU sequence number received from the SGSN, and shall use on the Iu interface for uplink PDUs the GA-RRC PDU sequence number received from the MS. In case of SRNS relocation and intersystem change, the GANC shall tunnel PDUs without changing the G-PDU sequence numbers.
11.1.4 Information Element Coding principles
Each information element after the relevant message header is coded using the TLV principle as following:
– The first part of each IE is the Type field identifying the Information Element. The Type field is coded using either 1 or 2 octets. The ext field in octet 1 of the Information Element is the field extension bit and defines if the 2nd Type field octet is included:
– if set to 0, then the Type field consists of one octet with a value less than or equal to 127 (see Figure 11.1.4.1);
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
ext=0 |
Type value |
octet 1 |
Figure 11.1.4.1: Type field structure (coding using one octet)
– if set to 1, then the Type field consists of two octets with a value greater than 127 (see Figure 11.1.4.2).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
ext=1 |
Type value |
octet 1 |
||||||||
Type value (cont.) |
octet 1a |
Figure 11.1.4.2: Type field structure (coding using two octets)
– The second part of each IE is the Length field identifying the length of the Value field of the Information Element. The Length field is coded using either 1 or 2 octets. The ext field in octet 2 of the information element is the field extension bit and defines if the 2nd Length field octet is included:
– if set to 0, then the Length field consists of one octet with a value less than or equal to 127 (see Figure 11.1.4.3);
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
ext=0 |
Length value |
octet 2 |
Figure 11.1.4.3: Length field structure (coding using one octet)
– if set to 1, then the Length field consists of two octets with a value greater than 127 (see Figure 11.1.4.4).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
ext=1 |
Length value |
octet 2 |
||||||||
Length value (cont.) |
octet 2a |
Figure 11.1.4.4: Length field structure (coding using two octets)
– The third part of each IE is the Value field of the Information Element. The length of the Value field depends on the Type field of the IE and is defined in the sub-clauses below 11.2.
When the Type field or the Length 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.
11.1.5 Network Byte order
The Network byte order shall be Big-Endian.
11.2 IE Type and Identifiers
Table 11.2.1: IE type and identifiers for Unlicensed Radio Resources management
IE |
Identifier |
Reference |
---|---|---|
Mobile Identity |
1 |
11.2.1 |
GAN Release Indicator |
2 |
11.2.2 |
Radio Identity |
3 |
11.2.3 |
GERAN Cell Identity |
4 |
11.2.4 |
Location Area Identification |
5 |
11.2.5 |
GERAN/UTRAN coverage Indicator |
6 |
11.2.6 |
GAN Classmark |
7 |
11.2.7 |
Geographical Location |
8 |
11.2.8 |
GANC-SEGW IP Address |
9 |
11.2.9 |
GANC-SEGW Fully Qualified Domain/Host Name |
10 |
11.2.10 |
Redirection Counter |
11 |
11.2.11 |
Discovery Reject Cause |
12 |
11.2.12 |
GAN Cell Description |
13 |
11.2.13 |
GAN Control Channel |
14 |
11.2.14 |
Cell Identifier List |
15 |
11.2.15 |
TU3907 Timer |
16 |
11.2.16 |
GSM RR/UTRAN RRC State |
17 |
11.2.17 |
Routing Area Identification |
18 |
11.2.18 |
GAN Band |
19 |
11.2.19 |
GA-RC/GA-CSR/GA-PSR State |
20 |
11.2.20 |
Register Reject Cause |
21 |
11.2.21 |
TU3906 Timer |
22 |
11.2.22 |
TU3910 Timer |
23 |
11.2.23 |
TU3902 Timer |
24 |
11.2.24 |
L3 Message |
26 |
11.2.26 |
Channel Mode |
27 |
11.2.27 |
Mobile Station Classmark 2 |
28 |
11.2.28 |
RR Cause |
29 |
11.2.29 |
Cipher Mode Setting |
30 |
11.2.30 |
GPRS Resumption |
31 |
11.2.31 |
Handover From GAN Command |
32 |
11.2.32 |
UL Quality Indication |
33 |
11.2.33 |
TLLI |
34 |
11.2.34 |
Packet Flow Identifier |
35 |
11.2.35 |
Suspension Cause |
36 |
11.2.36 |
TU3920 Timer |
37 |
11.2.37 |
QoS |
38 |
11.2.38 |
GA-PSR Cause |
39 |
11.2.39 |
User Data Rate |
40 |
11.2.40 |
Routing Area Code |
41 |
11.2.41 |
AP Location |
42 |
11.2.42 |
TU4001 Timer |
43 |
11.2.43 |
Location Status |
44 |
11.2.44 |
Cipher Response |
45 |
11.2.45 |
Ciphering Command RAND |
46 |
11.2.46 |
Ciphering Command MAC |
47 |
11.2.47 |
Ciphering Key Sequence Number |
48 |
11.2.48 |
SAPI ID |
49 |
11.2.49 |
Establishment Cause |
50 |
11.2.50 |
Channel Needed |
51 |
11.2.51 |
PDU in Error |
52 |
11.2.52 |
Sample Size |
53 |
11.2.53 |
Payload Type |
54 |
11.2.54 |
Multi-rate Configuration |
55 |
11.2.55 |
Mobile Station Classmark 3 |
56 |
11.2.56 |
LLC-PDU |
57 |
11.2.57 |
Location Exclude List indicator |
58 |
11.2.58 |
Reset Indicator |
59 |
11.2.59 |
TU4003 Timer |
60 |
11.2.60 |
AP Service Name |
61 |
11.2.61 |
GAN Service Zone Information |
62 |
11.2.62 |
RTP Redundancy Configuration |
63 |
11.2.63 |
UTRAN Classmark |
64 |
11.2.64 |
Classmark Enquiry Mask |
65 |
11.2.65 |
UTRAN Cell Identifier List |
66 |
11.2.66 |
Serving GANC table indicator |
67 |
11.2.67 |
Registration indicators |
68 |
11.2.68 |
GAN PLMN List |
69 |
11.2.69 |
Required GAN Services |
71 |
11.2.71 |
Broadcast Container |
72 |
11.2.72 |
3G Cell Identity |
73 |
11.2.73 |
MS Radio Identity |
96 |
11.2.3 |
GANC IP Address |
97 |
11.2.9 |
GANC Fully Qualified Domain/ |
98 |
11.2.10 |
IP address for GPRS user data transport |
99 |
11.2.9 |
UDP Port for GPRS user data transport |
100 |
11.2.25 |
GANC TCP port |
103 |
11.2.25 |
RTP UDP port |
104 |
11.2.25 |
RTCP UDP port |
105 |
11.2.25 |
GERAN Received Signal Level List |
106 |
11.2.70 |
UTRAN Received Signal Level List |
107 |
11.2.70b |
PS Handover to GERAN Command |
108 |
11.2.74 |
PS Handover to UTRAN Command |
109 |
11.2.75 |
PS Handover to GERAN PSI |
110 |
11.2.76 |
PS Handover to GERAN SI |
111 |
11.2.77 |
TU4004 Timer |
112 |
11.2.78 |
GAN Mode Indicator |
79 |
11.2.79 |
CN Domain Identity |
80 |
11.2.80 |
GAN Iu Mode Cell Description |
81 |
11.2.81 |
3G UARFCN |
82 |
11.2.82 |
RAB ID |
83 |
11.2.83 |
RAB ID List |
84 |
11.2.84 |
GA-RRC Establishment Cause |
85 |
11.2.85 |
GA-RRC Cause |
86 |
11.2.86 |
GA-RRC Paging Cause |
87 |
11.2.87 |
Intra Domain NAS Node Selector |
88 |
11.2.88 |
CTC Activation List |
89 |
11.2.89 |
CTC Description |
90 |
11.2.90 |
CTC Activation Ack List |
91 |
11.2.91 |
CTC Activation Ack Description |
92 |
11.2.92 |
CTC Modification List |
93 |
11.2.93 |
CTC Modification Ack List |
94 |
11.2.94 |
CTC Modification Ack Description |
95 |
11.2.95 |
PTC Activation List |
115 |
11.2.96 |
PTC Description |
116 |
11.2.97 |
PTC Activation Ack List |
117 |
11.2.98 |
PTC Activation Ack Description |
118 |
11.2.99 |
PTC Modification List |
119 |
11.2.100 |
PTC Modification Ack List |
120 |
11.2.101 |
PTC Modification Ack Description |
121 |
11.2.102 |
RAB Configuration |
122 |
11.2.103 |
Multi-rate Configuration 2 |
123 |
11.2.104 |
Selected Integrity Protection Algorithm |
124 |
11.2.105 |
Selected Encryption Algorithm |
125 |
11.2.106 |
CN Domains to Handover |
126 |
11.2.107 |
3G Security Capability |
74 |
11.2.108 |
NAS Synchronisation Indicator |
75 |
11.2.109 |
GANC TEID |
76 |
11.2.110 |
MS TEID |
77 |
11.2.110 |
UTRAN RRC Message |
78 |
11.2.111 |
SRNS Relocation Info |
127 |
11.2.111 |
MS Radio Access Capability |
128 |
11.2.112 |
Handover Reporting Control |
129 |
11.2.113 |
Tracking Area Identity |
130 |
11.2.114 |
E-UTRAN Cell Identity |
131 |
11.2.115 |
E-UTRAN Camping Indicator |
132 |
11.2.116 |
Bandwidth-efficient Mode Indicator |
133 |
11.2.117 |
11.2.1 Mobile Identity
The purpose of the Mobile Identity information element is to provide either the international mobile subscriber identity, IMSI, the temporary mobile subscriber identity, TMSI/P-TMSI, the international mobile equipment identity, IMEI or the international mobile equipment identity together with the software version number, IMEISV.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Mobile Identity IEI |
octet 1 |
||||||||
Length of mobile identity contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8] not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.1.1: Mobile Identity information element
11.2.2 GAN Release Indicator
This information element is used to indicate the GAN Release supported.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
GAN Release Indicator IEI |
octet 1 |
|||||||||
Length of GAN Release Indicator IE contents |
octet 2 |
|||||||||
spare |
URI |
octet 3 |
Figure 11.2.2.1: GAN Release Indicator information element
Table 11.2.2.1: GAN Release Indicator information element
URI, GAN Release Indicator (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
1 |
Release 1 (i.e. 3GPP Release-6) |
0 |
1 |
0 |
Release 2 (i.e. 3GPP Release-7) |
0 |
1 |
1 |
Release 3 (i.e. 3GPP Release-8) |
All other values are reserved. |
11.2.3 Access Identity
The Access Identity IE is used for transmission of identifiers of the Access Technologies e.g. the Bluetooth Device Address (BD_ADDR) or WLAN MAC Address.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Access Identity IEI |
octet 1 |
|||||||||
Length of Access Identity contents |
octet 2 |
|||||||||
Spare |
Type of identity |
octet 3 |
||||||||
Access Identity MSB value |
octet 4 |
|||||||||
Access Identity LSB value |
octet 9 |
Figure 11.2.3.1: Access Identity information element
Table 11.2.3.1: Access Identity information element
Type of Identity (octet 3) Bits |
||||
4 |
3 |
2 |
1 |
|
0 |
0 |
0 |
0 |
IEEE MAC-address format |
0 |
0 |
0 |
1 |
|
to |
||||
1 |
1 |
1 |
1 |
All other values are for future use. |
11.2.4 GERAN Cell Identity
The purpose of the Cell Identity information element is to identify a cell within a location area.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
GERAN Cell Identity IEI |
octet 1 |
||||||||
Length of GERAN Cell Identity IE contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8] not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.4.1 GERAN Cell Identity information element
11.2.5 Location Area Identification
The purpose of the Location Area Identification information element is to provide an unambiguous identification of location areas within the area covered by the GSM system.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Location Area Identification IEI |
octet 1 |
||||||||
Length of Location Area Identification IE contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8] not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.5.1: Location Area Identification information element
11.2.6 GERAN/UTRAN coverage Indicator
This information element is used to indicate the presence of GERAN/UTRAN coverage in the current MS location.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
GERAN/UTRAN coverage Indicator IEI |
octet 1 |
|||||||||
Length of GERAN/UTRAN coverage Identity contents |
octet 2 |
|||||||||
GCI |
octet 3 |
Figure 11.2.6.1 GERAN/UTRAN coverage Indicator information element
Table 11.2.6.1: GERAN/UTRAN coverage Indicator information element
GCI, GERAN/UTRAN coverage Indicator (octet 3) 0 Normal Service in the GERAN/UTRAN 1 Limited Service in the GERAN/UTRAN 2 MS has not found GERAN/UTRAN coverage (LAI information taken from SIM, if available). This value shall be used if the MS is camped on a E-UTRAN cell. 3 MS has found GERAN/UTRAN coverage, service state unknown 4-255 All other values are for future use |
11.2.7 GAN Classmark
The purpose of the GAN Classmark information element is to provide the network with information concerning aspects of both the cellular and generic access interfaces, as well as the support for RTP redundancy of the mobile station equipment.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GAN Classmark IEI |
octet 1 |
|||||||
Length of GAN Classmark IE contents |
octet 2 |
|||||||
spare |
UC |
GC |
TGA |
octet 3 |
||||
spare |
BMSI |
GMSI |
PS HO |
RRS |
octet 4 |
Figure 11.2.7.1: GAN Classmark information element
Table 11.2.7.1: GAN Classmark information element
TGA, Type of Generic Access (octet 3) This field is used to indicate the current Generic Access type used by the mobile station to access the GAN. Bit 4 3 2 1 0 0 0 0 no radio 0 0 0 1 Bluetooth 0 0 1 0 WLAN 802.11 1 1 1 1 unspecified All other values are reserved in Release 1. |
GC, GERAN Capable (octet 3) Bit 5 0 The MS is not GERAN capable. 1 The MS is GERAN capable. |
UC, UTRAN Capable (octet 3) Bit 6 0 The MS is not UTRAN capable. 1 The MS is UTRAN capable. |
RRS, RTP Redundancy Support (octet 4) Bit1 0 RTP Redundancy not supported 1 RTP Redundancy supported |
PS HO, PS Handover Capable (octet 4) Bit 2 0 The MS does not support PS handover to/from GAN A/Gb mode. 1 The MS supports PS handover to/from GAN A/Gb mode. |
GMSI, GAN Mode Support Indicator (octet 4) Bits 4 3 0 0 Unspecified 0 1 The MS supports GAN A/Gb mode only 1 0 The MS supports GAN Iu mode only 1 1 The MS supports GAN A/Gb mode and GAN Iu mode |
BMSI, Bandwidth-efficient Mode Support Indicator (octet 4) Bit 5 0 The MS does not support RFC 4867 [48] bandwidth-efficient mode. 1 The MS supports RFC 4867 [48] bandwidth-efficient mode. |
11.2.8 Geographical Location
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 |
||
Geographical Location Indicator IEI |
octet 1 |
||||||||
Length of Geographical Location value contents |
octet 2, 2a |
||||||||
Location estimate |
octet 3 |
Figure 11.2.8.1: Geographical Location information element
The Location Estimate field is composed of 1 or more octets with an internal structure according to section 7 in [5].
11.2.9 IP Address
The IP Address information element contains one IP address.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
IP address IEI |
octet 1 |
||||||||
Length of IP address IE contents |
octet 2, 2a |
||||||||
IP Address type |
octet 3 |
||||||||
Address information MSB |
octet 4 |
||||||||
Address information LSB |
octet n |
Figure 11.2.9.1: IP address information element
Table 11.2.9.1: IP address information element
IP address type number value (octet 3) All other values shall be interpreted as Ipv4 address |
If PDP type number indicates Ipv4, the Address information in octet 4 to octet 7 contains the Ipv4 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 7 the least significant bit .
If PDP type number indicates Ipv6, the Address information in octet 4 to octet 19 contains the Ipv6 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 19 the least significant bit.
11.2.10 Fully Qualified Domain/Host Name (FQDN)
The Fully Qualified Domain/Host Name (FQDN) information element contains the name of a network element (i.e. SEGW or a GANC). The information element is coded in string format.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FQDN IEI |
octet 1 |
||||||||
Length of FQDN IE contents |
octet 2, 2a |
||||||||
FQDN 1st character |
octet 3 |
||||||||
FQDN last character |
octet n |
Figure 11.2.10.1: FQDN information element
Table 11.2.10.1: FQDN information element
FQDN, Fully Qualified Domain/Host Name value (octet 3 to octet n) The FQDN is coded as a string. This means that the 1st character of the string is coded in octet 3 and the last character of the string is coded in the last octet of this IE (octet n). |
11.2.11 Redirection Counter
The purpose of this information element is to indicate to the GANC the number of times the MS has been redirect and still has not obtained service.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Redirection Counter IEI |
octet 1 |
||||||||
Length of Redirection Counter contents |
octet 2 |
||||||||
Redirection Counter value |
octet 3 |
Figure 11.2.11.1: Redirection Counter information element
Table 11.2.11.1: Redirection Counter information element
Redirection Counter value (octet 3 ) In the Redirection Counter value field bit 8 of octet 3 is the most significant bit The value is given in number redirections The Redirection Counter value consists of 1 octets. |
11.2.12 Discovery Reject Cause
The Discovery reject Cause information element contains information to the MS about the reason for a Discovery Reject. The MS shall act according to the cause value received.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Discovery Reject Cause IEI |
octet 1 |
||||||||
Length of Discovery Reject Cause IE contents |
octet 2 |
||||||||
Discovery Reject Cause Value |
octet 3 |
Figure 11.2.12.1: Discovery Reject Cause information element
Table 11.2.12.1: Discovery Reject Cause information element
Discovery Reject Cause (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
Network Congestion |
0 |
0 |
1 |
Unspecified |
0 |
1 |
0 |
IMSI not allowed |
1 |
0 |
0 |
|
to |
|||
1 |
1 |
1 |
Reserved for future use. |
11.2.13 GAN Cell Description
The purpose of the GAN Cell Description information element is to provide a minimum description of a GAN A/Gb mode cell, e.g. to identify the GAN A/Gb mode cell in order to be handed over from GERAN/UTRAN.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
GAN Cell Description IEI |
octet 1 |
||||||||
Length of GAN Cell Description value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], Cell Description IE, not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.13.1: GAN Cell Description information element
11.2.14 GAN Control Channel Description
The purpose of the Control Channel Description information element is to provide a variety of information about the GAN service.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GAN Control Channel Description IEI |
octet 1 |
|||||||
Length of GAN Control Channel Description contents |
octet 2 |
|||||||
MSCR |
ATT |
DTM |
GPRS |
NMO |
ECMC |
spare |
octet 3 |
|
T3212 timeout value |
octet 4 |
|||||||
RAC |
octet 5 |
|||||||
spare |
PS HO |
3GECS |
PFCFM |
RE |
ECMP |
SGSNR |
octet 6 |
|
AC C15 |
AC C14 |
AC C13 |
AC C12 |
AC C11 |
AC C10 |
AC C09 |
AC C08 |
octet 7 |
AC C07 |
AC C06 |
AC C05 |
AC C04 |
AC C03 |
AC C02 |
AC C01 |
AC C00 |
octet 8 |
Figure 11.2.14.1: GAN Control Channel Description information element
Table 11.2.14.1: GAN Control Channel Description information element
ECMC, Early Classmark Sending Control (octet 3) Bit 2 0 Early Classmark Sending is allowed |
NMO, Network Mode of Operation (octet 3) Bit 4 3 0 0 Network Mode of Operation I 0 1 Network Mode of Operation II 1 0 Network Mode of Operation III (this value is not valid in GAN Iu mode) 1 1 Reserved |
GPRS, GPRS Availability (octet 3) Bit 5 0 GPRS available |
DTM, Dual Transfer Mode of Operation by network (octet 3) Bit 6 0 Network does not support dual transfer mode |
ATT, Attach-detach allowed (octet 3) Bit 7 0 MSs in the cell are not allowed to apply IMSI attach and detach procedure. |
MSCR, MSC Release (octet 3) Bit 8 0 MSC is Release ’98 or older This field shall be disregarded in GAN Iu mode. |
T3212 timeout value (octet 4) The T3212 timeout value field is coded as the binary representation of the timeout value for periodic updating in decihours. Range: 1 to 255 The value 0 is used for infinite timeout value i.e. periodic updating shall not be used within the cell. |
RAC, Routing Area Code (octet 5) |
SGSNR, SGSN Release (octet 6) Bit 1 0 SGSN is Release ’98 or older This field shall be disregarded in GAN Iu mode. |
ECMP, Emergency Call Mode Preference (octet 6) Bit 2 0 GERAN/UTRAN is preferred for Emergency calls |
RE, Call re-establishment allowed (octet 6) Bit 3 0 Call Re-establishment allowed in the cell When call re-establishment is allowed, the mobile station may initiate call re-establishment if rove-in follows the RR/RRC connection failure in GSM/UMTS. |
PFCFM, PFC_FEATURE_MODE (octet 6) 3GECS, 3G Early Classmark Sending Restriction (octet 6) Bit 5 0 UTRAN classmark change message shall note be sent with the Early classmark sending 1 The sending of UTRAN Classmark Sending messages is controlled by the Early Classmark Sending Control parameter This field shall be disregarded in GAN Iu mode. PS HO, PS Handover indicator (octet 6) Bit 6 0 The network does not support PS handover between GERAN/UTRAN mode and GAN A/Gb mode. 1 The network supports PS handover between GERAN/UTRAN mode and GAN A/Gb mode. This field shall be disregarded in GAN Iu mode. |
AC CN, Access Control Class N (octet 7 and octet 8) These fields are specified and described in 3GPP TS 44.018 and 3GPP TS 22.011. |
11.2.15 Cell Identifier List
The Cell Identifier List information element is used to transfer multiple Cell Global Identifications in GAN.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
GAN Cell Identifier List IEI |
octet 1 |
||||||||
Length of GAN Cell Identifier List value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [16], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.15.1: Cell Identifier List information element
NOTE: Cell identification discriminator "The whole Cell Global Identification, CGI" as defined in [16] shall be used.
11.2.16 TU3907 Timer
The purpose of this information element is to indicate to the MS the minimum period of time it should wait before attempting Registration at the current GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU3907 Timer IEI |
octet 1 |
||||||||
Length of TU3907 Timer IE contents |
octet 2 |
||||||||
TU3907 Timer value MSB |
octet 3 |
||||||||
TU3907Timer value LSB |
octet 4 |
Figure 11.2.16.1: TU3907 Timer information element
Table 11.2.16.1: TU3907 Timer information element
TU3907 Timer value (octet 3 and 4) In the TU3907 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. The value is given in number of seconds. The TU3907 Timer value consists of 2 octets. |
11.2.17 GSM RR/UTRAN RRC State
This information element is used to indicate the state of the GSM RR or UTRAN RRC entity when the MS is registering for GAN service. If GSM-RR is the current serving RR entity, information about GSM RR shall be included and if UTRAN-RRC is the current serving RR entity, information about UTRAN RRC shall be included.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
GSM RR/UTRAN RRC State IEI |
octet 1 |
|||||||||
Length of GSM RR/ UTRAN RRC State contents |
octet 2 |
|||||||||
spare |
GRS |
octet 3 |
Figure 11.2.17.1 GSM RR/UTRAN RRC State information element
Table 11.2.17.1: GSM RR/UTRAN RRC State information element
GRS, GSM RR/UTRAN RRC State (octet 3) Bits 1-3 0 0 0 GSM RR is in IDLE state. 0 1 0 UTRAN RRC is in IDLE STATE 0 1 1 UTRAN RRC is in CELL_DCH STATE 1 0 0 UTRAN RRC is in CELL_FACH STATE 1 1 1 Unknown All other values are reserved for future use. |
11.2.18 Routing Area Identification
The purpose of the routing area identification information element is to provide an unambiguous identification of routing areas within the GPRS coverage area.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Routing Area Identification IEI |
octet 1 |
||||||||
Length of Routing Area Identification contents |
octet 2 |
||||||||
The rest of the IE is coded as in [8] not including IEI and length, if present. |
octet 3 …. octet 8 |
Figure 11.2.18.1: Routing Area Identification information element
11.2.19 GAN Band
The GAN Band information element is used to indicate to the mobile station the GSM Band that is associated with the GANC. The mobile station uses this information to construct the MS Classmark 2 information element. The GAN Band is applicable in GAN A/Gb mode only.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
GAN Band IEI |
octet 1 |
|||||||||
Length of GAN Band contents |
octet 2 |
|||||||||
spare |
GAN Band |
octet 3 |
Figure 11.2.19.1: GAN Band information element
Table 11.2.19.1: GAN Band information element
GAN Band (4 bit field) Bits 4 – 1 0 0 0 0 E-GSM is supported 0 0 0 1 P-GSM is supported 0 0 1 0 GSM 1800 is supported 0 0 1 1 GSM 450 is supported 0 1 0 0 GSM 480 is supported 0 1 0 1 GSM 850 is supported 0 1 1 0 GSM 1900 is supported 0 1 1 1 GSM 700 is supported All other values are reserved for future use and shall not be interpreted as an error. |
11.2.20 GAN State
This information element is used to indicate the state of the GAN protocol sub-layer entities in the MS to the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
GAN State IEI |
octet 1 |
|||||||||
Length of GAN State contents |
octet 2 |
|||||||||
spare |
GA-RRC-PS |
GA-RRC-CS |
UPS |
URS |
octet 3 |
Figure 11.2.20.1 GAN State information element
Table 11.2.20.1: GAN State information element
URS, GA-RC/GA-CSR State (octet 3) Bits 2-1 2 1 0 0 GA-CSR is in GA-CSR-IDLE state. 0 1 GA-CSR is in GA-CSR-DEDICATED state. 1 0 GA-RC is in GA-RC-REGISTERED state while in GERAN/UTRAN mode. UPS, GA-PSR State (octet 3) Bit 3 0 GA-PSR is in GA-PSR-STANDBY state. 1 GA-PSR is in GA-PSR-ACTIVE state. GA-RRC-CS, GA-RRC (CS) State (octet 3) Bit 4 0 GA-RRC (CS) is in GA-RRC-IDLE state. 1 GA-RRC (CS) is in GA-RRC-CONNECTED state. GA-RRC-PS, GA-RRC (PS) State (octet 3) Bit 5 0 GA-RRC (PS) is in GA-RRC-IDLE state. 1 GA-RRC (PS) is in GA-RRC-CONNECTED state. |
11.2.21 Register Reject Cause
This information element contains the reason for Register reject or deregistration.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Register Reject Cause IEI |
octet 1 |
||||||||
Length of Register Reject Cause IE contents |
octet 2 |
||||||||
RRC |
octet 3 |
Figure 11.2.21.1: Register Reject Cause information element
Table 11.2.21.1: Register Reject Cause information element
Register Reject Cause (octet 3) |
|
0 |
Network Congestion |
1 |
AP not allowed |
2 |
Location not allowed |
3 |
Invalid GANC |
4 |
Geo Location not known |
5 |
IMSI not allowed |
6 |
Unspecified |
7 |
GANC-SEGW certificate not valid |
8 |
EAP_SIM authentication failed |
9 |
TCP establishment failed |
10 |
Redirection |
11 |
EAP-AKA Authentication failed |
12 to 255 |
Reserved for future use. |
11.2.22 TU3906 Timer
The TU3906 Timer information element contains the value for the GA-RC Keep Alive mechanism, as described in section 5.5.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU3906 Timer IEI |
octet 1 |
||||||||
Length of TU3906 Timer IE contents |
octet 2 |
||||||||
TU3906 Timer value MSB |
octet 3 |
||||||||
TU3906 Timer value LSB |
octet 4 |
Figure 11.2.22.1: TU3906 Timer information element
Table 11.2.22.1: TU3906 Timer information element
TU3906 Timer value (octet 3 and 4) In the TU3906 Timer value field bit 8 of octet 3 is the most significant bit and bit 1of octet 4 the least significant bit. The value is given in number of seconds. The TU3906 Timer value consists of 2 octets. |
11.2.23 TU3910 Timer
When the MS roves out, it shall start timer TU3910 and shall not rove in until this timer has expired, unless the MS has detected loss of GERAN coverage.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU3910 Timer IEI |
octet 1 |
||||||||
Length of TU3910 Timer IE contents |
octet 2 |
||||||||
TU3910 Timer value MSB |
octet 3 |
||||||||
TU3910 Timer value LSB |
octet 4 |
Figure 11.2.23.1: TU3910 Timer information element
Table 11.2.23.1: TU3910 Timer information element
TU3910 Timer (octet 3 and 4) In the TU3910 Timer value field bit 8 of octet 3 is the most significant bit and bit 1of octet 4 the least significant bit. The value is given in number of seconds. The TU3910 value consists of 2 octets. |
11.2.24 TU3902 Timer
The purpose of this information element is to indicate to the MS the minimum period of time it should wait before attempting the Discovery procedure again.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU3902 Timer IEI |
octet 1 |
||||||||
Length of TU3902 Timer IE contents |
octet 2 |
||||||||
TU3902 Timer value MSB |
octet 3 |
||||||||
TU3902 Timer value LSB |
octet 4 |
Figure 11.2.24.1: TU3902 Timer information element
Table 11.2.24.1: TU3902 Timer information element
TU3902 Timer value (octet 3 and 4) In the TU3902 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. The value is given in number of seconds. The TU3902 Timer value consists of 2 octets. |
11.2.25 Communication Port Identity
The Communication Port Identity information element is used to identify the TCP or UDP port for the connection.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Communication Port Identity IEI |
octet 1 |
||||||||
Length of Communication Port Identity IE contents |
octet 2 |
||||||||
Communication Port MSB value |
octet 3 |
||||||||
Communication Port LSB value |
octet 4 |
Figure 11.2.25.1: Communication Port information element
Even though it is only recommended in [35], RTP shall use an even destination UDP port number and the corresponding RTCP stream shall use the next higher (odd) destination UDP port number. E.g. UDP ports 49170 and 49171 form one RTP/RTCP UDP port pair.
11.2.26 L3 Message
The L3 Message information element contains the upper layer message to be transported using the GA-CSR protocol or the GA-RRC protocol between the MS and the core network.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
L3 Message IEI |
octet 1 |
||||||||
Length of L3 Message IE contents |
octet 2, 2a |
||||||||
L3 Message contents, 1st octet |
octet 3 |
||||||||
L3 Message contents, last octet |
octet n |
Figure 11.2.26.1: L3 Message information element
11.2.27 Channel Mode
The Channel Mode information element gives information of the mode on coding/decoding and transcoding. The exact mode is determined by the contents of this IE and the channel type.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Channel Mode IEI |
octet 1 |
||||||||
Length of Channel Mode IE contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.27.1: Channel Mode information element
NOTE 1: Support for AMR FR codec, as specified in 3GPP TS 26.071 [7], is mandatory when operating in GAN A/Gb mode, with support for other codecs being optional.
11.2.28 Mobile Station Classmark 2
The purpose of the Mobile Station Classmark 2 information element is to provide the network with information concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Mobile station classmark 2 IEI |
octet 1 |
||||||||
Length of mobile station classmark 2 contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.28.1: Mobile Station Classmark 2 information element
11.2.29 RR Cause
The purpose of the RR Cause information element is to provide the reason for release or the reason for completion of an assignment or handover.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
RR Cause IEI |
octet 1 |
||||||||
Length of RR Cause contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.29.1: RR Cause information element
11.2.30 Cipher Mode Setting
The purpose of the Cipher Mode Setting information element is to indicate whether stream ciphering shall be started or not and if it is to be started, which algorithm to use. It is not used for ciphering when the MS is in GAN A/Gb mode or GAN Iu mode, but after handover from GAN A/Gb mode in the target RAT.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
Cipher Mode Setting IEI |
octet 1 |
||||||||||
Length of Cipher Mode Setting IE contents |
octet 2 |
||||||||||
spare |
algorithm identifier |
SC |
octet 3 |
Figure 11.2.30.1: Cipher Mode Setting information element
NOTE: The coding of fields SC and algorithm identifier is defined in [12] as part of the Cipher Mode Setting IE.
11.2.31 GPRS Resumption
The purpose of the GPRS Resumption information element is to indicate whether the network has successfully resumed GPRS services or not.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
GPRS Resumption IEI |
octet 1 |
||||||||
Length of GPRS Resumption contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.31.1: GPRS Resumption information element
11.2.32 Handover From GAN Command
The purpose of Handover From GAN Command information element is to provide information to the MS of handover from GAN. The Handover From GAN Command information element contains all information needed by the MS for handover from GAN.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Handover from GAN Command IEI |
octet 1 |
||||||||
Length of Handover from GAN Command value contents |
octet 2, 2a |
||||||||
If the target RAT is GERAN, the rest of the IE is coded as HANDOVER COMMAND message in [12]. If the target RAT is UTRAN, the rest of the IE is coded as INTER SYSTEM TO UTRAN HANDOVER COMMAND message in [12]. |
octet 3 …. octet n |
Figure 11.2.32.1: Handover From GAN Command information element
11.2.33 UL Quality Indication
This information element provides an indication to the MS that the GAN has detected insufficient signal quality on the uplink or is unable to support the service on the broadband network, thereby requiring the MS to trigger a Handover by providing the necessary information regarding the potential target cells in the other RAT. Handover from GAN can be triggered by GAN only if the MS has indicated presence of GSM coverage previously in the Register or Register Update messages.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
UL Quality Indication IEI |
octet 1 |
|||||||||
Length of UL Quality Indication contents |
octet 2 |
|||||||||
spare |
ULQI |
octet 3 |
Figure 11.2.33.1: UL Quality Indication information element
Table 11.2.33.1: UL Quality Indication information element
ULQI, UL Quality Indication (octet 3) Bits |
||||
4 |
3 |
2 |
1 |
|
0 |
0 |
0 |
0 |
Quality ok |
0 |
0 |
0 |
1 |
Radio problem |
0 |
0 |
1 |
0 |
Network problem |
0 |
1 |
0 |
0 |
Undetermined problem |
Other values are reserved for future use. |
11.2.34 TLLI
The purpose of the TLLI information element is to provide the Temporary Logical Link Identifier.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TLLI IEI |
octet 1 |
||||||||
Length of TLLI value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.34.1: TLLI information element
11.2.35 Packet Flow Identifier
The Packet Flow Identifier (PFI) information element indicates the Packet Flow Identifier for a Packet Flow Context.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Packet Flow Identifier IEI |
octet 1 |
||||||||
Length of Packet Flow Identifier value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.35.1: Packet Flow Identifier information element
11.2.36 Suspension Cause
The purpose of the Suspension Cause information element is to provide the reason for the GPRS suspension.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Suspension Cause IEI |
octet 1 |
||||||||
Length of Suspension Cause value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.36.1: Suspension Cause information element
11.2.37 TU3920 Timer
The purpose of this information element is to indicate to the MS the maximum period of time it should wait before aborting the Handover to GAN (A/Gb mode or Iu mode) procedure.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU3920 Timer IEI |
octet 1 |
||||||||
Length of TU3920 Timer IE contents |
octet 2 |
||||||||
TU3920 Timer value MSB |
octet 3 |
||||||||
TU3920 Timer value LSB |
octet 4 |
Figure 11.2.37.1: TU3920 Timer information element
Table 11.2. 37.1: TU3920 Timer information element
TU3920 Timer value (octet 3 and 4) In the TU3920 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. The value is given in number of hundreds of milliseconds. The TU3920 Timer value consists of 2 octets. |
11.2.38 QoS
This information element indicates the QoS Profile associated with a PDU.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||||
QoS IEI |
octet 1 |
|||||||||||
Length of QoS value contents |
octet 2 |
|||||||||||
spare |
RLC_MODE |
RADIO_PRIORITY |
PEAK_THROUGHPUT_CLASS |
octet 3 |
Figure 11.2.38.1: QoS information element
Table 11.2.38.1: QoS information element
PEAK_THROUGHPUT_CLASS (octet 3, bits 1-4) This field is coded as PEAK_THROUGHPUT_CLASS field in the Channel Request Description information element specified in [45] RADIO_PRIORITY (octet 3, bits 5-6) This field is coded as RADIO_PRIORITY field in the Channel Request Description information element specified in [45] RLC_MODE (octet 3, bit 7) This field is coded as RLC_MODE field in the Channel Request Description information element specified in [45] . |
11.2.39 GA-PSR Cause
This information element indicates the status related to GAN specific signalling procedures.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
GA-PSR Cause IEI |
octet 1 |
||||||||
Length of GA-PSR Cause value contents |
octet 2 |
||||||||
GA-PSR Cause value |
octet 3 |
Figure 11.2.39.1: GA-PSR Cause information element
Table 11.2.39.1 GA-PSR Cause value
GA-PSR Cause (octet 3) Value 0 "success" 2 "no available resources" 3 "GANC failure" 4 "not authorized for data service" 5 "message type non existent or not implemented" 6 "message type not compatible with the protocol state" 7 "invalid mandatory information" 8 "syntactically incorrect message" 9 "GPRS suspended" 10 "normal deactivation" 12 "conditional IE error" 13 "semantically incorrect message" 14 "PS handover failure – incorrect handover command" 15 "PS handover failure – target RAT access failure 16 "PS handover failure – missing SI/PSI information" 17 "PS handover failure – no uplink TBF allocation" All other values are for future use. |
11.2.40 User Data Rate
This information element indicates the User Data Rate used in flow control procedures:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
User Data Rate IEI |
octet 1 |
||||||||
Length of User Data Rate value contents |
octet 2 |
||||||||
R Value (MSB) |
octet 3 |
||||||||
octet 4 |
|||||||||
R Value (LSB) |
octet 5 |
Figure 11.2.40.1: User Data Rate IE
Table 11.2.40.1: User Data Rate IE
R value (octets 3, 4 and 5) In the R value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 5 the least significant bit. The R field is the binary encoding of the rate information expressed in 100 bits/sec increments, starting from 0 x 100 bits/sec until 16777215 x 100 bits/sec (1.6 Gbps). |
11.2.41 Routing Area Code
The purpose of the Routing Area Code IE is to provide an unambiguous identification of routing areas within a location area.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Routing Area Code IEI |
octet 1 |
||||||||
Length of the Routing Area Code value contents |
octet 2 |
||||||||
The rest of the IE is coded as in [3] not including IEI and length, if present. |
octet 3 |
Figure 11.2.41.1: Routing Area Code information element
11.2.42 AP Location
The AP Location information element is to indicate the location of the MS or AP to the network.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
AP Location IEI |
octet 1 |
||||||||
Length of AP Location contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [25], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.42.1: AP Location information element
11.2.43 TU4001 Timer
The purpose of this information element is to indicate to the MS the minimum period of time it should wait before deactivating an idle GAN A/Gb mode GA-PSR Transport Channel or GAN Iu mode Packet Transport Channel.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU4001 Timer IEI |
octet 1 |
||||||||
Length of TU4001 Timer IE contents |
octet 2 |
||||||||
TU4001 Timer value MSB |
octet 3 |
||||||||
TU4001 Timer value LSB |
octet 4 |
Figure 11.2.43.1: TU4001 Timer information element
Table 11.2.43.1: TU4001 Timer information element
TU4001 Timer value (octet 3 and 4) In the TU4001 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. The value is given in number of seconds. The TU4001Timer value consists of 2 octets. |
11.2.44 Location Status
This information element indicates whether the GANC is able to identify the location for the specific MS. Based on network or operator policy, the network may accept a Registration Request from a MS, even if the location of the MS (or AP) is not known in the network. This IE may be used by the MS to provide an indication to the user as to whether the MS’s location is known.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Location Status IEI |
octet 1 |
|||||||||
Length of Location Status value contents |
octet 2 |
|||||||||
spare |
LS |
octet 3 |
Figure 11.2.44.1 Location Status information element
Table 11.2.44.1: Location Status information element
LS, Location Status (octet 3) Bit 2 1 0 0 MS location known 0 1 MS location unknown All other value are for future use. |
11.2.45 Cipher Response
The purpose of the Cipher Response information element is to indicate to the mobile station which information the mobile station has to include in the GA-CSR CIPHERING MODE COMPLETE message.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Cipher Response IEI |
octet 1 |
|||||||||
Length of Cipher Response contents |
octet 2 |
|||||||||
spare |
CR |
octet 3 |
Figure 11.2.45.1: Cipher Response information element
Table 11.2.45.1: Cipher Response information element
CR Cipher Response (octet 3) Bit 1 0 IMEISV shall not be included 1 IMEISV shall be included |
11.2.46 Ciphering Command RAND
The Ciphering Command RAND information element contains the random number to be used for computing the MAC by the MS, to authenticate that the MS has the correct key Kc.
Ciphering Command RAND IEI |
octet 1 |
Length of Ciphering Command RAND contents |
octet 2 |
Ciphering Command RAND value part |
octet 3 …. octet 18 |
Figure 11.2.46.1: Ciphering Command RAND information element
The GANC generates the random number using the same pseudo-random function as first cryptographic suite as defined in the profile for IKEv2 in [37].
11.2.47 Ciphering Command MAC
The Ciphering Command MAC information element contains the Message Authentication Code computed by the MS, to authenticate that the MS has the correct key Kc.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Ciphering Command MAC IEI |
octet 1 |
||||||||
Length of Ciphering Command MAC contents |
octet 2 |
||||||||
Ciphering Command MAC value part |
octet 3 …. octet 14 |
Figure 11.2.47.1: Ciphering Command MAC information element
The MAC is computed as defined in sub-clause 7.9.2.
11.2.48 Ciphering Key Sequence Number
The purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to identify the ciphering key Kc which is stored in the mobile station without invoking the authentication procedure.
The ciphering key sequence number is allocated by the network and sent with the AUTHENTICATION REQUEST message to the mobile station where it is stored together with the calculated ciphering key Kc.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Ciphering Key Sequence IEI |
octet 1 |
|||||||||
Length of Ciphering Key Sequence IE contents |
octet 2 |
|||||||||
spare |
Key sequence |
octet 3 |
Figure 11.2.48.1: Ciphering Key Sequence Number information element
Table 11.2.48.1: Ciphering Key Sequence Number information element
Key sequence (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
|
through |
Possible values for the ciphering key |
||
1 |
1 |
0 |
sequence number |
1 |
1 |
1 |
No key is available (MS to network); |
Reserved (network to MS) |
11.2.49 SAPI ID
The SAPI ID IE is used by the MS to indicate the SAPI value for the upper layer message.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
SAPI ID IEI |
octet 1 |
|||||||||
Length of SAPI ID IE contents |
octet 2 |
|||||||||
spare |
SAPI ID |
octet 3 |
Figure 11.2.49.1: SAPI ID information element
Table 11.2.49.1: SAPI ID information element
SAPI ID, SAPI Identifier (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
SAPI 0 (all other except SMS) |
0 |
1 |
1 |
SAPI 3 (SMS) |
All other values are undefined in Release 1. |
11.2.50 Establishment Cause
The Establishment Cause IE is used by the MS the indicate the type of the transaction being initiated to the network.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Establishment Cause IEI |
octet 1 |
||||||||
Length of Establishment Cause IE contents |
octet 2 |
||||||||
Establishment Cause |
octet 3 |
Figure 11.2.50.1: Establishment Cause information element
Table 11.2.50.1: Establishment Cause information element
Establishment Cause (octet 3) Bits 8 … 1 1010 0000 Emergency 1100 0000 Call re-establishment 0000 0000 Location Update 0001 0000 Other SDCCH procedures including IMSI Detach, SMS, SS, paging response // note: Paging response for "SDCCH needed" is using codepoint "0001 0000" 0010 0000 Paging response (TCH/F needed) 0011 0000 Paging response (TCH/F or TCH/H needed) 1000 0000 Paging response ("any channel" needed) 0100 0000 Originating speech call from dual-rate mobile station when TCH/H is sufficient 0101 0000 Originating data call from dual-rate mobile station when TCH/H is sufficient 1110 0000 Originating speech call and TCH/F is needed 1111 0000 Originating data call and TCH/F is needed All other values are undefined in Release 1. |
11.2.51 Channel Needed
The Channel Needed IE is equivalent to the Channel Needed IE specified in [12] and is coded as per following definition:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Channel Needed IEI |
octet 1 |
|||||||||
Length of Channel Needed IE contents |
octet 2 |
|||||||||
spare |
CHANNEL |
octet 3 |
Figure 11.2.51.1: Channel Needed information element
Table 11.2.51.1: Channel Needed information element
CHANNEL (octet 3) Bits 2 1 0 0 Any channel. 0 1 SDCCH. 1 0 TCH/F (Full rate). 1 1 TCH/H or TCH/F (Dual rate). |
11.2.52 PDU in Error
The PDU in Error IE contains a faulty message returned to the sender of the message.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
PDU in Error IEI |
octet 1 |
||||||||
Length of PDU in Error contents |
octet 2, 2a |
||||||||
PDU in Error, 1st octet |
octet 3 |
||||||||
PDU in Error, last octet |
octet n |
Figure 11.2.52.1: PDU in Error information element
NOTE: If the faulty message included in the PDU in Error IE is larger than 255 octets then only the first 255 octets of the message are to be included and the Length of the PDU in Error field shall indicate that 255 octets are included.
11.2.53 Sample Size
The Sample Size IE is used by the network to indicate the minimum size of the CS payload frames to be included in each RTP/UDP packet. It is also used by the MS to indicate to the network the sample size used by the MS and to be applied by the network in the downlink.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Sample Size IEI |
octet 1 |
||||||||
Length of Sample Size IE contents |
octet 2 |
||||||||
Sample Size |
octet 3 |
Figure 11.2.53.1: Sample Size information element
Table 11.2.53.1: Sample Size information element
Sample Size (octet 3) |
|
20 |
20 ms of CS payload included in each RTP/UDP packet |
40 |
40 ms of CS payload included in each RTP/UDP packet |
60 |
60 ms of CS payload included in each RTP/UDP packet |
80 |
80 ms of CS payload included in each RTP/UDP packet |
All other values are undefined in Release 1. |
11.2.54 Payload Type
The Payload Type IE is used to indicate the RTP Payload Type for dynamically assigned Payload Type.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type IEI |
octet 1 |
||||||||
Length of Payload Type IE contents |
octet 2 |
||||||||
Payload Type |
octet 3 |
Figure 11.2.54.1: Payload Type information element
Table 11.2.54.1: Payload Type information element
Payload Type (octet 3) Allowed values are between 96 and 127. All other values are undefined in Release 1. |
11.2.55 Multirate Configuration
The MultiRate configuration information element gives parameters related to the multi-rate speech codec used in GAN A/Gb mode.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Multirate Configuration IEI |
octet 1 |
||||||||
Length of Multirate Configuration contents |
octet 2, 2a |
||||||||
The rest of the IE, except the Threshold and Hysteresis values, is coded as in [12], not including IEI and length, if present. The included Threshold and Hysteresis values shall be coded according to Table 11.2.55.1 and Annex D.1. |
octet 3 …. octet n |
Figure 11.2.55.1: Multirate Configuration information element
Table 11.2.55.1: MultiRate configuration information element
Octet 3 – n Threshold Frame Loss value Ratio 0 = 0 % 1 = 0.25 % … 19 = 4.75 % 20 = 5 % 21 = 5.5 % … 39 = 14.5 % 40 = 15 % 41 = 16 % … 50 = 25 % 51 = 26 % 52 = 28 % … 62 = 48 % 63 = 50 % |
Hysteresis Frame Loss value Ratio 0 = 0 % 1 = 0.25 % 2 = 0.5 % 3 = 0.75 % 4 = 1 % 5 = 1.5 % 6 = 2 % 7 = 2.5 % 8 = 3 % 9 = 4 % 10 = 5 % 11 = 6 % 12 = 8 % 13 = 10 % 14 = 13 % 15 = 17 % |
The Frame Loss Ratio (FLR) is the number of missing speech frames at the receiver, divided by the total number of expected speech frames for the speech signal during the actual measurement period. When there are redundant speech frames, these shall also be counted both when missing and as included in the complete speech signal respectively. In missing RTP packets, the number of redundant speech frames shall be assumed to follow the used RTP Redundancy Configuration and the latest Codec Mode Request value, CMR, signalled to the sending part. (For CMR, see annex A.) For example, when RTP sample size is 20 ms, single redundancy is used and two RTP packets are missing during the last second, the frame loss ratio is (2+2)/(2*50) = 4%. A filter shall be applied to the frame loss ratio before comparing it with the threshold and hysteresis values according to Annex D.1. |
11.2.56 Mobile Station Classmark 3
The purpose of the Mobile Station Classmark 3 information element is to provide the network with information concerning aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Mobile station classmark 3 IEI |
octet 1 |
||||||||
Length of mobile station classmark 3 contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [8], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.56.1: Mobile Station Classmark 3 information element
11.2.57 LLC-PDU
This information element contains an LLC-PDU. The element coding is:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
LLC-PDU IEI |
octet 1 |
||||||||
Length of LLC-PDU contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as in [19], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.57.1: LLC-PDU information element
11.2.58 Location Exclude List indicator
The Location Exclude List indicator information element is used to indicate which part of the Location Area Identification is to be added in the Location Exclude List.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Location Exclude List indicator IEI |
octet 1 |
|||||||||
Length of Location Exclude List indicator contents |
octet 2 |
|||||||||
spare |
LBLI |
octet 3 |
Figure 11.2.58.1: Location Exclude List indicator information element
Table 11.2.58.1: Location Exclude List indicator information element
LBLI, Location Exclude List indicator (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
MCC |
0 |
0 |
1 |
MCC and MNC |
0 |
1 |
0 |
MCC, MNC and LAC |
All other values are undefined in Release 1. |
11.2.59 Reset Indicator
The Reset Indicator information element is used to signal to the MS when the flow control procedure is complete and the MS can reset the maximum uplink data rate to normal level.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Reset Indicator IEI |
octet 1 |
|||||||||
Length of Reset Indicator contents |
octet 2 |
|||||||||
spare |
RI |
octet 3 |
Figure 11.2.59.1 Reset Indicator information element
Table 11.2.59.1: Reset Indicator information element
RI, Reset Indicator (octet 3) Bit 1 0 The flow control condition continues to exist.. 1 The flow control condition no longer exists. |
11.2.60 TU4003 Timer
The purpose of this information element is to indicate to the MS how often it is allowed to send flow control messages. In case of CS traffic channel is activated or released or in case of GA-CSR state transition, MS is allowed to update Flow Control condition by sending GA-PSR-DFC-REQ message while TU4003 is running.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU4003 Timer IEI |
octet 1 |
||||||||
Length of TU4003 Timer IE contents |
octet 2 |
||||||||
TU4003 Timer value MSB |
octet 3 |
||||||||
TU4003 Timer value LSB |
octet 4 |
Figure 11.2.60.1: TU4003 Timer information element
Table 11.2.60.1: TU4003 Timer information element
TU4003 Timer value (octet 3 and 4) In the TU4003 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. The value is given in number of seconds. The TU4003 Timer value consists of 2 octets. |
11.2.61 AP Service Name
The AP Service Name element contains either the SSID or the PAN Service Name of the unlicensed AP being used.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
AP Service Name IEI |
octet 1 |
||||||||
Length of AP Service Name IE contents |
octet 2, 2a |
||||||||
AP Service Name type |
octet 3 |
||||||||
AP Service Name MSB |
octet 4 |
||||||||
AP Service Name LSB |
octet n |
Figure 11.2.61.1: AP Service Name information element
Table 11.2.61.1: AP Service Name information element
AP Service Name type number value (octet 3) All other values are undefined in Release 1. AP Service Name value (octet 4 to octet n) |
11.2.62 GAN Service Zone Information
The purpose of the GAN Service Zone Information information element is to provide the mobile station with GAN Service Zone related information applicable to the current location of the user. It consists of two fields. GAN Service Zone Name string can be used by the GANC to indicate textual information related to the location. GAN Service Zone Icon Indicator can be used by the GANC to turn on various indicators in the mobile station.
GAN Service Zone Information IEI |
octet 1 |
|
Length of GAN Service Zone Information value contents |
octet 2, 2a |
|
GAN Service Zone Icon Indicator |
octet 3 |
|
Length of GAN Service Zone string |
octet 4 |
|
GAN Service Zone string, 1st character |
octet 5 |
|
GAN Service Zone string, last character |
octet n |
Figure 11.2.62.1: GAN Service Zone Information information element
Table 11.2.62.1: GAN Service Zone Information information element
GAN Service Zone Icon Indicator, octet 3 Value 1 Unlimited Calls 128-254 Operator specific values All other values are reserved. GAN Service Zone Name, octets 4-n Octet 4 defines the length (i.e. number of octets) of the GAN Service Zone Name string starting in octet 5. Maximum length of the GAN Service Zone Name string is 32 characters and as each character can be presented using 1 to 4 octets the maximum number of octets is 128. The GAN Service Zone Name string (octets 5 to n) is coded as a string according to UTF-8 format defined in RFC 3629 [50]. This means the 1st octet of the UTF-8 string is coded in octet 5 and the last octet of the UTF-8 string is coded in the last octet of this field (octet n). |
11.2.63 RTP Redundancy Configuration
The RTP Redundancy configuration information element provides the parameters related to redundancy policy for the AMR active codec set. For each mode of the AMR codec set, the redundancy level is indicated i.e. no redundancy (window size 1), single redundant frame (window size 2), double redundant frames (window size 3). The mode for encoding redundant frames can be equal to or lower than the mode for the primary encoding.
For each mode of the AMR Active Mode Set, as signaled in the Multi-rate Configuration IE, the window size for including redundant frames is indicated. So if e.g. the Active Mode Set contains four active modes, then the RTP Redundancy Configuration IE consists of six octets, of which four indicate the Codec Mode to Window Size mapping.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
RTP Redundancy Configuration IEI |
octet 1 |
||||||||||
Length of RTP Redundancy Configuration IE contents |
octet 2, 2a |
||||||||||
GAN A/Gb Mode Codec Mode |
GAN Iu Mode Codec Mode |
Window Size |
octet 3 …. octet n |
Figure 11.2.63.1: Redundancy Configuration information element
Table 11.2.63.1: Redundancy configuration IE
Window Size (octet 3 to octet n) Bits |
||||
2 |
1 |
|||
0 |
0 |
Window size 1, No redundancy |
||
0 |
1 |
Window size 2 (single redundancy) |
||
1 |
0 |
Window size 3 (double redundancy) |
||
All other values are reserved |
||||
GAN A/Gb Mode Codec Mode (octet 3 to octet n) Bits |
||||
8 |
7 |
|||
The GAN A/Gb Mode Codec Mode is coded as in [47] sub-clause 3.4.1 |
||||
GAN Iu Mode Codec Mode (octet 3 to octet n) Bits 6 5 4 3 0 0 0 0 Represents the lowest codec mode (lowest bit-rate) of the ACS 0 0 0 1 Represents the second lowest mode, if the ACS includes more than one mode 0 0 1 0 Represents the third lowest mode, if the ACS includes more than two modes 0 0 1 1 Represents the fourth lowest mode, if the ACS includes more than three modes 0 1 0 0 Represents the fifth lowest mode, if the ACS includes more than four modes 0 1 0 1 Represents the sixth lowest mode, if the ACS includes more than five modes 0 1 1 0 Represents the seventh lowest mode, if the ACS includes more than six modes 0 1 1 1 Represents the highest mode, if the ACS includes eight modes |
11.2.64 UTRAN Classmark
The UTRAN Classmark information element includes the INTER RAT HANDOVER INFO (defined in [40]) which gives UTRAN related information to the network (target system) for the purpose of intersystem handover.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
UTRAN Classmark IEI |
octet 1 |
||||||||
Length of UTRAN Classmark contents |
octet 2, 2a |
||||||||
The rest of the IE is the INTER RAT HANDOVER INFO coded as in [40], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.64.1: UTRAN Classmark information element
11.2.65 Classmark Enquiry Mask
The Classmark Enquiry mask defines the information to be returned to the network. The bit mask defines the specific information to be returned, such as UTRAN specific information and/or requests the sending of the GA-CSR CLASSMARK CHANGE message.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Classmark Enquiry Mask IEI |
octet 1 |
||||||||
Length of Classmark Enquiry Mask contents |
octet 2, 2a |
||||||||
The rest of the IE is the Classmark Enquiry Mask coded as in [12], not including IEI and length, if present. |
octet 3 …. octet n |
Figure 11.2.65.1: Classmark Enquiry Mask information element
11.2.66 UTRAN Cell Identifier List
The UTRAN Cell Identifier List information element is used to transfer multiple UTRAN target cell identifiers from the MS to the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
UTRAN Cell Identifier List IEI |
octet 1 |
|||||||||
Length of UTRAN Cell Identifier List value contents |
octet 2, 2a |
|||||||||
spare |
UTRAN Cell Identification Discriminator |
octet 3 |
||||||||
UTRAN Cell Identification 1 |
||||||||||
UTRAN Cell Identification n |
Figure 11.2.66.1: UTRAN Cell Identifier List information element
The length of the UTRAN Cell Identifier List information element depends on the UTRAN Cell Identification Discriminator (octet 3).
The "UTRAN Cell Identification Discriminator" is coded as follows:
0000 PLMN-ID, LAC and a 28-bit Cell Id are used to identify the target UTRAN cell.
All other values are reserved.
The coding of the UTRAN Cell Identifications 1 to n depends on the Cell identification discriminator (octet 3). Below the coding is shown for each UTRAN Cell Identification Discriminator:
Coding of UTRAN Cell Identification for UTRAN Cell Identification Discriminator = 0000
Table 11.2.66.1: Coding of UTRAN Cell Identification Discriminator = 0000
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MCC digit 2 |
MCC digit 1 |
octet m |
||||||
MNC digit 3 |
MCC digit 3 |
octet m+1 |
||||||
MNC digit 2 |
MNC digit 1 |
octet m+2 |
||||||
LAC |
octet m+3 |
|||||||
LAC cont. |
octet m+4 |
|||||||
3G Cell identity |
octet m+5 |
|||||||
3G Cell identity cont. |
octet m+6 |
|||||||
3G Cell identity cont. |
octet m+7 |
|||||||
3G Cell identity cont. |
Spare |
octet m+8 |
LAC, Location Area Code (2 octet field)
This field is the binary representation of the Location Area Code, see [3]. The LAC field consists of 16 bits. Bit 8 in octet m+3 is the most significant bit and bit 1 in octet m+4 is the least significant bit.
3G Cell Identity (4 octet field).
The octets (m+5)-(m+8) are coded as octets 3-6 in sub-clause 11.2.73.
11.2.67 Serving GANC table indicator
The purpose of the Serving GANC table indicator is to indicate to the mobile station if it is allowed to store information in the stored Serving GANC table after a successful registration.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Serving GANC table indicator IEI |
octet 1 |
|||||||||
Length of Serving GANC table indicator value contents |
octet 2 |
|||||||||
spare |
SUTI |
octet 3 |
Figure 11.2.67.1 Serving GANC table indicator information element
Table 11.2.67.1: Serving GANC table indicator information element
SUTI, Serving GANC table indicator (octet 3) Bit 1 0 The MS is not allowed to store information in the stored Serving GANC table but should still maintain the existing content of the serving GANC table – "Do Not Store". 1 The MS is allowed to store information in the stored Serving GANC table"Store". |
11.2.68 Registration indicators
The Registration indicators information element is used by the mobile station to indicate status information related to the registration request to the network. This information element is included only when attempting to register to the Default GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Registration indicators IEI |
octet 1 |
|||||||||
Length of Registration indicators contents |
octet 2 |
|||||||||
spare |
MPS |
octet 3 |
Figure 11.2.68.1 Registration indicators information element
Table 11.2.68.1: Registration indicators information element
MPS, Manual PLMN Selection indicator (octet 3) Bit 2 1 0 0 The MS is in Automatic PLMN selection mode and user reselection was not triggered. 0 1 The MS is in Manual PLMN selection mode and/or user reselection was triggered. The MS requests the list of PLMN identities that may provide GAN service in the current location. All other values are reserved for future use. |
11.2.69 GAN PLMN List
The GAN PLMN List information element is used by the network to indicate possible PLMNs that may provide GAN service to the MS in its current location. The information element contains the PLMN identifier and the associated GANC and GANC-SEGW address information for each PLMN in the list. It may also contain PLMN specific GAN Service Zone Information.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
GAN PLMN List IEI |
octet 1 |
||||||||||
Length of GAN PLMN List value contents |
octet 2, 2a |
||||||||||
Number of PLMNs |
octet 3 |
||||||||||
PLMN information, PLMN 1 |
|||||||||||
PLMN information, PLMN n |
Figure 11.2.69.1: PLMN List information element
The "Number of PLMNs" (octet 3) contains the number of PLMN information items in the list. Bit 8 of octet 3 is the most significant bit and bit 1 of octet 3 the least significant bit.
Coding of PLMN information for each PLMN is the following:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MCC digit 2 |
MCC digit 1 |
octet m |
||||||
MNC digit 3 |
MCC digit 3 |
octet m+1 |
||||||
MNC digit 2 |
MNC digit 1 |
octet m+2 |
||||||
Spare |
GAN Modes |
GSZI |
GANC-ADDR |
SEGW-ADDR |
octet m+3 |
|||
GANC-SEGW Address information |
||||||||
GANC Address information |
||||||||
GAN Service Zone information |
Figure 11.2.69.2: PLMN information part of PLMN List information element
Table 11.2.69.1: PLMN information part of PLMN List information element
MCC, Mobile country code (octet m, octet m+1 bits 1 to 4) The MCC field is coded as in ITU-T Rec. E212, Annex A. MNC, Mobile network code (octet m+2, octet m+1 bits 5 to 8). The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. For PCS 1900 for North America, Federal Regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC over the radio interface. In this case, bits 5 to 8 of octet m+1 shall be coded as "1111". Mobile equipment shall accept MNC coded in such a way. SEGW-ADDR, GANC-SEGW address type indicator (octet m+3) Bits 2 1 0 0 GANC-SEGW Address Information for this PLMN is coded as IP-address. The format is as defined in sub-clause 11.2.9, "IP Address" excluding the IP address IEI, but including Length Indicator, IP Address Type and Address Information. 1 0 GANC-SEGW Address Information for this PLMN is coded as FQDN. The format is as defined in sub-clause 11.2.10, "Fully Qualified Domain/Host Name (FQDN)" excluding the FQDN IEI, but including Length Indicator and FQDN. GANC-ADDR, GANC address type indicator (octet m+3) Bits 4 3 0 0 GANC Address Information is coded as IP-address. The format is as defined in sub-clause 11.2.9, "IP Address" excluding the IP address IEI, but including Length 1 0 GANC Address Information is coded as FQDN. The format is as defined in sub-clause 11.2.10, "Fully Qualified Domain/Host Name (FQDN)" excluding the FQDN GSZI, GAN Service Zone Information Indicator (octet m+3) Bit 5 0 GAN Service Zone Information is not included for this PLMN. 1 GAN Service Zone Information is included for this PLMN. GAN Modes Bit 7 6 0 0 Unknown 0 1 The PLMN can only be accessed using GAN A/Gb mode 1 0 The PLMN can only be accessed using GAN Iu mode 1 1 The PLMN can be accessed using GAN A/Gb mode or GAN Iu mode GANC-SEGW Address information and GANC Address information for each PLMN are coded as defined by GANC-SEGW and GANC address type indicators (for each PLMN). GAN Service Zone Information is of variable length and the format is as defined in the sub-clause 11.2.62, for the octets 3 to n (GAN Service Zone Icon Indicator, length of GAN Service Zone Name and GAN Service Zone Name). The inclusion of this field is optional for each PLMN and is defined by the GSZI bit. |
11.2.70 GERAN Received Signal Level List
The GERAN Received Signal Level List information element contains the received signal level for each cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
GERAN Received Signal Level List IEI |
octet 1 |
||||||||||
Length of GERAN Received Signal Level List value contents |
octet 2, 2a |
||||||||||
spare |
RXLEV-NCELL 1 |
octet 3 |
|||||||||
spare |
RXLEV-NCELL 2 |
octet 4 |
|||||||||
spare |
RXLEV-NCELL n |
octet n+2 |
Figure 11.2.70.1: GERAN Received Signal Level List information element
Table 11.2.70.1: GERAN Received Signal Level List information element
RXLEV-NCELL i, Result of measurement on the i’th neighbour cell (octet i+2), i ranges from 1 to n. The RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 45.008 to the received signal strength on the i’th neighbouring cell. Range: 0 to 63. |
11.2.70b UTRAN Received Signal Level List
The UTRAN Received Signal Level List information element contains the received signal level CPICH Ec/No and CPICH RSCP [46] value for each cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
UTRAN Received Signal Level List IEI |
octet 1 |
||||||||||
Length of UTRAN Received Signal Level List value contents |
octet 2, 2a |
||||||||||
spare |
Ec/No-NCELL 1 |
octet 3 |
|||||||||
spare |
RSCP-NCELL 1 |
octet 4 |
|||||||||
spare |
Ec/No-NCELL 2 |
octet 5 |
|||||||||
spare |
RSCP-NCELL 2 |
octet 6 |
|||||||||
spare |
Ec/No-NCELL n |
octet 2*n+1 |
|||||||||
spare |
RSCP-NCELL n |
octet 2*n+2 |
Figure 11.2.70b.1: UTRAN Received Signal Level List information element
Table 11.2.70b.1: UTRAN Received Signal Level List information element
Ec/No-NCELL i, Result of Ec/No measurement on the i’th neighbour cell is contained in octet 2*i+1, i ranges from 1 to n. RSCP-NCELL i, Result of RSCP measurement on the i’th neighbour cell is contained in octet 2*i+2, i ranges from 1 to n. The mapping is defined in [46]. For RSCP the range from "-116 dBm ≤ CPICH RSCP < -115 dBm" (reported as 0) to "-53 dBm ≤ CPICH RSCP < -52 dBm" (reported as 63) is used. RSCP values below -116 dBm shall be reported as 0 and values -52 dBm and above shall be reported as 63. For Ec/No the range from "-24 dB ≤ CPICH Ec/Io < -23.5 dB" (reported as 1) to "-0.5 ≤ CPICH Ec/Io < 0" (reported as 48) is used. Ec/Io values below -24 dB shall be reported as 0 and values 0 dB and above shall be reported as 49. |
11.2.71 Required GAN Services
The purpose of the Required GAN Services information element is to indicate to the GANC that the mobile station requires a GAN specific service and which of the GAN services the mobile station requires.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Required GAN Services IEI |
octet 1 |
|||||||||
Length of Required GAN Services contents |
octet 2 |
|||||||||
spare |
CBS |
octet 3 |
Figure 11.2.71.1: Required GAN Services information element
Table 11.2.71.1: Required GAN Services information element
CBS Cell Broadcast Service (octet 3) Bit 1 0 CBS is not required by the mobile station 1 CBS is required by the mobile station. |
11.2.72 Broadcast Container
The Broadcast Container information element is used by the network to encapsulate Cell Broadcast information being passed to a mobile station.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||
Broadcast Container IEI |
octet 1 |
||||||||||
Length of Broadcast Container value contents |
octet 2, 2a |
||||||||||
Number of CBS Frames |
octet 3 |
||||||||||
CBS Frames 1 |
octet 4-91 |
||||||||||
CBS Frames n |
octet m-(m+87) |
Figure 11.2.72.1: Broadcast Container information element
The "Number of CBS Frames" (octet 3) contains the number of CBS Frames in the list. Bit 8 of octet 3 is the most significant bit and bit 1 of octet 3 the least significant bit.
Coding of CBS Frame is the following:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Page from a CBS Message MSB |
octet x…octet x+87 |
|||||||
Page from a CBS Message LSB |
Figure 11.2.72.2: CBS Frame part of Broadcast Container information element
The coding of the page of the CBS message is defined in sub-clause 9.4.1 in TS 23.041.
11.2.73 3G Cell Identity
The purpose of the 3G Cell Identity information element is to identify a cell within a PLMN.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
3G Cell Identity IEI |
octet 1 |
||||||||
Length of 3G Cell Identity IE contents |
octet 2, 2a |
||||||||
See Annex F for coding |
octet 3 …. octet 6 |
Figure 11.2.73.1 3G Cell Identity information element
11.2.74 PS Handover to GERAN Command
The purpose of the PS Handover to GERAN Command information element is to provide the MS with Radio Resource and Non-Access Stratum information required for performing PS handover to a GERAN cell. The PS Handover to GERAN Command information element and either the PS Handover to GERAN PSI or the PS Handover to GERAN SI information element together contain all of the information needed by the MS to perform PS handover to a GERAN cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
PS Handover to GERAN Command IEI |
octet 1 |
||||||||
Length of PS Handover to GERAN Command value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as the PS HANDOVER COMMAND message defined in [45]. |
octet 3 …. octet n |
Figure 11.2.74.1: PS Handover to GERAN Command information element
11.2.75 PS Handover to UTRAN Command
The purpose of the PS Handover to UTRAN Command information element is to provide the MS with information required for performing PS handover to a UTRAN cell. The PS Handover to UTRAN Command information element contains all information needed by the MS for performing PS handover to a UTRAN cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
PS Handover to UTRAN Command IEI |
octet 1 |
||||||||
Length of PS Handover to UTRAN Command value contents |
octet 2, 2a |
||||||||
The rest of the IE is coded as the INTERSYSTEM HANDOVER TO UTRAN COMMAND message defined in [40]. |
octet 3 …. octet n |
Figure 11.2.75.1: PS Handover to UTRAN Command information element
11.2.76 PS Handover to GERAN PSI
The purpose of the PS Handover to GERAN PSI information element is to provide the MS with packet system information (corresponding to the target GERAN cell) required for performing PS handover to a GERAN cell where PBCCH is present. The PS Handover to GERAN Command information element and the PS Handover to GERAN PSI information element together contain all of the information needed by the MS for performing PS handover to a GERAN cell where PBCCH is present.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
PS Handover to GERAN PSI IEI |
octet 1 |
|||||||||
Length of PS Handover to GERAN PSI value contents |
octet 2, 2a |
|||||||||
Length of PS1 payload |
octet 3 |
|||||||||
The same system information sent using a PSI1 on a PBCCH (see 3GPP TS 44.060 [45]). |
octet 4 …. octet n |
|||||||||
Length of PSI2 payload |
octet n+1 |
|||||||||
The same system information sent using one or more instances of the PSI2 message on a PBCCH (see 3GPP TS 44.060 [45]). |
octet n+2 …. octet k |
|||||||||
Length of PSI14 payload |
octet k+1 |
|||||||||
The same system information sent using a PSI14 message on a PBCCH (see 3GPP TS 44.060 [45]). |
octet k+2 …. octet p |
Figure 11.2.76.1: PS Handover to GERAN PSI information element
11.2.77 PS Handover to GERAN SI
The purpose of the PS Handover to GERAN SI information element is to provide the MS with system information (corresponding to the target GERAN cell) required for performing PS handover to a GERAN cell where PBCCH is not present. The PS Handover to GERAN Command information element and the PS Handover to GERAN SI information element together contain all of the information needed by the MS for performing PS handover to a GERAN cell where PBCCH is not present.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
PS Handover to GERAN SI IEI |
octet 1 |
|||||||||
Length of PS Handover to GERAN SI value contents |
octet 2, 2a |
|||||||||
Length of S1 payload |
octet 3 |
|||||||||
The same system information sent using an SI1 on a BCCH (see 3GPP TS 44.018 [12]). |
octet 4 …. octet n |
|||||||||
Length of SI3 payload |
octet n+1 |
|||||||||
The same system information sent using an SI3 message on a BCCH (see 3GPP TS 44.018 [12]). |
octet n+2 …. octet k |
|||||||||
Length of SI13 payload |
octet k+1 |
|||||||||
The same system information sent using an SI13 message on a BCCH (see 3GPP TS 44.018 [12]). |
octet k+2 …. octet p |
Figure 11.2.77.1: PS Handover to GERAN SI information element
11.2.78 TU4004 Timer
The purpose of this information element is to indicate to the MS how long it should wait for a GA-PSR HANDOVER COMMAND message after sending a GA-PSR HANDOVER INFORMATION message to the network or receiving a GA-PSR HANDOVER CONTINUE message from the network.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
TU4004 Timer IEI |
octet 1 |
||||||||
Length of TU4004 Timer IE contents |
octet 2 |
||||||||
TU4004 Timer value |
octet 3 |
Figure 11.2.78.1: TU4004 Timer information element
Table 11.2.78.1: TU4004 Timer information element
TU4004 Timer value (octet 3) The value is given in number of seconds. |
11.2.79 GAN Mode Indicator
The GAN Mode Indicator information element indicates the GAN mode that the MS shall operate in for the current registration.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GAN Mode Indicator IEI |
octet 1 |
|||||||
Length of GAN Mode Indicator value contents |
octet 2 |
|||||||
GMI |
octet 3 |
Figure 11.2.79.1: GAN Mode Indicator information element
Table 11.2.79.1: GAN Mode Indicator information element
GMI, GAN Mode Indicator (octet 3) |
|
0 |
Reserved |
1 |
The MS shall operate in GAN A/Gb mode |
2 |
The MS shall operate in GAN Iu mode |
3 to 255 |
Reserved |
11.2.80 CN Domain Identity
The CN Domain Identity information element indicates the type of core network domain (CS or PS) to which the message applies.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CN Domain Identity IEI |
octet 1 |
|||||||
Length of CN Domain Identity value contents |
octet 2 |
|||||||
CNDI |
octet 3 |
Figure 11.2.80.1: CN Domain Identity information element
Table 11.2.80.1: CN Domain Identity information element
CNDI, CN Domain Identity (octet 3) |
|
0 |
Reserved |
1 |
CS domain |
2 |
PS domain |
3 to 255 |
Reserved |
11.2.81 GAN Iu Mode Cell Description
The GAN Iu Mode Cell Description information element provides a minimum description of a GAN Iu mode cell, e.g. to identify the GAN Iu mode cell in order to perform handover from GERAN/UTRAN.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GAN Iu Mode Cell Description IEI |
octet 1 |
|||||||
Length of GAN Iu Mode Cell Description value contents |
octet 2 |
|||||||
UARFCN |
octet 3 |
|||||||
UARFCN |
octet 4 |
|||||||
PSC |
octet 5 |
|||||||
PSC |
octet 6 |
Figure 11.2.81.1: GAN Iu Mode Cell Description information element
Table 11.2.81.1: GAN Iu Mode Cell Description information element
UARFCN, UTRA Absolute RF Channel Number (octet 3, 4) Allowed values are between 0 and 16383. This is a 14-bit quantity with the first bit (most significant bit) in octet 3 bit 6 and the last bit (least significant bit) in octet 4 bit 1. Octet 3 bits 7-8 are filled by ’00’ PSC, Primary Scrambling Code (octet 5, 6) Allowed values are between 0 and 511. This is a 9-bit quantity with the first bit (most significant bit) in octet 5 bit 1 and the last bit (least significant bit) in octet 6 bit 1. Octet 5 bits 2-8 are filled by ‘0000000’. |
11.2.82 3G UARFCN
The 3G UARFCN information element indicates the UARFCN value of the current UTRAN serving cell, if the current serving cell is a UTRAN cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
3G UARFCN IEI |
octet 1 |
|||||||
Length of 3G UARFCN value contents |
octet 2 |
|||||||
UARFCN |
octet 3 |
|||||||
UARFCN |
octet 4 |
Figure 11.2.82.1: 3G UARFCN information element
Table 11.2.82.1: 3G UARFCN information element
UARFCN, UTRA Absolute RF Channel Number (octet 3, 4) Allowed values are between 0 and 16383. This is a 14-bit quantity with the first bit (most significant bit) in octet 3 bit 6 and the last bit (least significant bit) in octet 4 bit 1. Octet 3 bits 7-8 are filled by ’00’ |
11.2.83 RAB ID
The RAB ID information element is used by the GANC to identify a circuit transport channel or packet transport channel.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
RAB ID IEI |
octet 1 |
|||||||
Length of RAB ID value contents |
octet 2 |
|||||||
RABID |
octet 3 |
Figure 11.2.83.1: RAB ID information element
Table 11.2.83.1: RAB ID information element
RABID, RAB ID (octet 3) Allowed values are between 0 and 255. |
11.2.84 RAB ID List
The RAB ID List information element is used by the GANC to identify a set of circuit transport channel(s) or packet transport channel(s).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
RAB ID List IEI |
octet 1 |
|||||||
Length of RAB ID List value contents |
octet 2, 2a |
|||||||
Number of RAB IDs |
octet 3 |
|||||||
RAB ID 1 |
||||||||
RAB ID n |
Figure 11.2.84.1: RAB ID List information element
Table 11.2.84.1: RAB ID List information element
Number of RAB IDs (octet 3) The number of RAB IDs in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. RAB ID 1..n The format is as defined in sub-clause 11.2.83, "RAB ID" but without the RAB ID IEI and length fields. |
11.2.85 GA-RRC Establishment Cause
The GA-RRC Establishment Cause information element indicates the cause for the GA-RRC connection establishment request.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GA-RRC Establishment Cause IEI |
octet 1 |
|||||||
Length of GA-RRC Establishment Cause value contents |
octet 2 |
|||||||
Cause |
octet 3 |
Figure 11.2.85.1: GA-RRC Establishment Cause information element
Table 11.2.85.1: GA-RRC Establishment Cause information element
Cause (octet 3) The GA-RRC Establishment Cause IE is aligned with the "Establishment cause" IE defined in section 10.3.3.11 of [TS 25.331]. A Cause value of 1 is assigned to the first value in the RRC "Establishment cause" enumerated list (i.e., "Originating Conversational Call") and the Cause value is incremented by one for each subsequent "Establishment cause" value. |
11.2.86 GA-RRC Cause
The GA-RRC Cause information element indicates the cause associated with the GA-RRC procedure (e.g., release, reject, etc.).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GA-RRC Cause IEI |
octet 1 |
|||||||
Length of GA-RRC Cause value contents |
octet 2 |
|||||||
Cause MSB |
octet 3 |
|||||||
Cause LSB |
octet 4 |
Figure 11.2.86.1: GA-RRC Cause information element
Table 11.2.86.1: GA-RRC Cause information element
Cause (octet 3) The GA-RRC Cause IE is aligned with the "Cause" IE defined in section 9.2.1.4 of 3GPP TS 25.413 [52]. The Cause value is coded per the values defined in section 9.2.1.4 of [52]. In addition, a value of 0 (zero) is considered a normal event or indicating success. |
11.2.87 GA-RRC Paging Cause
The GA-RRC Paging Cause information element indicates the cause for paging.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GA-RRC Paging Cause IEI |
octet 1 |
|||||||
Length of GA-RRC Paging Cause value contents |
octet 2 |
|||||||
Paging Cause |
octet 3 |
Figure 11.2.87.1: GA-RRC Paging Cause information element
Table 11.2.87.1: GA-RRC Paging Cause information element
Paging Cause (octet 3) |
|
0 |
Terminating Conversational Call |
1 |
Terminating Streaming Call |
2 |
Terminating Interactive Call |
3 |
Terminating Background Call |
4 |
Terminating Low Priority Signalling |
5 |
Terminating High Priority Signalling |
6 to 255 |
Reserved for future use |
11.2.88 Intra Domain NAS Node Selector
The Intra Domain NAS Node Selector information element carries information to be used to route the establishment of a signalling connection to a CN node within a CN domain.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Intra Domain NAS Node Selector IEI |
octet 1 |
|||||||
Length of Intra Domain NAS Node Selector value contents |
octet 2 |
|||||||
IDNNS Type |
octet 3 |
|||||||
Routing Parameter |
octet 4 |
|||||||
Routing Parameter |
octet 5 |
Figure 11.2.88.1: Intra Domain NAS Node Selector information element
Table 11.2.88.1: Intra Domain NAS Node Selector information element
IDNSS Type (octet 3) Value 0 Reserved 1 Local (P)TMSI 2 (P)TMSI of same PLMN, different (RA)LA 3 (P)TMSI of different PLMN 4 IMSI (response to IMSI paging) 5 IMSI (cause UE initiated event) 6 IMEI 7-255 Reserved All other values are reserved. Routing Parameter (octet 4, 5) This is a 10-bit quantity with the first bit (most significant bit) in octet 4 bit 2 and the last bit (least significant bit) in octet 5 bit 1. Octet 4 bits 3-8 are filled by ‘000000’. Refer to the Intra Domain NAS Node Selector information element definition in sub-clause 10.3.1.6 of [40] for a description of the above IDNSS Type and Routing Parameter values. |
11.2.89 CTC Activation List
The CTC Activation List information element is used by the GANC to describe the circuit transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Activation List IEI |
octet 1 |
|||||||
Length of CTC Activation List value contents |
octet 2, 2a |
|||||||
Number of CTCs |
octet 3 |
|||||||
CTC Description, CTC 1 |
||||||||
CTC Description, CTC n |
Figure 11.2.89.1: CTC Activation List information element
Table 11.2.89.1: CTC Activation List information element
Number of CTCs The number of CTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. CTC Description The format is as defined in sub-clause 11.2.90, "CTC Description". |
11.2.90 CTC Description
The CTC Description information element is used by the GANC to describe the circuit transport channel that shall be activated or modified between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Description IEI |
octet 1 |
|||||||
Length of CTC Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
RAB Configuration |
||||||||
Sample Size |
||||||||
RTP UDP Port |
||||||||
GANC IP Address |
||||||||
Payload Type |
||||||||
Multi-rate Configuration 2 |
||||||||
RTP Redundancy Configuration |
||||||||
RTCP UDP Port |
||||||||
NAS Synchronisation Indicator |
Figure 11.2.90.1: CTC Description information element
Table 11.2.90.1: CTC Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. RAB Configuration The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. Sample Size The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. RTP UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTP UDP Port". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. GANC IP Address The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "GANC IP Address". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. Payload Type The format is as defined in sub-clause 11.2.54, "Payload Type". This field shall be included in the case of CTC activation. It shall not be included in the case of CTC modification. Multi-rate Configuration 2 The format is as defined in sub-clause 11.2.104, "Multi-rate Configuration 2". This field shall be included in the case of CTC activation if the RAB Configuration specifies speech. It shall only be included in the case of CTC modification if modification of this parameter is requested. RTP Redundancy Configuration The format is as defined in sub-clause 11.2.63, "RTP Redundancy Configuration". This field shall be included in the case of CTC activation if the RAB Configuration specifies speech and the MS has indicated support for RTP redundancy in the GAN Classmark IE. It shall only be included in the case of CTC modification if modification of this parameter is requested. RTCP UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTCP UDP Port". This field may be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. NAS Synchronisation Indicator The format is as defined in sub-clause 11.2.109, "NAS Synchronisation Indicator". This field shall be included in the case of CTC activation if received by the GANC from the CN. It shall only be included in the case of CTC modification if modification of this parameter is requested. |
11.2.91 CTC Activation Ack List
The CTC Activation Ack List information element is used by the MS to describe certain parameters of the circuit transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Activation Ack List IEI |
octet 1 |
|||||||
Length of CTC Activation Ack List value contents |
octet 2, 2a |
|||||||
Number of CTCs |
octet 3 |
|||||||
CTC Activation Ack Description, CTC 1 |
||||||||
CTC Activation Ack Description, CTC n |
Figure 11.2.91.1: CTC Activation Ack List information element
Table 11.2.91.1: CTC Activation Ack List information element
Number of CTCs The number of CTC Activation Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. CTC Activation Ack Description The format is as defined in sub-clause 11.2.92, "CTC Activation Ack Description". |
11.2.92 CTC Activation Ack Description
The CTC Activation Ack Description information element is used by the MS to indicate CTC activation success or failure and, in the successful case, to describe certain parameters of the circuit transport channel that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Activation Ack Description IEI |
octet 1 |
|||||||
Length of CTC Activation Ack Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
GA-RRC Cause |
||||||||
RTP UDP Port |
||||||||
Sample Size |
||||||||
Payload Type |
||||||||
RTCP UDP Port |
Figure 11.2.92.1: CTC Activation Ack Description information element
Table 11.2.92.1: CTC Activation Ack Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. GA-RRC Cause The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than ‘success’ (i.e., value ‘0’) then the following fields shall not be present in the CTC Activation Ack Description IE. RTP UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTP UDP Port". This field shall be included if the GA-RRC Cause value is ‘0’. Sample Size The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included if the GA-RRC Cause value is ‘0’ and shall indicate what sample size the MS is using and what the network shall use in the downlink. The MS shall follow the minimum sample size for the channel sent by the network in the GA-RRC ACTIVATE CHANNEL message. Payload Type The format is as defined in sub-clause 11.2.54, "Payload Type". This field shall be included if the GA-RRC Cause value is ‘0’. It shall be set to the same value as the Payload Type for the channel in the GA-RRC ACTIVATE CHANNEL message. RTCP UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTCP UDP Port". This field shall be included if the GA-RRC Cause value is ‘0’ and RTCP shall be used towards the MS. It is used to indicate the UDP port for RTCP sent to the MS. |
11.2.93 CTC Modification List
The CTC Modification List information element is used by the GANC to describe the circuit transport channel(s) that shall be modified between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Modification List IEI |
octet 1 |
|||||||
Length of CTC Modification List value contents |
octet 2, 2a |
|||||||
Number of CTCs |
octet 3 |
|||||||
CTC Description, CTC 1 |
||||||||
CTC Description, CTC n |
Figure 11.2.93.1: CTC Modification List information element
Table 11.2.93.1: CTC Modification List information element
Number of CTCs The number of CTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. CTC Description The format is as defined in sub-clause 11.2.90, "CTC Description". |
11.2.94 CTC Modification Ack List
The CTC Modification Ack List information element is used by the MS to describe certain parameters of the circuit transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Modification Ack List IEI |
octet 1 |
|||||||
Length of CTC Modification Ack List value contents |
octet 2, 2a |
|||||||
Number of CTCs |
octet 3 |
|||||||
CTC Modification Ack Description, CTC 1 |
||||||||
CTC Modification Ack Description, CTC n |
Figure 11.2.94.1: CTC Modification Ack List information element
Table 11.2.94.1: CTC Modification Ack List information element
Number of CTCs The number of CTC Modification Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. CTC Modification Ack Description The format is as defined in sub-clause 11.2.95, "CTC Modification Ack Description". |
11.2.95 CTC Modification Ack Description
The CTC Modification Ack Description information element is used by the MS to describe certain parameters of the circuit transport channel that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CTC Modification Ack Description IEI |
octet 1 |
|||||||
Length of CTC Modification Ack Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
GA-RRC Cause |
||||||||
Sample Size |
Figure 11.2.95.1: CTC Modification Ack Description information element
Table 11.2.95.1: CTC Modification Ack Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. GA-RRC Cause The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than ‘success’ (i.e., value ‘0’) then the following fields shall not be present in the CTC Modification Ack Description IE. Sample Size The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included if the GA-RRC Cause value is ‘0’ and this parameter has been modified. |
11.2.96 PTC Activation List
The PTC Activation List information element is used by the GANC to describe the packet transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Activation List IEI |
octet 1 |
|||||||
Length of PTC Activation List value contents |
octet 2, 2a |
|||||||
Number of PTCs |
octet 3 |
|||||||
PTC Description, PTC 1 |
||||||||
PTC Description, PTC n |
Figure 11.2.96.1: PTC Activation List information element
Table 11.2.96.1: PTC Activation List information element
Number of PTCs The number of PTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. PTC Description The format is as defined in sub-clause 11.2.97, "PTC Description". |
11.2.97 PTC Description
The PTC Description information element is used by the GANC to describe the packet transport channel that shall be activated or modified between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Description IEI |
octet 1 |
|||||||
Length of PTC Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
RAB Configuration |
||||||||
GANC TEID |
||||||||
MS TEID |
||||||||
GANC UDP Port |
||||||||
GANC IP Address |
Figure 11.2.97.1: PTC Description information element
Table 11.2.97.1: PTC Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. RAB Configuration The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included. GANC TEID The format is as defined in sub-clause 11.2.110, "TEID" but with IEI as specified in Table 11.2.1 for "GANC TEID". This field shall be included. MS TEID The format is as defined in sub-clause 11.2.110, "TEID" but with IEI as specified in Table 11.2.1 for "MS TEID". This field shall be included. GANC UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included. GANC IP Address The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "IP Address for GPRS user data transport". This field shall be included. |
11.2.98 PTC Activation Ack List
The PTC Activation Ack List information element is used by the MS to describe certain parameters of the packet transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Activation Ack List IEI |
octet 1 |
|||||||
Length of PTC Activation Ack List value contents |
octet 2, 2a |
|||||||
Number of PTCs |
octet 3 |
|||||||
PTC Activation Ack Description, PTC 1 |
||||||||
PTC Activation Ack Description, PTC n |
Figure 11.2.98.1: PTC Activation Ack List information element
Table 11.2.98.1: PTC Activation Ack List information element
Number of PTCs The number of PTC Activation Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. PTC Activation Ack Description The format is as defined in sub-clause 11.2.99, "PTC Activation Ack Description". |
11.2.99 PTC Activation Ack Description
The PTC Activation Ack Description information element is used by the MS to describe certain parameters of the packet transport channel that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Activation Ack Description IEI |
octet 1 |
|||||||
Length of PTC Activation Ack Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
GA-RRC Cause |
||||||||
MS UDP Port |
Figure 11.2.99.1: PTC Activation Ack Description information element
Table 11.2.99.1: PTC Activation Ack Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. GA-RRC Cause The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than ‘success’ (i.e., value ‘0’) then the following fields shall not be present in the PTC Activation Ack Description IE. MS UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included if the GA-RRC Cause value is ‘0’. |
11.2.100 PTC Modification List
The PTC Modification List information element is used by the GANC to describe the circuit transport channel(s) that shall be modified between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Modification List IEI |
octet 1 |
|||||||
Length of PTC Modification List value contents |
octet 2, 2a |
|||||||
Number of PTCs |
octet 3 |
|||||||
PTC Description, PTC 1 |
||||||||
PTC Description, PTC n |
Figure 11.2.100.1: PTC Modification List information element
Table 11.2.100.1: PTC Modification List information element
Number of PTCs The number of PTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. PTC Description The format is as defined in sub-clause 11.2.97, "PTC Description". |
11.2.101 PTC Modification Ack List
The PTC Modification Ack List information element is used by the MS to describe certain parameters of the packet transport channel(s) that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Modification Ack List IEI |
octet 1 |
|||||||
Length of PTC Modification Ack List value contents |
octet 2, 2a |
|||||||
Number of PTCs |
octet 3 |
|||||||
PTC Modification Ack Description, PTC 1 |
||||||||
PTC Modification Ack Description, PTC n |
Figure 11.2.101.1: PTC Modification Ack List information element
Table 11.2.101.1: PTC Modification Ack List information element
Number of PTCs The number of PTC Modification Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. PTC Modification Ack Description The format is as defined in sub-clause 11.2.102, "PTC Modification Ack Description". |
11.2.102 PTC Modification Ack Description
The PTC Modification Ack Description information element is used by the MS to describe certain parameters of the packet transport channel that shall be activated between the GANC and MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PTC Modification Ack Description IEI |
octet 1 |
|||||||
Length of PTC Modification Ack Description value contents |
octet 2, 2a |
|||||||
RAB ID |
||||||||
GA-RRC Cause |
||||||||
RAB Configuration |
||||||||
GANC UDP Port |
||||||||
GANC IP Address |
Figure 11.2.102.1: PTC Modification Ack Description information element
Table 11.2.102.1: PTC Modification Ack Description information element
RAB ID The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. GA-RRC Cause The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than ‘success’ (i.e., value ‘0’) then the following fields shall not be present in the PTC Activation Ack Description IE. RAB Configuration The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included if the GA-RRC Cause value is ‘0’ and this parameter has been modified. GANC UDP Port The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included if the GA-RRC Cause value is ‘0’ and this parameter has been modified. GANC IP Address The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "IP Address for GPRS user data transport". This field shall be included if the GA-RRC Cause value is ‘0’ and this parameter has been modified. |
11.2.103 RAB Configuration
The purpose of the RAB Configuration information element is to specify the UMTS RAB parameter values that are associated with a circuit transport channel or packet transport channel and that are applicable in the GAN Iu mode context.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
RAB Configuration IEI |
octet 1 |
|||||||
Length of RAB Configuration value contents |
octet 2 |
|||||||
spare |
SI |
SSD |
DO |
AI |
Traffic Class |
octet 3 |
||
spare |
Traffic Handling Priority |
spare |
octet 4 |
|||||
Maximum DL Bit Rate |
octet 5 -octet 8 |
|||||||
Maximum UL Bit Rate |
octet 9 -octet 12 |
|||||||
Guaranteed DL Bit Rate (if present) |
octet 13 -octet 16 |
|||||||
Guaranteed UL Bit Rate (if present) |
octet 17 -octet 20 |
Figure 11.2.103.1: RAB Configuration information element
Table 11.2.103.1: RAB Configuration information element
Traffic Class (octet 3) Bits 2 1 0 0 conversational 0 1 streaming 1 0 interactive 1 1 background Note: The value ‘conversational’ shall be used for AMR/AMR-WB CS domain speech. The values ‘conversational’ or ‘streaming’ shall be used for CS domain data. AI, Asymmetry Indicator (octet 3) Bits 4 3 0 0 symmetric bi-directional 0 1 asymmetric uni-directional downlink 1 0 asymmetric uni-directional uplink 1 1 asymmetric bi-directional Note: The value ‘symmetric bi-directional’ shall be used for AMR/AMR-WB CS domain speech. DO, Delivery Order (octet 3) Bit 5 0 delivery order requested 1 delivery order not requested Note: The value ‘delivery order requested’ shall be used for AMR/AMR-WB CS domain speech. SSD, Source Statistics Descriptor (octet 3) Bit 6 0 speech 1 unknown Note: The value ‘speech’ shall be used for AMR/AMR-WB speech. SI, Signalling Indication (octet 3) Bit 7 0 signalling Indication is set 1 signalling Indication is not set Note: The value ‘signalling Indication is not set’ shall be used for AMR/AMR-WB speech. Traffic Handling Priority (octet 4) Bits 7 6 5 4 Bit 7 is the most significant bit and bit 4 the least significant bit. 0 0 0 0 spare 0 0 0 1 highest .. .. 1 1 1 0 lowest 1 1 1 1 no priority Values between 1 and 14 are ordered in decreasing order of priority. Maximum DL Bit Rate, (octets 5-8) The MSB is octet 5 and the LSB is octet 8. Unit is bits/s. Maximum UL Bit Rate, (octets 9-12) The MSB is octet 9 and the LSB is octet 12. If Asymmetry Indicator indicates "Symmetric bi-directional" then this value shall be the same as Maximum DL Bit Rate value. Unit is bits/s. Guaranteed DL Bit Rate, (octets 13-16) The MSB is octet 13 and the LSB is octet 16. Included only if the Traffic Class indicates conversational or streaming. Unit is bits/s. Guaranteed UL Bit Rate, (octets 17-20) The MSB is octet 17 and the LSB is octet 20. Included only if the Traffic Class indicates conversational or streaming. If included and the Asymmetry Indicator indicates "Symmetric bi-directional" then this value shall be the same as Guaranteed DL Bit Rate value. Unit is bits/s. |
11.2.104 Multi-rate Configuration 2
The Multi-rate Configuration 2 information element gives parameters related to the multi-rate speech codec used in GAN Iu mode.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Multi-rate Configuration 2 IEI |
octet 1 |
||||||||
Length of Multi-rate Configuration 2 contents |
octet 2, 2a |
||||||||
If no more than four modes are present in the active codec set, the rest of the IE is coded the same as the Multi-rate Configuration IE in sub-clause 11.2.55, not including IEI and length. |
octet 3 …. octet n |
Figure 11.2.104.1: Multi-rate Configuration 2 information element
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Set of AMR codec modes |
octet 4 |
|||||||
Spare |
||||||||
0 |
0 |
Threshold 1 |
octet 5 |
|||||
Hysteresis 1 |
Threshold 2 |
octet 6 |
||||||
Threshold |
Threshold 3 |
|||||||
2 (cont.) |
Hysteresis 2 |
octet 7 |
||||||
Threshold 3 (cont.) |
Hysteresis 3 |
octet 8 |
||||||
Spare |
||||||||
0 |
0 |
Threshold 4 |
octet 9 |
|||||
Spare |
||||||||
Hysteresis 4 |
0 |
0 |
0 |
0 |
octet 10 |
|||
Spare |
||||||||
0 |
0 |
Threshold 5 |
octet 11 |
|||||
Spare |
||||||||
Hysteresis 5 |
0 |
0 |
0 |
0 |
octet 12 |
|||
Spare |
||||||||
0 |
0 |
Threshold 6 |
octet 13 |
|||||
Spare |
||||||||
Hysteresis 6 |
0 |
0 |
0 |
0 |
octet 14 |
|||
Spare |
||||||||
0 |
0 |
Threshold 7 |
octet 15 |
|||||
Spare |
||||||||
Hysteresis 7 |
0 |
0 |
0 |
0 |
octet 16 |
Figure 11.2.104.2: Parameters for multirate speech field
for the Multi-rate speech versions 1 & 2 when more than four modes is chosen
Table 11.2.104.1: Multi-rate Configuration 2 information element
Set of AMR codec modes This field is coded the same as in the Multi-rate Configuration IE in sub-clause 11.2.55. Threshold n, Hysteresis n (n = 1, 2 or 3) These fields are included based on the rules for the Multi-rate Configuration IE in sub-clause 11.2.55. Threshold 4, Hysteresis 4 Included when five, six, seven or eight modes are present in the active codec set. Threshold 5, Hysteresis 5 Included when six, seven or eight modes are present in the active codec set. Threshold 6, Hysteresis 6 Included when seven or eight modes are present in the active codec set. Threshold 7, Hysteresis 7 Included when eight modes are present in the active codec set. |
11.2.105 Selected Integrity Protection Algorithm
The Selected Integrity Protection Algorithm information element specifies the integrity protection algorithm selected by the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Selected Integrity Protection Algorithm IEI |
octet 1 |
|||||||
Length of Selected Integrity Protection Algorithm value contents |
octet 2 |
|||||||
Selected Integrity Protection Algorithm |
octet 3 |
Figure 11.2.105.1: Selected Integrity Protection Algorithm information element
Table 11.2.105.1: Selected Integrity Protection Algorithm information element
Selected Integrity Protection Algorithm The Selected Integrity Protection Algorithm field consists of one octet with allowed values from 0 to 15. The values are as defined for the "Integrity Protection Algorithm" in [52]. |
11.2.106 Selected Encryption Algorithm
The Selected Encryption Protection Algorithm information element specifies the encryption algorithm selected by the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Selected Encryption Algorithm IEI |
octet 1 |
|||||||
Length of Selected Encryption Algorithm value contents |
octet 2 |
|||||||
Selected Encryption Algorithm |
octet 3 |
Figure 11.2.106.1: Selected Encryption Algorithm information element
Table 11.2.106.1: Selected Encryption Algorithm information element
Selected Encryption Algorithm The Selected Encryption Algorithm field consists of one octet with allowed values from 0 to 15. The values are as defined for the "Encryption Algorithm" in [52]. |
11.2.107 CN Domains to Handover
The CN Domains to Handover information element indicates the core network domains (CS, PS or both CS and PS) that need to be handed over.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CN Domains to Handover IEI |
octet 1 |
|||||||
Length of CN Domains to Handover value contents |
octet 2 |
|||||||
spare |
CNDH |
octet 3 |
Figure 11.2.107.1: CN Domains to Handover information element
Table 11.2.107.1: CN Domains to Handover information element
CNDH, CN Domains to Handover (octet 3) Bits 2 1 0 0 Reserved 0 1 CS domain only 1 0 PS domain only 1 1 Both CS and PS domains |
11.2.108 3G Security Capability
The 3G Security Capability information element indicates the 3G integrity protection and encryption algorithms that are supported by the MS.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
3G Security Capability IEI |
octet 1 |
|||||||
Length of 3G Security Capability value contents |
octet 2 |
|||||||
Ciphering Algorithm Capability |
octets 3, 4 |
|||||||
Integrity Protection Algorithm Capability |
octets 5, 6 |
Figure 11.2.108.1: 3G Security Capability information element
Table 11.2.108.1: 3G Security Capability information element
Ciphering Algorithm Capability The coding of this field is as specified for the Ciphering Algorithm Capability in sub-clause 10.3.3.37 in [40]. For example, octet 3 bit 1 indicates support for the UEA0 algorithm, octet 3 bit 2 indicates support for the UEA1 algorithm, etc. Integrity Protection Algorithm Capability The coding of this field is as specified for the Integrity Protection Algorithm Capability in sub-clause 10.3.3.37 in [40]. For example, octet 3 bit 1 indicates support for the UIA1 algorithm, octet 3 bit 2 indicates support for the UIA2 algorithm, etc. |
11.2.109 NAS Synchronisation Indicator
The purpose of NAS Synchronisation Indicator IE is to provide the "Speech Codec Selection" information, as described in [8], to the MS. This information element contains transparent NAS information that is transferred from the CN to the MS without interpretation in the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
NAS Synchronisation Indicator IEI |
octet 1 |
|||||||
Length of NAS Synchronisation Indicator value contents |
octet 2 |
|||||||
spare |
NSI |
octet 3 |
Figure 11.2.109.1: NAS Synchronisation Indicator information element
Table 11.2.109.1: NAS Synchronisation Indicator information element
NSI, NAS Synchronisation Indicator Value (octet 3) The coding of this field is as specified in the sub-clause "Speech Codec Selection" in [8]. The most significant bit is octet 3, bit 4. The least significant bit is octet 3, bit 1. |
11.2.110 TEID
The TEID information element identifies a GA-RRC packet transport channel tunnel endpoint.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
TEID IEI |
octet 1 |
|||||||
Length of TEID value contents |
octet 2 |
|||||||
TEID |
octet 3-6 |
Figure 11.2.110.1: TEID information element
Table 11.2.110.1: TEID information element
TEID, (octets 3-6) The MSB is octet 3 and the LSB is octet 6. |
11.2.111 UTRAN RRC Message
The UTRAN RRC Message information element contains a UTRAN RRC message to be transported using the GA-RRC protocol between the MS and the GANC.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
UTRAN RRC Message IEI |
octet 1 |
||||||||
Length of UTRAN RRC Message IE contents |
octet 2, 2a |
||||||||
UTRAN RRC Message contents, 1st octet |
octet 3 |
||||||||
UTRAN RRC Message contents, last octet |
octet n |
Figure 11.2.111.1: UTRAN RRC Message information element
11.2.112 MS Radio Access Capability
The MS Radio Access Capability information element provides the GANC with information concerning radio aspects of the mobile station.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MS Radio Access Capability IEI |
octet 1, 1a |
|||||||
Length of MS Radio Access Capability value contents |
octet 2 |
|||||||
MS RAC |
octet 3-n |
Figure 11.2.112.1: MS Radio Access Capability information element
Table 11.2.112.1: MS Radio Access Capability information element
MS RAC, (octets 3-n) The value is coded in the same way as the value part in the MS Radio Access Capability information element in TS 24.008 [8]. |
11.2.113 Handover Reporting Control
The Handover Reporting Control information element provides the MS with information concerning which cells/RATs may be reported during handover initiation..
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Handover Reporting Control IEI |
octet 1, 1a |
|||||||
Length of Handover Reporting Control value contents |
octet 2 |
|||||||
spare |
HO_3G |
HO_2G |
octet 3 |
Figure 11.2.113.1: Handover Reporting Control information element
The HO_2G and HO_3G indications specify whether a mobile may indicate a 2G (respectively 3G) cell as part of a handover initiation procedure (see sub-clauses 7.8.1, 8.14.1). If both of these bits are set to ‘1’ the mobile station shall treat these bits as set to ‘0’.
Table 11.2.113.2: HO_2G, HO_3G
HO_2G, HO_3G (octet 3, bits 1,2) |
|
0 |
MS may report cells |
1 |
MS shall not report cells |
11.2.114 Tracking Area Identity
The Tracking Area Identity (TAI) information element consists of a TAC, MNC and MCC (see [54]).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Tracking Area Identity IEI |
octet 1, 1a |
|||||||||
Length of Tracking Area Identity IE contents |
octet 2 |
|||||||||
MCC dig 2 |
MCC dig 1 |
octet 3 |
||||||||
MNC dig 3 |
MCC dig 3 |
octet 4 |
||||||||
MNC dig 2 |
MNC dig 1 |
octet 5 |
||||||||
Tracking Area Code |
octet 6-7 |
Figure 11.2.114.1: Tracking Area Identity information element
Table 11.2.114.1: Tracking Area Identity information element
Tracking Area Code, (octets 6-7) This is a 16-bit value, with the most significant bit is octet 7 bit 8 and the least significant bit is octet 8 bit 1. |
11.2.115 E-UTRAN Cell Identity
The E-UTRAN Cell Identity information element consists of a 28-bit Cell ID (see [55]).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
E-UTRAN Cell Identity IEI |
octet 1, 1a |
||||||||
Length of E-UTRAN Cell Identity IE contents |
octet 2 |
||||||||
E-UTRAN Cell ID |
octet 3-6 |
Figure 11.2.115.1: E-UTRAN Cell Identity information element
Table 11.2.115.1: E-UTRAN Cell Identity information element
E-UTRAN Cell ID, (octets 3-6) This is a 28-bit value, with the most significant bit in octet 4 bit 8 and the least significant bit in octet 7 bit 5. Octet 7 bits 1-4 are spare. |
11.2.116 E-UTRAN Camping Indicator
The E-UTRAN Camping Indicator information element is used to indicate that the MS is camped on a E-UTRAN cell.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
E-UTRAN Camping Indicator IEI |
octet 1, 1a |
||||||||
Length of E-UTRAN Camping Indicator IE contents |
octet 2 |
||||||||
ECI |
octet 3 |
Figure 11.2.116.1: E-UTRAN Camping Indicator information element
Table 11.2.116.1: E-UTRAN Camping Indicator information element
ECI, (octet 3) 0 MS is camped on a E-UTRAN cell in Normal Service state 1 MS is camped on a E-UTRAN cell in Limited Service state 2 MS is camped on a E-UTRAN cell in unknown service state 3-255 All other values are reserved. |
11.2.117 Bandwidth-efficient Mode Indicator
The Bandwidth-efficient Mode Indicator information element indicates that RFC 4867 [11] bandwidth-efficient mode shall be used for the GA-CSR traffic channel.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Bandwidth-efficient Mode Indicator IEI |
octet 1, 1a |
|||||||
Length of Bandwidth-efficient Mode Indicator value contents |
octet 2 |
|||||||
BMI |
octet 3 |
Figure 11.2.117.1: Bandwidth-efficient Mode Indicator information element
Table 11.2.117.1: Bandwidth-efficient Mode Indicator information element
BMI, Bandwidth-efficient Mode Indicator (octet 3) |
|
0 |
Reserved |
1 |
Use RFC 4867 [11] bandwidth-efficient mode |
2 to 255 |
Reserved |