Terminal operation method and device for IUC-information report in SL-U

Abstract

A method for a first device to perform wireless communication and a device supporting the method are provided. The method may comprise the steps of: acquiring a configuration related to inter-UE coordination (IUC) information reporting; initiating an IUC report timer based on the IUC information report being triggered; performing a listen before talk (LBT); and stopping the IUC report timer based on (i) generation of an IUC information medium access control (MAC) control element (CE) and based on (ii) success of the LBT.

Description

Technical Field

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

[0002] A sidelink (SL) refers to a communication method in which a direct link is configured between user equipments (UEs), and voice or data is directly exchanged between the UEs without passing through a base station (BS). Considering SL as a solution to the burden on the BS caused by the rapid increase in data traffic. Vehicle-to-everything (V2X) refers to a communication technology that exchanges information with other vehicles, pedestrians, objects equipped with infrastructure, etc. via wired / wireless communication. V2X can be classified into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication can be provided via a PC5 interface and / or a Uu interface.

[0003] In addition, since a wider range of communication devices requires a greater communication capacity, the demand for enhanced mobile broadband communication compared to existing radio access technologies (RAT) is on the rise. Therefore, services and user equipments that are sensitive to reliability and latency have been discussed. In addition, next-generation radio access technologies based on enhanced mobile broadband communication, massive machine type communication (MTC), ultra-reliable low-latency communication (URLLC), etc. can be referred to as new radio access technologies (RAT) or new radio (NR). In this document, NR can also support vehicle-to-everything (V2X) communication. Summary of the Invention

[0004] Technical Solution

[0005] In one embodiment, a method for a first device to perform wireless communication is provided. The method may include the following steps: obtaining a configuration related to an inter-UE coordination (IUC) information report; initiating an IUC report timer based on the triggering of the IUC information report; performing listen-before-talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information media access control (MAC) control element (CE) and (ii) the success of the LBT.

[0006] In one embodiment, a first device configured to perform wireless communication is provided. The first device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations, the operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT.

[0007] In one embodiment, a processing device configured to control a first device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations, the operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT.

[0008] In one embodiment, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, when executed, cause a first device to perform operations, the operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 2 Shows an electromagnetic spectrum based on an embodiment of the present disclosure.

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

[0012] Figure 4Shows a radio protocol architecture according to an embodiment of the present disclosure.

[0013] Figure 5 Shows the structure of an NR radio frame according to an embodiment of the present disclosure.

[0014] Figure 6 Shows the slot structure of an NR frame according to an embodiment of the present disclosure.

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

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

[0017] Figure 9 Shows three broadcast types according to an embodiment of the present disclosure.

[0018] Figure 10 Shows an interleaved RB based on an embodiment of the present disclosure.

[0019] Figure 11 Shows an example of a wireless communication system supporting an unlicensed band based on an embodiment of the present disclosure.

[0020] Figure 12 Shows a method of occupying resources in an unlicensed band based on an embodiment of the present disclosure.

[0021] Figure 13 Shows a case where an unlicensed band includes multiple LBT-SBs based on an embodiment of the present disclosure.

[0022] Figure 14 Shows a CAP operation performed by a base station to transmit a downlink signal through an unlicensed band based on an embodiment of the present disclosure.

[0023] Figure 15 Shows a type 1 CAP operation performed by a UE to transmit an uplink signal based on an embodiment of the present disclosure.

[0024] Figure 16 Shows a channel access process based on an embodiment of the present disclosure.

[0025] Figure 17 Shows an embodiment of an IUC information MAC CE report in an unlicensed band as proposed in the present disclosure.

[0026] Figure 18Shows an embodiment of the IUC information MAC CE report in the unlicensed band as proposed in the present disclosure.

[0027] Figure 19 Shows an embodiment of the IUC information MAC CE report in the unlicensed band as proposed in the present disclosure.

[0028] Figure 20 Shows an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operation as proposed in the present disclosure.

[0029] Figure 21 Shows an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operation as proposed in the present disclosure.

[0030] Figure 22 Shows an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operation as proposed in the present disclosure.

[0031] Figure 23 Shows an embodiment of the SL CSI report MAC CE in the unlicensed band as proposed in the present disclosure.

[0032] Figure 24 Shows an embodiment of the SL CSI report MAC CE in the unlicensed band as proposed in the present disclosure.

[0033] Figure 25 Shows an embodiment of the SL CSI report MAC CE in the unlicensed band as proposed in the present disclosure.

[0034] Figure 26 Shows a method for a first device to perform wireless communication based on an embodiment of the present disclosure.

[0035] Figure 27 Shows a method for a second device to perform wireless communication based on an embodiment of the present disclosure.

[0036] Figure 28 Shows a communication system 1 based on an embodiment of the present disclosure.

[0037] Figure 29 Shows a wireless device based on an embodiment of the present disclosure.

[0038] Figure 30 Shows a signal processing circuit for transmitting signals based on an embodiment of the present disclosure.

[0039] Figure 31Another example of a wireless device according to an embodiment of the present disclosure is shown.

[0040] Figure 32 A handheld device according to an embodiment of the present disclosure is shown.

[0041] Figure 33 A vehicle or autonomous vehicle according to an embodiment of the present disclosure is shown. Detailed embodiments

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

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

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

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

[0046] Furthermore, parentheses used in the present disclosure may mean "for example". Specifically, when indicated as "control information (PDCCH)", this may mean presenting "PDCCH" as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be presented as an example of "control information". Specifically, when indicated as "control information (i.e., PDCCH)", this may also mean presenting "PDCCH" as an example of "control information".

[0047] In the following description, "when, if, or in the case of" may be replaced by "based on".

[0048] The technical features described separately in one of the drawings of the present disclosure may be implemented separately or may be implemented simultaneously.

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

[0050] The techniques described below may be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented using radio technologies such as universal terrestrial radio access (UTRA) or CDMA-2000. TDMA may be implemented using radio technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented using radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), etc. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility for IEEE 802.16e-based systems. UTRA is part of the universal mobile telecommunications system (UMTS). The 3rd Generation Partnership Project (3GPP) long term evolution (LTE) is part of the evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in the downlink and SC-FDMA in the uplink. Long Term Evolution-Advanced (LTE-A) is an evolution of LTE.

[0051] 5G NR is a follow-on technology to LTE-A corresponding to a new and novel mobile communication system with characteristics such as high performance, low latency, high availability, etc. 5G NR may use resources of all available spectrums including low frequency bands below 1 GHz, intermediate frequency bands from 1 GHz to 10 GHz, and high frequencies (millimeter waves) above 24 GHz.

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

[0053] [Table 1]

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

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

[0056] Figure 1 A communication structure that can be provided in a 6G system based on an embodiment of the present disclosure is shown. Figure 1 Embodiments of can be combined with various embodiments of the present disclosure.

[0057] It is expected that the 6G system will have 50 times higher simultaneous radio connectivity than the 5G radio system. URLLC (a key feature of 5G) will become a more dominant technology in 6G communication, which provides an end-to-end latency of less than 1 ms. The 6G system will have better volumetric spectral efficiency compared to the more commonly used area spectral efficiency. The 6G system will be able to provide very long battery life and advanced battery technologies for energy harvesting, so that in the 6G system, mobile devices will not need to be charged separately. New network features in 6G can include the following.

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

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

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

[0061] - Ubiquitous super 3D connectivity: Access to network and core network functions from drones and very low Earth orbit satellites will enable ubiquitous super 3D connectivity in 6G.

[0062] Based on the above new network characteristics of 6G, some common requirements may include.

[0063] - Small cell networks: The concept of small cell networks has been introduced in cellular systems to improve the received signal quality due to increased processing throughput, energy efficiency, and spectral efficiency. Thus, small cell networks are a fundamental feature for 5G and beyond 5G (5GB) communication systems. Therefore, 6G communication systems will also adopt the characteristics of small cell networks.

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

[0065] - High-capacity backhaul: Backhaul connections are characterized by high-capacity backhaul networks to support a large amount of traffic. High-speed optical fibers and free space optical (FSO) systems can be possible solutions to this problem.

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

[0067] - Softwareization and virtualization: Softwareization and virtualization are two important features essential for the design process in 5GB networks to ensure flexibility, reconfigurability, and programmability. Additionally, billions of devices can be shared on a shared physical infrastructure.

[0068] The key enabling technologies for 6G systems are described below.

[0069] - Artificial Intelligence: The most important and latest technology to be introduced into the 6G system is AI. The 4G system does not involve AI. The 5G system will support partial or very limited AI. However, the 6G system will enable AI for full automation. In 6G, the advancement of machine learning will create more intelligent networks for real-time communication. The introduction of AI in telecommunications can simplify and improve real-time data transmission. AI can use many analyses to determine how to perform complex target tasks, which means that AI can improve efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be completed immediately by using AI. AI can also play an important role in M2M, machine-to-human, and human-to-machine communications. Additionally, AI can become fast communication in the brain-computer interface (BCI). The AI-based communication system can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

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

[0071] - Massive MIMO Technology (Massive MIMO)

[0072] - Holographic Beamforming (HBF, Holographic Beamforming)

[0073] - Optical Wireless Technology

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

[0075] - Non-Terrestrial Network (NTN)

[0076] - Quantum Communication

[0077] - Cell-Free Communication

[0078] - Integration of Wireless Information and Power Transmission

[0079] - Integration of Wireless Communication and Sensing

[0080] - Integrated Access and Backhaul Network

[0081] - Big Data Analytics

[0082] - Reconfigurable Intelligent Surface (Reconfigurable Intelligent Surface)

[0083] - Metaverse

[0084] - Blockchain

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

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

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

[0088] Figure 3 The structure of an NR system based on an embodiment of the present disclosure is shown. Figure 3 Embodiments of can be combined with various embodiments of the present disclosure.

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

[0090] Figure 3 Embodiments of illustrate only the case including only gNBs. The BS20s may be interconnected via the Xn interface. The BS20s may be interconnected via the fifth-generation (5G) core network (5GC) and the NG interface. More specifically, the BS20 may be connected to the access and mobility management function (AMF) 30 via the NG-C interface and may be connected to the user plane function (UPF) 30 via the NG-U interface.

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

[0092] Figure 4 Shows a radio protocol architecture according to an embodiment of the present disclosure. Figure 4 Embodiments of can be combined with various embodiments of the present disclosure. Specifically, Figure 4 (a) in shows a radio protocol stack for the user plane of Uu communication, and Figure 4 (b) in shows a radio protocol stack for the control plane of Uu communication. Figure 4 (c) in shows a radio protocol stack for the user plane of SL communication, and Figure 4 (d) in shows a radio protocol stack for the control plane of SL communication.

[0093] Referring to Figure 4 , the physical layer provides an information transfer service to the upper layer through physical channels. The physical layer is connected to the medium access control (MAC) layer, which is the upper layer of the physical layer, through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how data is transmitted through the radio interface and what characteristics of the data are transmitted.

[0094] Data is transferred through physical channels between different physical layers (i.e., the PHY layer of the transmitter and the PHY layer of the receiver). The physical channel can be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and the physical channel uses time and frequency as radio resources.

[0095] The MAC layer provides a service to the radio link control (RLC) layer via a logical channel, which is the upper layer of the MAC layer. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides a data transmission service through logical channels.

[0096] The RLC layer performs concatenation, segmentation, and reassembly of radio link control service data units (RLC SDUs). To ensure different quality of service (QoS) required by radio bearers (RBs), the RLC layer provides three types of operation modes, namely, transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). AM RLC provides error correction via automatic repeat request (ARQ).

[0097] The radio resource control (RRC) layer is defined only in the control plane. The RRC layer is used to control the logical channels, transport channels, and physical channels associated with the configuration, reconfiguration, and release of RBs. An RB is a logical path for data transfer between the UE and the network provided by the first layer (i.e., the physical layer or PHY layer) and the second layer (i.e., the MAC layer, RLC layer, packet data convergence protocol (PDCP) layer, and service data adaptation protocol (SDAP) layer).

[0098] The functions of the packet data convergence protocol (PDCP) in the user plane include the transmission of user data, header compression, and encryption. The functions of the packet data convergence protocol (PDCP) in the control plane include the transmission of control plane data and encryption / integrity protection.

[0099] The service data adaptation protocol (SDAP) layer is defined only in the user plane. The SDAP layer performs the mapping between quality of service (QoS) flows and data radio bearers (DRBs) and the QoS flow ID (QFI) marking in both DL packets and UL packets.

[0100] The configuration of an RB refers to the process of specifying radio protocol layer and channel attributes to provide a specific service and determining the corresponding detailed parameters and operation methods. An RB can then be classified into two types, namely, signaling radio bearer (SRB) and data radio bearer (DRB). An SRB is used as a path for sending RRC messages in the control plane, and a DRB is used as a path for sending user data in the user plane.

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

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

[0103] Examples of logical channels that belong to the higher layer of the transport channel and are mapped to the transport channel can include the broadcast control channel (BCCH), the paging control channel (PCCH), the common control channel (CCCH), the multicast control channel (MCCH), the multicast traffic channel (MTCH), etc.

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

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

[0106] In the case of using normal CP, each time slot can include 14 symbols. In the case of using extended CP, each time slot can include 12 symbols. Herein, a symbol can include an OFDM symbol (or CP-OFDM symbol) and a single-carrier FDMA (SC-FDMA) symbol (or discrete Fourier transform spread OFDM (DFT-s-OFDM) symbol).

[0107] Table 2 shown below represents the number of symbols per time slot (N slot symb ), the number of time slots per frame (N frame,μ slot ), and the number of time slots per sub-frame (N subframe,μ slot ) based on the SCS configuration (u) in the case of using normal CP or extended CP.

[0108] [Table 2]

[0109]

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

