Frequency Range 2 (FR2) sidelink discovery

Abstract

Certain aspects of the present disclosure relate to techniques for sidelink discovery in millimeter wave (e.g., frequency range 2 (FR2), or 24.25 GHz to 52.6 GHz) bands. For example, the disclosed techniques provide for generating a sidelink discovery message that includes device information and non-device information of a UE. The sidelink discovery message is output for transmission. A sidelink connection with a receiver (Rx) UE can then be established after the sidelink discovery message is output. FR2 communications generally require beam training. After beam sweeping, a transmitter (Tx) UE and the Rx UE are aware of the main beam direction and need to discover each other at a device level by associating the beam pair link to a peer UE. Since FR2 links generally have high overhead for establishment and maintenance, the disclosed techniques enable device level and service level discovery using discovery messages.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Application No. 17 / 131,223, filed on December 22, 2020, which has been assigned to the assignee of this application and is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to aspects of wireless communication, and more specifically, to techniques for side link communication and beam management. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3GPP Long Term Evolution (LTE) systems, LTE-A systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. New radios (such as 5G NR) are an example of emerging telecommunications standards. NR is a set of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards using OFDMA and cyclic prefixes (CP) on the downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0006] However, with the continued increase in demand for mobile broadband access, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0007] The systems, methods, and apparatuses of this disclosure have several aspects, none of which is solely responsible for their desired properties. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. Upon consideration of this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of this disclosure provide advantages including improved feedback signaling.

[0008] Some aspects provide a method for wireless communication by a user equipment (UE). The method includes: generating a sidelink discovery message that includes device information and non-device information of the UE; outputting the sidelink discovery message for transmission; and establishing a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0009] Some aspects provide a method for wireless communication. The method includes: detecting a sidelink discovery message that includes device information and non-device information of a transmitting (Tx) UE; and establishing a sidelink connection with the Tx UE based on the sidelink discovery message.

[0010] Some aspects provide a user equipment (UE). The UE typically includes a processing system configured to generate a sidelink discovery message that includes device information and non-device information of the UE; and a transmitter configured to transmit the sidelink discovery message, wherein the processing system is further configured to establish a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0011] Some aspects provide a UE. The UE typically includes at least one antenna; and a processing system configured to detect sidelink discovery messages, including device information and non-device information of the transmitting (Tx) UE, via the at least one antenna, and to establish a sidelink connection with the Tx UE via the at least one antenna based on the sidelink discovery messages.

[0012] Some aspects provide an apparatus for wireless communication by a UE. The apparatus typically includes a processing system configured to generate a sidelink discovery message including device information and non-device information of the UE; and an interface configured to output the sidelink discovery message for transmission, wherein the processing system is further configured to establish a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0013] Some aspects provide an apparatus for wireless communication by a UE. The apparatus typically includes a processing system configured to: detect a sidelink discovery message including device information and non-device information of the transmitting (Tx) UE; and establish a sidelink connection with the Tx UE based on the sidelink discovery message.

[0014] Some aspects provide an apparatus for wireless communication by a UE. The apparatus typically includes: a unit for generating a sidelink discovery message including device information and non-device information of the UE; a unit for outputting the sidelink discovery message for transmission; and a unit for establishing a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0015] Some aspects provide an apparatus for wireless communication by a UE. The apparatus typically includes: a unit for detecting a sidelink discovery message that includes device information and non-device information of the sending (Tx) UE; and a unit for establishing a sidelink connection with the Tx UE based on the sidelink discovery message.

[0016] Some aspects provide a computer-readable medium for wireless communication by a UE. The computer-readable medium typically includes code executable to: generate a sidelink discovery message including device information and non-device information of the UE; output the sidelink discovery message for transmission; and, after outputting the sidelink discovery message, establish a sidelink connection with a receiving (Rx) UE.

[0017] Some aspects provide a computer-readable medium for wireless communication by a UE. The computer-readable medium typically includes code executable to: detect a sidelink discovery message including device information and non-device information of the sending (Tx) UE; and, based on the sidelink discovery message, establish a sidelink connection with the Tx UE.

[0018] Various aspects of this disclosure provide UEs, units, apparatuses, processors, and computer-readable media for performing the methods described herein.

[0019] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0020] Therefore, the above-described features of this disclosure can be understood in detail by referring to a more specific description of the aspects briefly outlined above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be construed as limiting its scope, as the specification may allow for other equally valid aspects.

[0021] Figure 1 This is a conceptual block diagram illustrating an exemplary telecommunications system according to certain aspects of this disclosure.

[0022] Figure 2 This is a block diagram conceptually illustrating the design of an exemplary base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0023] Figure 3A and Figure 3B A schematic diagram of an example vehicle-to-everything (V2X) system is shown, representing some aspects of this disclosure.

[0024] Figure 4A and Figure 4B The message used for discovery in the side link is shown.

[0025] Figure 5 An example beam training period between two UEs in side link communication is shown in accordance with certain aspects of this disclosure.

[0026] Figure 6 An example rediscovery process using sidelink communication between two UEs is shown, based on certain aspects of this disclosure.

[0027] Figure 7 This is a flowchart illustrating example operations for wireless communication according to certain aspects of this disclosure.

[0028] Figure 8 This is a flowchart illustrating example operations for wireless communication according to certain aspects of this disclosure.

[0029] Figure 9 A communication device is shown that may include various components configured to perform the operations of the techniques disclosed herein.

[0030] Figure 10 A communication device is shown that may include various components configured to perform operations for the techniques disclosed herein.

[0031] For ease of understanding, the same reference numerals are used where possible to denote the same elements common in the figures. It is conceivable that elements disclosed in one aspect can be advantageously used in other aspects without specific description. Detailed Implementation

[0032] This disclosure provides apparatus, methods, processing systems, and computer-readable media for sidelink discovery. For example, the disclosed techniques provide methods for generating a sidelink discovery message that includes device information and non-device information of the UE. The sidelink discovery message is output for transmission. A sidelink connection can then be established with the receiving (Rx) UE after the output of the sidelink discovery message. Typically, high-frequency (e.g., frequency range 2, or 24.25 GHz to 52.6 GHz) communication requires beam training. After beam scanning, the sending (Tx) UE and the Rx UE become aware of the main beam direction and need to discover each other at the device level by associating beam pairs with peer UEs. Since FR2 links typically have high overhead for establishment and maintenance, the disclosed techniques enable device-level and service-level discovery using discovery messages. Furthermore, the discovery message can contain beamforming information for reception and future beam association.

[0033] The following description provides examples of configurations for SL communication in a communication system and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Moreover, features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement the apparatus or the method may be practiced. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods implemented as supplementary or alternative structures, functions, or structures and functions to the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims. The term “exemplary” as used herein means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0034] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks using different RATs. In some cases, 5G NR RAT networks can be deployed.

[0035] Figure 1 An example wireless communication network 100 in which aspects of this disclosure can be implemented is shown. For example, the wireless communication network 100 may be an NR system (e.g., a 5G NR network).

[0036] like Figure 1 As shown, the wireless communication network 100 may include multiple base stations (BSs) 110a-z (each BS is also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. BS 110 may provide communication coverage for a specific geographic area (sometimes referred to as a “cell”), which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown in the figure) within the wireless communication network 100 via various types of backhaul interfaces (e.g., direct physical connection, wireless connection, virtual network, etc.) using any suitable transport network.

