Content for TS 38.300 Word version: 19.0.0

1… 4… 4.7… 5… 5.3… 5.4… 6… 6.2… 6.6… 7… 8… 9… 9.2.2… 9.2.2.5… 9.2.3… 9.2.3.2… 9.2.3.3… 9.2.4… 9.2.6… 9.3… 10… 11… 15… 15.5… 16… 16.2… 16.3… 16.4… 16.8… 16.9… 16.10… 16.12… 16.12.5… 16.12.6… 16.12.6.3 16.12.7 16.13… 16.14… 16.15… 16.18… 16.19… 16.21… 16.22 16.23… 17… 18… 19 20… 21… 22… A… B… C… G…

16.12 Sidelink Relay 16.12.1 General 16.12.2 Protocol Architecture 16.12.2.1 L2 UE-to-Network Relay 16.12.2.2 L2 UE-to-UE Relay 16.12.3 Relay Discovery 16.12.4 Relay Selection/Reselection
...

16.12 Sidelink Relay |R17| p. 206

16.12.1 General p. 206

Sidelink relay supports 5G ProSe UE-to-Network Relay (U2N Relay) function (specified in TS 23.304) to provide single/multi-hop connectivity to the network for U2N Remote UE(s). Both L2 and L3 U2N Relay architectures are supported. The L3 U2N Relay architecture is transparent to the serving NG-RAN of the U2N Relay UE, except for controlling sidelink resources. The detailed architecture and procedures for L3 U2N Relay can be found in TS 23.304.

A U2N Relay UE shall be in RRC_CONNECTED to perform relaying of unicast data.

For L2 U2N Relay operation, the following RRC state combinations are supported:

Both L2 U2N Relay UE and L2 U2N Remote UE shall be in RRC_CONNECTED to perform transmission/ reception of relayed unicast data; and
The L2 U2N Relay UE can be in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED as long as all the L2 U2N Remote UE(s) that are connected to the L2 U2N Relay UE are either in RRC_INACTIVE or in RRC_IDLE.

A single unicast link is established between one L2 U2N Relay UE and one L2 U2N Remote UE and, in case of multi-hop L2 U2N relay, between L2 U2N Relay UEs. The traffic to the NG-RAN of L2 U2N Remote UE via a given L2 U2N Relay UE and the traffic of the L2 U2N Relay UE shall be separated in different Uu RLC channels.

In multi-hop U2N Relay, U2N Remote UE refers to both the actual U2N Remote UE and the intermediate U2N Relay UE that also functions as a U2N Remote UE. The intermediate U2N Relay UE can have its own traffic acting as a U2N Remote UE simultaneously.

For L2 U2N Relay, the L2 U2N Remote UE can only be configured to use resource allocation mode 2 (as specified in clause 5.7.2 and clause 16.9.3.1) for data to be relayed.

Sidelink relay additionally supports 5G ProSe UE-to-UE Relay (U2U Relay) function (specified in TS 23.304) to provide connectivity between U2U Remote UEs. Both L2 and L3 U2U Relay architectures are supported. The L3 U2U Relay architecture is transparent to the AS layer of the U2U Relay UE. The detailed architecture and procedures for L3 U2U Relay can be found in TS 23.304.

A U2U Relay UE is used to provide coverage extension of the sidelink transmissions between two U2U Remote UEs. For the coverage extension, the U2U Remote UE can communicate with a peer U2U Remote UE(s), which are not reachable within the sidelink coverage, via the U2U Relay UE.

The U2U Relay UE and U2U Remote UE can be in any RRC state. The U2U Relay UE and the U2U Remote UEs can be in the coverage of the same or different cells or out-of-coverage. Both sidelink resource allocation modes, i.e., mode 1 and mode 2 are supported for the U2U Relay UE and U2U Remote UEs. For U2U Relay, a single PC5 unicast link is established between U2U Relay UE and each of the U2U Remote UEs. After PC5 unicast link establishment between U2U Relay UE and U2U Remote UEs, end-to-end PC5 unicast link connection establishment is performed between U2U Remote UEs. Only unicast is supported between U2U Relay UE and U2U Remote UEs.

