Method and device for performing communication in wireless communication system

The method improves wireless communication efficiency by coordinating channel occupancy and scheduling in 6G systems, addressing challenges of high data rates and low latency through efficient resource management and energy optimization.

WO2024248561A1PCT designated stage expired Publication Date: 2024-12-05LG ELECTRONICS INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/007556
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-06-02
Filing Date
2024-06-03
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Current wireless communication systems, particularly 5G NR and future 6G systems, face challenges in efficiently managing channel occupancy and scheduling in multi-device, low-latency environments with high data rates and energy efficiency requirements, especially for battery-free IoT devices and ultra-reliable connectivity.

Method used

The proposed method involves a device transmitting control information for scheduling a physical shared channel and sharing channel occupancy information, including an additional ID and channel occupancy time, to enable efficient resource management and timing coordination among devices.

Benefits of technology

This approach enhances communication efficiency by optimizing channel usage and reducing energy consumption, supporting high data rates, low latency, and ultra-reliable connectivity in 6G systems, particularly for IoT devices and autonomous vehicles.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024007556_05122024_PF_FP_ABST
    Figure KR2024007556_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a method for a first device to perform wireless communication and a device for supporting same. The method may comprise the steps of: transmitting, on a physical control channel to a second device, first control information for scheduling a physical shared channel and second control information; and transmitting, on the physical shared channel to the second device, the second control information including sharing information, which includes data and an additional identity (ID) for channel occupancy time (COT) sharing related to a third device, about channel occupancy. For example, a timer related to an active time of the third device may start on the basis of the transmission of the second control information including the sharing information, which includes the data and the additional ID for COT sharing related to the third device, about channel occupancy.
Need to check novelty before this filing date? Find Prior Art

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] Per device peak data rate1 TbpsE2E latency1 msMaximum spectral efficiency100bps / HzMobility supportUp to 1000km / hrSatellite integrationFullyAIFullyAutonomous vehicleFullyXRFullyHaptic CommunicationFully

[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: transmitting, to a second device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and transmitting, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, the second control information including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on the transmission of the second control information including sharing information about channel occupancy, the additional ID for sharing data and a COT associated with the third device.

[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, cause the first device to: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on the transmission of the second control information including sharing information about channel occupancy, including the additional ID for sharing data and a COT associated with the third device.

[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, cause the first device to: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on the transmission of the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[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: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on the transmission of the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0010] In one embodiment, a method performed by a second device may be provided. The method may include: receiving, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receiving, from the first device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, the sharing information including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information about channel occupancy, the sharing information including the additional ID for sharing data and a COT associated with the third device.

[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, cause the second device to: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information about channel occupancy, including the additional ID for sharing data and a COT associated with the third device.

[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, cause the second device to: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information about channel occupancy, including the additional ID for sharing data and a COT associated with the third device.

[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: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0014] The present disclosure can provide a device and method capable of 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 an embodiment related to transmission operations of a terminal within a shared COT according to one embodiment of the present disclosure.

[0032] FIG. 18 illustrates an embodiment related to the initiation of a timer associated with an active time, according to one embodiment of the present disclosure.

[0033] FIG. 19 illustrates an embodiment related to the initiation of a timer associated with an active time, 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] - Blockchain

[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 illustrates the number of symbols per slot (Nslotsymb), the number of slots per frame (Nframe,uslot), and the number of slots per subframe (Nsubframe,uslot) depending on the SCS setting (u) when normal CP or extended CP is used.

[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] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. 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 may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S820, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S830, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S840, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

[0116] 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 within the set resource pool. For example, the terminal can select resources 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 within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal using the resources. In step S820, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S830, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0117] 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., 2-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., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

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

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

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

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

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

[0123] 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 3.

[0124] uM01015

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

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

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

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

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

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

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

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

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

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

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

[0136] - Channel Access Procedure (CAP): This refers to the procedure for evaluating channel availability based on sensing to determine whether other communication node(s) are using the channel before signal transmission. The basic unit for sensing is a sensing slot with a duration of Tsl=9us. If the base station or terminal senses the channel during the sensing slot period, and the detected power for at least 4us within the sensing slot period is less than the energy detection threshold XThresh, the sensing slot period Tsl is considered to be idle. Otherwise, the sensing slot period Tsl=9us is considered to be busy. CAP may be referred to as LBT (Listen-Before-Talk).

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

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

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

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

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

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

[0143] 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 a clear channel assessment (CCA) has been confirmed. If there is a CCA threshold (e.g., XThresh) that is predefined or set by a higher layer (e.g., RRC), the communication node may determine the channel state as busy if energy higher than the CCA threshold is detected in the channel, and otherwise determine the channel state as idle. If the channel condition is determined to be idle, the communicating node can initiate signal transmission in the unlicensed band. CAP can be replaced with LBT.

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

[0145] TypeExplanationDLType 1 CAPCAP with random back-off- time duration spanned by the sensing slots that are sensed to be idle before a downlink transmission(s) is randomType 2 CAP- Type 2A, 2B, 2CCAP without random back-off- time duration spanned by sensing slots that are sensed to be idle before a downlink transmission(s) is deterministicUL or SLType 1 CAPCAP with random back-off- time duration spanned by the sensing slots that are sensed to be idle before an uplink or sidelink transmission(s) is randomType 2 CAP- Type 2A, 2B, 2CCAP without random back-off- time duration spanned by sensing slots that are sensed to be idle before an uplink or sidelink transmission(s) is deterministic

[0146] Referring to Table 4, LBT types or CAPs for DL / UL / SL transmissions can be defined. However, Table 4 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.

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

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

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

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

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

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

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

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

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

[0156] 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 5 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.

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

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

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

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

[0161] 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:

[0162] - (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

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

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

[0165] Referring to Figure 13, the base station first senses whether the channel is idle during the sensing slot period of the defer duration Td, and then, when 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:

[0166] Step 1) (S120) Set N=Ninit, where Ninit is a random value uniformly distributed between 0 and CWp. Then, proceed to Step 4.

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

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

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

[0170] Step 5) (S160) Sensing the channel until a busy sensing slot is detected within the additional delay period Td or all sensing slots within the additional delay period Td are detected as idle.

[0171] Step 6) (S170) If the channel is sensed as idle during all sensing slot periods of the additional delay period Td (Y), go to Step 4. Otherwise (N), go to Step 5.

[0172] Table 6 illustrates how the mp, minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes applied to CAP vary depending on the channel access priority class.

[0173] Channel Access Priority Class (p)m p CW min,p CW max,p T me,p allowed CW p sizes11372 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}

[0174] Referring to Table 6, the contention window size (CWS) and maximum COT value for each CAPC can be defined. For example, Td = Tf + mp * Tsl.

[0175] The delay interval Td is composed of an interval Tf (16us) + mp consecutive sensing slot intervals Tsl (9us), in that order. Tf includes the sensing slot interval Tsl at the start of the 16us interval.

[0176] CWmin,p <= CWp <= CWmax,p. CWp is set as CWp = CWmin,p and can be updated (CW size update) before step 1 based on the HARQ-ACK feedback (e.g., ACK or NACK rate) for the previous DL burst (e.g., PDSCH). For example, CWp can be initialized to CWmin,p, increased to the next highest allowed value, or kept at the current value, based on the HARQ-ACK feedback for the previous DL burst.

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

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

[0179] Type 2A DL CAP can be applied to the transmissions below. In Type 2A DL CAP, the base station can transmit immediately after the channel is sensed as idle for at least a sensing period Tshort_dl = 25us. Here, Tshort_dl consists of a period Tf (= 16us) and one sensing slot period immediately following it. Tf includes a sensing slot at the beginning of the period.

[0180] - 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,

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

[0182] Type 2B DL ​​CAP is applicable to transmission(s) performed by the base station after a 16us gap from transmission(s) by the terminal within the shared channel occupancy time. In Type 2B DL ​​CAP, the base station can transmit transmission immediately after the channel is sensed as idle for Tf=16us. Tf includes the 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 maximum 16us gap 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 the transmission.

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

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

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

[0186] 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:

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

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

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

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

[0191] Referring to Figure 14, the terminal first senses whether the channel is idle during the sensing slot period of the defer duration Td, and then, 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:

[0192] Step 1) (S220) Set N=Ninit, where Ninit is a random value uniformly distributed between 0 and CWp. Then, proceed to Step 4.

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

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

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

