Methods, communication devices, and storage media for transmitting wireless channels, and methods, communication devices, and storage media for receiving wireless channels.

Abstract

The invention relates to a communication device that transmits a first control information format including channel occupancy time (COT) information, comprising time-domain and frequency-domain information relating to the cell's COT. The first control information format includes: i) a source ID field and a destination ID field for the transport block; and ii) at least one additional destination ID field for the COT information.

Description

Method for transmitting a wireless channel, communication device and storage medium, and method for receiving a wireless channel, communication device and storage medium

[0001] This specification relates to wireless communication systems.

[0002] Wireless communication systems utilize available system resources (e.g., bandwidth, transmission power, etc.) to support communication between user equipment (UEs). With the introduction of new wireless communication technologies, not only has the number of UEs that a base station (BS) must service within a given resource area increased, but so has the volume of data and control information transmitted and received by the BS to and from the UEs it serves. Since the amount of wireless resources available to a BS for communication with UE(s) is finite, a new method is needed for the BS to efficiently receive and transmit uplink / downlink data and / or uplink / downlink control information to / from the UE(s) using these limited wireless resources. In other words, as node density and / or UE density increase, methods for efficiently utilizing high-density nodes or high-density UEs for communication have become necessary. For example, to address the burden on BSs due to rapidly increasing data traffic, direct communication between two or more nearby UEs using wireless communication technologies, bypassing network nodes, has been studied. As the need for V2X (vehicle-to-everything), a communication technology that supports wired and wireless communication between vehicles and other vehicles, infrastructure, networks, or pedestrians, arises, a rapid increase in communication between devices is expected.

[0003] Considering the rapidly increasing volume and frequency of communication between devices, a solution is required to support stable communication between devices.

[0004] The technical tasks that this specification aims to achieve are not limited to the technical tasks mentioned above, and other technical tasks that are not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0005] In one aspect of the present disclosure, a method for transmitting a wireless channel by a communication device in a wireless communication system is provided. The method comprises: performing a type 1 channel connection on a cell for transmitting a transport block; and, based on a success of the type 1 channel connection to the cell, transmitting a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information regarding a COT for the cell, and transmitting the transport block within the COT determined by the type 1 channel connection, wherein the first control information format includes i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT sharing information.

[0006] In one aspect of the present disclosure, a communication device for transmitting a wireless channel in a wireless communication system is provided. The communication device includes: at least one transceiver; at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: performing a type 1 channel connection on a cell for transmitting a transport block; and, based on a success of the type 1 channel connection to the cell, transmitting the transport block within the COT determined by the type 1 channel connection, a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information regarding a COT for the cell, wherein the first control information format includes i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT sharing information.

[0007] In another aspect of the present disclosure, a computer-readable non-transitory storage medium comprising at least one computer program that causes at least one processor to perform operations, the operations comprising: performing a type 1 channel connection on a cell for transmission of a transport block; and, based on a success of the type 1 channel connection to the cell, transmitting the transport block within the COT determined by the type 1 channel connection, a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information regarding a COT for the cell, wherein the first control information format includes i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT sharing information.

[0008] In another aspect of the present disclosure, a method for a communication device to receive a wireless channel in a wireless communication system is provided. The method comprises: receiving a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information regarding a channel occupancy time (COT) for a cell; wherein the first control information format comprises i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT sharing information; performing a type 2 channel connection within a COT indicated by the COT sharing information based on a value of the additional destination ID field matching one of source Layer-2 IDs of the communication device; and performing a wireless transmission on at least one resource available within the COT based on a success of the type 2 channel connection.

[0009] In one aspect of the present disclosure, a communication device for receiving a wireless channel in a wireless communication system is provided. The communication device includes: at least one transceiver; at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: receiving a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information regarding a COT for a cell; the first control information format including i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT sharing information; and performing a type 2 channel connection within a COT indicated by the COT sharing information based on a value of the additional destination ID field matching one of source Layer-2 IDs of the communication device; And based on the success of the type 2 channel connection, performing wireless transmission on at least one resource available in the COT.

[0010] In another aspect of the present disclosure, a computer-readable, non-transitory storage medium comprising at least one computer program that causes at least one processor to perform operations, the operations comprising: receiving a first control information format comprising channel occupancy time (COT) sharing information comprising time domain information and frequency domain information regarding a COT for a cell; the first control information format comprising i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT sharing information; performing a type 2 channel connection within a COT indicated by the COT sharing information based on a value of the additional destination ID field matching one of source Layer-2 IDs of the communication device; and performing a wireless transmission on at least one resource available within the COT based on a success of the type 2 channel connection.

[0011] In each aspect of this specification, the source ID field may include 8 least significant bits (LSBs) of the source Layer-2 ID of the transport block, the destination ID field may include 16 LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field may include 16 LSBs of a destination Layer-2 ID different from the destination Layer-2 ID.

[0012] In each aspect of this specification, the transport block and the first control information format may be transmitted or received through a physical shared channel.

[0013] In each aspect of the present specification, the method or operations may include: transmitting or receiving, within the COT, a physical control channel carrying a second control information format for scheduling the physical shared channel and the first control information format.

[0014] The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0015] According to some implementations of this specification, wireless communication signals can be transmitted / received efficiently. Consequently, the overall throughput of a wireless communication system can be increased.

[0016] According to some implementations of this specification, the technology for direct communication between devices in licensed spectrum, which is licensed to a particular network operator and has exclusive or preferential use by that network operator, may also be utilized in shared spectrum.

[0017] Some implementations of this specification allow for efficient direct communication between devices over shared spectrum, which is unlicensed spectrum that is not licensed to a specific network operator and can be freely used by multiple network operators.

[0018] The effects according to this specification are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0019] FIG. 1 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification;

[0020] Figure 2 illustrates an example of a frame structure available in a 3GPP-based wireless communication system;

[0021] Figure 3 illustrates a resource grid of slots;

[0022] FIG. 4 illustrates communication links in a wireless communication system;

[0023] Figure 5 is a diagram illustrating frequency resources and time resources for communication between devices;

[0024] Figures 6 and 7 illustrate the transmission structure of physical channels for communication between devices within a slot;

[0025] FIG. 8 is a diagram illustrating a channel access mechanism on a shared spectrum according to some implementations;

[0026] Figure 9 illustrates the flow of the channel connection process;

[0027] Figure 10 illustrates channel occupancy time (COT) sharing between a BS and a UE;

[0028] FIG. 11 illustrates COT sharing between UEs according to some implementations of this specification;

[0029] Figure 12 illustrates the relationship between identifiers of a transmitting UE and identifiers of a receiving UE;

[0030] Figure 13 illustrates the use of additional identifiers (IDs) according to some implementations of this specification;

[0031] FIG. 14 is an example of a process in which a communication device performs wireless transmission according to some implementations of the present specification;

[0032] FIG. 15 is an example of a process in which a communication device performs wireless reception according to some implementations of the present specification.

[0033] Hereinafter, implementations according to this specification will be described in detail with reference to the attached drawings. The detailed description provided below, together with the attached drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only possible implementations of this specification. The detailed description below includes specific details to provide a thorough understanding of this specification. However, one of ordinary skill in the art will appreciate that this specification may be practiced without these specific details.

[0034] In some cases, to avoid ambiguity in the concepts of this specification, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device. Furthermore, identical components are described using the same drawing reference numerals throughout this specification.

[0035] The techniques, devices, and systems described below can be applied to various wireless multiple access systems.

[0036] For convenience of explanation, the following description is based on a 3rd Generation Partnership Project (3GPP)-based communication system. However, the technical features of this specification are not limited thereto. For example, although the detailed description below is based on 3GPP (3rd Generation Partnership Project) LTE or 5G technology, some implementations of this specification are applicable to any other mobile communication system and systems to be introduced in the future (e.g., 6G), except for those specific to 3GPP LTE / 5G.

[0037] For terms and technologies used in this specification that are not specifically explained, refer to 3GPP-based standard documents, for example, 3GPP TS 23.304, 3GPP TS 23.285, 3GPP TS 23.287, 3GPP TS 24.587, 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.300, 3GPP TS 36.321, 3GPP 36.322, 3GPP TS 36.323, 3GPP TS and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.322, 3GPP TS 38.323, and 3GPP TS 38.331.

[0038] In the examples of this specification described below, the expression "assumes" that a device "assumes" that the entity transmitting the channel transmits the channel in a manner consistent with the "assume." The entity receiving the channel may mean that, under the assumption that the channel was transmitted in a manner consistent with the "assume," the entity receiving the channel receives or decodes the channel in a manner consistent with the "assume."

[0039] In this specification, UE may be fixed or mobile, and includes various devices that communicate with a BS (base station, BS) to transmit and / or receive user data and / or various control information. UE may be referred to as (Terminal Equipment), MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), etc. In addition, in this specification, BS generally refers to a fixed station that communicates with UE and / or other BSs, and exchanges various data and control information by communicating with UE and other BSs. BS may be referred to by other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-NodeB), gNB, BTS (Base Transceiver System), Access Point, PS (Processing Server), etc. For convenience of explanation, base stations are collectively referred to as BSs regardless of the type or version of communication technology.

