Method and apparatus for performing sidelink communication in unlicensed band

Abstract

A method of performing wireless communication by a first device and a device supporting the same are provided. The method may comprise the steps of: acquiring information related to a resource for a sidelink synchronization signal block (S-SSB); obtaining information on a first time domain for a first cyclic prefix extension (CPE) related to the S-SSB transmission; performing the first CPE during the first time domain prior to the S-SSB transmission; and performing the S-SSB transmission based on the resource.

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, as more and more communication devices require greater communication capacity, the demand for enhanced mobile broadband communication compared to previous radio access technology (RAT) is rising. Therefore, communication systems for reliability and delay-sensitive services or user equipment (UE) are discussed. And, the next generation radio access technology based on improved mobile broadband communication, massive machine type communication (MTC), ultra-reliable low latency communication (URLLC), etc. can be called new radio access technology (RAT) or new radio (NR). Summary of the invention

[0004] Technical Solution

[0005] In an embodiment, a method for performing wireless communication by a first device is provided. The method may include: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing a first CPE during the first time domain before the S-SSB transmission; and performing S-SSB transmission based on the resources.

[0006] In an embodiment, a first device adapted 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, the instructions being executed by the at least one processor so that the first device performs operations including: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing a first CPE during a first time domain before S-SSB transmission; and performing S-SSB transmission based on the resources.

[0007] In an embodiment, a processing device suitable for controlling 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, the instructions being executed by the at least one processor so that the first device performs operations including the following items: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing a first CPE during the first time domain before the S-SSB transmission; and performing S-SSB transmission based on the resources.

[0008] In an embodiment, a non-transitory computer-readable storage medium storing instructions is provided. When the instructions are executed, the first device may perform operations including: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing a first CPE during the first time domain before the S-SSB transmission; and performing S-SSB transmission based on the resources. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0011] Figure 3 The structure of the NR system according to the 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 structure of the time slot of the NR frame based on the embodiment of the present disclosure is shown.

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

[0016] 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.

[0017] Fig. 9 Three cast types based on embodiments of the present disclosure are shown.

[0018] Fig.10 Interleaved RBs based on an embodiment of the present disclosure are shown.

[0019] Fig.11 A process in which a UE performs SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0020] Fig.12 is a diagram used to explain the problems caused by different CPEs.

[0021] Fig.13 is a diagram used to explain the problems caused by different CPEs.

[0022] Fig.14 A gap of UE-common LBT operation before PSFCH resources (eg, symbols) based on an embodiment of the present disclosure is shown.

[0023] Fig.15 A gap of UE common LBT operation before SL SSB resources (eg, time slots) based on an embodiment of the present disclosure is shown.

[0024] Fig.16 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0025] Fig.17 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0026] Fig.18 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0027] Fig.19 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0028] Fig. 20A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0029] Fig.21 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown.

[0030] Fig. 22 A method for a first device to perform wireless communication based on an embodiment of the present disclosure is shown.

[0031] Fig.23 A method for a second device to perform wireless communication based on an embodiment of the present disclosure is shown.

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

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

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

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

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

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

[0038] 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".

[0039] 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".

[0040] 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".

[0041] 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".

[0042] 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".

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

[0044] The technical features respectively described in one drawing in the present disclosure may be implemented separately or may be implemented simultaneously.

[0045] In the present disclosure, the higher layer parameter may be a parameter configured, preconfigured or predefined for the UE. For example, the base station or the network may send the higher layer parameter to the UE. For example, the higher layer parameter may be sent via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0046] 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.

[0047] 5G NR is a subsequent technology of LTE-A corresponding to a new mobile communication system with characteristics such as high performance, low latency, and high availability. 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 bands above 24 GHz (millimeter waves).

[0048] The 6G (wireless communication) system has objectives such as (i) very high data rates per device, (ii) very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT devices, (vi) ultra-reliable connectivity, and (vii) networked intelligence with machine learning capabilities. The vision of the 6G system may include four aspects such as intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system may meet the requirements shown in Table 1 below. That is, Table 1 shows the requirements of the 6G system.

[0049] [Table 1]

[0050]

[0051]

[0052] The 6G system may have key factors such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), massive machine type communications (mMTC), AI-integrated communications, tactile Internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0053] Figure 1 A communication structure that can be provided in a 6G system based on 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.

[0054] The 6G system will have 50 times higher simultaneous wireless communication connectivity than the 5G wireless communication system. URLLC, which is the main function of 5G, will become a more important technology by providing an end-to-end latency of less than 1ms in 6G communication. Unlike the frequently used domain spectrum efficiency, the 6G system can have better volume spectrum efficiency. The 6G system can provide advanced battery technology for energy harvesting and very long battery life, and therefore mobile devices may not need to be charged separately in the 6G system. In 6G, new network characteristics may be as follows.

[0055] -Satellite-integrated network: To provide global mobile constellations, 6G will be integrated with satellites. Integrating ground waves, satellites, and public networks into one wireless communication system could be very important for 6G.

[0056] -Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is innovative, and wireless evolution may be updated from "connected things" to "connected intelligence." AI can be applied in every step of the communication process (or every signal processing process described below).

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

[0058] -Ubiquitous hyper-3D connectivity: Access to networks and core network functions from drones and very low earth orbit satellites will establish hyper-3D connectivity in 6G ubiquity.

[0059] Among the new network features of 6G, several general requirements are as follows.

[0060] - Small cell network: The concept of small cell network is introduced to improve the received signal quality as a result of the improvement of the throughput, energy efficiency and spectrum efficiency of the cellular system. Therefore, the small cell network is an essential feature of the 5G and beyond 5G (5GB) communication system. Therefore, the 6G communication system also adopts the characteristics of the small cell network.

[0061] -Ultra-dense heterogeneous network: Ultra-dense heterogeneous network will be another important feature of 6G communication system. Multi-tier network composed of heterogeneous networks improves overall QoS and reduces costs.

[0062] - High Capacity Backhaul: Backhaul connections are characterized by high capacity backhaul networks in order to support high capacity traffic. High speed optical fiber and free space optics (FSO) systems can be possible solutions to this problem.

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

[0064] -Software and virtualization: Software and virtualization are two important functions that are the basis of the design process in 5GB networks in order to ensure flexibility, reconfigurability and programmability.

[0065] The core implementation technology of the 6G system is described below.

[0066] - Artificial Intelligence (AI): As the most important and newly introduced technology in 6G system is AI. AI is not involved in 4G system. 5G system will support partial or very limited AI. However, 6G system will support AI for full automation. Advances in machine learning will create smarter networks for real-time communication in 6G. When AI is introduced into communication, real-time data transmission can be simplified and improved. AI can use countless analyses to determine methods to perform complex target tasks. That is, AI can increase efficiency and reduce processing delays. Time-consuming operations such as switching, network selection, and resource scheduling can be performed instantly by AI. AI can also play an important role in M2M, machine to human, and human to machine. In addition, AI may be instant communication in brain-computer interface (BCI). AI-based communication systems can be supported by metamaterials, smart structures, smart networks, smart devices, smart cognitive radios, self-maintaining wireless networks, and machine learning.

[0067] -THz (THz) communication: Data rates can be increased by increasing bandwidth. This can be achieved by using sub-TH communications with wide bandwidth and applying advanced massive MIMO technology. THz waves are called submillimeter radiation, generally indicating a frequency band between 0.1THz and 10THz with a corresponding wavelength in the range of 0.03mm to 3mm. The band range of 100GHz to 300GHz (sub-THz band) is considered to be the main part of the THz band for cellular communications. When the sub-THz band is added to the millimeter wave band, the 6G cellular communication capacity increases. 300GHz to 3THz of the defined THz band is in the far infrared (IR) band. The 300GHz to 3THz band is part of the optical band, but is located at the boundary of the optical band and immediately after the RF band. Therefore, the 300GHz to 3THz band has similarities with RF. Figure 2 An electromagnetic spectrum according to an embodiment of the present disclosure is shown. Figure 2 The embodiments of can be combined with various embodiments of the present disclosure. The main features of THz communication include (i) a wide bandwidth that can be used to support very high data rates; and (ii) high path loss occurs at high frequencies (highly directional antennas are essential). The narrow beamwidth generated in highly directional antennas reduces interference. The small wavelength of THz signals allows a larger number of antenna elements to be integrated with devices and BSs operating in this band. Therefore, advanced adaptive placement techniques that can overcome range limitations can be used.

[0068] - Massive MIMO technology (Large MIMO)

[0069] -Holographic Beamforming (HBF)

[0070] -Optical wireless technology

[0071] - Free Space Optical Backhaul Network (FSO Backhaul Network)

[0072] -Non-Terrestrial Network (NTN)

[0073] -Quantum communication

[0074] - No cellular communication

[0075] -Integration of wireless information and power transmission

[0076] -Integration of wireless communication and sensing

[0077] -Integrated access and backhaul network

[0078] -Big Data Analysis

[0079] - Reconfigurable smart surface

[0080] -Metaverse

[0081] -Blockchain

[0082] - Unmanned Aerial Vehicles (UAV): Unmanned aerial vehicles (UAV) or drones will be an important factor in 6G wireless communications. In most cases, UAV technology is used to provide high-speed data wireless connections. A base station entity is installed inside the UAV to provide cellular connectivity. UAVs have certain features not found in fixed base station infrastructure, such as easy deployment, strong line-of-sight links, and freedom of mobility control. During emergencies such as natural disasters, it is economically unfeasible to deploy terrestrial telecommunication infrastructure and sometimes it is impossible to provide services in turbulent environments. UAVs can easily handle such situations. UAVs will become a new paradigm in the field of wireless communications. This technology promotes the three basic requirements of wireless networks, such as eMBB, URLLC, and mMTC. UAVs can also be used for a variety of purposes, such as network connectivity improvement, fire detection, disaster emergency services, security and monitoring, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0083] -Autonomous driving (self-driving): In order to achieve perfect autonomous driving, it is necessary to inform each other of dangerous situations through communication between vehicles and vehicles, to check information such as parking information location and signal change time through communication between vehicles and infrastructure such as parking lots and / or traffic lights. Vehicle-to-Everything (V2X) is a core element for building an autonomous driving infrastructure, and is a technology for vehicles to communicate and share with various elements in the road, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I). In order to maximize the performance of autonomous driving and ensure high safety, high transmission speed and low latency technology are required. In addition, in order to directly control vehicles in dangerous situations and actively intervene in vehicle driving at a level beyond warning or guidance messages to the driver, autonomous driving is expected to be maximized in 6G, which has faster transmission speeds and lower latency than 5G, because the amount of information to be sent and received is large.

[0084] For the sake of clarity of the specification, 5G NR is mainly described, but the technical ideas according to the embodiments of the present disclosure are not limited thereto. Various embodiments of the present disclosure can also be applied to 6G communication systems.

[0085] Figure 3 The structure of the NR system according to 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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) shows a radio protocol stack for the user plane of Uu communication, and Figure 4 (b) in FIG. 5 shows a radio protocol stack of a 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 a radio protocol stack of a control plane for SL communication.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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).

[0094] 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).

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

[0096] 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.

[0097] 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.

[0098] 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_INACTIVE) state is additionally defined, and the UE in the RRC_INACTIVE state can maintain the connection with the core network and release its connection with the BS.

[0099] Data is sent from the network to the UE via a downlink transport channel. Examples of downlink transport channels include a broadcast channel (BCH) for sending system information and a downlink shared channel (SCH) for sending other user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be sent via a downlink SCH or may be sent via a separate downlink multicast channel (MCH). In addition, uplink transport 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 traffic or control messages.

[0100] 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.

[0101] 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.

[0102] Reference Figure 5In 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).

[0103] 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).

[0104] Table 2 shown below represents the number of symbols (N) per slot based on the SCS configuration (μ) in the case of using a normal CP or an 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 ).

[0105] [Table 2]

[0106]

[0107]

[0108] 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.

[0109] 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.

[0110] 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).

[0111] [Table 3]

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

[0113] 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).

[0114] [Table 4]

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

[0116] Figure 6 The structure of the time slot of the NR frame according to an 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.

[0117] 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. For example, in the case of extended CP, one time slot may include 12 symbols. Additionally, 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.

[0118] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 subcarriers). A bandwidth part (BWP) can be defined as multiple consecutive (physical) resource blocks ((P)RBs) in the frequency domain, and a BWP can correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N BWPs (e.g., 5 BWPs). Data communication can be performed via an activated BWP. Each element can be referred to as a resource element (RE) in a resource grid, and a complex symbol can be mapped to each element.

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

[0120] 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.

[0121] 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.For power saving, if the UE cannot detect downlink control information (DCI) during a designated period, the UE may switch the UE's active BWP to the default BWP.

[0122] In addition, a BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may send a SL channel or SL signal on a specific BWP, and a receiving UE may receive a SL channel or SL signal on a specific BWP. In a licensed carrier, the SL BWP may be defined separately from the Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS / network. For example, the UE may 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 may be activated in the carrier.

[0123] 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. Assume that Figure 7 In the embodiment, the number of BWPs is 3.

[0124] 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.

[0125] 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.

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

[0127] 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.

[0128] 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).

[0129] S-PSS, S-SSS, and PSBCH can 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 can 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 can exist within the (pre-) configured sidelink (SL) BWP. For example, the S-SSB can have a bandwidth of 11 resource blocks (SBs). For example, the PSBCH can exist across 11 RBs. In addition, the frequency position of the S-SSB can be (pre-) configured. Therefore, the UE does not have to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0130] 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.

[0131] For example, Figure 8 (a) in FIG. 1 shows UE operations related to LTE transmission mode 1 or LTE transmission mode 3. In addition, 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.

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

[0133] 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 S800, 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.

[0134] 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.

[0135] 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 DCI may be DCI format 3_0 or DCI format 3_1.

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

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

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

[0139] - 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.

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

[0141] -HARQ process number - 4 bits

[0142] - New data indicator - 1 bit

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

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

[0145] -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.

[0146] -PUCCH resource indicator - 3 bits

[0147] - 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.

[0148] - 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

[0149] - Filling bits if necessary

[0150] 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 preconfigured SL resources. For example, the configured SL resources or the preconfigured 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.

[0151] 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.

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

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

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

[0155] - Priority - 3 bits

[0156] - 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 higher layer parameter sl-MaxNumPerReserve is configured as 3, ceiling log2(N SL subChannel (N SL subChannel +1)(2N SL subChannel +1) / 6) bit

[0157] - Time Resource Assignment - 5 bits when the higher layer parameter sl-MaxNumPerReserve is configured with a value of 2; otherwise, 9 bits when the higher layer parameter sl-MaxNumPerReserve is configured with a value of 3

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

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

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

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

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

[0163] - Modulation and coding scheme - 5 bits

[0164] - 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

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

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

[0167] [Table 5]

[0168] 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

[0169] [Table 6]

[0170] Value of the Number of DMRS Ports field Antenna Port 0 1000 1 1000 and 1001

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

[0172] 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.

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

[0174] -HARQ process number - 4 bits

[0175] - New data indicator - 1 bit

[0176] - Redundancy version - 2 bits

[0177] - Source ID - 8 bits

[0178] -Destination ID - 16 bits

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

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

[0181] -CSI request - 1 bit

[0182] [Table 7]

[0183] The value of the playback 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

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

[0185] 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.

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

[0187] -HARQ process number - 4 bits

[0188] - New data indicator - 1 bit

[0189] - Redundancy version - 2 bits

[0190] - Source ID - 8 bits

[0191] -Destination ID - 16 bits

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

[0193] - Region ID - 12 digits

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

[0195] 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 resources, and the second UE may send the HARQ feedback to the first UE using the PSFCH resources.

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

[0197] Fig. 9 Three broadcast types according to embodiments of the present disclosure are shown. 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.

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

[0199] 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.

[0200] 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.

