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

Abstract

The communication device according to the present invention transmits a first control information format that includes COT sharing information, which includes time domain information and frequency domain information relating to channel occupancy time (COT) for a cell. The first control information format includes i) a source 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.

Description

[Technical Field]

[0001] This specification relates to wireless communication systems. [Background technology]

[0002] Wireless communication systems utilize available system resources (e.g., bandwidth, transmission power) to support communication for user equipment (UEs). With the introduction of new wireless communication technologies, not only does the number of UEs that a base station (BS) must serve within a given resource area increase, but the amount of data and control information that the BS transmits and receives between itself and the UEs it serves also increases. Since the amount of wireless resources available to the BS for communication with the UEs is finite, new methods are required for the BS to efficiently receive and transmit uplink / downlink data and / or uplink / downlink control information from / to the UEs using these finite wireless resources. In other words, with the increase in node density and / or UE density, there has been a need for methods to efficiently utilize high-density nodes or high-density UEs for communication. For example, as a way to solve the load on BSs caused by rapidly increasing data traffic, technologies have been studied that use wireless communication technology to enable direct communication between two or more nearby UEs without going through network nodes. As the need for V2X (Vehicle-to-everything), a communication technology that supports wired / wireless communication between vehicles and other transportation systems, infrastructure, networks, or pedestrians, increases, a rapid increase in inter-device communication is expected. [Overview of the project] [Problems that the invention aims to solve]

[0003] Given the rapidly increasing volume and frequency of inter-device communications, a solution is needed to stably support these communications.

[0004] The technical problems that this disclosure aims to solve are not limited to those mentioned above, and other technical problems not mentioned above will be clearly understandable to a person with ordinary skill in the art to which this invention pertains from the following description. [Means for solving the problem]

[0005] In one aspect of this specification, a method is provided for a communication device to transmit a radio channel in a wireless communication system. The method includes: performing a type 1 channel access on a cell for the transmission of a transport block; and, based on the success of the type 1 channel access to the cell, transmitting the transport block within the COT determined by the type 1 channel access, and a first control information format including COT sharing information including time domain information and frequency domain information relating to the channel occupancy time (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.

[0006] In one aspect of this specification, a communication device is provided for transmitting a radio channel in a wireless communication system. 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, if executed, storing instructions for causing the at least one processor to perform an operation. The operation includes: performing a type 1 channel access on a cell for the transmission of a transport block; and, based on the success of the type 1 channel access to the cell, transmitting the transport block within the COT determined by the type 1 channel access, and a first control information format including COT sharing information including time domain information and frequency domain information relating to the channel occupancy time (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 this specification, a computer-readable non-transitory storage medium comprising at least one computer program causing at least one processor to perform an operation, the operation comprising: performing a type 1 channel access on a cell for the transmission of a transport block; and, based on the success of the type 1 channel access to the cell, transmitting the transport block within the COT determined by the type 1 channel access, the first control information format comprising a first control information format comprising 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] Another aspect of this specification provides a method for a communication device to receive a radio channel in a wireless communication system. The method includes: receiving a first control information format including COT sharing information, which includes time domain information and frequency domain information relating to channel occupancy time (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 a type 2 channel access within the COT indicated by the COT sharing information based on whether the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication device; and performing a radio transmission on at least one resource available within the COT based on the success of the type 2 channel access.

[0009] In one aspect of this specification, a communication device is provided for receiving a radio channel in a wireless communication system. 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, if executed, storing instructions causing the at least one processor to perform an operation. The operation includes: receiving a first control information format including COT sharing information, which includes time domain information and frequency domain information relating to channel occupancy time (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 a type 2 channel access within the COT indicated by the COT sharing information based on whether the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication device; and performing a radio transmission on at least one resource available within the COT based on the success of the type 2 channel access.

[0010] In another aspect of this specification, a computer-readable non-temporary storage medium comprising at least one computer program causing at least one processor to perform an operation, the operation comprising: receiving a first control information format comprising COT sharing information comprising time domain information and frequency domain information relating to channel occupancy time (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 access within the COT indicated by the COT sharing information based on whether the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication equipment; and performing a radio transmission on at least one resource available within the COT based on the success of the type 2 channel access.

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

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

[0013] In each embodiment of this specification, the method or operation may include: transmitting or receiving within the COT a physical control channel that carries the physical shared channel and a second control information format for scheduling the first control information format.

[0014] The aforementioned problem-solving methods are only a part of the embodiments described herein, and various embodiments reflecting the technical features of this specification can be derived and understood by those with ordinary skill in the art based on the detailed description of the present invention described later. [Effects of the Invention]

[0015] According to some implementations described herein, wireless communication signals can be transmitted and received efficiently. This improves the overall throughput of the wireless communication system.

[0016] As demonstrated in some implementations herein, direct inter-device communication technologies in the licensed spectrum, which are licensed to a specific network operator and can be used exclusively or preferentially by that network operator, can also be utilized in the shared spectrum.

[0017] As demonstrated in some implementations of this specification, direct inter-device communication can be efficiently performed in a shared spectrum, which is an unlicensed spectrum that is not licensed to a specific network operator and is freely used by multiple network operators.

[0018] The effects described herein are not limited to those mentioned above, and other effects not mentioned above will be readily apparent to a person with ordinary skill in the art to which the present invention pertains from the following description. [Brief explanation of the drawing]

[0019] [Figure 1] This block diagram shows an example of a communication device capable of performing the method described herein. [Figure 2] This figure shows an example of a frame structure usable in a 3GPP-based wireless communication system. [Figure 3] This diagram illustrates a resource grid for slots. [Figure 4] This diagram illustrates a communication link in a wireless communication system. [Figure 5] This diagram illustrates the frequency and time resources required for inter-device communication. [Figure 6] This diagram illustrates the transmission structure of a physical channel for inter-device communication within a slot. [Figure 7] This diagram illustrates the transmission structure of a physical channel for inter-device communication within a slot. [Figure 8] This diagram illustrates the channel access mechanism on a shared spectrum in several implementation examples. [Figure 9] This diagram illustrates the flow of the channel access process. [Figure 10] This diagram illustrates the sharing of channel occupancy time (COT) between the BS and UE. [Figure 11] This figure illustrates the COT sharing between UEs in some implementation examples of this specification. [Figure 12] This diagram illustrates the relationship between the identifier of the transmitting UE and the identifier of the receiving UE. [Figure 13] This figure illustrates the use of additional identifiers (IDs) in some implementation examples of this specification. [Figure 14] This figure shows an example of the process by which communication equipment performs wireless transmission according to several implementation examples in this specification. [Figure 15] This figure shows an example of the process by which a communication device performs wireless reception according to several implementation examples in this specification. [Modes for carrying out the invention]

[0020] The following detailed description of implementations relating to this specification will be provided with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to illustrate exemplary implementations of this specification and does not represent the only possible forms in which this specification may be implemented. The following detailed description includes specific details to provide a complete understanding of this specification. However, those skilled in the art will understand that this specification can be implemented even without these specific details.

[0021] In some cases, known structures and devices may be omitted or illustrated in block diagrams focusing on the core function of each structure and device, in order to avoid ambiguity of the concepts described herein. Furthermore, identical components throughout this specification will be denoted by the same reference numerals.

[0022] The technologies, equipment, and systems described below can be applied to various wireless multiplexing systems.

[0023] For the sake of explanation, the following specifications will be based on communication systems compliant with 3GPP (3rd Generation Partnership Project). However, the technical features of these specifications are not limited to these. For example, even if the following detailed descriptions are based on 3GPP LTE or 5G technology, some implementations of these specifications are applicable to any other mobile communication system and future systems (e.g., 6G), with the exception of those specific to 3GPP LTE / 5G.

[0024] For terms and techniques used herein that are not specifically described, please refer to the 3GPP standard documents, e.g., 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 TS 36.322, 3GPP TS 36.323, 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS You can refer to 38.214, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.322, 3GPP TS 38.323, and 3GPP TS 38.331, among others.

[0025] In the examples of this specification described later, when a device is described as “assuming,” this may mean that the entity transmitting the channel transmits the channel in a manner that conforms to the “assumment.” The entity receiving the channel may mean that, on the premise that the channel has been transmitted in a manner that conforms to the “assumment,” it receives or decodes the channel in a manner that conforms to the “assumment.”

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

[0027] In this specification, a node is a fixed location capable of communicating with a UE and transmitting / receiving radio signals. Various forms of BS can be used as nodes, regardless of their name. A node is equipped with at least one antenna. The antenna may be a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is sometimes referred to as a point.

[0028] On the other hand, 3GPP-based communication systems use the concept of cells to manage radio resources, but cells related to radio resources are distinct from cells in geographical areas. While a "cell" in a geographical area can be understood as the coverage over which a node can provide services using a carrier, a "cell" in radio resources is associated with the bandwidth (BW), which is the frequency range configured by the carrier. Downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a valid signal can be received from a UE, depend on the carrier that carries the signal. Therefore, a node's coverage may be associated with the coverage of the "cells" of radio resources used by that node. Thus, the term "cell" is used to mean, in some cases, the coverage of a node's services, in some cases, the radio resources themselves, and in some cases, the range over which signals using those radio resources can reach with valid strength.

[0029] A “cell” in relation to 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 as a DL resource alone, or as a combination of DL and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resource (or DL ​​CC) and the carrier frequency of the UL resource (or UL CC) can be indicated by system information. Here, the carrier frequency may be the same as or different from the center frequency of each cell or each CC.

[0030] In a wireless communication system, the UE receives information from the BS via the DownLink (DL), and the UE transmits information to the BS 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.

[0031] 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 used by the physical layer but not carrying information originating from higher layers. For example, Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH), and Physical Downlink Control Channel (PDCCH) are defined as downlink physical channels, while reference signals and synchronization signals are defined as downlink physical signals. A Reference Signal (RS), also called a pilot, refers to a predefined special waveform signal that is known to both the BS and UE. For example, Demodulation Reference Signal (DMRS) and 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 used by the physical layer but not carrying information originating from higher layers. For example, Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH) are defined as uplink physical channels, and demodulated reference signals (DMRS) for uplink control / data signals and sounding reference signals (SRS) used for uplink channel measurements are also defined.

[0032] In this specification, PDCCH means a set of time-frequency resources (e.g., Resource Element (RE)) that carry Downlink Control Information (DCI), and PDSCH means a set of time-frequency resources that carry Downlink Data. PUCCH, PUSCH, and PRACH mean sets of time-frequency resources that carry Uplink Control Information (UCI), Uplink Data, and Optional Connection Preamble, respectively. Hereafter, the expression that a UE / BS transmits / receives PUCCH / PUSCH / PRACH is used to mean the same as transmitting / receiving UCI / Uplink Data / Optional Connection Preamble on or via PUCCH / PUSCH / PRACH, respectively. Furthermore, the expressions "BS / UE transmits / receives PBCH / PDCCH / PDSCH" are used interchangeably with "transmits / receives broadcast information / DCI / downlink data over or via PBCH / PDCCH / PDSCH," respectively.

[0033] In this specification, radio resources (e.g., time-frequency resources) scheduled or set up by a BS for a UE for the transmission or reception of PUCCH / PUSCH / PDSCH may also be referred to as PUCCH / PUSCH / PDSCH resources.

[0034] Since communication equipment receives physical channels and / or physical signals on a cell in the form of radio signals, it is not possible to selectively receive only radio signals containing only specific physical channels or specific physical signals via a radio frequency (RF) receiver, or to selectively receive only radio signals excluding only specific physical channels or physical signals via an RF receiver. In actual operation, communication equipment first receives the radio signal on a cell via an RF receiver, converts the radio signal, which is an RF band signal, into a baseband signal, and decodes the physical signals and / or physical channels within the baseband signal using one or more processors. Therefore, in some implementations of this specification, not receiving physical signals and / or physical channels may not actually mean that the communication equipment does not receive any radio signal containing the physical signals and / or physical channels, but rather that it does not attempt to reconstruct the physical signals and / or physical channels from the radio signal, for example, it does not attempt to decode the physical signals and / or physical channels.

[0035] The communication system 1 to which this specification applies includes wireless equipment, BS, and a network. Here, wireless equipment may mean equipment that communicates using wireless connectivity technologies (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA), WiFi, and 6G to be introduced in the future).

[0036] Wireless devices, though not limited to these, can include robots, transportation equipment, XR (eXtended Reality) devices, handheld devices, home appliances, IoT (Internet of Things) devices, and AI devices / servers. For example, transportation equipment can include ground transportation equipment with wireless communication capabilities, autonomous transportation equipment, and transportation equipment capable of communicating with other transportation equipment. Here, transportation equipment can include UAVs (Unmanned Aerial Vehicles) (e.g., drones) and UAMs (Urban Air Mobility) (e.g., unmanned aerial traffic). XR devices can include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices. Handheld devices can include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., notebook computers). Home appliances can include TVs, refrigerators, washing machines, etc. IoT devices can include sensors, smart meters, etc. For example, a BS (Broadcasting System) or network may be implemented as wireless devices, and a specific wireless device may act as a BS / network node for other wireless devices.