16.12.2 Protocol Architecture p. 206

16.12.2.1 L2 UE-to-Network Relay p. 206

The protocol stacks for the user plane and control plane of single-hop L2 U2N Relay architecture are illustrated in Figure 16.12.2.1-1 and Figure 16.12.2.1-2. The protocol stacks for the user plane and control plane of multi-hop L2 U2N Relay architecture are illustrated in Figure 16.12.2.1-3 and Figure 16.12.2.1-4. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interface and Uu interface. The Uu SDAP, PDCP and RRC are terminated between L2 U2N Remote UE and gNB, while SRAP, RLC, MAC and PHY are terminated in each hop (i.e., the link between L2 U2N Remote UE and the L2 U2N Relay UE, the link between L2 U2N Relay UEs, and the link between L2 U2N Relay UE and the gNB).

For L2 U2N Relay, the SRAP sublayer over PC5 hop is only for the purpose of bearer mapping. The SRAP sublayer is not present over PC5 hop for relaying the L2 U2N Remote UE's message on BCCH and PCCH. For L2 U2N Remote UE's message on SRB0, the SRAP header is not present over PC5 hop between the U2N Remote UE and the directly connected U2N Relay UE, but the SRAP header is present over Uu hop or PC5 hop between U2N Relay UEs for both DL and UL.

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.1-1: User plane protocol stack for single-hop L2 UE-to-Network Relay

Figure 16.12.2.1-1: User plane protocol stack for single-hop L2 UE-to-Network Relay

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.1-2: Control plane protocol stack for single-hop L2 UE-to-Network Relay

Figure 16.12.2.1-2: Control plane protocol stack for single-hop L2 UE-to-Network Relay

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.1-3: User plane protocol stack for multi-hop L2 UE-to-Network Relay

Figure 16.12.2.1-3: User plane protocol stack for multi-hop L2 UE-to-Network Relay

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.1-4: Control plane protocol stack for multi-hop L2 UE-to-Network Relay

Figure 16.12.2.1-4: Control plane protocol stack for multi-hop L2 UE-to-Network Relay

For L2 U2N Relay, for uplink:

The Uu/PC5 SRAP sublayer at the U2N Relay UE performs UL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) and egress Uu/PC5 Relay RLC channels over the L2 U2N Relay UE Uu/PC5 interface. For uplink relaying traffic, the different end-to-end Uu Radio Bearers (SRBs or DRBs) of the same L2 U2N Remote UE and/or different L2 U2N Remote UEs can be multiplexed over the same egress Uu/PC5 Relay RLC channel;
The Uu/PC5 SRAP sublayer at the U2N Relay UE supports L2 U2N Remote UE identification for the UL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included in the Uu SRAP header at UL in order for gNB to correlate the received packets for the specific PDCP entity associated with the right end-to-end Uu Radio Bearer of the L2 U2N Remote UE;
The PC5 SRAP sublayer at the L2 U2N Remote UE supports UL bearer mapping between L2 U2N Remote UE end-to-end Uu Radio Bearers and egress PC5 Relay RLC channels.

For L2 U2N Relay, for downlink:

The Uu SRAP sublayer performs DL bearer mapping at gNB to map end-to-end Uu Radio Bearer (SRB, DRB) of L2 U2N Remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) into Uu Relay RLC channel. The Uu/PC5 SRAP sublayer at the U2N Relay UE performs DL bearer mapping and data multiplexing between multiple end-to-end Radio Bearers (SRBs or DRBs) of a L2 U2N Remote UE and/or different L2 U2N Remote UEs and one Uu Relay RLC channel over the L2 U2N Relay UE Uu/PC5 interface;
The Uu/PC5 SRAP sublayer at the U2N Relay UE supports L2 U2N Remote UE identification for DL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included into the Uu SRAP header by the gNB at DL for the L2 U2N Relay UE to identify the corresponding end-to-end Uu Radio Bearer(s) of L2 U2N Remote UE;
The PC5 SRAP sublayer at the L2 U2N Relay UE performs DL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE and egress PC5 Relay RLC channels;
The PC5 SRAP sublayer at the L2 U2N Remote UE correlates the received packets with the right PDCP entity associated with the given end-to-end Uu Radio Bearer of the L2 U2N Remote UE based on the identity information included in the PC5 SRAP header.

