Demodulation reference signal sequence for sidelink communication

Abstract

Various aspects relate to a demodulation reference signal (DMRS) in a sidelink wireless communication network. In some examples, a sidelink device generates a DMRS based on a first and a second identifier of the sidelink device. In some examples, the sidelink device generates a DMRS based on an initialization parameter and / or at least one scaling parameter. In some examples, the initialization parameter may be based on a first identifier of the sidelink device. In some examples, at least one scaling parameter may be based on a second identifier of the sidelink device. In some examples, a first sidelink device synchronizes with a second sidelink device based on broadcast channel information obtained by decoding a received broadcast signal using DMRS information. In some examples, the DMRS information may be based on a first identifier and a second identifier of the first sidelink device.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to and the benefit of co-pending nonprovisional application No. 17 / 174,088 filed in the U.S. Patent and Trademark Office on February 11, 2021, and provisional application No. 62 / 977,071 filed in the U.S. Patent and Trademark Office on February 14, 2020, which are assigned to the assignee thereof, and are hereby expressly incorporated herein by reference as if fully set forth below in their entirety and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication networks, and more particularly to generating and using demodulation reference signal (DMRS) sequences for sidelink communications. Background Art

[0004] In many existing wireless communication systems, cellular networks are implemented by enabling wireless user devices to communicate with each other through signaling with nearby base stations or cells. As user devices move across a service area, handover occurs so that each user device maintains communication with each other through its corresponding cell.

[0005] Another approach to wireless communication systems is a mesh or peer-to-peer (P2P) network, where wireless user devices can send signals directly to each other, rather than through an intermediate base station or cell. In between these approaches are systems configured for sidelink signaling. Using sidelink signaling, wireless user devices communicate in a cellular system, typically under the control of a base station. However, wireless user devices are also configured to perform sidelink signaling directly between user devices, without the need for transmission through a base station.

[0006] An example of a sidelink wireless communication system is a vehicle-to-everything (V2X) communication system. V2X communication involves the exchange of information not only between vehicles themselves, but also between vehicles and external systems, such as street lights, buildings, pedestrians, and wireless communication networks. V2X systems enable vehicles to obtain information related to weather, nearby accidents, road conditions, activities of nearby vehicles and pedestrians, objects near the vehicle, and other relevant information that can be used to improve the vehicle driving experience, increase vehicle safety, and support autonomous vehicles. Summary of the invention

[0007] An overview of one or more aspects of the present invention is presented below in order to provide a basic understanding of these aspects. This overview is not an extensive overview of all expected features of the present invention, and is neither intended to identify the key or critical elements of all aspects of the present disclosure, nor is it intended to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in some form as a prelude to a more detailed description presented later.

[0008] In some examples, the present invention provides a first side link device, including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to determine at least one of an initialization parameter based on at least a first side link identifier of the first side link device, at least one scaling parameter based on at least a second side link identifier of the first side link device, or a combination thereof. The processor and the memory may also be configured to generate a demodulation reference signal (DMRS) using at least one of the initialization parameter, the at least one scaling parameter, or a combination thereof. The processor and the memory may also be configured to send the DMRS to the second side link device.

[0009] In some examples, the present invention provides a method for wireless communication at a first side link device. The method may include determining at least one of an initialization parameter based on at least a first side link identifier of the first side link device, at least one scaling parameter based on at least a second side link identifier of the first side link device, or a combination thereof. The method may also include generating a demodulation reference signal (DMRS) using at least one of the initialization parameter, the at least one scaling parameter, or a combination thereof. The method may also include sending the DMRS to the second side link device.

[0010] In some examples, the present invention provides a first side link device. The first side link device may include a device for determining at least one of an initialization parameter based on at least a first side link identifier of the first side link device, at least one scaling parameter based on at least a second side link identifier of the first side link device, or a combination thereof. The first side link device may also include a device for generating a demodulation reference signal (DMRS) using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. The first side link device may also include a device for sending the DMRS to the second side link device.

[0011] In some examples, the present invention provides an article for use with a first side link device. The article may include a computer-readable medium storing therein instructions executable by one or more processors of the first side link device to determine at least one of an initialization parameter based on a first side link identifier of the first side link device, at least one scaling parameter based on a second side link identifier of the first side link device, or a combination thereof. The computer-readable medium may also store therein instructions executable by one or more processors of the first side link device to generate a demodulation reference signal (DMRS) using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. The computer-readable medium may also store therein instructions executable by one or more processors of the first side link device to send the DMRS to the second side link device.

[0012] In some examples, the present disclosure provides a first side link device, including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to: receive a broadcast signal from a second side link device, and determine at least one of an initialization parameter based on at least a first side link identifier of the second side link device, at least one scaling parameter based on at least a second side link identifier of the second side link device, or a combination thereof. The processor and the memory may be configured to: determine demodulation reference signal (DMRS) information using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. The processor and the memory may be configured to: decode the broadcast signal using the DMRS information to obtain broadcast channel information, and synchronize with the second side link device using the broadcast channel information.

[0013] In some examples, the present disclosure provides a method for wireless communication at a first side link device. The method may include receiving a broadcast signal from a second side link device and determining at least one of an initialization parameter based at least on a first side link identifier of the second side link device, at least one scaling parameter based at least on a second side link identifier of the second side link device, or a combination thereof. The method may also include determining demodulation reference signal (DMRS) information using at least one of the initialization parameter, the at least one scaling parameter, or a combination thereof. The method may also include decoding the broadcast signal using the DMRS information to obtain broadcast channel information, and synchronizing with the second side link device using the broadcast channel information.

[0014] In some examples, the present disclosure provides a first side link device. The first side link device may include a device for receiving a broadcast signal from a second side link device, and a device for determining at least one of an initialization parameter based on at least a first side link identifier of the second side link device, at least one scaling parameter based on at least a second side link identifier of the second side link device, or a combination thereof. The first side link device may also include a device for determining demodulation reference signal (DMRS) information using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. The first side link device may also include a device for decoding the broadcast signal using the DMRS information to obtain broadcast channel information, and a device for synchronizing with the second side link device using the broadcast channel information.

[0015] In some examples, the present disclosure provides an article of manufacture for use with a first side link device. The article of manufacture may include a computer-readable medium in which instructions executable by one or more processors of the first side link device may be stored to receive a broadcast signal from a second side link device and determine at least one of an initialization parameter based on at least a first side link identifier of the second side link device, at least one scaling parameter based on at least a second side link identifier of the second side link device, or a combination thereof. The computer-readable medium may also store therein instructions executable by one or more processors of the first side link device to determine demodulation reference signal (DMRS) information using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. The computer-readable medium may also store therein instructions executable by one or more processors of the first side link device to decode the broadcast signal using the DMRS information to obtain broadcast channel information, and synchronize with the second side link device using the broadcast channel information.

[0016] These and other aspects of the present disclosure will become more fully understood after reading the detailed description below. When reading the following description of the specific examples of the present disclosure in conjunction with the accompanying drawings, other aspects, features and examples of the present disclosure will become apparent to those of ordinary skill in the art. Although the features of the present disclosure can be discussed with respect to some of the following examples and drawings, all examples of the present disclosure can include one or more advantageous features discussed herein. In other words, although one or more examples can be discussed as having certain advantageous features, one or more of these features can also be used according to the various examples of the present disclosure discussed herein. In a similar manner, although examples can be discussed below as device, system or method examples, it should be understood that such examples can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a conceptual illustration of an example of a wireless radio access network in accordance with some aspects.

[0018] Figure 2 is a conceptual illustration of an example of a wireless communication network configured to support D2D or sidelink communications in accordance with some aspects.

[0019] Figure 3 is a diagram illustrating an example of a wireless communication network for facilitating both cellular and sidelink communications in accordance with some aspects.

[0020] Figure 4 is a diagram illustrating organization of wireless resources in an air interface using orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0021] Figure 5A and Figure 5BAn example of a sidelink slot structure according to some aspects is shown.

[0022] Figure 6 is a conceptual diagram of a side link synchronization signal block according to some aspects.

[0023] Figure 7 is a conceptual diagram of an example of synchronization in a sidelink wireless communication network in accordance with some aspects.

[0024] Figure 8 is a block diagram illustrating an example of a sidelink communication circuit according to some aspects.

[0025] Fig. 9 is a block diagram illustrating an example of a sidelink communication circuit according to some aspects.

[0026] Fig.10 is a block diagram illustrating an example of a sidelink communication circuit according to some aspects.

[0027] Fig.11 is a block diagram illustrating an example of a sidelink communication circuit according to some aspects.

[0028] Fig.12 is a diagram illustrating an example of a hardware implementation for a sidelink device employing a processing system according to some aspects.

[0029] Fig.13 is a flow chart illustrating an example of a method for providing a demodulation reference signal (DMRS) according to some aspects.

[0030] Fig.14 is a flow chart illustrating an example of a method for providing DMRS according to some aspects.

[0031] Fig.15 is a diagram illustrating an example of a hardware implementation for a sidelink device employing a processing system according to some aspects.

[0032] Fig.16 is a flow chart illustrating an example of a synchronization method for wireless communications over a sidelink carrier in accordance with some aspects.

[0033] Fig.17 is a flow chart illustrating an example of a synchronization method for wireless communications over a sidelink carrier in accordance with some aspects.

[0034] Fig.18 is a flow chart illustrating an example of a method for deriving a sidelink identifier according to some aspects.

[0035] Fig.19 is a flow chart illustrating an example of a method for wireless communications over a sidelink carrier in accordance with some aspects. DETAILED DESCRIPTION

[0036] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid confusing these concepts. In addition, well-known elements will not be described in detail or will be omitted to avoid confusing the relevant details of the present disclosure.

[0037] Although various aspects and examples are described in this application by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses may be implemented by integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI-enabled), etc.). Although some examples may or may not be specifically targeted at use cases or applications, various applicability of the described innovations may occur. The implementation may range from chip-level or modular components to non-modular, non-chip-level implementations to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include many components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summing, etc.). It is intended that the innovations described herein can be practiced in devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, end-user devices, etc.

[0038] Various aspects of the present disclosure relate to sidelink wireless communications. In some examples, a first sidelink device generates a demodulation reference signal (DMRS) based on a first identifier and a second identifier of the first sidelink device, and sends the DMRS to a second sidelink device. In some examples, the second sidelink device determines the first identifier and the second identifier of the first sidelink device and generates DMRS information based on these identifiers. The second sidelink device decodes a broadcast signal from the first sidelink device using the DMRS information and synchronizes with the first sidelink device based on the decoded broadcast signal.

[0039] The various concepts presented throughout this disclosure may be implemented across a variety of telecommunication systems, network architectures and communication standards. Figure 1 , as a non-limiting illustrative example, a schematic diagram of a radio access network (RAN) 100 is provided. The RAN 100 may implement any suitable wireless communication technology or technologies to provide radio access. As an example, the RAN 100 may operate in accordance with the Third Generation Partnership Project (3GPP) New Radio (NR) specifications, commonly referred to as 5G. As another example, the RAN 100 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be used within the scope of the present disclosure.

[0040] The geographical area covered by the radio access network 100 may be divided into a plurality of cellular areas (cells), which may be uniquely identified by a user equipment (UE) based on an identity broadcast over the geographical area from an access point or base station. Figure 1 Macro cells 102, 104, and 106 and small cells 108 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, each antenna being responsible for communicating with UEs in a portion of the cell.

[0041] Typically, a corresponding base station (BS) serves each cell. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission to or radio reception from a UE in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an eNode B (eNB), a gNode B (gNB), a transmit and receive point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs that may be collocated or non-collocated. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 100 operates according to both LTE and 5G NR standards, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station.

[0042] exist Figure 1, two base stations 110 and 112 are shown in cells 102 and 104; a third base station 114 is shown as controlling a remote radio head (RRH) 116 in cell 106. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH by a feeder cable. In the example shown, cells 102, 104, and 106 may be referred to as macro cells because base stations 110, 112, and 114 support cells with large sizes. In addition, base station 118 is shown in a small cell 108 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, cell 108 may be referred to as a small cell because base station 118 supports a cell with a relatively small size. The cell size may be determined based on system design and component constraints. It should be understood that the radio access network 100 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 110, 112, 114, 118 provide wireless access points to the core network for any number of mobile devices.

[0043] Figure 1 Also included is a quadcopter or drone 120, which can be configured to function as a base station 120. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile base station (such as a quadcopter or drone 120).

[0044] Typically, a base station may include a backhaul interface for communicating with a backhaul portion of the network (not shown). The backhaul may provide a link between the base station and a core network (not shown), and in some examples, the backhaul may provide interconnections between the various base stations. The core network may be part of a wireless communication system and may be independent of the radio access technology used in the radio access network. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, and the like.

[0045] RAN 100 is shown supporting wireless communications for multiple mobile devices. In the standards and specifications promulgated by the Third Generation Partnership Project (3GPP), mobile devices are generally referred to as user equipment (UE), but those skilled in the art may also refer to them as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other suitable terms. UE may be a device that provides access to network services to users.

[0046] In this document, a "mobile" device does not necessarily have the ability to move, and may be stationary. The term mobile device or mobile device refers broadly to a variety of devices and technologies. For example, some non-limiting examples of mobile devices include mobile phones, cellular phones (cell phones), smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide group of embedded systems, for example, corresponding to the "Internet of Things" (IoT). A mobile device may also be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. A mobile device may also be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. Mobile devices may also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure devices that control power (e.g., smart grids), lighting, water, etc., industrial automation and enterprise devices, logistics controllers, agricultural equipment, etc. In addition, mobile devices may provide connected medical or telemedicine support, i.e., healthcare at a distance. Telehealth devices may include remote health monitoring devices and remote health management devices, whose communications may be prioritized or given priority over other types of information, for example, in terms of priority access to critical service data transmission and / or associated QoS for critical service data transmission.

[0047] Within the RAN 100, the cells may include UEs that may communicate with one or more sectors of each cell. For example, UEs 122 and 124 may communicate with base station 110; UEs 126 and 128 may communicate with base station 112; UEs 130 and 132 may communicate with base station 114 via RRH 116; UE 134 may communicate with base station 118; and UE 136 may communicate with a mobile base station (e.g., a quadcopter or drone 120). Here, each base station 110, 112, 114, 118, and 120 may be configured to provide an access point to a core network (not shown) for all UEs in the corresponding cell. In another example, a mobile network node (e.g., a quadcopter or drone 120) may be configured to act as a UE. For example, a quadcopter or drone 120 may operate within cell 102 by communicating with base station 110.