[0201] (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.

[0202] (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.

[0203] 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.

[0204] 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.

[0205] 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.

[0206] Hereinafter, the UE procedure for reporting HARQ-ACK on the sidelink will be described.

[0207] Can be in N PSSCH subch The UE is instructed by the SCI format of the scheduled PSSCH reception in one or more of the subchannels to send a PSFCH with HARQ-ACK information in response to the PSSCH reception. The UE provides HARQ-ACK information including ACK or NACK or only NACK.

[0208] The number of slots in the resource pool used for the PSFCH transmission opportunity resource period may be provided to the UE by sl-PSFCH-Period-r16. If this number is zero, PSFCH transmission from the UE in the resource pool is disabled. The UE expects that if kmod N PSFCH PSSCH = 0, then time slot t' k SL (0≤k <T' max ) has PSFCH transmission opportunity resources, where t' k SL is the time slot belonging to the resource pool, T' max is the number of time slots belonging to the resource pool within 10240 milliseconds, and N PSFCH PSSCH Provided by sl-PSFCH-Period-r16. The UE may be instructed by higher layers not to transmit PSFCH in response to PSSCH reception. If the UE receives PSSCH in a resource pool and the HARQ Feedback Enable / Disable Indicator field in the associated SCI Format 2-A or SCI Format 2-B has a value of 1, the UE provides HARQ-ACK information in the PSFCH transmission in the resource pool. The UE transmits PSFCH in the first slot after at least the number of slots provided by sl-MinTimeGapPSFCH-r16 of the resource pool that includes PSFCH resources and after the last slot of PSSCH reception.

[0209] sl-PSFCH-RB-Set-r16 provides the UE with the M in the resource pool for PSFCH transmission in the PRB of the resource pool. PSFCH PRB,set The number of subchannels N in the resource pool provided by sl-NumSubchannel subch and less than or equal to N PSFCH PSSCH The UE sets M to the number of PSSCH time slots associated with the PSFCH time slot. PRB,set PSFCH [(i+j·N PSFCH PSSCH )·M PSFCH subch,slot ,(i+1+j·N PSFCH PSSCH )·M PSFCH subch,slot -1] PRBs are allocated to slot i and subchannel j among the PSSCH slots associated with the PSFCH slot, where M PSFCH subch,slot =M PSFCH PRB,set / (N subch ·N PSFCH PSSCH ),0≤i <N PSFCH PSSCH ,0≤j <N subch , and the allocation starts in ascending order of i and continues in ascending order of j. The UE expects M PSFCH PRB,set YesN subch ·N PSFCH PSSCH multiples of.

[0210] The UE determines the number of PSFCH resources available for multiplexing HARQ-ACK information in PSFCH transmission as R PSFCH PRB,CS =N PSFCH type ·M PSFCH subch,slot ·N PSFCH CS , where N PSFCH CS is the number of cyclic shift pairs used for the resource pool, and based on higher layer instructions,

[0211] -N PSFCH type =1 and M PSFCH subch,slot PRBs are associated with the starting subchannel of the corresponding PSSCH

[0212] -N PSFCH type =N PSSCH subch And N PSSCH subch ·M PSFCH subch,slot PRBs and corresponding PSSCH N PSSCH subch One or more sub-channels are associated

[0213] PSFCH resources are first based on N PSFCH type ·M PSFCH subch,slot The PRB indices in the N PRBs are indexed in ascending order, and then PSFCH CS The cyclic shift pairs are indexed in ascending order of the cyclic shift pair indices.

[0214] The UE determines the index of the PSFCH resource for PSFCH transmission in response to PSSCH reception as (P ID +M ID )modRPSFCH PRB,CS , where P ID is the physical layer source ID provided by SCI format 2-A or 2-B for scheduling PSSCH reception, and M ID M is the identity of the UE receiving the PSSCH indicated by the higher layer if the UE detects SCI format 2-A with the broadcast type indicator field value of "01"; otherwise M ID is zero.

[0215] The UE uses Table 8 to obtain the cyclic shift pair index corresponding to the PSFCH resource index and N PSFCH CS The value of m0 used to calculate the value of the cyclic shift α is determined.

[0216] [Table 8]

[0217]

[0218] In the case where the UE detects SCI format 2-A with a broadcast type indicator field value of "01" or "10" as in Table 9, or in the case where the UE detects SCI format 2-B or SCI format 2-A with a broadcast type indicator field value of "11" as in Table 10, the UE determines m for calculating the value of the cyclic shift α. cs The UE applies one of the cyclic shifts in the cyclic shift pair to the sequence used for PSFCH transmission.

[0219] [Table 9]

[0220] HARQ-ACK value 0(NACK) 1(ACK) Sequential cyclic shift 0 6

[0221] [Table 10]

[0222] HARQ-ACK value 0(NACK) 1(ACK) Sequential cyclic shift 0 N / A

[0223] At the same time, non-contiguous RBs (equidistant) in frequency may be allocated to the UE. This set of non-contiguous RBs may be referred to as interleaved RBs. This may be useful in a spectrum (e.g., shared spectrum) subject to regulations such as occupied channel bandwidth (OCB) and power spectral density (PSD).

[0224] Fig.10 Interleaved RBs based on an embodiment of the present disclosure are shown. Fig.10 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0225] Reference Fig.10, an interlace of RBs may be defined in the frequency domain. Interlace m∈{0,1,...,M-1} may include (common) RBs{m,M+m,2M+m,3M+m,...}, where M may represent the number of RBs of the interlace given by Table 11.

[0226] [Table 11]

[0227] u M 0 10 1 5

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

[0229] Meanwhile, in the next generation system, the UE may perform a sidelink transmission operation and / or a sidelink reception operation in an unlicensed band. Meanwhile, for operations in an unlicensed band, depending on the band-specific regulations or requirements, a channel sensing operation (e.g., energy detection / measurement) for the channel to be used may be performed before the UE performs transmission. Only when it is determined that the set of channels or RBs to be used is idle as a result of channel sensing (e.g., if the measured energy is less than or equal to a specific threshold), the UE may perform transmission in the unlicensed band. If it is determined that the set of channels or RBs to be used is busy as a result of channel sensing (e.g., if the measured energy is greater than or equal to a specific threshold), the UE may cancel all or part of the transmission in the unlicensed band. Meanwhile, in the operation of the unlicensed band, the UE may skip or simplify the channel sensing operation (making the channel sensing interval relatively small) within a certain time after the transmission within a specific time duration. On the other hand, after a certain time has passed after the transmission, the UE may determine whether to transmit after performing a conventional channel sensing operation. Meanwhile, for transmission in unlicensed bands, depending on regulations or requirements, the power spectral density (PSD) of the signal / channel sent by the UE and / or the size of the frequency occupied domain and / or the time interval may be greater than or equal to a certain level, respectively. Meanwhile, in unlicensed bands, in order to simplify channel sensing, the channel occupied time (COT) duration information may be used to inform that the channel obtained based on the initial general channel sensing is occupied within a certain time, and the maximum length of the COT duration may be configured differently depending on the priority value of the data packet or service.

[0230] At the same time, the base station can share the COT duration event obtained by the base station based on channel sensing through DCI transmission, and the UE can perform a specific (indicated) channel sensing type and / or CP extension within the COT duration based on the DCI information received from the base station. At the same time, the UE can share the COT duration obtained by the UE based on channel sensing with the base station that is the destination of the UE's UL transmission, and can provide relevant information through the UL through the configured grant uplink control information (CG-UCI). In the above situation, the base station can perform simplified channel sensing within the COT duration shared by the UE. In the case of sidelink communication, there is a situation where the UE receives information about the resources to be used for sidelink transmission from the base station through DCI or RRC signaling, such as mode 1 resource allocation (RA) operation, and there is a situation where the UE performs sidelink transmission and reception based on inter-UE sensing operations without the assistance of the base station, such as mode 2 RA operation.

[0231] Meanwhile, in case of channel access type 1 which may be used regardless of channel occupation time (COT) configuration, DL transmission may be performed based on the procedures shown in Tables 12 to 13.

[0232] [Table 12]

[0233]

[0234]

[0235] [Table 13]

[0236]

[0237] Meanwhile, for channel access type 1 which may be used regardless of channel occupation time (COT) configuration, UL transmission may be performed based on the procedures shown in Tables 14 to 15.

[0238] [Table 14]

[0239]

[0240]

[0241] [Table 15]

[0242]

[0243]

[0244] Meanwhile, channel access type 2, which is a simplified channel access type, may be used within a channel occupancy time (COT) before transmission, and DL transmission may be performed based on the procedure shown in Table 16.

[0245] [Table 16]

[0246]

[0247]

[0248] Meanwhile, channel access type 2, which is a simplified channel access type, may be used within the channel occupancy time (COT) before transmission, and UL transmission may be performed based on the procedure shown in Table 17.

[0249] [Table 17]

[0250]

[0251] In an embodiment of the present disclosure, type 2 ASL channel access may be performed in the same manner as type 2A DL and / or UL channel access. For example, type 2 ASL channel access may be performed in a sensing interval T_short_sl=25us, where the interval may consist of a duration T_f=16us followed by a sensing slot, and T_f may include a sensing slot at the beginning of T_f. The basic idle (IDLE) determination in type 2 ASL channel access may also draw on the IDLE determination from DL or UL channel access.

[0252] In an embodiment of the present disclosure, type 2B SL channel access may be performed in the same manner as type 2B DL ​​and / or UL channel access. For example, in the case of type 2B SL channel access, the UE may perform transmission immediately after sensing that the channel is idle within a duration of T_f=16us. T_f may include a sensing slot occurring within the last 9us of T_f. The basic IDLE determination in type 2B SL channel access may also draw on the IDLE determination from DL or UL channel access.

[0253] In an embodiment of the present disclosure, type 2C SL channel access may be performed in the same manner as type 2C DL and / or UL channel access. For example, in the case of type 2C SL channel access, the UE may not perform channel sensing. Instead, the duration of SL transmission may be at most 584us.

[0254] In an embodiment of the present disclosure, type 1SL channel access may be implemented in the same manner as type 1DL and / or UL channel access. For example, the UE may randomly derive an integer value N based on a contention window size corresponding to a priority level. Then, if the channel sensing result for the delay duration T_d corresponding to the priority level is idle, the UE may reduce the N-1 counter value by T_sl when IDLE. If the value of the counter is zero, the UE may occupy a set of RBs or a channel subjected to channel sensing. If a portion of the channel sensing result for the T_sl duration is determined to be busy, the UE may maintain the counter value until the channel sensing result for the delay duration T_d is idle, and the UE may continue to perform channel sensing. In the above, the delay duration T_d may be composed of T_f=16us and continuous m_p*T_sl after T_f=16us, where m_p may be a value determined by the priority level (p), and T_sl=9us may be a time interval for performing channel sensing.

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

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

[0257] - Fixed to the lowest priority for filling the Buffer Status Report (BSR) and the bit rate suggested MAC CE;

[0258] -For SRB0, SRB1, SRB3 and other MAC CEs, it is fixed as the highest priority;

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

[0260] When selecting the CAPC for a DRB, the base station considers fairness between other service types and transmissions while considering the 5QI of all QoS flows multiplexed to the corresponding DRB. Table 10 shows which CAPC should be used for a standardized 5QI, i.e., the CAPC 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.

[0261] [Table 18]

[0262]

[0263] Table 19 shows the m in DL p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT) and allowed CW size vary according to the channel access priority level.

[0264] [Table 19]

[0265]

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

[0267] Table 20 shows the m in UL p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT) and allowed CW size vary according to the channel access priority level.

[0268] [Table 20]

[0269]

[0270]

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

[0272] In an embodiment of the present disclosure, when the UE has occupied a channel through a type 1SL channel access, the UE may not be ready to send a sidelink transmission. In this case, the UE may configure a delay duration of length T_d and a sensing duration of length T_sl immediately before the sidelink transmission that it is ready to send. Here, if both are idle, the UE may perform the sidelink transmission immediately, but if at least one of the delay duration and the sensing duration is busy, the UE may perform type 1SL channel access again. For example, if the sidelink transmission is not possible at the end of channel sensing (for example, if the end of channel sensing is after the start of the sidelink transmission), the UE may reselect the sidelink transmission resource. For example, the reselected resource may be selected by considering the end time of the channel sensing and / or the length of the remaining sensing interval, etc. For example, the remaining sensing interval may be a value derived from assuming that all channel sensings are idle.

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

[0274] Reference Fig.11 (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.

[0275] Reference Fig.11 (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.

[0276] Meanwhile, the SL-UE related objectives can be as follows.

[0277] Study and specify support for sidelink on unlicensed spectrum for both Mode 1 and Mode 2, where Uu operation for Mode 1 is limited to licensed spectrum [RAN1, RAN2, RAN4]. Channel access mechanisms from NR-U should be reused for sidelink unlicensed operation. Evaluate the applicability of sidelink resource reservation from Release 16 / Release 17 to sidelink unlicensed operation within the boundaries of the unlicensed channel access mechanisms and operation. There are no specific enhancements to the Release 17 resource allocation mechanism. If the existing NR-U channel access framework does not support the required SL-U functionality, the WG will make appropriate recommendations for RAN approval.

[0278] Physical channel design framework: The changes required to the NR sidelink physical channel structure and procedures to operate on unlicensed spectrum. The existing NR sidelink and NR-U channel structure should be reused as a baseline. There are no specific enhancements to the existing NR SL features. This study should focus on the FR1 unlicensed bands (n46 and n96 / n102) and will be completed by RAN#98.

[0279] Meanwhile, issues related to the channel access mechanism can be as follows.

[0280] Representatively, the following two directions can be considered. However, based on preconfigured conditions / events, method (A) and method (B) can be used together, or method (A) and method (B) can be switched with each other.

[0281] [Method (A)]: After generating COT based on LBT, the UE can perform SL sensing / resource selection (SL grant generation) within the COT.

[0282] For example, if method (A) is applied, even if other UE Y occupies only some frequencies within the RB set in slot #N, the LBT result of the RB set can be determined to be busy. Therefore, there may be a limitation that UE X cannot select / reserve the frequency resources of the remaining FDM on slot #N.

[0283] For example, in the case of method (A), FDM may be difficult, but not impossible. If the LBT of UE X is not blocked by (UE Y) just before time slot #N (where UE Y occupies some frequency A), UE X may perform transmission on other frequency B corresponding to time slot #N. If UE X performs transmission on frequency B by COT initiation, UE X may perform backoff-based LBT, and if the COT of UE Y may be shared, UE X may perform transmission based on a single LBT.

[0284] [Method (B)]: After performing SL sensing / resource selection (SL grant generation), the UE can determine whether the corresponding resources are actually used based on LBT.

[0285] For example, in the case of LBT, if UE X reserves / selects some frequency resources within the RB set at a certain time, other UE Y cannot reserve / select frequency resources of FDM for some frequency resources. However, if method (B) is used, this limitation can be alleviated.

[0286] For example, even in the case of method B, COT sharing operation may be considered. For example, assuming that there are four resources such as slot #N, slot #N+1, slot #N+2, and slot #N+3, multiple UEs (UE X, UE Y, ...) may perform LBT just before slot #N, and may attempt FDM transmission on multiple frequencies in the corresponding slot #N. Through this, multiple UEs may plan to transmit on the next four slots (through the same COT). In this case, if the LBT of UE X fails, UE X may perform a single LBT (without backoff) just before the next slot #N+1 by detecting the COT of UE Y (in slot #N).

[0287] For example, if the result of LBT for a particular resource is busy, resource reselection may be triggered. This may be interpreted as a kind of SL re-evaluation / preemption.

[0288] For example, if the actual result of the LBT is busy (and / or if the actual LBT was not performed, but because too large a backoff value was chosen, the LBT could not be performed until just before resources were reached), resource (re)selection may be triggered.

[0289] For example, depending on the criteria below, the appropriate / applicable method may vary.

[0290] For example, depending on FBE or LBE, the appropriate / applicable method may be different. For example, in the case of FBE, method (A) may be appropriate, and in the case of LBE, method (B) may be appropriate.

[0291] For example, depending on mode 1 or mode 2, the appropriate / applicable method may be different. For example, in the case of mode 1, method (A) may be more appropriate. Even in the case of mode 2, the appropriate method may be different, depending on whether it is a case of resource selection / reservation for a single MAC PDU transmission (e.g., method (A)) or a case of resource selection / reservation for multiple MAC PDU transmissions. For example, in the case of resource selection / reservation for multiple MAC PDU transmissions, method (A) can be used for initial execution of resource selection and / or resource selection within the first cycle, and method (B) can be applied to periodically reserved resources outside the (maximum) COT.

[0292] For example, method (A) may be used when reselecting (or newly generating) all SL authorizations, or method (B) may be used when reselecting only a portion of SL authorizations.

[0293] For example, the resources selected / reserved based on SL sensing may be limited to within the (maximum) COT, or the resources selected / reserved based on SL sensing may be outside the (maximum) COT.

[0294] For example, even if the resources selected based on SL sensing are outside the (maximum) COT, there may not be a significant problem if SL resource exclusion is performed between SL-U UEs and the actual usage of the selected resources is determined based on LBT.

[0295] For example, through signaling such as SCI, the SL-U UE can be notified of the reserved resources included in its COT and the reserved resources not included in its COT (for example, reserved resources located outside the COT or resources reserved without COT configuration (sensed only by SL)). In addition, other SL-U UEs that receive the signaling can apply different weights (for example, offsets of RSRP measurement values) in their resource exclusion process.

[0296] For example, from the perspective of COT sharing, 1) multiple SL-U UEs can share the COT of the base station, or 2) UE-C can share the COT of UE-A and the COT of UE-B. For example, in case 1), weights can be applied to resources within the COT of the base station, and in case 2), whether weighting can be applied can be determined depending on which UE's COT it is.

[0297] For example, while maintaining the resource reservation information previously notified by SCI, the sending UE can additionally notify information about the length of its COT duration. In this case, the receiving UE can determine which resources are within the COT of the sending UE and which resources are outside the COT by combining the reserved resources and the COT duration.

[0298] For example, in method (A) / (B), for resources in slot #N+K indicated / reserved by SCI of other SL-U UEs received in slot #N, it is assumed that each DMRS RSRP measurement value measured in slot #N is applied as the power per RE. In this case, if the sum of the powers of the scheduled resources on slot #N+K is greater than a threshold, slot #N+K can be excluded from the selectable candidate resources.

[0299] For example, if SCI#1, SCI#2, and SCI#3 are transmitted in time slot #N, and if time slot #N+K is reserved in SCI#2 and SCI#3, and if the result of the sum of the DMRS RSRP measurement powers of SCI#2 and SCI#3 by the UE is greater than a certain threshold, time slot #N+K may be excluded from resource selection. For example, even if the SL UE reserves time slot #N+K through SCI#2 (and / or SCI#3), it may not perform actual transmission due to LBT failure, so taking this into account, time slot #N+K may be configured not to be excluded from resource selection.

[0300] For example, if other UEs inform the receiving UE through SCI whether the resources reserved in time slot #N+K are within or outside its COT, the receiving UE can assign weights based on this information. For example, resources within the COT can be excluded, and resources outside the COT can be selected first.

[0301] At the same time, there may be questions whether NR-U LBT is fully reused in SL-U.

[0302] For example, NR-U LBT and SL sensing operations can be supported in a hybrid form.

