5.3.2 Paging

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

5.3.2.1 General

Figure 5.3.2.1-1: Paging

The purpose of this procedure is:

– to transmit CN initiated paging information to a UE in RRC_IDLE or RRC_INACTIVE and/ or;

– to transmit RAN initiated paging information to a UE in RRC_INACTIVE and/or;

– to inform UEs in RRC_IDLE, UEs in RRC_INACTIVE and UEs in RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about a system information change and/ or;

– to inform UEs in RRC_IDLE other than NB-IoT UEs, UEs in RRC_INACTIVE and UEs in RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about an ETWS primary notification and/ or ETWS secondary notification and/ or;

– to inform UEs in RRC_IDLE other than NB-IoT UEs, UEs in RRC_INACTIVE and UEs in RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about a CMAS notification and/ or;

– to inform UEs other than NB-IoT UEs in RRC_IDLE, and other than UEs connected to 5GC about an EAB parameters modification and/ or;

– to inform UEs other than NB-IoT UEs in RRC_IDLE, and UEs in RRC_INACTIVE to perform E-UTRAN inter-frequency redistribution procedure.

The paging information of CN initiated paging is provided to upper layers, which in response may initiate RRC connection establishment, e.g. to receive an incoming call.

5.3.2.2 Initiation

E-UTRAN initiates the paging procedure by transmitting the Paging message at the UE’s paging occasion as specified in TS 36.304 [4]. E-UTRAN may address multiple UEs within a Paging message by including one PagingRecord for each UE. E-UTRAN may also indicate a change of system information, and/ or provide an ETWS notification or a CMAS notification in the Paging message.

5.3.2.3 Reception of the Paging message by the UE

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, accessType (if present) and, except for NB-IoT, the cn-Domain to the upper layers;

1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the stored fullI-RNTI:

3> if UE is configured with one or more access identities equal to 1, 2 or 11-15 applicable in the selected PLMN:

4> initiate RRC connection resume procedure in 5.3.3.2 with cause value set to ‘highProrityAccess’;

3> else:

4> initiate the RRC connection resumption procedure according to 5.3.3.2 with cause value set to ‘mt-access’;

2> else if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, accessType (if present) and the cn-Domain to the upper layers;

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause ‘other’;

1> if the UE is not configured with a DRX cycle longer than the modification period and the systemInfoModification is included; or

1> if the UE is configured with a DRX cycle longer than the modification period and the systemInfoModification-eDRX is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in 5.2.2;

1> if the etws-Indication is included and the UE is ETWS capable:

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary;

2> if the schedulingInfoList indicates that SystemInformationBlockType10 is present:

3> acquire SystemInformationBlockType10;

NOTE: If the UE is in CE, it is up to UE implementation when to start acquiring SystemInformationBlockType10.

2> if the schedulingInfoList indicates that SystemInformationBlockType11 is present:

3> acquire SystemInformationBlockType11;

1> if the cmas-Indication is included and the UE is CMAS capable:

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary as specified in 5.2.1.5;

2> if the schedulingInfoList indicates that SystemInformationBlockType12 is present:

3> acquire SystemInformationBlockType12;

1> if in RRC_IDLE, the eab-ParamModification is included and the UE is EAB capable:

2> consider previously stored SystemInformationBlockType14 as invalid;

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary as specified in 5.2.1.6;

2> re-acquire SystemInformationBlockType14 using the system information acquisition procedure as specified in 5.2.2.4;

1> if in RRC_IDLE, the redistributionIndication is included and the UE is redistribution capable:

2> perform E-UTRAN inter-frequency redistribution procedure as specified in TS 36.304 [4], clause 5.2.4.10;