[0040] In this specification, a node refers to a fixed point capable of transmitting and receiving wireless signals by communicating with a UE. Various types of BSs can be used as nodes, regardless of their designation. Each node is equipped with at least one antenna. The antenna may refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also referred to as a point.

[0041] Meanwhile, 3GPP-based communication systems use the concept of cells to manage wireless resources. Cells associated with wireless resources are distinct from cells within a geographic area. A "cell" within a geographic area can be understood as the coverage within which a node can provide services using a carrier, while a "cell" within a wireless resource is associated with a bandwidth (BW), which is the frequency range configured by the carrier. Downlink coverage, the range within which a node can transmit valid signals, and uplink coverage, the range within which a node can receive valid signals from a UE, depend on the carrier carrying the signals. Therefore, the coverage of a node is often associated with the coverage of the "cell" within which the wireless resources are used. Therefore, the term "cell" can sometimes refer to the coverage of a service provided by a node, sometimes to a wireless resource, and sometimes to the range within which a signal using the wireless resource can reach with effective intensity.

[0042] A "cell" associated with wireless resources can be defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), i.e., a combination of a DL component carrier (CC) and an UL CC. A cell can be configured with only DL resources or a combination of DL resources and UL resources. When carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. Here, the carrier frequency can be the same as or different from the center frequency of each cell or CC.

[0043] In a wireless communication system, a UE receives information from a base station (BS) via the downlink (DL), and the UE transmits information to the base station via the uplink (UL). The information transmitted and / or received by the BS and UE includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and / or receive.

[0044] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from higher layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal with a predefined special waveform that is known to the BS and UE. For example, the demodulation reference signal (DMRS) and the channel state information RS (CSI-RS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from higher layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0045] In this specification, PDCCH refers to a set of time-frequency resources (e.g., resource elements (REs)) that carry downlink control information (DCI), and PDSCH refers to a set of time-frequency resources that carry downlink data. In addition, PUCCH, PUSCH, and PRACH refer to sets of time-frequency resources that carry uplink control information (UCI), uplink data, and random access preamble, respectively (respectively). Hereinafter, the expression that a UE / BS transmits / receives a PUCCH / PUSCH / PRACH is used with the same meaning as that UCI / uplink data / random access preamble are transmitted / received on or through the PUCCH / PUSCH / PRACH, respectively. Additionally, the expression that BS / UE transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting / receiving broadcast information / DCI / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0046] In this specification, radio resources (e.g., time-frequency resources) scheduled or configured by the BS to the UE for transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0047] Since a communication device receives physical channels and / or physical signals in the form of radio signals on a cell, it cannot selectively receive only radio signals containing only a specific physical channel or a specific physical signal through a radio frequency (RF) receiver, nor can it selectively receive only radio signals excluding only a specific physical channel or a specific physical signal through an RF receiver. In actual operation, the communication device first receives radio signals on a cell through an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and decodes the physical signals and / or physical channels within the baseband signals using one or more processors. Therefore, in some implementations of the present specification, not receiving a physical signal and / or a physical channel may not actually mean that the communication device does not receive radio signals containing the physical signal and / or physical channel, but rather does not attempt to recover the physical signal and / or physical channel from the radio signals, for example, does not attempt to decode the physical signal and / or the physical channel.

[0048] The communication system applicable to this specification includes a wireless device, a base station (BS), and a network. Here, a wireless device may refer to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA), WiFi, and 6G to be introduced in the future).

[0049] Although not limited thereto, wireless devices may include robots, vehicles, XR (eXtended Reality) devices, handheld devices, home appliances, IoT (Internet of Things) devices, and AI devices / servers. For example, vehicles may include ground vehicles equipped with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Here, vehicles may include UAVs (Unmanned Aerial Vehicles) (e.g., drones) and UAMs (Urban Air Mobility) (e.g., unmanned aerial vehicles). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices. Handheld devices may include smartphones, smart pads, wearable devices (e.g., smartwatches, smartglasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc.. IoT devices may include sensors, smart meters, etc. For example, BS, network can also be implemented with wireless devices, and a specific wireless device can act as a BS / network node to other wireless devices.

[0050] Wireless devices can be connected to a network through a base station (BS). Artificial intelligence (AI) technology can be applied to wireless devices, and wireless devices can be connected to AI servers through the network. Wireless devices can communicate with each other through the base station / network, but they can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, transportation devices can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices.

[0051] Wireless communication / connection can be established between wireless devices, between BSs, or between wireless devices and BSs. Here, the wireless communication / connection can include uplink / downlink communication (UL / DL) and sidelink communication (SL) (or D2D communication), and can be established through various wireless access technologies (e.g., 5G NR). Through the wireless communication / connection (UL / DL, SL), the wireless devices and BS / wireless devices can transmit / receive wireless signals to / from each other. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of this specification.

[0052] FIG. 1 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 1, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals via various wireless access technologies. Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device, BS} and / or {the wireless device, the wireless device} described above.

[0053] Each of the first wireless device (100) and the second wireless device (200) includes one or more processors (102, 202) and one or more memories (104, 204), and may further include one or more transceivers (106, 206) and / or one or more antennas (108). The processors (102, 202) control the memories (104, 204) and / or the transceivers (106, 206), and may be configured to implement the functions, procedures, and / or methods described / suggested below. For example, the processors (102, 202) may process information in the memories (104, 204) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106, 206). In addition, the processor (102, 202) may receive a wireless signal including second information / signal through the transceiver (106, 206), and then store information obtained from signal processing of the second information / signal in the memory (104, 204). The memory (104, 204) may be connected to the processor (102, 202) and may store various information related to the operation of the processor (102, 202). For example, the memory (104, 204) may perform some or all of the processes controlled by the processor (102, 202), or store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (102, 202) and the memory (104, 204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (106, 206) may be connected to a processor (102, 202) and may transmit and / or receive wireless signals via one or more antennas (108, 208). The transceiver (106, 206) may include a transmitter and / or a receiver.

[0054] Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) in accordance with the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) may receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification.

[0055] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals, and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software in the form of codes, instructions, and / or sets of instructions.

[0056] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0057] One or more transceivers (106, 206) may transmit / receive user data, control information, wireless signals / channels, etc., referred to in the methods and / or flowcharts of this specification, to / from one or more other devices. Furthermore, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit / receive user data, control information, or wireless signals to / from one or more other devices. Furthermore, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, etc., referred to in the functions, procedures, proposals, methods, and / or flowcharts of this specification, via one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter.

[0058] In this specification, at least one memory (104, 204) can store instructions or programs, which, when executed, cause at least one processor (102, 202) operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0059] In this specification, a computer-readable (non-transitory) storage medium can store at least one instruction or computer program, which when executed by at least one processor causes the at least one processor to perform operations according to some embodiments or implementations of the present specification.

[0060] Figure 2 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0061] The structure of the frame in Fig. 2 is only an example, and the number of subframes, the number of slots, and the number of symbols in the frame can be varied. In some wireless communication systems, OFDM numerologies (e.g., subcarrier spacing (SCS)) may be set differently between multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., subframe, slot, or transmission time interval (TTI)) composed of the same number of symbols may be set differently between the aggregated cells. Here, the symbol may include an OFDM symbol (or a cyclic prefix - orthogonal frequency division multiplexing (CP-OFDM) symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol and DFT-s-OFDM symbol may be interchangeable.

[0062] Referring to Figure 2, uplink and downlink transmissions are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = 10 ms duration, where T is the basic time unit. c = 1 / (△f max *N f ) and △f max = 480*10 3 Hz, and N f =4096. For reference, the sampling time T s = 1 / (△f ref *Nf,ref ) and △f ref = 15*10 3 Hz, and N f,ref =2048. T c Wow T s is a constant κ = T s / T c = 64 relationship. A frame consists of 10 subframes, and the duration of a single subframe is T. sf is 1ms. Subframes are further divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot is divided into N slots based on a cyclic prefix (CP). slot symb It can be composed of symbols. For example, in some scenarios, in the case of normal CP, each slot consists of 14 OFDM symbols, and in the case of extended CP, each slot consists of 12 OFDM symbols. The numerology is exponentially scalable with subcarrier spacing △f = 2. u *Depends on 15 kHz. The following table shows the subcarrier spacing for regular CP △f = 2. u *Number of OFDM symbols per slot at 15 kHz (N) slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0063]

[0064] The following table shows the subcarrier spacing for extended CP △f = 2. u *Indicates the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe at 15 kHz.

[0065]

[0066] For a subcarrier spacing setting u, slots are n in increasing order within a subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - Numbered as 1}.