[0037] exist Figure 1 In the example shown, such as Figure 1 As shown, BS 110a, BS 110b, and BS 110c can be macro BSs corresponding to macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS corresponding to pico cell 102x. BS 110y and 110z can be femto BSs corresponding to femto cells 102y and 102z, respectively. A BS can support one or more cells. BS 110 in the wireless communication network 100 communicates with user equipment (UE) 120a-y (each UE is also individually referred to as UE 120 or collectively as UE 120 herein). UE 120 (e.g., 120x, 120y, etc.) can be distributed throughout the wireless communication network 100, and each UE 120 can be stationary or mobile. In some cases, UE 120a can establish sidelink communication with UE 120t, which may or may not be covered by another cell or base station (such as macro cell 102a or base station 110a). As further discussed in the various examples below, UE 120a and UE 120t can use millimeter waves to establish sidelink communication without relying on base station 110a.

[0038] Depending on certain aspects, UE 120 can be configured to perform discovery operations. For example... Figure 1As shown, UE 120a includes a discovery manager 122. Discovery manager 122 can be configured to perform discovery operations for reselecting a relay UE, as described in more detail herein. BS 110 may also include a discovery manager 112. Discovery manager 112 can use discovery messages to configure resources for relay selection, as described in more detail herein.

[0039] The wireless communication network 100 may also include a relay station (e.g., relay station 110r), also referred to as a relay station, which receives data and / or other information transmissions from an upstream station (e.g., BS 110a or UE 120r) and sends data and / or other information transmissions to a downstream station (e.g., UE 120 or BS 110), or relays transmissions between UEs 120 to facilitate communication between devices.

[0040] Network controller 130 can be coupled to a group of BSs 110 and provide coordination and control for these BSs 110. Network controller 130 can communicate with BSs 110 via backhaul. BSs 110 can also communicate with each other via wireless or wired backhaul (e.g., directly or indirectly).

[0041] Figure 2 It was shown (for example, Figure 1 Exemplary components of BS 110a and UE 120a in the wireless communication network 100, which can be used to implement aspects of this disclosure.

[0042] At BS 110a, the transmit processor 220 can receive data from data source 212 and control information from controller / processor 240. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. Processor 220 can process (e.g., encode and symbol mapping) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 220 can also generate reference symbols, such as for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). Transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable) and can provide the output symbol stream to modulators (MODs) 232a-232t. Each modulator 232 can process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-232t can be transmitted via antennas 234a-234t, respectively.

[0043] At UE 120a, antennas 252a-252r can receive downlink signals from BS 110a and can provide received signals to demodulators (DEMODs) in transceivers 254a-254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to data sink 260, and provide decoded control information to controller / processor 280.

[0044] On the uplink, at UE 120a, transmit processor 264 can receive and process data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Transmit processor 264 can also generate reference symbols for reference signals (e.g., for the Sounding Reference Signal (SRS)). Symbols from transmit processor 264 can be pre-coded (if possible) by TX MIMO processor 266, further processed by demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to BS 110a. At BS 110a, uplink signals from UE 120a can be received by antenna 234, processed by modulator 232, detected by MIMO detector 236 (if possible), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120a. The receiver processor 238 can provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240.

[0045] Memory 242 and 282 can store data and program code for BS 110a and UE 120a, respectively. Scheduler 244 can schedule data transmission for UE on downlink and / or uplink.

[0046] The controller / processor 280 and / or other processors and modules at UE 120a can perform or direct the execution of processes according to the techniques described herein. Figure 2 As shown, the controller / processor 280 of UE 120a has a discovery manager 122, and the controller / processor 280 of BS 110 has a discovery manager 112. Although shown at the controller / processor, the operations described herein can be performed using other components of UE 120a.

[0047] Figure 3A and Figure 3B A schematic diagram of an example vehicle-to-everything (V2X) system is shown, representing some aspects of this disclosure. For example, Figure 3A and Figure 3B The UE shown can communicate via the sidelink channel and can perform sidelink CSI reporting as described herein.

[0048] Figure 3A and Figure 3B The V2X system provided in China offers two complementary transmission modes. Figure 3AThe first transmission mode illustrated by example involves direct communication between participants who are close to each other in a local area (e.g., also known as side link communication). Figure 3B The second transmission mode, illustrated by way of example, involves network communication over a network, which can be implemented via a Uu interface (e.g., a wireless communication interface between a Radio Access Network (RAN) and a UE). As shown, UE352 and UE354 can communicate with each other using a side link (SL) 398.

[0049] refer to Figure 3A The diagram illustrates a V2X system 300 (e.g., including vehicle-to-vehicle (V2V) communication) with two UEs 302 and 304 (e.g., vehicles). A first transmission mode allows direct communication between different participants in a given geographic location. As shown, the vehicle can have a wireless communication link 306 with a person (V2P) (e.g., via a UE) through a PC5 interface. Communication between UEs 302 and 304 can also occur through PC5 interface 308. Similarly, communication from UE 302 to other highway components (e.g., highway component 310), such as traffic signals or signs (V2I), can occur through PC5 interface 312. Regarding... Figure 3A In each communication link shown, bidirectional communication can occur between components, so each component can be both a transmitter and a receiver of information. The V2X system 300 can be a self-managing system implemented without the assistance of a network entity. Since no network service interruption occurs during handover operations of mobile vehicles, the self-managing system can improve spectrum efficiency, reduce costs, and increase reliability. The V2X system can be configured to operate in licensed or unlicensed spectrum, so any vehicle equipped with the system can access public frequencies and share information. This coordinated / shared spectrum operation allows for secure and reliable operation.

[0050] Figure 3BA V2X system 350 is illustrated for communication between UE 352 (e.g., a vehicle) and UE 354 (e.g., a vehicle) via network entity 356. These network communications can occur through discrete nodes such as base stations (e.g., eNBs or gNBs), which send and receive information to and from UE 352 and UE 354 (e.g., relaying information between UE 352 and UE 354). For example, network communication via vehicle-to-network (V2N) links (e.g., Uu links 358 and 310) can be used for long-distance communication between vehicles, such as transmitting information about a car accident occurring a distance ahead along a road or highway. Nodes can send other types of communication to vehicles, such as traffic flow conditions, road hazard warnings, environmental / weather reports, and service station availability. This data can be obtained from cloud-based shared services.

[0051] In some cases, two or more dependent entities (e.g., UEs) can communicate with each other using sidelink signals. As mentioned above, V2V and V2X communications are examples of communications that can be transmitted via sidelinks. Other applications of sidelink communication can include public safety or service announcement communications, communications for nearby services, communications for UE-to-network relay, device-to-device (D2D) communications, Internet of Things (IoE) communications, Internet of Things (IoT) communications, mission-critical mesh communications, and other suitable applications. Typically, a sidelink can refer to a direct link between one dependent entity (e.g., UE1) and another dependent entity (e.g., UE2). Therefore, even if a scheduling entity (e.g., BS) can be used for scheduling or control purposes, a sidelink can be used to send and receive communications (also referred to herein as “sidelink signals”) without relaying the communications through the scheduling entity. In some examples, licensed spectrum (unlike WLANs, which typically use unlicensed spectrum) can be used to transmit sidelink signals.

[0052] Various sidelink channels can be used for sidelink communication, including the Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Feedback Channel (PSFCH). The PSDCH can carry a discovery expression that enables nearby devices to discover each other. The PSCCH can carry control signaling such as sidelink resource configuration and other parameters for data transmission, and the PSSCH can carry data transmission. The PSFCH can carry feedback such as Channel State Information (CSI) related to the quality of the sidelink channel.

[0053] Example discovery techniques for sidelink beam training