[0048] Wireless communication between RAN 100 and UE (e.g., UE 122 or 124) can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 110) to one or more UEs (e.g., UE 122 and 124) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 110). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 122) to a base station (e.g., base station 110) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 122).

[0049] For example, DL transmission may include unicast or broadcast transmission of control information and / or traffic information (e.g., user data traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), and UL transmission may include transmission of control information and / or traffic information originating from a UE (e.g., UE 122). In addition, uplink and / or downlink control information and / or traffic information may be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or time slots may be combined together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be used, and the various time divisions of waveforms may have any suitable duration.

[0050] In order to achieve a low block error rate (BLER) for transmission over the air interface while still achieving very high data rates, channel coding can be used. That is, wireless communications can often make use of suitable error-correcting block codes. In a typical block code, an information message or sequence is divided into code blocks (CBs), and then an encoder (e.g., CODEC) at the transmitting device mathematically adds redundancy to the information message. Exploiting this redundancy in the encoded information message can improve the reliability of the message, thereby being able to correct any bit errors that may occur due to noise.

[0051] Data encoding can be implemented in a variety of ways. In early 5G NR specifications, user data was encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap for large code blocks and / or high code rates, and another basemap used in other ways. Control information and the physical broadcast channel (PBCH) are encoded using Polar coding based on nested sequences. For these channels, rate matching is performed using puncturing, shortening, and repetition.

[0052] Aspects of the present invention may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communications.

[0053] The air interface in the RAN 100 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL or reverse link transmissions from UEs 122 and 124 to base station 110 and for multiplexed DL or forward link transmissions from base station 110 to UEs 122 and 124 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexed DL transmissions from base station 110 to UEs 122 and 124 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0054] In addition, the air interface in the RAN 100 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is often used for wireless links that utilize time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, sometimes the channel is dedicated to transmission in one direction, and at other times the channel is dedicated to transmission in another direction, where the direction may change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions may operate on different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0055] In the RAN 100, the ability of UEs to communicate while moving, regardless of their location, is referred to as mobility. The various physical channels between the UE and the RAN are typically established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage the security context of the control plane and user plane functions in whole or in part. The RAN 100 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this period, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover from the serving cell to the neighboring cell or to the (target) cell. For example, UE 124 may move from a geographic area corresponding to its serving cell 102 to a geographic area corresponding to a neighboring cell 106. When the signal strength or quality from a neighboring cell 106 exceeds that of its serving cell 102 for a given amount of time, UE 124 may send a report message to its serving base station 110 to indicate this. In response, UE 124 may receive a handover command, and the UE may undergo a handover to cell 106.

[0056] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 110, 112, and 114 / 116 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 122, 124, 126, 128, 130, and 132 can receive the unified synchronization signal, derive the carrier frequency and radio frame timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 124) can be received simultaneously by two or more cells (e.g., base stations 110 and 114 / 116) within the RAN 100. Each cell can measure the strength of the pilot signal, and the RAN (e.g., one or more of base stations 110 and 114 / 116 and / or a central node within the core network) can determine the serving cell of UE 124. As the UE 124 moves through the RAN 100, the network may continue to monitor the uplink pilot signals sent by the UE 124. When the signal strength or quality of the pilot signals measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 100 may handover the UE 124 from the serving cell to the neighboring cell with or without notifying the UE 124.

[0057] Although the synchronization signals sent by base stations 110, 112, and 114 / 116 may be uniform, the synchronization signals may not identify a specific cell, but may identify a region of multiple cells operating at the same frequency and / or the same timing. The use of regions in 5G networks or other next generation communication networks may enable an uplink-based mobility framework and improve the efficiency of both the UE and the network. Efficiency may be improved because the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

[0058] In various implementations, the air interface in the RAN 100 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically through a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. While some technical rules generally still need to be followed to access unlicensed spectrum, generally, any operator or device can gain access. Shared spectrum may be somewhere between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum may provide Licensed Shared Access (LSA) to share that spectrum with other parties, e.g., with conditions for obtaining access determined by the appropriate licensee.

[0059] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication between some or all devices and apparatuses within its service area or cell. In the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduling entities. That is, for scheduled communications, a UE or scheduled entity utilizes resources allocated by the scheduling entity.

[0060] The base station is not the only entity that can act as a scheduling entity. That is, in some examples, the UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, two or more UEs (e.g., UEs 138, 140, and 142) can communicate with each other using point-to-point (P2P) or sidelink signals 137 without relaying the communication through a base station. In some examples, UEs 138, 140, and 142 can each be used as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and transmit sidelink signals 137 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 126 and 128) within the coverage area of ​​a base station (e.g., base station 112) can also transmit sidelink signals 127 via a direct link (sidelink) without transmitting the communication through base station 112. In this example, base station 112 can allocate resources to UEs 126 and 128 for sidelink communication. In either case, such sidelink signaling 127 and 137 may be implemented in a P2P network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X), a mesh network, or other suitable direct-link network.

[0061] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 112 via a D2D link (e.g., side link 127 or 137). For example, one or more UEs (e.g., UE 128) within the coverage area of ​​base station 112 may operate as relay UEs to extend the coverage of base station 112, improve transmission reliability to one or more UEs (e.g., UE 126), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0062] The two main technologies that may be used by V2X networks include dedicated short-range communications (DSRC) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11p standard and cellular V2X based on LTE and / or 5G (New Radio) standards. For convenience, various aspects of the present disclosure may refer to New Radio (NR) cellular V2X networks, referred to herein as V2X networks. However, it should be understood that the concepts disclosed herein may not be limited to a specific V2X standard or may be directed to sidelink networks other than V2X networks.

[0063] Figure 2 An example of a wireless communication network 200 configured to support D2D or sidelink communications is shown. In some examples, the sidelink communications may include V2X communications. V2X communications involve not only the wireless exchange of information directly between the vehicles (e.g., UEs in vehicles 202 and 204) themselves, but also the wireless exchange of information directly between vehicles 202 / 204 and infrastructure (e.g., roadside units (RSUs) 206), such as street lights, buildings, traffic cameras, toll booths or other stationary objects, vehicles 202 / 204 and pedestrians / cyclists 208, and vehicles 202 / 204 and wireless communication networks (e.g., base stations 210). In some examples, V2X communications may be implemented in accordance with the New Radio (NR) cellular V2X standard defined by 3GPP, Release 16, or other suitable standards.

[0064] V2X communications enable vehicles 202 and 204 to obtain information related to weather, nearby accidents, road conditions, activities of nearby vehicles and pedestrians, objects near the vehicle, and other relevant information that can be used to improve the vehicle driving experience and increase vehicle safety. For example, such V2X data can enable autonomous driving and improve road safety and traffic efficiency. For example, the V2X connected vehicles 202 and 204 can use the exchanged V2X data to provide in-vehicle collision warnings, road hazard warnings, approaching emergency vehicle warnings, pre-collision / post-collision warnings and information, emergency braking warnings, forward traffic jam warnings, lane change warnings, smart navigation services, and other similar information. In addition, in the event of an imminent danger, the V2X data received by the V2X connected mobile device of the pedestrian / cyclist 208 can be used to trigger a warning sound, vibration, flashing lights, etc.

[0065] Sidelink communications between vehicle-UEs (V-UEs) 202 and 204 or between a V-UE 202 or 204 and an RSU 206 or a pedestrian-UE (P-UE) 208 may occur over a sidelink 212 utilizing a proximity services (ProSe) PC5 interface. In various aspects of the present disclosure, the PC5 interface may also be used to support D2D sidelink 212 communications under other proximity use cases. Examples of other proximity use cases may include proximity services based on public safety or business (e.g., entertainment, education, office, medical, and / or interaction). Figure 2 In the example shown, ProSe communication may further occur between UE 214 and 216. V-UE 202 and 204, P-UE 208, and UE 214 and 216 may correspond to Figure 1 , Figure 3 , Figure 7 , Fig.12 and Fig.15 Any UE or scheduled entity shown in any one of .

[0066] ProSe communication can support different operation scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario in which UEs (e.g., V-UE 202 and 204 and P-UE 208) are outside the coverage area of ​​a base station (e.g., base station 210), but each is still configured for ProSe communication. Partial coverage refers to a scenario in which some of the UEs (e.g., V-UE 204) are outside the coverage area of ​​the base station 210, while other UEs (e.g., V-UE 202 and P-UE 208) are communicating with the base station 210. In-coverage refers to a scenario in which UEs (e.g., UE 214 and 216) communicate with the base station 210 (e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information that supports ProSe operation.

[0067] To facilitate D2D sidelink communication on sidelink 212, for example, between UE 214 and 216, UE 214 and 216 may transmit discovery signals between them. In some examples, each discovery signal may include a synchronization signal, such as a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), which facilitates device discovery and enables synchronization of communications on sidelink 212. For example, UE 216 may utilize the discovery signal to measure the signal strength and channel state of a potential sidelink (e.g., sidelink 212) with another UE (e.g., UE 214). UE 216 may utilize the measurement results to select a UE (e.g., UE 214) for sidelink communication or relay communication.

[0068] In a 5G NR sidelink, sidelink communications may utilize a transmit or receive resource pool. For example, the minimum resource allocation unit in frequency may be a subchannel (e.g., which may include, for example, 10, 15, 20, 25, 50, 75, or 100 consecutive resource blocks), and the minimum resource allocation unit in time may be a time slot. The radio resource control (RRC) configuration of the resource pool may be pre-configured (e.g., a factory setting on the UE determined by a sidelink standard or specification) or configured by a base station (e.g., base station 210).

[0069] In addition, for sidelink (e.g., PC5) communications, there may be two main resource allocation operating modes. In the first mode (mode 1), the base station (e.g., gNB) 210 can allocate resources to sidelink devices (e.g., V2X devices or other sidelink devices) in various ways for sidelink communications between sidelink devices. For example, the base station 210 may dynamically (e.g., dynamic grant) allocate sidelink resources to the sidelink device in response to a request for sidelink resources from the sidelink device. The base station 210 may further activate a pre-configured sidelink grant (e.g., a configured grant) for sidelink communications between sidelink devices. In mode 1, the sidelink feedback may be reported back to the base station 210 by the sending sidelink device.

[0070] In the second mode (Mode 2), the sidelink devices may autonomously select sidelink resources for sidelink communications between them. In some examples, the transmitting sidelink device may perform resource / channel sensing to select unoccupied resources (e.g., subchannels) on the sidelink channel. The signaling on the sidelink 212 is the same between the two modes. Therefore, from the perspective of the receiver, there is no difference between these modes.

[0071] Figure 3 is a diagram illustrating an example of a wireless communication network 300 for facilitating both cellular and sidelink communications. For example, the wireless communication network 300 may correspond to Figure 1 RAN 100 is shown. The wireless communication network 300 includes multiple wireless communication devices 302a, 302b, and 302c and a base station (e.g., eNB or gNB) 306. In some examples, the wireless communication devices 302a, 302b, and 302c may be UEs capable of sidelink communication (e.g., V2X or D2D). The wireless communication devices 302a, 302b, and 302c may correspond to Figure 1 , Figure 2 , Figure 7 , Fig.12 and Fig.15 Any UE or scheduled entity shown in any of the above. The base station 306 may correspond to Figure 1 , Figure 2 and Figure 7 Any base station or scheduled entity shown in any of the .

[0072] Wireless communication devices 302a and 302b can communicate via a first side link 304a, while wireless communication devices 302a and 302c can communicate via a second side link 304b. Each of the side links 304a and 304b can utilize, for example, a PC5 interface. Wireless communication devices 302a, 302b, and 302c can also communicate with base station 306 via corresponding Uu links 308a, 308b, and 308b. Sidelink communications on sidelinks 304a and 304b can be carried in a licensed frequency domain, for example, using radio resources operating according to 5G NR or NR sidelink (SL) specifications and / or carried in an unlicensed frequency domain using radio resources operating according to 5G new radio unlicensed (NR-U) specifications.

[0073] In some examples, a common carrier can be shared between the sidelinks 304a and 304b and the Uu links 308a-308c, such that resources on the common carrier can be allocated for both sidelink communications between the wireless communication devices 302a-302c and cellular communications (e.g., uplink and downlink communications) between the wireless communication devices 302a-302c and the base station 306. For example, the wireless communication network 300 can be configured to support a mode 1 sidelink network in which resources for both sidelink and cellular communications are scheduled by the base station 306. In other examples where a mode 2 sidelink is implemented on the sidelinks 304a and 304b, the wireless communication devices 302a-302c can autonomously (e.g., from one or more frequency bands or sub-bands designated for sidelink communications) select sidelink resources for communication therebetween. In this example, the wireless communication devices 302a-302c can act as a scheduling entity and a scheduled entity that schedules sidelink resources for communication with each other.

[0074] Various aspects of the present invention will be described with reference to OFDM waveforms. Figure 4 Schematically shown in FIG. Those of ordinary skill in the art will appreciate that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to SC-FDMA waveforms.

[0075] Reference now Figure 4, shows an expanded view of an example subframe 402, showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical (PHY) layer transmission structure for any particular application may differ from the example described herein, depending on any number of factors. Here, time is measured in units of OFDM symbols in the horizontal direction; frequency is measured in units of subcarriers of a carrier in the vertical direction.

[0076] Resource grid 404 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple input multiple output (MIMO) implementation with multiple available antenna ports, corresponding multiple resource grids 404 can be used for communication. Resource grid 404 is divided into multiple resource elements (RE) 406. RE, which is 1 subcarrier × 1 symbol, is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some examples, RE blocks can be referred to as physical resource blocks (PRBs) or more simply resource blocks (RBs) 408, which contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, the number being independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB408 corresponds entirely to a single communication direction (transmission or reception of a given device).

