Method and device for performing communication in wireless communication system

Abstract

A method by which a first device performs wireless communication, and a device for supporting same are provided. The method may comprise the steps of: initiating channel occupancy; sharing the channel occupancy; releasing sharing of the channel occupancy; and performing sidelink (SL) transmission within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) related to the SL transmission can be generated on the basis that a second channel access priority class (CAPC) value related to the SL transmission is less than or equal to a first CAPC value related to sharing of the channel occupancy.

Description

Method and device for performing communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system.

[0002] 5G NR, the successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims to achieve (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. For example, Table 1 can represent an example of the requirements of a 6G system.

[0004] Maximum data rate per device: 1 Tbps, E2E latency: 1 ms, Maximum frequency efficiency: 100 bps / Hz, Mobility support: Up to 1000 km / hr, Satellite integration: Up to AI, Autonomous vehicles: Up to XR, Tactile communication: Up to

[0005] The present disclosure provides a device and method for effectively providing services in a wireless communication system. In particular, the present disclosure provides a method and device for communication.

[0006] In one embodiment, a method performed by a first device may be provided. The method may include: initiating channel occupation; sharing the channel occupation; retrieving the share of the channel occupation; and performing SL (sidelink) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second CAPC (channel access priority class) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupation.

[0007] In one embodiment, a first device configured to perform wireless communication may be provided. The first device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the first device to: initiate channel occupation; share the channel occupation; recover the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupation.

[0008] In one embodiment, a processing device configured to control a first device may be provided. The processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the first device to: initiate channel occupation; share the channel occupation; recover the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupation.

[0009] In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. The instructions, when executed, may cause a first device to: initiate channel occupation; share the channel occupation; recover the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupation.

[0010] In one embodiment, a method performed by a second device may be provided. The method may include a step of sharing channel occupancy. For example, the sharing of the channel occupancy may be recovered. The method may include a step of performing sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupancy.

[0011] In one embodiment, a second device configured to perform wireless communication may be provided. The second device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the second device to: share a channel occupancy. For example, the sharing of the channel occupancy may be reclaimed. The second device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the second device to: perform sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupancy.

[0012] In one embodiment, a processing device configured to control a second device may be provided. The processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the second device to: share a channel occupancy. For example, the sharing of the channel occupancy may be reclaimed. The processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, may cause the second device to: perform sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupancy.

[0013] In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. The instructions, when executed, may cause a second device to: share a channel occupancy. For example, the share of the channel occupancy may be reclaimed. The instructions, when executed, may cause the second device to: perform sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupancy.

[0014] The present disclosure can provide a device and method for effectively providing services in a wireless communication system. For example, communication can be performed efficiently through the embodiments proposed in the present disclosure.

[0015] FIG. 1 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0016] FIG. 2 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0017] FIG. 3 illustrates an example of a typical scenario of an NTN based on a transparent payload, according to one embodiment of the present disclosure.

[0018] FIG. 4 illustrates an example of a typical scenario of an NTN based on a regenerative payload, according to one embodiment of the present disclosure.

[0019] FIG. 5 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0020] FIG. 6 illustrates a slot structure of a frame according to one embodiment of the present disclosure.

[0021] FIG. 7 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0022] FIG. 8 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0023] FIG. 9 illustrates an interlaced RB according to one embodiment of the present disclosure.

[0024] FIG. 10 illustrates an example of a wireless communication system supporting an unlicensed band according to one embodiment of the present disclosure.

[0025] FIG. 11 illustrates a method for occupying resources within an unlicensed band, according to one embodiment of the present disclosure.

[0026] FIG. 12 illustrates a case where multiple LBT-SBs are included within an unlicensed band, according to one embodiment of the present disclosure.

[0027] FIG. 13 illustrates a CAP operation for downlink signal transmission through an unlicensed band of a base station according to an embodiment of the present disclosure.

[0028] FIG. 14 illustrates a type 1 CAP operation of a terminal for uplink signal transmission according to an embodiment of the present disclosure.

[0029] FIG. 15 illustrates a channel connection procedure according to an embodiment of the present disclosure.

[0030] FIG. 16 illustrates a procedure for LBT detection according to one embodiment of the present disclosure.

[0031] FIG. 17 illustrates the operation of a terminal related to a shared COT according to one embodiment of the present disclosure.

[0032] FIG. 18 illustrates terminal operations related to COT recovery according to one embodiment of the present disclosure.

[0033] FIG. 19 illustrates a procedure related to channel occupancy according to one embodiment of the present disclosure.

[0034] FIG. 20 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure.

[0035] FIG. 21 illustrates a method for a second device to perform wireless communication according to one embodiment of the present disclosure.

[0036] Fig. 22 shows a communication system (1) according to one embodiment of the present disclosure.

[0037] FIG. 23 illustrates a wireless device according to one embodiment of the present disclosure.

[0038] FIG. 24 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0039] FIG. 25 illustrates a wireless device according to one embodiment of the present disclosure.

[0040] FIG. 26 illustrates a mobile device according to one embodiment of the present disclosure.

[0041] FIG. 27 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure.

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

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

[0044] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

[0045] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0046] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0047] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0048] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0049] In this specification, higher layer parameters may be parameters that are set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0050] In this specification, "configured or defined" may be interpreted as being configured or preset to a device through predefined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "configured or defined" may be interpreted as being preset to a device.

[0051] The technology proposed in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0052] The technology proposed in this specification can be implemented with 6G wireless technology and applied to various 6G systems. For example, 6G systems can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

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

[0054] New network characteristics in 6G may include:

[0055] - Satellite integrated network

[0056] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).

[0057] - Seamless integration of wireless information and energy transfer

[0058] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.

[0059] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:

[0060] - small cell networks

[0061] - Ultra-dense heterogeneous network

[0062] - High-capacity backhaul

[0063] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0064] - Softwarization and virtualization

[0065] Below, the core implementation technologies of the 6G system are described.

[0066] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0067] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by utilizing sub-THz communication with a wide bandwidth and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (Sub-THz band) is considered a major portion of the THz band for cellular communications. Adding the Sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Figure 2 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0068] - Large-scale MIMO technology

[0069] - Hologram beamforming (HBF)

[0070] - Optical wireless technology

[0071] - Free-space optical transmission backhaul network (FSO backhaul network)

[0072] - Quantum communication

[0073] - Cell-free communication

[0074] - Integration of wireless information and power transmission

[0075] - Integration of wireless communication and sensing

[0076] - Integrated access and backhaul network

[0077] - Big data analysis

[0078] - Reconfigurable intelligent surface

[0079] - metaverse

[0080] - Block chain

[0081] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0082] - Advanced air mobility (AAM): AAM is a higher concept than urban air mobility (UAM), which is an air transportation method available in urban areas, and can refer to a means of transportation that includes movement between regional hubs as well as urban areas.

[0083] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0084] - Non-terrestrial networks (NTN): NTN may refer to a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform). FIG. 3 illustrates an example of a typical NTN scenario based on a transparent payload according to an embodiment of the present disclosure. FIG. 4 illustrates an example of a typical NTN scenario based on a regenerative payload according to an embodiment of the present disclosure. The embodiments of FIG. 3 or FIG. 4 may be combined with various embodiments of the present disclosure. Referring to FIG. 3, a satellite (or UAS platform) may create a service link with a UE. The satellite (or UAS platform) may be connected to a gateway via a feeder link. The satellite may be connected to a data network via the gateway. A beam footprint may refer to an area where a signal transmitted by a satellite can be received. Referring to Figure 4, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the playback payload, a satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between a satellite and another satellite, a feeder link between the satellite and the gateway may be required. Figures 3 and 4 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios.For example, a satellite (or UAS platform) may implement a transparent or regenerative (with onboard processing) payload. For example, a satellite (or UAS platform) may generate multiple beams over a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered. For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to equipping the satellite (or UAS platform) with all or part of the base station functionality.

[0085] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a device to connect to the object through a network, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, i.e., a sensing operation, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing may provide an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network. FIG. 5 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure. Specifically, FIG. 5 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 5 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

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

[0087] The physical layer provides information transmission services to higher layers using physical channels. The physical layer is connected to the upper layer, the Medium Access Control (MAC) layer, via a transport channel. Data travels between the MAC layer and the physical layer through the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.

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

[0089] The MAC layer provides services to the upper layer, the radio link control (RLC) layer, through logical channels. The MAC layer provides mapping from multiple logical channels to multiple transport channels. Furthermore, the MAC layer provides logical channel multiplexing, which maps multiple logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.

[0090] The RLC layer performs the concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

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

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

[0093] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. It performs mapping between QoS flows and data radio bearers, marking QoS flow identifiers (IDs) within downlink and uplink packets, and more.

[0094] Establishing an RB refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: the Signaling Radio Bearer (SRB) and the Data Radio Bearer (DRB). The SRB is used as a channel to transmit RRC messages in the control plane, while the DRB is used as a channel to transmit user data in the user plane.

[0095] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state. Otherwise, it is in the RRC_IDLE state. For NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state can maintain a connection with the core network while releasing the connection with the base station.

[0096] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH or a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.

[0097] Logical channels that are located above the transport channel and are mapped to the transport channel include the Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Multicast Control Channel (MCCH), and Multicast Traffic Channel (MTCH).

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

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

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

[0101] CP type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot Normal CP15kHz (u=0)1410130kHz (u=1)1420260kHz (u=2)14404120kHz (u=3)14808240kHz (u=4)1416016Extended CP60kHz (u=2)12404

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

[0103] Referring to FIG. 6, a slot includes a plurality of symbols in the time domain. A carrier includes a plurality of subcarriers in the frequency domain. An RB (Resource Block) may be defined as a plurality (e.g., 12) of consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) may be defined as a plurality of consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through activated BWPs. Each element may be referred to as a Resource Element (RE) in the resource grid, and one complex symbol may be mapped to it.

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

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

[0106] Referring to Figure 7, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0107] BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP ) can be set by. For example, point A can be an outer reference point of the PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) aligns. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth can be the number of PRBs in a given numerology.

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

[0109] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, 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 may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

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

[0111] In this specification, PSCCH may be replaced by a control channel, a physical control channel, a sidelink-related control channel, a sidelink-related physical control channel, etc. In this specification, PSSCH may be replaced by a shared channel, a physical shared channel, a sidelink-related shared channel, a sidelink-related physical shared channel, etc.

[0112] FIG. 8 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.

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

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

[0115] In step S810, the first terminal schedules the PSCCH (e.g., SCI (Sidelink Control Information) or 1) based on the resource scheduling. st -stage SCI) can be transmitted to the second terminal. In step S820, the first terminal transmits the PSSCH (e.g., 2) related to the PSCCH. nd-stage SCI, MAC PDU, data, etc.) can be transmitted to the second terminal. In step S830, the first terminal can receive a PSFCH related to PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) can be received from the second terminal through the PSFCH. In step S840, the first terminal can transmit / report HARQ feedback information to the base station through PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information that the first terminal generates based on HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information that the first terminal generates based on a rule set in advance. For example, the DCI may be DCI for scheduling of SL.

[0116] For example, the SCI transmitted on the PSCCH is 1 st - It may be a stage SCI, and the above 1 st - Stage SCI can carry sidelink scheduling information. For example, SCI format 1-A can carry sidelink scheduling information on PSSCH, and 2 on PSSCH. nd -can be used to schedule stage SCI. For example, SCI transmitted on PSSCH is 2 nd - It can be a stage SCI, and the above 2 nd -Stage SCI can transmit sidelink scheduling information.

