Techniques for sidelink-based discovery

Abstract

Methods, systems, and devices for wireless communication are described. A discovering user equipment may send, to a first network entity, a discovery message requesting information for discovery by a discovered UE for sidelink communications. The discovery message may include one or more parameters indicating a discovery model type, a geographical range relative to the discovery UE, a broadcast type, or a combination thereof. The first network entity may send a discovery message to one or more second network entities. The second network entity may send a discovery message to one or more discovered UEs. A given discovered UE may send a response to the discovery message that indicates whether the discovered UE is available for discovery by the discovering UE. The discovering UE may receive a response to the discovery message from the first network entity, the response indicating a list of discovered UEs that meet the criteria for discovery.

Description

Cross-referencing

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 468,465, filed September 15, 2023, entitled “TECHNIQUES FOR SIDELINK BASED DISCOVERY”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following discussion relates to wireless communications, including techniques for sidelink-based discovery. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting technologies for sidelink-based discovery. For example, the described technology provides a set of user equipment (UEs) using a Vehicle-to-Network-to-Everything (V2N2X) framework based on sidelink discovery. For instance, as part of establishing a V2N2X connection, a UE (e.g., a discovering UE) may send a discovery message to the network requesting one or more other UEs (e.g., the discovering UE) to indicate availability for discovery. The discovery message may indicate discovery information such as discovery model type (e.g., Model A discovery or Model B discovery), geographic location range, broadcast type (e.g., unicast, connectionless multicast, connected multicast, or broadcast), or combinations thereof. In some examples, the discovery message may include discovery codes indicating discovery information. For example, the UE may be configured using a set of discovery codes, each corresponding to the relevant discovery information (e.g., relevant model type, relevant geographic location range, and relevant broadcast type).

[0005] The discovering UE can send a discovery message to a first network entity (e.g., the network entity to which the sending UE connects), and the first network entity can relay the discovery message to one or more second network entities. Therefore, the second network entity serving the discovered UE can indicate the discovery message to the discovered UE. For example, the second network entity can include the discovery message in downlink control information (DCI) (e.g., a DCI scrambled with a discovery radio network temporary identifier (RNTI) or a DCI including bits indicating the presence of a discovery message). If a given discovered UE accepts the request to be discovered, the given discovered UE can respond to the second network entity, indicating its discoverability and its vehicular network (V2X) ID. The second network entity can generate a list of discoverable UEs willing to be discovered and send this list to the first network entity. Therefore, the first network entity can relay this list back to the discovering UE, and the discovering UE can establish a V2N2X connection with each receiving UE included in the list.

[0006] A method for wireless communication by a discovering UE is described. The method may include: sending a discovery message to a network entity requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; receiving a response from the network entity to the discovery message, the response indicating a list of one or more discovering UEs among the discovering UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters; and performing a wireless connection establishment procedure with at least one UE from the list of one or more discovering UEs among the discovering UEs.

[0007] A discoverer UE for wireless communication is described. The discoverer UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the discoverer UE to: send a discovery message to a network entity requesting information for discovery of the discoverer UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverer UE, broadcast type, or a combination thereof; receive a response from the network entity to the discovery message, the response indicating a list of one or more discoverer UEs among the discoverer UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters; and perform a wireless connection establishment procedure with at least one UE from the list of one or more discoverer UEs among the discoverer UEs.

[0008] Another discoverer UE for wireless communication is described. The discoverer UE may include: components for sending a discovery message to a network entity requesting information for discovery of the discoverer UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discoverer UE, a broadcast type, or a combination thereof; components for receiving a response from the network entity to the discovery message, the response indicating a list of one or more discoverer UEs among the discoverer UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters; and components for performing a wireless connection establishment procedure with at least one UE from the list of one or more discoverer UEs among the discoverer UEs.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions operable individually or jointly by one or more processors to: send a discovery message to a network entity requesting information for discovery of a discoverable UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverable UE, broadcast type, or a combination thereof; receive a response from the network entity to the discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters; and perform a wireless connection establishment procedure with at least one UE from the list of one or more discoverable UEs among the discoverable UEs.

[0010] In some examples of the methods, discovery UEs, and nontransitory computer-readable media described herein, the broadcast type includes a set of multiple broadcast types, and the geographic range includes a set of multiple geographic ranges, and each broadcast type in the set of multiple broadcast types may be associated with a corresponding geographic range in the set of multiple geographic ranges.

[0011] In some examples of the methods, discovering UEs, and nontransitory computer-readable media described herein, the discovery message includes a first discovery code indicating the one or more parameters, and the discovering UE may be associated with a set of discovery codes, each corresponding to a respective set of the one or more parameters.

[0012] In some examples of the methods described herein, the discoverer UE, and non-transitory computer-readable media, one or more parameters also indicate the reason for the discovery by the discoverer UE.

[0013] In some examples of the methods described herein, the discoverer UE, and the nontransitory computer-readable medium, the discoverer UE may be associated with the network entity, and the one or more discoverer UEs in the discoverer UE may be associated with one or more second network entities.

[0014] In some examples of the methods described herein, the discovering UE, and non-transitory computer-readable media, the discovery message may be sent via a Radio Resource Control (RRC) configuration message, an RRC reconfiguration message, a Media Access Control-Control Element (MAC-CE) message, or a Scheduling Request (SR) message.

[0015] In some examples of the methods, discoverer UEs, and nontransitory computer-readable media described herein, the response to the discovery message also indicates a corresponding V2X identifier for each of the discoverer UEs in the list of one or more discoverer UEs.

[0016] In some examples of the methods described herein, the discovering UE, and non-transitory computer-readable media, the discovering UE receives the response to the discovery message via an RRC message.

[0017] A method for wireless communication by a discovered UE is described. The method may include: receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discovered UE, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovered UE, a broadcast type, or a combination thereof; and sending a response to the discovery message to the network entity, the response indicating whether the discovered UE is capable of being discovered by the discovered UE according to the one or more parameters indicated in the discovery message.

[0018] A discoverer UE for wireless communication is described. The discoverer UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the discoverer UE to: receive from a network entity a discovery message requesting information associated with establishing sidelink communication with the discoverer UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverer UE, broadcast type, or a combination thereof; and send a response to the discovery message to the network entity, the response indicating whether the discoverer UE is capable of being discovered by the discoverer UE according to the one or more parameters indicated in the discovery message.

[0019] Another discoverer UE for wireless communication is described. The discoverer UE may include: components for receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discoverer UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverer UE, broadcast type, or a combination thereof; and components for sending a response to the discovery message to the network entity, the response indicating whether the discoverer UE is capable of being discovered by the discoverer UE according to the one or more parameters indicated in the discovery message.

[0020] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable individually or jointly by one or more processors to: receive from a network entity a discovery message requesting information associated with establishing sidelink communication with a discovering UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof; and send a response to the discovery message to the network entity indicating whether the discovered UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the discovery message.

[0021] The methods described herein, examples of the discovered UE, and non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving a DCI scrambled with an RNTI associated with sidelink discovery; and using the RNTI to decode the DCI, wherein the result of the decoding indicates that the associated downlink channel includes the discovery message.

[0022] The methods described herein, examples of the discovered UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an indication of the RNTI associated with sidelink discovery prior to receiving the DCI, wherein decoding of the DCI may be based on receiving the indication of the RNTI.

[0023] In some examples of the methods described herein, the discovering UE, and the nontransitory computer-readable medium, receiving the discovery message may include operations, features, components, or instructions for receiving a discovery code indicating one or more parameters of the discovery message via the associated downlink channel.

[0024] In the methods described herein, in some examples of the discoverer UE and nontransitory computer-readable media, the discoverer UE periodically monitors the DCI scrambled with the RNTI associated with sidelink discovery.

[0025] The methods described herein, examples of the discovered UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a DCI that includes bit values ​​indicating the presence of the discovery message and a discovery code indicating one or more parameters of the discovery message.

[0026] The methods described herein, examples of the discovered UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving a DCI including a bit value of the associated downlink channel including the discovery message; and receiving the discovery message including: receiving a discovery code indicating one or more parameters of the discovery message via the associated downlink channel.

[0027] In some examples of the methods described herein, the discovered UE, and nontransitory computer-readable media, receiving the discovery message may include operations, features, components, or instructions for: receiving the RRC reconfiguration message, the RRC reconfiguration message including a discovery message indicator indicating the existence of the discovery message, a discovery code indicating the discovery message or one or more parameters, and a reason for the discovery by the discovered UE.

[0028] In some examples of the methods described herein, the discovering UE, and the nontransitory computer-readable medium, the response to the discovery message may include operations, features, components, or instructions for: as part of the response to the discovery message, sending availability to be discovered by the discovering UE based on one or more parameters indicated in the discovery message, and a first V2X identifier associated with the discovering UE.

[0029] The methods described herein, examples of the discovered UE, and nontransitory computer-readable media may also include operations, features, components, or instructions for sending a mapping between a pseudo V2X identifier and the first V2X identifier to the network entity, wherein the mapping instructs the network entity to relay the pseudo V2X identifier to the discovered UE as part of the response to the discovery message.

