9.1.23 Paging request type 2

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

This message is sent on the CCCH by the network and may identify two mobile station and, possibly, either a third mobile station or an MBMS session. 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. Two of the mobile stations are identified by their TMSI/P-TMSI while the third is identified by its 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 3 IE, or if Mobile Identity 3 IE is not available, within the P2 Rest Octets. The remaining information pertinent to an MBMS notification may only be included within the P2 Rest Octets. See table 9.1.23.1.

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

Message type: PAGING REQUEST TYPE 2

Significance: dual

Direction: network to mobile station

Table 9.1.23.1: PAGING REQUEST TYPE 2 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 2 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	TMSI/P-TMSI 10.5.2.42	M	V	4
	Mobile Identity 2	TMSI/P-TMSI 10.5.2.42	M	V	4
17	Mobile Identity 3	Mobile Identity 10.5.1.4	O	TLV	3-10
	P2 Rest Octets	P2 Rest Octets 10.5.2.24	M	V	1-11

9.1.23.1 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.23.2 Mobile Identity 3

The Mobile Identity 3 information element shall not refer to IMEI.

9.1.23.3 P2 Rest Octets

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

This IE contains the channel needed indication related to the paging of Mobile Identity 3. The treatment of this indication in the case this message is used in a packet paging procedure is specified in sub-clause 9.1.23.1.

This IE may further contain a notification list number field and/or, referring respectively to the Mobile Identity 1 and Mobile Identity 2 IEs and, if present, Mobile Identity 3 IE, a Priority 1, 2 and 3 fields and/or, referring to the Mobile Identity 3 IE, a Packet Page Indication 3 field, or an MBMS Notification 3 field, and MBMS Information.