Techniques for communicating sidelink synchronization signals in existing wireless communication deployments
By configuring resources to convey side link synchronization signals (SLSS) in LTE V2X communication, the problem of inconsistent resource configuration between UEs is solved, communication quality and throughput are improved, interference is reduced, and user experience is improved.
Patent Information
- Application Number
- CN202280094653.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-19
- Publication Date
- 2024-11-26
AI Technical Summary
In LTE V2X communication, good communication between UEs may not be possible and frequent interference is caused by inconsistent resource configurations that affect communication quality and throughput.
By configuring resources to communicate SLSS while maintaining logical numbers of multiple consecutive time slots and receiving or sending SLSS in a specific time slot, ensuring synchronization between UEs that support SLSS is prevented from being supported by UEs in these Send data on time slots to reduce interference.
Improved resource determination and interference reduction between UEs are realized, synchronization between UEs that support SLSS is improved, communication quality and communication throughput of devices are improved, and user experience is improved.
Smart Images

Figure CN119032607A_ABST
Abstract
Description
Background Art
[0001] Aspects of the present disclosure relate generally to sidelink wireless communication systems, and more particularly to synchronous sidelink communications.
[0002] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include 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, and single-carrier frequency division multiple access (SC-FDMA) systems.
[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. For example, the fifth generation (5G) wireless communication technology, which may be referred to as 5G New Radio (5G NR), is designed to expand and support diverse usage scenarios and applications relative to current mobile network generations. On the one hand, 5G communication technology may include: enhanced mobile broadband addressing people-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and large-scale machine-type communications that may allow a very large number of connected devices and a relatively small amount of non-delay sensitive information to be sent. However, as the demand for mobile broadband access continues to grow, further improvements to 5G communication technology and beyond 5G technology may be expected.
[0004] In some wireless communication technologies such as 5G, a user equipment (UE) communicates via one or more of a plurality of interfaces. The plurality of interfaces may include a Uu interface between a UE and a base station, wherein the UE may receive communications from the base station via a downlink and send communications to the base station via an uplink. In addition, the plurality of interfaces may include a sidelink interface for communicating directly with one or more other UEs via a sidelink channel (e.g., without passing through a base station). Summary of the invention
[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.
[0006] According to one aspect, a device for wireless communication is provided, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors, the one or more processors being communicatively coupled to the memory and the transceiver. The one or more processors are configured to: configure resources in the one or more time slots for conveying a side link synchronization signal (SLSS) while maintaining a logical number of a plurality of consecutive time slots including the one or more time slots; and at least one of the following operations: receiving the SLSS from a node during at least one time slot of the one or more time slots; or sending the SLSS to one or more nodes during at least one time slot of the one or more time slots.
[0007] On the other hand, a method for wireless communication is provided, the method comprising: configuring resources in one or more time slots for communicating SLSS while maintaining logical numbering of a plurality of consecutive time slots including the one or more time slots; and at least one of the following operations: receiving SLSS from a node during at least one time slot of the one or more time slots; or sending SLSS to one or more nodes during at least one time slot of the one or more time slots.
[0008] On the other hand, an apparatus for wireless communication is provided, the apparatus comprising: a component for configuring resources in one or more time slots for communicating SLSS while maintaining logical numbering of a plurality of consecutive time slots including the one or more time slots; and at least one of the following components: a component for receiving SLSS from a node during at least one time slot of the one or more time slots; or a component for sending SLSS to one or more nodes during at least one time slot of the one or more time slots.
[0009] In another aspect, a computer-readable medium is provided, the computer-readable medium including code that can be executed by one or more processors for wireless communication. The code includes: code for configuring resources in one or more time slots for communicating SLSS while maintaining a logical number of a plurality of consecutive time slots including one or more time slots; and at least one of the following codes: code for receiving SLSS from a node during at least one time slot in the one or more time slots; or code for sending SLSS to one or more nodes during at least one time slot in the one or more time slots.
[0010] To achieve the above-mentioned and related purposes, one or more aspects include the features fully described and particularly pointed out in the following claims. The following detailed description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only a few of the various ways in which the principles of the various aspects can be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects, wherein like numerals represent like elements, and in which:
[0012] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is illustrated;
[0013] Figure 2 is a block diagram illustrating an example of a user equipment (UE) according to various aspects of the present disclosure;
[0014] Figure 3 is a flow chart illustrating an example of a method for configuring resources of a communication side link synchronization signal (SLSS) according to various aspects of the present disclosure;
[0015] Figure 4 An example of resource allocation for sending a scheduling assignment (SA) to reserve resources for SLSS communication according to various aspects of the present disclosure is illustrated; and
[0016] Figure 5 is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and UEs according to various aspects of the present disclosure. DETAILED DESCRIPTION
[0017] Various aspects are now described with reference to the accompanying drawings. In the following description, for the purpose of explanation, in order to provide a thorough understanding of one or more aspects, numerous specific details are described. However, it is apparent that such aspects can be practiced without these specific details.
[0018] The features described overall relate to synchronizing devices using sidelink (SL) communications. For example, SL communications may refer to device-to-device (D2D) communications between devices (e.g., user equipment (UE)) in a wireless network. In a specific example, SL communications of the following items may be defined: vehicle-based communications, such as vehicle-to-vehicle (V2V) communications between two vehicle-based communication devices (e.g., on-board units (OBUs)) located on a vehicle, vehicle-to-infrastructure (V2I) communications (e.g., from a vehicle-based communication device (such as an OBU) to a road infrastructure node (e.g., a roadside unit (RSU))), vehicle-to-network (V2N) communications (e.g., from a vehicle-based communication device to one or more network nodes (such as a base station)), combinations thereof and / or communications with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. In V2X communications, the OBUs may communicate with each other and / or with the RSUs via SL channels.
[0019] V2X communication may occur in one or more time slots. A time slot may be defined in wireless communication technology (e.g., 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) or 5th Generation (5G) New Radio (NR), etc.) as a set of multiple symbols, where the multiple symbols may be one of orthogonal frequency division multiplexing (OFDM) symbols, single carrier frequency division multiplexing (SC-FDM) symbols, or other types of symbols. In one example, the number of symbols in a time slot may vary based on a cyclic prefix (CP) length defined for the symbol.
[0020] In LTE V2X, for example, a UE may use a side link synchronization signal (SLSS) to synchronize timing and / or frequency to one or more of satellite sources such as a global navigation satellite system (GNSS), or to another UE. In some LTE V2X deployments, an evolved Node B (eNB) may not exist, such as deployments in an intelligent transport system (ITS) spectrum, and GNSS may be the primary synchronization source for the UE. However, in some areas or scenarios (e.g., in a tunnel, a garage, or other scenarios where the UE may not have a clear line of sight to the GNSS), the UE may not be able to receive GNSS signals for synchronization, and the UEs may send SLSS to each other to propagate GNSS timing. In some examples, an RSU, which may be static in terms of positioning or location compared to the OBU, may provide SLSS to a vehicle-based communication unit (OBU), where the RSU may synchronize directly to the GNSS or indirectly to the GNSS via other RSUs and LSSS.
[0021] However, in some configurations of LTE V2X, the SLSS feature may not be provided because there may not be time slots reserved for transmitting and receiving SLSS signals. The LTE standard may allow SLSS to be enabled, which may form time slots reserved for SLSS and may change the way the UE calculates the logical time slot index. For example, a UE enabled for SLSS may skip SLSS time slots when determining an incremental time slot index for a non-SLSS time slot. The logical time slot index calculation allows the UE to determine where data reception is expected and / or where interference from other UE transmissions is expected. In a deployment of LTE V2X where the UE is a UE produced before the introduction of the SLSS feature, a different logical time slot index may be followed than a UE produced after the introduction of the SLSS feature. Thus, for example, the two types of UEs may not communicate well with each other and may interfere more frequently because the semi-persistent scheduling (SPS) reservation may be equivalent to different time slots interpreted by the two types of UEs.
[0022] For example, in LTE V2X, a UE may receive a scheduling assignment (SA) from other UEs indicating the number of reserved subchannels reserved by other UEs, a resource reservation period (P_rsvp), a retransmission time interval (TRIV), and a retransmission start subchannel (FRIV). In this example, a UE receiving the SA may know which resources will be used by other UEs in the future. TRIV and P_rsvp may be the conversion numbers of logical time slots used for this purpose. Thus, the UE may form a set of candidate resources that are not reserved, and may sort the set of candidate resources based on the measured signal strength (e.g., received signal strength indicator (RSSI)). The UE may select a resource in the lowest ranked RSSI for transmission because the least interference is expected on the selected resource. However, when the UE has a different mechanism for calculating a logical time slot index, the UE may interpret P_rsvp, TRIB, or FRIV differently, and thus the UE may select a resource that conflicts with transmissions from other UEs for transmission.
[0023] Various aspects described herein relate to the use of SLSS in LTE in which a UE supporting SLSS and a UE not supporting SLSS can calculate the same logical time slot index for a given time slot. In one example, some time slots can be reserved for SLSS transmission (e.g., from an RSU), and an OBU not supporting SLSS does not need to transmit on those time slots, thereby not interfering with the SLSS transmission. This can improve the reception of SLSS by a device supporting SLSS, and can ensure that data transmissions from a device not supporting SLSS are also received without interference from SLSS. In one example, SLSS resources can be configured without actually configuring SLSS via a radio resource configuration (RRC) parameter. As described above, this prevents the UE from calculating different logical time slot indexes. In addition, for example, SLSS resources can be configured once every few milliseconds for SLSS communication (e.g., transmission and / or reception). In this example, a UE supporting SLSS can transmit SLSS in the time slot, which can create RSSI energy at the resource, so that a device not supporting SLSS can be prevented from using the resource for data communication. In another example, a UE supporting SLSS may transmit an SA without data to reserve SLSS resources, and devices not supporting SLSS may refrain from using these resources for data communication based on the SA. In another example, a UE supporting SLSS may transmit an SA without data in the first 2 resource blocks (RBs) of a slot to reserve SLSS slots, and devices not supporting SLSS may refrain from using these slots for data communication based on the SA.
[0024] Various aspects described herein may allow SLSS communications to be implemented in LTE V2X deployments with UEs that do not support SLSS without causing different numbers of logical slot indices between UEs. This may facilitate improved resource determination and interference mitigation between UEs while allowing SLSS functionality to be implemented. In this regard, using SLSS may facilitate improved synchronization between UEs that support SLSS, which may improve communication quality and communication throughput of devices, thereby improving user experience, etc.
[0025] The following will refer to Figures 1 to 5 The described features are presented in more detail.
[0026] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component can be but not limited to a process, a processor, an object, an executable file, a thread of execution, a program and / or a computer running on a processor. By way of example, both an application running on a computing device and a computing device can be a component. One or more components may reside in a process and / or an execution thread, and a component may be located in a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. A component may communicate by means of a local and / or remote process, such as according to a signal having one or more data packets (such as data from a component as follows, which interacts with another component in a local system, a distributed system, and / or interacts with other systems across a network such as the Internet). Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0027] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" can often be used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 version 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA20001xEV-DO, High Speed Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM TM Etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents of an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents of an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the above-mentioned systems and radio technologies and other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the following descriptions, but these techniques can also be applied to applications other than LTE / LTE-A (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems).
[0028] The following description provides examples, but does not limit the scope, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the present disclosure. Each example may omit, replace, or add individual procedures or components as appropriate. For example, the described method may be performed in a different order than described, and various steps may be added, omitted, or combined. In addition, the features described with respect to some examples may be combined in other examples.
[0029] Various aspects or features will be presented with respect to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these approaches may also be used.
[0030] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). The macro cell may include a base station. The small cell may include a femto cell, a pico cell, and a micro cell. In an example, the base station 102 may also include a gNB 180, as further described herein. In one example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for communicating SLSS, as further described herein. Although the UE 104-a is shown as having a modem 240 and a communication component 242, this is an illustrative example, and substantially any node or any type of node may include a modem 240 and a communication component 242 for providing the corresponding functionality described herein.
[0031] Base stations 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., using an S1 interface). Base stations 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) may interface with 5GC 190 via a backhaul link 184. Among other functions, base stations 102 may perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the 5GC 190) over the backhaul link 134 (e.g., using an X2 interface). The backhaul link 134 may be wired or wireless.
[0032] The base station 102 may communicate wirelessly with one or more UEs 104. Each of the base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved B node (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth per carrier allocated in carrier aggregation for up to Yx MHz (e.g., for x component carriers) in total for transmission in the DL and / or UL direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
[0033] In another example, some UEs (e.g., UEs 104-a and 104-b) may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.
[0034] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.
[0035] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network. Further in this regard, the UE 104-a, 104-b may use a portion of the frequencies in the 5 GHz unlicensed spectrum to communicate with the small cell 102', to communicate with other cells, to communicate with each other using side link communications, and the like. The UE 104-a, 104-b, the small cell 102', and other cells may also use other unlicensed spectrum, such as a portion of the frequencies in the 60 GHz unlicensed spectrum.
[0036] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to frequencies of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using the mmW / near mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 can use beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distance. The base station 102 mentioned in this article can include a gNB 180.
[0037] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.
[0038] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 may be a control node that handles signaling between UE 104 and 5GC 190. Generally speaking, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be delivered through UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.
[0039] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable terminology. Base station 102 provides an access point for UE 104 to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicles / vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), gas pumps, large or small kitchen appliances, medical / health care equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include machine type communication (MTC) / enhanced MTC (eMTC, also referred to as Category (CAT)-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
[0040] In one example, in a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.), including the base station 102 described above and further herein, may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.
[0041] The aggregated base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The aggregated base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0042] Base station type operations or network designs may take into account the aggregated nature of base station functions. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network architecture sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functions over two or more units at different physical locations, and distributing functions virtually for at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0043] In one example, UE 104-a may synchronize timing with a satellite system 198, which may include a GNSS. For example, UE 104-a may include an RSU, an OBU, etc. In one example, UE 104-b may not be able to synchronize with satellite system 198 (e.g., based on the area in which UE 104-b is located), but UE 104-b may be able to communicate with UE 104-a. Thus, for example, communication component 242 may send SLSS to UE 104-b. In this example, UE 104-b may receive SLSS (e.g., via its own communication component 242) and may synchronize timing based on SLSS. As described above and further herein, communication component 242 may send (or receive) SLSS on resources defined for SLSS without enabling SLSS configuration in a wireless communication system (e.g., in LTE V2X), which may prevent inconsistent logical time slot index calculations in UEs that support SLSS and do not support SLSS. Furthermore, in one example, communicating component 242 can transmit the SA to reserve resources for transmitting (or receiving) SLSS, thereby preventing UEs that do not support SLSS from using these resources for data communications.
[0044] Now turn to Figures 2 to 5 , various aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, where aspects in dashed lines may be optional. Figure 3 The operations described in the description are presented in a particular order and / or as being performed by example components, but it should be understood that the order of actions and the components performing the actions may vary depending on the specific implementation. In addition, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or any other combination of hardware components and / or software components capable of performing the described actions or functions.
[0045] refer to Figure 2 , an example of a specific implementation of the UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 in communication via one or more buses 244 and a transceiver 202, which may operate in conjunction with a modem 240 and / or a communication component 242 for prioritizing particular types of communications, as described herein.
[0046] In one aspect, the one or more processors 212 may include the modem 240 and / or may be part of the modem 240 using one or more modem processors. Thus, various functions associated with the communication component 242 may be included in the modem 240 and / or the processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 202. In other aspects, some of the features of the one or more processors 212 and / or the modem 240 associated with the communication component 242 may be performed by the transceiver 202.
[0047] In addition, the memory 216 can be configured to store data used herein and / or local versions of the applications 275 or the communication component 242 and / or one or more subcomponents executed by the at least one processor 212. The memory 216 may include any type of computer-readable medium usable by a computer or the at least one processor 212, such as random access memory (RAM), read-only memory (ROM), tape, disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. For example, in one aspect, when the UE 104 is operating the at least one processor 212 to execute the communication component 242 and / or one or more of its subcomponents, the memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes and / or data associated therewith that define the communication component 242 and / or one or more of its subcomponents.
[0048] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware and / or software that can be executed by a processor for receiving data, the code includes instructions and is stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive signals sent by at least one base station 102 or a SL transmitting UE. Additionally, the receiver 206 may process such received signals and may also obtain measurements of these signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 208 may include hardware and / or software that can be executed by a processor for sending data, the code includes instructions and is stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include, but are not limited to, an RF transmitter.
[0049] In addition, in an aspect, the UE 104 may include an RF front end 288 that may operate in communication with the one or more antennas 265 and the transceiver 202 for receiving and sending radio transmissions, such as receiving wireless communications sent by at least one base station 102 or SL-transmitting UE, sending wireless communications to at least one base station 102 or SL-receiving UE, etc. The RF front end 288 may be connected to the one or more antennas 265 and may include one or more low noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for sending and receiving RF signals.
[0050] In one aspect, the LNAs 290 can amplify the received signal at a desired output level. In one aspect, each LNA 290 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.
[0051] Additionally, for example, the RF front end 288 can use one or more PAs 298 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 298 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.
[0052] In addition, for example, the RF front end 288 can use one or more filters 296 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, the output from the corresponding PA 298 can be filtered using a corresponding filter 296 to produce an output signal for transmission. In one aspect, each filter 296 can be connected to a specific LNA 290 and / or PA 298. In one aspect, the RF front end 288 can use one or more switches 292 to select a transmit path or a receive path using a specified filter 296, LNA 290, and / or PA 298 based on a configuration as specified by the transceiver 202 and / or the processor 212.
[0053] Thus, the transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via the RF front end 288. In one aspect, the transceiver may be tuned to operate at a specified frequency so that the UE 104 may communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102, one or more other UEs in SL communication, etc. In one aspect, for example, the modem 240 may configure the transceiver 202 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 240.
[0054] In one aspect, the modem 240 can be a multi-band multi-mode modem that can process digital data and communicate with the transceiver 202 so that the digital data is transmitted and received using the transceiver 202. In one aspect, the modem 240 can be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 240 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 240 can control one or more components (e.g., RF front end 288, transceiver 202) of the UE 104 to enable the sending and / or receiving of signals from the network based on the specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration can be based on the UE configuration information associated with the UE 104 provided by the network during cell selection and / or cell reselection.
[0055] In an aspect, communication component 242 can optionally include a SLSS configuration component 252 for configuring resources for communicating a SLSS and / or a SLSS component 254 for communicating (eg, sending or receiving) a SLSS, as described herein.
[0056] In one aspect, processor 212 may correspond to combining Figure 5 Similarly, the memory 216 may correspond to one or more processors in conjunction with the UE described in the embodiment of the present invention. Figure 5 The memory described by the UE in.
[0057] Figure 3 A flowchart illustrating an example of a method 300 for communicating SLSS. In one example, a UE (eg, UE 104-a, UE 104-b) that may include an RSU, an OBU, etc. in SL communication may use Figure 1 and Figure 2 One or more of the components described in the method 300 may be used to perform the functions described in the method 300.
[0058] In the method 300, at block 302, resources in a plurality of consecutive time slots including the one or more time slots may be configured for communicating SLSS while maintaining a logical numbering of the one or more time slots. In one aspect, the SLSS configuration component 252 (e.g., in conjunction with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may configure resources in the one or more time slots for communicating SLSS while maintaining a logical numbering of the plurality of consecutive time slots including the one or more time slots. For example, the SLSS configuration component 252 may configure the resources as one or more periodic resources, such as at a time slot occurring every N milliseconds, where N may be a positive integer.
[0059] In one example, the SLSS configuration component 252 may configure two or three resources for a time period that is a multiple of 100 milliseconds or 160 milliseconds in duration. For example, the SLSS configuration component 252 may configure 2 resources every N=160ms (or a multiple of 160ms). In one example, the SLSS configuration component 252 may configure the resources as two resources at 0, 80 modulo 160. For example, the SLSS configuration component 252 may configure the SLSS to communicate (e.g., receive or transmit) in a time slot corresponding to the start time slot 0 and one or more other time slots corresponding to 0 or 80 modulo 160.
[0060] In another example, the SLSS configuration component 252 can configure 2 resources every N=100 ms (or multiples of 100 ms). In one example, the SLSS configuration component 252 can configure the resources as two resources at 0, 50 modulo 100. For example, the SLSS configuration component 252 can configure the SLSS to communicate (e.g., receive or transmit) in a time slot corresponding to the start time slot 0 and one or more other time slots corresponding to 0 or 50 modulo 100.
[0061] In one example, the SLSS configuration component 252 may select a time slot for communicating the SLSS based on parameters such as the above parameters that may be specified in the wireless communication technology (e.g., in the LTE V2X specification or standard), and the communication component 242 may therefore not change the numbering of the time slots because the SLSS resources may be fixed in the specification.
[0062] In the method 300, optionally at block 304, a SLSS may be sent to one or more nodes during at least one of the one or more time slots. In one aspect, the SLSS component 254 (e.g., in conjunction with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may send the SLSS to the one or more nodes during at least one of the one or more time slots. In one example, the RSU may send the SLSS in the configured time slots, and the OBU may not send the SLSS in the configured time slots. In this example, the UE 104-a may include or be included in the RSU that sends the SLSS to one or more nodes (e.g., one or more OBUs or RSUs) in at least one time slot.
[0063] In another example, the OBU may send SLSS in a configured time slot (or at least a portion thereof). In one example, once the OBU is synchronized with the SLSS received from the RSU, the OBU may also send SLSS in a configured time slot (or at least a portion thereof). In this example, the UE 104-a may include or be included in an OBU that is synchronized with a first SLSS and sends a second SLSS in at least one time slot. In one example, the OBU may send SLSS at a reduced intensity, which may include reduced power or reduced time slot periodicity. For example, the SLSS component 254 in the OBU may send SLSS in 0 to 160 modulo time slots, and the RSU may send SLSS in 0 and 80 to 160 modulo time slots. In any case, for example, sending SLSS may create more RSSI in at least one resource, which may prevent UEs (e.g., OBUs) that do not support SLSS from using the at least one resource for data communication. In another example, a UE (eg, an OBU) that does not support SLSS may perform an over-the-air software update to avoid transmitting on time slots reserved for SLSS (eg, as defined in the LTE V2X specification, as described above).
[0064] In the method 300, optionally at block 306, a SLSS may be received from a node during at least one of the one or more time slots. In one aspect, the SLSS component 254 (e.g., in conjunction with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may receive the SLSS from the node during at least one of the one or more time slots. For example, the UE 104-a may be an OBU that receives the SLSS from the RSU or from another OBU in at least one time slot. In one example, as the SLSS is transmitted at a defined time or time slot, the OBU receiving the SLSS may synchronize the time (or frequency) of its transceiver based on the SLSS.
[0065] In the method 300, at least one of the timing or frequency of the transceiver may be synchronized based on receiving the SLSS, optionally at block 308. In one aspect, the SLSS component 254 (e.g., in conjunction with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may synchronize at least one of the timing or frequency of the transceiver 202 based on receiving the SLSS. For example, the SLSS component 254 may synchronize the timing of the transceiver 202 to match the timing of the received SLSS or a time specified in the SLSS, etc.
[0066] In the method 300, optionally at block 310, a second SLSS may be sent to one or more nodes based on synchronization and during at least a second time slot in the one or more time slots. In one aspect, the SLSS component 254 (e.g., in conjunction with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may send the second SLSS to one or more nodes (e.g., to one or more OBUs) based on synchronization (e.g., at block 308) and during at least a second time slot in the one or more time slots (e.g., a next time slot configured for SLSS communication). The one or more nodes may similarly synchronize and / or send additional SLSSs based on the SLSS in accordance with aspects previously described.
[0067] In method 300, optionally at box 312, SA without data may be sent to at least reserve resources in one or more time slots for communicating SLSS. On the one hand, SLSS configuration component 252 (e.g., in conjunction with processor 212, memory 216, transceiver 202, communication component 242, etc.) may send SA without data to at least reserve resources in one or more time slots for communicating SLSS. For example, SLSS configuration component 252 may send SA in a side link channel (such as PSCCH, PSSCH, etc.) that may be received by other UEs (e.g., OBUs). In this example, OBUs that do not support SLSS may receive the SA and may avoid using the resources indicated in the SA for data communication. Therefore, OBUs that support SLSS, RSU, etc. may send SLSS on resources without interference, and do not interfere with the communication of OBUs that do not support SLSS. When individual RSSI sorting may not be enough, this may help release resources for SLSS from OBUs that do not support SLSS. In another aspect, SLSS configuring component 252 can send SAs without data in the first 2 RBs of a slot to reserve SLSS slots, and devices not supporting SLSS can refrain from using these slots for data communications based on SAs, as described.
[0068] In one example, the SLSS periodicity may be set to 100 or 200 milliseconds to support this functionality, since the P_rsvp in the SA may be limited to 20, 50, 100, 200, 300, ..., 1000. The SA content from different UEs may be the same, so it may be a single frequency network (SFN) combined at the receiver (e.g., at an OBU that does not support SLSS). Thus, for example, the periodicity of the resources used to communicate the SLSS may be based on the periodicity of the SA. In one example, not all UEs need to transmit the SA, and transmitting the SA may be based on periodicity, timer (timer expiration maintained by the SLSS configuration component 252), probability, etc. Thus, for example, the SLSS configuration component 252 may send the SA based on the periodicity, timer, probability, etc., the presence or parameters of which may be indicated in the LTE V2X specification and configured by the RSU or other devices in the SL communication to the OBU, etc. In addition, for example, a UE sending a SLSS may not send the SA at the same time, and therefore in one example, the OBU may transmit the SA instead of the RSU or more frequently than the RSU. In one example, when the SA is transmitted periodically, the SLSS configuration component 252 of the OBU may monitor which 100ms or 50ms period lacks SA coverage and choose to send the SA in such a period itself.
[0069] Figure 4 An example of resource allocation 400 for SA and SLSS transmission and reserved RBs is illustrated. For example, the SLSS configuration component 252 of the OBU may send an SA in a time slot 402, which may reserve the time slot 402 or a subsequent time slot 404 for SLSS communication by indicating one or more parameters (such as a P_rsvp indicating the periodicity of the reserved resources). An OBU receiving an SA that does not support SLSS may avoid data transmission in the time slot 402 and / or time slot 404 based on the SA indicating the reserved time slots or corresponding reserved resources (RBs) in the time slot 402 and / or time slot 404 (and / or subsequent time slots based on periodicity). In addition, for example, the SLSS component 254 of the RSU (and / or a different OBU) may send an SLSS in the time slot 402 and / or send another SLSS in the reserved RB in the time slot 404. In yet another example, the SLSS component 254 of the OBU that sends the SA in the time slot 404 may send the SLSS in the reserved RB of the time slot 402. Furthermore, in various examples, one or more OBUs (or RSUs) supporting SLSS communication may receive the SLSS transmitted in time slot 402 and may synchronize timing based on the received SLSS, as described.
[0070] In one specific example, N=100ms, and within each N, 2 resources may be designated for SLSS communication, such as at 0, 50 modulo 100. The SLSS configuration component 252 of the OBU may send an SA reserving 20 resource blocks (RBs) (e.g., 2 subchannels) starting from RB 40. The SLSS signal that may be sent by a different OBU or RSU may start from RB 47 and end at RB 52. Thus, for example, the SA may reserve a larger set of resources including resources configured for communicating SLSS in one or more time slots. In one example, P_rsvp may be 50 or 100. In the case of P_rsvp=50, there may be a single reservation chain for reserving resources in time slots with logical time slot indices 0, 50, 100, 150, etc. (which may each be 50ms apart). In another example, where P_rsvp=100, there may be 2 reservation chains; one for reserving resources in time slots with logical slot indices 0, 100, 200, etc. (which may be 100ms apart each); and one for reserving resources in time slots with logical slot indices 50, 150, 250, etc. For example, the RSU may not send an SA to reserve a SLSS subchannel. In one example, the SLSS component 254 of the OBU may send an SA to reserve a SLSS subchannel with a periodicity of 1000ms. In this example, at a given time, approximately ten percent of the OBUs may send SAs to reserve a SLSS subchannel. For example, the SLSS configuration component 252 of a given OBU may monitor and detect that there are SAs from other OBUs at time slots with logical slot indices 0, 50, 100, 150, etc., but not in time slot 750. In this example, based on the detection and the 1000 ms periodicity (which may be indicated in the LTE V2X specification or otherwise configured to the OBU), the SLSS configuration component 252 may send SAs reserving SLSS at time slots having logical time slot indices 750, 1750, 2750, etc. (which may be 1000 ms apart).
[0071] Figure 5 1 is a block diagram of a MIMO communication system 500 including UEs 104-a, 104-b. The MIMO communication system 500 may be exemplified with reference to Figure 1 1. The wireless communication access network 100 described herein may include aspects of the wireless communication access network 100. The UE 104-a may be a reference Figure 1 and Figure 3Examples of various aspects of UE 104 are described. UE 104-a may be equipped with antennas 534 and 535, and UE 104-b may be equipped with antennas 552 and 553. In a MIMO communication system 500, UEs 104-a, 104-b may be able to transmit data simultaneously over multiple communication links. Each communication link may be referred to as a "layer", and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system in which UE 104-a transmits two "layers", the rank of the communication link between UE 104-a and UE 104-b is two.
[0072] At UE 104-a, a transmit (Tx) processor 520 may receive data from a data source. The transmit processor 520 may process the data. The transmit processor 520 may also generate control symbols or reference symbols. The transmit MIMO processor 530 may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols (if applicable), and may provide output symbol streams to transmit modulators / demodulators 532 and 533. Each modulator / demodulator 532 to 533 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 532 to 533 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signals from modulators / demodulators 532 and 533 may be transmitted via antennas 534 and 535, respectively.
[0073] UE 104-b may be a reference Figure 1 and 3 Examples of various aspects of UE 104 are described. At UE 104-b, UE antennas 552 and 553 may receive signals from UE 104-a (e.g., via a side link) and may provide received signals to modulators / demodulators 554 and 555, respectively. Each modulator / demodulator 554 to 555 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each modulator / demodulator 554 to 555 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 556 may obtain received symbols from modulators / demodulators 554 and 555, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive (Rx) processor 558 may process (eg, demodulate, deinterleave, and decode) the detected symbols to provide decoded data for the UE 104 - b to a data output and provide decoded control information to a processor 580 or memory 582 .
[0074] At UE 104-b, a transmit processor 564 may receive and process data from a data source. The transmit processor 564 may also generate reference symbols for reference signals. The symbols from the transmit processor 564 may be pre-decoded by a transmit MIMO processor 566 (if applicable), further processed by modulators / demodulators 554 and 555 (e.g., corresponding to SC-FDMA, etc.), and sent to UE 104-a according to the communication parameters received from UE 104-a. At UE 104-a, signals from UE 104-b may be received by antennas 534 and 535, processed by modulators / demodulators 532 and 533, detected by a MIMO detector 536 (if applicable), and further processed by a receive processor 538. The receive processor 538 may provide decoded data to a data output terminal and a processor 540 or a memory 542.
[0075] In some cases, processors 540 and / or 580 may execute stored instructions to instantiate communication component 242 (eg, see Figure 1 and Figure 3 ).
[0076] The components of UE 104-a, 104-b may be implemented, individually or in the aggregate, using one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the indicated modules may be a means for performing one or more functions associated with the operation of the MIMO communication system 500. Similarly, the components of UE 104-a may be implemented, individually or in the aggregate, using one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the indicated components may be a means for performing one or more functions associated with the operation of the MIMO communication system 500.
[0077] The following aspects are merely illustrative, and aspects thereof may be combined with aspects of other embodiments or teachings described herein without limitation.
[0078] Aspect 1 is a method for wireless communication, the method comprising: configuring resources in one or more time slots for communicating SLSS while maintaining logical numbering of a plurality of consecutive time slots including the one or more time slots; and at least one of the following operations: receiving SLSS from a node during at least one time slot of the one or more time slots; or sending SLSS to one or more nodes during at least one time slot of the one or more time slots.
[0079] In aspect 2, the aspect of claim 1 includes, based on receiving the SLSS from the node, synchronizing at least one of a timing or a frequency of a transceiver based on the SLSS.
[0080] In aspect 3, the method according to aspect 2 includes, in accordance with synchronizing at least one of the timing or the frequency of the transceiver based on the SLSS, sending a second SLSS to one or more nodes during at least a second time slot of the one or more time slots.
[0081] In aspect 4, the method according to any one of aspects 1 to 3 includes, wherein the resources include two or three resources in a time period having a duration that is a multiple of 100 milliseconds or 160 milliseconds.
[0082] In aspect 5, the method according to any one of aspects 1 to 4 includes sending a SA without data to reserve at least the resources in the one or more time slots for communicating the SLSS.
[0083] In aspect 6, the method according to aspect 5 includes sending the SA based on at least one of periodicity or timer expiration or probability.
[0084] In aspect 7, the method according to any one of aspects 5 or 6 includes, wherein the periodicity of the resource is based on the periodicity of the SA.
[0085] In aspect 8, the method according to any one of aspects 5 to 7 includes, wherein sending the SA is based at least in part on determining that another UE did not send another SA within the one or more time slots.
[0086] In aspect 9, the method according to any one of aspects 5 to 8 includes, wherein the SA reserves a larger set of resources in the one or more time slots including the resources configured for communicating the SLSS.
[0087] Aspect 10 is a device for wireless communication, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors, the one or more processors being communicatively coupled to the memory and the transceiver, wherein the one or more processors are configured to execute the instructions so that the device performs one or more of the methods described in any one of Aspects 1 to 9.
[0088] Aspect 11 is an apparatus for wireless communication, the apparatus comprising means for performing one or more of the methods according to any one of aspects 1 to 9.
[0089] Aspect 12 is a computer-readable medium comprising code executable by one or more processors for wireless communication, the code comprising code for performing one or more of the methods according to any one of aspects 1 to 9.
[0090] The above specific embodiments described above in conjunction with the accompanying drawings describe examples and do not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" used in this specification means "used as an example, instance, or illustration", rather than "preferred" or "advantageous over other examples". The specific embodiments include specific details for providing an understanding of the technology. However, these technologies can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.
[0091] Information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, computer executable codes or instructions stored on computer-readable media, or any combination thereof.
[0092] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a specially programmed device, such as, but not limited to, a processor designed to perform the functions described herein, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The specially programmed processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.
[0093] The functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, these functions may be stored as one or more instructions or codes on a non-transient computer-readable medium or sent via a non-transient computer-readable medium. Other examples and specific implementations fall within the scope and essence of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software, hardware, hard wiring, or any combination of these items executed by a specially programmed processor. The features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, the phrase "or" is intended to represent an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly visible from the context, for example, the phrase "X adopts A or B" is intended to represent any one of the natural inclusive arrangements. That is, for example, any of the following examples satisfies the phrase "X adopts A or B": X adopts A; X adopts B; or X adopts both A and B. Additionally, as used herein, including in the claims, “or” as used in a list of items ending with “at least one of” indicates a disjunctive list, so that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (A and B and C).
[0094] Computer-readable medium includes both computer storage medium and communication medium, and this communication medium includes any medium that promotes computer program to be transferred from one place to another place.Storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device or can be used for carrying or storing expected program code member and any other medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0095] The previous description of the present disclosure is provided to enable those skilled in the art to implement or use the present disclosure. It will be apparent to those skilled in the art that various modifications to the present disclosure will be apparent, and the common principles defined herein may be applied to other variations without departing from the essence or scope of the present disclosure. In addition, although the elements of the described aspects and / or embodiments are described or claimed in the singular, the plural form may also be envisioned unless explicitly stated to be limited to the singular. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used together with all or part of any other aspect and / or embodiment. Thus, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A device for wireless communication, the device comprising: Transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: configuring resources in a plurality of consecutive time slots including the one or more time slots for communicating a side link synchronization signal (SLSS) while maintaining a logical numbering of the one or more time slots; and At least one of the following: receiving a SLSS from a node during at least one time slot of the one or more time slots; or The SLSS is transmitted to one or more nodes during at least one time slot of the one or more time slots.
2. The apparatus of claim 1, wherein the one or more processors are further configured to synchronize at least one of a timing or a frequency of a transceiver based on the SLSS based on receiving the SLSS from the node.
3. The apparatus of claim 2, wherein the one or more processors are further configured to send a second SLSS to one or more nodes during at least a second time slot of the one or more time slots based on synchronizing at least one of the timing or the frequency of the transceiver based on the SLSS. 4 . The apparatus of claim 1 , wherein the resource comprises two or three resources within a time period having a duration that is a multiple of 100 milliseconds or 160 milliseconds.
5. The apparatus of claim 1, wherein the one or more processors are further configured to send a scheduling assignment (SA) without data to reserve at least the resources in the one or more time slots for communicating the SLSS. 6 . The apparatus of claim 5 , wherein the one or more processors are configured to send the SA based on at least one of periodicity or timer expiration or probability. The apparatus of claim 5 , wherein a periodicity of the resource is based on a periodicity of the SA.
8. The apparatus of claim 5, wherein the one or more processors are configured to transmit the SA based at least in part on determining that another UE did not transmit another SA within the one or more time slots.
9. The apparatus of claim 5, wherein the SA reserves a larger set of resources in the one or more time slots including the resources configured for communicating the SLSS.
10. A method for wireless communication, the method comprising: configuring resources in a plurality of consecutive time slots including the one or more time slots for communicating a side link synchronization signal (SLSS) while maintaining a logical numbering of the one or more time slots; and At least one of the following: receiving a SLSS from a node during at least one time slot of the one or more time slots; or The SLSS is transmitted to one or more nodes during at least one time slot of the one or more time slots.
11. The method of claim 10, further comprising synchronizing at least one of a timing or a frequency of a transceiver based on the SLSS based on receiving the SLSS from the node.
12. The method of claim 11, further comprising transmitting a second SLSS to one or more nodes during at least a second time slot of the one or more time slots in accordance with synchronizing at least one of the timing or the frequency of the transceiver based on the SLSS.
13. The method of claim 10, wherein the resource comprises two or three resources within a time period having a duration that is a multiple of 100 milliseconds or 160 milliseconds.
14. The method of claim 10, further comprising sending a Scheduling Assignment (SA) without data to reserve at least the resources in the one or more time slots for communicating the SLSS.
15. The method of claim 14, wherein sending the SA is based on at least one of periodicity or timer expiration or probability. The method of claim 14 , wherein the periodicity of the resource is based on the periodicity of the SA.
17. The method of claim 14, wherein sending the SA is based at least in part on determining that another UE did not send another SA within the one or more time slots.
18. The method of claim 14, wherein the SA reserves a larger set of resources in the one or more time slots including the resources configured for communicating the SLSS.
19. An apparatus for wireless communication, the apparatus comprising: means for configuring resources in a plurality of consecutive time slots including the one or more time slots for communicating a side link synchronization signal (SLSS) while maintaining a logical numbering of the one or more time slots; as well as At least one of the following: means for receiving a SLSS from a node during at least one of the one or more time slots; or Means for transmitting the SLSS to one or more nodes during at least one of the one or more time slots.
20. The apparatus of claim 19, further comprising means for synchronizing at least one of timing or frequency of a transceiver based on the SLSS based on receiving the SLSS from the node.
21. The apparatus of claim 20, further comprising means for transmitting a second SLSS to one or more nodes during at least a second time slot of the one or more time slots in accordance with synchronizing at least one of the timing or the frequency of the transceiver based on the SLSS.
22. The apparatus of claim 19, wherein the resource comprises two or three resources within a time period having a duration that is a multiple of 100 milliseconds or 160 milliseconds.
23. The apparatus of claim 19, further comprising means for sending a scheduling assignment (SA) without data to reserve at least the resources in the one or more time slots for communicating the SLSS.
24. The apparatus of claim 23, wherein the means for sending the SA sends the SA based on at least one of periodicity or timer expiration or probability.
25. A computer-readable medium comprising code executable by one or more processors for wireless communication, the code comprising: code for configuring resources in a plurality of consecutive time slots including the one or more time slots for communicating a side link synchronization signal (SLSS) while maintaining a logical numbering of the one or more time slots; as well as At least one of the following codes: code for receiving a SLSS from a node during at least one of the one or more time slots; or Code for transmitting the SLSS to one or more nodes during at least one of the one or more time slots.
26. The computer-readable medium of claim 25, further comprising code for synchronizing at least one of timing or frequency of a transceiver based on the SLSS based on receiving the SLSS from the node.
27. The computer-readable medium of claim 26, further comprising code for transmitting a second SLSS to one or more nodes during at least a second time slot of the one or more time slots in accordance with synchronizing at least one of the timing or the frequency of the transceiver based on the SLSS.
28. The computer-readable medium of claim 25, wherein the resources include two or three resources within a time period having a duration that is a multiple of 100 milliseconds or 160 milliseconds.
29. The computer-readable medium of claim 25, further comprising code for sending a scheduling assignment (SA) without data to reserve at least the resources in the one or more time slots for communicating the SLSS.
30. The computer-readable medium of claim 29, wherein the code for sending the SA sends the SA based on at least one of periodicity or timer expiration or probability.