[0054] For Long Term Evolution (LTE), discovery and communication pools can be configured separately in Radio Resource Control (RRC) reconfiguration messages and System Information Blocks (SIBs), or they can be pre-configured (e.g., in the standard). For example, for a UE in idle operating mode, a common communication pool can be provided in LTE SIB18, and a common discovery pool can be provided in LTE SIB19. A common resource pool typically refers to resources available to multiple UEs for a specific purpose (e.g., data communication or discovery). Common communication and discovery pools can be provided separately in pre-configurations for out-of-coverage (OOC) UEs. For a UE in connected operating mode, dedicated communication and discovery pools can be provided separately in RRC reconfiguration messages. Dedicated resource pools typically refer to resources dedicated to a specific UE for communication or discovery.

[0055] In some cases, transmit (TX) and receive (RX) pools can be configured. For example, a public TX pool can be configured or pre-configured in the SIB. The public TX pool can be overridden by a dedicated configuration via an RRC reconfiguration message. The RX pool can always be public among LTE UEs and can only be provided (e.g., configured) via an RRC message during a handover (HO) from one cell to another. The RX pool can be unknown to the UE's RRC state. In some implementations, dedicated resource allocation can be configured only for the TX pool.

[0056] There are various differences between the discovery pool and the communication pool. For example, sidelink control information (SCI) cannot be used for discovery messages. Both the communication pool and the discovery pool can be defined by a periodic subframe resource pool in the time domain and a periodic resource block (RB) pool in the frequency domain. In LTE, the communication pool and the discovery pool can share the same RB pool definition. For example, the bandwidth used for the discovery and communication pools can be from 2 RBs to 200 RBs, and the start position of the resource pool can be configurable. For the communication pool, separate frequency allocations can be defined for control and data transmission. The communication pool and the discovery pool can use different periodicity configurations. For example, the period for the communication pool can be from 40ms to 320ms, but the period for the discovery pool can be from 320ms to 10.24 seconds. In other words, the communication pool can have a higher density than the discovery pool.

[0057] Figure 4A and Figure 4B The message used for discovery in the side link is shown. Figure 4A The discovery protocol, referred to as "Model A" discovery, is illustrated. As shown, UE 402 can send announcement messages 412, 414, 416, and 418 (hereinafter also referred to as "discovery announcements"). These announcement messages can be received by other UEs 404, 406, 408, and 410 that are listening for them. The announcement messages can be as follows: Figure 3A The message is transmitted in the PC5 communication channel. Once received, one or more announcement messages can be used by UE 402 to connect with one or more of UEs 404, UE 406, UE 408, and UE 410.

[0058] Figure 4B The discovery protocol, known as "Model B" discovery, is illustrated. As shown, UE 402 can be the discoverer UE and may be sending request messages 452, 454, 456, and 458 (hereinafter also referred to as "discovery announcements"). The request messages can be received by one or more UEs 404, 406, 408, and 410. For example, as shown, UEs 404 and 406 can send response messages 460 and 462 back to UE 402 to facilitate a connection on the sidelink. For example, UE 402 can perform channel measurements to select the UE among UEs 404 and 406 with the highest link quality and perform connection establishment with the selected UE.

[0059] Therefore, in some cases, for sidelink communication in frequency range 2 (FR2, e.g., encompassing the band from 24.25 GHz to 52.6 GHz, also known as the millimeter wave range) or similar frequency ranges subject to path loss (attenuation), beamforming is required to enable communication over the practical range, thereby mitigating the directional nature of high-frequency beams. This beamforming requires thorough beam searching and periodic beam training for maintenance, increasing the burden on energy efficiency and overhead.

[0060] Furthermore, sidelink FR2 communication can be more challenging in real-world scenarios where many UEs can form beam pairs (BPLs) with each other. This differs from beamforming at base stations (including base stations for Uu links in the sidelink), where each UE only needs to form a BPL with one base station (gNB). Due to this distributed nature of the network, system-wide resources need to be allocated for beam training. These resources are periodic. UEs can transmit beam training reference signals (BT-RS or BT-RS sequences) at the beam training time. The receiving (Rx) UE can detect the BT-RS and transmit feedback on the dominant beam (e.g., random access channel, "RACH"). Beam training is performed as a thorough beam search and scan of the entire 360-degree angular space at the transmitting (Tx) UE and Rx UE (e.g., ...). (One beam).

[0061] Once the Tx UE and Rx UE have established a possible BPL through beam scanning, the UE can perform device discovery to establish communication for various applications. Device discovery requires knowing the UE identifier (ID) (e.g., Layer 2 ID) used for sub-6 operations.

[0062] Figure 5 An example beam training period between two UEs in sidelink communication is shown, according to certain aspects of this disclosure. As shown, the beam training period includes multiple training periods T0, T1, ... T m Each training session T m This can include three events: (1) transmitting multiple beam pilots in multiple directions; (2) processing the beam pilots to identify the direction of the desired signal strength; and (3) transmitting a random access channel (RACH) sequence in the identified direction. Completing beam training will enable the Tx UE and Rx UE to know the beam direction.

[0063] For example, Figure 5 The Tx UE in the lower left can first transmit multiple pilot beams in various directions (e.g., thoroughly in 360 degrees). Figure 5 The Rx UE in the lower right corner can perform beam scanning similarly. After completing the beam scan, the Rx UE determines the main direction of each BT-RS sequence received from the Tx UE. Each Tx UE can have orthogonal BT-RS. The Rx UE then processes the beam pilots and transmits the RACH sequence to the Tx UE in the main direction.

[0064] For Tx and Rx UEs to discover each other, a UE must associate its BPL with another UE. This discovery allows the UE to identify devices and upper-layer services. Because FR2 links typically have high overhead for establishment and maintenance, it is beneficial for the UE to establish and / or maintain trained or paired links for relevant services. Therefore, operations can save time that would otherwise be spent creating and dismantling unnecessary links.

[0065] This disclosure enables the transmission of discovery messages at both the device and service levels. Discovery messages may also include beamforming information for receiving and future beam association or directional communication. Due to the directional nature of millimeter waves, such as in links at FR2, there are no system-wide resources for discovery messages. There is no broadcasting of directional messages.

[0066] In some cases, the discovery message may include the UE's device ID. Current and potential future device locations may also be included in the discovery message. For example, the UE may gather location information based on its current area ID and its direction of motion and / or acceleration. An Rx UE may use the location of a Tx UE or changes in its location to determine the trajectory of the Tx UE.

[0067] In some cases, a discovery message may include an application layer service ID or a list of application layer service IDs. The discovery message may also include metadata for one or more services listed in the service ID. The discovery message may also include beam and orientation information. For example, the discovery message may indicate the beam training pilots that the UE will use for current and future beam training periods. In some cases, the discovery message will also include the Tx, indicating the beam training timing that the UE will use in future beam training periods. The UE may also send a time-domain division (TDD) mode for the beam corresponding to a directional discovery message. The receiver uses the TDD mode to send a discovery response. The UE receiving the discovery message searches for PSSCH resources in the time slot indicated in the TDD mode to send a discovery response.

[0068] The UE can use device and service information to manage beamforming links. In one scenario, the service ID and metadata are used to accept or reject discovery announcements / notifications. If the Rx UE does not support the service, it can reject the discovery message. The Rx UE can infer that service information from a Tx UE is irrelevant. For example, information from a vehicle behind a Tx UE in another lane (i.e., an Rx UE in a V2X sidelink scenario) might be irrelevant and not used by the Rx UE. In another scenario, the service ID with device location and trajectory, along with metadata, can be used to accept / reject discovery.

