Priority of sidelink reference signal transmissions

Abstract

A first wireless device transmits, to a second wireless device, SL control information indicating a priority of SL transmissions including sidelink (SL) data and at least one SL reference signal (RS). The priority is based on a first priority of the at least one SL RS and a second priority of the SL data.

Description

Cross-reference to related applications

[0001] This application claims the benefits of U.S. Provisional Application No. 63 / 457,764, filed April 6, 2023, and U.S. Provisional Application No. 63 / 457,835, filed April 7, 2023, both of which are incorporated herein by reference in their entirety. Attached Figure Description

[0002] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0003] FIG. 1A and FIG. 1B An example mobile communication network in which embodiments of the present disclosure may be implemented is shown.

[0004] FIG. 2A and FIG. 2B The protocol stacks for the New Radio (NR) user plane and control plane are shown respectively.

[0005] FIG. 3 It shows in FIG. 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0006] FIG. 4A It shows the flow through FIG. 2A Example downlink data stream of the NR user plane protocol stack.

[0007] FIG. 4B This shows an example format of the MAC subheader in a MAC PDU.

[0008] FIG. 5 A and FIG. 5 B illustrates the mappings between logical channels, transport channels, and physical channels used for downlink and uplink, respectively.

[0009] FIG. 6 This is an example diagram illustrating the RRC state transition of the UE.

[0010] FIG. 7 An example configuration is shown in which OFDM symbols are grouped into NR frames.

[0011] FIG. 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown.

[0012] FIG. 9 Three examples of bandwidth adaptation using NR carriers with configured BWPs are shown.

[0013] FIG. 10A Three carrier aggregation configurations with two component carriers are shown.

[0014] FIG. 10B An example is shown of how aggregated cells can be configured into one or more PUCCH groups.

[0015] FIG. 11A An example of the SS / PBCH block structure and location is shown.

[0016] FIG. 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0017] FIG. 12A and FIG. 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0018] FIG. 13A , FIG. 13B and FIG. 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

[0019] FIG. 14A An example of the CORESET configuration for the bandwidth portion is shown.

[0020] FIG. 14B An example of CCE-to-REG mapping for DCI transport is shown on CORESET and PDCCH processing.

[0021] FIG. 15 An example of a wireless device communicating with a base station is shown.

[0022] FIG. 16A , FIG. 16B , FIG. 16C and FIG. 16D An example structure for uplink and downlink transmission is shown.

[0023] FIG. 17 An example of device-to-device (D2D) communication according to an exemplary embodiment of the present disclosure is shown.

[0024] FIG. 18 An example of a resource pool for sidelink operation is shown, according to an exemplary embodiment of the present disclosure.

[0025] FIG. 19 An example of a sidelink symbol in a time slot is shown according to an exemplary embodiment of the present disclosure.

[0026] FIG. 20 An example of resource indication for a first TB (e.g., a first data packet) and resource reservation for a second TB (e.g., a second data packet) is shown according to an exemplary embodiment of the present disclosure.

[0027] FIG. 21 An example of configuration information for sidelink communication is shown according to an exemplary embodiment of the present disclosure.

[0028] FIG. 22 An example of configuration information for sidelink communication is shown according to an exemplary embodiment of the present disclosure.

[0029] FIG. 23 An example format of the MAC subheader for a sidelink shared channel (SL-SCH) according to an exemplary embodiment of the present disclosure is shown.

[0030] FIG. 24 An example time of a resource selection procedure according to an exemplary embodiment of the present disclosure is shown.

[0031] FIG. 25 An example timing of a resource selection procedure according to an exemplary embodiment of the present disclosure is shown.

[0032] FIG. 26 An example flowchart of a resource selection procedure for transmitting a TB via a sidelink by a wireless device is shown, according to an example embodiment of the present disclosure.

[0033] FIG. 27 An example diagram is shown of a resource selection procedure in each layer of a wireless device according to an exemplary embodiment of the present disclosure.

[0034] FIG. 28 An example of a sidelink CSI-RS transmission and sidelink CSI reporting procedure according to an exemplary embodiment of the present disclosure is shown.

[0035] FIG. 29 An example of resource allocation for SL CSI RS according to an exemplary embodiment of this disclosure is shown.

[0036] FIG. 30 An example of an SL CSI report according to an exemplary embodiment of this disclosure is shown.

[0037] FIG. 31A An example of an SL RS according to an exemplary embodiment of the present disclosure is shown.

[0038] FIG. 31B An example of an SL RS according to an exemplary embodiment of the present disclosure is shown.

[0039] FIG. 32A An example of SL RS transmission according to an exemplary embodiment of this disclosure is shown.

[0040] FIG. 32B An example of SL RS transmission according to one aspect of an embodiment of this disclosure is shown.

[0041] FIG. 33 An example of the priority of sidelink transmissions according to an exemplary embodiment of the present disclosure is shown.

[0042] FIG. 34A An example embodiment of one aspect of an example embodiment according to the present disclosure is shown.

[0043] FIG. 34B An example embodiment of one aspect of an example embodiment according to the present disclosure is shown.

[0044] FIG. 35 An example embodiment of one aspect of an example embodiment according to the present disclosure is shown. Detailed Implementation

[0045] In this disclosure, various embodiments are presented as examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail can be made therein without departing from the scope of the invention. Indeed, alternative embodiments will be apparent to those skilled in the art upon reading the specification. The embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of this disclosure. Any figures highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in a flowchart can be reordered or used only optionally in certain embodiments.

[0046] Implementations can be configured to operate as needed. For example, the disclosed mechanisms can be executed in wireless devices, base stations, radio environments, networks, combinations thereof, etc., when certain criteria are met. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various example implementations can be applied when one or more criteria are met. Therefore, example implementations that selectively implement the disclosed protocols can be implemented.

[0047] A base station can communicate with a mixture of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have certain specific capabilities, depending on the wireless device category and / or capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure can refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure can mean multiple wireless devices having a given capability and in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure can refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0048] In this disclosure, “a (a)” and “an (an)” and similar phrases will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on” rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0049] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depending on" (or equivalently "at least depending on") indicates that the phrase following the phrase "depending on" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase following the phrase "adopting / using" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments.

[0050] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control message generated in the device" can mean that the control message has parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0051] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In an example embodiment, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0052] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the set of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0053] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has the defined interface to other elements. Modules described in this disclosure can be implemented as hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality on the programmable device. The aforementioned techniques are often used in combination to achieve the desired result of functional modules.

[0054] FIG. 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 100 may be, for example, a Public Land Mobile Network (PLMN) operated by a network operator. FIG. 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a radio device 106.

[0055] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functions, CN 102 can establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0056] RAN 104 can connect CN 102 to radio device 106 via radio communication through an air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplexing technologies.

[0057] The term "wireless device" is used throughout this disclosure to mean and cover any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, and / or any combination thereof. The term "wireless device" also encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0058] RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associating with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the donor Node; Next Generation Evolved Node B (ng-eNB); First Generation Node B (gNB, associating with NR and / or 5G standards); Access Point (AP, associating with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

[0059] The base stations included in RAN 104 may contain one or more sets of antennas for communicating with wireless device 106 via an air interface. For example, one or more base stations may contain three sets of antennas to control three cells (or sectors) respectively. The size of a cell may be determined by the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating within the cell. The cells of the base stations may together provide radio coverage over a wide geographical area to wireless device 106 to support wireless device mobility.

[0060] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeater or relay nodes for extending the coverage area of ​​the donor node. The baseband processing unit coupled to the RRH can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0061] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas where macrocell coverage is weak. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0062] The Third Generation Partnership Project (3GPP) was established in 1998 to facilitate collaboration with... FIG. 1AThe mobile communication network 100 in the text provides global standardization specifications for similar mobile communication networks. To date, 3GPP has defined specifications for three generations of mobile networks: the third-generation (3G) network known as Universal Mobile Telecommunications System (UMTS), the fourth-generation (4G) network known as Long Term Evolution (LTE), and the fifth-generation (5G) network known as 5G System (5GS). Embodiments of this disclosure are described with reference to the RAN of the 3GPP 5G network, known as Next Generation RAN (NG-RAN). These embodiments can be applied to the RAN of other mobile communication networks, such as... FIG. 1A RAN 104, the RAN of early 3G and 4G networks, and those RANs of future networks that have not yet been specified (e.g., 3GPP 6G networks). NG-RAN implements 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0063] FIG. 1B Another example mobile communication network 150 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. FIG. 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). This can be compared with... FIG. 1A These components are implemented and operated in the same or similar manner as the corresponding components described.

[0064] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of its interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functionality. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0065] like FIG. 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in FIG. 1BThese are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to the one or more DNs, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnecting with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0066] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., paging retransmission control and execution), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0067] 5G-CN 152 can be included for clarity. FIG. 1B One or more additional network functions not shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Open Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0068] NG-RAN 154 can connect 5G-CN 152 to UE 156 via radio communication over an air interface. NG-RAN 154 may include: one or more gNBs, designated gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, designated ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). gNB 160 and ng-eNB 162 may be more generally referred to as base stations. gNB 160 and ng-eNB 162 may include one or more sets of antennas for communicating with UE 156 over the air interface. For example, one or more gNBs in gNB 160 and / or one or more ng-eNBs in ng-eNB 162 may include three sets of antennas to control three cells (or sectors) respectively. The gNB160 and ng-eNB 162 cells can work together to provide UE 156 with radio coverage over a wide geographical area to support UE mobility.

[0069] like FIG. 1B As shown, gNB 160 and / or ng-eNB 162 can connect to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using a direct physical connection and / or an indirect connection via an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... FIG. 1B As shown, the gNB 160A can connect to the UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be... FIG. 1B The network elements in the system are used to exchange data and signaling messages, and can contain two planes: a user plane and a control plane. The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

[0070] The gNB 160 and / or ng-eNB 162 can connect to one or more AMF / UPF functions of the 5G-CN 152, such as AMF / UPF 158, via one or more NG interfaces. For example, the gNB 160A can connect to the UPF 158B of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface can provide user plane PDU delivery (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A can connect to the AMF 158A via an NG control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0071] The gNB 160 can provide NR user plane and control plane protocol termination to the UE 156 via the Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to the UE 156A via the Uu interface associated with the first protocol stack. The ng-eNB 162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to the UE 156 via the Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol termination to the UE 156B via the Uu interface associated with the second protocol stack.

[0072] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although FIG. 1B The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across said multiple AMF / UPF nodes.

[0073] As discussed, FIG. 1B The interfaces between network elements (e.g., Uu, Xn, and NG interfaces) can be associated with the protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can contain two planes: a user plane and a control plane. The user plane handles data of interest to the user, while the control plane handles signaling messages of interest to the network elements.

[0074] FIG. 2A andFIG. 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220 are shown respectively. FIG. 2A and FIG. 2B The protocol stack shown can be used with, for example, FIG. 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown are the same or similar.

[0075] FIG. 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Serving Data Application Protocol (SDAP) 215 and 225. These four protocols together constitute Layer 2 of the OSI model, or the Data Link Layer.

[0076] FIG. 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From FIG. 2A and FIG. 3 Starting from the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and the DN. The PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, SDAP 225 at gNB220 can mark downlink packets with QoS flow indicators (QFIs), which can be observed by SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0077] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicated received packets due to, for example, handover within a gNB. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packets being received and remove any duplicated packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0078] although FIG. 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are split bearers when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapping split radio bearers between RLC channels belonging to a cell group.

[0079] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicated data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on the logical channel, independent of the parameter set and / or Transmission Time Interval (TTI) duration. FIG. 3 As shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

[0080] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority processing between UEs via dynamic scheduling. Scheduling can be performed for downlink and uplink in gNB 220 (at MAC 222). MACs 212 and 222 can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing between logical channels of UE 210 via logical channel priority ordering, and / or padding. MACs 212 and 222 can support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... FIG. 3 As shown, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

[0081] PHYs 211 and 221 can perform transport-to-physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHYs 211 and 221 can perform multi-antenna mapping. For example... FIG. 3 As shown, PHYs 211 and 221 can provide one or more transport channels as services to MACs 212 and 222.

[0082] FIG. 4A An example downlink data flow is shown that passes through the NR user plane protocol stack. FIG. 4A The diagram shows three IP packets flowing through the NR user plane protocol stack to generate two TBs at the gNB 220. n , n+1 and m The downlink data stream. The uplink data stream flowing through the NR user plane protocol stack can be... FIG. 4A The downlink data flow described in the text is similar.

[0083] FIG. 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps these three packets to radio bearers. FIG. 4A In the middle, SDAP 225 will divide IP packets n and n+1Mapped to the first radio bearer 402, and the IP packet is... m Mapped to the second radio bearer 404. SDAP header (in FIG. 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). FIG. 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0084] FIG. 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). FIG. 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). FIG. 4A Regarding IP packets m (As shown) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed across MAC PDUs, such as... FIG. 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

[0085] FIG. 4B The example format of the MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a Logical Channel Identifier (LCID) field identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0086] FIG. 4B The diagram further illustrates the MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, FIG. 4B This shows two MAC CEs inserted into the MAC PDU. Downlink transmissions can be initiated at the beginning of the MAC PDU (e.g., ...). FIG. 4B(As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. MAC CEs can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used for PDCP copy detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information contained in the MAC CE.

[0087] Before describing the NR control plane protocol stack, we will first describe the mapping between logical channels, transport channels, and physical channels, as well as channel types. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack, which will be described later below.

[0088] FIG. 5 A and FIG. 5 B illustrates the mapping between logical channels, transport channels, and physical channels for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example: --Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level; --Broadcast Control Channel (BCCH), which carries system information messages in the form of Master Control Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how it operates within the cell; --Common Control Channel (CCCH), which is used to carry control messages and random access; --Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure the UE; and --Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0089] Transport channels are used between the MAC layer and the PHY layer, and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example: --Paging Channel (PCH), which is used to carry paging messages originating from PCCH; --Broadcast channel (BCH), which is used to carry MIBs from the BCCH; --Downlink Shared Channel (DL-SCH), which carries downlink data and signaling messages, including SIBs from BCCH; --Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and --Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0090] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this control information to lower levels of the PHY via physical control channels (called L1 / L2 control channels). The set of physical channels and physical control channels defined by the NR includes, for example: --Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH; --Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH; --Physical downlink control channel (PDCCH), which carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands; --The Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from the UL-SCH, and in some cases carries uplink control information (UCI) as described below. --Physical Uplink Control Channel (PUCCH), which carries the UCI, which may include HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and --Physical Random Access Channel (PRACH), which is used for random access.

[0091] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... FIG. 5 A and FIG. 5 As shown in B, the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals will be described in more detail below.

[0092] FIG. 2B An example NR control plane protocol stack is shown. FIG. 2B As shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0093] NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 (e.g., AMF 158A) or more generally between UE 210 and CN. NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages known as NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. NAS messages can be transmitted using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0094] RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally between UE 210 and RAN. RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages known as RRC messages. RRC messages can be transmitted between UE 210 and RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC can multiplex control plane and user plane data into the same transport block (TB). RRC 216 and 226 can provide control plane functions such as: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of RRC connections between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of said reports; detection and recovery of radio link failures (RLFs); and / or NAS messaging. As part of establishing an RRC connection, RRC 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0095] FIG. 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... FIG. 1A The wireless device 106 depicted in the text FIG. 2A and FIG. 2B The UE 210 depicted herein is identical or similar to any other wireless device described in this disclosure. FIG. 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0096] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: FIG. 1A The one or more base stations included in RAN 104 as depicted herein; FIG. 1B One of gNB 160 or ng-eNB 162 described herein; FIG. 2A and FIG. 2BThe gNB 220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

[0097] In RRC idle 604, an RRC context may not have been established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. When in RRC idle 604, the UE may be in sleep mode most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The UE's mobility can be managed by the UE through a procedure called cell reselection. The RRC state can be transitioned from RRC idle 604 to RRC connected 602 through connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0098] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connected 602 via connection resumption procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0099] RRC states can be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to notify the UE of events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE currently resides, rather than across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0100] A tracking area can be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0101] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identifiers, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in the RAN notification area assigned to that UE, the UE can perform a notification area update on the RAN to update the UE's RAN notification area.

[0102] The base station storing the RRC context for the UE, or the UE's last serving base station, may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

[0103] gNB, such as FIG. 1BThe gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0104] In NR, physical signals and physical channels (about FIG. 5 A and FIG. 5 The concept discussed in section B can be mapped to Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that uses... F Data is transmitted via orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols or M-PSK symbols), and is divided into... F A parallel symbol stream. F The parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) symbols that transform them to the time domain. An IFFT block can take... F Source symbols (from) F (One source symbol is taken from each of the parallel symbol streams), and each source symbol is used to modulate the signal with... F Corresponding to each orthogonal subcarrier F The amplitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent... F The sum of orthogonal subcarriers F One time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., the addition of a cyclic prefix) and upsampling, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The OFDM symbols can be inversely processed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0105] FIG. 7An example configuration of NR frames in which OFDM symbols are grouped is shown. NR frames can be identified by a System Frame Number (SFN). SFNs can repeat in a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can contain 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, which contain, for example, 14 OFDM symbols per time slot.

[0106] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). The parameter set can be defined in terms of subcarrier spacing and cyclic prefix duration. For the parameter set in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μs by powers of two. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0107] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter time slot durations and correspondingly more time slots per subframe. FIG. 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). FIG. 7 (A parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slots or sub-time slot transmissions.

[0108] FIG. 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown. The time slots contain resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... FIG. 8 As shown in the diagram. RB spans twelve consecutive REs in the frequency domain, as... FIG. 8As shown in the diagram, the NR carrier can be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. If this limitation is used, the NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on a bandwidth limit of 400 MHz per carrier.

[0109] FIG. 8 This illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other example configurations, multiple parameter sets can be supported on the same carrier.

[0110] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth can be prohibitively expensive in terms of UE power consumption. In the example, to reduce power consumption and / or for other purposes, the UE can adjust the size of its receive bandwidth based on the amount of traffic it plans to receive. This is called bandwidth adaptation.

[0111] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive Relay Buses (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0112] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0113] For a set of configured downlink BWPs on the primary cell (PCell), the base station can configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of time-domain and frequency-domain locations where a UE can locate control information. The search space can be a UE-specific search space or a shared search space (potentially usable by multiple UEs). For example, the base station can configure a shared search space for the UE on the PCell or primary / secondary cell (PSCell) within an active downlink BWP.

[0114] For an uplink BWP in the set of configured uplink BWPs, the BS can configure one or more resource sets for the UE to transmit one or more PUCCHs. The UE can receive downlink reception (e.g., PDCCH or PDSCH) in the downlink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix duration) used for the downlink BWP. The UE can transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0115] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields can indicate the active uplink BWP for one or more uplink transmissions.

[0116] The base station can semi-statically configure a default downlink BWP for the UE within a set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to the UE, the default downlink BWP can be the initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0117] The base station can configure the BWP inactivity timer value for the UE using the PCell. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer under the following circumstances: a When the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or ( bWhen the UE detects a DCI (Distributed Indication Code) for unpaired spectrum operation, indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP, the UE can proceed as follows: If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can advance the BWP inactivity timer towards its expiration (e.g., by incrementing from zero to the BWP inactivity timer value, or decrementing from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0118] In the example, the base station can semi-statically configure the UE using one or more BWPs. The UE can switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to the expiration of a BWP inactivity timer (e.g., in the case that the second BWP is the default BWP).

[0119] Downlink and uplink BWP handovers can be performed independently in paired spectrum (where BWP handover refers to switching from the currently active BWP to a non-currently active BWP). In unpaired spectrum, downlink and uplink BWP handovers can be performed simultaneously. Handovers can occur between configured BWPs based on RRC signaling, DCI, the expiration of a BWP inactivity timer, and / or the initiation of random access.

[0120] FIG. 9 An example of bandwidth adaptation using three configured BWPs on an NR carrier is shown. A UE configured with these three BWPs can switch from one BWP to another at a handover point. FIG. 9 In the example shown, the BWP includes: BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 can be the initial active BWP, and BWP904 can be the default BWP. The UE can switch between BWPs at a handover point. FIG. 9In the example, the UE can switch from BWP 902 to BWP 904 at handover point 908. The handover at handover point 908 can occur for any suitable reason, such as in response to the expiration of a BWP inactivity timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 906 at handover point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE can switch from active BWP 906 to BWP 904 at handover point 912 in response to the expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 902 at handover point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

[0121] If a UE is configured for a secondary cell with a default downlink BWP and timer values ​​from a set of configured downlink BWPs, the UE procedure for switching BWPs on the secondary cell can be the same as / similar to those on the primary cell. For example, the UE can use these values ​​of the secondary cell in the same / similar way as the UE would use the timer values ​​and default downlink BWP of the primary cell.

[0122] To provide higher data rates, carrier aggregation (CA) can be used to combine two or more carriers and transmit them simultaneously to / from the same UE. The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are multiple serving cells for the UE, with one serving cell per CC. A CC can have three configurations in the frequency domain.

[0123] FIG. 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (band A) and located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

[0124] In the example, up to 32 CCs can be aggregated. Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD or FDD). The serving cell for the UE using CA can have downlink CCs. For FDD, one or more uplink CCs can optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers can be useful when the UE has more data traffic in the downlink than in the uplink.