[0077] A group of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A group of subbands or BWPs may span the entire bandwidth. Scheduling a UE or sidelink device (hereinafter collectively referred to as a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Therefore, the UE typically uses only a subset of the resource grid 404. In some examples, an RB may be the smallest resource unit that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, the higher the modulation scheme selected for the air interface, and the higher the data rate of the UE. The RBs may be scheduled by a base station (e.g., a gNB, eNB, etc.) or may be self-scheduled by a UE / sidelink device implementing D2D sidelink communication.

[0078] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers shown above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Additionally, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is merely one possible example.

[0079] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include mini time slots with shorter durations (e.g., one to three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these mini time slots or shortened transmission time intervals (TTIs) may occupy resources scheduled for ongoing time slot transmissions of the same or different UEs for transmission. Any number of resource blocks can be used within a subframe or time slot.

[0080] An expanded view of one of the time slots 410 shows the time slot 410 including a control region 412 and a data region 414. Typically, the control region 412 may carry control channels, while the data region 414 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The structure shown is only an example, and different slot structures may be used and may include one or more of each of the control region and the data region.

[0081] Despite Figure 4 Not shown in the figure, various REs 406 within RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within RB 408 may also carry pilot or reference signals. These pilot or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control and / or data channels within RB 408.

[0082] In some examples, time slot 410 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended recipient devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0083] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information, including one or more DL control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or RE allocations for DL ​​and UL transmissions. The PDCCH may also carry a hybrid automatic repeat request (HARQ) feedback transmission, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, in which the integrity of a packet transmission may be checked on the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable chase combing, incremental redundancy, and the like.

[0084] The base station may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast periodically based on a period (e.g., 5, 10, 20, 40, 80, or 140 ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0085] The PBCH in the SSB may also include a master information block (MIB), which includes various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, a SystemInformationType 1 (SIB1) that may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., a default downlink parameter set), a system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), a cell barring indicator, a cell reselection indicator, a raster offset, and a search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, a random access search space, a paging search space, downlink configuration information, and uplink configuration information.

[0086] In UL transmission, the scheduled entity (e.g., UE) may carry UL control information (UCI) including one or more UL control channels (such as a physical uplink control channel (PUCCH)) to the scheduling entity using one or more REs 406. UCI may include multiple packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmission. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., requesting the scheduling entity to schedule uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI) that may schedule resources for uplink packet transmission. UCI may also include HARQ feedback, channel state feedback (CSF), such as a CSI report, or any other suitable UCI.

[0087] In addition to control information, one or more REs 406 (e.g., within the data region 414) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as, for DL ​​transmission, a physical downlink shared channel (PDSCH); or for UL transmission, a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0088] In an example of sidelink communication over a sidelink carrier via a PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or some other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by an initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be sent via various REs 406 within the time slot 410. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410.

[0089] These physical channels are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which may correspond to the number of bits of information, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0090] Figure 4 The channels or carriers shown in are not necessarily all channels or carriers that may be used between devices, and one of ordinary skill in the art will recognize that other channels or carriers may be used in addition to those shown, such as other traffic, control, and feedback channels.

[0091] As described above, a wireless communication device (e.g., V2X or other D2D device) may schedule sidelink communications (e.g., PC5) by using sidelink control information (SCI). SCI may include two SCI stages. Stage 1 sidelink control information (first stage SCI) may be referred to herein as SCI-1. Stage 2 sidelink control information (second stage SCI) may be referred to herein as SCI-2.

[0092] SCI-1 may be transmitted on a physical sidelink control channel (PSCCH). SCI-1 may include resource allocations for sidelink resources and information for the second stage (i.e., SCI-2) of decoding sidelink control information. SCI-1 may identify the priority (e.g., quality of service (QoS)) of PSSCH. For example, an ultra-reliable low-delay communication (URLLC) service may have a higher priority than a text message service (e.g., a short message service (SMS) service). SCI-1 may also include a physical sidelink shared channel (PSSCH) resource allocation and a resource reservation period (if enabled). In addition, SCI-1 may include a PSSCH demodulation reference signal (DMRS) mode (if more than one mode is configured). DMRS may be used by a receiver for radio channel estimation to demodulate the associated physical channel. As noted, SCI-1 may also include information about SCI-2, for example, SCI-1 may disclose the size of SCI-2 by indicating the number of time-frequency resources allocated to SCI-2, the number of PSSCH DMRS ports, and the modulation and coding scheme (MCS) index. SCI-1 may include other information useful for setting up and decoding PSSCH resources.

[0093] SCI-2 may also be transmitted on the PSCCH and may include information for decoding the PSSCH. According to some aspects, SCI-2 includes a 16-bit Layer 1 (L1) destination identifier (ID), an 8-bit L1 source ID, a HARQ process ID, a new data indicator (NDI), and a redundancy version (RV). For unicast communications, SCI-2 may also include a CSI report trigger. For multicast communications, SCI-2 may also include an area identifier and a maximum communication range for NACK. SCI-2 may include other information useful for establishing and decoding PSSCH resources. In various aspects of the present disclosure, SCI-2 may also include an SL PT-RS configuration indicating a configurable number of PT-RS ports and a PTRS-DMRS port association.

[0094] Figure 5A and Figure 5B An example of a sidelink time slot structure according to some aspects is shown. For example, the sidelink time slot structure can be used in a V2X or other D2D network that implements a sidelink. Figure 5A and Figure 5B In the example shown, time is in the horizontal direction in units of symbols 502 (e.g., OFDM symbols); frequency is in the vertical direction. Here, the carrier bandwidth 504 allocated to the sidelink communication is shown along the frequency axis. The carrier bandwidth 504 may include a plurality of subchannels, where each subchannel may include a configurable number of PRBs (e.g., 5, 15, 20, 25, 50, 75, or 50 PRBs).

[0095] Figure 5A and Figure 5B Each of the illustrated time slots 500a and 500b includes an example of 14 symbols 502 that may be used for sidelink communications. However, it should be understood that sidelink communications may be configured to occupy less than 14 symbols in time slots 500a and 500b, and the present invention is not limited to any particular number of symbols 502. Each sidelink time slot 500a and 500b includes a physical sidelink control channel (PSCCH) 506 that occupies a control region 520 of time slots 500a and 500b and a physical sidelink shared channel (PSSCH) 508 that occupies a data region 522 of time slots 500a and 500b. The PSCCH 506 and PSSCH 508 are each transmitted on one or more symbols 502 of time slot 500a. The PSCCH 506 includes, for example, SCI-1, which schedules the transmission of data traffic on the time-frequency resources of the corresponding PSSCH 508. As Figure 5A and Figure 5B As shown, PSCCH 506 and corresponding PSSCH 508 are transmitted in the same time slots 500a and 500b.

[0096] In some examples, the PSCCH 506 duration is configured to be two or three symbols. In addition, the PSCCH 506 can be configured to span a configurable number of PRBs, limited to a single subchannel. For example, the PSCCH 506 can span 5, 12, 15, 20, or 25 PRBs of a single subchannel. DMRS can also be present in each PSCCH symbol. In some examples, DMRS can be placed on every four REs of the PSCCH 506. Frequency domain orthogonal cover codes (FD-OCC) can be further applied to the PSCCH DMRS to reduce the impact of conflicting PSCCH transmissions on the side link channel. For example, the transmitting wireless communication device can randomly select a FD-OCC from a set of predefined FD-OCCs. Figure 5A and Figure 5B In each of the examples shown in , the starting symbol of the PSCCH 506 is the second symbol of the corresponding time slots 500a and 500b, and the PSCCH 506 spans three symbols 502.

[0097] PSSCH 508 may be time division multiplexed (TDMed) with PSCCH 506 and / or frequency division multiplexed (FDMed) with PSCCH 506. Figure 5A In the example shown, the PSSCH 508 includes a first portion 508a that is TDMed with the PSCCH 506 and a second portion 508b that is FDMed with the PSCCH 506 .

[0098] One and two layer transmissions of PSSCH 508 may be supported with various modulation orders (e.g., quadrature phase shift keying (QPSK), 16-QAM, 64-QAM, and 256-QAM). In addition, PSSCH 508 may include DMRS 514 configured with a DMRS pattern of two, three, or four symbols. For example, Figure 5A The time slot 500a shown in FIG. 5 shows a two-symbol DMRS pattern, while Figure 5B The time slot 500b shown in FIG. 5 shows a three-symbol DMRS pattern. In some examples, the transmitting wireless communication device can select a DMRS pattern based on channel conditions and indicate the selected DMRS pattern in SCI-1. For example, the DMRS pattern can be selected based on the number of PSSCH 508 symbols in time slots 500a and 500b. In addition, the gap symbol 516 appears after the PSSCH 508 in each time slot 500a and 500b.

[0099] Each time slot 500a and 500b also includes SCI-2 512 mapped to consecutive RBs in PSSCH 508 starting from the first symbol containing the PSSCH DMRS. Figure 5A In the example shown, the first symbol containing the PSSCH DMRS is the fifth symbol that occurs immediately after the last symbol carrying the PSCCH 506. Therefore, SCI-2 512 is mapped to the RB within the fifth symbol. Figure 5B In the example shown, the first symbol containing the PSSCH DMRS is the second symbol, which also includes the PSCCH 506. In addition, the SCI-2 / PSSCH DMRS 512 is shown as spanning symbols 2 to 5. As a result, the SCI-2 / PSSCH DMRS 512 can be frequency-division multiplexed with the PSCCH 506 in symbols 2 to 4, and time-division multiplexed with the PSCCH 506 in symbol 5.

[0100] SCI-2 can be scrambled separately from the sidelink shared channel. In addition, SCI-2 can use QPSK. When the PSSCH transmission spans two layers, the SCI-2 modulation symbols can be replicated on both layers. The SCI-1 in the PSCCH 506 can be blind decoded at the receiving wireless communication device. However, since the format, starting position and number of REs of SCI-2 512 can be derived from SCI-1, there is no need to blindly decode SCI-2 at the receiver (receiving wireless communication device).

[0101] exist Figure 5A and Figure 5B The second symbol of each time slot 500a and 500b is copied (repeated) onto its first symbol 510 for automatic gain control (AGC) setting. Figure 5AIn , the second symbol including the PSCCH 506 frequency division multiplexed with the second portion 508b of the PSSCH 508 may be transmitted on both the first symbol and the second symbol. Figure 5B In the example shown, the second symbol including the PSCCH 506 frequency division multiplexed with the SCI-2 / PSSCH DMRS 512 may be transmitted on both the first symbol and the second symbol.

[0102] In a sidelink network, quality of service (QoS) and system performance may be affected by timing misalignment between sidelink devices. Therefore, in order to maintain common synchronization of time and frequency between sidelink devices, each sidelink device can be synchronized to a synchronization source, such as a gNB, eNB, or a global navigation satellite system (GNSS), or based on a time / frequency reference within the sidelink device. One or more sidelink devices may further generate and send synchronization information for use by other sidelink devices when synchronizing radio frame timing (e.g., radio frame boundaries and frame indexes) to the transmitting sidelink device. For example, the synchronization information may include a sidelink synchronization signal (S-SSS). In some examples, the S-SS may be a sidelink synchronization block (S-SSB), which includes a sidelink primary synchronization signal (S-PSS), a sidelink secondary synchronization signal (S-SSS), and a physical sidelink broadcast channel (PSBCH). The S-SSB may also include a downlink modulation reference signal (DMRS), or other signals used for synchronization.

[0103] Figure 6 An example of an S-SSB structure 600 is shown. The S-SSB structure 600 includes a PSBCH symbol 602, an S-PSS symbol 604, an S-SSS symbol 606, and a gap 608.

[0104] Figure 7 7 is a diagram illustrating an example of synchronization in a sidelink wireless communication network 700. The sidelink wireless communication network 700 includes a synchronization source 702 and a plurality of sidelink devices (e.g., UEs) 704, 706, 708, and 710. In some examples, the synchronization source 702 may include a base station (e.g., gNB, eNB, GNSS, etc.) or other suitable synchronization information source. In some examples, the synchronization source 702 may correspond to Figure 1 , Figure 2 and Figure 3 UEs 704, 706, 708, and 710 may correspond to any base station or scheduling entity or timing source shown in any of the above. Figure 1 , Figure 2 , Figure 3 , Fig.12 and Fig.15 Any UE or scheduled entity shown in any one of .

[0105] The synchronization source 702 may be configured to generate and transmit a synchronization signal 712 that may be received and processed by the first UE (UE-1) 704. For example, in a scenario where the synchronization source 702 is a GNSS satellite, the synchronization signal 712 may include a timestamp that provides very reliable timing information. As another example, in a scenario where the synchronization source 702 is a gNB, the synchronization signal 712 may take the form of a synchronization signal block that provides reliable timing signaling.

[0106] The first UE 704 may utilize the synchronization information in the synchronization signal 710 to synchronize the radio frame timing (e.g., radio frame boundary and frame index) of the first UE 704 with the synchronization source 702. The first UE 704 may also be in sidelink wireless communication with a second UE (UE-2) 706. However, the second UE 706 may be outside the coverage area of ​​the synchronization source 702. Therefore, the first UE 704 may generate and send a first sidelink synchronization signal (S-SS) 714 based on the synchronization established with the synchronization source 702. The first S-SS 714 may be received by the second UE 706, and the second UE 706 may utilize the first S-SS 714 to synchronize radio frame timing with the first UE 704.

[0107] The second UE 706 may then generate and transmit a second S-SS 716 based on the synchronization established with the first UE 704 to synchronize the timing of a third UE (UE-3) 708 and the first UE 704 outside the coverage area of ​​the synchronization source 702. Similarly, the third UE 708 may generate and transmit a third S-SS 718 based on the synchronization established with the second UE 706 to synchronize the timing of a fourth UE (UE-4) 710 outside the coverage area of ​​the synchronization source 702 with each of the first UE 704 and the second UE 706.

[0108] Figure 7 Each UE in may be assigned a physical layer synchronization side link identifier. In some examples, there are 672 unique physical layer synchronization side link identifiers, as shown in Formula 1:

[0109]

[0110] Here, and The sequences are divided into two groups: The id_net is composed of In some examples, the first group (id_net) can be assigned to side-link devices within one hop of the synchronization source. In some examples, the second group (id_oon) can be assigned to side-link devices that are more than one hop from the synchronization source.

[0111] The S-PSS sequence dS-PSS(n) discussed above can be defined as:

[0112] d S-PSS (n) = 1-2x(m)

[0113]

[0114] 0≤n<127 Formula 2

[0115] in,

[0116] x(i+7)=(x(i+4)+x(i))mod 2

[0117] and

[0118] [x(6) x(5) x(4) x(3) x(2) x(1) x(0)]=[1 1 1 0 1 1 0]

[0119] As described below, the S-PSS is therefore based in part on a sidelink identifier (e.g., a physical layer synchronization sidelink identifier)

[0120] The S-PSS sequence dS-SSS(n) discussed above can be defined as:

[0121]

[0122]

[0123]

[0124] in

[0125] x0(i+7)=(x0(i+4)+x0(i))mod 2

[0126] x1(i+7)=(x1(i+1)+x1(i))mod 2

[0127] and

[0128] [x0(6) x0(5) x0(4) x0(3) x0(2) x0(1) x0(0)]=[0 0 0 0 0 0 1]

[0129] [x1(6) x1(5) x1(4) x1(3) x1(2) x1(1) x1(0)]=[0 0 0 0 0 0 1]

[0130] As described below, the S-SSS is therefore based in part on the sidelink identifier and side link identifier