[0069] Given the device-service specific discovery messages discussed above, Figures 4A-4B The Model A discovery and Model B discovery discussed can each exhibit the following characteristics. In Model A discovery, the Rx UE can send one or more RACHs to the Tx UE during the beam training period. The Rx UE also sends a discovery announcement in each direction of its sent RACHs. The discovery announcement can contain the BT-RS sequence ID used by the Tx UE for beam training. The discovery announcement can also include one or more future beam training opportunities within the BT period. The discovery announcement is sent via PSSCH (e.g., ...). Figure 6 (As discussed further below), and can be performed using a shared channel resource reservation procedure. The receiver of the discovery notice (e.g., the Tx UE) can send a discovery response. In some cases, even when the Tx UE receives a discovery notice and is not interested, it can still send a discovery response indicating rejection. In some cases, the Tx UE may not send any discovery response regarding the received discovery notice.

[0070] In Model B discovery, a Tx UE that has already sent a beam training pilot can send a discovery message in the direction from which the Rx UE receives the RACH. The Tx UE sends a discovery announcement to the Rx UE. Upon receiving the discovery announcement, the Rx UE determines whether to discover the Tx UE at the device or service level based on the UE ID or service ID indicated in the discovery announcement. If the Rx UE determines that the device or service is of interest, it can send a discovery response based on the time-domain division (TDD) mode of the discovery announcement.

[0071] Example techniques for FR2 discovery in sidelinks

[0072] Certain aspects of this disclosure relate to techniques for sidelink discovery in millimeter-wave (e.g., frequency range 2, or FR2) bands. For example, a UE can generate a sidelink discovery message including device information and non-device information of the UE; output the sidelink discovery message for transmission; and, after outputting the sidelink discovery message, establish a sidelink connection with a receiving (Rx) UE. The UE can identify devices and upper-layer services before performing discovery or abandoning a beamtraining link. Therefore, the discovery process can utilize existing beamtraining links even when different services are involved. In some cases, the discovery message may include beamforming information for reception and future beam association. Discovery messages can be sent directionally without broadcasting. Discovery messages do not require the use of system-wide resources. Discovery messages may include other information to enable future directional communication.

[0073] As discussed above, due to the inherent path loss in high-frequency ranges (e.g., FR2), radio links typically require beamforming and spatial filtering to achieve sufficient range. In relatively low-frequency ranges (e.g., FR1), links can transmit omnidirectionally or with wide beams, making beamforming unnecessary. In cases involving multiple UEs, each sidelink UE can form multiple beampuppet links (BPLs) with other sidelink UEs (or peer UEs). Therefore, the beam discovery process involved may have higher overhead than the beam discovery process between the UE and the base station (such as the gNB or eNB in ​​a Uu link).

[0074] Figure 6An example rediscovery process using sidelink communication between two UEs according to certain aspects of this disclosure is illustrated. As shown, discovery using PSSCH is performed after the beam training period. During the beam training period, system-wide resources can be used for beam discovery. The beam training process can use long beam training periods that repeat over a large timescale. For example, a 100ms beam training period can be repeated once per second, resulting in 10% overhead. By comparison, for beam training of the Uu link between the UE and the base station, a 5ms beam training period can be used every 20ms synchronization period.

[0075] The initial beamforming license (BPL) can be established after the beam training period. Then, the Tx UE and Rx UE can use the PSSCH to send and / or receive beam discovery messages for device and service discovery. As shown, various discovery events may occur in the PSSCH. By identifying device and service information, the Tx UE or Rx UE can respond to discovery messages when interested. For example, when the Tx UE is running an application that collects data useful to the Rx UE, the Rx UE may want to discover the Tx UE. For example, in a V2X scenario, the Rx UE may want to discover the Tx UE used to collect visual or navigational information collected at the Tx UE that is not directly usable by the Rx UE. On the other hand, even if beam training between the Tx UE and Rx UE is successful and a BPL can be established, the Tx or Rx UE may determine that information or applications provided by the other UE are not of interest or relevant. For example, in a V2X scenario, when the Rx UE is associated with a vehicle in a different lane, some safety messages provided by the Tx UE of the vehicle ahead may be useless. Similarly, sensor data from the front-facing camera may be useful for the RxUE behind the TxUE, but not for the RxUE in front.

[0076] This disclosure provides techniques for discovering FR2 devices using non-device information such as service information. For example, it is beneficial for a UE to continue using existing FR2 links for relevant services due to the high overhead of establishing and maintaining FR2 links. Using existing FR2 links can also reduce the time spent creating and dismantling FR2 links. Non-device information may also include beamforming information for reception and future beam association, or other information for enabling future directional communications.

[0077] Figure 7 This is a flowchart illustrating an example operation 700 for wireless communication according to certain aspects of this disclosure. Operation 700 can be, for example, by... Figure 3A , Figure 3B , Figure 4A , Figure 4B and Figure 5The UE is used to execute.