[0125] When using CA, one of the aggregated cells used for the UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE initially connects during RRC connection establishment, re-establishment, and / or handover. The PCell provides the UE with NAS mobility information and security input. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells used for the UE can be referred to as secondary cells (SCells). In the example, the SCell can be configured after the PCell is configured for the UE. For example, the SCell can be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

[0126] The configured SCell for the UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) FIG. 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0127] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant; this is called self-scheduling. A cell's DCI can be transmitted on another cell; this is called cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregation downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0128] FIG. 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each contain one or more downlink CCs. FIG. 10B In the example, PUCCH group 1010 contains three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example contains three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary SCells (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if FIG. 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0129] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carriers. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including the first carrier is activated.

[0130] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / authorization of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

[0131] In the downlink, the base station can transmit one or more reference signals (RS) (e.g., unicast, multicast, and / or broadcast) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, such as...). FIG. 5 (As shown in A). In the uplink, the UE can transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, such as...). FIG. 5 (As shown in B). PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

[0132] FIG. 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can contain one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). FIG. 11A (As shown in the diagram). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... FIG. 11AThis is an example, and these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factors. In this example, the UE can assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing.

[0133] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). FIG. 11A As shown in the example, and can span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH can have a common center frequency. PSS can be transmitted first and can span, for example, 1 OFDM symbol and 127 subcarriers. SSS can be transmitted after PSS (e.g., after two symbols) and can span 1 OFDM symbol and 127 subcarriers. PBCH can be transmitted after PSS (e.g., spanning the next 3 OFDM symbols) and can span 240 subcarriers.

[0134] The UE may not know the location of the SS / PBCH block in the time and frequency domains (e.g., when the UE is searching for a cell). To find and select a cell, the UE can monitor the carrier of the PSS. For example, the UE can monitor the frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at different frequency locations within the carrier, as indicated by the synchronization grating. If the PSS is found at a certain location in the time and frequency domains, the UE can determine the locations of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block can be a cell-defined SS block (CD-SSB). In the example, the primary cell can be associated with the CD-SSB. The CD-SSB can be located on the synchronization grating. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

[0135] The SS / PBCH block can be used by the UE to determine one or more parameters of the cell. For example, the UE can determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE can determine the location of the cell's frame boundary based on the location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission mode in which the SS / PBCH block is at a known distance from the frame boundary.

[0136] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can contain an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can contain a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can contain System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can contain SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0137] The UE may assume that one or more SS / PBCH blocks transmitted using the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

[0138] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In the example, the first SS / PBCH block can be transmitted in the first spatial direction using the first beam, and the second SS / PBCH block can be transmitted in the second spatial direction using the second beam.

[0139] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0140] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0141] The base station can semi-statically configure the UE using one or more CSI-RS resource sets. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0142] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, non-periodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI reports at specific times and / or periodically. For non-periodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

[0143] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0144] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0145] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. The set of PRBs can be represented as a Precode Resource Block Group (PRG).

[0146] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0147] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or association with one or more parameters (e.g., modulation and coding scheme (MCS)) indicated by the DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks can support multiple PT-RS densities defined in the time and / or frequency domains. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can employ the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0148] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols of PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS type and / or scrambling sequence of the DMRS can be the same or different.

[0149] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS on one or more layers present in the PUSCH. In the example, a higher layer may configure up to three DMRS for the PUSCH.

[0150] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured UE-specifically through a combination of RRC signaling and / or through one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least one MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the UE's scheduled time / frequency duration.

[0151] The UE can transmit SRS to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks to uplink PUSCH transmissions from the UE. The base station can semi-statically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In the example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In the example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0152] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe level periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiation OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0153] Antenna ports are defined such that a symbol on an antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port through the same channel. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to transmit the second symbol on the antenna port from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted, and the channel through which the first symbol on the first antenna port is transmitted. The one or more large-scale properties can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0154] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After establishing an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0155] FIG. 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. FIG. 11BThe square shown can represent a resource block (RB) within the cell's bandwidth. The base station can transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transport comb, and quasi-co-location (QCL) parameters (e.g., ...). QCL- scrambling identity , crs-ports count , mbsfn-subframeconfiglist , csi-rs- configZPid, qcl-csi-rs-configNZPid (and / or other radio resource parameters).

[0156] FIG. 11B The three beams shown can be configured for use in a UE-specific configuration. FIG. 11B The diagram shows three beams (beam #1, beam #2, and beam #3), with the possibility of configuring more or fewer beams. CSI-RS1101 can be assigned to beam #1, which can be transmitted on one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be assigned to beam #2, which can be transmitted on one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be assigned to beam #3, which can be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), the beam for a UE can be configured such that the beam for the UE uses symbols from beams of other UEs.

[0157] CSI-RS, such as FIG. 11BThose shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) configured with CSI-RS resources. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In the example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0158] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on the assessment, the UE can transmit a beam measurement report indicating one or more beampup quality parameters, including, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0159] FIG. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmission (Tx) beams for a Transport Receiver Point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP can include a Tx beam scan for the beam set (shown as an ellipse rotating counterclockwise in the top rows of P1 and P2, indicated by dashed arrows). Beamforming at the UE can include an Rx beam scan for the beam set (shown as an ellipse rotating clockwise in the bottom rows of P1 and P3, indicated by dashed arrows). Procedure P2 can be used to enable UE measurement of the Tx beams for a TRP (shown as an ellipse rotating counterclockwise in the top row of P2, indicated by dashed arrows). The UE and / or base station may perform procedure P2 using a smaller beam set than that used in procedure P1, or using a narrower beam set than that used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and scanning the Rx beam at the UE.

[0160] FIG. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, a Tx beam scan from the beam set (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam scan from the beam set (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0161] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect a beam fault based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0162] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station can indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels can be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0163] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam fault recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

[0164] FIG. 13A A four-step contention-based random access procedure is illustrated. Before initiating the procedure, the base station may transmit configuration message 1310 to the UE. FIG. 13AThe procedure shown involves the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may contain and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may contain and / or be referred to as a random access response (RAR).

[0165] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral ); cell-specific parameters (e.g., RACH-ConfigCommon ); and / or special parameters (e.g., RACH- configDedicated The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0166] The one or more RACH parameters provided in configuration message 1310 can indicate one or more physical RACH (PRACH) timings that can be used to transmit Msg 11311. These one or more PRACH timings can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH timings (e.g., prach- ConfigIndex The one or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0167] The one or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmission power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., the received target power and / or the initial power of the preamble transmission). One or more power offsets indicated by the one or more RACH parameters may exist. For example, the one or more RACH parameters can indicate: power ramp step size; power offset between SSB and CSI-RS; power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or power offset values ​​between preamble groups. The one or more RACH parameters can indicate one or more thresholds upon which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

[0168] Msg 1 1311 may contain one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude of Msg 3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than the RSRP threshold (e.g., ...). rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0169] The UE can determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE can determine the preamble contained in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList This can indicate the correlation between the PRACH timing and the one or more reference signals.

[0170] If no response is received after the preamble transmission, the UE can perform a preamble retransmission. The UE can increase the uplink transmission power used for preamble retransmission. The UE can select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE can determine the preamble to be retransmitted and can ramp up the uplink transmission power. The UE can receive one or more RACH parameters (e.g., indicating the ramp step size for preamble retransmission) indicating the ramp step size for preamble retransmission. PREAMBLE_POWER_RAMPING_STEP The ramp-up step size can be the amount by which the uplink transmission power used for retransmissions is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in previous preamble transmissions, the UE can ramp up the uplink transmission power. The UE can count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER For example, if the number of preamble transmissions exceeds a threshold configured by one or more of the RACH parameters (e.g., preambleTransMax If the UE determines that the random access procedure was not completed successfully, then the UE can be sure that the random access procedure was not completed successfully.

[0171] The Msg 2 1312 received by the UE may contain a RAR. In some scenarios, Msg 2 1312 may contain multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may contain a time comparison command that the UE can use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow The UE can monitor the PDCCH of Msg 21312. The UE can determine when to initiate a time window based on the PRACH timing in which it transmits the preamble. For example, the UE can initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). The one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate a random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0172] The UE may transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... FIG. 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. A conflict may occur if the multiple UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

[0173] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 contains a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 contains a TC-RNTI (e.g., if the UE is in RRC_IDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches (e.g., is transmitted) the CCCH SDU sent in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

[0174] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedure) can be supported on the uplink carriers. For example, the base station can configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. To enable random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, the UE can determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg 1 1311 and / or Msg 3 1313) can be preserved on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch uplink carriers for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (e.g., listen before speaking).

[0175] FIG. 13B This illustrates a two-step contention-free random access procedure. (Compared to...) FIG. 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. FIG. 13B The program shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... FIG. 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) FIG. 13A and FIG. 13B It will be understood that a contention-free random access procedure may not contain messages such as Msg 3 1313 and / or Msg 4 1314.

[0176] It can be initiated for beam fault recovery, other SI requests, SCell addition and / or handover. FIG. 13B The contention-free random access procedure is shown. For example, the base station can indicate or assign a preamble to the UE for Msg 1 1321. The UE can receive the preamble indication from the base station via PDCCH and / or RRC (e.g., ra-PreambleIndex ).

[0177] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow To monitor the PDCCH of the RAR. In the event of a beam fault recovery request, the base station can search the space indicated by the RRC message (e.g., recoverySearchSpaceIdThe UE can be configured with a separate time window and / or a separate PDCCH. The UE can monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) in the search space. FIG. 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that the response is an indication of confirmation of the SI request.

[0178] FIG. 13C Another two-step random access procedure is shown. (Compared to...) FIG. 13A and FIG. 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. FIG. 13C The program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0179] Msg A 1331 can be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... FIG. 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar to and / or equivalent to that shown in Msg 3 1313. FIG. 13A and FIG. 13B The Msg 2 1312 shown (e.g., RAR) and / or FIG. 13A The content shown is similar to and / or equivalent to Msg 41314.

[0180] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. FIG. 13CThe two-step random access procedure is used in the UE. The UE may determine whether to initiate a two-step random access procedure based on one or more factors. The one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; cell size; the UE's RRC status; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0181] The UE can determine the radio resources and / or uplink transmission power of the preamble 1341 and / or transport block 1342 contained in Msg A 1331 based on the two-step RACH parameters included in configuration message 1330. The RACH parameters can indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) for the transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) for the transmission of the transport block 1342 can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0182] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., radio resource allocation and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0183] The UE and the base station can exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0184] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling authorization indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a group-shared PDCCH (GC-PDCCH) common to the UE group.

[0185] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to a DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of a Radio Network Temporary Identifier (RNTI).

[0186] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled using a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled using a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). FIG. 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the UE may include: the configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0187] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 can be used for PUSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

[0188] After scrambling the DCI with RNTI, the base station can process the DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station can map the coded and modulated DCI onto resource elements used for and / or configured for the PDCCH. Based on the DCI payload size and / or the base station's coverage area, the base station can transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. CCEs can include the number of resource element groups (REGs) (e.g., 6). REGs can include resource blocks in OFDM symbols. The mapping of the coded and modulated DCI onto resource elements can be based on the mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0189] FIG. 14A An example of a CORESET configuration for the bandwidth portion is shown. A base station can transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode the DCI using one or more search spaces. The base station can configure the CORESET in the time-frequency domain. FIG. 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol of the time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol of the time slot. The fourth CORESET 1404 appears at the seventh symbol of the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0190] FIG. 14B An example of CCE-to-REG mapping for DCI transmission is shown in CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved (e.g., for providing frequency diversity) or non-interleaved (e.g., for facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mappings for different CORESETs. A CORESET can be associated with CCE-to-REG mapping via RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. Antenna port QCL parameters can indicate the QCL information for the demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0191] The base station can transmit an RRC message to the UE including configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring period and PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set can be predefined and known to the UE. The set of CCEs in the UE-specific search space set can be configured based on the UE's identifier (e.g., C-RNTI).

[0192] like FIG. 14B As shown, the UE can determine the time-frequency resources of the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE can determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambling bits of the CRC parity bit of the DCI that match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0193] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0194] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted in the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can contain two or fewer bits. If more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can contain two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can contain more than two bits. If more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not contain an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource contains an orthogonal overlay code, the UE can use PUCCH format 4.

[0195] The base station can transmit configuration parameters for multiple PUCCH resource sets to the UE using, for example, RRC messages. These multiple PUCCH resource sets (e.g., up to four sets) can be configured on the cell's uplink BWP. A PUCCH resource set can be configured with: a PUCCH resource set index; and multiple PUCCH resources (e.g., PUCCH resource resources identified by PUCCH resource identifiers). pucch-Resourceid The UE can transmit multiple (e.g., a maximum number) UCI ​​information bits using one of the multiple PUCCH resources in a PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0196] After determining a PUCCH resource set from multiple PUCCH resource sets, the UE can determine the PUCCH resources used for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE can determine the PUCCH resources based on the PUCCH resource indicator in the DCI received on the PDCCH (e.g., a DCI with DCI format 1_0 or a DCI for 1_1). The three-bit PUCCH resource indicator in the DCI can indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE can use the PUCCH resource indicated by the PUCCH resource indicator in the DCI to transmit UCI (HARQ-ACK, CSI, and / or SR).

[0197] FIG. 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as... FIG. 1A The mobile communication network 100 shownFIG. 1B The mobile communication network 150 shown or any other communication network. FIG. 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may contain more than one UE and / or more than one base station, which have the same characteristics as... FIG. 15 The same or similar configurations shown.

[0198] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0199] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. The data can be provided to processing system 1508 via, for example, a core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, information about… FIG. 2A , FIG. 2B , FIG. 3 and FIG. 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer are included. Layer 3 may contain elements such as... FIG. 2B The RRC layer.

[0200] After being processed by processing system 1508, data to be transmitted to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 can implement Layer 1 OSI functions. Layer 1 can include information about... FIG. 2A , FIG. 2B , FIG. 3 and FIG. 4A The PHY layer. For transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0201] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 can include information about... FIG. 2A , FIG. 2B , FIG. 3 and FIG. 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping from the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0202] like FIG. 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, wireless device 1502 and / or base station 1504 may have a single antenna.

[0203] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although FIG. 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0204] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0205] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the aforementioned one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar panel, a fuel cell unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0206] FIG. 16AAn example architecture for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports, etc. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, it can be achieved through... FIG. 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various embodiments.

[0207] Figure 16B An example architecture for modulation and upsampling of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0208] Figure 16C An example structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port, etc. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

[0209] Figure 16D Another example architecture for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

[0210] A wireless device can receive one or more messages (e.g., RRC messages) from a base station, including configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via these multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, and RRC layer. For example, configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0211] A timer can begin running once started and continues running until it stops or expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of the timer may not be updated until the timer stops or expires (e.g., due to BWP switching). The timer can be used to measure time periods / windows of a process. When the specification refers to embodiments and procedures relating to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other example embodiments for restarting the measurement of a time window can be provided.

[0212] Figure 17 An example of device-to-device (D2D) communication is illustrated, where direct communication exists between wireless devices. In the example, D2D communication can be performed via a sidelink (SL). Wireless devices can exchange sidelink communication via a sidelink interface. The sidelink interface can refer to a PC5 interface, a proximity-based service (e.g., direct) communication (or control) 5 interface, and / or a ProSe (e.g., direct) communication (or control) 5 interface. A sidelink is distinct from an uplink (where the wireless device communicates to the base station) and a downlink (where the base station communicates to the wireless device). The wireless device and the base station can exchange uplink and / or downlink communication via a user plane interface (e.g., a Uu interface).

[0213] like Figure 17As shown, wireless devices #1 and #2 can be within the coverage area of ​​base station #1. For example, both wireless devices #1 and #2 can communicate with base station #1 via the Uu interface. Wireless device #3 can be within the coverage area of ​​base station #2. Base station #1 and base station #2 can share the network and jointly provide network coverage. Wireless devices #4 and #5 can be outside the network coverage area.

[0214] Intra-coverage D2D communication can be performed when two wireless devices share a network coverage area. Wireless devices #1 and #2 are both within the coverage area of ​​base station #1. Therefore, they can perform intra-cell D2D communication within the coverage area, designated as sidelink A. Wireless devices #2 and #3 are in the coverage areas of different base stations but share the same network coverage area. Therefore, they can perform intra-cell D2D communication within the coverage area, designated as sidelink B. Partial coverage D2D communication can be performed when one wireless device is within the network coverage area and the other wireless device is outside the network coverage area. Wireless devices #3 and #4 can perform partial coverage D2D communication, designated as sidelink C. Out-of-coverage D2D communication can be performed when both wireless devices are outside the network coverage area. Wireless devices #4 and #5 can perform out-of-coverage D2D communication, designated as sidelink D.

[0215] Physical channels can be used to configure sidelink communication, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Feedback Channel (PSFCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Shared Channel (PSSCH). A first radio device can use the PSBCH to send broadcast information to a second radio device. The PSBCH may be similar to the PBCH in some respects. Broadcast information may include, for example, slot format indications, resource pool information, sidelink system frame numbers, or any other suitable broadcast information. A first radio device can use the PSFCH to send feedback information to a second radio device. Feedback information may include, for example, HARQ feedback information. A first radio device can use the PSDCH to send discovery information to a second radio device. The radio device can use the discovery information to signal its presence and / or service availability to other radio devices in the area. A first radio device can use the PSCCH to send sidelink control information (SCI) to a second radio device. The PSCCH may be similar to the PDCCH and / or PUCCH in some respects. Control information may include, for example, time / frequency resource allocation information (RB size, number of retransmissions, etc.), demodulation-related information (DMRS, MCS, RV, etc.), identification information for transmitting and / or receiving wireless devices, process identifiers (HARQ, etc.), or any other suitable control information. The PSCCH can be used to allocate, prioritize, and / or reserve sidelink resources for sidelink transmission. A first wireless device may use the PSSCH to send and / or relay data and / or network information to a second wireless device. The PSSCH may be similar to the PDSCH and / or PUSCH in some respects. Each sidelink channel may be associated with one or more demodulation reference signals. Sidelink operation may utilize sidelink synchronization signals to establish the timing of sidelink operation. A wireless device configured for sidelink operation may, for example, use the PSBCH to transmit a sidelink synchronization signal. The sidelink synchronization signal may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS).

[0216] Sidelink resources can be configured to wireless devices in any suitable manner. Wireless devices can be pre-configured for sidelinks, for example, pre-configured with sidelink resource information. Additionally or alternatively, the network can broadcast system information related to resource pools used for sidelinks. Additionally or alternatively, the network can configure specific wireless devices with dedicated sidelink configurations. These configurations can identify sidelink resources to be used for sidelink operation (e.g., configuring sidelink band combinations).

[0217] Wireless devices can operate in different modes, such as an auxiliary mode (which may be referred to as mode 1) or an autonomous mode (which may be referred to as mode 2). Mode selection can be based on the coverage status of the wireless device, the radio resource control status of the wireless device, information and / or instructions from the network, and / or any other suitable factors. For example, if the wireless device is idle or inactive, or if the wireless device is outside network coverage, the wireless device can choose to operate in autonomous mode. For example, if the wireless device is in connected mode (e.g., connected to a base station), the wireless device can choose to operate in auxiliary mode (or operate under the instruction of the base station). For example, the network (e.g., a base station) can instruct connected wireless devices to operate in a specific mode.

[0218] In auxiliary mode, a radio device can request scheduling from the network. For example, the radio device can send a scheduling request to the network, and the network can allocate sidelink resources to the radio device. Auxiliary mode may be referred to as network-assisted mode, gNB-assisted mode, or base station-assisted mode. In autonomous mode, a radio device can select sidelink resources based on measurements within one or more resource pools (e.g., pre-configured or network-allocated resource pools), sidelink resource selections made by other radio devices, and / or sidelink resource usage by other radio devices.

[0219] To select sidelink resources, a wireless device can observe a sensing window and a selection window. During the sensing window, the wireless device can use a pool of sidelink resources to observe SCIs transmitted by other wireless devices. SCIs can identify resources that can be used and / or reserved for sidelink transmissions. Based on the resources identified in the SCIs, the wireless device can select resources within the selection window (e.g., resources different from those identified in the SCIs). The wireless device can then use the selected sidelink resources for transmission.

