Relay node identifier update

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a network entity may receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier. The network entity may configure a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for a relay node identifier update.

BACKGROUND

SUMMARY

In some aspects, a method of wireless communication performed by a network entity includes receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configuring and supporting a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

In some aspects, a method of wireless communication performed by a relay node includes transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; transmitting, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and establishing a relay service using the link layer identifier.

In some aspects, an apparatus of a network entity for wireless communication includes a memory, and one or more processors, coupled to the memory, configured to: receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configure and support a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

In some aspects, an apparatus of a relay node for wireless communication includes a memory, and one or more processors, coupled to the memory, configured to: transmit a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; transmit, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and establish a relay service using the link layer identifier.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network entity, cause the network entity to: receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configure and support a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a relay node, cause the relay node to: transmit a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; transmit, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and establish a relay service using the link layer identifier.

In some aspects, an apparatus for wireless communication includes means for receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and means for configuring and supporting a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

In some aspects, an apparatus for wireless communication includes means for transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the apparatus; means for transmitting, to a network entity via a radio access link, information indicating the link layer identifier of the apparatus; and means for establishing a relay service using the link layer identifier.

DETAILED DESCRIPTION

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU). “Network entity” or “network node” can refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may transmit a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; transmit, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and establish a relay service using the link layer identifier. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a network entity such as the base station110or a network entity of the base station110may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configure and support a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, a network entity (e.g., BS110, an NG-RAN node, a CU, a DU, an RU) includes means for receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and/or means for configuring and supporting a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

In some aspects, the relay node (e.g., UE120, an IAB node) includes means for transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; means for transmitting, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and/or means for establishing a relay service using the link layer identifier. In some aspects, the means for the relay node to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, antenna234, modem232, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246. In some aspects, the means for the relay node to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

FIG.3is a diagram illustrating an example of a control-plane protocol architecture300for a Layer 2 UE-to-network relay, in accordance with the present disclosure.FIG.4is a diagram illustrating an example of a user-plane protocol architecture400for a Layer 2 UE-to-network relay, in accordance with the present disclosure. For example, the control-plane protocol architecture300and the user-plane protocol architecture400may correspond to a remote UE (e.g., UE120) shown by reference numbers305and405and a relay UE (e.g., UE120) shown by reference numbers310and410.

FIGS.3and4illustrate examples of protocol architectures relating to sidelink communication between UEs, such as PC5 interface based communication. However, it should be understood that the techniques described herein can be applied for other forms of relay based communication, such as a relaying service via a Bluetooth (BT) connection, a WiFi connection, a device-to-device (D2D) connection, a peer-to-peer (P2P) connection, or the like.

As shown inFIG.3, in the control-plane, there may be a PC5 interface (e.g., a sidelink interface) between the remote UE and the relay UE, a Uu interface between the relay UE and a next generation radio access network (NG-RAN), also referred to herein as a 5G access network (5G-AN), an N2 interface between the NG-RAN and an access and mobility management function (AMF) of the control-plane protocol architecture300, and an N11 interface between the AMF and a session management function (SMF).

As shown inFIG.4, there may be an N3 interface between the NG-RAN and a user-plane function (UPF) of the user-plane protocol architecture400, and an N6 interface between the UPF and a core network (CNW).

As further shown, the remote UE and the relay UE may be associated with respective PC5 protocol stacks315/320and415/420, enabling communication on the PC5 interface between the remote UE and the relay UE. The PC5 protocol stack may include a PC5 radio link control (RLC) component, a PC5 medium access control (MAC) component, a PC5 physical (PHY) component, and/or the like. “PC5” is generally referred to herein as “sidelink” (e.g., sidelink signaling interfaces, sidelink unicast link, sidelink RLC channels, and/or the like). Communications between the remote UE and the relay UE using the PC5 interface may be referred to as sidelink communications. The respective PC5 protocol stacks may be associated with one or more of PC5-S entities, PC5-radio resource control (RRC) entities, or PC5 packet-data convergence protocol (PDCP) entities, as shown by reference number325. The PC5-S entity may manage a sidelink signaling interface, such as a PC5-S interface. A UE that includes a PC5-S entity and/or a PC5-RRC entity may handle control signaling and configuration of a sidelink connection with another UE, such as the connection used for relaying between the remote UE and the relay UE. In some aspects, the PC5 protocol stacks315/320and415/420may not include PC5-S entities or PC5-RRC entities. Also, in some cases, the NG-RAN may handle control signaling and configuration of the sidelink connection.

As shown by reference number330ofFIG.3, the remote UE is associated with a non-access stratum (NAS) stack, which includes an NAS session management (NAS-SM) component, an NAS session management (NAS-SM) component, and one or more radio access components (e.g., an NR-RRC component and an NR-PDCP component). As shown by reference number335ofFIG.3, the relay UE is associated with a radio access stack, including an NR-RLC component, an NR-MAC component, and an NR-PHY component. Furthermore, the NG-RAN is associated with a radio access interface stack shown by reference number340, which includes an NR-RLC component, an NR-MAC component, an NR-PHY component, an NR-RRC entity, and an NR-PDCP entity.