[0303] For example, the reserved resource pattern can be considered in a form that is as continuous as possible in the time domain (considering coexistence with Wi-Fi and other SL-U), or methods such as relatively increasing the number of reserved resources for TB transmission or prioritizing resource selection at an earlier position within the selection window can be considered (considering the possibility of LBT failure).

[0304] For example, in the case of the number of reserved resources, the base station (or network) can determine the interference level of the corresponding unlicensed band (cell) and configure the number of reserved resources, or can dynamically indicate the number of reserved resources in the SCI by utilizing the success / failure statistics of each UE.

[0305] For example, considering the reserved resource mode (based on continuous time slots), the SL sensing and resource selection process can be changed.

[0306] For example, considering the possibility of LBT failure, when a relatively large amount of resources is reserved / selected for TB transmission, it is possible to configure / allow based on the existing SL sensing / resource selection process whether to use only candidate resources corresponding to X% or a (preconfigured) ratio greater than X%.

[0307] For example, considering the number of (consecutive) LBT failures, whether to allow additional resource selection / reservation operations and / or the number of corresponding resources may be configured / limited differently.

[0308] For example, a resource reservation method considering the SL minimum round trip time (RTT) gap (eg, INI_PSSCH-TO-RETX_PSSCH) may be proposed.

[0309] For example, the existing PSFCH format is only for 1 bit. Therefore, a multi-bit format / structure (e.g., CP-OFDM PUCCH format 2 with 2 symbols) that considers HARQ-ACK feedback omission / retransmission due to LBT failure (such as NR-U) can be newly considered.

[0310] For example, a form (eg, method (A) may be considered, which ensures (must) secure idle resources based on SL sensing within the formed COT related start time slot (or configuration time slot).

[0311] For example, a mechanism may be considered such as reporting (from the PHY layer to the MAC layer) (at least one or a preconfigured minimum number) of candidate resources (e.g., time slots) when considering the SL DRX active time of Release 17 (e.g., this can be interpreted as a starting time slot within the COT or time slots constituting the COT), and resource selection (performed by the MAC layer upon receiving the report).

[0312] For example, in unlicensed bands, coexistence between SL-U and NR-U Uu (or LAA Uu) needs to be considered (i.e., situations where a coexistence solution other than SCI utilization is required). To this end, shifting / randomizing the starting position (e.g., sub-symbol granularity) of SL-U transmission / reception may be considered. For example, if the transmission boundary of SL-U is delayed from a system perspective, and then NR-U Uu channel transmission is detected, SL-U transmission may be skipped.

[0313] For example, prioritizing resources at the front of the selection window may lead to load balancing issues. Therefore, similar to the method used in NR-U CG, the starting position can be randomly selected per UE at a sub-symbol granularity. In this way, if a specific UE seizes the channel, the channel becomes busy for other UEs, so that conflicts can be minimized.

[0314] For example, to this end, a symbol duration that can accommodate random position selection can be provided before an automatic gain control (AGC) symbol in the current SL structure, or since the AGC symbol includes a replica signal, a random position can be selected at a preconfigured level (e.g., sampling) within the AGC symbol.

[0315] For example, when considering coexistence between SL and Uu on the same U-band, especially when coexisting between Uu UL and SL, timing advance (TA) mismatch needs to be considered. If timing advance (TA) mismatch is not considered, this can be used as a blocking factor for LBT of SL UE due to the transmission of Uu UL UE in front. Of course, this makes sense in terms of prioritizing Uu, but the common reference timing can be configured to ensure fair operation between the two UEs. For example, a random shift can be applied based on the reference timing.

[0316] For example, re-evaluation and preemption operations of existing SLs may be supported in SL-U.

[0317] For example, it may be configured whether resource reselection triggering is allowed in the event of LBT failure (e.g., including consideration of SL DRX active time). For example, if the UE detects that LBT fails, the UE may trigger resource reselection. For example, if a UE performing LBT for a set of RBs detects that LBT fails for the set of RBs, the UE may trigger / perform resource reselection.

[0318] For example, a method may be proposed for handling the case where the COT provided by the base station for DL ​​or UL overlaps with the COT initiated by the Mode 2 SL-U UE.

[0319] For example, in an unlicensed band, SL resource pool configuration / SL communication using only cell-specific UL resources may be allowed, as described above.

[0320] Alternatively, SL resource pool configuration / SL communication in flexible resources or DL ​​resources or non-cell-specific UL resources may (additionally) be allowed.

[0321] For example, the priority ordering between UU and SL may be configured differently depending on the type of resource on which SL communication is performed / allowed.

[0322] For example, a method of indicating / determining a channel access type per channel (eg, PSFCH, SL CSI REPORT) may be proposed.

[0323] For example, this can be indicated in the SL authorization, or can be indicated by the SCI. If it is also necessary to indicate the cyclic prefix extension (CPE) (CP can be extended forward like NR-U, or the last symbol signal in SL can be extended backward) and CAPC, etc., then the LBT type and / or CPE and / or CAPC, etc. can be indicated in the form of joint coding.

[0324] For example, the combination of LBT type, CPE and / or CAPC can be notified through SL authorization or SCI, and in case of mode 2, at least which LBT type / CPE / CAPC the sending UE will apply can be predefined or (pre)configured just before SCI and PSSCH transmission.

[0325] For example, COT sharing can be proposed.

[0326] For example, in the case of "COT sharing" operation, since the UE sending the COT sharing information has performed (type 1) LBT, the UE receiving the COT sharing information can be allowed to use the type 2 series LBT process within the shared COT instead of the type 1 LBT process that takes a (relatively) long time to perform packet transmission. In other words, there is no constraint that the UE receiving the COT sharing information must perform transmission within the COT, and therefore, conflicts between WI-FI and NR-U UEs may occur within the shared COT.

[0327] For example, a possible scenario could be as follows.

[0328] For example, there may be a situation where the COT initiated by SL-U UE1 is shared with another SL-U UE2.

[0329] For example, COT sharing between target / source UEs may be considered limited to a pre-configured broadcast type (eg, unicast).

[0330] For example, it is necessary to consider whether UE2 can share the COT unconditionally with UE1's transmission. If UE1's transmission is actually sent by sharing UE0's COT, and UE2 sends again by sharing the COT, dual COT sharing operation that is not currently supported in NR-U may occur. As a way to prevent this, when transmitting, UE1 can indicate through SCI whether the transmission is based on UE1's COT or the transmission is based on another UE0's shared COT. This requires consideration of the following situation.

[0331] For example, a mechanism may be needed to prevent UE3 from mistaking a transmission by UE2 performed within a COT shared by UE1 as a transmission performed based on a COT shared by UE2 to UE3.

[0332] For example, the indication about SCI can be used to signal which COT (or which UE initiated COT) the relevant transmission is performed through. For example, the ID of the COT sharing initiator or a 1-bit indicator can be used to indicate whether the SCI sending UE is the COT initiator.

[0333] For example, transmissions on a shared COT may be limited to SL communications or related service communications with the COT initiator.

[0334] For example, based on the source / destination ID on the SCI, it can be implicitly derived which COT the transmission is using. For example, if burst traffic is generated between a source / destination pair, the related traffic transmission / reception can be completed quickly by allowing COT sharing to be used only by paired UEs. Therefore, from a system perspective, it may be advantageous.

[0335] However, considering that resource selection and the use of selected resources are not limited to ID, additional consideration is needed as to whether COT sharing is suitable for binding with ID information (especially when implicit indication method is applied). For example, if transmission based on type 1 LBT is indicated by only 1 bit on SCI, UE4 receiving SCI can share COT regardless of ID. In addition, UE4 can prevent other UEs from sharing COT again by indicating the application of non-type 1 LBT on its transmission-related SCI.

[0336] For example, the transmitting UE may explicitly inform the COT through the SCI whether the sharing target is limited to the destination ID UE or any UE.

[0337] For example, a method may be proposed to solve the problem that excessive COT sharing or multi-hop COT sharing with multiple UEs affects WI-FI transmission.

[0338] For example, the method of adjusting the energy detection (ED) threshold may be different depending on the case of a shared base station COT and the case of a shared UE-COT. In the case of a shared base station COT or a remote UE-COT, a low ED threshold may be used in consideration of relatively high power transmission. In contrast, in the case of a shared close UE-COT, a high ED threshold may be used and the transmit power may be reduced.

[0339] For example, when a COT is shared with a threshold number or more of UEs, or when a multi-hop COT is shared, a preconfigured (relatively low) ED threshold may be applied. For example, when a relatively high ED threshold X is used, COT sharing operation based on source / destination ID may be allowed, and when a relatively low ED threshold Y is used, COT / multi-hop COT sharing operation shared with multiple UEs may be allowed. For example, when a COT is shared with a threshold number or more of UEs, or when a multi-hop COT is shared, a preconfigured transmit power value for COT sharing information signaling may be applied.

[0340] For example, since the ED threshold used is signaled through SCI or the like, the UE receiving it can recognize the relevant intention.

[0341] For example, when the above-described method is applied, the broadcast type, destination ID, service type, etc. that can use the selected / reserved resources may be restricted.

[0342] For example, there may be a situation where SL-U UE2, which has received the COT sharing information initiated by SL-U UE1, shares the COT sharing information with another SL-U UE3.

[0343] For example, there may be a situation where the COT initiated by the base station is shared with the SL-U UE (e.g., Mode 1).

[0344] For example, there may be a situation where SL-U UE1 that has received COT sharing information initiated by the base station shares the COT sharing information with another SL-U UE2 (or SL-U UE2 that has received COT sharing information initiated by SL-U UE1 shares the COT sharing information with the base station).

[0345] For example, whether to apply the above operation may be configured differently depending on whether UE-B (e.g., UE2) is in the "out of coverage" state. For example, UE-B (e.g., UE2) may notify another UE (e.g., UE1) of its state information through pre-configured signaling. For example, in the case of base station initiation, COT sharing may be limited to UEs within the coverage of the corresponding cell.

[0346] For example, it may be pre-configured whether COT sharing is allowed for OOC UEs or UEs within the coverage of other base stations (eg, IDLE, INACTIVE, RRC CONNECTED).

[0347] For example, DCI 2_0 may indicate DL / UL / flexible use and SL use. For example, since the content of DCI2_0 is UE-specific, it may be indicated as UNKNOWN for legacy UEs for backward compatibility, and as SL use for SL-U UEs.

[0348] For example, SL usage may be provided by semi-static DL / UL configuration. For example, this may be in the form of providing a separate semi-static SL resource.

[0349] For example, basically, in the U band (different from the L band), in addition to the UL, the FLEXIBLE symbol / time slot can also be relaxed to be configured as a SL resource.

[0350] For example, a method may be needed to determine that SL-U UE2 is within the coverage of the same cell as SL-U UE1. For example, UE2 may convey information related to its cell or whether it is in OOC to UE1 through predefined signaling.

[0351] For example, the RB set indicator may specify some frequency resources (within all bandwidths) that may be used for SL. Note that in NR-U, the COT information is common across RB sets.

[0352] For example, there may be a situation where a base station that has received a COT initiated by SL-U UE1 (e.g., COT sharing information formed based on SL CG / DG) shares the COT for SL transmission (e.g., mode 1) or Uu communication (e.g., DL, UL) of SL-U UE1 / 2.

[0353] For example, SL signaling for COT sharing may be specified.

[0354] For example, there may be conditions for sharing a COT initiated by a SL-U UE or conditions for allowing COT sharing.

[0355] For example, COT sharing can be associated with SL mode.

[0356] For example, in case of Mode 1, COT sharing (similar to UL) may be used.

[0357] For example, there may be a form of COT sharing between a base station and a Mode 1 UE (eg, UL-SL, DL-SL), or a form of COT sharing between a Mode 1 UE and another UE (eg, SL-SL).

[0358] For example, in case of Mode 2, COT sharing may be useful for PSFCH-based SL HARQ feedback transmission / reception or SL CSI transmission / reception.

[0359] For example, a PSSCH transmitting UE may indicate the parameters required for LBT (e.g., LBT type) through SCI just before PSFCH transmission. If the "COT duration length" information is indicated through SCI, the LBT type may be determined based on whether the PSFCH exists within the COT duration or outside the COT duration. For example, if the PSFCH exists within the COT, the UE may perform a single LBT, and if the PSFCH exists outside the COT, the UE may perform a backoff-based LBT.

[0360] For example, SL HARQ feedback enabled data transmission may be configured / restricted to be allowed only in the case of forming / sharing a COT.

[0361] For example, the UE types associated with COT sharing may be restricted.

[0362] For example, only UEs of a specific broadcast type (eg, unicast) may be allowed to share COTs. For example, even in the case of implicit indication, COT sharing may be allowed only between UEs participating in related SL communications.

[0363] For example, the UE that initiates / triggering PC5 RRC connection establishment may be allowed to perform COT sharing.

[0364] For example, only UEs in the relationship between a relay UE and a remote UE may be allowed to perform COT sharing.

[0365] For example, the UE type of the initiator that allows any UE to use COT to share information may be restricted.

[0366] For example, UEs performing packet transmission (or UEs having packets to send in buffers) may be allowed to share COTs.

[0367] For example, there may be a case where information on UEs performing packet transmission within a shared COT is identified.

[0368] For example, the information may be identified by receiving SL BSR information or a COT sharing request message (eg, SCI), etc.

[0369] For example, when UE1 sends a SL BSR, it may send it through the COT. For example, UEs that have received the SL BSR may share the COT of UE1.

[0370] For example, the UE may basically operate based on method (B), but when an application event of method (A) occurs, the COT shared operation grant may be enabled.

[0371] For example, a (shared) COT initiated by the UE for UL transmission may be configured to be available for SL transmission.

[0372] For example, whether operation is allowed may be configured differently depending on the relationship between the magnitude of the UL frequency and the SL frequency, the relationship between the UL transmit power and the SL transmit power (eg, in determining the ED threshold for enabling COT initiation), etc.

[0373] For example, when a COT is shared, it may be configured whether the COT sharing information is in a form common to a RB set or in a form specific to a RB set.

[0374] For example, if there is no RB set indicator, COT sharing is possible only in the RB set in which the pre-configured control information (e.g., DCI 2_0, SCI) is detected. For example, if there is an RB set indicator in the pre-configured control information, COT sharing may be possible only specifically for the indicated RB set.

[0375] For example, the operation of the SL-U UE that receives COT sharing information can be specified.

[0376] For example, UE2 that detects COT shared information sent by UE1 can perform resource selection by performing only SL sensing (or type 2 series of LBT) on the relevant RB set excluding the remaining time / frequency resources other than the frequency resources indicated by the SCI or excluding the remaining (FDM) frequency resources other than the relevant RB set during the shared COT duration. For example, when method (A) is applied, UE2 that detects COT shared information sent by UE1 can perform resource selection by performing only SL sensing (or type 2 series of LBT) on the relevant RB set excluding the remaining time / frequency resources other than the frequency resources indicated by the SCI or excluding the remaining (FDM) frequency resources other than the relevant RB set during the shared COT duration.

[0377] For example, if COT is generated only for RB set #1, and the UE intends to send SL data in RB set #2, the UE may be configured to perform random backoff (ie, COT initiation).

[0378] For example, if UE2 detects COT sharing information sent by UE1 and does not use the COT sharing information (for example, UE2 is not the target UE of COT sharing), UE2 can exclude the frequency resources of the relevant RB set within the shared COT duration or the frequency resources indicated by the SCI on the relevant RB set from its selectable candidate resource set (or the target resource set on which SL sensing (or LBT) is performed).

[0379] For example, UE1 can notify UE2 of resources included in the COT and resources not included in the COT (e.g., reserved resources located outside the COT or resources reserved without COT configuration (sensed only by SL) through signaling (such as SCI). Through this, UE2 can identify resource domains that can be selected only by SL sensing (or LBT of type 2 series).

[0380] For example, in case of understanding related to RB set index, it can be configured to have a common understanding between UEs. For example, in SL, the absolute frequency domain linked to the RB set index can be aligned between UEs.

[0381] For example, COT sharing may be performed in the form of explicit indication, or COT sharing may be performed in the form of implicit indication.

[0382] (1) Implicit indication (e.g., increased FDM likelihood)

[0383] For example, UE X may form a COT (e.g., 5 slots) based on Type 1 LBT, and UE X may select resources on slot #1 and slot #2 within the COT through SL sensing, and UE X may signal this through SCI. In this case, another UE Y may select / use the remaining frequency resources other than the frequency resources signaled through SCI on slot #1 / 2 or resources on slot #3 / 4 / 5 without performing Type 1 LBT (LBT based on Type 2 series).

[0384] Here, for example, UE X may be informed through SCI that the reserved resources on time slot #1 / 2 are selected based on Type 1 LBT. However, information such as the number of time slots related to COT sharing may not be explicitly signaled.

[0385] For example, instead of information that resources are selected based on Type 1 LBT, UE X may notify the COT duration length so that UE Y may recognize the resources of UE X. If UE X performs transmission by sharing the COT of another UE, UE X may notify that the COT duration length is "0".

[0386] For example, if this method is applied, the problem that UE Y cannot select / reserve resources related to the (next) time slot #3 with a high probability due to the (type 1) LBT result for time slot #1 / 2 in which the reserved resources of UE X exist being determined to be busy, and the problem that UE Y cannot select frequency resources of FDM for the frequency resources reserved by UE X on time slot #1 / 2 due to the LBT characteristics can be alleviated.

[0387] (2) Explicit instructions (e.g., to ease complex LBT operations)

[0388] For example, for communication with another UE, it may be that the UE forms a COT based on a form such as an FBE form or an existing COT sharing form and signals it to the other UE.

[0389] In this case, the signaling may be limited to other UEs or in the form of a broadcast.

[0390] For example, there may be issues related to the physical structure.

[0391] For example, the time slot-based structure of the existing SL that takes into account the AGC problem (e.g., taking into account the problem between SL-U UE) may be reused. For example, the time slot-based structure of the existing SL that takes into account the AGC problem (e.g., taking into account the problem between SL-U UE) may not be reused.

[0392] Note that no symbol-level shift / delay is introduced in NR-U. (For example, considering the complexity of RE-SCRAMBLING, etc.) No symbol-level shift / delay is introduced in NR-U.

[0393] For example, if the result of LBT performed before an AGC symbol is busy, additional LBT execution and data / control information transmission may be allowed based on the result within the AGC symbol duration before actual data / control information transmission.

[0394] For example, for this operation, it may be limited to puncturing only about a predetermined length (eg, half) of the AGC symbol.

[0395] For example, the transmittable time may be limited to three: before the AGC symbol, before the AGC 2ND half symbol, and before the symbol immediately after the AGC symbol, thereby giving three LBT opportunities. If AGC is even partially required, the transmittable time may be limited to only two: before the AGC symbol, and before the AGC 2ND half symbol.

[0396] Meanwhile, when performing transmission on a shared spectrum band, the wireless device may send a cyclic prefix extension (CPE) before (or together with) the transmission to achieve alignment of orthogonal frequency division multiplexing (OFDM) symbols and reduce inter-symbol interference (ISI). In addition, the UE may perform CPE transmission to increase the likelihood that a channel where LBT is successful can be used for actual transmission. For example, when the UE succeeds in LBT for a specific channel, the UE may perform CPE transmission to prevent other devices from occupying the specific channel. In this case, if the time domain or the length of the time domain in which CPE is performed for SL transmission (e.g., PSFCH transmission, S-SSB transmission, etc.) is different between different devices, the CPE of a specific device may cause LBT failure of other devices. That is, the CPE performed by a specific device for SL transmission may affect the LBT of other devices for SL transmission.

[0397] Fig.12 is a diagram used to explain the problems caused by different CPEs. Fig.12 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0398] Reference Fig.12, in order to increase the possibility of PSFCH transmission in the unlicensed band, the device may perform CPE. In this case, if the time domain or the length of the time domain in which CPE is performed is different between different devices, the CPE of a specific device may cause LBT failure of other devices. Specifically, for example, if the CPE lengths of the devices are different, the first device and the second device may fail LBT within the T1 duration due to the CPE of the third device, and the first device and the second device may not be able to perform PSFCH transmission. In addition, the first device may fail LBT within the T2 duration due to the CPE of the second device, and the first device may not be able to perform PSFCH transmission. Similarly, although not shown, the third device may also fail LBT due to the CPE of another device, and the third device may not perform PSFCH transmission. For example, in the case of NACK feedback only, if the PSFCH transmission is discarded, a NACK to ACK error may occur (i.e., NACK is mistaken for ACK), and the reliability of SL communication may deteriorate. For example, in the case of ACK / NACK feedback, if the ACK transmission is discarded, unnecessary retransmissions may occur, which may result in unnecessary waste of resources.

[0399] Fig.13 is a diagram used to explain the problems caused by different CPEs. Fig.13 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0400] Reference Fig.13 , in order to increase the possibility of S-SSB transmission in the unlicensed band, the device may perform CPE. In this case, if the time domain or the length of the time domain in which CPE is performed is different between different devices, the CPE of a specific device may cause LBT failure of other devices. Specifically, for example, when the CPE lengths of the devices are different, the first device and the second device may fail LBT within the T1 duration due to the CPE of the third device, and the first device and the second device may not be able to perform S-SSB transmission. In addition, the first device may fail LBT within the T2 duration due to the CPE of the second device, and the first device may not be able to perform S-SSB transmission. Similarly, although not shown, the third device may also fail LBT due to the CPE of another device, and the third device may not be able to perform S-SSB transmission. S-SSB can be transmitted by multiple devices at the same time / frequency based on a single frequency network (SFN) operation. If as Fig.13 If S-SSB transmission is discarded as in the embodiment, the coverage of the synchronization signal transmission can be reduced, which may cause performance degradation of SL communication.