[0131] In the sidelink network, two synchronization (sync) resources are configured in the synchronization period. These resources can be designated as a first synchronization resource R-1 and a second synchronization resource R-2.

[0132] Table 1 shows how synchronization resources can be allocated to sidelink devices (e.g., in the case where a GNSS satellite is a synchronization source (e.g., synchronization source 702). Figure 7 ). In this example, a first UE (designated as UE-1) receives a synchronization signal from a GNSS satellite. A second UE (designated as UE-2) receives a synchronization signal (e.g., S-SSB) from the first UE (UE-1). A third UE (designated as UE-3) receives a synchronization signal (e.g., S-SSB) from the second UE (UE-2). A fourth UE (designated as UE-4) receives a synchronization signal (e.g., S-SSB) from the third UE (UE-3). A fifth UE (designated as UE-5) receives a synchronization signal (e.g., S-SSB) from the fourth UE (UE-4). Table 1 indicates which UEs are in-coverage of the synchronization source. In this example, only the first UE (UE-1) is in-coverage.

[0133] Priority Synchronous Tx resource Covering SLSS ID P0 GNSS -- -- -- P1 UE-1 R-1 real 0 P2 UE-2 R-2 Fake 0 P2_2 UE-3 R-1 Fake 336 P2_3 UE-4 R-2 Fake 336 P2_4 UE-5 R-1 Fake 336 … …

[0134] Table 1

[0135] The first UE (UE-1) transmits its synchronization signal via the first synchronization resource R-1. This transmission may be referred to as hop 0: the first hop of synchronization timing from the first UE (UE-1) to another UE, for example, the second UE (UE-2). The second UE (UE-2) transmits its synchronization signal via the second synchronization resource R-2. This transmission may be referred to as hop 1. The third UE (UE-3) transmits its synchronization signal via the first synchronization resource R-1. This transmission may be referred to as hop 2. The fourth UE (UE-4) transmits its synchronization signal via the second synchronization resource R-2, and so on. This transmission may be referred to as hop 3, and so on.

[0136] Each synchronization signal transmission is assigned a priority. The synchronization signal transmission from the GNSS satellite is assigned the highest priority (P0). The synchronization signal transmission from the first UE (UE-1) is assigned a lower priority (P1). The synchronization signal transmission from the second UE (UE-2) is assigned an even lower priority (P2). The synchronization signal transmission from the third UE (UE-3), the fourth UE (UE-4) and the fifth UE (UE-5) is assigned a lower priority based on the priority P2.

[0137] In some examples, these priorities represent the accuracy of the synchronization signal transmitted. For example, since the third UE (UE-3) is more hops away from the synchronization source than the first UE (UE-1), the priority of the synchronization signal transmission from the third UE (UE-3) will be lower than the priority of the synchronization signal transmission from the first UE (UE-1).

[0138] Table 1 also shows a side link synchronization signal identifier (SLSS ID) assigned to each UE. In this case, the first UE (UE-1) and the second UE (UE-2) are assigned SLSS ID 0. The remaining UEs are assigned SLSS ID 366.