The adaptation layer entity of the relay UE, shown by reference number345, may handle relaying from the remote UE to the network or from the network to the remote UE. As used herein, “the network” may refer to any one or more of the NG-RAN, the AMF, the SMF, the UPF, or the core network (CNW). The CNW may be referred to as a 5G core (5GC). In some aspects, the adaptation layer is referred to as an adaptation layer entity. In some aspects, the adaptation layer entity may be a separate entity between a radio link control (RLC) entity and a packet data convergence entity. In some aspects, the adaptation layer entity may be logically part of the packet data convergence entity or the radio link control entity

Communication between stacks of the remote UE is indicated by the lines shown by reference number350. The line between the NR-PDCP entity and the PC5-RLC entity indicates how a message (e.g., an NR RRC message generated by the radio access protocol stack) that is not encapsulated in a sidelink signaling container, such as a PC5-S container, might be communicated from the radio access stack to the PC5 stack for transmission via the sidelink interface, or how a message that is not encapsulated in a PC5-S container might be communicated from the PC5 stack to the radio access stack after being received via the sidelink interface. Note that the line between the NR-PDCP entity and the PC5-RLC entity does not involve the PC5-S or PC5-PDCP entities, meaning that the PC5-S and PC5-PDCP entities do not handle such messages. A similar line is shown to indicate communication between the adaptation layer and the PC5-RLC entity that bypasses the PC5-S and PC5-PDCP entities of the relay UE.

The line between the NR-PDCP entity and the PC5-S or PC5-RRC entity indicates how a message (e.g., an NR RRC message generated by the radio access protocol stack) that is encapsulated in a PC5-S container might be communicated from the radio access stack to the PC5 stack for transmission via the sidelink interface, or how a message that is encapsulated in a PC5-S container might be communicated from the PC5 stack to the radio access stack after being received via the sidelink interface. Note that the line between the NR-PDCP entity and the PC5-RLC entity involves the PC5-S entity, meaning that the PC5-S entity may handle such messages.

As shown by reference number425ofFIG.4, the remote UE is associated with a user-plane protocol stack, which may include an application (APP) component, a protocol data unit (PDU) component, an NR service data adaptation protocol (SDAP) component, and an NR-PDCP component. Furthermore, the NG-RAN is associated with user-plane components shown by reference number430, which include an NR-SDAP component and an NR-PDCP component. The NR-SDAP component and the NR-PDCP component may be referred to herein as radio access entities.

NR user-plane traffic (shown by a line indicated by “NR UP”) may be transported between the NR-PDCP entity and the PC5-RLC component, as shown by reference number435. Such NR user-plane traffic may be transported to the relay UE via one or more bearers, such as a data radio bearer (DRB) or signaling radio bearer (SRB). DRBs and SRBs can also be referred to as radio bearers or radio access bearers. As shown by reference number440, the NR user-plane traffic may be provided from the PC5 stack of the relay UE to the adaptation component, and from the adaptation component to the radio access stack of the relay UE. The radio access stack of the relay UE may provide the NR user-plane traffic to the NG-RAN (not shown).

The physical layer may offer, to the MAC sublayer, transport channels. The MAC sublayer may offer, to the RLC sublayer, logical channels. The RLC sublayer may offer, to the PDCP sublayer, RLC channels. The PDCP sublayer may offer, to the SDAP sublayer, radio bearers. The SDAP sublayer may offer, to the CNW, QoS flows. The RAP layer may handle the mapping of these types of flows, channels, and bearers to each other to facilitate Layer 2 relay services, as described elsewhere herein. In some aspects, the RAP layer may be referred to as an adaptation layer, a relay adaption layer, and/or the like. A radio access bearer may include an SRB, a DRB, and/or the like. An RLC channel can also be referred to as an RLC bearer. In such a case, an RLC channel identifier associated with the RLC channel may be referred to as an RLC bearer identifier. Techniques described herein enable the selection of an identifier by the relay UE310for a relay service between the relay UE310and the remote UE305. The identifier may be a link layer identifier. A link layer identifier is an identifier of a node that is used in a layer associated with a relay service. For example, for a Layer 2 relay service associated with a PC5 interface, the link layer identifier may be a UE identifier, such as a source Layer 2 identifier for ProSe direct discovery self-selected by the relay UE310. For a relay service associated with a WiFi interface, a BT interface, a D2D interface, or a P2P interface, the link layer identifier may be a MAC based identifier, as described elsewhere herein. Techniques described herein also enable the relay UE310to signal (such as via RRC signaling by an NR-RRC entity of the relay UE310, which is not shown inFIG.3) the self-selected link layer identifier to the NG-RAN such that the NG-RAN can maintain a mapping of the link layer identifier to a Uu layer identifier of the relay UE310.