[0030] In some examples of the methods described herein, the discoverer UE, and the nontransitory computer-readable medium, the discoverer UE may be associated with a second network entity that is different from the network entity associated with the discoverer UE.

[0031] A method for wireless communication by a network entity is described. The method may include: receiving from a discovering UE a discovery message requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; sending the discovery message received from the discovering UE to one or more second network entities; receiving a corresponding response from the one or more second network entities to the discovery message, the corresponding response indicating a corresponding list of one or more discovering UEs among the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; and sending a control message to the discovering UE, the control message including a list of the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters.

[0032] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the network entity to: receive from a discovering UE a discovery message requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; send the discovery message received from the discovering UE to one or more second network entities; receive from the one or more second network entities a corresponding response to the discovery message, the corresponding response indicating a corresponding list of one or more discovering UEs among the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; and send to the discovering UE a control message, the control message including a list of the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters.

[0033] Another network entity for wireless communication is described. This network entity may include: components for receiving from a discovering UE a discovery message requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; components for sending the discovery message received from the discovering UE to one or more second network entities; components for receiving a corresponding response from the one or more second network entities to the discovery message, the corresponding response indicating a corresponding list of one or more discovering UEs among the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; and components for sending a control message to the discovering UE, the control message including a list of the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters.

[0034] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable individually or jointly by one or more processors to: receive from a discovering UE a discovery message requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; send the discovery message received from the discovering UE to one or more second network entities; receive from the one or more second network entities a corresponding response to the discovery message, the corresponding response indicating a corresponding list of one or more discovering UEs among the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; and send to the discovering UE a control message, the control message including a list of the discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more second network entities satisfy the geographic range relative to the discovering UE.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more second network entities satisfy a certain number of second network entities closest to the discovering UE.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control message may be an RRC message for the vehicle-to-network-to-everything discovery result, and the list indicates the corresponding V2X identifier for each discoverer UE in the discoverer UE.

[0038] A method for wireless communication by a network entity is described. The method may include: receiving from a second network entity associated with a discovering UE a first discovery message requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters; receiving from the one or more discovering UEs a corresponding response to the second discovery message, the response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message; and sending to the second network entity a list of the one or more discovering UEs that meet the criteria for discovery for the sidelink communication, based on the one or more parameters.

[0039] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the network entity: receives from a second network entity associated with a discovering UE a first discovery message requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; sends a second discovery message to the one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters; receives a corresponding response from the one or more discovering UEs to the second discovery message, the corresponding response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message; and sends to the second network entity, according to the one or more parameters, a list of discovering UEs among the one or more discovering UEs that meet the criteria for discovery for the sidelink communication.

[0040] Another network entity for wireless communication is described. This network entity may include: components for receiving a first discovery message from a second network entity associated with a discovering UE, requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; components for sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters; components for receiving a corresponding response from the one or more discovering UEs to the second discovery message, the corresponding response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message; and components for sending a list of discovering UEs among the one or more discovering UEs that meet the criteria for discovery for the sidelink communication to the second network entity according to the one or more parameters.

[0041] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable individually or jointly by one or more processors to: receive from a second network entity associated with a discovering UE a first discovery message requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; send to one or more discovering UEs served by the network entity a second discovery message including the one or more parameters; receive from the one or more discovering UEs a corresponding response to the second discovery message, the response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message; and send to the second network entity, according to the one or more parameters, a list of discovering UEs among the one or more discovering UEs that meet the criteria for discovery for the sidelink communication.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each corresponding response to the second discovery message includes a corresponding V2X identifier associated with the corresponding discovered UE, and the list of discovered UEs that meet the criteria for the discovery includes each corresponding V2X identifier.

[0043] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a mapping between a pseudo-V2X identifier and a V2X identifier from a first discoverer UE among the one or more discoverer UEs, wherein the mapping instructs the network entity to include the pseudo-V2X identifier in the list of discoverer UEs that meet the discovery criteria.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the network entity sends the list of discoverer UEs that meet the discovery criteria via the X2 interface. Attached Figure Description

[0045] Figure 1 Examples of wireless communication systems supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure are shown.

[0046] Figure 2 Examples of wireless communication systems supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure are shown.

[0047] Figure 3 An example of a process flow supporting a technique for sidelink-based discovery according to one or more aspects of this disclosure is shown.

[0048] Figure 4 and Figure 5 A block diagram of an apparatus supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown.

[0049] Figure 6 A block diagram of a communication manager supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure, is shown.

[0050] Figure 7 A diagram is shown of a system including a device supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure.

[0051] Figure 8 and Figure 9 A block diagram of an apparatus supporting a sidelink-based discovery technique according to one or more aspects of this disclosure is shown.

[0052] Figure 10 A block diagram of a communication manager supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure, is shown.

[0053] Figure 11A diagram is shown of a system including a device supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure.

[0054] Figures 12 to 15 A flowchart illustrating a method for supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown. Detailed Implementation

[0055] Some radio systems support sidelink communication between a first user equipment (UE) and a second UE. The first and second UEs can use discovery mechanisms to establish a radio connection for sidelink communication. In some cases, the first and second UEs can use ProSe-based discovery (e.g., Evolved Packet Core (EPC) level discovery). For example, each UE can use a ProSe function corresponding to its respective Public Land Mobile Network (PLMN) to perform UE registration for ProSe. Therefore, the first UE can use a first ProSe function to receive location updates from the second UE, and the second UE can use a second ProSe function to receive location updates from the first UE. However, when the first and second UEs are connected to different PLMNs, ProSe-based discovery may introduce latency, which may be unsuitable for dynamic mobility scenarios (such as a vehicle UE intending to discover other vehicle UEs while turning). Additionally, ProSe-based discovery may not support multicast or broadcast-based discovery.

[0056] According to the techniques described herein, a set of UEs can utilize a Vehicle-to-Network-to-Everything (V2N2X) framework based on sidelink discovery. For example, as part of establishing a V2N2X connection, a UE (e.g., a discovering UE) can send a discovery message to the network requesting one or more other UEs (e.g., a discovered UE) to indicate their discoverability. The discovery message can indicate discovery information, such as discovery model type (e.g., Model A discovery or Model B discovery), geographic location range, broadcast type (e.g., unicast, connectionless multicast, connected multicast, or broadcast), or a combination thereof. In some examples, the discovery message may include discovery codes indicating discovery information. For example, UEs can be configured using sets of discovery codes, each corresponding to the relevant discovery information (e.g., relevant model type, relevant geographic location range, and relevant broadcast type).

[0057] The discovering UE can send a discovery message to a first network entity (e.g., the network entity to which the sending UE connects), and the first network entity can relay the discovery message to one or more second network entities. Therefore, the second network entity serving the discovered UE can indicate the discovery message to the discovered UE. For example, the second network entity can include the discovery message in downlink control information (DCI) (e.g., a DCI scrambled with a discovery radio network temporary identifier (RNTI) or a DCI including bits indicating the presence of a discovery message). If a given discovered UE accepts the request to be discovered, the given discovered UE can respond to the second network entity, indicating its discoverability and its vehicular network (V2X) ID. The second network entity can generate a list of discoverable UEs willing to be discovered and send this list to the first network entity. Therefore, the first network entity can relay this list back to the discovering UE, and the discovering UE can establish a V2N2X connection with each receiving UE included in the list.

[0058] The aspects of this disclosure are initially described in the context of wireless communication systems and processes. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to techniques for side-link-based discovery, and are described with reference to these diagrams.

[0059] Figure 1 Examples of wireless communication systems 100 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure are shown. Wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0060] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0061] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0062] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0063] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0064] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0065] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0067] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0068] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support techniques for sidelink-based discovery as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0069] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0070] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0071] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0072] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0073] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0074] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0075] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0076] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0077] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0078] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0079] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0080] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0081] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using V2X communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0082] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an EPC or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) routing packets or interconnecting to external networks. Control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets may be delivered through user plane entities, which may provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0083] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0084] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0085] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0086] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0087] In some examples of the wireless communication system 100, a set of UEs 115 may utilize a V2N2X framework based on sidelink discovery. For example, as part of establishing a V2N2X connection, a UE 115 (e.g., a discovering UE) may send a discovery message to the network requesting one or more other UEs 115 (e.g., a discovering UE) to indicate their discoverability. The discovery message may indicate discovery information, such as discovery model type (e.g., model A discovery or model B discovery), geographic location range, broadcast type (e.g., unicast, connectionless multicast, connected multicast, or broadcast), or a combination thereof. In some examples, the discovery message may include discovery codes indicating discovery information. For example, UEs 115 may be configured using sets of discovery codes, each corresponding to the relevant discovery information (e.g., relevant model type, relevant geographic location range, and relevant broadcast type).

