Search

US-12628071-B2 - Identifying relay user equipment for sidelink relay

US12628071B2US 12628071 B2US12628071 B2US 12628071B2US-12628071-B2

Abstract

The present application relates to devices and components including apparatus, systems, and methods for managing relay identifiers for sidelink relays in wireless networks.

Inventors

  • Zhibin Wu
  • Shu Guo
  • Chunxuan Ye
  • Haijing Hu
  • Haitong Sun
  • Seyed Ali Akbar FAKOORIAN
  • Sudeep Manithara Vamanan
  • Yuqin Chen

Assignees

  • APPLE INC.

Dates

Publication Date
20260512
Application Date
20211021

Claims (15)

  1. 1 . One or more non-transitory, computer-readable media having instructions that, when executed, cause processing circuitry to: receive, from a base station, a message with an indication to report user equipment (UE)-chosen identifiers (IDs) used for relay services and a keep interval value, at least one UE-chosen ID is identified as being within a time period based on the keep interval value; identify the at least one UE-chosen ID used for relay services, the at least one UE-chosen ID being chosen based on upper layer information; and generate a report for transmission to the base station with an indication of the at least one UE-chosen ID.
  2. 2 . The one or more non-transitory, computer-readable media of claim 1 , wherein the instructions, when executed, further cause the processing circuitry to: determine the keep interval value is provided as zero, is not provided, or is not defined; and identify a most recently used UE-chosen ID as the at least one UE-chosen ID based on said determining.
  3. 3 . The one or more non-transitory, computer-readable media of claim 1 , wherein the at least one UE-chosen ID includes a plurality of UE-chosen IDs and the instructions, when executed, further causes the processing circuitry to: generate the report to include an indication of a most recently used UE-chosen ID of the plurality of UE-chosen IDs.
  4. 4 . A method, comprising: identifying a system information block (SIB) received from a base station, the SIB requesting reporting of an identifier (ID) of a user equipment (UE); setting the ID based on upper layer information, the ID for inclusion in relay discovery messages; and generating, for transmission, a message that indicates the ID for the UE.
  5. 5 . The method of claim 4 , wherein the ID comprises a source layer 2 (L2) ID.
  6. 6 . The method of claim 4 , wherein the UE acts as a relay UE, and wherein the UE acting as the relay UE comprises the UE acting as a layer 2 (L2) UE-to-network (U2N) relay UE.
  7. 7 . The method of claim 4 , wherein the upper layer information is received via upper layer signaling.
  8. 8 . The method of claim 7 , wherein setting the ID of the UE comprises: receiving, from a policy control function (PCF), the ID for the UE; and setting the ID of the UE for inclusion in relay discovery messages to the ID for the UE received from the PCF.
  9. 9 . The method of claim 8 , wherein receiving, from the PCF, the ID for the UE comprises receiving proximity service (ProSe) parameters that include the ID for the UE, the ProSe parameters being encoded with a ProSe policy (ProSeP) data structure.
  10. 10 . The method of claim 7 , wherein further comprising receiving, from the upper layer, an upper layer message that indicates the ID for the UE.
  11. 11 . The method of claim 4 , wherein the UE acts as a relay UE by supporting relay services for one or more other UEs.
  12. 12 . The method of claim 4 , wherein the UE is a first UE, wherein the upper layer information is received from the base station based on a measurement report produced by a second UE, and wherein the measurement report is utilized to identify the first UE as a target relay for the second UE.
  13. 13 . A method, comprising: generating, for transmission to a user equipment (UE), a system information block (SIB) to elicit an identifier (ID) of the UE used for relay services when the UE is acting as a relay UE; and receiving, from the UE, a message that indicates the ID of the UE, the ID chosen based on upper layer information.
  14. 14 . The method of claim 13 , wherein the ID comprises a source layer 2 (L2) ID.
  15. 15 . The method of claim 13 , wherein the UE is a first UE, and wherein the method further comprises: receiving, from a second UE, a measurement report; and determining that the first UE is a target relay for the second UE, wherein the transmission is transmitted to the first UE based on the determination that the first UE is the target relay for the second UE.

Description

CROSS-REFERENCE TO RELATED APPLICATION This application is a 371 U.S. National Phase of PCT International Patent Application No. PCT/CN2021/125350, filed Oct. 21, 2021, which is herein incorporated by reference in its entirety for all purposes. BACKGROUND Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for New Radio (NR) wireless networks. These TSs describe aspects related to relay services that may be provided by a relay user equipment (UE) for the benefit of a remote UE. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 illustrates a network environment in accordance with some embodiments. FIG. 2 illustrates a mobility scenario in the network in accordance with some embodiments. FIG. 3 illustrates a signaling flow in accordance with some embodiments. FIG. 4 illustrates signaling of a relay discovery announcement in accordance with some embodiments. FIG. 5 illustrates a procedure of a first aspect in accordance with some embodiments. FIG. 6 illustrates a procedure of a second aspect in accordance with some embodiments. FIG. 7 illustrates a procedure of a third aspect in accordance with some embodiments. FIG. 8 illustrates a procedure for configuring and reporting identity history in accordance with some embodiments. FIG. 9 illustrates a procedure of a fourth aspect in accordance with some embodiments. FIG. 10 illustrates a procedure of a fifth aspect in accordance with some embodiments. FIG. 11 illustrates an operation flow/algorithmic structure in accordance with some embodiments. FIG. 12 illustrates another operation flow/algorithmic structure in accordance with some embodiments. FIG. 13 illustrates another operation flow/algorithmic structure in accordance with some embodiments. FIG. 14 illustrates a user equipment in accordance with some embodiments. FIG. 15 illustrates a network device in accordance with some embodiments. DETAILED DESCRIPTION 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, and techniques 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/B” and “A or B” mean (A), (B), or (A and B). The following is a glossary of terms that may be used in this disclosure. The term “circuitry” as used herein refers to, is part of, or includes hardware components that are configured to provide the described functionality. The hardware components may include 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)), or a digital signal processor (DSP). 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. 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. 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