11.2.19 Packet System Information Type 2

04.603GPPGeneral Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 1999TS

This message is sent by the network on PBCCH and PACCH giving information of reference frequency lists, cell allocation, GPRS mobile allocations and PCCCH descriptions being used in the cell. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 05.02.

PSI2 also contains Non-GPRS cell options applicable for non-packet access.

This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. A consistent set of this message type is required to completely decode the information (see sub-clause 5.5.2.1.4).

Message type: PACKET SYSTEM INFORMATION TYPE 2

Direction: network to mobile station

Classification: distribution message

Table 11.2.19.1: PSI2 information elements

< PSI2 message content > ::=

< PAGE_MODE : bit (2) >

< PSI2_CHANGE_MARK : bit (2) >

< PSI2_INDEX : bit (3) >

< PSI2_COUNT : bit (3) >

{ { 0 | 1 < Cell Identification : < Cell Identification IE > > }

{ 0 | 1 < Non GPRS Cell Options : < Non GPRS Cell Options IE > > }

< Reference Frequency Lists : < Reference Frequency Lists struct > >

< Cell Allocation : < Cell Allocation Lists struct > >

< GPRS Mobile Allocations : < GPRS Mobile Allocations Lists struct > >

< PCCCH Description : < PCCCH Description Lists struct > >

{ null | 0 bit** = < no string >

| 1 — Release 1999 additions:

{ 0 | 1 < COMPACT Control Information : < COMPACT Control Info struct > > }

{ 0 | 1 < Additional PSI Messages : < Additional PSI Messages struct > > }

< padding bits > } } // — truncation at end of message allowed, bits ‘0’ assumed

! < Distribution part error : bit (*) = < no string > > ;

< Reference Frequency Lists struct > ::= { 1 < Reference Frequency struct > } ** 0;

< Reference Frequency struct >::=

< RFL_NUMBER : bit (4) >

< Length of RFL contents : bit (4) >

< RFL contents : octet (val(Length of RFL contents) + 3) > ;

< Cell Allocation Lists struct > ::= { 1 < Cell Allocation struct > } ** 0 ;

< Cell Allocation struct > ::=

< RFL_NUMBER : bit (4) > ;

< GPRS Mobile Allocations Lists struct > ::= { 1 < GPRS Mobile Allocations struct > } ** 0 ;

< GPRS Mobile Allocations struct > ::=

< MA_NUMBER : bit (4) >

< GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ;

< PCCCH Description Lists struct > ::= { 1 < PCCCH Description struct > } ** 0 ;

< PCCCH Description struct > ::=

< TSC : bit (3) >

{ 0 < Non-hopping PCCCH carriers : < Non-Hopping PCCCH Carriers Lists struct > >

| 1 < MA_NUMBER : bit (4) >

< Hopping PCCCH carriers : < Hopping PCCCH Carriers Lists struct > > } ;

< Non-hopping PCCCH Carriers Lists struct > ::= { 1 < Non-Hopping PCCCH Carriers struct > } ** 0 ;

< Non-Hopping PCCCH Carriers struct > ::=

< ARFCN : bit (10) >

< TIMESLOT_ALLOCATION : bit (8) > ;

< Hopping PCCCH Carriers Lists struct > ::= { 1< Hopping PCCCH Carriers struct > } ** 0 ;

< Hopping PCCCH Carriers struct > ::=

< MAIO : bit (6) >

< TIMESLOT_ALLOCATION : bit (8) > ;

< COMPACT Control Info struct > ::=

< Large Cell Operation : bit (1) >

{0 | 1 <Number of Idle Blocks : <Number of Idle Blocks struct> >}

{0 | 1 <N_CCCH_NH : bit (4) >} ;

<Number of Idle Blocks struct> ::=

{0 | 1 { < NIB_CCCH_0 : bit (4) > } }

{0 | 1 { < NIB_CCCH_1 : bit (4) > } }

