Section: 5.3.2.3 Reception of the Paging message by the UE or PagingRecord by the L2 U2N Remote UE
Content: 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 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; NOTE 1: If the L2 U2N Relay UE supports the MUSIM feature, it can forward the paging cause to the connected L2 U2N Remote UE. 1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message, or 1> if in RRC_INACTIVE, for 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 if mt-SDT indication was included in the paging message and if the conditions for initiating SDT for a resume procedure initiated in response to RAN paging according to 5.3.13.1b are fulfilled: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-SDT: 3> else: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-Access; NOTE 2: If both conditions for initiating MT-SDT and MO-SDT according to 5.3.13.1b are fulfilled, UE may initiate RRC connection resumption procedure for MT-SDT or MO-SDT based on implementation. NOTE 3: 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[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ]  [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> if in RRC_IDLE, 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(s) included in the pagingGroupList: 2> if the UE is not configured to receive multicast in RRC_INACTIVE or if inactiveReceptionAllowed is not included for at least one of the MBS session (s) indicated by the TMGI(s) that the UE has joined: 3> if PagingRecordList is not included in the Paging message; or 3> if none of the ue-Identity included in any of the PagingRecord matches the UE identity allocated by upper layers or the UE's stored fullI-RNTI: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set as below: 5> if the UE is configured by upper layers with Access Identity 1: 6> set resumeCause to mps-PriorityAccess; 5> else if the UE is configured by upper layers with Access Identity 2: 6> set resumeCause to mcs-PriorityAccess; 5> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15: 6> set resumeCause to highPriorityAccess; 5> else: 6> set resumeCause to mt-Access; 3> else if the ue-Identity included in any of the PagingRecord matches the UE identity allocated by upper layers: 4> forward the TMGI(s) to the upper layers; 2> else: 3> start monitoring the G-RNTI(s) corresponding to the TMGI(s), if configured; 3> if the UE was notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions that are configured for reception in RRC_INACTIVE: 4> start monitoring the Multicast MCCH-RNTI; 4> acquire the MBSMulticastConfiguration message on multicast MCCH, if present; 3> else if the UE was notified to stop monitoring the G-RNTI for at least one multicast session for which the PTM configuration was not included in RRCRelease message: 4> acquire the MBSMulticastConfiguration message on multicast MCCH; 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;