[0088] Discovering UE 115 may send a discovery message to a first network entity 105 (e.g., the network entity 105 to which the sending UE 115 is connected), and the first network entity 105 may relay the discovery message to one or more second network entities 105. Therefore, a second network entity 105 providing services to the discovering UE 115 may indicate the discovery message to the discovering UE 115. For example, the second network entity 105 may include the discovery message in a DCI (e.g., a DCI scrambled with a discovery RNTI or a DCI including bits indicating the presence of a discovery message). If a given discovering UE 115 accepts the request to be discovered, the given discovering UE 115 may respond to the second network entity 105, indicating its discoverability and its V2X ID. The second network entity 105 may generate a list of discovering UEs 115 willing to be discovered and send that list to the first network entity 105. Therefore, the first network entity 105 can relay the list back to the discoverer UE 115, and the discoverer UE 115 can establish a V2N2X connection with each receiving UE 115 included in the list.

[0089] Figure 2 Examples of wireless communication systems 200 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure are shown. In some examples, wireless communication system 200 may implement or be implemented by one or more aspects of wireless communication system 100. For example, wireless communication system 200 may include UE 115-a, UE 115-b, UE 115-c, and UE 115-d, which may be as described in reference... Figure 1 The corresponding example of UE 115 described. Additionally, network entity 105-a and network entity 105-b may be referenced. Figure 1 The corresponding network entity 105 is described.

[0090] In some examples, UE 115 of wireless communication system 200 may operate according to sidelink discovery operations. Sidelink discovery can refer to the process by which two or more devices communicate directly with each other using various technologies, such as Bluetooth, Wi-Fi Direct, or D2D communication in a cellular network. In some examples, UE 115 may perform sidelink discovery via one or more discovery models. For example, Model A discovery includes two roles for a ProSe-enabled UE 115, wherein a first UE 115 (e.g., an advertising UE) broadcasts a discovery beacon indicating information associated with the first UE 115, and a second UE 115 (e.g., a monitoring UE 115) monitors the information included in the discovery beacon received from the advertising UE. Additionally or alternatively, Model B discovery includes two roles for a ProSe-enabled UE, wherein a first UE 115 (e.g., a discovering UE) sends a request including information about what types of devices the first UE 115 might be interested in discovering, and a second UE 115 (e.g., a discovered UE) may receive the request message and respond with information related to the request.

[0091] In some cases, UE 115 can perform EPC-level discovery. For example, UE 115 can use the ProSe function to perform UE 115 registration for ProSe, which can be associated with the corresponding UE 115's Home Public Land Mobile Network (PLMN). According to EPC-level discovery, the first UE 115 can send a proximity request to the first ProSe function requesting discovery information for the second UE 115 associated with the second ProSe function. In response, the first ProSe function can request location updates for both the first and second UE 115. To request a location update for the first UE 115, the first ProSe function can contact the first Secure User Plane Location (SUPL) Location Platform (SLP). To request a location update for the second UE 115, the first ProSe function can contact the second ProSe function, which requests an updated location for the second UE 115 from the second SLP associated with the second UE 115. According to EPC-level discovery, the locations of the first and second UE 115 can be periodically reported to the corresponding first and second ProSe functions.

[0092] Therefore, multiple wireless devices can use ProSe-based discovery (e.g., EPC-level discovery) to achieve direct communication between them while avoiding the use of cellular network infrastructure. However, in some cases, specific implementations of ProSe-based discovery may not be well-suited for dynamic mobility or low-latency scenarios. For example, UE 115-a may connect to network entity 105-a (e.g., via a Uu link), and UEs 115-b, 115-c, and 115-d may be served by network entity 105-b (e.g., via their respective Uu links). Figure 2 As illustrated, network entities 105-a and 105-b may be associated with the same network 205 or different networks 205. If network entity 105-a is associated with network 205-a and network entity 105-b is associated with network 205-b, then UE 115-a and UEs 115-b, 115-c, and 115-d may connect to different PLMNs. Therefore, ProSe functionality communicating across multiple networks 205 can increase the latency associated with discovery. Such increased latency may be less suitable for dynamic mobility scenarios, such as when UE 115-a is a vehicle in another vehicle designed to discover pedestrian UE 115. Additionally or alternatively, ProSe-based discovery may be associated with LTE discovery technology, which may not support broadcast types corresponding to 5G-NR-based communications (e.g., multicast or broadcast).

[0093] To reduce the latency associated with ProSe-based discovery, Figure 2 Wireless devices can operate under the V2N2X framework to initiate sidelink discovery. In some cases, the V2N2X framework can utilize Uu networks to provide V2X services. According to V2N2X, UE 115-a can send sidelink-related messages to network entity 105-a using an associated Uu link, and network entity 105-a can relay messages on behalf of UE 115-a to different network entities 105, different UE 115, or both. By using Uu links to relay sidelink-related messages, UE 115-a can avoid accessing ProSe functionality to communicate with UE 115 across different networks 205. Therefore, the V2N2X framework can support the transmission of sidelink messages (e.g., Basic Security Messages (BSM), Cooperative Aware Messages (CAM), Distributed Context Notification Messages (DENM), Signal Phase and Timing Mobility Aware Packets (SPAT-MAP), and other examples) by utilizing Uu network technology. Additionally or alternatively, the V2N2X framework can support discontinuous reception (DRX) or paging for power saving, quality of service (QoS) technologies, unicast communication, connection-based multicast protocols, distance-based communication, connectionless multicast technologies, feedback message transmission and reception, and sidelink message transmission and reception.

[0094] In some cases, UE 115-a may use the V2N2X framework to perform sidelink discovery. For example, UE 115-a may send discovery message 210 to network entity 105-a, and network entity 105-a may relay discovery message 210 to one or more second network entities 105 serving UE 115 adjacent to UE 115-a. In some examples, discovery message 210 may include one or more parameters associated with the discovery initiated by UE 115-a. For example, one or more parameters may indicate the discovery model type (e.g., model A or model B), the geographic range relative to UE 115-a, the broadcast type associated with the discovery (e.g., unicast, connectionless multicast, connected multicast, broadcast, etc.), or a combination thereof. Additionally or alternatively, the one or more parameters may indicate the reason for the discovery. For example, UE 115-a may utilize a set of application codes configured for ProSe technology, wherein UE 115-a includes ProSe application codes in discovery message 210 to indicate the reason for the discovery.

[0095] In some examples, the corresponding broadcast type may be associated with different geographical ranges relative to UE 115-a. For example, connectionless multicast may be associated with a first geographical range (e.g., THR1 meters), connected multicast may be associated with a second geographical range (e.g., THR2 meters), and unicast may be associated with a third geographical range. Therefore, the geographical range included in discovery message 210 may be selected based on UE 115 to perform the broadcast type for discovery.

[0096] In some cases, UE 115-a may send discovery message 210 via control signaling. For example, UE 115-a may send discovery message 210 as part of an RRC configuration message, an RRC reconfiguration message, a Media Access Control-Control Element (MAC-CE) message, or a Scheduling Request (SR) message.

[0097] In some cases, UE 115-a may indicate one or more parameters of discovery message 210 via discovery codes. For example, each UE in UE 115 may store a predefined set of discovery codes, where each discovery code is associated with a corresponding set of parameters used for discovery. That is, discovery message 210 may include a first discovery code indicating one or more parameters used for discovery. In some examples, each UE 115 may receive a set of discovery codes from serving network entity 105 via control signaling (e.g., RRC, MAC-CE, or DCI). In some examples, the set of discovery codes may be used to preconfigure each UE 115.

[0098] According to the V2N2X framework, network entity 105-a can receive discovery message 210 from UE 115-a and relay discovery message 210 to one or more second network entities 105 (e.g., via the X2 interface). In some cases, network entity 105-a can send discovery message 210 to second network entities 105 that satisfy a geographical range relative to UE 115-a, as indicated in discovery message 210. For example, network entity 105-a can relay discovery message 210 to network entity 105-b based on the geographical location of network entity 105-b residing within the geographical range indicated by UE 115. In some cases, network entity 105-a can send discovery message 210 to a certain number (e.g., a number of) network entities closest to UE 115-a. N The second network entity 105 sends discovery messages 210, wherein the number can be pre-configured at network entity 105-a. For example, network entity 105-a can do so based on the fact that network entity 105-b is the closest to UE 115-a. N One of the second network entities 105 will relay the discovery message 210 to network entity 105-b. Although Figure 2 The example illustrates network entity 105-a relaying discovery message 210 to network entity 105-b, but it should be understood that network entity 105-a may relay discovery message 210 to any number of second network entities 105 that satisfy the defined discovery parameters.

[0099] Based on the receipt of discovery message 210, network entity 105-b may signal discovery message 210 to associated UEs 115 (e.g., UEs 115-b, 115-c, and 115-d). In some examples, network entity 105-b may indicate the presence or absence of discovery message 210 in the downlink control channel (e.g., presence of discovery message indication 215). In some examples, network entity 105-b may implicitly indicate the presence of discovery message indication 215. For example, network entity 105-b may send a DCI scrambled with RNTI (e.g., discovery RNTI). In some examples, network entity 105-b may indicate the discovery RNTI to each of UEs 115 via a system information (SI) message or an RRC message (e.g., RRC connection establishment). Therefore, UEs 115-b, 115-c, and 115-d can each use a discovery RNTI to decode the DCI, where decoding the DCI indicates the presence of a discovery message 210 on the downlink channel associated with the DCI (e.g., the Physical Downlink Shared Channel (PDSCH)). In some examples, network entity 105-b can periodically send DCI scrambled with a discovery RNTI (e.g., in...). N (Once in a time slot), where periodicity can be pre-configured at network entity 105-b.