[0037] Wireless devices can connect to a network via BS (Body School). Artificial Intelligence (AI) technology can be applied to wireless devices, allowing them to connect to an AI server via the network. Wireless devices may communicate with each other via BS / network, but they can also communicate directly without BS / network (e.g., sidelink communication). For example, transportation equipment can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X communication). Furthermore, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices.

[0038] Wireless communication / connection can be performed between wireless devices / between BSs / between wireless devices. Here, wireless communication / connection includes uplink / downlink communication (UL / DL) and sidelink communication (SL) (or D2D communication) and can be performed by various wireless connection technologies (e.g., 5G NR). Through wireless communication / connection (UL / DL, SL), wireless devices and BSs / wireless devices can transmit / receive wireless signals from each other. To this end, at least some of the following can be performed based on the various proposals herein: various configuration information setting processes for the transmission / reception of wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0039] Figure 1 is a block diagram showing an example of a communication device capable of performing the method according to this specification. Referring to Figure 1, the first wireless device 100 and the second wireless device 200 can transmit and / or receive wireless signals by various wireless connection technologies. Here, {first wireless device 100, second wireless device 200} can correspond to the aforementioned {wireless device, BS} and / or {wireless device, wireless device}.

[0040] The first radio device 100 and the second radio device 200 each include 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 can control the memories 104, 204 and / or the transceivers 106, 206 and be configured to implement the functions, procedures and / or methods described / proposed below. For example, the processors 102, 202 can process information in the memories 104, 204 to generate first information / signals, and then transmit a radio signal containing the first information / signals via the transceivers 106, 206. Alternatively, the processors 102, 202 can receive a radio signal containing second information / signals via the transceivers 106, 206, and then store the information obtained from the signal processing of the second information / signals in the memories 104, 204. Memories 104 and 204 are connected to processors 102 and 202 and can store various information related to the operation of processors 102 and 202. For example, memories 104 and 204 can store software code that includes instructions for executing some or all of the processes controlled by processors 102 and 202, or for executing the procedures and / or methods described / proposed below. Here, processors 102 and 202 and memories 104 and 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology. Transceivers 106 and 206 are connected to processors 102 and 202 and can transmit and / or receive wireless signals via one or more antennas 108 and 208. Transceivers 106 and 206 may include a transmitter and / or receiver.

[0041] Without limiting itself, one or more protocol layers can be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 can implement one or more layers (e.g., 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, a Service Data Adaptation Protocol (SDAP) layer, and other functional layers). One or more processors 102, 202 can generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the functions, procedures, proposals and / or methods disclosed herein. One or more processors 102, 202 can generate messages, control information, data, or information according to the functions, procedures, proposals and / or methods disclosed herein. One or more processors 102, 202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information in accordance with the functions, procedures, suggestions, and / or methods disclosed herein and provide them to one or more transceivers 106, 206. One or more processors 102, 202 can receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and acquire PDUs, SDUs, messages, control information, data, or information in accordance with the functions, procedures, suggestions, and / or methods disclosed herein.

[0042] One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors 102, 202 can be implemented by hardware, firmware, software, or a combination thereof, and the firmware or software can be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals and / or methods disclosed herein may be contained in one or more processors 102, 202 or stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The functions, procedures, proposals and / or methods disclosed herein can be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0043] One or more memory units 104, 204 are connected to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memory units 104, 204 can be located inside and / or outside of one or more processors 102, 202. Furthermore, one or more memory units 104, 204 can be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0044] One or more transceivers 106, 206 can transmit / receive user data, control information, radio signals / channels, etc., as referred to in the methods and / or operation flowcharts disclosed herein, etc., to and from one or more other devices. Furthermore, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit / receive user data, control information, or radio signals to and from one or more other devices. In addition, one or more transceivers 106, 206 can be connected to one or more antennas 108, 208, and can be configured to transmit and / or receive user data, control information, radio signals / channels, etc., as referred to in the functions, procedures, proposals, methods and / or operation flowcharts disclosed herein, etc. In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). Furthermore, one or more transceivers 106, 206 can convert received user data, control information, radio signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 can convert user data, control information, radio signals / channels, etc. processed by one or more processors 102, 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

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