[0401] In order to solve the above problems, it may be necessary to change the existing SL 1-symbol TX-RX switching structure (e.g., CPE). For example, the target can be the last symbol within the SL time slot, or the symbol between the PSSCH and the PSFCH within the time slot (e.g., a form formed by a PSFCH TX UE (make-up), a form formed by a PSSCH TX UE and a PSFCH TX UE together, etc., taking into account that the LBT type may be different for each UE that sends a PSFCH of CDM). For example, this may also depend on whether the next time slot without PSFCH after the PSSCH is a time slot to be used for the Uu link or a time slot still used for the SL. For example, if the PSSCH is followed by an SL time slot, the UE can send a more extended PSSCH last symbol because the interference effect caused by the TA is reduced. For example, backward or forward formation can be beneficial to the sending and receiving UE pairs. However, this may result in LBT blocking of other UEs (FDM / CDM) that require PSFCH transmission. Taking this into account, a gap for UE common LBT operation can be configured in front of the PSFCH resource (e.g., symbol).

[0402] Fig.14 A gap for UE-common LBT operation in front of a PSFCH resource (eg, symbol) 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.

[0403] Reference Fig.14 , CPE can be performed before the PSFCH resource (e.g., symbol), and the length of CPE can be configured to be the same. In this case, the problem of LBT failure of other devices due to CPE of a specific device can be solved. By doing so, CDM / FDM can be enabled between UEs within a given PSFCH resource set, UE multiplexing can be enabled within a given PSFCH resource, and PSFCH transmission discard can be prevented. By doing so, in the case of only NACK feedback, the problem of NACK to ACK error caused by the loss of PSFCH transmission (i.e., the problem of mistaking NACK for ACK) can be solved, and the reliability of SL communication in the unlicensed band can be guaranteed. For example, in the case of ACK / NACK feedback, the problem of unnecessary retransmission due to the discard of ACK transmission can be solved, and resources can be efficiently used in the unlicensed band.

[0404] For example, the corresponding UE common gap may be configured in front of the SL SSB resource (eg, time slot). By doing so, the possibility that SL data transmission (performed in the form of TX burst) blocks SL SSB transmission may be reduced.

[0405] Fig.15 A gap of UE common LBT operation in front of a SL SSB resource (eg, time slot) based on an embodiment of the present disclosure is shown. Fig.15 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0406] Reference Fig.15 , CPE can be executed in front of the SL SSB resource (e.g., time slot), and the length of the CPE can be configured to be the same. In this case, the problem of LBT failure of other devices due to the CPE of a specific device can be solved. By doing so, the coverage of synchronization signal transmission can be improved by increasing the possibility of multiple devices performing S-SSB transmission simultaneously in the unlicensed band. Therefore, the detection capability of the synchronization signal can be improved, and the reliability of SL communication can be guaranteed.

[0407] For example, due to the PSFCH resource set existing in the resource pool, the SL-SSB resource set existing outside the resource pool, and the reserved time slots that cannot be configured as resource pools, coexistence issues with WI-FI may occur, and a solution for this may be required.

[0408] For example, SL-SSB and PSCCH / PSSCH may be allowed to coexist in a resource pool.

[0409] For example, in the U band, when SL communication is performed, a form of aggregating reserved slots into one place can be applied as an exception.

[0410] For example, if the reserved time slots are dispersed in the time domain, the reserved time slots can be aggregated into one location as much as possible. By doing so, it is possible to consider configuring the resource pool in the direction of gaplessness. For example, in order to further alleviate the delay that may occur when the reserved time slots are aggregated into one location, and considering that the actual shared COT length is at most 20 milliseconds (or the SLSSB transmission period is 160 milliseconds), a hybrid form of aggregating the reserved time slots into one location as much as possible within 20 milliseconds (or 160 milliseconds) can be considered.

[0411] For example, in case of Mode 2 SL grant, different from the existing case, multiple SL HARQ processes may be operated (eg, applied to reserved / selected resources within one reservation period).

[0412] For example, a SL-U LBT operation that reuses the size / structure of NR-U's RB sets may be proposed.

[0413] For example, a resource pool configuration method considering an inter-cell guard band (eg, a form in which multiple subchannel sizes coexist) and a method for supporting existing SL sensing operations may be proposed.

[0414] For example, a method of using RBs in a guard band in consideration of collision avoidance between SL-U UEs may be proposed.

[0415] For example, this may be a problem related to the SL subchannel structure design. For example, the UE may use the guard RB by combining the guard RB with the subchannel located below (or above) it in the frequency domain.

[0416] For example, additional considerations may also be made in terms of meeting power spectral density (PSD) requirements and coexistence with Uu channels (eg, interleaving structure).

[0417] For example, whether or not discovery of emergent events is supported and the associated structures and processes can be addressed.

[0418] For example, when considering LBT failure, the extended structure of SL SSB repetition still needs to be considered. For example, when considering LBT failure within one SL SSB cycle and extending two SL SSB resources, the UE can perform only one preconfigured actual transmission based on LBT. Of course, if the LBT results of both SL SSB resources are determined to be busy, the SL SSB transmission can be omitted.

[0419] For example, if the UE intends to send the SL SSB twice at 30 kHz, the UE may configure a window for sending the SL SSB three or four times, and the UE may send the SL SSB at most twice within the window starting from the time when the LBT succeeds.

[0420] For example, there may be congestion control issues.

[0421] For example, the UE may reuse the congestion control mechanism of the existing SL. For example, the UE may not reuse the congestion control mechanism of the existing SL. For example, the congestion control mechanism may be applied to UL TX.

[0422] For example, in addition to existing congestion, an LBT failure event may occur, which may be misjudged as worsening congestion. Therefore, a form of performing appropriate congestion level determination excluding the influence of LBT failure may be considered.

[0423] For example, in addition to the RSSI measurement information reported by the UE to the base station in NR-U, additional / separate metric reporting may be required.

[0424] For example, the SL RSSI measurement and the SL CBR (or the SL RSSI measurement value) may be reported (to the base station). In addition, for example, existing SL CBR-based congestion control (eg, Mode 2) and maximum retransmission count limits (eg, Mode 1CG) may need to be modified.

[0425] For example, when measuring SL RSSI or evaluating SL CBR, it may be necessary to consider domains that eliminate WI-FI interference as much as possible. For example, within the COT formed by the SL-U TX UE itself (using the form of SL RSSI measured only within the shared COT initiated by the base station / UE, within the FBE related duration (obtained based on LBT), within the SL-U UE common silence (SILENCE) resources, within the TX-RX switching symbol of the SL-U, etc.), the number of SL RSSI measurement time slots within the SL CBR evaluation window can be less than or equal to the preconfigured threshold number. In this case, for example, a preconfigured default CBR value can be used.

[0426] For example, if FBE operation is applied, coexistence with Wi-Fi may not need to be considered. Therefore, in this case, the existing congestion control and maximum retransmission count limit based on SL RSSI measurement / SL CBR can be applied.

[0427] For example, in terms of the SL RA mechanism (eg, since CBR also affects SL grant generation), the impact of the above issues needs to be considered.

[0428] For example, there may be coexistence issues between UL and SL.

[0429] For example, from a UE perspective, it is possible to configure whether BACK-TO-BACK TX is allowed between UL CG TX and SL TX. For example, it is possible to configure whether BACK-TO-BACK TX is allowed differently according to the relationship between frequency resource size, the relationship between CAPCs, the relationship between UL / SL TX power, etc.

[0430] For example, considering that the configured maximum powers between UL TX (e.g., P_CMAX_H) and SL TX are independent, when considering UL TX and SL TX within one COT, the ED threshold can be derived / applied based on the maximum value (or minimum value or (weighted) average) of the maximum power values.

[0431] For example, considering that the configured maximum powers between UL TX (e.g., P_CMAX_H) and SL TX are independent, when UL TX and SL TX are considered within separate COTs, independent ED thresholds can be derived / applied based on each maximum power value, or the ED threshold can be derived / applied based on the maximum value (or minimum value or (weighted) average) of the maximum power values.

[0432] For example, in order to allow the above operation, the relationship between the UL frequency and the SL frequency size needs to be considered, and in addition, the relationship between the UL TX power and the SL TX power needs to be considered. For example, when determining the ED threshold for LBT, COT initiation can be performed by performing LBT based on an energy detection threshold (EDT) that is configured based on the larger TX power of the two.

[0433] For example, UL-SL prioritization may be proposed.

[0434] For example, when the LBT of a TX with a higher priority fails, it may be configured whether to allow a TX with a lower priority that overlaps in the time domain. For example, when the LBT of a TX with a higher priority fails, a TX with a lower priority that overlaps in the time domain may be allowed. For example, after determining whether to allow the TX based on the LBT result, the final prioritized TX may be determined. To this end, for example, the UE may prepare a TX with a higher priority and a TX with a lower priority at the same time, or may involve the following processing: such as immediately entering the preparation process of the TX with a lower priority based on the LBT result.

[0435] For example, it may be configured whether the UL-SL prioritization rules of an existing SL may be reused.

[0436] For example, BACK-TO-BACK between SLs can be proposed.

[0437] For example, BACK-TO-BACK between Mode 1 SL and Mode 2 SL or BACK-TO-BACK between Mode 2 SL and Mode 1 SL may be allowed. For example, if there is a remaining COT related to Mode 1 SL shared by the base stations, it may be used for Mode 2 SL transmission.

[0438] For example, there may be issues related to link management.

[0439] For reference, although it is discussed that UL LBT failure handling in NR-U is operated on a per-channel basis, it is not introduced in the standard. That is, UL LBT failure handling in NR-U is operated on a carrier-common basis. This is because it is determined that it can be covered by appropriately configuring relevant parameters in the case of NR-U.

[0440] For example, DTX-based SL RLF enhancements that take into account LBT failures (eg, especially the NACK-only case) may be proposed.

[0441] For example, LBT failure itself may not indicate that SL quality is compromised.

[0442] For example, the priority order value of LBT failed MAC CE needs to be defined in SL Logical Channel Prioritization (LCP).

[0443] For example, LBT failure (and / or RLF declaration) may be managed / operated per unicast link. For example, LBT failure (and / or RLF declaration) may be managed / operated jointly for unicast links (e.g., per physical UE) or for any broadcast type.

[0444] For example, switching between multiple pre-configured SL-U carriers (and / or SL-U BWPs) may be allowed.

[0445] For example, NACK-only feedback operation in the U-band may be allowed only for non-LBT scenarios (eg, COT sharing).

[0446] For example, when LBT failure occurs, path switching (eg, Uu or ITS-only) may be allowed.

[0447] For example, SL session establishment and management related signals can be sent via the Uu carrier or an ITS dedicated carrier instead of the U band.

[0448] For example, LBT failure handling may be different depending on mode 1 / 2.

[0449] For example, in the case of mode 1, LBT failure may be reported to the base station. For example, in the case of mode 2, LBT failure may be handled based on predefined rules (e.g., switching between carriers or BWPs or RB sets or pools, resource reselection triggering).

[0450] For example, a method for handling LBT failure in multicast or broadcast may be proposed.

[0451] For example, SL-RSSI information reporting may be required. For example, only the remaining values ​​other than the SL-U UE-related RSRP may be used.

[0452] For example, there may be issues related to COT sharing. A COT sharing scenario is described below.

[0453] For example, the COT initiator can be as follows:

[0454] 1)UE A

[0455] -COT initiation based on UL resources

[0456] - COT initiation based on Mode 1SL resources or Mode 2SL resources

[0457] 2) UE A's base station

[0458] - Restrictions based on UE A's connection status

[0459] 3) Base station of UE B (e.g., destination UE of UE A)

[0460] - Restrictions based on UE B's connection status

[0461] For example, the COT responder could be as follows:

[0462] 1)UE A

[0463] 1.1) If the COT information initiated by UE-A's base station is shared

[0464] -UE A performs mode 1SL TX using type 2 LBT in shared COT

[0465] -UE A performs Mode 2SL TX using Type 2LBT in the shared COT

[0466] -UE A performs PSFCH TX using Type 2 LBT in the shared COT

[0467] -UE A performs UL TX using Type 2 LBT within the shared COT

[0468] 2)UE B

[0469] 2.1) If the COT information initiated by UE-A is shared from UE A

[0470] 2.1.1) COT initiated based on UL resources

[0471] -UE B performs mode 1SL TX using type 2 LBT in shared COT

[0472] -UE B performs mode 2SL TX using type 2LBT in the shared COT

[0473] -UE B performs PSFCH TX using Type 2 LBT within the shared COT

[0474] -UE B performs UL TX using Type 2 LBT within the shared COT

[0475] For example, on a shared COT, it may be desirable to target only certain link types. For example, considering the possibility that the applied ED thresholds are different, on a shared COT, it may be desirable to target only certain link types.

[0476] For example, in the current NR-U case, when the UL COT is shared, if the ED threshold configured by the base station is used, the base station can take this into account and adjust its TX power within the shared COT. Otherwise (for example, applying an ED threshold based on the maximum power of the UE), UL COT sharing may not be possible.

[0477] For example, if the base station recognizes that UE A and UE B are within the coverage of the same base station, as well as the maximum power information of UE A / B, the base station can indicate whether to share the COT between UE A and UE B.

[0478] 2.1.2) COT initiated based on Mode 1SL resources or Mode 2SL resources

[0479] -UE B performs mode 1SL TX using type 2 LBT in shared COT