A local Remote UE ID is included in both PC5 SRAP header and Uu SRAP header. L2 U2N Relay UE is configured by the gNB with the local Remote UE ID(s) to be used in SRAP header. L2 U2N Remote UE obtains the local Remote ID from the gNB via Uu RRC messages including RRCSetup, RRCReconfiguration, RRCResume and RRCReestablishment.

The end-to-end DRB(s) or end-to-end SRB(s), except SRB0, of L2 U2N Remote UE can be multiplexed to the PC5 Relay RLC channels and Uu Relay RLC channels in both PC5 hop and Uu hop, but an end-to-end DRB and an end-to-end SRB can neither be mapped into the same PC5 Relay RLC channel nor be mapped into the same Uu Relay RLC channel.

It is the gNB responsibility to avoid collision on the usage of local Remote UE ID. The gNB can update the local Remote UE ID by sending the updated local Remote UE ID via RRCReconfiguration message. The serving gNB can perform local Remote UE ID update independent of the PC5 unicast link L2 ID update procedure.

16.12.2.2 L2 UE-to-UE Relay |R18| p. 209

The protocol stacks for the user plane and the control plane of the L2 U2U Relay architecture are illustrated in Figure 16.12.2.2-1 and Figure 16.12.2.2-2. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interfaces. The sidelink SDAP, PDCP and RRC are terminated between two L2 U2U Remote UEs (i.e., end-to-end), while SRAP, RLC, MAC and PHY are terminated in each hop of PC5 link.

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay

Figure 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay

Reproduction of 3GPP TS 38.300, Fig. 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay

Figure 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay

For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Remote UE:

The SRAP sublayer at L2 U2U Remote UE performs bearer mapping between end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the L2 U2U Remote UE and PC5 Relay RLC Channels between the L2 U2U Remote UE and the L2 U2U Relay UE.
For the traffic transmitted from an L2 U2U Remote UE to an L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) towards the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs can be multiplexed to the same PC5 Relay RLC channel between the L2 U2U Remote UE(s) and the L2 U2U Relay UE. An end-to-end SL-DRB and an end-to-end SL-SRB cannot be multiplexed to the same PC5 Relay RLC channel.
For the traffic received at L2 U2U Remote UE, the same PC5 Relay RLC channel from one L2 U2U Relay UE can be de-multiplexed to the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs.
The SRAP sublayer at L2 U2U Remote UE supports identification of the peer L2 U2U Remote UE and itself. The local IDs are assigned by L2 U2U Relay UE to both L2 U2U Remote UEs for identification. For the two local IDs, one of them identifies L2 U2U Remote UE and the other identifies the peer L2 U2U Remote UE. The local ID of the peer L2 U2U Remote UE and the local ID of L2 U2U Remote UE are delivered by L2 U2U Relay UE to the L2 U2U Remote UEs along with the corresponding L2 ID of the peer L2 U2U Remote UE. The SRAP header includes the identity information of the end-to-end PC5 Radio Bearer and two local IDs. The peer L2 U2U Remote UE matches the received packets with the specific sidelink PDCP entity with the correct end-to-end PC5 Radio Bearer of the L2 U2U Remote UEs.

For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Relay UE:

The SRAP sublayer at L2 U2U Relay UE determines the egress PC5 Relay RLC Channel based on the mapping of the end-to-end PC5 Radio Bearer and egress PC5 Relay RLC Channel for a particular pair of L2 U2U Remote UE and the peer L2 U2U Remote UE.
For the ingress traffic received from an/multiple L2 U2U Remote UE(s) at L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same L2 U2U Remote UE and/or the same/different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of L2 U2U Remote UEs can be multiplexed to the same egress PC5 Relay RLC channel in between the L2 U2U Relay UE and the peer L2 U2U Remote UE. An end-to-end SL-DRB and an end-to-end SL-SRB cannot be multiplexed to the same PC5 Relay RLC channel.