[0196] Step 5) (S260) Sensing the channel until a busy sensing slot is detected within the additional delay period Td or all sensing slots within the additional delay period Td are detected as idle.

[0197] Step 6) (S270) If the channel is sensed as idle during all sensing slot periods of the additional delay period Td (Y), go to Step 4. Otherwise (N), go to Step 5.

[0198] Table 7 illustrates how the mp, minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes applied to a CAP vary depending on the channel access priority class.

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

[0200] Referring to Table 7, the contention window size (CWS) and maximum COT value for each CAPC can be defined. For example, Td = Tf + mp * Tsl.

[0201] The delay interval Td is composed of an interval Tf (16us) + mp consecutive sensing slot intervals Tsl (9us), in that order. Tf includes the sensing slot interval Tsl at the start of the 16us interval.

[0202] CWmin,p <= CWp <= CWmax,p. CWp is set as CWp = CWmin,p and can be updated (CW size update) before Step 1 based on the explicit / implicit reception acknowledgment for the previous UL burst (e.g., PUSCH). For example, CWp can be initialized to CWmin,p, increased to the next highest allowed value, or kept at the existing value, based on the explicit / implicit reception acknowledgment for the previous UL burst.

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

[0204] In a Type 2 UL CAP, the length of the time interval spanned by the sensing slots during which the channel is sensed as idle before a transmission(s) is deterministic. Type 2 UL CAP is divided into Type 2A / 2B / 2C UL CAP. In a Type 2A UL CAP, a UE can transmit a transmission immediately after the channel has been sensed as idle for at least a sensing interval Tshort_dl=25us. Here, Tshort_dl consists of an interval Tf(=16us) and one sensing slot interval immediately following it. In a Type 2A UL CAP, Tf includes a sensing slot at the beginning of the interval. In a Type 2B UL CAP, a UE can transmit a transmission immediately after the channel has been sensed as idle for a sensing interval Tf=16us. In a Type 2B UL CAP, Tf includes 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.

[0205] For example, according to the 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 perform the NR-U operation by applying the parameters of the corresponding CACP (e.g., minimum contention window size, maximum contention window size, mp, etc.). 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 0 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 sensing the channel decrements the BC by 1 when the channel is idle. When the BC becomes zero and the terminal detects that the channel is idle for a time Td (Td = Tf + mp * Tsl), the terminal can occupy the channel and attempt to transmit data. If a terminal attempting data transmission detects a collision, it can increase the CW size mapped to the CAPC, and reselect a BC between zero and the increased CW. A terminal that successfully transmits a packet can reset the CW size (to CW min).

[0206] For example, Tsl (= 9 usec) is a basic sensing unit or sensing slot and can include a measurement duration of at least 4 usec. For example, the first 9 usec of Tf (= 16 usec) can be configured as Tsl. For example, mp can be a constant mapped by CAPC and can be used in calculating Td. For example, a smaller value can be mapped as the CACP value decreases (the priority increases).

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

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

[0209] 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 is idle, the terminal can seize the channel and attempt to transmit data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0232] FIG. 17 illustrates an embodiment related to a transmission operation of a terminal within a shared COT according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.

[0233] Referring to FIG. 17, for example, a terminal (e.g., a COT initiating UE of FIG. 17) that generates a COT (which may be, for example, a shared COT) may share the COT it has acquired with a counterpart terminal (e.g., a responding UE). For example, a terminal (e.g., a COT initiating UE) that generates / acquires a COT (which may be, for example, a shared COT) may transfer the acquired (e.g., shared) COT to a counterpart terminal (e.g., a responding UE) via an SCI or MAC CE or PC5-RRC message. For example, when transmitting a COT (e.g., shared) obtained through SCI, the obtained (e.g., shared) COT can be transmitted to a destination terminal (e.g., a responding UE) for a unicast link (e.g., a pair of L1 Source ID and L1 Destination ID), and the obtained (e.g., shared) COT can be transmitted to a groupcast / broadcast destination terminal (e.g., a groupcast / broadcast L1 Destination ID) (e.g., a responding UE).For example, a terminal (e.g., a COT initiating UE) may transmit the acquired (e.g., shared) COT to a destination terminal (e.g., a pair of L1 / L2 source ID and L1 / L2 destination ID) for a unicast link when transmitting the acquired (e.g., shared) COT via a MAC CE (e.g., (SL) COT Information MAC CE), and may transmit the acquired (e.g., shared) COT to a groupcast / broadcast destination terminal (e.g., a groupcast / broadcast L1 / L2 destination ID) (e.g., a responding UE). For example, a terminal (e.g., a COT-receiving terminal (e.g., a COT-responding UE)) that has received a COT (e.g., a COT-initiating UE) from a terminal that has generated a COT (e.g., a COT-initiating UE) within the shared COT may 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 may transmit (SL) data to be transmitted within the shared COT. For example, Type 2C LBT: it may transmit (SL) data immediately without sensing (for a certain period of time).) operation after the transmission of the terminal that generated the COT (e.g., the COT-initiating UE) within the shared COT is completed.For example, the shared COT information that a COT generating UE (e.g., a COT initiating UE) transmits to a COT receiving UE (e.g., a responding UE) may include information such as a shared COT interval, a shared COT start offset, and an SL-CAPC value to be used by the COT receiving UE (e.g., the responding UE). As illustrated in FIG. 17, a COT initiating UE may generate and share a COT, and a COT receiving UE (e.g., a responding UE) may receive the shared COT and perform short LBT (e.g., type 2 series LBT: instead of random backoff-based LBT, sensing is performed only for a short period of time and (SL) data transmission is performed immediately when the channel is idle) within the COT to transmit (SL) data.