[0078] Operation 700 can be implemented in one or more processors (e.g., Figure 2 Software components that execute and run on the controller / processor 280. Furthermore, for example, this can be achieved via one or more antennas (e.g., Figure 2 The antenna 252 is used to enable the relay UE to transmit and receive signals in operation 700. In some aspects, the relay UE can transmit and / or receive signals by obtaining and / or outputting signals through the bus interface of one or more processors (e.g., controller / processor 280).

[0079] Operation 700 can begin at block 710, generating a sidelink discovery message that includes both device and non-device information of the UE. At block 720, the UE outputs the sidelink discovery message for transmission. At block 730, after outputting the sidelink discovery message, the UE establishes a sidelink connection with the receiving (Rx) UE. In some aspects, outputting the sidelink discovery message can be equivalent to sending the sidelink discovery message. In other aspects, outputting the sidelink discovery message can be used for transmission.

[0080] In some aspects, the UE can generate a sidelink discovery message that includes both device and non-device information, and establish a sidelink connection with the Rx UE based on this sidelink discovery message. In another aspect, the UE's processing system or chipset outputs the sidelink discovery message for transmission. For example, the UE can generate a sidelink discovery message for use by a network entity (e.g., via a Uu link). In this case, the Rx UE can obtain the discovery message from the network entity and use it in either direction relative to the UE to establish an FR2 sidelink connection. In this case, the UE or the Rx UE can use non-device information to determine whether to establish a sidelink connection. In some cases, at least one of the UE's current location or planned location can enable the Rx UE to determine the UE's trajectory, such as when the UE may reach certain future locations.

[0081] In some respects, non-device information includes service information. Non-device information enables the Rx UE to determine, based on service information, whether to initiate a sidelink connection establishment, send a sidelink connection establishment request, or avoid establishing a sidelink connection with the UE. Service information includes at least one of the following: current location, planned location, at least one application layer service identifier (ID), or metadata of one or more services with at least one application layer service ID. The planned location can be determined based on at least one of the following: current area ID, UE direction of movement, or UE maneuvering mode (e.g., in the context of V2X services, maneuvering mode may include lane changing).

[0082] In some respects, non-device information includes beam information. Beam information enables an Rx UE to determine whether to accept a discovery request, wait for discovery, send a signal for discovery, or avoid establishing a sidelink connection with the UE. For example, beam information may include at least one of the following (including all): an indication of at least one beam training pilot for the UE to use for the current or future beam training period, a time division duplex (TDD) mode, or one or more beam training times for the UE. TDD mode enables an Rx UE to send a discovery response. TDD mode allows an Rx UE to search for at least one Physical Sidelink Shared Channel (PSSCH) resource in the time slot indicated in TDD mode and output a discovery response for transmission based on at least one PSSCH resource.

[0083] In some aspects, the UE may also transmit one or more beam training resources along with non-device information during the current or future beam training period. Beam training resources may include storage and signal processing resources for beam training. For example, beam training resources may include a Random Access Channel (RACH), a Beam Training Reference Signal (BT-RS), or both RACH and BTR. In some cases, beam training resources may include only beam training information. Beam training resources may indicate the optimal beam with the maximum equivalent channel gain from possible beam pairs. This information can allow the UE to evaluate beam allocation considerations when multiple UE beam collisions exist. In some cases, the UE outputs a discovery announcement message for transmission via one or more beam training directions associated with one or more beam training resources. The discovery announcement message is output for transmission on the PSSCH.

[0084] In some respects, the UE may perform a shared channel resource reservation process before outputting a discovery announcement message for output. The discovery announcement message contains the Beam Training Reference Signal (BT-RS) identifier (ID) used by the UE for beam training. In some cases, the discovery announcement message may include one or more future beam training opportunities within the beam training period.

[0085] In some respects, the UE outputs a discovery announcement message for transmission via a direction associated with one of the one or more beam training resources on which the UE receives communication from the Rx UE.

[0086] Figure 8 This is a flowchart illustrating an example operation 800 for wireless communication according to certain aspects of this disclosure. Operation 800 can be, for example, by an Rx UE responding to an operation 700 by a UE (e.g., Figure 3A , Figure 3B , Figure 4A , Figure 4B and Figure 5 The corresponding UE in the code is used to execute the operation. Operation 800 can be used with... Figure 7 The operations are complementary to 700. Therefore, Figure 7 The aspects described in the text can be similarly applied to... Figure 8 .

[0087] Operation 800 can be implemented in one or more processors (e.g., Figure 2 The software components that execute and run on the controller / processor 280. Furthermore, the remote UE can transmit and receive signals during operation 600, for example, via one or more antennas (e.g., Figure 2 This can be achieved via antenna 252. In some aspects, the transmission and / or reception of signals by the remote UE can be achieved via a bus interface of one or more processors (e.g., controller / processor 280) that acquires and / or outputs signals.

[0088] Operation 800 can begin at block 810 by detecting a sidelink discovery message that includes both device and non-device information of the sending (Tx) UE. At 820, the Rx UE establishes a sidelink connection with the Tx UE based on the sidelink discovery message. For example, when the Rx UE receives and analyzes the non-device information indicated in the discovery message, the Rx UE can accept or reject the Tx UE's discovery request. In some cases, the discovery message may include a service ID and metadata in the form of a discovery announcement or notice. For example, if the Rx UE does not support the indicated service, it can reject the discovery message. The Rx UE can also infer that the service information from the Tx UE is irrelevant and reject the discovery request.

[0089] In some aspects, the UE receives a discovery announcement message from the Tx UE in the direction associated with the random access channel (RACH) through which the Tx UE transmits its sidelink discovery message. The UE determines whether it is interested in establishing a sidelink connection with the Tx UE based on at least one of the device information or non-device information from the sidelink discovery message. This determination may be in response to the discovery announcement message. In some aspects, the non-device information includes service information. The UE can establish a sidelink connection with the Tx UE by evaluating the service information.

[0090] In some aspects, service information includes at least one of the following: current location, planned location, metadata of one or more services with at least one application layer service identifier (ID) or at least one application layer service ID. The planned location is determined based on at least one of the current region ID, the Tx UE's direction of movement, or the Tx UE's maneuvering mode. The UE can determine the Tx UE's trajectory based on at least one of the Tx UE's current location or planned location. The UE can accept or reject sidelink discovery messages based on the Tx UE's current location and trajectory. In some cases, the UE can reject sidelink discovery messages if at least one application layer service ID or metadata does not support one or more services.

[0091] In some respects, the UE may infer that service information from the Tx UE is irrelevant. For example, service information includes the UE's current position after its position in different driving lanes. Therefore, when the UE receives instructions to travel at a higher speed than the Tx UE (e.g., after overtaking and in the absence of data indicating a possible collision), the UE's position in different lanes may be irrelevant to the UE.

[0092] In some aspects, discovery messages include device information and non-device information. Device information may include the identifier of the device, such as the device ID used for device discovery. Non-device information may include service information, location information, and other information (e.g., beamforming information). In some cases, location information may include the current device location or a predicted future device location (e.g., based on road map data and travel data). For example, a UE may collect location information based on its current area ID, its direction of movement, and / or its indicated movement patterns (e.g., turning, changing lanes, etc.). An Rx UE may use location information to determine the trajectory or movement pattern of a Tx UE, which is used to determine whether device discovery is accepted or rejected. Service information may include the identifier of the service provided, such as a service ID. Non-device information may also include metadata for one or more services listed in the service ID.

[0093] In some respects, discovery messages include beam and direction information. For example, a discovery message may indicate the beam training pilot used by the UE that generates the discovery message for current and / or future beam training. In some cases, beam and direction information may also include the beam training timing used by the Tx UE during future beam training periods. In some cases, the UE may also transmit a TDD mode for the beam corresponding to a direction discovery message. For example, an Rx UE may use TDD mode to transmit a discovery response: the Rx UE receiving the discovery message may search for PSSCH resources in the time slot indicated in the TDD mode to transmit a discovery response.

[0094] Figure 9 The diagram illustrates operations that may include those configured to perform the techniques disclosed herein (e.g., Figure 7 and Figure 8 The communication device 900 comprises various components (e.g., corresponding to functional module unit components) shown in the diagram. The communication device 900 includes a processing system 902 coupled to a transceiver 908. The transceiver 908 is configured to transmit and receive signals for the communication device 900, such as the various signals described herein, via an antenna 910. The processing system 902 may be configured to perform processing functions for the communication device 900, including processing signals received by and / or to be transmitted by the communication device 900.

[0095] Processing system 902 includes processor 904 coupled to computer-readable medium / memory 912 via bus 906. In some aspects, computer-readable medium / memory 912 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 904, cause processor 904 to perform. Figure 7 and Figure 8 The operation is illustrated. In some aspects, the computer-readable medium / memory 912 stores code 914 for generating a sidelink discovery message including device information and non-device information of the UE, code 916 for outputting the sidelink discovery message for transmission, and code 918 for establishing a sidelink connection with the receiving (Rx) UE after outputting the sidelink discovery message. In some aspects, the processor 904 has circuitry configured to implement the code stored in the computer-readable medium / memory 912. The processor 904 includes circuitry 922 for generating a sidelink discovery message including device information and non-device information of the UE, circuitry 924 for outputting the sidelink discovery message for transmission, and circuitry 926 for establishing a sidelink connection with the receiving (Rx) UE after outputting the sidelink discovery message.

[0096] Figure 10 A communication device 1000 is shown, which may include various components (e.g., corresponding to functional module components) configured to perform operations of the techniques disclosed herein, such as Figure 7 and Figure 8 The operation is illustrated in the diagram. The communication device 1000 includes a processing system 1002 coupled to a transceiver 1008. The transceiver 1008 is configured to transmit and receive signals for the communication device 1000 via an antenna 1010, such as the various signals described herein. The processing system 1002 may be configured to perform processing functions for the communication device 1000, including processing signals received and / or transmitted by the communication device 1000.

[0097] Processing system 1002 includes processor 1004 coupled to computer-readable medium / memory 1012 via bus 1006. In some aspects, computer-readable medium / memory 1012 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1004, cause processor 1004 to perform. Figure 7 and Figure 8 The operation is illustrated. In some aspects, the computer-readable medium / memory 1012 stores code 1014 for detecting a sidelink discovery message including device information and non-device information of the sending (Tx) UE; and code 1016 for establishing a sidelink connection with the Tx UE based on the sidelink discovery message. In some aspects, the processor 1004 has circuitry configured to implement the code stored in the computer-readable medium / memory 1012. The processor 1004 includes circuitry 1022 for detecting a sidelink discovery message including device information and non-device information of the sending (Tx) UE; and circuitry 1024 for establishing a sidelink connection with the Tx UE based on the sidelink discovery message.

[0098] In addition to the various aspects described above, specific combinations of aspects also fall within the scope of this disclosure, some of which are detailed below:

[0099] Aspect 1: A method for wireless communication by a user equipment (UE), comprising: generating a sidelink discovery message including device information and non-device information of the UE; outputting the sidelink discovery message for transmission; and, after outputting the sidelink discovery message, establishing a sidelink connection with a receiving (Rx) UE.

[0100] Aspect 2: According to the method of aspect 1, wherein the non-device information includes service information, the non-device information enabling the Rx UE to determine whether to avoid establishing the sidelink connection with the UE based on the service information.

[0101] Aspect 3: The method according to any one of Aspects 1-2, wherein the service information includes at least one of the following: current location, planned location, metadata of one or more services of at least one application layer service identifier (ID) or at least one application layer service ID.

[0102] Aspect 4: According to the method of aspect 3, the planned location is determined based on at least one of the current region ID, the movement direction of the UE, or the maneuvering mode of the UE.

[0103] Aspect 5: According to the method of aspect 3, wherein at least one of the current position or planned position of the planned position UE enables the Rx UE to determine the trajectory of the UE.

[0104] Aspect 6: The method according to any one of Aspects 1-5, wherein the non-device information includes beam information that enables the Rx UE to determine whether to avoid establishing the sidelink connection with the UE.

[0105] Aspect 7: According to the method of aspect 6, wherein the beam information includes at least one of the following: an indication of at least one beam training pilot for the UE for the current or future beam training period; a time division duplex (TDD) mode; or one or more beam training times of the UE.

[0106] Aspect 8: According to the method of aspect 7, wherein the TDD mode enables the Rx UE to send a discovery response.

[0107] Aspect 9: According to the method of aspect 7, wherein the TDD mode enables the Rx UE to search for at least one physical-side link shared channel (PSSCH) resource in the time slot indicated in the TDD mode, and output a discovery response based on the at least one PSSCH resource for transmission.

[0108] Aspect 10: The method according to aspect 7 further includes: outputting one or more beam training resources together with the non-device information for transmission during the current or future beam training period.

[0109] Aspect 11: The method according to aspect 10 further includes: outputting a discovery notification message for transmission via one or more beam training directions associated with the one or more beam training resources.

[0110] Aspect 12: According to the method of aspect 11, wherein the discovery notification message is output for transmission on PSSCH.

[0111] Aspect 13: The method according to aspect 11 further includes: performing a shared channel resource reservation process before outputting the discovery notification message for transmission.

[0112] Aspect 14: According to the method of aspect 11, wherein the discovery notification message includes a beam training reference signal (BT-RS) identifier (ID) for beam training by the UE.

[0113] Aspect 15: The method according to aspect 11, wherein the discovery notification message includes one or more future beam training opportunities within the beam training period.

[0114] Aspect 16: According to the method of aspect 10, a discovery announcement message is output for transmission via a direction associated with one of one or more beam training resources on which the UE receives communication from the Rx UE.

[0115] Aspect 17: A method for wireless communication by a user equipment (UE), comprising: detecting a sidelink discovery message including device information and non-device information of a transmitting (Tx) UE; and establishing a sidelink connection with the Tx UE based on the sidelink discovery message.

[0116] Aspect 18: The method according to aspect 17 further includes: obtaining a discovery announcement message from the Tx UE in a direction associated with a random access channel (RACH) through which the Tx UE transmits the sidelink discovery message; and determining, based on at least one of the device information or the non-device information in the sidelink discovery message, whether the UE is interested in establishing the sidelink connection with the Tx UE, the determination being in response to the discovery announcement message.

[0117] Aspect 19: The method according to aspects 17-18, wherein the non-device information includes service information, and wherein establishing the sidelink connection with the Tx UE includes: evaluating whether to establish the sidelink connection with the Tx UE based on the service information.

[0118] Aspect 20: The method according to aspect 19, wherein the service information includes at least one of the following: current location, planned location, metadata of one or more services of at least one application layer service identifier (ID) or said at least one application layer service ID.

[0119] Aspect 21: According to the method of aspect 20, the planned location is determined based on at least one of the current region ID, the movement direction of the TxUE, or the maneuvering mode of the TxUE.

[0120] Aspect 22: The method according to aspect 20 further includes: determining the trajectory of the Tx UE based on at least one of the current location or the planned location of the Tx UE.

[0121] Aspect 23: The method according to aspect 22 further includes: accepting or rejecting the sidelink discovery message based on the current location and trajectory of the Tx UE.

[0122] Aspect 24: The method according to aspect 20 further includes: rejecting the sidelink discovery message when the at least one application layer service ID or the metadata does not support the one or more services.

[0123] Aspect 25: The method according to aspect 19 further includes: inferring that the service information from the Tx UE is irrelevant.

[0124] Aspect 26: The method according to aspect 19, wherein the service information includes the current position of the UE after its position in different driving lanes.

[0125] Aspect 27: The method according to any one of Aspects 17-26, wherein the non-device information includes beam information, and further includes: determining whether to establish a side link with the Tx UE based on the beam information.

[0126] Aspect 28: The method according to aspect 27, wherein the beam information includes at least one of the following: an indication of a beam training pilot for the Tx UE for a current or future beam training period; a time division duplex (TDD) mode; or one or more beam training times of the Tx UE.

[0127] Aspect 29: The method according to aspect 28 further includes: in response to the detection of the side link discovery message, outputting a discovery response for transmission using the TDD mode.

[0128] Aspect 30: The method according to aspect 28 further includes: searching for at least one physical-side link shared channel (PSSCH) resource in the time slot indicated in the TDD mode; and outputting a discovery response for transmission by using the at least one PSSCH resource.

[0129] Aspect 31: The method according to aspect 28 further includes: obtaining a discovery notification message transmitted from the Tx UE via one or more beam directions indicated by transmission of one or more random access channels (RACH) associated with the current or future beam training period; and, in response to the discovery notification message, outputting a discovery response for transmission in one of the beam directions.

[0130] Aspect 32: The method according to aspect 31, wherein the discovery response includes rejection.

[0131] Aspect 33: The method according to any one of aspects 17-32 further includes: avoiding outputting a discovery response for transmission.

[0132] Aspect 34: The method according to aspect 28 further includes: determining, based on the non-device information of the sidelink discovery message, that the UE is interested in the Tx UE; and, based on the determination, outputting a discovery response for transmission to the Tx UE based on the TDD mode.

[0133] Aspect 35: A user equipment (UE) comprising: a processing system configured to generate a sidelink discovery message including device information and non-device information of the UE; and a transmitter configured to transmit the sidelink discovery message, wherein the processing system is further configured to establish a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0134] Aspect 36: A user equipment (UE) comprising: at least one antenna; and a processing system configured to detect a sidelink discovery message including device information and non-device information of a transmitting (Tx) UE via the at least one antenna, and to establish a sidelink connection with the Tx UE via the at least one antenna based on the sidelink discovery message.

[0135] Aspect 37: An apparatus for wireless communication by a user equipment (UE), comprising: a processing system configured to generate a sidelink discovery message including device information and non-device information of the UE; and an interface configured to output the sidelink discovery message for transmission, wherein the processing system is further configured to: establish a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0136] Aspect 38: An apparatus for wireless communication by a user equipment (UE), comprising: a processing system configured to detect a sidelink discovery message including device information and non-device information of a transmitting (Tx) UE, and to establish a sidelink connection with the Tx UE based on the sidelink discovery message.

[0137] Aspect 39: An apparatus for wireless communication by a user equipment (UE), comprising: a unit for generating a sidelink discovery message including device information and non-device information of the UE; a unit for outputting the sidelink discovery message for transmission; and a unit for establishing a sidelink connection with a receiving (Rx) UE after outputting the sidelink discovery message.

[0138] Aspect 40: An apparatus for wireless communication by a user equipment (UE), comprising: a unit for detecting a sidelink discovery message including device information and non-device information of a transmitting (Tx) UE; and a unit for establishing a sidelink connection with the Tx UE based on the sidelink discovery message.

[0139] Aspect 41: A computer-readable medium for wireless communication by a user equipment (UE), comprising code executable to: generate a sidelink discovery message including device information and non-device information of the UE; output the sidelink discovery message for transmission; and, after outputting the sidelink discovery message, establish a sidelink connection with a receiving (Rx) UE.

[0140] Aspect 42: A computer-readable medium for wireless communication by a user equipment (UE), comprising code executable to: detect a sidelink discovery message including device information and non-device information of a transmitting (Tx) UE; and establish a sidelink connection with the Tx UE based on the sidelink discovery message.

[0141] The techniques described in this article can be used in various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are generally used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variations of CDMA. cdma2000 encompasses the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are UMTS versions using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). NR is an emerging wireless communication technology under development.

[0142] The techniques described herein can be used in the wireless networks and radio technologies mentioned above, as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G, 4G, and / or 5G wireless technologies may be used to describe aspects herein, aspects of this disclosure can be applied to other generation-based communication systems.

[0143] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is used interchangeably with BS, Next Generation Node B (gNB or gNodeB), Access Point (AP), Distributed Unit (DU), and Carrier or Transmitter / Receiver Point (TRP). A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allows unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allows unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allows restricted access for UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a home), etc. A BS used for a macrocell can be called a macro BS. A BS used for a picocell can be called a pico BS. A BS used for a femtocell can be called a femto BS or a home BS.

[0144] A UE can also be referred to as a mobile station, terminal, access terminal, user unit, station, client equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical apparatus, biometric sensor / device, such as smartwatch, smart clothing, smart glasses, smart bracelet, smart jewelry (e.g., smart ring, smart bracelet, etc.), wearable device, entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or from a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, and include UEs or network entities such as BSs. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

[0145] Some wireless networks (e.g., LTE) use Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often also called tones, frequency bands, etc. Data can be modulated onto each subcarrier. Generally, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.8 MHz (e.g., 6 RBs), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0146] NR can utilize OFDM with CP on both uplink and downlink, and includes support for half-duplex operation using TDD. In NR, a subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16, ... slots) depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15 kHz, and other subcarrier spacings can be defined for the basic subcarrier spacing, such as 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. Symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. In some examples, MIMO configurations in DL can support up to 8 transmit antennas and multilayer DL transmission with up to 8 streams, and up to 2 streams per UE. In some examples, multi-layer transport with up to two streams per UE can be supported. Aggregation of multiple cells with up to eight serving cells can be supported.