[0480] -UE B performs mode 2SL TX using type 2LBT in the shared COT

[0481] -UE B performs PSFCH TX using Type 2 LBT within the shared COT

[0482] -UE B performs UL TX using Type 2 LBT within the shared COT

[0483] 2.2) If the COT information initiated by the base station of UE-A is shared from UE A

[0484] -UE B performs mode 1SL TX using type 2 LBT in shared COT

[0485] -UE B performs mode 2SL TX using type 2LBT in the shared COT

[0486] -UE B performs PSFCH TX using Type 2 LBT within the shared COT

[0487] -UE B performs UL TX using Type 2 LBT within the shared COT

[0488] 2.3) If the COT information initiated by UE-B's base station is shared (or if UE-B's base station indicates Type 2 LBT operation)

[0489] -UE B performs mode 1SL TX using type 2 LBT in shared COT

[0490] -UE B performs mode 2SL TX using type 2LBT in the shared COT

[0491] -UE B performs PSFCH TX using Type 2 LBT within the shared COT

[0492] -UE B performs UL TX using Type 2 LBT within the shared COT

[0493] 3) UE A's base station

[0494] 3.1) If the COT information initiated by UE-A is shared from UE A

[0495] 3.1.1) COT initiated based on UL resources

[0496] - Mode 1 SL resource allocation / scheduling of UE A in the shared COT (based on Type 2 LBT)

[0497] - UL resource allocation / scheduling of UE A in the shared COT (based on Type 2 LBT)

[0498] 3.1.2) COT initiated based on Mode 1SL resources or Mode 2SL resources

[0499] - Mode 1 SL resource allocation / scheduling of UE A in the shared COT (based on Type 2 LBT)

[0500] - UL resource allocation / scheduling of UE A in the shared COT (based on Type 2 LBT)

[0501] 4) UE B's base station

[0502] 4.1) If the COT information initiated by UE-A is shared from UE B

[0503] 4.1.1) COT initiated based on UL resources

[0504] - Mode 1 SL resource allocation / scheduling of UE B in the shared COT (based on Type 2 LBT)

[0505] - UL resource allocation / scheduling of UE B within the shared COT (based on Type 2 LBT)

[0506] For example, on a shared COT, it may be desirable to target only certain link types. For example, considering the possibility that the applied ED thresholds are different, on a shared COT, it may be desirable to target only certain link types.

[0507] 4.1.2) COT initiated based on Mode 1SL resources or Mode 2SL resources

[0508] - Mode 1 SL resource allocation / scheduling of UE B in the shared COT (based on Type 2 LBT)

[0509] - UL resource allocation / scheduling of UE B within the shared COT (based on Type 2 LBT)

[0510] 4.2) If the COT information initiated by the base station of UE-A is shared from UE B

[0511] - Mode 1 SL resource allocation / scheduling of UE B in the shared COT (based on Type 2 LBT)

[0512] - UL resource allocation / scheduling of UE B within the shared COT (based on Type 2 LBT)

[0513] 5) UE C (e.g., a UE that receives COT information initiated by UE-A or receives COT information initiated by UE-A's base station through another UE) - if the other UE and UE C are the target UEs of UE A, and UE C does not receive the COT sharing information sent by UE A

[0514] 5.1) If the COT information initiated by UE-A is shared from another UE

[0515] 5.1.1) COT initiated based on UL resources

[0516] -UE C uses Type 2 LBT execution mode 1SL TX in shared COT

[0517] -UE C uses Type 2LBT execution mode 2SL TX in shared COT

[0518] -UE C performs PSFCH TX using Type 2 LBT within the shared COT

[0519] -UE C performs UL TX using Type 2 LBT within the shared COT

[0520] 5.1.2) COT initiated based on Mode 1SL resources or Mode 2SL resources

[0521] -UE C uses Type 2 LBT execution mode 1SL TX in shared COT

[0522] -UE C uses Type 2LBT execution mode 2SL TX in shared COT

[0523] -UE C performs PSFCH TX using Type 2 LBT within the shared COT

[0524] -UE C performs UL TX using Type 2 LBT within the shared COT

[0525] 5.2) If the COT information initiated by UE-A's base station is shared from another UE

[0526] -UE C uses Type 2 LBT execution mode 1SL TX in shared COT

[0527] -UE C uses Type 2LBT execution mode 2SL TX in shared COT

[0528] -UE C performs PSFCH TX using Type 2 LBT within the shared COT

[0529] -UE C performs UL TX using Type 2 LBT within the shared COT

[0530] For example, a shared COT may be defined in SL-U.

[0531] For example, after the initiator shares the shared COT information with the responder, the initiator may be prevented from performing its own transmission within the shared COT. Alternatively, for example, after the initiator shares the shared COT information with the responder, whether to allow its own transmission within the shared COT may be configured.

[0532] For example, if the transmission is allowed, a half-duplex / SL resource conflict problem between the initiator and the responder may occur.

[0533] For example, on a shared COT, the responder's PSCCH / PSSCH-based general data transmission (e.g., GC) may be restricted. Alternatively, for example, on a shared COT, it may be configured whether the responder's PSCCH / PSSCH-based general data transmission (e.g., GC) may be allowed.

[0534] For example, in the case of GC, signaling may be required to instruct member UEs to divide the shared COT duration. For example, in addition to identifying the shared COT information based on the destination ID, in the case of GC, signaling may be required to instruct member UEs to divide the shared COT duration.

[0535] For example, issues such as MAC CE priority may be considered.

[0536] For example, (unlike PSFCH) PSCCH / PSSCH transmission may be allowed by distinguishing the COT initiator.

[0537] For example, when there are multiple shared COT information, a method for handling this can be proposed.

[0538] 1) TX UE receives shared COT information from multiple target UEs (e.g., GC)

[0539] For example, the TX UE may preferentially select resources on a common COT duration or on a COT duration that overlaps relatively more. Note that when this method is applied, the half-duplex / SL resource conflict problem between UEs participating in the GC may be exacerbated.

[0540] For example, the prioritized / valid information may be filtered using RSRP measurements of the channel / signal providing the shared COT information or the distance between the initiator and responder, etc. This allows the responder to preferentially consider shared COT information shared by an initiator that may have similar LBT results to itself, for example.

[0541] For example, it is possible to restrictively consider only the shared COT covering the SL grant-related resources generated by the TX UE / allocated by the base station or covering the amount of resources required for packet transmission determined by the TX UE.

[0542] For example, for a resource domain that the TX UE has already used to receive SL data from other UEs (and if the RSRP measurement value of the relevant channel / signal is less than or equal to a threshold), it is possible to restrictively consider only the shared COT that does not overlap with the resource domain whose RSSI value measured by the TX UE is greater than or equal to the threshold.

[0543] 2) The shared COT received from the SL PEER UE overlaps / exists with the shared COT (e.g., SL TX allowed domain) received from the base station

[0544] 3) Situations where COTs for different SL services / broadcast types derived from the same CAPC value overlap / exist

[0545] For example, in the case of a shared COT in NR-U, only CAPC transmissions with a priority equal to or less than the associated CAPC value may be allowed.

[0546] For example, even when UL COT is used in SL, the restriction may be applied. Alternatively, for example, whether the above restriction is applied when UL COT is used in SL may be configured.

[0547] For example, data-related CAPC information of the SL PEER UE may be transmitted to the initiator through pre-configured signaling.

[0548] For example, a restriction based on an ED threshold (ie, maximum transmission power) may be applied. Alternatively, for example, whether a restriction based on an ED threshold (ie, maximum transmission power) is applied may be configured.

[0549] For example, in Mode 1 operation, the responder UE may report the shared COT information received from the SL PEER UE to the base station so that the base station may allocate Mode 1 resources within the shared COT.

[0550] For example, a NACK-only based feedback operation (or SL CSI reporting operation) may be allowed based on only the shared COT.

[0551] For example, FBE may be supported. For example, this may be for scenarios where there is no other NR-U operation coexisting even in REL-17. For example, in the case of SL-U, FBE in its current form may not be easily applied.

[0552] For example, if SL TX is performed on the first time slot of the UE FFP (eg, Mode 2), additional techniques may be required to inform the base station of COT sharing.

[0553] For example, COT sharing for a base station may be limited to the case where UL transmission (eg, ULCG / DG, PUCCH, CFRA PRACH) is performed on the first time slot of the UE FFP.

[0554] For example, the following types of actions may be allowed within the UE FFP:

[0555] -SL CG TX on first slot + UL CG / DG TX on subsequent slots within UE FFP

[0556] -SL DG TX on the first slot + UL CG / DG TX on subsequent slots within UE FFP

[0557] -UL CG TX on the first slot + SL CG / DG TX on subsequent slots within UE FFP

[0558] -UL DG TX on the first slot + SL CG / DG TX on subsequent slots within UE FFP

[0559] - It can be restricted to the same link type.

[0560] For example, it may be proposed how to configure UE FFP configuration in OOC (or idle / inactive state (eg, RRC release message may be used to configure UE-specific UE FFP configuration)).

[0561] For example, in the case of unicast, it can be negotiated between UEs through PC5 RRC signaling.

[0562] For example, in case of multicast, the UE FFP field may be randomized based on the destination ID.For example, randomization of the offset value may not be required.

[0563] For example, when determining the FFP value, the relationship (eg, divisor) with the SL SSB period, the bitmap period value of the resource pool (taking into account the periodic characteristics in the SL), etc. may be considered.

[0564] For example, after attempting to detect TX by another UE on the first time slot, the UE may act as a responder UE.

[0565] For example, at the beginning of FFP, collisions may be tolerated, but minimum non-critical signals required to ensure COT (eg, DUMMY RS, or data that can be resolved later by HARQ even if collisions occur) may be sent.

[0566] For example, based on the above method, even if the SL UE selects resources that are not aligned with the FFP start time, the SL UE can send DUMMY resources at the FFP start time. If the COT initiation of the SL UE is allowed as described above, the resource domain in which the DUMMY signal can be sent at the FFP start time can be preconfigured.

[0567] For example, a form may be proposed in which multiple FFPs with the same period but different offsets are configured and the UE selects one (eg, OOC).

[0568] In the In-Coverage (IC) case, a method may be proposed where idle / inactive UEs select an offset based on UE ID.

[0569] For example, COT sharing or COT formation for SSB TX may be proposed.

[0570] For example, when the UE provides the base station with a UE-initiated COT, the SL RX (expected) resources may also be considered. For example, this may be in the form of excluding the SL RX (expected) resources.

[0571] For example, a method of compensating SL transmission when UL COT cannot be used for SL may be proposed.

[0572] For example, if the shared COT duration is not covered by the SL resource pool, the duration may be used for UL purposes only.

[0573] For example, COT sharing may be allowed only between UEs belonging to the same base station. To this end, information to be exchanged / reported may be proposed.

[0574] For example, in the case of PSFCH, the RX UE may send the PSFCH based on the COT sharing of the TX UE.

[0575] For example, in the case of SL CSI reporting, another UE may send a SL CSI report based on the COT sharing of the UE that triggered the SL CSI reporting.

[0576] For example, UE2 may perform transmission based on the COT shared information of UE1. For example, the COT shared information may be sent through the SCI, or a SL MAC CE for the COT shared information may be newly defined.

[0577] For example, COT sharing information may be sent via PSFCH. This may be limitedly applicable to unicast or relay, for example. This may also be extended to multicast, for example.

[0578] For example, UE COT sharing may be determined based on whether another UE is in SL mode 1 or SL mode 2. For example, since a UE operating based on SL mode 1 may operate based on the COT of a base station, the UE COT may be shared only with SL mode 2 UEs. For example, the SL mode of a UE may be notified to another UE via an SCI or MAC CE. For example, an inter-UE coordination request MAC CE may be used.

[0579] For example, UE COT sharing may be determined based on whether the other UE utilizes a unicast connection or is in the same cell.

[0580] For ease of description, the following assumptions may be made. For example, in the case of LBE, F1 may refer to an ITS or licensed or unlicensed band and F2 may refer to an unlicensed band, and UE-A may be an SL mode 1 source UE, and UE-B may be a destination UE of a PSSCH transmitted by UE-A, and UE-C may be an SL mode 2 source UE, and UE-D may be a destination UE of a PSSCH transmitted by UE-C.

[0581] For example, in case 1-1, the COT initiator may be a base station.

[0582] For example, in case 1-1, if UE-A is instructed to perform a single LBT when receiving a SL grant from the base station, or if UE-A receives the COT information of the base station through F1 or F2 (such as in NR-U) and recognizes that the SL resources are included in the COT of the base station, UE-A can send SL data after a single LBT through COT sharing. Otherwise, UE-A can send SL data after a random backoff LBT.

[0583] For example, in case 1-1, if UE-B receives the COT information of the base station through F1 or F2 (such as in NR-U) and recognizes that the PSFCH resources to be sent to UE-A are included in the COT of the base station, UE-B can perform PSFCH transmission to UE-A after a single LBT through COT sharing. Alternatively, if UE-B receives COT information from UE-A and recognizes that the PSFCH resources to be sent to UE-A are included in the COT of UE-A, UE-B can perform PSFCH transmission to UE-A after a single LBT through COT sharing. This may be only the case where UE-A newly generates COT after a random backoff LBT, and only the case where COT sharing between UEs is allowed. Otherwise, for example, UE-B may perform PSFCH transmission to UE-A after a random backoff LBT.

[0584] For example, in case 1-2, the COT initiator may be UE-A.

[0585] For example, in case 1-2, if UE-A is instructed to perform random backoff LBT when receiving SL authorization from the base station, or if UE-A recognizes that SL resources are not included in the COT of the base station, UE-A can send SL data after random backoff LBT.

[0586] For example, in case 1-2, if UE-B receives COT information of the base station through F1 or F2 (such as in NR-U) and recognizes that the PSFCH resources to be sent to UE-A are included in the COT of the base station, UE-B can perform PSFCH transmission to UE-A after a single LBT through COT sharing. Alternatively, if UE-B receives COT information from UE-A and recognizes that the PSFCH resources to be sent to UE-A are included in the COT of UE-A, UE-B can perform PSFCH transmission to UE-A after a single LBT through COT sharing. For example, this case can be limited to the case where COT sharing between UEs is allowed. Otherwise, for example, UE-B can perform PSFCH transmission to UE-A after a random backoff LBT.

[0587] For example, in case 2-1, the COT initiator may be a base station.

[0588] For example, in case 2-1, if UE-C receives the COT information of the base station through F2 (such as in NR-U) and recognizes that the SL resource is included in the COT of the base station, UE-C can send SL data after a single LBT through COT sharing. Otherwise, for example, UE-C can send SL data after a random backoff LBT.

[0589] For example, in case 2-1, if UE-D receives the COT information of the base station through F2 (such as in NR-U) and recognizes that the PSFCH resources to be sent to UE-C are included in the COT of the base station, UE-D can perform PSFCH transmission to UE-A after a single LBT through COT sharing. Alternatively, if UE-D receives COT information from UE-C and recognizes that the PSFCH resources to be sent to UE-C are included in the COT of UE-C, UE-D can perform PSFCH transmission to UE-C after a single LBT through COT sharing. This may be only the case where UE-C newly generates COT after random backoff LBT, and only the case where COT sharing between UEs is allowed. Otherwise, for example, UE-D can perform PSFCH transmission to UE-C after random backoff LBT.

[0590] For example, in case 2-2, the COT initiator may be UE-C.

[0591] For example, in case 2-2, if UE-C recognizes that SL resources are not included in the COT of the base station, UE-C can send SL data after random backoff LBT.

[0592] For example, in case 2-2, if UE-D receives COT information of the base station through F2 (such as in NR-U) and recognizes that the PSFCH resources to be sent to UE-C are included in the COT of the base station, UE-D can perform PSFCH transmission to UE-C after a single LBT through COT sharing. Alternatively, for example, if UE-D receives COT information from UE-C and recognizes that the PSFCH resources to be sent to UE-C are included in the COT of UE-C, UE-D can perform PSFCH transmission to UE-C after a single LBT through COT sharing. For example, this case can be limited to the case where COT sharing between UEs is allowed. Otherwise, UE-D can perform PSFCH transmission to UE-C after a random backoff LBT.

[0593] For example, when there is COT#1 generated by the base station and COT#2 generated by UE-A (or when there is COT#1 generated by UE-B and COT#2 generated by UE-A), operations can be proposed when the third UE knows the information of both COT#1 and COT#2. In the case of existing NR-U, a similar situation may occur when two or more UEs send CG-PUSCH and each notifies the base station of different COT information through CG-UCI. At this time, for example, the base station can perform COT sharing based on the maximum / minimum duration of the two COTs. For example, in NR-U or LTE LAA, the base station can autonomously share any COT. At the same time, in the case of SL, different operations may be required. In the above example, if there are COT#1 generated by the base station and COT#2 generated by the SL UE at the same time, COT#1 generated by the base station can be prioritized. For example, in the above example, if two SL UEs generate COTs separately, the third UE can perform SL communication based on a single COT sharing information.

[0594] For example, in order to increase CW_p when a NACK is received, a feedback-disabled TB can be temporarily changed to feedback-enabled. For example, if all HARQ-ACK feedbacks of the PSSCH belonging to the reference duration are disabled, one or some PSSCH transmissions can be temporarily changed to feedback-enabled. In this case, the physical layer of the transmitting UE can autonomously change the feedback-disabled TB to a feedback-enabled TB and indicate it through the SCI, and the physical layer of the transmitting UE may or may not instruct the MAC layer to do so. For example, this can be limited to the case where the resource pool supports feedback enabling. For example, for unicast / multicast logical channels in the U band, only feedback-enabled resource pools can be selected.

