5.3.2 Paging

38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS

5.3.2.1 General

Figure 5.3.2.1-1: Paging

The purpose of this procedure is:

– to transmit paging information to a UE in RRC_IDLE or RRC_INACTIVE.

– to transmit paging information for a L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE to its serving L2 U2N Relay UE in any RRC state.

5.3.2.2 Initiation

The network initiates the paging procedure by transmitting the Paging message at the UE’s paging occasion as specified in TS 38.304 [20]. The network may address multiple UEs within a Paging message by including one PagingRecord for each UE. The network may also include one or multiple TMGI(s) in the Paging message to page UEs for specific MBS multicast session(s).

5.3.2.3 Reception of the Paging message by the UE or PagingRecord by the L2 U2N Remote UE

Upon receiving the Paging message by the UE or receiving PagingRecord from its connected L2 U2N Relay UE by a L2 U2N Remote UE, the UE shall:

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

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the UuMessageTransferSidelink message received from the connected L2 U2N Relay UE:

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

3> if upper layers indicate the support of paging cause:

4> forward the ue-Identity, accessType (if present) and paging cause (if determined) to the upper layers;

3> else:

4> forward the ue-Identity and accessType (if present) to the upper layers;

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

1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the UuMessageTransferSidelink message received from the connected L2 U2N Relay UE:

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

3> if the UE is configured by upper layers with Access Identity 1:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mps-PriorityAccess;

3> else if the UE is configured by upper layers with Access Identity 2:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mcs-PriorityAccess;

3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to highPriorityAccess;

3> else:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-Access;

NOTE: A MUSIM UE may not initiate the RRC connection resumption procedure, e.g. when it decides not to respond to the Paging message due to UE implementation constraints as specified in TS 24.501 [23].

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

3> if upper layers indicate the support of paging cause:

4> forward the ue-Identity, accessType (if present) and paging cause (if determined) to the upper layers;

3> else:

4> forward the ue-Identity and accessType (if present) to the upper layers;

3> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘other’;

1> for each TMGI included in pagingGroupList, if any, included in the Paging message:

2> if the UE has joined an MBS session indicated by the TMGI included in the pagingGroupList:

3> forward the TMGI to the upper layers;

1> if in RRC_INACTIVE and the UE has joined one or more MBS session(s) indicated by the TMGI included in the pagingGroupList; and

1> if none of the ue-Identity included in any of the PagingRecord, if included in the Paging message, matches the UE identity allocated by upper layers:

2> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set as below:

3> if the UE is configured by upper layers with Access Identity 1:

4> resumeCause is set to mps-PriorityAccess;

3> else if the UE is configured by upper layers with Access Identity 2:

4> resumeCause is set to mcs-PriorityAccess;

3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15:

4> resumeCause is set to highPriorityAccess;

3> else:

4> resumeCause is set to mt-Access.

1> if the UE is acting as a L2 U2N Relay UE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord in the Paging message matches the UE identity in sl-PagingIdentityRemoteUE included in sl-PagingInfo-RemoteUE received in RemoteUEInformationSidelink message from a L2 U2N Remote UE:

3> inititate the Uu Message transfer in sidelink to that UE as specified in 5.8.9.9;