[0067] Hereinafter, implementations of this specification are described by referring to the minimum unit of time for scheduling uplink, downlink, and sidelink transmissions as a slot. However, depending on the wireless communication system, the minimum unit of time for scheduling may be referred to by a different term. For example, in an LTE-based system, the minimum unit of time for scheduling transmissions is referred to as a subframe or a transmission time interval (TTI), whereas in an NR-based system, the minimum unit of time for scheduling is referred to as a slot.

[0068] Figure 3 illustrates a resource grid of slots. A slot is a multiple (e.g., N) in the time domain. slot symb ) contains symbols of each numeral (e.g., subcarrier spacing) and carrier, a common resource block (CRB)N indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starting from,N size,u grid,x *N RB sc Dog subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,xis the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. N RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB sc is typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid is given to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex-valued symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. RBs can be classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with 'point A', which is a common reference point for resource block grids. PRBs for subcarrier spacing configuration u are defined in a bandwidth part (BWP), numbered from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. Common resource block n u CRB and bandwidth part i within physical resource block n PRB The relationship between the two is as follows: nu PRB = n u CRB +N start,u BWP,i , here N start,u BWP,i is a common resource block (BRB) whose bandwidth part starts relative to CRB 0. A BWP comprises multiple contiguous RBs in the frequency domain. For example, a BWP may be a given numeral u within a BWP i on a given carrier. i A subset of contiguous CRBs defined for a carrier. A carrier may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the activated BWPs, and only a predetermined number (e.g., 1) of BWPs configured for the UE may be activated on the carrier.

[0069] For each BWP, the UE may be provided with at least one of the following parameters for the serving cell: i) subcarrier spacing, ii) cyclic prefix, iii) N start BWP = Offset RB with the assumption of 275 set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates the resource indicator value (RIV). start BWP =O carrier +RB start and the number of contiguous RBsN size BWP =L RB , and the subcarrier spacing is provided by the RRC parameter offsetToCarrierO carrier; an index within the set of DL BWPs or UL BWPs; a set of BWP-common parameters and a set of BWP-specific parameters.

[0070] Virtual resource blocks (VRBs) are defined within the bandwidth part and are numbered from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. The UE may assume that VRBs are mapped to PRBs according to the mapping method indicated to the UE (e.g., non-interleaved or interleaved mapping). If no mapping method is indicated, the UE assumes non-interleaved mapping. In the case of non-interleaved VRB-to-PRB mapping, VRB n may be mapped to PRB n. In the case of interleaved VRB-to-PRB mapping, VRBs may be distributed and mapped to PRBs according to a predefined rule.

[0071] Figure 4 illustrates communication links in a wireless communication system.

[0072] Referring to FIG. 4, in a wireless communication system, a UE receives information from a BS via a downlink (DL), and the UE transmits information to the BS via an uplink (UL). To address the burden on the BS due to rapidly increasing data traffic, a technology (e.g., sidelink (SL)) that supports direct communication between two or more nearby UEs without going through a network node using wireless communication technology has been studied. UEs within or outside the coverage area of ​​a BS can send data to another UE via a sidelink that supports UE-to-UE direct communication using sidelink resource allocation modes, physical layer signals / channels, and physical layer processes. Hereinafter, direct communication between devices will be referred to as sidelink communication, and implementations of the present specification will be described.

[0073] Transmissions in SL use OFDM waveforms with CP. The frame structure described in Fig. 2 and the resource grid structure described in Fig. 3 can be applied to SL. In some scenarios, for example, in NR V2X, only certain slots can be (pre-)configured to accommodate SL transmissions, and the available sidelink resources can consist of (common) RBs in the sidelink (time resources) and SL BWP (frequency resources). A subset of the available SL resources can be (pre-)configured to be used by several UEs for SL transmissions. This subset of the available SL resources is called a resource pool.

[0074] Figure 5 illustrates frequency resources and time resources for direct communication between devices.

[0075] Referring to FIG. 5, a resource pool is composed of (pre-configured) i) contiguous PRBs and ii) contiguous or non-contiguous slots for direct communication between devices. The concept of BWP can also be applied to sidelink. A UE can be configured with a BWP having a numerology and a resource grid for direct communication between devices. Hereinafter, a BWP configured for direct communication between devices is referred to as an SL BWP. The SL BWP can occupy a contiguous portion of the bandwidth within a carrier. Direct transmissions between devices and direct receptions between devices can be performed within the SL BWP. Hereinafter, direct transmissions between devices are referred to as sidelink transmissions, and direct receptions between devices are referred to as sidelink receptions. A resource pool can be defined within an SL BWP, and a single numerology is used within the resource pool. A resource pool can be shared by several UEs for direct device-to-device communication and can be used for all transmission types (e.g., unicast, groupcast, and broadcast). A UE can be configured with one or more sidelink resource pools via higher-layer signaling (e.g., RRC signaling). A UE can transmit on the sidelink using its own transmission resource pool(s), while also receiving data on resource pools used for sidelink transmissions by other UE(s).

[0076] In the frequency domain, the resource pool is divided into a predefined number L of consecutive subchannels, each of which consists of a group of consecutive RBs within a slot. The number of RBs in a subchannel is N. sch corresponds to the subchannel size and is (pre-)set for the resource pool. L and N schcan be provided to the UE via higher layer signaling (e.g., RRC signaling). The first RB of the first subchannel within the SL BWP is (pre-)configured via RRC signaling. For example, the lowest RB index of the subchannel with the lowest index within the resource pool based on the lowest RB index of the SL BWP can be provided to the UE(s). In NR V2X, the subchannel size N sch can be equal to 10, 12, 15, 20, 25, 50, 70, or 100 RBs. In sidelink, a subchannel represents the smallest unit for sidelink data transmission or reception. Sidelink transmission can be performed using one or more subchannels.

[0077] In the time domain, slots that are part of a resource pool are (pre-)configured and occur at regular intervals (e.g., 10240 ms). In each slot of the resource pool, N slot symb Among the dog symbols, only a subset of the consecutive symbols are (pre-)configured for direct communication between devices. Hereinafter, the symbols (pre-)configured for direct communication between devices are referred to as sidelink symbols. The subset of sidelink symbols per slot is indicated by the number of start symbols and consecutive symbols, and these are (pre-)configured per resource pool.

[0078] 3GPP-based communication standards define sidelink physical channels corresponding to resource elements that carry information originating from higher layers, and sidelink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. For example, the physical sidelink shared channel (PSSCH), the physical sidelink control channel (PSCCH), the physical sidelink broadcast channel (PSBCH), and the physical sidelink feedback channel (PSFCH) can be used as sidelink physical channels. In this specification, the PSCCH carries sidelink control information (SCI) in the sidelink. For example, the SCI is used to indicate resources and other transmission parameters used by the UE for the PSSCH, and the PSCCH transmission is associated with a demodulation reference signal (DM-RS). The PSSCH can carry the data payload in the sidelink and additional control information. Data can be organized into TB(s), and each TB can be associated with an SCI. For example, the PSSCH is used to carry control information for transport block (TB)(s), hybrid automatic repeat request (HARQ) processes, and CSI feedback triggers. In some scenarios, at least six OFDM symbols are used for PSSCH transmission within a slot, and the PSSCH is associated with a DM-RS.The PSBCH carries information to support synchronization in the sidelink, and in some scenarios, the PSBCH may be sent within a sidelink synchronization signal block (S-SSB). The PSFCH carries HARQ feedback on the sidelink from the UE intended to be the recipient of the PSSCH to the UE that performed the PSSCH transmission. Hereinafter, the UE performing the sidelink transmission is referred to as the TX UE, and the intended recipient(s) of the sidelink transmission is referred to as the RX UE(s).

[0079] In some scenarios, SCI is transmitted in two stages. For example, in NR V2X, 1 st -Stage SCI is carried on PSCCH and 2 nd -Step SCI can be carried on the corresponding PSSCH. SCI 1 st -Stage SCI and 2 nd - Dividing into step SCI allows other UEs, other than the RX UEs of the sidelink transmission, to use the above 1 for channel sensing purposes, i.e. to determine resources reserved by other transmissions. st -Allows only step SCI to be decoded. Meanwhile, the above 2 nd -Step SCI provides additional control information required for the RX UE(s) of sidelink transmission.

[0080] The number of symbols used for sidelink transmission within a slot may vary depending on the physical channels carried within the slot.

[0081] Figures 6 and 7 illustrate the transmission structure of sidelink physical channels within a slot.