[0100] In some examples, network entity 105-b may explicitly send a presence discovery message indication 215. For example, network entity 105-b may send a DCI including bit values ​​(e.g., as part of DCI format 1, 1A, etc.), where a first value indicates the presence of a given discovery message 210, and a second value indicates the absence of a given discovery message 210. In some examples, the DCI including bit values ​​may additionally indicate the discovery message 210. For example, the DCI may include a discovery code indicating one or more parameters associated with the discovery of UE 115-a. In some examples, the DCI including bit values ​​may instruct UE 115 to receive the discovery message 210 on the corresponding downlink channel (e.g., the PDSCH associated with the DCI). In such examples, network entity 105-b may send the discovery message 210 via the downlink channel indicated in the DCI.

[0101] In some examples, network entity 105-b may send a presence discovery message indication 215 via RRC signaling. For example, network entity 105-b may send a discovery message 210 indicator and a discovery code included in the discovery message 210 during RRC reconfiguration. In such examples, the RRC signaling may also indicate that the reason for the RRC reconfiguration is based on V2N2X discovery.

[0102] Based on receiving discovery message 210 from network entity 105-b, given UE 115 can determine whether given UE 115 is capable of being used for discovery based on one or more parameters. For example, if given UE 115 satisfies each of the one or more parameters indicated in discovery message 210, given UE 115 can send discovery message response 220 indicating that given UE 115 is capable of being used for discovery by UE 115-a. If given UE 115 does not satisfy each of the one or more parameters indicated in discovery message 210, given UE 115 can send discovery message response 220 indicating that given UE 115 is not capable of being used for discovery by UE 115-a. In some cases, if given UE 115 does not satisfy each of the one or more parameters indicated in discovery message 210, given UE 115 may avoid sending discovery message response 220. If network entity 105-b does not receive a discovery message response 220 from a given UE 115, then network entity 105-b may determine that the given UE 115 cannot be used for discovery.

[0103] exist Figure 2In the example illustrated, each UE 115 served by network entity 105-b may send a corresponding discovery message response 220 (e.g., UEs 115-b, 115-c, and 115-d send discovery message responses 220-a, 220-b, and 220-c, respectively). In some examples, the discovery message response 220 may indicate whether the associated UE 115 is capable of being discovered using the discovery code included in the discovery message 210, and may indicate the ID (e.g., V2X ID) corresponding to the associated UE 115.

[0104] In some cases, a given UE 115 may determine a pseudo V2X ID for privacy protection purposes. In such cases, a given UE 115 may instruct network entity 105-b to use the pseudo V2X ID for discovery-related communications. For example, UE 115-b may send a V2X ID mapping indication 225 to network entity 105-b, indicating a mapping between UE 115-b's V2X ID and a pseudo V2X ID. Therefore, network entity 105-b may perform a pseudo V2X ID mapping procedure 230, whereby network entity 105-b may use UE 115-b's pseudo V2X ID when performing communications associated with UE 115-b.

[0105] Based on the received discovery message response 220, network entity 105-b may generate a discovery result message 235, which may indicate which UEs among the UEs 115 served by network entity 105-b are eligible for discovery by UE 115-a based on one or more parameters. In some examples, network entity 105-b may include the V2X ID associated with each of the available UEs 115 in the discovery result message 235. For example, the discovery result message 235 may include the pseudo V2X ID of UE 115-b, the V2X ID of UE 115-c, and the V2X ID of UE 115-d. Therefore, network entity 105-b may send the discovery result message 235 to network entity 105-a.

[0106] Network entity 105-a may receive a corresponding discovery result message 235 from each of the second network entities 105 to which network entity 105-a sent discovery message 210. In some examples, network entity 105-a may combine the V2X IDs included in each corresponding discovery result message 235 into a single V2X ID list, which indicates each available UE 115 across all second network entities 105. Therefore, network entity 105-a may send a V2N2X discovery result message 240 including the single V2X ID list to UE 115-a. In some examples, UE 115-a may perform a radio connection establishment procedure with one or more of the UEs 115 indicated in the V2N2X discovery result message 240.

[0107] Figure 3 Examples of a process flow 300 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure are shown. In some examples, process flow 300 may implement aspects of wireless communication system 100 and wireless communication system 200. Process flow 300 includes UE 115-f, which may be an example of UE 115 sending discovery message 210 (e.g., a declaring UE for model A discovery or UE 115-f for model B discovery). Additionally, UE 115-g and UE 115-h may be corresponding examples of UE 115 receiving discovery messages (e.g., a monitoring UE for model A discovery or a discoverer UE for model B discovery). In some examples, UE 115-f may be served by network entity 105-c, and UEs 115-g and 115-h may be served by network entity 105-d, wherein network entities 105-c and 105-d are corresponding examples of network entity 105, as referenced Figure 1 and Figure 2 Described. In some examples, network entity 105-c and network entity 105-d may be associated with the same network or different networks. The following alternative examples can be implemented, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added. Furthermore, while process flow 300 illustrates processes between multiple wireless devices, it should be understood that these processes can occur between any number of network devices and network device types.

[0108] At 305, UE 115-f may send a discovery message to network entity 105-c requesting information about UE 115 for sidelink communication. In some examples, the discovery message may include one or more parameters indicating the discovery model type, the geographic range relative to UE 115-f, the broadcast type, or a combination thereof.

[0109] In some examples, the broadcast type may include a set of broadcast types, where the geographic range includes a set of geographic ranges, and each broadcast type in the set of broadcast types is associated with a corresponding geographic range in the set of geographic ranges. In some examples, the discovery message may include a first discovery code indicating one or more parameters, and the UE 115-f may be associated with a set of discovery codes, each corresponding to a set of one or more parameters. In some examples, the one or more parameters may also indicate the reason for the discovery of the UE 115-f (e.g., V2N2X discovery). In some examples, the discovery message may be sent via an RRC configuration message, an RRC reconfiguration message, a MAC-CE message, or an SR message.

[0110] At 310, network entity 105-c may determine one or more second network entities 105 to which a discovery message should be sent. In some examples, the one or more second network entities 105 may satisfy a geographical range relative to UE 115-f, as indicated in the discovery message. In some examples, the one or more second network entities 105 may satisfy a certain number of second network entities closest to UE 115-f. Figure 3 As illustrated, network entity 105-c can determine to send a discovery message to at least network entity 105-d. However, it should be understood that network entity 105-d can determine to send a discovery message to... Figure 3 An additional second network entity 105, not illustrated in the text, sends a discovery message.

[0111] At 315, network entity 105-c may send a discovery message received from UE 115-f to one or more second network entities 105 (e.g., including at least network entity 105-d). In some examples, network entity 105-c may communicate with network entity 105-d via the X2 interface.

[0112] At 320, UEs 115-g and 115-h can receive from network entity 105-d an indication of the presence of a discovery message that requests information associated with establishing sidelink communication with UE 115-f.

[0113] In some cases, UEs 115-g and 115-h may receive a DCI scrambled with an RNTI associated with sidelink discovery, and decode the DCI using the RNTI, wherein the decoding result indicates that the associated downlink channel includes a discovery message. Therefore, UEs 115-g and 115-h may receive a first discovery code indicating one or more parameters of the discovery message via the associated downlink channel. In some cases, UEs 115-g and 115-h may receive an indication of the RNTI associated with sidelink discovery before receiving the DCI. Therefore, decoding the DCI may be based on receiving the indication of the RNTI. In some examples, UEs 115-g and 115-h may periodically monitor the DCI scrambled with the RNTI associated with sidelink discovery.

[0114] In some cases, UE 115-g and 115-h may receive a first discovery code that includes bit values ​​indicating the presence of a discovery message and one or more parameters indicating the discovery message.

[0115] In some cases, UEs 115-g and 115-h may receive a DCI that includes bits indicating the associated downlink channel including a discovery message. Therefore, UEs 115-g and 115-h may receive a first discovery code via the associated downlink channel that indicates one or more parameters of the discovery message.

[0116] In some cases, UEs 115-g and 115-h may receive an RRC reconfiguration message, which includes a discovery message indicator indicating the presence of a discovery message, a first discovery code indicating one or more parameters of the discovery message, and the reason for the discovery of UE 115-f.

[0117] In some examples, at 325, one or more of UEs 115-g and 115-h may indicate the mapping between the pseudo V2X ID and the V2X ID to network entity 105-d. For example, as part of a response to a discovery message, UE 115-g may send a mapping instructing network entity 105-d to relay the pseudo V2X ID to UE 115-f.

[0118] At 330, UEs 115-g and 115-h may each send a corresponding response to the discovery message, indicating whether the respective UE 115 is available for discovery by UE 115-f based on one or more parameters indicated in the discovery message. For example, at 330-a, UE 115-g may send a response to the discovery message, and at 330-b, UE 115-h sends a response to the discovery message. In some examples, each corresponding response to the discovery message may indicate availability for discovery by UE 115-f based on one or more parameters indicated in the discovery message, and indicate the V2X ID associated with the respective UE 115.