As indicated above,FIGS.3and4are provided as examples. Other examples may differ from what is described with respect toFIGS.3and4.

A network node referred to herein as a relay node (which may include a relay UE, an integrated access and backhaul (IAB) node, or the like) may relay communications from a remote node (which may include a UE, an IAB node, or the like) to a network or from the network to the remote UE. In some aspects, the relay node may perform Layer 2 UE-to-network relaying, in which an adaptation layer in the Layer 2 stack of the relay node performs forwarding of the remote node communications, as compared to Layer 3 relaying which may occur in the Internet Protocol (IP) layer. Communications between the relay node and the remote node, when both of these nodes are UEs, may be referred to herein as sidelink communications. Relaying can also be performed via BT, WiFi, P2P communication, or D2D communication, as some examples.

As described above, the relay node may select a link layer identifier. The link layer identifier may be used for discovery of the relay node, as well as configuration and support of a relay service between the remote node and the base station via the relay node. For example, the relay node may transmit the link layer identifier to the remote node in a discovery message. The remote node may report the link layer identifier of a selected relay node to the base station, such as in a measurement report. The base station may be aware of a radio access (e.g., Uu) identifier of the relay node, such as a cell-specific radio network temporary identifier (C-RNTI), an inactive radio network temporary identifier (I-RNTI), or the like. However, the base station may not be aware of the link layer identifier. Without the link layer identifier of the selected relay node, the base station is not capable of interpreting the measurement report, which means the base station cannot support mobility for the remote UE in the context of a relay service. Thus, configuration and support of the relay service may fail, which reduces throughput and coverage of the wireless network.

Some techniques and apparatuses described herein enable signaling of a link layer identifier from a relay node to a base station to support a relay service. For example, the relay node may signal a link layer identifier, selected by the relay node, to the base station. In some aspects, the relay node may signal information indicating a relay service associated with the link layer identifier, such as a relay service code. The relay node may also transmit the link layer identifier via a discovery message for a relay service. The base station may maintain a mapping of a link layer identifier associated with the relay node and a radio access identifier associated with the relay node. The base station may use the mapping to identify the relay node radio access connection associated with the link layer identifier reported by the remote UE. The base station may use this mapping during the remote node mobility handling to inform the remote node on the selected relay node link layer identifier and to prepare the target base station using the relay node radio access connection information corresponding to the mapped radio access identifier of the relay node. In this way, the relay node may support a relay service by notifying the base station of the relay node's self-selected link layer identifier. The base station may maintain a mapping of link layer identifiers and radio access identifiers, and may use this mapping to configure and support a relay service. Thus, mobility operations associated with relay services can be supported, which increases throughput and coverage of the wireless network.

FIG.5is a diagram illustrating an example500of signaling associated with providing a link layer identifier to support a relay service, in accordance with the present disclosure. As shown, example500includes a remote node (e.g., UE120, base station110, an IAB node, remote UE305), a relay node (e.g., UE120, base station110, an IAB node, relay UE310), and a network entity (e.g., BS110, an NG-RAN node).

As shown by reference number505, the remote node and the network entity may communicate uplink and/or downlink data with each other. For example, the remote node and the network entity may have a connection, such as an RRC connection, a radio access connection (e.g., a Uu connection), or the like. The remote node and the network entity may communicate via a radio access link, such as associated with a 5G/NR RAT or another form of RAT.

As shown by reference number510, the network entity may configure a measurement configuration for the remote node. The measurement configuration may indicate how to perform and report measurements associated with mobility, such as mobility associated with configuring a relay service with a relay node. In some aspects, the measurement configuration may indicate how to measure and report discovery messages transmitted by relay nodes. For example, the measurement configuration may relate to reporting a selected relay node based at least in part on a measurement associated with a discovery message transmitted by the selected relay node, as described below.

As shown by reference number515, a relay node may provide a link layer identifier to the network entity. In some aspects, the relay node may provide the link layer identifier in connection with relay discovery initiation, as described in connection withFIG.6. In some aspects, the relay node may provide the link layer identifier in connection with relay discovery updating or disabling, as described in connection withFIG.7. In some aspects, the relay node may provide the link layer identifier via a radio access message, such as an RRC message (e.g., a SidelinkUEInformationNR message or another form of RRC message).

The link layer identifier may be selected (e.g., self-selected, generated, determined) by the relay node. In some aspects, such as when a relay service supported by the relay node uses a sidelink interface, the link layer identifier may be a source Layer 2 identifier used for discovery message transmission by the relay node. In some aspects, a relay service supported by the relay node uses a BT connection, a WiFi connection, a P2P connection, or a D2D connection. In such aspects, the link layer identifier may be at least a MAC address associated with the relay node. For example, the link layer identifier may be a MAC address, or may be a combination (e.g., a hash) of a MAC address and a relay service code associated with a relay service associated with the link layer identifier.