[0595] For example, SL reservation may be performed in COT. In this case, the following method may be available.

[0596] - Method 1: The UE may not be able to obtain the COT including the resources indicated by other UEs through SCI.

[0597] - Method 2: The UE may obtain the COT regardless of the proposal of Method 1, and the UE may continuously reserve resources from N+1 to N+k-1 until resource N+k indicated by other UEs through SCI.

[0598] - Method 2-1: For N+k and subsequent resources, the UE can reselect the corresponding resources through reselection / re-evaluation to achieve continuous transmission. If reselection is not possible, the UE can stop transmission immediately after N+k-1.

[0599] - Method 3: The UE can obtain the COT regardless of the proposal of Method 1, and the UE can continuously reserve resources from N+1 to N+m, except for the resource N+k indicated by other UEs through the SCI. Among them, m < k, or m > k.

[0600] - Method 3-1: For the resource N+k, the UE can reselect the corresponding resource through reselection / re-evaluation to achieve continuous transmission. For example, if reselection for the resource N+k is impossible, the UE can stop transmission immediately after N+k-1. For example, if reselection for the resource N+k is impossible, the UE may not stop transmission immediately after N+k-1.

[0601] For example, a separate window can be configured for S-SSB transmission, which can guarantee the COT of the base station as much as possible. For example, by configuring the SL window, S-SSB can be sent based on Type 2A / B / C in the COT of the base station.

[0602] For example, there may be problems related to the physical channel design and / or structure and process.

[0603] For example, in the case of SL-U, the main objectives as commercial use cases have been discussed. However, since there may be broadcast signaling for various services (e.g., for session establishment / discovery purposes), broadcast-type signaling related to SL positioning, etc., it is necessary to consider broadcast types other than unicast when developing SL-U design / technology.

[0604] For example, a resource pool structure needs to be proposed.

[0605] For example, it is necessary to define the resource pool in the time domain.

[0606] For example, for SL communication between an RRC-connected UE and an idle UE or between an IC UE and an OOC UE, a common understanding of SL resources may be required.

[0607] As a reference, the time resource indicator value (TRIV) and the SL resource reservation interval can be operated / interpreted based on the logical index belonging to the resource pool.

[0608] For example, a definition of the minimum resources and extended resources (e.g., the SL communication target between IC UEs) that require a common understanding can be proposed. In this case, a mechanism for additionally signaling the extended resources to other UEs may be required.

[0609] For example, a distinction may be required between a pool that configures / permits PSFCH transmission / reception and a pool that does not configure / permits PSFCH transmission / reception.

[0610] For example, configuration of exception pools (eg, pools that perform random resource selection) may be required.

[0611] For example, rules related to the subchannel structure may be proposed. For example, mapping rules between the following parameters need to be defined.

[0612] -RB collection index

[0613] - Interweaving Index

[0614] -Subchannel Index

[0615] For example, considering the SL structure that allocates resources by a combination of TRIV and a frequency resource indicator value (FRIV), when the FRIV spans across RB sets, undesired resource allocation may occur. For example, if two resources are selected, the two resources are continuous in the time domain, but the two frequency resources selected by FRIV may belong to different RB sets. A method of reducing the TRIV / FRIV bit width by utilizing rules can be considered.

[0616] For example, in the case of an existing SL, scheduling based only on consecutive subchannel indices is possible. For example, if the FRIV indicator on the existing SCI is reused, the above principle can be maintained. Alternatively, for example, since the FRIV itself indicates the "starting subchannel index" and the "number of subchannels at consecutive positions on the frequency domain for PSSCH scheduling", the principle can be used as is. On the other hand, the scheduling principle based on consecutive subchannel indices may not be applied.

[0617] For example, there may be a form in which RB bundles having the same interleaving index for each RB set have consecutive subchannel indices. For example, the part may have two directions.

[0618] The first direction is to sequentially assign each interleave in a row in a manner of RB set index first - interleave index second (for example, in the case of two RB sets, interleave 0 in RB set 0, interleave 1 in RB set 0, ..., interleave 0 in RB set 1, interleave 1 in RB set 1, ...), and the second direction is to sequentially assign each interleave in a row in a manner of interleave index first - RB set index second (for example, interleave 0 in RB set 0, interleave 0 in RB set 1, interleave 1 in RB set 0, interleave 1 in RB set 1, ...).

[0619] For example, subchannel indexing may be performed at an RB set granularity (e.g., when a scheduling principle based on consecutive subchannel indexes is applied, the probability of TX drop due to LBT failure may be reduced). Alternatively, for example, subchannel indexing may be performed at an SL BWP granularity (similar to NR-U). Considering in-band transmission, consecutive subchannel indexes (within an RB set) may be configured to have gaps in the frequency domain.

[0620] For example, based on the above operations, even if the SL UE transmits across multiple RB sets (unlike the NR-U UE), the SL UE may not transmit on resources on the middle protection band of the multiple RB sets. Therefore, the impact on in-band transmission with / between other UEs can be reduced (although its own peak-to-average power ratio (PAPR) may be slightly affected).

[0621] For example, it is necessary to look at two cases where an interleaving structure is configured and where an interleaving structure is not configured.

[0622] For example, if no interleaving structure is configured, it is necessary to check whether the existing SL sub-channelization structure can be reused. In addition, it is necessary to check whether there are any problems, such as PSD requirements are met, guard bands exist, etc.

[0623] For example, this may be a question of how to perform sub-channelization when guard bands are configured but interleaving is not configured. For example, a sub-channel may be configured with only RBs that do not include a guard band, or a sub-channel may be configured to include a guard band, but the availability of a sub-channel that overlaps with the guard band may vary depending on whether one or more RB sets are transmitted.

[0624] For example, rules related to guard band usage may be proposed.

[0625] For example, it may be configured whether sub-channelization is required in the guard band.

[0626] For example, it may be configured whether sub-channelization is performed only within an RB set.

[0627] For example, only RBs within a guard band corresponding to an interleaving index scheduled / selected based on sensing may be used within an RB set.

[0628] For example, for RBs within the guard band, a separate sensing operation may not be performed.

[0629] For example, if sub-channelization is performed for RBs within the guard band, it may be different from the sub-channel size within the RB set.

[0630] For example, rules related to TX-RX switching gaps may be proposed.

[0631] For example, a method for reducing one symbol time gap between SL TX and SL TX or between SL TX and SL RX may be proposed.

[0632] For example, sub-symbol extension may be applied before the SL TX start symbol.

[0633] For example, when overlap occurs between SL TX and UL TX, the overlapping (sub) symbols may be only partially discarded to prevent excessive gaps between SL TX and UL TX.

[0634] For example, alternative schemes may be proposed to reduce the time gap between the PSSCH end symbol and the PSFCH start symbol within a time slot, as well as the existing form of PSFCH resource configuration.

[0635] For example, according to the NR-U specification, the size of the time slot itself can be 16 microseconds and 25 microseconds, and according to the 15kHz / 30kHz / 60kHz SCS, the relationship with the symbol duration needs to be considered. For example, in order to provide a time slot, CP extension can be performed for PSFCH. For example, in order to provide a time slot, the last symbol extension can be performed for PSSCH.

[0636] For example, if a SL structure in which multiple SL UEs simultaneously send PSFCH at a semi-static position is considered, the PSFCH can always start at the symbol boundary as described above, and the PSSCH before the PSFCH can be sent in an extended manner, and the COT information can be sent through the SCI, and the SL UE that has received the COT information can perform appropriate LBT.

[0637] For example, the above method may be limited to the case of COT sharing.

[0638] For example, the configuration of the position of the SL UE common (or COT shared UE common) LBT duration before the PSFCH start symbol may be considered. For example, this is intended to alleviate the problem of LBT failure associated with PSFCH transmission caused by extended symbols.

[0639] For example, rules related to the PSCCH and PSSCH structures may be proposed.

[0640] For example, it may be configured whether to reuse the FDM / TDM format between the existing PSCCH RE and PSSCH RE.

[0641] For example, in the case of NR-U, when the base station performs broadcast channel (e.g., SSB) transmission, etc., it was discussed how to apply / operate interleaving, but it was ultimately not introduced into DL.

[0642] For example, it may be configured whether it is necessary to maintain the existing FDM grant condition between PSCCH RE and PSSCH DMRS RE.

[0643] For example, rules related to the PSFCH structure may be proposed.

[0644] For example, a SL channel format may be introduced that can transmit information similar to CG-DFI. For example, it may be SCIONLY or PSCCH / PSSCH or PUCCH format 1.

[0645] For example, in case of LBT failure, a configuration may be made to use the existing PSFCH format but with an increased number of symbols.

[0646] For example, when an interleaving structure is applied, the number of symbols associated with the existing PSFCH format can be increased in the time domain (eg, T-OCC can be applied to the remaining PSFCH symbols except for the AGC symbols), thereby alleviating the problem of reduced multiplexing (MUX) capacity.

[0647] For example, a preconfigured number (e.g., 2) of PSFCH symbols may be grouped, and a TX-RX switching gap, LBT duration, etc. may be defined between the grouped PSFCH symbols.

[0648] For example, in the case of a large payload format, the transmission format may be a UE group common reception structure (eg, when multiple TX UEs transmit data to one RX UE).

[0649] For example, in the case of existing NR-U, the PDCCH / PDSCH RB set and the PUCCH RB set may be different (e.g., the PUCCH resource indication indicates the RB set).

[0650] For example, for SL-U UE, the PSCCH / PSSCH RB set and the PSFCH RB set may always be the same. For example, for SL-U UE, the PSCCH / PSSCH RB set and the PSFCH RB set may be different.

[0651] For example, an implicit association may be defined between PSSCH resources and PSFCH resources within the same RB set.

[0652] For example, SL SSB (SPSS+SSSS+PSBCH) structure related rules can be proposed.

[0653] For example, it is necessary to check whether there is a problem in applying the interleaving structure at the RB granularity.

[0654] For example, a method of adapting SL SSB of 11 RB to the interleaving structure of 10 RB (eg, 15 kHz SCS) may be proposed.

[0655] For example, it is possible to configure whether to allow FDM utilizing DUMMY data.

[0656] For example, the network may ensure that there is an interlace with 11 RBs.

[0657] For example, if the PSBCH mapping resource domain is increased along the frequency domain to achieve the target coverage of the PSBCH with a smaller number of symbols (e.g., coding rate gain), the remaining symbols within the SL time slot can be defined for other purposes, or the PSBCH information can be sent repeatedly.

[0658] For example, a form of increasing the sequence length, such as NR-U PRACH, may be considered.

[0659] For example, it may be suggested how to define or position the protection RE.

[0660] For example, if there are multiple RB sets, you can configure whether to define SL SSB transmit / receive candidate resources only within one RB set. For example, if there are multiple RB sets, you can configure SL SSB transmit / receive candidate resources only within one RB set. For example, if there are multiple RB sets, you can configure SL SSB transmit / receive candidate resources across multiple RB sets.

[0661] For example, if FDM is allowed between SL SSB TX and other SL channel TX, it may be necessary to check the power allocation / coverage imbalance between them. In addition, it may be proposed how the TX UE can determine that the target RX UE does not perform SL SSB transmission on the SL SSB resources.

[0662] For example, a TBS calculation method can be proposed.

[0663] For example, when RBs are used in a guard band, a TBS calculation method may be proposed.

[0664] For example, it may be configured whether to calculate the TBS in consideration of the number of RBs in the guard band. For example, the TBS may be derived by considering only the number of RBs within the RB set.

[0665] For example, if there are orphan RBs in the RB set that do not match the subchannel size, a TBS calculation method may be proposed.

[0666] For example, using isolated RBs, the isolated RBs may not be considered in TBS calculation.

[0667] For example, it may be suggested that TRIV and FRIV need to be modified.

[0668] For example, you can configure whether to reuse the PUSCH scheduling form (RB set + interleaving index) of NR-U.

[0669] For example, SL power control related rules may be proposed.

[0670] For example, it may be configured whether to derive DL PL based on detection of non-PLMN cells in the unlicensed band.

[0671] For example, it may be configured whether SL communication (eg, including COT sharing) between UEs of different PLMNs on an unlicensed band is considered / possible. For example, it may be configured whether this form is allowed in existing SL operation.

[0672] For example, the PLMN information may be included in the non-relay discovery signaling related to the SL communication. If the PLMN information is included in the non-relay discovery signaling related to the SL communication, it may be used for session establishment.

[0673] For example, an entity providing a SL configuration for performing SL communication may be configured.

[0674] For example, it is possible to configure whether the UE performs SL communication only using the SL configuration provided by its own PLMN-related base station.

[0675] For example, rules related to SL CSI reporting may be proposed.

[0676] For example, in the case of SL, SL-RS transmission resources may be limited to the scheduling domain of PSSCH and may only support aperiodic CSI reporting operations.

[0677] For example, rules related to SL RSRP measurement reporting may be proposed.

[0678] For example, rules related to the SL synchronization process can be proposed.

[0679] For example, issues related to multi-channel access can be raised.

[0680] For example, it is necessary to consider the scenario of sending multiple PSFCHs simultaneously on multiple RB sets. For example, even within an RB set, a situation may occur where PSFCHs with different characteristics need to be transmitted simultaneously. In this case, a method for handling PSFCH TX based on Type 1 LBT may be considered. For example, it may be possible to configure whether to apply multi-channel access.

[0681] For example, simultaneous transmission of PSFCH TX based on Type 1 LBT and PSFCH TX based on Type 2 LBT may be considered.

[0682] For example, it is possible to configure whether the DL multi-channel access procedure is applied only to PSFCH TX based on Type 1 LBT.

[0683] For example, the possibility that the CAPC value is different for each PSFCH TX may be considered.

[0684] For example, in case of multiple PSFCH TX, the lowest CAPC or the highest CAPC may be applied. For example, especially in the case where each PSFCH is sent to a different UE, the lowest CAPC or the highest CAPC may be applied to multiple PSFCH TX.

[0685] For example, UL multi-channel access in NR-U can be reused.

[0686] For example, in the case of NR-U, if PUCCH transmissions of different LBT types overlap, the last indicated LBT type may be applied.

[0687] For example, the last criterion may be applied when sending multi-bit PSFCH to the same UE.

[0688] For example, there may be problems due to the coexistence of LAA cells and NR-U cells on the U band.

[0689] For example, when an NR SL-U UE selects an LAA cell as its synchronization reference source, a method for expressing the LTE TDD U / D configuration (e.g., special SF) through the NR PSBCH may be required.

[0690] For example, a method for supporting SL operation under LAA cell of type 3 may be proposed. For example, it may be configured whether to perform SL operation by considering all flexible (ALL FELXIBLE) forms.

[0691] For example, there may be problems with multi-slot scheduling.

[0692] For example, in the case of SL sensing operation, a method may be proposed to derive idle candidate resources consisting of N SL resources that are continuous (or have an interval less than or equal to 16 microseconds) in the time domain.

[0693] For example, the maximum SL RSRP value measured on N SL resources may be less than or equal to the threshold.

[0694] For example, if different HARQ process related data can be sent for each of the N SL resources, such as in NR-U, then the method of determining the associated PUCCH timeline / resource in Mode 1 may need to be changed. For example, this may be the case where the locations of the PSFCH resources associated with the N SL resources are not the same.

[0695] For example, in NR-U, in case of multi-slot scheduling, it is possible to configure whether some of N are available for initial transmission and retransmission of the same HARQ process ID.

[0696] For example, in the case of NR UL, the number of HARQ processes can be fixed to 16.

[0697] For example, the maximum number of available SL HARQ processes may be configured per multi-slot scheduling grant.

[0698] For example, unused bits may be indicated as ACK or new status.

[0699] For example, the feedback payload may be specified as the maximum number of bits for the available SL HARQ processes.

[0700] For example, ACK / NACK may be stacked in transmission order.

[0701] For example, ACK / NACK may be stacked in ascending / descending order of HARQ process ID.

[0702] For example, a method of indicating an SL CSI report request may be proposed.

[0703] For example, if SL CSI report requests are allowed via SCI on multiple SL resources among N, the RX UE may be configured whether to start the latency budget timer based on the location of the last received request. For example, if SL CSI report requests are allowed via SCI on multiple SL resources among N, the RX UE may start the latency budget timer based on the location of the last received request.

[0704] For example, when an interleaved PRB structure is not configured, a method for processing a guard band may be proposed.

[0705] For example, in case sub-channelization is not applied, it may be used as an exception only when multiple RB sets are used.

[0706] For example, in the case of SL-U, the reuse requirement for RA type 0 / 1 for NR-U UL may be lower.

[0707] For example, PSCCH and / or 2ND SCI mapping resources may be proposed.

[0708] For example, PSCCH and / or 2ND SCI mapping resources may be limited to resources within one RB set.

[0709] For example, considering the possibility that multiple SL resources indicated by a PSCCH may be located on different RB sets, and the possibility that actual SL transmission is performed only on some LBT-successful RB sets among the SL authorization-related resources located on multiple RB sets, especially if COT sharing information is sent via the first SCI (and / or the second SCI), the first SCI can be sent on all RB sets in the multiple RB sets.

[0710] For example, it may also be considered that the TX UE sends multiple RB sets simultaneously.

[0711] For example, there might be a resource pool related issue.

[0712] For example, the COT duration may be configured.

[0713] For example, COT may be defined based on absolute time (eg, ms), such as NR-U.

[0714] For example, processing may be required for the case where the SL time slots belonging to the resource pool do not always exist within the COT.

