Notification operation method and device for shared COT in SL-U

Abstract

A method for operating a first device 100 in a wireless communication system is proposed. The method may include the steps of: receiving COT sharing information for a COT interval, including a first ID, from a second device 200; determining to use the COT interval based on the first ID being the same as a second ID of the first device 100; performing channel sensing on transmission resources in the COT interval; and performing SL communication based on a result of the channel sensing.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems. [Background technology]

[0002] Sidelink (SL) is a communication method that establishes a direct link between terminals (User Equipment, UE) and directly exchanges voice or data between terminals without going through a base station (BS). SL is being considered as a solution to alleviate the burden on base stations due to the rapidly increasing data traffic. V2X (vehicle-to-everything) is a communication technology that exchanges information with other vehicles, pedestrians, infrastructure-based objects, etc. via wired or wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided via the PC5 interface and / or Uu interface. Summary of the Invention [Problem to be solved by the invention]

[0003] Meanwhile, as more and more communication devices require larger communication capacities, there is an emerging need for improved mobile broadband communication compared to existing radio access technologies (RATs). As a result, communication systems that take into account reliability- and latency-sensitive services or terminals are being discussed, and next-generation wireless access technologies that take into account improved mobile broadband communication, massive machine-type communication (MTC), ultra-reliable and low latency communication (URLLC), etc. can be called new radio access technology (RAT) or new radio (NR). [Means for solving the problem]

[0004] According to an embodiment of the present disclosure, a method for wireless communication by a first device is provided, which may include: receiving, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determining to use the COT interval based on the first ID being the same as a second ID of the first device; performing channel sensing on transmission resources within the COT interval; and performing sidelink (SL) communication based on a result of the channel sensing.

[0005] According to one embodiment of the present disclosure, there is provided a first device that performs wireless communication. For example, the first device may include at least one transceiver; at least one processor; and at least one memory that is executablely connected to the at least one processor and that stores instructions that, when executed by the at least one processor, cause the first device to perform operations. For example, the operations may include: receiving, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determining to use the COT interval based on the first ID being the same as a second ID of the first device; performing channel sensing on transmission resources within the COT interval; and performing sidelink (SL) communication based on a result of the channel sensing.

[0006] According to one embodiment of the present disclosure, there is provided an apparatus configured to control a first terminal. For example, the apparatus may include at least one processor; and at least one memory executablely connected to the at least one processor and storing instructions that cause the first terminal to perform operations based on the instructions being executed by the at least one processor. For example, the operations may include: receiving, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determining to use the COT interval based on the first ID being the same as a second ID of the first device; performing channel sensing on transmission resources within the COT interval; and performing sidelink (SL) communication based on a result of the channel sensing.

[0007] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having stored thereon instructions, which, when executed, may cause a first device to: receive, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determine to use the COT interval based on the first ID being the same as a second ID of the first device; perform channel sensing on transmission resources within the COT interval; and perform sidelink (SL) communication based on a result of the channel sensing.

[0008] According to an embodiment of the present disclosure, there is provided a method for a second device to perform wireless communication. For example, the method may include: transmitting, to a first device, channel occupancy time (COT) sharing information for a COT interval, including a first identifier (ID). For example, based on the first ID being the same as a second ID of the first device, determining that the COT interval is to be used by the first device.

[0009] According to one embodiment of the present disclosure, there is provided a second device that performs wireless communication. For example, the second device may include at least one transceiver; at least one processor; and at least one memory that is operably connected to the at least one processor and that stores instructions that, when executed by the at least one processor, cause the second device to perform an operation. For example, the operation may include: transmitting, to a first device, channel occupancy time (COT) sharing information for a COT interval, the COT interval including a first identifier (ID), where the COT interval is determined to be used by the first device based on the first ID being the same as a second ID of the first device. [Effects of the Invention]

[0010] The terminal can efficiently carry out SL communication. [Brief explanation of the drawings]

[0011] [Figure 1] 1 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. [Figure 2] 1 illustrates the electromagnetic spectrum, according to one embodiment of the present disclosure. [Figure 3] 1 illustrates the structure of an NR system according to one embodiment of the present disclosure. [Figure 4] 1 illustrates a radio protocol architecture according to one embodiment of the present disclosure. [Figure 5] 1 illustrates a structure of an NR radio frame according to one embodiment of the present disclosure. [Figure 6] 1 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure. [Figure 7] 1 illustrates an example of a BWP according to an embodiment of the present disclosure. [Figure 8] According to one embodiment of the present disclosure, a procedure for a terminal to perform V2X or SL communication depending on a transmission mode is shown. [Figure 9] 1 illustrates three cast types according to one embodiment of the present disclosure. [Figure 10] 1 illustrates an example of a DRX cycle according to an embodiment of the present disclosure. [Figure 11] 1 illustrates an example of a wireless communication system that supports unlicensed spectrum, according to one embodiment of the present disclosure. [Figure 12] 1 illustrates a method for occupying resources in an unlicensed spectrum according to one embodiment of the present disclosure. [Figure 13] According to one embodiment of the present disclosure, a case is shown in which multiple LBT-SBs are included in the unlicensed band. [Figure 14] 1 illustrates a CAP operation for a base station transmitting a downlink signal over an unlicensed spectrum, according to one embodiment of the present disclosure. [Figure 15]1 illustrates a Type 1 CAP operation of a terminal for uplink signal transmission, according to one embodiment of the present disclosure. [Figure 16] 1 illustrates contention operation for LBE and FBE channels according to one embodiment of the present disclosure. [Figure 17] 1 illustrates an example of operations performed within a Shared COT according to one embodiment of the present disclosure. [Figure 18] 1 illustrates a procedure for a terminal receiving COT sharing information to use COT according to one embodiment of the present disclosure. [Figure 19] 1 illustrates a procedure for a terminal receiving COT sharing information to use COT according to one embodiment of the present disclosure. [Figure 20] 10 illustrates a procedure for a first device to perform wireless communication according to one embodiment of the present disclosure. [Figure 21] 10 illustrates a procedure for a second device to perform wireless communication according to an embodiment of the present disclosure. [Figure 22] 1 illustrates a communication system 1 according to one embodiment of the present disclosure. [Figure 23] 1 illustrates a wireless device according to one embodiment of the present disclosure. [Figure 24] 1 illustrates a signal processing circuit for a transmit signal according to one embodiment of the present disclosure. [Figure 25] 1 illustrates a wireless device according to one embodiment of the present disclosure. [Figure 26] 1 illustrates a mobile device according to one embodiment of the present disclosure. [Figure 27] 1 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Also, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0013] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Therefore, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0014] As used herein, "at least one of A and B" can mean "only A," "only B," or "both A and B." Additionally, as used herein, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted as "at least one of A and B."

[0015] Furthermore, in this specification, "at least one of A, B, and C" can mean "only A," "only B," "only C," or "any combination of A, B, and C." Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" can mean "at least one of A, B, and C."

[0016] Furthermore, parentheses used herein may mean "for example." Specifically, when "control information (PDCCH)" is used, "PDCCH" is proposed as an example of "control information." Furthermore, "control information" in this specification is not limited to "PDCCH," and "PDCCH" is proposed as an example of "control information." Furthermore, when "control information (i.e., PDCCH)" is used, "PDCCH" is proposed as an example of "control information."

[0017] In the following description, "when, if, in case of" may be replaced with "based on."

[0018] In this specification, technical features individually described in one drawing may be embodied individually or simultaneously.

[0019] In this specification, a higher layer parameter may be a parameter that is configured for a terminal, configured in advance, or predefined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0020] The following technologies can be used in various wireless communication systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented in wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000. TDMA can be implemented in wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), and enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and evolved UTRA (E-UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of evolved UMTS (E-UMTS) that uses evolved-UMTS terrestrial radio access (E-UTRA), and employs OFDMA on the downlink and SC-FDMA on the uplink. LTE-A (advanced) is an evolution of 3GPP LTE.

[0021] 5G NR is a successor technology to LTE-A and is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, including low-frequency bands below 1 GHz, intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0022] The goals of the 6G (wireless communication) system include (i) extremely high data speeds per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption for battery-free IoT devices, (vi) ultra-reliable connections, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system is based on four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements shown in Table 1 below. In other words, Table 1 is a table showing an example of the requirements for a 6G system.

[0023] [Table 1]

[0024] The 6G system has key elements such as eMBB (Enhanced mobile broadband), URLLC (Ultra-reliable low latency communications), mMTC (massive machine-type communication), AI integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0025] 1 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 1 can be combined with various embodiments of the present disclosure.

[0026] 6G systems are expected to have 50 times higher simultaneous wireless communication connectivity than 5G wireless communication systems. URLLC, a key feature of 5G, could become a key technology in 6G communications by providing end-to-end delays of less than 1 ms. 6G systems may have much better volumetric spectral efficiency than the commonly used area spectral efficiency. 6G systems can offer advanced battery technology for extremely long battery life and energy harvesting, eliminating the need for separate charging for mobile devices in 6G systems. The new network characteristics of 6G are as follows:

[0027] - Satellite integrated network: 6G is expected to be integrated with satellites to provide a global mobile network. The integration of terrestrial, satellite and public networks into one wireless communication system is crucial for 6G.

[0028] -Connected intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, evolving wirelessly from "connected things" to "connected intelligence." AI can be applied to each step of the communication process (or each step of signal processing, as described below).

[0029] Seamless integration of wireless information and energy transfer: 6G wireless networks will transmit power to charge the batteries of devices such as smartphones and sensors. Therefore, wireless information and energy transmission (WIET) can be integrated.

[0030] -Ubiquitous super 3D connectivity: Connecting drones and very low Earth orbit satellite networks to core network functions will create 6G ubiquitous super 3D connectivity.

[0031] Some common requirements for the characteristics of the new 6G network mentioned above are:

[0032] -Small cell networks: The idea of ​​small cell networks was introduced in cellular systems to improve the quality of received signals, resulting in increased throughput, energy efficiency, and spectral efficiency. As a result, small cell networks are an essential feature of 5G and beyond 5G (5G) communication systems. Therefore, 6G communication systems also adopt the features of small cell networks.

[0033] -Ultra-dense heterogeneous network: Ultra-dense heterogeneous networks are likely to become another key feature of 6G communication systems. Multi-layer networks composed of heterogeneous networks will improve overall QoS and reduce costs.

[0034] High-capacity backhaul: The backhaul connection is characterized as a high-capacity backhaul network to support large volumes of traffic. High-speed optical fiber and free-space optical communication (FSO) systems can be a possible solution to the problem.

[0035] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) via communication is one of the functions of 6G wireless communication systems. Therefore, radar systems may be integrated with 6G networks.

[0036] Softwarization and virtualization: Softwarization and virtualization are two key features that underpin the design process for 5GB networks to ensure flexibility, reconfigurability and programmability, and the ability for billions of devices to share a shared physical infrastructure.

[0037] The following describes the core implementation technologies of the 6G system.

[0038] Artificial Intelligence: The most important and newly introduced technology for the 6G system is AI. 4G systems did not involve AI. 5G systems partially or very limitedly support AI. However, 6G systems will fully support AI for automation. Advances in machine learning will create a more intelligent network for real-time communication in 6G. The introduction of AI into communications will simplify and improve real-time data transmission. AI can use numerous analyses to determine how complex target operations are executed. In other words, AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play an important role in M2M, machine-to-human, and human-to-machine communications. AI will also enable rapid communication in BCI (Brain-Computer Interface). AI-based communication systems are supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent radios, self-sustaining wireless networks, and machine learning.