In some aspects, the link layer identifier may be associated with (e.g., correspond to) a relay service. For example, the link layer identifier may correspond to a relay service code or a connection (e.g., a relay connection) that the relay node supports. In some aspects, the relay node may provide multiple link layer identifiers (such as a list of link layer identifiers). For example, if the relay node supports multiple relay services, the relay node may provide a plurality of link layer identifiers, and may provide information indicating one or more relay service codes associated with the plurality of link layer identifiers. In such a case, link layer identifiers and relay service codes may be associated with each other on a one-to-one basis, a one-to-many basis, a many-to-one basis, or a many-to-many basis.

The network entity may receive the link layer identifier from the relay node. The network entity may store or generate information indicating a mapping between the link layer identifier and a radio access identifier of the relay node. For example, the mapping may indicate that the link layer identifier of the relay node is associated with a given relay service code (provided by the relay node or known to the network entity) and a radio access identifier (such as a C-RNTI or an I-RNTI). In some aspects, the network entity may associate one or more link layer identifiers and one or more radio access identifiers. For example, link layer identifiers may be mapped to radio access identifiers on a one-to-one basis, a many-to-one basis, a one-to-many basis, or a many-to-many basis.

As shown by reference number520, the relay node may transmit a discovery message. The discovery message may indicate the link layer identifier and a relay service associated with the link layer identifier, such as a relay service code. In some aspects, the discovery message may include information associated with discovery for a relay service, such as a reference signal or a sequence that can be measured by the remote node.

As shown by reference number525, the remote node may select the relay node for a relay service. For example, the remote node may receive the discovery message indicating the link layer identifier. The remote node may perform a measurement on the discovery message based at least in part on the measurement configuration. The remote node may determine that the relay node is a candidate relay node for establishing a connection associated with a relay service based at least in part on the measurement configuration. For example, the remote node may determine that the measurement satisfies a condition indicated by the measurement configuration, such as one or more higher layer criteria indicated by the measurement configuration.

As shown by reference number530, the remote node may transmit a measurement report. The measurement report may indicate the relay node that was selected for the relay service. For example, the remote node may report one or more candidate relay nodes after the remote node measures and discovers the one or more candidate relay nodes. In some aspects, the remote node may filter the measurement report to identify the appropriate relay nodes meeting higher layer criteria indicated by the measurement configuration. In some aspects, the measurement report may identify the link layer identifier and measurement information associated with the link layer identifier, such as a sidelink reference signal received power (SL RSRP) (in some examples, a sidelink discovery RSRP (SD-RSRP)) or the like.

As shown by reference number535, the network entity may determine to switch the remote node to the relay node identified by the measurement report. For example, the network entity may determine to switch the remote node to the relay node for the relay service associated with the relay node based at least in part on the measurement information. This may be considered a mobility operation for the remote node in which a connection with the relay node is configured or updated.

As shown by reference number540, the network entity may reconfigure the relay node to support the relay service. For example, the network entity may transmit configuration information to the relay node associated with configuring the relay service (e.g., configuring a connection with the remote node for the relay service). If the relay node is connected to a different network entity, the source network entity may prepare the target network entity for relaying using the relay node radio access connection information corresponding to the relay node radio access identifier. The target network entity may transmit the configuration information to the relay node associated with configuring a connection with the remote node for the relay service. As another example, the configuration information may relate to relaying traffic between the remote node and the network entity, such as a mapping between one or more channels, bearers, or traffic flows of the remote node and one or more channels, bearers, or traffic flows of the network entity. The reconfiguration shown by reference number540may include a reconfiguration message transmitted from the source network entity to the relay node, which may include the target network entity reconfiguration message, and a reconfiguration complete message transmitted from the relay node to the source or target network entity.

As shown by reference number545, the network entity may transmit configuration information to the remote node. For example, the network entity may transmit the configuration information via the radio access connection with the remote node. The configuration information may include information associated with establishing the relay service between the relay node and the remote node. For example, the configuration information may indicate the link layer identifier, a relay service code associated with the relay service, a mobility trigger indicating to establish a connection with the relay node, or the like. Thus, the network entity may configure the relay service with the relay node and the remote node (by reconfiguring the relay node, as shown by reference number540, and the remote node, as shown by reference number545).

The network entity may configure the relay service based at least in part on the mapping between the link layer identifier provided by the relay node as shown by reference number520and a radio access identifier associated with the relay node, as described elsewhere herein. For example, the network entity may configure communications between the network entity and the relay node that use the radio access identifier, to be mapped at the relay node to communications between the relay node and the remote node that use the link layer identifier. As another example, the network entity may configure an adaptation layer of the relay node such that communications associated with the radio access identifier of the relay node and the relay service code associated with the relay service are mapped to an appropriate link layer identifier for forwarding between the remote node and the network entity.