[0119] In some examples, at 335, network entity 105-d may perform a pseudo-mapping V2X procedure. For example, if at 325, UE 115-g indicates a V2X ID mapping, then network entity 105-d may include the pseudo-V2X ID for UE 115-g in the list of UE 115s that meet the criteria used for discovery.

[0120] At 340, network entity 105-d may send to network entity 105-c a list of one or more serving UEs 115 that meet the discovery criteria for sidelink communication according to one or more parameters. In some examples, network entity 105-c may receive a corresponding response to the discovery message from each of the one or more second network entities 105, the corresponding response including a corresponding list of one or more UEs 115 that meet the discovery criteria for sidelink communication according to one or more parameters. Therefore, network entity 105-c may create a single list of UEs 115 that includes each of the one or more UEs 115 that meets the discovery criteria indicated in the corresponding list received from each of the second network entities 105.

[0121] At 345, network entity 105-c may send a control message (e.g., an RRC message) that includes a single list (e.g., V2N2X discovery results) of UEs 115 that meet the criteria for discovery used for sidelink communication based on one or more parameters. In some examples, the single list included in the V2N2X discovery results indicates the corresponding V2X ID of each UE 115 included in the single list.

[0122] At 350, UE 115-f can perform a radio connection establishment procedure with at least one UE 115 from a list of one or more UEs in UE 115, based on one or more parameters. For example, UE 115-f can perform a radio connection establishment procedure with UE 115-g, UE 115-h, or both. UE 115-f can use the corresponding V2X ID included in the V2N2X discovery results to perform each corresponding radio connection establishment procedure.

[0123] Figure 4 A block diagram 400 illustrates a device 405 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0124] Receiver 410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with techniques for sidelink-based discovery). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0125] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for sidelink-based discovery). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0126] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the techniques for side-link-based discovery described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0127] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0128] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0129] In some examples, the communication manager 420 may be configured to use or otherwise cooperate with the receiver 410, transmitter 415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or be integrated with the receiver 410, transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0130] Communication manager 420 may support wireless communication according to examples disclosed herein. For example, communication manager 420 may be capable of, configured to, or operable to support components for sending a discovery message to a network entity requesting information for discovery of a discoverable UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverable UE, broadcast type, or a combination thereof. Communication manager 420 may be capable of, configured to, or operable to support components for receiving a response from the network entity to the discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters. Communication manager 420 may be capable of, configured to, or operable to support components for performing a wireless connection establishment procedure with at least one UE from the list of one or more discoverable UEs among the discoverable UEs, according to the one or more parameters.

[0131] Additionally or alternatively, the communication manager 420 may support wireless communication according to examples disclosed herein. The communication manager 420 is capable of, configured to, or operable to support components for receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with a discovering UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 420 is capable of, configured to, or operable to support components for sending a response to the discovery message to the network entity, the response indicating whether the discovered UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the discovery message.

[0132] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources, reduced latency, and improved signal quality in mobility scenarios.

[0133] Figure 5A block diagram 500 of a device 505 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0134] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with techniques for sidelink-based discovery). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0135] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for sidelink-based discovery). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0136] Device 505 or its various components may be examples of parts used to perform various aspects of the techniques for side-link-based discovery as described herein. For example, communication manager 520 may include discovery message receiving and transmitting component 525, discovery monitoring component 530, wireless connectivity component 535, or any combination thereof. Communication manager 520 may be examples of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use or otherwise cooperate with receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0137] Communication Manager 520 may support wireless communication according to examples disclosed herein. Discovery Message Transmitting Component 525 is capable of, configured to, or operable to support components for sending a discovery message to a network entity requesting information for discovery of a discoverable UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverable UE, broadcast type, or a combination thereof. Discovery Monitoring Component 530 is capable of, configured to, or operable to support components for receiving a response from the network entity to the discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters. Wireless Connectivity Component 535 is capable of, configured to, or operable to support components for performing a wireless connection establishment procedure with at least one UE from the list of one or more discoverable UEs among the discoverable UEs, according to the one or more parameters.

[0138] Additionally or alternatively, the communication manager 520 may support wireless communication according to examples disclosed herein. The discovery monitoring component 530 is capable of, configured to, or operable to support components for receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discovering UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The discovery message receiving component 525 is capable of, configured to, or operable to support components for sending a response to the discovery message to the network entity, the response indicating whether the discovered UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the discovery message.

[0139] Figure 6 A block diagram 600 of a communication manager 620 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of the techniques for sidelink-based discovery as described herein. For example, the communication manager 620 may include a discovery message receiving and transmitting component 625, a discovery monitoring component 630, a wireless connectivity component 635, a decoding component 640, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0140] Communication manager 620 may support wireless communication according to examples disclosed herein. Discovery message sending and receiving component 625 is capable of, configured to, or operable to support components for sending a discovery message to a network entity requesting information for discovery of a discoverable UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverable UE, broadcast type, or a combination thereof. Discovery monitoring component 630 is capable of, configured to, or operable to support components for receiving a response from the network entity to the discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters. Wireless connectivity component 635 is capable of, configured to, or operable to support components for performing a wireless connection establishment procedure with at least one UE from the list of one or more discoverable UEs among the discoverable UEs, according to the one or more parameters.

[0141] In some examples, the broadcast type includes a collection of multiple broadcast types. In some examples, the geographic range includes a collection of multiple geographic ranges. In some examples, each broadcast type in the collection of multiple broadcast types is associated with a corresponding geographic range in the collection of multiple geographic ranges.

[0142] In some examples, the discovery message includes a first discovery code indicating one or more parameters. In other examples, the discovering UE is associated with a set of discovery codes, each corresponding to a specific set of one or more parameters.

[0143] In some examples, one or more parameters also indicate the reason for the discovery by the discovering UE.

[0144] In some examples, the discovering UE is associated with a network entity, and one or more of the discovering UEs are associated with one or more second network entities.

[0145] In some examples, it was found that messages were sent via RRC configuration messages, RRC reconfiguration messages, MAC-CE messages, or SR messages.

[0146] In some examples, the response to the discovery message also indicates the corresponding V2X identifier for each of the discoverer UEs in the list of one or more discoverer UEs.

[0147] In some examples, the discovering UE receives a response to the discovery message via an RRC message.

[0148] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. In some examples, the discovery monitoring component 630 is capable of, configured to, or operable to support components for receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discovering UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. In some examples, the discovery message receiving component 625 is capable of, configured to, or operable to support components for sending a response to the discovery message to the network entity, the response indicating whether the discovered UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the discovery message.

[0149] In some examples, the detection component 630 is capable of, configured to, or able to operate to support components for receiving DCI scrambled with RNTI associated with sidelink discovery. In some examples, the decoding component 640 is capable of, configured to, or able to operate to support components for decoding the DCI using RNTI, wherein the result of the decoding indicates that the associated downlink channel includes the discovery message.

[0150] In some examples, the discovery monitoring component 630 is capable of, configured to, or able to operate to support components for receiving an indication of the RNTI associated with sidelink discovery prior to receiving the DCI, wherein the decoding of the DCI is based on the receipt of the indication of the RNTI.

[0151] In some examples, in order to support receiving discovery messages, the discovery monitoring component 630 is capable of, configured to, or able to operate to support a component for receiving discovery codes for receiving one or more parameters indicating discovery messages via an associated downlink channel.

[0152] In some examples, the discovered UE periodically monitors DCI scrambled with RNTI associated with sidelink discovery.

[0153] In some examples, the detection monitoring component 630 is capable of, configured to, or able to operate to support components for receiving a DCI that includes a bit value indicating the presence of a detection message and one or more parameters indicating the detection message.

[0154] In some examples, the discovery monitoring component 630 is capable of, configured to, or operable to support components for receiving a DCI including a bit value indicating an associated downlink channel, including a discovery message. In some examples, the discovery monitoring component 630 is capable of, configured to, or operable to support components for receiving a discovery message, including a discovery code receiving one or more parameters indicating a discovery message via an associated downlink channel.

[0155] In some examples, to support receiving discovery messages, the discovery monitoring component 630 is capable of, configured to, or able to operate to support components for receiving RRC reconfiguration messages that include the discovery message. In some examples, to support receiving discovery messages, the discovery monitoring component 630 is capable of, configured to, or able to operate to support components for a discovery message indicator indicating the presence of a discovery message. In some examples, to support receiving discovery messages, the discovery monitoring component 630 is capable of, configured to, or able to operate to support components for a discovery code indicating one or more parameters of the discovery message. In some examples, to support receiving discovery messages, the discovery monitoring component 630 is capable of, configured to, or able to operate to support components for the reason for discovery by the discovering UE.

[0156] In some examples, in order to support sending a response to a discovery message, the discovery message receiving component 625 is capable of, configured to, or able to operate to support components for sending, as part of the response to the discovery message, the availability to be discovered by the discovering UE based on one or more parameters indicated in the discovery message, and a first V2X identifier associated with the discovering UE.