[0046] In this specification, a computer-readable (non-temporary) storage medium can store at least one instruction or computer program, and the at least one instruction or computer program can be configured, when executed by at least one processor, to cause the at least one processor to perform an operation relating to some embodiment or implementation described herein.

[0047] Figure 2 shows an example of a frame structure that can be used in a 3GPP-based wireless communication system.

[0048] The frame structure in Figure 2 is merely an example, and the number of subframes, slots, and symbols in a frame can be varied. In some wireless communication systems, OFDM numerology (e.g., Subcarrier Spacing: SCS) can be set differently among multiple cells aggregated under a single UE. This allows the duration (absolute time) of time resources (e.g., subframes, slots, or Transmission Time Interval: TTI) consisting of the same number of symbols to be set differently among the aggregated cells. Here, symbols can include OFDM symbols (or Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) symbols), SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols). In this specification, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM symbols are interchangeable.

[0049] Referring to FIG. 2, uplink and downlink transmissions are organized by frames. Each frame has a period of T f =(△f max ×N f / 100)×T c =10 ms, where T is the basic time unit c =1 / (△f max ×N f ), △f max =480×10 3 Hz, and N f =4096. For reference, the sampling time T s =1 / (△f ref ×N f,ref ), △f ref =15×10 3 Hz, and N f,ref =2048. T c and T s have a relationship of constant κ = T s / T c =64. A frame is composed of 10 sub - frames, and the period T sf of a single sub - frame is 1 ms. A sub - frame is further divided into slots, and the number of slots in a sub - frame depends on the sub - carrier spacing. Each slot is composed of N slot symb symbols based on the Cyclic Prefix (CP). For example, in some scenarios, for normal CP, each slot is composed of 14 OFDM symbols, and for extended CP, each slot is composed of 12 OFDM symbols. The said numerology depends on the exponentially scalable sub - carrier spacing △f = 2 u ×15 kHz. The following table shows the number of OFDM symbols per slot (N u slot ), the number of slots per frame (N symb ), and the number of slots per sub - frame (N frame,u slot ) for the sub - carrier spacing △f = 2 u ×15 kHz for normal CP.subframe,u slot ) indicates.

[0050] [Table 1]

[0051] The following table shows the subcarrier interval △f=2 for extended CP. u This shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe, all at ×15kHz.

[0052] [Table 2]

[0053] Given a subcarrier interval setting u, the slots are arranged in increasing order within the subframe, n. u s ∈{0,...,n subframe,u slot As {-1}, and in increasing order within the frame, n u s,f ∈{0,...,n frame,u slot It is numbered as -1}.

[0054] In the following, the smallest unit of time for scheduling uplink, downlink, and sidelink transmissions is referred to as a slot, and the implementations described herein are explained accordingly. However, in some wireless communication systems, the smallest unit of time for scheduling may be referred to by other terms. For example, in LTE-based systems, the smallest unit of time for scheduling transmissions is called a subframe or transmission time interval (TTI), while in NR-based systems, the smallest unit of time for scheduling is called a slot.

[0055] Figure 3 illustrates a resource grid of slots. Slots are multiple (for example, N) in the time domain. slot symbIncludes the symbol of ). For each neural network (e.g., subcarrier interval) and carrier, a Common Resource Block (CRB) N is indicated by higher-level signaling (e.g., Radio Resource Control (RRC) signaling). start,u grid Starting from, N size,u grid,x ×N RB sc Individual subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,x This is the number of resource blocks (RBs) in the resource grid, where the subscript x is DL for downlinks and UL for uplinks. RB sc This is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB sc It is usually 12. For a given antenna port p, subcarrier spacing setting u, and transmission direction (DL or UL), there is one resource grid. Carrier bandwidth N for subcarrier spacing setting u size,u gridThis is provided to the UE by higher-level parameters from the network (e.g., RRC parameters). Each element in the resource grid for the antenna port p and subcarrier spacing setting u is called a resource element (RE), and each resource element can be mapped to one complex-valued symbol. Each resource element in the resource grid is uniquely identified by index k in the frequency domain and index l in the time domain, which indicates the symbol position relative to a reference point. 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 the subcarrier spacing setting u. The center of subcarrier 0 in CRB0 for subcarrier spacing setting u coincides with "point A", which is the common reference point of the resource block grid. PRBs for subcarrier spacing setting u are defined within the Bandwidth Part (BWP), from 0 to N size,u BWP,i Numbered down to -1, where i is the number of the bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationship is as follows: n u PRB =n u CRB +N start,u BWP,i , here, N start,u BWP,i The BWP is a common resource block in which the bandwidth part starts relative to CRB0. The BWP contains multiple contiguous RBs in the frequency domain. For example, the BWP is a given neural network u within the BWPi on a given carrier. iThis is a subset of consecutive CRBs defined for a given component carrier. A carrier wave can contain up to N (e.g., 5) BWPs. A UE can be configured to have one or more BWPs on a given component carrier wave. Data communication is performed via activated BWPs, and only a predetermined number (e.g., 1) of the BWPs configured on the UE can be activated on that carrier wave.

[0056] For each BWP, the UE may provide at least one of the following parameters for the serving cell: i) subcarrier interval, ii) cyclic prefix, iii) N start BWP Assuming =275, offset RB set and length L RB The CRBN is provided by the RRC parameter locationAndBandwidth, which specifies the Resource Indicator Value (RIV). start BWP =O carrier +RB start and the number of consecutive RBs N size BWP =L RB , as well as the O provided by the RRC parameter offsetToCarrier for the subcarrier interval carrier ; Indexes within the DL BWP or UL BWP set; BWP-common parameter set and BWP-specific parameter set.

[0057] A Virtual Resource Block (VRB) is defined within the bandwidth portion, ranging from 0 to N. size,u BWP,iThe numbers are numbered down to -1, where i is the number of the bandwidth part. The UE can assume that the VRBs are mapped to the PRBs according to the mapping scheme specified to the UE (e.g., non-interleaved or interleaved mapping). If no mapping scheme is specified, the UE assumes non-interleaved mapping. In the case of non-interleaved VRB-to-PRB mapping, VRB n can be mapped to PRB n. In the case of interleaved VRB-to-PRB mapping, VRBs can be distributed and mapped to PRBs according to predefined rules.

[0058] Figure 4 illustrates a communication link in a wireless communication system.

[0059] Referring to Figure 4, in a wireless communication system, the UE receives information from the BS via the downlink (DL), and the UE transmits information to the BS via the uplink (UL). As a means to solve the burden on the BS due to rapidly increasing data traffic, technologies that support direct communication between two or more nearby UEs without going through network nodes using wireless communication technology (e.g., SideLink (SL)) communication have been studied. UEs within or outside the BS coverage can transmit data from one UE to another without going through the network via a sidelink that supports UE-to-UE direct communication using sidelink resource allocation mode, physical hierarchical signals / channels, and physical hierarchical processes. Hereinafter, direct communication between devices will be referred to as sidelink communication, and examples of its implementation will be described in this specification.

[0060] Transmission in SL uses OFDM waveforms with CP. The frame structure described in Figure 2 and the resource grid structure described in Figure 3 can be applied to SL. In some scenarios, for example in NR V2X, only specific slots can be pre-configured to accommodate SL transmission, and the available sidelink resources can consist of sidelink (time resources) and (common) RB within the SL BWP (frequency resources). A subset of available SL resources can be pre-configured to be used by several UEs for SL transmission. Such a subset of available SL resources is called a resource pool.

[0061] Figure 5 illustrates the frequency and time resources required for direct inter-device communication.

[0062] Referring to Figure 5, the resource pool consists of i) contiguous PRBs and ii) contiguous or non-contiguous slots (pre-configured) for direct inter-device communication. The BWP concept can also be applied to sidelinks. A UE can receive a BWP configuration with a neural network and resource grid for direct inter-device communication. Hereinafter, a BWP configured for direct inter-device communication will be referred to as an SL BWP. The SL BWP can occupy a contiguous portion of the carrier bandwidth. Direct inter-device transmission and direct inter-device reception take place within the SL BWP. Hereinafter, direct inter-device transmission will be referred to as sidelink transmission, and direct inter-device reception will be referred to as sidelink reception. The resource pool is defined within the SL BWP, and a single neural network is used within the resource pool. The resource pool is shared by several UEs for direct inter-device communication and is used for all transmission types (e.g., unicast, groupcast, and broadcast). A UE can receive configuration for one or more sidelink resource pools via higher-level signaling (e.g., RRC signaling). A UE can transmit over a sidelink using its own transmission resource pool while receiving data on resource pools used for sidelink transmission by other UEs.