[0082] A PSCCH can be multiplexed with an associated PSSCH on non-overlapping resources within the same slot. Referring to FIG. 6, a PSCCH is transmitted starting from the lowest RB in the subchannel(s) occupied by the associated PSSCH in the frequency domain, and starting from the second symbol in the slot in the time domain. The number of symbols for the PSCCH is (pre-)configured per resource pool and can be, for example, 2 or 3 symbols. According to some scenarios (e.g., NR V2X), in the frequency domain, the PSCCH is N PSCCH Occupying the RBs of N PSCCH can be (pre-)configured to UE(s) per resource pool via higher layer signaling (e.g. RRC signaling). In some scenarios (e.g. NR V2X), N PSCCH can be set to equal 10, 12, 15, 20, or 25 RBs per resource pool. In some scenarios (e.g., NR V2X), N PSCCH is contained within one subchannel, and the number of RBs for PSCCH is N. PSCCH N is the number of RBs in the subchannel sch can be constrained by (i.e., N PSCCH *N sch ) PSCCH is PSSCH and 2 nd -1 containing control information associated with the step SCI st - Carries the SCI step. For this, for example, SCI format 1-A can be used. 1 above st - The step SCI may indicate the frequency resources (e.g., subchannel(s)) of the PSSCH carrying the current (re-)transmission of the transport block (TB), and may indicate resource reservation for retransmission(s) of the TB up to a predefined number of times (e.g., 2). 1 st- The step SCI may include the priority of the associated PSSCH, 2 nd - May include information about the format and size of the step SCI. 1 above st - The step SCI may include information about the modulation and coding scheme (MCS) of the transport block (TB) carried on the associated PSSCH. Although not illustrated in FIG. 6, a DM-RS associated with the PSCCH (hereinafter, PSCCH DM-RS) may be transmitted within the PSCCH for demodulation of the PSCCH. For example, each PSCCH symbol (i.e., an OFDM symbol including the PSCCH) may include a PSCCH DM-RS. Although not illustrated in FIG. 6, the DM-RS associated with the PSSCH is carried on different symbols within the slot to which the PSSCH is allocated (hereinafter, PSSCH slot). Multiple time patterns may be (pre-)configured for the PSSCH DM-RS within the resource pool, and the above 1 st - The step SCI may include information about which time pattern is used for the associated PSSCH.

[0083] PSSCH is 2 nd - carries a data payload consisting of step SCI and TB(s). 2 above nd - The step SCI can carry information used to decode the PSSCH and information to support HARQ feedback and CSI reporting. 2 above. nd - The step SCI may include a layer 1 source ID representing the identifier (within the physical layer) of the TX UE and a layer 1 destination ID representing the identifier(s) of the intended recipient(s) (RX UE(s)) of the corresponding TB. 2 nd- The step SCI may carry a 1-bit new data indicator (NDI) used to specify whether the TB sent on the PSSCH corresponds to a transmission of new data or a retransmission. 1 in the PSCCH st -After decoding the step SCI, the RX UE nd - You will have the information needed to decode the step SCI. 2 nd -Step SCI can be decoded using PSSCH DM-RS. 2 before being mapped to PSSCH nd -Step SCI and TB are each channel coded and multiplexed according to a predefined process. Depending on the number of layers supported in PSSCH (i.e., the number of data streams), the multiplexed 2 nd -Stage SCI and TB, PSSCH's L PSSCH Before being mapped to subchannel(s), it is mapped and precoded to one or two layers. The PSSCH starts from the lowest RB within the subchannel carrying the PSCCH, starting from N PSSCH =L PSSCH *N sch Occupying the dog RBs, here N PSSCH is the number of RBs occupied by the PSSCH, and L PSSCH is the number of subchannels for PSSCH, and N sch is the number of RBs per subchannel.