[0715] For example, if the SL SSB does not belong to the resource pool, some time slots within the COT length that do not belong to the resource pool can be used for SL SSB transmission (for example, UL transmission can also be considered).

[0716] For example, a COT may be defined as a set of SL time slots belonging to a resource pool.

[0717] For example, the start time of COT generation can be limited to the time of the SL time slot belonging to the resource pool, and the maximum COT length that can be configured by MIN{the length of the SL time slot belonging to the continuous resource pool in the time domain, the maximum COT length based on CAPC} can be determined. Here, MIN{X, Y} can be the smaller value between X and Y.

[0718] For example, the COT may be configured based on logical SL time slots.

[0719] For example, in the case of NR-U, in the case of a single U / D switching, it can be configured whether gaps of multiple time slots are also allowed within the COT.

[0720] For example, multi-slot scheduling can be proposed.

[0721] For example, the number of resources associated with multi-slot scheduling may be limited by the number of SL slots belonging to a continuous resource pool in the time domain.

[0722] For example, there may be issues associated with SL SSB transmissions.

[0723] For example, in order to generate a COT for SL SSB transmission, a predefined CAPC value (eg, 4) is required.

[0724] For example, within the COT, it can be configured whether all SL SSB transmissions are possible within one SLSS cycle.

[0725] For example, for SL SSB transmission (or for a UE sending (and / or receiving) SL SSB), a COT type or shared COT operation may be configured to be performed.

[0726] For example, COT sharing can be proposed.

[0727] For example, SL SSB related COT sharing can be proposed. In this case, the following information can be considered.

[0728] - Granularity: COT sharing based on synchronization source type, COT sharing through synchronization hops (e.g., direct, indirect, etc.)

[0729] -COT shared information signaling: reserved bits on SCI, PSBCH (including information such as SLSSID, synchronization source type, synchronization hop, etc.)

[0730] For example, SL SSB transmissions may be allowed in any shared COT (without any restrictions).

[0731] For example, it is possible to configure whether data transmission is allowed in the COT associated with SL SSB transmission.

[0732] For example, if the SL SSB TX meets the requirement of transmitting within 1 ms within a 20 ms duty cycle, the SL SSB TX may also apply Type 2 ALBT.

[0733] For example, in the case of IC, whether it is short control signaling can be configured by the network.

[0734] For example, in the case of OOC, it may be considered (by default) that it is not short control signaling. For example, in the case of OOC, it may be (pre) configured whether it is short control signaling.

[0735] For example, there may be issues related to SL DRX.

[0736] For example, Uu DRX operation in U-band can be applied to SL-U.

[0737] For example, if a separate enhancement is introduced to consider the possibility of omitting PDCCH transmission based on LBT failure, the enhancement can be applied to SL-U.

[0738] For example, there may be problems with the channel access mechanism.

[0739] For example, considering energy saving, a channel access mechanism needs to be designed. Therefore, method (A) needs to be considered.

[0740] [Method (A)]: After LBT-based COT generation, SL sensing / resource selection (SL grant generation) is performed within the COT

[0741] Fig.16 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown. Fig.16 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0742] Reference Fig.16 In the case of scenario 1, the reselected resource or PSFCH resource (e.g., the case where the TX UE can determine the PSFCH resource location, the case where the PSFCH resource is repeated) may be located in the sensing window or the T_PROC0 domain. For example, in the case where the resource is to be reselected, information on whether to reselect may be notified in advance through the previous SCI.

[0743] For example, SL sensing for SL grant generation may be performed.

[0744] For example, in the case of the existing NR-U, when COT is initiated by the base station, only the time slots in which the base station actually performs DL TX and the time slots in which the base station schedules UL TX for the UE can be reflected in the COT reduction. That is, the gap between them may not be reflected in the COT reduction.

[0745] For example, in the case where COT is initiated by the UE, the above principle may not be applied. That is, if there is a gap between scheduled UL resources, the time slot associated with the gap may also be reflected in the COT reduction.

[0746] Example 1) If a UE that succeeds in LBT in time slot 4 performs COT sharing, the UE that receives it can perform transmission based on short LBT within the shared COT.

[0747] Example 2) Even if LBT fails in time slot 4, the UE may additionally perform LBT on subsequent time slots, and the UE may generate a COT using the result.

[0748] For example, in the case of scenario 1 / 2, refer to Fig.16, according to the COT definition, the start time of the COT can be shifted based on the time when the actual transmission starts (e.g., SELF-DEFERRAL). For example, it may not be easy to exploit the resource (re)selection effect based on SL sensing. For example, transmission resource selection cannot be performed on the first time slot within the COT. For example, a solution can be proposed to perform random resource selection in the front area within the COT and perform resource selection based on SL sensing in the rear area. For example, it can be used within a shared COT.

[0749] For example, in the case of scenario 2, a UE that has performed COT sharing may perform resource selection / transmission on time slots 5 / 6.

[0750] For example, in the case of scenario 3, assuming that LBT is successful, there may be complications in repeatedly performing the resource selection process based on SL sensing. For example, within the COT, a method that allows transmission resource selection on the first time slot and a method that allows resource selection based on consecutive time slots may still be needed.

[0751] For example, in the case of method (A), the direction of priority use in the COT sharing scenario can be considered.

[0752] For example, the direction of reducing SL processing time can be considered.

[0753] For example, only the gap between the start time of the selection window (or the first selected resource time or the time triggering resource selection) and the LBT time can be defined, and the satisfaction of the remaining processing time can be UE-implemented.

[0754] For example, if another UE reserves / selects forward resources on the COT after LBT succeeds, it can be configured whether the UE can use them.

[0755] For example, a mechanism for sharing resources in the form of FDM within a COT may be proposed.

[0756] For example, the UE may anticipate that another UE will form a COT on the resources it has reserved, and may exclude it. For example, this may be a situation where another UE has already initiated operation based on method (B).

[0757] For example, the base station may share COT initiated by the base station with multiple UEs, and the UEs may share FDM resources with each other.

[0758] [Method (B)]: After performing SL sensing / resource selection (generating SL authorization), determine whether the corresponding resource is actually used based on LBT

[0759] Fig.17A method for performing SL communication in an unlicensed band according to 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.

[0760] For example, when feedback for data on resource 1 is sent through PSFCH on resource 2, the TX UE may be caused to select resources for data transmission on resource 2. Through this, there may be a single LBT gain of PSFCH.

[0761] For example, in the case of unicast, PSFCH may be piggybacked on the data on resource 2. For example, it may be in the form of UCI or MAC CE.

[0762] Fig.18 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown. Fig.18 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0763] For example, a resource reselection condition related to SL authorization may be proposed. For example, a resource reselection condition related to SL authorization may include LBT failure. For example, T_PROC1 may end in time slot 10, and considering the possibility of reselecting resource 2 based on LBT failure, the UE may pre-select resource 2'. In fact, if this event occurs, the UE may utilize resource 2'. For example, the UE may add additional resource 2'. Alternatively, if the above event does not occur, the UE may release additional resource 2'. For example, signaling for adding an indication or releasing an indication may be defined.

[0764] Fig.19 A method for performing SL communication in an unlicensed band 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.

[0765] Fig.19 The embodiments show situations that trigger preemption or re-evaluation.

[0766] Fig. 20 A method for performing SL communication in an unlicensed band 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.

[0767] Reference Fig. 20, the UE may relocate the SL grant-related resources to the position of (continuous) time slots within the newly formed COT. For example, the synchronization that should be separated in the time domain when selecting the initial SL grant-related resources may be configured. For example, when reserving periodic resources for different MAC PDU transmissions, the synchronization that should be separated in the time domain may be configured.

[0768] For example, a method for implicitly determining the release of resources may be proposed.

[0769] For example, if the gap between selected resources is not large, there is a possibility that the subsequent resources cannot be used due to LBT failure. Considering this, a method for reselecting resources to have a specific gap or a larger gap may be required.

[0770] For example, a method for making up other SL grant-related resources, or a method for making up by generating additional retransmission-related SL grants, instead of relocating existing generated SL grant resources (eg, condition-based operation), may be proposed.

[0771] Fig.21 A method for performing SL communication in an unlicensed band according to an embodiment of the present disclosure is shown. Fig.21 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0772] Reference Fig.21 , the UE may move the SL grant-related resources into the shared COT. For example, even if the UE reselects resource 2 as resource 2', the UE may consider reusing the existing resource 2. For example, if an idle resource in a position of a continuous time slot is found as a result of performing additional SL sensing, the UE may reallocate the SL grant-related resources to the position.

[0773] For example, when resource 2 is reselected, resource 2 may be moved with the PSFCH based on the timeline with the PSFCH. Alternatively, if resource 2 is not moved with the PSFCH resource, HARQ feedback may be disabled. If the moved resource does not meet the HARQ timeline, HARQ feedback may be disabled.

[0774] For example, if the UE can determine that there is no actual transmission on the PSFCH resources associated with the PSSCH (eg, a case of WI-FI occupancy), the UE can use the corresponding PSFCH resources as data resources.

[0775] For example, in all the examples discussed in method (B), resource 1 and resource 2 may be associated with different SL grants, or may be associated with different MAC PDUs.

[0776] For example, when selecting resources associated with different MAC PDUs or resources associated with different SL grants, the emphasis may be on prioritizing adjacent time slots of existing SL grant associated resources.

[0777] [Method (A) + Method (B)]:

[0778] For example, the UE may operate based on method (B) by default, but may apply method (A) when reselecting resources.

[0779] For example, method (A) may be useful when COTs are shared.

[0780] For example, you can configure whether to allow hybrid mode per resource pool or per BWP.

[0781] [Method (C)]:

[0782] After LBT succeeds, resources on consecutive time slots are selected, but in the frequency domain, they are randomly selected.

[0783] For example, when operating based on a shared COT, resource selection restrictions on consecutive time slots may not apply.

[0784] [Method (D)]:

[0785] A form that triggers additional selection of required resources based on LBT failure without completing the selection of all relevant resources when the SL authorization is generated

[0786] For example, FBE can be proposed.

[0787] For example, it may be configured whether base station based FBE makes sense (eg, particularly with respect to Mode 2 SL-U UEs).

[0788] For example, it can be configured whether FBE boundaries need to be randomized (e.g., especially in the case of OOC).

[0789] For example, L2 DST ID-based FBE can be configured.

[0790] For example, in the case of unicast, FBE can be determined between UEs through PC5 RRC.

[0791] For example, operation in Mode 1 may be proposed.

[0792] For example, an LBT type indication may be raised in mode 1.

[0793] For example, in the case of SL resources with large time gaps in the time domain, it is possible to configure whether the LBT type indication is possible.

[0794] For example, the spread associated with the propagation delay in Mode 1 may be considered.

[0795] For example, when generating a SL authorization, you can configure whether to additionally use the LBT result to apply resource exclusion.

[0796] For example, it is possible to configure whether the conflict between UL and SL between UEs requires special processing.

[0797] For example, when LBT for multiple RB sets is successful, the UE may select SL grant-related resources limited to one RB set. For example, when LBT for multiple RB sets is successful, the UE may select SL grant-related resources in the form of TDM or FDM on multiple RB sets.

[0798] For example, if a collision occurs between UL TX and SL TX, extension of the subsequent SL TX may be required to perform the subsequent SL TX based on a single LBT.

[0799] For example, if the maximum TX power value configured between UL TX and SL TX is different, it is possible to configure whether single LBT is impossible between adjacent UL / SL TXs. For example, if the maximum TX power value configured between UL TX and SL TX is different, it is possible to configure whether to adjust the transmit power of a specific TX.

[0800] For example, the location of the LBT duration between SL-U UEs may be defined. For example, in order to mitigate conflicts between SL-UE UEs based on LBT, the location of the LBT duration between SL-U UEs may be defined.

[0801] For example, a UE common position may be generated, but depending on the priority, the length of the CP extension may be configured differently. For example, in the case of S-SSB and / or PSFCH, a UE common position for CPE extension may be generated, but in the case of PSCCH and / or PSSCH, the length of the CP extension may be determined / configured differently depending on the priority.

[0802] For example, a resource / channel structure that takes into account PSD and OCB requirements can be proposed.

[0803] For example, in the case of a resource pool, the resource pool may be a unit larger than a subchannel, for example, a resource pool may be composed of one or more subchannels. For example, it may be configured whether the frequency size of a single resource pool is equal to the LBT-BW (e.g., 20 MHz). For example, it may be configured whether to operate multiple resource pool frequencies within one LBT-BW. For example, it may be configured whether to consider a resource pool structure spanning multiple LBT-BWs. For example, in this case, it may be configured to operate only for successful LBT configurations of certain LBT BWs.

[0804] For example, in the case of subchannels, the subchannel size in the existing SL can be 10 / 12 / 15 / 20 / 25 / 50 / 75 / 100 RBs. For example, in SL-U, it can be configured whether to change the subchannel size to 1 / 2 / … RB interleaving. For example, if the frequency of a resource pool or a single SL TX is limited to a single LBT-BW, it can be configured whether to define the maximum subchannel size differently depending on whether the SCS is 15kHz or 30kHz. For example, in NR-U, in the case of a 15kHz SCS, it can be 100 RBs per 20MHz, and in the case of a 30kHz SCS, it can be 50 RBs per 20MHz. Alternatively, for example, in order to maintain a maximum subchannel size of 100 RBs, the subchannel can be limited to one LBT-BW (20MHz) for 15kHz and limited to two LBT-BWs (40MHz) for 30kHz. For example, from the perspective of FDRA, the configuration / instruction for the combination of subchannels and resource pools can be considered in the form of configuring / indicating a combination of an RB interleaving index (with X bits) and an LBT-BW index (with Y bits), similar to the NR-U structure. For example, when a SL resource unit / structure such as a subchannel is changed to RB interleaving as described above, it is necessary to check whether there is a problem with the SL sensing operation of such an RB interleaving unit.

[0805] For example, in the case of PSFCH, it may be necessary to change to an RB interleaving structure by default. However, the resulting capacity reduction (compared to the existing SL) may also need to be considered. For example, it may be configured whether to support up to TDM by adding X symbols. For example, X may be 1 or 2 (with LBT gaps). For example, it may be configured whether to apply TD-OCC by adding Y symbols. For example, Y may be 1. In this case, the symbol / OCC domain also needs to be considered when indexing PSFCH RB subsets and indexing resources within a PSFCH resource set. For example, it may be configured whether a sub-RB interleaving or RE-level interleaving (IFDMA) structure is required. For example, when selecting N PSFCH transmissions, it may be configured whether not only the maximum power but also the PSD limit is considered. For example, when N PSFCHs are sent by interleaving multiple RBs using FDM, in addition to the maximum power and PSD limits, it may also be configured whether PAPR / CM performance is considered. For example, a good interleaving / CS combination with FDM capability may be considered.

[0806] For example, in the case of PSCCH / PSSCH / S-SSB, if only one resource pool is considered per LBT-BW frequency, it is possible to configure whether the change is unnecessary. For example, if FDM is considered between multiple resource pools within the LBT-BW, it is possible to configure whether to change to an RB interleaved structure. For example, in the case of S-SSB, since the SL cannot guarantee simultaneous transmission of SSB and other FDM signals (e.g., PSXCH) from the base station (like DL), the OCB requirements may not be met, and if the PSD limit is reached (because it is a UE transmission), the TX power may be insufficient, resulting in problems in SL coverage. Therefore, it is possible to configure whether to change to an RB interleaved structure. For example, it is possible to configure whether to configure an S-SSB with a wide bandwidth of 20 MHz to reduce the symbol duration, thereby providing two S-SSB transmission opportunities within one SL time slot.

[0807] For example, an SL time slot structure considering LBT and an LBT configuration considering SL operation may be proposed.

[0808] For example, in the case of a time slot format, it can be configured whether the gap required for LBT operation including backoff is sufficient for one symbol currently defined for Tx-Rx switching. For example, it can be configured whether to increase the number of symbols based on the backoff size / statistics. However, it may be effective to have a certain degree of gap alignment between UEs. For example, if LBT fails just before SL resource transmission, it can be configured whether to discard all or part of the AGC symbol signal and retry LBT. For example, when configuring SL-TDD-Config, it can be configured whether to consider minimizing / preventing the gap required for LBT.

[0809] For example, in the case of LBT parameters, when operating in FBE mode, the FFP period / offset per UE / pool can be configured. For example, it can be configured identically between UEs or differently per UE. For example, it can be configured only for a specific UE, and COT sharing can be allowed only for the remaining UEs. For example, when operating in LBE mode, LBT / CPE parameters per UE / pool can be configured. For example, it can be configured whether the LBT parameters of SL can be indicated via Uu in mode 1. For example, the indication method can also be configured in mode 2. For example, when the source UE indicates Category 2 / 4 LBT to the target UE via SCI to indirectly notify whether its own COT initiation has been performed, other UEs receiving it can also distinguish whether the transmission signal of the source UE is within the initiating COT or the shared COT.

[0810] For example, for LBT considerations, for S-SSB, it can be configured whether multiple S-SSB time slots are configured per cycle to provide additional LBT opportunities. For example, when reporting SL A / N to the base station, if the TX UE fails to send the PSSCH due to LBT failure, the operation of the TX UE can be proposed. For example, the COT initiating UE can be limited to synchronization reference UEs, multicast TX UEs, etc. For example, it can be configured whether the gap block required for LBT (immediately before the resource) is considered in the resource selection. For example, it can be configured whether the LBT failure of the previous resource is considered in the resource selection. For example, if the PSFCH time slot is semi-statically configured, it can be configured whether to dynamically specify the PSFCH time slot timing to encourage transmission within the COT. For example, if this is implemented implicitly, the association between the PSSCH time slot and the PSFCH time slot can be determined locally based only on the time slots within the COT. For example, the above dynamic or local method may not be expected due to possible mismatches with other UEs outside the COT. For example, considering LBT failure in U band, the mapping between PSSCH resources and PSFCH resources can be configured as 1:M instead of 1:1, and the UE can use the resource that first succeeds in LBT among M for transmission. For example, if the existing PSFCH structure within the SL time slot (without TDM) should remain as it is, the current PSSCH time slot:PSFCH time slot=N:1 structure can be extended to N:M form.