[0234] For example, instead of transmitting a shared COT to a COT responding UE (e.g., a responding UE), a UE can generate a COT for sidelink data transmission in an unlicensed band itself and perform type 2 LBT within the generated COT interval to transmit sidelink data. For example, if a receiving UE (e.g., a responding UE) is a UE performing (SL) DRX operation, if a transmitting UE (e.g., a COT initiating UE) generates and secures a COT itself (e.g., an interval in which type 2 LBT can be performed), only an interval belonging to the (SL) DRX active time of the receiving UE (e.g., a interval in which PSCCH / PSSCH is monitored for data reception by the transmitting UE) can be considered as a COT generation interval. For example, since the COT interval that a transmitting terminal (e.g., a UE initiating a COT) generates and secures falls within the (SL) DR active time of its own receiving terminal (e.g., a UE responding), if it transmits sidelink data in the interval in which it generated the sidelink data, the receiving terminal (e.g., a UE responding) can properly receive the sidelink data that it transmits.

[0235] For example, when a transmitting terminal (e.g., a COT initiating UE) directly generates a COT and uses it to perform type 2 LBT, the transmitting terminal may transmit the COT it generated to a receiving terminal (via PC5 RRC message or MAC CE or SCI) so that the receiving terminal (e.g., a responding UE) may consider the COT period it transmitted as the (SL) DRX active time and perform an (SL) DRX active time operation (e.g., an operation of monitoring PSCCH / PSSCH for data reception by the transmitting terminal). For example, when a transmitting terminal (e.g., a terminal that supports (SL) DRX operation when it acts as a receiving terminal) directly generates a COT and performs (SL) DATA transmission based on type 2 LBT in the generated COT, the transmitting terminal may perform (SL) DRX operation by considering the COT section it generated as (SL) DRX active time.

[0236] For example, a COT responding UE (e.g., a terminal that supports (SL) DRX operation when acting as a receiving terminal) (e.g., the responding UE) that receives a shared COT from a COT initiating UE may consider the shared COT period as its (SL) DRX active time and receive a signal or message transmitted by the COT initiating UE during the (SL) DRX active time.

[0237] During the active time, additional devices corresponding to additional IDs can receive signals on the PSCCH and / or PSSCH. This optimized reception time ensures that additional devices corresponding to additional IDs consume resources and battery power only when receiving actual data transmissions, thereby improving overall energy efficiency and extending device life. By allowing additional devices corresponding to additional IDs to have specific active times to receive PSCCH and / or PSSCH, the system can enhance sidelink communication capabilities for vehicle-to-everything (V2X) communications, public safety messages, and other direct device-to-device interactions without network infrastructure.

[0238] FIG. 18 illustrates an embodiment of a timer associated with an active time, according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.

[0239] FIG. 19 illustrates an embodiment of a timer associated with an active time, according to an embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure.

[0240] Referring to FIGS. 18 and / or 19, COT sharing operation may be supported. For example, UE to UE COT sharing may be supported for (SL-)U(unlicensed) (NR) (in sidelink operation). For example, when performing PSSCH / PSCCH transmissions, the responding UE may utilize the COT shared by the COT initiating UE when the transmission(s) of the responding UE are intended for the COT initiating UE. For example, in unicast, the destination / source ID of the transmission of the responding UE may match the source / destination ID of the transmission of the initiator UE for the same unicast link. For example, in groupcast / broadcast, the destination ID of the transmission of the responding UE may need to match the destination ID of the initiator. For example, the COT initiating UE may transmit additional pairs of additional source / destination IDs among unicast, groupcast, or broadcast. For example, in this case (e.g., if the COT initiating UE transmits additional pairs of additional source / destination IDs), the responding UE may use the COT shared by the COT initiating UE if the destination / source (e.g., for unicast) or destination (e.g., for groupcast / broadcast) of the responding UE matches what is conveyed in the additional ID(s).For example, a UE's transmission in a shared COT may have a (SL-)CAPC value less than or equal to the (SL-)CAPC value indicated in the COT sharing information. For example, to satisfy the COT sharing requirement, the responding UE may perform an enhanced LCP procedure (e.g., as described in 3GPP TS 38.321). For example, when receiving multiple COT sharing indications from different COT initiators, it may be up to the UE implementation to decide which shared COT to use.

[0241] For example, in step S1810, UE A may transmit control information including an additional ID for COT sharing associated with UE C. For example, the control information may be transmitted on the PSCCH and / or the PSSCH. For example, in step S1910, UE A may transmit first control information to UE B. For example, the first control information may be transmitted on the PSCCH. For example, in step S1920, UE A may transmit second information to UE B including an additional ID for COT sharing associated with UE C. For example, the second control information may be transmitted on the PSSCH. For example, the first terminal may transmit an SCI to the second terminal on the PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In the present disclosure, the SCI transmitted on the PSCCH may be referred to as a 1st SCI, a first SCI, a 1st-stage SCI, or a 1st-stage SCI format, and the SCI transmitted on the PSSCH may be referred to as a 2nd SCI, a second SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0242] For example, the SCI transmitted on the PSCCH may be a 1st-stage SCI, which may carry (sidelink) scheduling information. For example, SCI format 1-A may be used to schedule the PSSCH. For example, SCI format 1-A may be used to schedule 2nd-stage SCI on the PSSCH.

[0243] For example, the SCI carried on the PSSCH may be a 2nd-stage SCI, which may carry (sidelink) scheduling information. For example, the SCI format 2-A may include a source ID. For example, the SCI format 2-A may include a destination ID. For example, the SCI format 2-A may include a cast type indicator. For example, if the cast type indicator field indicates a value of '00', the cast type may be broadcast. For example, if the cast type indicator 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 cast type indicator field indicates a value of '10', the cast type may be unicast. For example, if the cast type indicator field indicates a value of '11', the cast type may be groupcast when the HARQ-ACK information contains only NACK.

[0244] 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 a 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 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.