[0147] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and apparatuses within its service area or cell. The scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entity uses the resources allocated by the scheduling entity. A base station is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by that UE for wireless communication. In some examples, a UE can act as a scheduling entity in a point-to-point (P2P) network and / or in a mesh network. In the mesh network example, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0148] In some examples, two or more dependent entities (e.g., UEs) can communicate with each other using sidelink signals. Practical applications of these sidelink communications can include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical mesh, and / or various other suitable applications. Generally, a sidelink signal can refer to a signal transmitted from one dependent entity (e.g., UE1) to another dependent entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., a UE or BS), even if that scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum (unlike wireless LANs that typically use unlicensed spectrum) can be used to transmit sidelink signals.

[0149] The methods disclosed herein include one or more steps or actions for implementing these methods. The method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0150] As used herein, the phrase “at least one of the items” refers to any combination of those items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, cc, and ccc, or any other order of a, b, and c).

[0151] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, derivation, investigation, searching (e.g., searching in a table, database, or other data structure), and confirmation. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and parsing, selecting, choosing, and creating.

[0152] The preceding description is provided to enable those skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the few aspects shown herein, but rather to the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to a singular element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” means one or more. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. No claim shall be construed in accordance with 35 USC. No claim element shall be construed in accordance with the provisions of 35 USC §112(f) unless the element is expressly stated using the phrase “module for…” or, in the case of a method claim, the element is expressly stated using the phrase “step for…”.

