9.1.22 Paging request type 1

3GPP44.018GSM/EDGE Radio Resource Control (RRC) protocolMobile radio interface Layer 3 specificationRelease 17TS

This message is sent on the CCCH by the network and may identify up to two mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure) or to perform an MBMS pre-notification or an MBMS notification. It may be sent to mobile stations in idle mode to transfer the segments of an ETWS Primary Notification message. The mobile stations are identified by their TMSI/P-TMSI or IMSI. If an MBMS (pre)notification is included in this message, the corresponding TMGI and, if available, MBMS Session Identity shall be included within Mobile Identity 1 or 2 IEs, or if Mobile Identity 1 and 2 IEs are not available, within the P1 Rest Octets. The remaining information pertinent to an MBMS notification may only be included within the P1 Rest Octets. See table 9.1.22.1.

The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the P1 Rest Octets and L2 Pseudo Length information elements.

The P1 Rest Octets may contain a notification for a VGCS/VBS call or a segment of an ETWS Primary Notification message.

It is possible in the case of a notification for a ciphered VGCS/VBS call that the notification cannot be described within one message. When the notification is segmented across two messages, the first message shall contain the group channel description whilst the second message can be used to contain the group call reference, the VSTK_RAND and possibly the CELL_GLOBAL_COUNT. The second message shall be sent at the next but one PCH block after the PCH block containing the first message.

Message type: PAGING REQUEST TYPE 1

Significance: dual

Direction: network to mobile station

Table 9.1.22.1: PAGING REQUEST TYPE 1 message content

IEI

Information element

Type / Reference

Presence

Format

length

L2 Pseudo Length

L2 Pseudo Length
10.5.2.19

M

V

1

RR management Protocol Discriminator

Protocol Discriminator
10.2

M

V

1/2

Skip Indicator

Skip Indicator
10.3.1

M

V

1/2

Paging Request Type 1 Message Type

Message Type
10.4

M

V

1

Page Mode

Page Mode
10.5.2.26

M

V

1/2

Channels Needed for Mobiles 1 and 2

Channel Needed
10.5.2.8

M

V

1/2

Mobile Identity 1

Mobile Identity
10.5.1.4

M

LV

2-9

17

Mobile Identity 2

Mobile Identity
10.5.1.4

O

TLV

3-10

P1 Rest Octets

P1 Rest Octets
10.5.2.23

M

V

0-17

9.1.22.1 Unnecessary IE

A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the Page Mode IE.

9.1.22.2 Channels needed for Mobiles 1 and 2

The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of Channel Needed IE is associated with Mobile Identity 2.

If this message is used in the packet paging procedure, the Channel Needed IE associated with the corresponding Mobile Identity 1 or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message.

9.1.22.3 Mobile Identities

The Mobile Identity 1 and 2 IEs shall not refer to IMEI.

9.1.22.4 P1 Rest Octets

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

This IE may contain a notification list number field and/or, referring respectively to the Mobile Identity 1 IE and, if present, to the Mobile Identity 2 IE, a Priority 1 and a Priority 2 field(s), and/or a Packet Page Indication 1 and a Packet Page Indication 2 field(s), or an MBMS Notification 1 and/or an MBMS Notification 2 field(s), and MBMS Information, or a segment of an ETWS Primary Notification message.