[0117] Referring to (b) of FIG. 8, in resource allocation mode 2, the terminal can determine SL transmission resources within SL resources set by the base station / network or preset SL resources. For example, the set SL resources or preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting resources by itself within the set resource pool. For example, the terminal can select resources by itself within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S810, the first terminal that has selected resources by itself within the resource pool transmits PSCCH (e.g., SCI (Sidelink Control Information) or 1) using the resources. st -stage SCI) can be transmitted to the second terminal. In step S820, the first terminal transmits the PSSCH (e.g., 2) related to the PSCCH. nd -stage SCI, MAC PDU, data, etc.) can be transmitted to the second terminal. In step S830, the first terminal can receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0118] Referring to (a) or (b) of FIG. 8, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., two-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., two-stage SCIs) to receive the PSSCH from the first terminal. In the present specification, an SCI transmitted on a PSCCH is 1 stSCI, 1st SCI, 1 st -Stage SCI or 1 st - It can be called a stage SCI format, and the SCI transmitted on the PSSCH is 2 nd SCI, 2nd SCI, 2 nd -Stage SCI or 2 nd - It can be called a stage SCI format.

[0119] For example, 1 st - Stage SCI format may include SCI Format 1-A and / or SCI Format 1-B, and 2 nd - Stage SCI formats may include SCI Format 2-A, SCI Format 2-B, SCI Format 2-C, and / or SCI Format 2-D.

[0120] Below, an example of SCI format 1-A is described.

[0121] SCI Format 1-A is a 2-bit format on the PSSCH and PSSCH nd - Used for scheduling stage SCI.

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

[0123] - Priority - 3 bits

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

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

[0126] - Resource reservation cycle - ceiling (log2N) rsv_period ) bits, where N rsv_period The number of entries in the upper layer parameter sl-ResourceReservePeriodList if the upper layer parameter sl-MultiReserveResource is set; otherwise, 0 bits.

[0127] - DMRS pattern - ceiling (log2N pattern ) bits, where N pattern is the number of DMRS patterns set by the upper layer parameter sl-PSSCH-DMRS-TimePatternList.

[0128] - 2 nd -Stage SCI format - 2 bits

[0129] - Beta_Offsets indicator - 2 bits as provided by the upper layer parameter sl-BetaOffsets2ndSCI

[0130] - Number of DMRS ports - 1 bit

[0131] - Modulation and coding method - 5 bits

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

[0133] - PSFCH Overhead Indicator - 1 bit if the upper layer parameter sl-PSFCH-Period = 2 or 4; otherwise 0 bit

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

[0135] Below, an example of SCI format 2-A is described.

[0136] In HARQ operation, when HARQ-ACK information contains ACK or NACK, or when HARQ-ACK information contains only NACK, or when there is no feedback of HARQ-ACK information, SCI format 2-A is used for decoding PSSCH.

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

[0138] - HARQ process number - 4 bits

[0139] - New data indicator - 1 bit

[0140] - Redundancy version - 2 bits

[0141] - Source ID - 8 bits

[0142] - Destination ID - 16 bits

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

[0144] - Cast type indicator - 2 bits as defined in Table 3

[0145] - CSI request - 1 bit

[0146] Value of cast type indicator Cast type 00 Broadcast 01 If HARQ-ACK information contains ACK or NACK, Groupcast 10 Unicast 11 If HARQ-ACK information contains only NACK, Groupcast

[0147] Below, an example of SCI format 2-B is described.

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

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

[0150] - HARQ process number - 4 bits

[0151] - New data indicator - 1 bit

[0152] - Redundancy version - 2 bits

[0153] - Source ID - 8 bits

[0154] - Destination ID - 16 bits

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

[0156] - Zone ID - 12 bits

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

[0158] Referring to (a) or (b) of FIG. 8, in step S830, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

[0159] Referring to (a) of FIG. 8, in step S840, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0160] Meanwhile, the existing NR-U (unlicensed spectrum) supports communication between terminals and base stations in unlicensed bands. Furthermore, Rel-18 plans to support mechanisms that enable communication between sidelink terminals in unlicensed bands.

[0161] Meanwhile, a set of non-contiguous RBs (equally spaced) in frequency may be allocated to a UE. Such a set of non-contiguous RBs may be referred to as interlaced RBs. This may be useful in spectrums subject to restrictions such as occupied channel bandwidth (OCB) and power spectral density (PSD), such as shared spectrum.

[0162] FIG. 9 illustrates an interlaced RB according to an embodiment of the present disclosure. The embodiment of FIG. 9 can be combined with various embodiments of the present disclosure.

[0163] Referring to Fig. 9, multiple interlaces of RBs can be defined in the frequency domain. An interlace m∈{0, 1, ..., M-1} can be composed of (common) RBs {m, M+m, 2M+m, 3M+m, ...}, where M can represent the number of interlaced RBs given by Table 4.

[0164] uM01015

[0165] A communication device (e.g., a device, UE, vehicle, drone, etc. as proposed through various embodiments of the present disclosure) may transmit a signal / channel using one or more interlaced RBs.

[0166] In this disclosure, a channel may refer to a set of frequency-domain resources that performs Listen-Before-Talk (LBT). In NR-U, a channel may refer to a 20 MHz LBT bandwidth and may have the same meaning as an RB set. For example, an RB set may be defined in Section 7 of 3GPP TS 38.214 V17.0.0.

[0167] In the present disclosure, CO (channel occupancy) may mean time / frequency axis resources acquired by a base station or terminal after successful LBT.

[0168] In this disclosure, channel occupancy time (COT) may refer to a time-domain resource acquired by a base station or terminal after successful LBT. It may be shared between the base station (or terminal) that acquired the CO and the terminal (or base station), and this may be referred to as COT sharing. Depending on the initiating device, this may be referred to as gNB-initiated COT or UE-initiated COT.

[0169] Below, a wireless communication system supporting unlicensed bands (shared spectrum) is described.

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

[0171] In the following description, a cell operating in a licensed band (hereinafter, L-band) can be defined as an LCell, and the carrier of the LCell can be defined as a (DL / UL / SL) LCC. In addition, a cell operating in an unlicensed band (hereinafter, U-band) can be defined as an UCell, and the carrier of the UCell can be defined as a (DL / UL / SL) UCC. The carrier / carrier-frequency of a cell can mean the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., CC) is collectively referred to as a cell.

[0172] As shown in (a) of Fig. 10, when a terminal and a base station transmit and receive signals through carrier-aggregated LCC and UCC, the LCC may be set to PCC (Primary CC) and the UCC may be set to SCC (Secondary CC). As shown in (b) of Fig. 10, the terminal and the base station may transmit and receive signals through one UCC or multiple carrier-aggregated UCCs. In other words, the terminal and the base station may transmit and receive signals only through UCC(s) without LCC. For standalone operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supported in the UCell.

[0173] In the embodiment of FIG. 10, the base station may be replaced by a terminal. In this case, for example, PSCCH, PSSCH, PSFCH, S-SSB transmission, etc. may be supported in UCell.

[0174] Unless otherwise stated, the definitions below apply to terms used in this specification.

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

[0176] - Channel Access Procedure (CAP): This refers to the procedure for evaluating channel availability based on sensing to determine whether other communication nodes are using the channel before signal transmission. The basic unit for sensing is T sl =9us duration sensing slot. The base station or terminal senses the channel during the sensing slot period, and the power detected for at least 4us within the sensing slot period is the energy detection threshold X Thresh If it is smaller than T, the sensing slot interval is sl is considered to be idle. Otherwise, the sensing slot interval T sl =9us is considered a busy state. CAP can be referred to as LBT (Listen-Before-Talk).

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

[0178] - Channel Occupancy Time (COT): This refers to the total time that the base station / terminal and any base station / terminal(s) sharing the channel occupancy can perform transmission(s) on the channel after the base station / terminal performs the channel access procedure. When determining the COT, if the transmission gap is 25us or less, the gap period is also counted in the COT. The COT can be shared for transmission between the base station and the corresponding terminal(s).

[0179] - DL Transmission Burst: Defined as a set of transmissions from a base station without gaps exceeding 16us. Transmissions from a base station separated by gaps exceeding 16us are considered separate DL transmission bursts. A base station may perform transmission(s) after a gap without sensing channel availability within a DL transmission burst.

[0180] - UL or SL Transmission Burst: Defined as a set of transmissions from a terminal without a gap exceeding 16us. Transmissions from a terminal separated by a gap exceeding 16us are considered separate UL or SL transmission bursts. A terminal may perform transmission(s) after a gap without sensing channel availability within a UL or SL transmission burst.

[0181] - Discovery burst: refers to a DL transmission burst that includes a set of signal(s) and / or channel(s) that is limited within a (time) window and associated with a duty cycle. In an LTE-based system, a discovery burst is a transmission(s) initiated by a base station, including PSS, SSS and CRS (cell-specific RS), and may further include a non-zero power CSI-RS. In an NR-based system, a discovery burst is a transmission(s) initiated by a base station, including at least an SS / PBCH block, and may further include a CORESET for a PDCCH scheduling a PDSCH having SIB1, a PDSCH carrying SIB1, and / or a non-zero power CSI-RS.

[0182] FIG. 11 illustrates a method for occupying resources within an unlicensed band, according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0183] Referring to Fig. 11, a communication node (e.g., a base station, a terminal) within an unlicensed band must determine whether other communication node(s) are using the channel before transmitting a signal. To this end, the communication node within the unlicensed band may perform a channel access procedure (CAP) to access the channel(s) on which the transmission(s) are performed. The channel access procedure may be performed based on sensing. For example, the communication node may first perform carrier sensing (CS) before transmitting a signal to determine whether other communication node(s) are transmitting a signal. If it is determined that other communication node(s) are not transmitting a signal, it is defined that CCA (Clear Channel Assessment) is confirmed. A CCA threshold (e.g., X) that is predefined or set by a higher layer (e.g., RRC) Thresh ), the communication node can determine the channel state as busy if energy higher than the CCA threshold is detected in the channel, and determine the channel state as idle otherwise. If the channel state is determined to be idle, the communication node can start transmitting signals in the unlicensed band. CAP can be replaced with LBT.

[0184] Table 5 illustrates the channel access procedures (CAPs) supported in NR-U.

[0185] Type Description DL Type 1 CAP CAP with random backoff - The duration of a sensing slot sensed as idle before downlink transmission(s) is random. Type 2 CAP - Type 2A, 2B, 2C CAP without random backoff - The duration of a sensing slot sensed as idle before downlink transmission(s) is deterministic. UL or SL Type 1 CAP with random backoff - The duration of a sensing slot sensed as idle before uplink or sidelink transmission(s) is random. Type 2 CAP - Type 2A, 2B, 2C CAP without random backoff - The duration of a sensing slot sensed as idle before uplink or sidelink transmission(s) is deterministic.

[0186] Referring to Table 5, LBT types or CAPs for DL / UL / SL transmissions can be defined. However, Table 5 is only an example, and new types or CAPs can be defined in a similar manner. For example, Type 1 (also called Cat-4 LBT) can be a random back-off based channel access procedure. For example, in the case of Cat-4, the contention window can be changed. For example, Type 2 can be performed in case of COT sharing within COT acquired by gNB or UE.

[0187] Below, LBT-SB (SubBand) (or RB set) is described.

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

