Technologies for multi-hop user equipment to network relay
Enhancements to RRC messages and protocol stacks address downlink path ambiguity and signaling overhead in multi-hop U2N relays, enhancing efficiency and reliability in 3GPP wireless networks.
Patent Information
- Application Number
- PCT/CN2025/093540
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication networks face challenges in managing multi-hop user equipment to network relay due to unclear downlink paths, signaling overhead, and double-direction failure reporting in multi-hop U2N relays, particularly in 3GPP wireless networks.
Enhancements to RRC messages and protocol stacks for multi-hop U2N relays, including automatic routing table creation, enhanced notification and message handling, and differentiated RLC channel configurations to manage upstream and downstream traffic efficiently.
Improves signaling efficiency and reliability in multi-hop U2N relays by optimizing routing and reducing overhead, ensuring accurate configuration and failure reporting across multiple hops.
Smart Images

Figure CN2025093540_12112026_PF_FP_ABST
Abstract
Description
TECHNOLOGIES FOR MULTI-HOP USER EQUIPMENT TO NETWORK RELAYTECHNICAL FIELD
[0001] This application relates generally to communication networks and, in particular, to technologies for multi-hop user equipment to network relay in said networks.BACKGROUND
[0002] Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for wireless networks. These TSs describe aspects related to signaling traffic through systems that incorporate wireless networks.BRIEF DESCRIPTION OF THE DRAWINGS
[0003] FIG. 1 illustrates a network environment in accordance with some embodiments.
[0004] FIG. 2 illustrates an end-to-end control plane protocol stacks in accordance with some embodiments.
[0005] FIG. 3 illustrates a multi-tiered topology in accordance with some embodiments.
[0006] FIG. 4 illustrates various topologies in accordance with some embodiments.
[0007] FIG. 5 illustrates a configuration element in accordance with some embodiments.
[0008] FIG. 6 illustrates another configuration element in accordance with some embodiments.
[0009] FIG. 7 illustrates an operational flow / algorithmic structure in accordance with some embodiments.
[0010] FIG. 8 illustrates another operational flow / algorithmic structure in accordance with some embodiments.
[0011] FIG. 9 illustrates another operational flow / algorithmic structure in accordance with some embodiments.
[0012] FIG. 10 illustrates another operational flow / algorithmic structure in accordance with some embodiments.
[0013] FIG. 11 illustrates another operational flow / algorithmic structure in accordance with some embodiments.
[0014] FIG. 12illustrates a user equipment in accordance with some embodiments.
[0015] FIG. 13 illustrates a network device in accordance with some embodiments.DETAILED DESCRIPTION
[0016] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A / B” mean (A) , (B) , or (A and B) ; and the phrase “based on A” means “based at least in part on A, ” for example, it could be “based solely on A” or it could be “based in part on A. ”
[0017] The following is a glossary of terms that may be used in this disclosure.
[0018] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an application specific integrated circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , digital signal processors (DSPs) , etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
[0019] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit (CPU) , a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.
[0020] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I / O interfaces, peripheral component interfaces, network interface cards, or the like.
[0021] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless / wired device or any computing device including a wireless communications interface.
[0022] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
[0023] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, workload units, or the like. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware element (s) . A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices / systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
[0024] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.
[0025] The terms “instantiate, ” “instantiation, ” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
[0026] The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
[0027] The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, or the like.
[0028] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.
[0029] FIG. 1 illustrates a network environment 100 in accordance with some embodiments. The network environment 100 may include a UE 104 coupled with a base station (BS) 108 of a radio access network (RAN) 110 that provides one or more serving cells. In some embodiments, the BS 108 is a gNB that provides one or more 3GPP new radio (NR) cells. The air interface over which the UE 104 and the base station 108 communicate may be compatible with 3GPP technical specifications (TSs) , such as those that define 5G NR or later system standards (e.g., Sixth Generation (6G) standards) . The RAN 110 may include a number of base stations that provide services to various UEs through serving cells of one or more radio access technologies.
[0030] Operations describedherein as associated or performed by a particular device (for example, UE 104 or base station 108) may be performed by a processor that is incorporated into that device.
[0031] The network environment 100 may further include a core network 112 to couple the RAN 110 to an external data network 120. For example, the core network 112 may comprise a 5G core network (5GC) , a 6G core network (6GC) , or later generation core network. The core network 112 may be coupled to the base station 108 via a fiber optic or wireless backhaul. The core network 112 may provide functions for the UE 104 via the base station 108. These functions may include managing subscriber profile information, subscriber location, authentication of services, or switching functions for voice and data sessions.
[0032] In some embodiments, the UE 104 may provide service to one or additional UEs, which may be outside a coverage area provided by the base station 108. The UE 104, in this scenario, may be referred to as a relay UE.
[0033] In legacy networks, one relay UE could provide a connection to one remote UE. Embodiments of the present disclosure provide for communicatively coupling a remote UE 124 to the RAN 110 using a multi-hop UE-to-network (U2N) relay. As shown, the remote UE 124 may be coupled with the RAN 110 via a plurality of relay UEs including, for example, relay UE 128 and 104. While two relay UEs are shown, embodiments may apply to any number of relay UEs / hops.
[0034] As used herein, the UE 128 may be referred to as a first relay UE 128 as it is adjacent to the remote UE 124 and the UE 104 may be referred to as a last relay UE 104 as it is adjacent to the base station 108. The last relay UE 104 is within coverage of a serving cell provided by the base station 108. Any relay UE between the last relay UE 104 and the remote UE 124 may be referred to as intermediate relay UEs, which may be outside the coverage of the serving cell. As used herein, an upstream direction may be a direction toward the RAN 110 and a downstream direction may be a direction toward the remote UE 124. Further, a first UE may be a child of a second UE if the first UE is downstream from the second UE. In this situation, the second UE could also be referred to as a parent of the first UE.
[0035] Two adjacent UEs may be coupled with one another over a sidelink interface, which may also be referred to as a PC5 interface / link / hop or simply PC5. The last relay UE 104 may be coupled with the base station 108 over a Uu interface, which may also be referred to as a Uulink / hop or simply Uu.
[0036] Legacy radio resource control (RRC) messages transmitted over the PC5 link may include one or more of the following.
[0037] A remote UE information sidelink (RemoteUEInformationSidelink) message may be used by a remote UE to request a relay UE to help obtain system information (SI) , positioning SI (posSI) , paging information, or to cancel a request.
[0038] A Uu message transfer sidelink (UuMessageTransferSidelink) message may be used by a relay UE to deliver SI, posSI, and paging information to a remote UE.
[0039] A notification message sidelink (NotificationMessageSidelink) message may be used to communicate information of a Uu radio link failure (RLF) or relay cell reselection to a remote UE.
[0040] An RRC reconfiguration sidelink (RRCReconfigurationSidelink) message may be used to configure SL radio / link parameters including PC5 radio link control (RLC) channels.
[0041] A measurement report sidelink (MeasurementReportSidelink) message may be used to report PC5 link measurements to the peer SL UEs.
[0042] UE SL information request or response (UEInformationReqSL / UEInformationRspSL) messages may be used for UE-based quality of service (QoS) splits among two adjacent PC5 hops.
[0043] Legacy RRC messages transmitted over the Uu link may include one or more of the following.
[0044] A sidelink UE information (SidelinkUEInformation) message may be used by a sidelink UE to request transmit (Tx) resources for Tx destinations. For relay UE reporting, remote UEs may be considereddestinations. In legacy messages, this would implicitly tell a base station that the relay-remote topology is one-hop. For remote UE reporting, the selected relay UE is the destination.
[0045] A RRC reconfiguration (RRCReconfiguration) message may provide sidelink radio adaptation protocol (SRAP) and relay RLC channel configurations to the UEs. For a PC5 hop, the configurations may map into egress PC5 link and PC5 relay RLC channels. For a Uu hop, the configurations may map into egress Uu link and Uurelay RLC channel. As used herein, egress may refer to a UE’s transmit configurations, while ingress may refer to a UE’s receive configurations.
[0046] Embodiments of the present disclosure enhance various of these messages to improve signaling and procedures for multi-hop U2N relays.
[0047] In some embodiments, the remote UE 124 may provide a request to the last relay UE 104 to monitor for certain SI or paging messages from the network. The request may be conveyed by RemoteUEInformationSL messages transmitted hop-by-hop to the last relay UE 104. The last relay UE 104 may monitor transmissions from the base station 108 and if the requested SI or paging information is received, the last relay UE 104 may send the requested information to the remote UE 124. The requested information may be conveyed by UuMessageTransferSL messages transmitted hop-by-hop to the remote UE 124.
[0048] FIG. 2 illustrates an end-to-end control plane (CP) protocol stack of the UEs of the network environment 100 in accordance with some embodiments. FIG. 2 illustrates aspects similar to FIG. 1, for example, remote UE 124, first relay UE 128, last relay UE 104, and base station 108. For the end-to-end CP traffic (over the Uu signaling radio bearer (SRB) ) and user plane (UP) traffic (over the Uu data radio bearer (DRB) ) , an SRAP layer may be used to identify an identity of the remote UE 124 and an appropriate bearer.
[0049] FIG. 3 illustrates multi-tiered topology 300 in accordance with some embodiments. The topology 300 illustrates the challenges associated with multi-hop U2N relays in which an uplink path is self-evident as each child UE has one parent UE in the upstream. However, a downlink path may not be clear because each parent UE may have more than one child UE in the downstream. For each relay UE to reach an indirect child, it may need to decide the exact correct child to route through. Full path information may not be available to any node, at least initially. When a remote UE chooses a relay, it may only know the next hop. There may be signaling overhead concerns to share / build path information with dedicated control signaling.
[0050] Assuming there is no dedicated new path reporting procedure, a base station or relay nodes may not have full topology information. The relay UEs may need to build a routing table based on its own partial information that has been collected. For idle / inactive UEs, it is unclear as to where this information will be sourced. It is further unclear whether connected UEs will operate in a similar manner, at least before the base station knows the full path. Once the base station knows the full path, it is unclear whether benefits outweigh the cost of the signaling overhead incurred for the base station to reconfigure relays every time the topology changes.
[0051] Another issue may stem from intermediate relay UEs needing to handle two PC5 links, one for the upstream and one for the downstream. Consider the topologies of FIG. 4, which illustrate double-direction failure reporting issues that may occur in accordance with embodiments of the present disclosure.
[0052] Topology 404 illustrates an RLF at the Uu interface. In Release 17, only the relay UE would need to notify the remote UE about the RLF, because a failure in the other direction (for example, an RLF on a PC5 link) isalways reported as legacy SL procedure.
[0053] With more than one PC5 link capable of having a failure, reporting of the PC5 RLF may be needed in more than one direction. For example, with topology 408, the RLF may occur in a PC5 link between remote UE and first relay UE and the PC5 RLF report may need to be transmitted upstream. For another example, with topology 412, the RLF may occur in PC5 link between intermediate relay UE and last relay UE and the PC5 RLF report may need to be transmitted downstream.
[0054] In some instance, a double-direction PC5 link configuration issue may also arise. For example, for SL design, a network configuration is usually destinationagnostic. However, it may be beneficial for the network to explicitly label the SLconfiguration as either for the upstream direction or for the downstream direction. It may also be beneficial for the base station to know whether the SL destinationsreported by a relay UE in its SidelinkUEInformation belongs to upstream or downstream direction.
[0055] A number of aspects are defined to address various issues. Five aspects are briefly introduced below.
[0056] A first aspect may include automatic routing table creation. For whatever multi-hop upstream transmission, a unique identifier may be remembered to be associated with a child node and the PC5 link to reach this child node. When a downlink (DL) packet is generated or to be forwarded in the downstream direction, the UE will use this remembered routing table entry to send the packet directly to the appropriate child UE, instead of broadcasting it to every child UE.
[0057] A second aspect may include enhancements of NotificationMessageSideLink. When a PC5 RLF happens, the relay UE may notify its upstream relay UEs in the path so that the upstream node (s) can take corresponding actions. In some embodiments, the notification may include a list of children so the parent relay knows what nodes have been impacted.
[0058] A third aspect may include enhancements of RemoteUEInformationSidelink and UuMessageTransferSidelink messages. A relay UE may provide a list of child UEs for which a paging monitoring request has been canceled due to, for example, a PC5 RLF or some other reason. This may additionally / alternatively be used to add paging monitoring requests. Further, when a relay receives multiple paging records (PagingRecords) that are to be delivered through a child relay UE, the relay UE may combine the PagingRecords to deliver together to the child relay UE for further distribution.
[0059] A fourth aspect may include enhancements of the SidelinkUEInformation message. Benefits may be associated with an intermediate relay UE distinguishing its children and parent relays in reporting. This may help the base station to identify the needed configuration in both directions. It may also be helpful to include tier-2 (or greater) children for the network to further understand the topology so that it may provide more accurate (re-)configurations.
[0060] The fifth aspect may include enhancements to the RRCReconfigurationmessage. In particular, aPC5 RLC channel configuration may be enhanced to indicate direction information, for example, to indicate whether an RLC channel configuration is for upstream ordownstream with associated QoS requirements. Some embodiments describe a light SRAP configuration option in which the base station only provides the same egress PC5 relay RLC channel for all children of the relay UE. The same may be true forUu Relay RLC channel configuration for the last Uu hop. Some embodiments may further describe a heavy SRAP configuration option in which the base station provides dedicated PC5 Relay RLC channel configurations and Uu Relay RLC channel configurationsindividually for every remote UE in the topology.
[0061] These and other aspects will be described in further detail below.
[0062] With respect to the first aspect for automatically creating the routing table, UEs may rely on uplink-downlink traffic correspondence to build a routing table by assuming the uplink traffic will occur first. The uplink traffic will include an uplink message with a unique identifier that may be paired with a routing table entry to be used for subsequent downlink traffic.
[0063] In some embodiments, the routing table may be used for paging delivery as follows. When a paging identifier of a remote UE is first submitted in upstream traffic, each relay UE node can store, in a routing table entry, the sidelink paging identity of the remote UE (sl-PagingIdentityRemoteUE) and an associated PC5 link upon which the message including the paging identifier is received. When a paging record is intercepted in Uu RRC, or forwarded in PC5 RRC, a relay UE will access the routing table to determine the PC5 link associated with the sidelinkpaging identity. The relay UE will then route the paging record toward the associated PC5 link.
[0064] In some embodiments, the routing table may be used for SI or posSI delivery as follows. When a request for certain SI is submitted in upstream traffic (for example, in a RemoteUEInformationSidelink message) , a relay UE node can store, in a routing table entry, the requested SI (for example, SIB type or SI type) and an associated PC5 link upon which the request is received. When the requested SI is acquired, the relay UE will access the routing table to determine the PC5 link that it will use to forward the requested SI.
[0065] In some embodiments, the routing table may be used for remote UE RRC message routing as follows. When the remote UE’s first RRC message, transmitted using SRB 0, is forwarded by a relay UE, the RRC message may be associated with a layer 2 (L2) ID of the remote UE. The relay UE may store, in a routing table entry, the L2 ID and associated PC5 link upon which the RRC message is received. When the relay UE receives a downlink transmission with an SRB 0 message, the relay UE may use the L2 ID to determine the proper PC5 link upon which to forward the SRB 0 message.
[0066] In some embodiments, the routing table may be used for remote UE generic traffic routing. When the remote UE sends its first uplink traffic with a UE ID in an SRAP header, the relay UE will store the UE ID and associated PC5 link in a routing table entry. When the same UE ID is received in an SRAP header of a downlink transmission, the relay UE will route the packet to the associated PC5 link based on the routing table entry. The UE ID may be allocated to the remote UE by the base station. However, this routing mechanism may work even when the base station has not yet configured the relay UE with a UE ID.
[0067] With respect to the second aspect for enhancements to the NotificationMessageSidelink message, additional information may be provided to clarify the nature and impact of PC5 RLFs.
[0068] In a first embodiment, a new sidelinkindication type may be designed for Release 19 (sl-indicationType-r19) that includes an indication of a PC5 failure detected by a relay UE in a multi-hop U2N relay path (relayUE-PC5-RLF) . This is in contrast to a legacy sidelink indication type designed for Release 18 (sl-indicationType-r18) , which is limited to providing an indication of a PC5 failure detected by a relay UE in a UE-to-UE relay path. Further, while an sl-indicationType-r18 is sent by a relay UE that detects the RLF, the sl-indicationType-r19 may be forwarded by a relay UE that receives the indication of the RLF from a UE further downstream.
[0069] In some embodiments, the sl-indicationType-r19 may not need to provide an indication of the direction in which the RLF occurs. If a UE receives the sl-indicationType-r19 from the downstream direction, the UE will understand the RLF has occurred in the downstream direction, and vice versa.
[0070] In a second embodiment, a sidelinkindication type (sl-indicationType) included in the NotificationMessageSidelink message may be enhanced to indicate a direction in which the RLF is detected. For example, the sidelink indication type may include a first value to indicate that the relay UE detected a PC5 failure associated with a parent UE of the relay UE (PC5-RLF parent) or a second value to indicate that the relay UE detected a PC5 failure associated with a child UE of the relay UE (PC5-RLF child) . In another example, the sidelink indication type may include a first value to indicate that the relay UE detected a PC5 failure upstream of the relay UE (PC5-RLF upstream) or a second value to indicate that the relay UE detected a PC5 failure downstream of the relay UE (PC5-RLF downstream) .
[0071] In some embodiments, the NotificationMessageSidelink message may additionally / alternatively include a list of one or more child UEs that have been impacted for a PC5-RLF child (or PC5-RLF downstream) case. The list may include a sequence of local identifiers or a sequence of L2 IDs.
[0072] In some embodiments, the NotificationMessageSidelink message may additionally / alternatively include a numerical value (x=0, 1, 2. . . ) to indicate a location of the RLF (for example, the PC5 link x hops away (in either upstream or downstream direction) has failed) .
[0073] If the triggering condition for the NotificationMessageSidelink message is detected based on a downstream RLF, a relay UE may send / forward the message upstream with the failure indication. As discussed above, this message may include a list of local or L2 IDs impacted in some embodiments.
[0074] If the triggering condition for the NotificationMessageSidelink message is detected based on an upstream RLF, a relay UE may send / forward the message downstream with the failure indication.
[0075] With respect to the third aspect, the RemoteUEInformationSL and UuMessageTransferSL messages may be enhanced to avoid excessive signaling.
[0076] With respect to the RemoteUEInformationSidelink message, a relay UE may provide a list of child UEs for which a paging monitoring request has been added or canceled due to, for example, PC5 RLF or other reasons. To accommodate the lists, “SetupRelease” of the RemoteUEInformationSidelink message may be replaced by a first list (ToAddModList) for IDs to be added to a master list and a second list (ToReleaseList) for IDs to be removed from the master list.
[0077] In some embodiments, a RemoteUEInformatonSidelink message may be triggered when a PC5 RLF is detected between a relay UE and its adjacent child relay. In this case, the relay UE may send the RemoteUEInformatonSidelinkmessage to request cancelation of all remote UE paging identities affected in a list.
[0078] In some embodiments, a RemoteUEInformatonSidelink message may be triggered when a relay UE receives a PC5 RLF notification from a child UE about a failure further downstream. In this case, the relay UE may combine the reported paging identities with potentially other paging monitor requests to be cancelled in a new RemoteUEinformationSL message.
[0079] In some embodiments, a RemoteUEInformatonSidelink message may be triggered when the relay UE enters CONNECTED. In this case, the relay UE includes itself and all its children in a list to be released as the relay UE can monitor paging itself and does not need an upstream UE to perform the monitoring on its behalf.
[0080] With respect to the UuMessageTransferSidelink message, a relay UE may combine multiple paging records (PagingRecords) to deliver together to a child relay UE so that this can be further distributed. For example, if a relay UE is coupled with one child UE and that child UE includes three child UEs of its own (or three grandchild UEs of the relay UE), the relay UE may combine all paging records associated with the three grandchild UEs into one UuMessageTransferSidelink message that is transmitted to the child UE of the relay UE.
[0081] In some embodiments, a UuMessageTransferSidelink message may be triggered when one or more pagingRecordshave been intercepted for forwarding. In this case, the relay UE may combine them in a single message with a list of PagingRecords andtransfer downstream for further distribution.
[0082] With respect to the fourth aspect, enhancements may be presented with respect to the SidelinkUEInformationNR message and associated procedures.
[0083] In some embodiments, the SidelinkUEInformationNR message may be enhanced by providing for an indication that a UE requesting the Tx resources is an intermediate relay UE. This may be done by extending the legacy UE-type parameter (ue-Type) to include an enumerated value of intermediate UE (intermediateUE) , in addition to the current enumerated values of relay UE (relayUE) and remote UE (remoteUE) . In this case, a value type of relayUE may be interpreted to be a last relay UE. Additionally / alternatively, a new ueTypelist (for example, ueType-r19) may be used for an intermediate relay UE. In this case the intermediate relay UE will not use the legacy ueType list (ueType-r17) , which will just have the relayUE and remoteUE values. Again, in this case, the relayUE may be considered as the last relay UE.
[0084] In some embodiments, the SidelinkUEInformationNR message may be enhanced to provide relay relationship information with respect to the destination. The SidelinkUEInformationNR message may include a SL destination L2 identity (SL-DestinationIdentityL2U2N) that indicates a destination L2 ID for which the Tx resource request and allocation from the network are concerned for an established PC5 link for relay by the L2 U2N relay UE. In some embodiments, an additional relay relationship type (RelayRelationshipType) parameter may be added for each SL-DestinationIdentityL2U2N. The RelayRelationshipType parameter may include a value of child / parent or upstream / downstream to indicate whether the destination UE is a child / parent UE or upstream / downstream with respect to the relay UE.
[0085] In some embodiments, a sidelink local ID request (sl-LocalID-Request) may be required to be set for every child UE, but never set for the parent UE. While this may help to differentiate theparent or relay, it may also prevent the relay UE from requesting a local ID reassignment for its children correctly. For example, 3GPP TS 38.331 v18.5.1 (2025-03-21) may need to add additional field description restrictions to forbid the absence of “sl-LocalID-Request” in any child UE to different them from the parent node, but that means the local ID will be assigned again and again.
[0086] In some embodiments, the SidelinkUEInformationNR message may be enhanced to include an indirect children list. This indirect children list may include hop distance information for the indirect child nodesthat are included. This may provide the base station with additional information about the topology.
[0087] In some embodiments, a relay UE acting as an intermediate relay UE will send the SidelinkUEInformationNR message only if it is in RRC connected state with the network. Additionally / alternatively, a relay UE acting as an intermediate relay UE will send the SidelinkUEInformationNR message only if a SIB12 of a serving cell indicated that the serving cell supportsL2 multi-hop U2N relay. The serving cell may be the one with which the last relay UE is directly connected, and the relay UE may acquire the SIB12 and forward it to the intermediate relay UE.
[0088] With respect to the fifth aspect, enhancements may be presented to the RRCReconfiguration message and associated procedures.
[0089] The RRCReconfiguration message may be sent to a UE to configure various aspects of communication on the multi-hop U2N relay path. Among other things, the RRCReconfiguration message may provide a PC5 Relay RLC Channel Configuration and SRAP configurations.
[0090] The PC5 Relay RLC Channel Configuration (SL-RLC-ChannelConfig) may specify configuration information for a PC5 relay RLC channel between L2 U2N relay UEs or between an L2 U2N relay UE and an L2 U2N remote UE.
[0091] Each RLC channel configuration may include a SL RLC channel ID (sl-RLC-ChannelID) to indicate the RLC channel in the PC5 link. In some embodiments, for each SL RLC channel ID, the relay UE may establish a logical channel (LCH) toward a different SL destination. Since upstream and downstream destinations are different, the same SL RLC channel ID may be reused. However, certain QoS parameters (for example, the packet delay budget) may be different in different directions. Thus, embodiments provide for PC5 Relay RLC channel configurations to provide two different QoS (for example, packet delay budget) configurations, one for an UL PC5 hop and one for a DL PC5 hop. This may be accomplished by providing different IEs in one Relay RLC channel configurations for the different QoS configurations (for example, an upstream sidelink packet delay budget (sl-PacketDelayBudget_upstream) and a downstream sidelink packet delay budget (sl-PacketDelayBudget_downstream) ) . In other embodiments, one relay RLC channel configuration may be provided to configure an upstream PC5 relay RLC channel and another relay RLC channel configuration may be provided to configure a downstream PC5 relay RLC channel. In other embodiments, this may also be realized by linking the PC5 Relay RLC channel configuration in the SRAP configuration, where when the PC5 relay RLC channel is configured as upstream egress channel, then the packet delay budget (PDB) is the UL transmission PDB, when the PC5 Relay RLC channel is configured as downstream egress RLC channel, then the PDB will be the downstream PDB.
[0092] To reduce the overall signaling overhead, the PC5 Relay RLC channel configuration can also be designated as default channel configuration, which is used to setup the default PC5 relay RLC channel to be used for forwarding either upstream or downstream, when explicit SRAP mapping for one or more bearer is not provided. In this case, the SL-RLC-ChannelID associated with the default SL-RLC-channel-configuration is assumed to be the egress RLC channel configuration by default. In some further designs, this default designation can also be refined as “SRB default RLC channel” or “DRB default RLC channel, ” where one of designated default configuration is used for forwarding SRB traffic between gNB and remote UE, and another one is used for DRB traffic forwarding
[0093] An SRAP configuration (SL-SRAP-Config) may be used to set configurable SRAP parameter used by L2 U2N relay / remote UEs.
[0094] A legacy SRAP configuration provided to a relay UE will include an L2 identity of a child of the relay UE (sl-LocalIdentity) , an identity of a remote UE (sl-RemoteUE-RB-Identity) , which may be an SRB identity or a DRB identity, and egress mappings. A first egress mapping may be for the RLC channel of the Uu (sl-EgressRLC-ChannelUu) and may include an RLC channel ID to configure the RLC channel of the Uu interface for the relay UE (Uu-RelayRLC-ChannelID) . A second egress mapping may be for the RLC channel of the PC5 (sl-EgressRLC-ChannelPC5) and may include an RLC channel ID to configure the RLC channel of the PC5 interface for the relay UE (PC5-RelayRLC-ChannelID) .
[0095] In embodiments of the disclosure, the network may provide an SRAP configuration with egress mappings for RLC channel of the PC5 in both upstream and downstream. Thus, the network may provide one PC5-RelayRLC-ChannelID (mapped to an SRB / DRB) for upstream and one PC5-RelayRLC-ChannelID (mapped to the same SRB / DRB) for downstream. Further details are provided below with respect to FIG. 6.
[0096] In some embodiments, the network may determine whether to use a light SRAP configuration option or a heavy SRAP configuration option.
[0097] A light SRAP configuration option may include the base station only providing the sameegress PC5 relay RLC channel for all children of the relay UE. The same may be true for Uu Relay RLC channel configuration for the last Uu hop.
[0098] A heavy SRAP configuration option may include the base station providing dedicated PC5Relay RLC channel configurations and Uu Relay RLC channelconfigurations individually for every remote UE in the topology.
[0099] FIGS. 5 and 6 illustrate configuration elements in accordance with some embodiments. In particular, FIG. 5 illustrates a SL multi-hop L2 relay UE configuration (SL-Multihop-L2RelayUE-Config) 500 and FIG. 6 illustrates a SL multi-hop SRAP configuration (SL-MH-SRAP-Config) 600 in accordance with some embodiments.
[0100] With reference to FIG. 5, theSL-Multihop-L2RelayUE-Config 500 may include a first list (sl-ChildUE-ToAddModList) of child UEs to be added to a relay UE and a second list (sl-ChildUE-ToReleaseModList) of child UEs to be removed from the relay UE.
[0101] For each child UE in the first list, the SL-Multihop-L2RelayUE-Config 500 may include a sidelink L2 identity for a remote UE (sl-L2IdentityRemote) and a sidelink SRAP configuration (sl-SRAP-ConfigRelay) that refers to an SL multi-hop SRAP configuration (SL-MH-SRAP-Config) such as SL-MH-SRAP-Config 600.
[0102] The SL-MH-SRAP-Config 600 may include a local identity associated with the added child UE (sl-LocalIdentity) and a first list of mappings to add (SL-MappingToAddModList) and a second list of mappings to release (SL-MappingToReleaseList) . For the added mappings, the SL-MH-SRAP-Config 600 may include an identity of a remote UE (sl-RemoteUE-RB-Identity) , which may be an SRB identity or a DRB identity, and various egress mappings. A first egress mapping may be for the RLC channel of the Uu (sl-EgressRLC-ChannelUu) and may include an RLC channel ID to configure the RLC channel of the Uu interface for the child UE (Uu-RelayRLC-ChannelID) . A second egress mapping may be for the RLC channel of the PC5 for the upstream (sl-UpstreamEgressRLC-ChannelPC5) and may include an RLC channel ID to configure the RLC channel of the upstream PC5 interface for the child UE (SL-RLC-ChannelID) . A third egress mapping may be for the RLC channel of the PC5 for the downstream (sl-DownstreamEgressRLC-ChannelPC5) and may include an RLC channel ID to configure the RLC channel of the downstream PC5 interface for the child UE (SL-RLC-ChannelID) .
[0103] It may be noted that the SL-MH-SRAP-Config 600 shown may be a generic configuration that could be used for both a direct child UE and an indirect child UE. Not all parts may be included in a specific situation. For example, the configuration of an indirect child UE may not need a Uu interface to be configured.
[0104] In some embodiments, the SL‐MH‐SRAP‐Config 600 may be designed to be specifically used for an indirect child, for example. In this case, the SL‐MH‐SRAP‐Config 600 may include sl-upstreamEgressRLCChannelPC5 and sl-downstreamEgressRLCChannelPC5, but not sl-EgressRLC-ChannelUu. In these embodiments, another configuration, for example, a legacy release 17 SL-SRAP-config may be used for direct child UEs.
[0105] With respect to the light SRAP configuration option, the mappings provided by the SL-MH-SRAP-Config 600 may be used for all local IDs (for example, not only for the child UE but indirect child UEs as well) .
[0106] For the heavy SRAP configuration option, and referring back to the SL-MultiHop-L2RelayUE-Config 500, for each added child, additional lists may be provided with respect to indirect children. In particular, afirst list (sl-indirectChildren-ToAddModList) of indirect child UEs to be added to a relay UE and a second list (sl-indirectChildren-ToReleaseModList) of indirect child UEs to be removed from the relay UE. For each indirect child UE to be added, the SL-MultiHop-L2RelayUE-Config 500 may include a sidelink L2 remote identity (sl-L2IdentityRemote) and a corresponding relay SRAP configuration (sl-SRAP-ConfigRelay) that has a value that points to an SL-MH-SRAP config that may be used to configure that indirect child UE with SRAP configuration parameters that may be different from those of its parent UE or any other relay UEs.
[0107] FIG. 7 is an operational flow / algorithmic structure 700 in accordance with some embodiments. The operational flow / algorithmic structure 700 may be implemented by a relay UE such as, for example, relay UE 128, relay UE 104, or UE 1200 (shown in FIG. 12 and discussed further below) , or components thereof; for example, a baseband processor 1204A.
[0108] The operational flow / algorithmic structure 700 may include, at 704, receiving an uplink transmission from a downstream UE. The downstream UE may also be referred to as a relay UE in this embodiment. The uplink transmission may be received on the first link of a multi-hop U2N relay path. The first link may be a PC5 link.
[0109] The operational flow / algorithmic structure 700 may further include, at 708, outputting the uplink transmission on a second link of the multi-hop U2N relay path for transmission to a network. In some embodiments, the uplink transmission may be a remote UE information sidelink message.
[0110] The operational flow / algorithmic structure 700 may further include, at 712, identifying an identity of a remote UE based on the uplink transmission. The remote UE may be different from the relay UE that directly provides the uplink transmission.
[0111] The operational flow / algorithmic structure 700 may further include, at 716, generating an entry in a routing table to associate the identity of the remote UE with the first link with the relay UE. While some embodiments describe storing the identity of the remote UE with the first link, other embodiments may store other associations with the first link. For example, if the uplink transmission requests specific information, for example, a specific SIB, the requested information may be stored in the entry of the routing table and associated with the first link. For another example, the identity stored in the entry of the routing table may be an identity of a DRB or an SRB.
[0112] The operational flow / algorithmic structure 700 may further include, at 720, receiving a downlink transmission to the remote UE. The downlink transmission may include an identity of the remote UE, which is used to access the routing table and to discover the association of the first link with the identity.
[0113] The operational flow / algorithmic structure 700 may further include, at 724, outputting the downlink transmission on the first link based on the entry in the routing table. In some embodiments, the downlink transmission may be output as a unicast message on the first link. Outputting of a message, as used herein, may be performed by processor circuitry that outputs the message to circuitry that performs lower-layer functions such as, for example, conversion, amplification, and over-the-air transmission of radio-frequency signals.
[0114] In some embodiments, the identifier of the remote UE may be a paging identifier and the downlink transmission may be a paging message.
[0115] In some embodiments, the uplink transmission may be a request for system information (for example, a SIB or posSIB) and the downlink transmission may include the requested system information.
[0116] In some embodiments, the uplink transmission may be a first RRC message using SRB 0, the identity may be an L2 identity of the remote UE, and the downlink transmission may be a second RRC message using SRB 0.
[0117] In some embodiments, the uplink and downlink transmissions may include an SRAP header with the identity of the remote UE.
[0118] FIG. 8 is an operational flow / algorithmic structure 800 in accordance with some embodiments. The operational flow / algorithmic structure 800 may be implemented by a relay UE such as, for example, relay UE 128, relay UE 104, or UE 1200 (shown in FIG. 12 and discussed further below) , or components thereof; for example, a baseband processor 1204A.
[0119] The operational flow / algorithmic structure 800 may include, at 804, detecting an RLF on a first link of a multi-hop U2N relay path. The first link may be a first PC5 link.
[0120] The operational flow / algorithmic structure 800 may further include, at 808, generating an SL indication type parameter to indicate the RLF. In some embodiments, the SL indication type parameter may indicate the RLF is associated with an upstream PC5 link or a downstream PC5 link.
[0121] The operational flow / algorithmic structure 800 may further include, at 812, generating an SL notification message to include the SL indication type parameter. In some embodiments, the SL notification message may additionally / alternatively include one or more identifiers respectively associated with one or more UEs impacted by the RLF. In some embodiments, the SL notification message may additionally / alternatively include the indication of a location of the RLF in the multi-hop U2N relay path. For example, the location may be a number of hop separating a node that performed the operation flow / algorithmic structure 800 and the RLF.
[0122] The operational flow / algorithmic structure 800 may further include, at 816, outputting the SL notification message on a second link. If the RLF is a downstream are left, the SL notification message may be output as an upstream transmission. If the RLF is an upstream RLF, the SL notification message may be output as a downstream transmission.
[0123] FIG. 9 is an operational flow / algorithmic structure 900 in accordance with some embodiments. The operational flow / algorithmic structure 900 may be implemented by a relay UE such as, for example, relay UE 128, relay UE 104, or UE 1200 (shown in FIG. 12 and discussed further below) , or components thereof; for example, a baseband processor 1204A.
[0124] The operational flow / algorithmic structure 900 may include, at 904, generating a remote UE information sidelink message to include information associated with a plurality of downstream UEs.
[0125] In some embodiments, the information may be a collective paging monitoring request. The collective paging monitoring request may represent a number of individual paging monitoring requests collected from downstream UEs. In some embodiments, the remote UE information sidelink message may be generated to include a list of paging identifiers associated with the downstream UEs from which the individual paging monitoring requests are collected. In this manner, the downstream UEs may be associated with the collective paging monitoring request.
[0126] In some embodiments, the remote UE information sidelink message may include a list of paging identifiers, associated with downstream UEs, that are to disassociate the plurality of downstream UEs from the collective paging monitoring request. This may be used if one or downstream UEs no longer need to have paging messages monitored on their behalf.
[0127] In some embodiments, the remote UE information sidelink message may include a list of downstream UEs affected by a downstream RLF. The downstream RLF may be one or more hops away from the UE / processor generating the remote UE information sidelink message.
[0128] The operational flow / algorithmic structure 900 may further include, at 908, outputting the remote UE information sidelink message for transmission to the network.
[0129] In some embodiments, if the remote UE information sidelink message transmitted to the network includes a paging monitoring request, a UE / processor may detect and forward requested paging records in the downstream direction. In some embodiments, a UE / processor may receive individual paging records directed to target downstream UEs. If a relay UE that is upstream of the target downstream UEs is identified, a collective paging record may be generated based on the individual paging records. The collective paging record may then be output to the relay UE that is upstream of the target downstream UEs.
[0130] FIG. 10 is an operational flow / algorithmic structure 1000 in accordance with some embodiments. The operational flow / algorithmic structure 1000 may be implemented by a base station such as, for example, base station 108 or network device 1300 (shown in FIG. 13 and discussed further below) , or components thereof; for example, a baseband processor 1304A.
[0131] The operational flow / algorithmic structure 1000 may include, at 1004, receiving a sidelink UE information message. The message may be associated with a first UE that is coupled with the network through a multi-hop U2N relay path. The message may include a UE-type indication to indicate the UE is an intermediate UE type. That is, the first UE is between the remote UE and a last relay UE.
[0132] The sidelink UE information may requests transmit resources so the first UE can transmit to a second UE in the multi-hop U2N relay path. In some embodiments, the sidelink UE information message may include a destination L2 ID associated with the second UE.In these embodiments, the sidelink UE information message may also include an indication of whether the second UE is upstream or downstream from the first UE.
[0133] In some embodiments, the sidelink UE information message may include an identity of a second UE that is downstream from the first UE. The message may additionally include a number of hop between the first UE and the second UE.
[0134] In some embodiments, the sidelink UE information message may be transmitted from the first UE based on the first UE entering an RRC connected state with the network or based on a serving cell transmitting a SIB 12 block that indicates support for L2 U2N relay.
[0135] The operational flow / algorithmic structure 1000 may include, at 1008, scheduling resources based on the sidelink UE information message. An indication of the scheduled resources may then be transmitted to the first UE.
[0136] FIG. 11 is an operational flow / algorithmic structure 1100 in accordance with some embodiments. The operational flow / algorithmic structure 1100 may be implemented by a base station such as, for example, base station 108 or network device 1300 (shown in FIG. 13 and discussed further below) , or components thereof; for example, a baseband processor 1304A.
[0137] The operational flow / algorithmic structure 1100 may include, at 1104, generating an RRC reconfiguration message. The RRC reconfiguration message may include one or SL RLC channel configurations to configure first and second PC5 RLC channels for a UE. The first PC5 relay RLC channel may be provided with a first QoS configuration for upstream traffic and the second PC5 relay RLC channel may be provided with a second QoS configuration for downstream traffic. The QoS configurations may be packet delay budgets or other QoS parameters.
[0138] In some embodiments, one SL RLC channel configuration may configure both upstream and downstream PC5 relay RLC channels. In other embodiments, different SL RLC channel configurations may be used to configure the upstream and downstream PC5 relay RLC channels.
[0139] In some embodiments, the RRC reconfiguration message may include a SRAP configuration that is applied to the UE and a plurality of UEs downstream from the UE. This may be referred to as the light SRAP configuration option.
[0140] In some embodiments, the RRC reconfiguration message may include different SRAP configurations for the UE and one or more of the UEs that are downstream from the UE. This may be referred to as the heavy SRAP configuration option.
[0141] The operational flow / algorithmic structure 1100 may include, at 1108, outputting the RRC reconfiguration message for transmission to UE.
[0142] FIG. 12 illustrates a UE 1200 in accordance with some embodiments. The UE 1200 may be similar to and substantially interchangeable with UE 124.
[0143] The UE 1200 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage / current meters, or actuators) , video surveillance / monitoring devices (for example, cameras or video cameras) , wearable devices (for example, a smart watch) , or Internet-of-things devices.
[0144] The UE 1200 may include processors 1204, RF interface circuitry 1208, memory / storage 1212, user interface 1216, sensors 1220, driver circuitry 1222, power management integrated circuit (PMIC) 1224, antenna 1226, and battery 1228. The components of the UE 1200 may be implemented as integrated circuits (ICs) , portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 12is intended to show a high-level view of some of the components of the UE 1200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.
[0145] The components of the UE 1200 may be coupled with various other components over one or more interconnects 1232, which may represent any type of interface, input / output, bus (local, system, or expansion) , transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
[0146] The processors 1204 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1204A, central processor unit circuitry (CPU) 1204B, and graphics processor unit circuitry (GPU) 1204C. The processors 1204 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1212 to cause the UE 1200 to performmulti-path U2N relay operations as described herein. The processors 1204 may also include interface circuitry 1204D to enable communication by, for example, communicatively coupling the processor circuitry with one or more other components of the UE 1200.
[0147] In some embodiments, the baseband processor circuitry 1204A may access a communication protocol stack 1236 in the memory / storage 1212 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 1204A may access the communication protocol stack 1236 to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a NAS layer. In some embodiments, the PHY layer operations may additionally / alternatively be performed by the components of the RF interface circuitry 1208.
[0148] The baseband processor circuitry 1204A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0149] The memory / storage 1212 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 1236) that may be executed by one or more of the processors 1204 to cause the UE 1200 to perform various delay-adaptive operations described herein.
[0150] The memory / storage 1212 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1200. In some embodiments, some of the memory / storage 1212 may be located on the processors 1204 themselves (for example, memory / storage 1212 may be part of a chipset that corresponds to the baseband processor circuitry 1204A) , while other memory / storage 1212 is external to the processors 1204 but accessible thereto via a memory interface. The memory / storage 1212 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM) , static random access memory (SRAM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , Flash memory, solid-state memory, or any other type of memory device technology.
[0151] The RF interface circuitry 1208 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 1200 to communicate with other devices over a radio access network. The RF interface circuitry 1208 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.
[0152] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna 1226 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 1204.
[0153] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 1226.
[0154] In various embodiments, the RF interface circuitry 1208 may be configured to transmit / receive signals in a manner compatible with NR access technologies.
[0155] The antenna 1226 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 1226 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 1226 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 1226 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
[0156] The user interface 1216 includes various input / output (I / O) devices designed to enable user interaction with the UE 1200. The user interface 1216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, and projectors) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 1200.
[0157] The sensors 1220 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to some other device, module, or subsystem. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other like audio capture devices.
[0158] The driver circuitry 1222 may include software and hardware elements that operate to control particular devices that are embedded in the UE 1200, attached to the UE 1200, or otherwise communicatively coupled with the UE 1200. The driver circuitry 1222 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 1200. For example, driver circuitry 1222 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 1220 and control and allow access to sensors 1220, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
[0159] The PMIC 1224 may manage power provided to various components of the UE 1200. In particular, with respect to the processors 1204, the PMIC 1224 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
[0160] A battery 1228 may power the UE 1200, although in some examples the UE 1200 may be deployed in a fixed location and may have a power supply coupled to an electrical grid. The battery 1228 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 1228 may be a typical lead-acid automotive battery.
[0161] FIG. 13 illustrates a network device 1300 in accordance with some embodiments. The network device 1300 may be similar to and substantially interchangeable with base station 108 or a device of the core network 132 or external data network 120.
[0162] The network device 1300 may include processors 1304, RF interface circuitry 1308 (if implemented as a base station) , core network (CN) interface circuitry 1314, memory / storage circuitry 1312, and antenna structure 1326.
[0163] The components of the network device 1300 may be coupled with various other components over one or more interconnects 1328.
[0164] The processors 1304, RF interface circuitry 1308, memory / storage circuitry 1312 (including communication protocol stack 1310) , antenna structure 1326, and interconnects 1328 may be similar to like-named elements shown and described with respect to FIG. 12.
[0165] The processors 1304 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1304A, central processor unit circuitry (CPU) 1304B, and graphics processor unit circuitry (GPU) 1304C. The processors 1304 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage circuitry 1312 to cause the network device 1300 to perform multi-path U2N relay operations described herein. The processors 1304 may also include interface circuitry 1304D to enable communication by, for example, communicatively coupling the processor circuitry with one or more other components of the network device 1300.
[0166] The CN interface circuitry 1314 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the network device 1300 via a fiber optic or wireless backhaul. The CN interface circuitry 1314 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1314 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
[0167] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0168] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.Examples
[0169] In the following sections, further exemplary embodiments are provided.
[0170] Example 1 includes a method comprising: receiving, from a downstream user equipment (UE) , an uplink transmission on a first link of a multi-hop UE-to-network (U2N) relay path, wherein the first link is a PC5 link; outputting the uplink transmission on a second link of the multi-hop U2N relay path for transmission to a network; identifying an identity of a remote UE based on the uplink transmission, wherein the remote UE is different from the downstream UE; generating an entry in a routing table to associate the identity and the first link; receiving a downlink transmission to the remote UE; and outputting the downlink transmission on the first link based on the entry in the routing table.
[0171] Example 2 includes the method of example 1 or some other example herein, wherein the uplink transmission is a remote UE information sidelink message.
[0172] Example 3 includes the method of example 1 or some other example herein, wherein the identifier is a paging identifier and the downlink transmission is a paging message.
[0173] Example 4 includes the method of example 1 or some other example herein, wherein the uplink transmission is a request for system information and the downlink transmission includes the system information.
[0174] Example 5 includes the method of example 4 or some other example herein, wherein: the request for system information is a request for a system information block (SIB) and the downlink transmission includes the SIB; or the request for system information is a request for positioning system information block (posSIB) and the downlink transmission includes the posSIB.
[0175] Example 6 includes the method of example 1 or some other example herein, wherein the uplink transmission is a first radio resource control (RRC) message using signaling radio bearer (SRB) 0, the identity is a layer 2 (L2) identity of the remote UE and the DL transmission is a second RRC message using SRB 0.
[0176] Example 7 includes the method of example 1 or some other example herein, wherein the identity is in a sidelink relay adaptation protocol (SRAP) header of the uplink transmission and said outputting the downlink transmission further comprises: detecting the identity within an SRAP header of the downlink transmission; and outputting the downlink transmission on the first link based on detecting the identity within the SRAP header of the downlink transmission.
[0177] Example 8 include the method of any one of examples 1–7 or some other example herein, wherein the first link is one of a plurality of links with a corresponding plurality of downstream UEs and the downlink transmission is unicast on the first link.
[0178] Example 9 includes a method comprising: detecting a radio link failure (RLF) on a first link of a multi-hop UE-to-network (U2N) relay path from a remote user equipment (UE) to a network, wherein the first link is a first PC5 link; generating a sidelink (SL) indication type parameter to indicate the RLF; generating a SL notification message to include the SL indication type parameter; and outputting the SL notification message on a second link of the multi-hop U2N relay path, wherein the second link is a second PC5 link or is a Uu link.
[0179] Example 10 includes the method of example 9 or some other example herein, wherein the SL indication type parameter is to indicate the RLF is associated with an upstream PC5 link or a downstream PC5 link.
[0180] Example 11 includes the method of example 9 or some other example herein, wherein generating the SL notification message includes: generating the SL notification message to include one or more identifiers (IDs) respectively associated with one or more UEs impacted by the RLF.
[0181] Example 12 includes the method of example 9 or some other example herein, wherein generating the SL notification message includes: generating the SL notification message to include an indication of a location of the RLF in the multi-hop U2N relay path.
[0182] Example 13 includes the method of example 12 or some other example herein, wherein the indication of the location is a number of hops separating a node generating the SL indication type parameter from the RLF.
[0183] Example 14 include the method of any one of examples 9–13 or some other example herein, wherein the RLF is a downstream RLF and outputting the SL notification message includes: outputting the SL notification message as an upstream transmission.
[0184] Example 14 include the method of any one of examples 9–13 or some other example herein, wherein the RLF is an upstream RLF and outputting the SL notification message includes: outputting the SL notification message as a downstream transmission.
[0185] Example 16 includes a method comprising: generating a remote UE information sidelink message to include information associated with a plurality of downstream user equipments (UEs) having multi-hop UE-to-network (U2N) relay paths to a network; and outputting the remote UE information sidelink message for transmission to the network.
[0186] Example 17 includes the method of example 16 or some other example herein, wherein the information is a collective paging monitoring request and the method further comprises: collecting a plurality of individual paging monitoring requests from the plurality of downstream UEs; generating a list of paging identifiers associated with the plurality of downstream UEs; and including the list within the remote UE information sidelink message to associate the plurality of downstream UEs with the collective paging monitoring request.
[0187] Example 18 includes the method of example 16 or some other example herein, wherein the information is a collective paging monitoring request and the method further comprises: generating a list of paging identifiers associated with the plurality of downstream UEs; and including the list within the remote UE information sidelink message to disassociate the plurality of downstream UEs with the collective paging monitoring request.
[0188] Example 19 includes the method of example 18 or some other example herein, further comprising: receiving at least two individual paging records respectively directed to at least two downstream UEs; identifying a relay UE that is upstream of the at least two downstream UEs; and generating a collective paging record based on the at least two individual paging records; and outputting the collective paging record for transmission to the relay UE.
[0189] Example 20 includes the method of example 18 or some other example herein, further comprising: detecting a radio link failure (RLF) in a downstream PC5 link; identifying the plurality of downstream UEs as being affected by the RLF; andincluding the list within the remote UE information sidelink message based on said identifying the plurality of downstream UEs as being affected by the RLF.
[0190] Example 21 includes the method of example 20 or some other example herein, wherein the downstream PC5 link is between a first downstream UE and a second downstream UE.
[0191] Example 22 includes the method of example 18 or some other example herein, further comprising: entering a radio resource control (RRC) connected state with the network; including the list within the remote UE information sidelink message based on said entering the RRC connected state.
[0192] Example 23 includes the method of example 16 or some other example herein, wherein the information is a system information request.
[0193] Example 24 includes a method comprising: receiving a sidelink UE information message associated with a user equipment (UE) that is coupled with a network through a multi-hop UE-to-network (U2N) relay path, wherein the sidelink UE information message includes a UE-type indication to indicate the UE is an intermediate UE type; and scheduling resources on the multi-hop UE-to-network (U2N) relay path based on the sidelink UE information message.
[0194] Example 25 includes the method of example 24 or some other example herein, wherein the UE is a first UE and the sidelink UE information message further includes: a destination layer 2 (L2) identifier (ID) associated with a second UE for which a transmit resource is requested; andan indication of whether the second UE is upstream or downstream from the first UE.
[0195] Example 26 includes the method of example 24 or some other example herein, wherein the UE is a first UE and the sidelink UE information message further includes: an identity of a second UE that is downstream from the first UE.
[0196] Example 27 includes the method of example 26 or some other example herein, wherein the sidelink UE information message further includes: an indication of a number of hops between the first UE and the second UE.
[0197] Example 28 includes the method of example 24 or some other example herein, wherein receiving the sidelink UE information message is based on: the UE entering a radio resource control (RRC) connected state with a network; ora serving cell transmitting a system information block 12 with an indication of support for layer 2 multi-hop U2N relay.
[0198] Example 29 includes a method comprising: generating a sidelink UE information message associated with a user equipment (UE) that is coupled with a network through a multi-hop UE-to-network (U2N) relay path, wherein the sidelink UE information message includes a UE-type indication to indicate the UE is an intermediate UE type; and outputting the sideink UE information message for transmission to a network.
[0199] Example 30 includes the method of example 29 or some other example herein, wherein the UE is a first UE and the sidelink UE information message further includes: a destination layer 2 (L2) identifier (ID) associated with a second UE for which a transmit resource is requested; andan indication of whether the second UE is upstream or downstream from the first UE.
[0200] Example 31 includes the method of example 29 or some other example herein, wherein the UE is a first UE and the sidelink UE information message further includes: an identity of a second UE that is downstream from the first UE.
[0201] Example 32 includes the method of example 31 or some other example herein, wherein the sidelink UE information message further includes: an indication of a number of hops between the first UE and the second UE.
[0202] Example 33 includes the method of example 29 or some other example herein, wherein receiving the sidelink UE information message is based on: the UE entering a radio resource control (RRC) connected state with a network; ora serving cell transmitting a system information block 12 with an indication of support for layer 2 multi-hop U2N relay.
[0203] Example 34 includes a method comprising: generating a radio resource control (RRC) reconfiguration message to include one or more sidelink (SL) radio link control (RLC) channel configurations to configure first and second PC5 relay RLC channels for a user equipment (UE) on a multi-hop UE-to-network (U2N) relay path, wherein the one or more SL RLC channel configurations are to configure the first PC5 relay RLC channel with a first quality of service (QoS) configuration for upstream traffic and to configure the second PC5 relay RLC channel with a second QoS configuration for downstream traffic; andoutputting the RRC reconfiguration message for transmission to the UE.
[0204] Example 35 includes the method of example 34 or some other example herein, wherein the one or more SL RLC channel configurations include one SL RLC channel configuration, the first QoS configuration is associated with a first packet delay budget, the second QoS configuration is associated with a second packet delay budget, and the one SL RLC channel configuration includes a first SL packet delay budget field to indicate the first packet delay budget and a second SL packet delay budget field to indicate the second packet delay budget.
[0205] Example 36 includes the method of example 34 or some other example herein, wherein the one or more SL RLC channel configurations include a first SL RLC channel configuration to configure the first PC5 relay RLC channel and a second SL RLC channel configuration to configure the second PC5 relay RLC channel.
[0206] Example 37 includes the method of example 34 or some other example herein, wherein the one or more SL RLC channel configurations include a SL RLC channel configuration to be designated as a default PC5 relay RLC channel for upstream or downstream traffic forwarding.
[0207] Example 38 includes the method of example 34 or some other example herein, wherein the RRC reconfiguration message further includes: asidelink relay adaptation protocol (SRAP) configuration that is to be applied to the UE and a plurality of UEs downstream from the UE.
[0208] Example 39 includes the method of example 34 or some other example herein, wherein the RRC reconfiguration message further includes: a first sidelink relay adaptation protocol (SRAP) configuration that is to be applied to the UE; anda second SRAP configuration that is to be applied to a UE downstream from the UE.
[0209] Another example may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1–39, or any other method or process described herein.
[0210] Another example may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1–39, or any other method or process described herein.
[0211] Another example may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1–39, or any other method or process described herein.
[0212] Another example may include a method, technique, or process as described in or related to any of examples 1–39, or portions or parts thereof.
[0213] Another example may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–39, or portions thereof.
[0214] Another example may include a signal as described in or related to any of examples 1–39, or portions or parts thereof.
[0215] Another example may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1–39, or portions or parts thereof, or otherwise described in the present disclosure.
[0216] Another example may include a signal encoded with data as described in or related to any of examples 1–39, or portions or parts thereof, or otherwise described in the present disclosure.
[0217] Another example may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1–39, or portions or parts thereof, or otherwise described in the present disclosure.
[0218] Another example may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–39, or portions thereof.
[0219] Another example may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1–39, or portions thereof.
[0220] Another example may include a signal in a wireless network as shown and described herein.
[0221] Another example may include a method of communicating in a wireless network as shown and described herein.
[0222] Another example may include a system for providing wireless communication as shown and described herein.
[0223] Another example may include a device for providing wireless communication as shown and described herein.
[0224] Any of the above-described examples may be combined with any other example (or combination of examples) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0225] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
Claims
1.A method comprising:receiving, from a downstream user equipment (UE) , an uplink transmission on a first link of a multi-hop UE-to-network (U2N) relay path, wherein the first link is a PC5 link;outputting the uplink transmission on a second link of the multi-hop U2N relay path for transmission to a network;identifying an identity of a remote UE based on the uplink transmission, wherein the remote UE is different from the downstream UE;generating an entry in a routing table to associate the identity and the first link;receiving a downlink transmission to the remote UE; andoutputting the downlink transmission on the first link based on the entry in the routing table.2.The method of claim 1, wherein the identifier is a paging identifier and the downlink transmission is a paging message.3.The method of claim 1, wherein the uplink transmission is a request for system information and the downlink transmission includes the system information.4.The method of claim 1, wherein the uplink transmission is a first radio resource control (RRC) message using signaling radio bearer (SRB) 0, the identity is a layer 2 (L2) identity of the remote UE and the DL transmission is a second RRC message using SRB 0.5.The method of claim 1, wherein the identity is in a sidelink relayadaptation protocol (SRAP) header of the uplink transmission and said outputting the downlink transmission further comprises:detecting the identity within an SRAP header of the downlink transmission; andoutputting the downlink transmission on the first link based on detecting the identity within the SRAP header of the downlink transmission.6.A method comprising:detecting a radio link failure (RLF) on a first linkof a multi-hop UE-to-network (U2N) relay path from a remote user equipment (UE) to a network, wherein the first link is a first PC5 link;generating a sidelink (SL) indication type parameter to indicate the RLF;generating a SL notification message to include the SL indication type parameter; andoutputting the SL notification message on a second link of the multi-hop U2N relay path, wherein the second link is a second PC5 link or is a Uu link.7.The method of claim 6, wherein the SL indication type parameter is to indicate the RLF is associated with an upstream PC5 link or a downstream PC5 link.8.The method of claim 6, wherein generating the SL notification message includes:generating the SL notification message to include one or more identifiers (IDs) respectively associated with one or more UEs impacted by the RLF.9.The method of claim 6, wherein generating the SL notification message includes:generating the SL notification message to include an indication of a location of the RLF in the multi-hop U2N relay path, wherein the indication of the location is a number of hops separating a node generating the SL indication type parameter from the RLF.10.A method comprising:generating a remote UE information sidelink message to include information associated with a plurality of downstream user equipments (UEs) having multi-hop UE-to-network (U2N) relay paths to a network; andoutputting the remote UE information sidelink message for transmission tothe network.11.The method of claim 10, wherein the information is a collective paging monitoring request and the method further comprises:collecting a plurality of individual paging monitoring requests from the plurality of downstream UEs;generating a list of paging identifiers associated with the plurality of downstream UEs; andincluding the list within the remote UE information sidelink message to associate the plurality of downstream UEs with the collective paging monitoring request.12.The method of claim 10, wherein the information is a collective paging monitoring request and the method further comprises:generating a list of paging identifiers associated with the plurality of downstream UEs; andincluding the list within the remote UE information sidelink message to disassociate the plurality of downstream UEs with the collective paging monitoring request.13.The method of claim 12, further comprising:receiving at least two individual paging records respectively directed to at least two downstream UEs;identifying a relay UE that is upstream of the at least two downstream UEs; andgenerating a collective paging record based on the at least two individual paging records; andoutputting the collective paging record for transmission to the relay UE.14.The method of claim 12, further comprising:detecting a radio link failure (RLF) in a downstream PC5 link;identifying the plurality of downstream UEs as being affected by the RLF; andincluding the list within the remote UE information sidelink message based on said identifying the plurality of downstream UEs as being affected by the RLF.15.The method of claim 12, further comprising:entering a radio resource control (RRC) connected state with the network;including the list within the remote UE information sidelink message based on said entering the RRC connected state.16.A method comprising:receiving a sidelink UE information message associated with a user equipment (UE) that is coupled with a network through a multi-hop UE-to-network (U2N) relay path, wherein the sidelink UE information message includes a UE-type indication to indicate the UE is an intermediate UE type; andscheduling resources on the multi-hop UE-to-network (U2N) relay path based on the sidelink UE information message.17.The method of claim 16, wherein the UE is a first UE and the sidelink UE information message further includes:a destination layer 2 (L2) identifier (ID) associated with a second UE for which a transmit resource is requested; andan indication of whether the second UE is upstream or downstream from the first UE.18.A method comprising:generating a sidelink UE information message associated with a user equipment (UE) that is coupled with a network through a multi-hop UE-to-network (U2N) relay path, wherein the sidelink UE information message includes a UE-type indication to indicate the UE is an intermediate UE type; andoutputting the sideink UE information message for transmission to a network.19.The method of claim 18, wherein the UE is a first UE and the sidelink UE information message further includes:a destination layer 2 (L2) identifier (ID) associated with a second UE for which a transmit resource is requested; andan indication of whether the second UE is upstream or downstream from the first UE.20.The method of claim 18, wherein receiving the sidelink UE information message is based on:the UE entering a radio resource control (RRC) connected state with a network; ora serving cell transmitting a system information block 12 with an indication of support for layer 2 multi-hop U2N relay.21.A method comprising:generating a radio resource control (RRC) reconfiguration message to include one or more sidelink (SL) radio link control (RLC) channel configurations to configure first and second PC5 relay RLC channels for a user equipment (UE) on a multi-hop UE-to-network (U2N) relay path, wherein the one or more SL RLC channel configurationsare to configure the first PC5 relay RLC channel with a first quality of service (QoS) configuration for upstream traffic and to configure the second PC5 relay RLC channel with a second QoS configuration for downstream traffic; andoutputting the RRC reconfiguration message for transmission to the UE.22.The method of claim 21, wherein the one or more SL RLC channel configurations include a first SL RLC channel configuration to configure the first PC5 relay RLC channel and a second SL RLC channel configuration to configure the second PC5 relay RLC channel.23.The method of claim 21, wherein the one or more SL RLC channel configurations include a SL RLC channel configuration to be designated as a default PC5 relay RLC channel for upstream or downstream traffic forwarding.24.The method of claim 21, wherein the RRC reconfiguration message further includesa sidelink relay adaptation protocol (SRAP) configuration that is to be applied to the UE and a plurality of UEs downstream from the UE.25.The method of claim 21, wherein the RRC reconfiguration message further includesa first sidelink relay adaptation protocol (SRAP) configuration that is to be applied to the UE anda second SRAP configuration that is to be applied to a UE downstream from the UE.