16.12.3 Relay Discovery p. 210

Model A and Model B discovery models as defined in TS 23.304 are supported for U2N/U2U Relay discovery. The protocol stack used for discovery is illustrated in Figure 16.12.3-1.

Reproduction of 3GPP TS 38.300, Fig. 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay

Figure 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay

The U2N Remote UE can perform Relay discovery message (i.e., as specified in TS 23.304) transmission and may monitor the sidelink for Relay discovery message while in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a Uu RSRP threshold, which is used by the U2N Remote UE to determine if it can transmit Relay discovery messages to U2N Relay UE(s).

The U2N Relay UE can perform Relay discovery message (i.e., as specified in TS 23.304) transmission and may monitor the sidelink for Relay discovery message while in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a maximum Uu RSRP threshold, a minimum Uu RSRP threshold, or both, which are used by the U2N Relay UE to determine if it can transmit Relay discovery messages to U2N Remote UE(s).

In multi-hop U2N relay, one U2N Relay UE establishes a PC5 connection with each of its child UE(s). One intermediate U2N Relay UE or U2N Remote UE maintains a single PC5 connection with its parent UE.

The U2U Remote UE and U2U Relay UE can perform Relay discovery message transmission or DCR/DCA message with integrated discovery transmission and may monitor for Relay discovery message or DCR/DCA message with integrated discovery while in coverage (i.e. RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED) or out-of-coverage.

The network may provide the Relay discovery configuration using broadcast or dedicated signalling. In addition, the U2N/U2U Remote UE, L3 U2N Relay UE and U2U Relay UE may use pre-configuration for Relay discovery. If the candidate intermediate U2N Relay UE is out of coverage without a PC5 connection to a parent UE, it can forward discovery messages based on pre-configuration. If the candidate intermediate U2N Relay UE is in coverage without a PC5 connection to a parent UE or out of coverage with a PC5 connection to a parent UE, it can forward discovery message based on SIB12 or dedicated configuration.

The resource pool(s) used for NR sidelink communication can be used for Relay discovery or the network may configure resource pool(s) dedicated for Relay discovery. Resource pool(s) dedicated for Relay discovery can be configured simultaneously with resource pool(s) for NR sidelink communication in system information, dedicated signalling and/or pre-configuration. Whether dedicated resource pool(s) for Relay discovery are configured is based on network implementation. If resource pool(s) dedicated for Relay discovery are configured, only those resource pool(s) dedicated for Relay discovery shall be used for Relay discovery. If only resource pool(s) for NR sidelink communication are configured, all the configured resource pool(s) can be used for Relay discovery and NR sidelink communication. Only the resource pool for NR sidelink communication is used for the DCR/DCA message with integrated discovery.

For U2N Remote UE (including both in-coverage and out of coverage cases) that has been connected to the network via single/multi-hop U2N Relay UE(s), only resource allocation mode 2 is used for Relay discovery message transmission.

For in-coverage U2N Relay UE, and for both in-coverage and out of coverage U2N Remote UEs, NR sidelink resource allocation principles are applied for Relay discovery message transmission.

For U2U Remote UE and U2U Relay UE, NR sidelink resource allocation principles, both mode 1 and mode 2, can be applied for Relay discovery message transmission.

The sidelink power control for the transmission of Relay discovery messages is same as for NR sidelink communication.

No ciphering or integrity protection in PDCP layer is applied for the Relay discovery messages.

The U2N/U2U Remote UE and U2N/U2U Relay UE can determine from SIB12 whether the gNB supports Relay discovery, or Non-Relay discovery, or both.

16.12.4 Relay Selection/Reselection p. 211

The U2N Remote UE performs radio measurements at PC5 interface and uses them for U2N Relay selection and reselection along with higher layer criteria, as specified in TS 23.304. When there is no unicast PC5 connection between the U2N Relay UE and the U2N Remote UE, the U2N Remote UE uses SD-RSRP measurements to evaluate whether PC5 link quality towards a candidate parent U2N Relay UE satisfies relay selection criterion.