[0245] For example, in step S1820, UE C may initiate a timer associated with an active time. For example, in step S1930, UE C may initiate a timer associated with an active time. For example, the timer associated with the active time may be a (sidelink) onduration timer, a (sidelink) inactivity timer, and / or a (sidelink) retransmission timer. For example, if terminal C (e.g., responding UE C) is a terminal performing (sidelink) DRX operation, when terminal C (e.g., responding UE C) receives shared COT information from terminal A (e.g., COT initiating UE A) and determines that its source layer-1 ID is included in the additional ID field, the terminal may not start the (sidelink) DRX inactivity timer and the (sidelink) DRX retransmission timer or the (sidelink) DRX HARQ RTT timer (e.g., or may start the (sidelink) DRX inactivity timer and the (sidelink) DRX retransmission timer or the (sidelink) DRX HARQ RTT timer).For example, a timer related to the active time may be a (sidelink) DRX onduration timer, a (sidelink) DRX inactivity timer, and / or a (sidelink) DRX retransmission timer. For example, the (sidelink) DRX onduration timer may be a period during which a UE performing a (sidelink) DRX operation must basically operate as an active time for receiving a PSCCH / PSSCH of a counterpart UE. For example, the (sidelink) DRX inactivity timer may be a period that extends a (sidelink) DRX onduration period during which a UE performing a (sidelink) DRX operation must basically operate as an active time for receiving a PSCCH / PSSCH of a counterpart UE. For example, the (sidelink) DRX onduration timer can be extended by the period of the (sidelink) DRX inactivity timer. For example, when the UE receives a PSCCH (1st SCI and 2nd SCI) for a new TB from the counterpart UE or a new packet (new PSSCH transmission), the UE can start the (sidelink) DRX inactivity timer and extend the (sidelink) DRX onduration timer.For example, a (sidelink) DRX retransmission timer may be a period during which a UE performing a (sidelink) DRX operation operates as an active time to receive a retransmitted packet (e.g., PSSCH assignment) transmitted by a counterpart UE. For example, during the (sidelink) DRX retransmission timer period, the UE may monitor the reception of a retransmitted sidelink packet (e.g., or PSSCH assignment) transmitted by a counterpart UE.

[0246] For example, sidelink may support (SL) DRX for unicast, groupcast, and broadcast. For example, onduration, inactivity timer, retransmission timer, and / or cycle may be defined (for SL) to determine (SL) active time for (SL) DRX. For example, during (SL) active time, the UE may perform SCI monitoring for data reception (e.g., 2nd stage SCI on PSCCH and / or PSSCH). For example, during (SL) inactive time, the UE may omit monitoring of SCI for data reception. For example, the (SL) active time of the RX UE may include the time that any of the applicable (SL) onduration timer(s), (SL) inactivity timer(s), or (SL) retransmission timer(s) (e.g., for unicast, groupcast, or broadcast) is running.

[0247] For example, the TX UE may maintain a set of timers corresponding to the (SL) DRX timers in the RX UE(s) for each pair of source / destination L2 IDs for unicast or destination L2 IDs for groupcast / broadcast. For example, when data is available for transmission to one or more RX UE(s) configured with (SL) DRX, the TX UE may select a resource considering the active time of the RX UE(s).

[0248] For example, the UE can determine from SIB12 whether the gNB supports (SL) DRX or not.

[0249] For example, there may be a (SL) channel access procedure in a shared channel occupancy. For example, when a UE initiates a channel occupancy using a channel access procedure on a channel(s) to transmit (SL) transmission(s) including PSCCH / PSSCH(s), the UE may provide channel occupancy sharing information in the (SL) control information including at least layer 1 source and destination IDs, a corresponding channel access priority class (e.g., CAPC), a remaining channel occupancy duration, and frequency domain information about the applicable RB set(s) of the channel occupancy. For example, the channel occupancy sharing information may also include additional IDs and an associated cast type. For example, the additional IDs may include a pair of layer 1 source and destination IDs for every cast type, where the source ID may be set to the source ID of the UE initiating channel occupancy for unicast and may be set to a reserved bit for groupcast and broadcast.

[0250] For example, for a case where a UE transmits (SL) transmission(s) in a shared channel occupancy initiated by another UE, the channel access priority class (e.g., CAPC) value corresponding to the (SL) transmission(s) may be equal to the maximum of the channel access priority class (e.g., CAPC) values ​​provided by the channel access priority class (e.g., CAPC) in the channel occupancy sharing information.

[0251] For example, when a UE initiates a channel occupancy to transmit (SL) transmission(s) within an RB set(s) and provides information sharing the channel occupancy with a unicast PSCCH / PSSCH transmission within the RB set(s), another UE may transmit unicast PSCCH / PSSCH transmission(s) sharing the initiated channel occupancy within the RB set(s), if the destination and source IDs in the corresponding (SL) control information match the source and destination IDs in the unicast PSCCH / PSSCH transmission conveying the channel occupancy information, respectively, or if the destination and source IDs in the corresponding (SL) control information match an additional pair of source and destination IDs, and an associated cast type, and if the channel occupancy If the COT sharing cast type provided by the sharing information and corresponding to it indicates a value of '10' for the unicast cast type, then there is a match.For example, another UE may transmit groupcast or broadcast PSCCH / PSSCH transmissions sharing the disclosed channel occupancy within the RB set(s), if the destination ID in the corresponding (SL) control information matches an additional destination ID and an associated cast type, and if the corresponding COT sharing cast type provided by the channel occupancy sharing information indicates a value of '01' or '00' for the groupcast or broadcast cast type.

[0252] For example, when a UE initiates a channel occupancy to transmit (SL) transmission(s) within an RB set(s) and provides channel occupancy sharing information with a groupcast or broadcast PSCCH / PSSCH transmission within the RB set(s), another UE may transmit groupcast or broadcast PSCCH / PSSCH transmission(s) sharing the initiated channel occupancy within the RB set(s), if the destination IDs in the corresponding (SL) control information match a destination ID in the groupcast or broadcast PSCCH / PSSCH transmission conveying the channel occupancy information, or if the destination and source IDs in the corresponding (SL) control information are additional destination IDs and an associated cast type and if the COT is provided by the channel occupancy sharing information. If the sharing cast type matches a value of '01' or '00' for a group cast or broadcast cast type, respectively.For example, another UE may transmit unicast PSCCH / PSSCH transmissions sharing the above-initiated channel occupancy within the RB set(s), if the destination and source IDs in the corresponding (SL) control information match a pair of additional destination and source IDs, and an associated cast type, provided by the channel occupancy sharing information, if the corresponding COT sharing cast type indicates a value of '10' for the unicast cast type.