[0039] Terahertz Communication: Data transmission rates can be increased by increasing bandwidth. This can be achieved by using sub-THz communication over a wide bandwidth and applying advanced massively multiple input / output (MIMO) technology. Also known as submillimeter radiation, THz waves typically refer to the frequency band between 0.1 THz and 10 THz, with wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (sub-THz band) is considered the primary portion of the THz band for cellular communications. Adding the sub-THz band to the mmWave band will increase 6G cellular communication capacity. Of the defined THz bands, 300 GHz-3 THz is in the far-infrared (IR) frequency band. While the 300 GHz-3 THz band is part of a broadband, it is at the boundary of the broadband and immediately behind the RF band. Therefore, the 300 GHz-3 THz band is similar to RF. Figure 2 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure. The example of Figure 2 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a wide usable bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth produced by highly directional antennas reduces interference. The small wavelength of THz signals allows a greater number of antenna elements to be integrated into devices and base stations operating in this band. This allows for the use of advanced adaptive array techniques that can overcome range limitations.

[0040] -Large-scale MIMO technology

[0041] -Hologram beam forming (HBF)

[0042] -Optical wireless technology

[0043] -Free Space Optical Transmission Backhaul Network (FSO Backhaul Network)

[0044] -Non-Terrestrial Networks (NTN)

[0045] -Quantum Communication

[0046] -Cell-free Communication

[0047] -Integration of Wireless Information and Power Transmission

[0048] -Integration of Wireless Communication and Sensing

[0049] -Integrated Access and Backhaul Network

[0050] -Big data analysis

[0051] -Reconfigurable Intelligent Surface

[0052] -Metaverse

[0053] -Blockchain

[0054] Unmanned Aerial Vehicles (UAVs): UAVs (Unmanned Aerial Vehicles), or drones, have the potential to become a key element in 6G wireless communications. In most cases, high-speed data wireless connections are provided using UAV technology. BS entities are installed on UAVs to provide cellular connectivity. UAVs possess certain features not found in fixed BS infrastructure, such as easy deployment, strong line-of-sight links, and freedom of controlled mobility. During emergency situations such as natural disasters, deploying terrestrial communication infrastructure is economically unfeasible and sometimes unable to provide services in volatile environments. UAVs can easily handle such situations. UAVs have the potential to become a new paradigm in the field of wireless communications. This technology facilitates the three fundamental requirements of wireless networks: eMBB, URLLC, and mMTC. UAVs can also support various purposes such as improved network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0055] -Autonomous Driving (Self-driving): Perfect autonomous driving requires vehicle-to-vehicle communication to notify each other of dangerous situations, or vehicle-to-vehicle communication with infrastructure such as parking lots and traffic lights to confirm information such as parking location and traffic light change times. V2X (Vehicle-to-Everything), a key element in building autonomous driving infrastructure, is a technology that allows vehicles to communicate and share information with various elements on the road for autonomous driving, including wireless communication between vehicles (V2V, Vehicle-to-Vehicle) and between vehicles and infrastructure (V2I, Vehicle-to-Infrastructure). High-speed transmission and low-latency technology are essential to maximize autonomous driving performance and ensure high safety. Furthermore, autonomous driving will go beyond simply providing warnings and guidance messages to drivers and actively intervene in vehicle operation, directly controlling the vehicle in dangerous situations. This will require a huge amount of information to be transmitted and received, and 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0056] For clarity of explanation, the description focuses on 5G NR, but the technical idea according to an embodiment of the present disclosure is not limited thereto, and various embodiments of the present disclosure may also be applied to 6G communication systems.

[0057] 3 illustrates an NR system architecture according to one embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

[0058] Referring to FIG. 3, a Next Generation Radio Access Network (NG-RAN) may include a base station 20 that provides user plane and control plane protocol termination for a terminal 10. For example, the base station 20 may include a next generation NodeB (gNB) and / or an evolved NodeB (eNB). For example, the terminal 10 may be fixed or mobile, and may be referred to as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, or other terms. For example, a base station is a fixed station that communicates with the terminal 10, and may be referred to as a base transceiver system (BTS), an access point, or other terms.

[0059] The embodiment of Figure 3 illustrates a case where only gNBs are included. Base stations 20 may be connected to each other via an Xn interface. Base stations 20 may be connected to a 5G Core Network (5GC) via an NG interface. More specifically, base stations 20 may be connected to an access and mobility management function (AMF) 30 via an NG-C interface and to a user plane function (UPF) 30 via an NG-U interface.

[0060] The radio interface protocol layers between a terminal and a network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the bottom three layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems. Among these, the physical layer, which belongs to Layer 1, provides an information transfer service using a physical channel, and the Radio Resource Control (RRC) layer, which is located in Layer 3, controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0061] Figure 4 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of Figure 4 can be combined with various embodiments of the present disclosure. Specifically, Figure 4(a) illustrates a user plane radio protocol stack for Uu communications, and Figure 4(b) illustrates a control plane radio protocol stack for Uu communications. Figure 4(c) illustrates a user plane radio protocol stack for SL communications, and Figure 4(d) illustrates a control plane radio protocol stack for SL communications.

[0062] Referring to Figure 4, the physical layer provides information transfer services to higher layers using physical channels. The physical layer is connected to the higher layer, the Medium Access Control (MAC) layer, via transport channels. Data moves between the MAC layer and the physical layer via the transport channels. Transport channels are classified according to how and what characteristics data is transmitted over the radio interface.

[0063] Data is transferred between different physical layers, i.e., between the physical layers of a transmitter and a receiver, via a physical channel, which can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0064] The MAC layer provides services to the higher-level radio link control (RLC) layer via logical channels. The MAC layer provides a mapping function from multiple logical channels to multiple transport channels. The MAC layer also provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. The MAC sublayer provides data transfer services on the logical channels.

[0065] The RLC layer performs concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To guarantee various Quality of Service (QoS) requirements for Radio Bearers (RBs), the RLC layer provides three operation modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction via automatic repeat request (ARQ).

[0066] The Radio Resource Control (RRC) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. RB refers to the logical path provided by layer 1 (physical layer or PHY layer) and layer 2 (MAC layer, RLC layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer) for data transmission between the terminal and the network.

[0067] The functions of the PDCP layer in the user plane include user data transmission, header compression, and ciphering, and the functions of the PDCP layer in the control plane include control plane data transmission and encryption / integrity protection.

[0068] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. The SDAP layer performs mapping between QoS flows and data radio bearers, QoS flow identifier (ID) marking in downlink and uplink packets, etc.

[0069] RB configuration refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service and setting their specific parameters and operation methods. RBs are divided into two types: SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer). SRB is used as a path to transmit RRC messages in the control plane, and DRB is used as a path to transmit user data in the user plane.

[0070] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in an RRC_CONNECTED state; otherwise, it is in an RRC_IDLE state. In the case of NR, an RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network and can release the connection with the base station.

[0071] Downlink transport channels for transmitting data from a network to a terminal include a Broadcast Channel (BCH) for transmitting system information and a Downlink Shared Channel (SCH) for transmitting user traffic and control messages. Traffic or control messages of a downlink multicast or broadcast service can be transmitted via the Downlink SCH or via a separate Multicast Channel (MCH). Meanwhile, uplink transport channels for transmitting data from a terminal to a network include a Random Access Channel (RACH) for transmitting initial control messages and an Uplink Shared Channel (SCH) for transmitting user traffic and control messages.

[0072] Above the transport channels, logical channels that are mapped to the transport channels include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0073] 5 illustrates a radio frame structure for NR according to one embodiment of the present disclosure. The embodiment of FIG. 5 can be combined with various embodiments of the present disclosure.

[0074] Referring to Figure 5, in NR, radio frames can be used for uplink and downlink transmission. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame can include five 1 ms subframes (SF). A subframe can be divided into one or more slots, and the number of slots in a subframe can be determined by the subcarrier spacing (SCS). Each slot can include 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP).

[0075] When a normal CP is used, each slot can contain 14 symbols. When an extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols) or Single Carrier-FDMA (SC-FDMA) symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).

[0076] Table 2 below shows the number of symbols per slot (N) depending on the SCS setting (u) when a normal CP or an extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown below.

[0077] [Table 2]

[0078] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) can be set to be different between multiple cells merged into one terminal, thereby allowing the (absolute time) duration of time resources (e.g., subframes, slots, or TTIs) (commonly referred to as TUs (Time Units) for convenience) consisting of the same number of symbols to be set to be different between the merged cells.

[0079] In NR, multiple numerologies or SCSs can be supported to support various 5G services. For example, if the SCS is 15 kHz, wide areas in traditional cellular bands can be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban areas, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0080] The NR frequency band can be defined as two types of frequency ranges. The two types of frequency ranges are FR1 and FR2. The values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges are shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range" and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0081] [Table 3]

[0082] As mentioned above, the numerical values ​​of the frequency range of the NR system may be changed. For example, FR1 may include the band from 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as communications for vehicles (e.g., autonomous driving).

[0083] [Table 4]

[0084] 6 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0085] 6, a slot includes a plurality of symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, and in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, and in the case of an extended CP, one slot may include 6 symbols.

[0086] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) can be defined as multiple (P)RBs (Physical Resource Blocks) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed via activated BWPs. Each element is called a resource element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0087] The following explains BWP (Bandwidth Part) and carriers.

[0088] A Bandwidth Part (BWP) is a contiguous set of physical resource blocks (PRBs) in a given numerology. PRBs can be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

[0089] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the UE may not monitor downlink radio link quality in DL BWPs other than the active DL BWP on the primary cell (PCell). For example, the UE may not receive a PDCCH, a physical downlink shared channel (PDSCH), or a CSI-RS (reference signal) (excluding RRM) outside the active DL BWP. For example, the UE may not trigger a CSI (Channel State Information) report for an inactive DL BWP. For example, the UE may not transmit a PUCCH (physical uplink control channel) or a PUSCH (physical uplink shared channel) outside the active UL BWP. For example, in the downlink, the initial BWP is given as a contiguous RB set for the remaining minimum system information (RMSI) control resource set (CORESET) (set by the physical broadcast channel (PBCH)). For example, in the uplink, the initial BWP is provided by a system information block (SIB) for the random access procedure. For example, the default BWP is configured by a higher layer. For example, the initial value of the default BWP is the initial DL BWP. To save energy, when the terminal cannot detect DCI for a certain period of time, the terminal can switch the active BWP of the terminal to the default BWP.

[0090] Meanwhile, a BWP can be defined for SL. The same SL BWP can be used for transmission and reception. For example, a transmitting terminal can transmit an SL channel or an SL signal on a specific BWP, and a receiving terminal can receive an SL channel or an SL signal on the specific BWP. In a licensed carrier, an SL BWP can be defined separately from a Uu BWP, and the SL BWP can have separate configuration signaling from the Uu BWP. For example, a terminal can receive a configuration for the SL BWP from a base station / network. For example, a terminal can receive a configuration for the Uu BWP from a base station / network. An SL BWP can be configured (pre-configured) for out-of-coverage NR V2X terminals and RRC_IDLE terminals within a carrier. For a terminal in RRC_CONNECTED mode, at least one SL BWP can be activated within the carrier.

[0091] 7 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 7 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 7, it is assumed that there are three BWPs.

[0092] Referring to Figure 7, CRBs (common resource blocks) are carrier resource blocks numbered from one end of a carrier band to the other end, and PRBs are resource blocks numbered within each BWP. Point A can indicate a common reference point for the resource block grid.

[0093] BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP) For example, point A is the external reference point of the PRB of the carrier to which subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on the carrier) is aligned. For example, the offset is the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth is the number of PRBs in a given numerology.

[0094] The following describes V2X or SL communication.

[0095] The Sidelink Synchronization Signal (SLSS) is a SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may perform initial signal detection and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and S-SSS.

[0096] The PSBCH (Physical Sidelink Broadcast Channel) is a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information includes information related to SLSS, duplex mode (DM), TDDUL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, for evaluating PSBCH performance, in NR V2X, the size of the PSBCH payload is 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0097] The S-PSS, S-SSS, and PSBCH can be included in a block format (e.g., an S-SS (Synchronization Signal) / PSBCH block, hereinafter referred to as an S-SSB (Sidelink-Synchronization Signal Block)) that supports periodic transmission. The S-SSB can have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in a carrier, and the transmission bandwidth is within a (pre-) configured S-BWP (Sidelink Bandwidth Part). For example, the bandwidth of the S-SSB is 11 RBs (Resource Blocks). For example, the PSBCH spans 11 RBs. The frequency location of the S-SSB can be (pre-) configured. Therefore, the terminal does not need to perform hypothesis detection in frequency to find the S-SSB in the carrier.

