Section: 5.8.9.10.4 Actions related to reception of NotificationMessageSidelink message
Content: Upon receiving the NotificationMessageSidelink, the Remote UE shall: 1> if the UE is acting as U2N Remote UE: 2> if the indicationType is included: 3> if the UE is L2 U2N Remote UE in RRC_CONNECTED: 4> if MP is configured and MCG transmission (i.e. direct path) is not suspended; 5> initiate the indirect path failure information procedure as specified in 5. 7. 3c to report indirect path failure; 4> else if T301 is not running, initiate the RRC connection re-establishment procedure as specified in 5.3.7; 3> else (the UE is L3 U2N Remote UE, or L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE): 4> if the PC5-RRC connection with the U2N Relay UE is determined to be released: 5> indicate upper layers to trigger PC5 unicast link release; 4> else (i.e., maintain the PC5 RRC connection): 5> if the UE is L2 U2N Remote UE and the indicationType is relayUE-HO or relayUE-CellReselection: 6> consider cell re-selection occurs; NOTE 1: For L3 U2N Remote UE, or L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE, it is up to Remote UE implementation whether to release or keep the PC5 unicast link. NOTE 2: The L2 U2N Remote UE may ignore the NotificationMessageSidelink if it does not release the PC5 unicast link in source side yet during an indirect-to-direct path switch, i.e. T304 is running. 1> if the UE is acting as L2 U2U Remote UE: 2> if sl-IndicationType is relayUE-PC5-RLF: 3> indicate PC5 RLF received from L2 U2U Relay UE to the upper layers for the indicated L2 U2U Remote UE based on the received sl-DestinationIdentityRemoteUE; 3> perform PC5 RLF related actions as specified in 5.8.9.3, for the indicated L2 U2U Remote UE based on the received sl-DestinationIdentityRemoteUE; NOTE 3: It is up to the upper layers on whether to trigger U2U Relay reselection and whether to keep or release the PC5 link with the U2U Relay UE after the PC5 RLF indication received from U2U Relay UE.