[0253] 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., 2-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., 2-stage SCIs) to receive the PSSCH from the first terminal. In the present disclosure, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0254] For example, when terminal A (e.g., COT initiating UE A) shares a COT (e.g., a shared COT) with terminal B (e.g., a COT responding UE B) (e.g., a responding UE B), the ID (e.g., an additional ID) (e.g., an additional ID: a source layer-1 ID or a source layer-2 ID of another terminal) of another terminal (e.g., terminal C (e.g., responding UE C)) (e.g., a terminal other than terminal B (e.g., a COT responding UE B): for example, a terminal that has established a unicast configuration with terminal A (e.g., a COT initiating UE A) or a terminal that has the same groupcast service or broadcast service as terminal A (e.g., a COT initiating UE A)) is shared It can be transmitted including COT. For example, the shared COT can be transmitted via 2nd SCI or MAC CE or PC5 RRC message. For example, when UE A (e.g., COT initiating UE A) transmits the shared COT to UE B (e.g., COT responding UE B) via 2nd SCI (e.g., PSSCH), UE A (e.g., COT initiating UE A) can also transmit (sidelink) data (e.g., data-related PSSCH) to UE B (e.g., COT responding UE B).For example, if UE A (e.g., initiating a COT) includes an additional ID (e.g., UE C (e.g., responding UE C)) in the shared COT that it transmits to UE B (e.g., responding UE B), UE C (e.g., responding UE C) may not transmit (sidelink) data (e.g., data-related PSSCH) corresponding to the additional ID to UE C (e.g., responding UE C) (e.g., UE A (e.g., initiating a COT) may transmit only the shared COT that includes the additional ID to UE C (e.g., responding UE C) via PSSCH (e.g., 2nd SCI)).