[0811] For example, if a consistent LBT failure occurs for a specific RB set, the UE may always exclude the RB set when selecting resources. Alternatively, for example, if a consistent LBT failure occurs for a specific RB set, the UE may deprioritize the selection of idle resources on the RB set in resource selection. For example, in the case of deprioritization, the UE may exceptionally use idle resources on the RB set only when the number of resources required for TB transmission in the remaining RB set is insufficient. For example, when the UE obtains idle resources based on sensing, the UE may ensure X% of candidate resources from the remaining RB set. For example, on the RB set where the problem occurs, the UE may ensure / reinforce candidate resources by applying a preconfigured separate percentage.

[0812] In an embodiment of the present disclosure, the channel access type and whether / how to indicate can be applied differently to the method for each SL channel. In an embodiment of the present disclosure, the channel access type and whether / how to indicate can be applied differently to the method depending on the type of information included in the SL channel.

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

[0814] Reference Fig. 22 In step S2210, the first device may obtain information related to resources for a sidelink synchronization signal block (S-SSB). In step S2220, the first device may obtain information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission. In step S2230, the first device may perform a first CPE during a first time domain before S-SSB transmission. In step S2240, the first device may perform S-SSB transmission based on the resources.

[0815] For example, the length of the first time domain may be configured as a value.

[0816] In addition, for example, the first device may obtain information related to a resource set for performing a channel access process in a shared spectrum. For example, based on a listen-before-talk (LBT) failure for a resource set, resource reselection may be triggered by the first device. For example, based on a failure of LBT for a resource set, a radio link failure (RLF) for a unicast connection may be declared by the first device. For example, based on a failure of LBT for a resource set, information related to the LBT failure may be sent by the first device to a base station. For example, based on a failure of LBT for a resource set, the first device may change a resource set to a resource set different from the resource set.

[0817] Additionally, for example, the first device may obtain information about a second time domain for a second CPE associated with a physical sidelink feedback channel (PSFCH) transmission. Additionally, for example, the first device may receive a physical sidelink shared channel (PSSCH). Additionally, for example, the first device may determine a PSFCH resource for PSFCH transmission in response to receiving the PSSCH. Additionally, for example, the first device may perform a second CPE during a second time domain prior to the PSFCH transmission. Additionally, for example, the first device may perform a PSFCH transmission based on the PSFCH resource. For example, the length of the second time domain may be configured as a value.

[0818] For example, a channel access priority class (CAPC) value for generating a channel occupancy time (COT) for S-SSB transmission may be predefined.

[0819] In addition, for example, the first device may perform the third CPE during the third time domain for the third CPE. For example, the length of the third time domain may be determined based on the priority.

[0820] For example, an S-SSB transmission may include multiple S-SSBs repeatedly sent in the frequency domain.

[0821] In addition, for example, the first device may obtain information indicating a first number of S-SSB transmissions in an S-SSB transmission cycle in a shared spectrum. For example, the first number may be greater than a second number of S-SSB transmissions configured in a licensed spectrum. For example, the first device may be allowed to perform a second number of S-SSB transmissions in an S-SSB transmission cycle based on listen-before-talk (LBT). For example, the first device may not be allowed to perform more than a second number of S-SSB transmissions in an S-SSB transmission cycle based on LBT.

[0822] The proposed method can be applied to devices based on various embodiments of the present disclosure. First, the processor 102 of the first device 100 can obtain information related to resources for a sidelink synchronization signal block (S-SSB). In addition, the processor 102 of the first device 100 can obtain information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission. In addition, the processor 102 of the first device 100 can control the transceiver 106 to perform a first CPE during a first time domain before the S-SSB transmission. In addition, the processor 102 of the first device 100 can control the transceiver 106 to perform S-SSB transmission based on the resource.

[0823] According to an embodiment of the present disclosure, a first device suitable for performing wireless communication may be provided. For example, 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 may be executed by the at least one processor so that the first device performs operations including the following items: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing the first CPE during the first time domain before the S-SSB transmission; and performing the S-SSB transmission based on the resources.

[0824] Based on an embodiment of the present disclosure, a processing device suitable for controlling a first device may be provided. For example, 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 may be executed by the at least one processor to enable the first device to perform operations including the following items: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing the first CPE during the first time domain before the S-SSB transmission; and performing the S-SSB transmission based on the resources.

[0825] Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, when the instructions are executed, a first device may perform operations including: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); obtaining information about a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission; performing a first CPE during a first time domain before S-SSB transmission; and performing S-SSB transmission based on the resources.

[0826] Fig.23 A method for a second device to perform wireless communication based on an embodiment of the present disclosure is shown. Fig.23 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0827] Reference Fig.23 In step S2310, the second device may obtain information related to resources for a sidelink synchronization signal block (S-SSB). In step S2320, the second device may receive the S-SSB from the first device based on the resources. For example, before the resources, during a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission, a first CPE may be performed by the first device.

[0828] The proposed method can be applied to devices based on various embodiments of the present disclosure. First, the processor 202 of the second device 200 can obtain information related to resources for a sidelink synchronization signal block (S-SSB). In addition, the processor 202 of the second device 200 can control the transceiver 206 to receive the S-SSB from the first device based on the resources. For example, before the resources, during a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission, a first CPE can be performed by the first device.

[0829] Based on an embodiment of the present disclosure, a second device suitable for performing wireless communication may be provided. For example, 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 may be executed by the at least one processor so that the second device performs operations including the following items: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); and receiving the S-SSB from a first device based on the resources. For example, before the resources, during a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission, a first CPE may be performed by the first device.

[0830] Based on an embodiment of the present disclosure, a processing device suitable for controlling a second device may be provided. For example, 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 may enable the second device to perform operations including the following items based on being executed by the at least one processor: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); and receiving the S-SSB from a first device based on the resources. For example, before the resources, during a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission, a first CPE may be performed by the first device.

[0831] Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, when the instructions are executed, the second device may perform operations including: obtaining information related to resources for a sidelink synchronization signal block (S-SSB); and receiving the S-SSB from the first device based on the resources. For example, before the resources, during a first time domain for a first cyclic prefix extension (CPE) related to S-SSB transmission, a first CPE may be performed by the first device.

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

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

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

[0835] 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.

[0836] Fig.24 A communication system 1 according to an embodiment of the present disclosure is shown. Fig.24 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0837] Reference Fig.24, 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 (HMDs), head up displays (HUDs) installed in vehicles, televisions, smart phones, computers, wearable devices, home appliances, 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.

[0838] 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, the 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. Alternatively or additionally, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may perform communication based on the LTE-M technology. In this case, as an example, the LTE-M technology may be an example of an LPWAN, and may be referred to as various names including enhanced machine type communication (eMTC), etc. For example, the 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. Alternatively or additionally, 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 can generate a personal area network (PAN) related to small / low power digital communication based on various standards including IEEE 802.15.4, etc., and can be referred to as various names.

[0839] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. 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 going 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.

[0840] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS 200. 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.

[0841] Fig.25 A wireless device according to an embodiment of the present disclosure is shown. Fig.25 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

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

[0843] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may also additionally include one or more transceivers 106 and / or one or more antennas 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) memory 104 may store software code including commands for executing part or all of the processing controlled by (one or more) processor 102 or for executing the description, function, process, proposal, method and / or operation flow disclosed in this document. Here, (one or more) processor 102 and (one or more) memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). (One or more) transceiver 106 may be connected to (one or more) processor 102 and send and / or receive radio signals through (one or more) antenna 108. Each transceiver 106 may include a transmitter and / or a receiver. (One or more) transceiver 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.

[0844] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may also additionally 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 send 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. (One or more) memory 204 can be connected to (one or more) processors 202, and can store various information related to the operation of (one or more) processors 202. For example, (one or more) memory 204 can store software code including commands for executing part or all of the processing controlled by (one or more) processors 202 or for executing the description, function, process, proposal, method and / or operation flow disclosed in this document. Here, (one or more) processors 202 and (one or more) memory 204 can be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). (One or more) transceivers 206 can be connected to (one or more) processors 202, and send 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 can be used interchangeably with (one or more) RF units. In the present disclosure, a wireless device can represent a communication modem / circuit / chip.

[0845] 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 descriptions, functions, processes, proposals, methods, and / or operating procedures disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operating procedures disclosed in this document. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, 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 signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206, and obtain the PDU, SDU, message, control information, data, or information according to the description, function, process, proposal, method, and / or operation flow disclosed in this document.

[0846] 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 perform 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 codes, commands and / or command sets.

[0847] 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, register, cash memory, computer-readable storage medium, and / or a combination 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.

[0848] 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 of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0849] Fig.26 A signal processing circuit for transmitting a signal according to an embodiment of the present disclosure is shown. Fig.26 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0850] Reference Fig.26 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.26 Operation / function, not limited to Fig.25The processor (102, 202) and / or transceiver (106, 206) of Fig.25 The processor (102, 202) and / or the transceiver (106, 206) are implemented Fig.26 For example, you can Fig.25 The processor (102, 202) implements blocks 1010 to 1060. Alternatively, Fig.25 The processor (102, 202) implements blocks 1010 to 1050 and can be implemented by Fig.25 The transceiver (106, 206) is used to implement box 1060.

[0851] Can be through Fig.26 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).

[0852] 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. Additionally, the precoder 1040 may perform precoding without performing transform precoding.

[0853] The resource mapper 1050 can 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 can generate a radio signal from the mapped modulation symbols, and the generated radio signal can 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.

[0854] Can Fig.26 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.25 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.

[0855] Fig. 27 Another example of a wireless device based on an embodiment of the present disclosure is shown. The wireless device can be implemented in various forms according to use cases / services (see Fig.24 ). Fig. 27 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0856] Reference Fig. 27 , the wireless device (100, 200) may correspond to Fig.25 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 storage 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.25 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.25The control unit 120 is electrically connected to the communication unit 110, the memory 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 storage unit 130. The control unit 120 can send the information stored in the storage 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 storage unit 130.

[0857] The additional component 140 may be configured in various ways depending on the type of 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.24 100a), vehicles ( Fig.24 100b-1 and 100b-2), XR devices ( Fig.24 100c), handheld devices ( Fig.24 100d), household appliances ( Fig.24 100e), IoT devices ( Fig.24 100f), digital broadcasting terminals, hologram equipment, public safety equipment, MTC equipment, medical equipment, fintech equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Fig.24 400), BS( Fig.24 200), network nodes, etc. Depending on the use case / service, the wireless device can be used in a mobile or fixed place.

[0858] exist Fig. 27In 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 within 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 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.

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

[0860] Fig.28 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.28 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0861] Reference Fig.28 , the handheld device 100 may include an antenna unit (108), a communication unit 110, a control unit 120, a storage 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. 27 Frame 110 to 130 / 140.

[0862] 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 storage unit 130 may store data / parameters / programs / codes / commands required to drive the handheld device 100. The storage 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.

[0863] 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 storage 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 storage unit 130, and can be output as various types (e.g., text, voice, image, video, or tactile) through the I / O unit 140.

[0864] Fig.29 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.29 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure.

[0865] Reference Fig.29 , 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. 27 Frame 110 / 130 / 140.

[0866] 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 / backward 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 can implement technology for maintaining the lane in which the vehicle is traveling, technology for automatically adjusting the speed (e.g., adaptive cruise control), technology for autonomously driving along a determined path, technology for driving by automatically setting a path when a destination is set, and the like.

[0867] For example, the communication unit 110 can receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d can generate an autonomous driving path and a driving plan from the acquired data. The control unit 120 can control the drive unit 140a so that the vehicle or the autonomous vehicle 100 can 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 can aperiodically / periodically obtain the latest traffic information data from the external server and obtain the surrounding traffic information data from the adjacent vehicle. In the middle of autonomous driving, the sensor unit 140c can obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d can update the autonomous driving path and driving plan based on the newly acquired data / information. The communication unit 110 can transmit information about the vehicle position, autonomous driving path and / or driving plan to the external server. The external server can predict traffic information data based on the information collected from the vehicle or autonomous vehicle using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0868] The claims in this specification can be combined in various ways. For example, the technical features in the method claims of this specification can be combined to be implemented or performed in a device, and the technical features in the device claims can 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 can 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 can 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 resources used for a sidelink synchronization signal block S-SSB; obtaining information about a first time domain of the CPE for a first cyclic prefix extension associated with an S-SSB transmission; performing, before the S-SSB transmission, the first CPE during the first time domain; as well as The S-SSB transmission is performed based on the resources.

2. The method according to claim 1, wherein: The length of the first time domain is configured as a value.

3. The method according to claim 1, further comprising: Information related to a set of resources in a shared spectrum for performing a channel access procedure is obtained.

4. The method according to claim 3, wherein: Based on a listen-before-talk (LBT) failure for the resource set, resource reselection is triggered by the first device.

5. The method according to claim 3, wherein: Based on the LBT failure for the set of resources, a radio link failure RLF for the unicast connection is declared by the first device.

6. The method according to claim 3, wherein: Based on the LBT failure for the resource set, the first device sends information related to the LBT failure to a base station.

7. The method according to claim 3, wherein: Based on a LBT failure for the resource set, the resource set is changed, by the first device, to a resource set different from the resource set.

8. The method according to claim 1, further comprising: Obtaining information about a second time domain for a second CPE associated with a physical sidelink feedback channel (PSFCH) transmission; Receive physical side link shared channel PSSCH; In response to receiving the PSSCH, determining a PSFCH resource for PSFCH transmission; performing the second CPE during the second time domain before the PSFCH transmission; as well as The PSFCH transmission is performed based on the PSFCH resources.

9. The method according to claim 8, wherein: The length of the second time domain is configured as a value.

10. The method according to claim 1, wherein: A channel access priority level CAPC value is predefined for generating a channel occupancy time COT for the S-SSB transmission.

11. The method according to claim 1, further comprising: performing a third CPE during a third time domain for the third CPE, The length of the third time domain is determined based on the priority.

12. The method according to claim 1, wherein: The S-SSB transmission includes multiple S-SSBs repeatedly transmitted in the frequency domain.

13. The method according to claim 1, further comprising: obtaining information indicating a first number of S-SSB transmissions in an S-SSB transmission period in a shared spectrum, wherein the first number is greater than a second number of S-SSB transmissions configured in the licensed spectrum, wherein the first device is allowed to perform the second number of S-SSB transmissions within the one S-SSB transmission period based on listen-before-talk (LBT); and The first device is not allowed to perform more than the second number of S-SSB transmissions within the one S-SSB transmission cycle based on the LBT.

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, the at least one memory is connected to the at least one processor and stores instructions, the instructions are executed by the at least one processor, causing the first device to perform operations including: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; obtaining information about a first time domain of the CPE for a first cyclic prefix extension associated with an S-SSB transmission; performing, before the S-SSB transmission, the first CPE during the first time domain; as well as The S-SSB transmission is performed based on the resources.

15. A processing device adapted to control a first device, the processing device comprising: at least one processor; as well as At least one memory, the at least one memory is connected to the at least one processor and stores instructions, the instructions are executed by the at least one processor, causing the first device to perform operations including: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; obtaining information about a first time domain of the CPE for a first cyclic prefix extension associated with an S-SSB transmission; performing, before the S-SSB transmission, the first CPE during the first time domain; as well as The S-SSB transmission is performed based on the resources.

16. A non-transitory computer-readable storage medium storing instructions that, when executed, cause a first device to perform operations comprising: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; obtaining information about a first time domain of the CPE for a first cyclic prefix extension associated with an S-SSB transmission; performing, before the S-SSB transmission, the first CPE during the first time domain; as well as The S-SSB transmission is performed based on the resources.

17. A method for performing wireless communication by a second device, the method comprising: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; as well as receiving the S-SSB from a first device based on the resource, Wherein, prior to the resource, the first CPE is executed by the first device during a first time domain for a first cyclic prefix extension CPE associated with S-SSB transmission.

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, the at least one memory is connected to the at least one processor and stores instructions, the instructions are executed by the at least one processor so that the second device performs operations including the following items: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; as well as receiving the S-SSB from a first device based on the resource, Wherein, prior to the resource, the first CPE is executed by the first device during a first time domain for a first cyclic prefix extension CPE associated with S-SSB transmission.

19. A processing device adapted to control a second device, the processing device comprising: at least one processor; as well as At least one memory, the at least one memory is connected to the at least one processor and stores instructions, the instructions are executed by the at least one processor so that the second device performs operations including the following items: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; as well as receiving the S-SSB from a first device based on the resource, Wherein, prior to the resource, the first CPE is executed by the first device during a first time domain for a first cyclic prefix extension CPE associated with S-SSB transmission.

20. A non-transitory computer-readable storage medium storing instructions that, when executed, cause a second device to perform operations comprising: Obtaining information related to resources used for a sidelink synchronization signal block S-SSB; and receiving the S-SSB from a first device based on the resource, in, The first CPE is performed by the first device during a first time domain for a first cyclic prefix extension CPE associated with S-SSB transmission prior to the resource.

Images