{0 | 1 { < NIB_CCCH_2 : bit (4) > } }

{0 | 1 { < NIB_CCCH_3 : bit (4) > } } ;

< Additional PSI Messages struct > ::=

< NON_GSM_INFORMATION : bit(2) >

< PSI8_BROADCAST : bit (1) >
< PSI3ter_BROADCAST : bit (1) >

< PSI3quater_BROADCAST : bit (1) > ;

Table 11.2.19.2: PSI2 information element details

PAGE_MODE (2 bit field)
This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 04.08

PSI2_CHANGE_MARK (2 bit field)
This field is the binary representation of the PSI change mark parameter identifying a consistent set of PSI2 messages. Range: 0 to 3.

PSI2_INDEX (3 bit field) and PSI2_COUNT (3 bit field)
These fields are the binary representation of the PSI index and PSI count parameters associated with the PSI2 message.

Cell Identification
This information element is defined in sub-clause 12.23. This field shall be present in at least one instance of PSI2 and may appear only once in a complete set of PSI2 messages.

Non GPRS Cell Options
This field is defined in sub-clause 12.27.
This field shall be present in at least one instance of PSI2.

Reference Frequency Lists (construction)
This construction is the representation of the reference frequency lists provided in an instance of the PSI2 message. An RFL_NUMBER field preceding each reference frequency list (RFL) identifies the RFL.

Cell Allocations (construction)
This construction is a representation of the cell allocation (CA) defined for the cell. The set of radio frequency channels contained in the referenced RFLs in this construction defines the cell allocation.

GPRS Mobile Allocations (construction)
This construction is the representation of the GPRS mobile allocations provided in an instance of the PSI2 message. An MA_NUMBER field preceding each GPRS mobile allocation identifies the GPRS mobile allocation. The receiver shall disregard a GPRS mobile allocation provided in this message that is identified by MA_NUMBER = 14 or 15.

PCCCH Description (construction)
This construction is a representation of the timeslots carrying PCCCH in the cell and their frequency configurations. The preceding training sequence code (TSC) shall be used for each timeslot carrying PCCCH.

The number of timeslots carrying PCCCH in the cell is denoted KC. This is also the implicit value of the parameter BS_PCC_CHANS, see 3GPP TS 05.02. The range for KC is 1 to 16 if PBCCH (and PCCCH) is present in the cell. (KC = 0 if PBCCH is not present in the cell.)

The mapping of the PCCCH_GROUPs (numbered from 0 to KC-1) starts with the lowest numbered PCCCH_GROUP, which is mapped on the lowest numbered timeslot carrying PCCCH on the first (non-hopping or hopping) PCCCH carrier appearing in this construction. The next higher numbered PCCCH_GROUP is mapped on the next (if any) higher numbered timeslot carrying PCCCH on the same carrier, and so on. When all timeslots carrying PCCCH on the first carrier have been used, the next higher numbered PCCCH_GROUP is mapped on the lowest numbered timeslot carrying PCCCH on the next PCCCH carrier appearing in this construction, and so on. The highest numbered PCCCH_GROUP is mapped on the highest numbered timeslot carrying PCCCH on the last PCCCH carrier appearing in this construction.

RFL_NUMBER (4 bit field)
This field is the binary identification of an RFL provided in this message or the binary reference to such.
Range: 0 to 15.

RFL contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining an RFL provided in the PSI2 message. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List, defined in 3GPP TS 04.08. The allowed formats of the Frequency List information element are the bit map 0, 1024 range, 512 range, 256 range, 128 range and variable bit map formats.

MA_NUMBER (4 bit field)
This field is the binary identification of a GPRS Mobile Allocation provided in this message or the binary reference to such.
Range: 0 to 13. (MA_NUMBER = 14 and 15 shall not be used in this message.)

GPRS Mobile Allocation (information element)
The GPRS Mobile Allocation information element is defined in sub-clause 12.10a.

TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 05.02.
Range: 0 to 7.