[0255] For example, when terminal C (e.g., responding UE C) receives a shared COT (e.g., data) transmitted by terminal A (e.g., initiating UE A) and verifies that its source layer-1 ID is included in the shared COT, the terminal may perform the following actions (e.g., if the shared COT information is transmitted via MAC CE or PC5 RRC message, terminal C (e.g., responding UE C) may check the Layer-2 ID to determine whether the shared COT information is the shared COT information that it should receive or not). For example, if terminal C (e.g., responding UE C) is a terminal performing (sidelink) DRX operation, terminal C (e.g., responding UE C) may start a (sidelink) DRX inactivity timer and a (sidelink) DRX retransmission timer or a (sidelink) DRX HARQ RTT timer when it receives shared COT information from terminal A (e.g., COT initiating UE A) and confirms that its source layer-1 ID is included in the additional ID field.For example, if terminal C (e.g., responding UE C) is a terminal performing a (sidelink) DRX operation, terminal C (e.g., responding UE C) may not start a (sidelink) DRX inactivity timer and a (sidelink) DRX retransmission timer or a (sidelink) DRX HARQ RTT timer when it receives shared COT information from terminal A (e.g., initiating UE A) and confirms that its source layer-1 ID is included in the additional ID field (e.g., terminal C (e.g., responding UE C) knows that terminal A (e.g., initiating UE A) will not transmit (sidelink) data in the shared COT section to terminal C (e.g., The responding UE C may not need to extend its active time by triggering the (sidelink) DRX inactivity timer and the (sidelink) DRX retransmission timer.For example, if terminal C (e.g., responding UE C) is a terminal performing (sidelink) DRX operation, when terminal C (e.g., responding UE C) receives shared COT information from terminal A (e.g., COT initiating UE A) and confirms that its source layer-1 ID is included in the additional ID field, it may be left to the terminal implementation whether to start or not the (sidelink) DRX inactivity timer and (sidelink) DRX retransmission timer or (sidelink) DRX HARQ RTT timer. For example, the (sidelink) inactivity timer and / or the (sidelink) retransmission timer may be timers associated with an active time. For example, the (sidelink) DRX inactivity timer may be a period that extends a (sidelink) DRX onduration period, which is a period during which a UE performing a (sidelink) DRX operation must basically operate as an active time for receiving a PSCCH / PSSCH of a counterpart UE. For example, the (sidelink) DRX onduration timer may be extended by the amount of the (sidelink) DRX inactivity timer period.For example, when a UE receives a PSCCH (1st SCI and 2nd SCI) for a new TB from a counterpart UE or a new packet (new PSSCH transmission), the UE may start a (sidelink) DRX inactivity timer to extend the (sidelink) DRX onduration timer. For example, the (sidelink) DRX retransmission timer may be a period during which a UE performing a (sidelink) DRX operation operates as an active time to receive a retransmitted packet (e.g., PSSCH assignment) transmitted by the counterpart UE. For example, during the (sidelink) DRX retransmission timer period, the UE may monitor reception of retransmitted sidelink packets (e.g., or PSSCH assignments) transmitted by the counterpart UE.

[0256] During the active time, additional devices corresponding to additional IDs can receive signals on the PSCCH and / or PSSCH. This optimized reception time ensures that additional devices corresponding to additional IDs consume resources and battery power only when receiving actual data transmissions, thereby improving overall energy efficiency and extending device life. By allowing additional devices corresponding to additional IDs to have specific active times to receive PSCCH and / or PSSCH, the system can enhance sidelink communication capabilities for vehicle-to-everything (V2X) communications, public safety messages, and other direct device-to-device interactions without network infrastructure. By starting the active time of additional devices corresponding to additional IDs in accordance with their reception capabilities, the network can better coordinate information distribution and scheduling. This promotes more organized and efficient network utilization, enabling smooth operation in congested or highly dynamic environments and an improved user experience. By coordinating the start of the active time of additional devices corresponding to additional IDs to match specific channel occupancy (COT) requirements, this approach minimizes overlapping signal transmissions and reduces the potential for interference between devices. This results in a clean signal path and high data integrity, which can be essential for maintaining robust communication links in critical applications.

[0257] For example, if terminal C (e.g., responding UE C) is a terminal performing (sidelink) DRX operation, terminal C (e.g., responding UE C) receives shared COT information from terminal A (e.g., COT initiating UE A) and confirms that its source layer-1 ID or source layer-2 ID is included in the additional ID field, then terminal C can maintain the active time from the time of receiving the shared COT (e.g., 2nd SCI, MAC CE, or PC5 RRC) until an offset time. For example, the offset value can be set to the terminal in advance by the base station or can be preset (e.g., pre-configuration). For example, the offset value can be configured per logical channel group, or per logical channel, or per (sidelink) priority, or per PFI (e.g., PC5 QoS Flow Identifier), or per PQI (e.g., PC5 5QI), or per QoS flow, or per (sidelink) CAPC priority. For example, the offset value can be configured (e.g., implicitly) by the UE to be greater than or equal to a minimum processing time required for the UE C (e.g., the responding UE C) to decode a 2nd SCI, MAC CE, or PC5 RRC message (e.g., PSSCH) containing shared COT information.For example, UE C (e.g., responding UE C) may know that UE A (e.g., initiating UE A) will not transmit (sidelink) data to it during the shared COT interval, but may transmit (sidelink) data to it before the shared COT starts, so it may need to operate in DRX active time and monitor the PSCCH / PSSCH transmitted by UE A (e.g., initiating UE).

[0258] For example, when UE C (e.g., responding UE C) receives shared COT information from UE A (e.g., initiating UE A) and determines that its source layer-1 ID or source layer-2 ID is included in the additional ID field, it may not operate in DRX active time during the COT duration of the shared COT after an offset time from the time of receiving the shared COT (e.g., 2nd SCI, MAC CE, or PC5 RRC) (e.g., it may not monitor PSCCH / PSSCH of UE A (e.g., initiating UE A) during the COT duration). For example, when UE C (e.g., responding UE C) receives shared COT information from UE A (e.g., initiating UE A) and confirms that its source layer-1 ID or source layer-2 ID is included in the additional ID field, UE C may operate in DRX active time during the COT duration of the shared COT after an offset time from the time of receiving the shared COT (e.g., 2nd SCI, MAC CE, or PC5 RRC) (e.g., UE C may perform PSCCH / PSSCH monitoring operation of UE A (e.g., UE A initiating COT) during the COT duration).

[0259] For example, the Uu DRX timer mentioned in the present disclosure below can be used for the following purposes:

[0260] - DRX HARQ RTT Timer (SL) (e.g., drx-HARQ-RTT-TimerSL): A period during which a Tx UE (e.g., a UE supporting Uu DRX operation) performing (sidelink) communication based on (sidelink) resource allocation mode 1 does not monitor PDCCH (e.g., or DCI) for (sidelink) mode 1 resource allocation from a base station.

[0261] - DRX retransmission timer (SL) (e.g., drx-RetransmissionTimerSL): A period during which a Tx UE (e.g., a UE supporting Uu DRX operation) performing (sidelink) communication based on (sidelink) resource allocation mode 1 monitors PDCCH (e.g., or DCI) for (sidelink) mode 1 resource allocation from a base station.

[0262] For example, the (sidelink) DRX timer mentioned in the present disclosure can be used for the following purposes:

[0263] - (Sidelink) DRX onduration timer: (Sidelink) The period during which a UE performing DRX operation must basically operate as an active time to receive PSCCH / PSSCH from the other UE.

[0264] - (Sidelink) DRX inactivity timer: A period for extending the (sidelink) DRX onduration period, which is a period during which a UE performing (sidelink) DRX operation must basically operate as an active time in order to receive PSCCH / PSSCH of the counterpart UE. For example, the (sidelink) DRX onduration timer may be extended by the period of the (sidelink) DRX inactivity timer. For example, when the UE receives a PSCCH (1st SCI and 2nd SCI) for a new TB from the counterpart UE or a new packet (new PSSCH transmission), the UE may start the (sidelink) DRX inactivity timer and extend the (sidelink) DRX onduration timer.

[0265] - (Sidelink) DRX HARQ RTT timer: A period during which a UE performing (sidelink) DRX operation operates in sleep mode until it receives a retransmission packet (e.g., PSSCH assignment) transmitted by a counterpart UE. For example, if a UE starts a (sidelink) DRX HARQ RTT timer, the UE may determine that the counterpart UE will not transmit a sidelink retransmission packet to it until the (sidelink) DRX HARQ RTT timer expires, and may operate in sleep mode during the timer (e.g., or may not monitor a sidelink channel / signal transmitted by a Tx UE).

[0266] - (Sidelink) DRX retransmission timer: A period during which a UE performing (sidelink) DRX operation operates as an active time to receive a retransmitted packet (e.g., PSSCH assignment) transmitted by a counterpart UE. For example, during the (sidelink) DRX retransmission timer period, the UE can monitor the reception of a retransmitted sidelink packet (e.g., or PSSCH assignment) transmitted by a counterpart UE.

[0267] For example, in the present disclosure, the names of the timers (e.g., (sidelink) DRX onduration timer, (sidelink) DRX inactivity timer, (sidelink) DRX HARQ RTT timer, (sidelink) DRX retransmission timer, etc.) are exemplary, and a timer that performs the same / similar function based on the contents described in each timer can be considered as the same / similar timer regardless of its name.

[0268] The operation of the present disclosure can be applied to all (sidelink) unicast / groupcast / broadcast operations.

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

[0270] In the present disclosure, multi-carrier can be extended to be interpreted as carrier aggregation (CA).

[0271] In the present disclosure, sidelink multi-carrier can be extended and interpreted as sidelink carrier aggregation (CA). In the present disclosure, sidelink carrier aggregation (CA) can be extended and interpreted as sidelink multi-carrier.

[0272] The (sidelink) resource pool (e.g., or (sidelink) HARQ entity) exemplified in the present disclosure may be interpreted as a sidelink resource pool (e.g., or (sidelink) HARQ entity) for a specific sidelink carrier.

[0273] In order to ensure HARQ feedback enabled MAC PDU transmission in (sidelink) multi-carrier operation, the base station may expect the terminal to configure PSFCH resources in an exceptional pool (e.g., a normal TX pool or a normal RX pool) on at least one (sidelink) carrier / (SL) BWP / (SL) HARQ entity among multiple (sidelink) carriers / (SL) BWP / (SL) HARQ entities to which the same unicast service or the same source layer-2 ID / destination layer-2 ID pair (e.g., or the same groupcast / broadcast service or the same destination layer-2 ID) are mapped. The present disclosure is not limited thereto.

[0274] When a base station forms a unicast session, groupcast, or broadcast session that performs HARQ feedback enabled MAC PDU transmission, the base station may restrict the terminal to include at least one carrier that includes an exceptional pool (e.g., a normal TX pool or a normal RX pool) in which the PSFCH resource is set. The present disclosure is not limited thereto.

[0275] When a terminal forms a unicast session, groupcast, or broadcast session that performs HARQ feedback enabled MAC PDU transmission, it may be restricted to include at least one carrier that includes an exceptional pool (e.g., a normal TX pool or a normal RX pool) in which PSFCH resources are configured. The present disclosure is not limited thereto.

[0276] In the present disclosure, the CBR threshold(s) associated with (sidelink) carrier(s) / (SL) BWP(s) / (SL) HARQ entities can be set per priority or per QoS profile (e.g., PDB, reliability) or per (SL) Radio Bearer or per logical channel.

[0277] In the present disclosure, a (sidelink) carrier can be extended to be interpreted as a (sidelink) BWP or a (sidelink) HARQ entity.

[0278] In the present disclosure, a (sidelink) carrier, a (sidelink) BWP, a (SL) resource pool, or a (sidelink) HARQ entity may be substituted for each other. For example, a (sidelink) carrier, a (sidelink) BWP, a (SL) resource pool, or a (sidelink) HARQ entity may be applied as substitutes for each other.

[0279] In an embodiment of the present disclosure, a unicast service may be interpreted as a pair of a source layer-2 ID and a destination layer-2 ID (Source Layer-2 ID and Destination Layer-2 ID pair).

[0280] In embodiments of the present disclosure, the groupcast service may be interpreted as a Groupcast Destination Layer-2 ID.

[0281] In embodiments of the present disclosure, a broadcast service may be interpreted as a Broadcast Destination Layer-2 ID.

[0282] In embodiments of the present disclosure, “carrier” may be replaced with “band” or “resource block set of a specific carrier” or “resource pool set of a specific carrier” or “channel”.

[0283] In an embodiment of the present disclosure, the DCR (direct communication request) message and / or the DCA (direct communication accept) message may be interpreted as being replaced with a PC5-S (sidelink) DCR message and / or a PC5-S (sidelink) DCA message.

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

[0285] For example, whether (some) of the proposed schemes / rules of the present disclosure are applied and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set depending on whether LBT succeeds / fails, LBT-related energy detection levels, sidelink channels (PSCCH / PSSCH, PSFCH, SL-SSB (or S-SSB)), whether MCSt (Multi-Consecutive Slot Transmission) is applied, whether multi-PSFCH occasions are applied, resource order / location for setting MCSt, whether multiple starting points are set within one slot, whether the 1st starting point (or 2nd starting point) is applied, etc.

[0286] Whether (some) of the proposed methods / rules of the present disclosure are applied and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set according to whether LBT is successful / failure, LBT-related energy detection level, sidelink channel (PSCCH / PSSCH, PSFCH, SL-SSB), whether MCSt (multi-consecutive slot transmission) is applied, whether multi-PSFCH (multi-PSFCH) occasion is applied, resource order / location constituting MCSt, whether multiple starting points are set within one slot, whether 1st starting point (or 2nd starting point) is applied, etc.

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

[0288] 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. In case of transmitting (and / or HARQ feedback disabled MAC PDU), whether to set PUCCH-based (SL) HARQ feedback reporting operation, in case of (non)performing (or resource reselection-based) pre-emption (and / or re-evaluation), (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,For 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)performed (or supported), a (SL) mode type (resource allocation mode 1, resource allocation mode 2), (non)periodic resource reservation performed, 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), it can be configured specifically (and / or independently and / or differently).

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

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

[0291] Referring to FIG. 20, in step S2010, the first device may transmit, to the second device, first control information for scheduling a physical shared channel and second control information on the physical control channel. In step S2020, the first device may transmit, to the second device, second control information including sharing information on channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device, on the physical shared channel. For example, a timer associated with an active time of the third device may be started based on the transmission of the second control information including sharing information on channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0292] For example, the timer associated with the activity time of the third device may be an inactivity timer of the third device.