[0111] In NR, multiple parameter sets or SCSs can be supported to support various 5G services. For example, when the SCS is 15 kHz, a wide range of traditional cellular bands can be supported, and when the SCS is 30 kHz / 60 kHz, dense urban areas, lower latency, and wider carrier bandwidth can be supported. When the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz can be used to overcome phase noise.

[0112] NR bands can be defined as two different types of frequency ranges. The two different types of frequency ranges can be FR1 and FR2. The values of the frequency ranges can change (or vary), for example, the two different types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean "the range below 6 GHz", and FR2 can mean "the range above 6 GHz", and can also be referred to as millimeter wave (mmW).

[0113] [Table 3]

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

[0115] As described above, the values of the frequency ranges in the NR system can change (or vary). For example, as shown in Table 4 below, FR1 can include a bandwidth in the range of 410 MHz to 7125 MHz. More specifically, FR1 can include bands at 6 GHz (or 5850, 5900, 5925 MHz, etc.) and higher. For example, the bands at 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 can include unlicensed bands. The unlicensed bands can be used for various purposes, for example, the unlicensed bands are used for vehicle-specific communication (e.g., autonomous driving).

[0116] [Table 4]

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

[0118] Figure 6 The structure of a slot of an NR frame according to an embodiment of the present disclosure is shown. Figure 6The embodiments thereof may be combined with various embodiments of the present disclosure.

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

[0120] A carrier may include up to N BWPs (e.g., 5 BWPs). Data communication may be performed via an active BWP. Each element may be referred to as a resource element (RE) in a resource grid, and one complex symbol may be mapped to each element.

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

[0122] A BWP may be a continuous set of physical resource blocks (PRBs) within a given parameter set. The PRBs may be selected from a continuous subset of common resource blocks (CRBs) for a given parameter set on a given carrier.

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

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

[0125] Figure 7 An example of a BWP according to an embodiment of the present disclosure is shown. Figure 7 The embodiments of can be combined with various embodiments of the present disclosure. Assume that in Figure 7 the embodiment of, the number of BWPs is 3.

[0126] Referring to Figure 7, a Common Resource Block (CRB) can be a carrier resource block numbered from one end of a carrier frequency band to the other end. Additionally, a PRB can be a resource block numbered within each BWP. Point A can indicate a common reference point of the resource block grid.

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

[0128] In the following, V2X or SL communication will be described.

[0129] A Sidelink Synchronization Signal (SLSS) can include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS) as SL-specific sequences. The PSSS can be referred to as the Sidelink Primary Synchronization Signal (S-PSS), and the SSSS can be referred to as the Sidelink Secondary Synchronization Signal (S-SSS). For example, an M sequence with a length of 127 can be used for the S-PSS, and a Gold sequence with a length of 127 can be used for the S-SSS. For example, a UE can use the S-PSS for initial signal detection and synchronization acquisition. For example, a UE can use the S-PSS and the S-SSS for detailed synchronization acquisition and for the detection of the synchronization signal ID.

[0130] The Physical Sidelink Broadcast Channel (PSBCH) can be a (broadcast) channel for transmitting default (system) information that a UE must first know before SL signal transmission / reception. For example, the default information can be information related to SLSS, duplex mode (DM), Time Division Duplex (TDD) uplink / downlink (UL / DL) configuration, information related to the resource pool, the type of application related to SLSS, subframe offset, broadcast information, etc. For example, to evaluate the PSBCH performance, in NR V2X, the payload size of the PSBCH can be 56 bits, including a 24-bit Cyclic Redundancy Check (CRC).

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

[0132] Figure 8 A process by which a UE performs V2X or SL communication based on a transmission mode according to an embodiment of the present disclosure is shown. Figure 8 Embodiments of may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be referred to as a mode or a resource allocation mode. Hereinafter, for ease of explanation, in LTE, the transmission mode may be referred to as the LTE transmission mode. In NR, the transmission mode may be referred to as the NR resource allocation mode.

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

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

[0135] Referring to Figure 8 (a) of, in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, the base station may schedule sidelink resources to be used by the UE for sidelink transmission. For example, in step S600, the base station may send information related to the sidelink resources and / or information related to the UL resources to the first UE. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting sidelink HARQ feedback to the base station.

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

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

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

[0139] DCI format 3_0 is used to schedule NR PSCCH and NR PSSCH in a cell

[0140] The following information is sent by means of DCI format 3_0 having a CRC scrambled by SL-RNTI or SL-CS-RNTI:

[0141] - Resource pool index - ceiling(log 2I-th bit, where I is the number of resource pools for transmission configured by the higher layer parameter sl-TxPoolScheduling.

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

[0143] - HARQ process number - 4 bits

[0144] - New data indicator - 1 bit

[0145] - Lowest index ceiling for subchannel allocation to initial transmission - (log 2 (N SL subChannel )) bits

[0146] - SCI format 1 - A field: Frequency resource assignment, Time resource assignment

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

[0148] - PUCCH resource indicator - 3 bits

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

[0150] - Counter sidelink assignment index - 2 bits if the UE is configured with pdsch-HARQ-ACK-codebook = dynamic, 2 bits if the UE is configured with pdsch-HARQ-ACK-codebook = semi-static.

[0151] - Padding bits, if needed

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

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

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

[0155] SCI format 1-A is used for scheduling the second-level SCI and the PSSCH on the PSSCH.

[0156] The following information is sent by means of SCI format 1-A:

[0157] - Priority - 3 bits

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

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

[0160] - Resource reservation period - ceiling(log 2 N rsv_period ) bits, where if the higher layer parameter sl-MultiReserveResource is configured, N rsv_period is the number of entries in the higher layer parameter sl-ResourceReservePeriodList; otherwise, 0 bits

[0161] - DMRS mode - ceiling(log 2 N pattern ) bits, where N pattern is the number of DMRS modes configured by the higher layer parameter sl-PSSCH-DMRS-TimePatternList

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

[0163] - Beta_offset indicator - 2 bits provided by the higher layer parameter sl-BetaOffsets2ndSCI

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

[0165] - Modulation and coding scheme - 5 bits

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

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

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

[0169] [Table 5]

[0170] Value of the second-level SCI format field Second-level SCI format 00 SCI format 2-A 01 SCI format 2-B 10 Reserved 11 Reserved

[0171] [Table 6]

[0172] Value of the DMRS port number field Antenna port 0 1000 1 1000 and 1001

[0173] In the following, an example of SCI format 2-A will be described.

[0174] In HARQ operations, SCI format 2-A is used for PSSCH decoding when the HARQ-ACK information includes ACK or NACK, when the HARQ-ACK information only includes NACK, or when there is no feedback of HARQ-ACK information.

[0175] The following information is sent by means of SCI format 2-A:

[0176] - HARQ process number - 4 bits

[0177] - New data indicator - 1 bit

[0178] - Redundancy version - 2 bits

[0179] - Source ID - 8 bits

[0180] - Destination ID - 16 bits

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

[0182] - Broadcast type indicator - 2 bits as defined in Table 7

[0183] - CSI request - 1 bit

[0184] [Table 7]

[0185] Value of the broadcast type indicator Broadcast type 00 Broadcast 01 Multicast when the HARQ-ACK information includes ACK or NACK 10 Unicast 11 Multicast when the HARQ-ACK information only includes NACK

[0186] In the following, an example of SCI format 2-B will be described.

[0187] SCI format 2-B is used for the decoding of PSSCH, and HARQ operations are utilized when the HARQ-ACK information only includes NACK, or when there is no feedback of HARQ-ACK information.

[0188] The following information is sent by means of SCI format 2-B:

[0189] - HARQ process number - 4 bits

[0190] - New data indicator - 1 bit

[0191] - Redundancy version - 2 bits

[0192] - Source ID - 8 bits

[0193] - Destination ID - 16 bits

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

[0195] - Zone ID - 12 bits

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

[0197] Refer to Figure 8 In (a) or (b) of, in step S830, the first UE may receive the PSFCH. For example, the first UE and the second UE may determine the PSFCH resource, and the second UE uses the PSFCH resource to send HARQ feedback to the first UE.

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

[0199] Figure 9 Three broadcast types based on the embodiments of the present disclosure are shown. Figure 9 The embodiments of can be combined with various embodiments of the present disclosure. Specifically, Figure 9 In (a) of, broadcast-type SL communication is shown, Figure 9 In (b) of, unicast-type SL communication is shown, and Figure 9 In (c) of, multicast-type SL communication is shown. In the case of unicast-type SL communication, the UE may perform one-to-one communication for another UE. In the case of multicast-type SL transmission, the UE may perform SL communication for one or more UEs in the group to which the UE belongs. In various embodiments of the present disclosure, SL multicast communication may be replaced by SL multiple-cast communication, SL one-to-many communication, etc.

[0200] In the following, the Hybrid Automatic Repeat reQuest (HARQ) process will be described.

[0201] For example, SL HARQ feedback can be enabled for unicast. In this case, in non-Code Block Group (non-CBG) operation, if the receiving UE decodes the PSCCH targeted at the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may generate a HARQ-ACK. Additionally, the receiving UE may send the HARQ-ACK to the sending UE. Otherwise, if the receiving UE fails to successfully decode the transport block after decoding the PSCCH targeted at the receiving UE, the receiving UE may generate a HARQ-NACK. Additionally, the receiving UE may send the HARQ-NACK to the sending UE.

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

[0203] (1) Multicast Option 1: After the receiving UE decodes the PSCCH targeted at the receiving UE, if the receiving UE fails to decode the transport block associated with the PSCCH, the receiving UE may send a HARQ-NACK to the sending UE via the PSFCH. Otherwise, if the receiving UE decodes the PSCCH targeted at the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may not send a HARQ-ACK to the sending UE.

[0204] (2) Multicast Option 2: After the receiving UE decodes the PSCCH targeted at the receiving UE, if the receiving UE fails to decode the transport block associated with the PSCCH, the receiving UE may send a HARQ-NACK to the sending UE via the PSFCH. Additionally, if the receiving UE decodes the PSCCH targeted at the receiving UE and if the receiving UE successfully decodes the transport block associated with the PSCCH, the receiving UE may send a HARQ-ACK to the sending UE via the PSFCH.

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

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

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

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

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

[0210] (1) drx-HARQ-RTT-Timer-SL (per HARQ process): drx-HARQ-RTT-Timer-SL may be the minimum duration before the MAC entity expects a sidelink HARQ retransmission grant. drx-HARQ-RTT-Timer-SL may refer to the minimum time required to prepare the resources for SL mode 1 retransmission. That is, the resources for sidelink retransmission cannot be prepared before the drx-HARQ-RTT-Timer-SL timer. Therefore, the transmitting UE may reduce power consumption by transitioning to the sleep mode during the drx-HARQ-RTT-Timer-SL timer. Alternatively, the transmitting UE may not perform mode 1 DCI monitoring from the base station. If the drx-HARQ-RTT-Timer-SL timer expires, the transmitting UE may determine that the resources for SL retransmission can be prepared. Therefore, the transmitting UE may start the drx-RetransmissionTimer-SL timer and monitor whether it receives the resources for SL HARQ retransmission. Once the drx-HARQ-RTT-Timer-SL timer expires, the SL HARQ retransmission resources may or may not be received. Therefore, the transmitting UE may start the drx-RetransmissionTimer-SL timer, and the transmitting UE may monitor the mode 1 DCI from the base station to receive the resources for SL HARQ retransmission. For example, the drx-HARQ-RTT-Timer-SL timer may be the duration during which a transmitting UE (e.g., a UE supporting Uu DRX operation) performing sidelink communication based on sidelink resource allocation mode 1 does not perform PDCCH (or DCI) monitoring for sidelink mode 1 resource allocation from the base station.

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

[0212] For example, the SL DRX configuration can include at least one of the parameters / information described below.

[0213] (1) SL drx-onDurationTimer: The duration at the start of the SL DRX cycle

[0214] (2) SL drx-SlotOffset: The delay before starting the sl drx-onDurationTimer

[0215] (3) SL drx-InactivityTimer: The duration after a PSCCH opportunity indicating a new SL transmission for the MAC entity by the PSCCH.

[0216] (4) SL drx-RetransmissionTimer (per HARQ process or per sidelink process): The maximum duration until a retransmission is received

[0217] (5) SL drx-HARQ-RTT-Timer (per HARQ process or per sidelink process): The minimum duration before which the MAC entity expects PSSCH and PSCCH (sidelink control information) for SL HARQ retransmission.

[0218] (6) SL drx-LongCycleStartOffset: The long DRX cycle and drx-StartOffset, which define the subframe at which the long DRX cycle and the short DRX cycle start.

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

[0220] (8) SL drx-ShortCycleTimer (optional): The duration for which the UE shall follow the short DRX cycle

[0221] (9) SL drx-HARQ-RTT-Timer (per sidelink process): The minimum duration before which the MAC entity expects an assignment for HARQ retransmission.

[0222] (10) SL drx-StartOffset: The subframe at which the SL DRX cycle starts

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

[0224] The SL DRX timers described in this disclosure can be used for the following purposes.

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

[0226] (2) SL DRX Inactivity Timer: The duration that extends the SL DRX On Duration, which is the duration for which a UE performing SL DRX operation shall operate substantially in the active time to receive PSCCH / PSSCH from other UEs.

[0227] For example, the UE can extend the SL DRX On Duration Timer by the SL DRX Inactivity Timer duration. Additionally, if the UE receives a new packet (e.g., a new PSSCH transmission) from another UE, the UE can extend the SL DRX On Duration Timer by starting the SL DRX Inactivity Timer.

[0228] For example, the SL DRX inactivity timer can be used to extend the SL DRX on-duration, which is the duration during which a receiving UE performing SL DRX operations should operate substantially in the active time to receive PSCCH / PSSCH from other UEs. That is to say, the SL DRX on-duration timer can be extended by the SL DRX inactivity timer period. Additionally, if the receiving UE receives a new packet (e.g., a new PSSCH transmission) from another transmitting UE, the receiving UE can extend the SL DRX on-duration timer by starting the SL DRX inactivity timer.

[0229] (3) SL DRX HARQ RTT timer: The duration during which a UE performing SL DRX operations operates in the sleep mode until it receives a retransmitted packet (or PSSCH assignment) sent by another UE

[0230] For example, if a UE starts the SL DRX HARQ RTT timer, the UE can determine that another UE will not send a sidelink retransmitted packet to the UE until the SL DRX HARQ RTT timer expires, and the UE can operate in the sleep mode while the corresponding timer is running. For example, if a UE starts the SL DRX HARQ RTT timer, the UE can refrain from monitoring for sidelink retransmitted packets from other UEs until the SL DRX HARQ RTT timer expires. For example, if a receiving UE that has received PSCCH / PSSCH sent by a transmitting UE sends an SL HARQ NACK feedback, the receiving UE can start the SL DRX HARQ RTT timer. In this case, the receiving UE can determine that another transmitting UE will not send a sidelink retransmitted packet to the receiving UE until the SL DRX HARQ RTT timer expires, and the receiving UE can operate in the sleep mode while the corresponding timer is running.

[0231] (4) SL DRX retransmission timer: A timer started when the SL DRX HARQ RTT timer expires, and the duration during which a UE performing SL DRX operations operates in the active time to receive a retransmitted packet (or PSSCH assignment) sent by another UE.

[0232] For example, for the corresponding timer duration, the UE can receive or monitor for retransmitted sidelink packets (or PSSCH assignments) sent by other UEs. For example, while the SL DRX retransmission timer is running, the receiving UE can receive or monitor for retransmitted sidelink packets (or PSSCH assignments) sent by other transmitting UEs.

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

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

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

[0236] When SL DRX is for the operation of the receiving UE, the transmitting UE also needs to know the SL DRX operation state of the receiving UE (active or sleep mode, or at the start of the DRX on-duration / inactivity / HARQ RTT / retransmission timer, at the expiration of the DRX on-duration / inactivity / HARQ RTT / retransmission timer, etc.). For example, when allocating and transmitting resources, the transmitting UE should be able to determine whether the receiving UE is operating in the active mode or the sleep mode. Therefore, the transmitting UE can apply the same SL DRX configuration as the receiving UE to maintain the operation state of the same SL DRX timer as the receiving UE, etc.

[0237] The AS layer of a UE (receiving UE or transmitting UE) supporting SL DRX behavior can receive a Tx profile mapped for available sidelink services from a higher layer (e.g., the V2X layer). The Tx profile can include information differentiating whether the available sidelink service or the sidelink service of interest is the sidelink service for which SL DRX operation needs to be performed. Thus, when the AS layer of the UE receives available sidelink data (or sidelink service of interest) and the Tx profile from the upper layer, the UE can decide (or determine) whether it should or should not support SL DRX operation for the available sidelink data (or sidelink service of interest).

[0238] In addition, in the normal unlicensed spectrum (NR-U), a communication method between a UE and a base station in the unlicensed band is supported. Additionally, in Rel-18, a mechanism for supporting communication in the unlicensed band between sidelink UEs is planned to be supported.

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

[0240] Figure 10 An interleaved RB based on an embodiment of the present disclosure is shown. Figure 10 Embodiments can be combined with various embodiments of the present disclosure.

[0241] Referring to Figure 10 , multiple interleavings of RBs can be defined in the frequency domain. Interleaving m ∈ {0, 1, ···, M - 1} can include (common) RBs {m, M + m, 2M + m, 3M + m, ···}, where M represents the number of interleaved RBs given in Table 8.

[0242] [Table 8]

[0243] u M 0 10 1 5

[0244] A communication device (e.g., the devices, UEs, vehicles, drones, etc. proposed in various embodiments of the present disclosure) can use one or more interleaved RBs to transmit signals / channels.

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

[0246] In the present disclosure, Channel Occupancy (CO) may refer to the time-frequency resources obtained by a base station or a UE after successful LBT.

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

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

[0249] Figure 11 An example of a wireless communication system supporting an unlicensed band based on an embodiment of the present disclosure is shown. For example, Figure 11 it may include an unlicensed spectrum (NR-U) wireless communication system. Figure 11 Embodiments of may be combined with various embodiments of the present disclosure.

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

[0251] As Figure 11 shown in (a) of, when a base station and a UE transmit and receive signals on the LCC and UCC of carrier aggregation, the LCC and UCC may be respectively configured as a Primary CC (PCC) and a Secondary CC (SCC). As Figure 11 shown in (b) of, a base station and a UE may transmit and receive signals on one UCC or on multiple carrier-aggregated UCCs. In other words, a base station and a UE may transmit and receive signals only on the UCC without using any LCC. For independent operation, PRACH transmission, PUCCH transmission, PUSCH transmission, SRS transmission, etc. may be supported on a U cell.

[0252] In Figure 11 an embodiment of, a base station may be replaced by a UE. In this case, for example, PSCCH transmission, PSSCH transmission, PSFCH transmission, S-SSB transmission, etc. may be supported on a U cell.

[0253] Unless otherwise specified, the following definitions apply to the following terms used in the present disclosure.

[0254] - Channel: A carrier or a part of a carrier consisting of a continuous set of RBs that perform a channel access procedure in a shared spectrum.

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

[0256] - Channel Occupancy: The transmission of the base station / UE on the channel after the channel access procedure.

[0257] - Channel Occupancy Time (COT): The total time during which the base station / UE that shares the channel occupancy and any base station / UE can perform transmission on the channel after the base station / UE executes the channel access procedure. When determining COT, if the transmission gap is less than or equal to 25 us, the gap duration can be counted in COT. COT can be shared for transmission between the base station and the corresponding UE.

[0258] - DL Transmission Burst: A set of transmissions from the base station without any gap greater than 16 us. Transmissions from the base station separated by a gap greater than 16 us are considered separate DL transmission bursts. The base station can perform transmission after the gap without sensing channel availability within the DL transmission burst.

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

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

[0261] Figure 12 A method of occupying resources in an unlicensed frequency band according to an embodiment of the present disclosure is shown. Figure 12 Embodiments can be combined with various embodiments of the present disclosure.

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

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

[0264] [Table 9]

[0265]

[0266] Referring to Table 9, an LBT type or CAP for DL / UL / SL transmission can be defined. However, Table 9 is only an example, and new types or CAPs can be defined in a similar manner. For example, Type 1 (also referred to as Cat-4 LBT) can be a channel access procedure based on random backoff. For example, in the case of Cat-4, the contention window can change. For example, Type 2 can be performed in the case of COT sharing within the COT obtained by a base station (gNB) or a UE.

[0267] In the following, the LBT-subband (SB) (or set of RBs) will be described.

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

[0269] Figure 13 A case where multiple LBT-SBs are included in an unlicensed band based on an embodiment of the present disclosure is shown. Figure 13 Embodiments of may be combined with various embodiments of the present disclosure.

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

[0271] In the following, the channel access priority class (CAPC) will be described.

[0272] The CAPC of the MAC CE and radio bearer may be fixed or configured to operate in FR1:

[0273] - Fixed to the lowest priority for the padding buffer status report (BSR) and recommended bitrate MAC CE;

[0274] - Fixed to the highest priority for SRB0, SRB1, SRB3, and other MAC CE;

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

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

[0277] [Table 10]

[0278]

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

[0280] The base station can perform one of the following channel access procedures (e.g., CAP) for downlink signal transmission in the unlicensed band.

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

[0282] In Type 1 DL CAP, the length of the duration spanned by the sensed time slots sensed as idle before transmission can be random. Type 1 DL CAP can be applied to the following transmissions:

[0283] - Transmissions initiated by the base station include (i) a unicast PDSCH with user plane data or (ii) a unicast PDSCH with user plane data and a unicast PDCCH scheduling the user plane data, or

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

[0285] Figure 14 Shows the CAP operation performed by the base station based on an embodiment of the present disclosure to transmit a downlink signal through an unlicensed band. Figure 14 The embodiments can be combined with various embodiments of the present disclosure.

[0286] Referring to Figure 14 , the base station can sense whether the channel is idle for a sensed delay duration T d of the time slot duration. Then, if the counter N is zero, the base station can perform the transmission (S134). In this case, the base station can adjust the counter N by sensing the channel within an additional sensed time slot duration according to the following steps:

[0287] Step 1) (S120) The base station sets N to N init (N = N init ), where N init is a random number uniformly distributed between 0 and CW p . Then, proceed to Step 4.

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

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

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

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

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

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

[0294] [Table 11]

[0295]

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

[0297] The delay duration T dConfigured in the following order: Duration T f (16us)+m p Continuous sensing slot duration T sl (9us). T f Including the sensing slot duration T at the start of the 16us duration sl .

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

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

[0300] In type 2 DL CAP, the length of the duration spanned by the sensing slots sensed as idle before transmission can be determined. Type 2 DL CAP is classified as type 2A / 2B / 2C DL CAP.

[0301] Type 2A DL CAP can be applied to the following transmissions. In type 2A DL CAP, the base station can perform transmission immediately after the channel has been sensed as idle for at least the sensing duration T short_dl = 25us. Here, T short_dl Includes the duration T f (= 16us) and one sensing slot duration immediately following the duration T f , where the duration T f Includes the sensing slot at its start.

[0302] - Transmissions initiated by the base station, including (i) discovery bursts only or (ii) discovery bursts multiplexed with non-unicast information, or

[0303] - Transmissions by the base station after a 25us gap from the UE's transmission within the shared channel occupancy.

[0304] Type 2B DL CAP is applicable to transmissions performed by the base station after a gap of 16 μs from the transmission of the UE within the shared channel occupancy time. In Type 2B DL CAP, the base station can perform a transmission immediately after the channel is sensed idle within T f = 16 μs. T f includes a sensing time slot within 9 μs from the end of the duration. Type 2C DL CAP is applicable to transmissions performed by the base station after up to 16 μs from the transmission of the UE within the shared channel occupancy time. In Type 2C DL CAP, the base station does not perform channel sensing before performing a transmission.

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

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

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

[0308] In Type 1 UL CAP, the length of the duration spanned by the sensing time slot sensed idle before transmission is random. Type 1 UL CAP can be applied to the following transmissions.

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

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

[0311] - Transmissions related to the random access procedure (RAP)

[0312] Figure 15 shows a Type 1 CAP operation performed by the UE to transmit an uplink signal based on an embodiment of the present disclosure. Figure 15 The embodiments can be combined with various embodiments of the present disclosure.

[0313] Referring to Figure 15 , the UE can sense the channel at a delay duration T dWhether it is idle during the sensing time slot duration. Then, if the counter N is zero, the UE can perform a transmission (S234). In this case, the UE can adjust the counter N by sensing the channel during an additional sensing time slot duration according to the following steps:

[0314] Step 1) (S220) The UE sets N to N init (N = N init ), where N init is a random number uniformly distributed between 0 and CW p . Then, proceed to Step 4.

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

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

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

[0318] Step 5) (S260) The UE senses the channel until a busy sensing time slot is detected within an additional delay duration T d or all time slots of the additional delay duration T d are detected as idle.

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

[0320] Table 12 shows that m p , the minimum CW, the maximum CW, the maximum channel occupancy time (MCOT), and the allowed CW size vary according to the channel access priority class.

[0321] [Table 12]

[0322]

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

[0324] The delay duration T d is configured in the following order: the duration T f (16 us) + m p The continuous sensing time slot duration T sl (9 us).T f includes the sensing time slot duration T starting at the beginning of the 16 us duration sl .

[0325] Satisfies the following relationship: CW min,p <= CW p <= CW max,p .CW p Can be configured by CW p = CW min,p configured and updated (CW size update) based on the explicit / implicit reception response for the previous UL burst (e.g., PUSCH) before step 1. For example, CW p can be initialized to CW min,p . Alternatively, CW p can be increased to the next higher allowed value or remain unchanged.

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

[0327] In Type 2 UL CAP, the length of the duration spanned by the sensing time slot sensed as idle before transmission can be determined. Type 2 UL CAP is classified as Type 2A / 2B / 2C UL CAP. In Type 2A UL CAP, the UE can perform transmission immediately after the channel has been sensed as idle for at least the sensing duration T short_dl = 25 us. Here, T short_dl includes the duration T f (= 16 us) and one sensing time slot duration immediately following the duration T f . In Type 2A UL CAP, T f includes a sensing time slot at its start. In Type 2B UL CAP, the UE can perform transmission immediately after the channel has been sensed as idle within the sensing duration T f = 16 us. In Type 2B UL CAP, T f includes the sensing time slot within 9 us from the end of the duration. In Type 2C UL CAP, the UE does not perform channel sensing before performing transmission.

[0328] For example, according to NR-U operation based on Type 1 LBT, a UE having uplink data to transmit may select a CAPC for the 5QI to which the data is mapped, and the UE may perform NR-U operation by applying the parameters of the corresponding CAPC (e.g., minimum contention window size, maximum contention window size, m p etc.). For example, the UE may select a backoff counter (BC) after selecting a random value between 0 and CW (the minimum CW and the maximum CW mapped to the CAPC). In this case, for example, the BC may be a positive integer less than or equal to the random value. For example, if the UE detects that the channel is idle at time T d (T d = T f + m p * T sl ), the BC is decremented by 1. When the BC becomes zero, the UE may attempt to transmit data by occupying the channel. For example, if the UE detects a collision when it attempts to transmit data, it may increase the contention window size (CW size) mapped to the CAPC. Additionally, the UE may reselect a random value for the backoff count between 0 and CW, and reselect the random value with the increased CW. For example, if the UE successfully performs packet transmission, the contention window (CW size) may be initialized to the default value mapped to the initial CAPC. For example, T sl (= 9 microseconds) is a basic sensing unit or sensing time slot, and may include a measurement duration of at least 4 microseconds. For example, the first 9 microseconds of T f (= 16 microseconds) may be configured as T sl . For example, m p may be a constant mapped for each CAPC, and is used to calculate T d . For example, as the CAPC value decreases (or the priority increases), m p may be mapped to a smaller value.

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

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

[0331] For example, Type 2B can be LBT once every 16 microseconds. In this case, transmission can start immediately after sensing an idle period of 16 microseconds. That is, the UE can sense the channel within the COT for 16 microseconds, and if the channel is idle, the UE can attempt to send data by occupying the channel.

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

[0333] In the sidelink unlicensed band, the UE can perform channel access operations based on Listen Before Talk (LBT). Before the UE accesses a channel in the unlicensed band, the UE should check whether the channel to be accessed is idle (e.g., the state where the UE does not occupy the channel, the state where the UE can access the corresponding channel and send data) or busy (e.g., the state where the channel is occupied and data transmission / reception is being performed on the corresponding channel, and the UE attempting to access the channel cannot send data when the channel is busy). That is, the operation of the UE to check whether the channel is idle or busy can be referred to as Clear Channel Assessment (CCA), and the UE can check whether the channel is idle or busy within the CCA duration.

[0334] Figure 16 A channel access process according to an embodiment of the present disclosure is shown. Specifically, Figure 16 (a) of shows an example of a dynamic channel access process (Load-Based Equipment, LBE), and Figure 16 (b) of shows an example of a semi-static channel access process (Frame-Based Equipment, FBE). Figure 16 Embodiments of can be combined with various embodiments of the present disclosure.

[0335] Referring to Figure 16 In (a) of, if the channel is idle, the UE can compete with other UEs on the unlicensed band to immediately occupy the channel. Additionally, if the UE occupies the channel, the UE can send data.

[0336] Referring to Figure 16In (b) of this, the UE can perform contention with other UEs on the unlicensed frequency band at the last time within the synchronization frame boundary (or fixed frame period (FFP)) (e.g., a specific time before the start of the next FFP (or start time)). Additionally, if the UE occupies a channel within the fixed frame period (FFP), the UE can send data. The data transmission should be completed before the start of the next FFP.

[0337] Furthermore, when the UE receives an inter-UE coordination (IUC) request from the corresponding UE, the IUC information reporting process can be triggered and the IUC report timer can be initiated. If secondary link (SL) resources for a new transmission are allocated before the expiration of the initiated IUC report timer and the SL shared channel (SCH) resources can accommodate the IUC information media access control (MAC) control element (CE) and its sub-header, the UE can generate the IUC information MAC CE. If the UE generates the IUC information, it can determine that the IUC information MAC CE has been successfully sent to the corresponding UE that sent the IUC request and can stop the initiated IUC report timer. However, in the secondary link unlicensed spectrum (SL-U), since the UE should first perform listen-before-talk (LBT) to occupy the channel for SL transmission, even if the UE generates the IUC information MAC CE, if the LBT fails, it may not send the IUC information MAC CE to the corresponding UE that sent the IUC request.

[0338] In this disclosure, a method for operating to report the IUC information MAC CE in the unlicensed frequency band and an apparatus supporting the method are proposed.

[0339] 1. IUC-Request Transmission

[0340] The secondary link inter-UE coordination request (SL-IUC Req) transmission process is used to trigger the peer UE to send secondary link inter-UE coordination information, as specified in clause 8.1.4 of Technical Specification (TS) 38.214.

[0341] 2. IUC-Information Reporting

[0342] The secondary link inter-UE coordination information (SL-IUC Info) reporting process is used to provide inter-UE coordination information to the peer UE, as specified in clause 8.1.4 of TS 38.214.

[0343] Radio resource control (RRC) can configure the following parameters to control the SL-IUC information reporting process.

[0344] -sl-LatencyBoundIUC-Report (which can be maintained for each PC5-RRC connection)

[0345] The MAC entity can maintain a sl-IUC-ReportTimer for each pair of source layer-2 ID and destination layer-2 ID corresponding to a PC5-RRC connection. The sl-IUC-ReportTimer can be used for the SL-IUC information reporting UE to comply with the latency requirements for triggering UE signaling from IUC-information. The value of the sl-IUC-ReportTimer can be the same as the latency requirement of the SL-IUC information in the RRC-configured sl-LatencyBoundIUC-Report.

[0346] The MAC entity can perform the following for each pair of source layer-2 ID and destination layer-2 ID corresponding to an established upper-layer PC5-RRC connection:

[0347] 1> If the SL-IUC information report has been triggered by an SL-IUC request MAC CE (and / or SCI) and has not been cancelled:

[0348] 2> If the sl-IUC-ReportTimer for the triggered SL-IUC information report is not running:

[0349] 3> The sl-IUC-ReportTimer can be started.

[0350] 2> If the sl-IUC-ReportTimer for the triggered SL-IUC information report expires:

[0351] 3> The triggered SL-IUC information report can be cancelled.

[0352] 2> Otherwise, if the MAC entity has SL resources allocated for a new transmission and, due to logical channel prioritization, the SL-SCH resources can accommodate the SL-IUC information MAC CE and its sub-header:

[0353] 3> The multiplexing and assembly process can be indicated to generate the sidelink UE-to-UE coordination information MAC CE, as defined in clause 6.1.3.35;

[0354] 3> If LBT operation is supported for the active SL BWP or SLLBTFailureRecoveryConfig is configured for the active SL BWP:

[0355] 4> If an LBT success indication has been received from the lower layer:

[0356] 5>The sl-IUC-ReportTimer for the triggered SL-IUC information report can be stopped;

[0357] 5>The triggered SL-IUC information report can be cancelled.

[0358] 3>Otherwise:

[0359] 4>The sl-IUC-ReportTimer for the triggered SL-IUC information report can be stopped;

[0360] 4>The triggered SL-IUC information report can be cancelled.

[0361] 3.Another implementation of IUC-Information reporting

[0362] The sidelink UE-to-UE coordination information (SL-IUC Info) reporting procedure is used to provide UE-to-UE coordination information to the peer UE, as specified in clause 8.1.4 of TS 38.214.

[0363] Radio Resource Control (RRC) can configure the following parameters to control the SL-IUC information reporting procedure.

[0364] -sl-LatencyBoundIUC-Report (sl-LatencyBoundIUC-Report can be maintained for each PC5-RRC connection)

[0365] The MAC entity can maintain the sl-IUC-ReportTimer for each pair of source layer-2 ID and destination layer-2 ID corresponding to a PC5-RRC connection. The sl-IUC-ReportTimer can be used by the SL-IUC information reporting UE to comply with the latency requirement for the UE to signal from the IUC-information trigger. The value of the sl-IUC-ReportTimer can be the same as the latency requirement for the SL-IUC information in the sl-LatencyBoundIUC-Report configured by RRC.

[0366] The MAC entity can perform the following for each pair of source layer-2 ID and destination layer-2 ID corresponding to an established upper layer PC5-RRC connection:

[0367] 1>If the SL-IUC information report has been triggered by an SL-IUC request MAC CE (and / or SCI) and has not been cancelled:

[0368] 2>If the sl-IUC-ReportTimer for the triggered SL-IUC information report is not running:

[0369] 3> The sl-IUC-ReportTimer can be started.

[0370] 2> If the sl-IUC-ReportTimer for the triggered SL-IUC information report expires:

[0371] 3> The triggered SL-IUC information report can be cancelled.

[0372] 2> Otherwise, if the MAC entity has SL resources allocated for new transmissions and, due to logical channel prioritization, the SL-SCH resources can accommodate the SL-IUC information MAC CE and its sub-header:

[0373] 3> The multiplexing and assembly process can be indicated to generate the sidelink UE - to - UE coordination information MAC CE, as defined in clause 6.1.3.35;

[0374] 3> If sidelink LBT operation is supported for the active SL BWP or SLLBTFailureRecoveryConfig is configured for the active SL BWP:

[0375] 4> If a sidelink LBT failure indication has not been received from the lower layer:

[0376] 5> The sl-IUC-ReportTimer for the triggered SL-IUC information report can be stopped;

[0377] 5> The triggered SL-IUC information report can be cancelled.

[0378] 3> Otherwise (for example, a sidelink LBT failure indication has been received from the lower layer):

[0379] 4> The sl-IUC-ReportTimer for the triggered SL-IUC information report can not be stopped;

[0380] 4> The triggered SL-IUC information report can not be cancelled.

[0381] Figure 17 An embodiment of the IUC information MAC CE reporting in the license - free band as proposed in this disclosure is shown. Figure 17 The embodiments can be combined with various embodiments of this disclosure.

[0382] In Figure 17In , a UE that has been triggered by an IUC-request MAC CE to send an IUC-information MAC CE can stop the sl-IUC-ReportTimer only when LBT is successful, can cancel the triggered SL-IUC information report simultaneously (operation: cancel the triggered SL-IUC information report because it will send the SL-IUC information MAC CE), and can report the generated SL-IUC information MAC CE to the UE that sent the IUC-request MAC CE.

[0383] Figure 18 Illustrates an embodiment of IUC information MAC CE reporting in an unlicensed band as proposed in the present disclosure. Figure 18 The embodiments of can be combined with various embodiments of the present disclosure.

[0384] In Figure 18 In , a UE that has been triggered by an IUC-request MAC CE to send an IUC-information MAC CE can stop the sl-IUC-ReportTimer only when it does not receive an LBT failure indication from the PHY layer, can cancel the triggered SL-IUC information report simultaneously (operation: cancel the triggered SL-IUC information report because it will send the SL-IUC information MAC CE), and can report the generated SL-IUC information MAC CE to the UE that sent the IUC-request MAC CE.

[0385] Figure 19 Illustrates an embodiment of IUC information MAC CE reporting in an unlicensed band as proposed in the present disclosure. Figure 19 The embodiments of can be combined with various embodiments of the present disclosure.

[0386] In Figure 19 In , a UE that has been triggered by an IUC-request MAC CE to send an IUC-information MAC CE may not stop the sl-IUC-ReportTimer when it receives an LBT failure indication from the PHY layer. Additionally, for example, it may not cancel the triggered SL-IUC information report. That is, for example, since the triggered SL-IUC information MAC CE is not sent due to LBT failure, the triggered SL-IUC information report may not be canceled.

[0387] Furthermore, in the present disclosure, a method for the operation of a UE for PC5 RRC reconfiguration in an unlicensed band is proposed.

[0388] Proposal 1.

[0389] 1-1. Actions related to the transmission of RRCReconfigurationSidelink message

[0390] The UE can configure the content of the RRCReconfigurationSidelink message as follows:

[0391] 1> For each sidelink DRB to be released, according to Clause 5.8.9.1a.1.1, due to the configuration through sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or through the upper layer:

[0392] 2> The SLRB-PC5-ConfigIndex included in the slrb-ConfigToReleaseList corresponding to the sidelink DRB can be set;

[0393] 1> For each sidelink DRB to be established or modified, according to Clause 5.8.9.1a.2.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:

[0394] 2> The SLRB-Config included in the slrb-ConfigToAddModList can be set according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the sidelink DRB;

[0395] 1> The sl-MeasConfig can be set as follows:

[0396] 2> If the frequency used for NR sidelink communication is included in the sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within the RRCReconfiguration message or is included in sl-ConfigCommonNR within SIB12:

[0397] 3> If the UE is in RRC_CONNECTED:

[0398] 4> The sl-MeasConfig can be set according to the stored NR sidelink measurement configuration information for that destination;

[0399] 3> If the UE is in RRC_IDLE or RRC_INACTIVE:

[0400] 4> The sl-MeasConfig can be set according to the stored NR sidelink measurement configuration received from SIB12;

[0401] 2> Otherwise:

[0402] 3> The sl-MeasConfig can be set according to the sl-MeasPreconfig in SidelinkPreconfigNR;

[0403] 1> The sl-LatencyBoundIUC-Report can be set;

[0404] 1> If LBT operation is supported for the active SL BWP or SLLBTFailureRecoveryConfig is configured for the active SL BWP:

[0405] 2> If an LBT success indication has been received from the lower layer:

[0406] 3> The timer T400 for the destination can be started;

[0407] That is, in the present disclosure, the following operations of the UE are proposed, which enable the UE to perform an LBT process for transmitting the RRCReconfigurationSidelink message in the sidelink unlicensed band, and start the T400 timer only when the LBT process is successful (for example, if it does not receive an LBT failure indication or receives an LBT success indication from the lower layer (i.e., the PHY layer)). For example, if the UE performs an LBT process for transmitting the RRCReconfigurationSidelink message in the sidelink unlicensed band and the LBT process fails (for example, if it receives an LBT failure indication or does not receive an LBT success indication from the lower layer (i.e., the PHY layer)), it may not start the T400 timer.

[0408] 1> Otherwise:

[0409] 2> The timer T400 for the destination can be initiated;

[0410] 1> The sl-CSI-RS-Config can be set;

[0411] 1> Set the sl-LatencyBoundCSI-Report,

[0412] Note 1: How to set the parameters included in the sl-CSI-RS-Config and sl-LatencyBoundCSI-Report may depend on the UE implementation.

[0413] 1> The sl-DRX-ConfigUC-PC5 can be configured as follows:

[0414] 2> If the frequency used for NR sidelink communication is included in the sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within the RRCReconfiguration message or in sl-ConfigCommonNR within SIB12:

[0415] 3> If the UE is in RRC_CONNECTED and if the sl-ScheduledConfig is included in sl-ConfigDedicatedNR within the RRCReconfiguration:

[0416] 4> The sl-DRX-ConfigUC-PC5 can be configured according to the stored NR sidelink DRX configuration information for that destination.

[0417] Note 2: If the UE is in RRC_IDLE or RRC_INACTIVE or out of coverage, or is in RRC_CONNECTED and the sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within the RRCReconfiguration, the sl-DRX-ConfigUC-PC5 can be configured according to the UE implementation.

[0418] 1> For each PC5 relay RLC channel to be released due to the configuration of sl-ConfigDedicatedNR:

[0419] 2> The SL-RLC-ChannelID corresponding to the PC5 relay RLC channel in the sl-RLC-ChannelToReleaseListPC5 can be configured;

[0420] 1> For each PC5 relay RLC channel to be established or modified due to the reception of sl-ConfigDedicatedNR:

[0421] 2> The SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 can be configured according to the received sl-RLC-ChannelConfig corresponding to the PC5 relay RLC channel;

[0422] For example, the UE can submit the RRCReconfigurationSidelink message to the lower layer for transmission.

[0423] 1 - 2. The UE receives RRCReconfigurationSidelink

[0424] The UE may perform the following actions after receiving RRCReconfigurationSidelink:

[0425] 1> If RRCReconfigurationSidelink includes sl - ResetConfig:

[0426] 2> The sidelink reset configuration procedure specified in 5.8.9.1.10 may be performed;

[0427] 1> If RRCReconfigurationSidelink includes slrb - ConfigToReleaseList:

[0428] 2> For each SLRB - PC5 - ConfigIndex value included in slrb - ConfigToReleaseList that is part of the current UE sidelink configuration;

[0429] 3> According to Clause 5.8.9.1a.1, the sidelink DRB release procedure may be performed;

[0430] 1> If RRCReconfigurationSidelink includes slrb - ConfigToAddModList:

[0431] 2> For each slrb - PC5 - ConfigIndex value included in slrb - ConfigToAddModList that is not part of the current UE sidelink configuration:

[0432] 3> If sl - MappedQoS - FlowsToAddList is included:

[0433] 4> The SL - PQFI included in sl - MappedQoS - FlowsToAddList may be applied;

[0434] 3> According to Clause 5.8.9.1a.2, the sidelink DRB addition procedure may be performed;

[0435] 2> For each slrb - PC5 - ConfigIndex value included in slrb - ConfigToAddModList that is part of the current UE sidelink configuration:

[0436] 3> If sl-MappedQoS-FlowsToAddList is included:

[0437] 4> The SL-PQFIs included in sl-MappedQoS-FlowsToAddList can be added to the corresponding secondary link DRB;

[0438] 3> If sl-MappedQoS-FlowsToReleaseList is included:

[0439] 4> The SL-PQFIs included in sl-MappedQoS-FlowsToReleaseList can be removed from the corresponding secondary link DRB;

[0440] 3> If the secondary link DRB release conditions described in Clause 5.8.9.1a.1.1 are met:

[0441] 4> The secondary link DRB release procedure can be executed according to Clause 5.8.9.1a.1.2;

[0442] 3> Otherwise, if the secondary link DRB modification conditions described in Clause 5.8.9.1a.2.1 are met:

[0443] 4> The secondary link DRB release procedure can be executed according to Clause 5.8.9.1a.2.2;

[0444] 1> If the RRCReconfigurationSidelink message includes sl-MeasConfig:

[0445] 2> The secondary link measurement configuration procedure specified in 5.8.10 can be executed;

[0446] 1> If the RRCReconfigurationSidelink message includes sl-CSI-RS-Config:

[0447] 2> The secondary link CSI-RS configuration can be applied;

[0448] 1> If the RRCReconfigurationSidelink message includes sl-LatencyBoundCSI-Report:

[0449] 2> The configured secondary link CSI report latency bound can be applied;

[0450] 1> If RRCReconfigurationSidelink includes sl-RLC-ChannelToReleaseListPC5:

[0451] 2>For each SL-RLC-ChannelID value included in sl-RLC-ChannelToReleaseListPC5 that is part of the current UE sidelink configuration;

[0452] 3>The PC5 relay RLC channel release procedure can be performed according to Clause 5.8.9.7.1;

[0453] 1>If RRCReconfigurationSidelink includes sl-RLC-ChannelToAddModListPC5:

[0454] 2>For each sl-RLC-ChannelID-PC5 value included in sl-RLC-ChannelToAddModListPC5 that is not part of the current UE sidelink configuration:

[0455] 3>The sidelink RLC channel addition procedure can be performed according to Clause 5.8.9.7.2;

[0456] 2>For each sl-RLC-ChannelID-PC5 value included in sl-RLC-ChannelToAddModListPC5 that is part of the current UE sidelink configuration:

[0457] 3>The PC5 relay RLC channel modification procedure can be performed according to Clause 5.8.9.7.2;

[0458] 1>If the RRCReconfigurationSidelink message includes sl-DRX-ConfigUC-PC5, and

[0459] 1>If the UE accepts sl-DRX-ConfigUC-PC5:

[0460] 2>The lower layers can be configured to perform sidelink DRX operations according to sl-DRX-ConfigUC-PC5 for the associated destination as defined in TS 38.321;

[0461] 1>If the RRCReconfigurationSidelink message includes sl-LatencyBoundIUC-Report:

[0462] 2>The configured sidelink IUC reporting latency bound can be applied;

[0463] 1> If the UE fails to comply with the configuration (a part of it) included in RRCReconfigurationSidelink (i.e., sidelink RRC reconfiguration fails):

[0464] 2> It can continue to use the configuration used before receiving the RRCReconfigurationSidelink message;

[0465] 2> It can set the content of the RRCReconfigurationFailureSidelink message;

[0466] 3> It can submit the RRCReconfigurationFailureSidelink message to the lower layer for transmission;

[0467] 1> Otherwise:

[0468] 2> It can set the content of the RRCReconfigurationCompleteSidelink message;

[0469] 3> If the UE rejects the sidelink DRX configuration sl-DRX-ConfigUC-PC5 received from the peer UE:

[0470] 4> It can include sl-DRX-ConfigReject in the RRCReconfigurationCompleteSidelink message;

[0471] 3> It can submit the RRCReconfigurationCompleteSidelink message to the lower layer for transmission;

[0472] Note 1: When the same logical channel is configured with different RLC modes by another UE, the UE can handle this situation as a sidelink RRC reconfiguration failure.

[0473] Note 2: The UE can decide whether to indicate the rejection of the received sidelink DRX configuration to the peer UE.

[0474] The following Figures 20 to 22 represents an implementation manner of the RRCReconfigurationSidelink message transmission and T400 timer start operation in the license-free band proposed in this disclosure.

[0475] For example, as the following Figures 20 to 22, when the transmission of the RRCReconfigurationSidelink message is triggered, the UE can send the RCReconfigurationSidelink message and initiate the T400 timer only when LBT is successful (e.g., when an SL LBT success indication is received from the lower layer or when an SL LBT failure indication is not received from the lower layer). For example, if the transmission of the RRCReconfigurationSidelink message is triggered and LBT fails (e.g., when an SL LBT failure indication is not received from the lower layer), the UE may not initiate the T400 timer (since it is a situation where the RRCReconfigurationSidelink message cannot be sent, the T400 timer may not be initiated).

[0476] Figure 20 Illustrates an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operations as proposed in the present disclosure. Figure 20 The embodiments of can be combined with various embodiments of the present disclosure.

[0477] Figure 21 Illustrates an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operations as proposed in the present disclosure. Figure 21 The embodiments of can be combined with various embodiments of the present disclosure.

[0478] Figure 22 Illustrates an embodiment of the RRCReconfigurationSidelink message transmission and T400 timer initiation operations as proposed in the present disclosure. Figure 22 The embodiments of can be combined with various embodiments of the present disclosure.

[0479] Proposal 2.

[0480] 2-1. Actions related to the transmission of the RRCReconfigurationSidelink message

[0481] The UE can configure the content of the RRCReconfigurationSidelink message as follows:

[0482] 1> For each sidelink DRB to be released, according to Clause 5.8.9.1a.1.1, due to the configuration through sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, or through the upper layer:

[0483] 2> The SLRB-PC5-ConfigIndex included in the slrb-ConfigToReleaseList corresponding to the secondary link DRB can be set;

[0484] 1> For each secondary link DRB to be established or modified, according to Clause 5.8.9.1a.2.1, due to the reception of sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:

[0485] 2> The SLRB-Config included in the slrb-ConfigToAddModList can be set according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the secondary link DRB;

[0486] 1> The sl-MeasConfig can be set as follows:

[0487] 2> If the frequency used for NR secondary link communication is included in the sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within the RRCReconfiguration message or in sl-ConfigCommonNR within SIB12:

[0488] 3> If the UE is in RRC_CONNECTED:

[0489] 4> The sl-MeasConfig can be set according to the stored NR secondary link measurement configuration information for that destination;

[0490] 3> If the UE is in RRC_IDLE or RRC_INACTIVE:

[0491] 4> The sl-MeasConfig can be set according to the stored NR secondary link measurement configuration received from SIB12;

[0492] 2> Otherwise:

[0493] 3> The sl-MeasConfig can be set according to the sl-MeasPreconfig in SidelinkPreconfigNR;

[0494] 1> The sl-LatencyBoundIUC-Report can be set;

[0495] 1> If LBT operation is supported for the active SL BWP or SLLBTFailureRecoveryConfig is configured for the active SL BWP:

[0496] 2> If an LBT failure indication has been received from a lower layer:

[0497] 3> A timer T400 for the destination can be started;

[0498] That is, in the present disclosure, the following operation of the UE is proposed, which causes the UE to perform an LBT process for transmitting an RRCReconfigurationSidelink message in a sidelink grant-free band, and if the LBT process fails (for example, if it receives an LBT failure indication from a lower layer (i.e., the PHY layer)), start the T400 timer. For example, if the UE performs the next LBT process for transmitting an RRCReconfigurationSidelink message in a sidelink grant-free band and the LBT process is successful, then since the RRCReconfigurationSidelink message can be transmitted, the UE can initiate T400 in order to save the time required to perform the PC5 RRC reconfiguration process even if an SL LBT failure occurs. Additionally, for example, when the UE successfully performs the next LBT process and transmits the RRCReconfigurationSidelink message, it may not initiate the T400 timer.

[0499] For example, when the UE initiates the T400 timer and an SL LBT failure (e.g., a consistent LBT failure) occurs up to a threshold number of times before the T400 timer expires, it can stop the T400 timer and can declare an SL RLF (e.g., via the SL RLF of the PC5RRC reconfiguration process).

[0500] 1> Otherwise:

[0501] 2> A timer T400 for the destination can be initiated;

[0502] 1> sl-CSI-RS-Config can be set;

[0503] 1> Set sl-LatencyBoundCSI-Report,

[0504] Note 1: How to set the parameters included in sl-CSI-RS-Config and sl-LatencyBoundCSI-Report can depend on the UE implementation.

[0505] 1> The sl-DRX-ConfigUC-PC5 can be configured as follows:

[0506] 2> If the frequency used for NR sidelink communication is included in the sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within the RRCReconfiguration message or in sl-ConfigCommonNR within SIB12:

[0507] 3> If the UE is in RRC_CONNECTED and if the sl-ScheduledConfig is included in the sl-ConfigDedicatedNR within the RRCReconfiguration:

[0508] 4> The sl-DRX-ConfigUC-PC5 can be configured according to the stored NR sidelink DRX configuration information for that destination.

[0509] Note 2: If the UE is in RRC_IDLE or RRC_INACTIVE or out of coverage, or is in RRC_CONNECTED and the sl-UE-SelectedConfig is included in the sl-ConfigDedicatedNR within the RRCReconfiguration, the sl-DRX-ConfigUC-PC5 can be configured according to the UE implementation.

[0510] 1> For each PC5 relay RLC channel to be released due to the configuration of sl-ConfigDedicatedNR:

[0511] 2> The SL-RLC-ChannelID corresponding to the PC5 relay RLC channel in the sl-RLC-ChannelToReleaseListPC5 can be configured;

[0512] 1> For each PC5 relay RLC channel to be established or modified due to the reception of sl-ConfigDedicatedNR:

[0513] 2> The SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 can be configured according to the received sl-RLC-ChannelConfig corresponding to the PC5 relay RLC channel;

[0514] For example, the UE can submit the RRCReconfigurationSidelink message to the lower layer for transmission.

[0515] 2 - 2. UE receives RRCReconfigurationSidelink

[0516] The UE can perform the following actions after receiving RRCReconfigurationSidelink:

[0517] 1> If RRCReconfigurationSidelink includes sl - ResetConfig:

[0518] 2> The sidelink reset configuration procedure specified in 5.8.9.1.10 can be performed;

[0519] 1> If RRCReconfigurationSidelink includes slrb - ConfigToReleaseList:

[0520] 2> For each SLRB - PC5 - ConfigIndex value included in slrb - ConfigToReleaseList that is part of the current UE sidelink configuration;

[0521] 3> According to Clause 5.8.9.1a.1, the sidelink DRB release procedure can be performed;

[0522] 1> If RRCReconfigurationSidelink includes slrb - ConfigToAddModList:

[0523] 2> For each slrb - PC5 - ConfigIndex value included in slrb - ConfigToAddModList that is not part of the current UE sidelink configuration:

[0524] 3> If sl - MappedQoS - FlowsToAddList is included:

[0525] 4> The SL - PQFI included in sl - MappedQoS - FlowsToAddList can be applied;

[0526] 3> According to Clause 5.8.9.1a.2, the sidelink DRB addition procedure can be performed;

[0527] 2> For each slrb - PC5 - ConfigIndex value included in slrb - ConfigToAddModList that is part of the current UE sidelink configuration:

[0528] 3> If sl-MappedQoS-FlowsToAddList is included:

[0529] 4> The SL-PQFIs included in sl-MappedQoS-FlowsToAddList can be added to the corresponding sidelink DRB;

[0530] 3> If sl-MappedQoS-FlowsToReleaseList is included:

[0531] 4> The SL-PQFIs included in sl-MappedQoS-FlowsToReleaseList can be removed from the corresponding sidelink DRB;

[0532] 3> If the sidelink DRB release conditions described in Clause 5.8.9.1a.1.1 are met:

[0533] 4> According to Clause 5.8.9.1a.1.2, the sidelink DRB release procedure can be executed;

[0534] 3> Otherwise, if the sidelink DRB modification conditions described in Clause 5.8.9.1a.2.1 are met:

[0535] 4> According to Clause 5.8.9.1a.2.2, the sidelink DRB release procedure can be executed;

[0536] 1> If the RRCReconfigurationSidelink message includes sl-MeasConfig:

[0537] 2> The sidelink measurement configuration procedure specified in 5.8.10 can be executed;

[0538] 1> If the RRCReconfigurationSidelink message includes sl-CSI-RS-Config:

[0539] 2> The sidelink CSI-RS configuration can be applied;

[0540] 1> If the RRCReconfigurationSidelink message includes sl-LatencyBoundCSI-Report:

[0541] 2> The configured sidelink CSI report latency bound can be applied;

[0542] 1> If RRCReconfigurationSidelink includes sl-RLC-ChannelToReleaseListPC5:

[0543] 2>For each SL-RLC-ChannelID value included in sl-RLC-ChannelToReleaseListPC5 that is part of the current UE sidelink configuration;

[0544] 3>The PC5-relay RLC channel release procedure can be performed according to Clause 5.8.9.7.1;

[0545] 1>If RRCReconfigurationSidelink includes sl-RLC-ChannelToAddModListPC5:

[0546] 2>For each sl-RLC-ChannelID-PC5 value included in sl-RLC-ChannelToAddModListPC5 that is not part of the current UE sidelink configuration:

[0547] 3>The sidelink RLC channel addition procedure can be performed according to Clause 5.8.9.7.2;

[0548] 2>For each sl-RLC-ChannelID-PC5 value included in sl-RLC-ChannelToAddModListPC5 that is part of the current UE sidelink configuration:

[0549] 3>The PC5-relay RLC channel modification procedure can be performed according to Clause 5.8.9.7.2;

[0550] 1>If the RRCReconfigurationSidelink message includes sl-DRX-ConfigUC-PC5, and

[0551] 1>If the UE accepts sl-DRX-ConfigUC-PC5:

[0552] 2>The lower layers can be configured to perform sidelink DRX operations according to sl-DRX-ConfigUC-PC5 for the associated destination as defined in TS 38.321;

[0553] 1>If the RRCReconfigurationSidelink message includes sl-LatencyBoundIUC-Report:

[0554] 2>The configured sidelink IUC reporting latency bound can be applied;

[0555] 1> If the UE fails to comply with the configuration (part of it) included in RRCReconfigurationSidelink (i.e., sidelink RRC reconfiguration fails):

[0556] 2> It can continue to use the configuration used before receiving the RRCReconfigurationSidelink message;

[0557] 2> It can set the content of the RRCReconfigurationFailureSidelink message;

[0558] 3> It can submit the RRCReconfigurationFailureSidelink message to the lower layer for transmission;

[0559] 1> Otherwise:

[0560] 2> It can set the content of the RRCReconfigurationCompleteSidelink message;

[0561] 3> If the UE rejects the sidelink DRX configuration sl-DRX-ConfigUC-PC5 received from the peer UE:

[0562] 4> It can include sl-DRX-ConfigReject in the RRCReconfigurationCompleteSidelink message;

[0563] 3> It can submit the RRCReconfigurationCompleteSidelink message to the lower layer for transmission;

[0564] Note 1: When the same logical channel is configured with a different RLC mode by another UE, the UE can handle this situation as a sidelink RRC reconfiguration failure.

[0565] Note 2: The UE can decide whether to indicate the rejection of the received sidelink DRX configuration to the peer UE.

[0566] Table 13 shows the start and stop times of the T400 timer and the operations upon expiration.

[0567] [Table 13]

[0568]

[0569] In addition, in the present disclosure, operations of the UE for SL channel state information (CSI) report MAC CE transmission in SL-U are proposed.

[0570] 1. Channel State Information (CSI) Report

[0571] The sidelink channel state information (SL-CSI) reporting procedure can be used to provide the sidelink channel state information specified in clause 8.5 of TS 38.214 to a peer UE.

[0572] RRC may configure the following parameters to control the SL-CSI reporting procedure:

[0573] - sl-LatencyBoundCSI-Report (sl-LatencyBoundCSI-Report can be maintained for each PC5-RRC connection)

[0574] The MAC entity may maintain a sl-CSI-ReportTimer for each pair of source layer-2 ID and destination layer-2 ID corresponding to a PC5-RRC connection. The sl-CSI-ReportTimer can be used by the SL-CSI reporting UE to comply with the latency requirement for CSI-triggered UE signaling. The value of the sl-CSI-ReportTimer may be the same as the latency requirement for SL-CSI reporting in the sl-LatencyBoundCSI-Report configured by RRC.

[0575] The MAC entity may perform the following for each pair of source layer-2 ID and destination layer-2 ID corresponding to an established upper-layer PC5-RRC connection:

[0576] 1> If the SL-CSI report has been triggered by an SCI and not cancelled:

[0577] 2> If the sl-CSI-ReportTimer for the triggered SL-CSI report is not running:

[0578] 3> The sl-CSI-ReportTimer may be started.

[0579] 2> If the sl-CSI-ReportTimer for the triggered SL-CSI report expires:

[0580] 3> The triggered SL-CSI report may be cancelled.

[0581] 2> Otherwise, if the MAC entity has SL resources allocated for a new transmission and, due to logical channel prioritization, the SL-SCH resources can accommodate the SL-CSI report MAC CE and its sub-header:

[0582] 3> The multiplexing and assembly procedure may be indicated to generate the sidelink CSI report MAC CE as defined in clause 6.1.3.35;

[0583] 3> If LBT operation is supported for the active SL BWP or sl-lbt-FailureRecoveryConfig is configured for the active SL BWP:

[0584] 4> If an LBT success indication has been received from the lower layer:

[0585] 5> The sl-CSI-ReportTimer for the triggered SL-CSI report can be stopped;

[0586] 5> The triggered SL-CSI report can be cancelled.

[0587] 3> Otherwise:

[0588] 4> The sl-CSI-ReportTimer for the triggered SL-CSI report can be stopped;

[0589] 4> The triggered SL-CSI report can be cancelled.

[0590] 2> Otherwise, if the MAC entity is configured with sidelink resource allocation mode 1:

[0591] 3> A scheduling request can be triggered.

[0592] Note: If the transmission of a pending SL-CSI report with sidelink grant cannot meet the latency requirements related to the SL-CSI report, the MAC entity configured with sidelink resource allocation mode 1 can trigger a scheduling request.

[0593] 2. Another implementation of CSI reporting

[0594] The sidelink channel state information (SL-CSI) reporting procedure can be used to provide sidelink channel state information to a peer UE as specified in clause 8.5 of TS 38.214.

[0595] The RRC can configure the following parameters to control the SL-CSI reporting procedure:

[0596] - sl-LatencyBoundCSI-Report (sl-LatencyBoundCSI-Report can be maintained for each PC5-RRC connection)

[0597] The MAC entity may maintain a sl-CSI-ReportTimer for each pair of source layer-2 ID and destination layer-2 ID corresponding to a PC5-RRC connection. The sl-CSI-ReportTimer may be used for the SL-CSI reporting UE to comply with the latency requirement signaled by the CSI trigger UE. The value of the sl-CSI-ReportTimer may be the same as the latency requirement of the SL-CSI report in the sl-LatencyBoundCSI-Report configured by RRC.

[0598] The MAC entity may perform the following for each pair of source layer-2 ID and destination layer-2 ID corresponding to an established upper layer PC5-RRC connection:

[0599] 1> If the SL-CSI report has been triggered by an SCI and not cancelled:

[0600] 2> If the sl-CSI-ReportTimer for the triggered SL-CSI report is not running:

[0601] 3> The sl-CSI-ReportTimer may be started.

[0602] 2> If the sl-CSI-ReportTimer for the triggered SL-CSI report expires:

[0603] 3> The triggered SL-CSI report may be cancelled.

[0604] 2> Otherwise, if the MAC entity has SL resources allocated for a new transmission and, due to logical channel prioritization, the SL-SCH resources can accommodate the SL-CSI report MAC CE and its sub-header:

[0605] 3> The multiplexing and assembly process may be indicated to generate a sidelink CSI report MAC CE, as defined in clause 6.1.3.35;

[0606] 3> If sidelink LBT operation is supported for the active SL BWP or sl-lbt-FailureRecoveryConfig is configured for the active SL BWP:

[0607] 4> If a sidelink LBT failure indication has not been received from the lower layer:

[0608] 5> The sl-CSI-ReportTimer for the triggered SL-CSI report may be stopped;

[0609] 5> The triggered SL-CSI report may be cancelled.

[0610] 3> Otherwise (a sidelink LBT failure indication has been received from a lower layer):

[0611] 4> Do not stop the sl-CSI-ReportTimer for the triggered SL-CSI report;

[0612] 4> Do not cancel the triggered SL-CSI report.

[0613] 2> Otherwise, if the MAC entity is configured with sidelink resource allocation mode 1:

[0614] 3> A scheduling request may be triggered.

[0615] Note: If the transmission of a pending SL-CSI report with sidelink grant cannot meet the latency requirements related to the SL-CSI report, the MAC entity configured with sidelink resource allocation mode 1 may trigger a scheduling request.

[0616] Figure 23 Embodiments of SL CSI report MAC CE in an unlicensed band as proposed in the present disclosure are shown. Figure 23 Embodiments of may be combined with various embodiments of the present disclosure.

[0617] In Figure 23 The UE triggered by the SCI to send the SL CSI report MAC CE may generate the SL CSI report MAC CE, then stop the sl-CSI-ReportTimer only when the LBT is successful, and may cancel the triggered SL CSI report at the same time (operation: cancel the triggered SL CSI report because it will send the SL CSI report MAC CE), and may report the generated SL CSI report MAC CE to the UE requesting the SL CSI report via the SCI.

[0618] Alternatively, for example, the UE triggered by the SCI to send the SL CSI report MAC CE may generate the SL CSI report MAC CE only when the LBT is successful, then stop the sl-CSI-ReportTimer, and may cancel the triggered SL CSI report at the same time (operation: cancel the triggered SL CSI report because it will send the SL CSI report MAC CE), and may report the generated SL CSI report MAC CE to the UE requesting the SL CSI report via the SCI.

[0619] Figure 24 Embodiments of SL CSI report MAC CE in an unlicensed band as proposed in the present disclosure are shown. Figure 24 Embodiments of may be combined with various embodiments of the present disclosure.

[0620] In Figure 24 , a UE triggered by an SCI to send an SL CSI report MAC CE may generate an SL CSI report MAC CE, then stop the sl-CSI-ReportTimer only when no LBT failure indication is received from the PHY layer, and may cancel the triggered SL CSI report simultaneously (operation: cancel the triggered SL CSI report because it will send an SL CSI report MAC CE), and may report the generated SL CSI report MAC CE to the UE requesting the SL CSI report via the SCI.

[0621] Alternatively, for example, a UE triggered by an SCI to send an SL CSI report MAC CE may generate an SL CSI report MAC CE only when no LBT failure indication is received from the PHY layer, then stop the sl-CSI-ReportTimer, and may cancel the triggered SL CSI report simultaneously (operation: cancel the triggered SL CSI report because it will send an SL CSI report MAC CE), and may report the generated SL CSI report MAC CE to the UE requesting the SL CSI report via the SCI.

[0622] Figure 25 Embodiments of the SL CSI report MAC CE in the unlicensed band as proposed in the present disclosure are shown. Figure 25 Embodiments of

[0623] In Figure 25 , a UE triggered by an SCI to send an SL CSI report MAC CE may generate an SL CSI report MAC CE, then when an LBT failure indication is received from the PHY layer, may not stop the sl-CSI-ReportTimer. Additionally, for example, it may not cancel the triggered SL CSI report. That is, for example, since it cannot send the triggered SL CSI report MAC CE due to LBT failure, it may not cancel the triggered SL CSI report.

[0624] Alternatively, for example, when a UE triggered by an SCI to send an SL CSI report MAC CE receives an LBT failure indication from the PHY layer, it may not generate an SL CSI report MAC CE and may not stop the sl-CSI-ReportTimer. Additionally, for example, it may not cancel the triggered SL CSI report. That is, for example, since it may not generate (or may not generate and send) the triggered SL CSI report MAC CE due to LBT failure, it may not cancel the triggered SL CSI report.

[0625] In addition, in the present disclosure, a method for the operation of the UE for the transmission of IUC request messages and IUC information messages in NR V2X is proposed.

[0626] For example, when a type-B UE (SL data transmission UE) receives an IUC information MAC CE from a type-A UE (UE that sends an IUC information MAC CE), it can select resources for SL data transmission by referring to the information (e.g., resource pool) of the received IUC information MAC CE. Additionally, for example, a type-B UE can request the transmission of an IUC information MAC CE of a type-A UE by sending an IUC request MAC CE (or SCI) that requests the transmission of the IUC information MAC CE. For example, a type-A UE that receives an IUC request MAC CE from a type-B UE can send an IUC information MAC CE to the type-B UE.

[0627] The IUC information MAC CE or message described in the present disclosure may refer to a message or MAC CE that includes IUC information (e.g., includes preferred / non-preferred recommended resource information), and the IUC request MAC CE or message may refer to a MAC CE that requests an IUC information MAC CE or message.

[0628] The type of IUC information MAC (MAC CE including IUC information) may be as follows.

[0629] - Request-based IUC MAC CE: An IUC information MAC CE sent as a response when an IUC request MAC CE is received from UE-B

[0630] - Condition-based IUC MAC CE: An IUC information MAC CE that is triggered and sent when UE-A meets a specific condition, rather than the transmission of a request-based IUC information MAC CE

[0631] In the present disclosure, a method for the operation of the UE for the transmission of IUC request messages (MAC CE or SCI) and IUC information messages (MAC CE or SCI) is proposed.

[0632] In the present disclosure, a method for the operation of the UE is proposed as follows when a resource set (e.g., preferred resource set or non-preferred resource set) to be reported by UE-A (UE that sends an IUC information message or MAC CE) is indicated in an IUC request message (MAC CE or SCI) sent by the UE.

[0633] Solution 1: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., preferred resource set or non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., preferred resource set or non-preferred resource set), then the UE can send only the IUC information triggered by the IUC request message within sl-LatencyBoundIUC-Report (e.g., the time limit value for which an IUC information message or MAC CE should be sent by receiving the IUC request message or MAC CE. That is, within the time limit, UE-A can send an IUC information message to UE-B (the UE that sent the IUC request message). That is to say, for example, an IUC information message triggered and generated based on conditions may not be sent within sl-LatencyBoundIUC-Report).

[0634] Solution 2: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., preferred resource set or non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., preferred resource set or non-preferred resource set), then the UE can leave the choice of which IUC information message among the IUC information triggered by the IUC request message and the IUC information message triggered and generated based on conditions to be sent within sl-LatencyBoundIUC-Report to the UE-A implementation method (e.g., the time limit value for which an IUC information message or MAC UE should be sent by receiving the IUC request information or MAC CE. That is, within the time limit, UE-A can send an IUC information message to UE-B (the UE that sent the IUC request message).).

[0635] Solution 3: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., preferred resource set or non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., preferred resource set or non-preferred resource set), then the UE (or UE-A) can send, within sl-LatencyBoundIUC-Report, the IUC information triggered by the IUC request message and the IUC information message triggered and generated based on conditions to UE-B (e.g., the time limit value for which an IUC information message or MAC CE should be sent by receiving the IUC request information or MAC CE. That is, within the time limit, UE-A can send an IUC information message to UE-B (the UE that sent the IUC request message).).

[0636] In the present disclosure, a method for the operation of a UE is proposed as follows when a resource set (e.g., a preferred resource set or a non-preferred resource set) to be reported by UE-A (the UE that sends the IUC information message or MAC CE) is not indicated in the IUC request message (MAC CE or SCI) sent by the UE and the type of the resource set generated by UE-A (e.g., a preferred resource set or a non-preferred resource set) is indicated in the information of the IUC information message or MAC CE.

[0637] Solution 1: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., a preferred resource set or a non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., a preferred resource set or a non-preferred resource set), the UE may only send the IUC information triggered by the IUC request message within sl-LatencyBoundIUC-Report (e.g., the time limit value for sending the IUC information message or MAC UE by receiving the IUC request information or MAC CE. That is, within the time limit, UE-A may send an IUC information message to UE-B (the UE that sends the IUC request message)). That is, for example, the IUC information message triggered and generated based on conditions may not be sent within sl-LatencyBoundIUC-Report.

[0638] Solution 2: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., a preferred resource set or a non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., a preferred resource set or a non-preferred resource set), the UE may leave the selection of which IUC information message among the IUC information triggered by the IUC request message and the IUC information message triggered and generated based on conditions to be sent within sl-LatencyBoundIUC-Report to the UE-A implementation method (e.g., the time limit value for sending the IUC information message or MAC UE by receiving the IUC request information or MAC CE. That is, within the time limit, UE-A may send an IUC information message to UE-B (the UE that sends the IUC request message)).

[0639] Solution 3: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., the preferred resource set or the non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., the preferred resource set or the non-preferred resource set), the UE (or UE-A) may send, in the sl-LatencyBoundIUC-Report, the IUC information triggered by the IUC request message and the IUC information message generated by being triggered based on conditions (e.g., the time limit value for sending the IUC information message or the MAC CE by receiving the IUC request information or the MAC CE. That is, within the time limit, UE-A may send the IUC information message to UE-B (the UE that sends the IUC request message).).

[0640] In the present disclosure, a method for the operation of the UE is proposed as follows when a resource set (e.g., the preferred resource set or the non-preferred resource set) to be reported by UE-A (the UE that sends the IUC information message or the MAC CE) is indicated in the IUC request message (MAC CE or SCI) sent by the UE.

[0641] Solution 1: For example, from the perspective of UE-A, only when the resource set indicated in the IUC request message (e.g., the preferred resource set or the non-preferred resource set) is different from the resource set included in the IUC information message triggered and generated based on conditions (e.g., the preferred resource set or the non-preferred resource set), UE-A may send, in the sl-LatencyBoundIUC-Report, the most recently generated IUC information message triggered based on conditions (e.g., the time limit value for sending the IUC information message or the MAC CE by receiving the IUC request information or the MAC CE. That is, within the time limit, UE-A may send the IUC information message to UE-B (the UE that sends the IUC request message).).

[0642] Solution 2: For example, from the perspective of UE-A, even if the resource set indicated in the IUC request message (e.g., the preferred resource set or the non-preferred resource set) is the same as the resource set included in the IUC information message triggered and generated based on conditions (e.g., the preferred resource set or the non-preferred resource set), UE-A can send, in the sl-LatencyBoundIUC-Report, the most recently generated IUC information message triggered by conditions (e.g., the time limit value for sending the IUC information message or the MAC UE by receiving the IUC request information or the MAC CE. That is, within the time limit, UE-A can send the IUC information message to UE-B (the UE that sends the IUC request message)) only when the included resource pool information is different.

[0643] Solution 3: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., the preferred resource set or the non-preferred resource set) is the same as or different from the resource set included in the IUC information message triggered and generated based on conditions (e.g., the preferred resource set or the non-preferred resource set), UE-A can send, in the sl-LatencyBoundIUC-Report, the most recently generated IUC information message among the IUC request message triggered by the IUC request message and the most recently generated IUC information message triggered by conditions (e.g., the time limit value for sending the IUC information message or the MAC UE by receiving the IUC request message or the MAC CE. That is, within the time limit, UE-A can send the IUC information message to UE-B (the UE that sends the IUC request message)).

[0644] In the present disclosure, a method for the operation of the UE is proposed as follows when the resource set (e.g., the preferred resource set or the non-preferred resource set) to be reported by UE-A (the UE that sends the IUC information message or the MAC CE) is not indicated in the IUC request message (MAC CE or SCI) sent by the UE and the type of the resource set generated by UE-A is indicated in the information of the IUC information message or the MAC CE.

[0645] Solution 1: For example, from the perspective of UE-A, UE-A can send the most recently generated IUC information message triggered by a condition (e.g., the time limit value for sending the IUC information message or MAC UE by receiving IUC request information or MAC CE. That is, within the time limit, UE-A can send the IUC information message to UE-B (the UE that sent the IUC request message)) in the sl-LatencyBoundIUC-Report only when the resource set indicated in the IUC request message (e.g., the preferred resource set or non-preferred resource set) is different from the resource set included in the IUC information message triggered by a condition and generated (e.g., the preferred resource set or non-preferred resource set).

[0646] Solution 2: For example, from the perspective of UE-A, even if the resource set indicated in the IUC request message (e.g., the preferred resource set or non-preferred resource set) is the same as the resource set included in the IUC information message triggered by a condition and generated (e.g., the preferred resource set or non-preferred resource set), UE-A can send the most recently generated IUC information message triggered by a condition (e.g., the time limit value for sending the IUC information message or MAC UE by receiving IUC request information or MAC CE. That is, within the time limit, UE-A can send the IUC information message to UE-B (the UE that sent the IUC request message)) in the sl-LatencyBoundIUC-Report only when the included resource pool information is different.

[0647] Solution 3: For example, from the perspective of UE-A, if the resource set indicated in the IUC request message (e.g., the preferred resource set or non-preferred resource set) is the same as or different from the resource set included in the IUC information message triggered by a condition and generated (e.g., the preferred resource set or non-preferred resource set), UE-A can send the most recently generated IUC information message among the IUC information message triggered by the IUC request message and the most recently generated IUC information message triggered by a condition (e.g., the time limit value for sending the IUC information message or MAC UE by receiving IUC request message or MAC CE. That is, within the time limit, UE-A can send the IUC information message to UE-B (the UE that sent the IUC request message)) in the sl-LatencyBoundIUC-Report.

[0648] The channels specified in this disclosure can be applied by replacing carriers, a set of resource blocks (RBs) of a specific carrier, or frequency bands.

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

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

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

[0652] The proposal and whether to apply the proposed rules of the present disclosure (and / or related parameter configuration values) can also be applied to millimeter-wave SL operations.

[0653] According to various embodiments of the present disclosure, even if the UE generates IUC information MAC CE according to the IUC information reporting process in SL-U, the initiated IUC reporting timer can be stopped only when LBT is successful. In this case, the UE can ensure the transmission of IUC information MAC CE according to the IUC information reporting process in SL-U. Additionally, even if the UE generates IUC information MAC CE according to the IUC information reporting process in SL-U, when LBT fails, the initiated IUC reporting timer may not be stopped. In this case, the UE can perform additional LBT until the IUC reporting timer expires to ensure an opportunity to send IUC information MAC CE.

[0654] Figure 26 A method for a first device to perform wireless communication according to an embodiment of the present disclosure is shown. Figure 26 Embodiments of can be combined with various embodiments of the present disclosure.

[0655] Referring to Figure 26 , at step S2610, the first device may obtain a configuration related to the inter-UE coordination (IUC) information report. At step S2620, the first device may initiate an IUC report timer based on the triggering of the IUC information report. At step S2630, the first device may perform listen-before-talk (LBT). At step S2640, the first device may stop the IUC report timer based on (i) the generation of the IUC information media access control (MAC) control element (CE) and (ii) the success of the LBT.

[0656] For example, the IUC report timer may be stopped based on (i) the generation of the IUC information MAC CE and (ii) not receiving an LBT failure indication from the lower layer.

[0657] For example, based on (i) the generation of the IUC information MAC CE and (ii) the failure of the LBT, the IUC timer may not be stopped. For example, based on (i) the generation of the IUC information MAC CE and (ii) receiving an LBT failure indication from the lower layer, the IUC timer may not be stopped.

[0658] In addition, for example, the first device may cancel the triggered IUC information report based on (i) the generation of the IUC information MAC CE and (ii) the success of the LBT. In addition, for example, the first device may send the generated IUC information MAC CE to the second device.

[0659] For example, LBT may be performed on an active sidelink (SL) bandwidth part (BWP), and an LBT failure recovery configuration may be configured for the active SL BWP.

[0660] 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 may control the transceiver 106 to obtain a configuration related to the inter-UE coordination (IUC) information report. And, the processor 102 of the first device 100 may initiate an IUC report timer based on the triggering of the IUC information report. And, the processor 102 of the first device 100 may perform listen-before-talk (LBT). And, the processor 102 of the first device 100 may stop the IUC report timer based on (i) the generation of the IUC information media access control (MAC) control element (CE) and (ii) the success of the LBT.

[0661] According to an embodiment of the present disclosure, a first device configured to perform wireless communication is provided. The first device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT.

[0662] According to an embodiment of the present disclosure, a processing device configured to control a first device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT.

[0663] According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, when executed, cause the first device to perform operations including: obtaining a configuration related to an Inter-UE Coordination (IUC) information report; initiating an IUC report timer based on the IUC information report being triggered; performing Listen Before Talk (LBT); and stopping the IUC report timer based on (i) the generation of an IUC information Medium Access Control (MAC) Control Element (CE) and (ii) the success of the LBT.

[0664] Figure 27 A method for a first device to perform wireless communication based on an embodiment of the present disclosure is shown. Figure 27 Embodiments of may be combined with various embodiments of the present disclosure.

[0665] Refer to Figure 27, at step S2710, the first device may obtain a configuration related to a channel state information (CSI) report. At step S2720, the first device may initiate a CSI report timer based on being triggered by the CSI report. At step S2730, the first device may perform LBT. At step S2740, the first device may stop the CSI report timer based on (i) the generation of the CSI report MAC CE and (ii) the success of the LBT.

[0666] For example, the CSI report timer may be stopped based on (i) the generation of the CSI report MAC CE and (ii) not receiving an LBT failure indication from a lower layer.

[0667] For example, LBT may be performed based on the generation of the CSI report MAC CE, the CSI report timer may be stopped based on the success of the LBT, and the success of the LBT may be based on not receiving an LBT failure indication from a lower layer.

[0668] For example, the CSI report MAC CE may be generated based on the success of the LBT, the CSI report timer may be stopped based on the generation of the CSI report MAC CE, and the success of the LBT may be based on not receiving an LBT failure indication from a lower layer.

[0669] For example, based on (i) the generation of the CSI report MAC CE and (ii) the failure of the LBT, the CSI report timer may not be stopped. For example, LBT may be performed based on the generation of the CSI report MAC CE, the CSI report timer may not be stopped based on the failure of the LBT, and the failure of the LBT may be based on receiving an LBT failure indication from a lower layer.

[0670] Additionally, for example, the first device may cancel the triggered CSI report based on (i) the generation of the CSI report MAC CE and (ii) the success of the LBT.

[0671] The proposed method may be applied to a device according to various embodiments of the present disclosure. First, the processor 102 of the first device 100 may control the transceiver 106 to obtain a configuration related to a channel state information (CSI) report. Also, the processor 102 of the first device 100 may initiate a CSI report timer based on being triggered by the CSI report. Also, the processor 102 of the first device 100 may perform LBT. Also, the processor 102 of the first device 100 may stop the CSI report timer based on (i) the generation of the CSI report MAC CE and (ii) the success of the LBT.

[0672] According to an embodiment of the present disclosure, a first device configured to perform wireless communication is provided. The first device may include: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

[0673] According to an embodiment of the present disclosure, a processing device configured to control a first device is provided. The processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to perform operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

[0674] According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium recording instructions is provided. For example, the instructions, when executed, cause the first device to perform operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

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

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

[0677] Various descriptions, functions, processes, proposals, methods, and / or operation flows of the present disclosure described in this document can be applied to, but are not limited to, various fields that require wireless communication / connection (e.g., 5G) between devices.

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

[0679] Figure 28 A communication system 1 based on an embodiment of the present disclosure is shown.Figure 28 The implementation manners can be combined with various implementation manners of the present disclosure.

[0680] Referring to Figure 28 , the communication system 1 applying various implementation manners of the present disclosure includes a wireless device, a base station (BS), and a network. Herein, the wireless device represents a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or Long-Term Evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include, without limitation, a robot 100a, vehicles (100b-1, 100b-2), an extended reality (XR) device (100c), a handheld device 100d, a household appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicle may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing vehicle-to-vehicle communication. Herein, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). 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) mounted in a vehicle, a television, a smart phone, a computer, a wearable device, a household appliance device, a digital signage, a vehicle, a robot, etc. The handheld device may include a smart phone, a smart board, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a notebook). The household appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include sensors and smart meters. For example, the BS and the network may be implemented as wireless devices, and a specific wireless device (200a) may operate as a BS / network node with respect to other wireless devices.

[0681] Here, in addition to LTE, NR, and 6G, the wireless communication technologies implemented in the wireless devices 100a to 100f of the present disclosure may further include NarrowBand Internet of Things (NB-IoT) for low-power communication. In this case, for example, the NB-IoT technology may be an example of a Low-Power Wide-Area Network (LPWAN) technology and may be implemented as a standard such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100a to 100f of the present disclosure may perform communication based on the LTE-M technology. In this case, as an example, the LTE-M technology may be an example of an LPWAN and may be referred to by various names including Enhanced Machine-Type Communication (eMTC), etc. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE Non-Bandwidth Limited (Non-BL), 5) LTE-MTC, 6) LTE Machine-Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100a to 100f of the present disclosure may include at least one of Bluetooth, Low-Power Wide-Area Network (LPWAN), and ZigBee considering low-power communication, and is not limited to the above names. As an example, the ZigBee technology may generate a Personal Area Network (PAN) related to small / low-power digital communication based on various standards including IEEE 802.15.4, etc., and may be referred to by various names.

[0682] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without going through the BS / network. For example, vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V) / Vehicle-to-Everything (V2X) communication). IoT devices (e.g., sensors) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

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

[0684] Figure 29 A wireless device according to an embodiment of the present disclosure is shown. Figure 29 Embodiments of can be combined with various embodiments of the present disclosure.

[0685] Referring to Figure 29 , the first wireless device 100 and the second wireless device 200 can send radio signals through various RATs (e.g., LTE and NR). Here, {the first wireless device 100 and the second wireless device 200} can correspond to Figure 19 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x} in

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

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

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

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

[0690] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be constituted by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, register, cache memory, computer-readable storage medium, and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various techniques such as wired or wireless connections.

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

[0692] Figure 30 A signal processing circuit for transmitting a signal based on an embodiment of the present disclosure is shown. Figure 30 Embodiments of may be combined with various embodiments of the present disclosure.

[0693] Referring to Figure 30 , 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. The operations / functions of may be performed, not limited to Figure 30 the processors (102, 202) and / or transceivers (106, 206) of Figure 29 It may be throughFigure 29 implemented by processors (102, 202) and / or transceivers (106, 206) Figure 30 hardware components. For example, Figure 29 frames 1010 to 1060 can be implemented by processors (102, 202) of Figure 29 frames 1010 to 1050 can be implemented by processors (102, 202) of Figure 29 and frame 1060 can be implemented by transceivers (106, 206) of

[0694] It can be converted into a radio signal via Figure 30 signal processing circuit 1000 of. Here, a codeword is a sequence of coded bits of an information block. The information block can include transport blocks (e.g., UL - SCH transport blocks, DL - SCH transport blocks). The radio signal can be transmitted through various physical channels (e.g., PUSCH and PDSCH).

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

[0696] Resource mapper 1050 can map the modulation symbols of each antenna port to time - frequency resources. The time - frequency resources can include multiple symbols in the time domain (e.g., CP - OFDMA symbols and DFT - s - OFDMA symbols) and multiple sub - carriers in the frequency domain. Signal generator 1060 can generate a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices through each antenna. For this purpose, signal generator 1060 can include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital - to - analog converter (DAC), and an up - converter.

[0697] The signal processing procedure for the signals received in a wireless device can be configured in a manner opposite to that of Figure 30 the signal processing procedure (1010 to 1060). For example, a wireless device (e.g., Figure 29 100, 200) can receive radio signals from the outside through an antenna port / transceiver. The received radio signals can be converted into baseband signals by 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. Next, the baseband signals can be restored into codewords through a resource demapping process, a post-coding process, a demodulation processor, and a descrambling process. The codewords can be restored into the original information blocks through decoding. Therefore, the signal processing circuit (not illustrated) for receiving signals can include a signal restorer, a resource demapper, a post-encoder, a demodulator, a descrambler, and a decoder.

[0698] Figure 31 Another example of a wireless device according to an embodiment of the present disclosure is shown. The wireless device can be implemented in various forms according to use cases / services (refer to Figure 28 ). Figure 31 The embodiments of

[0699] can be combined with various embodiments of the present disclosure. Figure 31 Referring to Figure 29 , the wireless devices (100, 200) can correspond to the wireless devices (100, 200) of Figure 29 and can be configured by various elements, components, units / parts, and / or modules. For example, each of the wireless devices (100, 200) can include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit can include a communication circuit 112 and one or more transceivers 114. For example, the communication circuit 112 can include Figure 29 one or more processors (102, 202) and / or one or more memories (104, 204) of Figure 29One or more transceivers (106, 206) and / or one or more antennas (108, 208). The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operations of the wireless device based on programs / codes / commands / information stored in the memory unit 130. The control unit 120 may send the information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store the information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0700] The additional components 140 may be variously configured according to the type of the wireless device. For example, the additional components 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. The wireless device may be implemented in, but not limited to, the following forms: a robot ( Figure 28 100a), a vehicle ( Figure 28 100b-1 and 100b-2), an XR device ( Figure 28 100c), a handheld device ( Figure 28 100d), a home appliance ( Figure 28 100e), an IoT device ( Figure 28 100f), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device ( Figure 28 400), a BS ( Figure 28 200), a network node, etc. According to use cases / services, the wireless device may be used in a mobile or fixed place.

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

[0702] In the following, examples of implementing Figure 31 will be described in detail with reference to the accompanying drawings.

[0703] Figure 32 FIG. [number] shows a handheld device according to an embodiment of the present disclosure. The handheld device can include a smart phone, a smart tablet, a wearable device (e.g., a smart watch or smart glasses), or a portable computer (e.g., a notebook). The handheld device can 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). Figure 32 Embodiments of

[0704] Referring to Figure 32 , the handheld device 100 can include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an I / O unit 140c. The antenna unit 108 can be configured as part of the communication unit 110. Blocks 110 to 130 / 140a to 140c respectively correspond to Figure 31 blocks 110 to 130 / 140 of

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

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

[0707] Figure 33 A vehicle or an autonomous vehicle according to an embodiment of the present disclosure is shown. The vehicle or the autonomous vehicle can be implemented by a mobile robot, an automobile, a train, a manned / unmanned aerial vehicle (AV), a ship, etc. Figure 24 Embodiments of can be combined with various embodiments of the present disclosure.

[0708] Referring to Figure 33 , the vehicle or the autonomous vehicle 100 can 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 can be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to Figure 31 blocks 110 / 130 / 140 of

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

[0710] For example, the communication unit 110 can receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d can generate an autonomous driving path and a driving plan from the acquired data. The control unit 120 can control the driving unit 140a so that the vehicle or autonomous driving vehicle 100 can move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 can acquire the latest traffic information data from the external server non-periodically / periodically, and acquire the surrounding traffic information data from adjacent vehicles. During autonomous driving, the sensor unit 140c can acquire vehicle status and / or surrounding environment information. The autonomous driving unit 140d can update the autonomous driving path and the driving plan based on the newly acquired data / information. The communication unit 110 can transmit information on the relevant vehicle position, autonomous driving path, and / or driving plan to the external server. The external server can use AI technology, etc. to predict traffic information data based on the information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0711] The claims in this specification can be combined in various ways. For example, the technical features in the method claims of this specification can be combined to be implemented or executed in a device, and the technical features in the device claims can be combined to be implemented or executed in a method. Additionally, the technical features in the (one or more) method claims and the (one or more) device claims can be combined to be implemented or executed in a device. Additionally, the technical features in the (one or more) method claims and the (one or more) device claims can be combined to be implemented or executed in a method.

Claims

1. A method for a first device to perform wireless communication, the method comprises the following steps: Obtain a configuration related to the inter-UE coordination (IUC) information report; Based on the triggering of the IUC information report, initiate an IUC report timer; Perform listen-before-talk (LBT); And Based on (i) the generation of the IUC information media access control (MAC) control element (CE) and (ii) the success of the LBT, stop the IUC report timer.

2. The method according to claim 1, wherein, Based on (i) the generation of the IUC information MAC CE and (ii) not receiving an LBT failure indication from the lower layer, stop the IUC report timer.

3. The method according to claim 1, wherein, Based on (i) the generation of the IUC information MAC CE and (ii) the failure of the LBT, do not stop the IUC timer.

4. The method according to claim 3, wherein, Based on (i) the generation of the IUC information MAC CE and (ii) receiving an LBT failure indication from the lower layer, do not stop the IUC timer.

5. The method according to claim 1, the method further comprises the following steps: Based on (i) the generation of the IUC information MAC CE and (ii) the success of the LBT, cancel the triggered IUC information report.

6. The method according to claim 5, the method further comprises the following steps: Send the generated IUC information MAC CE to a second device.

7. The method according to claim 1, wherein, The LBT is performed on an active sidelink (SL) bandwidth part (BWP), and wherein, the LBT failure recovery configuration is configured for the active SL BWP.

8. A first device adapted to perform wireless communication, the first device comprises: At least one transceiver; At least one processor; And At least one memory, the at least one memory is connected to the at least one processor and stores instructions, the instructions when executed cause the first device to perform operations, the operations include: Obtain a configuration related to the inter-UE coordination (IUC) information report; Based on the triggering of the IUC information report, initiate an IUC report timer; Perform listen-before-talk (LBT); and Based on (i) the generation of the IUC information media access control (MAC) control element (CE) and (ii) the success of the LBT, stop the IUC report timer.

9. A processing device adapted to control a first device to perform wireless communication, the processing device comprises: At least one processor; And At least one memory, the at least one memory is connected to the at least one processor and stores instructions, the instructions when executed cause the at least one processor to perform operations, the operations include: Obtain a configuration related to the inter-UE coordination (IUC) information report; Based on the triggering of the IUC information report, initiate an IUC report timer; Perform listen-before-talk (LBT); and Stop the IUC reporting timer based on (i) the generation of the IUC information medium access control (MAC) control element (CE) and (ii) the success of the LBT.

10. A non-transitory computer-readable storage medium recording instructions that, when executed, cause a first device to perform operations, the operations comprising: obtaining a configuration related to the UE-to-UE coordination (IUC) information reporting; initiating an IUC reporting timer based on the IUC information reporting being triggered; performing listen-before-talk (LBT); and stop the IUC reporting timer based on (i) the generation of the IUC information medium access control (MAC) control element (CE) and (ii) the success of the LBT.

11. A method for a first device to perform wireless communication, the method comprising the steps of: obtaining a configuration related to the channel state information (CSI) reporting; initiating a CSI reporting timer based on the CSI reporting being triggered; performing LBT; and stop the CSI reporting timer based on (i) the generation of the CSI reporting MAC CE and (ii) the success of the LBT.

12. The method according to claim 11, wherein stop the CSI reporting timer based on (i) the generation of the CSI reporting MAC CE and (ii) not receiving an LBT failure indication from a lower layer.

13. The method according to claim 11, wherein the LBT is performed based on the generation of the CSI reporting MAC CE, wherein, based on the success of the LBT, the CSI reporting timer is stopped, and wherein the success of the LBT is based on not receiving an LBT failure indication from a lower layer.

14. The method according to claim 11, wherein the CSI reporting MAC CE is generated based on the success of the LBT, wherein, based on the generation of the CSI reporting MAC CE, the CSI reporting timer is stopped, and wherein the success of the LBT is based on not receiving an LBT failure indication from a lower layer.

15. The method according to claim 11, wherein do not stop the CSI reporting timer based on (i) the generation of the CSI reporting MAC CE and (ii) the failure of the LBT.

16. The method according to claim 15, wherein the LBT is performed based on the generation of the CSI reporting MAC CE, wherein, based on the failure of the LBT, the CSI reporting timer is not stopped, and wherein the failure of the LBT is based on receiving an LBT failure indication from a lower layer.

17. The method according to claim 11, the method further comprising the steps of: canceling the triggered CSI reporting based on (i) the generation of the CSI reporting MAC CE and (ii) the success of the LBT.

18. A first device adapted to perform wireless communication, the first device comprising: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed, cause the first device to perform operations, the operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

19. A processing device adapted to control a first device to perform wireless communication, the processing device comprising: at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

20. A non-transitory computer-readable storage medium recording instructions that, when executed, cause a first device to perform operations, the operations including: obtaining a configuration related to a channel state information (CSI) report; initiating a CSI report timer based on the CSI report being triggered; performing LBT; and stopping the CSI report timer based on (i) the generation of a CSI report MAC CE and (ii) the success of the LBT.

Images