[0157] In some examples, the discovery message receiving component 625 is capable of, configured to, or able to operate to support components for sending a mapping between a pseudo V2X identifier and the first V2X identifier to the network entity, wherein the mapping instructs the network entity to relay the pseudo V2X identifier as part of the response to the discovery message to the discovering UE.

[0158] In some examples, the discovering UE is associated with a second network entity that is different from the network entity associated with the discovering UE.

[0159] Figure 7A diagram of a system 700 including a device 705 supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0160] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0161] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725 as described herein, or via a wired or wireless link. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0162] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 730 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting techniques for sidelink-based discovery). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 740 or a processing system including at least one processor 740 may be configured, configurable, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 730 or otherwise.

[0164] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for sending a discovery message to a network entity requesting information for discovery of a discoverable UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discoverable UE, broadcast type, or a combination thereof. The communication manager 720 may be capable of, configured to, or operable to support components for receiving a response from the network entity to the discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters. The communication manager 720 may be capable of, configured to, or operable to support components for performing a wireless connection establishment procedure with at least one UE from the list of one or more discoverable UEs among the discoverable UEs, according to the one or more parameters.

[0165] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. The communication manager 720 is capable of, configured to, or operable to support components for receiving from a network entity a discovery message that requests information associated with establishing sidelink communication with a discovering UE, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 720 is capable of, configured to, or operable to support components for sending a response to the discovery message to the network entity, the response indicating whether the discovered UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the discovery message.

[0166] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0167] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported by or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of the techniques for sidelink-based discovery as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0168] Figure 8 A block diagram 800 of a device 805 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0169] Receiver 810 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0170] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0171] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the techniques for side-link-based discovery described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0172] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0173] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0174] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0175] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving a discovery message from a discovering UE requesting discovery for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting the discovery message received from the discovering UE to one or more second network entities. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a corresponding response to the discovery message from one or more second network entities, the response indicating a corresponding list of one or more discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting a control message to the discovering UE, the control message including a list of discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters.

[0176] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving a first discovery message from a second network entity associated with a discovering UE, requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 820 may be capable of, configured to, or operable to support components for sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a corresponding response from the one or more discovering UEs to the second discovery message, the response indicating whether the corresponding discovering UE is available for discovery by the discovering UE according to the one or more parameters indicated in the second discovery message. The communication manager 820 is capable of, can be configured to, or is operable to support a component for sending to the second network entity a list of one or more discoverable UEs that meet the discovery criteria for the sidelink communication based on one or more parameters.

[0177] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources, reduced latency, and improved signal quality in mobility scenarios.

[0178] Figure 9 A block diagram 900 illustrates a device 905 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0179] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0180] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0181] Device 905 or its various components may be examples of parts used to perform various aspects of the techniques for side-link-based discovery as described herein. For example, communication manager 920 may include discovery monitoring component 925, discovery message sending and receiving component 930, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0182] Communication Manager 920 may support wireless communication according to examples disclosed herein. Discovery Monitoring Component 925 is capable of, configured to, or operable to support components for receiving discovery messages from a discovering UE requesting discovery for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. Discovery Message Transmitting Component 930 is capable of, configured to, or operable to support components for transmitting discovery messages received from the discovering UE to one or more second network entities. Discovery Monitoring Component 925 is capable of, configured to, or operable to support components for receiving corresponding responses to discovery messages from one or more second network entities, the responses indicating a corresponding list of one or more discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters. Discovery Message Transmitting Component 930 is capable of, configured to, or operable to support components for transmitting control messages to the discovering UE, the control messages including a list of discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters.

[0183] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The discovery monitoring component 925 is capable of, configured to, or operable to support components for receiving a first discovery message from a second network entity associated with the discovering UE, requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The discovery message receiving component 930 is capable of, configured to, or operable to support components for sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters. The discovery monitoring component 925 is capable of, configured to, or operable to support components for receiving a corresponding response from the one or more discovering UEs to the second discovery message, the response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message. The discovery message receiving component 930 is capable of being configured or operated to support a component for sending to the second network entity a list of one or more discoverable UEs that meet the criteria for discovery for the sidelink communication based on one or more parameters.

[0184] Figure 10A block diagram 1000 of a communication manager 1020 supporting techniques for sidelink-based discovery according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of the techniques for sidelink-based discovery as described herein. For example, the communication manager 1020 may include a discovery monitoring component 1025, a discovery message sending and receiving component 1030, and an identifier mapping component 1035, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0185] The communication manager 1020 may support wireless communication according to examples disclosed herein. The discovery monitoring component 1025 is capable of, configured to, or operable to support components for receiving a discovery message from a discovering UE requesting discovery for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The discovery message receiving and transmitting component 1030 is capable of, configured to, or operable to support components for transmitting the discovery message received from the discovering UE to one or more second network entities. In some examples, the discovery monitoring component 1025 is capable of, configured to, or operable to support components for receiving a corresponding response to the discovery message from one or more second network entities, the response indicating a corresponding list of one or more discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters. In some examples, the discovery message sending and receiving component 1030 is capable of, configured to, or able to operate to support components for sending control messages to the discovering UE, the control messages including a list of discovering UEs that meet the criteria for discovery for sidelink communication based on one or more parameters.

[0186] In some examples, one or more second network entities satisfy the geographical range relative to the discovering UE.

[0187] In some examples, one or more second network entities satisfy a certain number of second network entities that are closest to the discovering UE.

[0188] In some examples, the control message is an RRC message for the vehicle-to-network-to-everything discovery result, and the list indicates the corresponding V2X identifier for each discoverer UE in the discoverer UE.

[0189] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. In some examples, the discovery monitoring component 1025 is capable of, configured to, or operable to support components for receiving a first discovery message from a second network entity associated with the discovering UE, requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. In some examples, the discovery message receiving component 1030 is capable of, configured to, or operable to support components for sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters. In some examples, the discovery monitoring component 1025 is capable of, configured to, or operable to support components for receiving a corresponding response from the one or more discovering UEs to the second discovery message, the response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message. In some examples, the discovery message sending and receiving component 1030 is capable of, configured to, or able to operate to support a component for sending to the second network entity a list of one or more discoverable UEs that meet the criteria for discovery for the sidelink communication based on one or more parameters.

[0190] In some examples, each corresponding response to the second discovery message includes a corresponding V2X identifier associated with the corresponding discovered UE. In some examples, the list of discovered UEs that meet the discovery criteria includes each corresponding V2X identifier.

[0191] In some examples, the identifier mapping component 1035 is capable of, configured to, or operable to support components for receiving a mapping between a pseudo-V2X identifier and a V2X identifier from a first discoverer UE among the one or more discoverer UEs, wherein the mapping instructs the network entity to include the pseudo-V2X identifier in the list of discoverer UEs that meet the discovery criteria.

[0192] In some examples, the network entity sends a list of discoverable UEs that meet the criteria used for discovery via the X2 interface.

[0193] Figure 11A diagram of a system 1100 including a device 1105 supporting techniques for sidelink-based discovery, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and obtaining communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0194] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0195] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by one or more of at least one processor 1135, cause device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by one of the at least one processor 1135, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0196] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks supporting techniques for sidelink-based discovery). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1130) host functions for performing the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories in at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configurable, or operable to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0197] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

[0198] In some examples, the communication manager 1120 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1120 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1120 may manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1120 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0199] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving a discovery message from a discovering UE requesting discovery for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 1120 may be capable of, configured to, or operable to support components for transmitting the discovery message received from the discovering UE to one or more second network entities. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a corresponding response to the discovery message from one or more second network entities, the response indicating a corresponding list of one or more discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters. The communication manager 1120 may be capable of, configured to, or operable to support components for transmitting a control message to the discovering UE, the control message including a list of discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters.

[0200] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving a first discovery message from a second network entity associated with a discovering UE, requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, geographic range relative to the discovering UE, broadcast type, or a combination thereof. The communication manager 1120 may be capable of, configured to, or operable to support components for sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a corresponding response from the one or more discovering UEs to the second discovery message, the response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message. The communication manager 1120 is capable of, configured to, or operable to support a component for sending to the second network entity a list of one or more discoverable UEs that meet the discovery criteria for the sidelink communication based on one or more parameters.

[0201] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0202] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors in at least one processor 1135 to cause the device 1105 to perform various aspects of the techniques for sidelink-based discovery as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0203] Figure 12 A flowchart illustrating a method 1200 for supporting techniques for side-link-based discovery according to various aspects of this disclosure is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0204] At 1205, the method may include: sending a discovery message to a network entity requesting information for the discovery of the discovered UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference needed]. Figure 6 The discovery message sending and receiving component 625 is described and executed.

[0205] At 1210, the method may include: receiving a response from a network entity to a discovery message, the response indicating a list of one or more discoverable UEs among the discoverable UEs that meet the discovery criteria for sidelink communication according to one or more parameters. Operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1210 may be provided by reference to [reference needed]. Figure 6 The detection and monitoring component 630 described herein is used to perform this action.

[0206] At 1215, the method may include: performing a radio connection establishment procedure with at least one UE from a list of one or more discoverable UEs, based on one or more parameters. The operation of block 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to... Figure 6 The wireless connectivity component 635 described is used to perform this function.