[0220] Figure 18 An example of a resource pool for sidelink operation is shown. A radio device can operate using one or more sidelink cells. A sidelink cell can contain one or more resource pools. Each resource pool can be configured to operate according to a specific mode (e.g., assisted or autonomous). A resource pool can be divided into resource elements. In the frequency domain, each resource element can include one or more resource blocks, such as those referred to as subchannels. In the time domain, each resource element can include, for example, one or more time slots, one or more subframes, and / or one or more OFDM symbols. Resource pools can be contiguous or non-contiguous in the frequency and / or time domains (e.g., including contiguous or non-contiguous resource elements). Resource pools can be divided into overlapping resource pool portions. Resource pools can be shared among one or more radio devices. For example, each radio device can attempt to transmit using different resource elements to avoid collisions.

[0221] Sidelink resource pools can be arranged in any suitable manner. In the diagram, the example resource pool is non-contiguous in the time domain and limited to a single sidelink BWP. In the example resource pool, frequency resources are divided into Nf resource units per time unit, numbered from zero to Nf-1. The example resource pool may include multiple parts that repeat every k time units (non-contiguous in this example). In the diagram, time resources are numbered n, n+1…n+k, n+k+1…etc.

[0222] A wireless device can select one or more resource units from a resource pool for transmission. In the example resource pool, the wireless device selects resource unit (n,0) for sidelink transmission. The wireless device can also select periodic resource units in later portions of the resource pool, such as resource unit (n+k,0), resource unit (n+2k,0), resource unit (n+3k,0), etc. The selection can be based, for example, on the determination that transmission using resource unit (n,0) will not (or is unlikely to) conflict with sidelink transmissions of wireless devices sharing the same sidelink resource pool. The determination can be based, for example, on the behavior of other wireless devices sharing the resource pool. For example, if no sidelink transmission is detected in resource unit (nk,0), the wireless device can select resource unit (n,0), resource (n+k,0), etc. For example, if a sidelink transmission from another wireless device is detected in resource unit (nk,1), the wireless device can avoid selecting resource unit (n,1), resource (n+k,1), etc.

[0223] Different sidelink physical channels can use different resource pools. For example, PSCCH can use a first resource pool, and PSSCH can use a second resource pool. Different resource priorities can be associated with different resource pools. For example, data associated with a first QoS, service, priority, and / or other characteristics can use the first resource pool, and data associated with a second QoS, service, priority, and / or other characteristics can use the second resource pool. For example, the network (e.g., a base station) can configure priority levels for each resource pool, and configured supported services for each resource pool, etc. For example, the network (e.g., a base station) can configure a first resource pool for unicast UEs, a second resource pool for multicast UEs, etc. For example, the network (e.g., a base station) can configure a first resource pool for transmitting sidelink data, a second resource pool for transmitting discovery messages, etc.

[0224] In an example of vehicle-to-everything (V2X) communication via a Uu interface and / or PC5 interface, V2X communication can be vehicle-to-vehicle (V2V) communication. The wireless device in V2V communication can be a vehicle. In one example, V2X communication can be vehicle-to-pedestrian (V2P) communication. The wireless device in V2P communication can be a pedestrian equipped with a mobile phone / handheld device. In one example, V2X communication can be vehicle-to-infrastructure (V2I) communication. The infrastructure in V2I communication can be a base station / access point / node / roadside unit. The wireless device in V2X communication can be a transmitting wireless device performing one or more sidelink transmissions to a receiving wireless device. The wireless device in V2X communication can be a receiving wireless device receiving one or more sidelink transmissions from a transmitting wireless device.

[0225] Figure 19 An example of a sidelink symbol in a time slot is shown. In the example, a sidelink transmission can be carried out in a time slot in the time domain. In the example, the wireless device may have data to transmit via a sidelink. The wireless device can segment the data into one or more transport blocks (TBs). One or more TBs can include different data segments. One TB in one or more TBs can be data packets of data. The wireless device can transmit one or more TBs (e.g., data packets) via one or more sidelink transmissions (e.g., via PSCCH / PSSCH in one or more time slots). In the example, a sidelink transmission (e.g., in a time slot) can include a SCI. A sidelink transmission can also include TBs. An SCI can include a first-level SCI and a second-level SCI. The PSCCH of a sidelink transmission can include a first-level SCI for scheduling PSSCHs (e.g., TBs). The PSSCH of a sidelink transmission can include a second-level SCI. The PSSCH of a sidelink transmission can also include TBs. In the example, a sidelink symbol in a time slot may or may not start at the first symbol of the time slot. A sidelink symbol in a time slot may or may not end at the last symbol of the time slot. exist Figure 19 In the example, the side-link symbols in the time slot begin from the second symbol of the time slot. Figure 19In the example, the sidelink symbol in the time slot ends at the twelfth symbol of the time slot. The first sidelink transmission may include a first Automatic Gain Control (AGC) symbol (e.g., the second symbol in the time slot), a PSCCH (e.g., the third, fourth, and fifth symbols in the sub-channels of the time slot), a PSSCH (e.g., the third to eighth symbols in the time slot), and / or a first guard symbol (e.g., the ninth symbol in the time slot). The second sidelink transmission may include a second AGC symbol (e.g., the tenth symbol in the time slot), a PSFCH (e.g., the eleventh symbol in the time slot), and / or a second guard symbol for the second sidelink transmission (e.g., the twelfth symbol in the time slot). In the example, one or more HARQ feedbacks (e.g., positive acknowledgment or ACK and / or negative acknowledgment or NACK) may be transmitted via the PSFCH. In the example, the PSCCH, PSSCH, and PSFCH may have different numbers of sub-channels in the frequency domain (e.g., different numbers of frequency resources).

[0226] The first-level SCI can be SCI format 1-A. SCI format 1-A can include multiple fields used to schedule the first TB on the PSSCH and the second-level SCI on the PSSCH. The following information can be transmitted via SCI format 1-A.

[0227] -Side link transmission Priority For example, priority can be the physical layer (e.g., Layer 1) priority of sidelink transmission. For example, priority can be determined based on the logical channel priority of sidelink transmission. -PSSCH Frequency resource allocation ; -PSSCH Time resource allocation ; - The second TB Resource Retention Period / Interval ; - Demodulation Reference Signal (DMRS) mode ; - Second-tier SCI format ; - Beta_offset indicator ; - DMRS port number ; -PSSCH Modulation and coding schemes ; - Additional MCS table indicator ; - PSFCH Overhead Indication ; - Reserved bits .

[0228] The second-level SCI can be SCI format 2-A. SCI format 2-A can be used to decode the PSSCH using HARQ operations when the HARQ-ACK message contains ACK or NACK, or when there is no HARQ-ACK feedback. SCI format 2-A can include multiple fields indicating the following information.

[0229] - HARQ process number ; - New data indicator ; - Redundant version ; - Transmitter for side-link transmission (e.g., a wireless transmission device) Source ID ; - Receiver for side-link transmission (e.g., receiving wireless device) Destination ID ; - HARQ Feedback Enable / Disable Indicator ; - Indicates whether the sidelink transmission is broadcast, multicast, and / or unicast. Broadcast type indicator ; - CSI Request .

[0230] The second-level SCI can be SCI format 2-B. SCI format 2-B can be used to decode PSSCH using HARQ operations when the HARQ-ACK message contains only NACK, or when there is no HARQ-ACK feedback. SCI format 2-B can include multiple fields indicating the following information.

[0231] - HARQ process number ; - New data indicator ; - Redundant version ; - Transmitter for side-link transmission (e.g., a wireless transmission device) Source ID ; - Receiver for side-link transmission (e.g., receiving wireless device) Destination ID ; - HARQ Feedback Enable / Disable Indicator ; - Indicates the geographical location of the transmitter (e.g., the transmitting wireless device) for sidelink transmission. Region ID ; - Indicates the communication range of the side link transmission Communication range requirements .

[0232] Figure 20An example of resource indication for a first TB (e.g., a first data packet) and resource reservation for a second TB (e.g., a second data packet) is shown. The SCI for the initial transmission (e.g., the first transmission) and / or retransmission of the first TB may include one or more first parameters (e.g., Frequency resource allocation and Time resource allocation The one or more first parameters indicate one or more first time and frequency (T / F) resources for transmission and / or retransmission of the first TB. The SCI may also include one or more second parameters (e.g., Resource Retention Period The one or more second parameters indicate the retention period / interval of one or more second T / F resources for the initial transmission and / or retransmission of the second TB.

[0233] In the example, in response to triggering a resource selection procedure, the wireless device can select one or more first T / F resources for initial transmission and / or retransmission of the first TB. For example... Figure 20 As shown, the wireless device can select three resources to transmit the first TB. The wireless device can transmit the initial transmission of the first TB via the first of the three resources. Figure 20 The initial Tx of the first TB in the three resources). The wireless device can transmit the first retransmission of the first TB via the second resource of the three resources ( Figure 20 The first re-Tx in the three resources). The wireless device can transmit the first TB of second retransmission via the third resource of the three resources ( Figure 20 The second re-Tx in the first TB). The duration between the start time of the initial transmission of the first TB and the second retransmission of the first TB can be less than or equal to 32 side link time slots (e.g., Figure 20 In (Slots). The first SCI can be associated with the initial transmission of the first TB. The first SCI can indicate the first T / F resource indication for the initial transmission of the first TB, the first retransmission of the first TB, and the second retransmission of the first TB. The first SCI can further indicate the reservation period / interval for resource reservation for the second TB. The second SCI can be associated with the first retransmission of the first TB. The second SCI can indicate the second T / F resource indication for the first retransmission of the first TB and the second retransmission of the first TB. The second SCI can further indicate the reservation period / interval for resource reservation for the second TB. The third SCI can be associated with the second retransmission of the first TB. The third SCI can indicate the third T / F resource indication for the second retransmission of the first TB. The third SCI can further indicate the reservation period / interval for resource reservation for the second TB.

[0234] Figure 21 and Figure 22An example of configuration information for sidelink communication is shown. In the example, the base station may transmit one or more Radio Resource Control (RRC) messages to the radio device to deliver configuration information for sidelink communication. The configuration information may include fields. sl-UE-SelectedConfigRP Parameters in the field sl-ThresPSSCH-RSRP- List A list of 64 thresholds can be specified. In the example, the wireless device can receive a first side link control information (SCI) indicating a first priority. The wireless device can have a second SCI to transmit. The second SCI can indicate a second priority. The wireless device can select a threshold from the list based on the first priority in the first SCI and the second priority in the second SCI. (Reference) Figure 26 The second exclusion mechanism allows the wireless device to exclude resources from the candidate resource set based on a threshold. (Parameters in the field...) sl- MaxNumPerReserve This can indicate the maximum number of PSCCH / PSSCH resources to be reserved as specified in SCI. Parameters in the field sl-MultiReserveResource This can indicate, based on sensing and resource selection procedures, whether to allow the reservation of sidelink resources for the initial transmission of a TB via an SCI associated with a different TB. Parameters sl- ResourceReservePeriodList It can indicate the set of possible resource retention periods / intervals allowed in the resource pool (e.g., SL-ResourceReservedPeriod Each resource pool can be configured with up to 16 values. Parameters sl-RS- For Sensing This can indicate whether the DMRS of the PSCCH or PSSCH is used for Layer 1 (e.g., physical layer) RSRP measurements during sensing operations. Parameter sl-SensingWindow This can indicate the start of the sensing window. Parameters sl- SelectionWindowList This can indicate the end of the selection window in the resource selector for TB regarding the priority indicated in SCI. Value It can correspond to ,value Corresponding to Wait, for the subcarrier spacing (SCS) of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively .parameter SL- SelectionWindowConfig Sidelink priority can be indicated (e.g., sl-Priority ) and selection window (e.g. sl-SelectionWindow The mapping between the end of ) .

[0235] Configuration information may include parameters sl-PreemptionEnableThe parameter indicates whether sidelink preemption is disabled or enabled in the resource pool. For example, if sidelink preemption is enabled, a priority level can be configured. p_ preemption For example, if sidelink preemption is enabled but not configured... p_preemption Then, sidelink preemption may apply to all priority levels.

[0236] Configuration information may include parameters sl-TxPercentageList The parameter indicates a portion of the candidate single-slot PSSCH resources on the total resources. For example, the value p20 could correspond to 20%, and so on. SL-TxPercentageConfig It can indicate sidelink priority (e.g.) sl-Priority ) and candidate single-slot PSSCH resources on total resources (e.g. sl- TxPercentage Mapping between parts of ).

[0237] Figure 23 An example format of the MAC subheader for a Sidelink Shared Channel (SL-SCH) is shown. The SL-SCH MAC subheader can include seven header fields: V / R / R / R / R / SCR / DST. The MAC subheader is octet aligned. For example, the V field could be a MAC Protocol Date Unit (PDU) format version number field indicating which version of the SL-SCH subheader is used. For example, the SRC field could carry a 16-bit Source Layer 2 Identifier (ID) field set to a first identifier provided by an upper layer. For example, the DST field could carry an 8-bit Destination Layer 2 ID field set to a second identifier provided by an upper layer. In the example, if the V field is set to "1", the second identifier could be a unicast identifier. In the example, if the V field is set to "2", the second identifier could be a multicast identifier. In the example, if the V field is set to "3", the second identifier could be a broadcast identifier. For example, the R field could indicate reserved bits.

[0238] Figure 24 An example of a resource selection procedure is shown. A wireless device can execute a resource selection procedure to select resources for one or more sidelink transmissions. For example... Figure 24 As shown, the sensing window of the resource selection program can be in time. (For example, parameters) sl-SensingWindow (Start) The sensing window can be set in time. End. New data transmitted via one or more sidelinks can be completed in time. Arrival at the wireless device. Time period. The processing delay that the wireless device determines to trigger the resource selection procedure can be determined at a specific time. Trigger the resource selector to select resources for use at time. New data resources arriving. Wireless devices can [access data] in time. Complete the resource selection process. The wireless device can determine parameters based on its capabilities. The capability of a wireless device can be attributed to the processing latency of its processor. The selection window for the resource selector can be set in time. Start. The selection window can indicate the end time of the selection window. End. Wireless devices can be based on parameters. (For example, sl-SelectionWindow To determine the parameters In the example, the wireless device can be based on... Determine parameters Here, PDB (Packet Delay Budget) can be the maximum allowable delay (e.g., delay budget) for transmitting new data via one or more sidelinks. The wireless device can use this parameter... The corresponding value is determined as the priority for transmission on one or more sidelinks (e.g., based on the indication of sidelink priority). sl-Priority With selection window sl-SelectionWindow Parameters of the mapping between the ends SL- SelectionWindowConfig In the example, if the parameter Then the wireless device can set parameters. .

[0239] Figure 25 An example timing diagram of a resource selection procedure is shown. A wireless device can execute a resource selection procedure to select resources for one or more sidelink transmissions. Reference Figure 24 The initially selected sensing window can be in time Begin. The initially selected sensing window can be set in time. End. New data transmitted via one or more sidelinks can be completed in time. Arrival at the wireless device. Time period. This could be the processing delay by which the wireless device determines the initial selection of trigger resources. The wireless device can determine the time... Trigger the initial selection to choose the option to use at time. New data resources arriving. Wireless devices can [access data] in time. Complete the resource selection process. Time It can be used to complete in time The maximum allowed processing wait time for the resource selection procedure that is triggered at the location, where The initial selection window can be set up in time. Begin. The initial selection window can be accessed at any time. End. Parameters can be configured, pre-configured, or determined at the wireless device. .

[0240] Wireless devices can be based on time The resource selection procedure is completed to determine the first resource for transmission on one or more sidelinks (e.g., Figure 25 (Selected resources in the initial selection window). The wireless device can select a first resource from candidate resources in the initial selection window based on measurements in the sensing window used for initial selection. The wireless device can determine a resource conflict between the first resource and other resources reserved by another wireless device. The wireless device can determine to discard the first resource to avoid interference. The wireless device can time... and / or in time Previously triggered a resource reselection process (e.g., a second resource selector). Time period. This could be the processing delay of the wireless device completing a resource reselection procedure (e.g., a second resource selection procedure). The wireless device can determine the second resource (e.g., ...) via the resource reselection procedure (e.g., the second resource selection procedure). Figure 25 (Reselected resources in the process). The start time of the first resource can be time. (For example, the first resource can be in a time slot) middle).

[0241] In the example, the time parameter , , , and At least one of these can be configured by the base station for the wireless device. In the example, the time parameter... , , , and At least one of them can be pre-configured for the wireless device. Time parameter , , , and At least one of these can be stored in the memory of the wireless device. In the example, the memory can be a Subscriber Identity Module (SIM) card. Figure 24 and Figure 25 In the example, time , , , , , , , , and This can be in terms of time slots and / or time slot indices.

[0242] Figure 26 An example flowchart is shown of a resource selection procedure used by a wireless device to transmit TB (e.g., data packets) via a side link.

[0243] Figure 27 An example diagram of the resource selection process between different layers of a wireless device is shown.

[0244] refer to Figure 26 and Figure 27 The wireless device can transmit one or more sidelink transmissions for transmitting the TB (e.g., the first transmission of the TB and one or more retransmissions of the TB). Reference Figure 19 A sidelink transmission in one or more sidelink transmissions may include a PSCCH. A sidelink transmission may include a PSSCH. A sidelink transmission may include a PSFCH. The radio device may trigger a resource selection procedure for transmitting a TB. The resource selection procedure may include two actions. The first of these two actions may be a resource evaluation action. The physical layer (e.g., Layer 1) of the radio device may perform the first action. The physical layer may determine a subset of resources based on the first action and report the subset of resources to higher layers of the radio device (e.g., RRC layer and / or MAC layer). The second of these two actions may be a resource selection action. The higher layers of the radio device (e.g., RRC layer and / or MAC layer) may perform the second action based on the reported subset of resources from the physical layer.

[0245] In the example, a higher layer of the wireless device (e.g., the RRC layer and / or the MAC layer) can trigger a resource selection procedure to request the wireless device to determine a subset of resources. The higher layer can select resources from the subset of resources used for PSSCH and / or PSCCH transmissions. For example, in a time slot... The resource selection procedure is triggered in the middle layer, and higher layers can provide the following parameters for PSSCH and / or PSCCH transmission: - A resource pool from which wireless devices can determine a subset of resources; -Level 1 priority for PSSCH / PSCCH transmission (For example, see reference) Figure 21 and Figure 22 of sl-Priority ); - Remaining packet delay budget (PDB) for PSSCH and / or PSCCH transmissions; - Number of sub-channels , used for PSSCH and / or PSCCH transmission in a time slot; -Resource reservation period / interval In milliseconds ( (in units of )

[0246] In the example, if a higher layer requests the wireless device to determine a subset of resources (from which the higher layer will select resources for PSSCH and / or PSCCH transmissions for re-evaluation and / or preemption), the higher layer can provide a set of resources that may undergo re-evaluation. and the collection of resources that may be contested. .

[0247] In the example, a base station (e.g., a network) may transmit a message including one or more parameters to a wireless device for performing a resource selection procedure. The message may be an RRC / SIB message, a MAC CE, and / or a DCI. In the example, a second wireless device may transmit a message including one or more parameters to a wireless device for performing a resource selection procedure. The message may be an RRC message, a MAC CE, and / or a SCI. The one or more parameters may indicate the following information.

[0248] - sl-SelectionWindowList (For example, see reference) Figure 21 and Figure 22 of sl-SelectionWindow ): For a given value It is possible (e.g., based on reference) Figure 21 and Figure 22 of SL-SelectionWindowConfig ) internal parameters (For example, see reference) Figure 24 of ) set with parameter sl-SelectionWindowList The corresponding value.

[0249] - sl-ThresPSSCH-RSRP-List (For example, see reference) Figure 21 and Figure 22 of sl-ThresPSSCH-RSRP- List ): The parameter can indicate each combination The RSRP threshold, where It is the value of the priority field in the received SCI format 1-A, and This refers to the priority of sidelink transmissions (e.g., PSSCH / PSCCH transmissions) of the wireless device; in the example of the resource selection procedure, for The call can be .

[0250] - sl-RS-ForSensing (For example, see reference) Figure 21 and Figure 22 of sl-RS-ForSensing ): This parameter can indicate whether the wireless device uses the DMRS of the PSCCH or PSSCH for the Layer 1 (e.g., physical layer) RSRP measurement during sensing operations.

[0251] - sl-ResourceReservePeriodList (For example, see reference) Figure 21 and Figure 22 of sl- ResourceReservePeriodList ).

[0252] - sl-SensingWindow (For example, see reference) Figure 21 and Figure 22 of sl-SensingWindow ): Internal parameters It can be defined as corresponding to t0_SensingWindow The number of time slots.