For relay reselection, U2N Remote UE uses SL-RSRP measurements towards the serving U2N Relay UE for relay reselection trigger evaluation when there is data transmission from U2N Relay UE to U2N Remote UE, and it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation in case of no data transmission from U2N Relay UE to U2N Remote UE.

A U2N Relay UE is considered suitable by a U2N Remote UE in terms of radio criteria if the PC5 link quality measured by U2N Remote UE towards the U2N Relay UE exceeds configured threshold (pre-configured or provided by gNB). The U2N Remote UE searches for suitable U2N Relay UE candidates that meet all AS layer and higher layer criteria (see TS 23.304). If there are multiple such suitable U2N Relay UEs, it is up to U2N Remote UE implementation to choose one U2N Relay UE among them. For L2 U2N Relay (re)selection, the PLMN ID, NID, CAG ID and cell ID can be used as additional AS criteria.

The U2N Remote UE triggers U2N Relay selection in following cases:

Direct Uu signal strength of current serving cell of the U2N Remote UE is below a configured signal strength threshold;
Indicated by upper layer of the U2N Remote UE.

The U2N Remote UE may trigger U2N Relay reselection in following cases:

PC5 signal strength of current U2N Relay UE is below a (pre)configured signal strength threshold;
Cell reselection, handover, Uu RLF, or Uu RRC connection establishment/resume failure has been indicated by U2N Relay UE via PC5-RRC signalling;
When U2N Remote UE receives a PC5-S link release message from U2N Relay UE;
When U2N Remote UE detects PC5 RLF;
Indicated by upper layer.

For L2 U2N Remote UEs in RRC_IDLE or RRC_INACTIVE and L3 U2N Remote UEs, the cell (re)selection procedure and relay (re)selection procedure run independently. If both suitable cells and suitable U2N Relay UEs are available, it is up to the U2N Remote UE implementation to select either a cell or a U2N Relay UE. A L3 U2N Remote UE may select a cell and a L3 U2N Relay UE simultaneously and this is up to implementation of L3 U2N Remote UE.

For both L2 and L3 U2N Relay UE in RRC_IDLE or RRC_INACTIVE, the PC5-RRC message is used to inform their connected U2N Remote UE(s) or child UE(s) when U2N Relay UE selects a new cell. If the PC5-RRC message for informing is triggered by Uu/PC5 RLF, the intermediate U2N Relay UE in RRC_IDLE or RRC_INACTIVE can send the PC5-RRC message after it performs a recovery action successfully. If the recovery action is failed, it is the intermediate U2N Relay UE implementation whether to release or send the PC5-RRC message to the U2N Remote UE(s) or child UE(s). The intermediate U2N Relay UE may omit sending the PC5-RRC message if the relay reselection or cell selection does not cause the change of the serving cell. The PC5-RRC message(s) are also used to inform their connected L2 or L3 child UE(s) when L2 or L3 U2N Relay UE performs handover, detects Uu/PC5 RLF, detects its Uu RRC connection establishment/resume fails, or is released PC5 unicast link with its parent UE. Upon reception of the PC5 RRC message for notification, it is up to U2N Remote UE/intermediate U2N Relay UE implementation whether to release or keep the unicast PC5 link with its parent UE. Upon reception of the PC5 RRC message for notification, it is up to intermediate U2N Relay UE implementation whether to release or send the notification message to the child Relay UE(s). If U2N Remote UE/intermediate U2N Relay UE decides to release the unicast PC5 link, it triggers the PC5 release procedure and may perform cell or relay reselection.

For the discovery model A, the intermediate U2N Relay UE should send the discovery announcement message after PC5 connection establishes with its parent UE. There are no additional SD/SL-RSRP threshold criteria when forwarding discovery messages.