[0084] Referring to Fig. 6, the PSSCH may be transmitted from the second symbol to the second to the last symbol in the slot, or from the second symbol to the symbol immediately preceding the last symbol in the slot. In some scenarios, 7 to 14 symbols may be (pre-)configured in the slot for sidelink, and the PSCCH may be sent in 5 to 12 consecutive symbols. The number of symbols occupied by the PSSCH depends on the number of SL symbols allocated in the slot and whether the PSFCH is sent in that slot. Within the symbols carrying the PSCCH, the PSSCH may be transmitted (the PSCCH may be transmitted in the entire L PSSCH (If the subchannel(s) are not occupied) may be multiplexed in the frequency domain with the PSCCH. The second symbol in the slot (i.e., the first symbol with the PSCCH or with the PSCCH / PSSCH) may be duplicated in the first symbol of the slot for use in automatic gain control (AGC) purposes. Additionally, the symbol after the last symbol with the PSSCH may be used as a guard symbol.

[0085] FIG. 6 illustrates a sidelink transmission structure in which the PSCCH occupies three symbols in the time domain and 14 symbols within a slot of 14 symbols are used for PSCCH / PSSCH transmission; however, the PSCCH may occupy two symbols, or some leading symbols within a slot may be used for PSCCH / PSSCH transmission and the remaining symbols may be used for PSFCH or for additional guard symbols.

[0086] Referring to Fig. 7, according to some scenarios (e.g., NR V2X), for a resource pool with L subchannels, there are L possible PSCCH locations within a slot, starting from the second SL symbol within the slot and from the lowest RB within each subchannel. In other words, for a resource pool with L subchannels, there may be L PSCCH candidate resources in each slot. Therefore, in some scenarios, 1 st - To receive a step SCI, the UE needs to check (or monitor) L possible PSCCH locations in each slot within the resource pool.

[0087] Referring to FIGS. 6 and 7, in some scenarios (e.g., NR V2X), the UE may, through higher layer signaling (e.g., RRC signaling), specify the number of symbols for PSCCH for the resource pool, N. sym,PSCCH and the number of RBs for PSCCHN PSCCH , and the PSCCH starts from the second symbol available for SL transmissions within the slot. sym,PSCCH Starting from the lowest RB of the lowest subchannel of the associated PSSCH within the dog symbols, N PSCCH It is transmitted on the dog RBs.

[0088] A UE may be configured with one or more sidelink resource pools via higher-layer signaling (e.g., RRC signaling). The sidelink resource pools may be used for transmitting or receiving PSSCHs. In some scenarios, the PSSCH is transmitted in the same slot as the associated PSCCH. In some scenarios, the minimum resource allocation unit for the PSSCH in the time domain is a slot. PSSCHs transmitted in consecutive symbols within a slot are not transmitted in symbols not configured for sidelink. The index of the first symbol among consecutive symbols that can be used for sidelink and the number of consecutive symbols that can be used for sidelink may be provided to the UE(s) via higher-layer signaling (e.g., RRC signaling). The UE does not transmit the PSSCH in the last symbol configured for sidelink, which may be used as a guard symbol. In some scenarios, the minimum resource allocation unit for the PSSCH in the frequency domain is a subchannel.

[0089] Referring to FIG. 7, when a PSCCH is transmitted / received in a PSCCH resource candidate of a slot within a resource pool, the PSSCH associated with the PSCCH is transmitted / received within consecutive symbols within the slot in the time domain, and in the frequency domain, the subchannel on which the PSCCH is transmitted / received is L having the lowest subchannel. PSSCHThe PSSCH is transmitted / received on the subchannels. When the PSSCH occupies multiple subchannels, the PSCCH resource candidate(s) of the remaining subchannel(s) other than the lowest subchannel among the multiple subchannels are used for transmission of the PSSCH. The PSCCH resource candidate(s) of the subchannel(s) that are not used for PSSCH transmission in the slot within the resource pool are not used for PSCCH transmission either. The RX UE attempts to detect the PSCCH from the PSCCH resource candidates, and when it detects the PSCCH in the slot, it considers the lowest RB in which the PSCCH is detected based on the SCI carried by the PSCCH as the lowest RB of the PSSCH, and starting from the lowest RB, N PSSCH =L PSSCH *N sch The PSSCH can be received on the dog RBs.

[0090] As the need for vehicle-to-everything (V2X), a communication technology that supports wired / wireless communication between vehicles and other vehicles, infrastructure, networks, or pedestrians, is emerging, a rapid increase in SL communication is expected. To support SL communication stably, it may be considered to support SL communication not only in licensed spectrum, which is licensed to a specific network operator and can be used exclusively or preferentially by that network operator, but also in shared spectrum, which is unlicensed spectrum, which is not licensed to a specific network operator and can be used freely by multiple network operators. However, to support SL communication in shared spectrum, a method for coexisting communication in shared spectrum and SL communication is required. Below, among 3GPP-based communication technologies, technologies applied to uplink and / or downlink communication between UE and BS in shared spectrum are described.

[0091] Unless otherwise stated, the following definitions apply to terms relating to shared spectrum in this specification:

[0092] - Channel: Consists of consecutive RBs on which a channel access process is performed in a shared spectrum, and may refer to a carrier or a portion of a carrier.

[0093] - Channel access procedure (CAP): This refers to the process of evaluating channel availability based on sensing to determine whether other communication devices(s) are using the channel before signal transmission. The BS or UE senses the channel during a sensing slot period, and if the detected power is less than an energy detection threshold for at least a certain period of time within the sensing slot period, the sensing slot period is considered idle or free, otherwise the sensing slot period is considered busy. CAP may be referred to as Listen-Before-Talk (LBT).

[0094] - Channel occupancy: refers to the corresponding transmission(s) on the channel(s) by the BS / UE after the CAP is performed.

[0095] - Channel Occupancy Time (COT): refers to the total time that the BS / UE and any BS / UE(s) sharing the channel occupancy can perform transmission(s) on the channel after the BS / UE performs CAP. COT can be shared for transmissions between the BS and corresponding UE(s).

[0096] In some scenarios, when a carrier with SCS setting u in shared spectrum is configured with IntraCellGuardBandsPerSCS, the UE may use N RB-set - 1 intra-cell guard band is provided, each intra-cell guard band starts from RB GB start,u s and size G in terms of the number of RBs size,u s is defined by GB start,u s and GB size,u s is determined by the upper layer parameters provided from the BS to the UE, and s∈{0,1,…, N RB-set- 2}. Intra-cell guard bands are N RB-set Separate the dog RB sets, each RB set starting with a RB (RB start,u s ) and end RB (RB end,u s ) is defined by s∈{0,1,…, N RB-set - Start RB index RB for {1} start,u s and end RB index RB end,u s can be determined by the following mathematical formulas.

[0097]

[0098]

[0099] The RB set with index s is RB size,u s It consists of dog resource blocks, where RB size,u s = RB end,u s - RB start,u s + 1. If the UE is not configured with IntraCellGuardBandsPerSCS for u, the UE sets u and carrier size N size,u grid According to the nominal intra-cell guard band and RB pattern corresponding to the carrier, the RB indices for the intra-cell guard band(s) and the corresponding RB set(s) are determined. If the nominal intra-cell guard band and RB set pattern do not include any intra-cell guard bands, the number of RB sets for the carrier N RB-set = 1.

[0100] If a UE is provided with the number of RBs = 0 for all intra-cell guard band(s) on a carrier with SCS configuration u, the UE is instructed that no intra-cell guard bands are configured for the cell, and N RB-set > I expect it to be 1 day.

[0101] Since shared spectrum is not dedicated to a specific network operator, BSs and UEs can apply Listen-Before-Talk (LBT) before transmitting on cells configured with shared spectrum channel access. With LBT, the transmitter listens / senses the channel to determine whether the channel is free or busy, and transmits only if the channel is deemed free. In other words, for shared spectrum, a communication device must determine whether the channel is occupied by other communication devices before transmitting a signal.

[0102] Figure 8 is a diagram illustrating a channel access mechanism on a shared spectrum according to some implementations.

[0103] In 3GPP-based systems, channel access in both downlink and uplink relies on LBT. The UE and BS must first sense the communication channel to detect the absence of communication before transmission. If the communication channel is an unlicensed band with a wide bandwidth, the channel sensing process relies on detecting energy levels on multiple subbands of the communication channel. LBT parameters, such as channel assessment parameters, can be configured for the UE by the BS.

[0104] In some implementations, the channel access mechanism for a cell configured with shared spectrum channel access, i.e., the LBT mechanism, can be broadly divided into a Type 1 channel access process and a Type 2 channel access process.

[0105] Figure 9 illustrates the flow of a channel connection process. In particular, Figure 9 illustrates the flow of a Type 1 channel connection process.

[0106] Type 1 channel access is a counter-based random back-off channel access mechanism. A UE / BS wishing to transmit performs LBT to sense idle channels on a cell in the shared spectrum. The UE / BS detects that the channel is idle for a deferred time T. d If the UE / BS senses that it is idle during the period (S901), a random back-off counter N between 0 and the contention window size is generated (S902). The contention window size is adjusted based on the HARQ-ACK and priority access class. If the counter is 0 and the UE / BS is not transmitting, the UE / BS adds an additional short LBT slot duration T before the transmission. sl With additional slot period T d is performed during (S903, S904). The duration of the additional short LBT is 43 μs, 52 μs, and 88 μs depending on the channel access priority class (CAPC) levels. For example, T d = T f + m p *T sl and m p is determined based on the channel access priority class (CAPC). T f can be, for example, 16 μs, and T sl can be 9 μs. NR's shared spectrum channel access introduces mini-slot level channel access to increase the number of transmissions, and supports back-to-back transmissions during COT as long as the time gap between two consecutive transmissions is no longer than 16 μs.

[0107] NR's shared spectrum channel access (hereinafter, NR-U) supports Co-Op (Coordinated Transmission) (COT) sharing. Different devices (e.g., UE / BS, UE, BS) can alternately use the medium / channel, provided that activity gaps are maintained between transmissions. For example, when a UE / BS initiates a COT through a Type 1 channel access procedure, resources within the COT can be used not only for transmissions by the UE / BS, but also shared for transmissions by BS / UE(s). NR-U supports Type 2 LBT for COT sharing. When the resources in the COT initiated through the Type 1 channel access process performed on the device are shared by another device, the other device may use a Type 2A channel access, a Type 2B channel access, or a Type 2C channel access, and there are specific gap limitations between two adjacent transmissions for these channel access types, and a Type 2 channel transmission can be classified into a Type 2A channel access, a Type 2B channel access, and a Type 2C channel access according to the specific gap limitations. In the case of a Type 2A channel access, the UE / BS performs channel sensing for a period of 25 μs before starting a transmission, and performs the transmission after the channel sensing is successful. In the case of a Type 2B channel access, the UE / BS performs channel sensing for a period of 16 μs before starting a transmission, and performs the transmission after the channel sensing is successful, wherein the gap between the start position of the transmission and the end position of the previous transmission is 16 μs. For Type-2C channel access, the UE may transmit immediately without channel sensing after a gap, wherein the gap between the start position of the transmission and the end position of the previous transmission may be less than or equal to 16 μs.

[0108] Type 2 LBT, i.e., the gap for Type 2 channel access, can be controlled by the BS via the LBT type indication (i.e., channel access type indication) and CAPC indication in the DCI. For example, for a UL transmission burst of a UE occurring within a COT shared by the BS, if the start time position of the UL transmission and the end time position of the previous DL transmission burst are less than or equal to 16 μs, the BS can perform a Type-2C channel access to the UE before the UL transmission burst.

[0109] To enable dynamic TDD on shared spectrum, the UE / BS determines when and where to transmit and / or receive based on the indication of the channel occupancy time (COT) structure. The COT comprises multiple slots, each of which may contain downlink resources, uplink resources, or flexible resources. The COT structure reduces power consumption and channel access delay. In some scenarios (e.g., NR), the COT is typically about 8 ms, and the COT duration and the available RB sets within the COT duration can be indicated by DCI format 2_0. The higher layer parameter availableRB-SetsToAddModList and the higher layer parameter co-DurationsPerCellToAddModList can be set by the BS. The following illustrates part of the SlotFormatIndicator information element (IE), which includes availableRB-SetsToAddModList and co-DurationsPerCellToAddModList. In some scenarios, the IESlotFormatIndicator is used to configure monitoring of the group-common-PDCCH for slot format indicators (SFIs).

[0110]

[0111] In the above table, sfi-RNTI is a parameter used to set the RNTI used for SFI on a given cell, dci-PayloadSize is a parameter used to set the total length of the DCI payload scrambled with SFI-RNTI, slotFormatCombToAddModList is a list of SlotFormatCombinations for the serving cells of the UE, where each SlotFormatCombination is a parameter used to set the slot formats that occur in consecutive slots in time domain order as listed in the corresponding SlotFormatCombination, and slotFormatCombToReleaseList is a list of SlotFormatCombinations to be released.

[0112] The availableRB-SetsToAddModList is a list of AvailableRB-SetsPerCell objects, each of which contains a parameter servingCellId indicating the ID of the cell to which the corresponding settings are applicable, and a parameter positionInDCI indicating the (start) position of bits in the DCI payload indicating the availability of RB sets of the serving cell. For the serving cell, the UE is provided with the position of the available RB set indicator in DCI format 2_0 via the parameter positionInDCI. The position of the available RB set indicator in DCI format 2_0 is:

[0113] i) If no intra-cell guard bands are set for the serving cell, then 1 bit, a value of '1' at that position indicates that the serving cell is available for receptions and a value of '0' at that position indicates that the serving cell is not available for receptions, and the serving cell remains available or unavailable for receptions until the end of the remaining channel occupancy period.

[0114] ii) If intra-cell guard band(s) are indicated to be set for the serving cell, N having a one-to-one mapping with the RB sets of the serving cell. RB-set It is a bitmap of dog bits, N RB-set is the number of RB sets within the serving cell, a value of '1' in the bitmap indicates that the corresponding RB set is available for receptions, and a value of '0' in the bitmap indicates that the corresponding RB set is not available for receptions, and the RB set remains available or unavailable for reception until the end of the remaining channel occupancy period.