[0253] - sl-TxPercentageList (For example, based on reference) Figure 21 and Figure 22 of SL-TxPercentageConfig ): Used for a given (For example, see reference) Figure 21 and Figure 22 of sl-Priority ) internal parameters (For example, see reference) Figure 21 and Figure 22 of sl-TxPercentage () can be defined as converting a percentage to a ratio. sl-xPercentage ( ).

[0254] - sl-PreemptionEnable (For example, see reference) Figure 21 and Figure 22 of p_preemption ): Internal parameters It can be set to parameters provided by higher layers. sl-PreemptionEnable .

[0255] Resource Retention Period / Interval (If provided) can be obtained from the unit Converted to logical time slot units, thus obtaining .

[0256] Notice: It can represent the set of time slots of the sidelink resource pool.

[0257] In resource assessment actions (e.g., Figure 26 In the first action of the process, the wireless device can determine the sensing window based on the triggered resource selection procedure (e.g., based on...). sl-SensingWindow of Figure 24 and Figure 25 The sensing window shown. The wireless device can determine the selection window based on a triggered resource selection procedure (e.g., based on...). sl-SelectionWindowList of Figure 24and Figure 25 The selection window shown. The wireless device can determine one or more retention periods / intervals for resource reservation (e.g., parameters). sl-ResourceReservePeriodList In the example, candidate single-slot resources are used for transmission. It can be defined as A set of consecutive sub-channels, sub-channels In the time slot Among them Wireless devices can assume time intervals. In the resource pool A set of consecutive sub-channels corresponds to a candidate single-slot resource (e.g., reference). Figure 24 and Figure 25 The total number of candidate single-slot resources can be determined by... Indicated. In the example, refer to Figure 24 and Figure 25 The sensing window can be determined by the duration. The number of time slots in the time frame is used to define the function. The wireless device can monitor a first subset of time slots in the sidelink resource pool within the sensing window. Due to half-duplex operation, the wireless device may not monitor a second subset of time slots beyond the first subset. The wireless device can perform the following actions based on the PSCCH decoded in the first subset of time slots and the measured RSRP. In the example, the internal parameters... It can be set by sl-ThresPSSCH-RSRP-List The first in The field indicates the corresponding value of the RSRP threshold, where .

[0258] refer to Figure 26 and Figure 27 In resource assessment actions (e.g., Figure 26 In the first action, the wireless device can select a candidate resource set (e.g., a collection). Initialize as a candidate resource set. In the example, the candidate resource set can be the union of candidate resources within the selection window. In the example, candidate resources can be candidate single subframe resources. In the example, candidate resources can be candidate single time slot resources. In the example, the set... It can be initialized as a set of all candidate single-slot resources.

[0259] refer to Figure 26 and Figure 27 In resource assessment actions (e.g., Figure 26In the first action, the wireless device may perform a first exclusion to exclude a second resource from the candidate resource set based on a first resource and one or more retention periods / intervals. In the example, the wireless device may not monitor the first resource within a sensing window. In the example, one or more retention periods / intervals may be configured with a resource pool of the second resource or associated with said resource pool. In the example, the wireless device may determine the second resource within a selection window based on one or more retention periods / intervals, the second resource being retained by a transmission via the first resource. In the example, the wireless device may exclude a second resource from the set based on the following conditions: Excluding candidate single-slot resources : - The wireless device has not yet detected time slots within the sensing window. .

[0260] -For parameters sl-ResourceReservePeriodList Any allowed period value, and in the time slot The received "Resource Retention Period" field, set to the stated periodic value, and indicating all sub-channels of the resource pool in this time slot, according to the assumed SCI format 1-A, will satisfy the second exclusion. .

[0261] refer to Figure 26 and Figure 27 In resource assessment actions (e.g., Figure 26 In the first action, the wireless device can perform a second exclusion to exclude a third resource from the candidate resource set. In the example, the SCI can indicate the resource reservation of the third resource. The SCI can further indicate a priority value (e.g., determined by higher-layer parameters). sl-Priority (Instructions). A wireless device may have a reference signal received power (RSRP) from a third resource that exceeds an RSRP threshold (e.g., determined by higher-layer parameters). sl- ThresPSSCH-RSRP-ListThe RSRP threshold can be associated with a priority value based on a mapping list configured and / or pre-configured to the priority value assigned to the radio device. In the example, the base station can transmit a message to the radio device to configure the mapping list. This message can be a Radio Resource Control (RRC) message. In the example, the mapping list can be pre-configured to the radio device. The radio device's memory can store the mapping list. In the example, the priority indicated by the priority value can be a Layer 1 priority (e.g., a physical layer priority). In the example, a larger priority value can indicate a higher priority for sidelink transmissions. A smaller priority value can indicate a lower priority for sidelink transmissions. In another example, a larger priority value can indicate a lower priority for sidelink transmissions. A smaller priority value can indicate a higher priority for sidelink transmissions. In the example, the radio device can exclude a third resource from the set based on the following conditions. Excluding candidate single-slot resources : a) Wireless devices in time slots The system receives SCI format 1-A, and the "Resource Retention Period" field (if present) and "Priority" field in the received SCI format 1-A indicate the values. and ; b) The RSRP measurement performed on the received SCI format 1-A is higher than... ; c) In time slots The SCI format received, or if and only if the "Resource Retention Period" field exists in the received SCI format 1-A, is assumed to be in the time slot. The same SCI format received in the middle is determined and A collection of overlapping resource blocks and time slots. and .here, It is converted to logical time slot units. ,if and ,but If the time slot Belongs to set ,but Otherwise time slot It belongs to a set time slot The first time slot afterwards; otherwise . It is set to convert to units Select window size .

[0262] refer to Figure 26 and Figure 27 In resource assessment actions (e.g., Figure 26 In the first action (of the process), after performing the first and second exclusions, the wireless device can determine, based on a condition, whether the remaining candidate resources in the candidate resource set are sufficient to select resources for one or more sidelink transmissions in the TB. In the example, this condition could be that, before performing the first and second exclusions, the total amount of remaining candidate resources in the candidate resource set is greater than a certain percentage of the total number of candidate resources in the candidate resource set. (For example, by higher-level parameters) sl-TxPercentageList (Instruction). If this condition is not met, the wireless device can use the value. Increase the RSRP threshold used to exclude third resources, and iteratively re-execute the initialization, first exclusion, and second exclusion until the condition is met. In the example, if the set The number of remaining candidate single-slot resources is less than ,but This can be increased by 3 dB, and the procedure continues to re-execute initialization, the first exclusion, and the second exclusion until the conditions are met. In the example, the wireless device can report the set to a higher layer of the wireless device. (For example, the remaining candidate resources in the candidate resource set). In the example, based on the set The number of remaining candidate single-slot resources is greater than or equal to The wireless device can report the set to the higher level of the wireless device. (For example, the remaining candidate resources in the candidate resource set when the conditions are met).

[0263] refer to Figure 26 and Figure 27 In resource selection actions (e.g., Figure 26 In the second action, the wireless device (e.g., a higher layer of the wireless device) can select from a set of candidate resources (e.g., a set reported by the physical layer). The fourth resource is selected from the remaining candidate resources in the candidate resource set for one or more sidelink transmissions of the TB. In the example, the wireless device may randomly select the fourth resource from the remaining candidate resources in the candidate resource set.

[0264] refer to Figure 26 and Figure 27 In the example, if it comes from a set resources no If a member (e.g., the remaining candidate resources in the candidate resource set when conditions are met) is identified, the wireless device can report the resource to a higher layer. A reassessment.

[0265] refer to Figure 26and Figure 27 In the example, if it comes from a set resources A wireless device can report resource availability to a higher layer if the following conditions are met. The seizure.

[0266] - no members, and - The second exclusion condition is met, where Set to reach The final threshold, and -Associated Priority One of the following conditions must be met: - sl-PreemptionEnable Provided and equal to 'enabled', and ; - sl-PreemptionEnable Being provided is not the same as being 'enabled', and and .

[0267] In the example, if resources Instructed for re-evaluation by a wireless device (e.g., the physical layer of the wireless device), the higher layer of the wireless device can be selected from the set. Remove resources In the example, if the resource If instructed to be preempted by a wireless device (e.g., the physical layer of the wireless device), then the higher layer of the wireless device can obtain the set. Remove resources Higher layers of the wireless device can access candidate resource sets (e.g., sets reported by the physical layer). The remaining candidate resources in the list that are not to be removed and / or New time and frequency resources are randomly selected. Higher layers of the wireless device can then replace the removed resources with the new time and frequency resources. and / or For example, wireless devices can be collected from a set. and / or sets Remove resources and / or And based on resources and / or The removal adds new time and frequency resources to the collection. and / or sets .

[0268] Sidelink preemption may occur between a first wireless device and a second wireless device. The first wireless device may select a first resource for first sidelink transmission. The first sidelink transmission may have a first priority. The second wireless device may select a second resource for second sidelink transmission. The second sidelink transmission may have a second priority. The first resource may partially and / or completely overlap with the second resource. The first wireless device may determine resource conflict between the first and second resources based on the partial and / or complete overlap of the first and second resources. Resource conflict may mean that the first and second resources completely and / or partially overlap in the time domain, frequency domain, code domain, power domain, and / or spatial domain. (Reference) Figure 18 For example, the first resource may include one or more first sidelink resource elements in a sidelink resource pool. The second resource may include one or more second sidelink resource elements in a sidelink resource pool. A partial resource conflict between the first and second resources may indicate that at least one of the one or more first sidelink resource elements belongs to one or more second sidelink resource elements. A complete resource conflict between the first and second resources may indicate that one or more first sidelink resource elements may be the same as one or more second sidelink resource elements or a subset of one or more second sidelink resource elements. In the example, a larger priority value may indicate a lower priority for sidelink transmission. A smaller priority value may indicate a higher priority for sidelink transmission. In the example, the first radio device may determine sidelink preemption based on resource conflict and a second priority being higher than the first priority. That is, the first radio device may determine sidelink preemption based on resource conflict and a second priority value being less than the first priority value. In another example, the first radio device may determine sidelink preemption based on resource conflict, a second priority value being less than a priority threshold, and a second priority value being less than the first priority value.

[0269] refer to Figure 25 The first wireless device can trigger the selection of a first resource for transmission on the first side link (e.g., in...). Figure 25 The first resource selection procedure (selected resource after conflicting resource selection) is as follows: The second wireless device can transmit an SCI indicating resource reservation of the first resource for second sidelink transmission. The first wireless device can determine resource conflicts on the first resource between the first sidelink transmission and the second sidelink transmission. The first wireless device can determine resource conflicts based on time... The resource reassessment is triggered at and / or prior to the resource reassessment (e.g., the resource assessment action of the second resource selection procedure). The first wireless device may trigger resource reselection (e.g., the resource selection action of the second resource selection procedure) based on the resource reassessment to select the second resource (e.g., in...). Figure 25(The resource selected after the resource reselection in the middle). The start time of the second resource can be time. .

[0270] The UE can receive one or more messages (e.g., RRC messages and / or SIB messages) that include configuration parameters for the sidelink BWP. Configuration parameters may include a first parameter (e.g., sl-StartSymbol) indicating the start symbol of the sidelink. The first parameter may indicate the start symbol for the sidelink in the time slot (e.g., symbol #0, symbol #1, symbol #2, symbol #3, symbol #4, symbol #5, symbol #6, symbol #7, etc.). For example, the time slot may not include SL-SSB (S-SSB). In this example, the UE may (pre-)configure one or more values ​​for the start symbol of the sidelink for each sidelink BWP. Configuration parameters may include a second parameter (e.g., sl-LengthSymbols) indicating the number of symbols used for the sidelink in the time slot (e.g., 7 symbols, 8 symbols, 9 symbols, 10 symbols, 11 symbols, 12 symbols, 13 symbols, 14 symbols, etc.). For example, the time slot may not include SL-SSB (S-SSB). In the example, the UE can be (pre-configured) with one or more values ​​for the number of sidelinks (symbol length) for each sidelink BWP.

[0271] The configuration parameters of a sidelink BWP can indicate one or more sidelink (communication) resource pools for the sidelink BWP (e.g., via SL-BWP-PoolConfig and / or SL-BWP-PoolConfigCommon). A resource pool can be a sidelink receive resource pool configured on the sidelink BWP (e.g., indicated by sl-RxPool). For example, a receive resource pool, if configured, can be used for PSFCH transmission / reception. A resource pool can also be a sidelink transmission resource pool configured on the sidelink BWP (e.g., indicated by sl-TxPool and / or sl-ResourcePool). For example, a transmission resource pool can include resources that allow the UE to transmit NR sidelink communication on the configured BWP (e.g., under special conditions and / or based on network scheduling). For example, a transmission resource pool, if configured, can be used for PSFCH transmission / reception.

[0272] The configuration parameters of a resource pool can indicate the size of a subchannel in the resource pool in units of PRBs (e.g., via sl-SubchannelSize). For example, the subchannel size can indicate the smallest granularity in the frequency domain used for sensing and / or for PSSCH resource selection. The configuration parameters of a resource pool can indicate the lowest / starting RB index of the subchannel with the lowest RB index relative to the sidelink BWP in the resource pool (e.g., via sl-StartRB-Subchannel). The configuration parameters of a resource pool can indicate the number of subchannels in the corresponding resource pool (e.g., via sl-NumSubchannel). For example, subchannels and / or the resource pool can consist of consecutive PRBs.

[0273] The configuration parameters of a resource pool can indicate the configuration of one or more sidelink channels on / in the resource pool. For example, the configuration parameters can indicate that the resource pool is configured with PSSCH and / or PSCCH and / or PSFCH.

[0274] The configuration parameters of a PSCCH can indicate the time resources for PSCCH transmission in a time slot. The configuration parameters of a PSCCH (e.g., SL-PSCCH-Config) can indicate the number of PSCCH symbols in a resource pool (e.g., 2 or 3) (e.g., via sl-TimeResourcePSCCH). The configuration parameters of a PSCCH (e.g., SL-PSCCH-Config) can indicate the frequency resources for PSCCH transmission in the corresponding resource pool (e.g., via sl-FreqResourcePSCCH). For example, the configuration parameters can indicate the number of PRBs (Programmable Buffers) for the PSCCH in the resource pool, which may not be greater than the number of PRBs (sub-channel size) of the sub-channels in the resource pool.

[0275] The configuration parameters of PSSCH can indicate one or more DMRS time-domain modes of PSSCH that can be used in the resource pool (e.g., PSSCH DMRS symbols in a time slot).

[0276] The resource pool may or may not have a PSFCH configured. PSFCH configuration parameters can indicate the PSFCH period in units / numbers of slots within the resource pool (e.g., via sl-PSFCH-Period). For example, a period value of 0 can indicate that no resources for PSFCH are configured in the resource pool, and / or HARQ feedback is disabled for (all) transmissions in the resource pool. For example, the period can be 1 slot, 2 slots, or 4 slots, etc. PSFCH configuration parameters can indicate the set of PRBs (actually) used for PSFCH transmission and reception (e.g., via sl-PSFCH-RB-Set). For example, a bitmap can indicate the set of PRBs, where the leftmost bit of the bitmap can point to the lowest RB index in the resource pool, and so on. PSFCH configuration parameters can indicate the minimum time gap between the PSFCH and its associated PSSCH in units of slots (e.g., via sl-MinTimeGapPSFCH). The configuration parameters of PSFCH can indicate the number of PSFCH resources available for multiplexing HARQ-ACK information in PSFCH transport (e.g., via sl-PSFCH-CandidateResourceType).

[0277] The UE can be configured by a higher layer (e.g., by RRC configuration parameters) having one or more sidelink resource pools. Sidelink resource pools can be used for PSSCH transmission and / or PSSCH reception. Sidelink resource pools can be associated with sidelink resource allocation mode 1 and / or sidelink resource allocation mode 2. In the frequency domain, a sidelink resource pool consists of one or more (e.g., sl-NumSubchannel A subchannel consists of one or more (e.g., ...) consecutive subchannels. sl- SubchannelSize ) Consecutive PRBs. For example, higher-layer parameters (e.g., RRC configuration parameters) can indicate the number of sub-channels in the sidelink resource pool (e.g., sl-NumSubchannel ) and / or the number of PRBs per sub-channel (e.g., sl-SubchannelSize ).

[0278] The time slot set can belong to the sidelink resource pool. The time slot set can be composed of... It means that among them The time slot index can be relative to time slot #0 of the radio frame corresponding to SFN 0 or DFN 0 of the serving cell. The set includes, in addition to those configured with S-SS / PSBCH blocks (S-SSB), [other types of time slots]. All time slots other than the specified time slot. The set includes all time slots except those specified in the original time slot. All time slots outside of time slots, In each of the time slots, the first Y , No. (Y+1),…,No. (Y+X-1) At least one of the OFDM symbols is not based on higher-layer parameters (e.g., the serving cell's). tdd-UL-DL-ConfigurationCommon-r16 (If provided) and / or sl-TDD- Configuration-r16 (If provided) and / or received PSBCH sl-TDD-Config-r16 (If provided) Semi-static configuration as UL. For example, higher-level parameters (e.g., MAC or RRC) can indicate values. Y As the side link start symbol of the time slot (e.g., sl-StartSymbol For example, higher-level parameters (e.g., MAC or RRC) can indicate values. X As the number of side link symbols in a time slot (e.g., sl-LengthSymbols The set contains all time slots except for one or more reserved time slots. Time slots in the set can be arranged in ascending order of their time slot indices. The UE can be based on a bitmap associated with the resource pool. To determine the set of time slots assigned to the sidelink resource pool, where the bitmap length is... Configured by a higher level. If ,in Then time slot A set of time slots that can belong to a time slot. Time slots in the set are reindexed, resulting in the remaining time slots... subscript i It is a continuous {0, 1, …, },in It represents the number of remaining time slots in the set.

[0279] The UE can determine the set of resource blocks assigned to the sidelink resource pool, where the resource pool consists of... Composed of PRBs. Sub-channel m (in, ) is composed of physical resource blocks numbered (in, )of It consists of a set of contiguous resource blocks, where and Each is determined by higher-level parameters sl-StartRB-Subchannel and sl-SubchannelSize Given. It is possible that the UE will not use the last resource in the resource pool. One PRB.

[0280] The UE can have / configured multiple symbols in the PSCCH resource pool (e.g., by...). sl- TimeResourcePSCCH (Indicated). The PSCCH symbol can start from the second symbol available for sidelink transmission in a time slot. The UE can have / configured multiple PRBs in the PSCCH resource pool (e.g., by...). sl-FreqResourcePSCCH(Representation). A PSCCH PRB can start from the lowest PRB of the lowest subchannel of the associated PSCCH, for example, for a PSCCH transmission with SCI format 1-A. In the example, PSCCH resources / symbols can be configured in each slot of the resource pool. In the example, PSCCH resources / symbols can be configured in a subset of slots of the resource pool (e.g., based on a time period comprising two or more slots).

[0281] In the example, each PSSCH transmission is associated with a PSCCH transmission. The PSCCH transmission can carry the first level of the SCI associated with the PSSCH transmission. The second level of the associated SCI can be carried within the PSSCH resource. In the example, the UE determines the time slot based on... n PSCCH resource configuration and PSCCH resources m The first SCI (e.g., Level 1 SCI, SCI format 1-A) is transmitted on the PSCCH. For associated PSSCH transmissions in the same time slot, the UE can transmit a transport block (TB) with up to two layers (e.g., one or two layers). The number of layers ( ) can be based on 'SCI' Number of DMRS ports The field determines the set of coherent symbols used for PSSCH transmission within a time slot. The UE can determine the set of contiguous resource blocks used for PSSCH transmission. Transform precoding may not be supported for PSSCH transmission. For example, wideband precoding may be supported for PSSCH transmission.

[0282] The UE can set the content of the second SCI (e.g., Level 2 SCI, SCI format 2-A). The UE can set the values ​​of SCI fields as indicated by higher layers (e.g., MAC and / or RRC), including... 'HARQ process number' Field, ' NDI 'field,' source ID 'field,' Destination ID 'field,' HARQ Feedback Enable / Disable Indicator 'field,' Broadcast type indicator 'fields and / or' CSI Request 'Fields. The UE can set the content of the second SCI (e.g., Level 2 SCI, SCI format 2-B). The UE can set the values ​​of SCI fields as indicated by higher layers (e.g., MAC and / or RRC), including...' 'HARQ process number' Field, ' NDI 'field,' Source ID 'field,' Destination ID 'field,' HARQ Feedback Enable / Disable Indicator 'field,' Region ID 'fields and / or' Communication range requirements 'Field'.

[0283] In the example, a transmission scheme can be defined for PSSCH, and this scheme can be used for all PSSCH transmissions. PSSCH transmissions can be performed using at most two antenna ports, for example, antenna ports 1000-1001.

[0284] In sidelink resource allocation mode 1, dynamic granting, configured grant type 1, and / or configured grant type 2 can be supported for PSSCH and / or PSCCH transmissions. Configured grant type 2 sidelink transmissions are semi-persistently scheduled by SL granting in an active DCI.

[0285] The UE can transmit the PSSCH in the same time slot as the associated PSCCH. The (minimum) resource allocation unit in the time domain can be a time slot. The UE can transmit the PSSCH in consecutive symbols within a time slot. The UE may not transmit the PSSCH in symbols not configured for sidelinks. The UE will start transmitting the sidelink symbol according to the indication (e.g., startSLsymbols ) and multiple coherent sidelink symbols (e.g., lengthSLsymbols The higher-level parameters of the symbol can be configured for use in side links. For example, startSLsymbols It is configured for the side link. lengthSLsymbols The symbol index of the first symbol in a coherent symbol set. Within a time slot, PSSCH resource allocation can be performed on symbols. startSLsymbols+1 (For example, the second sidelink symbol of the time slot). If PSFCH is configured in this time slot, the UE may not transmit PSSCH in the symbols configured for PSFCH. The UE may not transmit PSSCH in the last symbol configured for the sidelink (e.g., the last sidelink symbol of the time slot). If PSFCH is configured in this time slot, the UE may not transmit PSSCH in the symbols immediately preceding the symbols configured for PSFCH. Figure 19 An example of sidelink symbols and PSSCH resource allocation within a time slot is shown.

[0286] Sidelink grants can be dynamically received on the PDCCH, and / or configured semi-persistently by the RRC, and / or autonomously selected by the UE's MAC entity. The MAC entity can have sidelink grants on active SL BWPs to determine the set of PSCCH durations for which SCI transmissions occur and the set of PSSCH durations for which SL-SCH transmissions associated with the SCI occur. Sidelink grants addressed to SLCS-RNTI with NDI = 1 are considered dynamic sidelink grants. The UE can be configured with sidelink resource allocation mode 1. The UE can use sidelink grants to determine the PSCCH duration and / or PSSCH duration for each PDCCH timing and for each grant received for that PDCCH timing (e.g., for the UE's SL-RNTI or SLCS-RNTI) for the initial transmission and / or one or more retransmissions of the MAC PDU corresponding to the sidelink process (e.g., associated with the HARQ buffer and / or HARQ process ID).

[0287] The UE can be configured with sidelink resource allocation mode 2 to use a resource pool in the carrier for transmission based on sensing or random selection. The MAC entity of each sidelink process can choose to create a selected sidelink grant corresponding to the transmission of multiple MAC PDUs, and SL data can be available in the logical channel. The UE can select the resource pool, for example, based on parameters enabling / disabling sidelink HARQ feedback. The UE can perform a TX resource (reselection) selection check on the selected resource pool. The UE can select time and frequency resources for a transmission opportunity from the resource pool and / or from resources indicated by the physical layer, based on the amount of selected frequency resources and the remaining PDB of SL data available in the allowed logical channel on the carrier. The UE can use the selected resources to select a set of periodic resources spaced by resource reservation intervals for the transmission of PSCCH and PSSCH corresponding to the number of transmission opportunities for the MAC PDU. The UE can consider the first set of transmission opportunities as the initial transmission opportunity and the other sets of transmission opportunities as retransmission opportunities. The UE can consider the set of initial transmission opportunities and retransmission opportunities as the selected sidelink grant. The UE can consider the set as the selected sidelink grant. The UE can use the selected sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations.

[0288] The UE can select the allowed MCS table associated with the sidelink grant from the resource pool for each PSSCH duration and / or for each sidelink grant occurring within this PSSCH duration. The UE can determine / set the resource reservation interval to a selected value (e.g., 0 or more). In the example, if the configured sidelink grant is activated and this PSSCH duration (and, if available, all subsequent PSSCH durations occurring within this configured sidelink grant period) corresponds to the first PSSCH transmission opportunity within this configured sidelink grant period, the UE can set the HARQ process ID to the HARQ process ID associated with this PSSCH duration. The UE can clear the HARQ buffer of the sidelink process associated with the HARQ process ID. The UE can deliver the sidelink grant, the selected MCS, and the associated HARQ information to the sidelink HARQ entity within this PSSCH duration.

[0289] A MAC entity can contain at most one sidelink HARQ entity for transmissions on SL-SCH, which maintains multiple parallel sidelink processes. The (maximum) number of transmission sidelink processes associated with a sidelink HARQ entity can be a value (e.g., 16). Sidelink processes can be configured for the transmission of multiple MAC PDUs. For the transmission of multiple MAC PDUs with sidelink resource allocation mode 2, the (maximum) number of transmission sidelink processes associated with a sidelink HARQ entity can be a second value (e.g., 4). Delivered sidelink grants and their associated sidelink transmission information can be associated with sidelink processes. Each sidelink process can support one TB.

[0290] For each sidelink grant and associated sidelink process, the sidelink HARQ entity can obtain the MAC PDU to be transmitted (if present) from the multiplexing and assembly entity. The UE can determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU. The UE can set the source Layer 1 ID to 8 LSBs of the source Layer 2 ID of the MAC PDU and the destination Layer 1 ID to 16 LSBs of the destination Layer 2 ID of the MAC PDU. The UE can set the following information for the TB: broadcast type indicator, HARQ feedback enable / disable, priority, NDI, and RV. The UE can deliver the TB's MAC PDU, sidelink grant, and sidelink transmission information to the associated sidelink process. The UE's MAC entity can instruct the associated sidelink process to trigger a new transmission or retransmission.

[0291] In sidelink resource allocation mode 1, for sidelink dynamic granting, PSSCH transmissions can be scheduled by DCI (e.g., DCI format 3_0). In sidelink resource allocation mode 1, for sidelink configured granting type 2, configured granting can be activated by DCI (e.g., DCI format 3_0). In sidelink resource allocation mode 1, for both sidelink dynamic granting and sidelink configured granting type 2, the "time gap" field value of DCI... m Indexes can be used m +1 is provided to the slot offset table (e.g., the table can be generated by higher layer parameters). sl-DCI-ToSL-Trans Configuration). Index. m The value at +1 can be referred to as the time slot offset. The time slot for transmission on the first-side link scheduled by DCI can be no earlier than […]. The first SL time slot corresponding to the starting resource pool, where It is the start time of the downlink timeslot carrying the corresponding DCI. It is the timing advance value corresponding to the TAG of the serving cell on which DCI is received, and It is the time slot offset between the DCI time slot and the first-side link transmission scheduled by the DCI, and This is the SL slot duration. If provided and not reserved, the DCI's "Configuration Index" field can indicate the index of the sidelink via Configuration Type 2. In Sidelink Resource Allocation Mode 1, for sidelinks configured with Authorization Type 1, the slots transmitted on the first sidelink can follow the higher-layer configuration.

[0292] Resource allocation units in the frequency domain can be subchannels. The subchannel assignment for sidelink transmission can be determined using the “Frequency Resource Assignment” field in the associated SCI. The lowest subchannel for sidelink transmission can be the subchannel on which the lowest PRB (Period Back Buffer) of the associated PSCCH is transmitted. For example, if a PSSCH scheduled by a PSCCH would overlap with resources containing the PSCCH, then the resources corresponding to the union of the scheduled PSCCH and the associated PSCCH DM-RS may not be available for the PSSCH.

[0293] The redundant version used for transmitting TB can be given by the "Redundant Version" field in the second-level SCI (e.g., SCI format 2-A or 2-B). Modulation and coding scheme I MCS It can be derived from the first-level SCI (e.g., SCI format 1-A) ' Modulation and coding plan The field is provided. The UE can determine the MCS table based on the following: if no additional MCS table is provided, it is determined by higher-layer parameters. sl-MCS- TableIf configured, predefined tables can be used; otherwise, based on the first-level SCI (e.g., SCI format 1-A), ' MCS stands for indicator The field is used to determine the MCS table. UE can use I MCS And determine the modulation order used in the physical side link shared channel based on the MCS table determined in the previous step. Q m ) and target bitrate ( R ).

[0294] UE can be based on the number of REs within a time slot ( N RE The TB size (TBS) is determined using [the UE]. Determine the number of REs allocated to PSSCH within the PRB ( ),in It is the number of subcarriers in a physical resource block; ,in sl-LengthSymbols This is the number of sidelink symbols within a time slot provided by a higher layer; if SCI format 1-A' PSFCH Overhead Indication If the field indicates "1", then Otherwise, if higher-level parameters sl-PSFCH-Period If it is 2 or 4, then If higher-level parameters sl-PSFCH-Period If it is 0, then If higher-level parameters sl-PSFCH-Period If it is 1, then . These are higher-level parameters. sl-X-Overhead The given cost. From higher level parameters sl-PSSCH-DMRS-TimePattern Provided. UE can be accessed via Determine the total number of REs allocated to PSSCH ( ),in n PRB It is the total number of PRBs allocated to PSSCH; This is the total number of REs occupied by PSCCH and PSCCH DM-RS; This is the number of coded modulation symbols generated for the second-level SCI transmission (if present, before the second-level replication). The UE can base this on the total number of REs allocated to the PSSCH ( ) and / or the modulation order used in the physical side link shared channel ( Q m ) and target bitrate ( R To determine TBS.

[0295] For a single codeword of PSSCH , bit block ,in On the physical channel The number of bits in the transmitted codeword can be scrambled before modulation (e.g., using a scrambling sequence based on the CRC of the PSCCH associated with the PSSCH). For a single codeword It can modulate scrambling bit blocks, thereby generating complex-valued modulation symbol blocks. ,in Layer mapping can be done using the number of layers. To complete, thereby generating , It is possible to work on vector blocks. Precoding, where the precoding matrix It equals the identity matrix, and For each antenna port used for PSSCH transmission, a complex value symbol block... Can be used with amplitude scaling factor Multiply to match the transmission power and map to resource elements in the virtual resource block assigned for transmission. ,in This assigns the first subcarrier in the lowest-numbered virtual resource block used for transmission. The mapping operation can be completed in two steps: First, the complex-valued symbols corresponding to the second-level SCI are mapped in the following ascending order—first the index on the assigned virtual resource block. Then, the index starts from the first PSSCH symbol carrying the associated DM-RS. The corresponding resource element in the corresponding physical resource block is not used for the transmission of the associated DM-RS, PT-RS, or PSCCH; secondly, complex-valued modulation symbols not corresponding to the second-level SCI are mapped in the following ascending order—first, the index on the assigned virtual resource block. Next is the index of the starting position. The resource element is not used for the second-level SCI in the first step; and / or the corresponding resource element in the corresponding physical resource block is not used for the transmission of the associated DM-RS, PT-RS, CSI-RS or PSCCH.

[0296] Resource elements of the PSSCH (containing DM-RS, PT-RS and / or CSI-RS appearing in the first OFDM symbol) used in the above mapping operation can be copied in the OFDM symbol immediately preceding the first OFDM symbol in the mapping (e.g., for AGC training purposes).

[0297] Virtual resource blocks can be mapped to physical resource blocks based on non-interleaved mapping. For non-interleaved VRB to PRB mapping, virtual resource blocks... Mapped to physical resource blocks .

[0298] For PSCCH, bit block (in (This refers to the number of bits transmitted over the physical channel) can be scrambled before modulation, thus according to... Generate scrambling bit blocks QPSK modulation scrambling blocks can be used. This generates complex-valued modulation symbol blocks. ,in Complex-valued modulation symbol set Can be used with amplitude scaling factor Multiply to match the transmission power, and from Begin mapping sequentially to the resource elements assigned for transport. And not used for the demodulation reference signal associated with the PSCCH, proceeding in the following ascending order—first the index on the assigned physical resource. Next is the index on antenna port p. (For example, ).

[0299] The resource elements of the PSCCH (containing DM-RS, PT-RS and / or CSI-RS appearing in the first OFDM symbol) used in the above mapping operation can be copied in the immediately preceding OFDM symbol (e.g. for AGC training purposes).

[0300] For sidelink resource allocation mode 1, upon detecting a first SCI (e.g., SCI format 1-A) on the PSCCH, the UE can decode the PSSCH based on the detected second SCI (e.g., SCI formats 2-A and / or 2-B) and the associated PSSCH resource configuration configured by the higher layer. It may not be necessary for the UE to decode more than one PSCCH at each PSCCH resource candidate. For sidelink resource allocation mode 2, upon detecting a first SCI (e.g., SCI format 1-A) on the PSCCH, the UE can decode the PSSCH based on the detected second SCI (e.g., SCI formats 2-A and / or 2-B) and the associated PSSCH resource configuration configured by the higher layer. It may not be necessary for the UE to decode more than one PSCCH at each PSCCH resource candidate. If the first SCI indicates an MCS table that the UE does not support, the UE may be required to decode the corresponding second SCI (e.g., SCI formats 2-A and / or 2-B) or the PSSCH associated with the first SCI (e.g., SCI format 1-A).

[0301] Throughout this disclosure, a set (subset) of symbols for a time slot associated with a resource pool of a sidelink BWP (Pre-configured for sidelink communication, e.g., transmission and / or reception) may be referred to as a 'sidelink symbol' for the time slot. A sidelink symbol can be a consecutive / coherent symbol of the time slot. A sidelink symbol may begin with a sidelink start symbol (e.g., indicated by an RRC parameter), such as symbol #0 or symbol #1. A sidelink symbol may include one or more symbols of the time slot, where a parameter (e.g., indicated by an RRC parameter) may indicate the number of sidelink symbols for the time slot. A sidelink symbol may include one or more protection symbols, e.g., providing a time slot for the UE to switch from transmission mode to reception mode. For example, an OFDM symbol immediately following the last symbol used for PSSCH, PSFCH, and / or S-SSB may be used as a protection symbol. Figure 19 As shown, a sidelink symbol may include one or more PSCCH resources / timings and / or one or more PSCCH resources and / or zero or more PSFCH resources / timings. A sidelink symbol may include one or more AGC symbols.

[0302] AGC symbols may include copies of the content of resource elements of the immediately following / following symbols (e.g., TB and / or SCI may be mapped to the immediately following symbol). In the example, an AGC symbol may be a dummy OFDM symbol. In the example, an AGC symbol may include a reference signal. For example, the first OFDM symbol of the PSSCH and its associated PSCCH may be copied (e.g., in the AGC symbol immediately preceding the first OFDM symbol of the PSSCH). For example, the first OFDM symbol of the PSFCH may be copied (e.g., for AGC training purposes).

[0303] In the sidelink time-slot configuration, the first symbol is used for Automatic Gain Control (AGC), and the last symbol is used for the gap. During the AGC symbol, the receiving and / or sensing UE can perform AGC training. For AGC training, the UE detects the energy / power of the signal in the channel during the AGC symbol and applies hardware gain to maximize the signal amplitude to the dynamic range of the analog-to-digital converter (ADC) at the receiver. The receiver can determine the gain of the received signal, and the AGC duration allows the receiver time to determine and apply the gain (e.g., a hardware gain component) so that when the receiver (e.g., in the following symbol) receives data, the amplifier gain has been adjusted.

[0304] For sidelink communication, the transmitter (UE) may not map data / control information to AGC symbols. AGC symbols cannot be used to transmit or send information other than energy. An AGC symbol can be the last symbol before the earliest transmitted symbol, minimizing the gap between the AGC symbol and signal / channel transmission, and determining the accurate gain for receiving subsequent signals / channels. For example, as... Figure 19 As shown, an AGC symbol can be a symbol that immediately precedes the first / earliest symbol of a resource used for transmission via the channel (e.g., PSCCH and / or PSSCH and / or PSFCH transmission).

[0305] In the example, an AGC symbol may include resource elements that copy the next (immediately following) OFDM symbol. In the example, an AGC symbol may include any signal, such as predefined signals / sequences and / or dummy information. The purpose of an AGC symbol is to allow the receiver UE to perform AGC training and adjust the hardware gain for most efficient reception of subsequent signals.

[0306] Throughout this disclosure, "AGC symbol" may be referred to as "replication symbol" and / or "replication" and / or "symbol for replication" and / or "the preceding symbol that includes a copy of the first symbol".

[0307] Figure 28 An example of a sidelink CSI-RS transmission and sidelink CSI reporting procedure according to an exemplary embodiment of this disclosure is shown. A first radio device (transmitter UE) may initiate (trigger, execute, run, and / or apply) a sidelink RRC reconfiguration procedure with a second radio device (receiver UE). The purpose of the sidelink RRC reconfiguration procedure may include instructing (e.g., configuring or reconfiguring) one or more parameters related to sidelink measurements and reporting, instructing (e.g., configuring or reconfiguring) sidelink CSI reference signal resources, and / or instructing (e.g., configuring or reconfiguring) CSI reporting wait time limits.

[0308] For example, refer to Figure 28 The first wireless device may initiate a sidelink RRC reconfiguration procedure on (e.g., for) a corresponding PC5-RRC connection and / or PC5 link (e.g., established between the first and second wireless devices). In the example, in response to initiating the sidelink RRC reconfiguration procedure or after initiating the sidelink RRC reconfiguration procedure, the first wireless device may transmit a message (e.g., an RRC message, such as...) to the second wireless device. RRCReconfigurationSidelink For example, the message may include one or more parameters, such as... Figure 28 The SL CSI RS configuration parameters. One or more parameters can include sl-LatencyBoundCSI-Report (For example, Figure 28 (Waiting time limit in the middle). sl-LatencyBoundCSI-Report (For example, the side link waiting time limit in Figure 32) can instruct the SL CSI to report the waiting time limit. 。 For SL CSI-RS transmission (and / or reception), one or more parameters included in the message may include: time resource allocation and / or time resource offset (e.g., sl-CSI-RS- FirstSymbol ), which indicates the first OFDM symbol in the PRB of the SL CSI-RS (e.g., if / when a sidelink CSI report is triggered, carried); and / or frequency resource allocation and / or frequency resource offset (e.g., sl-CSI-RS- FreqAllocation The frequency resource allocation and / or frequency resource offset can be initiated from the reference symbol in the time slot of the SCI indicating the SL CSI-RS report received by the radio device. For example, the reference symbol could be the first symbol of the time slot, the first symbol of the PSCCH transmission in the time slot, or the first symbol of the PSSCH transmission in the time slot. The frequency resource allocation and / or frequency resource offset can be initiated from the reference PRB (or RB or subchannel) in the time slot of the SCI indicating the SL CSI-RS report received by the radio device. For example, the reference PRB (or RB) could be the lowest PRB (or RB) in the frequency domain of the PSSCH transmission (e.g., carrying the PSSCH transmission). For example, the reference subchannel could be the lowest subchannel in the frequency domain of the PSSCH transmission (e.g., carrying the PSSCH transmission). For example, the reference PRB (or RB) could be the lowest PRB (or RB) of the lowest subchannel in the frequency domain that carries the PSSCH transmission (e.g., the lowest PRB of the PSSCH transmission).

[0309] In the example, refer to Figure 28 The first wireless device may transmit sidelink transmissions including SCIs via time slots (e.g., a single time slot), the sidelink transmissions including values ​​of fields (e.g., and / or indicators) for transmissions that trigger (e.g., indicate triggering) SL CSI reports and / or SLCSI-RS transmissions. For example, the sidelink transmissions may include a first sidelink transmission via a time slot and a second sidelink transmission via a time slot. The first sidelink transmission may be a PSCCH transmission including a first-level SCI (e.g., PSCCH) (e.g., as...). Figure 19 (As shown). The second-side link transmission can be a PSSCH transmission (e.g., PSSCH) that includes second-level SCI and SL-SCH data (e.g., including MAC PDU, MAC SDU, and / or MAC CE). Figure 19(As shown). The SCI that triggers the SL CSI report can be at least one of a Level 1 SCI and / or a Level 2 SCI. The first radio device can transmit the sidelink CSI-RS within or via a PSSCH transmission. The sidelink transmission can be a unicast transmission. The PSSCH transmission can be a unicast PSSCH transmission.

[0310] refer to Figure 28 For example, at least one of the first-level SCI and / or the second-level SCI may include a destination identifier associated with a unicast PC5 link (e.g., ProSe and / or the V2X application layer / server sends the destination identifier to the first wireless device). The second wireless device may receive sidelink transmissions. The second wireless device may determine that the destination identifier in the sidelink transmission matches the identifier of the second wireless device. The second wireless device may determine that the value of a field in the SCI indicates the triggering of a sidelink CSI report (e.g., triggering a sidelink CSI report). For example, if the second wireless device determines that the destination identifier in the sidelink transmission matches the identifier of the second wireless device, and / or if the value of a field in the SCI indicates the triggering of a sidelink CSI report (e.g., triggering a sidelink CSI report), then the second wireless device may determine to transmit (e.g., may transmit) a sidelink CSI report to the first wireless device.

[0311] In the example, for instance, refer to Figure 28 If, for example, the second wireless device determines a transmission (e.g., transmission) sidelink CSI report (e.g., in response to this and / or after this), the second wireless device may start a timer or window (e.g., sl-CSI-ReportTimer For example, if, for instance, the first wireless device transmits an SCI triggered by an indication of an SL CSI report (e.g., in response to this and / or after this), the first wireless device may initiate a second timer or second window that is the same as the timer or window initiated by the second wireless device (e.g., sl-CSI-ReportTimer The second wireless device may transmit a sidelink CSI report before the timer expires and / or while the timer is running. The SL wait time limit in Figure 32 can be the value of the timer. For example, the timer may run for a duration indicated by the SL wait time limit.

[0312] In the example, refer to Figure 28 For example, a second wireless device configured with resource allocation mode 1 receives an authorization from the base station indicating sidelink resources (e.g., Figure 28The sidelink resources are used to transmit SL CSI reports to the first radio device and / or within an SL waiting time limit starting from the start time of the timer (e.g., occurring thereafter). For example, if the second radio device does not have an SL authorization to transmit an SL CSI report, the second radio device may transmit a scheduling request to the base station to receive an authorization (e.g., an SL authorization in Figure 32). The base station may, for example, respond to receiving a scheduling request from the second radio device and / or transmit an authorization (e.g., an SL authorization in Figure 32) to the second radio device thereafter. For example, the second radio device configured with resource allocation mode 2 selects sidelink resources for transmitting SL CSI reports to the first radio device and / or within an SL waiting time limit starting from the start time of the timer.

[0313] In the example, refer to Figure 28 The second wireless device may, for example, transmit a sidelink CSI report to the first wireless device via sidelink resources (indicated by the SL grant in FIG32 or selected by the second wireless device configured with resource allocation mode 2) before the timer expires, while the timer is running, and / or within a waiting time limit starting from the timer's start time. For example, if the timer runs for the duration indicated by the waiting time limit, the second wireless device may determine that the timer has expired. For example, if (e.g., the second wireless device determines) the timer has expired and / or if the second wireless device does not transmit a sidelink CSI report before / until the timer expires, while the timer is running, and / or within a waiting time limit starting from the timer's start time, the second wireless device may cancel the triggered sidelink CSI report (e.g., the transmission of the sidelink CSI report may be cancelled).

[0314] The conditions for the first wireless device to transmit sidelink CSI-RS may include: 1) the sidelink CSI report is generated by higher-layer parameters (e.g., sl-CSI-Acquisition ) Enabled; and 2) the corresponding field in the SCI (e.g., SCI format 2-A) (e.g., ' CSI Request The field is set to 1. The corresponding SCI can schedule PSSCH (e.g., for PSSCH decoding). The first wireless device can set the field as indicated by the higher layer. CSI Request The value of the field (e.g., set to 1). When the first wireless device is configured in the side link. Q p ={1,2} sidelink CSI-RS ports and the number of scheduling layers is At that time, the side-link CSI-RS scaling factor Depend on Given, among which It is the scaling factor for the corresponding PSSCH.

[0315] The SL CSI report may include SL CSI. The SL CSI may include information and / or one or more measurements instructing a second wireless device to determine and / or measure the channel state based on a sidelink CSI-RS received from a first wireless device. For example, the information and / or one or more measurements may include CQI, RI, LI, CRI, PMI, L1-RSRP, L1-SINR, and / or any combination thereof. The second wireless device may transmit the SL CSI to the first wireless device via the SL CSI report. CQI and RI may be reported together. The procedure for transmitting the SL CSI report (and generating the sidelink CSI) may be represented as an SL CSI report. The CSI report may be aperiodic or periodic. The configured SL CSI-RS may be aperiodic, semi-persistent, or periodic.

[0316] In embodiments of the invention, for example, if CSI-RS is transmitted via / as a sidelink transmission, then SL CSI-RS can be interchanged with CSI-RS and / or referred to as CSI-RS. In embodiments of the invention, for example, if the CSI in a CSI-RS report includes information and / or one or more measurements indicating that a wireless device can determine and / or measure the channel state based on SL CSI-RS received from another wireless device, then SL CSI report / reporting can be interchanged with CSI-RS report / reporting and / or referred to as CSI-RS report.

[0317] In the example, refer to Figure 28 CSI reports triggered by an SCI can be aperiodic CSI reports. An SCI (e.g., SCI format 2-A) may include a 'CSI Request' field with a value set to 1, indicating (e.g., aperiodic) CSI report triggering. A first wireless device (e.g., the wireless device triggering the CSI or the wireless device transmitting CSI-RS) may not be allowed to trigger (e.g., aperiodic) CSI reports for the same wireless device (e.g., a second wireless device) before / until the expiration of the SL CSI report timer, or before / until the receipt of a CSI report triggered by an SCI (e.g., SCI format 2-A) with a 'CSI Request' field set to 1. It may be undesirable for the second wireless device to transmit overlapping sidelink CSI-RS and sidelink PT-RS.

[0318] exist Figure 28In this context, the second wireless device can receive messages including SL CSI RS configuration parameters (e.g., RRC messages and / or RRCReconfigurationSidelink The message may include... SL-CSI-RS-Config . SL-CSI- RS-Config This can include SL CSI RS configuration parameters, such as sl-CSI-RS- FreqAllocation , sl-CSI-RS- FirstSymbol It indicates the resource allocation of SL CSI-RS in the frequency and time domains.

[0319] Figure 29 An example of resource allocation for SL CSI RS according to an exemplary embodiment of this disclosure is shown. Figure 28 The SL CSI RS configuration parameters transmitted by the first radio device and / or received by the second radio device can indicate the start frequency and start time of the SL CSI-RS in the time slot of the SCI that triggers the SL CSI report transmitted by the first radio device. For example, the SL CSI RS configuration parameters can indicate the number of symbols carrying the SL CSI RS and / or the number of REs and / or the number of PRBs.

[0320] The second radio device can determine (e.g., assume) the non-zero transmission power of the SL CSI-RS. The SL CSI-RS and PSCCH (located in the same time slot and / or scheduling a PSSCH carrying the SL CSI-RS) may not be mapped to the same resource element. The SL CSI-RS and PSSCH DM-RS may not be scheduled, mapped, and allocated in the same symbol. The SL CSI-RS and SCI (Level 1 CSI and / or Level 2 SCI) may not be scheduled, mapped, and allocated in the same symbol. The first radio device can transmit the SL CSI-RS in a resource block used for transmitting the PSSCH (e.g., SCI format 2-A carrying the scheduled PSSCH), thereby triggering an SL CSI report including the SL CSI measured based on the SL CSI-RS. The second radio device can, for example, receive from the first radio device an SL latency limit configured for different SL CSI-RS transmissions. sl-LatencyBoundCSI- Report .

[0321] In the example, SL CSI reporting (e.g., an SL CSI reporting procedure) can be used to provide sidelink CSI to the peer wireless device (the first wireless device). For example, SL wait time limits can be defined, configured, and / or received based on (e.g., for) each PC5-RRC connection. sl-LatencyBoundCSI-ReportFor example, the second wireless device can receive from the first wireless device a first SL waiting time limit for a first PC5-RRC connection and / or a first PC5 link established with the first wireless device. For example, the second wireless device can receive from the third wireless device a second SL waiting time limit for a second PC5-RRC connection and / or a second PC5 link established with the third wireless device.

[0322] In the example, the MAC entity (of the first and / or second wireless devices) can maintain a timer for each pair of source Layer 2 IDs and destination Layer 2 IDs corresponding to the PC5-RRC connection (e.g., sl-CSI-ReportTimer , Figure 28 (SL CSI report timer in the middle). sl-CSI-ReportTimer This can be used for SL-CSI reporting wireless devices (e.g., a second wireless device) to comply with the waiting time requirement for signal notification from a CSI reporting triggering wireless device (e.g., a first wireless device). sl-LatencyBoundCSI-Report ). sl-CSI-ReportTimer The value (e.g., the initial value) can be related to the value configured by RRC. sl-LatencyBoundCSI-Report The waiting time requirement for SL-CSI reports is the same. The value indicates... sl-CSI-ReportTimer The (e.g., maximum) runtime. If sl-CSI-ReportTimer The wireless device can determine the duration indicated by the value. sl-CSI-ReportTimer Expiration. If the wireless device receives a CSI report, the wireless device can stop. sl-CSI-ReportTimer For each pair of source Layer 2 IDs and destination Layer 2 IDs corresponding to the established PC5-RRC connection at the upper layer, the MAC entity can: 1> If SL-CSI Report If it has been triggered by SCI and has not been canceled, then: 2> If the SL-CSI report used for triggering sl-CSI-ReportTimer If not running, then: 3> Start sl-CSI-ReportTimer (For example, t0 in Figure 32) 2> If the SL-CSI report used for triggering sl-CSI-ReportTimer If it expires, then: 3. Cancel the triggered SL-CSI report. (For example, t2 in Figure 32) 2> Otherwise, if the MAC entity has SL resources allocated for the new transmission, and as a result of logical channel priority ordering, the SL-SCH resources can be used to report the MAC CE and its subheadings to the SL-CSI, then: 3> Instructions for the multiplexing and assembly process to generate a sidelink CSI report MAC CE; 3> Stop using SL-CSI reports that are triggered sl-CSI-ReportTimer (For example, t1 in Figure 32) 3> Cancel the triggered SL-CSI report.

[0323] 2> If the MAC entity is already configured with sidelink resource allocation mode 1, then: 3> Trigger a scheduling request.

[0324] For example, if a wireless device triggers an SL CSI report, the wireless device can determine that the SL CSI report is pending (e.g., until the SL CSI report is cancelled). If the transmission of a pending SL-CSI report with sidelink authorization cannot meet the waiting time requirement associated with the SL-CSI report, a MAC entity configured with sidelink resource allocation mode 1 can trigger a scheduling request (e.g., Figure 28 ).

[0325] Figure 30 An example of an SL CSI report according to an exemplary embodiment of this disclosure is shown. For example, an SLCSI report may include a MAC CE containing an SL CSI. For example, a MAC CE may be a sidelink CSI report MAC CE identified by a MAC subheader with a predefined LCID. The priority of the sidelink CSI report MAC CE is fixed to a predefined value (e.g., '1' indicating the highest priority). Figure 30 In this context, RI can be a field indicating the value of a rank indicator derived from measurements taken by the SL CSI-RS for side-link CSI reporting. The length of the RI field is predefined (e.g., 1 bit). Figure 30 In this context, CQI can be a field indicating the value of a channel quality indicator used for sidelink CSI reporting, derived from measurements taken by the SL CSI-RS. The length of the CQI field can be predefined (e.g., 4 bits). Figure 30 In this context, R can indicate one or more reserved bits that are set to a predefined value (e.g., 0).

[0326] In the example, sidelink transmissions can be beam-centric. For instance, between peer wireless devices, transmissions of PSCCH, PSSCH, and / or PSFCH can be performed via, through, and / or using a specific beam. Sidelink reference signals (e.g., SL SSB and / or SL CSI-RS) can represent the specific beam used for sidelink transmissions.

[0327] In a side link, a wireless device can perform beam scanning for beam-centric side link transmissions. For example, as a beam scan, a first wireless device can transmit multiple side link reference signals (SL RS) (e.g., SL CSI-RS) to a second wireless device, each of the multiple SL RSs corresponding to (e.g., associated with) a specific beam of the first wireless device.

[0328] Beam scanning can be used for sidelink unicast links between a pair of sources (e.g., identified / indicated by a source identifier) ​​and a destination (e.g., identified / indicated by a destination identifier). A sidelink unicast link can refer to a direct communication link established between a pair of sources and destinations. Sidelink unicast links can be referred to as PC5 (Proximity Services Communication 5) links, PC5 unicast links, PC5-RRC connections, etc. For example, a PC5-RRC connection can refer to a PC5 link that sets up / establishes an RRC layer between a source and a destination.

[0329] Figure 31A and Figure 31B An example of an SL RS according to an exemplary embodiment of the present disclosure is shown. For example, such as Figure 31A As shown, the first wireless device can transmit multiple SL RSs (e.g., a group / set of SL RSs) corresponding to (e.g., associated with) a corresponding beam scan within a sidelink time slot. For example, as... Figure 31B As shown, the first wireless device can transmit multiple SL RSs (e.g., a group / set of SL RSs) corresponding to (e.g., associated with) a respective beam scan via (e.g., across) multiple side link time slots. The first wireless device can transmit via (e.g., across) multiple side link time slots. Figure 31B Each side link time slot transmits one or more SL RS.

[0330] Figure 31A and / or Figure 31BMultiple SL RSs are associated with a specific set or group (e.g., beam scan) of SL RS transmissions. For example, each of the multiple SL RSs is associated with the same set or group. For example, a set or group (e.g., associated with or including one or more SL RSs) may be associated with a specific beam scan of SL RS transmissions. Each set or group (or its corresponding beam scan) may be associated with a specific purpose of SL RS transmissions. For example, a specific set or group (or its corresponding beam scan) may be for periodic transmissions of multiple SL RSs, non-periodic transmissions of multiple SL RSs and / or semi-persistent transmissions of multiple SL RSs, transmissions of multiple SL RSs for initial beam pairing procedures, transmissions of multiple SL RSs for beam management procedures, transmissions of multiple SL RSs for beam failure detection / recovery procedures, and / or any combination thereof. For example, a first wireless device may transmit a message to a second wireless device including multiple configurations (e.g., Configuration IE, SL-CSIRS-ResourceConfig IE, etc.). Each of the multiple configurations may be associated with a corresponding set (or group) in a set (or group). Each of the plurality of configurations may include a corresponding configuration identifier (or alternatively, a corresponding set identifier or a corresponding group identifier) ​​indicating the corresponding set (or group) among the plurality of sets (or groups). Each of the plurality of configurations may include parameters indicating one or more SL RSs associated with the corresponding set (or group).

[0331] exist Figure 31A and Figure 31B In this context, the first wireless device can transmit SLRS to the second wireless device, the SLRS having an indication of a set and / or group associated with the SLRS. For example, in... Figure 31A In a sidelink time slot, a first wireless device may transmit control information (e.g., SCI, first-level SCI, and / or second-level SCI) to a second wireless device. This control information includes field values ​​(e.g., set identifier, group identifier, and / or configuration identifier) ​​indicating a set and / or group associated with the SL RS. For example, the first wireless device transmits control information via a sidelink time slot of the SL RS. The second wireless device may determine that the control information (including field values) indicates that the transmission of the SL RS associated with the set and / or group (indicated by field values ​​in the SCI) is in a sidelink time slot. Figure 31B In, for example, in Figure 31BIn at least one of the three sidelink time slots (e.g., the first positioned sidelink time slot or all three sidelink time slots), the first wireless device may transmit control information (e.g., SCI, first-level SCI, and / or second-level SCI) to the second wireless device. This control information includes field values ​​(e.g., set identifier, group identifier, and / or configuration identifier) ​​indicating a set and / or group associated with the SL RS. The second wireless device may determine that the control information (including field values) indicates that the transmission of the SL RS associated with the set and / or group (indicated by the field values ​​in the SCI) is in at least one sidelink time slot and / or in all three sidelink time slots.

[0332] Figure 32A An example of SL RS transmission according to one aspect of an embodiment of this disclosure is shown. A first wireless device may transmit SL RS (e.g., SL CSI RS), such as each of the SL RS (e.g., SL CSI-RS), and (e.g., unicast) PSSCH to a second wireless device in a sidelink (e.g., same) time slot. Figure 32A As shown in the diagram. For example, the first wireless device can transmit multiple SL RS and PSSCH in the same sidelink time slot. The first wireless device can transmit Figure 32A The SL RS in the image can be used for beam scanning (e.g., initial beam pairing procedure, beam management procedure, and / or beam fault detection / recovery procedure). Figure 32A SL RS in the text can be Figure 31A At least one of the SL RSs in the 31B, or any one of the SL RSs in one of the three side link slots in the 31B. Figure 32A The side link time slot in the middle can be Figure 31A The side link time slot in the middle, or Figure 31B Any one of the side link time slots in the network.

[0333] Figure 32A An example of SL RS transmission according to an exemplary embodiment of this disclosure is shown. For example, SLRS can be multiplexed with PSSCH in different ways within a sidelink (e.g., the same) time slot. In the example, one or more PSSCHs may first reside in a sidelink time slot, followed by one or more SLRSs in the same sidelink time slot. In the example, SL RSs may first reside in a sidelink time slot, followed by one or more PSSCHs in the same sidelink time slot. In the example, one or more PSSCHs may be allocated between two SLRSs in a sidelink time slot. Transmitting SL RSs and PSSCHs in the same time slot can be referred to as non-independent transmission of SL RSs, etc. Figure 32AIn this configuration, the first wireless device may transmit PSCCH and / or SCI in a sidelink time slot, wherein the first wireless device transmits SL RS and / or PSSCH. The PSCCH and / or SCI may include one or more fields, the values ​​of which indicate at least one of the following: the number of SL RSs in the sidelink time slot, the start position (symbol) of each SL RS in the sidelink time slot, the end position (symbol) of each SL RS in the sidelink time slot, or the frequency resource allocation of each SL RS in the sidelink time slot.

[0334] Figure 32B An example of SL RS transmission according to one aspect of an embodiment of the present disclosure is shown. A first wireless device may transmit each of the SL RS (e.g., SL CSI RS), such as each of the SL RS (e.g., SLCSI-RS), to a second wireless device in the same time slot, without transmitting (e.g., unicast) PSSCH, as... Figure 32B As shown in the diagram, the first wireless device can transmit... Figure 32B The SL RS in the image can be used for beam scanning (e.g., initial beam pairing procedure, beam management procedure, and / or beam fault detection / recovery procedure). Figure 32B SL RS in the text can be Figure 31A At least one of the SL RSs in the 31B, or any one of the SL RSs in one of the three side link slots in the 31B. Figure 32A The side link time slot in the middle can be Figure 31A The side link time slot in the middle, or Figure 31B Any one of the side link time slots in the network.

[0335] like Figure 32B As shown, transmitting SL RS but not PSSCH in a side link time slot can be referred to as independent transmission of SL RS, etc. Figure 32B In this configuration, the first wireless device may transmit PSCCH and / or SCI in a sidelink (e.g., the same) time slot, wherein the first wireless device transmits SL RS. The PSCCH and / or SCI may include one or more fields, the values ​​of which indicate at least one of the following: the number of SL RS in the sidelink time slot, the start position (symbol) of each SL RS in the sidelink time slot, the end position (symbol) of each SL RS in the sidelink time slot, or the frequency resource allocation of each SL RS in the sidelink time slot.

[0336] In the example, the transmission of SL RS can be the transmission of SL RS (e.g., SL CSI-RS) sequences. For example, the SL RS sequence can be generated by... The first wireless device can generate a sequence according to a predefined formula. For example, sequences It can be . It can be a pseudo-random sequence. It can be used at the beginning of each OFDM symbol. initialization. It can be a time slot number (or index) within a radio frame. This could be the OFDM symbol number (or index) within the time slot. In the example, the first wireless device could be connected via a time slot containing an OFDM symbol number. The symbol is used to transmit SL RS. In the example, the parameter sl-CSI-RS- FirstSymbol It can indicate OFDM symbol number The second wireless device can receive SL RS via symbols within a time slot.

[0337] The first wireless device can transmit multiple SL RSs (e.g., SL CSI RSs) (e.g., for SL beam management) via multiple OFDM symbols within a time slot, such as... Figure 31A , Figure 31B , Figure 32A and / or Figure 32B As shown in the diagram. The first wireless device can transmit multiple SL RS and PSSCH (e.g., in time slots) within a time slot. Figure 32A (in) or transmit SL RS in a time slot but not PSSCH (in) Figure 32B (In the context of the original text). For example, if a first wireless device transmits multiple SL RSs and PSSCHs in the same time slot, the multiple SL RSs and PSSCHs can occupy different OFDM symbols in the time slot (or be carried on or scheduled within the different OFDM symbols). Multiple OFDM symbols can be assigned to SL RSs. An indication (e.g., a field of the SCI within the time slot) can indicate the presence of an SL RS for beam measurement in the transmission of PSSCH. For example, a 1-bit field in SCI format 1-A can inform (or indicate) that the transmitting SL RS is used for beam management.

[0338] In the exemplary embodiments of this disclosure, beam scanning may refer to or include transmissions of multiple SL RSs from one wireless device to another. Transmissions of multiple SL RSs may occur over a single time slot during multiple symbols (e.g., Figure 31A ) or occur via multiple time slots / across multiple time slots (e.g., Figure 31BEach of the multiple SL RSs can be associated with or grouped into the same configuration IE (e.g., sl-CSIRS-ResourceConfig IE, etc.), the same set, and / or the same group. The same configuration IE (e.g., sl-CSIRS-ResourceConfig IE, etc.), the same set, and / or the same group are identified by the corresponding identifier (e.g., configuration id, set id, group id, etc.).

[0339] SL RS can be referred to by different terms or indicated by different terms. For example, SL TCI status, SL SRI, and SL beam can be used to refer to SL RS. For example, an SL configuration may include a first SL TCI status or a first SL SRI field (or container or IE) that includes a first SL RS (e.g., an SL CSI RS), is coupled to a first SL RS, or is associated with a first SL RS. In this case, the first SL TCI status or the first SL SRI field (or container or IE) can be used as a term to indicate the first SL RS. Similarly, in this case, the first SL RS can be used as a term to indicate the first SL TCI status or the first SL SRI field (or container or IE).

[0340] Each of the plurality of SL RSs can be associated with a corresponding spatial filter of the wireless device. For example, the first wireless device can: determine to transmit the first SL RS of the plurality of SL RSs to the second wireless device using a first TX spatial filter; determine to transmit the second SL RS of the plurality of SL RSs to the second wireless device using a second TX spatial filter; and so on. For example, if the first SL RS and the second SL RS are associated with the same TX spatial filter, the first wireless device and / or the second wireless device can determine that the first SL RS and the second SL RS are quasi-co-located. If the first SL RS and the second SL RS are linked to the same SLTCI or SL SRI or associated with the same SL TCI or SL SRI, the first wireless device and / or the second wireless device can determine that the first SL RS and the second SL RS are quasi-co-located.

[0341] For example, if the first SL RS and the second SL RS are associated with the same TX spatial filter, the first wireless device and / or the second wireless device can determine that the first SL RS and the second SL RS are quasi-co-located. If the first SL TCI (or the first SLSRI) and the second SL TCI (or the second SL SRI) are linked to or associated with the same SL RS, the first wireless device and / or the second wireless device can determine that the first SL TCI and the second SL TCI are quasi-co-located.

[0342] For example, an SL TCI can be referred to as an SL TCI state or used interchangeably with an SL TCI state. An SL TCI (or its configuration) may include a corresponding SL TCI identifier or be associated with a corresponding SL TCI identifier. The SL TCI identifier can be used to indicate the corresponding SL TCI. An SL SRI (or its configuration) may include a corresponding SL SRI identifier or be associated with a corresponding SL SRI identifier. The SL SRI identifier can be used to indicate the corresponding SL SRI. An SL RS (or its configuration) may include a corresponding SL RS identifier or be associated with a corresponding SL RS identifier. The SL RS identifier can be used to indicate the corresponding SL RS.

[0343] During beam scanning of multiple SL RSs transmitted from the first wireless device to the second wireless device, the second wireless device may determine a preferred SL beam or preferred SL beam pair. For example, (e.g., preferred) the SL beam or preferred SL beam pair may be represented or identified by a corresponding SL TCI, SL SRI, or SL RS. For example, the second wireless device may determine a measurement (e.g., RSRP or RSRQ) for each of the multiple SL RSs. The second wireless device may determine or select a preferred SL beam in response to the measurement satisfying one or more conditions (e.g., an RSRP value greater than or equal to an RSRP threshold).

[0344] During beam scanning, the second wireless device may determine / select its corresponding (e.g., preferred) RX spatial filter for the SL beam. The determined / selected preferred SL beam and the determined / selected RX spatial filter may be referred to as (e.g., preferred) SL beam pair. The second wireless device may transmit a signal or message (e.g., CSI report) to the first wireless device indicating the selected (e.g., preferred) SL beam and / or (e.g., preferred) SL beam pair. For example, the signal or message (e.g., CSI report) may include a field indicating an SLTCI, SL SRI, or SL RS identifier associated with the selected (e.g., preferred) SL beam and / or (e.g., preferred) SL beam pair, for example, as a manner of indicating the selected (e.g., preferred) SL beam and / or (e.g., preferred) SL beam pair.

[0345] The wireless device can transmit multiple SL RS as beam scans for use in (e.g.) beam pairing procedures, beam management (or maintenance) procedures, and beam fault detection / recovery procedures.

[0346] (For example, the initial) beam pairing procedure may include determining a beam pair for transmission via a unicast link between the first and second wireless devices. Prior to the actual SL transmission, the first and second wireless devices may select a preferred TX beam (e.g., a TX spatial filter or precoder) and a preferred RX beam (e.g., an RX spatial filter) for the SL transmission, for example, beam pairing.

[0347] For example, a beam pairing procedure may include transmitting multiple SL RSs from a first wireless device to a second wireless device to select the beam used by the first wireless device to transmit sidelink transmissions to and / or receive sidelink transmissions from the second wireless device. For example, the first wireless device may use different beams or different TX spatial filters to transmit the multiple SL RSs (e.g., each of the multiple SL RSs is associated with a corresponding beam in a different beam or a corresponding TX spatial filter in a different TX spatial filter). The second wireless device may determine the measurements measured on the multiple SL RSs and transmit a measurement report (e.g., a CSI report) to the first wireless device. The measurement report may include one or more and / or one or more preferred / selected beams (or SL RSs among the multiple SL RSs) of the measurements from the multiple SL RSs. The first wireless device may select or determine its TX beam and / or RX beam (associated with one of the multiple SL RSs) for sidelink transmissions with the second wireless device based on the measurements and / or one or more preferred / selected beams.

[0348] For example, a beam pairing procedure may include a first wireless device transmitting an SL RS to a second wireless device via (e.g., across) multiple symbols or time slots, so that the second wireless device scans its RX beam to select the beam for which the second wireless device will transmit sidelink transmissions to and / or receive sidelink transmissions from the first wireless device. For example, the first wireless device may transmit the SL RS via (e.g., across) multiple symbols or time slots using the same beam or the same TX spatial filter. The SL RS may be associated with (e.g., may correspond to) a preferred TX or RX beam selected by the first wireless device for transmitting sidelink transmissions to and / or receiving sidelink transmissions from the second wireless device. When the first wireless device transmits the SL RS via multiple symbols or multiple time slots, the second wireless device may use different RX beams to receive the SL RS (e.g., an RX beam scan may be performed). For example, the second wireless device may determine a measurement on the SL RS based on each RX beam and select one of the RX beams as the beam for transmitting sidelink transmissions to and / or receiving sidelink transmissions from the first wireless device.

[0349] The beam pairing procedure can occur when the first and second wireless devices establish a unicast link (e.g., during the unicast link establishment procedure). The beam pairing procedure can also occur after the first and second wireless devices have completed establishing the unicast link (e.g., after completing the unicast link establishment procedure). The beam pairing procedure may include the transmission of SL configuration parameters from the first wireless device to the second wireless device.

[0350] The beam management procedure may include the transmission of one or more SL RSs, the transmission of measurement reports associated with one or more SL RSs, and / or determining whether to maintain or switch the current TX beam (and / or the current RX beam). For example, beam management may include the transmission of one or more SL RSs by a first wireless device to a second wireless device using one or more TX beams. For example, the beam management procedure may be used for link monitoring on a unicast link established between the first and second wireless devices. The first wireless device may transmit a message including configuration parameters indicating the SL RSs used for the beam management procedure. The configuration parameters may include one or more parameters indicating the radio resource mapping from each of the SL RSs to the corresponding RE, one or more reporting quantities (e.g., L1-RSRP, CQI, RI, PMI, etc.) measured by each of the SL RSs and to be reported to the first wireless device, and / or resource scheduling information (e.g., whether the SL RSs are periodic, aperiodic, or semi-persistent transmissions). The second wireless device may determine the measurement quantities based on the configuration parameters and transmit a measurement report including one or more measurement quantities to the first wireless device. The first and / or second wireless devices may switch their TX and / or RX beams used for sidelink transmission between them to another TX and / or RX beam based on measurement reports.

[0351] Beam fault detection / recovery procedures enable beamforming sidelink unicast links to quickly and efficiently re-establish disconnected communication links, for example, without performing potentially time-consuming (e.g., initial) beam pairing procedures. For example, beam fault detection / recovery procedures may include at least one of beam fault detection (BFD) and / or candidate beam identification or beam fault recovery.

[0352] Beam Detection (BFD) can be based on measurements from one or more first SL RSs. For example, a first wireless device can transmit a message (e.g., an SL RRC reconfiguration message) to a second wireless device, indicating, for example, one or more first SL RSs from a plurality of first SL RSs as the first SL RSs for BFD. The first wireless device can transmit one or more first SL RSs to the second wireless device once or multiple times, and / or transmit one or more first SL RSs after transmitting the message. The second wireless device can determine the measurements of the received one or more first SL RSs, for example, each time the first wireless device transmits one or more first SL RSs. For example, if the measurements satisfy one or more BFD conditions, the second wireless device can determine a beam failure instance. For example, if the RSRP value (or similar value) measured on one or more first SL RSs is below a BFD threshold, the second wireless device can determine a beam failure instance (e.g., indicating that BFD has occurred). For example, if a beam failure instance occurs consecutively N times within a time window (e.g., N≥1), the second wireless device can determine BFD.

[0353] Candidate beam identifiers may include: one or more second SL RSs monitored by the second wireless device and transmitted by the first wireless device; and / or candidate beams determined based on one or more second SL RSs. For example, the first wireless device may transmit a message (e.g., an SL RRC reconfiguration message) to the second wireless device indicating, for example, one or more second SL RSs from a plurality of second SL RSs as the second SL RSs for monitoring candidate beam identifiers. For example, the plurality of first SL RSs may be the same as the plurality of second SL RSs. The second wireless device may determine a measurement (e.g., RSRP) for each of the one or more second SL RSs. For example, if the measurement (e.g., RSRP value) of the first SL RS among the one or more second SL RSs satisfies one or more second conditions (e.g., greater than or equal to an RSRP threshold), the second wireless device may determine candidate beams (e.g., SL TCI, SL SRI, SL CSI RS) associated with the first SL RS among the one or more second SL RSs. The second wireless device may transmit signals or messages (e.g., SCI, MAC CE, and / or RRC messages) including identifiers of the first SL RSs, for example as candidate beams or beam pairs to which the first wireless device and / or the second wireless device shall switch. For example, the identifier of the first SL RS can be the identifier of the SL TCI or SL SRI associated with (or linked to) the first SL RS.

[0354] Beam fault recovery can be triggered when a beam fault is detected and / or a candidate beam is identified. For example, a first wireless device transmitting (e.g., to a second wireless device) one or more first SL RSs or one or more second SL RSs can trigger beam fault recovery. For example, a second wireless device receiving (e.g., from a first wireless device) one or more first SL RSs or one or more second SL RSs can trigger beam fault recovery. Beam fault recovery may include transmitting a signal or message including an identifier of a first SL RS, such as a candidate beam or beam pair that the first and / or second wireless devices switch to.

[0355] In an example embodiment, transmissions of one or more (e.g., multiple) SL RSs for beam scanning (e.g., for initial beam pairing procedures, beam management procedures, and / or beam fault detection / recovery procedures) may occur via SL resources (e.g., via time slots) indicated by the SL grant. If the first radio device is configured with or selects resource allocation mode 1, the first radio device may receive SL grants from the base station. For example, the DCI (e.g., DCI 3_0 or DCI 3_1, or any DCI including SL grants) received by the first radio device from the base station includes SL grants for sidelink transmissions.

[0356] The wireless device can determine the priority of sidelink transmissions. Sidelink transmissions can refer to the transmission of the PSSCH. Sidelink transmissions can refer to the transmission of SL SS / PSBCH blocks (e.g., SL-SSB). Sidelink transmissions can refer to the transmission of the PSFCH, which includes at least one of the following: HARQ feedback associated with (or corresponding to) a specific PSSCH; or collision information. 7 For example, when / if a sidelink transmission overlaps at least partially with another transmission in the time domain, the wireless device can determine the priority of the sidelink transmission to prioritize or de-prioritize it relative to the other transmission. For example, a sidelink transmission may include transmissions from the wireless device to another wireless device via a sidelink, such as PSSCH, SL SSB, and / or PSFCH. For example, a sidelink transmission may include receptions from the wireless device to another wireless device via a sidelink, such as PSSCH, SL SSB, and / or PSFCH. For example, the other transmission may include at least one of: another sidelink transmission; a UL transmission from the wireless device to the base station; or a DL transmission from the base station to the wireless device. For example, if the wireless device cannot (e.g., simultaneously) transmit or receive a sidelink transmission with the other transmission during at least the duration during which the sidelink transmission overlaps at least partially with the other transmission in the time domain, the wireless device can determine the priority of the sidelink transmission to prioritize or de-prioritize it relative to the other transmission.

[0357] In the example, the priority of the PSSCH (including the SL MAC PDU) can be the priority indicated by the SCI that schedules the transmission / reception of the PSSCH (e.g., the priority field in SCI format 1-A). For example, a wireless device can set the priority of the MAC PDU on / carried by the PSSCH to the priority of the PSSCH (including the SL MAC PDU) and / or the priority indicated by the SCI that schedules the transmission / reception of the PSSCH (e.g., the priority field in SCI format 1-A).

[0358] Priorities can be associated with corresponding priority values. For example, a priority value indicates a specific priority. A priority value can be one of a range of values. For example, a priority value can be an integer value.

[0359] For example, the priority value range can be 1 to 8. For example, a lower priority value can indicate a higher priority. For example, a priority value of 1 can indicate the highest priority, for example, if the priority value range is 1 to 8. For example, a priority value of 8 can indicate the highest priority, for example, if the priority value range is 1 to 8.

[0360] In the example, the wireless device may multiplex at least one of one or more SL MAC SDUs and / or one or more SL MAC CEs onto an SL MAC PDU. For example, an SL MAC PDU may include at least one of one or more SL MAC SDUs and / or one or more SL MAC CEs.

[0361] An SL MAC SDU can be associated with a corresponding SL logical channel. For example, an SL MAC SDU can be associated with one (e.g., at most one) SL logical channel. For example, a MAC SDU can include SL data from its corresponding SL logical channel (e.g., selected or received from its corresponding SL logical channel). The wireless device can receive one or more messages (e.g., RRC messages, RRC set / restore / reconfiguration messages, RRC reconfiguration sidelink messages, SIBs (e.g., SIB1, 2, ... SIB15)). One or more messages include SL logical channel configurations (e.g., sl-LogicalChannelConfig). Each of the SL logical channel configurations includes parameters configuring the corresponding logical channel (e.g., sidelink logical channel parameters). Each of the SL logical channel configurations includes a priority parameter indicating the priority of the corresponding SL logical channel (e.g., sl-Priority). For example, a first SL logical channel configuration includes a first priority parameter (e.g., sl-Priority) whose value indicates the priority of the first SL logical channel. In the example embodiments of this disclosure, the priority of an SL SDU refers to a priority indicated by the value of a priority parameter in the SL logical channel configuration corresponding to the SL logical channel associated with the SL SDU, or is interchangeable with the priority.

[0362] For example, the wireless device can determine the priority of the SL MAC CE. The priority of the SL MAC CE can be predefined (or fixed to / set to) a predefined value. For example, the priority of the sidelink CSI report MAC CE is fixed to '1' (e.g., indicating the highest priority value). For example, the priority of the sidelink DRX command MAC CE is fixed to '1' (e.g., indicating the highest priority value).

[0363] For example, the priority of the SL MAC CE can be configurable. For instance, when determining sidelink transmission information, the priority of the sidelink UE-to-UE coordination information MAC CE can be set in the RRC parameters when triggered by a condition. sl- PriorityCoordInfoCondition The value configured in, or when triggered by an explicit request. sl- PriorityCoordInfoExplicit The value configured in the configuration. For example, the priority of the sidelink UE-to-UE coordination request MAC CE can be set in the RRC parameter. sl-PriorityRequest The value configured in [the configuration]. When determining sidelink transmission information, if not configured... sl-PriorityCoordInfoExplicit-r17Then, the priority of the sidelink inter-UE coordination information MAC CE can be the value indicated in the priority field of the sidelink inter-UE coordination request MAC CE provided by the UE when triggered by an explicit request. For example, when determining sidelink transmission information used to perform sensing and candidate resource selection in the PHY, for example, if not configured... sl-PriorityCoordInfoCondition-r17 Then the UE can determine the priority value of the sidelink UE-to-UE coordination information (MAC CE) triggered under a certain condition. For example, when determining the sidelink transmission information used to perform sensing and candidate resource selection in the PHY, if it is not configured... sl-PriorityCoordInfoCondition-r17 Then the priority value of the MACCE (Inter-UE Coordination Request) between sidelink UEs can be the same as the priority value of the TB (Transmission Block) that the UE wants to transmit.

[0364] In the example, the wireless device multiplexes at least one of the following onto the MAC PDU: one or more SLSDUs (e.g., if present), and / or one or more SL MAC CEs (if present). The wireless device may determine the priority of the MAC PDU based on at least one of the one or more MAC SDUs and / or one or more SL MAC CEs. For example, the wireless device may determine the priority of the SL MAC PDU as the highest priority of the SL logical channel or an SL MAC CE within the SL MAC PDU. For example, the wireless device may set the priority value of the SL MAC PDU to the highest priority value of the SL logical channel (if present), and if included in the SL MAC PDU, to the value of the SL MAC CE. For example, each of the logical channels may be associated with an SL MAC SDU multiplexed onto (or included in) the SL MAC PDU.

[0365] The wireless device can determine the SL TB, which includes the SL MAC PDU. The wireless device can determine or set the priority of the SL TB to the priority of the SL MAC PDU. The wireless device can schedule the transmission of the PSSCH carrying the SL TB (and / or SL MAC PDU). The wireless device can determine the priority of the PSSCH to the priority of the SL MAC PDU and / or the priority of the SL TB. The wireless device can set the value of the 'priority' field in the SCI (e.g., SCI format 1-A, first-level SCI, and / or second-level SCI) to the priority of the PSSCH, to the priority of the SL MAC PDU, and / or to the priority of the SL TB, for example, if the wireless device transmits the SCI as control information for the PSSCH, for example, via the PSCCH.

[0366] The wireless device can transmit one or more SL synchronization signals (SS) (e.g., SL SSB). The priority of the SL SS can be configurable. For example, the wireless device can receive RRC messages or SIBs that include a priority parameter indicating the value of the SL SS priority. For example, the priority parameter... sl-SSB-PriorityEUTRA This can be a parameter indicating the priority of the PSSS / SSSS / PSBCH block. For example, the priority parameter S-SS / PSBCH block can be a parameter indicating the priority of the SL SS / PSBCH block.

[0367] The wireless device can determine the priority of the PSFCH. The PSFCH can carry HARQ-ACK information. The PSFCH can carry collision information. For example, for PSFCH transmission or reception with HARQ-ACK information, the wireless device can determine that the priority value of the PSFCH is equal to the priority value indicated by the SCI format 1-A associated with the PSFCH. For example, for PSFCH transmission or reception with HARQ-ACK information, the wireless device can determine that the priority value of the PSFCH is equal to the priority value indicated by SCI format 1-A, which schedules or indicates the transmission of PSFCH and / or schedules or indicates the transmission of HARQ-ACK information corresponding to the PSFCH via the PSFCH. For example, for PSFCH transmission with collision information, the wireless device can determine that the priority value of the PSFCH is equal to the minimum priority value determined by the corresponding SCI format 1-A of the collision resource. For example, for PSFCH reception with collision information, the wireless device can determine that the priority value of the PSFCH is equal to the priority value determined by the corresponding SCI format 1-A of the collision resource.

[0368] In beam-based SL transmission or reception, a wireless device may transmit or receive multiple SL RSs as part of a beam scan, as described in the exemplary embodiments of this disclosure. The wireless device may transmit or receive multiple SL RSs during beam pairing procedures (e.g., for initial beam pairing), beam management procedures (e.g., for beam monitoring, beam switching, etc.), and / or beam failure detection / recovery procedures. Depending on urgency, latency limits, and impact on QoS management, the wireless device may prioritize or de-prioritize the transmission or reception of multiple SL RSs.

[0369] In the prior art, no priority value or priority is assigned / allocated to the SL CSI-RS. For example, in the prior art, the SL CSI-RS is carried by the PSSCH in sidelink transmissions. In the prior art, the wireless device determines the priority of the sidelink transmission as the priority value of the PSSCH.

[0370] Problems arise when a wireless device schedules sidelink transmissions of multiple SL RSs for beam scanning that overlap with another transmission (e.g., another SL transmission, UL transmission, and / or DL ​​transmission, etc.). The transmissions of multiple SL RSs can have a higher priority than the other transmission. For example, the SL RS transmissions can be used to measure quantities, and a pair of wireless devices can determine an initial beam, candidate beams, and / or a reconstructed beam based on these measurements. According to existing technology, for example, if the PSSCH and multiple SL RSs are transmitted in the same sidelink time slot as the sidelink transmission (e.g., ...), ... Figure 32A If the priority of a sidelink transmission is higher than that of another transmission, the wireless device may discard (e.g., cancel, omit, de-prioritize, or not transmit) the transmission of a sidelink transmission (e.g., multiple SLRS). Multiple SLRSs may be more important than the PSSCH. In this case, based on the lower priority of the PSSCH, the wireless device does not transmit multiple SLRSs. The absence of multiple SLRSs causes a delay in the wireless device when selecting or switching SL beams. If multiple SLRSs are used for beam failure detection / recovery procedures on the PC5 link, this results in a PC5 link failure.

[0371] Additionally, when multiple SL RSs are transmitted independently for beam scanning (e.g., Figure 31B Problems arise when a transmission overlaps with another transmission (e.g., another SL transmission, UL transmission, and / or DL ​​transmission, etc.). In such cases, in the prior art, no priority value or no priority is assigned / assigned to multiple SL RSs (e.g., multiple SL CSI RSs). This causes errors in the system due to undefined definitions or parameters (missing / undefined priorities for multiple SL RSs). For example, the system could perform independent transmissions of multiple SL RSs (e.g., Figure 31B This increases decoding / detection errors on independent transmissions and / or on another transmission.

[0372] In an example embodiment, the wireless device determines priority values ​​or priorities for a plurality of SLRSs. For example, in an example embodiment, the priority values ​​of the priorities of the plurality of SLRSs are set to predefined values. For example, in an example embodiment, the priority values ​​of the priorities of the plurality of SLRSs are configurable.

[0373] In example embodiments, for instance, if the PSSCH and multiple SL RS are transmitted in the same sidelink time slot as the sidelink transmission (e.g., Figure 32AThen the wireless device can determine the priority of the sidelink transmission based on the priority values ​​of multiple SL RSs. For example, if the PSSCH and multiple SL RSs are transmitted in the same sidelink time slot as the sidelink transmission (e.g., Figure 32A The wireless device can then determine whether to prioritize the sidelink transmissions as the value of the PSSCH priority or the value of the multiple SLRS priorities. For example, if the PSSCH and multiple SLRSs are transmitted in the same sidelink time slot as the sidelink transmissions (e.g., Figure 32A If the wireless device determines that the priority of the sidelink transmission is set to the highest value among the priority values ​​of the PSSCH and the multiple SL RS, then the wireless device can determine that the priority of the sidelink transmission is set to the highest value among the priority values ​​of the PSSCH and the multiple SL RS.

[0374] The example embodiment prevents the priority of a sidelink transmission from being set to the priority value of the PSSCH, which would result in the discarding (e.g., possible cancellation, omission, de-prioritization, or non-transmission) of a sidelink transmission (e.g., including the PSSCH and multiple SL RSs) because the PSSCH priority value is higher than the priority value of another transmission that at least partially overlaps with the sidelink transmission in the time domain. The example embodiment reduces latency for the wireless device when selecting or switching SL beams and / or prevents PC5 link failures. The example embodiment provides priority ordering among independent transmissions of multiple SL RSs when an independent transmission overlaps with another transmission (e.g., another SL transmission, UL transmission, and / or DL ​​transmission, etc.).

[0375] Example implementations may define priorities for SL RSs (e.g., multiple SL RSs) configured for beam scanning and / or SL beam management. For example, for SL RSs transmitted for CQI acquisition (e.g., SL CSI RSs), priorities or priority values ​​may not be defined / assigned / allocated.

[0376] In an example embodiment, the priority values ​​of the multiple SL RS priorities can be priority values ​​determined, selected, and / or preferred by the wireless device. For example, the wireless device determines the priority values ​​of the multiple SL RS priorities. The wireless device can transmit one or more first messages to the base station. For example, the one or more first messages can be at least one of the following: MAC CE, UE capability information message, UE assistance information message, UE information response message, sidelinkUEinformation message, RRC message, RRC reconfiguration complete message, or RRC setup / recovery request message. The priority values ​​of the multiple SL RS priorities can be preferred values ​​of the wireless device. For example, the one or more first messages contain the priority values ​​of the multiple SL RS priorities as preferred values ​​of the wireless device. The wireless device can, for example, use the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs after transmitting one or more first messages or in response to transmitting one or more first messages. The wireless device can, for example, use the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs after receiving a response to one or more first messages or in response to receiving a response to one or more first messages. The response can include an indicator confirming the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs. The response may include a second priority value as a priority value for multiple SL RSs. In this case, the second priority value may be a priority value for multiple SL RSs determined, selected, and / or preferred by the base station. In this case, the wireless device can use the second priority value as the priority value for multiple SL RSs.

[0377] In an example embodiment, the priority values ​​of the multiple SL RS priorities can be priority values ​​determined, selected, and / or preferred by the base station. For example, the base station determines the priority values ​​of the multiple SL RS priorities. The base station can transmit one or more third messages to the wireless device. For example, the one or more third messages can be at least one of the following: MAC CE, RRC message, or RRC set / restore / reconfigure message. The priority values ​​of the multiple SL RS priorities can be preferred values ​​of the base station. For example, the one or more third messages contain the priority values ​​of the multiple SL RS priorities as preferred values ​​of the base station. The wireless device can, for example, use the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs after receiving one or more third messages or in response to receiving one or more third messages. The wireless device can, for example, use the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs after transmitting a response to one or more first messages or in response to transmitting a response to one or more first messages. The response can include an indicator acknowledging the priority values ​​of the multiple SL RS priorities as the priority values ​​of the multiple SL RSs. The response can include a second priority value as the priority value of the multiple SL RSs. In this scenario, the second priority value can be a priority value among multiple SL RSs determined, selected, and / or preferred by the wireless device. In this case, the wireless device can use the second priority value as the priority value for multiple SL RSs.

[0378] In an example embodiment, the priority values ​​of the multiple SL RSs can be priority values ​​determined, selected, and / or preferred by the wireless device. For example, the wireless device determines the priority values ​​of the multiple SL RSs. The wireless device can transmit one or more second messages to a second wireless device, and the wireless device establishes a PC5 link with the second wireless device. The multiple SL RSs can be configured or used for beam scanning of the PC5 link. For example, the one or more second messages can be at least one of the following: SL MAC CE, MasterInformationBlockSidelink Messages, NotificationMessageSidelink messages, RemoteUEInformationSidelink information, RRCReconfigurationSidelink message, RRCReconfigurationCompleteSidelink message UEAssistanceInformationSidelink information, UECapabilityInformationSidelink and / or UuMessageTransferSidelinkThe priority values ​​of multiple SL RS priorities can be preferred values ​​for the wireless device. For example, one or more second messages contain the priority values ​​of multiple SL RS priorities as preferred values ​​for the wireless device. The wireless device may use the priority values ​​of multiple SL RS priorities as priority values ​​for multiple SL RSs, for example, after transmitting one or more second messages to the second wireless device or in response to transmitting one or more second messages to the second wireless device. The wireless device may use the priority values ​​of multiple SL RS priorities as priority values ​​for multiple SL RSs, for example, after receiving a response from the second wireless device to one or more first messages or in response to receiving a response from the second wireless device to one or more first messages. The response may include an indicator acknowledging the priority values ​​of multiple SL RS priorities as priority values ​​for multiple SL RSs. The response may include a second priority value as a priority value for multiple SL RSs. For example, the second priority value may be a priority value of multiple SL RSs determined, selected, and / or preferred by the second wireless device. In this case, the wireless device may use the second priority value as a priority value for multiple SL RSs.

[0379] In the example embodiment, the priority of the SL RS can be based on the SL RS configuration. Different SL RS configurations can have different priority values ​​(associated with different priority values).

[0380] For example, a wireless device may configure one or more SL RS configurations for a PC5 link. For example, one or more SL RS configurations in one or more messages transmitted by the wireless device to a base station (e.g., MAC CE, UE Capability Information Message, UE Assistance Information Message, UE Information Response Message, sidelinkUEinformation Message, RRC Message, RRC Reconfiguration Complete Message, or RRC Setup / Restore Request Message). For example, one or more SL RS configurations in one or more messages received by the wireless device from a base station (e.g., MAC CE, RRC Message, or RRC Setup / Restore / Reconfiguration Message). For example, one or more SL RS configurations in one or more messages received by the wireless device from a second wireless device with which the wireless device establishes / maintains a PC5 link (e.g., SL MAC CE, MasterInformationBlockSidelink Message, NotificationMessageSidelink Message, RemoteUEInformationSidelink Message, RRCReconfigurationSidelink Message, RRCReconfigurationCompleteSidelink Message, UEAssistanceInformationSidelink Message, UECapabilityInformationSidelink Message, and / or UuMessageTransferSidelink Message). For example, the radio device transmits one or more SL RS configurations in one or more messages (e.g., SL MAC CE, MasterInformationBlockSidelink message, NotificationMessageSidelink message, RemoteUEInformationSidelink message, RRCReconfigurationSidelink message, RRCReconfigurationCompleteSidelink message, UEAssistanceInformationSidelink message, UECapabilityInformationSidelink message and / or UuMessageTransferSidelink message) to a second radio device that has established / maintained a PC5 link with the radio device.

[0381] For example, each of one or more SL RS configurations may be associated with a corresponding plurality of SL RSs. For example, each of one or more SL RS configurations may include an SL RS identifier. Each of the corresponding plurality of SL RSs is identified by one of the SL RS identifiers (associated with or corresponding to one of the SL RS identifiers). Each of one or more SL RS configurations may include resource configurations for a plurality of SL RSs, the resource configurations indicating the mapping of each of the plurality of SL RSs to a corresponding RE. Different SL RS configurations may indicate a different number of SL RSs (including different numbers of SL RSs, and different numbers of SL RSs associated with them). Different SL RS configurations may have different priority values ​​(associated with different priority values).

[0382] For example, a first SL RS configuration in one or more S SL RS configurations may be associated with a first plurality of SL RSs, wherein the number of the first plurality of SL RSs is a first quantity (or value); a second SL RS configuration in one or more S SL RS configurations may be associated with a second plurality of SL RSs, wherein the number of the second plurality of SL RSs is a second quantity (or value), and so on.

[0383] For example, an SL RS configuration in one or more SL RS configurations is associated with a corresponding priority value of a plurality of SL RSs corresponding to the SL RS configuration. For example, a first SL RS configuration in one or more SL RS configurations associated with a first plurality of SL RSs may be associated with a first priority value that is a priority value of the first plurality of SL RSs. For example, a second SL RS configuration in one or more SL RS configurations associated with a second plurality of SL RSs may be associated with a second priority value that is a priority value of the second plurality of SL RSs, and so on.

[0384] For example, an SL RS configuration in one or more SL RS configurations may include a parameter (e.g., sl-priority) indicating a corresponding priority value for a plurality of SL RSs corresponding to the SL RS configuration. For example, a first SL RS configuration in one or more SL RS configurations associated with a first plurality of SL RSs may include a parameter (e.g., sl-priority) whose value indicates a first priority value as a priority value for the first plurality of SL RSs. For example, a second SL RS configuration in one or more SL RS configurations associated with a second plurality of SL RSs may include a parameter (e.g., sl-priority) whose value indicates a second priority value as a priority value for the second plurality of SL RSs, and so on.

[0385] For example, an SL RS configuration in one or more SL RS configurations may include a parameter (e.g., sl-priority) indicating a corresponding priority value for a plurality of SL RSs corresponding to the SL RS configuration. For example, a first SL RS configuration in one or more SL RS configurations associated with a first plurality of SL RSs may include a parameter (e.g., sl-priority) whose value indicates a first priority value as a priority value for the first plurality of SL RSs. For example, a second SL RS configuration in one or more SL RS configurations associated with a second plurality of SL RSs may include a parameter (e.g., sl-priority) whose value indicates a second priority value as a priority value for the second plurality of SL RSs, and so on.

[0386] In the example embodiment, the priority value indicating the priority of a particular transmission of the SL RS can be fixed or set (or predefined) to a specific value within the priority value range. For example, the priority value indicating the priority of a transmission of the SL RS can be fixed or set (or predefined) to a specific value within the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0387] For example, if the SL RS transmission occurs in the same side link time slot (e.g., Figure 31A If the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0388] For example, if SL RS transmissions occur across different side link time slots (e.g., Figure 31B If the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0389] For example, if the SL RS transmission is a non-independent SL RS transmission (e.g., Figure 32A If the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0390] For example, if the SL RS transmission is an independent SL RS transmission (e.g., Figure 32BIf the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0391] For example, if a wireless device initiates / triggers / executes a transmission of SL RS for beam-pairing procedures (as part of beam-pairing procedures), the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value within a priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0392] For example, if a wireless device initiates / triggers / executes a transmission of SL RS for beam management / maintenance procedures (as part of beam management / maintenance procedures), the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value within a priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0393] For example, if a wireless device initiates / triggers / executes a transmission of SL RS for beam fault detection / recovery procedures (as part of beam fault detection / recovery procedures), the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value within a priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0394] For example, if the wireless device initiates / triggers / executes an SL RS transmission as a periodic SL RS transmission and / or if the SL RS configuration indicates that the SL RS transmission is a periodic SL RS transmission, then the priority value indicating the priority of the SL RS transmission can be fixed or set to (or predefined as) a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0395] For example, if the wireless device initiates / triggers / executes an SL RS transmission as an aperiodic SL RS transmission and / or if the SL RS configuration indicates that the SL RS transmission is an aperiodic SL RS transmission, then the priority value indicating the priority of the SL RS transmission can be fixed or set (or predefined) to a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0396] For example, if the wireless device initiates / triggers / executes a transmission of SL RS as a semi-persistent transmission of SL RS and / or if the SL RS configuration of SL RS indicates that the transmission of SL RS is a semi-persistent transmission of SL RS, then the priority value indicating the priority of the transmission of SL RS can be fixed or set to (or predefined as) a specific value in the priority value range (e.g., the lowest value indicating the highest priority or the highest value indicating the lowest priority).

[0397] In an example embodiment, the wireless device may determine the priority of an SL transmission (which includes a PSSCH carrying an SL TB including an SL MAC PDU) based on at least one of the following: the priority of the SL logical channel associated with the SL MAC SDU (if the SL MAC SDU is contained in the SL MAC PDU), the priority of the SL MAC CE (if the SL MAC CE is contained in the SL MAC PDU), and / or the priority of a plurality of SL RSs (if at least one of the plurality of SL RSs is contained in the SL transmission).

[0398] Figure 33 An example of prioritizing sidelink transmissions according to an exemplary embodiment of the present disclosure is shown. For example, the wireless device determines the priority of SL transmissions. For example, SL transmissions include at least one SL RS (e.g., SL RSs) configured for beam scanning. Figure 33 The transmission of SL RSs (SL MAC SDUs) is described. The priority value of at least one SL RS among the plurality of SL RSs may be represented by p3. For example, an SL transmission may also include one or more SL MAC SDUs. The priority value of a first SL logical channel associated with a first MAC SDU among one or more SL MAC SDUs may be represented by p11, the priority value of a second SL logical channel associated with a second SL MAC SDU among one or more SL MAC SDUs ma...

Claims

1. A method comprising: The first wireless device receives one or more messages indicating an SL resource pool for the transmission of one or more sidelink SL reference signals RS; For an SL transmission that includes a Media Access Control (MAC) Packet Data Unit (PDU) and at least one SL RS, the priority value of the SL transmission is determined to be the highest priority value of the following: The at least one SL RS; The logical channel associated with the MAC PDU; and The MAC control element CE in the MAC PDU; and SL control information indicating the priority value is transmitted to the second wireless device via the SL resources of the SL resource pool.

2. A method comprising: SL control information, transmitted from a first wireless device to a second wireless device, indicates the priority of SL transmissions, including sidelink SL data and at least one SL reference signal RS, wherein the priority is based on: The first priority of the at least one SL RS; and The second priority of the SL data.

3. The method of claim 2, further comprising receiving one or more messages indicating an SL resource pool for transmission of one or more SL RSs.

4. The method according to any one of claims 2 to 3, wherein transmitting the SL control information includes transmitting the SL control information via SL resources of the SL resource pool.

5. The method according to any one of claims 3 to 4, wherein the one or more messages comprise at least one of the following: Radio resource configuration message; or System information message.

6. The method according to any one of claims 2 to 5, further comprising determining the priority based on the highest priority among: The first priority of the at least one SL reference signal; and The second priority of the SL data.

7. The method of claim 6, wherein determining the priority is further based on the value of the highest priority.

8. The method according to any one of claims 2 to 7, wherein the priority value is the highest priority value among the following: The at least one SL reference signal; and The SL data.

9. The method according to any one of claims 2 to 8, wherein the SL data includes a Media Access Control (MAC) Packet Data Unit (PDU).

10. The method according to any one of claims 2 to 9, wherein the priority is the highest priority of the following: The at least one SL reference signal; and The logical channel associated with the MAC PDU.

11. The method according to any one of claims 2 to 9, wherein the priority is the highest priority of the following: The at least one SL reference signal; and The MAC control element CE in the MAC PDU.

12. The method according to any one of claims 2 to 9, wherein the priority is the highest priority of the following: The at least one SL reference signal; and The logical channel associated with the MAC PDU; The MAC control element CE in the MAC PDU.

13. The method of any one of claims 11 to 12, wherein the MAC CE is associated with a corresponding priority or a corresponding priority value.

14. The method of any one of claims 9 to 13, wherein the MAC PDU comprises a MAC Service Data Unit (SDU) from the logical channel associated with a corresponding priority or a corresponding priority value.

15. The method according to any one of claims 2 to 14, wherein the SL control information includes scheduling information for the SL transmission.

16. The method according to any one of claims 2 to 15, wherein the SL transmission further indicates a destination identifier of the second wireless device.

17. The method according to any one of claims 2 to 16, wherein the SL transmission includes second SL control information indicating the destination identifier.

18. The method according to any one of claims 2 to 17, wherein the SL control information includes first-level SL control information.

19. The method according to any one of claims 2 to 18, wherein transmitting the SL control information comprises transmitting via time slots: The SL control information; and The at least one SL RS.

20. The method according to any one of claims 2 to 19, wherein transmitting the SL control information further comprises transmitting the SL data via the time slot.

21. The method according to any one of claims 19 to 20, wherein one or more first symbols of the time slot for transmitting the at least one SL RS are different from one or more second symbols of the time slot for transmitting the SL data.

22. The method according to any one of claims 19 to 21, wherein one or more first symbols of the time slot for transmitting the at least one SL RS appear after one or more second symbols of the time slot for transmitting the SL data.

23. The method according to any one of claims 19 to 22, wherein one or more first symbols of the time slot for transmitting the at least one SL RS occur before one or more second symbols of the time slot for transmitting the SL data.

24. The method according to any one of claims 20 to 23, wherein: The SL control information is carried on the Physical SL Shared Channel (PSSCH) of the time slot; and The SL data is carried on the PSSCH of the time slot.

25. The method according to any one of claims 2 to 24, wherein the at least one SL RS comprises at least one of the following: Non-periodic SL RS; Periodic SL RS; or Semi-permanent SL RS.

26. The method according to any one of claims 2 to 25, wherein the SL control information includes a second-level SCI.

27. The method according to any one of claims 2 to 26, wherein the SL control information includes an SL RS request field indicating a request for a measurement report based on the at least one SL RS.

28. The method according to any one of claims 2 to 27, wherein the at least one SL RS includes at least one SL channel state information CSI RS.

29. The method according to any one of claims 2 to 28, wherein the at least one SL RS is a plurality of SL RSs.

30. The method of claim 29, wherein the plurality of SL RSs includes a plurality of SL channel state information CSIRSs.

31. The method according to any one of claims 2 to 30, wherein the at least one SL RS is used for SL beam management between the first wireless device and the second wireless device.

32. The method of claim 31, wherein the SL beam management is used for a proximity service communication 5 PC5 link between the first wireless device and the second wireless device.

33. The method of any one of claims 31 to 32, further comprising triggering the SL transmission of a plurality of SL RSs in response to initiating the SL beam management, the SL beam management comprising at least one of the following: Beam pairing procedure; Beam maintenance procedure; or Beam fault detection / recovery procedure.

34. The method of claim 33, wherein the triggering of the SL transmission is after the periodic SL RS timer expires or in response to the expiration of the periodic SL RS timer.

35. The method of claim 34, wherein the value of the periodic SL RS timer indicates the transmission periodicity of the at least one SL RS.

36. The method of claim 35, wherein triggering the SL transmission is in response to: Received from the second wireless device an instruction indicating beam fault detection on the proximity service communication 5 PC5 link between the first wireless device and the second wireless device; Received from the second wireless device a beam fault recovery request for the PC5 link between the first wireless device and the second wireless device; or The first wireless device determines a beam fault on the PC5 link between the first wireless device and the second wireless device.

37. A wireless device, comprising: One or more processors; as well as A memory that stores instructions that, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1 to 36.

38. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method according to any one of claims 1 to 36.

Images