For the discovery model B, if the intermediate U2N Relay UE already has been established a PC5 connection with its parent UE, the intermediate U2N Relay UE may send a response message without forwarding the received discovery solicitation message to the parent UE. Otherwise, the intermediate Relay UE should forward the received discovery solicitation message to the candidate parent UE only when the PC5 RSRP between the child UE and itself is above a SD-RSRP threshold. Upon receiving the discovery solicitation message, a last U2N Relay UE without having a PC5 link between itself and an intermediate U2N Relay UE sends the discovery response message only when the PC5 RSRP between itself and child UE is above the SD-RSRP threshold. Upon receiving the discovery response message, the intermediate U2N Relay UE does not check the PC5 AS condition to forward the response message towards the U2N Remote UE since it assumed that the PC5 links have already been checked when the solicitation messages were forwarded. Upon receiveing the discovery response message, the U2N Remote UE considers an intermediate Relay UE(s) as a candidate first U2N Relay UE(s) along the path to the last U2N Relay UE if the PC5 RSRP towards the first U2N Relay UE is above a SD-RSRP threshold.

The U2U Remote UE performs radio measurements (i.e., SD-RSRP and/or SL-RSRP) at PC5 interface and uses them for U2U Relay selection and reselection along with higher layer criteria, as specified in TS 23.304.

For relay selection, U2U Remote UE uses SL-RSRP measurements towards the peer U2U Remote UE for relay selection trigger evaluation when valid SL-RSRP measurements are available. For relay reselection, U2U Remote UE uses SL-RSRP measurement towards the U2U Relay UE for relay reselection trigger evaluation when there is data transmission from U2U Relay UE to U2U Remote UE. It is left to U2U Remote UE implementation whether to use SL-RSRP or SD-RSRP for relay selection or reselection trigger evaluation in case of no data transmission. The thresholds for SD-RSRP and SL-RSRP can be configured separately for the trigger evaluation of U2U relay selection or reselection. The same value(s) of the SD-RSRP and SL-RSRP thresholds, which is used for relay selection or reselection, are applied for all the discovery models including DCR with integrated discovery.

The U2U Remote UE may trigger U2U Relay selection in the following cases:

When the SL-RSRP or SD-RSRP between U2U Remote UEs is below a (pre)configured signal strength threshold;
When U2U Remote UE receives an indication to trigger U2U relay selection from the upper layer of the UE.

The U2U Remote UE may trigger U2U Relay reselection in the following cases:

When the SL-RSRP or SD-RSRP of the current U2U Relay UE is below a (pre)configured signal strength threshold;
When U2U Remote UE receives an indication from the upper layer due to detecting PC5 RLF;
When L2 U2U Remote UE receives an indication from the upper layer due to receiving the PC5 RLF indication from the L2 U2U Relay UE;
When U2U Remote UE receives a PC5-S link release message from U2U Relay UE;
When U2U Remote UE receives an indication to trigger U2U relay reselection from the upper layer of the UE.

For the discovery model A, the U2U Relay UE should announce via discovery announcement message only the neighbour U2U Remote UE(s) for which the SD-RSRP/SL-RSRP between the U2U Relay and the neighbour U2U Remote UE(s) is above a configured threshold. Upon discovery message reception, U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met.

For the discovery model B, when the U2U Relay UE receives the discovery solicitation message from U2U Remote UE, the U2U Relay UE forwards the discovery solicitation message only if the SD-RSRP between the U2U Relay UE and the U2U Remote UE is above a threshold. After the peer U2U remote UE receives a discovery solicitation message from the U2U Relay UE, the peer U2U Remote UE transmits the discovery response message only if the SD-RSRP between the peer U2U Remote UE and the U2U Relay UE is above a configured threshold. Upon discovery response message reception forwarded by the U2U Relay UE, the U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met.

For the DCR message with integrated discovery, when the U2U Relay UE receives the DCR message with integrated discovery from U2U Remote UE, the U2U Relay UE forwards the DCR message with integrated discovery only if the SL-RSRP between the U2U Relay UE and the U2U Remote UE is above a configured SD-RSRP threshold (not the SL-RSRP, as broadcast is used). Upon receiving DCR message with integrated discovery from one or multiple U2U Relay UEs, the peer U2U Remote UE should consider to which received DCR message to respond amongst candidate U2U Relay UEs towards which the SL-RSRP is above a configured SD-RSRP threshold (not the SL-RSRP, as broadcast is used) and that satisfy upper-layer criteria, and select a U2U Relay UE among them.