[0207] Figure 13 A flowchart illustrating a method 1300 for supporting techniques for side-link-based discovery according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0208] At 1305, the method may include: receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discovering UE, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 6 The detection and monitoring component 630 described herein is used to perform this action.

[0209] At 1310, the method may include: sending a response to a discovery message to a network entity, the response indicating whether the discovered UE is capable of being discovered by the discovered UE according to one or more parameters indicated in the discovery message. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 6 The discovery message sending and receiving component 625 is described and executed.

[0210] Figure 14A flowchart illustrating a method 1400 for sidelink-based discovery, exemplifying various aspects of this disclosure, is shown. Operation of method 1400 can be implemented by a network entity or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 3 and Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0211] At 1405, the method may include: receiving from the discovering UE a discovery message requesting information for discovery of the discovering UE to conduct sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference]. Figure 10 The detection and monitoring component 1025 is described as performing this action.

[0212] At 1410, the method may include: sending a discovery message received from the discovering UE to one or more second network entities. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to... Figure 10 The discovery message sending and receiving component 1030 is used to perform this action.

[0213] At 1415, the method may include: receiving a corresponding response to a discovery message from one or more second network entities, the corresponding response indicating a corresponding list of one or more discovering UEs that meet the discovery criteria for sidelink communication according to one or more parameters. Operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1415 may be provided by reference to [reference needed]. Figure 10 The detection and monitoring component 1025 is described as performing this action.

[0214] At 1420, the method may include: sending a control message to the discovering UE, the control message including a list of discovering UEs that meet the criteria for discovery for sidelink communication according to one or more parameters. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be derived from references... Figure 10 The discovery message sending and receiving component 1030 is described and executed.

[0215] Figure 15A flowchart illustrating a method 1500 for sidelink-based discovery, exemplifying various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a network entity or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figures 1 to 3 and Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0216] At 1505, the method may include: receiving from a second network entity associated with the discovering UE a first discovery message requesting information for discovering the discovering UE to conduct sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 10 The detection and monitoring component 1025 is described as performing this action.

[0217] At 1510, the method may include: sending a second discovery message to one or more discoverer UEs served by a network entity, the second discovery message including one or more parameters. The operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to... Figure 10 The discovery message sending and receiving component 1030 is described and executed.

[0218] At 1515, the method may include: receiving a corresponding response to a second discovery message from one or more discovering UEs, the corresponding response indicating whether the respective discovering UE is capable of being used for discovery by the discovering UE according to one or more parameters indicated in the second discovery message. Operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1515 may be provided by reference to [reference needed]. Figure 10 The detection and monitoring component 1025 is described as performing this action.

[0219] At 1520, the method may include: sending to a second network entity a list of one or more discoverable UEs that meet the discovery criteria for sidelink communication based on one or more parameters. The operation of block 1520 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 10 The discovery message sending and receiving component 1030 is described and executed.

[0220] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a discovering UE, the method comprising: sending to a network entity a discovery message requesting information for discovering the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; receiving from the network entity a response to the discovery message, the response indicating a list of one or more discovering UEs among the discovering UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters; and performing a wireless connection establishment procedure with at least one UE from the list of one or more discovering UEs among the discovering UEs.

[0221] Aspect 2: According to the method of aspect 1, wherein the broadcast type includes a plurality of broadcast types, and the geographic range includes a plurality of geographic ranges, and each of the plurality of broadcast types is associated with a corresponding geographic range among the plurality of geographic ranges.

[0222] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the discovery message includes a first discovery code indicating the one or more parameters, and the discovering UE is associated with a set of discovery codes, each corresponding to a corresponding set of the one or more parameters.

[0223] Aspect 4: The method according to any one of Aspects 1 to 3, wherein one or more parameters further indicate the reason for the discovery by the discoverer UE.

[0224] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the discovering UE is associated with the network entity, and the one or more discovering UEs among the discovering UEs are associated with one or more second network entities.

[0225] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the discovery message is sent via an RRC configuration message, an RRC reconfiguration message, a MAC-CE message, or an SR message.

[0226] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the response to the discovery message further indicates a corresponding V2X identifier for each of the discoverer UEs in the list of one or more discoverer UEs.

[0227] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the discovering UE receives the response to the discovery message via an RRC message.

[0228] Aspect 9: A method for wireless communication at a discovered UE, the method comprising: receiving from a network entity a discovery message requesting information associated with establishing sidelink communication with the discovered UE, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovered UE, a broadcast type, or a combination thereof; and sending to the network entity a response to the discovery message, the response indicating whether the discovered UE is capable of being discovered by the discovered UE according to the one or more parameters indicated in the discovery message.

[0229] Aspect 10: The method according to aspect 9, the method further comprising: receiving a DCI scrambled with an RNTI associated with sidelink discovery; and decoding the DCI using the RNTI, wherein the result of the decoding indicates that the associated downlink channel includes the discovery message.

[0230] Aspect 11: The method according to aspect 10, the method further comprising: receiving an indication of the RNTI associated with sidelink discovery before receiving the DCI, wherein decoding of the DCI is based at least in part on receiving the indication of the RNTI.

[0231] Aspect 12: The method according to any one of Aspects 10 to 11, wherein receiving the discovery message comprises: receiving a discovery code indicating one or more parameters of the discovery message via the associated downlink channel.

[0232] Aspect 13: The method according to any one of Aspects 10 to 12, wherein the discovered UE periodically monitors the DCI scrambled with the RNTI associated with sidelink discovery.

[0233] Aspect 14: The method according to any one of Aspects 9 to 13, the method further comprising: receiving a DCI including a bit value indicating the presence of the discovery message and a discovery code indicating the one or more parameters of the discovery message.

[0234] Aspect 15: The method according to any one of Aspects 9 to 14, the method further comprising: receiving a DCI including a bit value indicating an associated downlink channel including the discovery message; and receiving the discovery message including: receiving a discovery code indicating the one or more parameters of the discovery message via the associated downlink channel.

[0235] Aspect 16: The method according to any one of Aspects 9 to 15, wherein receiving the discovery message comprises: receiving an RRC reconfiguration message, the RRC reconfiguration message comprising: a discovery message indicator indicating the existence of the discovery message; a discovery code indicating the one or more parameters of the discovery message; and a reason for the discovery by the discovering UE.

[0236] Aspect 17: The method according to any one of Aspects 9 to 16, wherein sending the response message to the discovery message comprises: as part of the response to the discovery message, sending availability to be discovered by the discovering UE according to the one or more parameters indicated in the discovery message and a first V2X identifier associated with the discovering UE.

[0237] Aspect 18: The method according to aspect 17, the method further comprising: sending to the network entity a mapping between a pseudo V2X identifier and the first V2X identifier, wherein the mapping instructs the network entity to relay the pseudo V2X identifier as part of the response to the discovery message to the discovering UE.

[0238] Aspect 19: The method according to any one of Aspects 9 to 18, wherein the discovering UE is associated with a second network entity, the second network entity being different from the network entity associated with the discovering UE.

[0239] Aspect 20: A method for wireless communication at a network entity, the method comprising: receiving from a discovering UE a discovery message requesting information for discovery of the discovering UE for sidelink communication, the discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; sending the discovery message received from the discovering UE to one or more second network entities; receiving from the one or more second network entities a corresponding response to the discovery message, the corresponding response indicating a corresponding list of one or more discovering UEs among the discovering UEs that satisfy the discovery criteria for the sidelink communication according to the one or more parameters; and sending to the discovering UE a control message, the control message including a list of the discovering UEs that satisfy the discovery criteria for the sidelink communication according to the one or more parameters.

[0240] Aspect 21: According to the method of aspect 20, wherein one or more second network entities satisfy the geographical range relative to the discovering UE.

[0241] Aspect 22: The method according to any one of Aspects 20 to 21, wherein the one or more second network entities satisfy a certain number of second network entities closest to the discovering UE.

[0242] Aspect 23: The method according to any one of Aspects 20 to 22, wherein the control message is an RRC message for the vehicle-to-network-to-everything discovery result, and the list indicates the corresponding V2X identifier of each discoverer UE in the discoverer UE.

[0243] Aspect 24: A method for wireless communication at a network entity, the method comprising: receiving from a second network entity associated with a discovering UE a first discovery message requesting information for discovery of the discovering UE for sidelink communication, the first discovery message including one or more parameters indicating a discovery model type, a geographic range relative to the discovering UE, a broadcast type, or a combination thereof; sending a second discovery message to one or more discovering UEs served by the network entity, the second discovery message including the one or more parameters; receiving from the one or more discovering UEs a corresponding response to the second discovery message, the corresponding response indicating whether the corresponding discovering UE is capable of being discovered by the discovering UE according to the one or more parameters indicated in the second discovery message; and sending to the second network entity a list of the one or more discovering UEs that meet the criteria for discovery for the sidelink communication according to the one or more parameters.

[0244] Aspect 25: The method according to aspect 24, wherein each corresponding response to the second discovery message includes a corresponding V2X identifier associated with the corresponding discovered UE, and the list of discovered UEs satisfying the discovery criteria includes each corresponding V2X identifier.