As shown by reference number550, the remote node and the relay node may establish a connection with each other. For example, the remote node and the relay node may establish the connection if a connection does not already exist between the remote node and the relay node. In some aspects, the remote node and the relay node may establish the connection based at least in part on the configuration information shown by reference numbers540and545. The connection between the remote node and the relay node may be a PC5 connection, a D2D connection, a P2P connection, a WiFi connection, a BT connection, or another form of connection between the relay node and the remote node.

As shown by reference number555, the remote node may transmit a reconfiguration complete message to the network entity. For example, the reconfiguration complete message may be relayed via the relay node, as indicated by the circle at the relay node. The reconfiguration complete message may indicate that the connection shown by reference number550has been established and that data communication via the relay node can commence. Thus, the relay node and the remote node may establish a relay service. In some aspects, “establishing a relay service” may include establishing a connection associated with a relay service, as described in connection with reference number550. In some aspects, “establishing a relay service” may include performing or relaying data communications in connection with a relay service, as shown by reference number560. For example, the remote UE may perform data communication with the network entity via the relay node.

FIG.6is a diagram illustrating an example600of signaling associated with providing a link layer identifier to support a relay service in connection with initiating discovery, in accordance with the present disclosure. As shown, example600includes a remote node (e.g., UE120, base station110, an IAB node, remote UE305), a relay node (e.g., UE120, base station110, an IAB node, relay UE310), and a network entity (e.g., BS110, an NG-RAN node).

As shown by reference number610, the relay node may determine to support a relay service. For example, the relay node may determine to support Layer 2 relaying and, thus, to initiate discovery for the relay service. Accordingly, as shown by reference number620, the relay node may provide via an NR RRC message (e.g. SidelinkUEInformationNR (SUI) or other RRC message) that indicates one or more link layer identifiers of the relay node. For example, the one or more link layer identifiers may be selected by the relay node. In some aspects, the message shown by reference number620may include information indicating one or more relay services associated with the one or more link layer identifiers, as described in connection withFIG.5. As shown by reference number630, the relay node may transmit a discovery message including the link layer identifier. Thus, the link layer identifier broadcasted in the discovery message has been reported to the network entity, which enables the network entity to identify the relay node associated with the link layer identifier if the remote node reports the relay node as a candidate relay node for a relaying service.

As shown by reference number640, the network entity may maintain a mapping between one or more relay node Uu identifiers (that is, one or more radio access identifiers of the relay node) and one or more relay node link layer identifiers (that is, the one or more link layer identifiers transmitted to the network entity, as shown by reference number620). For example, the network entity may add, to a table, information indicating a link layer identifier, a corresponding relay service code, and a corresponding radio access identifier, if such information is received (such as in connection with the relay node determining to support a relay service).

FIG.7is a diagram illustrating an example700of signaling associated with providing a link layer identifier to support a relay service in connection with updating or disabling the relay service, in accordance with the present disclosure. As shown, example700includes a remote node (e.g., UE120, base station110, an IAB node, remote UE305), a relay node (e.g., UE120, base station110, an IAB node, relay UE310), and a network entity (e.g., BS110, an NG-RAN node).

As shown by reference number710, the relay node may determine to update a link layer identifier associated with a relay service (referred to herein as a link layer identifier update). In some examples, the link layer identifier update can be for maintaining privacy of the service or detecting a conflict with any other UE chosen identifier. As shown by reference number720, the relay node may provide via an NR RRC message (e.g., SidelinkUEInformationNR (SUI) or another RRC message) that indicates one or more link layer identifier updates for the relay node. For example, the message shown by reference number720may include information indicating an original link layer identifier and an updated link layer identifier associated with the original link layer identifier. As another example, the message shown by reference number720may identify an updated link layer identifier and a relay service code or a radio access identifier with which the updated link layer identifier is associated. As shown by reference number730, the network entity may update the mapping determined in connection with reference number640to indicate the updated link layer identifier for the corresponding radio access identifier. Updating the mapping may be referred to herein as “updating the relay service.”

In some aspects, the relay node may determine to stop supporting a relay service. In this case, the relay node may suspend discovery using the link layer update. The relay node may provide sidelink update information that indicates that the relay service should be disabled. For example, the relay node may provide an updated link layer identifier (as described in connection with reference number720) with a value (such as a null value) indicating to disable the relay service. The network entity may disable the relay service based at least in part on the value indicating to disable the relay service. For example, the network entity may configure the remote node to establish a connection with another node (such as the network entity, another network entity, or another relay node).

FIG.8is a diagram illustrating an example process800performed, for example, by a network entity, in accordance with the present disclosure. Example process800is an example where the network entity (e.g., base station110, an NG-RAN, a CU, a DU, an RU) performs operations associated with a relay node identifier update.