[0189] FIG. 12 illustrates a case in which multiple LBT-SBs are included within an unlicensed band, according to an embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0190] Referring to Fig. 12, a BWP of a cell (or carrier) may include multiple LBT-SBs. An LBT-SB may have, for example, a 20MHz band. An LBT-SB is composed of multiple consecutive (P)RBs in the frequency domain, which may be referred to as a (P)RB set. Although not illustrated, a guard band (GB) may be included between LBT-SBs. Accordingly, a BWP may be composed in the form of {LBT-SB #0 (RB set #0) + GB #0 + LBT-SB #1 (RB set #1 + GB #1) + ... + LBT-SB #(K-1) (RB set (#K-1))}. For convenience, the LBT-SB / RB index may be set / defined to increase starting from a lower frequency band and moving to a higher frequency band.

[0191] Below, CAPC (channel access priority class) is explained.

[0192] The MAC CEs and CAPCs of the radio bearers are fixed or configurable to operate in FR1:

[0193] - Fixed to lowest priority for padding BSR (buffer status report) and recommended bit rate MAC CE;

[0194] - Fixed to highest priority for SRB0, SRB1, SRB3 and other MAC CEs;

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

[0196] When selecting a CAPC for a DRB, the base station considers the 5QIs of all QoS flows multiplexed to the DRB, while also considering fairness among other traffic types and transmissions. Table 6 shows which CAPC to use for a standardized 5QI, i.e., which CAPC to use for a given QoS flow. For standardized 5QIs, CAPCs are defined as shown in the table below, and for non-standardized 5QIs, the CAPC that best matches the QoS characteristics should be used.

[0197] CAPC5QI11, 3, 5, 65, 66, 67, 69, 70, 79, 80, 82, 83, 84, 8522, 7, 7134, 6, 8, 9, 72, 73, 74, 764 - Note: Lower CAPC values ​​indicate higher priority

[0198] Below, a method for transmitting downlink signals via an unlicensed band is described. For example, this method for transmitting downlink signals via an unlicensed band can be applied to a method for transmitting sidelink signals via an unlicensed band.

[0199] A base station may perform one of the following channel access procedures (CAP) for downlink signal transmission in an unlicensed band.

[0200] (1) Type 1 downlink (DL) CAP method

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

[0202] - (i) a unicast PDSCH having user plane data, or (ii) a transmission(s) initiated by a base station, including a unicast PDSCH having user plane data and a unicast PDCCH scheduling user plane data, or

[0203] - Transmission(s) initiated by a base station, either (i) having only a discovery burst, or (ii) having a discovery burst multiplexed with non-unicast information.

[0204] FIG. 13 illustrates a CAP operation for downlink signal transmission through an unlicensed band of a base station according to an embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.

[0205] Referring to Figure 13, the base station first determines the defer duration T d During the sensing slot period, the channel is sensed to be in an idle state, and if the counter N becomes 0, transmission can be performed (S134). At this time, the counter N is adjusted by sensing the channel during additional sensing slot period(s) according to the following procedure:

[0206] Step 1)(S120) N=N init Set to . Here, N init Silver 0 to CWp It is a random value that is evenly distributed among them. Then, move on to step 4.

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

[0208] Step 3) (S150) The channel is sensed during the additional sensing slot period. If the additional sensing slot period is idle (Y), proceed to Step 4. If not (N), proceed to Step 5.

[0209] Step 4) (S130) If N=0 (Y), terminate the CAP procedure (S132). Otherwise (N), proceed to Step 2.

[0210] Step 5)(S160) Additional delay section T d A busy sensing slot is detected within the frame, or an additional delay interval T d Sensing the channel until all sensing slots within it are detected as idle.

[0211] Step 6)(S170) Additional delay section T d If the channel is sensed as idle during all sensing slot intervals (Y), go to step 4. Otherwise (N), go to step 5.

[0212] Table 7 shows the m applied to CAP according to the channel access priority class. p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes are shown.

[0213] CAPC (Channel Access Priority Class) (p)m p CW min,p CW max,p T me,p Allowed CW pSizes11372 ms{3,7}217153 ms{7,15}3315638 or 10 ms{15,31,63}471510238 or 10 ms{15,31,63,127,255,511,1023}

[0214] Referring to Table 7, the contention window size (CWS) and maximum COT value for each CAPC can be defined. For example, T d = T f + m p * T sl It could be.

[0215] Delay interval T d is the section T f (16us) + m p A continuous sensing slot interval T of a dog sl It is composed of the order of (9us). T f is the sensing slot interval T at the start of the 16us interval. sl Includes.

[0216] CW min,p <= CW p <= CW max,p It is. CW p is CW p = CW min,p is set to , and can be updated (CW size update) prior to step 1 based on the HARQ-ACK feedback (e.g., ACK or NACK ratio) for the previous DL burst (e.g., PDSCH). For example, CW p is based on the HARQ-ACK feedback for the previous DL burst, CW min,p It can be initialized to , incremented to the next highest allowed value, or kept at the existing value.

[0217] (2) Type 2 downlink (DL) CAP method

[0218] In Type 2 DL CAP, the length of the time interval spanned by the sensing slots that are sensed as idle before transmission(s) is deterministic. Type 2 DL CAP is divided into Type 2A / 2B / 2C DL CAP.

[0219] Type 2A DL CAP can be applied to the transmissions below. In Type 2A DL CAP, the base station must have at least a sensing period T short_dl = Transmission can be transmitted immediately after the channel is sensed as idle for 25us. Here, T short_dl Silver section T f (=16us) and one sensing slot section immediately following it. T f contains a sensing slot at the start of the interval.

[0220] - transmission(s) initiated by the base station, (i) having only a discovery burst, or (ii) having a discovery burst multiplexed with non-unicast information, or,

[0221] - Transmission(s) by the base station after a 25us gap from the transmission(s) by the terminal within the shared channel occupancy.

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

[0223] Below, a method for transmitting uplink signals via an unlicensed band is described. For example, this method for transmitting uplink signals via an unlicensed band can be applied to a method for transmitting sidelink signals via an unlicensed band.

[0224] The UE performs Type 1 or Type 2 CAP for uplink signal transmission in the unlicensed band. Typically, the UE can perform the CAP (e.g., Type 1 or Type 2) configured by the base station for uplink signal transmission. For example, the UE may include CAP type indication information in the UL grant (e.g., DCI format 0_0, 0_1) that schedules PUSCH transmission.

[0225] (1) Type 1 uplink (UL) CAP method

[0226] In a Type 1 UL CAP, the length of the time interval spanned by the sensing slots that are sensed as idle before a transmission(s) is random. A Type 1 UL CAP can be applied to the following transmissions:

[0227] - Scheduled and / or configured PUSCH / SRS transmission(s) from the base station

[0228] - PUCCH transmission(s) scheduled and / or configured from the base station;

[0229] - Transmission(s) related to RAP (Random Access Procedure)

[0230] FIG. 14 illustrates a Type 1 CAP operation of a terminal for uplink signal transmission according to an embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.

[0231] Referring to Figure 14, the terminal first provides a defer duration T d During the sensing slot period, the channel is sensed to be in an idle state, and if the counter N becomes 0, transmission can be performed (S234). At this time, the counter N is adjusted by sensing the channel during additional sensing slot period(s) according to the following procedure:

[0232] Step 1)(S220) N=N init Set to . Here, N init Silver 0 to CW p It is a random value that is evenly distributed among them. Then, move on to step 4.

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

[0234] Step 3) (S250) The channel is sensed during the additional sensing slot section. If the additional sensing slot section is idle (Y), proceed to Step 4. If not (N), proceed to Step 5.

[0235] Step 4) (S230) If N=0 (Y), terminate the CAP procedure (S232). Otherwise (N), proceed to Step 2.

[0236] Step 5) (S260) Additional delay section T d A busy sensing slot is detected within the frame, or an additional delay interval T d Sensing the channel until all sensing slots within it are detected as idle.

[0237] Step 6)(S270) Additional delay section T dIf the channel is sensed as idle during all sensing slot intervals (Y), go to step 4. Otherwise (N), go to step 5.

[0238] Table 8 shows the m applied to CAP according to the channel access priority class. p , minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes vary.

[0239] CAPC (Channel Access Priority Class) (p)m p CW min,p CW max,p T ulmcot,p Allowed CW p Sizes12372 ms{3,7}227154 ms{7,15}331510236 or 10 ms{15,31,63,127,255,511,1023}471510236 or 10 ms{15,31,63,127,255,511,1023}

[0240] Referring to Table 8, the contention window size (CWS) and maximum COT value for each CAPC can be defined. For example, T d = T f + m p * T sl It could be.

[0241] Delay interval T d is the section T f (16us) + m p A continuous sensing slot interval T of a dog sl It is composed of the order of (9us). T f is the sensing slot interval T at the start of the 16us interval. sl Includes.

[0242] CW min,p <= CW p <= CW max,pIt is. CW p is CW p = CW min,p is set to , and can be updated (CW size update) prior to step 1 based on explicit / implicit reception acknowledgment for the previous UL burst (e.g., PUSCH). For example, CW p is based on explicit / implicit reception acknowledgment to the previous UL burst, CW min,p It can be initialized to , incremented to the next highest allowed value, or kept at the existing value.

[0243] (2) Type 2 uplink (UL) CAP method

[0244] In Type 2 UL CAP, the length of the time interval spanned by the sensing slots that are sensed as idle before transmission(s) is deterministic. Type 2 UL CAP is divided into Type 2A / 2B / 2C UL CAP. In Type 2A UL CAP, the terminal must sense at least the sensing interval T short_dl = Transmission can be transmitted immediately after the channel is sensed as idle for 25us. Here, T short_dl Silver section T f (=16us) and one sensing slot section immediately following it. T in Type 2A UL CAP f includes a sensing slot at the start of the interval. In Type 2B UL CAP, the terminal starts sensing interval T f = Transmission can be transmitted immediately after the channel is sensed as idle for 16us. T in Type 2B UL CAP f contains a sensing slot within the last 9us of the interval. In Type 2C UL CAP, the terminal does not sense the channel before performing a transmission.

[0245] For example, according to Type 1 LBT-based NR-U operation, a terminal having uplink data to transmit can select a CAPC mapped to the 5QI of the data, and the terminal can set parameters of the corresponding CACP (e.g., minimum contention window size, max contention window size, m p ) can be applied to perform NR-U operation. For example, the terminal can select a random value between the minimum CW and the maximum CW mapped to the CAPC, and then select a BC (Backoff Counter) between zero and the random value. In this case, for example, the BC can be a positive integer less than or equal to the random value. The terminal that senses the channel decreases the BC by 1 when the channel is idle. When the BC becomes zero and the terminal is in T d (T d = T f + m p * T sl ) If the channel is detected to be idle for a period of time, the terminal can attempt to occupy the channel and transmit data. If the terminal attempting data transmission detects a collision, the terminal can increase the CW size mapped to the CAPC, and the terminal can reselect the BC between zero and the increased CW. A terminal that successfully transmits a packet can initialize the CW size (to CW min).

[0246] For example, T sl (= 9 usec) is a basic sensing unit or sensing slot, which may include a measurement duration of at least 4 usec. For example, T f The first 9 usec of (= 16 usec) is T sl It can be composed of. For example, m pcan be a constant mapped by CAPC, and T d It can be used in calculations. For example, a lower CACP value (higher priority) can be mapped to a smaller value.

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

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

[0249] For example, Type 2B can be a 16-usec one-shot LBT. In this case, transmission can begin immediately after idle sensing for a 16-usec gap. That is, the terminal can sense the channel for 16 usec within the COT, and when the channel becomes idle, the terminal can seize the channel and attempt to transmit data.

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

[0251] In a sidelink unlicensed band, a terminal can perform a channel access operation based on LBT (Listen Before Talk). Before accessing a channel in an unlicensed band, the terminal must check whether the access channel is idle (e.g., a state in which the terminal does not occupy the channel, a state in which terminals can access the channel and transmit data) or busy (e.g., a state in which the channel is occupied and data transmission and reception operations are performed on the channel, a terminal attempting to access the channel cannot transmit data when the channel is busy). In other words, the operation in which the terminal checks whether the channel is idle or busy can be referred to as CCA (Clear Channel Assessment), and the terminal can check whether the channel is idle or busy during the CCA period.