[0245] Aspect 26: The method according to aspect 25, the method further comprising: receiving from a first discoverer UE of the one or more discoverer UEs a mapping between a pseudo V2X identifier and a V2X identifier, wherein the mapping instructs the network entity to include the pseudo V2X identifier in the list of discoverer UEs that satisfy the discovery criteria.

[0246] Aspect 27: The method according to any one of Aspects 24 to 26, wherein the network entity transmits the list of discoverer UEs that satisfy the criteria for the discovery via the X2 interface.

[0247] Aspect 28: A discoverer UE for wireless communication, the discoverer UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the discoverer UE to perform a method according to any one of Aspects 1 to 8.

[0248] Aspect 29: A discoverer UE for wireless communication, the discoverer UE comprising: at least one component for performing the method according to any one of aspects 1 to 8.

[0249] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors individually or jointly to perform the method according to any one of aspects 1 to 8.

[0250] Aspect 31: A discoverer UE for wireless communication, the discoverer UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the discoverer UE to perform a method according to any one of aspects 9 to 19.

[0251] Aspect 32: A discoverer UE for wireless communication, the discoverer UE comprising at least one component for performing the method according to any one of aspects 9 to 19.

[0252] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors individually or jointly to perform the method according to any one of aspects 9 to 19.

[0253] Aspect 34: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 20 to 23.

[0254] Aspect 35: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 20 to 23.

[0255] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors individually or jointly to perform the method according to any one of aspects 20 to 23.

[0256] Aspect 37: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 24 to 27.

[0257] Aspect 38: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 24 to 27.

[0258] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors individually or jointly to perform the method according to any one of aspects 24 to 27.

[0259] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0260] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0261] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0262] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0263] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0264] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0265] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0266] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0267] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0268] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0269] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0270] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A discoverer user equipment (UE), the discoverer user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the discoverer UE: A discovery message is sent to a network entity requesting information for the discovery of a discoverable UE to enable sidelink communication. The discovery message includes one or more parameters indicating the discovery model type, the geographic range relative to the discoverable UE, the broadcast type, or a combination thereof. Receive a response to the discovery message from the network entity, the response indicating a list of one or more discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; as well as A wireless connection establishment process is performed with at least one UE from the list of one or more discoverable UEs based on the one or more parameters.

2. The discoverer UE according to claim 1, wherein the broadcast type includes a plurality of broadcast types, and wherein the geographic range includes a plurality of geographic ranges, and wherein each of the plurality of broadcast types is associated with a corresponding geographic range among the plurality of geographic ranges.

3. The discoverer UE of claim 1, wherein the discovery message includes a first discovery code indicating the one or more parameters, and wherein the discoverer UE is associated with a set of discovery codes, each corresponding to a respective set of the one or more parameters.

4. The discoverer UE according to claim 1, wherein one or more parameters further indicate the reason for the discovery by the discoverer UE.

5. The discoverer UE of claim 1, wherein the discoverer UE is associated with the network entity, and the one or more discoverer UEs in the discoverer UEs are associated with one or more second network entities.

6. The discoverer UE according to claim 1, wherein the discovery message is sent via a radio resource control configuration message, a radio resource control reconfiguration message, a media access control-control element message, or a scheduling request message.

7. The discoverer UE of claim 1, wherein the response to the discovery message further indicates a corresponding vehicular network identifier for each of the discoverer UEs in the list of one or more discoverer UEs.

8. The discoverer UE according to claim 1, wherein the discoverer UE receives the response to the discovery message via a radio resource control message.

9. A discoverer user equipment (UE), said discoverer user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the discoverer UE: The network entity receives a discovery message that requests information associated with establishing sidelink communication with the discovering UE. The discovery message includes one or more parameters indicating the discovery model type, the geographic range relative to the discovering UE, the broadcast type, or a combination thereof. as well as Send a response to the discovery message to the network entity, the response indicating whether the discovered UE can be used for discovery by the discovered UE based on one or more parameters indicated in the discovery message.

10. The discoverer UE of claim 9, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the discoverer UE to: Receive downlink control information scrambled with a radio network temporary identifier associated with sidelink discovery; and The radio network temporary identifier is used to decode the downlink control information, wherein the decoding result indicates that the associated downlink channel includes the discovery message.

11. The discoverer UE of claim 10, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the discoverer UE to: Before receiving the downlink control information, an indication of the radio network temporary identifier associated with sidelink discovery is received, wherein decoding of the downlink control information is based at least in part on receiving the indication of the radio network temporary identifier.

12. The discoverer UE according to claim 10, wherein, In order to receive the discovery message, the one or more processors can operate individually or jointly to execute the code to enable the discovered UE to: A discovery code indicating one or more parameters of the discovery message is received via the associated downlink channel.

13. The discoverer UE of claim 10, wherein the discoverer UE periodically monitors the downlink control information scrambled with the radio network temporary identifier associated with sidelink discovery.

14. The discoverer UE of claim 9, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the discoverer UE to: Receive downlink control information including bit values ​​indicating the presence of the discovery message and discovery codes indicating one or more parameters of the discovery message.

15. The discoverer UE of claim 9, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the discoverer UE to: Receive downlink control information including bit values ​​indicating the associated downlink channel, including the discovery message; and In order to receive the discovery message, the one or more processors can also operate individually or jointly to execute the code to enable the discovered UE to: A discovery code indicating one or more parameters of the discovery message is received via the associated downlink channel.

16. The discoverer UE according to claim 9, wherein, In order to receive the discovery message, the one or more processors can operate individually or jointly to execute the code to enable the discovered UE to: Receive a radio resource control reconfiguration message, the radio resource control reconfiguration message including: A discovery message indicator that indicates the existence of the discovery message; The discovery code indicating one or more parameters of the discovery message; and The reason for the discovery by the discoverer UE.

17. The discovery UE according to claim 9, wherein, In order to send a response to the discovery message, the one or more processors can operate individually or jointly to execute the code to enable the discovered UE to: As part of the response to the discovery message, the availability to be discovered by the discovering UE based on one or more parameters indicated in the discovery message, and a first vehicle network identifier associated with the discovering UE, are sent.

18. The discoverer UE of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the discoverer UE to: Send a mapping between a pseudo vehicular network identifier and the first vehicular network identifier to the network entity, wherein the mapping instructs the network entity to relay the pseudo vehicular network identifier as part of the response to the discovery message to the discovering UE.

19. The discoverer UE of claim 9, wherein the discoverer UE is associated with a second network entity, the second network entity being different from the network entity associated with the discoverer UE.

20. A method for conducting wireless communication at a discoverer user equipment (UE), the method comprising: A discovery message is sent to a network entity requesting information for the discovery of a discoverable UE to enable sidelink communication. The discovery message includes one or more parameters indicating the discovery model type, the geographic range relative to the discoverable UE, the broadcast type, or a combination thereof. Receive a response to the discovery message from the network entity, the response indicating a list of one or more discovering UEs that meet the discovery criteria for the sidelink communication according to the one or more parameters; as well as A wireless connection establishment process is performed with at least one UE from the list of one or more discoverable UEs based on the one or more parameters.

21. The method of claim 20, wherein the broadcast type includes a plurality of broadcast types, and wherein the geographic range includes a plurality of geographic ranges, and wherein each of the plurality of broadcast types is associated with a corresponding geographic range among the plurality of geographic ranges.

22. The method of claim 20, wherein the discovery message includes a first discovery code indicating the one or more parameters, and wherein the discovering UE is associated with a set of discovery codes, each corresponding to a corresponding set of the one or more parameters.

23. The method of claim 20, wherein one or more parameters further indicate the reason for the discovery by the discovering UE.

24. The method of claim 20, wherein the discovering UE is associated with the network entity, and the one or more discovering UEs are associated with one or more second network entities.

25. The method of claim 20, wherein the discovery message is sent via a radio resource control configuration message, a radio resource control reconfiguration message, a media access control-control element message, or a scheduling request message.

26. The method of claim 20, wherein the response to the discovery message further indicates a corresponding vehicular network identifier for each of the list of one or more of the discovered UEs.

27. The method of claim 20, wherein the discovering UE receives the response to the discovery message via a radio resource control message.

28. A method for conducting wireless communication at a discovering user equipment (UE), the method comprising: The network entity receives a discovery message that requests information associated with establishing sidelink communication with the discovering UE. The discovery message includes one or more parameters indicating the discovery model type, the geographic range relative to the discovering UE, the broadcast type, or a combination thereof. as well as Send a response to the discovery message to the network entity, the response indicating whether the discovered UE can be used for discovery by the discovered UE based on one or more parameters indicated in the discovery message.

29. The method of claim 28, further comprising: Receive downlink control information scrambled with a radio network temporary identifier associated with sidelink discovery; as well as The radio network temporary identifier is used to decode the downlink control information, wherein the decoding result indicates that the associated downlink channel includes the discovery message.

30. The method according to claim 29, further comprising: Before receiving the downlink control information, an indication of the radio network temporary identifier associated with sidelink discovery is received, wherein decoding of the downlink control information is based at least in part on receiving the indication of the radio network temporary identifier.

Images