As shown inFIG.8, in some aspects, process800may include receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier (block810). For example, the network entity (e.g., using communication manager150and/or reception component1002, depicted inFIG.10) may receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier, as described above.

As further shown inFIG.8, in some aspects, process800may include configuring a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier (block820). For example, the network entity (e.g., using communication manager150and/or configuration component1008, depicted inFIG.10) may configure a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier, as described above. In some aspects, the network entity may support the relay service. For example, the network entity may transmit or receive communications associated with relaying via the relay node using the mapping.

In a first aspect, the information indicating the link layer identifier is received in association with initiation of discovery for the relay service.

In a second aspect, alone or in combination with the first aspect, the information indicating the link layer identifier indicates a relay service code for the link layer identifier, and configuring the relay service is based at least in part on the relay service code.

In a third aspect, alone or in combination with one or more of the first and second aspects, process800includes receiving a plurality of link layer identifiers associated with respective relay service codes.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the information indicating the link layer identifier is received in association with a link layer identifier update, the link layer identifier is an original link layer identifier, the information indicating the link layer identifier indicates an updated link layer identifier, and process800includes updating the mapping to indicate the updated link layer identifier.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the information indicating the link layer identifier is received in association with disabling the relay service, the link layer identifier is an original link layer identifier, the information indicating the link layer identifier indicates an updated link layer identifier with a null value, and configuring the relay service further comprises disabling the relay service based at least in part on the updated link layer identifier having the null value.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, information indicating the link layer identifier is received via an RRC message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the relay service uses a sidelink interface between the relay node and the remote node, and the link layer identifier is a source Layer 2 identifier of the relay node.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, communication between the relay node and the remote node associated with the relay service is over one of a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and the link layer identifier is at least a medium access control address associated with the relay node.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, communication between the relay node and the remote node associated with the relay service is over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection, and the link layer identifier is based at least in part on a combination of a medium access control address associated with the relay node and a relay service code associated with the relay service.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the link layer identifier is self-selected by the relay node for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process800includes receiving, from the remote node, a report of one or more candidate relay nodes, wherein the report includes the link layer identifier, and wherein configuring and supporting the relay service is based at least in part on the report.

FIG.9is a diagram illustrating an example process900performed, for example, by a relay node, in accordance with the present disclosure. Example process900is an example where the relay node (e.g., UE120, an IAB node) performs operations associated with a relay node identifier update.

As shown inFIG.9, in some aspects, process900may include transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node (block910). For example, the relay node (e.g., using communication manager140and/or transmission component1104, depicted inFIG.11) may transmit a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node, as described above.

As further shown inFIG.9, in some aspects, process900may include transmitting, to a network entity via a radio access link, information indicating the link layer identifier of the relay node (block920). For example, the relay node (e.g., using communication manager140and/or transmission component1104, depicted inFIG.11) may transmit, to a network entity via a radio access link, information indicating the link layer identifier of the relay node, as described above.

As further shown inFIG.9, in some aspects, process900may include establishing a connection associated with a relay service using the link layer identifier (block930). For example, the relay node (e.g., using communication manager140and/or establishment component1108, depicted inFIG.11) may establish a connection associated with a relay service using the link layer identifier, as described above. In some aspects, by establishing the connection, the relay node may establish the relay service.

In a first aspect, the discovery message and the information indicating the link layer identifier are transmitted in association with initiation of discovery for the relay service.

In a second aspect, alone or in combination with the first aspect, the information indicating the link layer identifier indicates a relay service code for the link layer identifier.

In a third aspect, alone or in combination with one or more of the first and second aspects, process900includes transmitting a plurality of link layer identifiers associated with respective relay service codes if the relay node supports a plurality of relay services associated with the respective relay service codes.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the link layer identifier is an original link layer identifier, and process900includes transmitting, in association with a link layer identifier update, information indicating the original link layer identifier and an updated link layer identifier, and updating the relay service based at least in part on the updated link layer identifier.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the link layer identifier is an original link layer identifier, and process900includes transmitting, in association with disabling the relay service, information indicating the original link layer identifier and an updated link layer identifier with a null value, and disabling the relay service.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, information indicating the link layer identifier is transmitted via a radio resource control (RRC) message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the relay service uses a sidelink interface between the relay node and the remote node, and the link layer identifier is a source Layer 2 identifier of the relay node.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, communication between the relay node and the remote node associated with the relay service is over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection, and the link layer identifier is at least a medium access control address associated with the relay node.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, communication between the relay node and the remote node associated with the relay service is over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection, and the link layer identifier is based at least in part on a combination of a medium access control address associated with the relay node and a relay service code associated with the relay service.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process900includes selecting the link layer identifier for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection.

