< SI Message List struct > ::=

{ 1 < SI_MESSAGE_TYPE : bit (8) >

{ < MESS_REC : bit (2) == 00 > < null > — Message type supported but not received

| < MESS_REC : bit (2) == 01 > < null > — Message type supported and received, single instance

| < MESS_REC : bit (2) == 10 > — Message type supported and partially received, multiple instances

< SIX_CHANGE_MARK : bit (3) >

< SIX_COUNT : bit (4) >

< Instance bitmap : bit (val(SIX_COUNT) + 1) >

| < MESS_REC : bit (2) == 11 > — Message type supported and completely received, multiple
instances

< SIX_CHANGE_MARK : bit (3) > }

} ** 0

< ADDITIONAL_MSG_TYPE : bit > ;

< Unknown SI Message List struct > ::=

{ 1 < SI_MESSAGE_TYPE : bit (8) > } ** 0

< ADDITIONAL_MSG_TYPE : bit > ;

BCCH_CHANGE_MARK (3 bit field)
This field is the binary representation of the last BCCH_CHANGE_MARK received in the SI13 message on BCCH or PACCH.

Received SI Message List (construction)
This construction contains a list of supported SI messages (see sub-clause 5.5.1.4.3). The sender of this message may indicate as many messages in this list as can be fit into the message. Messages are listed by message type in descending order of priority. If there are more SI messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list.

If the sender of this message has received an SI message which is part of a consistent set of SI messages (see sub-clause 5.5.2.1.4), the Instance Bitmap may indicate which instances of this message type that have been received.

Received Unknown SI Message List (construction)
This construction contains a list of message types that are received on BCCH, which are either unknown or not recognised as supported SI message types. The sender of this message may indicate as many messages in this list as can be fit into the message following the Received SI Message List. Messages are listed by message type in the inverse order of reception, starting with the most recently received message type. If there are more messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list.

SI_MESSAGE_TYPE (8 bit field)
This field is the binary representation of the message type of the indicated SI message (see 3GPP TS 24.007 and 3GPP TS 44.018).

MESS_REC (2 bit field)
This field indicates for each message type that is supported by the mobile station whether one or more instances of the message have been received. The field is coded:

Bit

2 1

0 0 The message type is supported but not received;

0 1 The message type is supported and received; this type of SI message does not exist in multiple instances;

1 0 The message type is supported and instances of the message with the indicated change mark are partially received;

1 1 The message type is supported and all instances of the message are received with the indicated change mark.

SIX_CHANGE_MARK (3 bit field)
This field is the binary representation of the SI change mark parameter received for a certain SI message type, except for the SI2ter, the SI2quater and the SI15 message types. For the SI2ter, SI2n,, SI18, SI19 and SI20 messages, the range is: 0 to 3. For the SI2quater and SI15 messages, the range is: 0 to 7.

For the SI2ter message type, the three bits are used according to the following principles:

SI2ter
Bit
3 2 1
0 – X Bit 1: SI2ter_3G_CHANGE_MARK
0 X – Bit 2: SI2ter_MP_CHANGE_MARK.

For the SI2quater message type, the mobile station shall include the latest received values of the BA_IND, 3G_BA_IND and MP_CHANGE_MARK fields. The field is coded as follows:

Bit
3 2 1
– – X Bit 1: MP_CHANGE_MARK
– X – Bit 2: 3G_BA_IND
X – – Bit 3: BA_IND

For the SI15 message type, the mobile station shall include the three least significant bits of the DM_CHANGE_MARK parameter (i.e., DM_CHANGE_MARK modulo 8).

SIX_COUNT (4 bit field)
This field is the binary representation of the SI count parameter received for a certain SI message type. This field indicates the length of the corresponding Instance bitmap field and shall be provided only if the corresponding Instance bitmap field is provided in the message.

For SI18, SI19 and SI20 messages, this field shall be set to 7 if present.

For the SI15 message the range is 0 to 3.

For the SI2ter message the range is 0 to 7.

For the SI2quater message the range is 0 to 15.

For the SI2n message the range is 0 to 15.

Instance bitmap (1 – 16 bit field)
This field is a bitmap indicating which instances of a certain message type that are received within a consistent set of SI messages. This field shall be included when a sub-set of these messages has been received. This field shall not be included when the complete set of these messages has been received.

The most significant bit of this bitmap (bit N) refers to the message instance with the SIX index parameter = N-1, where N is the number of instances of the particular message type (SIX count + 1). The least significant bit of this bitmap (bit 1) refers to the message instance with the SI index parameter = 0. Each bit position is coded:

0 Message instance is not received;
1 Message instance is received.

ADDITIONAL_MSG_TYPE (1 bit field)
0 No additional message type is present.
1 Additional message type(s) are available, but this information does not fit in to the message.

PSCSI_SUPPORT (1 bit field)

0 PACKET SERVING CELL SI message not supported
1 PACKET SERVING CELL SI message supported

The MS shall set the PSCSI_SUPPORT bit to "1" in this revision of the specification. This field shall always be present in the PACKET SI STATUS message. If not present, ‘0’ shall be assumed by the receiver

PS_REL_REQ (1 bit field)
This field indicates whether the mobile station requests the release of the RR connection and packet resources. This field may only be set to "1" in certain cases, see 3GPP TS 44.018. This field shall always be present in the message when the enhanced DTM CS release procedure is ongoing.

0 The mobile station does not request the release of the RR connection and packet resources.
1 The mobile station requests the release of the RR connection and packet resources.