11.2.10 Packet Paging Request

3GPP44.060General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 17TS

This message is sent on the PCCCH by the network to trigger channel access by up to four mobile stations, for either TBF or RR connection establishment. It may also be sent on PACCH to a mobile station in packet transfer mode to indicate page request for RR connection establishment. The mobile stations are identified by either IMSI, TMSI, P-TMSI or G-RNTI. Depending on the method used to identify the mobile station, 1 – 4 mobile stations can be addressed in the message. The PACKET PAGING REQUEST message may also be used to send MBMS (pre-)notifications. Special requirements for the transmission of this message on PACCH applies, see 3GPP TS 45.002. The PACKET PAGING REQUEST message may also be used to broadcast an ETWS Primary Notification message on the PCCCH. If not all information fits into one instance of the PACKET PAGING REQUEST message, the PACKET PAGING REQUEST message can be repeated.

Message type: PACKET PAGING REQUEST

Direction: network to mobile station

Classification: distribution message

Table 11.2.10.1: PACKET PAGING REQUEST message content

< Packet Paging Request message content > ::=

< PAGE_MODE : bit (2) >

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

{ 0 | 1 < NLN(PPCH) : bit (2) > }

{ { 1 < Repeated Page info : < Repeated Page info struct > > } ** 0

{ null

| 0 bit** = < no string > — Receiver compatible with earlier release

| 1 — REL-5 additions:

{ 1 < Repeated Iu Page info : < Repeated Iu Page info struct > > } ** 0

{ null | 0 bit** = < no string > — Receiver compatible with earlier release

| 1 — REL-6 additions:

{ 0 | 1 < MBMS Information > }

{ 0 | 1 < NLN status(PPCH) : bit (1) > }

{ null | 0 bit** = < no string > — Receiver compatible with earlier release

| 1 — REL-8 additions:

{ 0 | 1 < ETWS Primary Notification : < ETWS Primary Notification struct > > }

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

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

< Repeated Page info struct > ::=

{ 0 — Page request for TBF establishment

{ 0 < PTMSI : bit (32) >

| 1 < Length of Mobile Identity contents : bit (4) >

< Mobile Identity : octet (val (Length of Mobile Identity contents)) > }

| 1 — Page request for RR conn. establishment

{ 0 < TMSI : bit (32) >

| 1 < Length of Mobile Identity contents : bit (4) >

< Mobile Identity : octet (val (Length of Mobile Identity contents)) > }

< CHANNEL_NEEDED : bit (2) >

{ 0 | 1 < eMLPP_PRIORITY : bit (3) > } }

! < Ignore : bit (*) = <no string> > ;

< Repeated Iu Page info struct > ::=

{

{ 0 < G-RNTI: bit(32) > — used for a CN page to an MS in RRC connected mode, or a GERAN initiated page { 0 | 1 < Page info struct : < Page info struct > > } — only included for a CN page

| 1

{ 00 < TMSI : bit (32) >

| 01 < PTMSI : bit (32) >

| 11 { < Length of Mobile Identity contents : bit (4) >

< Mobile Identity : octet (val (Length of Mobile Identity contents)) > }

< Page info struct : < Page info struct > > }

{ 0 | 1 < eMLPP_PRIORITY : bit (3) > } }

! < Ignore : bit (*) = <no string> > ;

< MBMS Information > ::=

{

— Pre-notifications

< MBMS Sessions List : < MBMS Sessions List IE > >

— Notifications: listed per MBMS Channel Parameters

{ 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > >

< MBMS Sessions List : < MBMS Sessions List IE > > } ** 0 } }

! < Ignore : bit (*) = <no string> > ;

< Page info struct > :: =

< PAGING CAUSE : bit (3) >

< CN DOMAIN IDENTITY : bit (2) >

{ 0 | 1 < Paging Record Type Identifier : bit (2) > }; — This field Is only included if the MS is paged using a G-RNTI

< ETWS Primary Notification struct > ::=

{0 — First segment of ETWS Primary Notification, number of segments included

< Total No Of Segments For ETWS Primary Notification : bit (4) >

| 1 — Not first segment, segment number included

< Segment Number : bit (4) >

}

< PNI: bit (1) > — identifier for segments belonging to one and the same ETWS Primary Notification message

< Length Of Segment : bit (7) > — length of segment in bits

< ETWS Primary Notification Data : bit (val(Length of segment)) >;

Table 11.2.10.2: PACKET PAGING REQUEST information element details

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1…4)
This field is defined in sub-clause 12.14, PRACH Control Parameters.

NLN(PPCH) (2 bit field)
Notification List Number – This field may only be present if the message contains at least one page request for an RR connection establishment. The presence of the NLN(PPCH) field indicates that if an NCH is present, reduced NCH monitoring can be used, and gives the NLN(PPCH) value, to be used as specified in 3GPP TS 44.018.The field is coded as defined in the P1 Rest Octets information element in 3GPP TS 44.018.

NLN status(PPCH) (1 bit field)

Notification List Number status – This field may only be present if the message contains at least one page request for an RR connection establishment.The NLN status indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls, as specified in 3GPP TS 44.018. The field is coded as defined in the P1 Rest Octets information element in 3GPP TS 44.018.

Repeated Page info struct
The Repeated Page info struct is repeated as many times as required to fulfil the number of wanted paged mobiles. If the Paging Request Message is used with only P-TMSIs or TMSIs, the field can be repeated up to four times within one message. If the Paging Request Message is used with only IMSIs, the field can be repeated up to two times within one message.

The first bit in the Repeated Page info field indicates if this is a page request for TBF connection establishment or for RR connection establishment.

A page request for TBF connection establishment can either be addressed with P-TMSI or IMSI.

A page request for RR connection establishment contains a Channel Needed and optionally a Priority parameter and can either be addressed with TMSI or IMSI.

PTMSI (32 bit field)
The Packet Temporary Mobile Station Identity (PTMSI) is defined in 3GPP TS 23.003. This field is encoded as a binary number.
Range 0 to 4294967295

Mobile Identity (variable length octet string)
This octet string is the representation of the Mobile Identity. It shall provide the international mobile subscriber identity, IMSI. The encoding of this octet string is the value part (starting with octet 3) of the type 4 information element Mobile Identity defined in 3GPP TS 44.018.

Any value other than IMSI for the type of identity in this octet string is spare. Such mobile identity shall be disregarded by the receiver but any further occurrence of the Repeated Page Info struct in the message shall be analysed.

TMSI (32 bit field)
TMSI is a unique Temporary Mobile Subscriber Identity. TMSI is associated with the mobile subscriber and defined in 3GPP TS 23.003. This field is coded as a binary number.
Range 0 to 4294967295

CHANNEL_NEEDED (2 bit field)
The channel needed field indicates which type of channel is needed for the mobile station for the transaction linked to the paging procedure. The field is coded according to following table:

bit
2 1
0 0 Any channel
0 1 SDCCH
1 0 TCH/F (Full rate)
1 1 TCH/H or TCH/F (Dual rate)

eMLPP_PRIORITY (3 bit field)
The optional eMLPP_PRIORITY field relates to Mobile Station Identity i(i = 1, 2, 3, 4) and may only be present when the page relates to a paging request to trigger RR/RRC connection establishment. The eMLPP_PRIORITY field is coded as the Priority field defined in the P1 Rest Octets information element in 3GPP TS 44.018.

Repeated MBMS Notification info struct
The Repeated MBMS Notification info struct is repeated as many times as required to fulfil the number of wanted paged Temporary Mobile Groups.

The MBMS session identity is optional and shall be included whenever being made available in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU received from the SGSN.

If no counting should take place then a MBMS p-t-m channel description may be included.

If counting is requested then a MPRACH description may be included.

MBMS Sessions List
This information element contains a list of MBMS sessions identified by their TMGI and if available MBMS Session Identity. This information element is defined in sub-clause 12.39.

MBMS Channel Parameters
This information element contains the MBMS channel parameters of one or more MBMS sessions. This information element is defined in sub-clause 12.36.

Page info struct
This struct contains all information to be passed between RLC/MAC and RRC in the MS.

Repeated Iu_Page info struct
The Repeated Iu_Page info struct is repeated as many times as required to fulfil the number of wanted paged mobiles. If the PACKET PAGING REQUEST message is used with only P-TMSIs, TMSIs or G-RNTIs, the field can be repeated up to four times within one message. If the Paging Request Message is used with only IMSIs, the field can be repeated up to two times within one message.

G-RNTI (32 bits)
The G-RNTI field identifies the MS within GERAN when an RRC connection exists between this MS and GERAN.

PAGING RECORD TYPE IDENTIFIER (2 bits field)
The Paging Record Type Identifier field indicates the type of identity used in the core network page. This field shall be included in the message if the MS is identified in the page with a G-RNTI

bit
2 1
0 0 IMSI (GSM-MAP)
0 1 TMSI (GSM-MAP) / P-TMSI
1 0 IMSI (DS-41)
1 1 TMSI (DS-41)

CN DOMAIN IDENTITY (2 bit field)
The CN Domain Identity field indicates the domain of the core network from which the MS is paged.

Bit

2 1

0 0 CS domain

0 1 PS domain

1 0 Either

1 1 Reserved

PAGING CAUSE (3 bits field)
The Paging Cause field indicates the cause for paging.

bit
3 2 1
0 0 0 Terminating Conversational Call
0 0 1 Terminating Streaming Call
0 1 0 Terminating Interactive Call
0 1 1 Terminating Background Call
1 0 0 Terminating High Priority Signalling
1 0 1 Terminating Low Priority Signalling
1 1 0 Terminating – cause unknown
1 1 1 Reserved

Total No Of Segments For ETWS Primary Notification (4 bits)
This field contains the number of segments for the ETWS Primary Notification message.

Bits

4 3 2 1

0 0 0 0 reserved

0 0 0 1 one segment

0 0 1 0 two segments

. . .

0 0 1 0 fifteen segments

Segment Number (4 bits)
This field contains the Segment Number of the ETWS Primary Notification message.

Bits

4 3 2 1

0 0 0 0 reserved

0 0 0 1 reserved

0 0 1 0 second segment

0 0 1 1 third segment

. . .

0 0 1 1 fifteenth segment

PNI, Primary Notification Identifier (1 bit)
This field is used as an identifier to determine the set of segments belonging to a certain ETWS Primary Notification message. This information element will have the same value (0 or 1) for all segments belonging to the same ETWS Primary Notification message.

Length Of Segment (7 bits)
This field indicates the length of a segment in number of bits.

ETWS Primary Notification Data (n*8 bits)
The ETWS Primary Notification data is coded as specified in 3GPP TS 23.041.