The transmission component1004may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1006. In some aspects, one or more other components of the apparatus1000may generate communications and may provide the generated communications to the transmission component1004for transmission to the apparatus1006. In some aspects, the transmission component1004may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1006. In some aspects, the transmission component1004may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection withFIG.2. In some aspects, the transmission component1004may be co-located with the reception component1002in a transceiver. In some aspects, the transmission component1004and/or the reception component1002may include interfaces with a radio unit, such as a radio unit of a disaggregated base station or a remote radio head. Thus, radio functionality may be implemented separately from the apparatus1000(or more generally the network entity described herein).

The reception component1002may receive, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier. The configuration component1008may configure (and optionally support) a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

The reception component1002may receive a plurality of link layer identifiers associated with respective relay service codes.

The reception component1002may receive, from the remote node, a report of one or more candidate relay nodes, wherein the report includes the link layer identifier.

FIG.11is a block diagram of an example apparatus1100for wireless communication, in accordance with the present disclosure. The apparatus1100may be a relay node, or a relay node may include the apparatus1100. In some aspects, the apparatus1100includes a reception component1102and a transmission component1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1100may communicate with another apparatus1106(such as a UE, a base station, or another wireless communication device) using the reception component1102and the transmission component1104. As further shown, the apparatus1100may include the communication manager140. The communication manager140may include one or more of an establishment component1108or a selection component1110, among other examples.

The transmission component1104may transmit a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node. The transmission component1104may transmit, to a network entity via a radio access link, information indicating the link layer identifier of the relay node. The establishment component1108may establish a connection associated with a relay service using the link layer identifier.

The transmission component1104may transmit a plurality of link layer identifiers associated with respective relay service codes if the relay node supports a plurality of relay services associated with the respective relay service codes.

The selection component1110may select the link layer identifier for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a P2P connection, or a D2D connection.

Aspect 1: A method of wireless communication performed by a network entity, comprising: receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configuring a relay service with the relay node and a remote node using a mapping between the radio access identifier and the link layer identifier.

Aspect 2: The method of Aspect 1, wherein the information indicating the link layer identifier is received in association with initiation of discovery for the relay service.

Aspect 3: The method of any of Aspects 1-2, wherein the information indicating the link layer identifier indicates a relay service code for the link layer identifier, and wherein configuring the relay service is based at least in part on the relay service code.

Aspect 4: The method of Aspect 3, further comprising: receiving a plurality of link layer identifiers associated with respective relay service codes.

Aspect 5: The method of any of Aspects 1-4, wherein the information indicating the link layer identifier is received in association with a link layer identifier update, wherein the link layer identifier is an original link layer identifier, wherein the information indicating the link layer identifier indicates an updated link layer identifier, and wherein the method further comprises: updating the mapping to indicate the updated link layer identifier.

Aspect 6: The method of any of Aspects 1-5, wherein the information indicating the link layer identifier is received in association with disabling the relay service, wherein the link layer identifier is an original link layer identifier, wherein the information indicating the link layer identifier indicates an updated link layer identifier with a null value, and wherein configuring the relay service further comprises: disabling the relay service based at least in part on the updated link layer identifier having the null value.

Aspect 7: The method of any of Aspects 1-6, wherein information indicating the link layer identifier is received via a radio resource control (RRC) message.

Aspect 8: The method of any of Aspects 1-7, wherein the relay service uses a sidelink interface between the relay node and the remote node, and wherein the link layer identifier is a source Layer 2 identifier of the relay node.

Aspect 9: The method of any of Aspects 1-8, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier is at least a medium access control address associated with the relay node.

Aspect 10: The method of any of Aspects 1-9, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier is based at least in part on a combination of a medium access control address associated with the relay node and a relay service code associated with the relay service.

Aspect 11: The method of any of Aspects 1-10, wherein the link layer identifier is self-selected by the relay node for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection.

Aspect 12: The method of any of Aspects 1-11, further comprising: receiving, from the remote node, a report of one or more candidate relay nodes, wherein the report includes the link layer identifier, and wherein configuring and supporting the relay service is based at least in part on the report.

Aspect 13: A method of wireless communication performed by a relay node, comprising: transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; transmitting, to a network entity via a radio access link, information indicating the link layer identifier of the relay node; and establishing a connection associated with a relay service using the link layer identifier.

Aspect 14: The method of Aspect 13, wherein the discovery message and the information indicating the link layer identifier are transmitted in association with initiation of discovery for the relay service.

Aspect 15: The method of any of Aspects 13-14, wherein the information indicating the link layer identifier indicates a relay service code for the link layer identifier.

Aspect 16: The method of any of Aspects 13-15, further comprising: transmitting a plurality of link layer identifiers associated with respective relay service codes if the relay node supports a plurality of relay services associated with the respective relay service codes.