[0063] In the frequency domain, the resource pool is divided into a predetermined number L of consecutive subchannels, and each subchannel consists of a group of consecutive RBs within a slot. The number of RBs within a subchannel is N. sch This corresponds to the subchannel size and is (pre-configured) for the resource pool. L and N schIt is provided to the UE via upper 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, based on the lowest RB index of the SL BWP, the lowest RB index of the subchannel having the lowest index within the resource pool is provided to the UE. In NR V2X, the subchannel size N sch can be the same as 10, 12, 15, 20, 25, 50, 70 or 100 RBs. In sidelink, a subchannel indicates the minimum unit for sidelink data transmission or reception. Sidelink transmission can be performed using one or more subchannels.

[0064] In the time domain, slots that are part of the resource pool are (pre)-configured and occur at a fixed period (e.g., 10240 ms). In each slot within the resource pool, among the N slot symb symbols per slot, only a subset of consecutive symbols are (pre)-configured for device-to-device direct communication. Hereinafter, the symbols (pre)-configured for device-to-device direct communication are referred to as sidelink symbols. The subset of sidelink symbols per slot is indicated by a start symbol and the number of consecutive symbols, which are (pre)-configured for each resource pool.

[0065] 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, Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Broadcast Channel (PSBCH), and Physical Sidelink Feedback Channel (PSFCH) can be used as sidelink physical channels. In this specification, PSCCH carries Sidelink Control Information (SCI) on the sidelink. For example, SCI is used to indicate resources and other transmission parameters used by the UE for PSSCH, and PSCCH transmission is associated with a Demodulation Reference Signal (DMRS). PSSCH can carry data payload and additional control information on the sidelink. Data can be organized as TBs, with each TB associated with an SCI. For example, PSSCH is used to carry control information for Transport Blocks (TBs), Hybrid Automatic Repeat reQuest (HARQ) processes, and CSI feedback triggers. In some scenarios, at least six OFDM symbols in a slot are used for PSSCH transmission, and the PSSCH is associated with a DMRS. PSBCH carries information to support synchronization in sidelinks, and in some scenarios, PSBCH can be transmitted within a Sidelink Synchronization Signal Block (S-SSB).PSFCH carries HARQ feedback over the sidelink from the UE intended as the recipient of PSSCH to the UE that performed the PSSCH transmission. Hereinafter, the UE performing the sidelink transmission will be referred to as the TX UE, and the intended recipient of the sidelink transmission will be referred to as the RX UE.

[0066] In some scenarios, SCI is transmitted in two stages. For example, in NR V2X, 1 st - The first stage SCI can be transported by PSCCH, and the second stage SCI can be transported by the same PSCCH. st - Stage SCI and 2 nd -By dividing into stages SCI, the purpose of channel sensing is to determine the resources reserved by other transmissions, i.e., other UEs that are not RX UEs of the sidelink transmission. st - Allows decoding only the SCI of stage 2. nd - The stage SCI provides additional control information required for the RX UE of the sidelink transmission.

[0067] The number of symbols used for sidelink transmission within a slot may vary depending on the physical channel being carried within that slot.

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

[0069] The PSCCH can be multiplexed on non-overlapping resources within the same slot as the associated PSSCH. Referring to FIG. 6, in the frequency domain, the PSCCH starts from the lowest RB within the subchannel occupied by the associated PSSCH, and in the time domain, it is transmitted from the second symbol within the slot. The number of symbols for the PSCCH is (pre-)set for each resource pool and may be, for example, 2 or 3 symbols. According to some scenarios (e.g., NR V2X), in the frequency domain, the PSCCH occupies N PSCCH RBs, and N PSCCH can be (pre-)set for each resource pool for the UE via higher layer signaling (e.g., RRC signaling). In some scenarios (e.g., NR V2X), N PSCCH can be set to 10, 12, 15, 20, or 25 RBs for each resource pool. In some scenarios (e.g., NR V2X), N PSCCH is contained within one subchannel, and the number of RBs N PSCCH for the PSCCH is restricted by the number of RBs N sch within the subchannel (i.e., N PSCCH ×N sch ). The PSCCH carries a 1 nd -stage SCI containing control information related to the PSSCH and the 2 st -stage SCI. For this reason, for example, SCI format 1-A is used. The 1 st -stage SCI indicates the frequency resources (e.g., subchannels) of the PSSCH that carry the current (re-)transmission of the transport block (TB), and can also indicate resource reservation for re-transmissions up to a predefined number (e.g., 2 times) of the TB. The 1 st -stage SCI includes the priority of the associated PSSCH and can include information regarding the format and size of the 2 nd -stage SCI. The 1 st-The stage SCI may include information about the Modulation and Coding Scheme (MCS) of the transport block (TB) carried by the associated PSSCH. Although not shown in Figure 6, for demodulation of the PSCCH, a DMRS associated with the PSCCH (hereinafter, PSCCH DMRS) can be transmitted within the PSCCH. For example, each PSCCH symbol (i.e., an OFDM symbol containing the PSCCH) may include a PSCCH DMRS. Although not shown in Figure 6, the DMRS associated with the PSSCH is carried on different symbols within the slot to which the PSSCH is assigned (hereinafter, PSSCH slot). Multiple time patterns are (pre-configured) within the resource pool for the PSSCH DMRS, and the 1 st -The stage SCI may include information about which time pattern is used for the associated PSSCH.

[0070] PSSCH is 2 nd - Transports a data payload consisting of a stage SCI and TB. nd - The SCI stage carries information used to decode the PSSCH and information to support HARQ feedback and CSI reporting. nd - The stage SCI may include a Stage 1 Source ID representing the identifier of the TX UE (within the physical hierarchy) and a Stage 1 Destination ID representing the identifier of the intended recipient (RX UE) of the TB. nd - The stage SCI can carry a 1-bit New Data Indicator (NDI) used to determine whether the TB transmitted in the PSSCH corresponds to a new data transmission or a retransmission. st - After decoding the stage SCI, RX UE is 2 nd - Contains the information necessary to decode the stage SCI. 2 nd -The stage SCI can be decoded using PSSCH DMRS. Before being mapped to PSSCH, 2 nd-The stage SCI and TB are channel coded and multiplexed according to a predetermined process. Depending on the number of layers (i.e., the number of data streams) supported by PSSCH, the multiplexed 2 nd - Stages SCI and TB are L of PSSCH PSSCH Before being mapped to a subchannel, it is mapped to one or two layers and precoded. The PSSCH starts from the lowest RB in the subchannel that carries the PSSCH, N PSSCH =L PSSCH ×N sch Occupying RBs, where N PSSCH is the number of RBs occupied by the PSSCH, LPSSCH is the number of subchannels for the PSSCH, and N sch This represents the number of RBs per subchannel.

