RELAY USER EQUIPMENT IDENTIFICATION FOR SIDELINK RELAY
The introduction of unique relay UE identifiers managed by the core network or base station addresses the disambiguation issues in NR wireless networks, enhancing network reachability and handover efficiency.
Patent Information
- Application Number
- JP2024523719
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-10-21
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2041-10-21
AI Technical Summary
Existing relay UE discovery protocols in New Radio (NR) wireless networks lack a unique identifier for relay user equipment (UE), leading to disambiguation and reachability issues during handover processes, as current identifiers are not unique and can cause difficulties in tracking relay UEs by the network.
Implementing a system where relay UE identifiers are managed and assigned by the core network (CN) or base station, ensuring uniqueness and synchronization through various methods such as NGAP signaling, RRC reconfiguration, and UE ID history reporting, allowing for efficient tracking and management of relay UEs.
Enhances network reachability and handover feasibility by ensuring unique relay UE identification, reducing misjudgment of handover candidates and improving network management of relay services.
Smart Images

Figure 2024540954000001_ABST
Abstract
Description
[Background technology]
[0001] The Third Generation Partnership Project (3GPP) Technical Specifications (TS) 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 a remote UE. [Brief description of the drawings]
[0002] [Figure 1] 1 illustrates a network environment according to some embodiments.
[0003] [Diagram 2] 1 illustrates a mobility scenario in a network according to some embodiments.
[0004] [Diagram 3] 1 illustrates a signaling flow according to some embodiments.
[0005] [Figure 4] 1 illustrates signaling for relay discovery announcement according to some embodiments.
[0006] [Diagram 5] 1 illustrates a procedure of a first aspect, according to some embodiments.
[0007] [Figure 6] 1 illustrates a procedure of a second aspect, according to some embodiments.
[0008] [Figure 7] 13 illustrates a procedure of a third aspect, according to some embodiments.
[0009] [Figure 8]1 illustrates a procedure for configuring and reporting identity history according to some embodiments.
[0010] [Figure 9] 13 illustrates a procedure of a fourth aspect, according to some embodiments.
[0011] [Figure 10] 13 illustrates a procedure of a fifth aspect, according to some embodiments.
[0012] [Figure 11] FIG. 1 illustrates an example operational flow / algorithm structure according to some embodiments.
[0013] [Figure 12] FIG. 13 illustrates another example operational flow / algorithm structure according to some embodiments.
[0014] [Figure 13] FIG. 13 illustrates another example operational flow / algorithm structure according to some embodiments.
[0015] [Figure 14] 1 illustrates a user equipment according to some embodiments.
[0016] [Figure 15] 1 illustrates a network device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] 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 of certain structures, architectures, interfaces, and techniques are set forth in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of various embodiments may be practiced in other examples that depart from these specific details. In some cases, 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 purposes of this document, the phrases "A / B" and "A or B" mean (A), (B), or (A and B).
[0018] Below is a glossary of terms that may be used in this disclosure.
[0019] The term "circuitry" as used herein refers to, is a part of, or includes a hardware component configured to provide a described function. The hardware component may include electronic circuits, logic circuits, processors (shared, dedicated, or group) or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, programmable systems on chips (SoCs)), or digital signal processors (DSPs). In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuitry" may also refer to the combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit configuration.
[0020] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or the recording, storage, or transfer of digital data. The term "processor circuitry" may refer to an application processor, a 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 that can execute or otherwise operate computer-executable instructions, such as program code, software modules, or functional processes.
[0021] As used herein, the term "interface circuitry" refers to, is a 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, such as a bus, an I / O interface, a peripheral component interface, and a network interface card.
[0022] The term "user equipment" or "UE" as used herein refers to a device having wireless communication capabilities that may enable a user to access network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless equipment, reconfigurable wireless equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.
[0023] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. In addition, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and configured to share computing or networking resources.
[0024] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, databases and applications, or workload units. A "hardware resource" may refer to a computational, storage, or network resource provided by a physical hardware element. A "virtualized resource" may refer to a computational, storage, or network resource provided by a virtualization infrastructure to an application, device, or system. The term "network resource" or "communication resource" may refer to a resource accessible by a computer device / system through a communication network. The term "system resource" may refer to any kind of shared entity for providing a service and may include a computing resource or a network resource. A system resource may be considered as a set of coherent functions, network data objects, or services, where such system resources reside on a single host or multiple hosts and are accessible through a clearly identifiable server.
[0025] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.
[0026] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, such as may occur during the execution of program code.
[0027] The term "connected" may mean that two or more elements at a common communications protocol layer have an established signaling relationship with each other via a communications channel, link, interface, or reference point.
[0028] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered or referred to as synonymous with a networked computer, networking hardware, network equipment, network node, or virtualized network function.
[0029] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an information element or an individual content of a data element that contains the content. An information element may contain one or more further information elements.
[0030] 1 illustrates a network environment 100 according to some embodiments. The network environment 100 may include a UE 104, a UE 106, and a base station 108 of a radio access network (RAN). The base station (BS) 108 may be a next-generation (NG)-RAN next-generation Node B (gNB) that provides one or more 5G New Radio (NR) cells. The NR cells may present NR user plane and control plane protocol terminations towards the UE 104 / 106.
[0031] The network environment 100 may further include a Core Network (CN) 112. For example, the CN 112 may comprise a fifth generation core network (5GC). The CN 112 may be coupled to the base stations 108 via optical fiber or wireless backhaul. The CN 112 may provide functions for the UEs 104 via the base stations 108. These functions may include managing subscriber profile information, subscriber location, service authentication, or voice and data session switching functions. The CN 112 may include an Access and Mobility Function (AMF) 120, which is responsible for registration management (e.g., for registering the UEs 104, etc.), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The CN 112 may also include a Policy Control Function (PCF) that provides policies associated with mobility and session management. The functions provided by the CN 112 may be implemented in one or more servers or other devices at a centralized or distributed location.
[0032] The UE 104 may be located in an NR cell provided by the base station 108 and may be coupled to the base station 108 via an NR Uu interface. The UE 104 may also have a sidelink connection with the UE 106, which may also be referred to as a remote UE 106, via a sidelink physical interface, which may also be referred to as a PC5 interface. The UE 104 may act as a UE-to-Network (U2N) relay to extend network coverage to the remote UE 106. The UE 104 may be referred to as a relay UE 104. The remote UE 106 may be outside of the network coverage due to the location of the remote UE 106 being outside of the NR cell or due to the remote UE 106 having turned off its Uu modem and only operating its sidelink modem, for example, to save power. By providing a Layer 2 UE-NW relay, the remote UE 106 may be accessible and controllable by the base station 108 via an end-to-end NR Uu interface, including the PC5 interface and the NR Uu interface.
[0033] Except as otherwise described herein, devices of the network environment 100 may provide Proximity Services (ProSe) direct discovery, direct communication, and UE-network relaying consistent with the descriptions provided in 3GPP TS 24.555 v0.4.0 (2021-08).
[0034] FIG. 2 illustrates devices of the network environment 100 for a mobility scenario, according to some embodiments. In particular, the mobility scenario may correspond to an intra-BS direct-indirect handover. This type of handover may occur when the remote UE 106 selects a relay (e.g., relay UE 104) camped on the same base station (e.g., base station 108) to which the remote UE 106 was originally connected as the target of the handover. Thus, the remote UE 106 may be under the control of the same base station before and after the handover. These types of handovers may occur for several reasons, including, for example, the remote UE 106 moving out of the coverage of the base station 108, the remote UE 106 powering down its NR Uu modem, or based on a determination that the remote UE 106 can be better served by the relay UE 104 in terms of uplink throughput or reliability.
[0035] FIG. 3 shows a signaling flow 300 illustrating an intra-BS direct-to-indirect handover, according to some embodiments.
[0036] The signaling flow 300 may include, at 304, the remote UE 106 and the base station 108 exchanging uplink / downlink data directly over the NR Uu interface.
[0037] The signaling flow 300 may further include measurement configuration and reporting at 308. The remote UE 106 may measure / discover several candidate U2N relay UEs and send a resulting report to the network. The report may correspond to one or more candidate U2N relay UEs and legacy Uu measurements. The remote UE 106 may filter suitable U2N relay UEs based on relay selection criteria before reporting. The remote UE 106 may report only U2N relay UE candidates that meet higher layer criteria that may be configured in the remote UE 106 by the network. The report may include U2N relay UE identifier (ID), NR serving cell ID (NCI) of the U2N relay UE, and sidelink discovery-reference signal received power (SD-RSRP) information.
[0038] At 316, the base station 108 may decide to switch the remote UE 106 to a target U2N relay UE, e.g., the relay UE 104. The base station 108 may then send a radio resource control (RRC) reconfiguration message to the relay UE 104 to configure the relay UE 104 to provide relay services for the remote UE 106 at 312. The base station 108 may also send an RRC reconfiguration message to the remote UE 106 at 316. The RRC reconfiguration message sent to the remote UE 106 may include a relay UE ID and a PC5 radio link control (RLC) configuration for relay traffic and associated end-to-end radio bearers. The remote UE 106 may stop user plane and control plane transmissions over the Uu interface after receiving the RRC reconfiguration message from the base station 108.
[0039] The signaling flow 300 may further include, at 320, the remote UE 106 establishing a PC5 connection with the relay UE 104. In some instances, the PC5 connection may have been previously established and no connection needs to be established at this point.
[0040] At 324, the signaling flow 300 may include the remote UE 106 sending an RRC reconfiguration complete message to the base station 108 to complete the path switch procedure. The RRC reconfiguration complete message may be sent to the base station 108 via the relay UE 104. The data path may then be switched from the direct path to the indirect path. At 328, uplink and downlink data may be exchanged between the remote UE 104 and the base station 108 via an end-to-end NR Uu connection. As shown in FIG. 1, the end-to-end NR Uu connection includes a PC5 connection between the remote UE 106 and the relay UE 104 and an NR Uu connection between the relay UE 104 and the base station 108.
[0041] The U2N Relay UE ID (or simply "Relay UE ID") used in the mobility scenario illustrated in Figure 3 is a commonly shared identifier between the remote UE 106, the relay UE 104, and the base station 108. This sharing may be desirable in L2 relay, but may not be required in L3 relay. In contrast to an L2 relay UE, an L3 relay UE may not need to be synchronized with the base station since the relay service may be transparent to the NG-RAN.
[0042] 4 illustrates signaling of a relay discovery announcement 400 according to some embodiments. A relay UE 104 may send a relay discovery announcement 400 to a remote UE 106 as part of a discovery procedure. The discovery procedure may be a Model A or B procedure similar to that described in Section 5.3.1.2 of Technical Specification (TS) 23.303 v16.0.0 (2020-07-09).
[0043] The Model A procedure, sometimes colloquially referred to as the "I am here" procedure, may define two roles for UEs participating in ProSe direct discovery. The first role may be that of an announcing UE that announces certain information that may be used by nearby UEs that have permission to discover. The relay UE 104 may play the first role and act as the announcing UE. The second role may be that of a monitoring UE that monitors certain information of interest in the vicinity of the announcing UE. The remote UE 104 may play the second role and act as the monitoring UE. In this model, the announcing UE may broadcast relay discovery announcements 400 at predefined discovery intervals. The monitoring UEs that are interested in these announcements may read and process them.
[0044] The Model B procedure, which may be colloquially referred to as the "Who is there? / Are you there?" procedure, may also define two roles for ProSe-enabled UEs participating in ProSe direct discovery. The first role may be that of a discovering UE that sends a request containing specific information about what it is interested in discovering. The remote UE 106 may play the first role and act as a discovering UE. The second role may be that of a discovered UE that can receive the request message and respond with some information related to the discoverer's request. The relay UE 104 may play the second role and act as a discovered UE. Thus, the discovering UE may send information about other UEs from which it would like to receive a response. For example, the information may be about a ProSe application identity corresponding to a group, and members of the group may respond. In response, the relay UE 104 may send a relay discovery announcement 400.
[0045] The relay discovery announcement 400 may include various fields organized in a Layer 1 (L1) / L2 header, higher layer discovery message content, and application layer information.
[0046] The L1 / L2 header may include fields for carrying a source (src) L2 ID, a destination (dst) L2 ID, a media access control (MAC) content, a radio link control (RLC) content, and a packet data convergence protocol (PDCP) header.
[0047] The upper layer discovery message content may include a Model A / B field to carry an indication of whether Model A or Model B discovery type is supported. The upper layer discovery message content may further include a Layer 2 / 3 field to carry an indication of whether the relay UE 104 can operate as an L2 or L3 relay. The upper layer discovery message content may further include a Relay Service Code (RSC) field to carry an RSC that provides an indication of the type of relay service provided by the relay UE 104. The upper layer discovery message content may further include an NCI field to include an ID of the NR cell on which the relay UE 104 is camped. The upper layer discovery message content may further include a Public Land Mobile Network (PLMN) field to provide an indication of the PLMN to which the relay UE 104 is connected.
[0048] The application layer information may include user information that may be provided to the application layer of the remote UE 106.
[0049] The relay discovery message may be used by relay UEs to advertise access services on behalf of the network. However, when the network uses the relay discovery message in the legacy discovery procedure, it may not be able to track which advertisements are announced by which relay UEs. This may be because the legacy message lacks a relay UE ID and the existing fields are insufficient to uniquely identify the relay UE. For example, the relay service code, which may be assigned by higher layers, may be shared by a group of relay UEs rather than a unique identifier. The source L2 ID is self-selected by the relay UE 104, and the destination L2 ID is a common broadcast address. This may cause various disambiguation and reachability problems. For example, a base station may have difficulty reaching a relay UE for handover.
[0050] Thus, embodiments describe how the relay UE ID should be defined, the temporal nature of the relay UE ID (e.g., whether it is persistent, semi-persistent, or dynamically changed), and how to change the relay UE ID such that all parties are synchronized with the change.
[0051] Various embodiments also describe how the relay UE 104 should signal the relay UE ID in the relay discovery announcement. As described in more detail below, the relay UE ID may be provided in the source L2 ID field or in a new field in the higher layer discovery message content. In some cases, the new field may be in the ProSe layer. If the relay UE ID is provided in the source L2 ID field, it may be part or all of the 24-bit source L2 ID. If the relay UE ID is provided in a new field in the higher layer discovery message content, it may or may not be 24-bit.
[0052] 5 illustrates a procedure 500 of a first aspect of the disclosure in which a higher layer approach is used to create and assign a relay UE ID, according to some embodiments. In the first aspect, a network function of the CN 112 may provide a higher layer relay UE ID to the relay UE 104. The relay UE ID may also be provided to the base station 108 via Next Generation Application Protocol (NGAP) signaling together with a ProSe relay grant. Changing the relay UE ID may be controlled by the CN 112.
[0053] The PCF 120 may provision the relay UE 104 (and other relay UEs) with ProSe parameters. The ProSe parameters may include a relay UE ID along with a relay service code. The ProSe parameters may be provisioned to the relay UE as part of a UE policy encoded in a ProSeP (ProSe Policy) data structure. In particular, the relay UE ID(s) may be provided along with the RSC list. ProSeP may be provided to the relay UE 104 using a UE policy delivery service such as that described in 3GPP TS 24.501 v17.4.1 (2021-09-27).
[0054] The AMF 116 can send an NGAP message to the NG-RAN (e.g., the base station 108) based on the ProSe parameters. The NGAP message can include a relay UE ID along with a ProSe permission of whether the relay UE 104 is authorized to operate as a 5G ProSe L2 U2N relay. In some embodiments, the NGAP message can be part of a UE context modification request or an initial context setup request message.
[0055] The relay UE ID may be an N-bit identifier associated with the relay UE 104 for the provision of the relay service. In some embodiments, if the relay UE 104 supports multiple relay services, it may be associated with a respective multiple relay UE identifiers. Each relay UE identifier may correspond to one or more relay UE services. The relay UE 104 may then identify the provided relay service by including the corresponding relay UE ID in a relay discovery message (e.g., a relay discovery announcement).
[0056] Upon receiving the relay UE ID from the remote UE 106 report (or from another base station via inter-base station signaling), the base station 108 can locate the UE context associated with the relay UE 104 (assuming the relay UE 104 is currently connected to the base station 108). The base station 108 can then reconfigure the relay UE 104 and the remote UE 106 for relay services as described above with respect to FIG.
[0057] The second and third aspects of the present disclosure provide a lower layer approach in which the relay UE ID is generated and managed by the relay UE 104 or the base station 108 without involvement from the core network 112. The base station 108 may discard the relay UE ID whenever the UE context is deleted. This may occur when the relay UE 104 enters an RRC idle state. The base station 108 may maintain an ID space such that relays in its cell(s) do not use the same ID. This may ensure uniqueness among relay UEs in an RRC connected state. The relay UE ID may be determined or confirmed every time a relay UE enters an RRC connected state in a cell.
[0058] 6 illustrates a procedure 600 for a second aspect of the disclosure in which a lower layer approach is used to create and assign a relay UE ID, according to some embodiments. In the second aspect, the base station 108 may select a unique identifier for the relay UE 104 to use as its relay UE ID. The base station 108 may then provide an indication of the ID in an RRC message sent to the relay UE 104. In some embodiments, the relay UE ID may be the same as, or at least based on, the Cell RNTI (C-RNTI).
[0059] The procedure 600 may include, at 604, the relay UE 104 sending sidelink UE information to the base station 108. The sidelink UE information may include an identity request. In some embodiments, the sidelink UE information may also include a UE selection identity currently or previously used by the relay UE 104 for the relay service.
[0060] At 608, the base station may select an unused ID, which may be based on the ID request in the sidelink UE information received at 604. However, in other embodiments, the base station 108 may initiate the procedure 600 autonomously, without relying on a request from the relaying UE 104.
[0061] The unused ID may be selected based on an ID space that includes a list of currently associated or unassociated IDs. In this manner, the base station may identify a unique identifier that may be assigned to the relaying UE as a relaying UE ID.
[0062] In some embodiments, the Relay UE ID may be the same as, or at least based on, the 16-bit C-RNTI. This may avoid the burden of having a separate cell management ID. Furthermore, there are fewer privacy concerns regarding the use of the C-RNTI in announcement messages, given that this identifier is already exposed at the Access Stratum (AS) layer.
[0063] At 612, the base station may send the NW-allocated ID to the relay UE for use as a relay UE ID. The identifier may be sent to the relay UE 104 in an RRC reconfiguration message.
[0064] FIG. 7 illustrates a procedure 700 for a third aspect of the disclosure in which a lower layer approach is used to create and assign relay UE IDs, according to some embodiments. In the third aspect of the disclosure, another lower layer approach may be used to create and assign relay UE IDs. In this aspect, the relay UE 104 may select an identifier and convey it to the base station 108. The base station 108 may confirm the selection or override it with a different ID (e.g., if the selected identifier is already associated with another relay UE, resulting in a collision). The base station 108 may then send a confirmation or a new identifier back to the relay UE 104.
[0065] The procedure 700 may include, at 704, the relay UE 104 transmitting sidelink UE information to the base station 108. The sidelink UE information may include a UE selection ID. In some embodiments, the sidelink UE information may further include one or more UE selection IDs that were previously used as relay UE IDs.
[0066] At 708, the base station 108 may check to determine whether the UE selection ID is used by another UE in the same cell. The result of this determination may affect whether the base station 108 sends a confirmation or override indication in an RRC reconfiguration message at 712. If the UE selection ID is used by another in the same cell, the base station 108 may select an unused ID that the relay UE 104 may use as a relay UE ID. Then, at 712, the NW selection ID may be sent with an override indication in an RRC reconfiguration message. This may be similar to that described above with respect to FIG. 6. If the UE selection ID is not used by another in the same cell, the base station 108 may send a confirmation indication in an RRC reconfiguration message at 712.
[0067] There may be various reasons why it may be desirable to change the relay UE ID. For example, the relay UE 104 may want to change its ID periodically to protect its own privacy. In another example, the network may want to assign a new relay UE ID to the relay UE 104 to facilitate management at the cell level. In various embodiments, the relay UE ID may change based on a UE trigger or a base station trigger. The assignment of an updated relay UE ID may be based on procedures described elsewhere, e.g., procedures 600 or 700.
[0068] In some embodiments, the relay UE 104 may receive an RRC release and transition from a connected state to an idle or inactive state. After the relay UE 104 transitions to an idle or inactive state, it may continue to use the previously assigned relay UE ID. This may be true even if the relay UE 104 has left the current cell and is not reachable after transitioning from the connected state.
[0069] In the AS layer solution, the relay UE ID is assumed to identify a relay UE in an RRC connected state. However, the relay UE 104 may use an identifier (possibly a self-selected ID) in the discovery message before entering the connected state. Thus, some embodiments may include the relay UE 104 providing the base station with a UE-selected ID that may have been used during an RRC idle or inactive state. See, for example, messages 604 or 704. Providing the UE-selected ID to the network in this manner may help the network track relay UE ID usage history.
[0070] The network may benefit from understanding the history of relay UE ID changes in order to associate measurement reports of remote UEs of various IDs with the appropriate relay UE. For example, with respect to the second aspect of the present disclosure, if the relay UE 104 does not provide an indication of the previous / current UE selection IDs, the base station 108 will not be able to link previous measurement reports (by the remote UE) containing those IDs with the relay UE 104 after it newly (re)connects with the base station 108. Also, with respect to the third aspect of the present disclosure, it may not be sufficient for the relay UE to report its current UE selection ID. For example, the base station may not have information about the UE selection ID used by the relay UE 104 before the current UE selection ID, which may be indicated in the measurement report from the remote UE. In either case, if the network fails to associate the measurement report with the relay UE 106 due to an unknown association between the relay UE 106 and the UE selection ID, the network may erroneously determine the feasibility of the relay UE 106 to operate as a handover candidate.
[0071] In some embodiments, the relay UE may report all UE selected UDs used over a certain time interval before (re)connecting with the network. The time interval defining the length of the ID history may be configured by the network or may be predefined as a fixed value in the TS, e.g. 10 seconds.
[0072] 8 illustrates a procedure 800 for configuring and reporting relay UE ID history, according to some embodiments. In the procedure 800, the relay UE 104 may report a sequence of previous and currently used relay UE IDs to the base station 108 via RRC signaling. This may occur when the relay UE 104 transitions from an idle / inactive state to a connected state. Reporting the relay UE ID history may occur at additional times in some instances.
[0073] At 804, the procedure 800 may include the base station 108 sending a configuration message with an indication that the UE should report a UE selection ID used for relay services. In some embodiments, the message may include a relay ID history retention interval (hereinafter, "retention interval") value. The configuration information may be a system information block (SIB) as part of a common U2N relay configuration or may be a dedicated RRC signaling (e.g., an RRC reconfiguration message). Alternatively, the retention interval value may be defined as a fixed value (e.g., 10 seconds).
[0074] At 808, the relay UE 104 may maintain a list of relay UE IDs used for relay discovery during a time interval defined by the retention interval value. For example, if the retention interval value is N seconds, the relay UE may maintain a list of all relay UE IDs used for relay discovery during the previous N seconds.
[0075] At 812, the relay UE 104 may establish an RRC connection with the base station 108.
[0076] At 816, the relay UE 104 may transmit sidelink UE information NR to the base station 108. The sidelink UE information NR may include a current version of the list of relay UE IDs maintained by the relay UE 104. For example, the relay UE 104 may report a list of all IDs used in a window [t,t], where t is the time to report sidelink UE information NR and N is a retention interval value.
[0077] In some embodiments, the reported list of relay UE IDs may always start with the current relay UE ID. Alternatively, the current relay UE ID may be transmitted in a separate standalone information element. If the report transmitted at 816 includes multiple UE selected IDs, it may also include an indication of the most recently used ID.
[0078] If a retention interval value is not provided in the configuration message or is not otherwise defined, the relaying UE 104 may only report the most recently used UE selection ID.
[0079] FIG. 9 illustrates a procedure 900 of a fourth aspect of the disclosure in which a lower layer approach is used to create and assign relay UE IDs, according to some embodiments. In the fourth aspect of the disclosure, relay UE IDs may be assigned by the NG-RAN for a group of cells. The relay UE IDs may be unique among a large area that includes two or more cells. In some embodiments, the relay UE IDs may be assigned / managed by a centralized unit in the NG-RAN, for example, a gNB centralized unit (CU).
[0080] The procedure 900 may include, at 904, the base station 108 sending an RRC release to the relay UE 104. The RRC release may include a suspend configuration (suspendConfig) that includes an inactive RNTI (I-RNTI) that may be used to identify a suspended UE context of the relay UE 104 while in the inactive state. The RRC release may further include a relay ID (IDx) assigned to the relay UE 104 to be used while the relay UE 104 is in the inactive state. In this manner, the relay UE ID is associated with the I-RNTI when the relay UE 104 enters RRC_INACTIVE.
[0081] The relay UE 104 may use the assigned relay UE IE (IDx) in the PC5 relay announcement 908 transmitted while within the RAN-based notification area (RNA) of the base station 108. Any base station in the RNA that receives a measurement report with IDx may be able to determine that IDx is associated with the relay UE 104 based on RAN paging. For example, a base station may receive a measurement report with IDx and use the I-RNTI associated with IDx to retrieve the suspended UE context of the relay UE 104. It may use the suspended UE context to page the relay UE 104 to put it into a connected state so that it may perform handover preparation.
[0082] If the base station 108 receives a measurement report with the relay UE ID and an indication of a serving cell provided by the base station 108, the base station 108 may have a suspended UE context stored locally. Thus, it may page the relay UE 104 based on the I-RNTI. However, in some cases, the base station 108 may receive a measurement report with the relay UE ID and an indication of a serving cell provided by another base station in the same RNTI. In this case, the base station 108 may send a request to the other base station for the suspended UE context associated with the relay UE ID. Upon receiving the suspended UE context, the base station 108 may proceed to page the relay UE ID and prepare for handover.
[0083] At 912, the relay UE 104 may move out of the RNA and may need to change its relay UE ID to ensure RAN paging reachability. To do this, the relay UE 104 may send an RRC resume request to the base station 908 of the new RNA at 916. The RRC resume request may include an RNA update element and a relay ID update request.
[0084] At 920, the base station 908 may send an RRC RELEASE message with the suspend configuration and an updated relay UE ID (relayID(y)) to be used while the relay UE 104 is in the inactive state. The relay UE 104 may use the newly assigned relay UE IE (IDy) in the PC5 relay announcement 924 sent while in the RNA of the base station 908.
[0085] 10 illustrates a signaling flow 1000 of a fifth aspect of the present disclosure in which a higher layer approach is used to create and assign a relay UE ID, according to some embodiments. In the fifth aspect of the present disclosure, the relay UE ID may be managed / assigned by the AMF 116, for example, based on the 5G S-Temporary Mobile Subscriber Identity (TMSI).
[0086] The signaling flow 1000 may include the AMF 116 assigning a relay UE ID to the relay UE 104. In some embodiments, the AMF 116 may provide a 48-bit 5G S-TMSI to the relay UE 104 for use in deriving the relay UE ID. The S-TMSI is a shortened version of the 5G global unique temporary identifier (GUTI) designed to facilitate efficient over-the-air signaling procedures during paging and service requests. The S-TMSI may be constructed from a mobility management entity code (MMEC) and a mobile TMSI (M-TMSI). To derive the relay UE ID based on the S-TMSI, the relay UE 104 may determine a hash output of the S-TMSI and its serving cell ID (NR cell identifier (NCI)). For example, the relay UE 104 may determine the relay UE ID based on the following formula:
number
[0087] Providing the relay UE ID as a hash output of the S-TMSI and the serving cell ID may mitigate any privacy concerns considering that the 48-bit S-TMSI may be resistant to brute force attacks. Furthermore, the relay UE ID may change automatically when the relay UE 104 moves from one serving cell to another. It may not be necessary to notify the network of this change in the relay UE ID.
[0088] The signaling flow 1000 may further include the relay UE 104 broadcasting the relay UE ID (and NCI shown in FIG. 4) in a relay discovery message sent according to the Model A or B discovery procedure.
[0089] The remote UE 106 may send a measurement report with the relay UE ID to the base station 108.
[0090] Upon receiving the measurement report from the remote UE 106, the base station 108 may send a query with the relay UE ID to the AMF 116. The AMF 116 may resolve the relay UE ID to a 5G-S-TMSI value and use this value to identify the UE context and state of the relay UE 104. The AMF 116 may then send the UE context / state to the base station 108. If the context is stored in the base station 108, the base station 108 may update the context with the new identifier to maintain future association.
[0091] Various features of aspects of the present disclosure are described below.
[0092] In a first aspect, the same network assigned ID may be created / used as a relay UE ID for relay UEs in RRC idle, RRC connected, or RRC inactive / idle after RRC release. Network reachability of relay UEs (e.g., during handover) may be possible in idle, inactive, and connected states.
[0093] In a second aspect, the UE selected ID may be created / used as a relay UE ID for a relay UE in RRC idle state, the base station assigned ID may be created / used as a relay UE ID for a relay UE in RRC connected state, and the relay UE may continue to use the previous ID as a relay UE ID in inactive / idle state after RRC release. Network reachability of the relay UE (e.g., during handover) may be possible in the connected state.
[0094] In a third aspect, a UE selected ID may be created / used as a relay UE ID for a relay UE in RRC idle state, and an ID selected by the UE and confirmed by the base station or an ID set by the base station after overriding the UE selected ID may be created / used as a relay UE ID for a relay UE in RRC connected state, and the relay UE may continue to use the previous ID as a relay UE ID in inactive / idle state after RRC release. Network reachability of a relay UE (e.g. during handover) may be possible in the connected state.
[0095] In a fourth aspect, a UE selected ID may be created / used as a relay UE ID for a relay UE in RRC idle state, a NG-RAN assigned ID may be created / used as a relay UE ID for a relay UE in RRC connected state, and the relay UE may continue to use the previous ID or use a new network assigned ID as a relay UE ID in inactive / idle state after RRC release. Network reachability of a relay UE (e.g. during handover) may be possible in inactive and connected states.
[0096] The second, third, and fourth aspects describe the use of UE selection ID in RRC idle state. This can be avoided by requiring relay UEs to enter connected state at least once before initiating relay discovery procedure. In some cases, this can alleviate the need to update the network with the history of UE selection ID to ensure all entities are properly synchronized.
[0097] In a fifth aspect, the same AMF allocation ID, which may be different for each cell when hashed with the NCI, may be created / used as a relay UE ID for relay UEs in RRC idle, RRC connected, or RRC inactive / idle after RRC release. Network reachability of relay UEs (e.g., during handover) may be possible in idle, inactive, and connected states.
[0098] 11 illustrates an operational flow / algorithm structure 1100 according to some embodiments. The operational flow / algorithm structure 1100 may be executed / implemented by a UE, such as relay UE 104, UE 1400, or a component thereof, such as processor 1404.
[0099] The operational flow / algorithm structure 1100 may include receiving a message from the network at 1104. The message received from the network may include information for determining the relay UE ID. In some embodiments, the information may be the relay UE ID itself. In other embodiments, the information may provide a basis for deriving the relay UE ID. For example, the information may be the S-TMSI that the UE may use along with the NCI to determine the relay UE ID.
[0100] In some embodiments, the message may be an AS message received from a base station, or a NAS message received from a PCF (via the base station) or an AMF (via the base station).
[0101] In some embodiments, the message may include the relay UE ID in the source Layer 2 ID field or in a separate relay UE ID field, for example in the ProSe layer.
[0102] The operational flow / algorithm structure 1100 may further include generating a relay discovery announcement to include the relay UE ID, at 1108. The relay discovery announcement may be part of a Model A or B discovery process.
[0103] The operational flow / algorithm structure 1100 may further include transmitting a relay discovery announcement, at 1112. The relay discovery announcement may be transmitted while the UE is in an RRC connected state or an RRC inactive state.
[0104] 12 illustrates an operational flow / algorithm structure 1200 according to some embodiments. The operational flow / algorithm structure 1200 may be executed / implemented by a base station, such as, for example, the base station 108, the device 1500, or a component thereof, such as, for example, the processor 1504.
[0105] The operational flow / algorithm structure 1200 may include, at 1204, receiving a message to authorize the first UE for ProSe relay. The message may be received from the AMF and may include a relay UE ID for the first UE. In some embodiments, the message may be an NGAP message including a UE context modification request or an initial context setup request.
[0106] The operational flow / algorithm structure 1200 may further include receiving a measurement report from the second UE, at 1208. The measurement report may include a relay UE ID, an NCI, and SD-RSRP information. Based on the measurement report, the base station may identify the first UE as a target relay for the second UE.
[0107] The operational flow / algorithm structure 1200 may further include, at 1212, sending configuration information to the first UE to configure the first UE as a relay for the second UE.
[0108] 13 illustrates an operational flow / algorithm structure 1300 according to some embodiments. The operational flow / algorithm structure 1300 may be executed / implemented by a function of the core network, such as the AMF 116, the PCF 120, or the device 1500, or by a component thereof, such as the processor 1504.
[0109] The operational flow / algorithm structure 1300 may include, at 1304, assigning a relay UE ID to the relay UE. The CN function may assign a relay UE ID having a desired uniqueness. For example, the CN function may determine that no other UEs are associated with the relay UE ID within a particular granularity, e.g., cell, RNA, etc. The association between the relay UE ID and the relay may be stored in a memory of a device implementing the CN function.
[0110] The operational flow / algorithm structure 1100 may further include generating a message to include an ID used to determine a relay UE ID, at 1108. In some embodiments, the message may include the relay UE ID itself or may include information that the UE may use to derive the relay UE ID (e.g., S-TMSI).
[0111] The operational flow / algorithm structure 1100 may further include sending a message to the relay UE, at 1112. The message may include a ProSe policy structure having other ProSe parameters.
[0112] 14 illustrates a UE 1400 according to some embodiments. The UE 1400 may be similar to and substantially interchangeable with the relay UE 104 or the remote UE 106.
[0113] The UE 1400 may be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smart watch), or an Internet of Things device.
[0114] The UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, an antenna structure 1426, and a battery 1428. The components of the UE 1400 may be implemented as an integrated circuit (IC), a portion thereof, a separate electronic device, or other module, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 14 is intended to illustrate a high-level view of some components of the UE 1400. 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.
[0115] The components of the UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, or the like that allows various circuit components (on a common or different chips or chipsets) to interact with one another.
[0116] The processor 1404 may include processor circuitry such as, for example, baseband processor circuitry (BaseBand, BB) 1404A, central processing unit circuitry (CPU) 1404B, and graphics processing unit circuitry (Graphics Processor Unit, GPU) 1404C. The processor 1404 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 1412 to cause the UE 1400 to perform the operations described herein.
[0117] In some embodiments, the baseband processor circuitry 1404A may access a communications protocol stack 1436 in the memory / storage 1412 to communicate over a 3GPP compliant network. In general, the baseband processor circuitry 1404A may access the communications protocol stack 1436 to perform user plane functions at the PHY, MAC, RLC, PDCP, and SDAP layers, and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and NAS layers. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuitry 1408.
[0118] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, 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.
[0119] The memory / storage 1412 may include one or more non-transitory computer-readable media (e.g., communication protocol stack 1436) that include instructions that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 and L2 caches), while other memory / storage 1412 may be external to the processor 1404 but accessed via a memory interface. The memory / storage 1412 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.
[0120] The RF interface circuitry 1408 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 1400 to communicate with other devices over a radio access network. The RF interface circuitry 1408 may include various elements disposed in the transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, and control circuits.
[0121] In the receive path, the RFEM may receive radiated signals from the air interface via the antenna structure 1426 and filter and amplify the signals (using a low noise amplifier). The signals may be provided to a transceiver receiver that downconverts the RF signals to baseband signals that are provided to a baseband processor of the processor 1404.
[0122] In the transmit path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides an RF signal to the RFEM, which may amplify the RF signal using a power amplifier before the signal is radiated over the air interface via the antenna 1426.
[0123] In various embodiments, the RF interface circuitry 1408 may be configured to transmit and receive signals in a manner that is compliant with NR and sidelink access technologies.
[0124] The antenna 1426 may include antenna elements that convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof, allowing for beamforming and multiple-input multiple-output communication. The antenna 1426 may include microstrip antennas, printed antennas assembled on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 1426 may have one or more panels designed for a particular frequency band, including bands within FR1 or FR2.
[0125] The user interface circuitry 1416 includes various input / output (I / O) devices designed to enable user interaction with the UE 1400. The user interface 1416 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for accepting input, including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as a sensor reading, an actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among others, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as a display device or touch screen (e.g., a liquid crystal display (LCD), LED display, quantum dot display, or projector), where output such as text, graphics, multimedia objects, etc. are generated or created from operation of the UE 1400.
[0126] The sensors 1420 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and transmit information about the detected events (sensor data) to some other devices, modules, or subsystems. Examples of such sensors include inertial measurement units with accelerometers, gyroscopes, or magnetometers; microelectromechanical or nanoelectromechanical systems with 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, and microphones or other similar audio capture devices.
[0127] The driver circuitry 1422 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuitry 1422 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1400. For example, the driver circuitry 1422 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for obtaining sensor readings of the sensor circuitry 1420 and controlling and allowing access to the sensor circuitry 1420, a driver for obtaining actuator positions of electromechanical components or for controlling and allowing access to electromechanical components, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.
[0128] The PMIC 1424 may manage the power supplied to various components of the UE 1400. In particular, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.
[0129] The battery 1428 may provide power to the UE 1400, although in some examples the UE 1400 may be deployed and mounted at a fixed location and may have a power source coupled to a power grid. The battery 1428 may be a lithium ion battery, a metal air battery such as an air zinc battery, an aluminum air battery, a lithium air battery, etc. In some implementations, such as vehicle-based applications, the battery 1428 may be a typical automotive lead acid battery.
[0130] 15 illustrates a network device 1500 according to some embodiments. The network device 1500 may be similar to and substantially interchangeable with the base station 108, the AMF 116, or the PCF 120 of FIG.
[0131] The network device 1500 may include a processor 1504, RF interface circuitry 1508 (if implemented as a base station), core network (CN) interface circuitry 1512, memory / storage circuitry 1516, and antenna structure 1526 (if implemented as a base station).
[0132] The components of the network device 1500 may be coupled to various other components via one or more interconnects 1528.
[0133] The processor 1504, RF interface circuitry 1508, memory / storage circuitry 1516 (including the communications protocol stack 1510), antenna structure 1526, and interconnect 1528 may be similar to the like-named elements shown and described with respect to FIG. 15. If the device 1500 is implemented as a base station, the communications protocol stack 1510 may include an access stratum layer. If the network device 1500 is implemented as an AMF 116 or PCF 120, the communications protocol stack 1510 may include a NAS layer.
[0134] The CN interface circuitry 1512 may provide connectivity to a core network, e.g., a fifth generation core network (5GC), using a 5GC compliant network interface protocol, such as a Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the network device 1500 via optical fiber or wireless backhaul. The CN interface circuitry 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0135] It is understood that use of personally identifiable information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.
[0136] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, or methods as described in the example section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. For another example, circuitry associated with a UE, base station, network element, as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples described below in the Example section. Working Example
[0137] Further exemplary embodiments are provided in the following sections.
[0138] Example 1 includes a method of operating a user equipment (UE), the method including receiving a message from a network, the message including a relay UE identifier (ID), generating a relay discovery announcement to include the relay UE ID, and transmitting the relay discovery announcement.
[0139] Example 2 includes the method of example 1 or any other example herein, further including receiving a message from a Policy Control Function (PCF).
[0140] Example 3 includes the method of example 2 or any other example herein, wherein the message further includes a relay service code for identifying the relay service provided by the UE.
[0141] Example 4 includes the method of example 2 or any other example herein, wherein the message is a proximity service policy message.
[0142] Example 5 includes the method of example 1 or any other example herein, wherein the relay discovery announcement includes a source Layer 2 ID field having a value based on a relay UE ID or a relay UE ID field having a relay UE ID.
[0143] Example 6 includes the method of example 1 or any other example herein, wherein the message includes a plurality of relay UE IDs for the UE and a plurality of relay service codes respectively corresponding to the plurality of relay UE IDs.
[0144] Example 7 includes the method of example 1 or any other example herein, wherein the message is an access stratum message.
[0145] Example 8 includes the method as in example 1 or any other example herein, wherein the message is a radio resource control (RRC) release message.
[0146] Example 9 includes the method of Example 8 or any other example herein, further including transitioning to an RRC inactive state based on the RRC release message, and sending an RRC resume request with a relay ID update request based on a determination that the UE has moved outside a radio access network notification area (RNA).
[0147] Example 10 includes the method of example 8 or any other example herein, further including sending a relay discovery announcement in an RRC inactive state.
[0148] Example 11 includes a method of operating a relay user equipment (UE), the method including receiving a message from a base station having instructions to report UE selection identifiers (IDs) used for a relay service, identifying one or more UE selection IDs used for the relay service, and sending a report to the base station with an indication of the one or more UE selection IDs.
[0149] Example 12 includes the method of Example 11 or any other example herein, wherein the message includes a retention interval value, and one or more UE selected IDs are identified as being within a period based on the retention interval value.
[0150] Example 13 can include any of Example 11 or any other examples herein, and can further include determining that the retention interval value is provided as 0, not provided, or not defined, and based on the determination, identifying a most recently used UE selection ID as the one or more UE selection IDs.
[0151] Example 14 includes the method of example 11 or any other example herein, wherein the one or more UE selected IDs include a plurality of UE selected IDs, and the method further includes generating the report to include an indication of a most recently used UE selected ID among the plurality of UE selected IDs.
[0152] Example 15 includes a method of operating a base station, the method including: receiving a message from an access and mobility management function (AMF) for authorizing a first user equipment (UE) to provide proximity services, the NGAP message including a relay UE identifier (ID) for the first UE; receiving a measurement report from a second UE, the measurement report including the relay UE ID; and, based on the measurement report, sending configuration information to the first UE to configure the first UE as a relay for the second UE.
[0153] Example 16 includes the method of example 15 or any other example herein, wherein the message is a Next Generation Application Protocol (NGAP) message including a UE context modification request or an initial context setup request.
[0154] Example 17 includes a method of operating a function of a core network, the method including: assigning a relay user equipment (UE) identifier (ID) to a UE; generating a message including the identifier (ID) used to determine the relay UE ID; and transmitting the message to the UE.
[0155] Example 18 includes the method of example 17 or any other example herein, wherein the function is a Policy Control Function (PCF), the message includes a proximity service policy structure, and the ID is a relay UE ID.
[0156] Example 19 includes the method of Example 17 or any other example herein, wherein the function is an Access and Mobility Management Function (AMF) and the identity is an S-temporary mobile subscriber identity (S-TMSI).
[0157] Example 20 includes the method of example 19 or any other example herein, further including receiving a query from the base station having a relay UE ID, and providing a response to the base station having an indication of the relay UE.
[0158] Example 21 includes a method of operating a base station, the method including associating a relay user equipment (UE) identifier (ID) with a UE for providing a relay service, and sending an indication of the association to the UE.
[0159] Example 22 includes the method of Example 21, further including: receiving an ID request from the UE; identifying one or more IDs not associated with another UE in a cell served by the base station; and determining a relay UE ID associated with the UE by selecting an ID from the one or more IDs.
[0160] Example 23 includes the method of Example 22 or any other example herein, further including receiving the ID request in a sidelink UE information message and sending the indication in a radio resource configuration (RRC) message.
[0161] Example 24 includes the method of example 21 or any other example herein, wherein the relaying UE ID is based on a Cell Radio Network Temporary Identifier (C-RNTI).
[0162] Example 25 includes the method of example 21 or any other example herein, further including: deassociating the relay UE ID with the UE based on determining that the UE is in the idle mode.
[0163] Example 26 includes the method of example 21 or any other example herein, further including: receiving an indication from the UE that the UE has selected a desired relay UE ID; and determining whether the desired relay UE ID is associated with another UE in a cell provided by the base station; if the desired UE ID is not associated with another UE in the cell, the relay UE ID is a desired relay UE ID; and if the desired UE ID is associated with another UE in the cell, the relay UE ID is not a desired relay UE ID.
[0164] Example 27 includes the method of example 21 or any other example herein, further including initiating the change of the relay UE ID or changing the relay UE ID based on a request from the UE.
[0165] Example 28 includes the method of example 21 or any other example herein, further including ensuring that the relay UE ID is uniquely associated with the UE in the multiple cells.
[0166] Example 29 includes the method of Example 21 or any other example herein, further including: sending an indication to the UE in a radio resource control (RRC) release message; and associating the relay UE ID with an inactive context of the UE.
[0167] Example 30 includes the method of example 21 or any other example herein, wherein the relaying UE ID is based on the base station ID and the UE ID.
[0168] Example 31 includes the method of Example 21 or any other example herein, and further includes associating the relay UE ID with an inactive radio network temporary identity (I-RNTI), receiving a measurement report including the relay UE ID, and paging the UE using the I-RNTI.
[0169] Example 32 includes a method of operating a relay user equipment (UE), the method including receiving an S-temporary mobile subscriber identity (S-TMSI) from an access and mobility management function (AMF), generating a relay UE identifier (ID) based on the S-TMSI and a cell identity, and sending a relay discovery announcement together with the relay UE ID.
[0170] Example 33 includes the method of example 32 or any other example herein, wherein generating the relay UE ID includes generating the relay UE ID as a hash value of the S-TMSI and the cell identity.
[0171] Example 34 can include an apparatus including means for performing one or more elements of the method described or related to any of Examples 1-33, or any other method or process described herein.
[0172] Example 35 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any of Examples 1-33, or any other method or process described herein.
[0173] Example 36 may include an apparatus having logic, modules, or circuitry for performing one or more elements of the method described or related to any of Examples 1-33, or any other method or process described herein.
[0174] Example 37 may include any method, technique, or process described or related to any of Examples 1-33, or any portion or part thereof.
[0175] Example 38 may include an apparatus having one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in any of Examples 1-33 or a related method, technique, or process, or portions thereof.
[0176] Example 39 may include any of the signals described in or related to any of Examples 1-33, or a portion or parts thereof.
[0177] Example 40 may include a datagram, information element, packet, frame, segment, PDU, or message described or related to any of Examples 1 to 33, or that is a part or portion thereof, or described in this disclosure.
[0178] Example 41 may include a signal encoded with data described or relating to, or being a part or portion of, any of Examples 1-33, or described in this disclosure.
[0179] Example 42 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message described or related to any of Examples 1 to 33, or a portion or part thereof, or described in this disclosure.
[0180] Example 43 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to 33, or a portion thereof.
[0181] Example 44 may include a computer program comprising instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples 1 to 33, or a portion thereof.
[0182] Example 45 may include a signal in a wireless network as shown and described herein.
[0183] Example 46 may include a method of communicating in a wireless network as shown and described herein.
[0184] Example 47 may include a system for providing wireless communication as shown and described herein.
[0185] Example 48 may include a device for providing wireless communication as shown and described herein.
[0186] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. 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 the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0187] Although the above embodiments 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, and it is intended that the following claims be interpreted to embrace all such variations and modifications.
Claims
1. 1. A method of operating a user equipment (UE), comprising: receiving a message from a network, the message including a relay UE identifier (ID); generating a relay discovery announcement to include the relay UE ID; transmitting said relay discovery announcement; A method comprising:
2. The method of claim 1 , further comprising receiving the message from a Policy Control Function (PCF).
3. The method of claim 2 , wherein the message further comprises a relay service code for identifying a relay service provided by the UE.
4. The method of claim 2 , wherein the message is a proximity service policy message.
5. The relay discovery announcement, a Source Layer-2 ID field having a value based on the Relay UE ID; or The method of claim 1 , further comprising a Relay UE ID field having the relay UE ID.
6. The method of claim 1 , wherein the message includes a plurality of relay UE IDs for the UE and a plurality of relay service codes corresponding respectively to the plurality of relay UE IDs.
7. The method of claim 1 , wherein the message is an access stratum message.
8. The method of claim 1 , wherein the message is a Radio Resource Control (RRC) release message.
9. transitioning to an RRC inactive state based on the RRC release message; sending an RRC resumption request with a relay ID update request based on a determination that the UE has moved outside a radio access network notification area (RNA); The method of claim 8 further comprising:
10. transmitting the relay discovery announcement in the RRC inactive state; The method of claim 8 further comprising:
11. One or more computer-readable media having instructions that, when executed, cause a user equipment (UE) to: receiving, from a base station, a message having an instruction to report a UE selection identifier (ID) used for the relay service; Identifying one or more UE selection IDs to be used for the relay service; One or more computer-readable media for causing a report to be sent to the base station with an indication of the one or more UE selection IDs.
12. 12. The one or more computer-readable media of claim 11, wherein the message includes a retention interval value, and the one or more UE selected IDs are identified as being within a time period based on the retention interval value.
13. The instructions, when executed, further cause the device to: determining whether a retention interval value is provided as 0, not provided, or undefined; The one or more computer-readable media of claim 11 , further comprising: identifying a most recently used UE selected ID as the one or more UE selected IDs based on the determining.
14. The one or more UE selection IDs include a plurality of UE selection IDs, and the instructions, when executed, further cause the device to:
12. The one or more computer-readable media of claim 11, further comprising: generating the report to include an indication of a most recently used UE selection ID of the plurality of UE selection IDs.
15. 1. A method of operating a base station, comprising the steps of: receiving a message from an Access and Mobility Management Function (AMF) for authorizing a first user equipment (UE) to provide proximity services, the message including a relay UE identifier (ID) for the first UE; receiving a measurement report from a second UE, the measurement report including the relay UE ID; sending configuration information to the first UE to configure the first UE as a relay for the second UE based on the measurement report; A method comprising:
16. 16. The method of claim 15, wherein the message is a Next Generation Application Protocol (NGAP) message including a UE context modification request or an initial context setup request.
17. 1. A network device, comprising: a memory for storing an association between a relay user equipment (UE) identifier (ID) and a UE; a processing circuit coupled to the memory, generating a message including an identifier (ID) used to determine the relay UE ID; a processing circuit configured to transmit the message to the UE; A network device comprising:
18. The network device, a Policy Control Function (PCF) is implemented, and the message includes a proximity service policy structure and the identity is the relay UE identity; or 18. The network device of claim 17, implementing an Access and Mobility Management Function (AMF), and wherein the identity is an S-temporary mobile subscriber identity (S-TMSI).
19. The network device implements the AMF, and the processing circuitry further comprises: receiving an inquiry from a base station having the relay UE ID; 20. The network device of claim 18, further comprising: providing a response to the base station having an indication of the relay UE.
20. 1. A method of operating a base station, comprising the steps of: Associating a relay user equipment (UE) identifier (ID) with a UE for provision of a relay service; sending the association indication to the UE; A method comprising:
21. receiving an identity request from the UE; identifying one or more identities not associated with another UE within a cell served by the base station; determining the Relay UE ID associated with the UE by selecting an ID from the one or more IDs; 21. The method of claim 20, further comprising:
22. receiving the identity request in a Sidelink UE Information message; sending the indication in a Radio Resource Configuration (RRC) message; 22. The method of claim 21 further comprising:
23. receiving an indication from the UE that the UE has selected a desired relay UE ID; determining whether the desired relay UE ID is associated with another UE within a cell served by the base station; if the desired UE ID is not associated with another UE in the cell, the relay UE ID is the desired relay UE ID; The method of claim 20, wherein the relay UE ID is not the desired relay UE ID if the desired UE ID is associated with another UE in the cell.
24. 1. A method of operating a relay user equipment (UE), comprising: Receiving an S-temporary mobile subscriber identity (S-TMSI) from an access and mobility management function (AMF); and generating a relay UE identifier (ID) based on the S-TMSI and a cell identity; sending a relay discovery announcement with the relay UE ID; A method comprising:
25. generating the relay UE ID, The method of claim 24, comprising generating the Relay UE ID as a hash value of the S-TMSI and the cell identity.
Citation Information
Patent Citations
Method and apparatus for creating a packet data network connection for a terminal - Patents.com
JP2018524883A
Apparatus and method for wireless communication
WO2017187713A1
Enabling fifth-generation proximity services in fifth-generation systems
WO2021138166A1