[0115] co-DurationsPerCellToAddModList is a list of CO-DurationsPerCell object(s), each of which contains a parameter servingCellId indicating the ID of the cell to which the setting is applicable, a parameter positionInDCI indicating the position in the DCI of a bit field indicating the channel occupancy duration for the UE's serving cells, a parameter subcarrierSpacing indicating the reference subcarrier spacing for the list of channel occupancy durations, and a co-DurationList indicating the list of channel occupancy durations in symbol units.

[0116] In some implementations, referring to FIG. 8, the available RB sets and COT duration for COT sharing may be notified to the UE(s) via DCI format 2_0 with a cyclic redundancy check (CRC) scrambled by the SFI-RNTI.

[0117] Figure 10 illustrates COT sharing between BS and UE.

[0118] When the upper layer parameter availableRB-SetsToAddModList is set, the following information can be transmitted via DCI format 2_0: Available RB Set Indicator 1, Available RB Set Indicator 2, ..., Available RB Set Indicator N1.

[0119] When the upper layer parameter co-DurationsPerCellToAddModList is set, the following information can be transmitted via the DCI format 2_0: COT Duration Indicator 1, COT Duration Indicator 2, ..., COT Duration Indicator N2.

[0120] For example, referring to FIG. 10, if the position of the COT duration indicator 1 among the bit fields in the DCI format 2_0 is set by the parameters servingCellId and positionInDCI in the CoDurationsPerCell object as a bit field for a serving cell having a serving cell index of 1, and the reference subcarrier spacing for the serving cell is set by the subcarrierSpacing as 15 kHz, and the bit field COT duration indicator 1 in the DCI format 2_0 transmitted by the BS to the UEs includes a bit value indicating 280, the UE(s) detecting the DCI format 2_0 can assume that a COT of 280 OFDM symbols based on the 15 kHz subcarrier spacing for the serving cell is initiated by the BS. If the position of the available RB set indicator 1 among the bit fields in the DCI format 2_0 is set by AvailableRB-SetsPerCell to include a bitmap for a serving cell with serving cell index 1, and the serving cell includes four RB sets, and the available RB set indicator 1 includes a bitmap of '1010', then RB sets on the serving cell can be shared by the BS and the UE during the COT period as illustrated in FIG. 10.

[0121] As mentioned above, to support SL communication stably, supporting SL communication on a shared spectrum may be considered. The SL BWP and SL resource pool discussed in the sidelink of 3GPP-based systems, as well as the RB set discussed in the shared spectrum transmission of 3GPP-based systems, may be considered to be reused for SL transmission on the shared spectrum. Hereinafter, the shared spectrum supporting SL transmission is referred to as SL-U. Below, implementations of this specification for coexisting UL / DL transmission and SL transmission on the shared spectrum are described.

[0122] In some implementations of the present specification, one or more SL BWPs may be (pre-)configured within a carrier on a shared spectrum. In some implementations of the present specification, an SL BWP may be (pre-)configured to include one or more SL resource pools. In some implementations of the present specification, at least one resource pool may be (pre-)configured to include an integer number of RB sets, where an RB set may correspond to about 20 MHz. In some implementations of the present specification, if a resource pool includes two adjacent RB sets, the RB(s) within the intra-cell guard band of the two adjacent RB sets may be defined as belonging to the resource pool. In some implementations of the present specification, interlaced RB-based transmission may be configured for PSCCH / PSSCH transmission for the SL BWP. If the UE is not configured to use interlaced RB-based PSCCH / PSSCH transmission for SL BWP, or if contiguous-RB-based transmission is configured, the UE may perform PSCCH / PSSCH transmission using contiguous-RB-based transmission.

[0123] LBT is also required for SL transmission in SL-U. The Type 1 SL channel access procedure is applicable to other SL transmissions, including PSCCH / PSSCH transmissions, S-SSB, and PSFCH transmissions. The Type 2A / 2B / 2C SL channel access procedure is applicable to the following cases:

[0124] > Type-2A is applicable if the gap is at least 25 μs.

[0125] > Type-2B is applicable if the gap is at least 16 μs.

[0126] > Type-2C is applicable for gaps less than or equal to 16 μs, and the transmission period is at most 584 μs.

[0127] Figure 11 illustrates COT sharing between UEs according to some implementations of this specification.

[0128] In the case of conventional communication on a shared spectrum, COT sharing is initiated by a BS, and all UEs that receive a DCI format (e.g., DCI format 2_0) including COT sharing information transmitted by the BS can share the COT. Since UE-to-UE sharing is performed by a COT initiating UE using only interference information around itself, if the COT is shared with an unspecified number of UEs, the interference environment around each UE may be different from the interference environment around the COT initiating UE, and thus unexpected interference problems may occur. Therefore, UE-to-UE COT sharing requires a method in which the COT initiating UE, which is the subject of sensing, shares the COT only with the UE(s) with which the COT initiating UE intends to communicate, based on the channel occupancy state determined by the COT initiating UE. Referring to FIG. 11, UE-to-UE COT sharing can be supported in a sidelink. For S-SSB / PSFCH / PSSCH / PSCCH transmission(s), a responding UE may utilize a COT shared by a COT initiating UE (using Type 1 channel access) within the RB set(s) corresponding to the shared COT. In this specification, a COT initiating UE is a UE performing a Type 1 channel access procedure, and a responding UE may be a UE that receives a PSCCH / PSSCH from a COT initiating UE and shares the COT initiated by the COT initiating UE with the COT initiating UE. SL transmission(s) from the responding UE within the shared COT may be performed if the CAPC value(s) of the SL transmission(s) have a CAPC value that is less than or equal to a CAPC value indicated in an SCI format including a corresponding COT sharing indication.

[0129] In some implementations of this specification, the SCI format may be used to transmit COT shared information. For example, SCI Format 2-A, SCI Format 2-B, or SCI Format 2-C may include the following sidelink transmission information:

[0130] > HARQ process number - 4 bits.

[0131] > New data indicator - 1 bit

[0132] > Redundancy version - 2 bits

[0133] > Source ID - 8 bits

[0134] > Destination ID - 16 bits

[0135] > HARQ feedback enabled / disabled indicator - 1 bit

[0136] > Cast type indicator - 2 bits

[0137] The above cast type directive can contain values ​​according to the following table.

[0138]

[0139] In some implementations of the present disclosure, for example, a responding UE for a shared COT may be a receiving UE that is the target of a PSCCH / PSSCH transmission from the COT initiating UE, i) in the case of a unicast from the COT initiating UE, when the source and destination IDs included in the SCI of the COT initiating UE match the corresponding destination and source IDs associated with the same unicast from the receiving UE, and ii) in the case of a groupcast and broadcast, when the destination ID included in the SCI of the COT initiating UE matches a destination ID known to the receiving UE. In some implementations of the present disclosure, a responding UE for a shared COT may be a UE identified by ID(s) if additional IDs (in addition to the source and destination IDs of the PSCCH / PSSCH transmission) are included in the COT shared information from the COT initiating UE.

[0140] Figure 12 illustrates the relationship between identifiers of a transmitting UE and identifiers of a receiving UE. In Figure 12, L1 represents Layer-1, and L2 represents Layer-2.

[0141] Each UE is assigned one or more Layer-2 IDs consisting of a source Layer-2 ID(s) and a destination Layer-2 ID(s), and the Layer-2 ID is determined according to the V2X communication mode.

[0142] The transport block carried by the PSSCH corresponds to a MAC PDU in the MAC layer, and the MAC PDU may include a MAC SDU containing SL-SCH data and a MAC subheader for the MAC SDU. The MAC subheader includes an SRC field and a DST field, and carries 16 most significant bits (MSBs) of a source Layer-2 ID set to an identifier provided by a higher layer than the MAC layer in a protocol stack, and the DST field carries 8 MSBs of a destination Layer-2 ID set to the identifier provided by a higher layer than the MAC layer.

[0143] When a transmitting (TX) UE performs transmission, the (8-bit) source Layer-1 ID is determined as the 8 LSBs of the source Layer-2, and the (16-bit) destination Layer-1 ID is determined as the 16 LSBs of the destination Layer-2 ID. For example, the TX UE sets the source Layer-1 ID (e.g., source ID of SCI format 2-A) in the sidelink transmission information of the transport block (TB) for the source and destination pair of the MAC PDU to be transmitted to the 8 least significant bits (LSBs) of the source Layer-2 ID of the MAC PDU, and sets the destination Layer-1 ID (e.g., destination ID of SCI format 2-A) to the 16 LSBs of the destination Layer-2 ID of the MAC PDU.

[0144] When a receiving (RX) UE receives, the RX UE receives 2 nd - Obtain the source Layer-1 ID and destination Layer-1 ID from the step SCI format (e.g., SCI format 2-A).