[0293] For example, the timer associated with the active time of the third device may be a retransmission timer of the third device.

[0294] For example, the timer associated with the active time of the third device may be a hybrid automatic repeat request (HARQ) retransmission timer of the third device.

[0295] For example, the shared information for the channel occupancy may include a cast type of an additional ID for COT sharing associated with the third device.

[0296] For example, based on the cast type of the additional ID for COT sharing associated with the third device including information about unicast, a unicast reception can be received from the third device.

[0297] For example, based on the cast type of the additional ID for COT sharing related to the third device including information about the group cast, the group cast reception can be received from the third device.

[0298] For example, a broadcast reception can be received from the third device based on the cast type of the additional ID for COT sharing associated with the third device including information about the broadcast.

[0299] For example, an additional ID for COT sharing associated with the third device may be associated with a layer 1 ID of the third device.

[0300] For example, the layer 1 ID of the third device may include the layer 1 source ID of the third device.

[0301] For example, shared information about channel occupancy including additional ID for COT sharing associated with the third device may be transmitted to the third device.

[0302] For example, the first control information may be a first sidelink control information (SCI). For example, the second control information may be a second SCI. For example, the physical control channel may be a physical sidelink control channel (PSCCH). For example, the physical shared channel may be a physical sidelink shared channel (PSSCH). For example, the active time may be related to a sidelink.

[0303] For example, the active time may relate to a time for monitoring to receive at least one of the PSCCH or PSSCH.

[0304] 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 control the transceiver (106) to transmit, to the second device, first control information for scheduling a physical shared channel and second control information on the physical control channel. Then, the processor (102) of the first device (100) can control the transceiver (106) to transmit, to the second device, second control information including sharing information on channel occupancy, including an additional identity (ID) for sharing data and a COT (channel occupancy time) associated with a third device, on the physical shared channel. For example, a timer associated with an active time of the third device can be started based on the transmission of the second control information including sharing information on channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0305] 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: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information regarding channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be initiated based on the transmission of the second control information including sharing information regarding channel occupancy, including the additional ID for sharing data and a COT associated with the third device.

[0306] 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: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be initiated based on the transmission of the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0307] 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: transmit, to a second device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and transmit, to the second device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be initiated based on the transmission of the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

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

[0309] Referring to FIG. 21, in step S2110, the second device may receive, from the first device, first control information for scheduling a physical shared channel and second control information on a physical control channel. In step S2120, the second device may receive, from the first device, second control information on the physical shared channel, including sharing information on channel occupancy, including an additional identity (ID) for sharing data and a COT (channel occupancy time) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information on channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0310] For example, the timer associated with the activity time of the third device may be an inactivity timer of the third device.

[0311] For example, the timer associated with the active time of the third device may be a retransmission timer of the third device.

[0312] For example, the timer associated with the active time of the third device may be a hybrid automatic repeat request (HARQ) retransmission timer of the third device.

[0313] For example, the shared information for the channel occupancy may include a cast type of an additional ID for COT sharing associated with the third device.

[0314] For example, a unicast transmission can be transmitted from the third device based on the cast type of the additional ID for COT sharing associated with the third device including information about unicast.

[0315] For example, a groupcast transmission can be transmitted from the third device based on the cast type of the additional ID for COT sharing associated with the third device including information about the groupcast.

[0316] For example, a broadcast transmission may be transmitted from the third device based on the cast type of the additional ID for COT sharing associated with the third device including information about the broadcast.