[0139] The following observations can be made based on Table 1. Hop 0 (S-SSB from UE-1) is on resource 1, in-coverage = true, and SLSS ID = 0. Hop 1 (S-SSB from UE-1) is on resource 2, in-coverage = false, and SLSS ID = 0. S-SSBs from UE-4 / 6 / 8... will be single frequency networked (SFN'ed) on resource 2 (in-coverage = false, SLSS ID = 336). S-SSBs from UE-3 / 5 / 7... will be SFN'ed on resource-1 (in-coverage = false, SLSS ID = 336).

[0140] Table 2 shows how synchronization resources can be allocated to sidelink devices (e.g., in the scenario where the gNB is the synchronization source (e.g., synchronization source 702). Figure 7 In this case, the synchronization signal transmission from the gNB is assigned priority P3 / 4 / 5 or P0′ / 1′ / 2′. Similar to Table 1, two synchronization resources (R-1 and R-2) are allocated in Table 2. In this case, SLSS IDs ranging from 1 to 335 can be allocated to the first UE (UE-1) and the second UE (UE-1). The SLSS ID allocated to the remaining UEs is equal to the SLSS ID of the first UE (UE-1) plus 336. For example, if the SLSS ID of the first UE (UE-1) = 1, the SLSS ID of the third UE (UE-3) = 337.

[0141] Priority Synchronous Tx resource Covering SLSS ID P3 / P0' gNB -- -- -- P4 / P1' UE-1 R-1 real ID = [1-335] P5 / P2' UE-2 R-2 Fake The ID is the same as UE1 UE-3 R-1 Fake ID+336 UE-4 R-2 Fake ID+336 ....

[0142] Table 2

[0143] It can be observed that the resource usage of the gNB synchronization source scenario (Table 2) is similar to that of the GNSS synchronization source scenario (Table 1).

[0144] In both cases, S-SSBs from multiple sidelink devices may be transmitted on the same resource. Thus, a first sidelink device may have difficulty receiving an S-SSB from a second sidelink device over a designated resource (e.g., resource R-1) due to S-SSB transmissions by other sidelink devices on the same resource (e.g., resource R-1). If the first sidelink device is unable to successfully receive an S-SSB and its associated DMRS, the first sidelink device may resort to synchronizing with a sidelink device that provides lower priority synchronization signaling. As a result, the performance of the sidelink network may be affected.

[0145] Therefore, in various aspects of the present disclosure, the side link device can map different hops to the same resources and sequences, but with orthogonal DMRS. For example, the side link device can map hop 0 and hop 2 to the same resources and sequences, but with orthogonal DMRS. Similarly, the side link device can map hop 1 and hop 3 to the same resources and sequences, but with orthogonal DMRS.

[0146] In a first aspect, the side link device may initialize a DMRS sequence generator based on a first side link identifier. As an example, the first side link identifier may be And the DMRS sequence generator initialization parameter can be c init In this case, hop 0 and hop 2 (assigned to the same resource R-1) will have the same sequence initialization because they have the same first side link identifier (e.g., SLSS ID=0 for GNSS scenario or the same SLSS ID 1-355 for gNB scenario). In other examples, the first side link identifier and / or initialization parameters may take other forms.

[0147] The following is an example of a DMRS sequence generator. Other DMRS sequence generators may be used in other examples. Here, it can be seen that c init is the initializer of the DMRS sequence generator. Specifically, the parameter x2(n) of the pseudo-random sequence c(n) is used by c init Initialization. A sequence r(m) (eg, a sequence used to modulate a sidelink reference signal such as an S-SS / PSBCH block) may be generated based on a pseudo-random sequence c(n).

[0148] For example, the reference signal sequence r(m) of the S-SS / PSBCH block can be defined as:

[0149]

[0150] The parameter c(n) is a pseudo-random sequence. A pseudo-random sequence c(n) of 31 elements can be generated as follows:

[0151]

[0152] in

[0153] x1(n+31)=(x1(n+3)+x1(n))mod2

[0154] and

[0155] x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod2

[0156] Here, the sequence x2 is initialized with parameter c init To initialize:

[0157]

[0158] In various examples, the initialization value (e.g., c init ) can be based on the first side link identifier in different ways (e.g., ). In some scenarios, the initialization value is set equal to the first side link identifier (e.g., ). For example, a sequence generator can be used in a is initialized at the beginning of each S-SS / PSBCH block.

[0159] In other scenarios, the first side link identifier may be based on the first side link identifier and another value (e.g., ) to set the initialization value. In some examples, the other value can be defined (e.g., specified by a wireless communication standard such as one of the 3GPP specifications). In some examples, the other value can be configured (e.g., by the gNB). For example, the gNB can send a radio resource control (RRC) message or some other message to the sidelink device to configure the sidelink device with the other value. In some examples, the other value can be pre-configured (e.g., when an integrated circuit for the sidelink device is manufactured, tested, powered on, etc.). For example, the programming circuit can send an RRC message or some other message to the sidelink device to configure the sidelink device with the other value.

[0160] In a second aspect, the sidelink device may scale the DMRS sequence in conjunction with mapping the DMRS to resource elements (REs).For example, the sidelink device may scale the DMRS sequence using at least one scaling parameter.

[0161] In some examples, when mapping the DMRS sequence to a resource element (RE), the sidelink device may apply a frequency domain cover code (e.g., an orthogonal cover code (OCC)). In some examples, the cover code may be based on a second sidelink identifier (e.g., ).

[0162] In an example using OCC, different hops may use orthogonal sequences. For example, when mapping a DMRS sequence to REs, the sidelink device may apply OCC such that hop 0 and hop 2 use orthogonal resources. As another example, the sidelink device may apply OCC when mapping a DMRS sequence to REs such that hop 1 and hop 3 use orthogonal resources.

[0163] Therefore, when the side link device maps different hops to the same resource and sequence, the side link device can use scaling as discussed herein so that the different hops use orthogonal DMRS. Therefore, even when there is an S-SSB transmission on the same resource (e.g., resource R-1) by the other side link device, the first side link device can effectively receive the S-SSB from the second side link device through the designated resource (e.g., resource R-1), provided that the first side link device and the other side link device use orthogonal resources. Therefore, in this case, the first side link device is more likely to receive the S-SSB and its associated DMRS than when the first side link device and the other side link device do not use orthogonal resources.

[0164] The scaling described herein can be used in conjunction with different techniques for mapping different hops to the same resources and sequence. In some examples, the DMRS sequence generator initialization techniques described herein can be used to map different hops to the same resources and sequence. In some examples, fixed initialization parameters can be used (e.g., for hops 0 and 2) so that the hops will map to the same sequence. In some examples, the initialization parameters to be used (e.g., for hops 0 and 2) can be signaled to the sidelink device (e.g., via RRC signaling from the gNB) so that the hops will map to the same sequence. In any of these scenarios, the scaling taught herein can be used (e.g., applying OCC) so that different hops are mapped to the same resources and sequence, but using orthogonal DMRS.

[0165] Below is a detailed example of scaling based on the second side link identifier. Other types of scaling may be used in other examples.

[0166] When mapping a symbol r(x) (referred to as r(m) in Equation 4 above) from a sequence to REs in symbol l and subcarrier k, the sequence r(x) can be factored Scaled to match the specified transmit power and mapped to resource elements (k, l) according to the following formula p，u :

[0167]

[0168] In some examples, when mapping symbol r(x) from the sequence to symbol l and REs in subcarrier k, the sidelink device can further scale the symbol r(x) by a factor w(k), where the value of w(k) depends at least in some aspects on the second sidelink identifier (e.g., ). Table 3A, Table 3B, Table 4, and Table 5 show three examples of w(k).

[0169] For example, Table 3A or Table 3B may be used to There are two possible values ​​(eg, 0 and 1). In some examples, the first column of w(k) may be used for even values ​​of k (k mode 2=0), while the second column of w(k) is used for odd values ​​of k (k mode 2=1).

[0170] In some examples, the complex-valued symbol sequence r(0), ..., r(XXX) constituting the demodulation reference signal for the S-SS / PSBCH block can be factored Scaled to conform to the specified PSBCH power allocation, scaled by the factor w(k) given in Table 3A or 3B, and mapped to resource elements (k, l) in increasing order of first k and then l p，u , where k and l represent the frequency and time index within an S-SS / PSBCH block, respectively.

[0171]

[0172] Table 3A

[0173]

[0174] Table 3B

[0175] Tables 4 and 5 can be used, for example, for There are more than two possible values. In some examples, the w(k) values ​​of Table 4 may provide good orthogonality, but with increased implementation complexity. In some examples, the w(k) values ​​of Table 5 may provide an easier implementation with less orthogonality (since only +1 and -1 values ​​are used).

[0176]

[0177] Table 4

[0178]

[0179] Table 5

[0180] In different examples, the scaling parameter can be based on the second side link identifier (e.g., ). In some scenarios, at least one scaling parameter is set based on the value of the side link identifier (e.g., as shown in Table 3-5). In other scenarios, at least one scaling parameter can be set based on the first side link identifier and another value. In some examples, the other value can be defined (e.g., specified by a wireless communication standard such as one of the 3GPP specifications). In some examples, the other value can be configured (e.g., by the gNB). For example, the gNB can send a radio resource control (RRC) message or some other message to the side link device to configure the side link device with the other value. In some examples, the other value can be pre-configured (e.g., when an integrated circuit for the side link device is manufactured, tested, powered on, etc.). For example, the programming circuit can send an RRC message or some other message to the side link device to configure the side link device with the other value.

[0181] Figure 8 800 is a block diagram illustrating an example of a sidelink communication circuit 800 that may be configured to perform any of the DMRS generation-related operations discussed herein. The sidelink communication circuit 800 includes a sidelink identifier determination circuit 802 and a sidelink DMRS generation circuit 804.

[0182] The side link identifier determination circuit 802 may be configured to determine a first side link identifier and / or a second side link identifier of a side link device. For example, the side link identifier determination circuit 802 may determine and In some examples, the side link identifier determination circuit 802 can retrieve the identifier from a memory (e.g., from a memory location storing identifier information configured for the side link device). The side link identifier determination circuit 802 outputs the determined side link identifier 806 to the side link DMRS generation circuit 804.

[0183] The sidelink DMRS generation circuit 804 may be configured to generate a DMRS 808 based on the sidelink identifier 806. In some examples, the sidelink DMRS generation circuit 804 may be configured to perform any DMRS generation operations discussed herein. The following are several non-limiting examples of this functionality.

[0184] In some examples, the sidelink DMRS generation circuit 804 can determine an initialization parameter based on at least the first side link identifier and use the initialization parameter to generate a DMRS.

[0185] In some examples, the side link DMRS generation circuit 804 can determine an initialization parameter based on at least the first side link identifier, initialize a sequence generator with the initialization parameter, generate a pseudo-random sequence using the sequence generator, and generate a DMRS from the pseudo-random sequence.

[0186] In some examples, the sidelink DMRS generation circuit 804 can generate a sequence, determine at least one scaling parameter based on at least the second side link identifier, and scale the sequence using the at least one scaling parameter to generate a DMRS.

[0187] In some examples, the sidelink DMRS generation circuit 804 can generate a sequence, determine a frequency domain cover code based on at least the second side link identifier, and apply the frequency domain cover code to the sequence to generate a DMRS.

[0188] In some examples, the side link DMRS generation circuit 804 may determine an initialization parameter based at least on a first side link identifier, generate a sequence using the initialization parameter, determine at least one scaling parameter based at least on a second side link identifier, and scale the sequence using the at least one scaling parameter to generate a DMRS.

[0189] In some examples, the side link DMRS generation circuit 804 can determine an initialization parameter based on at least a first side link identifier, initialize a sequence generator with the initialization parameter, generate a pseudo-random sequence using the sequence generator, generate a first sequence from the pseudo-random sequence, determine a frequency domain orthogonal cover code (OCC) based on at least a second side link identifier, and apply the frequency domain OCC to the first sequence to generate a DMRS.

[0190] In some examples, the side link DMRS generation circuit 804 can determine at least one of an initialization parameter based on at least a first side link identifier of the first side link device, at least one scaling parameter based on at least a second side link identifier of the first side link device, or a combination thereof, and use at least one of the initialization parameter, at least one scaling parameter, or a combination thereof to generate a demodulation reference signal (DMRS).

[0191] In some examples, the sidelink DMRS generation circuit 804 may initialize a sequence generator with an initialization parameter, generate a pseudo-random sequence using the sequence generator, and generate a DMRS from the pseudo-random sequence.

[0192] In some examples, the sidelink DMRS generation circuit 804 can generate a sequence and scale the sequence with at least one scaling parameter to generate a DMRS.

[0193] In some examples, the sidelink DMRS generation circuit 804 may determine parameters of a sequence generator, initialize the sequence generator with the parameters, generate a pseudo-random sequence using the sequence generator, and generate a DMRS from the pseudo-random sequence.

[0194] In some examples, the sidelink DMRS generation circuit 804 may receive parameters of a sequence generator via a radio resource control (RRC) message, initialize the sequence generator with the parameters, generate a pseudo-random sequence using the sequence generator, and generate a DMRS from the pseudo-random sequence.

[0195] In some examples, the side link DMRS generation circuit 804 can initialize a sequence generator with an initialization parameter, use the sequence generator to generate a pseudo-random sequence, generate a first sequence from the pseudo-random sequence, determine a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier, and apply the frequency domain OCC to the first sequence to generate a DMRS.

[0196] Fig. 9 is a block diagram illustrating an example of a sidelink communication circuit 900 that can be configured to perform one or more of the DMRS generation related operations discussed herein. In some examples, the sidelink communication circuit 900 can be Figure 8 The side link communication circuit 900 includes an initialization parameter determination circuit 902, a sequence generation circuit 904, and a DMRS generation circuit 906.

[0197] The initialization parameter determination circuit 902 may be configured to determine an initialization parameter for the sequence generation circuit 904. In some examples, the initialization parameter determination circuit 902 determines the initialization parameter based on a first side link identifier of the side link device. For example, the initialization parameter determination circuit 902 may determine the initialization parameter based on Determine c init In some examples, the initialization parameter may be a determined seed parameter (e.g., a parameter selected by the side link device) or a received seed parameter (e.g., a parameter received at the side link device). The initialization parameter determination circuit 902 outputs the determined initialization parameter 910 to the sequence generation circuit 904.

[0198] The sequence generation circuit 904 may be configured to generate a sequence based on the initialization parameters 910. In some examples, the sequence generation circuit 904 may be configured to perform any sequence generation operation discussed herein. The following are several non-limiting examples of this function. In some examples, the sequence generation circuit 904 may initialize a sequence generator with initialization parameters and use the sequence generator to generate a sequence (e.g., a pseudo-random sequence). In some examples, the sequence generation circuit 904 may include (e.g., may be) a sequence generator. The sequence generation circuit 904 outputs the generated sequence 912 to the DMRS generation circuit 906.

[0199] The DMRS generation circuit 906 may be configured to generate a DMRS 914 based on the sequence 912. In some examples, the DMRS generation circuit 906 may be configured to perform one or more DMRS generation operations discussed herein. The following are several non-limiting examples of this functionality. In some examples, the DMRS generation circuit 906 may generate a DMRS from a pseudo-random sequence. In some examples, the DMRS generation circuit 906 may determine at least one scaling parameter based on at least a second side link identifier, and scale the sequence using at least one scaling parameter to generate a DMRS. In some examples, the DMRS generation circuit 906 may determine a frequency domain cover code based at least on the second side link identifier, and apply the frequency domain cover code to the sequence to generate a DMRS. In some examples, the DMRS generation circuit 906 may determine at least one scaling parameter based on at least a second side link identifier, and scale the sequence using at least one scaling parameter to generate a DMRS. In some examples, the DMRS generation circuit 906 may generate a first sequence from a pseudo-random sequence, determine a frequency domain orthogonal cover code (OCC) based at least on the second side link identifier, and apply the frequency domain OCC to the first sequence to generate a DMRS. In some examples, the DMRS generation circuit 906 may generate a demodulation reference signal (DMRS) using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof.

[0200] Fig.10 1 is a block diagram illustrating an example of a sidelink communication circuit 1000 that can be configured to perform one or more of the DMRS scaling-related operations and / or DMRS mapping-related operations discussed herein. In some examples, the sidelink communication circuit 1000 can be Figure 8 The side link communication circuit 1000 includes a scaling parameter determination circuit 1002 and a DMRS mapping circuit 1004.

[0201] The scaling parameter determination circuit 1002 may be configured to determine a scaling parameter for the DMRS mapping circuit 1004. In some examples, the scaling parameter determination circuit 1002 determines at least one scaling parameter based on a side link identifier 1006 of the side link device. For example, the scaling parameter determination circuit 1002 may be based on To determine w(k). In some examples, at least one scaling parameter may be a frequency domain cover code. In some examples, at least one scaling parameter may be a frequency domain orthogonal cover code. Scaling parameter determination circuit 1002 outputs the determined scaling parameter 1008 to DMRS mapping circuit 1004.

[0202] DMRS mapping circuit 1004 may be configured to map DMRS sequence 1010 to RE 1012. In some examples, the DMRS sequence may be Fig. 9 In some examples, the DMRS mapping circuit 1004 may scale the DMRS sequence 1010 with the scaling parameter 1008 to generate a DMRS for transmission. In some examples, the DMRS mapping circuit 1004 may apply a frequency domain cover code to the DMRS sequence 1010 to generate a DMRS for transmission. In some examples, the cover code may be a frequency domain orthogonal cover code.

[0203] Fig.11 1 is a block diagram illustrating an example of a sidelink communication circuit 1100 that can be configured to perform any DMRS-based synchronization-related operations discussed herein. The sidelink communication circuit 1100 includes a sidelink identifier determination circuit 1102, a DMRS information determination circuit 1104, a decoding circuit 1106, and a synchronization circuit 1108.

[0204] The side link identifier determination circuit 1102 may be configured to determine a first side link identifier and / or a second side link identifier of a side link device. For example, the side link identifier determination circuit 1102 may derive the first side link identifier and / or the second side link identifier from the S-SSS. and derived from S-PSS and / or S-SSS The side link identifier determination circuit 1102 outputs the determined side link identifier 1110 to the DMRS information determination circuit 1104 .

[0205] The DMRS information determination circuit 1104 may be configured to determine a DMRS sequence associated with the received broadcast signal 1114. In some examples, the DMRS information determination circuit 1104 may determine the DMRS information based on the side link identifier 1110. In some examples, the DMRS information determination circuit 1104 may be configured to perform one or more of the DMRS determination or generation operations discussed herein. The following are several non-limiting examples of this functionality.

[0206] In some examples, the DMRS information determination circuit 1104 can determine an initialization parameter based on at least the first side link identifier and use the initialization parameter to generate DMRS information.

[0207] In some examples, the DMRS information determination circuit 1104 can determine an initialization parameter based on at least the first side link identifier, initialize a sequence generator with the initialization parameter, generate a pseudo-random sequence using the sequence generator, and generate DMRS information from the pseudo-random sequence.

[0208] In some examples, the DMRS information determination circuit 1104 can generate a sequence, determine at least one scaling parameter based on at least the second side link identifier, and scale the sequence using the at least one scaling parameter to generate the DMRS information.

[0209] In some examples, the DMRS information determination circuit 1104 may generate a sequence, determine a frequency domain cover code based on at least the second side link identifier, and apply the frequency domain cover code to the sequence to generate DMRS information.

[0210] In some examples, the DMRS information determination circuit 1104 can determine an initialization parameter based at least on a first side link identifier, generate a sequence using the initialization parameter, determine at least one scaling parameter based at least on a second side link identifier, and scale the sequence using the at least one scaling parameter to generate DMRS information.

[0211] In some examples, the DMRS information determination circuit 1104 can determine an initialization parameter based on at least the first side link identifier, initialize a sequence generator with the initialization parameter, generate a pseudo-random sequence using the sequence generator, generate a first sequence from the pseudo-random sequence, determine a frequency domain orthogonal cover code (OCC) based on at least the second side link identifier, and apply the frequency domain OCC to the first sequence to generate DMRS information.

[0212] DMRS information determination circuit 1104 outputs the determined DMRS information 1112 to decoding circuit 1106. Decoding circuit 1106 may be configured to decode received broadcast signal 1114 based on DMRS information 1112. In some examples, decoding circuit 1106 uses DMRS information 1112 for channel estimation and demodulation of received broadcast signal 1114. Decoding circuit 1106 outputs decoded broadcast channel information 1116 based on received broadcast signal 1114 to synchronization circuit 1108.

[0213] The synchronization circuit 1108 may be configured to synchronize with the sidelink device using the broadcast channel information 1116. In some examples, the synchronization circuit 1108 determines which sidelink device has the best synchronization signal priority based on the broadcast channel information 1116 (e.g., based on information carried by a master information block (MIB) 1 or another system information block identified by the MIB 1). The synchronization circuit 1108 may then invoke a synchronization procedure whereby the timing of the sidelink device including the synchronization circuit 1108 synchronizes its timing with the timing of the sidelink device having the best synchronization signal priority.

[0214] Fig.12 is a block diagram illustrating an example of a hardware implementation of a side link device 1200 using a processing system 1214. For example, the side link device 1200 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 7 and Fig.15 Any one of the sidelink devices, UEs, or scheduled entities shown in any one of .

[0215] The sidelink device 1200 may be implemented with a processing system 1214 including one or more processors 1204. Examples of processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described herein. In various examples, the sidelink device 1200 may be configured to perform any one or more of the functions described herein. That is, the processor 1204 as used in the sidelink device 1200 may be used to implement any one or more of the processes and procedures described below.

[0216] In this example, the processing system 1214 may be implemented with a bus architecture, generally represented by bus 1202. Bus 1202 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1214. Bus 1202 links together various circuits including one or more processors (generally represented by processor 1204), memory 1205, and computer readable media (generally represented by computer readable media 1206). Bus 1202 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further.

[0217] The bus interface 1208 provides an interface between the bus 1202 and the transceiver 1210. The transceiver 1210 provides a device for communicating with various other devices through a transmission medium (e.g., an air interface). Depending on the nature of the device, a user interface 1212 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, a control knob, etc.) may also be provided. Of course, such a user interface 1212 is optional and may be omitted in some examples.

[0218] The processor 1204 is responsible for managing the bus 1202 and general processing, including the execution of software stored on the computer-readable medium 1206. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be broadly interpreted as referring to instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software, when executed by the processor 1204, causes the processing system 1214 to perform various functions described below for any particular device. The computer-readable medium 1206 and memory 1205 can also be used to store data used and / or manipulated by the processor 1204 when executing the software. For example, the memory 1205 can store an ID 1215 (e.g., a sidelink device identifier) ​​and parameters 1216 (e.g., initialization and scaling parameters) used by the processor 1204 to generate a sequence.

[0219] Computer readable medium 1206 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1206 may reside in processing system 1214, external to processing system 1214, or distributed among multiple entities including processing system 1214. Computer readable medium 1206 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging material. In some examples, computer readable medium 1206 may be part of memory 1205. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0220] In some aspects of the present invention, the processor 1204 may include circuits configured for various functions. For example, the processor 1204 may include: a communication and processing circuit 1241 configured to communicate via a sidelink carrier to exchange sidelink control information and sidelink data with other sidelink devices. In some examples, the communication and processing circuit 1241 may be configured to send a PSCCH, which may include a sidelink synchronization signal block (S-SSB), other control information and / or pilot signals, and / or a PSSCH, which may include sidelink data within a radio frame based on the sidelink transmission timing. In some examples, the sidelink transmission timing may be determined based on synchronization with a synchronization source (e.g., gNB, eNB, GNSS, etc.), self-synchronization with an internal timing / frequency reference, or synchronization with another sidelink device (e.g., based on a received S-SS as described herein). The communication and processing circuit 1241 may also be configured to execute communication and processing software 1251 stored on a computer-readable medium 1206 to implement one or more functions described herein.