[0145] Referring to FIG. 12(a), in the case of unicast, the RX UE checks whether 16 LSBs among the source Layer-2 IDs it has are identical to the destination Layer-1 ID acquired by the RX UE, and whether 8 LSBs among the destination Layer-2 IDs it has are identical to the source Layer-1 ID acquired by the RX UE. If the 16 LSBs of the source Layer-2 ID it has are identical to the destination Layer-1 ID acquired by the RX UE, and the 8 LSBs of the destination Layer-2 ID it has are identical to the source Layer-1 ID acquired by the RX UE, decoding of the received PSSCH can be performed to acquire a transport block. For example, if a transport block is associated with unicast, and the DST field of a MAC PDU subheader decoded by the UE is equal to 8 MSBs and 16 LSBs of one of the source Layer-2 ID(s) of the UE and is equal to a destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU subheader is equal to 16 MSBs and 8 LSBs of one of the destination Layer-2 ID(s) of the UE and is equal to a source ID in the corresponding SCI, the UE can determine that the target UE of the transport block is itself.

[0146] Referring to Fig. 12(b), in the case of groupcast, the RX UE can check whether 16 LSBs among the destination Layer-2 IDs it has are identical to the destination Layer-1 ID acquired by the RX UE, and if so, can decode the received PSSCH to acquire a transport block. For example, if the transport block is associated with groupcast, and the DST field of the MAC PDU subheader decoded by the UE is identical to 8 MSBs of any one of the destination Layer-2 ID(s) of the UE and 16 LSBs are identical to the destination ID in the corresponding SCI, the UE can determine that it is one of the target UEs of the transport block.

[0147] In some implementations of this specification, more source IDs and / or destination IDs may be included in the COT sharing information (COT-SI) to allow more SL UEs to access the channel and utilize resources within a COT period. This can improve resource utilization efficiency and reduce system load / congestions by allowing fewer UEs to perform Type 1 channel access. The question is which ID to indicate and how to indicate it. Below, implementations of this specification that provide additional IDs for COT sharing are described. In the following description, the following assumptions are made:

[0148] > COT-SI is assumed to contain the CAPC used to initiate the COT, source and destination Layer-1 IDs, time domain information of the shared COT (e.g., COT duration), and frequency domain information of the shared COT (e.g., available RB set(s)).

[0149] > COT-SI is 1 st -Step SCI format and / or 2 nd -Can be included in the step SCI format.

[0150] > The responding UE sharing the above COT is i) in case of unicast, 2 nd - The receiving UE, where the source / destination IDs indicated by the step SCI format match the destination / UE IDs in the receiving UE, and / or ii) in case of groupcast, 2 nd - The destination ID indicated by the step SCI format may be a receiving UE when it matches the destination ID in the receiving UE.

[0151] In some implementations of this specification, the cell in which the COT-SI is transmitted and the cell in which the COT period and available frequency resource(s) (e.g., available RB set(s)) are indicated by the COT-SI may be the same or different.

[0152] The following may be considered as SCI format(s) for transmission of ID(s): In the following, the original ID is 2 nd - This refers to the source ID and destination ID that were transmitted in the SCI format 2-A, SCI format 2-B, or SCI format 2-C.

[0153] * Alt 1-1. 1 is SCI transmitted via PSCCH st -Step SCI format is used for additional ID and is 2 SCI transmitted via PSSCH. nd - The original ID can be used in the step SCI format. In other words, the additional ID is 1. st - It can be included in the step SCI format and transmitted through PSCCH. According to Alt 1-1, 1 st -Since the step format includes an additional ID, 2 nd - Blind decoding for step SCI format can potentially be skipped / omitted.

[0154] * Alt 1-2. 2 for both additional ID and original ID nd -Step SCI format can be used. In other words, additional ID 2 nd- It can be transmitted through PSSCH included in the step SCI format. According to Alt 1-2, even if signaling of additional ID is introduced, 1 st - The step SCI format may not be changed.

[0155] * Alt 1-3. 1 for both additional ID and original ID st -Step SCI format can be used. According to Alt 1-3, both additional ID and original ID are 1 st - Since it is transmitted through PSCCH included in the step SCI format, both the COT responding UE(s) and the receiving UE(s) of the PSSCH associated with the PSCCH are included in the 2 PSSCH. nd -You can quickly determine whether the step SCI format can be used.

[0156] Meanwhile, the question arises as to which ID is additionally indicated. The following may be considered:

[0157] * Alt 2-1. For both unicast and groupcast, the destination Layer-1 ID is additionally indicated. For example, a 16-bit destination Layer-1 ID may be included in the SCI format carrying the COT-SI. In this case, the responding UE(s) for COT sharing may be determined as follows.

[0158] ** Alt 2-1-1

[0159] For unicast, the responding UE is 2 nd - The receiving UE may be the receiving UE when the (original) source ID and (additional) destination ID indicated by the step SCI format match the destination ID and source ID of the receiving UE. In this case, COT sharing is allowed only for unicast transmissions with the COT initiating UE. In the case of groupcast, the responding UE may be the receiving UE when the (additional) destination ID matches the destination ID of the receiving UE.

[0160] ** Alt 2-1-2

[0161] In the case of unicast, the responding UE may be the receiving UE when the (additional) destination ID matches the source ID of the receiving UE. In this case, it may be possible for other UEs besides the COT initiating UE to perform unicast transmissions to the COT initiating UE or to another UE within the COT by the COT initiating UE. In the case of groupcast, the responding UE may be the UE when the (additional) destination ID matches the destination ID of the receiving UE.

[0162] Figure 13 illustrates the utilization of additional IDs according to some implementations of the present specification. Referring to Figure 13, a COT initiating UE may perform a Type 1 channel connection, and if the Type 1 channel connection is successful, may transmit a COT-SI including an original source ID, an original destination ID, and an additional destination ID within the COT. In the example of Figure 13, a COT initiator TX UE 1 may transmit the COT-SI by setting the original source ID equal to 8 LSBs of the source Layer-2 ID of TX UE 1, setting the original destination ID equal to 16 LSBs of the source Layer-2 ID of RX UE 1, and setting the additional destination ID equal to 16 LSBs of the source Layer-2 ID of TX UE 2. The RX UE 1 may determine that it is the target RX UE of the PSSCH associated with the PSCCH containing the COT-SI or the transport block carried by the PSSCH containing the COT-SI, if the 16 LSB of any one of its source Layer-2 IDs is identical to the original destination ID and the 8 LSB of any one of its destination Layer-2 IDs is identical to the original source ID. The TX UE 2 may determine that it can perform a transmission within the COT initiated by the TX UE 1, if the 16 LSB of any one of its source Layer-2 IDs is identical to the additional destination ID. For example, the TX UE 2 may perform a unicast transmission to the RX UE 2 using a Type 2 channel connection on the available RB set(s) within the COT period based on the COT-SI.

[0163] * Alt 2-2. In the case of unicast, the source ID is additionally indicated, and in the case of groupcast, the destination ID is additionally indicated. In this case, the responding UE(s) for COT sharing can be determined as follows.

[0164] For unicast, the responding UE includes (additional) source ID and 2 nd - The receiving UE may be the receiving UE when the (original) destination ID indicated by the step SCI format matches the destination ID and source ID of the receiving UE. In this case, COT sharing is allowed only for an unspecified number of UEs that wish to communicate with the COT initiating UE. In the case of groupcast, the responding UE may be the receiving UE when the (additional) destination ID matches the destination ID of the receiving UE.

[0165] According to Alt 2-2, 8 bits are required for the source ID and 16 bits for the destination ID, so the size of the SCI format may vary depending on the cast type. Taking this into account, the following methods may be considered.

[0166] ** Alt 2-2-1. The field size of the additional ID(s) is fixed at 16 bits. For unicast, the 8 LSBs (or 8 MSBs) of the additional ID(s) field are used for the source ID.

[0167] ** Alt 2-2-2. The field size of the additional ID(s) is variable depending on the cast type. The field size is 8 bits for unicast and 16 bits otherwise. According to Alt 2-2-2, since the field size of the additional ID(s) depends on the cast type, the UE is required to perform additional blind decoding.

[0168] * Alt 2-3. Both the source ID and destination ID are indicated. For example, additional 24-bit ID(s) may be included in the SCI format carrying the COT-SI. In this case, the responding UE(s) for COT sharing may be determined as follows.

[0169] For unicast, the responding UE is 1 st -Step SCI format or 2 nd- The receiving UE may be the receiving UE when the (additional) source and destination IDs indicated by the step SCI format match the destination and source IDs in the receiving UE.

[0170] For groupcast, the responding UE may be the receiving UE when the (additional) destination ID matches the destination ID in the receiving UE.

[0171] * Alt 2-4. Additional IDs are applicable only to unicast. The same methods as in Alt 2-1, Alt 2-2, and / or Alt 2-3 may be considered to determine the responding UE(s).

[0172] Meanwhile, the COT initiating UE may not wish to transmit additional ID(s). In this case, the COT initiating UE may process the ID field(s) defined for signaling additional ID(s) according to some implementations of this specification as follows.