ARFCN (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 05.05.
Range 0 to 1023.

MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 05.02.
Range: 0 to 63.

TIMESLOT_ALLOCATION (8 bit field)
This field indicates which timeslot are assigned as PCCCH. This field is coded as defined in sub-clause 12.18. . Note that for a CPCCCH this information shall be ignored by the MS, the CPCCCH is rotating between odd timeslots and not allocated to a specific timeslot, see 3GPP TS 05.02.

Large Cell Operation (LARGE_CELL_OP)
If this bit is set to one, the cell is in large cell operation mode (see 3GPP TS 05.02).

0 This cell is a nominal size cell
1 This cell is a large cell

NIB_CCCH_0 (4 bit field)
This field is the binary representation of the number of radio blocks that shall remain idle in time group 0 for blocks associated with CPBCCH and CPCCCH (see 3GPP TS 05.02). If this information element is not present the value 0 shall be used. Note that this information element shall not be present for the serving cell time group (e.g. if the serving cell time group is time group zero, this information element is not present, but if the serving cell time group is time group one this information element is present).

NIB_CCCH_1, NIB_CCCH_2, NIB_CCCH_3
Defined exactly as NIB_CCCH_0, except applied to time group 1, 2, and 3 respectively.

N_CCCH_NH (4 bit field)
This field is the binary representation of the amount of non-hopping blocks on control channels (see 3GPP TS 05.02).
Range 1 to 11.

Additional PSI messages struct
If any of the PSI messages named in this structure are broadcast in the cell, this field shall be present in at least one instance of PSI2 and may appear only once in a complete set of PSI2 messages.

NON_GSM_INFORMATION (2 bit field)
This field indicates whether non-GSM information is broadcast on the cell and specifies the messages that are used for this purpose. If this field indicates that both PSI6 and PSI7 are broadcast on the cell, these messages shall be broadcast within different repetition rate groups (see 3GPP TS 05.02).

Bit
2 1
0 0 non-GSM information is not broadcast on the cell
0 1 non-GSM information is broadcast on the cell in PSI6 message
1 0 non-GSM information is broadcast on the cell in PSI7 message
1 1 non-GSM information is broadcast on the cell in PSI6 and PSI7 messages

PSI8_BROADCAST (1 bit field)
0 PSI8 is not broadcast on the cell
1 PSI8 is broadcast on the cell

PSI3ter_BROADCAST (1 bit field)
0 PSI3ter is not broadcast on the cell
1 PSI3ter is broadcast on the cell

PSI3quater_BROADCAST (1 bit field)
0 PSI3quater is not broadcast on the cell
1 PSI3quaer is broadcast on the cell

11.2.19.1 Reference Frequency Lists in PSI2

A Reference Frequency Lists construction may be included in each instance of the PSI2 message. The presence of reference frequency lists (RFLs) is optional. RFLs shall be provided as required for the decoding of GPRS mobile allocations and cell allocation.

11.2.19.2 Cell Allocation in PSI2

A Cell Allocation construction shall not be included in more than one instance of the PSI2 message within the consistent set of PSI2 messages. The presence of a Cell Allocation construction is optional. It shall be provided as required for the decoding of GPRS mobile allocations and for the support of GPRS mobile stations which may access the network in dedicated, group receive and group transmit modes, see 3GPP TS 04.08.

11.2.19.3 GPRS Mobile Allocation in PSI2

A GPRS Mobile Allocations construction may be included in each instance of the PSI2 message. The presence of GPRS mobile allocations is optional. The GPRS mobile allocations shall be provided as required for determining the frequency configuration of PDCHs.

11.2.19.4 PCCCH Description

A PCCCH Description construction shall be included in one and only one instance of the PSI2 message within the consistent set of PSI2 messages.

11.2.19.5 Abnormal cases

If the receiver detects any violation against the rules for the appearance of the different constructions defined for this message within the consistent set of this message type, it may regard the contents of these messages as invalid.