[0252] FIG. 15 illustrates a channel access procedure according to an embodiment of the present disclosure. Specifically, FIG. 15 (a) illustrates an example of a dynamic channel access procedure (load-based equipment, LBE), and FIG. 15 (b) illustrates an example of a semi-static channel access procedure (frame-based equipment, FBE). The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.

[0253] Referring to Figure 15 (a), a terminal can compete with other unlicensed band terminals to immediately occupy a channel when the channel is idle. Once a terminal occupies the channel, it can transmit data.

[0254] Referring to (b) of FIG. 15, a terminal can compete with other unlicensed band terminals at the last point (e.g., a certain time (or starting point) before the start of the next FFP) within a synchronized frame boundary (or Fixed Frame Period (FFP)). Then, if the terminal occupies the channel within the Fixed Frame Period (FFP), the terminal can transmit data. The data transmission must be completed before the start of the next FFP. The terminal can perform a Type 2 series LBT operation within the FFP. For example, within the FFP, the terminal may not perform random backoff-based LBT, and the terminal may sense the channel for a certain short time and perform data transmission when the channel is idle.

[0255] FIG. 16 illustrates a procedure for LBT detection according to an embodiment of the present disclosure. The embodiment of FIG. 16 can be combined with various embodiments of the present disclosure.

[0256] Referring to FIG. 16, for example, a lower layer of a MAC entity may perform a (SL) LBT procedure. For example, as in 3GPP TS 37.213, a lower layer of a MAC entity may perform a (SL) LBT procedure. For example, a lower layer of a MAC entity may perform a (SL) LBT procedure, and if a channel is identified as occupied, transmission may not be performed by a lower layer of the MAC entity according to the (SL) LBT procedure. For example, when a lower layer of a MAC entity performs a LBT procedure before transmission and the transmission is not performed, an (SL) LBT failure indication may be transmitted from a lower layer of the MAC entity to the MAC entity. For example, if there is no separate disclosure, when the (SL) LBT procedure is performed for transmission, the action may be performed as disclosed in the present disclosure regardless of whether an (SL) LBT failure indication is received from a lower layer of the MAC entity. For example, when the (SL) LBT is not performed from a lower layer of the MAC entity, an (SL) LBT failure indication may not be received from the lower layer of the MAC entity.

[0257] For example, the (sidelink) LBT failure and / or recovery procedure may be performed as follows:

[0258] For example, a MAC entity may be configured by RRC with (SL) LBT failure detection and / or recovery procedures. (SL) Consistent LBT failures may be detected on a per-RB-set basis by counting (SL) LBT failure indication(s) for every (SL) transmission from a lower layer of the MAC entity to the MAC entity.

[0259] For example, RRC can set the following parameters in the (SL) LBT failure recovery configuration (e.g., (sl-)lbt-FailureRecoveryConfig):

[0260] - (SL) Maximum count of (SL) LBT failure instances for consistent LBT failure detection (e.g., (sl-)lbt-FailureInstanceMaxCount)

[0261] - (SL) LBT failure detection timer for consistent LBT failure detection (e.g., (sl-)lbt-FailureDetectionTimer)

[0262] - (SL) LBT recovery timer for recovery from triggered (SL) consistent LBT failures (e.g., (sl-)LBT-RecoveryTimer)

[0263] For example, the following UE variables can be used in a (SL) consistent LBT failure detection procedure:

[0264] - LBT_COUNTER (e.g. SL_LBT_COUNTER) (e.g. RB (set) by): Counter for (SL) LBT failure indications, initially set to 0.

[0265] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the RB set by 1. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for an RB set in the configured pool(s) of resources in the (SL) BWP, the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the RB set by 1. For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may increment the LBT_COUNTER (e.g., SL_LBT_COUNTER) for the set of RBs by 1.

[0266] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer for a set of RBs. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer for the set of RBs. For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart the (sl-)lbt-FailureDetectionTimer for the set of RBs.

[0267] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the LBT_COUNTER (e.g., SL_LBT_COUNTER) is greater than or equal to (sl-)lbt-FailureInstanceMaxCount, the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the LBT_COUNTER (e.g., SL_LBT_COUNTER) is greater than or equal to 3, which is (sl-)lbt-FailureInstanceMaxCount, the MAC entity can trigger a (SL) consistent LBT failure for a set of RBs in the (SL) BWP. For example, (sl-)lbt-FailureInstanceMaxCount is not limited to 3. For example, (sl-)lbt-FailureInstanceMaxCount can be set to a value different from 3.

[0268] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity can indicate to the upper layer of the MAC entity (e.g., to RRC) (SL) consistent LBT failure-based (sidelink) RLF detection for all destination IDs associated with the unicast service. For example, for an (activated) (SL) BWP (e.g. configured with (sl-)lbt-FailureRecoveryConfig), if a consistent LBT failure is triggered on all RB sets of the configured pool(s) of resources in the (SL) BWP, the MAC entity may indicate to the upper layer of the MAC entity (e.g., to RRC) (sidelink) RLF detection based on the (SL) consistent LBT failure for all destination IDs associated with the unicast service.

[0269] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if a (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart (sl-)lbt-FailureDetectionTimer. For example, as illustrated in Figure 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if an (SL) LBT failure indication is received from a lower layer for a set of RBs in the configured pool(s) of resources in the (SL) BWP, the MAC entity may start or restart the (sl-)lbt-FailureDetectionTimer.

[0270] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if all triggered (SL) consistent LBT failures in the RB set are canceled, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the (sl-)lbt-FailureDetectionTimer has expired for an RB set, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set. For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if all triggered (SL) consistent LBT failures in the RB set have been canceled, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set.For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if the (sl-)lbt-FailureDetectionTimer has expired for an RB set, the MAC entity may set the LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for the RB set.

[0271] For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureDetectionTimer is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureInstanceMaxCount is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets. For example, as illustrated in FIG. 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureDetectionTimer is reset by upper layers, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets.For example, as illustrated in Figure 16, for an (activated) (SL) BWP (e.g., configured with (sl-)lbt-FailureRecoveryConfig), if (sl-)lbt-FailureInstanceMaxCount is reset by the upper layer, the MAC entity may set LBT_COUNTER (e.g., SL_LBT_COUNTER) to 0 for all RB sets.

[0272] In an unlicensed band, a terminal can generate or share (or receive) the shared channel occupancy time (Shared COT) for sidelink data transmission as follows.

[0273] FIG. 17 illustrates the operation of a terminal associated with a shared COT according to one embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.

[0274] Referring to FIG. 17, for example, a terminal generating a (shared) COT (e.g., a COT initiating UE) can share the COT it has secured with a counterpart terminal. The terminal generating / securing the (shared) COT can transfer the secured (shared) COT to the counterpart terminal via an SCI or MAC CE or PC5-RRC message. For example, when transferring the (shared) COT secured via SCI, the secured (shared) COT can be transferred to a destination UE for a unicast link (e.g., a pair of L1 Source ID and L1 Destination ID), and the secured (shared) COT can be transferred to a groupcast / broadcast destination UE (e.g., a groupcast / broadcast L1 destination ID). For example, when transmitting a (shared) COT acquired through MAC CE (e.g., SL Channel Occupancy Time (COT) Information MAC CE), the acquired (shared) COT can be transmitted to a destination UE for a unicast link (e.g., a pair of L1 / L2 Source ID and L1 / L2 Destination ID), and the acquired (shared) COT can be transmitted to a groupcast / broadcast destination UE (e.g., a groupcast / broadcast L1 / L2 destination ID).For example, a UE (e.g., a COT responding UE) that receives a (shared) COT from a UE that generated a (shared) COT can perform a Type 2 LBT (e.g., Type 2A or Type 2B LBT: if it performs a sensing operation to confirm that the channel is idle for a certain period of time, it can transmit SL data to be transmitted within the (shared) COT. For example, Type 2C LBT can transmit SL data immediately without sensing for a certain period of time.) operation after the transmission of the UE that generated the (shared) COT within the shared COT is completed. For example, the shared COT information that a COT initiating UE transmits to a COT responding UE may include information such as a shared COT duration, a shared COT starting offset, and an SL-CAPC value to be used by the COT responding UE.

[0275] For example, although the descriptions related to FIG. 17 and FIG. 17 illustrate an embodiment in which a (shared) COT is shared from a counterpart terminal, the terminal may also receive a (shared) COT to use from the base station. For example, a transmitting terminal that will transmit sidelink data can directly generate a COT to use and perform type 2 LBT within the COT to transmit sidelink data within the generated COT.

[0276] For example, a transmitting terminal performing sidelink communication in a sidelink unlicensed band (e.g., sidelink-unlicensed (SL-U))) can perform an LBT operation to occupy a channel in the unlicensed band. For example, if the LBT is successful, the terminal can transmit packets in the occupied channel. For example, if the LBT fails (e.g., if the terminal detects that the channel is busy as a result of sensing during the sensing slot period), the terminal cannot perform sidelink transmission because the channel in the unlicensed band has not been occupied.

[0277] FIG. 18 illustrates terminal operations related to COT recovery according to one embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.

[0278] Referring to FIG. 18, for example, according to an embodiment of the present disclosure, an operation may be proposed whereby a terminal that has generated a COT (e.g., a COT initiating terminal) can retrieve the COT it has acquired. For example, a terminal that has generated and acquired a COT and shared the COT with a counterpart terminal (e.g., a COT initiating terminal) may transmit a COT END MAC CE to the counterpart terminal in order to retrieve the acquired COT. For example, the COT END MAC CE may be transmitted to a destination UE for a unicast link (e.g., a pair of L1 / L2 source ID and L1 / L2 destination ID) and may be transmitted to a groupcast / broadcast destination UE (e.g., a groupcast / broadcast L1 / L2 destination ID). For example, a terminal that receives a COT END MAC CE can transmit SL data by performing type 1 LBT from the time of receiving the COT END MAC CE until the expiration of the previously shared COT. For example, before receiving a COT END MAC CE, a terminal that has shared a COT can transmit SL data by performing type 2 LBT within the shared COT until the COT expires.

[0279] For example, COT recovery may be possible not only via MAC CE but also via SCI or PC5-RRC messages. For example, SCI may be used to transmit the destination UE for a unicast link (e.g., a pair of L1 source ID and L1 destination ID) and to a groupcast / broadcast destination UE (e.g., a groupcast / broadcast L1 destination ID).

[0280] For example, in SL-U, a terminal may first need to occupy a channel in a sidelink unlicensed band in order to transmit SL data. For example, in order to occupy a channel in a sidelink unlicensed band, the terminal may perform LBT (e.g., type 1 LBT: random backoff-based LBT) to find a channel in the unlicensed band that is not occupied by the terminal. For example, if a terminal performing LBT finds a channel that is not occupied by other terminals, it can occupy the channel and transmit SL data. For example, if the LBT process fails, the terminal may adjust the parameter values ​​for performing LBT (e.g., adjusting the contention window size, etc.) to re-perform LBT and continue the process of finding a channel in the unlicensed band that is not occupied by the terminal.

[0281] For example, a transmitting terminal performing (sidelink) communication in an unlicensed band (sl-U) can perform an LBT operation to occupy a channel in the unlicensed band. For example, if the LBT is successful, the terminal can transmit packets in the occupied channel. For example, if the LBT fails (for example, if the terminal detects that the channel is busy as a result of sensing during the sensing slot period), the (sidelink) transmission cannot be performed because the channel in the unlicensed band was not occupied. For example, if the MAC layer of the transmitting terminal detects an (SL) LBT failure while performing an LBT operation to occupy a channel in the unlicensed band, the MAC layer can receive an indication of an (SL) LBT failure event from the physical layer.