[0221] In some implementations where the communication involves receiving information, the communication and processing circuitry 1241 may obtain information from a component of the sidelink device 1200 (e.g., from a transceiver 1210 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1241 may output the information to another component of the processor 1204, the memory 1205, or the bus interface 1208. In some examples, the communication and processing circuitry 1241 may receive one or more signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 1241 may receive information via one or more channels. In some examples, the communication and processing circuitry 1241 may include functionality of a means for receiving. In some examples, the communication and processing circuitry 1241 may include functionality of a means for decoding.

[0222] In some implementations where communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1241 may obtain the information (e.g., from another component of the processor 1204, the memory 1205, or the bus interface 1208), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1241 may output the information to the transceiver 1210 (e.g., by sending the information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium). In some examples, the communication and processing circuitry 1241 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1241 may send information over one or more channels. In some examples, the communication and processing circuitry 1241 may include functionality of a means for sending (e.g., a means for sending). In some examples, the communication and processing circuitry 1241 may include functionality of a means for encoding.

[0223] Processor 1204 may include side link identifier determination circuitry 1242 configured to perform operations related to side link identifier determination as discussed herein (e.g., in conjunction with Figure 8-Figure 11 In some examples, the sidelink identifier determination circuit 1242 may include functionality of a device for determining a sidelink identifier. For example, the sidelink identifier determination circuit 1242 may be configured to maintain and retrieve identifier values ​​in the memory 1205. In some examples, the sidelink identifier determination circuit 1242 may also be configured to execute the sidelink identifier determination software 1252 included in the computer-readable medium 1206 to implement one or more functions described herein.

[0224] In some examples, the side link identifier determination circuit 1242 may correspond to the above combined Figure 8 In some examples, the side link identifier determination circuit 1242 may be configured to determine a first side link identifier and / or a second side link identifier of a side link device. For example, the side link identifier determination circuit 1242 may determine and

[0225] Processor 1204 may include DMRS generation circuit 1243, which is configured to perform DMRS generation related operations as discussed herein (e.g., in conjunction with Figure 8-11In some examples, the DMRS generation circuit 1243 may include the functionality of a device for determining an initialization parameter. In some examples, the DMRS generation circuit 1243 may include the functionality of a device for determining a scaling parameter. In some examples, the DMRS generation circuit 1243 may include the functionality of a device for generating a DMRS. In some examples, the DMRS generation circuit 1243 may include the functionality of a device for sending a DMRS. In some examples, the DMRS generation circuit 1243 may also be configured to execute DMRS generation software 1253 included on the computer-readable medium 1206 to implement one or more functions described herein.

[0226] In some examples, the DMRS generation circuit 1243 may correspond to the above combined Figure 8 In some examples, the DMRS generation circuit 1243 may correspond to the side link DMRS generation circuit 804 described above. Fig. 9 In some examples, the DMRS generation circuit 1243 may correspond to the side link communication circuit 900 described above. Fig.10 The side link communication circuit 1000 described above. In some examples, the DMRS generation circuit 1243 can be configured to determine an initialization parameter based on at least the first side link identifier and use the initialization parameter to generate the DMRS. In some examples, the DMRS generation circuit 1243 can be configured to generate a sequence, determine at least one scaling parameter based on at least the second side link identifier, and scale the sequence using the at least one scaling parameter to generate the DMRS.

[0227] Processor 1204 may include sidelink timing circuitry 1244 configured to perform sidelink timing related operations as discussed herein (e.g., in conjunction with Figure 8-11 In some examples, the sidelink timing circuit 1244 may include functionality of a device for generating a synchronization signal. In some examples, the sidelink timing circuit 1244 may also be configured to execute sidelink timing software 1254 included on the computer-readable medium 1206 to implement one or more functions described herein.

[0228] The sidelink timing circuit 1244 may generate the S-SSB as discussed above, for example, in conjunction with Figure 6 and Figure 7 For example, the sidelink timing circuit 1244 may generate an S-SSS based on the first sidelink identifier and the second sidelink identifier and generate an S-PSS based on the second sidelink identifier.

[0229] Fig.131 is a flow chart of a method 1300 for wireless communication via a sidelink carrier. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present invention, and some of the illustrated features may not be required for implementations of all examples. In some examples, as described above and in Fig.12 As shown in FIG. 1 , the method may be performed by the sidelink device 1200 , by a processor or a processing system or by any suitable means for performing the described functions.

[0230] At block 1302, the first side link device may determine at least one of an initialization parameter based at least on a first side link identifier of the first side link device, at least one scaling parameter based at least on a second side link identifier of the first side link device, or a combination thereof. Fig.11 The DMRS generation circuit 1243 shown and described may be based on the Calculate c init As another example, the DMRS generation circuit 1243 may be based on Calculate the scaling parameters as discussed in this article.

[0231] In some examples, the first side link identifier is a first value from a set of values ​​from 0 to N. In some examples, the second side link identifier is 0 or 1.

[0232] In some examples, at least one scaling parameter may include a frequency domain cover code. In some examples, the cover code is an orthogonal cover code.

[0233] In some examples, determining the initialization parameter is also based on a configured value (e.g., the value is configured via signaling sent by the base station). In some examples, determining the initialization parameter is also based on a pre-configured value (e.g., the value is set when manufacturing, testing, powering on, etc. an integrated circuit for the sidelink device). In some examples, determining the initialization parameter is also based on a defined value (e.g., the value is specified by a wireless communication standard such as one of the 3GPP specifications).

[0234] At block 1304, the first side link device may generate a demodulation reference signal (DMRS) using (eg, based on) at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. For example, the DMRS generation circuit 1243 may generate a demodulation reference signal (DMRS) based on c init and / or scaling parameters to generate a sequence, and then generate a DMRS based on the sequence discussed in this article.

[0235] In some examples, generating the DMRS may include initializing a sequence generator with an initialization parameter, generating a pseudo-random sequence using the sequence generator, and generating the DMRS from the pseudo-random sequence.

[0236] In some examples, generating the DMRS may include generating a sequence and scaling the sequence using at least one scaling parameter to generate the DMRS. In some examples, generating the DMRS may include determining parameters for a sequence generator, initializing the sequence generator using the parameters, generating a pseudo-random sequence using the sequence generator, and generating the DMRS from the pseudo-random sequence. In some examples, generating the DMRS may include receiving parameters for the sequence generator via a radio resource control (RRC) message, initializing the sequence generator using the parameters, generating a pseudo-random sequence using the sequence generator, and generating the DMRS from the pseudo-random sequence.

[0237] In some examples, generating the DMRS can include initializing a sequence generator using an initialization parameter, generating a pseudo-random sequence using the sequence generator, generating a first sequence from the pseudo-random sequence, determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier, and applying the frequency domain OCC to the first sequence to generate the DMRS.

[0238] At block 1306, the first side link device may send a DMRS to the second side link device. Fig.12 As shown and described, the DMRS generation circuit 1243 together with the communication and processing circuit 1241 and the transceiver 1210 can send DMRS on the specified resources, for example, as described above in conjunction with Figure 5A and Figure 5B described.

[0239] In some examples, method 1300 may also include determining a physical layer side link synchronization identifier for the first side link device based on the first side link identifier and the second side link identifier.

[0240] Fig.14 1400 is a flow chart of a method 1400 for wireless communication via a sidelink carrier. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present invention, and some of the illustrated features may not be required for all example implementations. In some examples, as described above and in Fig.12 As shown in FIG. 1 , the method may be performed by the sidelink device 1200 , by a processor or a processing system or by any suitable means for performing the described functions.

[0241] At block 1402, the first side link device may determine a first side link identifier of the first side link device. In some examples, the first side link identifier is a first value in a set of values ​​from 0 to N. For example, as described above in conjunction with Fig.12 As shown and described, the side link identifier determination circuit 1242 may retrieve the

[0242] At block 1404, the first side link device may determine a second side link identifier for the first side link device. In some examples, the second side link identifier is 0 or 1. For example, the side link identifier determination circuit 1242 may retrieve the second side link identifier from the memory 1205.

[0243] At block 1406, the first sidelink device may generate a demodulation reference signal (DMRS) using (e.g., based on) the first sidelink identifier and the second sidelink identifier. Fig.12 The DMRS generation circuit 1243 shown and described may be based on Calculate c init And based on The scaling parameters are calculated as discussed herein. The DMRS generation circuit 1243 may then generate a sequence based on these values ​​and generate a DMRS based on the sequence.

[0244] In some examples, generating the DMRS may include determining an initialization parameter based at least on the first side link identifier, and generating the DMRS using the initialization parameter.

[0245] In some examples, generating the DMRS may include determining an initialization parameter based at least on the first side link identifier, initializing a sequence generator using the initialization parameter, generating a pseudo-random sequence using the sequence generator (e.g., the sequence generator is used to generate the sequence), and generating the DMRS from the pseudo-random sequence. In some examples, determining the initialization parameter is also based on a configured value (e.g., the value is configured by signaling sent by the base station). In some examples, determining the initialization parameter is also based on a pre-configured value (e.g., the value is set when manufacturing, testing, powering on, etc., an integrated circuit for a side link device). In some examples, determining the initialization parameter is also based on a defined value (e.g., the value is specified by a wireless communication standard such as one of the 3GPP specifications).

[0246] In some examples, generating the DMRS may include generating a sequence, determining at least one scaling parameter based on at least the second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS.

[0247] In some examples, generating the DMRS may include generating a sequence, determining a frequency domain cover code based on at least the second side link identifier, and applying the frequency domain cover code to the sequence to generate the DMRS. In some examples, the cover code may be an orthogonal cover code.

[0248] In some examples, generating the DMRS may include determining an initialization parameter based at least on a first side link identifier, generating a sequence using (e.g., based on) the initialization parameter, determining at least one scaling parameter based at least on a second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS.

[0249] In some examples, generating the DMRS can include determining an initialization parameter based at least on a first side link identifier, initializing a sequence generator with the initialization parameter, generating a pseudo-random sequence using the sequence generator, generating a first sequence from the pseudo-random sequence, determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier, and applying the frequency domain OCC to the first sequence to generate the DMRS.

[0250] At block 1408, the first side link device may send a DMRS to the second side link device. Fig.12 As shown and described, the DMRS generation circuit 1243 together with the communication and processing circuit 1241 and the transceiver 1210 can send DMRS on the specified resources, for example, as described above in conjunction with Figure 5A and Figure 5B described.

[0251] In some examples, method 1400 may also include determining a physical layer side link synchronization identifier for the first side link device based on the first side link identifier and the second side link identifier.

[0252] Fig.15 is a block diagram illustrating an example of a hardware implementation of a side link device 1500 employing a processing system 1514. For example, the side link device 1500 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 7 and Fig.12 Any one of the sidelink devices, UEs, or scheduled entities shown in any one of .

[0253] The sidelink device 1500 may be implemented with a processing system 1514 including one or more processors 1504. Examples of processors 1504 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described herein. In various examples, the sidelink device 1500 may be configured to perform any one or more of the functions described herein. That is, the processor 1504 as used in the sidelink device 1500 may be used to implement any one or more of the processes and procedures described below.

[0254] In this example, the processing system 1514 may be implemented with a bus architecture, generally represented by bus 1502. Bus 1502 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1514. Bus 1502 links together various circuits including one or more processors (generally represented by processor 1504), memory 1505, and computer-readable media (generally represented by computer-readable media 1506). Memory 1505 may store IDs 1515 (e.g., sidelink device identifiers) and parameters 1516 (e.g., initialization and scaling parameters) used by processor 1504 to generate sequences. Bus 1502 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further.

[0255] The bus interface 1508 provides an interface between the bus 1502 and the transceiver 1510. The transceiver 1510 provides a device for communicating with various other devices via a transmission medium (e.g., an air interface). Depending on the nature of the device, a user interface 1512 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, a control knob, etc.) may also be provided. Of course, such a user interface 1512 is optional and may be omitted in some examples.

[0256] The processor 1504 is responsible for managing the bus 1502 and general processing, including the execution of software stored on the computer-readable medium 1506. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be broadly construed to refer to instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software, when executed by the processor 1504, causes the processing system 1514 to perform various functions described below for any particular device. The computer-readable medium 1506 and memory 1505 may also be used to store data used and / or manipulated by the processor 1504 when executing the software.

[0257] Computer readable medium 1506 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1506 may reside in processing system 1514, external to processing system 1514, or distributed among multiple entities including processing system 1514. Computer readable medium 1506 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging material. In some examples, computer readable medium 1506 may be part of memory 1505. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0258] In some aspects of the present invention, the processor 1504 may include circuits configured for various functions. For example, the processor 1504 may include a communication and processing circuit 1541 configured to communicate via a sidelink carrier to exchange sidelink control information and sidelink data with other sidelink devices. In some examples, the communication and processing circuit 1541 may be configured to send a PSCCH, which may include a sidelink synchronization signal block (S-SSB), other control information and / or pilot signals, and / or a PSSCH, which may include sidelink data within a radio frame based on the sidelink transmission timing. In some examples, the sidelink transmission timing may be determined based on synchronization with a synchronization source (e.g., gNB, eNB, GNSS, etc.), self-synchronization with an internal timing / frequency reference, or synchronization with another sidelink device (e.g., based on a received S-SS as described herein). The communication and processing circuit 1541 may also be configured to execute communication and processing software 1551 stored on a computer-readable medium 1506 to implement one or more functions described herein.

[0259] In some implementations where the communication involves receiving information, the communication and processing circuitry 1541 may obtain information from a component of the sidelink device 1500 (e.g., from a transceiver 1510 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1541 may output the information to another component of the processor 1504, the memory 1505, or the bus interface 1508. In some examples, the communication and processing circuitry 1541 may receive one or more signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 1541 may receive information via one or more channels. In some examples, the communication and processing circuitry 1541 may include functionality of a means for receiving. In some examples, the communication and processing circuitry 1241 may include functionality of a means for decoding.

[0260] In some implementations where communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1541 may obtain information (e.g., from another component of the processor 1504, the memory 1505, or the bus interface 1508), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1541 may output the information to the transceiver 1510 (e.g., by sending the information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium). In some examples, the communication and processing circuitry 1541 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1541 may send information via one or more channels. In some examples, the communication and processing circuitry 1541 may include functionality of a means for sending (e.g., a means for sending). In some examples, the communication and processing circuitry 1541 may include functionality of a means for encoding.

[0261] Processor 1504 may include side link identifier determination circuitry 1542 configured to perform operations related to side link identifier determination as discussed herein (e.g., in conjunction with Figure 8-Figure 11 In some examples, the sidelink identifier determination circuit 1542 may include functionality of a means for determining a sidelink identifier. In some examples, the sidelink identifier determination circuit 1542 may include functionality of a means for deriving a sidelink identifier. For example, the sidelink identifier determination circuit 1542 may determine an identifier associated with a received synchronization signal when decoding the synchronization signal. In some examples, the sidelink identifier determination circuit 1542 may include functionality of a means for determining a physical layer sidelink synchronization identifier based on a first sidelink identifier and a second sidelink identifier of the other sidelink device. For example, the sidelink identifier determination circuit 1542 may determine a physical layer sidelink synchronization identifier based on a first sidelink identifier and a second sidelink identifier of the second sidelink device. and To calculate the physical layer identifier. In some examples, the sidelink identifier determination circuit 1542 may also be configured to execute the sidelink identifier determination software 1552 included in the computer-readable medium 1506 to implement one or more functions described herein.

[0262] The side link identifier determination circuit 1542 corresponds to Fig.11 . In some examples, the side link identifier determination circuit 1542 can be configured to derive a first side link identifier and a second side link identifier of the side link device from the S-PSS and the S-SSS. In some examples, the side link identifier determination circuit 1542 can be configured to determine the first side link identifier and / or the second side link identifier of the side link device. For example, the side link identifier determination circuit 1542 can determine and

[0263] Processor 1504 may include DMRS information determination circuit 1543 configured to perform DMRS information determination related operations as discussed herein (e.g., in conjunction with Figure 8-11 In some examples, the DMRS information determination circuit 1543 may include the functionality of a device for determining an initialization parameter. In some examples, the DMRS information determination circuit 1543 may include the functionality of a device for determining a scaling parameter. In some examples, the DMRS information determination circuit 1543 may include the functionality of a device for determining DMRS information. In some examples, the DMRS information determination circuit 1543 may also be configured to execute DMRS information determination software 1553 included on the computer-readable medium 1506 to implement one or more functions described herein.

[0264] In some examples, the DMRS information determination circuit 1543 may correspond to the above combined Fig.11 DMRS information determination circuit 1104 described. In some examples, DMRS information determination circuit 1543 can be configured to determine DMRS information based on the first side link identifier and the second side link identifier.

[0265] Processor 1504 may include decoding circuitry 1544 configured to perform decoding-related operations as discussed herein (e.g., in conjunction with Figure 8-11 In some examples, decoding circuitry 1544 may include functionality of a device for decoding a signal. In some examples, decoding circuitry 1544 may also be configured to execute decoding software 1554 included on computer-readable medium 1506 to implement one or more functions described herein.

[0266] The decoding circuit 1544 may correspond to the above combined Fig.11 Decoding circuit 1106 described. In some examples, decoding circuit 1544 can be configured to decode the received broadcast signal based on DMRS information.

[0267] Processor 1504 may include sidelink timing synchronization circuitry 1545 configured to perform sidelink synchronization related operations as discussed herein (e.g., in conjunction with Figure 8-11 In some examples, the sidelink timing synchronization circuit 1545 may include functionality of a device for synchronizing with a sidelink device. In some examples, the sidelink timing synchronization circuit 1545 may also be configured to execute sidelink timing synchronization software 1555 included on the computer-readable medium 1506 to implement one or more functions described herein.

[0268] The side link timing synchronization circuit 1545 may correspond to the above combined Fig.11 Synchronization circuit 1108 described. In some examples, sidelink timing synchronization circuit 1545 can be configured to synchronize with the sidelink device based on broadcast channel information.

[0269] Fig.16 1 is a flow chart of a method 1600 for wireless communication via a sidelink carrier. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for all example implementations. In some examples, as described above and in Fig.15 As shown in FIG. 1 , the method may be performed by the sidelink device 1500 , by a processor or a processing system or by any suitable means for performing the described functions.

[0270] At block 1602, a first side link device may receive a broadcast signal from a second side link device. Fig.15 As shown and described, the communication and processing circuitry 1541 and transceiver 1510 may monitor designated resources (eg, PSSCH) for signals broadcast by any nearby sidelink devices.

[0271] At block 1604, the first side link device may determine at least one of an initialization parameter based at least on the first side link identifier of the second side link device, at least one scaling parameter based at least on the second side link identifier of the second side link device, or a combination thereof. Fig.15 The DMRS information determination circuit 1543 shown and described may be based on Calculate c initAs another example, the DMRS information determination circuit 1543 may be based on Calculate the scaling parameters as discussed in this article.

[0272] In some examples, the first side link identifier is a first value from a set of values ​​from 0 to N. In some examples, the second side link identifier is 0 or 1.

[0273] At block 1606, the first side link device may determine demodulation reference signal (DMRS) information using at least one of the initialization parameter, at least one scaling parameter, or a combination thereof. For example, the DMRS information determination circuit 1543 may determine the demodulation reference signal (DMRS) information based on c init and / or scaling parameters to generate a sequence, and then generate a DMRS based on the sequence.

[0274] In some examples, determining the DMRS information may include determining an initialization parameter based at least on the first side link identifier, and determining the DMRS information may include generating the DMRS information using the initialization parameter.

[0275] In some examples, determining the DMRS information may include determining an initialization parameter based at least on the first side link identifier, initializing a sequence generator with the initialization parameter, generating a pseudo-random sequence using the sequence generator, and generating the DMRS information from the pseudo-random sequence.

[0276] In some examples, determining the DMRS information may include generating a sequence, determining at least one scaling parameter based at least on the second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS information.

[0277] In some examples, determining the DMRS information can include generating a sequence, determining a frequency domain cover code based on at least the second side link identifier, and applying the frequency domain cover code to the sequence to generate the DMRS information. In some examples, the cover code is an orthogonal cover code.

[0278] In some examples, determining DMRS information may include determining an initialization parameter based at least on a first side link identifier, generating a sequence using the initialization parameter, determining at least one scaling parameter based at least on a second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS information.

[0279] In some examples, determining DMRS information can include determining an initialization parameter based at least on a first side link identifier, initializing a sequence generator with the initialization parameter, generating a pseudo-random sequence using the sequence generator, generating a first sequence from the pseudo-random sequence, determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier, and applying the frequency domain OCC to the first sequence to generate the DMRS information.

[0280] At block 1608, the first side link device may decode the broadcast signal using (e.g., based on) the DMRS information to obtain the broadcast channel information. Fig.15 As shown and described, decoding circuitry 1544 in conjunction with communication and processing circuitry 1541 and transceiver 1510 may receive a broadcast signal and perform a decoding operation on the broadcast signal using the DMRS information as an input to the decoding operation.

[0281] At block 1610, the first side link device may synchronize with the second side link device using (e.g., based on) the broadcast channel information. Fig.15 As shown and described, the sidelink timing synchronization circuit 1545 can adjust the timing for communicating with the second sidelink device based on the timing of the broadcast information.

[0282] In some examples, method 1600 may also include receiving a primary synchronization signal and a secondary synchronization signal from a second side link device. In some examples, determining the first side link identifier may include deriving the first side link identifier from the secondary synchronization signal. In some examples, determining the second side link identifier may include deriving the second side link identifier from the primary synchronization signal.

[0283] In some examples, method 1600 may also include determining a physical layer side link synchronization identifier of a second side link device based on the first side link identifier and the second side link identifier. In some examples, method 1600 may also include communicating with the second side link device using the physical layer side link synchronization identifier.

[0284] Fig.17 1700 is a flow chart of a method 1700 for wireless communication via a sidelink carrier. As described below, some or all of the features shown may be omitted in certain implementations within the scope of the present invention, and some of the features shown may not be required for all example implementations. In some examples, the method may be performed by the sidelink device 1500, as described above and in Fig.15 As shown, by a processor or processing system or by any suitable means for performing the functions described.

[0285] At block 1702, a first side link device may receive a broadcast signal from a second side link device. Fig.15 As shown and described, the communication and processing circuitry 1541 and transceiver 1510 may monitor designated resources (eg, PSSCH) for signals broadcast by any nearby sidelink devices.

[0286] At block 1704, the first side link device may determine a first side link identifier of the second side link device. In some examples, the first side link identifier is a first value in a set of values ​​from 0 to N. For example, as described above in conjunction with Fig.15 As shown and described, the side link identifier determination circuit 1542 can process the received synchronization signal to determine the side link identifier associated with the signal.

[0287] At block 1706, the first side link device may determine a second side link identifier for the second side link device. In some examples, the second side link identifier is 0 or 1. For example, as described above in conjunction with Fig.15 As shown and described, the side link identifier determination circuit 1542 can process the received synchronization signal to determine the side link identifier associated with the signal.

[0288] At block 1708, the first sidelink device may determine demodulation reference signal (DMRS) information using (e.g., based on) the first sidelink identifier and the second sidelink identifier. Fig.15 As shown and described, the DMRS information determination circuit 1543 can be based on Calculate c init And based on The scaling parameters are calculated as discussed herein.The DMRS information determination circuit 1543 may then generate a sequence based on these values ​​and generate a DMRS based on the sequence.

[0289] In some examples, determining the DMRS information may include determining an initialization parameter based on at least the first side link identifier and generating the DMRS information using the initialization parameter.

[0290] In some examples, determining the DMRS information may include determining an initialization parameter based at least on the first side link identifier, initializing a sequence generator with the initialization parameter, generating a pseudo-random sequence using the sequence generator, and generating the DMRS information from the pseudo-random sequence.

[0291] In some examples, determining the DMRS information may include generating a sequence, determining at least one scaling parameter based at least on the second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS information.

[0292] In some examples, determining the DMRS information may include generating a sequence, determining a frequency domain cover code based on at least the second side link identifier, and applying the frequency domain cover code to the sequence to generate the DMRS information. In some examples, the cover code may be an orthogonal cover code.

[0293] In some examples, determining DMRS information can include determining an initialization parameter based at least on a first side link identifier, generating a sequence using (e.g., based on) the initialization parameter, determining at least one scaling parameter based at least on a second side link identifier, and scaling the sequence using the at least one scaling parameter to generate the DMRS information.

[0294] In some examples, determining DMRS information can include determining an initialization parameter based at least on a first side link identifier, initializing a sequence generator with the initialization parameter, generating a pseudo-random sequence using the sequence generator, generating a first sequence from the pseudo-random sequence, determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier, and applying the frequency domain OCC to the first sequence to generate the DMRS information.

[0295] At block 1710, the first side link device may decode the broadcast signal using (e.g., based on) the DMRS information to obtain broadcast channel information. Fig.15 As shown and described, decoding circuitry 1544 in conjunction with communication and processing circuitry 1541 and transceiver 1510 may receive a broadcast signal and perform a decoding operation on the broadcast signal using the DMRS information as an input to the decoding operation.

[0296] At block 1712, the first side link device may synchronize with the second side link device using (e.g., based on) the broadcast channel information. Fig.15 As shown and described, the sidelink timing synchronization circuit 1545 can adjust the timing for communicating with the second sidelink device based on the timing of the broadcast information.

[0297] In some examples, method 1700 may also include receiving a primary synchronization signal and a secondary synchronization signal from a second side link device. In some examples, determining the first side link identifier may include deriving the first side link identifier from the secondary synchronization signal. In some examples, determining the second side link identifier may include deriving the second side link identifier from the primary synchronization signal.

[0298] Fig.18 1 is a flow chart of a method 1800 for wireless communication via a sidelink carrier. As described below, some or all of the features shown may be omitted in certain implementations within the scope of the present invention, and some of the features shown may not be required for all example implementations. In some examples, the method may be performed by the sidelink device 1500, as described above and in Fig.15 As shown, by a processor or processing system or by any suitable means for performing the functions described.

[0299] At block 1802, the sidelink device may derive a first sidelink identifier from the primary synchronization signal. Fig.15 As shown and described, the side link identifier determination circuit 1542 can process the received synchronization signal to determine the side link identifier associated with the signal.

[0300] At block 1804, the sidelink device may derive a second sidelink identifier from the secondary synchronization signal. Fig.15 As shown and described, the side link identifier determination circuit 1542 can process the received synchronization signal to determine the side link identifier associated with the signal.

[0301] Fig.19 1 is a flow chart of a method 1900 for wireless communication via a sidelink carrier. As described below, some or all of the features shown may be omitted in certain implementations within the scope of the present invention, and some of the features shown may not be required for all example implementations. In some examples, the method may be performed by the sidelink device 1500, as described above and in Fig.15 As shown, by a processor or processing system or by any suitable means for performing the functions described.

[0302] At block 1902, the first side link device may determine a physical layer side link synchronization identifier of the second side link device based on the first side link identifier and the second side link identifier. Fig.15 As shown and described, the side link identifier determination circuit 1542 can be based on the second side link device and Calculate the physical layer identifier.

[0303] At block 1904, the first side link device may communicate with the second side link device using (e.g., based on) a physical layer side link synchronization identifier. Fig.15 As shown and described, the communication and processing circuit 1541 and the transceiver 1510 may encode signals transmitted to the second side-link device and / or decode signals received from the second side-link device based on the physical layer identifier.

[0304] The following provides a summary of several aspects of the invention.

[0305] Aspect 1: A method for wireless communication at a first side link device, the method comprising: determining at least one of an initialization parameter based on at least a first side link identifier of the first side link device, at least one scaling parameter based on at least a second side link identifier of the first side link device, or a combination thereof; generating a demodulation reference signal (DMRS) using the initialization parameter, at least one scaling parameter, or at least one of the combinations thereof; and sending the DMRS to a second side link device.

[0306] Aspect 2: The method according to aspect 1, wherein generating the DMRS comprises: initializing a sequence generator with an initialization parameter; generating a pseudo-random sequence using the sequence generator; and generating the DMRS from the pseudo-random sequence.

[0307] Aspect 3: The method according to aspect 2, wherein determining the initialization parameter is further based on a configuration value, a preconfigured value or a defined value.

[0308] Aspect 4: The method according to any one of aspects 1 to 3, wherein generating the DMRS comprises: generating a sequence; and scaling the sequence using at least one scaling parameter to generate the DMRS.

[0309] Aspect 5: The method according to aspect 4, wherein at least one scaling parameter comprises a frequency domain cover code.

[0310] Aspect 6: The method according to aspect 5, wherein the cover code is an orthogonal cover code.

[0311] Aspect 7: A method according to any one of Aspects 4 to 6, wherein generating DMRS comprises: determining parameters of a sequence generator; initializing the sequence generator using the parameters; generating a pseudo-random sequence using the sequence generator; and generating DMRS from the pseudo-random sequence.

[0312] Aspect 8: A method according to any one of Aspects 4 to 7, wherein generating DMRS includes: receiving parameters for a sequence generator through a radio resource control (RRC) message; initializing the sequence generator using the parameters; generating a pseudo-random sequence using the sequence generator; and generating DMRS from the pseudo-random sequence.

[0313] Aspect 9: A method according to any one of Aspects 1 to 8, wherein generating DMRS includes: initializing a sequence generator using initialization parameters; generating a pseudo-random sequence using the sequence generator; generating a first sequence from the pseudo-random sequence; determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier; and applying the frequency domain OCC to the first sequence to generate DMRS.

[0314] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: determining a physical layer side link synchronization identifier of the first side link device based on the first side link identifier and the second side link identifier.

[0315] Aspect 11: A method according to any one of Aspects 1 to 10, wherein: the first side link identifier is a first value in a group of values ​​from 0 to N; and the second side link device identifier is 0 or 1.

[0316] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: initializing a sequence generator using an initialization parameter; generating a pseudo-random sequence using the sequence generator; and generating a DMRS from the pseudo-random sequence.

[0317] Aspect 14: The method according to any one of Aspects 1 to 13, further comprising determining an initialization parameter based on a configuration value, a preconfigured value or a defined value.

[0318] Aspect 15: The method according to any one of aspects 1 to 14, further comprising: generating a sequence; and scaling the sequence using at least one scaling parameter to generate a DMRS.

[0319] Aspect 16: A method for performing wireless communication at a first side link device, the method comprising: receiving a broadcast signal from a second side link device; determining at least one of an initialization parameter based at least on a first side link identifier of the second side link device, at least one scaling parameter based at least on a second side link identifier of the second side link device, or a combination thereof; using the initialization parameter, at least one scaling parameter, or at least one combination thereof to determine demodulation reference signal (DMRS) information; using the DMRS information to decode the broadcast signal to obtain broadcast channel information; and synchronizing with the second side link device using the broadcast channel information.

[0320] Aspect 17: The method according to Aspect 16 also includes receiving a primary synchronization signal and a secondary synchronization signal from a second side link device, wherein: determining the first side link identifier includes deriving the first side link identifier from the secondary synchronization signal; and determining the second side link identifier includes deriving the second side link identifier from the primary synchronization signal.

[0321] Aspect 18: The method according to any one of aspects 16 to 17, wherein determining the DMRS information comprises: determining an initialization parameter based at least on the first side link identifier; and generating the DMRS information using the initialization parameter.

[0322] Aspect 19: A method according to any one of Aspects 16 to 18, wherein determining DMRS information includes: determining an initialization parameter based at least on a first side link identifier; initializing a sequence generator using the initialization parameter; generating a pseudo-random sequence using the sequence generator; and generating DMRS information from the pseudo-random sequence.

[0323] Aspect 20: A method according to any one of Aspects 16 to 19, wherein determining DMRS information comprises: generating a sequence; determining at least one scaling parameter based at least on the second side link identifier; and scaling the sequence using the at least one scaling parameter to generate the DMRS information.

[0324] Aspect 21: A method according to any one of Aspects 16 to 20, wherein determining DMRS information comprises: generating a sequence; determining a frequency domain cover code based at least on a second side chain identifier; and applying the frequency domain cover code to the sequence to generate DMRS information.

[0325] Aspect 22: The method according to Aspect 21, wherein the cover code is an orthogonal cover code.

[0326] Aspect 23: A method according to any one of Aspects 16 to 22, wherein determining DMRS information includes: determining an initialization parameter based at least on a first side link identifier; generating a sequence using the initialization parameter; determining at least one scaling parameter based at least on a second side link identifier; and scaling the sequence using at least one scaling parameter to generate DMRS information.

[0327] Aspect 24: A method according to any one of Aspects 16 to 23, wherein determining DMRS information includes: determining an initialization parameter based at least on a first side link identifier; initializing a sequence generator using the initialization parameter; generating a pseudo-random sequence using the sequence generator; generating a first sequence from the pseudo-random sequence; determining a frequency domain orthogonal cover code (OCC) based at least on a second side link identifier; and applying the frequency domain OCC to the first sequence to generate DMRS information.

[0328] Aspect 25: The method according to any one of Aspects 16 to 24 further includes: determining a physical layer side link synchronization identifier of a second side link device based on the first side link identifier and the second side link identifier; and communicating with the second side link device using the physical layer side link synchronization identifier.

[0329] Aspect 26: A method according to any one of Aspects 16 to 25, wherein: the first side link identifier is a first value in a group of values ​​from 0 to N; and the second side link device identifier is 0 or 1.

[0330] Aspect 29: The method according to any one of Aspects 16 to 28 further includes: determining an initialization parameter based at least on the first side link identifier; and generating DMRS information using the initialization parameter.

[0331] Aspect 30: The method according to any one of Aspects 16 to 29 further includes: determining an initialization parameter based at least on the first side link identifier; initializing a sequence generator using the initialization parameter; generating a pseudo-random sequence using the sequence generator; and generating DMRS information from the pseudo-random sequence.

[0332] Aspect 31: A sidelink device comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1 to 15.

[0333] Aspect 32: An apparatus configured for wireless communication, comprising at least one apparatus for performing any one of Aspects 1 to 15.

[0334] Aspect 33: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform any one of aspects 1 to 15.

[0335] Aspect 34: A sidelink device comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 16 to 30.

[0336] Aspect 35: An apparatus configured for wireless communication, comprising at least one apparatus for performing any one of aspects 16 to 30.

[0337] Aspect 36: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform any one of aspects 16 to 30.

[0338] Several aspects of wireless communication networks have been presented with reference to example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0339] For example, various aspects may be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0340] In this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "various aspects" does not require that all aspects of the disclosure include the discussed features, advantages, or modes of operation. The term "coupled," as used herein, refers to a direct or indirect coupling between two objects. For example, if object A is in physical contact with object B, and object B is in contact with object C, objects A and C may still be considered to be coupled to each other - even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, are capable of performing the functions described in the present invention without limitation to the type of electronic circuitry, as well as software implementations of information and instructions that, when executed by a processor, are capable of performing the functions described in the present invention.

[0341] exist Figure 1-Figure 19 One or more components, steps, features and / or functions shown in the present invention may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. Additional elements, components, steps and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figure 6 , Figure 8-Figure 12 or Fig.15 The apparatus, device and / or component shown in any one of the above may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0342] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of example processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in an example order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0343] The foregoing description is provided to enable any person skilled in the art to practice 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 various aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless otherwise specified, but "one or more". Unless otherwise explicitly stated, the term "some" refers to one or more. The "at least one" phrase referring to a list of items refers to any combination of these items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described in the present invention are known or will be known to those of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is clearly recorded in the claims.

Claims

1. A method for wireless communication at a first side-link device, the method comprising: Sending a sidelink secondary synchronization signal S-SSS based on a first sidelink identifier of the first sidelink; Sending a sidelink primary synchronization signal S-PSS based on a second sidelink identifier of the first sidelink; determining at least one of an initialization parameter based at least on the first side link identifier of the first side link device, at least one scaling parameter based at least on the second side link identifier of the first side link device, or a combination thereof; generating a demodulation reference signal DMRS using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; as well as The DMRS is sent to the second side-link device.

2. The method according to claim 1, wherein: Generating DMRS includes: Initialize the sequence generator using initialization parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS is generated from a pseudo-random sequence.

3. The method according to claim 2, wherein: Determining the initialization parameter is further based on a configured value, a preconfigured value, or a defined value.

4. The method according to claim 1, wherein: Generating DMRS includes: Generate a sequence; and The sequence is scaled using at least one scaling parameter to generate a DMRS.

5. The method according to claim 4, wherein: The at least one scaling parameter comprises a frequency domain cover code.

6. The method according to claim 5, wherein: The cover codes are orthogonal cover codes.

7. The method according to claim 1, wherein: Generating DMRS includes: Determine the parameters of the sequence generator; Initialize the sequence generator with the parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS is generated from a pseudo-random sequence.

8. The method according to claim 1, wherein: Generating DMRS includes: receiving parameters for a sequence generator via a radio resource control, RRC, message; Initialize the sequence generator with the parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS is generated from a pseudo-random sequence.

9. The method according to claim 1, wherein: Generating DMRS includes: Initialize the sequence generator using initialization parameters; Generate a pseudo-random sequence using a sequence generator; generating a first sequence from a pseudo-random sequence; determining a frequency domain orthogonal cover code OCC based at least on the second side link identifier; and The frequency domain OCC is applied to the first sequence to generate a DMRS.

10. The method according to claim 1, further comprising: A physical layer sidelink synchronization identifier of the first sidelink device is determined based on the first sidelink identifier and the second sidelink identifier.

11. The method according to claim 1, wherein: The first sidelink identifier is a first value in a set of values ​​from 0 to N; and The second side link identifier is 0 or 1.

12. A first side link device, comprising: Transceiver; Memory; as well as A processor is communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: Sending a sidelink secondary synchronization signal S-SSS based on a first sidelink identifier of the first sidelink; Sending a sidelink primary synchronization signal S-PSS based on a second sidelink identifier of the first sidelink; determining at least one of an initialization parameter based at least on the first side link identifier of the first side link device, at least one scaling parameter based at least on the second side link identifier of the first side link device, or a combination thereof; generating a demodulation reference signal DMRS using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; and The DMRS is sent to the second side-link device.

13. The first side link device according to claim 12, wherein: The processor and memory are further configured to: Initialize the sequence generator using initialization parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS is generated from a pseudo-random sequence.

14. The first side link device according to claim 13, wherein: The processor and memory are further configured to: Determines initialization parameters based on configured values, preconfigured values, or defined values.

15. The first side link device according to claim 12, wherein: The processor and memory are further configured to: Generate a sequence; and The sequence is scaled using at least one scaling parameter to generate a DMRS.

16. A method for wireless communication at a first side-link device, the method comprising: receiving a sidelink secondary synchronization signal S-SSS and determining a first sidelink identifier, wherein the first sidelink identifier is derived from the S-SSS; receiving a sidelink primary synchronization signal, S-PSS, and determining a second sidelink identifier, wherein the second sidelink identifier is derived from at least one of the S-PSS and S-SSS; receiving a broadcast signal from a second side-link device; determining at least one of an initialization parameter based at least on the first side link identifier of a second side link device, at least one scaling parameter based at least on the second side link identifier of a second side link device, or a combination thereof; Determine demodulation reference signal (DMRS) information using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; decoding the broadcast signal using the DMRS information to obtain broadcast channel information; and Synchronize with the second side-link device using the broadcast channel information.

17. The method according to claim 16, further comprising: The primary synchronization signal and the secondary synchronization signal are received from a second side-link device.

18. The method according to claim 16, wherein: Determine the DMRS information including: determining an initialization parameter based at least on the first side link identifier; and Generate DMRS information using initialization parameters.

19. The method according to claim 16, wherein: Determine the DMRS information including: determining an initialization parameter based at least on the first side link identifier; Initialize the sequence generator using initialization parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS information is generated from a pseudo-random sequence.

20. The method according to claim 16, wherein: Determine the DMRS information including: Generate a sequence; determining at least one scaling parameter based at least on the second side link identifier; and The sequence is scaled using at least one scaling parameter to generate DMRS information.

21. The method according to claim 16, wherein: Determine the DMRS information including: Generate a sequence; determining a frequency domain cover code based at least on the second side link identifier; and A frequency domain cover code is applied to the sequence to generate DMRS information.

22. The method according to claim 21, wherein: The cover codes are orthogonal cover codes.

23. The method according to claim 16, wherein: Determine the DMRS information including: determining an initialization parameter based at least on the first side link identifier; Generate a sequence using initialization parameters; determining at least one scaling parameter based at least on the second side link identifier; and The sequence is scaled using at least one scaling parameter to generate DMRS information.

24. The method according to claim 16, wherein: Determine the DMRS information including: determining an initialization parameter based at least on the first side link identifier; Initialize the sequence generator using initialization parameters; Generate a pseudo-random sequence using a sequence generator; generating a first sequence from a pseudo-random sequence; determining a frequency domain orthogonal cover code OCC based at least on the second side link identifier; and The frequency domain OCC is applied to the first sequence to generate DMRS information.

25. The method of claim 16, further comprising: determining a physical layer side link synchronization identifier of a second side link device based on the first side link identifier and the second side link identifier; as well as Communicate with the second sidelink device using the physical layer sidelink synchronization identifier.

26. The method of claim 16, wherein: The first sidelink identifier is a first value in a set of values ​​from 0 to N; and The second side link identifier is 0 or 1.

27. A first side link device, comprising: Transceiver; Memory; as well as A processor is communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving a sidelink secondary synchronization signal S-SSS and determining a first sidelink identifier, wherein the first sidelink identifier is derived from the S-SSS; receiving a sidelink primary synchronization signal, S-PSS, and determining a second sidelink identifier, wherein the second sidelink identifier is derived from at least one of the S-PSS and S-SSS; receiving a broadcast signal from a second side-link device; determining at least one of an initialization parameter based at least on the first side link identifier of a second side link device, at least one scaling parameter based at least on the second side link identifier of a second side link device, or a combination thereof; Determine demodulation reference signal (DMRS) information using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; decoding the broadcast signal using the DMRS information to obtain broadcast channel information; and synchronizing with the second sidelink device using the broadcast channel information.

28. The first side-link device of claim 27, wherein: The processor and memory are further configured to: The primary synchronization signal and the secondary synchronization signal are received from a second side-link device.

29. The first side-link device of claim 27, wherein: The processor and memory are further configured to: determining an initialization parameter based at least on the first side link identifier; and Generate DMRS information using initialization parameters.

30. The first side-link device of claim 27, wherein: The processor and memory are further configured to: determining an initialization parameter based at least on the first side link identifier; Initialize the sequence generator using initialization parameters; generating a pseudo-random sequence using a sequence generator; and The DMRS information is generated from a pseudo-random sequence.

31. An apparatus configured for wireless communication at a first side-link device, the apparatus comprising: means for sending a sidelink secondary synchronization signal S-SSS based on a first sidelink identifier of the first sidelink; means for transmitting a sidelink primary synchronization signal S-PSS based on a second sidelink identifier of the first sidelink; means for determining at least one of an initialization parameter based at least on the first side link identifier of the first side link device, at least one scaling parameter based at least on the second side link identifier of the first side link device, or a combination thereof; means for generating a demodulation reference signal DMRS using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; as well as Means for sending the DMRS to a second side-link device.

32. A non-transitory computer readable medium storing computer executable code, comprising code for causing an apparatus to: Sending a sidelink secondary synchronization signal S-SSS based on a first sidelink identifier of the first sidelink; Sending a sidelink primary synchronization signal S-PSS based on a second sidelink identifier of the first sidelink; determining at least one of an initialization parameter based at least on the first side link identifier of the first side link device, at least one scaling parameter based at least on the second side link identifier of the first side link device, or a combination thereof; generating a demodulation reference signal DMRS using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; as well as The DMRS is sent to the second side-link device.

33. An apparatus configured for wireless communication at a first side-link device, the apparatus comprising: means for receiving a sidelink secondary synchronization signal, S-SSS, and determining a first sidelink identifier, wherein the first sidelink identifier is derived from the S-SSS; means for receiving a sidelink primary synchronization signal, S-PSS, and determining a second sidelink identifier, wherein the second sidelink identifier is derived from at least one of the S-PSS and the S-SSS; means for receiving a broadcast signal from a second side-link device; means for determining at least one of an initialization parameter based at least on the first side link identifier of a second side link device, at least one scaling parameter based at least on the second side link identifier of a second side link device, or a combination thereof; means for determining demodulation reference signal (DMRS) information using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; means for decoding the broadcast signal using the DMRS information to obtain broadcast channel information; and Means for synchronizing with a second side-link device using the broadcast channel information.

34. A non-transitory computer readable medium storing computer executable code, comprising code for causing an apparatus to: receiving a sidelink secondary synchronization signal S-SSS and determining a first sidelink identifier, wherein: the first sidelink identifier is derived from the S-SSS; receiving a sidelink primary synchronization signal, S-PSS, and determining a second sidelink identifier, wherein the second sidelink identifier is derived from at least one of the S-PSS and S-SSS; receiving a broadcast signal from a second side-link device; determining at least one of an initialization parameter based at least on the first side link identifier of a second side link device, at least one scaling parameter based at least on the second side link identifier of a second side link device, or a combination thereof; Determine demodulation reference signal (DMRS) information using at least one of an initialization parameter, at least one scaling parameter, or a combination thereof; decoding the broadcast signal using the DMRS information to obtain broadcast channel information; and Synchronize with the second side-link device using the broadcast channel information.

Images