[0071] Referring to Figure 6, PSSCH can be transmitted from the second symbol in a slot to the second or final symbol, or from the second symbol in a slot to the symbol immediately preceding the final symbol. In some scenarios, 7 to 14 symbols are (pre-)set in a slot for sidelinking, and PSCCH can be transmitted in 5 to 12 consecutive symbols. The number of symbols occupied by PSSCH depends on the number of SL symbols allocated in the slot and whether or not PSFCH is transmitted in that slot. Within the symbols carrying PSCCH, PSSCH is (the PSCCH is the overall L PSSCH If a subchannel is not occupied, the PSCCH can be multiplexed in the frequency domain. The second symbol in the slot (i.e., the first symbol having a PSCCH, or having PSCCH / PSSCH) can be duplicated to the first symbol in the slot for use in Automatic Gain Control (AGC). Furthermore, symbols after the last symbol in which a PSSCH exists can be used as guard symbols.

[0072] Figure 6 illustrates a sidelink transmission structure in which PSCCH occupies three symbols in the time domain, and 14 symbols in a slot consisting of 14 symbols are used for PSCCH / PSSCH transmission. However, PSCCH may occupy two symbols, and some of the leading symbols in the slot may be used for PSCCH / PSSCH transmission, with the remaining symbols used for PSFCH or for additional guard symbols.

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

[0074] Referring to Figures 6 and 7, according to some scenarios (e.g., NR V2X), the UE sends a number of symbols N for PSCCH to the resource pool via higher-level signaling (e.g., RRC signaling). sym,PSCCH And, the number of RBs N for PSCCH PSCCH Provided, PSCCH starts from the second symbol available for SL transmission in the slot and N sym,PSCCH Within each symbol, starting from the lowest RB of the lowest subchannel of the associated PSSCH, N PSCCH It is transmitted on individual RBs.

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

[0076] Referring to Figure 7, when a PSCCH is transmitted / received in a PSCCH resource candidate in a slot within the resource pool, the PSSCH associated with the PSCCH is transmitted / received in the time domain within the continuous symbols in the slot, and in the frequency domain, the L is the lowest subchannel in which the PSCCH was transmitted / received. PSSCH It is transmitted / received over multiple subchannels. If a PSSCH occupies multiple subchannels, the PSCCH resource candidates of the remaining subchannels that are not the lowest subchannel are used for the transmission of the PSSCH. PSCCH resource candidates of subchannels that are not used for PSSCH transmission in a slot in the resource pool are not used for PSCCH transmission either. The RX UE attempts to detect a PSCCH in a PSCCH resource candidate, and if it detects a PSCCH in a slot, it considers the lowest RB at which the PSCCH was detected as the lowest RB of the PSSCH, based on the SCI carried by the PSCCH, and starts from the lowest RB and proceeds N PSSCH =L PSSCH ×Nsch The PSSCH can be received on each RB.

[0077] With the emergence of the need for V2X, a communication technology that supports wired / wireless communication between vehicles and other transportation systems, infrastructure, networks, or pedestrians, a rapid increase in SL communication is anticipated. To stably support SL communication, it is possible to consider supporting SL communication not only in licensed spectra, which are licensed to specific network operators and can be used exclusively or preferentially by those network operators, but also in shared spectra, which are unlicensed spectra that are not licensed to specific network operators and can be freely used by multiple network operators. However, supporting SL communication in shared spectra requires a plan for coexistence between communication in shared spectra and SL communication. The following describes 3GPP-based communication technologies that are applicable to uplink and / or downlink communication between UEs and BSs in shared spectra.

[0078] Unless otherwise specified, the following definitions apply to terms related to shared spectra in this specification.

[0079] - Channel: A series of R&Bs in the shared spectrum where the channel access process is performed, representing the carrier wave or a portion of the carrier wave.

[0080] -Channel Access Procedure (CAP): This refers to the process of evaluating channel availability based on sensing in order to determine whether the channel is being used by other communication devices before signal transmission. The BS or UE senses the channel during a sensing slot interval, and if the power detected within the sensing slot interval for at least a certain period of time is less than the energy detection threshold, the sensing slot interval is considered idle or free; otherwise, the sensing slot interval is considered busy. CAP is indicated as LBT (Listen-Before-Talk).

[0081] -Channel occupancy: After CAP execution, this refers to the corresponding transmission on the channel by the BS / UE.

[0082] - Channel Occupancy Time (COT): This indicates the total time that a BS / UE can perform transmissions on a channel after the BS / UE has performed a CAP. COT is shared for transmissions between the BS and the corresponding UE.

[0083] In some scenarios, when set with IntraCellGuardBandsPerSCS for a carrier wave with SCS setting u in the shared spectrum, the UE is N on the carrier wave. RB-set - Given one intra-cell guard band, each intra-cell guard band is the GB of the starting RB. start,u s and size G in terms of the number of RBs size,u s Defined by GB start,u s and GB size,u s This is determined by higher-level parameters given from BS to UE, where s∈{0, 1, ..., N} RB-set The intra-cell guard band is N RB-set Separate the RB sets, and each RB set starts with RB(RB start,u s) and termination RB (RB end,u s ) is defined by UE is s∈{0, 1, ..., N RB-set Starting RB index RB for -1} start,u s and end RB index RB end,u s These are determined by the following formulas.

[0084]

number

[0085]

number

[0086] The RB set of the index is RB size,u s It consists of individual resource blocks, where RB size,u s =RB end,u s -RB start,u s It is +1. If the UE is not set for u in IntraCellGuardBandsPerSCS, the UE is set for u and carrier size N size,u grid The RB index and RB set of the intra-cell guard band are determined according to the corresponding nominal intra-cell guard band and RB pattern. If the nominal intra-cell guard band and RB set pattern does not include any intra-cell guard band, the number of RB sets for the carrier wave is N. RB-set It is 1.

[0087] If the UE is given the number of RBs = 0 for all intra-cell guard bands on a carrier where the SCS setting is u, then the UE is instructed that no intra-cell guard bands are set for the cell, then N RB-set We expect it to be >1.

[0088] Because the shared spectrum is not exclusive to any particular network operator, BS and UE can apply Listen-Before-Talk (LBT) before performing transmissions on cells configured for shared spectrum channel access. When LBT is applied, the transmitter listens to / senses the channel to determine whether it is free or congested, and only performs a transmission if the channel is deemed free. In other words, for the shared spectrum, communication equipment must determine whether the channel is being used by other communication equipment before transmitting a signal.

[0089] Figure 8 illustrates the channel access mechanism on the shared spectrum in several implementation examples.

[0090] In 3GPP-based systems, channel access on downlinks and uplinks relies on LBT (Language-Based Testing). Prior to transmission, the UE (User Environment) and BS (Bridge System) must first sense the communication channel to detect the absence of any communication. If the communication channel is an unlicensed band with a wide bandwidth, the channel sensing process relies on detecting energy levels across multiple subbands of the communication channel. LBT parameters, such as channel assessment parameters, can be set by the BS for the UE.

[0091] In some implementations, the channel access mechanism for cells configured for shared spectral channel access, i.e., the LBT mechanism, can be broadly divided into Type 1 channel access processes and Type 2 channel access processes.

[0092] Figure 9 illustrates the flow of the channel access process. In particular, Figure 9 illustrates the flow of the Type 1 channel access process.

[0093] The Type 1 channel access process is a counter-based random backoff channel access mechanism. A UE / BS attempting to perform a transmission performs LBT to sense idle channels on a shared spectrum cell. The UE / BS then checks if the channel has a deferred time T d If it senses that there is a pause during this period (S901), a random backoff counter N is generated between 0 and the competition window size (S902). The competition window size is adjusted based on the HARQ-ACK and priority access class. If the counter is 0 and the UE / BS is not performing a transmission, the UE / BS performs an additional short LBT before the transmission, with an additional slot period T. sl and additional slot period T d This is performed during (S903, S904). The duration of the additional short LBT is 43 μs, 52 μs, or 88 μs depending on the Channel Access Priority Class (CAPC) level. For example, T d =T f +m p ×T sl And, m p This is determined based on the channel access priority class. f For example, this is 16 μs, and T sl This is 9 μs. NR's shared spectral channel access introduces mini-slot level channel access to increase the number of transmissions and supports back-to-back transmissions between COTs, provided the type gap between two consecutive transmissions is not longer than 16 μs.

[0094] NR's Shared Spectrum Channel Access (NR-U) supports COT sharing. Different devices (e.g., UE / BS) can alternately use a medium / channel while maintaining an activity gap between their transmission and other transmissions. For example, when a UE / BS initiates a COT through a Type 1 channel access process, the resources within the COT can be used not only for transmission by the UE / BS but also shared for transmission by the BS / UE. NR-U supports Type 2 LBT for COT sharing. When resources within a COT initiated through a Type 1 channel access process performed by a device are shared by another device, the other device can use Type-2A, Type-2B, or Type-2C channel access, and for each type of channel access there is a specific gap limit between two adjacent transmissions, and according to this specific gap limit, Type 2 channel transmissions are distinguished into Type-2A, Type-2B, and Type-2C channel access. For Type-2A channel access, the UE / BS performs channel sensing for a period of 25 μs before the start of transmission, and performs the transmission after the channel sensing is successful. For Type-2B channel access, the UE / BS performs channel sensing for a period of 16 μs before the start of transmission, and performs the transmission after the channel sensing is successful, where the gap between the start of the transmission and the end of the previous transmission is 16 μs. For Type-2C channel access, the UE can perform the transmission immediately after the end of the gap without channel sensing, where the gap between the start of the transmission and the end of the previous transmission is less than or equal to 16 μs.

[0095] Type 2 LBT, i.e., the gap for Type 2 channel access, can be controlled by the BS through the LBT type indication (i.e., channel access type indication) and CAPC indication within 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 cause the UE to perform a Type-2C channel access before the UL transmission burst.

[0096] To enable dynamic TDD on a 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 consists of multiple slots, each slot can contain a downlink resource, an uplink resource, or a flexible resource. The COT structure reduces power consumption and channel access latency. In some scenarios (e.g., NR), the COT is typically around 8ms, and the COT period and the sets of RBs available within the COT period are indicated by DCI format 2_0. The BS sets the higher-level parameters availableRB-SetsToAddModList and co-DurationsPerCellToAddModList. The following is an example of a portion of the SlotFormatIndicator, which is an Information Element (IE) containing availableRB-SetsToAddModList and co-DurationsPerCellToAddModList. In some scenarios, the IE (Internet Indicator) SlotFormatIndicator is used to configure the group common-PDCCH to monitor for Slot Format Indicators (SFIs).

[0097] [Table 3]

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

[0099] `availableRB-SetsToAddModList` is a list of `AvailableRB-SetsPerCell` objects, each `AvailableRB-SetsPerCell` object containing a parameter `servingCellId`, which indicates the ID of the cell to which the setting can be applied, and `positionInDCI`, which is a parameter relating to the (starting) position of the bit in the DCI payload indicating the availability of the RB set for the serving cell. For a 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:

[0100] i) If it is indicated that no intra-cell guard bandwidth is set for the serving cell, the bit is 1, where a value of "1" at the position indicates that the serving cell is available for reception, and a value of "0" at the position indicates that the serving cell is not available for reception, and the serving cell remains available or unavailable for reception until the end of the remaining channel occupancy time.