[0153] The various operations described above can be performed by any suitable unit capable of performing the corresponding function. The unit may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, in the cases of the operations shown in the figures, those operations may have corresponding functional module unit components with similar numbering. For example, Figure 2 The processors 258, 264, and 266 of the UE 120 and / or the controller / processor 280, and / or the processors 220, 230, 238, and / or the controller / processor 240 of the BS 110 shown can be configured to perform Figure 7 Operation 700 and / or Figure 8 Operation 800.

[0154] The unit for receiving may include Figure 2The transceiver, receiver, or at least one antenna and at least one receiver processor shown. The unit for transmitting, the unit for sending, or the unit for outputting may include... Figure 2 The transceiver, transmitter, or at least one antenna and at least one transmitting processor are shown. Units for generating, establishing, executing, detecting, determining, accepting, rejecting, inferring, and searching may include a processing system, which may include one or more processors, such as... Figure 2 The processors 258, 264, and 266 of the UE 120, and / or the controller / processor 280, and / or the processors 220, 230, 238, and / or the controller / processor 240 of the BS 110.

[0155] In some cases, a device may have an interface (output unit) for outputting frames for transmission, rather than actually sending frames. For example, a processor may output frames to a radio frequency (RF) front end for transmission via a bus interface. Similarly, a device may have an interface (acquisition unit) for acquiring frames received from another device, rather than actually receiving frames. For example, a processor may acquire (or receive) frames from an RF front end via a bus interface for reception.

[0156] The various illustrative logic blocks, modules, and circuits described in connection with this disclosure may be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but optionally, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration.

[0157] If implemented in hardware, an exemplary hardware configuration may include a processing system in a wireless node. The processing system can be implemented using a bus architecture. The bus may include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus can link various circuits, including processors, machine-readable media, and bus interfaces. The bus interface can be used to connect network adapters, etc., to the processing system via the bus. The network adapter can be used to implement signal processing functions at the PHY layer. In the case of user terminal 120 (see...), Figure 1The user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also link various other circuits, such as timing sources, peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how the described functions for the processing system can be optimally implemented, depending on the specific application and the overall design constraints imposed on the system.