[0282] For example, in (sidelink) unlicensed bands (sl-U), a terminal can perform actions based on (SL) LBT failure events as follows.

[0283] For example, the terminal may receive the following parameters for (SL) LBT failure management from the base station and perform (SL) LBT failure recovery or (SL) LBT failure declaration operations.

[0284] - (sl-)lbt-FailureInstanceMaxCount: When the terminal detects an (SL) LBT failure, it increments the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1, and can declare an (SL) LBT failure when it detects (sl-)lbt-FailureInstanceMaxCount number of (SL) LBT failures before (sl-)lbt-FailureDetectionTimer expires.

[0285] - (sl-)lbt-FailureDetectionTimer: A timer that starts when (SL) LBT failure is detected. The (SL) LBT failure recovery process can be performed while the timer is running.

[0286] For example, when the MAC layer of a transmitting terminal receives a (SL) LBT failure event from the physical layer (i.e., when the terminal detects an (SL) LBT failure), the MAC layer may start the (sl-)lbt-FailureDetectionTimer timer and simultaneously increase the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1. For example, the (SL) LBT recovery process may be performed during the operation of the (sl-)lbt-FailureDetectionTimer timer. For example, when the terminal detects an (SL) LBT failure again during the operation of the (sl-)lbt-FailureDetectionTimer timer, the terminal may increase the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1. For example, if the LBT_COUNTER (e.g., SL_LBT_COUNTER) incremented due to (SL) LBT detection does not reach the threshold number of times ((sl-)lbt-FailureInstanceMaxCount) before the (sl-)lbt-FailureDetectionTimer timer expires, the terminal considers the (SL) LBT failure to have been recovered and can continue to perform normal (sidelink) communication using the (sidelink) grant in use.

[0287] For example, a consistent (SL) LBT failure can be declared if the LBT_COUNTER (e.g., SL_LBT_COUNTER) incremented due to (SL) LBT failure detection reaches a threshold number of times ((sl-)lbt-FailureInstanceMaxCount) before the (sl-)lbt-FailureDetectionTimer timer expires. For example, a transmitting terminal can declare an SL LBT failure if the SL LBT failure is not recovered by the time the (sl-)lbt-FailureDetectionTimer timer expires.

[0288] For example, if a transmitting terminal declares an SL LBT failure, it can perform the following actions:

[0289] - A (sidelink) grant can be released / discarded / ignore for a specific unicast link (a pair of source Layer-2 ID and destination Layer-2 ID or a PC5 link identifier) ​​where an SL LBT failure has occurred. For example, if a transmitting terminal has multiple unicast links with a destination terminal with which a unicast configuration has been established, the transmitting terminal can release / discard / ignore only the sidelink grant (mode 1 grant, mode 2 grant) allocated or created for the specific unicast link that declared an SL LBT failure and report an ACK to the base station on PUCCH so that the base station does not allocate any more mode 1 sidelink grants. For example, only a specific unicast link on which an SL LBT failure occurred can be released. For example, when an LBT failure is declared on a specific unicast link (a pair of Source Layer-2 ID and Destination Layer-2 ID or a PC5 link identifier), the AS layer can report the identifier of the unicast link that declared the LBT failure (e.g., the PC5 link identifier) ​​and an indication of the SL LBT failure to a higher layer (e.g., the V2X layer).When the V2X layer receives an SL LBT failure indication and a PC5 link identifier from the AS layer, the V2X layer can terminate the SL unicast link for the corresponding PC5 link identifier.

[0290] For example, the terminal can perform LBT failure detection operation per sidelink resource pool or per (sidelink) RB set. For example, the physical layer of the terminal can detect (sidelink) LBT failure per sidelink resource pool or per (sidelink) RB set and report an SL LBT failure indication to the MAC layer. For example, when the MAC layer receives an (SL) LBT failure indication from the physical layer, the MAC layer can increase SL_LBT_COUNTER per sidelink resource pool or per (sidelink) RB set by 1. For example, when the (SL) LBT failure per sidelink resource pool or per (sidelink) RB set reaches a threshold, the UE may declare a consistent (SL) LBT failure for the corresponding sidelink resource pool or sidelink RB set and switch to another sidelink resource pool or sidelink RB set to continue the SL LBT operation for SL TB transmission. For example, if the UE declares a consistent SL LBT failure for all (sidelink) resource pools or all (sidelink) RB sets, it may declare an SL RLF for the corresponding sidelink session (declare an SL RLF only for unicast) and release the corresponding sidelink session (unicast / broadcast / groupcast).

[0291] For example, in a logical channel prioritization (LCP) procedure, a terminal may preferentially select data (e.g., MAC SDU or destination Layer-2 ID) with the highest priority among data of a logical channel, MAC CE, and SCCH data, and multiplex the selected data (e.g., MAC SDU or destination Layer-2 ID) with the same destination Layer-2 ID and data with the same cast type to generate (e.g., obtain) a single MAC PDU.

[0292] For example, resource (re)selection in MCSt and COT and logical channel prioritization (LCP) constraints may be as follows.

[0293] For example, when a user equipment (UE) generates multiple sidelink grants within a COT it has generated, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of the SL data on the sidelink grants. For example, when a UE generates multiple sidelink grants within a COT it has generated, if the CAPC value of the SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of the SL data associated with a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure for the subsequent sidelink grant can be triggered. For example, after the UE selects an MCSt resource for multiple sidelink TBs, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of the SL data for the sidelink grant on the MCSt.

[0294] For example, after the UE selects MCSt resources for multiple sidelink TBs, the UE may perform a destination selection procedure in the LCP procedure by considering the CAPC value of the SL data on the sidelink grant for the MCSt. For example, when the UE selects MCSt resources for multiple sidelink TBs, if the CAPC value of the SL data related to the subsequent sidelink grant resource is greater than the CAPC value of the SL data on the preceding sidelink grant resource, a resource reselection procedure for the subsequent sidelink grant may be triggered.

[0295] For example, when a UE generates multiple sidelink grants within a COT it has generated, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of SL data on the sidelink grant.

[0296] For example, when a UE generates multiple sidelink grants within a COT it has generated, if the CAPC value of SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of SL data on a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure of the subsequent sidelink grant may be triggered.

[0297] For example, after the UE selects MCSt resources for multiple sidelink TBs, it may perform a destination selection procedure in the LCP procedure by considering the CAPC value of SL data on the sidelink grant for MCSt.

[0298] For example, when a UE selects an MCSt resource for multiple sidelink TBs, if the CAPC value of SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of SL data on a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure of the subsequent sidelink grant may be triggered.

[0299] For example, the above proposals (e.g., the proposals for sidelink transmission burst-based terminal operation described in the present disclosure) can be equally extended and applied to the case where a terminal performs multiple consecutive slot transmission (MCSt)-based operation in the sidelink (e.g., terminal operation when MCSt resources are allocated).

[0300] For example, in MCSt, sidelink slots less than or equal to a certain gap are consecutively allocated as transmission resources for sidelink transmission, and the same sidelink TB or multiple sidelink TBs can be transmitted using multiple consecutive slots. For example, in MCSt, a terminal can perform LBT in the first slot and transmit the sidelink TB without performing LBT for the sidelink TB transmitted through the subsequent consecutive slots (e.g., consecutive slots less than or equal to a certain gap). For example, performing MCSt-based sidelink transmission may have the effect of reducing the overhead of transmission operations (e.g., performing LBT) in the sidelink unlicensed band, since sidelink data can be transmitted without performing LBT during the gap between consecutive slots for sidelink transmission.

[0301] For example, in the present disclosure, the unlicensed band operation of a terminal for performing sidelink data transmission (e.g., sidelink transmission burst operation or MCSt operation) in consecutive slots within a COT generated by the terminal by performing type 1 LBT may be proposed as follows.

[0302] For example, a terminal may perform type 2 LBT-based data transmission (e.g., sidelink data transmission in consecutive slots without performing LBT (e.g., sidelink transmission burst operation or MCSt operation)) within a COT generated by performing type 1 LBT. For example, a terminal may transmit sidelink data within a COT it generated and then pause the COT so that the COT is not used. For example, the terminal may resume the paused COT and then perform sidelink data transmission (e.g., sidelink transmission burst operation or MCSt operation) again within the generated COT in consecutive slots without performing LBT.

[0303] For example, in the present disclosure, a logical channel prioritization (LCP) operation for sidelink data transmission may be proposed as follows when a terminal suspends and resumes COT use.