[0101] ii) When it is instructed that an intra-cell guard band be set for the serving cell, N has a one-to-one mapping with the RB set of the serving cell. RB-set It is a bitmap of N bits. RB-set is the number of RB sets in the serving cell, where a value of "1" in the bitmap indicates that the RB set is available for reception, and a value of "0" in the bitmap indicates that the RB set is not available for reception. The RB set remains available or unavailable for reception until the end of the remaining channel occupancy time.

[0102] co-DurationsPerCellToAddModList is a list of CO-DurationsPerCell objects, each of which includes a parameter servingCellId, which indicates the ID of the cell to which the setting can be applied; positionInDCI, which indicates the position in the DCI of the bit field that indicates the channel occupancy duration for the UE's serving cell; subcarrierSpacing, which indicates the reference subcarrier interval for the list of channel occupancy durations; and co-DurationList, which shows the list of channel occupancy durations on a symbol-by-symbol basis.

[0103] In some implementations, as shown in Figure 8, the UE is notified of the available RB sets and COT periods for COT sharing via DCI format 2_0, which has a CRC (cyclic redundancy check) scrambled by SFI-RNTI.

[0104] Figure 10 illustrates the sharing of COT between BS and UE.

[0105] When the higher-level parameter availableRB-SetsToAddModList is set, the following information is transmitted via DCI format 2_0: available RB set indicator 1, available RB set indicator 2, ..., available RB set indicator N1.

[0106] When the higher-level parameter co-DurationsPerCellToAddModList is set, the following information is transmitted via DCI format 2_0: COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2.

[0107] For example, referring to Figure 10, if the parameters servingCellId and positionInDCI in the CoDurationsPerCell object set that the position of the COT duration indicator 1 in the bit field of DCI format 2_0 is the bit field for the serving cell whose serving cell index is 1, and the reference subcarrier interval for the serving cell is set to 15 kHz by subcarrierSpacing, and the COT duration indicator 1, which is the bit field in DCI format 2_0 transmitted to the UE by BS, contains a bit value indicating 280, then the UE, upon detecting DCI format 2_0, can assume that the COT of 280 OFDM symbols has been initiated by BS for the serving cell based on a subcarrier interval of 15 kHz. AvailableRB-SetsPerCell is set such that the bit field in the DCI format 2_0 where the available RB set indicator 1 is located contains a bitmap for a serving cell whose serving cell index is 1, and the serving cell contains four RB sets and the available RB set indicator 1 contains a bitmap of "1010", then on the serving cell, the RB sets can be shared by the BS and UE during the COT period, as illustrated in Figure 10.

[0108] As mentioned above, to ensure stable support for SL communication, it is possible to consider supporting SL communication on the shared spectrum. The SL BWP and SL resource pool discussed in the sidelink of the 3GPP-based system, as well as the RB set discussed in the shared spectrum transmission of the 3GPP-based system, are to be reused for SL transmission on the shared spectrum. Hereafter, the shared spectrum on which SL transmission is supported will be referred to as SL-U. Below, an example of implementation of this specification for coexisting UL / DL transmission and SL transmission on the shared spectrum will be described.

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

[0110] In SL-U as well, LBT is required for SL transmission. Type 1 SL channel access processes are applicable to PSCCH / PSSCH transmissions, as well as other SL transmissions including S-SSB and PSFCH transmissions. Type-2A / 2B / 2C SL channel access processes are applicable in the following cases: Type-2A is applicable if the gap is at least 25 μs. Type-2B is applicable if the gap is at least 16 μs. Type-2C is applicable to gaps smaller than or equal to 16 μs, with a maximum transmission duration of 584 μs.

[0111] Figure 11 illustrates COT sharing between UEs in some implementations of this specification.

[0112] In conventional communication over a shared spectrum, COT sharing is initiated by a BS (Broadcasting Station), and all UEs that receive a DCI format (e.g., DCI format 2_0) containing COT sharing information transmitted by the BS can share the COT. In UE-to-UE sharing, the COT-initiating UE performs COT sharing using only interference information from its own vicinity. Therefore, if the COT is shared with an unspecified number of UEs, the interference environment around each UE may differ from the interference environment around the COT-initiating UE, potentially leading to unexpected interference problems. Consequently, UE-to-UE COT sharing requires a method in which the channel occupancy state determined by the COT-initiating UE, which is the main sensing entity, is shared only with the UEs that the COT-initiating UE intends to communicate with. Referring to Figure 11, UE-to-UE COT sharing can be supported in sidelinks. In the case of S-SSB / PSFCH / PSSCH / PSCCH transmission, the responding UE can utilize the COT shared by the initiating UE (using type 1 channel access) within the RB set corresponding to the shared COT. In this specification, the initiating UE is a UE that performs a type 1 channel access process, and the responding UE is a UE that receives PSCCH / PSSCH from the initiating UE, thus sharing the COT initiated by the initiating UE with the initiating UE. SL transmission from the responding UE within the shared COT can be performed if the CAPC value of the SL transmission is less than or equal to the CAPC value indicated in the SCI format containing the COT sharing instruction.

[0113] In some implementations described herein, the SCI format can 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: >HARQ process number - 4 bits >New data indicator - 1 bit >Redundant version - 2 bits >Source ID - 8 bits >Destination ID - 16 bits >HARQ feedback enabled / disabled indicator - 1 bit >Cast type indicator - 2 bits

[0114] The cast type indicator may include values ​​according to the following table.

[0115] [Table 4]

[0116] In some implementations of this specification, for example, a responding UE to a shared COT may be a receiving UE that is the target of a PSCCH / PSSCH transmission from a COT initiating UE, i) in the case of a unicast from a COT initiating UE, when the source and destination IDs included in the SCI of the COT initiating UE match the destination and source IDs associated with the same unicast at the receiving UE, within the same COT; and ii) in the case of a group cast 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 this specification, a responding UE to a shared COT may be a UE identified by an ID, if an additional ID (in addition to the source and destination IDs of the PSCCH / PSSCH transmission) is included in the COT sharing information from the COT initiating UE.

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

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

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

[0120] When a transmitting (TX)UE performs a transmission, the (8-bit) Source Layer-1 ID is determined to be the eight least significant bits (LSBs) of the Source Layer-2 ID, and the (16-bit) Destination Layer-1 ID is determined to be the sixteenth LSB of the Destination Layer-2 ID. For example, the TX UE sets the Source Layer-1 ID (e.g., Source ID in SCI format 2-A) in the sidelink transmission information of the transport block (TB) for the source and destination pair of MAC PDUs to be transmitted to the eight 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 in SCI format 2-A) to the sixteenth LSB of the Destination Layer-2 ID of the MAC PDU.

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