[0158] If implemented in software, these functions can be stored or transmitted as one or more instructions or code via a computer-readable medium. Software should be interpreted broadly as representing instructions, data, or any combination thereof, whether it refers to software, firmware, middleware, microcode, hardware description languages, or others. Computer-readable media includes computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be an integral part of the processor. As an example, machine-readable media may include transmission lines, carrier waves modulated by data, and / or computer-readable storage media on which instructions separate from the wireless node are stored, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, for example, in cases where there may be caches and / or general-purpose register files. As an example, machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0159] Software modules can comprise a single instruction or a number of instructions, and can be distributed across several different code segments, different programs, and multiple storage media. Computer-readable media can include multiple software modules. Software modules include instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules can include send modules and receive modules. Each software module can reside in a single storage device or be distributed across multiple storage devices. For example, when a trigger event occurs, a software module can be loaded from a hard disk drive into RAM. During the execution of a software module, the processor can load some instructions into a cache to improve access speed. One or more caches can then be loaded into a general-purpose register file for processor execution. When referring to the functionality of the software module below, it should be understood that these functions are implemented by the processor when instructions are executed from that software module.

[0160] Furthermore, any connection is appropriately referred to as computer-readable medium. 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 (IR), radio, and microwave, the definition of media includes coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. Disks and optical discs as used herein include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray® discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Therefore, in some aspects, computer-readable medium may include non-transitory computer-readable medium (e.g., tangible media). Furthermore, in other aspects, computer-readable medium may include transient computer-readable medium (e.g., signals). Combinations of the above should also be included within the scope of computer-readable medium.

[0161] Therefore, certain aspects may include a computer program product for performing the operations described herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded thereon) thereon, which can be executed by one or more processors to perform the operations described herein. For example, the instructions are used to perform the operations described herein.

[0162] Furthermore, it should be understood that modules and / or other suitable units for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by the user terminal and / or base station as appropriate. For example, such a device may be coupled to a server to facilitate the transmission of units for performing the methods described herein. Alternatively, the various methods described herein may be provided via storage devices (e.g., RAM, ROM, physical storage media such as compressed optical discs (CDs) or floppy disks), enabling the user terminal and / or base station to obtain the various methods when the storage units are coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device may be used.

[0163] It should be understood that the claims are not limited to the precise configurations and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the above-described methods and apparatus without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Generate a sidelink discovery message that includes device information and non-device information of the UE, wherein the non-device information includes beam information that enables the receiving (Rx) UE to determine whether to avoid establishing a sidelink connection with the UE, and wherein the beam information includes at least one of the following: an indication of at least one beam training pilot for the UE for the current or future beam training period, a time division duplex (TDD) mode, or one or more beam training times of the UE; Output the sidelink discovery message for transmission; and Following the output of the sidelink discovery message, a sidelink connection is established with the Rx UE.

2. The method according to claim 1, wherein, The non-device information includes service information, which enables the Rx UE to determine whether to avoid establishing the sidelink connection with the UE based on the service information.

3. The method according to claim 2, wherein, The service information includes at least one of the following: current location, planned location, at least one application layer service identifier (ID), or metadata for one or more services for the at least one application layer service ID.

4. The method according to claim 3, wherein, The planned location is determined based on at least one of the current region ID, the direction of movement of the UE, or the maneuvering mode of the UE, or wherein at least one of the current location or the planned location of the UE enables the Rx UE to determine the trajectory of the UE.

5. The method according to claim 1, wherein, The TDD mode enables the Rx UE to send a discovery response, or wherein the TDD mode enables the Rx UE to search for at least one physical-side crosslink shared channel (PSSCH) resource in the time slot indicated in the TDD mode, and output a discovery response based on the at least one PSSCH resource for transmission.

6. The method according to claim 1, further comprising: One or more beam training resources are output along with the non-device information for transmission during the current or future beam training period.

7. The method according to claim 6, further comprising: Output discovery notification messages for transmission via one or more beam training directions associated with the one or more beam training resources.

8. The method according to claim 7, wherein: The discovery notification message is output for transmission on the PSSCH; The discovery notification message includes the Beam Training Reference Signal (BT-RS) identifier (ID) used by the UE for beam training; or The discovery notification message contains one or more future beam training opportunities within the beam training period.

9. The method according to claim 7, further comprising: Before outputting the discovery notification message for transmission, a shared channel resource reservation process is performed.

10. The method of claim 6, wherein a discovery announcement message is output for transmission via a direction associated with one of the one or more beam training resources on which the UE receives communication from the Rx UE.

11. A method for wireless communication by a user equipment (UE), comprising: The detection includes a sidelink discovery message containing device information and non-device information of the sending (Tx) UE, wherein the non-device information includes beam information that enables the UE to determine whether to avoid establishing a sidelink connection with the Tx UE, and wherein the beam information includes at least one of the following: an indication of at least one beam training pilot for the Tx UE for the current or future beam training period, a time-division duplex (TDD) mode, or one or more beam training times of the Tx UE; and Based on the sidelink discovery message, a sidelink connection is established with the Tx UE.

12. The method of claim 11, further comprising: Discovery announcement messages are obtained from the Tx UE in the direction associated with the random access channel (RACH) through which the Tx UE transmits the sidelink discovery messages; as well as Based on at least one of the device information or the non-device information in the sidelink discovery message, it is determined whether the UE is interested in establishing the sidelink connection with the Tx UE, the determination being in response to the discovery announcement message.

13. The method according to claim 11, wherein, The non-device information includes service information, and establishing the sidelink connection with the Tx UE includes: evaluating whether to establish the sidelink connection with the Tx UE based on the service information.

14. The method according to claim 13, wherein, The service information includes at least one of the following: current location, planned location, at least one application layer service identifier (ID), or metadata for one or more services for the at least one application layer service ID.

15. The method according to claim 14, wherein, The planned location is determined based on at least one of the current region ID, the movement direction of the Tx UE, or the maneuvering mode of the Tx UE.

16. The method of claim 14, further comprising: The trajectory of the Tx UE is determined based on at least one of the current location or the planned location of the Tx UE.

17. The method of claim 16, further comprising: Based on the current location and trajectory of the Tx UE, the sidelink discovery message can be accepted or rejected.

18. The method of claim 14, further comprising: The sidelink discovery message is rejected when the at least one application layer service ID or the metadata does not support the one or more services.

19. The method of claim 13, further comprising: It is inferred that the service information from the Tx UE is irrelevant.

20. The method according to claim 13, wherein, The service information includes the current location of the UE after its position in different driving lanes.

21. The method of claim 11, further comprising: In response to the detection of the sidelink discovery message, a discovery response is output for transmission using the TDD mode.

22. The method of claim 11, further comprising: Search for at least one physical side link shared channel (PSSCH) resource in the time slot indicated in the TDD mode; as well as A discovery response is output for transmission by using the at least one PSSCH resource.

23. The method of claim 11, further comprising: The discovery announcement message sent from the Tx UE is obtained via one or more beam directions indicated by one or more random access channels (RACH) associated with the current or future beam training period; and In response to the discovery notification message, a discovery response is output for transmission in one of the beam directions.

24. The method according to claim 23, wherein, The discovery response includes rejection.

25. The method of claim 11, further comprising: Avoid outputting a discovery response for transmission.

26. The method of claim 11, further comprising: Based on the non-device information in the sidelink discovery message, it is determined that the UE is interested in the Tx UE; as well as Based on the determination, a discovery response is output for transmission to the Tx UE based on the TDD mode.

27. An apparatus for wireless communication, the apparatus comprising: One or more memory units; as well as One or more processors coupled to the one or more memories and configured to perform the method according to any one of claims 1-26.

28. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1-26.

Images