[0098] 8 illustrates a procedure in which a terminal performs V2X or SL communication according to a transmission mode according to an embodiment of the present disclosure. The embodiment of FIG. 8 can be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be referred to as a mode or a resource allocation mode. Hereinafter, for convenience of description, in LTE, the transmission mode may be referred to as an LTE transmission mode, and in NR, the transmission mode may be referred to as an NR resource allocation mode.

[0099] For example, (a) of Figure 8 illustrates terminal operation associated with LTE transmission mode 1 or LTE transmission mode 3. Alternatively, for example, (a) of Figure 8 illustrates terminal operation associated with NR resource allocation mode 1. For example, LTE transmission mode 1 may be applied to general SL communication, and LTE transmission mode 3 may be applied to V2X communication.

[0100] For example, (b) of FIG. 8 illustrates terminal operation associated with LTE transmission mode 2 or LTE transmission mode 4. Or, for example, (b) of FIG. 8 illustrates terminal operation associated with NR resource allocation mode 2.

[0101] 8(a), in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, a base station may schedule SL resources to be used by a terminal for SL transmission. For example, in step S800, the base station may transmit information related to SL resources and / or information related to UL resources to a first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0102] For example, the first terminal may receive information related to dynamic grant (DG) resources and / or information related to configured grant (CG) resources from the base station. For example, the CG resources may include CG type 1 resources or CG type 2 resources. In this specification, the DG resources may be resources configured / assigned to the first terminal by the base station via downlink control information (DCI). In this specification, the CG resources may be (periodic) resources configured / assigned to the first terminal by the base station via DCI and / or an RRC message. For example, in the case of CG type 1 resources, the base station may send an RRC message including information related to the CG resources to the first terminal. For example, in the case of CG type 2 resources, the base station may send an RRC message including information related to the CG resources to the first terminal, and the base station may send a DCI related to the activation or release of the CG resources to the first terminal.

[0103] In step S810, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal based on the resource scheduling. In step S820, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) associated with the PSCCH to a second terminal. In step S830, the first terminal may receive a PSFCH associated with the PSCCH / PSSCH from a second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S840, the first terminal may transmit / report HARQ feedback information to a base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a preset rule. For example, the DCI may be DCI for SL scheduling. For example, the format of the DCI may be DCI format 3_0 or DCI format 3_1.

[0104] Referring to (b) of FIG. 8, in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, the terminal can determine SL transmission resources within SL resources configured by the base station / network or pre-configured SL resources. For example, the configured SL resources or pre-configured SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can self-select resources within a configured resource pool to perform SL communication. For example, the terminal can perform sensing and resource (re)selection procedures and self-select resources within a selection window. For example, the sensing can be performed in units of subchannels. For example, in step S810, the first terminal that self-selected resources within the resource pool may use the resources to transmit PSCCH (e.g., SCI (Sidelink Control Information) or 1 st In step S820, the first terminal transmits a PSSCH (e.g., a 2-stage SCI) associated with the PSCCH to the second terminal. nd In step S830, the first terminal may receive a PSFCH associated with the PSCCH / PSSCH from the second terminal.

[0105] Referring to (a) or (b) of FIG. 8, for example, the first terminal can transmit an SCI to the second terminal on the PSCCH. Alternatively, for example, the first terminal can transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or PSSCH. In this case, the second terminal can decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, the SCI transmitted on the PSCCH is referred to as a 1 st SCI, 1st SCI, 1 st -stage SCI or 1 st The SCI transmitted on the PSSCH can be referred to as a 2-stage SCI format. nd SCI, 2nd SCI, 2nd -stage SCI or 2 nd -stage SCI format. For example, st -stage SCI formats can include SCI format 1-A, 2 nd -stage SCI formats may include SCI format 2-A and / or SCI format 2-B.

[0106] An example of SCI format 1-A will be described below.

[0107] SCI format 1-A is PSSCH and 2 on PSSCH nd -stage Used for scheduling SCI.

[0108] The following information is transmitted using SCI Format 1-A.

[0109] - Priority - 3 bits

[0110] - Frequency resource allocation - When the value of the upper layer parameter sl-MaxNumPerReserve is set to 2, the ceiling(log2(N SL subChannel (N SL subChannel +1) / 2)) bits; otherwise, if the value of the upper layer parameter sl-MaxNumPerReserve is set to 3, then ceilinglog2(N SL subChannel (N SL subChannel +1)(2N SL subChannel +1) / 6) bits

[0111] - Time resource allocation - 5 bits if the value of the upper layer parameter sl-MaxNumPerReserve is set to 2; otherwise, 9 bits if the value of the upper layer parameter sl-MaxNumPerReserve is set to 3

[0112] -Resource reservation period-ceiling(log2N rsv_period ) bits, where N rsv_period is the number of entries in the upper layer parameter sl-ResourceReservePeriodList if the upper layer parameter sl-MultiReserveResource is set; otherwise, a 0 bit

[0113] -DMRS pattern -ceiling(log2N pattern ) bits, where N pattern is the number of DMRS patterns configured by the higher layer parameter sl-PSSCH-DMRS-TimePatternList

[0114] -2 nd -stage SCI format - 2 bits as defined in Table 5

[0115] - Better_OffsetsIndicator - 2 bits as provided by the upper layer parameter sl-BetaOffsets2ndSCI

[0116] Number of DMRS ports - 1 bit as defined in Table 6

[0117] -Modulation and coding method - 5 bits

[0118] - Additional MCS table indicator - 1 bit if one MCS table is configured by the higher layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by the higher layer parameter sl-Additional-MCS-Table; 0 bit otherwise

[0119] PSFCH overhead indicator - 1 bit if the higher layer parameter sl-PSFCH-Period=2 or 4; 0 bit otherwise

[0120] Reserved Bits - The number of bits determined by the higher layer parameter sl-NumReservedBits, whose value is set to 0.

[0121] [Table 5]

[0122] [Table 6]

[0123] An example of SCI format 2-A will be described below.

[0124] In HARQ operation, if the HARQ-ACK information includes an ACK or a NACK, or if the HARQ-ACK information includes only a NACK, or if there is no feedback of the HARQ-ACK information, SCI format 2-A is used to decode the PSSCH.

[0125] The following information is transmitted via SCI Format 2-A.

[0126] - HARQ process number - 4 bits

[0127] -New Data Indicator - 1 bit

[0128] -redundancy version - 2 bits

[0129] - Source ID - 8 bits

[0130] -Destination ID - 16 bits

[0131] HARQ feedback activation / deactivation indicator - 1 bit

[0132] Cast Type Indicator - 2 bits as defined in Table 7

[0133] - CSI Request - 1 bit

[0134] [Table 7]

[0135] An example of SCI format 2-B will be described below.

[0136] SCI format 2-B is used for decoding the PSSCH and is used with HARQ operation when the HARQ-ACK information includes only NACK or there is no feedback of HARQ-ACK information.

[0137] The following information is transmitted via SCI Format 2-B.

[0138] - HARQ process number - 4 bits

[0139] -New Data Indicator - 1 bit

[0140] -redundancy version - 2 bits

[0141] - Source ID - 8 bits

[0142] -Destination ID - 16 bits

[0143] HARQ feedback activation / deactivation indicator - 1 bit

[0144] - Zone ID - 12 bits

[0145] - Range requirements - 4 bits determined by the higher layer parameter sl-ZoneConfigMCR-Index --

[0146] The following describes power saving.

[0147] Terminal power saving techniques can consider terminal adaptation to traffic and power consumption characteristics, adaptation related to frequency / time changes, adaptation to antennas, adaptation to DRX (discontinuous reception) settings, adaptation to terminal processing capabilities, adaptation to reduce PDCCH monitoring / decoding, power saving signals / channels / procedures to trigger adaptation to terminal power consumption, and reduction of power consumption in RRM measurements.

[0148] The following describes discontinuous reception (DRX), which is one of the technologies that can achieve terminal power saving.

[0149] The procedure for DRX-related terminals can be summarized as shown in Table 8 below.

[0150] [Table 8]

[0151] 10 illustrates an example of a DRX cycle according to one embodiment of the present disclosure. The example of FIG. 10 can be combined with various embodiments of the present disclosure.

[0152] 10, the UE uses DRX in the RRC_IDLE state and the RRC_INACTIVE state to reduce power consumption. If DRX is configured, the UE performs DRX operation according to the DRX configuration information. The UE operating as DRX repeatedly turns on and off the reception operation.

[0153] For example, if DRX is configured, the UE attempts to receive the PDCCH, which is a downlink channel, only within a pre-defined time period and does not attempt to receive the PDCCH within the remaining time period. The time period during which the UE must attempt to receive the PDCCH is called an on-duration, and the on-duration period is defined once per DRX period.

[0154] The terminal can receive DRX setting information from the gNB via RRC signaling and can operate as a DRX by receiving a (long) DRX command MAC CE.

[0155] DRX configuration information is included in MAC-CellGroupConfig, which is an IE used to configure MAC parameters for a cell group, including DRX.

[0156] A DRX command MAC CE or a long DRX command MAC CE is identified by a MAC PDU subheader with an LCID (logical channel ID), which has a fixed size of 0 bits.

[0157] Table 9 below shows example LCID values ​​for DL-SCH.

[0158] [Table 9]

[0159] The PDCCH monitoring operation of the UE is controlled by DRX and Bandwidth Adaptation (BA). On the other hand, if DRX is configured, the UE does not need to continuously monitor the PDCCH. On the other hand, DRX has the following characteristics.

[0160] -on-duration: This is the period during which the UE waits to receive the PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE remains awake and starts an inactivity timer.

[0161] Inactivity timer: This is the time period during which the UE waits for normal PDCCH decoding after the last normal PDCCH decoding and then goes to sleep again if the time period fails. The UE must restart the inactivity timer after a single normal decoding of the PDCCH for the first transmission (i.e., not for a retransmission).

[0162] Retransmission timer: The time interval during which retransmissions are expected.

[0163] - Cycle: Specifies the cyclic repetition of on-duration followed by a possible inactive period.

[0164] The following describes DRX in the MAC layer. Hereinafter, a MAC entity may be expressed as a terminal or a MAC entity of a terminal.

[0165] The MAC entity is configured by RRC with a DRX function that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI (radio network temporary identifier), CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, and TPC-SRS-RNTI. When using DRX operation, the MAC entity must monitor the PDCCH. In the RRC_CONNECTED state, if DRX is configured, the MAC entity can discontinuously monitor the PDCCH using DRX operation. Otherwise, the MAC entity must continuously monitor the PDCCH.

[0166] RRC controls the DRX operation by setting parameters in the DRX configuration information.

[0167] If a DRX cycle is set, the active time includes the following times:

[0168] - the time that the drx-onDurationTimer or the drx-InactivityTimer or the drx-RetransmissionTimerDL or the drx-RetransmissionTimerUL or the ra-ContentionResolutionTimer is running; or

[0169] - the time when a scheduling request is transmitted on the PUCCH and is pending; or

[0170] The time during which a PDCCH indicating a new transmission to the C-RNTI of the MAC entity is not received after successfully receiving a random access response for a random access preamble not selected by the MAC entity among contention-based random access preambles.

[0171] If DRX is configured, the terminal must comply with the following procedures:

[0172] 1> If a MAC PDU is to be transmitted in a configured uplink grant

[0173] 2> Start drx-HARQ-RTT-TimerUL for the corresponding HARQ process immediately after the first reception of the corresponding PUSCH transmission;

[0174] 2> Stop the drx-RetransmissionTimerUL for the corresponding HARQ procedure.

[0175] 1> If drx-HARQ-RTT-TimerDL expires:

[0176] 2> If the data of the corresponding HARQ procedure is not successfully decoded:

[0177] 3> Start the drx-RetransmissionTimerDL for the corresponding HARQ procedure.

[0178] 1> If drx-HARQ-RTT-TimerUL expires:

[0179] 2> Start the drx-RetransmissionTimerUL for the corresponding HARQ procedure.

[0180] 1> If a DRX Command MAC CE or Long DRX Command MAC CE is received:

[0181] 2>Abort drx-onDurationTimer;

[0182] 2>Stop the drx-InactivityTimer.

[0183] 1> If the drx-InactivityTimer expires or a DRX command MAC CE is received:

[0184] 2> If a short DRX period is configured:

[0185] 3>Start or restart the drx-ShortCycleTimer;

[0186] 3> Use a short DRX cycle.

[0187] 2>If not:

[0188] 3> Use a long DRX cycle.

[0189] 1> If drx-ShortCycleTimer expires:

[0190] 2> Use a long DRX cycle.

[0191] 1> If a long DRX command MAC CE is received:

[0192] 2>Abort drx-ShortCycleTimer;

[0193] 2> Use a long DRX cycle.

[0194] 1> if a short DRX cycle is used and [(SFN*10) + subframe number] modulo(drx-ShortCycle) = (drx-Startoffset) modulo(drx-ShortCycle); or

[0195] 1> If a long DRX cycle is used and [(SFN*10)+subframe number] modulo(drx-LongCycle)=drx-Start offset:

[0196] 2>If drx-Slotoffset is set:

[0197] 3> After drx-Slotoffset, start drx-onDurationTimer.

[0198] 2>If not:

[0199] 3>Start drx-onDurationTimer.

[0200] 1> If the MAC entity is within its liveness time:

[0201] 2>Monitoring PDCCH;

[0202] 2> If PDCCH indicates DL transmission or if DL allocation is configured:

[0203] 3> Start drx-HARQ-RTT-TimerDL for the corresponding HARQ procedure immediately after the corresponding PUCCH transmission;

[0204] 3> Stop the drx-RetransmissionTimerDL for the corresponding HARQ procedure.

[0205] 2> If PDCCH indicates UL transmission:

[0206] 3> start drx-HARQ-RTT-TimerUL for the corresponding HARQ procedure immediately after the first reception of the corresponding PUSCH transmission;

[0207] 3> Stop the drx-RetransmissionTimerUL for the corresponding HARQ procedure.

[0208] 2> If the PDCCH indicates a new transmission (UL or DL):

[0209] 3>Start or restart the drx-InactivityTimer.

[0210] 1> Otherwise (i.e. not part of the active time):

[0211] 2>Do not send type-0-triggeredSRS.

[0212] 1> If CQI masking (cqi-Mask) is configured by higher layers:

[0213] 2>If drx-onDurationTimer doesn't work:

[0214] 3> No CSI reporting on PUCCH.

[0215] 1>If not:

[0216] 2> If the MAC entity is not within the liveness period:

[0217] 3> No CSI reporting on PUCCH.

[0218] Regardless of whether the MAC entity monitors the PDCCH or not, the MAC entity transmits HARQ feedback and type-1-triggered SRS when expected.

[0219] If it is not a full PDCCH moment (ie, if the active time starts or expires in the middle of the PDCCH moment), the MAC entity does not need to monitor the PDCCH.

[0220] On the other hand, the conventional NR-U (unlicensed spectrum) supports communication between terminals and base stations in unlicensed spectrum, and Rel-18 is scheduled to support a mechanism that can support communication between sidelink terminals in unlicensed spectrum.

[0221] In this disclosure, a channel can refer to a frequency axis resource set for performing Listen-Before-Talk (LBT). In NR-U, a channel refers to a 20 MHz LBT bandwidth and has the same meaning as an RB set. For example, an RB set is defined in Section 7 of 3GPP TS38.214V17.0.0.

[0222] In this disclosure, CO (channel occupancy) refers to the time / frequency axis resources acquired by a base station or a terminal after successful LBT.

[0223] In this disclosure, COT (channel occupancy time) refers to the time axis resource acquired by a base station or a terminal after successful LBT. It is shared between the base station (or terminal) that acquired CO and the terminal (or base station), which can be called COT sharing. Depending on the initiating device, this can be called gNB-initiated COT or UE-initiated COT.

[0224] In the following, a wireless communication system that supports unlicensed bands (shared spectrum) will be described.

[0225] 11 illustrates an example of a wireless communication system supporting unlicensed spectrum according to an embodiment of the present disclosure. For example, FIG. 11 may include an NR-U (unlicensed spectrum) wireless communication system. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0226] In the following description, a cell operating in a licensed band (hereinafter, L-band) may be defined as an LCell, and a carrier of an LCell may be defined as a (DL / UL / SL)LCC. Also, a cell operating in an unlicensed band (hereinafter, U-band) may be defined as a UCell, and a carrier of a UCell may be defined as a (DL / UL / SL)UCC. A cell's carrier / carrier-frequency refers to the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., CC) is commonly referred to as a cell.

[0227] As shown in (a) of Figure 11, when a terminal and a base station transmit and receive signals via carrier-coupled LCC and UCC, the LCC is set as a PCC (Primary CC) and the UCC is set as an SCC (Secondary CC). As shown in (b) of Figure 11, the terminal and a base station can transmit and receive signals via one UCC or multiple carrier-coupled UCCs. That is, the terminal and a base station can transmit and receive signals via only UCC(s) without an LCC. For standalone operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. are supported in the UCell.

[0228] In the embodiment of Figure 11, the base station can be replaced by a terminal, in which case, for example, PSCCH, PSSCH, PSFCH, S-SSB transmission, etc. are supported in the UCell.

[0229] Unless otherwise stated, the following definitions apply to terms used herein.

[0230] Channel: Consists of consecutive RBs in which a channel access procedure is performed in a shared spectrum, and can also be called a carrier or a part of a carrier.

[0231] -Channel access procedure (CAP): This refers to a procedure for evaluating channel availability based on sensing to determine whether other communication nodes (etc.) can use the channel before transmitting a signal. The basic unit for sensing is T sl The sensing slot has a duration of 9 us. The base station or the terminal senses the channel during the sensing slot, and the power detected for at least 4 us within the sensing slot is equal to or exceeds the energy detection threshold X Thresh If it is smaller, the sensing slot period T sl is considered to be inactive. Otherwise, the sensing slot period T sl =9us is considered busy. CAP can be called LBT (Listen-Before-Talk).

[0232] Channel occupancy: refers to the corresponding transmission(s) on the channel(s) by the base station / terminal after performing the channel access procedure.

[0233] Channel occupancy time (COT): After a base station / terminal performs a channel access procedure, this refers to the total time that the base station / terminal and any base station / terminal(s) sharing the channel occupancy can transmit(s) on the channel. When determining COT, if the transmission gap is 25us or less, the gap period is also counted in COT. COT can be shared for transmission between the base station and corresponding terminal(s).

[0234] DL transmission burst: Defined as a set of transmissions from a base station without gaps exceeding 16 us. Transmissions from a base station separated by gaps exceeding 16 us are considered separate DL transmission bursts. The base station can perform transmissions (etc.) after the gaps without sensing channel availability within the DL transmission burst.

[0235] UL or SL transmission burst: Defined as a set of transmissions from a terminal without a gap of more than 16 us. Transmissions from a terminal separated by a gap of more than 16 us are considered separate UL or SL transmission bursts. The terminal can perform transmission (etc.) after the gap without sensing channel availability within the UL or SL transmission burst.

[0236] Discovery burst: refers to a DL transmission burst containing a set of signals and / or channels bounded within a (time) window and associated duty cycle. In an LTE-based system, a discovery burst includes PSS, SSS, and CRS (cell-specific RS) as base station initiated transmissions, and may further include non-zero power CSI-RS. In an NR-based system, a discovery burst includes at least SS / PBCH blocks as base station initiated transmissions, and may further include a CORESET for a PDCCH scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and / or non-zero power CSI-RS.

[0237] 12 illustrates a method for occupying resources in an unlicensed spectrum according to one embodiment of the present disclosure. The example of FIG. 12 can be combined with various embodiments of the present disclosure.

[0238] Referring to FIG. 12, a communication node (e.g., a base station, a terminal) in an unlicensed band needs to determine whether other communication node(s) can use the channel before transmitting a signal. To this end, the communication node in the unlicensed band can perform a channel access procedure (CAP) to connect to the channel(s) on which transmission(s) will be performed. The channel access procedure can be performed based on sensing. For example, a communication node can first perform carrier sensing (CS) before transmitting a signal to check whether other communication node(s) will transmit a signal. When it is determined that other communication node(s) will not transmit a signal, it is defined that clear channel assessment (CCA) is confirmed. A CCA threshold (e.g., X) that is previously defined or set by an upper layer (e.g., RRC) is used. Thresh ), a communication node can determine the channel state as busy if energy higher than the CCA threshold is detected in the channel, and determine the channel state as idle if not. If the channel state is determined to be idle, the communication node can start transmitting signals in the unlicensed band. CAP can be substituted for LBT.

[0239] Table 10 illustrates the channel access procedures (CAP) supported in NR-U.

[0240] [Table 10]

[0241] Referring to Table 10, LBT types or CAPs for DL / UL / SL transmission are defined. However, Table 10 is merely an example, and new types or CAPs may be defined in a similar manner. For example, Type 1 (also referred to as Cat-4 LBT) may be a random back-off based channel access procedure. For example, in the case of Cat-4, the contention window may change. For example, Type 2 may be performed in the case of COT sharing within COT acquired by a base station or terminal.

[0242] In the following, the LBT-SB (Subband) (or RB set) will be described.

[0243] In a wireless communication system supporting unlicensed bands, a cell (or carrier (e.g., CC)) or BWP configured in a terminal is configured with a wideband having a larger BW (Band Width) than that of existing LTE. However, the BW required for CCA based on independent LBT operation is limited due to regulations, etc. If a sub-band (SB) on which an individual LBT is performed is defined as an LBT-SB, multiple LBT-SBs are included in one wideband cell / BWP. The RB set constituting the LBT-SB is configured via higher layer (e.g., RRC) signaling. Therefore, one cell / BWP includes one or more LBT-SBs based on (i) the BW of the cell / BWP and (ii) RB set allocation information.

[0244] 13 illustrates a case where multiple LBT-SBs are included in the unlicensed spectrum according to one embodiment of the present disclosure. The example of FIG. 13 can be combined with various other examples of the present disclosure.

[0245] Referring to FIG. 13, the BWP of a cell (or carrier) includes multiple LBT-SBs. The LBT-SB has, for example, a 20 MHz bandwidth. The LBT-SB is composed of multiple consecutive (P)RBs in the frequency domain and can be called a (P)RB set. Although not shown, guard bands (GBs) are included between the LBT-SBs. Therefore, the BWP is composed of the following format: {LBT-SB#0(RBset#0)+GB#0+LBT-SB#1(RBset#1+GB#1)+...+LBT-SB#(K-1)(RBset(#K-1))}. For convenience, the LBT-SB / RB index is set / defined to start from a lower frequency band and increase as it moves to a higher frequency band.

[0246] CAPC (Channel Access Priority Class) will be explained below.

[0247] The CAPC of the MAC CE and radio bearer is fixed or configurable to operate in FR1:

[0248] - Padding BSR (Buffer Status Report) and recommended bit rate are fixed as the lowest priority for MAC CE;

[0249] -Fixed as the highest priority for SRB0, SRB1, SRB3 and other MAC CEs;

[0250] Configured by the base station for SRB2 and DRB.

[0251] When selecting a CAPC for a DRB, the base station considers the 5QI of all QoS flows multiplexed into the DRB and considers fairness between other traffic types and transmissions. Table 9 shows which CAPC should be used for a standardized 5QI, i.e., the CAPC to use for a given QoS flow. For standardized 5QI, CAPC is defined as shown in the table below, and for non-standardized 5QI, the CAPC that best matches the QoS characteristics should be used.

[0252] [Table 11]

[0253] A method for transmitting a downlink signal through an unlicensed band will be described below. For example, the method for transmitting a downlink signal through an unlicensed band can be applied to a method for transmitting a sidelink signal through an unlicensed band.

[0254] A base station may perform one of the following channel access procedures (CAP) for downlink signal transmission in the unlicensed spectrum:

[0255] (1) Type 1 Downlink (DL) CAP Method

[0256] In Type 1DL CAP, the length of the time interval spanned by the sensing slots that are sensed in idle before transmission (etc.) is random. Type 1DL CAP can be applied to the following transmissions:

[0257] - a base station initiated transmission (etc.) including (i) a unicast PDSCH with user plane data, or (ii) a unicast PDSCH with user plane data and a unicast PDCCH scheduling user plane data, or

[0258] - Base station initiated transmissions (etc.) that have (i) only a discovery burst or (ii) a discovery burst multiplexed with non-unicast information.

[0259] 14 illustrates a CAP operation for a base station transmitting a downlink signal over an unlicensed spectrum, according to one embodiment of the present disclosure. The embodiment of FIG. 14 can be combined with various embodiments of the present disclosure.

[0260] Referring to FIG. 14, the base station first sets a defer duration T d The channel is sensed to be idle during the sensing slot period, and if the counter N then becomes 0, transmission can be performed (S134). At this time, the counter N is adjusted by sensing the channel during the additional sensing slot period (etc.) according to the following procedure:

[0261] Step 1) (S120) N=N init where N init is 0 to CW p is a random value evenly distributed between . Then go to step 4.

[0262] Step 2) (S140) If N>0 and the base station chooses to decrement the counter, set N=N-1.

[0263] Step 3) (S150) Sense the channel during the additional sensing slot period. If the additional sensing slot period is a pause (Y), proceed to step 4. If not (N), proceed to step 5.

[0264] Step 4) (S130) If N=0 (Y), then end the CAP procedure (S132). Otherwise (N), go to step 2.

[0265] Step 5) (S160) Additional delay period T dIf a busy sensing slot is detected within the additional delay period T d The channel is sensed until all sensing slots in are detected as idle.

[0266] Step 6) (S170) Additional delay period T d If the channel is sensed as idle during all sensing slot periods (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0267] Table 12 shows the m applied to CAP by channel connection priority class. p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes are shown to vary.

[0268] [Table 12]

[0269] Refer to Table 12, which defines the CWS (contention window size) and maximum COT value for each CAPC. For example, T d =T f +m p *T sl It could be.

[0270] Delay period T d is interval T f (16us)+m p T consecutive sensing slot intervals sl (9us) in that order. T f is the sensing slot period T at the start of the 16us period. sl Includes:

[0271] CW min , p <=CW p<=CW max , p CW p is CW p =CW min , p and is updated before step 1 (CW size update) based on HARQ-ACK feedback (e.g., ACK or NACK ratio) for the previous DL burst (e.g., PDSCH). p is determined based on the HARQ-ACK feedback for the previous DL burst. min , p It can be initialized to , increased to the next highest allowed value, or the existing value can be kept as is.

[0272] (2) Type 2 Downlink (DL) CAP Method

[0273] In Type 2DL CAP, the length of the time interval spanned by the sensing slots in which idle sensing is performed before transmission (etc.) is deterministic. Type 2DL CAP is divided into Type 2A / 2B / 2C DL CAP.

[0274] Type 2A DL CAP is applicable to the following transmissions: In Type 2A DL CAP, the base station transmits the data for at least the sensing period T short_dl A transmission can be sent immediately after the channel is sensed as idle for T = 25us. short_dl is interval T f (=16us) and one sensing slot section immediately following it. f includes a sensing slot at the beginning of the interval.

[0275] - a base station initiated transmission (e.g.,) having (i) only a discovery burst, or (ii) a discovery burst multiplexed with non-unicast information, or

[0276] - A base station transmission (etc.) after a 25us gap from a terminal transmission (etc.) within shared channel occupancy.

[0277] Type 2B DL ​​CAP is applicable to transmissions (etc.) performed by the base station after a 16 us gap from a transmission (etc.) by a terminal within the shared channel occupancy time. In Type 2B DL ​​CAP, the base station f A transmission can be sent immediately after the channel is sensed as idle for T = 16us. f includes a sensing slot within the last 9 us of the interval. Type 2C DL CAP is applicable to transmissions (etc.) performed by the base station after a maximum 16 us gap from a transmission (etc.) by the terminal within the shared channel occupancy time. In Type 2C DL CAP, the base station does not sense the channel before performing a transmission.

[0278] A method for transmitting an uplink signal through an unlicensed band will be described below. For example, the method for transmitting an uplink signal through an unlicensed band can be applied to a method for transmitting a sidelink signal through an unlicensed band.

[0279] A terminal performs Type 1 or Type 2 CAP for uplink signal transmission in an unlicensed band. Typically, a terminal can perform a CAP (e.g., Type 1 or Type 2) set by a base station for uplink signal transmission. For example, an UL grant (e.g., DCI format 0_0, 0_1) for scheduling PUSCH transmission includes CAP type indication information for the terminal.

[0280] (1) Type 1 Uplink (UL) CAP Method

[0281] In Type 1 UL CAP, the length of the time interval spanned by the sensing slots that are sensed in idle before transmission (etc.) is random. Type 1 UL CAP can be applied to the next transmission.

[0282] -Scheduled and / or configured PUSCH / SRS transmission (etc.) from the base station

[0283] - PUCCH transmissions (etc.) scheduled and / or configured by the base station

[0284] -RAP (Random Access Procedure) related transmissions (etc.)

[0285] 15 illustrates a Type 1 CAP operation of a terminal for uplink signal transmission according to one embodiment of the present disclosure. The embodiment of FIG. 15 can be combined with various embodiments of the present disclosure.

[0286] Referring to FIG. 15, the terminal first receives a delay period T d The channel is sensed to be idle during the sensing slot period, and if the counter N then becomes 0, transmission can be performed (S234). At this time, the counter N is adjusted by sensing the channel during the additional sensing slot period (etc.) according to the following procedure:

[0287] Step 1) (S220) N=N init where N init is 0 to CW p is a random value evenly distributed between . Then go to step 4.

[0288] Step 2) (S240) If N>0 and the terminal selects to decrement the counter, set N=N-1.

[0289] Step 3) (S250) Sense the channel during the additional sensing slot period. If the additional sensing slot period is a pause (Y), proceed to step 4. If not (N), proceed to step 5.

[0290] Step 4) (S230) If N=0 (Y), end the CAP procedure (S232). Otherwise (N), go to step 2.

[0291] Step 5) (S260) Additional delay period T d If a busy sensing slot is detected within the additional delay period T d Senses the channel until all sensing slots in are detected as idle.

[0292] Step 6) (S270) Additional delay period T d If the channel is sensed to be idle during all sensing slot periods (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0293] Table 13 shows the m applied to CAP by channel connection priority class. p , minimum CW, maximum CW, maximum channel occupancy time (MCOT) and allowed CW sizes vary.

[0294] [Table 13]

[0295] Refer to Table 13, which defines the CWS (contention window size) and maximum COT value for each CAPC. For example, T d =T f +m p *T sl It could be.

[0296] Delay period T d is interval T f (16us)+m p T consecutive sensing slot intervals sl (9us) in that order. T fis the sensing slot period T at the start of the 16us period. sl Includes:

[0297] CW min , p <=CW p <=CW max , p CW p is CW p =CW min , p and is updated before step 1 (CW size update) based on explicit / implicit acknowledgement to previous UL bursts (e.g., PUSCH). p CW based on explicit / implicit acknowledgement of previous UL bursts. min , p It can be initialized to , increased to the next highest allowed value, or the existing value can be kept as is.

[0298] (2) Type 2 Uplink (UL) CAP Method

[0299] In Type 2 UL CAP, the length of the time interval spanned by the sensing slots that sense idle before transmission (etc.) is deterministic. Type 2 UL CAP is classified into Type 2A / 2B / 2C UL CAP. In Type 2A UL CAP, the terminal must sense the sensing interval T short_dl A transmission can be sent immediately after the channel is sensed as idle for T = 25us. short_dl is interval T f (=16us) and one sensing slot section immediately following it. f The sensing slot is included at the beginning of the period. In Type 2B UL CAP, the terminal starts the sensing period T f A transmission can be sent immediately after the channel is sensed as idle for 16us. In Type 2B UL CAP, T fincludes a sensing slot within the last 9 us of the interval. In Type 2C UL CAP, the terminal does not sense the channel before transmitting.

[0300] For example, according to Type 1 LBT-based NR-U operation, a terminal with uplink data to transmit can select a CACP that is mapped to the 5QI of the data, and the terminal can set the parameters of the CACP (e.g., minimum contention window size, maximum contention window size, m p For example, the UE can select a random value between the minimum CW and the maximum CW mapped to CAPC and then select a back-off counter (BC). In this case, for example, BC can be a positive integer less than or equal to the random value. A UE that senses a channel decreases BC by 1 if the channel is idle. When BC becomes zero and the UE enters T d (T d =T f +m p *T sl If a terminal detects that the channel is idle for a period of time, it can occupy the channel and attempt to transmit data. For example, if a terminal detects that the channel is idle for a period of time, it can occupy the channel and attempt to transmit data. sl (=9 usec) is a basic sensing unit or sensing slot, and includes a measurement duration of at least 4 usec. For example, T f (=16usec) 9usec in front is T sl It consists of:

[0301] For example, according to Type 2 LBT-based NR-U operation, a terminal can perform Type 2 LBT (e.g., Type 2A LBT, Type 2B LBT, Type 2C LBT) within the COT to perform data transmission.

[0302] For example, Type 2A (also called Cat-2 LBT (oneshot LBT) or one-shot LBT) can be a 25-usec one-shot LBT. In this case, transmission can begin immediately after idle sensing for at least a 27-usec gap. Type 2A is used to initiate SSB and non-unicast DL information transmission. That is, the terminal can sense the channel for 25 usec within the COT, and if the channel is idle, the terminal can occupy the channel and attempt data transmission.

[0303] For example, Type 2B can be a 16-usec one-shot LBT. In this case, transmission can start immediately after idle sensing for a 16-usec gap. That is, the terminal can sense the channel for 16 usec within the COT, and if the channel is idle, the terminal can occupy the channel and attempt data transmission.

[0304] For example, in the case of Type 2C (also called Cat-1 LBT or No LBT), LTB may not be performed. In this case, transmission may start immediately after a gap of up to 16 usec without sensing the channel before the transmission. The duration of the transmission may be up to 584 usec. The terminal may attempt transmission after 16 usec without sensing, and the terminal may perform transmission for up to 584 usec.

[0305] In a sidelink unlicensed band, a terminal can perform a channel access operation based on Listen Before Talk (LBT). Before connecting to a channel in an unlicensed band, the terminal needs to check whether the access channel is idle (e.g., a state in which the terminal does not occupy the channel, a state in which the terminal is connected to the channel and can transmit data) or busy (e.g., a state in which the channel is occupied and a data transmission / reception operation is performed on the channel, a terminal attempting to access the channel cannot transmit data when the channel is busy). That is, the operation in which the terminal checks whether the channel is idle or busy can be called Clear Channel Assessment (CCA), and the terminal can check whether the channel is idle or busy during the CCA duration.

[0306] Referring to the standard document, some procedures and technical specifications relevant to this disclosure are as follows:

[0307] [Table 14]

[0308] [Table 15]

[0309] [Table 16]

[0310] [Table 17]

[0311] On the other hand, the conventional NR-U (Unlicensed) standard supported communication between terminals and base stations in unlicensed bands, and Rel-18 is expected to support a mechanism to support SL (Sidelink) terminal-to-terminal communication in unlicensed bands.

[0312] For example, the conventional NR-U technology is as follows:

[0313] Channel: A frequency axis resource set on which LBT is performed. In NR-U, this refers to the 20 MHz LBT bandwidth, and has the same meaning as an RB set.

[0314] CO (Channel occupancy): refers to the time / frequency axis resources acquired by a base station or a terminal after successful LBT.

[0315] COT (Channel Occupancy Time): The time axis resource acquired by a base station or terminal after successful LBT. CO can be shared between a base station (or terminal) that has acquired it and a terminal (or base station), and this operation can be referred to as COT sharing. For example, depending on the initiating device, it can be referred to as gNB-initiated COT or terminal (UE)-initiated COT.

[0316] According to one embodiment of the present disclosure, LBT types (or channel access procedures) for DL / UL transmissions are described.

[0317] 1. Type 1 (can be referred to as Cat-4 LBT): Random back-off based channel access procedure

[0318] 1.1.Cat-4: This means that the contention window is variable.

[0319] 2. Type 2: In the case of COT sharing, it can be performed within the COT acquired by the gNB or the terminal.

[0320] 2.1. Type 2A (Cat-2 LBT (One-Shot LBT) or One-Shot LBT): 25usec One-Shot LBT

[0321] 2.1.1. Transmission begins immediately after idle sensing for a minimum 25 usec gap.

[0322] 2.1.2. Used for SSB and non-unicast DL information transmission.

[0323] 2.2. Type 2B (16usec one-shot LBT)

[0324] 2.2.1. Transmission begins immediately after idle sensing for a minimum 16 usec gap.

[0325] 2.3. Type 2C (can be referred to as Cat-1 LBT (LBT not performed) or No LBT)

[0326] 2.3.1. Transmission begins immediately after a gap of up to 16 usec, and the channel is not sensed before transmission.

[0327] 2.3.2. The duration of the transmission is a maximum of 584 usec.

[0328] According to one embodiment of the present disclosure, a channel access priority class (CAPC) is described. For example, CAPC1 is supported for SRB0 / 1 / 3, and the base station can configure which CAPC is supported for SRB2 or DRB. For example, for standardized 5QI, CAPC is defined as shown in the table below, and for non-standardized 5QI, the CAPC that best matches the QoS characteristics should be used.

[0329] Table 18 shows the mapping relationship between CAPC and 5QI.

[0330] [Table 18]

[0331] For example, the contention window size (CWS) and maximum COT value are defined for each CAPC. For example, the formula Td=Tf+mp*Tsl can be established.

[0332] The contents of Table 19 are applicable to DL communications.

[0333] [Table 19]

[0334] The contents of Table 20 are applicable to UL communications.

[0335] [Table 20]

[0336] According to an embodiment of the present disclosure, a terminal in a sidelink unlicensed band can perform a listen-before-talk (LBT)-based channel access operation. Before accessing a channel in an unlicensed band, the terminal may need to check whether the access channel is idle (a state in which the terminal does not occupy the channel, and a state in which the terminal is connected to the channel and can transmit data) or busy (a state in which the channel is occupied and a data transmission / reception operation is being performed on the channel, and a terminal attempting to access the channel cannot transmit data when the channel is busy). In other words, the operation in which the terminal checks whether a channel is idle or busy can be called clear channel assessment (CCA), and the terminal can check whether the channel is idle or busy during the CCA period.

[0337] 16 illustrates contention operations for LBE and FBE channels according to one embodiment of the present disclosure. The embodiment of FIG. 16 can be combined with various embodiments of the present disclosure.

[0338] 16(a) shows a dynamic channel access procedure (load based equipment, LBE). For example, a terminal competes with other unlicensed terminals to immediately occupy a channel immediately after the channel becomes idle, and after occupying the channel, the terminal can transmit data.

[0339] 16(b) shows a semi-static channel access procedure (frame based equipment, FBE). For example, a terminal competes with other unlicensed band terminals at the end of a synchronized frame boundary (or fixed frame period), e.g., at a certain time (or start) before the start of the next FFP, and the terminal can transmit data after occupying the channel within the fixed frame period. Data transmission must be completed before the start of the next FFP. For example, within the FFP, a Type 2 sequence of LBT (which does not perform random backoff-based LBT, but senses the channel for a certain short time and allows data transmission if the channel is idle) can be performed.

[0340] According to one embodiment of the present disclosure, an operation is proposed in which the terminal reports the shared COT information to the base station or the counterpart terminal.

[0341] For example, a terminal that generates a COT can share the COT it has secured with a counterpart terminal. For example, a terminal that generates / secures a COT can transmit the COT it has secured to a counterpart terminal via an SCI, MAC CE, or PC5-RRC message.

[0342] For example, when a terminal transmits its reserved COT via an SCI, it can transmit it to a destination terminal (a pair of L1 source ID and L1 destination ID) associated with a unicast link. Alternatively, for example, a terminal that generates / reserves a COT can transmit its reserved COT to a groupcast / broadcast destination terminal (groupcast / broadcast L1 destination ID).

[0343] For example, when a terminal transmits its reserved COT via MAC CE (e.g., SL COT (Channel Occupancy Time) Information MAC CE), it can be transmitted to a destination terminal (a pair of L1 / L2 source ID and L1 / L2 destination ID) for a unicast link. Alternatively, for example, a terminal that generates / reserves a COT can transmit its reserved COT to a groupcast / broadcast destination terminal (groupcast / broadcast L1 / L2 destination ID).

[0344] For example, a terminal that receives a COT from a terminal that generated the COT can perform a Type 2 LBT operation after the terminal that generated the COT completes transmission within the shared COT. For example, the Type 2 LBT operation can include Type 2A, Type 2B LBT, and Type 2C LBT. For example, according to Type 2A and Type 2B LBT, a terminal can perform a sensing operation and transmit its own SL data within the shared COT if it is determined that the channel is idle for a certain period of time. For example, according to Type 2C LBT, a terminal can immediately transmit SL data without sensing for a certain period of time.

[0345] In an embodiment (or the like) of the present disclosure, if a terminal that receives a COT generated and shared by a COT generating terminal is unable to normally perform SL data transmission using the shared COT, it is proposed to request COT reconfiguration, and the terminal that is requested to reconfigure the COT reconfigures and shares a new COT.

[0346] 17 illustrates an example of operations performed within a Shared COT according to one embodiment of the present disclosure. The example of FIG. 17 can be combined with various examples of the present disclosure.

[0347] 17, a COT initiating terminal generates and shares a COT, and a COT shared terminal can transmit SL data by performing a short LBT within the shared COT. For example, the short LBT refers to a type 2 sequence LBT, and a terminal performing a short LBT can perform sensing for a short period other than a random backoff-based LBT, and can immediately transmit SL data if the channel state is idle.

[0348] In the present disclosure, when a terminal is shared with a COT, the subsequent operation (COT notification) of the terminal that has shared the COT is proposed as follows.

[0349] 1. When the terminal receives (or sets) COT information from its serving base station

[0350] For example, the COT is set for terminal A by its own serving base station. If the COT is set by the serving base station, terminal A can notify (via an SCI, MAC CE, or PC5 RRC message) the COT information to a counterpart terminal B that is connected to terminal A via a unicast setting.

[0351] For example, if the counterpart terminal B (or the serving base station of terminal B) is the terminal that configures its own (terminal A) SL DRX configuration, the counterpart terminal B (or the serving base station of terminal B) can refer to the COT information when aligning the COT with terminal A's SL DRX configuration (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer).

[0352] For example, if terminal B receives COT information from terminal A, terminal B can report the COT information to its (terminal B's) serving base station (terminal B's serving base station that configures the SL DRX configuration of terminal A). For example, the serving base station of terminal B can refer to the COT information to align the received COT with terminal A's SL DRX configuration (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer).

[0353] For example, based on the COT information of the remote terminal that transmitted the COT, the base station or terminal can refer to the COT information not only for alignment between the COT and the SL DRX setting, but also for alignment between the COT and other settings used by terminal A.

[0354] For example, the COT information reported by the terminal (to the base station) includes the COT information as well as L2 source ID and destination ID information, QoS profile information, and / or SL-priority information of the terminal using the COT.

[0355] For example, if terminal A is configured with a COT to be used by itself (terminal A) from a base station (or terminal B), terminal A can notify other counterpart terminals C or D that have established a unicast connection with terminal A of the configured COT information (via an SCI, MAC CE, or PC5 RRC message) so that the counterpart terminal can use its own COT information. For example, a terminal that receives the COT information can perform its own SL-U transmission by referring to the COT information of terminal A. For example, a terminal that receives the COT information may not perform a transmission operation during terminal A's COT. For example, a terminal that receives the COT information can perform an SL data transmission operation by performing a random backoff-based LBT during terminal A's COT. Alternatively, for example, if the terminal that receives the COT information is a terminal that configures the SL DRX configuration of terminal A, the terminal that receives the COT information can configure the SL DRX configuration of terminal A by referring to the COT information.

[0356] 2. When a terminal receives (or is set to receive) COT information from the other terminal (the other terminal that set up the unicast connection)

[0357] For example, terminal A is configured with the COT it (terminal A) uses (for reception) from terminal B, which has established a unicast configuration with terminal A. For example, if terminal A is configured with the COT from terminal B, terminal A can notify its serving base station of the configured COT information (via PUCCH, MAC CE, or RRC message: Sidelink UE Information / UE Assistance Information). For example, the serving base station of terminal A can align the COT with terminal A's SL DRX configuration (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer) and Uu DRX configuration (e.g., DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) by referring to the COT information received from terminal A.

[0358] For example, if terminal A is configured with a COT to be used (for reception) by terminal B, terminal A can notify (via an SCI, MAC CE, or PC5 RRC message) its own COT information (the COT configured by terminal B) to another counterpart terminal C or D that has established a unicast connection with terminal A, thereby allowing the counterpart terminal to use its own COT information. For example, a terminal that receives the COT information can perform its own SL-U transmission by referring to the COT information of terminal A. For example, a terminal that receives the COT information may not perform a transmission operation during the COT of terminal A. For example, a terminal that receives the COT information can perform an SL data transmission operation by performing a random backoff-based LBT during the COT of terminal A. Alternatively, for example, if the terminal that receives the COT information is a terminal that configures the SL DRX configuration of terminal A, the terminal that receives the COT information can configure the SL DRX configuration of terminal A by referring to the COT information.

[0359] For example, the COT information reported by a terminal may include the COT information as well as L2 source ID and destination ID information, QoS profile information, and / or SL-priority information of the terminal using the COT.

[0360] 3. When the terminal receives (or is set) the COT information to be used (for reception) by the serving base station of the other terminal (the terminal that established the unicast connection).

[0361] For example, terminal A receives the COT it uses (for reception) from the serving base station of terminal B (when terminal B is RRC CONNECTED with the serving base station) that has unicast configuration with terminal A. For example, when terminal B is RRC CONNECTED with the serving base station, terminal B can request the base station to configure COT information for terminal A (via PUCCH, MAC CE, Sidelink UE Information, UE Assistance Information, or other RRC message). For example, when terminal B requests COT information for terminal A from the base station, the message it transmits includes a cause (COT request) value for the COT information request and the L2 ID of the terminal using the COT (i.e., the L2 source ID of terminal A, or the L2 source / destination of terminal B, or the L2 source ID and destination ID of terminal B).

[0362] For example, the serving base station of terminal B can configure the COT of terminal A, which has established a unicast configuration with terminal B, and transmit it to terminal B. Terminal B can notify terminal A (via an SCI, MAC CE, or PC5 RRC message) of the COT information used by terminal A received from the serving base station. For example, if terminal A receives the COT it uses from terminal B, terminal A can notify its serving base station of the received COT information (via a PUCCH, MAC CE, or RRC message: Sidelink UE Information / UE Assistance Information). For example, the serving base station of terminal A can align the COT with terminal A's SL DRX configuration (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer) and Uu DRX configuration (e.g., DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) by referring to terminal A's COT information.

[0363] According to an embodiment of the present disclosure, a serving base station of terminal A can allocate a Mode 1 grant (dynamic grant or configured grant) to terminal A by referring to COT information of terminal A. That is, the serving base station can allocate a Mode 1 grant (initial transmission grant or retransmission grant) within the COT interval of terminal A. Alternatively, for example, the serving base station can allocate a Mode 1 grant (initial transmission grant or retransmission grant) outside the COT of terminal A.

[0364] For example, if terminal A is notified by terminal B of the COT it (terminal A) uses (for reception), terminal A can notify (via an SCI, MAC CE, or PC5RRC message) its own COT information (the COT set by terminal B) to another counterpart terminal C or D that has established a unicast setting with terminal A, so that the counterpart terminal can use its own COT information. For example, a terminal that receives the COT information can perform its own SL-U transmission by referring to the COT information of terminal A. For example, a terminal that receives the COT information may not perform a transmission operation during the COT of terminal A. For example, a terminal that receives the COT information can perform an SL data transmission operation by performing an LBT based on a random backoff during the COT of terminal A. Alternatively, for example, if the terminal that receives the COT information is a terminal that sets the SL DRX setting of terminal A, the terminal that receives the COT information can set the SL DRX setting of terminal A by referring to the COT information.

[0365] For example, the COT information reported by a terminal may include the COT information as well as L2 source ID and destination ID information, QoS profile information, and / or SL-priority information of the terminal using the COT.

[0366] 4. When the device sets and uses its own COT

[0367] For example, a terminal can secure a COT to be used by directly generating it and perform SL data transmission within the secured COT in an unlicensed band. In this case, for example, if the terminal is in an RRC CONNECTED state with a serving base station, the terminal can report the COT to be used by the terminal to the base station (via a PUCCH, MAC CE, or RRC message). The serving base station can then finally determine and confirm whether the terminal can use the COT generated and secured by the terminal and notify the terminal (via a PDCCH or RRC message). For example, the terminal can perform SL data transmission without performing a random backoff-based LBT by performing a Type 2 sequence LBT within the secured COT only if the base station permits use of the COT generated and secured by the terminal. Alternatively, for example, the terminal can perform a Type 2 LBT within the secured COT to transmit SL data without confirmation from the base station.

[0368] For example, the COT information reported by a terminal may include the COT information as well as L2 source ID and destination ID information, QoS profile information, and / or SL-priority information of the terminal using the COT.

[0369] 18 illustrates a procedure for a terminal receiving COT sharing information to use COT according to one embodiment of the present disclosure. The embodiment of FIG. 18 can be combined with various embodiments of the present disclosure.

[0370] 18, a COT sharing terminal and a responding terminal are shown. For example, the COT sharing terminal refers to a terminal that acquires (generates and / or receives from a base station) a COT. For example, the responding terminal refers to a terminal that receives COT sharing information.

[0371] In step S1810, the COT sharing terminal may perform PSCCH and / or PSSCH transmission to the responding terminal. In step S1820, the COT sharing terminal may transmit COT sharing information to the responding terminal. For example, step S1810 may be performed before or after step S1820. Alternatively, step S1810 may be performed simultaneously with step S1820. That is, COT sharing information, which is information on the COT interval, is received by the responding terminal through the PSCCH and / or PSSCH transmission. For example, a source / destination ID of the COT sharing terminal is transmitted to the responding terminal through the PSCCH and / or PSSCH transmission.

[0372] In step S1830, the responding terminal may determine whether to use the received COT section for transmitting SL data. For example, if the source ID of the COT sharing terminal and its own destination ID are the same and the destination ID of the COT sharing terminal and its own source ID are the same, the responding terminal may determine to use the COT section.

[0373] In step S1840, the responding terminal may perform channel sensing on the transmission resources within the COT interval. For example, the channel sensing may include a Type 2 LBT operation as described in this disclosure. In this embodiment, it is assumed that the result of the channel sensing is idle.

[0374] In step S1850, the channel sensing result of the responding terminal is idle, so that the responding terminal can transmit SL data to the COT sharing terminal based on the transmission resource.

[0375] 19 illustrates a procedure for a terminal receiving COT sharing information to use COT according to one embodiment of the present disclosure. The embodiment of FIG. 19 can be combined with various embodiments of the present disclosure.

[0376] 19, a COT sharing terminal and a responding terminal are shown. For example, the COT sharing terminal refers to a terminal that acquires (generates and / or receives from a base station) a COT. For example, the responding terminal refers to a terminal that receives COT sharing information.

[0377] In step S1910, the COT sharing terminal may transmit COT sharing information to the responding terminal. For example, the COT sharing information includes the ID(s) of the terminal(s) that can use the COT in the COT sharing information. For example, the ID(s) of the terminal(s) that can use the COT may be a new ID different from the source / destination ID included in the SCI and / or MAC CE. Or, for example, if the COT sharing information is transmitted via a PSCCH and / or PSSCH transmission, the ID(s) of the terminal(s) that can use the COT may be a new ID different from the ID indicated via the source / destination ID field on the SCI.

[0378] In step S1920, the responding terminal may determine whether to use the received COT section for transmitting SL data. For example, the responding terminal may check whether its own ID is included in the ID(s) of the terminal(s) that can use the COT, and may decide to use the COT section if its own ID is included in the ID(s) of the terminal(s) that can use the COT.

[0379] In step S1930, the responding terminal may perform channel sensing on the transmission resources within the COT interval. For example, the channel sensing may include a Type 2 LBT operation as described in this disclosure. In this embodiment, it is assumed that the result of the channel sensing is idle.

[0380] In step S1940, the channel sensing result of the responding terminal is idle, so that the responding terminal can transmit SL data to the COT sharing terminal based on the transmission resource.

[0381] According to an embodiment of the present disclosure, a COT initiator refers to a COT generating terminal and / or a COT sharing terminal. For example, a responding terminal refers to a terminal that acquires information about the COT and uses the COT for SL communication.

[0382] For example, a responding terminal related to a shared COT may be a receiving terminal that is a target of a PSCCH / PSSCH transmission of the COT initiator. For example, when the responding terminal is a receiving terminal that is a target of a PSCCH / PSSCH transmission of the COT initiator, the following cases may occur: i) in the case of a unicast from the COT initiator, the source and destination IDs included in the SCI of the COT initiator are the same as the destination and source IDs of the receiving terminal of the same unicast in the same COT; ii) in the case of a groupcast and broadcast, the destination ID included in the SCI of the COT initiator is the same as the destination ID of the receiving terminal.

[0383] For example, the responding terminal associated with the shared COT may be a terminal identified by an additional ID included in the COT sharing information from the COT initiator if the additional ID in the COT sharing information is further supported for the source and destination ID of the PSCCH / PSSCH transmission.

[0384] According to one embodiment of the present disclosure, the serving base station of a terminal can align the terminal's COT with the terminal's SL DRX settings (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer) and Uu DRX settings (e.g., DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) by referring to the COT information generated by the terminal.

[0385] For example, the serving base station of the terminal can allocate a Mode 1 grant (dynamic grant or configured grant) to the terminal by referring to the COT information of the terminal. That is, the serving base station of the terminal can allocate a Mode 1 grant (initial transmission grant or retransmission grant) within the COT duration of the terminal. Alternatively, the serving base station of the terminal can allocate a Mode 1 grant (initial transmission grant or retransmission grant) outside the COT duration of the terminal.

[0386] The proposal of the present disclosure may be a solution that is applicable not only when a terminal is configured with COT from a base station or a counterpart terminal, but also when a terminal is configured with FBE setting (FFP information, FFP starting offset) information from a base station or a counterpart terminal.

[0387] The SL DRX Configuration referred to in this disclosure may include at least one or more of the following parameters:

[0388] [Table 21]

[0389] The Uu DRX Configuration referred to in this disclosure may include at least one or more of the following parameters:

[0390] [Table 22]

[0391] For example, the following Uu DRX timer mentioned in this disclosure is used for the following purposes:

[0392] drx-HARQ-RTT-Timer SL timer: This timer can indicate an interval during which a transmitting terminal (a terminal supporting Uu DRX operation) performing sidelink communication based on sidelink resource allocation mode 1 does not perform PDCCH (or DCI) monitoring for sidelink mode 1 resource allocation from the base station.

[0393] drx-Retransmission Timer (SL timer): This timer can indicate the interval during which a transmitting terminal (a terminal supporting Uu DRX operation) performing sidelink communication based on sidelink resource allocation mode 1 performs PDCCH (or DCI) monitoring for sidelink mode 1 resource allocation from the base station.

[0394] For example, the following SL DRX timer mentioned in this disclosure is used for the following purposes:

[0395] SL DRX on-duration timer: This can indicate the interval during which a terminal performing SL DRX operation must basically operate during active time to receive the PSCCH / PSSCH of the remote terminal.

[0396] SL DRX inactivity timer: This timer indicates a period for extending the SL DRX on duration, which is a period during which a terminal performing SL DRX operation must operate in an active time to receive the PSCCH / PSSCH of the remote terminal. In other words, the SL DRX on duration timer can be extended by the SL DRX inactivity timer period. In addition, the SL DRX on duration timer can be extended by the SL DRX inactivity timer period when the terminal receives a PSCCH (1 stSCI and 2 nd If the terminal receives a SL DRX inactivity timer, the terminal may extend the SL DRX on duration timer by starting the SL DRX inactivity timer.

[0397] SL DRX HARQ RTT timer: This timer may indicate a period during which a terminal performing an SL DRX operation operates in a sleep mode until it receives a retransmission packet (or a PSSCH assignment) transmitted by a remote terminal. That is, when a terminal starts an SL DRX HARQ RTT timer, the terminal determines that the remote terminal will not transmit an SL retransmission packet to the terminal until the SL DRX HARQ RTT timer expires, and may operate in a sleep mode during the timer. Alternatively, the terminal may not monitor an SL channel / signal transmitted by a transmitting terminal until the remote terminal expires the SL DRX HARQ RTT timer.

[0398] SL DRX retransmission timer: This can indicate an interval during which a terminal performing an SL DRX operation operates in an active time to receive a retransmission packet (or a PSSCH allocation) transmitted by a remote terminal. For example, when the SL DRX HARQ RTT timer expires, the SL DRX retransmission timer is started. During this timer interval, the terminal can monitor reception of a retransmission SL packet (or a PSSCH allocation) transmitted by the remote terminal.

[0399] The applicability and / or related parameters (e.g., thresholds) of (some) proposed methods / rules of the present disclosure are set specifically (or differently or independently) depending on the specific SL-CAPC, SL-LBT type (e.g., Type 1 LBT, Type 2A LBT, Type 2B LBT, Type 2C LBT), whether FBE (Frame Based LBT) is applicable, whether LBE (Load Based LBT) is applicable, etc.

[0400] For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) depending on the resource pool (e.g., resource pool with PSFCH configured, resource pool without PSFCH configured), congestion level, service priority (and / or type), QoS requirement (e.g., delay, reliability) or PQI, traffic type (e.g., (a)periodic generation), SL transmission resource allocation mode (mode 1, mode 2), Tx profile (e.g., Tx profile indicating a service that supports SL DRX operation, Tx profile indicating a service that does not need to support SL DRX operation), etc.

[0401] For example, whether the proposed rules of the present disclosure can be applied (and / or related parameter setting values) depends on whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or not), resource pool, service / packet type (and / or priority), QoS profile or QoS requirement (e.g., URLLC / EMBB traffic, reliability, delay), PQI, PFI, cast type (e.g., unicast, groupcast, broadcast), (resource pool) congestion level (e.g., CBR), SL HARQ feedback method (e.g., NACK-only feedback, ACK / NACK feedback), HARQ feedback enabled MAC PDU (and / or HARQ feedback disabled MAC PDU) transmission, PUCCH-based SL The HARQ feedback reporting operation setting is configured specifically (and / or independently and / or differently) for at least one of the following: whether to configure HARQ feedback reporting operation; if preemption (and / or re-evaluation) is (not) performed (or if resource reselection is based on preemption); (L2 or L1) (source and / or destination) identifier; (L2 or L1) (combination of source hierarchical ID and destination hierarchical ID) identifier; (L2 or L1) (combination of source hierarchical ID and destination hierarchical ID pair and cast type) identifier; direction of source hierarchical ID and destination hierarchical ID pair; PC5 RRC connection / link; if SL DRX is performed; SL mode type (resource allocation mode 1, resource allocation mode 2); (non-)periodic resource reservation; and Tx profile (e.g., a Tx profile indicating a service that supports SL DRX operation, a Tx profile indicating a service that does not need to support SL DRX operation).

[0402] Also, for example, the proposals and proposed rule applicability (and / or associated parameter settings) of this disclosure may also be applied to mmWave SL operation.

[0403] With existing technology, when executing a COT sharing operation, there was an insufficient method for instructing which terminal should use the COT. The wider the COT sharing, the higher the probability of smooth SL communication in unlicensed bands. However, using the existing L2 source / destination ID has the problem that the target of COT sharing is limited to only the terminal receiving the message.

[0404] According to the embodiment of the present disclosure, an additional ID besides the L2 source / destination ID is utilized for the COT sharing operation, thus enabling more terminals to receive COT sharing.

[0405] 20 illustrates a procedure for a first device to perform wireless communication according to one embodiment of the present disclosure. The embodiment of FIG. 20 can be combined with various embodiments of the present disclosure.

[0406] Referring to FIG. 20, in step S2010, a first device may receive, from a second device, COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID). In step S2020, the first device may determine to use the COT interval based on whether the first ID is the same as a second ID of the first device. In step S2030, the first device may perform channel sensing on transmission resources within the COT interval. In step S2040, the first device may perform sidelink (SL) communication based on the channel sensing result.

[0407] For example, the COT sharing information and SCI (sidelink control information) are received by a third device, and based on the third ID included in the SCI and the fourth ID of the third device, it is determined whether the third device will use the COT section.

[0408] For example, based on the result of the channel sensing being idle, the SL communication may be a transmission of SL data.

[0409] For example, based on the channel sensing result being BUSY, the SL communication may be resource reselection or resource dropping.

[0410] For example, the first device can further report the COT sharing information to the first base station; obtain an SL DRX (discontinuous reception) setting set based on the COT interval; and transmit the SL DRX setting to the second device.

[0411] For example, the COT interval is set from a second base station to the second device.

[0412] For example, the SL DRX configuration is set to be aligned with the COT interval.

[0413] For example, the active time of the SL DRX setup is the same as the COT interval.

[0414] For example, the DRX cycle of the SL DRX setting is the same as the COT period.

[0415] The operation of acquiring the SL DRX configuration may include: setting the SL DRX configuration based on the COT interval.

[0416] For example, the SL communication may be performed to the second device.

[0417] For example, the COT sharing information is received via an SCI, a medium access control (MAC) control element (CE), or a PC5 radio resource control (RRC) message.

[0418] For example, the COT sharing information may be received via an SCI, and the first ID may not be included in a source ID field or a destination ID field of the SCI.

[0419] The above-described embodiments can be applied to various devices described below. First, the processor 102 of the first device 100 can control the transceiver 106 to receive COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID), from the second device 200. Then, the processor 102 of the first device 100 can determine to use the COT interval based on the fact that the first ID is the same as the second ID of the first device 100. Then, the processor 102 of the first device 100 can perform channel sensing on transmission resources within the COT interval. Then, the processor 102 of the first device 100 can control the transceiver 106 to perform sidelink (SL) communication based on the result of the channel sensing.

[0420] According to one embodiment of the present disclosure, there is provided a first device that performs wireless communication. For example, the first device may include at least one transceiver; at least one processor; and at least one memory that is executablely connected to the at least one processor and that stores instructions that, when executed by the at least one processor, cause the first device to perform operations. For example, the operations may include: receiving, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determining to use the COT interval based on the first ID being the same as a second ID of the first device; performing channel sensing on transmission resources within the COT interval; and performing sidelink (SL) communication based on a result of the channel sensing.

[0421] For example, the COT sharing information and SCI (sidelink control information) are received by a third device, and based on the third ID included in the SCI and the fourth ID of the third device, it is determined whether the third device will use the COT section.

[0422] For example, based on the result of the channel sensing being idle, the SL communication may be a transmission of SL data.

[0423] For example, based on the channel sensing result being BUSY, the SL communication may be resource reselection or resource dropping.

[0424] For example, the operation may further include: reporting the COT sharing information to the first base station; acquiring an SL DRX (discontinuous reception) setting set based on the COT interval; and transmitting the SL DRX setting to the second device.

[0425] For example, the COT interval is set from a second base station to the second device.

[0426] For example, the SL DRX configuration is set to be aligned with the COT interval.

[0427] For example, the active time of the SL DRX setup is the same as the COT interval.

[0428] For example, the DRX cycle of the SL DRX setting is the same as the COT period.

[0429] The step of obtaining the SL DRX configuration may include the step of: setting the SL DRX configuration based on the COT interval.

[0430] For example, the SL communication may be performed to the second device.

[0431] For example, the COT sharing information is received via an SCI, a medium access control (MAC) control element (CE), or a PC5 radio resource control (RRC) message.

[0432] For example, the COT sharing information may be received via an SCI, and the first ID may not be included in a source ID field or a destination ID field of the SCI.

[0433] According to one embodiment of the present disclosure, there is provided an apparatus configured to control a first terminal. For example, the apparatus may include at least one processor; and at least one memory executablely connected to the at least one processor and storing instructions that cause the first terminal to perform operations based on the instructions being executed by the at least one processor. For example, the operations may include: receiving, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determining to use the COT interval based on the first ID being the same as a second ID of the first device; performing channel sensing on transmission resources within the COT interval; and performing sidelink (SL) communication based on a result of the channel sensing.

[0434] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having stored thereon instructions, which, when executed, may cause a first device to: receive, from a second device, channel occupancy time (COT) sharing information for a COT interval, the COT sharing information including a first identifier (ID); determine to use the COT interval based on the first ID being the same as a second ID of the first device; perform channel sensing on transmission resources within the COT interval; and perform sidelink (SL) communication based on a result of the channel sensing.

[0435] 21 illustrates a procedure for a second device to perform wireless communication according to one embodiment of the present disclosure. The embodiment of FIG. 21 can be combined with various embodiments of the present disclosure.

[0436] 21, in step S2110, a second device may transmit COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID), to a first device. For example, the COT interval may be determined to be used by the first device based on whether the first ID is the same as a second ID of the first device.

[0437] For example, the COT sharing information may be transmitted via sidelink control information (SCI), and the first ID may not be included in a source ID field or a destination ID field of the SCI.

[0438] The above-described embodiment can be applied to various devices described below. First, the processor 202 of the second device 200 can control the transceiver 206 to transmit COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID), to the first device 100. For example, based on the first ID being the same as the second ID of the first device 100, it is determined that the COT interval is to be used by the first device 100.

[0439] According to one embodiment of the present disclosure, there is provided a second device that performs wireless communication. For example, the second device may include at least one transceiver; at least one processor; and at least one memory that is operably connected to the at least one processor and that stores instructions that, when executed by the at least one processor, cause the second device to perform an operation. For example, the operation may include: transmitting, to a first device, channel occupancy time (COT) sharing information for a COT interval, the COT interval including a first identifier (ID), where the COT interval is determined to be used by the first device based on the first ID being the same as a second ID of the first device.

[0440] For example, the COT sharing information may be transmitted via sidelink control information (SCI), and the first ID may not be included in a source ID field or a destination ID field of the SCI.

Claims

1. 1. A method comprising: receiving, by the first device, from the second device via the PSCCH (Physical Sidelink Control Channel), a first SCI for scheduling a PSSCH (Physical Sidelink Shared Channel) and a second SCI (Sidelink Control Information); receiving, by the first device, from the second device via the PSSCH, the second SCI including a source identifier, a destination identifier, channel occupancy time (COT) information, and an additional ID; The method comprises: a step of using the COT information to transmit the control information and data based on the first ID of the first device included in the control information being matched with the additional ID.

2. The method of claim 1 , wherein whether to use the COT information is determined based on whether the first ID of the first device matches the additional ID.

3. The method of claim 1 , wherein the transmission of the control information and the data is performed within a COT period obtained by the COT information.

4. The transmission of the control information and the data is performed based on sensing of channel access using the COT information; The method of claim 1 , wherein a time duration associated with the sensing is deterministic.

5. 2. The method of claim 1, wherein a field associated with the additional ID is different from a field associated with the source ID and a field associated with the destination ID.

6. information relating to a first channel access priority class (CAPC) value is included in the second SCI; 2. The method of claim 1, wherein the transmission of the control information and the data is performed by using the COT information based on a second CAPC value included in the control information being less than or equal to the first CAPC value.

7. transmitting the COT information to a base station (BS); Receiving sidelink (SL) DRX (discontinuous reception) configuration information from the base station; and transmitting the SL DRX configuration information to a third device that receives the control information and the data; The method of claim 1 , wherein the SL DRX setting information is set by the base station and aligns the COT information.

8. The method of claim 7 , wherein the SL DRX setting information aligns the COT information, and the active time of the third device coincides with the COT interval obtained by the COT information.

9. The method of claim 8 , wherein the control information and the data are received from the first device to the third device within the COT interval that overlaps the active time.

10. 9. The method of claim 8, wherein the SL DRX configuration information includes at least one of an interval related to an SL DRX onduration timer, an interval related to an SL DRX inactivity timer, an interval related to an SL DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer, or an interval related to an SL DRX retransmission timer.

11. 11. The method of claim 10, wherein the active time includes at least one of an interval associated with the SL DRX on-duration timer, an interval associated with the SL DRX inactivity timer, an interval associated with the SL DRX HARQ RTT timer, or an interval associated with an SL DRX retransmission timer.

12. At least one of the first SCI or the second SCI is transmitted from the second device to the first device based on at least one of a first unicast, a first groupcast, or a first broadcast; The method of claim 1 , wherein the transmission of the control information and the data is performed based on at least one of a second unicast, a second groupcast, or a second broadcast.

13. The method of claim 1 , wherein the additional ID includes at least one of a source ID different from the source ID included in the second SCI, or a destination ID different from the destination ID included in the second SCI.

14. a first device configured to perform wireless communication, at least one transceiver; at least one processor; and at least one memory; the at least one memory is coupled to the at least one processor and stores instructions that, when executed by the at least one processor, cause an operation to be performed; The operation is receiving, from a second device, a first SCI for scheduling a Physical Sidelink Shared Channel (PSSCH) and a second SCI (Sidelink Control Information) via a Physical Sidelink Control Channel (PSCCH); receiving a second SCI from the second device via the PSSCH, the second SCI including a source identifier, a destination identifier, channel occupancy time (COT) information, and an additional ID; A first device comprising: a step of using the COT information to transmit the control information and data based on the first ID of the first device included in the control information being matched with the additional ID.

15. 1. A device configured to control a first device and to perform wireless communication, comprising: at least one processor; and at least one memory; the at least one memory is coupled to the at least one processor and stores instructions that, when executed by the at least one processor, cause an operation to be performed; The operation is receiving, from a second device, a first SCI for scheduling a Physical Sidelink Shared Channel (PSSCH) and a second SCI (Sidelink Control Information) via a Physical Sidelink Control Channel (PSCCH); receiving a second SCI from the second device via the PSSCH, the second SCI including a source identifier, a destination identifier, channel occupancy time (COT) information, and an additional ID; The device comprises: a step of using the COT information to transmit the control information and data based on the first ID of the first device included in the control information being matched with the additional ID.

Images