[0304] For example, the terminal can perform data transmission based on Type 2 LBT (e.g., sidelink data transmission (e.g., sidelink transmission burst operation or MCSt operation) in consecutive slots without performing LBT) in the COT section generated by successfully performing Type 1 LBT. For example, when the terminal performs Type 2 LBT-based data transmission (e.g., sidelink transmission burst operation or MCSt operation-based data transmission without performing LBT through consecutive slots) in the generated COT, the representative SL-CAPC value for data transmission is the SL CAPC value selected for Type 1 LBT applied when generating the COT (e.g., the SL CAPC value with the highest value among the representative SL-CAPC values ​​of sidelink transmissions (e.g., data) belonging to the sidelink transmission burst or MCSt transmission) (e.g., the SL CAPC value with the lowest SL-CAPC priority) as the SL CAPC value for Type 1 LBT. A representative SL CAPC value for execution can be selected. For example, the terminal can transmit SL TB 1 in slot 1 among the resources selected for transmitting SL data within the generated COT (e.g., resources consisting of consecutive slots). For example, the terminal can suspend its SL data transmission in slot 2 of the consecutive slot resources (e.g., the terminal can determine that the sensing result in this slot 2 is continuously idle).For example, if the terminal decides to resume the use of COT in slot 3 and transmit SL TB 2, when selecting data to transmit in slot 3, the terminal selects the SL CAPC value selected for type 1 LBT when generating the previous COT among logical channel data / MAC CE / PC5-S message / PC5-RRC message (e.g., or a representative SL CAPC value selected for performing type 1 LBT of sidelink transmission burst or MCSt transmission (e.g., a representative SL-CAPC value to be used when performing type 1 LBT for sidelink transmission burst or MCSt transmission, and the representative SL-CAPC value of sidelink transmissions (e.g., data) belonging to the sidelink transmission burst or MCSt transmission) with the largest value (e.g., the SL CAPC with the lowest SL-CAPC priority) The LCP operation can be performed to generate a MAC PDU by filtering only logical channel data / MAC CE / PC5-S messages / PC5-RRC messages having a SL-CAPC value less than or equal to value.

[0305] If a logical channel that satisfies the Channel Access Priority Class (CAPC) is not selected when resuming transmission after a channel sharing has begun, the system may face inefficiencies and priority handling issues. Specifically, without this selection mechanism, if the system does not differentiate between CAPC-based transmissions when resuming transmission, lower-priority data may be transmitted before higher-priority data.

[0306] FIG. 19 illustrates a procedure related to channel occupancy according to an embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure.

[0307] For example, in step S1910, the first device may initiate channel occupation. For example, in step S1920, the first device may share channel occupation with the second device. In step S1930, the first device may reclaim the channel occupation share for the second device. In step S1940, the first device may transmit an SL to the second device within the channel occupation.

[0308] For example, the SL channel access procedure in shared channel occupancy may be as follows.

[0309] For example, when a UE initiates channel occupation using a channel access procedure (e.g., a Type 1 SL channel access procedure) on a channel(s) to transmit SL transmission(s) including PSCCH / PSSCH(s), the UE may provide channel occupation sharing information in the SL control information including at least Layer 1 source and destination IDs, corresponding Channel Access Priority Class (CAPC), remaining channel access interval, and frequency domain information about RB set(s) applicable to the channel occupation.

[0310] For example, when a UE transmits SL transmission(s) in a shared channel occupancy initiated by another UE, the Channel Access Priority Class (CAPC) value corresponding to the SL transmission(s) may be at most equal to the Channel Access Priority Class (CAPC) value provided by the Channel Access Priority Class (CAPC) in the channel occupancy sharing information.

[0311] For example, if a UE shares a channel occupation initiated by another UE using a channel access procedure (e.g., a Type 1 SL channel access procedure) on the channel for transmitting SL transmission(s), the UE may perform an SL transmission following the SL transmission by the UE that initiated the channel occupation after a transmission gap such that:

[0312] - If the transmission gap is 25us, the UE can transmit SL transmission on the channel after performing the Type 2A channel access procedure.

[0313] - If the transmission gap is 16us, the UE can transmit SL transmission on the channel after performing the Type 2B channel access procedure.

[0314] - If the transmission gap is up to 16us, the UE can transmit SL transmission on the channel after performing the Type 2C channel access procedure.

[0315] For example, when using a channel access procedure to initiate channel occupation for transmitting SL transmission(s) and sharing the corresponding channel occupation with another UE transmitting SL transmission(s), the UE that initiated the channel occupation may follow the SL transmission(s) from the other UE in the following manner:

[0316] - If the UE determines the transmission gap from the SL transmission(s) of another UE, the following may apply: - If the transmission gap is 25us, the UE may transmit the SL transmission on the channel after performing the Type 2A channel access procedure. - If the transmission gap is 16us, the UE may transmit the SL transmission on the channel after performing the Type 2B channel access procedure. - If the transmission gap is up to 16us, the UE may transmit the SL transmission on the channel after performing the Type 2C channel access procedure.

[0317] - Otherwise, the UE can transmit SL transmission on the channel after performing the Type 2A channel access procedure.

[0318] For example, the Type 2A SL channel access procedure may be applied to the following transmission(s) performed by the UE:

[0319] - When a UE initiates channel occupation on a channel to transmit SL transmission(s) within the channel occupation, if the UE stops transmitting on the channel, the UE may resume the SL transmission(s) within the channel occupation on the channel after performing a Type 2A SL channel attachment procedure (e.g., if the UE continuously senses that the channel is idle before resuming transmission, when a UE initiates channel occupation on a channel to transmit SL transmission(s) within the channel occupation on the channel, if the UE stops transmitting on the channel, the UE may resume the SL transmission(s) within the channel occupation on the channel after performing a Type 2A SL channel attachment procedure).

[0320] For example, if a series of transmissions includes a transmission pause, the following may apply:

[0321] - If the UE has stopped transmitting, or if the channel sensed by the UE is continuously idle after the UE stopped transmitting, the UE may use the Type 2 channel access procedure or the Channel 2A channel access procedure for subsequent transmissions in the set.

[0322] - If the channel sensed by the UE is not continuously idle after the UE stops transmitting, the UE may use a Type 1 channel access procedure for subsequent transmissions in the set.

[0323] For example, the SCI transmitted on the PSSCH may be a 2nd-stage SCI, which may carry (sidelink) scheduling information. For example, the SCI format 2-A may include CAPC. For example, the SCI format 2-A may include a COT sharing cast type. For example, if the COT sharing cast type field indicates a value of '00', the cast type may be broadcast. For example, if the COT sharing cast type field indicates a value of '01', the cast type may be groupcast when the HARQ-ACK information includes an ACK or a NACK. For example, if the COT sharing cast type field indicates a value of '10', the cast type may be unicast. For example, if the COT sharing cast type field indicates a value of '11', the cast type may be groupcast when the HARQ-ACK information contains only NACK. For example, SCI Format 2-A may include a COT sharing additional ID. For example, the COT sharing additional ID may include a layer 1 destination ID and / or a layer 1 source ID. For example, the layer 1 source ID may be a reserved bit when the cast type field indicates a value of '00' or '01'. For example, SCI Format 2-A may include a remaining COT duration.

[0324] For example, a COT initiating UE can share a COT generated based on type 1 LBT success with a COT responding UE. The COT responding UE can perform type 2 LBT-based data transmission using the shared COT received from the COT initiating UE. For example, the COT initiating UE can retrieve the shared COT it shared with the COT responding UE after the data transmission of the COT responding UE (e.g., data transmitted to its own COT initiating UE) and perform type 2 LBT-based data transmission using the shared COT. For example, when the COT initiating UE retrieves the COT and performs data transmission, the following LCP actions can be performed. For example, a COT initiating UE can transmit a shared COT it generated to a COT responding UE while transmitting SL TB1 in slot 1. For example, the COT responding UE can perform a type 2 LBT-based data transmission using the shared COT received from the COT initiating UE in slot 2. The COT initiating UE can retrieve the shared COT and perform a SL TB 2 transmission in slot 3 within the shared COT.For example, when a COT initiating UE selects sidelink data to transmit when retrieving the shared COT and resuming data transmission in slot 3, the UE may perform an LCP operation to generate MAC PDUs by filtering only logical channel data / MAC CE / PC5 RRC messages / PC5-S messages that have an SL CAP value less than or equal to the representative SL CAPC value for SL TB 1 (or the type 1 LBT associated SL CAPC value used for generating the shared COT) that was transmitted together with the shared COT in the previous slot 1 to the COT initiating UE.

[0325] For example, SL-CAPC applied by a sidelink terminal to perform LBT in a sidelink unlicensed band can be defined as follows.

[0326] - For example, SL-CAPC can be defined to map to each type of data traffic corresponding to SL-CAPC.

[0327] - For example, SL-CAPC contention window size (CWS) and maximum COT value can be defined.

[0328] - For example, SL-CAPC 1 (i.e., the highest priority class): The contention window size (CWS) can be set to the smallest value among SL-CAPCs. For example, it may take the least time to occupy the channel because it has the smallest contention window size (CWS). For example, it may take the least time for clear channel assessment (i.e., the process of determining whether the channel is busy or idle).

[0329] - SL-CAPC 2

[0330] - SL-CAPC 3

[0331] - SL-CAPC 4 (e.g., the lowest priority class): For example, the contention window size (CWS) may be set to the largest value among SL-CAPCs. For example, it may take the longest time to occupy the channel because it has the largest contention window size (CWS). For example, it may take the most time for clear channel assessment (e.g., determining whether the channel is busy or idle).

[0332] By selecting a logical channel that satisfies CAPC when terminating channel occupancy sharing and resuming transmission, a more efficient, reliable, and priority-aware communication system can be built.

[0333] For example, in SL-U, a terminal may first need to occupy a channel in a sidelink unlicensed band in order to transmit SL data. For example, in order to occupy a channel in a sidelink unlicensed band, the terminal may perform LBT (e.g., type 1 LBT: random backoff-based LBT) to find a channel in the unlicensed band that is not occupied by the terminal. For example, if a terminal performing LBT finds a channel that is not occupied by other terminals, it can occupy the channel and transmit SL data. For example, if the LBT process fails, the terminal may adjust the parameter values ​​for performing LBT (e.g., adjusting the contention window size, etc.) to re-perform LBT and continue the process of finding a channel in the unlicensed band that is not occupied by the terminal.

[0334] For example, a transmitting terminal performing (sidelink) communication in an unlicensed band (sl-U) can perform an LBT operation to occupy a channel in the unlicensed band. For example, if the LBT is successful, the terminal can transmit packets in the occupied channel. For example, if the LBT fails (for example, if the terminal detects that the channel is busy as a result of sensing during the sensing slot period), the (sidelink) transmission cannot be performed because the channel in the unlicensed band was not occupied. For example, if the MAC layer of the transmitting terminal detects an (SL) LBT failure while performing an LBT operation to occupy a channel in the unlicensed band, the MAC layer can receive an indication of an (SL) LBT failure event from the physical layer.

[0335] For example, in (sidelink) unlicensed bands (sl-U), a terminal can perform actions based on (SL) LBT failure events as follows.

[0336] For example, the terminal may receive the following parameters for (SL) LBT failure management from the base station and perform (SL) LBT failure recovery or (SL) LBT failure declaration operations.

[0337] - (sl-)lbt-FailureInstanceMaxCount: When the terminal detects an (SL) LBT failure, it increments the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1, and can declare an (SL) LBT failure when it detects (sl-)lbt-FailureInstanceMaxCount number of (SL) LBT failures before (sl-)lbt-FailureDetectionTimer expires.

[0338] - (sl-)lbt-FailureDetectionTimer: A timer that starts when (SL) LBT failure is detected. The (SL) LBT failure recovery process can be performed while the timer is running.

[0339] For example, when the MAC layer of a transmitting terminal receives a (SL) LBT failure event from the physical layer (i.e., when the terminal detects an (SL) LBT failure), the MAC layer may start the (sl-)lbt-FailureDetectionTimer timer and simultaneously increase the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1. For example, the (SL) LBT recovery process may be performed during the operation of the (sl-)lbt-FailureDetectionTimer timer. For example, when the terminal detects an (SL) LBT failure again during the operation of the (sl-)lbt-FailureDetectionTimer timer, the terminal may increase the LBT_COUNTER (e.g., SL_LBT_COUNTER) by 1. For example, if the LBT_COUNTER (e.g., SL_LBT_COUNTER) incremented due to (SL) LBT detection does not reach the threshold number of times ((sl-)lbt-FailureInstanceMaxCount) before the (sl-)lbt-FailureDetectionTimer timer expires, the terminal considers the (SL) LBT failure to have been recovered and can continue to perform normal (sidelink) communication using the (sidelink) grant in use.

[0340] For example, a consistent (SL) LBT failure can be declared if the LBT_COUNTER (e.g., SL_LBT_COUNTER) incremented due to (SL) LBT failure detection reaches a threshold number of times ((sl-)lbt-FailureInstanceMaxCount) before the (sl-)lbt-FailureDetectionTimer timer expires. For example, a transmitting terminal can declare an SL LBT failure if the SL LBT failure is not recovered by the time the (sl-)lbt-FailureDetectionTimer timer expires.

[0341] For example, a terminal can reselect resources by triggering a pre-emption or re-evaluation procedure if the following conditions are met:

[0342] pre-emption

[0343] - When the priority value related to the other party's reserved resources is lower than the pre-emption priority threshold set by the base station.

[0344] - When the priority value related to the other party's reserved resources is lower than the priority value of one's own transmission packet.

[0345] - When the RSRP measurement value of the other party's reservation resource that overlaps with my reservation resource in the SA set (e.g., the physical layer can select a sensing-based idle resource set (e.g., the SA set) and pass it to the MAC layer) is above the threshold level.

[0346] re-evaluation

[0347] - When the RSRP measurement value of the other party's reservation resource that overlaps with my reservation resource in the SA set is above the threshold level.

[0348] For example, resource (re)selection in MCSt and COT and logical channel prioritization (LCP) constraints may be as follows.

[0349] For example, when a user equipment (UE) generates multiple sidelink grants within a COT it has generated, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of the SL data on the sidelink grants. For example, when a UE generates multiple sidelink grants within a COT it has generated, if the CAPC value of the SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of the SL data associated with a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure for the subsequent sidelink grant can be triggered. For example, after the UE selects an MCSt resource for multiple sidelink TBs, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of the SL data for the sidelink grant on the MCSt.

[0350] For example, after the UE selects MCSt resources for multiple sidelink TBs, the UE may perform a destination selection procedure in the LCP procedure by considering the CAPC value of the SL data on the sidelink grant for the MCSt. For example, when the UE selects MCSt resources for multiple sidelink TBs, if the CAPC value of the SL data related to the subsequent sidelink grant resource is greater than the CAPC value of the SL data on the preceding sidelink grant resource, a resource reselection procedure for the subsequent sidelink grant may be triggered.

[0351] For example, when a UE generates multiple sidelink grants within a COT it has generated, it can perform a destination selection procedure in an LCP procedure by considering the CAPC value of SL data on the sidelink grant.

[0352] For example, when a UE generates multiple sidelink grants within a COT it has generated, if the CAPC value of SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of SL data on a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure of the subsequent sidelink grant may be triggered.

[0353] For example, after the UE selects MCSt resources for multiple sidelink TBs, it may perform a destination selection procedure in the LCP procedure by considering the CAPC value of SL data on the sidelink grant for MCSt.

[0354] For example, when a UE selects an MCSt resource for multiple sidelink TBs, if the CAPC value of SL data associated with a subsequent sidelink grant resource (e.g., the subsequent sidelink grant in the time domain) is greater than the CAPC value of SL data on a preceding sidelink grant resource (e.g., the preceding sidelink grant in the time domain), a resource reselection procedure of the subsequent sidelink grant may be triggered.

[0355] For example, the above proposals (e.g., the proposals for sidelink transmission burst-based terminal operation described in the present disclosure) can be equally extended and applied to the case where a terminal performs multiple consecutive slot transmission (MCSt)-based operation in the sidelink (e.g., terminal operation when MCSt resources are allocated).

[0356] For example, in MCSt, sidelink slots less than or equal to a certain gap are consecutively allocated as transmission resources for sidelink transmission, and the same sidelink TB or multiple sidelink TBs can be transmitted using multiple consecutive slots. For example, in MCSt, a terminal can perform LBT in the first slot and transmit the sidelink TB without performing LBT for the sidelink TB transmitted through the subsequent consecutive slots (e.g., consecutive slots less than or equal to a certain gap). For example, performing MCSt-based sidelink transmission may have the effect of reducing the overhead of transmission operations (e.g., performing LBT) in the sidelink unlicensed band, since sidelink data can be transmitted without performing LBT during the gap between consecutive slots for sidelink transmission.

[0357] For example, a) during MCSt operation, the RSRP threshold value that triggers pre-emption or re-evaluation-based resource reselection may be independently set (e.g., compared to the RSRP threshold value related to existing sensing operations, e.g., compared to the RSRP threshold value related to sensing operations in non-MCSt operations or licensed band operations) or a preset offset value may be additionally applied (e.g., compared to the RSRP threshold value obtained as a result of existing sensing operations). For example, the purpose of separately defining an independent parameter in MCSt may be to operate the resource selection procedure conservatively (e.g., to operate so that resource reselection is not triggered frequently).