[0173] * Alt 3-1. Additional ID(s) are set to the same value as the original ID(s). For example, the additional source ID (or destination ID) is 2 nd -Sets the value of the original source ID (or destination ID) in the step SCI format to be the same. In some implementations, additional ID(s) are set to 1 st -If included in the step SCI format, the responding UE will 2 if the additional ID(s) do not match its own ID(s). nd -Blind decoding for SCI format can be skipped.

[0174] * Alt 3-2. Additional ID(s) are set to a value of 0.

[0175] * Alt 3-3. The additional ID(s) field is not included in the SCI format. In this case, the SCI format size may vary depending on whether the additional ID(s) are included. Therefore, Alt 3-3 requires the UE to perform additional blind decoding for different SCI format sizes.

[0176] A COT initiating UE may perform Type 1 LBT (i.e., Type 1 channel access) on behalf of other UEs and transmit a COT-SI including an additional ID according to some implementations of the present specification described above. A UE receiving the COT-SI may determine whether it can perform transmission using resources within the COT based on the additional ID and its own ID.

[0177] According to some implementations of this specification, other UEs than the target RX UE to which the TX UE transmits the physical control channel and / or physical shared channel can also perform SL transmission on the COT initiated by the TX UE based on the COT-SI. In other words, by allowing the COT initiating UE to transmit additional IDs in addition to the existing source ID and destination ID, the COT initiating UE can grant more UEs the opportunity to share the COT.

[0178] In the case of conventional communication on shared spectrum, all UEs that received the DCI format (e.g., DCI format 2_0) including COT sharing information transmitted by the BS can share the COT, whereas according to some implementations of the present specification, the COT can be shared between one or more UEs intended by the COT initiating UE and the COT initiating UE based on the source ID and destination ID.

[0179] FIG. 14 is an example of a process in which a communication device performs wireless transmission according to some implementations of this specification.

[0180] A TX UE may perform operations according to some implementations of the present disclosure in connection with a wireless transmission. The TX UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the TX UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0181] In the TX UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations include: performing a type 1 channel connection on a cell for transmitting a transport block; and, based on the success of the type 1 channel connection to the cell (S1401), transmitting the transport block within the COT determined by the type 1 channel connection, the first control information format including COT sharing information including time domain information and frequency domain information regarding a COT for the cell (S1403). The first control information format may include i) a source ID field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT sharing information.

[0182] In some implementations, the source ID field may include 8 LSBs of the source Layer-2 ID of the transport block, the destination ID field may include 16 LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field may include 16 LSBs of a destination Layer-2 ID different from the destination Layer-2 ID.

[0183] In some implementations, the transport block and the first control information format may be transmitted over a physical shared channel (i.e., a physical data channel).

[0184] In some implementations, the operations may include transmitting within the COT a physical control channel carrying a second control information format for scheduling the physical shared channel and the first control information format.

[0185] In some implementations, the time domain information may include information regarding the channel occupancy period. The information regarding the channel occupancy period may include information regarding the remaining COT period. In some implementations, the information regarding the channel occupancy period may include information regarding the absolute time length. In some implementations, the information regarding the channel occupancy period may include information regarding the number of slots. In some implementations, the information regarding the channel occupancy period may include information regarding the payload size.

[0186] In some implementations, the frequency domain information may be information about available RB sets(s). In some implementations, the frequency domain information may be a frequency resource indicator value indicating available frequency resource(s).

[0187] FIG. 15 is an example of a process in which a communication device performs wireless reception according to some implementations of the present specification.

[0188] An RX UE may perform operations according to some implementations of the present disclosure in connection with SL reception. The RX UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the RX UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0189] In the RX UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: receiving (S1501) a first control information format including COT sharing information including time domain information and frequency domain information regarding a COT for a cell, the first control information format including i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT sharing information; performing (S1505) a type 2 channel connection within a COT indicated by the COT sharing information based on whether a value of the additional destination ID field matches one of source Layer-2 IDs of the communication device (S1503); and performing wireless transmission on at least one resource available within the COT based on whether the type 2 channel connection is successful.

[0190] In some implementations, the first control information format may be received over a physical shared channel (i.e., a physical data channel) carrying the transport block.

[0191] In some implementations, the source ID field may include 8 LSBs of the source Layer-2 ID of the transport block, the destination ID field may include 16 LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field may include 16 LSBs of a destination Layer-2 ID different from the destination Layer-2 ID.

[0192] In some implementations, the operations may further comprise: receiving a physical control channel carrying a second control information format for scheduling the physical shared channel and the first control information format within the COT.

[0193] As described above, the examples disclosed herein are provided to enable those skilled in the art to implement and practice the present disclosure. While the examples have been described above with reference to the examples of the present disclosure, those skilled in the art will appreciate that various modifications and variations may be made to the examples of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the examples described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0194] Implementations of this specification can be used in wireless communication systems, BSs, user equipment, and other equipment.

Claims

1. In a wireless communication system, when a communication device transmits a wireless channel, Perform type 1 channel connection on the cell for transmission of transport blocks; Based on the success of the type 1 channel connection to the cell, a first control information format including COT sharing information including time domain information and frequency domain information regarding channel occupancy time (COT) for the cell and transmitting the transport block within the COT determined by the type 1 channel connection, The first control information format comprises i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT shared information. Method of transmitting wireless channels.

2. In paragraph 1, The source ID field includes 8 least significant bits (LSBs) of the source Layer-2 ID of the transport block, the destination ID field includes 16 LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field includes 16 LSBs of a destination Layer-2 ID different from the destination Layer-2 ID. Method of transmitting wireless channels.

3. In paragraph 1, The above transport block and the first control information format are transmitted through a physical shared channel. Method of transmitting wireless channels.

4. In paragraph 3, Including transmitting a physical control channel carrying a second control information format for scheduling the physical shared channel and the first control information format within the COT. Method of transmitting wireless channels.

5. In a wireless communication system, when a communication device transmits a wireless channel, At least one transmitter / receiver; at least one processor; and At least one memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Perform type 1 channel connection on the cell for transmission of transport blocks; Based on the success of the type 1 channel connection to the cell, a first control information format including COT sharing information including time domain information and frequency domain information regarding channel occupancy time (COT) for the cell and transmitting the transport block within the COT determined by the type 1 channel connection, The first control information format comprises i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT shared information. Communication device.

6. A computer-readable non-transitory storage medium comprising at least one computer program that causes at least one processor to perform operations, the operations comprising: Perform type 1 channel connection on the cell for transmission of transport blocks; Based on the success of the type 1 channel connection to the cell, a first control information format including COT sharing information including time domain information and frequency domain information regarding channel occupancy time (COT) for the cell and transmitting the transport block within the COT determined by the type 1 channel connection, The first control information format comprises i) a source identifier (ID) field and a destination ID field for the transport block, and ii) at least one additional destination ID field for the COT shared information. Storage media.

7. When a communication device receives a wireless channel in a wireless communication system, Receive a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information about the channel occupancy time (COT) for the cell; The first control information format comprises i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT shared information; Performing a type 2 channel connection within the COT indicated by the COT shared information based on whether the value of the additional destination ID field matches any one of the source Layer-2 IDs of the communication device; and Based on the success of the above type 2 channel connection, performing wireless transmission on at least one resource available in the COT, How to receive wireless channels.

8. In paragraph 7, The above first control information format is received through a physical shared channel carrying the transport block. How to receive wireless channels.

9. In paragraph 8, The source ID field includes 8 least significant bits (LSBs) of the source Layer-2 ID of the transport block, the destination ID field includes 16 LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field includes 16 LSBs of a destination Layer-2 ID different from the destination Layer-2 ID. How to receive wireless channels.

10. In paragraph 8, Further comprising receiving a physical control channel carrying a second control information format for scheduling the physical shared channel and the first control information format within the COT. How to receive wireless channels.

11. When a communication device receives a wireless channel in a wireless communication system, At least one transmitter / receiver; at least one processor; and At least one memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Receive a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information about the channel occupancy time (COT) for the cell; The first control information format comprises i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT shared information; Performing a type 2 channel connection within the COT indicated by the COT shared information based on whether the value of the additional destination ID field matches any one of the source Layer-2 IDs of the communication device; and Based on the success of the above type 2 channel connection, performing wireless transmission on at least one resource available in the COT, Communication device.

12. A computer-readable non-transitory storage medium comprising at least one computer program that causes at least one processor to perform operations, the operations comprising: Receive a first control information format including channel occupancy time (COT) sharing information including time domain information and frequency domain information about the channel occupancy time (COT) for the cell; The first control information format comprises i) a source identifier (ID) field and a destination ID field for a transport block, and ii) at least one additional destination ID field for the COT shared information; Performing a type 2 channel connection within the COT indicated by the COT shared information based on whether the value of the additional destination ID field matches any one of the source Layer-2 IDs of the communication device; and Based on the success of the above type 2 channel connection, performing wireless transmission on at least one resource available in the COT, Storage media.

Images