[0122] Referring to Figure 12(a), in the case of unicast, the RX UE checks whether 16 LSBs from its own source Layer-2 ID are the same as the destination Layer-1 ID acquired by the RX UE, and whether 8 LSBs from its own destination Layer-2 ID are the same as the source Layer-1 ID acquired by the RX UE. If 16 LSBs of the source Layer-2 ID owned by the RX UE are the same as the acquired destination Layer-1 ID, and 8 LSBs of the destination Layer-2 ID owned by the RX UE are the same as the source Layer-1 ID acquired by the RX UE, the RX UE can perform decomposition on the received PSSCH and obtain the transport block. For example, if a transport block is associated with a unicast, and the DST field of the MAC PDU subheader decoded by the UE is identical to the eight MSBs of any one of the UE's source Layer-2 IDs, and the sixteen LSBs are identical to the destination ID in the SCI, and the SRC field of the decoded MAC PDU subheader is identical to the sixteen MSBs of any one of the UE's destination Layer-2 IDs, and the eight LSBs are identical to the source ID in the SCI, then the UE can determine that it is the target UE of the transport block.

[0123] Referring to Figure 12(b), in the case of a group cast, the RX UE checks whether 16 LSBs from its own destination Layer-2 IDs are the same as the destination Layer-1 ID acquired by the RX UE. If they are the same, the RX UE can decode the received PSSCH and obtain the transport block. For example, if the transport block is associated with a group cast, and the DST field of the MAC PDU subheader decoded by the UE is the same as the 8 MSBs of any one of the UE's destination Layer-2 IDs, and the 16 LSBs are the same as the destination ID in the SCI, the UE can determine that one of the target UEs of the transport block is itself.

[0124] In some implementations of this specification, more source IDs and / or destination IDs can be included in the COT Sharing Information (COT-SI) to allow more SL UEs to access the channel and utilize resources within the COT period. This can improve resource utilization efficiency and reduce system load / congestion by allowing fewer UEs to perform Type 1 channel access. The question then becomes which IDs to specify and how to indicate them. The following describes implementations of this specification for providing additional IDs for COT sharing. The following assumptions are made in the following description: >COT-SI is assumed to include 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 said shared COT (e.g., available RB sets). >COT-SI is 1 st - Stage SCI format and / or 2 nd - Can be included in the SCI format. >The response UE that shares the aforementioned COT is i) unicast, 2 nd - A receiving UE where the source / destination ID indicated by the stage SCI format matches the destination / UE ID in the receiving UE, and / or ii) in the case of a group cast, 2 nd - A recipient UE can be one whose destination ID, as indicated by the staged SCI format, matches the destination ID in the receiving UE.

[0125] In some implementations of this specification, the cell on which the COT-SI is transmitted and the cell on which the COT period and available frequency resources (e.g., available RB sets) are indicated by the COT-SI may be the same or different.

[0126] The following can be considered as the SCI format for ID transmission. In the following, the original ID is 2nd - This refers to source IDs and destination IDs transmitted in the tiered SCI format, which is SCI Format 2-A, SCI Format 2-B, or SCI Format 2-C.

[0127] *Alt1-1.SCI is transmitted via PSCCH. st - The tiered SCI format is used for the additional ID, and is SCI transmitted via PSSCH. nd - The tiered SCI format can be used for the original ID. That is, the additional ID is 1 st -Included in the SCI format and transmitted via PSCCH. According to Alt1-1, 1 st -The stage format includes an additional ID, so 2 nd - Blind decoding for the tiered SCI format may potentially be skipped / omitted.

[0128] *Alt1-2. For both the additional ID and the original ID, 2 nd - A tiered SCI format can be used. That is, if the additional ID is 2 nd -It can be included in the tiered SCI format and transmitted via PSSCH. According to Alt1-2, even if signaling of additional IDs is introduced, 1 st - The tiered SCI format may not change.

[0129] *Alt1-3. For both the additional ID and the original ID, 1 st -The tiered SCI format can be used. According to Alt1-3, both the additional ID and the original ID are 1 st - Since it is included in the staged SCI format and transmitted via PSCCH, both the COT response UE and the receiving UE of the PSSCH associated with the PSCCH are included in the PSSCH. nd - It allows for a quick determination of whether or not the tiered SCI format can be utilized.

[0130] On the other hand, the question arises as to which IDs will be additionally specified. The following can be considered:

[0131] *Alt2-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 response UE for COT sharing can be determined as follows:

[0132] **Alt2-1-1

[0133] In the case of unicast, the response UE is 2 nd - The receiving UE may be the (original) source ID and (additional) destination ID indicated by the tiered SCI format when they match the destination ID and source ID in the receiving UE. In this case, COT sharing is permitted only for unicast transmission with the COT initiating UE. In the case of a group cast, the responding UE may be the receiving UE when its (additional) destination ID matches the destination ID in the receiving UE.

[0134] **Alt2-1-2

[0135] In the case of a unicast, the responding UE can be the receiving UE if the (additional) destination ID matches the source ID in the receiving UE. In this case, other UEs other than the COT initiating UE may perform a unicast transmission to the COT initiating UE or to another UE within the COT initiated by the COT initiating UE. In the case of a groupcast, the responding UE can be the receiving UE if the (additional) destination ID matches the destination ID in the receiving UE.

[0136] Figure 13 illustrates the use of additional IDs in some implementations of this specification. Referring to Figure 13, a COT-initiating UE can perform a Type 1 channel access, and if the Type 1 channel access is successful, it can transmit a COT-SI within the COT that includes the original source ID, the original destination ID, and an additional destination ID. In the example in Figure 13, TX UE 1, which is the COT initiator, can transmit a COT-SI by setting the original source ID to be the same as the eight LSBs of the source Layer-2 ID of TX UE 1, setting the original destination ID to be the same as the sixteen LSBs of the source Layer-2 ID of RX UE 1, and setting the additional destination ID to be the same as the sixteen LSBs of the source Layer-2 ID of TX UE 2. RX UE 1 can determine that it is the target RX UE of the PSCCH associated with the COT-SI, or the transport block carried by the PSCCH containing the COT-SI, if 16 LSBs of any one of its source Layer-2 IDs are the same as the original destination ID, and 8 LSBs of any one of its destination Layer-2 IDs are the same as the original source ID. TX UE 2 can determine that it is capable of performing a transmission within the COT initiated by TX UE 1 if 16 LSBs of any one of its source Layer-2 IDs are the same as the additional destination ID. For example, based on the COT-SI, TX UE 2 can perform a unicast transmission to RX UE 2 using type 2 channel access on an available RB set within the COT period.

[0137] *Alt2-2. In the case of a unicast, the source ID is additionally specified, and in the case of a groupcast, the destination ID is additionally specified. In this case, the response UE for COT sharing can be determined as follows:

[0138] In the case of a unicast, the responding UE may be the receiving UE if the (additional) source ID and the (original) destination ID indicated by the 2nd-stage SCI format match the destination ID and source ID in the receiving UE. In this case, COT sharing is permitted only to an unspecified number of UEs attempting to communicate with the COT initiating UE. In the case of a groupcast, the responding UE may be the receiving UE if the (additional) destination ID matches the destination ID in the receiving UE.

[0139] According to Alt2-2, since 8 bits are required for the source ID and 16 bits for the destination ID, the size of the SCI format may vary depending on the cast type. Taking this into consideration, the following approach can be considered.

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

[0141] **Alt2-2-2. The field size of the additional ID is variable depending on the cast type. The field size is 8 bits for unicast and 16 bits otherwise. According to Alt2-2-2, because the field size of the additional ID depends on the cast type, the UE is required to perform additional blind decoding.**

[0142] *Alt2-3. Both the source ID and destination ID are indicated. For example, an additional 24-bit ID may be included in the SCI format carrying the COT-SI. In this case, the response UE for COT sharing can be determined as follows:

[0143] In the case of unicast, the response UE is 1 st - Stage SCI format or 2 nd- The receiving UE may be the (additional) source and destination IDs indicated by the tiered SCI format when they match the destination and source IDs in the receiving UE.

[0144] In the case of a group cast, the responding UE may be the receiving UE if the (additional) destination ID matches the destination ID in the receiving UE.

[0145] *Alt2-4. Additional IDs are applicable only to unicasts. The same methods as Alt2-1, Alt2-2, and / or Alt2-3 can be considered to determine the response UE.

[0146] On the other hand, there may be cases where the COT-initiated UE does not wish to transmit additional IDs. In this case, the COT-initiated UE may process the ID field defined for signaling additional IDs as follows, according to some implementations herein.

[0147] *Alt3-1. The additional ID will be set to the same value as the original ID. For example, the additional source ID (or destination ID) will be 2 nd - The value of the original source ID (or destination ID) in the tiered SCI format is set to be the same. In some implementations, the additional ID is 1 st -If included in the stage SCI format, if the additional ID does not match its own ID, the response UE will be 2 nd - Blind decoding for the SCI format can be skipped.

[0148] *Alt3-2. The additional ID will be set to a value of 0.