[0358] For example, a priority threshold (e.g., and / or RSRP threshold value) for MCSt operation (related to reserved resources of own or other terminals) may be set separately from a priority threshold (e.g., and / or RSRP threshold value) related to pre-emption or re-evaluation (related to reserved resources of own or other terminals) applied to non-MCSt operation. For example, the purpose of defining an independent parameter separately in MCSt may be to operate the resource selection procedure conservatively (e.g., to operate so that resource re-selection is not triggered frequently).

[0359] For example, in the case of MCSt operation, if the terminal has some degree of anticipation that an LBT failure will occur in the future, it may not perform resource reselection even if a resource satisfying the pre-emption or re-evaluation conditions is detected. For example, the terminal operation may be applied only to a resource other than the last resource among the MCSt resources.

[0360] For example, when the MCSt operation is performed, the terminal may perform a resource reselection procedure (e.g., 1. reselect all MCSt resources or 2. reselect only resources that satisfy the pre-emption or re-evaluation conditions) if LBT fails or succeeds and a resource satisfying the pre-emption or re-evaluation conditions is detected.

[0361] For example, when an LBT failure occurs during MCSt operation, the terminal can perform resource reselection for resources that do not satisfy the pre-emption or re-evaluation conditions (e.g., 1. reselect all MCSt resources or 2. reselect only resources that satisfy the pre-emption or re-evaluation conditions).

[0362] For example, when the MCSt operation is successful, the terminal can perform resource reselection (e.g., 1. reselect all MCSt resources or 2. reselect only resources that satisfy the pre-emption or re-evaluation conditions) for resources that do not satisfy the LBT conditions.

[0363] For example, it can be assumed that a terminal performs unlicensed band operation by selecting the following resources as MCSt resources.

[0364] For example, an MCSt structure could be resource 1 (e.g., slot 1) + resource 2 (e.g., slot 2) + resource 3 (e.g., slot 3).

[0365] For example, if the re-evaluation check is performed at (slot 1 - offset 1) and resource 2 satisfies the conditions for re-evaluation-based resource reselection, then resource 2 and resource 3 can be re-selected to reconstruct the MCSt structure of resource 1 / resource 2 / resource 3, or resource 1 / resource 2 / resource 3 can be re-selected to reconstruct the resource 1 / resource 2 / resource 3 resources. This behavior is possible because the re-evaluation check is performed at a time before resource 1 is reached.

[0366] For example, it can be assumed that the terminal performs unlicensed band operation by selecting the following resources as MCSt resources.

[0367] For example, an MCSt structure could be resource 1 (e.g., slot 1) + resource 2 (e.g., slot 2) + resource 3 (e.g., slot 3) + resource 4 (e.g., slot 4) + resource 5 (e.g., slot 5).

[0368] For example, if the re-evaluation execution check point is between slot 1 and slot 2, and resource 2 / resource 3 is indicated through SCI of resource 1, and MAC requests PHY to perform a re-evaluation check for resource 4 and resource 5, if resource 4 satisfies the re-evaluation-based resource reselection condition, resource 4 or resource 4 and / or resource 5 can be reselected to maintain resource 1 / resource 2 / resource 3 / resource 4 / resource 5 as MCSt structure.

[0369] For example, although the operation in the present disclosure is described as an unlicensed band operation between terminals, the same may be applied to an unlicensed band operation between a terminal and a base station.

[0370] For example, in the embodiments of the present disclosure, “channel” may be replaced with “carrier” or “a set of resource blocks of a specific carrier” or “band”.

[0371] For example, in the embodiments of the present disclosure, “transmission resources” may be replaced with “uplink grant” or “sidelink grant”.

[0372] For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to SL-CAPC (Channel Access Priority Class). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to SL-LBT types (e.g., Type 1 LBT, Type 2A LBT, Type 2B LTB, or Type 2C LBT). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to FBE (Frame Based LBT). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applied and / or the associated parameters (e.g., threshold values)) may be set specifically (and / or independently and / or differently) depending on whether LBE (Load Based LBT) is applied.

[0373] For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applied and / or related parameters (e.g., threshold values)) can be specifically (and / or independently and / or differently) set depending on whether LBT is successful and / or LBT is unsuccessful. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applied and / or related parameters (e.g., threshold values)) can be specifically (and / or independently and / or differently) set depending on whether LBT is successful and / or LBT is unsuccessful. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applied and / or related parameters (e.g., threshold values)) can be specifically (and / or independently and / or differently) set depending on LBT-related energy detection levels. For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure apply and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured for each sidelink channel (e.g., PSCCH / PSSCH, PSFCH, SL-SSB). For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure apply and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured depending on whether MCSt (multi-consecutive slot transmission) applies. For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure apply and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured depending on whether multiple PSFCH (multi-PSFCH) occasions apply.For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) may be specifically (and / or independently and / or differently) set depending on the resource order / location constituting the MCSt. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) may be specifically (and / or independently and / or differently) set depending on whether multiple starting points are set within one slot. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applied and / or the associated parameters (e.g., threshold values)) may be set specifically (and / or independently and / or differently) depending on whether the first (1st) starting point (e.g., or the second (2nd) starting point) is applied.

[0374] For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the resource pool. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the congestion level. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the priority of the service. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to the type of service. For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to QoS requirements (e.g., latency, reliability). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) set according to PQI (5QI (5G QoS identifier) ​​for PC5). For example, the present disclosure (e.g., whether (some) of the proposed methods / rules of the present disclosure are applicable and / or the associated parameters (e.g., thresholds)) may be set specifically (and / or independently and / or differently) depending on the traffic type (e.g., periodic generation and / or aperiodic generation).For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured according to a (SL) transmission resource allocation mode (e.g., mode 1 and / or mode 2). For example, the present disclosure (e.g., whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds)) can be specifically (and / or independently and / or differently) configured according to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).

[0375] For example, the present disclosure may determine whether a proposed rule is applied (and / or a related parameter setting value) whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured), resource pool (e.g., resource pool with PSFCH configured, resource pool without PSFCH configured), service / packet type (and / or priority), QoS profile or QoS requirement (e.g., URLLC / EMBB traffic, reliability, latency), PQI, PFI, cast type (e.g., unicast, groupcast, broadcast), (resource pool) congestion level (e.g., CBR), SL HARQ feedback scheme (e.g., NACK only feedback, ACK / NACK feedback), HARQ feedback enabled MAC PDU. (and / or HARQ feedback disabled MAC PDU) transmission, whether to set PUCCH-based SL HARQ feedback reporting operation, pre-emption (and / or re-evaluation) (non)perform (or resource reselection based on), (L2 or L1) (source and / or destination) identifier, (L2 or L1) (combination of source layer ID and destination layer ID) identifier, (L2 or L1) (combination of a pair of source layer ID and destination layer ID and cast type) identifier,At least one of a direction of a pair of source layer ID and destination layer ID, a PC5 RRC connection / link, SL DRX (non)performance (or support), SL mode type (resource allocation mode 1, resource allocation mode 2), (non)periodic resource reservation performance, and a Tx profile (e.g., a Tx profile indicating that the service supports (sidelink) DRX operation, a Tx profile indicating that the service does not need to support (sidelink) DRX operation) can be configured specifically (and / or independently and / or differently).