[0317] For example, an additional ID for COT sharing associated with the third device may be associated with a layer 1 ID of the third device.

[0318] For example, the layer 1 ID of the third device may include the layer 1 source ID of the third device.

[0319] For example, shared information about channel occupancy including additional ID for COT sharing associated with the third device may be transmitted to the third device.

[0320] For example, the first control information may be a first sidelink control information (SCI). For example, the second control information may be a second SCI. For example, the physical control channel may be a physical sidelink control channel (PSCCH). For example, the physical shared channel may be a physical sidelink shared channel (PSSCH). For example, the active time may be related to a sidelink.

[0321] For example, the active time may relate to a time for monitoring to receive at least one of the PSCCH or PSSCH.

[0322] 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 control the transceiver (206) to receive, from the first device, first control information for scheduling a physical shared channel and second control information on the physical control channel. Then, the processor (202) of the second device (200) can control the transceiver (206) to receive, from the first device, second control information including sharing information on channel occupancy, including an additional identity (ID) for sharing data and a COT (channel occupancy time) associated with a third device, on the physical shared channel. For example, a timer associated with an active time of the third device can be started based on receiving the second control information including sharing information on channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

[0323] 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 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: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information regarding channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be initiated based on receiving the second control information including sharing information regarding channel occupancy, including the additional ID for sharing data and a COT associated with the third device.

[0324] 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: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information on a channel occupancy including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be initiated based on receiving the second control information including sharing information on a channel occupancy including an additional ID for sharing data and a COT associated with the third device.

[0325] 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: receive, from a first device, first control information on a physical control channel for scheduling a physical shared channel and second control information; and receive, from the first device, second control information on the physical shared channel, the second control information including sharing information about channel occupancy, including an additional identity (ID) for sharing data and a channel occupancy time (COT) associated with a third device. For example, a timer associated with an active time of the third device may be started based on receiving the second control information including sharing information about channel occupancy, including an additional ID for sharing data and a COT associated with the third device.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0362] 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. A method performed by a first device in a wireless communication system, A step of transmitting, to a second device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and A step of transmitting, to the second device, the second control information including sharing information about channel occupancy including an additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel; A method wherein a timer associated with the active time of the third device is started based on the transmission of the second control information including shared information about channel occupancy including additional ID for COT sharing related to the data and the third device.

2. In paragraph 1, A method wherein the timer associated with the activity time of the third device is an inactivity timer of the third device.

3. In paragraph 1, A method wherein the timer associated with the activity time of the third device is a retransmission timer of the third device.

4. In paragraph 3, A method wherein the timer associated with the active time of the third device is a hybrid automatic repeat request (HARQ) retransmission timer of the third device.

5. In paragraph 1, A method wherein the shared information for the above channel occupancy includes a cast type of an additional ID for COT sharing associated with the third device.

6. In paragraph 5, A method in which a unicast reception is received from the third device based on the cast type of the additional ID for COT sharing related to the third device including information about unicast.

7. In paragraph 5, A method in which groupcast reception is received from the third device based on the cast type of the additional ID for COT sharing related to the third device including information about groupcast.

8. In paragraph 5, A method in which a broadcast reception is received from the third device based on the cast type of the additional ID for COT sharing related to the third device including information about the broadcast.

9. In paragraph 1, A method wherein an additional ID for COT sharing associated with the third device is associated with a layer 1 ID of the third device.

10. In paragraph 9, A method wherein the layer 1 ID of the third device includes the layer 1 source ID of the third device.

11. In paragraph 1, A method in which shared information about channel occupancy, including an additional ID for COT sharing related to the third device, is transmitted to the third device.

12. In paragraph 1, The above first control information is the first SCI (sidelink control information), The above second control information is the second SCI, The above physical control channel is a physical sidelink control channel (PSCCH), The above physical shared channel is a physical sidelink shared channel (PSSCH), and The above active time is related to the side link, method.

13. In paragraph 12, A method wherein the above active time relates to a time for monitoring to receive at least one of the PSCCH or PSSCH.

14. In a first device configured to perform wireless communication, 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: To cause the second device to transmit first control information for scheduling a physical shared channel and second control information on a physical control channel; and To the second device, transmit the second control information including sharing information about channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A first device, wherein a timer associated with the active time of the third device is started based on the transmission of the second control information including shared information about channel occupancy including additional ID for COT sharing related to the data and the third device.

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: To cause the second device to transmit first control information for scheduling a physical shared channel and second control information on a physical control channel; and To the second device, transmit the second control information including sharing information about channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A processing device, wherein a timer associated with the active time of the third device is started based on the transmission of the second control information including shared information about channel occupancy including additional ID for COT sharing related to the data and the third device.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: To cause the second device to transmit first control information for scheduling a physical shared channel and second control information on a physical control channel; and To the second device, transmit the second control information including sharing information about channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A non-transitory computer-readable storage medium, wherein a timer associated with the active time of the third device is started based on the transmission of the second control information including shared information about channel occupancy including an additional ID for COT sharing associated with the data and the third device.

17. In a method performed by a second device in a wireless communication system, A step of receiving, from a first device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and A step of receiving, from the first device, the second control information including sharing information for channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel; A method wherein a timer associated with the active time of the third device is started based on receiving the second control information including shared information about channel occupancy including additional ID for COT sharing associated with the data and the third device.

18. In a second device configured to perform wireless communication, 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: Receive, from a first device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and Receive, from the first device, the second control information including sharing information for channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A second device, wherein a timer associated with the active time of the third device is started based on receiving the second control information including shared information about channel occupancy including additional ID for COT sharing related to the data and the third device.

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: Receive, from a first device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and Receive, from the first device, the second control information including sharing information for channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A processing device, wherein a timer associated with the active time of the third device is started based on receiving the second control information including shared information about channel occupancy including additional ID for COT sharing related to the data and the third device.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the second device to: Receive, from a first device, first control information for scheduling a physical shared channel and second control information on a physical control channel; and Receive, from the first device, the second control information including sharing information for channel occupancy including additional identity for sharing data and channel occupancy time (COT) with a third device on the physical shared channel, A non-transitory computer-readable storage medium, wherein a timer associated with the active time of the third device is started based on receiving the second control information including shared information about channel occupancy including additional ID for COT sharing associated with the data and the third device.

Citation Information

Patent Citations

  • Timer-based discontinuous reception for sidelink communications

    US20220272789A1

  • Method and apparatus for listen before talk for sidelink transmission in a wireless communication system

    US20230064680A1

  • Channel occupancy time (COT) sharing for sidelink

    WO2021061880A1

  • Method and apparatus for selecting resource on basis of partial sensing under SL DRX operation in nr v2x

    WO2023287203A1