[0149] *Alt3-3. The additional ID field is not included in the SCI format. In this case, the size of the SCI format may differ depending on whether or not the additional ID is included. Therefore, according to Alt3-3, the UE is required to perform additional blind decoding for different SCI format sizes.

[0150] A COT-initiating UE can perform a 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 of the implementations described herein above. A UE that receives the COT-SI can determine, based on the additional ID and its own ID, whether it can use resources within the COT to perform the transmission.

[0151] According to some implementations of this specification, other UEs that are not the target RX UE on 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. That is, by allowing the COT-initiating UE to transmit additional IDs in addition to the conventional source ID and destination ID, the COT-initiating UE can give more UEs the opportunity to share the COT.

[0152] In conventional communication over a shared spectrum, all UEs that receive a DCI format (e.g., DCI format 2_0) containing COT sharing information transmitted by a BS can share the COT. In contrast, according to some implementations herein, the COT can be shared between the COT initiating UE and one or more UEs intended by the COT initiating UE, based on the source ID and destination ID.

[0153] Figure 14 shows an example of the process by which communication equipment performs wireless transmission according to some implementations described herein.

[0154] A TX UE can perform operations relating to some of the implementations described herein in connection with wireless transmission. A 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 relating to some of the implementations described herein. A processing device for a 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 relating to some of the implementations described herein. A computer-readable (non-temporary) storage medium may store at least one computer program that, when executed by the at least one processor, includes instructions that cause the at least one processor to perform operations relating to some of the implementations described herein. A computer program or computer program product may be recorded on at least one computer-readable (non-temporary) storage medium and, when executed, include instructions that cause (at least one processor) to perform operations relating to some of the implementations described herein.

[0155] In the TX UE, the processing device, the computer-readable (non-temporary) storage medium, and / or the computer program product, the operation includes: performing a type 1 channel access on a cell for the transmission of a transport block; and, based on the success of the type 1 channel access to the cell (S1401), transmitting the transport block within the COT determined by the type 1 channel access, and a first control information format including COT sharing information including time domain information and frequency domain information relating to the 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.

[0156] In some implementations, the source ID field may include eight LSBs of the source Layer-2 ID of the transport block, the destination ID field may include sixteen LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field may include sixteen LSBs of destination Layer-2 IDs different from the destination Layer-2 ID.

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

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

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

[0160] In some implementations, the frequency domain information may be information about the available RB set. In some implementations, the frequency domain information may be a frequency resource indicator value indicating the available frequency resources.

[0161] Figure 15 shows an example of the process by which a communication device performs wireless reception according to some implementations described herein.

[0162] The RX UE can perform operations relating to some implementations herein 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, when executed, storing instructions causing the at least one processor to perform operations relating to some implementations herein. 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, when executed, storing instructions causing the at least one processor to perform operations relating to some implementations herein. A computer-readable (non-temporary) storage medium may store at least one computer program that, when executed by the at least one processor, includes instructions causing the at least one processor to perform operations relating to some implementations herein. A computer program or computer program product may be recorded on at least one computer-readable (non-temporary) storage medium and, when executed, include instructions causing (at least one processor) to perform operations relating to some implementations herein.

[0163] In the RX UE, the processing device, the computer-readable (non-temporary) storage medium, and / or the computer program product, the operation may include: receiving a first control information format including COT sharing information, which includes time-domain and frequency-domain information relating to the COT for a cell (S1501), 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 a type 2 channel access within the COT indicated by the COT sharing information (S1505) based on whether the value of the additional destination ID field matches any one of the source Layer-2 IDs of the communication device (S1503); and performing a radio transmission on at least one resource available within the COT based on the success of the type 2 channel access.

[0164] In some implementations, the first control information format can be received via a physical shared channel (i.e., a physical data channel) that carries the transport block.

[0165] In some implementations, the source ID field may include eight LSBs of the source Layer-2 ID of the transport block, the destination ID field may include sixteen LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field may include sixteen LSBs of destination Layer-2 IDs different from the destination Layer-2 ID.

[0166] In some implementations, the operation may further include: receiving the physical shared channel and the physical control channel carrying the second control information format for scheduling the first control information format within the COT.

[0167] As described above, the examples of the present invention disclosed are provided so that a person of the ordinary skill in the art relating to the present invention can realize and implement the present invention. While the above has been described with reference to preferred embodiments of the present invention, a person of the ordinary skill in the art can modify and change the present invention in various ways. Therefore, the present invention is not limited to the examples disclosed herein, but is intended to provide the broadest possible scope consistent with the principles and novel features disclosed herein.

[0168] The realization of the present invention can be used in wireless communication systems, such as in BS or user equipment or other equipment.

Claims

1. In a wireless communication system, when communication equipment transmits a wireless channel, Perform a Type 1 channel access on the cell for the transmission of transport blocks; Based on the success of the Type 1 channel access to the cell, the transmission of a first control information format including COT sharing information, which includes time domain information and frequency domain information regarding the Channel Occupancy Time (COT) for the cell, and the transport block within the COT determined by the Type 1 channel access, The first control information format includes i) a source identifier (IDifier: 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. Wireless channel transmission method.

2. The source ID field includes the eight least significant bits (LSBs) of the source Layer-2 ID of the transport block, the destination ID field includes the sixteen LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field includes the sixteen LSBs of a destination Layer-2 ID different from the destination Layer-2 ID. The wireless channel transmission method according to claim 1.

3. The transport block and the first control information format are transmitted via a physical shared channel. The wireless channel transmission method according to claim 1.

4. This includes transmitting within the COT a physical control channel that carries the physical shared channel and a second control information format for scheduling the first control information format, The wireless channel transmission method according to claim 3.

5. In a wireless communication system, when communication equipment transmits a wireless channel, At least one transceiver; At least one processor; and It includes at least one memory that is operablely connected to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform an operation, the operation being: Perform a Type 1 channel access on the cell for the transmission of transport blocks; Based on the success of the Type 1 channel access to the cell, the first control information format, which includes COT sharing information including time domain information and frequency domain information relating to the channel occupancy time (COT) for the cell, and the transport block are transmitted within the COT determined by the Type 1 channel access. 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 shared information. Communication equipment.

6. A computer-readable non-transitor storage medium comprising at least one computer program causing at least one processor to perform an operation, wherein the operation is: Perform a Type 1 channel access on the cell for the transmission of transport blocks; Based on the success of the Type 1 channel access to the cell, the first control information format, which includes COT sharing information including time domain information and frequency domain information relating to the channel occupancy time (COT) for the cell, and the transport block are transmitted within the COT determined by the Type 1 channel access. 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 shared information. storage medium.

7. In a wireless communication system, when a communication device receives a wireless channel, A first control information format is received, which includes COT sharing information, including time domain information and frequency domain information regarding the channel occupancy time (COT) for a cell. 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 shared information; Based on the fact that the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication device, perform a type 2 channel access within the COT as indicated by the COT sharing information; and Based on the success of the Type 2 channel access, the following is performed: Wireless channel reception method.

8. The first control information format is received via a physical shared channel that carries the transport block. The wireless channel receiving method according to claim 7.

9. The source ID field includes the eight least significant bits (LSBs) of the source Layer-2 ID of the transport block, the destination ID field includes the sixteen LSBs of the destination Layer-2 ID of the transport block, and the additional destination ID field includes the sixteen LSBs of a destination Layer-2 ID different from the destination Layer-2 ID. The wireless channel receiving method according to claim 8.

10. The COT further includes receiving the physical shared channel and a physical control channel that carries a second control information format for scheduling the first control information format. The wireless channel receiving method according to claim 8.

11. In a wireless communication system, when a communication device receives a wireless channel, At least one transceiver; At least one processor; and It includes at least one memory that is operablely connected to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform an operation, the operation being: A first control information format is received, which includes COT sharing information, including time domain information and frequency domain information regarding the channel occupancy time (COT) for a cell. 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 shared information; Based on the fact that the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication device, perform a type 2 channel access within the COT as indicated by the COT sharing information; and Based on the success of the Type 2 channel access, the following is performed: Communication equipment.

12. A computer-readable non-temporary storage medium comprising at least one computer program that causes at least one processor to perform an operation, wherein the operation is: A first control information format is received, which includes COT sharing information, including time domain information and frequency domain information regarding the channel occupancy time (COT) for a cell. 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 shared information; Based on the fact that the value of the additional destination ID field matches one of the source Layer-2 IDs of the communication device, perform a type 2 channel access within the COT as indicated by the COT sharing information; and Based on the success of the Type 2 channel access, the following is performed: storage medium.

Images