[0376] For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) configured for whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured). For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) configured for a resource pool (e.g., a resource pool where PSFCH is configured, a resource pool where PSFCH is not configured). For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) configured for a service / packet type (and / or priority). For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) set for a QoS profile or QoS requirements (e.g., URLLC / EMBB traffic, reliability, latency). For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) set for a PQI. For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) set for a PFI.For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be set specifically (and / or independently and / or differently) for a cast type. For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be set specifically (and / or independently and / or differently) for unicast. For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be set specifically (and / or independently and / or differently) for groupcast. For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be set specifically (and / or independently and / or differently) for broadcast. For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) set for a (resource pool) congestion level (e.g., CBR). For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) set for a SL HARQ feedback scheme (e.g., NACK only feedback, ACK / NACK feedback).For example, the present disclosure (e.g., whether the proposed rule applies (and / or the relevant parameter setting value)) can be specifically (and / or independently and / or differently) configured for HARQ feedback enabled MAC PDU (and / or HARQ feedback disabled MAC PDU) transmission. For example, the present disclosure (e.g., whether the proposed rule applies (and / or the relevant parameter setting value)) can be specifically (and / or independently and / or differently) configured for PUCCH-based SL HARQ feedback reporting operation configuration. For example, the present disclosure (e.g., whether a proposed rule applies (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) set for pre-emption (and / or re-evaluation) (non)performance (or resource reselection based). For example, the present disclosure (e.g., whether a proposed rule applies (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) set for (L2 or L1) (source and / or destination) identifiers. For example, the present disclosure (e.g., whether a proposed rule applies (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) set for (L2 or L1) (a combination of source layer ID and destination layer ID) identifiers.For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) set for an identifier (L2 or L1) (a combination of a pair of source layer ID and destination layer ID and a cast type). For example, the present disclosure (e.g., whether a proposed rule is applied (and / or a related parameter setting value)) can be specifically (and / or independently and / or differently) set for a direction of a pair of source layer ID and destination layer ID. For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be configured specifically (and / or independently and / or differently) for PC5 RRC connection / link. For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be configured specifically (and / or independently and / or differently) for SL DRX (non)performance (or support). For example, the present disclosure (e.g., whether to apply a proposed rule (and / or related parameter setting values)) can be configured specifically (and / or independently and / or differently) for SL mode types (resource allocation mode 1, resource allocation mode 2).For example, the present disclosure (e.g., whether a proposed rule is applied (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) configured for performing (non-)periodic resource reservation. For example, the present disclosure (e.g., whether a proposed rule is applied (and / or related parameter setting values)) can be specifically (and / or independently and / or differently) configured for a Tx profile (e.g., a Tx profile indicating that the service supports (sidelink) DRX operation, a Tx profile indicating that the service does not need to support (sidelink) DRX operation).

[0377] For example, the applicability of the proposals and proposed rules of the present disclosure (and / or the associated parameter settings) may also be applied to mmWave SL operation.

[0378] FIG. 20 illustrates a method for a first device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure.

[0379] Referring to FIG. 20, in step S2010, the first device can initiate channel occupation. In step S2020, the first device can share the channel occupation. In step S2030, the first device can recover the share of the channel occupation. In step S2040, the first device can perform SL (sidelink) transmission within the channel occupation. For example, a MAC (medium access control) protocol data unit (PDU) related to the SL transmission can be generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to the sharing of the channel occupation.

[0380] For example, the initiation of the above channel occupation may be based on type 1 LBT (listen before talk).

[0381] For example, the above SL transmission may be based on Type 2 LBT.

[0382] For example, the Type 2 LBT may include any one of a Type 2A LBT, a Type 2B LBT, or a Type 2C LBT.

[0383] For example, the above method can be performed by a first device.

[0384] For example, the first device may be a user equipment (UE) that initiates a channel occupancy time (COT).

[0385] For example, the sharing of the channel occupancy may be based on the provision of channel occupancy sharing information by the first device.

[0386] For example, the channel occupancy sharing information may include the first CAPC value.

[0387] For example, the channel occupancy sharing information can be transmitted from the first device to the second device.

[0388] For example, the second device may be a responding UE.

[0389] For example, the first device can perform SL reception from the second device to the first device in the shared channel occupancy.

[0390] For example, the above SL reception may be based on Type 2 LBT.

[0391] For example, the Type 2 LBT may include any one of a Type 2A LBT, a Type 2B LBT, or a Type 2C LBT.

[0392] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) can initiate channel occupation. Then, the processor (102) of the first device (100) can share the channel occupation. Then, the processor (102) of the first device (100) can recover the share of the channel occupation. Then, the processor (102) of the first device (100) can perform SL (sidelink) transmission within the channel occupation. For example, a MAC (medium access control) protocol data unit (PDU) related to the SL transmission can be generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to the sharing of the channel occupation.

[0393] According to one embodiment of the present disclosure, a first device configured to perform 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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: initiate channel occupation; share the channel occupation; reclaim the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupation.

[0394] According to one embodiment of the present disclosure, a processing device configured to control a first device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: initiate channel occupation; share the channel occupation; reclaim the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupation.

[0395] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: initiate channel occupation; share the channel occupation; recover the share of the channel occupation; and perform sidelink (SL) transmission within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupation.

[0396] FIG. 21 illustrates a method for a second device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure.

[0397] Referring to FIG. 21, in step S2110, the second device can share the second channel occupancy. For example, the sharing of the channel occupancy can be recovered. In step S2120, the second device can perform SL (sidelink) reception within the channel occupancy. For example, a MAC (medium access control) protocol data unit (PDU) related to the SL transmission can be generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to the sharing of the channel occupancy.

[0398] For example, the initiation of the above channel occupation may be based on type 1 LBT (listen before talk).

[0399] For example, the above SL transmission may be based on Type 2 LBT.

[0400] For example, the Type 2 LBT may include any one of a Type 2A LBT, a Type 2B LBT, or a Type 2C LBT.

[0401] For example, the above method can be performed by a first device.

[0402] For example, the first device may be a user equipment (UE) that initiates a channel occupancy time (COT).

[0403] For example, the sharing of the channel occupancy may be based on the provision of channel occupancy sharing information by the first device.

[0404] For example, the channel occupancy sharing information may include the first CAPC value.

[0405] For example, the channel occupancy sharing information can be transmitted from the first device to the second device.

[0406] For example, the second device may be a responding UE.

[0407] For example, the second device can perform SL transmission from the second device to the first device in the shared channel occupancy.

[0408] For example, the above SL reception may be based on Type 2 LBT.

[0409] For example, the Type 2 LBT may include any one of a Type 2A LBT, a Type 2B LBT, or a Type 2C LBT.

[0410] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the second device (200) can share the second channel occupancy. For example, the sharing of the channel occupancy can be recovered. Then, the processor (202) of the second device (200) can control the transceiver (206) to perform SL (sidelink) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) related to the SL transmission can be generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to the sharing of the channel occupancy.

[0411] According to one embodiment of the present disclosure, a second device configured to perform 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, based on execution by the at least one processor, may cause the second device to: share a channel occupation. For example, the share of the channel occupation may be reclaimed. For example, the instructions, based on execution by the at least one processor, may cause the second device to: perform sidelink (SL) reception within the channel occupation. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupation.

[0412] According to one embodiment of the present disclosure, a processing device configured to control a second device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the second device to: share a channel occupancy. For example, the share of the channel occupancy may be reclaimed. For example, the instructions, based on execution by the at least one processor, may cause the second device to: perform sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the share of the channel occupancy.

[0413] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a second device to: share channel occupancy. For example, the share of the channel occupancy may be reclaimed. For example, the instructions, when executed, may cause the second device to: perform sidelink (SL) reception within the channel occupancy. For example, a medium access control (MAC) protocol data unit (PDU) associated with the SL transmission may be generated based on a second channel access priority class (CAPC) value associated with the SL transmission being less than or equal to a first CAPC value associated with the sharing of the channel occupancy.

[0414] The various embodiments of the present disclosure may be combined with each other.

[0415] Below, a description is given of devices to which various embodiments of the present disclosure can be applied.

[0416] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0417] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0418] FIG. 22 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 22 can be combined with various embodiments of the present disclosure.

[0419] Referring to FIG. 22, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., an Advanced Air Mobility (AAM)). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may also be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0420] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0421] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0422] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0423] FIG. 23 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure.

[0424] Referring to FIG. 23, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 22.

[0425] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0426] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0427] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0428] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. 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, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0429] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0430] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 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, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0431] FIG. 24 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 24 can be combined with various embodiments of the present disclosure.

[0432] Referring to FIG. 24, 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). Although not limited thereto, the operations / functions of FIG. 24 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. The hardware elements of FIG. 24 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 23. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 23, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 23.

[0433] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 24. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., a PUSCH or a PDSCH).

[0434] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by a precoding matrix W of N*M. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.

[0435] The resource mapper (1050) can map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator (1060) generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0436] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 24. For example, a wireless device (e.g., 100, 200 of FIG. 23) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0437] Figure 25 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 22). The embodiment of Figure 25 may be combined with various embodiments of the present disclosure.

[0438] Referring to FIG. 25, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 23 and may be composed of various elements, components, units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 23. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 23. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0439] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 22, 100a), a vehicle (Fig. 22, 100b-1, 100b-2), an XR device (Fig. 22, 100c), a portable device (Fig. 22, 100d), a home appliance (Fig. 22, 100e), an IoT device (Fig. 22, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 22, 400), a base station (Fig. 22, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0440] In FIG. 25, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be interconnected entirely via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of 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.

[0441] Below, the implementation example of Fig. 25 is described in more detail with reference to the drawings.

[0442] FIG. 26 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile 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). The embodiment of FIG. 26 may be combined with various embodiments of the present disclosure.

[0443] Referring to FIG. 26, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output 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 blocks 110 to 130 / 140 of FIG. 25, respectively.

[0444] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control components of the mobile device (100) to perform various operations. The control unit (120) can include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / codes / commands required for operating the mobile device (100). In addition, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the mobile device (100) and can include a wired / wireless charging circuit, a battery, etc. The interface unit (140b) can support connection between the mobile device (100) and other external devices. The interface unit (140b) can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can input or output video information / signals, audio information / signals, data, and / or information input from a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker, and / or a haptic module.

[0445] For example, in the case of data communication, the input / output unit (140c) obtains information / signals (e.g., touch, text, voice, image, video) input by the user, and the obtained information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals, and can directly transmit the converted wireless signals to other wireless devices or to a base station. In addition, the communication unit (110) can receive wireless signals from other wireless devices or base stations, and then restore the received wireless signals to the original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0446] Figure 27 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like. The embodiment of Figure 27 may be combined with various embodiments of the present disclosure.

[0447] Referring to FIG. 27, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving 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 blocks 110 / 130 / 140 of FIG. 25, respectively.

[0448] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection 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, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0449] 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 route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0450] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In the method, Step of initiating channel occupation; Step of sharing the above channel occupancy; a step of recovering the share of the above channel occupancy; and A step of performing SL (sidelink) transmission within the above channel occupancy; including, A method in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

2. In paragraph 1, A method in which the above channel occupation is initiated based on type 1 LBT (listen before talk).

3. In paragraph 1, The above SL transmission method is based on type 2 LBT.

4. In paragraph 3, A method wherein the above type 2 LBT comprises any one of type 2A LBT, type 2B LBT, or type 2C LBT.

5. In paragraph 1, A method, wherein the above method is performed by a first device.

6. In paragraph 5, A method wherein the first device is a UE (user equipment) that initiates a COT (channel occupancy time).

7. In paragraph 5, A method wherein the sharing of the above channel occupancy is based on the provision of channel occupancy sharing information by the first device.

8. In paragraph 7, A method wherein the channel occupancy sharing information includes the first CAPC value.

9. In paragraph 7, A method in which the above channel occupancy sharing information is transmitted from the first device to the second device.

10. In paragraph 9, A method wherein the second device is a responding UE.

11. In paragraph 9, A method further comprising: performing SL reception from the second device to the first device in the shared channel occupancy; 12. In paragraph 11, The above SL reception method is based on type 2 LBT.

13. In paragraph 12, A method wherein the above type 2 LBT comprises any one of type 2A LBT, type 2B LBT, or type 2C LBT.

14. In the first device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Initiate channel occupation; Share the above channel occupancy; To recover the share of the above channel occupancy; and Perform SL (sidelink) transmission within the above channel occupancy, A first device, wherein a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

15. In a processing device set to control the first device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Initiate channel occupation; Share the above channel occupancy; To recover the share of the above channel occupancy; and Perform SL (sidelink) transmission within the above channel occupancy, A processing device in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Initiate channel occupation; Share the above channel occupancy; To recover the share of the above channel occupancy; and Perform SL (sidelink) transmission within the above channel occupancy, A non-transitory computer-readable storage medium in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupancy.

17. In the method, Steps to share channel occupancy, The share of the above channel occupancy is recovered; and A step of performing SL (sidelink) reception within the above channel occupancy; A method in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

18. In the second device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Let's share the channel occupancy, The share of the above channel occupancy is recovered; and Perform SL (sidelink) reception within the above channel occupancy, A second device, wherein a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

19. In a processing device set to control a second device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Let's share the channel occupancy, The share of the above channel occupancy is recovered; and Perform SL (sidelink) reception within the above channel occupancy, A processing device in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupation.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the second device to: Let's share the channel occupancy, The share of the above channel occupancy is recovered; and Perform SL (sidelink) reception within the above channel occupancy, A non-transitory computer-readable storage medium in which a MAC (medium access control) PDU (protocol data unit) related to the SL transmission is generated based on a second CAPC (channel access priority class) value related to the SL transmission being less than or equal to a first CAPC value related to sharing of the channel occupancy.

Images