Aspect 17: The method of any of Aspects 13-16, wherein the link layer identifier is an original link layer identifier, and wherein the method further comprises: transmitting, in association with a link layer identifier update, information indicating the original link layer identifier and an updated link layer identifier, and wherein the method further comprises: updating the relay service based at least in part on the updated link layer identifier.

Aspect 18: The method of any of Aspects 13-17, wherein the link layer identifier is an original link layer identifier, and wherein the method further comprises: transmitting, in association with disabling the relay service, information indicating the original link layer identifier and an updated link layer identifier with a null value; and disabling the relay service.

Aspect 19: The method of any of Aspects 13-18, wherein information indicating the link layer identifier is transmitted via a radio resource control (RRC) message.

Aspect 20: The method of any of Aspects 13-19, wherein the relay service uses a sidelink interface between the relay node and the remote node, and wherein the link layer identifier is a source Layer 2 identifier of the relay node.

Aspect 21: The method of any of Aspects 13-20, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier is at least a medium access control address associated with the relay node.

Aspect 22: The method of any of Aspects 13-21, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier is based at least in part on a combination of a medium access control address associated with the relay node and a relay service code associated with the relay service.

Aspect 23: The method of any of Aspects 13-22, further comprising: selecting the link layer identifier for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection.

Aspect 23: A method of wireless communication performed by a network entity, comprising: receiving, from a relay node via a radio access link, information indicating a link layer identifier of the relay node associated with a relay service, wherein the relay node is associated with a radio access identifier; and configuring the relay service with the relay node and a remote node.

Aspect 24: The method of Aspect 23, wherein the information indicating the link layer identifier indicates a relay service code for the link layer identifier, and wherein configuring the relay service is based at least in part on the relay service code.

Aspect 25: The method of Aspect 24, further comprising: receiving a plurality of link layer identifiers associated with respective relay service codes.

Aspect 26: The method of Aspect 23, wherein configuring the relay service with the relay node and a remote node comprises configuring the relay service using a mapping between the radio access identifier and the link layer identifier.

Aspect 27: The method of Aspect 26, wherein the information indicating the link layer identifier is received in association with a link layer identifier update, wherein the link layer identifier is an original link layer identifier, wherein the information indicating the link layer identifier indicates an updated link layer identifier, and wherein the method further comprises: updating the mapping to indicate the updated link layer identifier.

Aspect 28: The method of any of Aspects 23-27, wherein the information indicating the link layer identifier is received in association with discovery for the relay service.

Aspect 29: The method of any of Aspects 23-28, wherein the information indicating the link layer identifier is received in association with disabling the relay service, wherein the link layer identifier is an original link layer identifier, wherein the information indicating the link layer identifier indicates an updated link layer identifier with a null value, and wherein configuring the relay service further comprises: disabling the relay service based at least in part on the updated link layer identifier having the null value.

Aspect 30: The method of any of Aspects 23-29, wherein information indicating the link layer identifier is received via a radio resource control (RRC) message.

Aspect 31: The method of any of Aspects 23-30, wherein the relay service uses a sidelink interface between the relay node and the remote node, and wherein the link layer identifier is a source Layer 2 identifier for discovery message transmission by the relay node.

Aspect 32: The method of any of Aspects 23-31, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier comprises at least a medium access control address associated with the relay node.

Aspect 33: The method of any of Aspects 23-32, wherein communication between the relay node and the remote node associated with the relay service is over one of: a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection, and wherein the link layer identifier is based at least in part on a combination of a medium access control address associated with the relay node and a relay service code associated with the relay service.

Aspect 34: The method of any of 23-33, wherein the link layer identifier is self-selected by the relay node for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection.

Aspect 35: The method of any of Aspects 23-34, further comprising: receiving, from the remote node, a report of one or more candidate relay nodes, wherein the report includes the link layer identifier, and wherein configuring and supporting the relay service is based at least in part on the report.

Aspect 36: A method of wireless communication performed by a relay node, comprising: transmitting a discovery message for relaying communications with a remote node, wherein the discovery message includes a link layer identifier of the relay node; and transmitting, via a radio access link, information indicating the link layer identifier of the relay node.

Aspect 37: The method of Aspect 36, further comprising establishing a connection associated with a relay service using the link layer identifier.

Aspect 38: The method of any of Aspects 36-37, wherein the discovery message and the information indicating the link layer identifier are transmitted in association with discovery for a relay service.

Aspect 39: The method of any of Aspects 36-38, further comprising: transmitting a plurality of link layer identifiers associated with respective relay service codes.

Aspect 40: The method of any of Aspects 36-39, further comprising: selecting the link layer identifier for discovery when communicating with the remote node over one of a Bluetooth connection, a WiFi connection, a peer-to-peer (P2P) connection, or a D2D connection.

Aspect 41: The method of any of Aspects 36-40, wherein the relay service uses a sidelink interface between the relay node and the remote node, and wherein the link layer identifier is a source Layer 2 identifier for discovery message transmission by the relay node.