9 Contents of information elements value parts
3GPP44.068Group Call Control (GCC) protocolRelease 17TS
The figures and text in this clause describe the contents of Information Elements (IE) value parts. The structure of an IE as composed of Information Element Identifier (IEI), length, and value part is defined in 3GPP TS 24.007.
9.1 Protocol Discriminator
The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007.
9.2 Transaction identifier
Bits 5 to 8 of the first octet of every message belonging to the GCC protocol contain the transaction identifier (TI). The transaction identifier and its use are defined in 3GPP TS 24.007.
9.3 Message Type
The message type IE and its use are defined in 3GPP TS 24.007. Table 9.1 defines the value part of the message type IE used in the GCC protocol.
Table 9.1: Message types for GCC
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
0 |
x |
1 |
1 |
0 |
0 |
0 |
1 |
IMMEDIATE SETUP |
|
0 |
x |
1 |
1 |
0 |
0 |
1 |
0 |
SETUP |
|
0 |
x |
1 |
1 |
0 |
0 |
1 |
1 |
CONNECT |
|
0 |
x |
1 |
1 |
0 |
1 |
0 |
0 |
TERMINATION |
|
0 |
x |
1 |
1 |
0 |
1 |
0 |
1 |
TERMINATION REQUEST |
|
0 |
x |
1 |
1 |
0 |
1 |
1 |
0 |
TERMINATION REJECT |
|
0 |
x |
1 |
1 |
1 |
0 |
0 |
0 |
STATUS |
|
0 |
x |
1 |
1 |
1 |
0 |
0 |
1 |
GET STATUS |
|
0 |
x |
1 |
1 |
1 |
0 |
1 |
0 |
SET PARAMETER |
|
0 |
x |
1 |
1 |
1 |
0 |
1 |
1 |
IMMEDIATE SETUP 2 |
Bit 8 is reserved for possible future use as an extension bit, see 3GPP TS 24.007.
Bit 7 is reserved for the send sequence number in GCC messages sent from the MS. In GCC messages sent from the network an, bit 7 is coded with a "0", see 3GPP TS 24.007.
9.4 Other information elements
For coding of other IEs, the rules defined in 3GPP TS 24.007 annex B apply.
9.4.1 Call Reference
The Call Reference information element identifies the group call reference, group identity or group identity with prefix of a group call. It is coded as shown below. It is a type 3 information element.
<call reference> ::= reference { 0 spare_4 | 1 { priority spare_1 } }
Attributes
The information element defines a reference which, depending on the situation, is to be interpreted as a group call reference, group identity, or as a group identity with prefix. If the priority field is present in <call reference>, the information element also specifies a priority.
If the Call Reference IE is included in the SETUP message and if the priority field is present in <call reference>, then the MS shall set the priority value to be the same as the priority value in the CM_SERVICE_REQUEST message.
Field contents
The field of the call reference information element are coded as shown in table 9.2.
Table 9.2: call reference information element
|
reference (27 bits) |
|||
|
This field contains the 27 bit binary encoding (with leading zeroes) of the number the decimal encoding of which (with leading zeroes) is the group call reference, the group identity (see 3GPP TS 23.003), or the group identity with prefix. |
|||
|
priority (3 bits) |
|||
|
This field encodes the priority level of the call (see 3GPP TS 23.067): |
|||
|
Bits |
|||
|
0 0 0 |
reserved |
||
|
0 0 1 |
priority level 4 |
||
|
0 1 0 |
priority level 3 |
||
|
0 1 1 |
priority level 2 |
||
|
1 0 0 |
priority level 1 |
||
|
1 0 1 |
priority level 0 |
||
|
1 1 0 |
priority level B |
||
|
1 1 1 |
priority level A |
||
|
spare_4 (4 bits) |
|||
|
This field shall be ignored |
|||
|
spare_1 (1 bit) |
|||
|
This field shall be ignored |
|||
9.4.2 Call state
The call state information element identifies a state, and, if applicable, a sub-state of the group call protocol at the MS side. It is coded as defined below. It is a type 1 information element.
<call state> ::= state
Attributes
The state field defines an integer N in the range 0..15. The call state information element defines a call state or a sub-state of state U2, ACTIVE, of the GCC protocol.
Field contents
See table 9.3.
Static conditions
The values 12 to 15 of integer N are reserved.
Table 9.3: call state information element
|
state (4 bits) |
|||
|
This field contains the 4 bit encoding (with leading zeroes) of an integer N = 0, 15. The state or substate associated to integer N is defined below: |
|||
|
N |
state |
||
|
0 |
U0 |
||
|
1 |
U1 |
||
|
2 |
U2sl |
||
|
3 |
U3 |
||
|
4 |
U4 |
||
|
5 |
U5 |
||
|
6 |
U0.p |
||
|
7 |
U2wr |
||
|
8 |
U2r |
||
|
9 |
U2ws |
||
|
10 |
U2sr |
||
|
11 |
U2nc |
||
9.4.3 Cause
The purpose of the cause information element is to describe the reason for generating certain messages and to provide diagnostic information in the event of procedural errors.
The cause information element is a type 4 information element. Its value part has a minimal length of 1 octet. The maximum length is given by the maximum number of octets in a L3 message (see 3GPP TS 44.006).
The value part is coded as shown below:
<cause > ::= 1 cause_part [ diagnostics ]
| 0 cause_part <cause>
Attributes
The cause_part field defines a non-negative integer N. If more than one cause_part fields are present in <cause>, the information element indicates an unspecific cause; otherwise, it indicates a cause as defined by N.
Field contents
The fields of the information element are coded as shown in table 9.4.
Table 9.4: cause information element
|
cause_part (7 bits) |
||
|
This field contains the 7 bit encoding (with leading zeroes) of a non-negative integer which |
||
|
specifies a cause as defined below: |
||
|
N |
cause |
|
|
3 |
Illegal MS |
|
|
5 |
IMEI not accepted |
|
|
6 |
Illegal ME |
|
|
8 |
Service not authorized |
|
|
9 |
Application not supported on the protocol |
|
|
10 |
RR connection aborted |
|
|
16 |
Normal call clearing |
|
|
17 |
Network failure |
|
|
20 |
Busy |
|
|
22 |
Congestion |
|
|
23 |
User not originator of call |
|
|
24 |
Network wants to maintain call |
|
|
30 |
Response to GET STATUS |
|
|
32 |
Service option not supported |
|
|
33 |
Requested service option not subscribed |
|
|
34 |
Service option temporarily out of order |
|
|
38 |
Call cannot be identified |
|
|
48 – 63 |
retry upon entry into a new cell |
|
|
81 |
Invalid transaction identifier value |
|
|
95 |
Semantically incorrect message |
|
|
96 |
Invalid mandatory information |
|
|
97 |
Message type non-existent or not implemented |
|
|
98 |
Message type not compatible with the protocol state |
|
|
99 |
Information element non-existent or not implemented |
|
|
100 |
Message type not compatible with the protocol state |
|
|
112 |
Protocol error, unspecified |
|
|
Any other value received shall be treated as an unspecific cause. |
||
|
Diagnostics |
||
|
This field contains a message or information element. |
||
9.4.4 Originator indication
The originator indication information element informs the group call control entity in the MS whether it is the calling user. It is a type 1 information element.
The value part is coded as shown below:
<originator indication> ::= spare_3 OI
Attributes
The IE defines whether the MS is the originator of the group call.
Field contents
The fields of the information element are coded as shown in table 9.5.
Table 9.5: originator indication information element fields
|
spare_3 (3 bits) |
||
|
This field shall be ignored. |
||
|
OI (1 bit) |
||
|
0 |
The MS is not the originator of the call |
|
|
1 |
The MS is the originator of the call |
|
9.4.5 Not used
9.4.6 Spare Half Octet
This element is used in the description of messages in clause 8 when an odd number of half octet type 1 information elements are used . This element consists of 4 bits set to zero and is placed in bits 5 to 8 of the octet unless otherwise specified. It is a type 1 information elemen t. The contents of this element shall be ignored by the receiver.
9.4.7 State attributes
The state attributes information element contains information about parameter values of the MS. It is a type 1 information element.
The value part is coded as shown below:
<state attributes> ::= DA UA COMM OI
Attributes
The IE defines values of parameters D-ATT, U-ATT, ORIG, and COMM.
Field contents
The fields of the information element are coded as shown in table 9.7.
Table 9.7: state attributes information element fields
|
DA (1 bit) |
||
|
0 |
User connection in the downlink not attached (D-ATT = F) |
|
|
1 |
User connection in the downlink attached (D-ATT = T) |
|
|
UA (1 bit) |
||
|
0 |
User connection in the uplink not attached (U-ATT = F) |
|
|
1 |
User connection in the uplink attached (U-ATT = T) |
|
|
COMM (1 bit) |
||
|
0 |
COMM = F |
|
|
1 |
COMM = T |
|
|
OI (1 bit) |
||
|
0 |
The MS is not the originator of the call (ORIG = F) |
|
|
1 |
The MS is the originator of the call (ORIG = T) |
|
9.4.8 Compressed otdi
The Compressed otdi information element specifies an integer N in 40 bit binary representation; bit 8 of octet 1 is the most significant bit and bit 1 of octet 5 is the least significant bit. The integer denotes compressed originator-to-dispatcher information. The corresponding decompressed originator-to-dispatcher information is given by the following attributes:
– User-user protocol discriminator: IA5 characters
– User-user information: The user-user information is a string of 12 digits which are the decimal representation of the integer N with leading zeros. Each digit after decompression is coded in one octet. The bits 1 to 7 are used for the coding of the IA5 character, and bit 8 is coded as "0". A coding example is given in annex A.
9.4.9 Talker priority
The Talker priority information element identifies the talker priority requested or used by the MS or the talker priority used by the network for the setup of the group call. It is a type 1 information element.
The value part is coded as shown below:
<talker priority> ::= spare_1 talker_priority
Attributes
The talker_priority field defines the talker priority requested or used by the MS or the talker priority used by the network.
Field contents
The fields of the information element are coded as shown in table 9.8.
Table 9.8: talker priority information element
|
spare_1 (1 bit) |
|||
|
This field shall be encoded as "0" and ignored by the receiver. |
|||
|
priority (3 bits) |
|||
|
This field encodes the talker priority requested or used by the MS or the talker priority used by the network. |
|||
|
Bits |
|||
|
0 0 0 |
Normal priority |
||
|
0 0 1 |
Privileged priority |
||
|
0 1 0 |
Emergency priority |
||
|
0 1 1 |
Not used (Note) |
||
|
to |
|||
|
1 1 1 |
Not used (Note) |
||
|
An MS or a network not supporting the use of talker priorities shall encode the priority as "000". |
|||
|
Note: This value shall be interpreted by the receiver as "normal priority". |
|||
9.4.10 SMS indications
The SMS indications information element informs the group call control entity in the MS whether or not SMS data confidentiality and SMS guaranteed privacy are required for mobile originated short messages (see TS 43.068 for further details). It is a type 1 information element.
The value part is coded as shown below:
<SMS indications> ::= spare_2 DC GP
Attributes
The IE defines values of parameters DC and GP.
Field contents
The fields of the information element are coded as shown in table 9.9.
Table 9.9: SMS indications information element fields
|
spare_2 (2 bits) |
||
|
This field shall be encoded as "00" and ignored by the receiver. |
||
|
DC (1 bit) |
||
|
0 |
SMS data confidentiality not required |
|
|
1 |
SMS data confidentiality required |
|
|
GP (1 bit) |
||
|
0 |
SMS guaranteed privacy not required |
|
|
1 |
SMS guaranteed privacy required |
|
Annex A (informative):
Example of the coding of the user-user information after decompression of the originator-to-dispatcher information
If the originator-to-dispatcher information after the decompression in decimal representation with leading zeros is "000000009123", then the user-user information is coded in IA5 characters as follows:
Table A.1: Example of user-user information in IA5 characters after decompression
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
content |
IA5 Code |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
1. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
2. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
3. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
4. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
5. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
6. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
7. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
8. digit: 0 |
0x30 |
|
0 |
0 |
1 |
1 |
1 |
0 |
0 |
1 |
9. digit: 9 |
0x39 |
|
0 |
0 |
1 |
1 |
0 |
0 |
0 |
1 |
10. digit: 1 |
0x31 |
|
0 |
0 |
1 |
1 |
0 |
0 |
1 |
0 |
11. digit: 2 |
0x32 |
|
0 |
0 |
1 |
1 |
0 |
0 |
1 |
1 |
12. digit: 3 |
0x33 |
Annex B (informative):
Change History
|
TSG# |
TSG doc |
WG doc |
Spec |
CR |
Rev |
Ph |
Cat |
Old vers |
New vers |
Title |
WI |
|
S#31 |
Feb 2000 |
04.68 |
7.1.0 |
8.0.0 |
Specification version upgrade to Release 1999 version 8.0.0 |
||||||
|
CN#7 |
N1-000469 |
04.68 |
A024 |
R99 |
8.0.0. |
8.1.0 |
Addition of cause values, Approved by TSGN#7 then SMG email approval before SMG#32 |
||||
|
S#32, CN#8 |
N1-000677 |
04.68 |
A025 |
R00 |
8.1.0 |
9.0.0 |
Introduction of Originator-to-dispatcher information into VGCS |
||||
|
04.68 / 44.068 |
04.68 v9.0.0 |
44.068 v4.0.0 |
Conversion to 3GPP TS format |
– |
|||||||
|
CN#9 |
NP-000449 |
N1-001006 |
44.068 |
001 |
1 |
R00 |
C |
4.0.0 |
4.1.0 |
The repetition of the priority in the Call Reference IE in the setup message |
ASCI |
|
4.1.0 |
4.1.1 |
Oct 2000: correction of references. |
|||||||||
|
NP-12 |
NP-010269 |
N1-010854 |
44.068 |
002 |
1 |
Rel-4 |
F |
4.1.1 |
4.2.0 |
Clarification of the coding of otdi information in IA5 format |
ASCI |
|
NP-16 |
NP-020224 |
N1-021368 |
44.068 |
003 |
1 |
Rel-4 |
F |
4.2.0 |
4.3.0 |
Various clean-up of wrong references, eg towards 44.018 |
TEI4 |
|
NP-16 |
44.068 |
Rel-5 |
4.3.0 |
5.0.0 |
CN plenary decision to make this TS also for Release 5. |
June 2002 |
|||||
|
44.068 |
Rel-5 |
5.0.0 |
5.0.1 |
Editorial update to remove corrupted headings and bullets |
June 2002 |
||||||
|
NP-22 |
NP-030486 |
N1-031546 |
44.068 |
004 |
Rel-6 |
C |
5.0.1 |
6.0.0 |
Clarification of the muting and unmuting of the downlink |
TEI6 |
|
|
CP-29 |
CP-050365 |
C1-050900 |
44.068 |
005 |
Rel-7 |
B |
6.0.0 |
7.0.0 |
Addition of talker prioirty |
EVGCS |
|
|
CP-33 |
CP-060464 |
C1-061467 |
44.068 |
011 |
Rel-7 |
B |
7.0.0 |
7.1.0 |
Talker Priority IEI in Termination Request Message |
EVGCS |
|
|
CP-33 |
CP-060506 |
C1-061468 |
44.068 |
012 |
Rel-7 |
F |
7.0.0 |
7.1.0 |
TC RT Increase VGCS setup timeout (MS timer TMM-est) |
TEI7 |
|
|
CP-35 |
CP-070144 |
C1-070524 |
44.068 |
014 |
1 |
Rel-7 |
B |
7.1.0 |
7.2.0 |
Addition of SMS indications in GCC Connect Message |
IVGCS |
|
CP-42 |
Rel-8 |
7.2.0 |
8.0.0 |
Upgrade to Rel-8 |
Dec 2008 |
||||||
|
CP-46 |
Rel-9 |
8.0.0 |
9.0.0 |
Upgrade to Rel-9 |
Dec 2009 |
||||||
|
CP-50 |
CP-100763 |
C1-104238 |
44.068 |
0015 |
1 |
Rel-10 |
B |
9.0.0 |
10.0.0 |
TC-RT: Introduction of group IDs with prefix |
Dec 2010 |
|
CP-57 |
Rel-11 |
10.0.0 |
11.0.0 |
Upgrade to Rel-11 |
Sept 2012 |
||||||
|
CP-65 |
Rel-12 |
11.0.0 |
12.0.0 |
Upgrade to Rel-12 |
Sept 2014 |
||||||
|
CP-70 |
Rel-13 |
12.0.0 |
13.0.0 |
Upgrade to Rel-13 |
Dec 2015 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA#80 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-06 |
SA#88e |
Update to Rel-16 version (MCC) |
16.0.0 |
||||
|
2022-04 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |