Method and apparatus for operating terminal reporting during LBT failure in sl-u

Abstract

A method of performing wireless communication by a first device and a device for supporting the same are provided. The method may comprise the steps of: acquiring information related to a plurality of resource block (RB) sets; performing a listen before talk (LBT); and transmitting LBT failure report information to the second device based on the LBT failure with respect to the first RB set.

Description

Technical Field

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

[0002] Sidelink (SL) refers to a communication method in which a direct link is configured between user equipment (UE) to directly exchange voice or data between user equipment without passing through a base station (BS). SL is being considered as a solution to the burden on base stations caused by the rapid increase in data traffic. V2X (Vehicle to Everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and objects equipped with infrastructure through wired / 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 through the PC5 interface and / or the Uu interface.

[0003] In addition, since a wider range of communication devices require greater communication capacity, the demand for enhanced mobile broadband communications compared to existing radio access technologies (RATs) is rising. Therefore, services and user equipment that are sensitive to reliability and latency have been discussed. In addition, next-generation radio access technologies based on enhanced mobile broadband communications, massive machine type communications (MTC), ultra-reliable low-latency communications (URLLC), etc. may be referred to as new radio access technologies (RATs) or new radios (NRs). Summary of the invention

[0004] Technical Solution

[0005] In one embodiment, a method for performing wireless communication by a first device is provided. The method may include: obtaining information related to a plurality of resource block (RB) sets; performing listen before talk (LBT); and sending first LBT failure report information to a second device based on a failure of LBT for a first RB set.

[0006] In one embodiment, a first device configured to perform wireless communication is provided. The first device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the first device to perform operations including the following items: obtaining information related to multiple resource block (RB) sets; performing listen before talk (LBT); based on the failure of LBT for the first RB set, sending first LBT failure report information to the second device.

[0007] In one embodiment, a processing device configured to control a first device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the first device to perform operations including the following items: obtaining information related to multiple resource block (RB) sets; performing listen before talk (LBT); based on the failure of LBT for the first RB set, sending first LBT failure report information to the second device.

[0008] In one embodiment, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, upon being executed, cause a first device to perform operations including: obtaining information related to a plurality of resource block (RB) sets; performing listen before talk (LBT); and, upon failure of LBT for a first RB set, sending first LBT failure report information to a second device. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A communication structure that may be provided in a 6G system according to an embodiment of the present disclosure is shown.

[0010] Figure 2 The electromagnetic spectrum is shown according to one embodiment of the present disclosure.

[0011] Figure 3 The structure of the NR system according to an embodiment of the present disclosure is shown.

[0012] Figure 4 A radio protocol architecture according to an embodiment of the present disclosure is shown.

[0013] Figure 5 The structure of a radio frame of NR according to an embodiment of the present disclosure is shown.

[0014] Figure 6 The time slot structure of the NR frame according to an embodiment of the present disclosure is shown.

[0015] Figure 7 An example of a BWP according to an embodiment of the present disclosure is shown.

[0016] Figure 8 A process in which a UE according to an embodiment of the present disclosure performs V2X or SL communication according to a transmission mode is shown.

[0017] Fig. 9 Three broadcast types according to embodiments of the present disclosure are shown.

[0018] Fig.10Interleaving RBs according to an embodiment of the present disclosure is shown.

[0019] Fig.11 An example of a wireless communication system supporting a license-free band according to an embodiment of the present disclosure is shown.

[0020] Fig.12 A method for occupying resources in an unlicensed frequency band according to an embodiment of the present disclosure is shown.

[0021] Fig.13 A case where a plurality of LBT-SBs are included in a license-free band according to an embodiment of the present disclosure is shown.

[0022] Fig.14 A CAP operation performed by a base station to transmit a downlink signal through an unlicensed frequency band according to an embodiment of the present disclosure is shown.

[0023] Fig.15 A Type 1 CAP operation performed by a UE to transmit an uplink signal according to an embodiment of the present disclosure is shown.

[0024] Fig.16 The channel access process according to the embodiment of the present disclosure is shown.

[0025] Fig.17 The operation of a UE sending an LBT failure report message to a counterpart UE based on an embodiment of the present disclosure is shown.

[0026] Fig.18 Operations related to PSFCH transmission failure of UE due to LBT failure according to an embodiment of the present disclosure are shown.

[0027] Fig.19 A process in which a first device performs wireless communication according to an embodiment of the present disclosure is shown.

[0028] Fig. 20 A process of a second device performing wireless communication according to an embodiment of the present disclosure is shown.

[0029] Fig.21 A communication system 1 according to an embodiment of the present disclosure is shown.

[0030] Fig. 22 A wireless device according to an embodiment of the present disclosure is shown.

[0031] Fig.23 A signal processing circuit for transmitting a signal according to an embodiment of the present disclosure is shown.

[0032] Fig.24 Another example of a wireless device according to an embodiment of the present disclosure is shown.

[0033] Fig.25 A handheld device according to an embodiment of the present disclosure is shown.

[0034] Fig.26 A vehicle or autonomous vehicle according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0035] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, in the present disclosure, "A or B" may be interpreted as "A and / or B". For example, in the present disclosure, "A, B or C" may mean "only A", "only B", "only C", or "any combination of A, B, C".

[0036] A slash ( / ) or a comma used in the present disclosure may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0037] In the present disclosure, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, in the present disclosure, the expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as "at least one of A and B".

[0038] In addition, in the present disclosure, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B and / or C" may mean "at least one of A, B, and C".

[0039] In addition, brackets used in the present disclosure may mean "for example". Specifically, when indicated as "control information (PDCCH)", this may mean proposing "PDCCH" as an example of "control information". In other words, the "control information" of the present disclosure is not limited to "PDCCH", and "PDDCH" may be proposed as an example of "control information". Specifically, when indicated as "control information (i.e., PDCCH)", this may also mean proposing "PDCCH" as an example of "control information".

[0040] In the following description, "when, if, or in the event of" may be replaced with "based on".

[0041] The technical features respectively described in a pair of drawings in the present disclosure may be implemented separately or simultaneously.

[0042] In the present disclosure, the high-level parameters may be parameters configured, preconfigured, or predefined for the UE. For example, the base station or the network may send the high-level parameters to the UE. For example, the high-level parameters may be sent via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0043] The techniques described below 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), single carrier frequency division multiple access (SC-FDMA), etc. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA-2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented using radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), etc. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility for systems based on IEEE 802.16e. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in the downlink and SC-FDMA in the uplink. LTE-Advanced (LTE-A) is an evolution of LTE.

[0044] 5G NR is a subsequent technology of LTE-A corresponding to a new mobile communication system with high performance, low latency, high availability, etc. 5G NR can use all available spectrum resources including low frequency bands less than 1 GHz, intermediate frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) above 24 GHz.

[0045] The 6G (wireless communication) system aims at (i) very high data rate per device, (ii) very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) lower energy consumption for battery-free IoT devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be embodied in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can meet the requirements shown in Table 1 below. In other words, Table 1 is an example of the requirements of the 6G system.

[0046] [Table 1]

[0047] Peak data rate per device 1Tbps E2E Latency 1ms Maximum spectral efficiency 100bps / Hz Mobility support Up to 1000km / hr Satellite Integration completely AI completely Autonomous Vehicles completely XR completely Tactile communication completely

[0048] The 6G system can have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low-latency communication), 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.

[0049] Figure 1 A communication structure that may be provided in a 6G system according to an embodiment of the present disclosure is shown. Figure 1 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0050] -6G systems are expected to have 50 times higher simultaneous radio connectivity than 5G radio systems. URLLC (a key feature of 5G) will become a more dominant technology in 6G communications by providing end-to-end latency of less than 1ms. In 6G systems, volume spectral efficiency will be better as opposed to area spectral efficiency which is often used today. 6G systems will be able to provide very long battery life and advanced battery technology for energy harvesting, so in 6G systems, mobile devices will not need to be charged separately. In 6G, new network features may be as follows.

[0051] -Satellite integrated network: In order to provide global mobile groups, 6G is expected to be integrated with satellites. Integrating terrestrial, satellite, and airborne networks into a single wireless communication system is important for 6G.

[0052] -Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, and wireless evolution will be updated from "connecting things" to "connected intelligence." AI can be applied to every step of the communication process (or every step of signal processing, as will be described later).

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

[0054] -Ubiquitous Super 3D Connectivity: Super 3D connectivity will be generated from 6G ubiquitous to access networks and core network functions on drones and very low Earth orbit satellites.

[0055] Given the above new network characteristics of 6G, some common requirements can be as follows

[0056] - Small cell network: The idea of ​​small cell network is introduced in cellular systems to improve the received signal quality due to improved processing throughput, energy efficiency and spectrum efficiency. Therefore, small cell network is an essential feature of communication systems through 5G and beyond 5G (5GB). Therefore, 6G communication systems will also adopt the characteristics of small cell network.

[0057] -Ultra-dense heterogeneous network: Ultra-dense heterogeneous network will be another important feature of 6G communication system. Multi-layer network composed of heterogeneous networks will improve the overall QoS and reduce costs.

[0058] - High Capacity Backhaul: Backhaul connectivity is characterized by a high capacity backhaul network to support a large volume of traffic. High-speed optical fiber and free space optics (FSO) systems can be possible solutions to this problem.

[0059] - Radar technology integrated with mobile technology: High-precision positioning (or location-based services) through communication is one of the characteristics of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0060] -Software and virtualization: Software and virtualization are two important features essential to the design process in 5Gb networks to ensure flexibility, reconfigurability and programmability. In addition, billions of devices can be shared on a shared physical infrastructure.

[0061] The following describes the core implementation technologies for 6G systems.

[0062] -Artificial Intelligence: The most important and latest technology that will be introduced in 6G systems is AI. 4G systems do not involve AI. 5G systems will support partial or very limited AI. However, 6G systems will be fully AI-enabled for automation. In 6G, advances in machine learning will create more intelligent networks for real-time communications. The introduction of AI in telecommunications can simplify and improve real-time data transmission. AI can use many analyses to determine the way to perform complex target operations, which means that AI can improve efficiency and reduce processing delays. Time-consuming tasks such as switching, network selection, and resource scheduling can be completed instantly by using AI. AI can also play an important role in M2M, machine-to-man, and man-to-machine communications. In addition, AI can become a fast communication in brain-computer interfaces (BCI). AI-based communication systems can be supported by metamaterials, smart structures, smart networks, smart devices, smart cognitive radios, self-sustaining wireless networks, and machine learning.

[0063] -THz communication (THz communication): The data rate can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced massive MIMO technology. THz waves (also called sub-millimeter radiation) refer to the frequency band between 0.1THz and 10THz, where the corresponding wavelength is generally in the range of 0.03mm to 3mm. The 100GHz-300GHz frequency band range (sub-THz band) is considered to be the main part of the THz band for cellular communication. Adding the sub-THz band to the millimeter wave band increases the capacity of 6G cellular communication. 300GHz-3 THz in the defined THz band is in the far infrared (IR) band. The 300GHz-3 THz band is part of the optical band, but it is on the boundary of the optical band, just behind the RF band. Therefore, the 300GHz-3 THz band exhibits similarities with RF. Figure 2 The electromagnetic spectrum is shown according to one embodiment of the present disclosure. Figure 2 The embodiments of can be combined with various embodiments of the present disclosure. Key characteristics of THz communication include (i) widely available bandwidth supporting very high data rates, and (ii) high path loss at high frequencies (for which highly directional antennas are indispensable). The narrow beamwidth produced by highly directional antennas reduces interference. The small wavelength of THz signals allows a larger number of antenna elements to be integrated into devices and BSs operating in this frequency band. This enables the use of advanced adaptive array techniques that can overcome range limitations.

[0064] - Massive MIMO

[0065] -Holographic Beamforming (HBF)

[0066] -Optical wireless technology

[0067] -FSO backhaul network

[0068] -Non-Terrestrial Network (NTN)

[0069] -Quantum communication

[0070] - No cell communication

[0071] -Integration of wireless information and power transmission

[0072] -Integration of wireless communication and sensing

[0073] -Integrated access and backhaul network

[0074] -Big Data Analysis

[0075] - Reconfigurable smart surfaces

[0076] -Metaverse

[0077] -Blockchain

[0078] -UAV, Unmanned Aerial Vehicle: Unmanned Aerial Vehicle (UAV) or drone will be an important part of 6G wireless communications. In most cases, high-speed data wireless connectivity is provided using UAV technology. The BS entity is installed on the UAV to provide cellular connectivity. UAV has specific features not found in fixed BS infrastructure (e.g., easy deployment, strong line-of-sight link, and freedom of controlled mobility). During emergencies such as natural disasters, the deployment of terrestrial communication infrastructure is economically infeasible and sometimes cannot provide services in volatile environments. UAV can easily handle these situations. UAV will be a new paradigm in wireless communications. The technology contributes to the three basic requirements of wireless networks: eMBB, URLLC, and mMTC. UAV can also support many other purposes such as enhanced network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, accident monitoring, etc. Therefore, UAV technology is considered to be one of the most important technologies for 6G communications.

[0079] -Autonomous driving, automated driving: For perfect autonomous driving, vehicles must communicate with each other to notify each other of dangerous situations, or communicate with infrastructure such as parking lots and traffic lights to check information such as the location of parking information and signal change time. Vehicle-to-Everything (V2X), a key element in building autonomous driving infrastructure, is a technology that allows vehicles to communicate with various elements on the road and share information in order to perform autonomous driving (e.g., vehicle-to-vehicle (V2V) wireless communication and vehicle-to-infrastructure (V2I) wireless communication). In order to maximize the performance of autonomous driving and ensure high safety, fast transmission speeds and low-latency technologies are necessary. In addition, in the future, autonomous driving will go beyond delivering warning or guidance messages to the driver to actively intervene in vehicle operations and directly control the vehicle in dangerous situations, so the amount of information that needs to be sent and received will be large, and 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0080] For the sake of clarity, the description focuses on 5G NR, but the technical concept of one embodiment of the present disclosure is not limited thereto. Various embodiments of the present disclosure may also be applicable to 6G communication systems.

[0081] Figure 3 The structure of the NR system based on the embodiment of the present disclosure is shown. Figure 3 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0082] Reference Figure 3, the next generation radio access network (NG-RAN) may include a BS 20 that provides user plane and control plane protocol terminations to the UE 10. For example, the BS 20 may include a next generation Node B (gNB) and / or an evolved Node B (eNB). For example, the UE 10 may be fixed or mobile and may be referred to as other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. For example, the BS may be referred to as a fixed station that communicates with the UE 10 and may be referred to as other terms such as a base transceiver system (BTS), an access point (AP), etc.

[0083] Figure 3 The embodiment of the present invention illustrates a case where only gNB is included. BS20 may be connected to each other via an Xn interface. BS20 may be connected to each other via a fifth generation (5G) core network (5GC) and an NG interface. More specifically, BS20 may be connected to an access and mobility management function (AMF) 30 via an NG-C interface, and may be connected to a user plane function (UPF) 30 via an NG-U interface.

[0084] The radio interface protocol layer between the UE and the network can be classified into the first layer (L1), the second layer (L2), and the third layer (L3) based on the lower three layers of the open system interconnection (OSI) model known in the communication system. Among them, the physical (PHY) layer belonging to the first layer provides an information transmission service using a physical channel, and the radio resource control (RRC) layer located at the third layer controls the radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS layer.

[0085] Figure 4 A radio protocol architecture according to an embodiment of the present disclosure is shown. Figure 4 The embodiments of can be combined with various embodiments of the present disclosure. Specifically, Figure 4 (a) in FIG. 1 shows a radio protocol stack for a user plane of Uu communication, and Figure 4 (b) in FIG. 5 shows the radio protocol stack of the control plane for Uu communication. Figure 4 (c) in FIG. 1 shows a radio protocol stack of a user plane for SL communication, and Figure 4 (d) in FIG. 5 shows the radio protocol stack of the control plane for SL communication.

[0086] Reference Figure 4, the physical layer provides information transfer services to the upper layer through the physical channel. The physical layer is connected to the medium access control (MAC) layer, which is the upper layer of the physical layer, through the transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how the data is transmitted through the radio interface and what characteristics of the data it transmits.

[0087] Data is transmitted through a physical channel between different physical layers (ie, a PHY layer of a transmitter and a PHY layer of a receiver). The physical channel may be modulated using an Orthogonal Frequency Division Multiplexing (OFDM) scheme, and uses time and frequency as radio resources.

[0088] The MAC layer provides services to the Radio Link Control (RLC) layer via logical channels, and the RLC layer is a higher layer of the MAC layer. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transmission services through logical channels.

[0089] The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Units (RLC SDUs). In order to ensure different Quality of Service (QoS) required by Radio Bearers (RBs), the RLC layer provides three types of operation modes, namely, Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through Automatic Repeat Request (ARQ).

[0090] The Radio Resource Control (RRC) layer is defined only in the control plane. The RRC layer is used to control logical channels, transport channels, and physical channels associated with the configuration, reconfiguration, and release of RBs. RBs are logical paths for data transmission between UEs and networks provided by the first layer (i.e., the physical layer or PHY layer) and the second layer (i.e., the MAC layer, the RLC layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer).

[0091] The functions of the Packet Data Convergence Protocol (PDCP) in the user plane include transmission, header compression and encryption of user data. The functions of the Packet Data Convergence Protocol (PDCP) in the control plane include transmission and encryption / integrity protection of control plane data.

[0092] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. The SDAP layer performs mapping between Quality of Service (QoS) flows and Data Radio Bearers (DRBs) and QoS Flow ID (QFI) marking in both DL and UL packets.

[0093] Configuration of RB means a process for specifying radio protocol layers and channel attributes to provide a specific service and for determining corresponding detailed parameters and operation methods. RBs can then be classified into two types, namely, signaling radio bearers (SRBs) and data radio bearers (DRBs). SRBs are used as a path for sending RRC messages in the control plane, and DRBs are used as a path for sending user data in the user plane.

[0094] When the RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC connected (RRC_CONNECTED) state, otherwise the UE can be in the RRC idle (RRC_IDLE) state. In the case of NR, the RRC inactive (RRC_INACTRIVE) state is additionally defined, and the UE in the RRC_INACTRIVE state can maintain the connection with the core network and release its connection with the BS.

[0095] The downlink transmission channels for sending (or transmitting) data from the network to the UE include a broadcast channel (BCH) for sending system information and a downlink shared channel (SCH) for sending other user services or control messages. The services or control messages of downlink multicast or broadcast services can be sent via the downlink SCH or can be sent via a separate downlink multicast channel (MCH). In addition, the uplink transmission channels for sending (or transmitting) data from the UE to the network include a random access channel (RACH) for sending initial control messages and an uplink shared channel (SCH) for sending other user services or control messages.

[0096] Examples of logical channels belonging to a higher layer of a transport channel and mapped to a transport channel may include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc.

[0097] Figure 5 The structure of a radio frame of NR according to an embodiment of the present disclosure is shown. Figure 5 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0098] Reference Figure 5 In NR, a radio frame can be used to perform uplink and downlink transmissions. The length of a radio frame is 10ms and can be defined as consisting of two half frames (HF). A half frame can include five 1ms subframes (SF). A subframe (SF) can be divided into one or more time slots, and the number of time slots within a subframe can be determined according to the subcarrier spacing (SCS). Each time slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0099] When a normal CP is used, each time slot may include 14 symbols. When an extended CP is used, each time slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or a CP-OFDM symbol) and a single carrier-FDMA (SC-FDMA) symbol (or a discrete Fourier transform spread OFDM (DFT-s-OFDM) symbol).

[0100] Table 2 below shows the number of symbols per slot (N) according to the SCS configuration (u) when using the normal CP or the extended CP. slot symb ), the number of time slots per frame (N frame,μ slot ) and the number of time slots per subframe (N subframe,μ slot ).

[0101] [Table 2]

[0102]

[0103] In the NR system, OFDM (A) parameter sets (e.g., SCS, CP length, etc.) between multiple cells integrated into one UE may be configured differently. Therefore, the (absolute time) duration (or interval) of a time resource (e.g., a subframe, a time slot, or a TTI) (collectively referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently in the integrated cells.

[0104] In NR, multiple parameter sets or SCSs can be supported to support various 5G services. For example, with an SCS of 15kHz, a wide range of traditional cellular bands can be supported, and with an SCS of 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidths can be supported. With an SCS of 60kHz or higher, bandwidths greater than 24.25GHz can be used to overcome phase noise.

[0105] The NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values ​​of the frequency ranges may be changed (or varied), for example, the two different types of frequency ranges may be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 may mean "a range below 6 GHz", and FR2 may mean "a range above 6 GHz", and may also be referred to as millimeter wave (mmW).

[0106] [Table 3]

[0107] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 450MHz–6000MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0108] As described above, the value of the frequency range in the NR system may be changed (or varied). For example, as shown in Table 4 below, FR1 may include a bandwidth in the range of 410 MHz to 7125 MHz. More specifically, FR1 may include frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) and higher. For example, the frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) and higher included in FR1 may include unlicensed frequency bands. Unlicensed frequency bands may be used for various purposes, for example, unlicensed frequency bands are used for vehicle-specific communications (e.g., autonomous driving).

[0109] [Table 4]

[0110] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0111] Figure 6 The structure of the time slot of the NR frame based on the embodiment of the present disclosure is shown. Figure 6 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0112] Reference Figure 6 , a time slot includes multiple symbols in the time domain. For example, in the case of normal CP, one time slot may include 14 symbols. However, in the case of extended CP, one time slot may include 12 symbols. Alternatively, in the case of normal CP, one time slot may include 7 symbols. However, in the case of extended CP, one time slot may include 6 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A bandwidth part (BWP) can be defined as a plurality of consecutive (physical) resource blocks ((P)RBs) in the frequency domain, and a BWP may correspond to a parameter set (e.g., SCS, CP length, etc.).

[0113] A carrier may include a maximum of N BWPs (eg, 5 BWPs). Data communication may be performed via the activated BWPs. Each element may be referred to as a resource element (RE) in a resource grid, and one complex symbol may be mapped to each element.

[0114] Hereinafter, the bandwidth part (BWP) and the carrier will be described in detail.

[0115] A BWP may be a contiguous set of physical resource blocks (PRBs) within a given parameter set. A PRB may be selected from a contiguous set of common resource blocks (CRBs) for a given parameter set on a given carrier.

[0116] For example, the BWP may be at least any one of an active BWP, an initial BWP, and / or a default BWP. For example, the UE may not monitor the downlink radio link quality in a DL BWP other than an activated DL BWP on a primary cell (PCell). For example, the UE may not receive a PDCCH, a physical downlink shared channel (PDSCH), or a channel state information-reference signal (CSI-RS) (excluding RRM) other than an activated DL BWP. For example, the UE may not trigger a channel state information (CSI) report for an unactivated DL BWP. For example, the UE may not send a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) other than an activated UL BWP. For example, in the case of a downlink, the initial BWP may be given as a set of contiguous RBs for a remaining minimum system information (RMSI) control resource set (CORESET) (configured by a physical broadcast channel (PBCH)). For example, in the case of an uplink, the initial BWP may be given by a system information block (SIB) for a random access procedure. For example, a default BWP may be configured by a higher layer. For example, the initial value of the default BWP may be the initial DL BWP.To save energy, if the UE cannot detect downlink control information (DCI) during a specified period, the UE may switch the active BWP of the UE to the default BWP.

[0117] In addition, a BWP can be defined for SL. The same SL BWP can be used in transmission and reception. For example, a transmitting UE can send a SL channel or a SL signal on a specific BWP, and a receiving UE can receive a SL channel or a SL signal on a specific BWP. In a licensed carrier, the SL BWP can be defined separately from the Uu BWP, and the SL BWP can have configuration signaling separate from the Uu BWP. For example, the UE can receive a configuration for the SL BWP from the BS / network. For example, the UE can receive a configuration for the Uu BWP from the BS / network. SLBWP is (pre-)configured in the carrier for out-of-coverage NR V2X UEs and RRC_IDLE UEs. For UEs in RRC_CONNECTED mode, at least one SL BWP can be activated in the carrier.

[0118] Figure 7 An example of a BWP according to an embodiment of the present disclosure is shown. Figure 7 The embodiments of can be combined with various embodiments of the present disclosure. Figure 7 In an implementation manner, the number of BWPs is 3.

[0119] Reference Figure 7, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier frequency band to the other end thereof. Additionally, a PRB may be a resource block numbered within each BWP. Point A may indicate a common reference point of a resource block grid.

[0120] It can be obtained by point A, the offset relative to point A (N start BWP ) and bandwidth (N size BWP ) to configure the BWP. For example, point A can be an external reference point of the PRBs of the carrier, and subcarrier 0 of all parameter sets (e.g., all parameter sets supported by the network on the corresponding carrier) are aligned in point A. For example, the offset can be the PRB distance between the lowest subcarrier within a given parameter set and point A. For example, the bandwidth can be the number of PRBs within a given parameter set.

[0121] Hereinafter, V2X or SL communication will be described.

[0122] The side link synchronization signal (SLSS) may include a primary side link synchronization signal (PSSS) and a secondary side link synchronization signal (SSSS) as SL specific sequences. The PSSS may be referred to as a side link primary synchronization signal (S-PSS), and the SSSS may be referred to as a side link secondary synchronization signal (S-SSS). For example, an M sequence of length 127 may be used for the S-PSS, and a Gold sequence of length 127 may be used for the S-SSS. For example, the UE may use the S-PSS for initial signal detection and synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID.

[0123] The physical sidelink broadcast channel (PSBCH) can be a (broadcast) channel for sending default (system) information, which the UE must first know before SL signal transmission / reception. For example, the default information can be information related to SLSS, duplex mode (DM), time division duplex (TDD) uplink / downlink (UL / DL) configuration, information related to resource pool, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH can be 56 bits, including a 24-bit cyclic redundancy check (CRC).

[0124] S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL synchronization signal (SS) / PSBCH block, hereinafter, sidelink synchronization signal block (S-SSB)). The S-SSB may have the same parameter set (i.e., SCS and CP length) as the physical sidelink control channel (PSCCH) / physical sidelink shared channel (PSSCH) in the carrier, and the transmission bandwidth may exist within a (pre-) configured sidelink (SL) BWP. For example, the S-SSB may have a bandwidth of 11 resource blocks (SBs). For example, the PSBCH may exist across 11 RBs. In addition, the frequency position of the S-SSB may be (pre-) configured. Therefore, the UE does not have to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0125] Figure 8 A process of performing V2X or SL communication by a UE based on a transmission mode according to an embodiment of the present disclosure is shown. Figure 8 The embodiments of the present disclosure may 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 ease of explanation, in LTE, the transmission mode may be referred to as an LTE transmission mode. In NR, the transmission mode may be referred to as an NR resource allocation mode.

[0126] For example, Figure 8 (a) in FIG. 1 shows UE operations related to LTE transmission mode 1 or LTE transmission mode 3. Alternatively, for example, Figure 8 (a) in FIG. 1 shows UE operations related to NR resource allocation mode 1. For example, LTE transmission mode 1 may be applied to conventional SL communication, and LTE transmission mode 3 may be applied to V2X communication.

[0127] For example, Figure 8 (b) in FIG. 4 shows UE operations related to LTE transmission mode 2 or LTE transmission mode 4. Alternatively, for example, Figure 8 (b) in FIG. 1 shows UE operation related to NR resource allocation mode 2.

[0128] Reference Figure 8 (a), in LTE transmission mode 1, LTE transmission mode 3 or NR resource allocation mode 1, the base station may schedule SL resources to be used by the UE for SL transmission. For example, in step S600, the base station may send information related to the SL resources and / or information related to the UL resources to the first UE. 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.

[0129] For example, the first UE may receive information related to dynamic grant (DG) resources and / or information related to configuration grant (CG) resources from the base station. For example, the CG resources may include CG type 1 resources or CG type 2 resources. In the present disclosure, the DG resources may be resources configured / allocated to the first UE by the base station through downlink control information (DCI). In the present disclosure, the CG resources may be (periodic) resources configured / allocated to the first UE by the base station through DCI and / or RRC messages. 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 UE. 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 UE, and the base station may send a DCI related to the activation or release of the CG resources to the first UE.

[0130] In step S810, the first UE may send a PSCCH (e.g., sidelink control information (SCI) or a first-level SCI) to a second UE based on resource scheduling. In step S820, the first UE may send a PSSCH (e.g., a second-level SCI, a MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S830, the first UE may receive a PSFCH related to the PSCCH / PSSCH from the second UE. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second UE via the PSFCH. In step S840, the first UE may send / report the HARQ feedback information to the base station via the PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on the HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on a preconfigured rule. For example, the DCI may be a DCI for SL scheduling. For example, the format of the DCI may be DCI format 3_0 or DCI format 3_1.

[0131] Hereinafter, an example of DCI format 3_0 will be described.

[0132] DCI format 3_0 is used for scheduling NR PSCCH and NR PSSCH in one cell.

[0133] The following information is sent via DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI:

[0134] - Resource pool index - ceiling (log2I) bits, where I is the number of resource pools used for transmission as configured by the higher layer parameter sl-TxPoolScheduling.

[0135] - Time gap - 3 bits determined by the higher layer parameter sl-DCI-ToSL-Trans

[0136] -HARQ process number - 4 bits

[0137] - New data indicator - 1 bit

[0138] - the lowest index of the subchannel allocated to the initial transmission -ceiling(log2(N SL subChannel ))Bit

[0139] -SCI format 1-A field: frequency resource assignment, time resource assignment

[0140] -PSFCH-to-HARQ feedback timing indicator -ceiling(log2N fb_timing ) bits, where N fb_timing is the number of entries in the higher layer parameter sl-PSFCH-ToPUCCH.

[0141] -PUCCH resource indicator - 3 bits

[0142] - Configuration Index - 0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI; otherwise 3 bits. If the UE is configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI.

[0143] - Counter sidelink assignment index - 2 bits, 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic; 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static

[0144] - Filling bits if necessary

[0145] Reference Figure 8(b), in LTE transmission mode 2, LTE transmission mode 4 or NR resource allocation mode 2, the UE can determine the SL transmission resources within the SL resources configured by the base station / network or the pre-configured SL resources. For example, the configured SL resources or the pre-configured SL resources can be a resource pool. For example, the UE can autonomously select or schedule resources for SL transmission. For example, the UE can perform SL communication by autonomously selecting resources within the configured resource pool. For example, the UE can autonomously select resources within the selection window by performing a sensing process and a resource (re)selection process. For example, sensing can be performed in units of subchannels. For example, in step S810, the first UE that has selected resources from the resource pool by itself can send a PSCCH (e.g., sidelink control information (SCI) or a first-level SCI) to a second UE by using the resources. In step S820, the first UE can send a PSSCH (e.g., a second-level SCI, a MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S830, the first UE can receive a PSFCH related to the PSCCH / PSSCH from the second UE.

[0146] Reference Figure 8 (a) or (b), for example, the first UE may send the SCI to the second UE via the PSCCH. Alternatively, for example, the first UE may send two consecutive SCIs (e.g., level 2 SCIs) to the second UE via the PSCCH and / or the PSSCH. In this case, the second UE may decode the two consecutive SCIs (e.g., level 2 SCIs) to receive the PSSCH from the first UE. In the present disclosure, the SCI sent via the PSCCH may be referred to as the first SCI, the first SCI, the first level SCI, or the first level SCI format, and the SCI sent via the PSSCH may be referred to as the second SCI, the second SCI, the second level SCI, or the second level SCI format. For example, the first level SCI format may include SCI format 1-A, and the second level SCI format may include SCI format 2-A and / or SCI format 2-B.

[0147] Hereinafter, an example of SCI format 1-A will be described.

[0148] SCI format 1-A is used for scheduling PSSCH and secondary SCI on PSSCH.

[0149] The following information is sent via SCI Format 1-A:

[0150] - Priority - 3 bits

[0151] - Frequency resource assignment - When the value of the higher layer parameter sl-MaxNumPerReserve is configured as 2, ceiling(log2(N SL subChannel (N SL subChannel +1) / 2)) bits; otherwise, when the value of the high-level parameter sl-MaxNumPerReserve is configured as 3, ceiling log2(N SL subChannel (N SL subChannel +1)(2N SL subChannel +1) / 6) bits.

[0152] - Time resource assignment - 5 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured as 2; otherwise, 9 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured as 3

[0153] -Resource reservation period - If the high-level parameter sl-MultiReserveResource is configured, the ceiling (log2 N rsv_period ) bits, where N rsv_period is the number of entries in the higher-level parameter sl-ResourceReservePeriodList; otherwise, 0

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

[0155] - Second level SCI format - 2 bits, as defined in Table 5

[0156] - Beta_offset indicator - 2 bits, as provided by the higher layer parameter sl-BetaOffsets2ndSCI

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

[0158] - Modulation and compilation scheme - 5 bits

[0159] - 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; otherwise, 0 bit

[0160] -PSFCH overhead indication - 1 bit if higher layer parameter sl-PSFCH-Period = 2 or 4; otherwise, 0 bit

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

[0162] [Table 5]

[0163] Value of the second level SCI format field Second level SCI format 00 SCI Format 2-A 01 SCI Format 2-B 10 reserve 11 reserve

[0164] [Table 6]

[0165] The value of the Number of DMRS Ports field Antenna Port 0 1000 1 1000 and 1001

[0166] Hereinafter, an example of SCI format 2-A will be described.

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

[0168] The following information is sent via SCI Format 2-A:

[0169] -HARQ process number - 4 bits

[0170] - New data indicator - 1 bit

[0171] - Redundancy version - 2 bits

[0172] - Source ID - 8 bits

[0173] -Destination ID - 16 bits

[0174] -HARQ feedback enable / disable indicator - 1 bit

[0175] - Broadcast Type Indicator - 2 bits, as defined in Table 7

[0176] -CSI request - 1 bit

[0177] [Table 7]

[0178] The value of the broadcast type indicator Broadcast Type 00 broadcast 01 Multicast when HARQ-ACK information includes ACK or NACK 10 Unicast 11 Multicast when HARQ-ACK information includes only NACK

[0179] Hereinafter, an example of SCI format 2-B will be described.

[0180] For HARQ operation, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information, SCI format 2-B is used for decoding of PSSCH.

[0181] The following information is sent via SCI Format 2-B:

[0182] -HARQ process number - 4 bits

[0183] - New data indicator - 1 bit

[0184] - Redundancy version - 2 bits

[0185] - Source ID - 8 bits

[0186] -Destination ID - 16 bits

[0187] -HARQ feedback enable / disable indicator - 1 bit

[0188] - Region ID - 12 digits

[0189] -Communication range requirement - 4 bits determined by the higher-level parameter sl-ZoneConfigMCR-Index

[0190] Reference Figure 8 (a) or (b), in step S830, the first UE may receive the PSFCH. For example, the first UE and the second UE may determine the PSFCH resource, and the second UE may use the PSFCH resource to send the HARQ feedback to the first UE.

[0191] Reference Figure 8 (a), in step S840, the first UE may send SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0192] Fig. 9 Three types of broadcasts are shown in accordance with embodiments of the present disclosure. Fig. 9 The embodiments of can be combined with various embodiments of the present disclosure. Specifically, Fig. 9 (a) shows broadcast type SL communication, Fig. 9 (b) in FIG. 4 shows unicast type SL communication, and Fig. 9 (c) shows multicast SL communication. In the case of unicast SL communication, the UE can perform one-to-one communication with another UE. In the case of multicast SL transmission, the UE can perform SL communication with one or more UEs in the group to which the UE belongs. In various embodiments of the present disclosure, SL groupcast communication can be replaced by SL multicast communication, SL one-to-many communication, etc.

[0193] Hereinafter, a hybrid automatic repeat request (HARQ) process will be described.

[0194] For example, SL HARQ feedback may be enabled for unicast. In this case, in non-code block group (non-CBG) operation, if the receiving UE decodes the PSCCH whose target is the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may generate a HARQ-ACK. In addition, the receiving UE may send a HARQ-ACK to the transmitting UE. Otherwise, if the receiving UE fails to successfully decode the transport block after decoding the PSCCH whose target is the receiving UE, the receiving UE may generate a HARQ-NACK. In addition, the receiving UE may send a HARQ-NACK to the transmitting UE.

[0195] For example, SL HARQ feedback may be enabled for multicast.For example, in non-CBG operation, two HARQ feedback options may be supported for multicast.

[0196] (1) Multicast Option 1: After the receiving UE decodes the PSCCH whose target is the receiving UE, if the receiving UE cannot decode the transport block associated with the PSCCH, the receiving UE may send HARQ-NACK to the sending UE through the PSFCH. Otherwise, if the receiving UE decodes the PSCCH whose target is the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may not send HARQ-ACK to the sending UE.

[0197] (2) Multicast Option 2: After the receiving UE decodes the PSCCH whose destination is the receiving UE, if the receiving UE cannot decode the transport block associated with the PSCCH, the receiving UE may send HARQ-NACK to the transmitting UE via the PSFCH. In addition, if the receiving UE decodes the PSCCH whose destination is the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may send HARQ-ACK to the transmitting UE via the PSFCH.

[0198] For example, if multicast option 1 is used for SL HARQ feedback, all UEs performing multicast communication may share PSFCH resources. For example, UEs belonging to the same group may send HARQ feedback by using the same PSFCH resources.

[0199] For example, if multicast option 2 is used for SL HARQ feedback, each UE performing multicast communication may use different PSFCH resources for HARQ feedback transmission. For example, UEs belonging to the same group may send HARQ feedback by using different PSFCH resources.

[0200] In the present disclosure, HARQ-ACK may be referred to as ACK, ACK information, or positive ACK information, and HARQ-NACK may be referred to as NACK, NACK information, or negative ACK information.

[0201] In various embodiments of the present disclosure, a TX UE and / or an RX UE may obtain a discontinuous reception (DRX) configuration. For example, the DRX configuration may include a Uu DRX configuration and / or an SL DRX configuration. For example, the TX UE may receive the DRX configuration from a base station, and the RX UE may receive the DRX configuration from the TX UE. For example, the DRX configuration may be configured or preconfigured for the TX UE and / or the RX UE.

[0202] For example, the Uu DRX configuration may include information related to drx-HARQ-RTT-Timer-SL and / or information related to drx-RetransmissionTimer-SL. For example, the timer may be used for the following purposes.

[0203] (1) drx-HARQ-RTT-Timer-SL (per HARQ process): The drx HARQ RTT timer SL may be the minimum duration before the MAC entity expects a sidelink HARQ retransmission grant. The drx-HARQ-RTT-Timer-SL may refer to the minimum time required until resources for SL mode 1 retransmission are ready. That is, resources for sidelink retransmission cannot be prepared before the drx-HARQ-RTT-Timer-SL timer. Therefore, the TX UE may reduce power consumption by transitioning to sleep mode during the drx-HARQ-RTT-Timer-SL timer. Alternatively, the TX UE may not perform mode 1 DCI monitoring from the base station. If the drx-HARQ-RTT-Timer-SL timer expires, the TX UE may determine that resources for SL retransmission may be ready. Therefore, the TX UE may start the drx-RetransmissionTimer-SL timer and monitor whether resources for SL HARQ retransmission are received. Once the drx-HARQ-RTT-Timer-SL timer expires, the SL HARQ retransmission resources may or may not be received, so the TX UE may start the drx-RetransmissionTimer-SL timer, and the TX UE may monitor the mode 1 DCI from the base station to receive resources for SL HARQ retransmission. For example, the drx-HARQ-RTT-Timer-SL timer may be a duration during which a TX UE (e.g., a UE supporting UuDRX 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.

[0204] (2) drx-RetransmissionTimer-SL (per HARQ process): drx-RetransmissionTimer-SL can be the maximum duration until a grant for sidelink retransmission is received. That is, the drx-RetransmissionTimer-SL timer can be a timer that is started when the drx-HARQ-RTT-Timer-SL timer expires, and it can be a timer that allows the TX UE to transition to an active state for SL retransmission. Alternatively, while the corresponding timer is running, the TX UE can monitor the mode 1 DCI from the base station. The TX UE can monitor the SL mode 1 DCI from the base station from the time when the drx-RetransmissionTimer-SL is started to check whether the retransmission resources (i.e., the grant for sidelink retransmission) to the RX UE are ready. And, if the retransmission resources are ready, the TX UE can perform sidelink HARQ retransmission to the RX UE. When sending a HARQ retransmission packet to the RX UE, the TX UE can stop the drx-RetransmissionTimer-SL timer. When the drx-RetransmissionTimer-SL timer is running, the UE may maintain an active state. For example, the drx-RetransmissionTimer-SL timer may be a duration for a TX UE (e.g., a UE supporting Uu DRX operation) that performs sidelink communication based on sidelink resource allocation mode 1 to perform PDCCH (or DCI) monitoring for sidelink mode 1 resource allocation from a base station.

[0205] For example, the SL DRX configuration may include at least one parameter / information among the parameters / information described below.

[0206] (1)SL drx-onDurationTimer: Duration when the SL DRX cycle starts

[0207] (2)SL drx-SlotOffset: Delay before starting sl drx-onDurationTimer

[0208] (3) SL drx-InactivityTimer: Duration after the PSCCH opportunity, where the PSCCH indicates a new SL transmission by the MAC entity

[0209] (4) SL drx-RetransmissionTimer (per HARQ process or per side link process): Maximum duration until a retransmission is received

[0210] (5) SL drx-HARQ-RTT-Timer (per HARQ process or per side link process): The minimum duration before the PSCCH (side link control information) and PSSCH that the MAC entity expects to be used for SL HARQ retransmissions

[0211] (6)SL drx-LongCycleStartOffset: Long DRX cycle and drx-StartOffset, which define the subframes where the long DRX cycle and the short DRX cycle start.

[0212] (7)SL drx-ShortCycle (optional): short DRX cycle

[0213] (8)SL drx-ShortCycleTimer (optional): Duration of the short DRX cycle that the UE should follow

[0214] (9)SL drx-HARQ-RTT-Timer (each link process): The minimum duration before the MAC entity expects a HARQ retransmission allocation

[0215] (10)SL drx-StartOffset: The subframe where the SL DRX cycle starts

[0216] (11)SL drx-Cycle: SL DRX cycle

[0217] The SL DRX timer described in this disclosure may be used for the following purposes.

[0218] (1) SL DRX On Duration Timer: The duration during which a UE performing SL DRX operation should operate substantially in the active time in order to receive PSCCH / PSSCH from other UEs

[0219] (2) SL DRX Inactivity Timer: extends the duration of the SL DRX On-Duration, which is a duration in which a UE performing a SL DRX operation should substantially operate in an active time in order to receive a PSCCH / PSSCH from other UEs.

[0220] For example, the UE may extend the SL DRX On Duration timer by the SL DRX Inactivity timer duration. In addition, if the UE receives a new packet (eg, a new PSSCH transmission) from other UEs, the UE may extend the SL DRX On Duration timer by starting the SL DRX Inactivity timer.

[0221] For example, the SL DRX inactivity timer can be used to extend the duration of the SL DRX on duration, which is the duration during which the RX UE performing the SL DRX operation should operate substantially in active time in order to receive PSCCH / PSSCH from other UEs. That is, the SL DRX on duration timer can extend the SL DRX inactivity timer period. In addition, if the RX UE receives a new packet (e.g., a new PSSCH transmission) from other TX UEs, the RX UE can extend the SL DRX on duration timer by starting the SL DRX inactivity timer.

[0222] (3) SL DRX HARQ RTT timer: the duration during which a UE performing SL DRX operation operates in sleep mode until receiving a retransmission packet (or PSSCH allocation) sent by other UEs.

[0223] For example, if the UE starts the SL DRX HARQ RTT timer, the UE can determine that other UEs will not send sidelink retransmission packets to the UE until the SL DRX HARQ RTT timer expires, and the UE can operate in sleep mode while the corresponding timer is running. For example, if the UE starts the SL DRX HARQ RTT timer, the UE may not monitor sidelink retransmission packets from other UEs until the SL DRX HARQ RTT timer expires. For example, if the RX UE that has received the PSCCH / PSSCH sent by the TX UE sends a SL HARQ NACK feedback, the RX UE can start the SL DRXHARQ RTT timer. In this case, the RX UE can determine that other TX UEs will not send sidelink retransmission packets to the RX UE until the SL DRX HARQ RTT timer expires, and the RX UE can operate in sleep mode while the corresponding timer is running.

[0224] (4) SL DRX Retransmission Timer: A timer that is started when the SL DRX HARQ RTT timer expires, and the duration that a UE performing SL DRX operation operates in the active time to receive retransmission packets (or PSSCH allocations) sent by other UEs

[0225] For example, for the corresponding timer duration, the UE may receive or monitor retransmission side link packets (or PSSCH allocations) sent by other UEs. For example, the RX UE may receive or monitor retransmission side link packets (or PSSCH allocations) sent by other TX UEs while the SL DRX retransmission timer is running.

[0226] In the present disclosure, the names of timers (drx-HARQ-RTT-Timer-SL, drx-RetransmissionTimer-SL, sidelink DRX duration timer, sidelink DRX inactivity timer, sidelink DRX HARQ RTT timer, sidelink DRX retransmission timer, etc.) are exemplary, and timers that perform the same / similar functions based on the contents described in each timer can be considered as the same / similar timers regardless of the name of the timer.

[0227] A UE operating in sidelink DRX may operate in active mode to perform PSCCH / PSSCH monitoring during the DRX active time (e.g., the on-duration timer, the inactivity timer, the retransmission timer, or the duration when operating in active mode). However, the UE may operate in sleep mode during the sidelink DRX inactive duration and not perform PSCCH / PSSCH monitoring operations for SL data reception.

[0228] In sidelink unicast, the UE can negotiate / determine the sidelink DRX configuration (SL DRX configuration to be used during sidelink unicast communication) with another UE with which a unicast connection has been established. If there is a connection (RRC connection) between the sending UE and the base station, the base station of the sending UE can configure the SL DRX configuration to be used by the receiving UE that has established a unicast connection with the sending UE and notify the sending UE, and the sending UE can send the SL DRX configuration to be used by the receiving UE received from the base station to the receiving UE through a PC5 RRC message. If there is no connection (RRC connection) between the sending UE and the base station, the sending UE can directly configure the SL DRX configuration to be used by the receiving UE that has established a unicast connection with the sending UE, and send it to the receiving UE through a PC5 RRC message.

[0229] Although SL DRX is the operation of the receiving UE, the sending UE also needs to know the SL DRX operation status of the receiving UE (active or sleep mode, or when the DRX on duration / inactivity / HARQ RTT / retransmission timer starts, when the DRX on duration / inactivity / HARQ RTT / retransmission timer expires, etc.). For example, when allocating and transferring resources, the sending UE should be able to determine whether the receiving UE is operating in active mode or sleep mode. Therefore, the sending UE can apply the same SL DRX configuration as the receiving UE to maintain the same SL DRX timer operation status as the receiving UE, etc.

[0230] The AS layer of a UE (RX UE or TX UE) that supports SL DRX behavior can receive a Tx profile mapped for an available side link service from a higher layer (e.g., a V2X layer). The Tx profile may include information that distinguishes whether an available side link service or a concerned side link service is a side link service that requires SL DRX operation. Therefore, when the AS layer of the UE receives available side link data (or concerned side link service) and a Tx profile from an upper layer, the UE can decide (or determine) that it should or should not support SL DRX operation for the available side link data (or concerned side link service).

[0231] In addition, in the conventional unlicensed spectrum (NR-U), a communication method between a UE and a base station is supported in an unlicensed band. In addition, it is planned in Rel-18 to support a mechanism for supporting communication in an unlicensed band between sidelink UEs.

[0232] On the other hand, a set of non-contiguous RBs (equally spaced) on frequency can be allocated to a UE. Such a set of non-contiguous RBs can be called interleaved RBs. This may be useful in applying spectrum (e.g., shared spectrum) with provisions such as occupied channel bandwidth (OCB) and power spectral density (PSD).

[0233] Fig.10 The interleaved RBs according to an embodiment of the present disclosure are shown. The embodiment of FIG. 110 may be combined with various embodiments of the present disclosure.

[0234] Reference Fig.10 , multiple interlaces of RBs can be defined in the frequency domain. Interlace m∈{0,1,...,M-1} can be composed of (common) RBs{m,M+m,2M+m,3M+m,...}, where M represents the number of interlace RBs given in Table 8.

[0235] [Table 8]

[0236] u M 0 10 1 5

[0237] A communication device (e.g., a device, UE, vehicle, drone, etc. proposed in various embodiments of the present disclosure) may use one or more interleaved RBs to send a signal / channel.

[0238] In the present disclosure, a channel may refer to a set of frequency domain resources that perform listen-before-talk (LBT). In NR-U, a channel may refer to an LBT bandwidth of 20 MHz and may have the same meaning as an RB set. For example, an RB set may be defined in Section 7 of 3GPP TS38.214 V17.0.0.

[0239] In the present disclosure, channel occupancy (CO) may refer to time domain / frequency domain resources obtained by a base station or a UE after LBT succeeds.

[0240] In the present disclosure, channel occupation time (COT) may refer to the time domain resources obtained by a base station or UE after LBT is successful. The channel occupation time (COT) may be shared between a base station (or UE) that obtains CO and a UE (or base station), and this may be referred to as COT sharing. Depending on the initiating device, this may be referred to as gNB-initiated COT or UE-initiated COT.

[0241] Hereinafter, a wireless communication system supporting an unlicensed band / shared spectrum will be described.

[0242] Fig.10 An example of a wireless communication system supporting an unlicensed frequency band based on an embodiment of the present disclosure is shown. Fig.10 Unlicensed spectrum (NR-U) wireless communication systems may be included. Fig.10 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0243] In the following description, a cell operating in an authorized frequency band (hereinafter, L band) may be defined as an L cell, and a carrier of the L cell may be defined as (DL / UL / SL)LCC. In addition, a cell operating in an unlicensed frequency band (hereinafter, U band) may be defined as a U cell, and a carrier of the U cell may be defined as (DL / UL / SL)UCC. The carrier / carrier frequency of a cell may refer to an operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., CC) is generally referred to as a cell.

[0244] like Fig.10 As shown in (a), when the base station and the UE send and receive signals on the LCC and UCC of carrier aggregation, the LCC and the UCC can be configured as a primary CC (PCC) and a secondary CC (SCC), respectively. Fig.10 As shown in (b), the base station and the UE can send and receive signals on one UCC or on a UCC of multiple carrier aggregation. In other words, the base station and the UE can send and receive signals only on the UCC without using any LCC. For independent operation, PRACH transmission, PUCCH transmission, PUSCH transmission, SRS transmission, etc. can be supported on the U cell.

[0245] exist Fig.10 In the implementation manner, the base station can be replaced by a UE. In this case, for example, PSCCH transmission, PSSCH transmission, PSFCH transmission, S-SSB transmission, etc. can be supported on the U cell.

[0246] Unless otherwise stated, the following definitions apply to the following terms used in this disclosure.

[0247] Channel: A carrier or a portion of a carrier consisting of a contiguous set of RBs where a channel access procedure is performed in a shared spectrum.

[0248] Channel Access Procedure (CAP): A procedure to evaluate channel availability based on sensing before signal transmission to determine whether other communication nodes are using the channel. The basic sensing unit is a sensing time slot, where the duration T sl =9us. The base station or UE senses the channel during the sensing time slot duration. If the power detected within at least 4us during the sensing time slot duration is less than the energy detection threshold X thresh , then the sensing time slot duration T sl is considered idle. Otherwise, the sensing time slot duration T sl = 9us is considered busy. CAP can also be called Listen Before Talk (LBT).

[0249] Channel occupancy: The transmission of the base station / UE on the channel after the channel access procedure.

[0250] Channel Occupancy Time (COT): The total time that the base station / UE sharing the channel and any base station / UE can perform transmission on the channel after the base station / UE performs the channel access procedure. In the case of determining the COT, if the transmission gap is less than or equal to 25us, the gap duration can be counted in the COT. The COT can be shared for transmission between the base station and the corresponding UE.

[0251] DL transmission burst: A collection of transmissions from a base station without any gaps greater than 16us. Transmissions from a base station separated by gaps greater than 16us are considered separate DL transmission bursts. The base station may perform transmissions after a gap without sensing channel availability within a DL transmission burst.

[0252] UL or SL transmission burst: A set of transmissions from a UE without any gaps greater than 16us. Transmissions from a UE separated by gaps greater than 16us are considered separate UL or SL transmission bursts. The UE may perform a transmission after a gap without sensing channel availability within a UL or SL transmission burst.

[0253] Discovery Burst: A DL transmission burst includes a set of signals and / or channels that are confined within a window and associated with a duty cycle. In LTE-based systems, a discovery burst may be a transmission initiated by a base station that includes PSS, SSS, and cell-specific RS (CRS), and also includes non-zero power CSI-RS. In NR-based systems, a discovery burst may be a transmission initiated by a base station that includes at least a SS / PBCH block, and also includes a CORESET for scheduling a PDSCH carrying SIB1, a PDSCH carrying SIB1, and / or a PDCCH with non-zero power CSI-RS.

[0254] Fig.11 A method for occupying resources in an unlicensed frequency band according to an embodiment of the present disclosure is shown. Fig.11 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0255] Reference Fig.11 , a communication node (e.g., base station, UE) in an unlicensed band should determine whether other communication nodes are using the channel before signal transmission. To this end, a communication node in an unlicensed band may perform a channel access procedure (CAP) to access the channel where the transmission is performed. The channel access procedure may be performed based on sensing. For example, a communication node may perform carrier sensing (CS) before sending a signal to check whether other communication nodes are performing signal transmission. When other communication nodes are not performing signal transmission, a clear channel assessment (CCA) is confirmed. If the CCA threshold (e.g., X Thresh ) is predefined or configured by a higher layer (e.g., RRC), the communication node may determine that the channel is busy if the detected channel energy is above the CCA threshold. Otherwise, the communication node may determine that the channel is idle. If the channel is determined to be idle, the communication node may start signal transmission in the unlicensed band. CAP may be replaced by LBT.

[0256] Table 9 shows an example of a channel access procedure (CAP) supported in NR-U.

[0257] [Table 9]

[0258]

[0259] Referring to Table 9, LBT types or CAPs for DL / UL / SL transmission may be defined. However, Table 9 is only 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 channel access procedure based on random backoff. For example, in the case of Cat-4, the contention window may be changed. For example, Type 2 may be performed in the case of COT sharing within a COT acquired by a base station (gNB) or UE.

[0260] Hereinafter, an LBT-subband (SB) (or RB set) will be described.

[0261] In a wireless communication system supporting an unlicensed band, a cell (or carrier (e.g., CC)) or BWP configured for a UE may have a broadband having a larger bandwidth (BW) than in conventional LTE. However, the BW of a CCA that requires independent LBT operation may be limited according to regulations. A subband (SB) in which LBT is performed alone is defined as an LBT-SB. Then, multiple LBT-SBs may be included in one broadband cell / BWP. The RB set included in the LBT-SB may be configured by higher layer (e.g., RRC) signaling. Therefore, based on (i) the BW of the cell / BWP and (ii) the RB set allocation information, one or more LBT-SBs may be included in one cell / BWP.

[0262] Fig.12 A case where a plurality of LBT-SBs are included in a license-free band according to an embodiment of the present disclosure is shown. Fig.12 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0263] Reference Fig.12 , multiple LBT-SBs may be included in the BWP of a cell (or carrier). The LBT-SB may have, for example, a 20MHz frequency band. The LBT-SB may include multiple consecutive (P)RBs in the frequency domain and may therefore be referred to as a (P)RB set. Although not shown, a guard band (GB) may be inserted between the LBT-SBs. Therefore, the BWP may be configured in the form of {LBT-SB#0 (RB set #0) + GB#0 + LBT-SB#1 (RB set #1 + GB#1) + ··· + LBT-SB#(K-1) (RB set (#K-1))}. For convenience, the LBT-SB / RB index may be configured / defined in increasing order from the lowest frequency to the highest frequency.

[0264] Hereinafter, a channel access priority class (CAPC) will be described.

[0265] The CAPC of the MAC CE and radio bearers can be fixed or configured to operate in FR1:

[0266] Fixed to the lowest priority for filling buffer status report (BSR) and recommended bit rate MAC CE;

[0267] For SRB0, SRB1, SRB3 and other MAC CEs, they are fixed to the highest priority;

[0268] For SRB2 and DRB, it is configured by the base station.

[0269] When selecting the CAPC for a DRB, the base station considers fairness between other service types and transmissions while considering the 5QIs of all QoS flows multiplexed to the corresponding DRB. Table 9 shows which CAPC should be used for a standardized 5QI (i.e., the CAPC to be used for a given QoS flow). For a standardized 5QI, the CAPC is defined as shown in the following table, and for a non-standardized 5QI, the CAPC with the best QoS characteristics should be used.

[0270] [Table 10]

[0271]

[0272] Hereinafter, a method of transmitting a downlink signal through an unlicensed frequency band will be described. For example, the method of transmitting a downlink signal through an unlicensed frequency band may be applied to a method of transmitting a sidelink signal through an unlicensed frequency band.

[0273] The base station may perform one of the following channel access procedures (eg, CAP) for downlink signal transmission in the unlicensed band.

[0274] Type 1 Downlink (DL) CAP Method

[0275] In a Type 1 DL CAP, the length of the duration spanned by a sensing slot that is sensed as idle before a transmission may be random. Type 1 DL CAP may be applied to the following transmissions:

[0276] A transmission initiated by a base station includes (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

[0277] Transmissions initiated by the base station include (i) only a discovery burst or (ii) a discovery burst multiplexed with non-unicast information.

[0278] Fig.13 A CAP operation performed by a base station to transmit a downlink signal through an unlicensed frequency band according to an embodiment of the present disclosure is shown. Fig.13 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0279] Reference Fig.13 , the base station can sense whether the channel is idle for the sensing delay duration T d Then, if the counter N is zero, the base station may perform transmission (S134). In this case, the base station may adjust the counter N by sensing the channel during the additional sensing time slot duration according to the following steps:

[0280] Step 1) (S120) The base station sets N to N init (N=N init ), where N init For uniform distribution from 0 to CW p Then, proceed to step 4.

[0281] Step 2) (S140) If N>0 and the base station determines to decrease the counter, the base station sets N to N-1 (N=N-1).

[0282] Step 3) (S150) The base station senses the channel during the additional sensing time slot duration. If the additional sensing time slot duration is idle (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0283] Step 4) (S130) If N=0 (Y), the base station terminates CAP (S132). Otherwise (N), proceed to step 2.

[0284] Step 5) (S160) The base station senses the channel until the additional delay duration T d The busy sensing time slot or additional delay duration T is detected d All time slots are detected as idle.

[0285] Step 6) (S170) If the additional delay duration T d If the channel is sensed as idle during all time slot durations (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0286] Table 11 shows the m applied to CAP p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW size vary according to the channel access priority category.

[0287] [Table 11]

[0288]

[0289] Referring to Table 11, the contention window size (CWS), maximum COT value, etc. for each CAPC can be defined. d Can be equal to T f +m p *T sl (T d =T f +m p *T sl ).

[0290] Delay duration T dConfigure in the following order: Duration T f (16us)+m p Continuous sensing time slot duration T sl (9us).T f The sensing time slot duration T includes the time slot duration T at the beginning of the 16us duration. sl .

[0291] Satisfies the following relationship: CW min,p <=CW p <=CW max,p .CW p Available via CW p =CW min,p The CW size may be configured and updated (CW size update) based on HARQ-ACK feedback (e.g., ratio of ACK or NACK) for a previous DL burst (e.g., PDSCH) before step 1. For example, the CW size may be updated based on HARQ-ACK feedback for a previous DL burst. p Initialize to CW min,p . Alternatively, CW p Can be increased to the next higher allowed value or left unchanged.

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

[0293] In a Type 2 DL CAP, the length of the duration spanned by a sensing slot sensed as idle before transmission may be determined. Type 2 DL CAPs are classified into Type 2A / 2B / 2C DL CAPs.

[0294] Type 2A DL CAP may be applied to the following transmissions. In Type 2A DL CAP, the base station may send a signal when the channel is sensed to be idle for at least the sensing duration T. short_dl = 25us and then the transmission is performed immediately. In this paper, T short_dl Including duration T f (=16us) and immediately after the duration T f After a sensing time slot duration, the duration T f Includes a sensing slot at its beginning.

[0295] A transmission initiated by a base station, including (i) only a discovery burst or (ii) a discovery burst multiplexed with non-unicast information, or

[0296] The base station transmits after a gap of 25us from the UE's transmission within the shared channel occupation.

[0297] Type 2B DL ​​CAP applies to transmissions performed by the base station after a 16us gap from the UE's transmission during the shared channel occupation time. In Type 2B DL ​​CAP, the base station can f = Transmission is performed immediately after being sensed as idle within 16us. T f Includes sensing slots within 9us from the end of the duration. Type 2C DL CAP applies to transmissions performed by the base station at most 16us after the UE's transmission during the shared channel occupation time. In Type 2C DL CAP, the base station does not perform channel sensing before performing transmission.

[0298] Hereinafter, a method of transmitting an uplink signal through an unlicensed frequency band will be described. For example, the method of transmitting an uplink signal through an unlicensed frequency band may be applied to a method of transmitting a sidelink signal through an unlicensed frequency band.

[0299] The UE may perform a Type 1 CAP or a Type 2 CAP for UL signal transmission in an unlicensed band. Typically, the UE may perform a CAP (e.g., Type 1 or Type 2) for UL signal transmission configured by the base station. For example, a UL grant (e.g., DCI format 0_0 and DCI format 0_1) for scheduling PUSCH transmission may include CAP type indication information for the UE.

[0300] Type 1 Uplink (UL) CAP method

[0301] In Type 1 UL CAP, the length of the duration spanned by the sensing slots sensed as idle before transmission is random. Type 1 UL CAP may be applied to the following transmissions.

[0302] PUSCH / SRS transmission scheduled and / or configured by the base station

[0303] PUCCH transmission scheduled and / or configured by the base station

[0304] Transmissions related to the Random Access Procedure (RAP)

[0305] Fig.14 A Type 1 CAP operation performed by a UE to transmit an uplink signal according to an embodiment of the present disclosure is shown. Fig.14 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0306] Reference Fig.14 , the UE can sense the channel at a delay duration T dThen, if the counter N is zero, the UE may perform transmission (S234). In this case, the UE may adjust the counter N by sensing the channel during the additional sensing slot duration according to the following steps:

[0307] Step 1) (S220) UE sets N to N init (N=N init ), where N init For uniform distribution from 0 to CW p Then, proceed to step 4.

[0308] Step 2) (S240) If N>0 and the UE determines to decrease the counter, the UE sets N to N-1 (N=N-1).

[0309] Step 3) (S250) The UE senses the channel during the additional sensing time slot duration. If the additional sensing time slot duration is idle (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0310] Step 4) (S230) If N=0 (Y), the UE terminates the CAP (S132). Otherwise (N), proceed to step 2.

[0311] Step 5) (S260) The UE senses the channel until the additional delay duration T d The busy sensing time slot or additional delay duration T is detected d All time slots are detected as idle.

[0312] Step 6) (S270) If the channel is within the additional delay duration T d If the time slot is sensed as idle for all time slot durations (Y), proceed to step 4. Otherwise (N), proceed to step 5.

[0313] Table 12 shows the m applied to CAP p , minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW size vary according to the channel access priority category.

[0314] [Table 12]

[0315]

[0316] Referring to Table 12, the contention window size (CWS), maximum COT value, etc. for each CAPC can be defined. d Can be equal to T f +m p *T sl (T d =Tf +m p *T sl ).

[0317] Delay duration T d Configure in the following order: Duration T f (16us)+m p Continuous sensing time slot duration T sl (9us).T f The sensing time slot duration T includes the time slot duration T at the beginning of the 16us duration. sl .

[0318] Satisfies the following relationship: CW min,p <=CW p <=CW max,p .CW p Available via CW p =CW min,p Configuration, and before step 1, update (CW size update) based on explicit / implicit reception response for previous UL burst (e.g., PUSCH). For example, CW may be updated based on explicit / implicit reception response for previous UL burst. p Initialize to CW min,p . Alternatively, CW p Can be increased to the next higher allowed value or left unchanged.

[0319] (2) Type 2 Uplink (UL) CAP method

[0320] In a Type 2 UL CAP, the length of the duration spanned by the sensing slot that is sensed as idle before transmission can be determined. Type 2 UL CAP is classified as Type 2A / 2B / 2C UL CAP. In a Type 2A UL CAP, the UE can determine the duration of the sensing slot that is sensed as idle before transmission when the channel is sensed as idle for at least the sensing duration T. short_dl = 25us and then the transmission is performed immediately. In this paper, T short_dl Including duration T f (=16us) and immediately after the duration T f The duration of a sensing slot after that. In Type 2A UL CAP, T f In a Type 2B UL CAP, the UE may sense the channel during the sensing duration T. f = Transmission is performed immediately after being sensed as idle within 16us. In Type 2B UL CAP, T f The sensing slot within 9us from the end of the duration is included. In Type 2C UL CAP, the UE does not perform channel sensing before performing transmission.

[0321] For example, according to NR-U operation based on Type 1 LBT, a UE having uplink data to be transmitted may select a CAPC mapped to 5QI data, and the UE may select a CAPC mapped to 5QI data by applying parameters of the corresponding CACP (e.g., minimum contention window size, maximum contention window size, m p For example, the UE may select a backoff counter (BC) after selecting a random value between 0 and CW (e.g., the minimum CW and the maximum CW mapped to the CAPC). In this case, for example, BC may be a positive integer less than or equal to the random value. For example, if the UE detects that the channel is at time T d (T d =T f +m p *T sl ), it decreases BC by 1. When BC becomes zero, the UE may try to send data by occupying the channel. For example, if the UE detects a collision while trying to send data, it may increase the contention window size (CW size) mapped to the CAPC. In addition, the UE may reselect a random value of the backoff count between 0 and CW, which is reselected by increasing the CW. For example, T sl (=9 microseconds) is a basic sensing unit or sensing time slot and may include a measurement duration of at least 4 microseconds. f The first 9 microseconds (=16 microseconds) can be configured as T sl For example, m p Can be a constant mapped per CAPC and used to calculate T d For example, as the CAPC value decreases (or the priority increases), m p Can be mapped to smaller values.

[0322] For example, according to NR-U operation based on Type 2 LBT, the UE may send data by performing Type 2 LBT (e.g., Type 2A LBT, Type 2B LBT, or Type 2C LBT) within the COT.

[0323] For example, Type 2A (also known as Cat-2 LBT (one shot LBT) or single LBT) can be a 25 microsecond single LBT. In this case, transmission can be started immediately after idle sensing for at least a 25 microsecond gap. Type 2A can be used to initiate transmission of SSB and non-unicast DL information. That is, the UE can sense the channel within the COT for 25 microseconds, and if the channel is idle, the UE can attempt to send data by occupying the channel.

[0324] For example, type 2B may be a 16 microsecond single LBT. In this case, transmission may start immediately after idle sensing for a 16 microsecond gap. That is, the UE may sense the channel for 16 microseconds within the COT, and if the channel is idle, the UE may attempt to send data by occupying the channel.

[0325] For example, in the case of Type 2C (also known as Cat-1 LBT or No LBT), LBT may not be performed. In this case, the transmission may start immediately after a gap of up to 16 microseconds, and the channel may not be sensed before the transmission. The duration of the transmission may be up to 584 microseconds. The UE may attempt to transmit without sensing after 16 microseconds, and the UE may perform transmissions for up to 584 microseconds.

[0326] In the sidelink unlicensed band, the UE can perform a channel access operation based on listen before talk (LBT). Before the UE accesses a channel in the unlicensed band, the UE should check whether the channel to be accessed is idle (e.g., a state in which the UE does not occupy the channel, a state in which the UE can access the corresponding channel and send data) or busy (e.g., a state in which the channel is occupied and data transmission / reception is performed on the corresponding channel, and the UE attempting to access the channel cannot send data when the channel is busy). That is, the operation of the UE checking whether the channel is idle or busy can be referred to as clear channel assessment (CCA), and the UE can check whether the channel is idle or busy during the CCA duration.

[0327] Fig.16 The channel access process based on the embodiment of the present disclosure is shown. Specifically, Fig.16 (a) shows an example of a dynamic channel access process (payload-based equipment, LBE), and Fig.16 (b) shows an example of a semi-static channel access procedure (frame-based equipment, FBE). Fig.16 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0328] Reference Fig.16 (a), if the channel is idle, the UE can perform contention with other UEs in the unlicensed band to immediately occupy the channel. In addition, if the UE occupies the channel, the UE can send data.

[0329] Reference Fig.16 (b), the UE may perform contention with other UEs on the unlicensed band at the last time within the synchronization frame boundary (or fixed frame period (FFP)) (e.g., a time (or start time) before the start of the next FFP). In addition, if the UE occupies the channel within the fixed frame period (FFP), the UE may send data. Data transmission should be completed before the start of the next FFP.

[0330] Meanwhile, the UE may perform sidelink (SL) transmission by performing LBT for each resource block (RB) set in the sidelink-unlicensed spectrum (SL-U), and may report LBT failure to the base station when LBT fails. However, if the UE does not transmit information related to the RB set for which LBT failed to a counterpart UE that performs sidelink communication with the UE in the unlicensed band, the counterpart UE may unnecessarily perform resource selection for the RB set even for which LBT failed, which may result in unnecessary power consumption of the counterpart UE or unnecessary delay in communication in the SL-U.

[0331] In addition, radio link failure (RLF) may occur when transmission fails due to channel quality degradation or unstable conditions, but in an unlicensed band, transmission may fail due to LBT failure regardless of the channel quality, so if the value of the DTX count is increased only due to transmission failure, RLF operation may be performed unnecessarily even if the channel conditions are good.

[0332] In the present disclosure, an operation of a UE reporting an LBT failure to a counterpart UE when the LBT process fails and the device supports the LBT process is proposed.

[0333] For example, in the sidelink-unlicensed spectrum, in order to send SL data, the UE should first occupy a channel in the SL-U. For example, in order to occupy a channel in the SL-U, the UE may perform a process to find a channel that is not occupied by a neighboring sidelink UE by performing LBT (e.g., Type 1 LBT: LBT based on random backoff). For example, when the UE performing LBT finds that the channel is not occupied by a different UE, it may occupy the channel and perform SL data transmission. In the present disclosure, an operation of the UE when LBT (e.g., a single LBT failure or a continuous LBT failure (when as many LBT failure indications as a threshold are received from the physical (PHY) layer)) fails (e.g., when the process of finding an unoccupied channel fails) is proposed. For example, when sidelink data to be sent occurs (e.g., when available SL data occurs in a SL logical channel), the UE may send the sidelink data to the destination UE by including the data in the sidelink grant. For example, if sidelink data to be sent occurs (e.g., by using the allocated sidelink grant) and an LBT process for finding an unoccupied channel in the unlicensed band to send the sidelink data is performed, but the LBT process fails (e.g., one failure or a continuous LBT failure (when the LBT failure reaches a threshold (the threshold can be pre-configured by the base station or by the UE))), the UE can report a single LBT failure report or a continuous LBT failure report to the counterpart UE (e.g., a destination UE that has established a unicast connection, a destination UE that has established an RRC connection, or a destination UE that receives a multicast / broadcast message).

[0334] For example, a UE that reports a single LBT failure report or a continuous LBT failure report can send an LBT failure report message to the opposite UE via an SCI or MAC CE or PC5RRC message. For example, an LBT failure report message via a MAC CE or PC5 RRC message can be sent in a unicast (including a source layer 2ID and a destination layer 2ID in the message) or a multicast / multicast (including a multicast / broadcast destination layer 2ID in the message). For example, an LBT failure report message via an SCI can be sent in a unicast (including a source layer 1ID and a destination layer 1ID in the message) or a multicast / multicast (including a multicast / broadcast destination layer 1ID in the message). In addition, for example, information about the number of times an LBT failure has occurred can be included in a continuous LBT failure report message.

[0335] For example, if the UE receiving the single LBT failure report or the continuous LBT failure report message performs the role of the sending UE, it may perform LBT by applying a SL-CAPC of a lower priority category than the currently applied SL-CAPC (e.g., a SL-CAPC with a larger SL-CAPC value). Alternatively, for example, if the UE receiving the single LBT failure report or the continuous LBT failure report message performs the role of the sending UE, it may perform LBT by applying a SL-CAPC of a higher priority category than the currently applied SL-CAPC (e.g., a SL-CAPC with a smaller SL-CAPC value). Alternatively, for example, if the UE receiving the single LBT failure report or the continuous LBT failure report message performs the role of the sending UE, it may perform LBT and transmission operations by using a different resource pool or a different RB set other than the currently used resource pool or RB set. Alternatively, for example, a UE that receives a single LBT failure report or a continuous LBT failure report message may transmit the single LBT failure report or the continuous LBT failure report to its serving base station (for example, it may be transmitted by side link UE information or UE assistance information or LBT failure report MAC CE to indicate a side link LBT failure).

[0336] For example, if the UE that sends a single LBT failure report or a continuous LBT failure report message also performs the role of a sending UE, it may perform LBT by applying a SL-CAPC of a lower priority category than the currently applied SL-CAPC (e.g., a SL-CAPC with a larger SL-CAPC value). Alternatively, for example, if the UE that sends a single LBT failure report or a continuous LBT failure report message also performs the role of a sending UE, it may perform LBT by applying a SL-CAPC of a higher priority category than the currently applied SL-CAPC (e.g., a SL-CAPC with a smaller SL-CAPC value). Alternatively, for example, if the UE that sends a single LBT failure report or a continuous LBT failure report message also performs the role of a sending UE, it may perform LBT and sending operations by using a different RB set other than the currently used RB set.

[0337] In addition, for example, when sending a single LBT failure report or a continuous LBT failure, the UE declaring a single LBT failure or a continuous LBT failure can send a single LBT failure report or a continuous LBT failure report message to the opposite UE by using a resource pool or a different RB set from the currently used resource pool or RB set (for example, it can be sent through an SCI or MAC CE or PC5 RRC message). For example, the proposed operation can increase the probability that the receiving UE successfully receives the LBT failure report message.

[0338] For example, if the receiving UE receives a single LBT failure report message or a report message of LBT failures occurring less than N times of continuous LBT failures or a continuous LBT failure report message from the transmitting UE, it can use it as information for the purpose of maintaining the current side link session (e.g., unicast or multicast or broadcast). In addition, for example, for other purposes, if the receiving UE receives a single LBT failure report message or a report message of LBT failures occurring less than N times of continuous LBT failures or a continuous LBT failure report message from the transmitting UE, it can use it as information for the purpose of early release of the current side link session (e.g., unicast or multicast or broadcast).

[0339] Fig.17 The operation of a UE sending an LBT failure report message to a counterpart UE based on an embodiment of the present disclosure is shown. Fig.17 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0340] refer to Fig.17, in step S1710, UE A and UE B may obtain information related to multiple RB sets. For example, UE A may establish a unicast connection or a PC5 RRC connection with UE B. In step S1720, UE A may perform LBT for each of the multiple RB sets. For example, a configuration related to LBT may be independently configured for each of the multiple RB sets. For example, the configuration related to LBT may be an LBT failure recovery configuration. For example, the LBT failure recovery configuration may include information related to an LBT counter or information related to a maximum count of LBT failure instances. For example, the LBT may be a type 1 LBT (e.g., an LBT based on random backoff). For example, the LBT may be a single LBT or a continuous LBT. For example, UE A may perform LBT for a first RB set and a second RB set included in the multiple RB sets, respectively. For example, a first LBT failure recovery configuration may be configured for a first RB set, and the first LBT failure recovery configuration may include information related to a first LBT counter or information related to a maximum count of first LBT failure instances. In step S1730, the LBT of UE A for the first RB set may be failed. For example, when LBT is a continuous LBT, the value of the first LBT counter for the first RB set may be incremented whenever an LBT failure indication is transmitted from a lower layer to a higher layer. For example, when the value of the first LBT counter reaches the maximum count of the first LBT failure instance, the LBT failure of the first RB set is determined. In step S1740, based on the LBT failure, UE A may send LBT failure report information to UE B (opposite UE B) other than the base station. For example, UE A may include information for the first RB set in the LBT failure report information. For example, UE A may send LBT failure report information related to the first RB set to UE B on the second RB set based on the LBT success for the second RB set. For example, the LBT failure report information may be sent via an SCI, MAC CE, or PC5RRC message. In step S1750, UE B, which receives the LBT failure report information, may perform LBT on different RB sets excluding the first RB set based on the information related to the first RB set included in the LBT failure report information. Alternatively, for example, UE B receiving the LBT failure report information may perform resource selection on resources excluding the first RB set (or an RB set excluding the first RB set) based on information related to the first RB set included in the LBT failure report information.

[0341] In the present disclosure, as another embodiment, a method for differently applying a persistent LBT failure declaration according to a type of a message sent by a UE is proposed.

[0342] For example, the LBT failure count for continuous LBT failure declaration of physical sidelink feedback channel (PSFCH) transmission, the LBT failure count for continuous LBT failure declaration of sidelink synchronization signal block (SSB) transmission, and the LBT failure count for continuous LBT failure declaration of physical sidelink control channel / physical sidelink shared channel (PSCCH / PSSCH) for sidelink data transmission can be independently executed by the UE. In addition, for example, by differently defining the threshold value (e.g., sl-lbt-FailureInstanceMaxCount) for continuous LBT failure declaration according to the type of message sent by the UE, the operation of continuous LBT failure declaration can be defined differently according to the type of message.

[0343] -sl-lbt-FailureInstanceMaxCount=N of persistent LBT failure declarations for PSCCH / PSSCH for sidelink data transmission

[0344] -sl-lbt-FailureInstanceMaxCount=M for persistent LBT failure declarations for PSFCH transmission

[0345] - S1-LBT-FailureInstanceMaxCount = L for persistent LBT failure declarations for sidelink SSB transmission

[0346] For example, the s1-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for PSCCH / PSSCH for sidelink data transmission may be configured to be a larger value than the s1-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for PSFCH transmission or the s1-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for sidelink SSB transmission. Alternatively, for example, the sl-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for PSCCH / PSSCH for sidelink data transmission may be configured to be a smaller value than the sl-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for PSFCH transmission or the sl-lbt-FailureInstanceMaxCount of persistent LBT failure declarations for sidelink SSB transmission.

[0347] Meanwhile, in the prior art, when the transmitting UE sends a MAC CE (e.g., PSCCH or PSSCH) enabling HARQ feedback to the receiving UE and does not receive HARQ feedback from the receiving UE, it may regard the transmission as discontinuous transmission (DTX) and increment numConsecutiveDTX by 1. For example, when the transmitting UE again sends a MAC CE (e.g., PSCCH or PSSCH) enabling HARQ feedback to the receiving UE and does not receive HARQ feedback from the receiving UE, it may again regard the retransmission as DTX and increment numConsecutiveDTX by 1. For example, when numConsecutiveDTX reaches sl-maxNumConsecutiveDTX (e.g., a DTX threshold configured by the base station), the transmitting UE may declare a sidelink radio link failure (RLF), may release the PC5 RRC connection in which the RLF occurs, and may report the occurrence of the sidelink RLF to the base station.

[0348] Meanwhile, in an unlicensed band, in a situation where a transmitting UE fails to send sidelink data (e.g., PSCCH or PSSC) due to a failure in LBT, it may not be considered as a channel quality degradation condition, which is the same as the occurrence of DTX. For example, even if the channel condition is good, LBT may fail if the channel is occupied by another UE. Therefore, for example, if the transmitting UE can detect that the receiving UE fails to send HARQ feedback due to a failure in LBT, the transmitting UE can reduce the probability of RLF declaration by deducting the number of times the transmitting UE fails to send PSFCH (e.g., HARQ feedback) due to a failure in LBT from the number of numConsecutiveDTX counts that the transmitting UE increments by treating it as DTX. For example, when the transmitting UE obtains channel state information (or channel busy rate (CBR)), the transmitting UE can detect whether the failure of the receiving UE to send HARQ feedback is due to poor channel conditions or the receiving UE fails to perform LBT on the channel even if the channel conditions are good. Alternatively, for example, when the transmitting UE receives a channel state information (CSI) report from the receiving UE, the transmitting UE can detect whether the failure of the receiving UE to send HARQ feedback is due to poor channel conditions, or even if the channel conditions are good, the receiving UE's LBT for the channel fails. Alternatively, for example, when the transmitting UE receives an LBT failure report from the receiving UE, the transmitting UE can detect that the failure of the receiving UE's HARQ feedback transmission is due to the LBT failure of the receiving UE, regardless of the channel conditions. In the present disclosure, an operation for independently performing LBT counting for PSCCH / PSSCH, PSFCH or SL-SSB and independently declaring a continuous LBT failure is proposed. That is, for example, if the transmitting UE receives a continuous LBT failure report for PSFCH from the receiving UE, the transmitting UE can decrement the DTX count (e.g., numConsecutiveDTX) by sl-lbt-FailureInstanceMaxCount for the continuous LBT failure report for PSFCH. Thus, for example, since the transmitting UE may decrement the DTX count, the transmitting UE may not include a case where the PSFCH is not received due to LBT failure in the RLF declaration operation.

[0349] In addition, in the present disclosure, a method is proposed to set the sl-lbt-FailureInstanceMaxCount of PSFCH to a value less than sl-maxNumConsecutiveDTX. For example, using the proposal in the present disclosure, the number of times that the sending UE does not receive PSFCH due to LBT failure can be detected in advance before declaring RLF.

[0350] For example, when the transmitting UE declares LBT failure in the current resource pool or the current RB set, it can continue the sidelink transmission and reception operation in the unlicensed band by switching to a different resource pool or a different RB set, instead of immediately declaring SL RLF.

[0351] In another embodiment of the present disclosure, in order to enable the receiving UE to detect in advance which new resource pool or other RB set to switch to when a continuous LBT failure occurs in the sending UE, the sending UE can notify the receiving UE in advance through a MAC CE or PC5 RRC message or SCI which resource pool or RB set to switch to when a continuous LBT failure occurs (or pre-configured, or receiving information about a threshold N from the base station).

[0352] In another embodiment of the present disclosure, when a sending UE declares continuous LBT failure of multiple (e.g., a threshold number) resource pools or multiple (e.g., a threshold number) RB sets, if the operation of declaring SL RLF is supported, the sending UE can notify the receiving UE of information of threshold N (e.g., threshold N resource pools, or when SL RLF continuous LBT failure occurs in threshold N RB sets and SL RLF is declared, the resource pool is determined to declare SL RLF, or threshold N continuous LBT failures occur in RB sets) in advance (e.g., when a unicast connection is established or when a PC5 RRC reconfiguration process is performed, etc.) through a MAC CE or PC5 RRC message or SCI (or pre-configure, or receive information of threshold N from the base station).

[0353] Fig.18 Operations related to PSFCH transmission failure of UE due to LBT failure according to an embodiment of the present disclosure are shown. Fig.18 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0354] refer to Fig.18, in step S1810, UE A may send a PSSCH to UE B. In step S1820, UE B may perform LBT to send feedback (PSFCH) for the PSSCH to UE A. For example, the LBT sent by UE B for the PSFCH may fail. In step S1830, the PSFCH transmission of UE B may fail. For example, the UE may fail to send the PSFCH due to poor channel conditions. For example, even if the channel conditions are good, the PSFCH transmission of UE B may fail because the channel is occupied by another UE. For example, even if the channel conditions are good, the PSFCH transmission of UE B may fail due to LBT failure. In step S1840, UE A may determine whether the PSFCH reception failure (or the PSFCH transmission failure of UE B) is due to LBT failure. For example, UE A may determine whether the PSFCH reception failure (or the PSFCH transmission failure of UE B) is due to poor channel conditions, or UE B fails to LBT even if the channel conditions are good. For example, if UE A obtains channel state information (e.g., CBR information), UE A can detect whether the PSFCH reception failure is due to a poor channel condition, or even if the channel is good, UE B has LBT failure. For example, if UE A receives channel state information (e.g., CSI) from UE B, UE A can detect whether the PSFCH reception failure is due to a poor channel condition, or even if the channel is good, UE B has LBT failure. For example, if UE A receives LBT failure report information from UE B, UE A can detect that the PSFCH reception failure is due to the LBT failure of UE B, and in step S1850, UE A may not increment the DTX count based on determining that the PSFCH reception failure is due to the LBT failure of UE B. For example, when UE A receives LBT failure report information, UE A may obtain information related to the maximum count of LBT failures of PSFCH included in the LBT failure report information, and UE A may not increment the DTX count by the maximum count of LBT failure instances of PSFCH.

[0355] At the same time, a transmitting UE performing sidelink communication in the sidelink unlicensed band can perform a sidelink LBT operation (or a persistent SL LBT failure operation) for each unicast link to occupy a channel of the sidelink unlicensed band. In the present disclosure, an operation for declaring a persistent SL LBT failure of a UE in unicast communication is proposed.

[0356] For example, when the UE's LBT is successful, it can send packets on the occupied channel. For example, when the UE's LBT fails (for example, when the UE performs sensing during the sensing slot duration and the result indicates that the channel is busy), it may not perform side link transmission because it does not occupy a channel of the unlicensed band. In addition, for example, when an SL LBT failure is detected during an LBT operation occupying a channel of the unlicensed band, the MAC layer of the UE (or the transmitting UE) may receive an indication of an SL LBT failure event from the PHY layer.

[0357] For example, the UE may receive the following parameters for SL LBT failure management for each sidelink unicast link from the base station, and may perform SL LBT failure recovery or SL LBT failure declaration operations.

[0358] -sl-lbt-FailureInstanceMaxCount: When the UE detects a SL LBT failure, it may increment the SL_LBT_COUNTER by 1, and if it detects as many SL LBT failures as sl-lbt-FailureInstanceMaxCount until the sl-lbt-FailureDetectionTimer expires, it may declare a SL LBT failure.

[0359] -sl-lbt-FailureDetectionTimer: A timer that is started when the UE detects a SL LBT failure, and the UE may perform the SL LBT failure recovery procedure while the timer is running.

[0360] For example, when the MAC layer of the UE (or sending UE) receives an SL LBT failure event from the PHY layer (i.e., when the UE detects an SL LBT failure), it may start the sl-lbt-FailureDetectionTimer and simultaneously increment the SL_LBT_COUNTER by 1. However, for example, when it configures multiple unicast links and performs unicast communication, if the MAC layer of the UE receives an SL LBT failure event from the PHY layer, the MAC layer of the UE may not be able to distinguish which of the multiple unicast links (or multiple PC5 RRC connections) has the SL LBT failure event. Therefore, in the present disclosure, a UE operation is proposed that allows the MAC layer of the UE to transmit the PC5 link identifier or the identifier information of the PC5 RRC connection to the PHY layer when configuring a unicast link or a PC5 RRC connection. In addition, in the present disclosure, an operation is proposed that allows the PHY layer of the UE to report the SL LBT failure event of each PC5 unicast link or PC5 RRC connection (distinguished by the PC5 link identifier or the identifier of the PC5 RRC connection) to the MAC layer. That is, for example, when the PHY layer of the UE detects an SL LBT failure of a PC5 unicast link or a PC5 RRC connection (distinguished by a PC5 link identifier or an identifier of the PC5 RRC connection), it may report the SL LBT failure event together with the PC5 link identifier or the identifier of the PC5 RRC connection to the MAC layer. In addition, for example, the UE may perform an SL LBT recovery procedure during an sl-lbt-FailureDetectionTimer operation for each unicast link. That is, for example, when the UE detects an SL LBT failure again during an sl-lbt-FailureDetectionTimer operation (an SL LBT failure event reported for each PC5 link identifier or an identifier of the PC5 RRC connection), it may increment the SL_LBT_COUNTER of the corresponding unicast link by 1. For example, if the SL_LBT_COUNTER incremented by SL LBT detection does not reach a threshold number (e.g., sl-lbt-FailureInstanceMaxCount) before the sl-lbt-FailureDetectionTimer expires, the UE may regard the SL LBT failure as recovered and may continue normal sidelink communications by using the sidelink grant in use.However, for example, if the SL_LBT_COUNTER incremented by SL LBT failure detection reaches a threshold number (e.g., sl-lbt-FailureInstanceMaxCount) before the sl-lbt-FailureDetectionTimer expires, the UE may declare a persistent SL LBT failure for the corresponding unicast link. For example, if the UE declares a persistent SL LBT failure in unicast communication, it may declare a SL radio link failure (RLF) for the corresponding unicast link, and may release the PC5 RRC connection associated with the unicast link for which the SL RLF is declared. And, for example, by reporting a PC5 link identifier associated with the released PC5 RRC connection to a higher layer (e.g., a V2X layer), the higher layer may release the PC5 unicast link. And, for example, if the UE declares a SL RLF due to a persistent SL LBT failure, it may transmit to the base station a destination address (e.g., a destination layer 2 (L2) ID or a PC5 link identifier) ​​where the SL RLF occurred and a cause of the SL RLF that occurred due to the persistent SL LBT failure (e.g., a persistent SL LBT failure based on the SL RLF).

[0361] A channel specified in the present disclosure may be applied by replacing a carrier, a resource block (RB) set of a specific carrier, or a frequency band.

[0362] For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured (differently or independently) for each SL channel access priority category (CAPC). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured (differently or independently) for each SL-LBT type (e.g., type 1LBT, type 2A LBT, type 2B LBT, type 2C LBT). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be specifically (or differently or independently) configured based on whether frame-based LBT is applied. For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be specifically (or differently or independently) configured based on whether load-based LBT is applied.

[0363] For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each resource pool (differently or independently). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each congestion level (differently or independently). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each service priority (differently or independently). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each service type (differently or independently). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each QoS requirement (e.g., latency, reliability) (differently or independently). For example, whether to apply (some) of the methods / rules and / or related parameters (e.g., thresholds) proposed in the present disclosure may be configured for each PQI (5G QoS Identifier (5QI) for PC5) (differently or independently). For example, whether to apply (some) of the proposed methods / rules and / or related parameters (e.g., thresholds) of the present disclosure may be configured (differently or independently) for each service type (e.g., periodic generation or non-periodic generation). For example, whether to apply (some) of the proposed methods / rules and / or related parameters (e.g., thresholds) of the present disclosure may be configured (differently or independently) for each SL transmission resource allocation mode (e.g., mode 1 or mode 2). For example, whether to apply (some) of the proposed methods / rules and / or related parameters (e.g., thresholds) of the present disclosure may be configured (differently or independently) for each Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).

[0364] For example, depending on whether PUCCH configuration is supported (for example, when PUCCH resources are configured or when PUCCH resources are not configured), whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be specifically (or differently or independently) configured. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each resource pool (for example, a resource pool with PSFCH or a resource pool without PSFCH) (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each service / packet type (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each service / packet priority (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each QoS requirement (for example, URLLC / EMBB service, reliability, delay) (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each PQI (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each PFI (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each broadcast type (e.g., unicast, multicast, broadcast) (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each (resource pool) congestion level (e.g., CBR) (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured for each SL HARQ feedback option (e.g., only NACK feedback, ACK / NACK feedback) (differently or independently). For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured specifically (or differently or independently) for HARQ feedback-enabled MAC PDU transmission. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured specifically (or differently or independently) for HARQ feedback-disabled MAC PDU transmission. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be configured specifically (or differently or independently) according to whether a PUCCH-based SL HARQ feedback report operation is configured. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be configured specifically (or differently or independently) for preemption or depending on whether a resource reselection based on preemption is performed. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be configured specifically (or differently or independently) for reassessment or depending on whether a resource reselection based on reassessment is performed.For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured (differently or independently) for each (L2 or L1) (source and / or destination) identifier. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured (differently or independently) for each (L2 or L1) (combination of source ID and destination ID) identifier. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured (differently or independently) for each (L2 or L1) (combination of source ID and destination ID pair and broadcast type) identifier. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured (differently or independently) for each direction of the source layer ID and target layer ID pair. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured (differently or independently) for each PC5 RRC connection / link. For example, whether the proposed rules and / or related parameter configuration values ​​of the present disclosure are applied can be configured specifically (or differently or independently) depending on whether SL DRX is performed. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be specifically (or differently or independently) configured depending on whether SL DRX is supported. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be specifically (or differently or independently) configured for each SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be specifically (or differently or independently) configured for the case of performing (non-) periodic resource reservation. For example, whether to apply the proposed rules and / or related parameter configuration values ​​of the present disclosure may be specifically (or differently or independently) configured for each Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).

[0365] It is proposed that the rules (and / or related parameter configuration values) proposed in the present disclosure may also be applied to mmWave SL operations.

[0366] According to various embodiments of the present disclosure, when an LBT failure occurs, a UE performing communication in the SL-U may send LBT failure report information to a peer UE, and in this case, information related to the RB set where the LBT failure occurs may be included in the LBT failure report information. The peer UE may perform LBT on a different RB set excluding the RB set where the LBT failure occurs based on the LBT failure report information. By doing so, it is possible to prevent the peer UE from performing resource selection on the RB set where the LBT failure occurs. Alternatively, by doing so, the peer UE may perform resource selection on resources of the RB set excluding the LBT failure. Alternatively, by doing so, it is possible to prevent the power of the peer UE from being consumed unnecessarily, and to prevent unnecessary delays in communications on the SL-U.

[0367] According to various embodiments of the present disclosure, the UE can perform LBT failure counting independently by message type, and can exclude the case of transmission failure due to LBT failure from the DTX counter used for RLF operation. By doing so, even if the UE fails to transmit due to LBT failure, if the channel is in a good condition, the value of the DTX counter may not be incremented, and unnecessary RLF operation may be prevented.

[0368] Fig.19 A method for performing wireless communication by a first device according to an embodiment of the present disclosure is shown. Fig.19 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0369] refer to Fig.19 In step S1910, the first device may obtain information related to a plurality of resource block (RB) sets. In step S1920, the first device may perform listen before talk (LBT). In step S1930, the first device may send first LBT failure report information to the second device based on the LBT failure for the first RB set.

[0370] For example, the first LBT failure report information may include information related to the first RB set. For example, resource selection of the second device may be performed on a RB set excluding the first RB set.

[0371] For example, based on the success of LBT for the second RB set, the first device may send first LBT failure report information to the second device on the second RB set.

[0372] In addition, for example, the first device may send a physical sidelink shared channel (PSSCH) to the second device based on the success of LBT for the second RB set, and may determine whether the failure to receive a physical sidelink feedback channel (PSFCH) from the second device is due to the failure of LBT of the second device. For example, based on determining that the LBT of the second device has failed, the discontinuous transmission (DTX) count may not be incremented. For example, determining that the LBT of the second device has failed may be based on information related to the channel state, and the information related to the channel state may include channel busy rate (CBR) information obtained by the first device. For example, determining that the LBT of the second device has failed may be based on second LBT failure report information received by the first device from the second device. For example, based on the information related to the maximum count of LBT failure instances for PSFCH being included in the second LBT failure report information, the DTX count may not be incremented by the value of the maximum count of LBT failure instances for PSFCH.

[0373] For example, an LBT failure recovery configuration including information related to an LBT counter and information related to a maximum count of LBT failure instances may be configured to the first device, and the LBT failure recovery configuration may be configured for each channel type or signal type.

[0374] For example, a first LBT failure recovery configuration including information related to an LBT counter for a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH) and information related to a maximum count of LBT failure instances for the PSCCH or PSSCH, a second LBT failure recovery configuration including information related to an LBT counter for a physical sidelink feedback channel (PSFCH) and information related to a maximum count of LBT failure instances for the PSFCH, and a third LBT failure recovery configuration including information related to an LBT counter for a sidelink synchronization signal block (S-SSB) and information related to a maximum count of LBT failure instances for the S-SSB may be independently configured to the first device. For example, the value of the maximum count of LBT failure instances for the PSCCH or PSSCH may be greater than (i) the value of the maximum count of LBT failure instances for the PSFCH and (ii) the value of the maximum count of LBT failure instances for the S-SSB. For example, the value of the maximum count of LBT failure instances for PSCCH or PSSCH may be smaller than (i) the value of the maximum count of LBT failure instances for PSFCH and (ii) the value of the maximum count of LBT failure instances for S-SSB.

[0375] The proposed method can be applied to the devices according to various embodiments of the present invention. First, the processor 102 of the first device 100 can control the transceiver 106 to obtain information related to multiple resource block (RB) sets. And, the processor 102 of the first device 100 can perform listen before talk (LBT). And, the processor 102 of the first device 100 can control the transceiver 106 to send first LBT failure report information to the second device based on the LBT failure for the first RB set.

[0376] According to one embodiment of the present disclosure, a first device configured to perform wireless communication is provided. The first device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the first device to perform operations including the following items: obtaining information related to multiple resource block (RB) sets; performing listen before talk (LBT); based on the failure of LBT for the first RB set, sending first LBT failure report information to the second device.

[0377] According to one embodiment of the present disclosure, a processing device configured to control a first device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the first device to perform operations including the following items: obtaining information related to multiple resource block (RB) sets; performing listen before talk (LBT); based on the failure of LBT for the first RB set, sending first LBT failure report information to the second device.

[0378] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, upon being executed, cause a first device to perform operations including: obtaining information related to a plurality of resource block (RB) sets; performing listen before talk (LBT); and, upon failure of LBT for a first RB set, sending first LBT failure report information to a second device.

[0379] Fig. 20 A method for performing wireless communication by a second device according to an embodiment of the present disclosure is shown. Fig. 20 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0380] refer to Fig. 20In step S2010, the second device may obtain information related to a plurality of resource block (RB) sets. In step S2020, the second device may receive listen-before-talk (LBT) failure report information from the first device. In step S2020, the second device may perform resource selection on resources excluding the RB set for which LBT has failed based on the LBT failure report information.

[0381] The proposed method can be applied to the devices according to various embodiments of the present invention. First, the processor 202 of the second device 200 can control the transceiver 206 to obtain information related to multiple resource block (RB) sets. And, the processor 202 of the second device 200 can control the transceiver 206 to receive listen-before-talk (LBT) failure report information from the first device. And, the processor 202 of the second device 200 can perform resource selection on the resources of the RB set excluding the LBT failure based on the LBT failure report information.

[0382] According to one embodiment of the present disclosure, a second device configured to perform wireless communication is provided. The second device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the second device to perform operations including the following items: obtaining information related to multiple resource block (RB) sets; receiving listen-before-talk (LBT) failure report information from the first device; and performing resource selection on resources excluding the RB set for which LBT has failed based on the LBT failure report information.

[0383] According to one embodiment of the present disclosure, a processing device configured to control a second device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions are executed by the at least one processor to cause the second device to perform operations including the following items: obtaining information related to a plurality of resource block (RB) sets; receiving listen-before-talk (LBT) failure report information from a first device; and performing resource selection on resources excluding the RB set for which the LBT has failed based on the LBT failure report information.

[0384] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, upon being executed, cause a second device to perform operations including: obtaining information related to a plurality of resource block (RB) sets; receiving listen-before-talk (LBT) failure report information from a first device; and performing resource selection on resources excluding the RB set for which the LBT has failed based on the LBT failure report information.

[0385] Various embodiments of the present disclosure may be combined with each other.

[0386] Hereinafter, devices to which various embodiments of the present disclosure can be applied will be described.

[0387] The various descriptions, functions, processes, proposals, methods and / or operational flows of the present disclosure described in this document may be applied to, but not limited to, various fields requiring wireless communication / connection between devices (e.g., 5G).

[0388] Hereinafter, a description will be given in more detail with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise described, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0389] Fig.19 A communication system 1 according to an embodiment of the present disclosure is shown. Fig.19 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0390] Reference Fig.19 , a communication system 1 to which various embodiments of the present disclosure are applied includes a wireless device, a base station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or long term evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, a vehicle (100b-1, 100b-2), an extended reality (XR) device (100c), a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head mounted devices (HMD), head up displays (HUD) installed in vehicles, televisions, smart phones, computers, wearable devices, home appliance devices, digital signage, vehicles, robots, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device (200a) may operate as a BS / network node relative to other wireless devices.

[0391] Here, in addition to LTE, NR and 6G, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may also include a narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology, and may be implemented as a standard such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may perform communication based on LTE-M technology. In this case, as an example, LTE-M technology may be an example of LPWAN, and may be referred to as various names including enhanced machine type communication (eMTC), etc. For example, LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine type communication and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may include at least one of Bluetooth, a low power wide area network (LPWAN), and ZigBee considering low power communication, and is not limited to the above names. As an example, the ZigBee technology may generate a personal area network (PAN) related to small / low power digital communication based on various standards including IEEE 802.15.4, etc., and may be referred to as various names.

[0392] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. The AI ​​technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0393] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation and resource mapping / demapping) and at least a portion of the resource allocation process can be performed based on various proposals of the present disclosure.

[0394] Fig. 20 A wireless device according to an embodiment of the present disclosure is shown. Fig. 20 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0395] Reference Fig. 20 , the first wireless device 100 and the second wireless device 200 may transmit radio signals through various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.19 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x} in.

[0396] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally further include one or more transceivers 106 and / or one or more antennas (antenna units) 108. The (one or more) processors 102 may control the (one or more) memories 104 and / or the (one or more) transceivers 106, and may be configured to implement the descriptions, functions, processes, proposals, methods and / or operation flows disclosed in this document. For example, the (one or more) processors 102 may process the information in the (one or more) memories 104 to generate first information / signals, and then send a radio signal including the first information / signals through the (one or more) transceivers 106. The (one or more) processors 102 may receive a radio signal including second information / signals through the transceiver 106, and then store the information obtained by processing the second information / signals in the (one or more) memories 104. The (one or more) memories 104 may be connected to the (one or more) processors 102, and may store various information related to the operation of the (one or more) processors 102. For example, (one or more) memories 104 may store software code including commands for executing part or all of the processing controlled by (one or more) processors 102 or for executing the descriptions, functions, processes, proposals, methods and / or operational flows disclosed in this document. Here, (one or more) processors 102 and (one or more) memories 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). (One or more) transceivers 106 may be connected to (one or more) processors 102 and send and / or receive radio signals through (one or more) antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. (One or more) transceivers 106 may be used interchangeably with (one or more) radio frequency (RF) units. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0397] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally further include one or more transceivers 206 and / or one or more antennas 208. The (one or more) processors 202 may control the (one or more) memories 204 and / or the (one or more) transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods and / or operation flows disclosed in this document. For example, the (one or more) processors 202 may process the information in the (one or more) memories 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the (one or more) transceivers 206. The (one or more) processors 202 may receive a radio signal including a fourth information / signal through the (one or more) transceivers 106, and then store the information obtained by processing the fourth information / signals in the (one or more) memories 204. The (one or more) memories 204 may be connected to the (one or more) processors 202, and may store various information related to the operation of the (one or more) processors 202. For example, (one or more) memories 204 may store software code including commands for executing part or all of the processing controlled by (one or more) processors 202 or for executing the descriptions, functions, processes, proposals, methods and / or operational flows disclosed in this document. Here, (one or more) processors 202 and (one or more) memories 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). (One or more) transceivers 206 may be connected to (one or more) processors 202 and transmit and / or receive radio signals through (one or more) antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. (One or more) transceivers 206 may be used interchangeably with (one or more) RF units. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0398] Below, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the description, function, process, proposal, method, and / or operation flow disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the description, function, process, proposal, method, and / or operation flow disclosed in this document. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the description, function, process, proposal, method, and / or operation flow disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 can receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operating procedures disclosed in this document.

[0399] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flows disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flows disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204, thereby being driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flows disclosed in this document may be implemented using software or firmware in the form of code, commands, and / or command sets.

[0400] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and may store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be composed of read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cash memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0401] One or more transceivers 106 and 206 may send user data, control information, and / or radio signals / channels mentioned in the method and / or operation flow of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the description, function, process, proposal, method, and / or operation flow disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202, and may send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flows disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0402] Fig.21 A signal processing circuit for transmitting a signal according to an embodiment of the present disclosure is shown. Fig.21 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0403] Reference Fig.21 The signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. Fig.21 Operation / function, not limited to Fig. 20 The processor (102, 202) and / or transceiver (106, 206) of Fig. 20 The processor (102, 202) and / or the transceiver (106, 206) are implemented Fig.21 For example, you can Fig. 20 The processor (102, 202) implements blocks 1010 to 1060. Alternatively, Fig. 20 The processor (102, 202) implements blocks 1010 to 1050 and can be implemented by Fig. 20 The transceiver (106, 206) is used to implement box 1060.

[0404] Can be through Fig.21 The signal processing circuit 1000 converts the codeword into a radio signal. Herein, the codeword is a coded bit sequence of an information block. The information block may include a transport block (e.g., UL-SCH transport block, DL-SCH transport block). The radio signal may be transmitted through various physical channels (e.g., PUSCH and PDSCH).

[0405] Specifically, the codeword can be converted into a scrambled bit sequence by the scrambler 1010. The scrambling sequence for scrambling can be generated based on an initial value, and the initial value can include the ID information of the wireless device. The scrambled bit sequence can be modulated into a modulation symbol sequence by the modulator 1020. The modulation scheme may include pi / 2-binary phase shift keying (pi / 2-BPSK), m-phase shift keying (m-PSK) and m-quadrature amplitude modulation (m-QAM). The complex modulation symbol sequence can be mapped to one or more transmission layers by the layer mapper 1030. The modulation symbol of each transmission layer can be mapped (precoded) to (one or more) corresponding antenna ports by the precoder 1040. The output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 with the N*M precoding matrix W. Here, N is the number of antenna ports and M is the number of transmission layers. The precoder 1040 can perform precoding after performing transform precoding (e.g., DFT) for the complex modulation symbol. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

[0406] The resource mapper 1050 may map the modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include multiple symbols in the time domain (e.g., CP-OFDMA symbols and DFT-s-OFDMA symbols) and multiple subcarriers in the frequency domain. The signal generator 1060 may generate a radio signal from the mapped modulation symbols, and the generated radio signal may be sent to other devices through each antenna. To this end, the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), and an up-converter.

[0407] Can be used with Fig.21 The signal processing process for the signal received in the wireless device is configured in a manner opposite to the signal processing process (1010-1060) of the wireless device. Fig. 20 100, 200) can receive a radio signal from the outside through an antenna port / transceiver. The received radio signal can be converted into a baseband signal by a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Next, the baseband signal can be restored to a codeword through a resource demapping process, a post-coding process, a demodulation processor, and a descrambling process. The codeword can be restored to the original information block by decoding. Therefore, a signal processing circuit (not illustrated) for receiving a signal may include a signal restorer, a resource demapper, a post-encoder, a demodulator, a descrambler, and a decoder.

[0408] Fig. 22 Another example of a wireless device according to an embodiment of the present disclosure is shown. The wireless device can be implemented in various forms according to use cases / services (see Fig.19 ). Fig. 22 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0409] Reference Fig. 22 , the wireless device (100, 200) may correspond to Fig. 20 The wireless devices (100, 200) may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices (100, 200) may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and (one or more) transceivers 114. For example, the communication circuit 112 may include Fig. 20 One or more processors (102, 202) and / or one or more memories (104, 204) of the present invention. For example, the transceiver(s) 114 may include Fig. 20The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 can control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 can send the information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store the information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0410] The additional component 140 may be configured in various ways depending on the type of the wireless device. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be implemented in the following forms without limitation: a robot ( Fig.19 100a), vehicles ( Fig.19 100b-1 and 100b-2), XR devices ( Fig.19 100c), handheld device ( Fig.19 100d), household appliances ( Fig.19 100e), IoT devices ( Fig.19 100f), digital broadcast terminal, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.19 400), BS( Fig.19 200), network nodes, etc. Depending on the use case / service, the wireless device can be used in a mobile or fixed place.

[0411] exist Fig. 22In the wireless device (100, 200), all the various elements, components, units / parts and / or modules in the wireless device (100, 200) can be connected to each other through a wired interface, or at least part of them can be connected wirelessly through the communication unit 110. For example, in each of the wireless devices (100, 200), the control unit 120 and the communication unit 110 can be connected by wire, and the control unit 120 and the first unit (e.g., 130, 140) can be connected wirelessly through the communication unit 110. Each element, component, unit / part and / or module in the wireless device (100, 200) can also include one or more elements. For example, the control unit 120 can be constructed by a set of one or more processors. As an example, the control unit 120 can be constructed by a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. As another example, the memory unit 130 can be constructed by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0412] Hereinafter, the implementation will be described in detail with reference to the accompanying drawings. Fig.18 .

[0413] Fig.23 A handheld device based on an embodiment of the present disclosure is shown. The handheld device may include a smart phone, a smart board, a wearable device (e.g., a smart watch or smart glasses), or a portable computer (e.g., a notebook). The handheld device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT). Fig.23 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0414] Reference Fig.23 , the handheld device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an I / O unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to Fig. 22 Frame 110 to 130 / 140.

[0415] The communication unit 110 may send and receive signals (e.g., data signals and control signals) to and from other wireless devices or BSs. The control unit 120 may perform various operations by controlling the constituent elements of the handheld device 100. The control unit 120 may include an application processor (AP). The memory unit 130 may store data / parameters / programs / codes / commands required to drive the handheld device 100. The memory unit 130 may store input / output data / information. The power supply unit 140a may supply power to the handheld device 100 and include a wired / wireless charging circuit, a battery, etc. The interface unit 140b may support the connection of the handheld device 100 to other external devices. The interface unit 140b may include various ports (e.g., audio I / O ports and video I / O ports) for connecting to external devices. The I / O unit 140c may input or output video information / signals, audio information / signals, data and / or information input by a user. The I / O unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker and / or a tactile module.

[0416] For example, in the case of data communication, the I / O unit 140c can obtain information / signals (e.g., touch, text, voice, image, or video) input by the user, and the obtained information / signals can be stored in the memory unit 130. The communication unit 110 can convert the information / signals stored in the memory into radio signals, and directly send the converted radio signals to other wireless devices or to the BS. The communication unit 110 can receive radio signals from other wireless devices or BSs, and then restore the received radio signals to the original information / signals. The restored information / signals can be stored in the memory unit 130, and can be output as various types (e.g., text, voice, image, video, or tactile) through the I / O unit 140.

[0417] Fig.24 A vehicle or autonomous vehicle based on an embodiment of the present disclosure is shown. The vehicle or autonomous vehicle can be implemented by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc. Fig.24 The embodiments of the present invention can be combined with various embodiments of the present disclosure.

[0418] Reference Fig.24 , the vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig. 22 Frame 110 / 130 / 140.

[0419] The communication unit 110 may send and receive signals (e.g., data signals and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a may cause the vehicle or autonomous vehicle 100 to travel on the road. The drive unit 140a may include an engine, a motor, a transmission system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous vehicle 100, and may include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire vehicle status, external environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously driving along a determined path, a technology for driving by automatically setting a path when a destination is set, and the like.

[0420] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the acquired data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed / direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically / periodically acquire the most recent traffic information data from an external server and acquire surrounding traffic information data from adjacent vehicles. In the middle of autonomous driving, the sensor unit 140c may acquire vehicle status and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and driving plan based on the newly acquired data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving path, and / or driving plan to an external server. The external server may predict traffic information data using AI technology, etc. based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0421] The claims in this specification may be combined in various ways. For example, the technical features in the method claims of this specification may be combined to be implemented or performed in a device, and the technical features in the device claims may be combined to be implemented or performed in a method. In addition, the technical features in (one or more) method claims and (one or more) device claims may be combined to be implemented or performed in a device. In addition, the technical features in (one or more) method claims and (one or more) device claims may be combined to be implemented or performed in a method.

Claims

1. A method for performing wireless communication by a first device, the method comprising: Obtaining information related to a plurality of resource block RB sets; Implement Listen Before You Talk LBT; Based on the LBT failure for the first RB set, first LBT failure report information is sent to the second device.

2. The method according to claim 1, wherein: The first LBT failure report information includes information related to the first RB set.

3. The method according to claim 2, wherein: The resource selection by the second device is performed on a set of RBs excluding the first set of RBs.

4. The method according to claim 1, wherein: Based on the LBT success for the second RB set, the first device sends the first LBT failure report information to the second device on the second RB set.

5. The method according to claim 1, further comprising: Based on the LBT success for the second RB set, sending a physical sidelink shared channel PSSCH to the second device; as well as determining whether a failure to receive a physical sidelink feedback channel (PSFCH) from the second device is due to a failure of an LBT of the second device, Wherein, based on the determination that the LBT of the second device has failed, a discontinuous transmission DTX count is not incremented.

6. The method according to claim 5, wherein: The determination that the LBT of the second device has failed is based on information related to a channel state, and The information related to the channel status includes channel busy rate CBR information obtained by the first device.

7. The method according to claim 5, wherein: The determination that the LBT of the second device has failed is based on second LBT failure report information received by the first device from the second device.

8. The method according to claim 7, wherein: Based on the information related to the maximum count of LBT failure instances for the PSFCH being included in the second LBT failure report information, the DTX count does not increase the value of the maximum count of LBT failure instances for the PSFCH.

9. The method according to claim 8, wherein: The value of the maximum count of LBT failure instances for the PSFCH is less than the DTX threshold.

10. The method according to claim 1, wherein: An LBT failure recovery configuration including information related to an LBT counter and information related to a maximum count of LBT failure instances is configured to the first device, and Wherein, the LBT failure recovery configuration is configured for each channel type or signal type.

11. The method according to claim 1, wherein: A first LBT failure recovery configuration including information related to an LBT counter for a physical sidelink control channel PSCCH or a physical sidelink shared channel PSSCH and information related to a maximum count of LBT failure instances for the PSCCH or the PSSCH, a second LBT failure recovery configuration including information related to an LBT counter for a physical sidelink feedback channel PSFCH and information related to a maximum count of LBT failure instances for the PSFCH, and a third LBT failure recovery configuration including information related to an LBT counter for a sidelink synchronization signal block S-SSB and information related to a maximum count of LBT failure instances for the S-SSB are independently configured to the first device.

12. The method according to claim 11, wherein: The value of the maximum count of LBT failure instances for the PSCCH or the PSSCH is greater than i) the value of the maximum count of LBT failure instances for the PSFCH and ii) the value of the maximum count of LBT failure instances for the S-SSB.

13. The method according to claim 11, wherein: The value of the maximum count of LBT failure instances for the PSCCH or the PSSCH is less than i) the value of the maximum count of LBT failure instances for the PSFCH and ii) the value of the maximum count of LBT failure instances for the S-SSB.

14. A first device adapted to perform wireless communication, the first device comprising: at least one transceiver; at least one processor; as well as at least one memory connected to the at least one processor and storing instructions that upon being executed, cause the first device to perform operations including: Obtaining information related to a plurality of resource block RB sets; Implement Listen Before You Talk LBT; Based on the LBT failure for the first RB set, first LBT failure report information is sent to the second device.

15. A processing device adapted to control a first device to perform wireless communication, the processing device comprising: at least one processor; as well as At least one memory, the at least one memory being connected to the at least one processor and storing instructions, the instructions, upon being executed, causing the at least one processor to perform operations comprising: Obtaining information related to a plurality of resource block RB sets; Implement Listen Before You Talk LBT; Based on the LBT failure for the first RB set, first LBT failure report information is sent to the second device.

16. A non-transitory computer-readable storage medium recording instructions, wherein when the instructions are executed, the first device performs operations including: Obtaining information related to a plurality of resource block RB sets; Implement Listen Before You Talk LBT; Based on the LBT failure for the first RB set, first LBT failure report information is sent to the second device.

17. A method for performing wireless communication by a second device, the method comprising: Obtaining information related to a plurality of resource block RB sets; receiving a listen-before-talk (LBT) failure report message from the first device; as well as Based on the LBT failure report information, resource selection is performed on resources excluding the RB set for which LBT has failed.

18. A second device adapted to perform wireless communication, the second device comprising: at least one transceiver; at least one processor; as well as at least one memory connected to the at least one processor and storing instructions that upon being executed, cause the second device to perform operations including: Obtaining information related to a plurality of resource block RB sets; receiving a listen-before-talk (LBT) failure report message from the first device; as well as Based on the LBT failure report information, resource selection is performed on resources excluding the RB set for which LBT has failed.

19. A processing device adapted to control a second device to perform wireless communication, the processing device comprising: at least one processor; as well as At least one memory, the at least one memory being connected to the at least one processor and storing instructions, the instructions, upon being executed, causing the at least one processor to perform operations comprising: Obtaining information related to a plurality of resource block RB sets; receiving a listen-before-talk (LBT) failure report message from the first device; as well as Based on the LBT failure report information, resource selection is performed on resources excluding the RB set for which LBT has failed.

20. A non-transitory computer-readable storage medium recording instructions, the instructions, when executed, causing a second device to perform operations comprising: Obtaining information related to a plurality of resource block RB sets; receiving a listen-before-talk (LBT) failure report message from the first device; as well as Based on the LBT failure report information, resource selection is performed on resources excluding the RB set for which LBT has failed.

Images