WO2023200312A1 - Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치 - Google Patents

Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치 Download PDF

Info

Publication number
WO2023200312A1
WO2023200312A1 PCT/KR2023/005135 KR2023005135W WO2023200312A1 WO 2023200312 A1 WO2023200312 A1 WO 2023200312A1 KR 2023005135 W KR2023005135 W KR 2023005135W WO 2023200312 A1 WO2023200312 A1 WO 2023200312A1
Authority
WO
WIPO (PCT)
Prior art keywords
cot
terminal
information
channel
drx
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2023/005135
Other languages
English (en)
French (fr)
Korean (ko)
Inventor
박기원
이승민
백서영
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to KR1020237030068A priority Critical patent/KR20250001855A/ko
Priority to US18/549,160 priority patent/US20250324451A1/en
Priority to JP2023554349A priority patent/JP7759957B2/ja
Priority to EP23761413.6A priority patent/EP4510754A4/de
Priority to CN202380010781.XA priority patent/CN117242890A/zh
Publication of WO2023200312A1 publication Critical patent/WO2023200312A1/ko
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • This disclosure relates to wireless communication systems.
  • V2X vehicle-to-everything refers to a communication technology that exchanges information with other vehicles, pedestrians, and objects with built infrastructure through wired/wireless communication.
  • V2X can be divided into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P).
  • V2X communication may be provided through the PC5 interface and/or the Uu interface.
  • next-generation wireless access technology that takes these into consideration may be referred to as new radio access technology (RAT) or new radio (NR).
  • RAT new radio access technology
  • NR new radio
  • a method for a first device to perform wireless communication includes: receiving, from a second device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier); determining to use the COT section based on the first ID being the same as the second ID of the first device; Performing channel sensing on transmission resources within the COT section; And it may include performing sidelink (SL) communication based on the result of the channel sensing.
  • COT channel occupancy time
  • a first device that performs wireless communication may be provided.
  • the first device may include at least one transceiver; at least one processor; and at least one memory executable coupled to the at least one processor and recording instructions that cause the first device to perform operations based on execution by the at least one processor.
  • the operations include: receiving, from a second device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier); determining to use the COT section based on the first ID being the same as the second ID of the first device; Performing channel sensing on transmission resources within the COT section; And it may include performing sidelink (SL) communication based on the result of the channel sensing.
  • COT channel occupancy time
  • identifier a first ID
  • SL sidelink
  • a device configured to control a first terminal.
  • the device may include at least one processor; and at least one memory executable connectable to the at least one processor and recording instructions that cause the first terminal to perform operations based on execution by the at least one processor.
  • the operations include: receiving, from a second device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier); determining to use the COT section based on the first ID being the same as the second ID of the first device; Performing channel sensing on transmission resources within the COT section; And it may include performing sidelink (SL) communication based on the result of the channel sensing.
  • COT channel occupancy time
  • identifier a first ID
  • SL sidelink
  • a non-transitory computer readable storage medium recording instructions may be provided.
  • the above instructions when executed, cause a first device to: receive, from a second device, COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID); do; determine to use the COT section based on the first ID being the same as the second ID of the first device; Perform channel sensing on transmission resources within the COT section; And sidelink (SL) communication can be performed based on the results of the channel sensing.
  • COT channel occupancy time
  • ID first identifier
  • SL sidelink
  • a method for a second device to perform wireless communication may be provided.
  • the method may include: transmitting, to a first device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier).
  • COT channel occupancy time
  • the COT section may be determined to be used for the first device.
  • a second device that performs wireless communication may be provided.
  • the second device may include at least one transceiver; at least one processor; and at least one memory executable coupled to the at least one processor and recording instructions that cause the second device to perform operations based on execution by the at least one processor.
  • the operations include: transmitting, to a first device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier), wherein the first ID Based on that is the same as the second ID of the first device, the COT section may be determined to be used for the first device.
  • the terminal can efficiently perform sidelink communication.
  • Figure 1 shows a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure.
  • Figure 2 shows an electromagnetic spectrum, according to one embodiment of the present disclosure.
  • Figure 3 shows the structure of an NR system according to an embodiment of the present disclosure.
  • Figure 4 shows a radio protocol architecture, according to an embodiment of the present disclosure.
  • Figure 5 shows the structure of a radio frame of NR, according to an embodiment of the present disclosure.
  • Figure 6 shows the slot structure of an NR frame according to an embodiment of the present disclosure.
  • Figure 7 shows an example of BWP, according to an embodiment of the present disclosure.
  • Figure 8 shows a procedure in which a terminal performs V2X or SL communication depending on the transmission mode, according to an embodiment of the present disclosure.
  • Figure 9 shows three cast types, according to an embodiment of the present disclosure.
  • Figure 10 shows an example of a DRX cycle, according to an embodiment of the present disclosure.
  • Figure 11 shows an example of a wireless communication system supporting an unlicensed band, according to an embodiment of the present disclosure.
  • Figure 12 shows a method of occupying resources within an unlicensed band, according to an embodiment of the present disclosure.
  • Figure 13 shows a case where a plurality of LBT-SBs are included in an unlicensed band, according to an embodiment of the present disclosure.
  • Figure 14 shows a CAP operation for downlink signal transmission through an unlicensed band of a base station, according to an embodiment of the present disclosure.
  • Figure 15 shows a type 1 CAP operation of a terminal for uplink signal transmission, according to an embodiment of the present disclosure.
  • Figure 16 shows contention operation for channels of LBE and FBE, according to an embodiment of the present disclosure.
  • Figure 17 shows an example of an operation performed within a shared COT, according to an embodiment of the present disclosure.
  • Figure 18 shows a procedure in which a terminal receiving COT sharing information uses COT, according to an embodiment of the present disclosure.
  • Figure 19 shows a procedure in which a terminal receiving COT sharing information uses COT, according to an embodiment of the present disclosure.
  • Figure 20 shows a procedure in which a first device performs wireless communication, according to an embodiment of the present disclosure.
  • Figure 21 shows a procedure in which a second device performs wireless communication, according to an embodiment of the present disclosure.
  • Figure 22 shows a communication system 1, according to one embodiment of the present disclosure.
  • Figure 23 shows a wireless device according to an embodiment of the present disclosure.
  • Figure 24 shows a signal processing circuit for a transmission signal, according to an embodiment of the present disclosure.
  • Figure 25 shows a wireless device, according to an embodiment of the present disclosure.
  • 26 shows a portable device according to an embodiment of the present disclosure.
  • FIG. 27 shows a vehicle or autonomous vehicle, according to an embodiment of the present disclosure.
  • a or B may mean “only A,” “only B,” or “both A and B.” In other words, as used herein, “A or B” may be interpreted as “A and/or B.”
  • A, B or C refers to “only A,” “only B,” “only C,” or “any and all combinations of A, B, and C ( It can mean “any combination of A, B and C)”.
  • the slash (/) or comma used in this specification may mean “and/or.”
  • A/B can mean “A and/or B.”
  • A/B can mean “only A,” “only B,” or “both A and B.”
  • A, B, C can mean “A, B, or C.”
  • At least one of A and B may mean “only A,” “only B,” or “both A and B.”
  • the expression “at least one of A or B” or “at least one of A and/or B” means “at least one It can be interpreted the same as "at least one of A and B”.
  • At least one of A, B and C means “only A”, “only B”, “only C”, or “A, B and C”. It can mean “any combination of A, B and C.” Also, “at least one of A, B or C” or “at least one of A, B and/or C” means It may mean “at least one of A, B and C.”
  • control information may be proposed as an example of “control information.”
  • control information in this specification is not limited to “PDCCH,” and “PDCCH” may be proposed as an example of “control information.”
  • PDCCH control information
  • a higher layer parameter may be a parameter set for the terminal, set in advance, or defined in advance.
  • a base station or network can transmit upper layer parameters to the terminal.
  • upper layer parameters may be transmitted through radio resource control (RRC) signaling or medium access control (MAC) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA can be implemented with wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA can be implemented with wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • E-UTRA evolved UTRA
  • IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.
  • UTRA is part of the universal mobile telecommunications system (UMTS).
  • 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC in the uplink.
  • -Adopt FDMA LTE-A (advanced) is the evolution of 3GPP LTE.
  • 5G NR is a successor technology to LTE-A and is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability.
  • 5G NR can utilize all available spectrum resources, including low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.
  • 6G (wireless communications) systems require (i) very high data rates per device, (ii) very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) battery- The goal is to reduce the energy consumption of battery-free IoT devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities.
  • the vision of the 6G system can be four aspects such as intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. That is, Table 1 is a table showing an example of the requirements of a 6G system.
  • the 6G system includes eMBB (Enhanced mobile broadband), URLLC (Ultra-reliable low latency communications), mMTC (massive machine-type communication), AI integrated communication, Tactile internet, High throughput, High network capacity, High energy efficiency, Low backhaul and It can have key factors such as access network congestion and enhanced data security.
  • eMBB Enhanced mobile broadband
  • URLLC Ultra-reliable low latency communications
  • mMTC massive machine-type communication
  • AI integrated communication Tactile internet, High throughput, High network capacity, High energy efficiency, Low backhaul and It can have key factors such as access network congestion and enhanced data security.
  • Figure 1 shows a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure.
  • the embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.
  • the 6G system is expected to have simultaneous wireless communication connectivity that is 50 times higher than that of the 5G wireless communication system.
  • URLLC a key feature of 5G, will become an even more important technology in 6G communications by providing end-to-end delay of less than 1ms.
  • the 6G system will have much better volumetric spectral efficiency, unlike the frequently used area spectral efficiency.
  • 6G systems can provide ultra-long battery life and advanced battery technologies for energy harvesting, so mobile devices in 6G systems will not need to be separately charged.
  • New network characteristics in 6G may include:
  • 6G is expected to be integrated with satellites to serve the global mobile constellation. Integration of terrestrial, satellite and aerial networks into one wireless communication system is very important for 6G.
  • 6G wireless networks will deliver power to charge the batteries of devices such as smartphones and sensors. Therefore, wireless information and energy transfer (WIET) will be integrated.
  • WIET wireless information and energy transfer
  • Small cell networks The idea of small cell networks was introduced to improve received signal quality resulting in improved throughput, energy efficiency and spectral efficiency in cellular systems. As a result, small cell networks are an essential feature for 5G and Beyond 5G (5GB) communications systems. Therefore, the 6G communication system also adopts the characteristics of a small cell network.
  • Ultra-dense heterogeneous networks will be another important characteristic of the 6G communication system. Multi-tier networks comprised of heterogeneous networks improve overall QoS and reduce costs.
  • Backhaul connections are characterized by high-capacity backhaul networks to support high-capacity traffic.
  • High-speed fiber and free-space optics (FSO) systems may be possible solutions to this problem.
  • High-precision localization (or location-based services) through communication is one of the functions of the 6G wireless communication system. Therefore, radar systems will be integrated with 6G networks.
  • Softwarization and virtualization are two important features that form the basis of the design process in 5GB networks to ensure flexibility, reconfigurability, and programmability. Additionally, billions of devices may be shared on a shared physical infrastructure.
  • AI Artificial Intelligence
  • 5G systems will support partial or very limited AI.
  • 6G systems will be AI-enabled for full automation.
  • Advances in machine learning will create more intelligent networks for real-time communications in 6G.
  • Introducing AI in communications can simplify and improve real-time data transmission.
  • AI can use numerous analytics to determine how complex target tasks are performed. In other words, AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly by using AI.
  • AI can also play an important role in M2M, machine-to-human and human-to-machine communications. Additionally, AI can enable rapid communication in BCI (Brain Computer Interface).
  • AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.
  • THz Communication Data transmission rate can be increased by increasing bandwidth. This can be accomplished by using sub-THz communications with wide bandwidth and applying advanced massive MIMO technology.
  • THz waves also known as submillimeter radiation, typically represent a frequency band between 0.1 THz and 10 THz with a corresponding wavelength in the range 0.03 mm-3 mm.
  • the 100GHz-300GHz band range (Sub THz band) is considered the main part of the THz band for cellular communications.
  • Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity.
  • 300GHz-3THz is in the far infrared (IR) frequency band.
  • the 300GHz-3THz band is part of the wideband, but it is at the border of the wideband and immediately behind the RF band. Therefore, this 300 GHz-3 THz band shows similarities to RF.
  • Figure 2 shows an electromagnetic spectrum, according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) widely available bandwidth to support very high data rates, (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beamwidth produced by a highly directional antenna reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array techniques that can overcome range limitations.
  • NTN Non-Terrestrial Networks
  • Unmanned Aerial Vehicle UAV
  • UAV Unmanned Aerial Vehicle
  • the BS entity is installed on the UAV to provide cellular connectivity.
  • UAVs have certain features not found in fixed BS infrastructure, such as easy deployment, strong line-of-sight links, and controlled degrees of freedom for mobility.
  • emergency situations such as natural disasters, the deployment of terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments.
  • UAVs can easily handle these situations.
  • UAV will become a new paradigm in the wireless communication field. This technology facilitates three basic requirements of wireless networks: eMBB, URLLC, and mMTC.
  • UAVs can also support several purposes, such as improving network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, accident monitoring, etc. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.
  • V2X Vehicle to Everything
  • V2V Vehicle to Vehicle
  • V2I Vehicle to Infrastructure
  • 5G NR is mainly described, but the technical idea according to an embodiment of the present disclosure is not limited thereto. Various embodiments of the present disclosure can also be applied to 6G communication systems.
  • Figure 3 shows the structure of an NR system according to an embodiment of the present disclosure.
  • the embodiment of FIG. 3 may be combined with various embodiments of the present disclosure.
  • NG-RAN Next Generation - Radio Access Network
  • the base station 20 may include a next generation-Node B (gNB) and/or an evolved-NodeB (eNB).
  • the terminal 10 may be fixed or mobile, and may be referred to by other terms such as MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), and wireless device. It can be called .
  • a base station may be a fixed station that communicates with the terminal 10, and may be called other terms such as BTS (Base Transceiver System) or Access Point.
  • BTS Base Transceiver System
  • the embodiment of FIG. 3 illustrates a case including only gNB.
  • the base stations 20 may be connected to each other through an Xn interface.
  • the base station 20 can be connected to the 5th generation core network (5G Core Network: 5GC) and the NG interface. More specifically, the base station 20 may be connected to an access and mobility management function (AMF) 30 through an NG-C interface, and may be connected to a user plane function (UPF) 30 through an NG-U interface.
  • AMF access and mobility management function
  • UPF user plane function
  • the layers of the Radio Interface Protocol between the terminal and the network are L1 (layer 1, first layer) based on the lower three layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. layer), L2 (layer 2, layer 2), and L3 (layer 3, layer 3).
  • OSI Open System Interconnection
  • layer 2 layer 2, layer 2
  • L3 layer 3, layer 3
  • the physical layer belonging to the first layer provides information transfer service using a physical channel
  • the RRC (Radio Resource Control) layer located in the third layer provides radio resources between the terminal and the network. plays a role in controlling.
  • the RRC layer exchanges RRC messages between the terminal and the base station.
  • Figure 4 shows a radio protocol architecture, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 4 may be combined with various embodiments of the present disclosure.
  • Figure 4 (a) shows the wireless protocol stack of the user plane for Uu communication
  • Figure 4 (b) shows the wireless protocol of the control plane for Uu communication.
  • Figure 4(c) shows the wireless protocol stack of the user plane for SL communication
  • Figure 4(d) shows the wireless protocol stack of the control plane for SL communication.
  • the physical layer provides information transmission services to upper layers using a physical channel.
  • the physical layer is connected to the upper layer, the MAC (Medium Access Control) layer, through a transport channel.
  • Data moves between the MAC layer and the physical layer through a transport channel. Transmission channels are classified according to how and with what characteristics data is transmitted through the wireless interface.
  • the physical channel can be modulated using OFDM (Orthogonal Frequency Division Multiplexing), and time and frequency are used as radio resources.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the MAC layer provides services to the radio link control (RLC) layer, an upper layer, through a logical channel.
  • the MAC layer provides a mapping function from multiple logical channels to multiple transport channels. Additionally, the MAC layer provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel.
  • the MAC sublayer provides data transmission services on logical channels.
  • the RLC layer performs concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs).
  • SDUs RLC Service Data Units
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM automatic repeat request
  • the Radio Resource Control (RRC) layer is defined only in the control plane.
  • the RRC layer is responsible for controlling logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers.
  • RB is used in the first layer (physical layer or PHY layer) and second layer (MAC layer, RLC layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer) to transfer data between the terminal and the network. It refers to the logical path provided by .
  • the functions of the PDCP layer in the user plane include forwarding, header compression, and ciphering of user data.
  • the functions of the PDCP layer in the control plane include forwarding and encryption/integrity protection of control plane data.
  • the SDAP Service Data Adaptation Protocol
  • the SDAP layer performs mapping between QoS flows and data radio bearers, and marking QoS flow identifiers (IDs) in downlink and uplink packets.
  • Setting an RB means the process of defining the characteristics of the wireless protocol layer and channel and setting each specific parameter and operation method to provide a specific service.
  • RB can be further divided into SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer).
  • SRB is used as a path to transmit RRC messages in the control plane
  • DRB is used as a path to transmit user data in the user plane.
  • the terminal If an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state. Otherwise, it is in the RRC_IDLE state.
  • the RRC_INACTIVE state has been additionally defined, and a UE in the RRC_INACTIVE state can release the connection with the base station while maintaining the connection with the core network.
  • Downlink transmission channels that transmit data from the network to the terminal include a BCH (Broadcast Channel) that transmits system information and a downlink SCH (Shared Channel) that transmits user traffic or control messages.
  • BCH Broadcast Channel
  • SCH Shared Channel
  • uplink transmission channels that transmit data from the terminal to the network include RACH (Random Access Channel), which transmits initial control messages, and uplink SCH (Shared Channel), which transmits user traffic or control messages.
  • Logical channels located above the transmission channel and mapped to the transmission channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic). Channel), etc.
  • BCCH Broadcast Control Channel
  • PCCH Paging Control Channel
  • CCCH Common Control Channel
  • MCCH Multicast Control Channel
  • MTCH Multicast Traffic. Channel
  • Figure 5 shows the structure of a radio frame of NR, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 5 may be combined with various embodiments of the present disclosure.
  • NR can use radio frames in uplink and downlink transmission.
  • a wireless frame has a length of 10ms and can be defined as two 5ms half-frames (HF).
  • a half-frame may include five 1ms subframes (Subframe, SF).
  • a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined according to subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • Each slot may contain 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP).
  • each slot may contain 14 symbols.
  • each slot can contain 12 symbols.
  • the symbol may include an OFDM symbol (or CP-OFDM symbol), a single carrier-FDMA (SC-FDMA) symbol (or a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).
  • OFDM symbol or CP-OFDM symbol
  • SC-FDMA single carrier-FDMA
  • DFT-s-OFDM Discrete Fourier Transform-spread-OFDM
  • Table 2 shows the number of symbols per slot (N slot symb ), the number of slots per frame (N frame,u slot ), and the number of slots per subframe according to the SCS setting (u) when normal CP or extended CP is used.
  • N slot symb the number of symbols per slot
  • N frame,u slot the number of slots per frame
  • u the number of slots per subframe according to the SCS setting (u) when normal CP or extended CP is used.
  • OFDM(A) numerology eg, SCS, CP length, etc.
  • OFDM(A) numerology eg, SCS, CP length, etc.
  • the (absolute time) interval of time resources e.g., subframes, slots, or TTI
  • TU Time Unit
  • multiple numerologies or SCSs can be supported to support various 5G services. For example, if SCS is 15kHz, a wide area in traditional cellular bands can be supported, and if SCS is 30kHz/60kHz, dense-urban, lower latency latency) and wider carrier bandwidth may be supported. For SCS of 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.
  • the NR frequency band can be defined as two types of frequency ranges.
  • the two types of frequency ranges may be FR1 and FR2.
  • the values of the frequency range may be changed, for example, the frequency ranges of the two types may be as shown in Table 3 below.
  • FR1 may mean "sub 6GHz range”
  • FR2 may mean “above 6GHz range” and may be called millimeter wave (mmW).
  • mmW millimeter wave
  • FR1 may include a band of 410MHz to 7125MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. Unlicensed bands can be used for a variety of purposes, for example, for communications for vehicles (e.g., autonomous driving).
  • Figure 6 shows the slot structure of an NR frame according to an embodiment of the present disclosure.
  • the embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.
  • a slot includes a plurality of symbols in the time domain.
  • one slot may include 14 symbols, but in the case of extended CP, one slot may include 12 symbols.
  • one slot may include 7 symbols, but in the case of extended CP, one slot may include 6 symbols.
  • a carrier wave includes a plurality of subcarriers in the frequency domain.
  • a Resource Block (RB) may be defined as a plurality (eg, 12) consecutive subcarriers in the frequency domain.
  • BWP (Bandwidth Part) can be defined as a plurality of consecutive (P)RB ((Physical) Resource Blocks) in the frequency domain and can correspond to one numerology (e.g. SCS, CP length, etc.) there is.
  • a carrier wave may include up to N (e.g., 5) BWPs. Data communication can be performed through an activated BWP.
  • Each element may be referred to as a Resource Element (RE) in the resource grid, and one complex symbol may be mapped.
  • RE Resource Element
  • BWP Bandwidth Part
  • a Bandwidth Part may be a contiguous set of physical resource blocks (PRBs) in a given numerology.
  • PRB physical resource blocks
  • a PRB may be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.
  • CRBs common resource blocks
  • the BWP may be at least one of an active BWP, an initial BWP, and/or a default BWP.
  • the terminal may not monitor downlink radio link quality in DL BWPs other than the active DL BWP on the primary cell (PCell).
  • the UE may not receive PDCCH, physical downlink shared channel (PDSCH), or reference signal (CSI-RS) (except RRM) outside of the active DL BWP.
  • the UE may not trigger Channel State Information (CSI) reporting for an inactive DL BWP.
  • the UE may not transmit a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) outside the active UL BWP.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the initials BWP can be given as a set of contiguous RBs for the remaining minimum system information (RMSI) control resource set (CORESET) (established by the physical broadcast channel (PBCH)).
  • RMSI remaining minimum system information
  • CORESET control resource set
  • PBCH physical broadcast channel
  • SIB system information block
  • the default BWP may be set by a higher layer.
  • the initial value of the default BWP may be the initials DL BWP.
  • DCI downlink control information
  • BWP can be defined for SL.
  • the same SL BWP can be used for transmission and reception.
  • the transmitting terminal may transmit an SL channel or SL signal on a specific BWP, and the receiving terminal may receive the SL channel or SL signal on the specific BWP.
  • the SL BWP may be defined separately from the Uu BWP, and the SL BWP may have separate configuration signaling from the Uu BWP.
  • the terminal may receive settings for SL BWP from the base station/network.
  • the terminal may receive settings for Uu BWP from the base station/network.
  • SL BWP can be set (in advance) for out-of-coverage NR V2X terminals and RRC_IDLE terminals within the carrier. For a UE in RRC_CONNECTED mode, at least one SL BWP may be activated within the carrier.
  • FIG. 7 shows an example of BWP, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. In the embodiment of Figure 7, it is assumed that there are three BWPs.
  • a common resource block may be a carrier resource block numbered from one end of the carrier band to the other end.
  • the PRB may be a numbered resource block within each BWP.
  • Point A may indicate a common reference point for the resource block grid.
  • BWP can be set by point A, offset from point A (N start BWP ), and bandwidth (N size BWP ).
  • point A may be an external reference point of the carrier's PRB to which subcarriers 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned.
  • the offset may be the PRB interval between point A and the lowest subcarrier in a given numerology.
  • bandwidth may be the number of PRBs in a given numerology.
  • SSS Primary Sidelink Synchronization Signal
  • SSSS Secondary Sidelink Synchronization Signal
  • the PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal)
  • S-SSS Sidelink Secondary Synchronization Signal
  • length-127 M-sequences can be used for S-PSS
  • length-127 Gold sequences can be used for S-SSS.
  • the terminal can detect the first signal and obtain synchronization using S-PSS.
  • the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect the synchronization signal ID.
  • PSBCH Physical Sidelink Broadcast Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the basic information includes information related to SLSS, duplex mode (DM), TDD UL/DL (Time Division Duplex Uplink/Downlink) configuration, resource pool related information, type of application related to SLSS, This may be subframe offset, broadcast information, etc.
  • the payload size of PSBCH may be 56 bits, including a 24-bit Cyclic Redundancy Check (CRC).
  • S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL Synchronization Signal (SL SS)/PSBCH block, hereinafter referred to as Sidelink-Synchronization Signal Block (S-SSB)).
  • the S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel)/PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth is (pre-set) SL BWP (Sidelink BWP).
  • the bandwidth of S-SSB may be 11 RB (Resource Block).
  • PSBCH may span 11 RB.
  • the frequency position of the S-SSB can be set (in advance). Therefore, the UE does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.
  • Figure 8 shows a procedure in which a terminal performs V2X or SL communication depending on the transmission mode, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.
  • the transmission mode may be referred to as a mode or resource allocation mode.
  • the transmission mode in LTE may be referred to as the LTE transmission mode
  • the transmission mode in NR may be referred to as the NR resource allocation mode.
  • Figure 8(a) shows terminal operations related to LTE transmission mode 1 or LTE transmission mode 3.
  • Figure 8(a) shows UE operations related to NR resource allocation mode 1.
  • LTE transmission mode 1 can be applied to general SL communication
  • LTE transmission mode 3 can be applied to V2X communication.
  • Figure 8(b) shows terminal operations related to LTE transmission mode 2 or LTE transmission mode 4.
  • Figure 8(b) shows UE operations related to NR resource allocation mode 2.
  • the base station may schedule SL resources to be used by the terminal for SL transmission.
  • the base station may transmit information related to SL resources and/or information related to UL resources to the first terminal.
  • the UL resources may include PUCCH resources and/or PUSCH resources.
  • the UL resource may be a resource for reporting SL HARQ feedback to the base station.
  • the first terminal may receive information related to dynamic grant (DG) resources and/or information related to configured grant (CG) resources from the base station.
  • CG resources may include CG Type 1 resources or CG Type 2 resources.
  • the DG resource may be a resource that the base station configures/allocates to the first terminal through downlink control information (DCI).
  • the CG resource may be a (periodic) resource that the base station configures/allocates to the first terminal through a DCI and/or RRC message.
  • the base station may transmit an RRC message containing information related to the CG resource to the first terminal.
  • the base station may transmit an RRC message containing information related to the CG resource to the first terminal, and the base station may send a DCI related to activation or release of the CG resource. It can be transmitted to the first terminal.
  • the first terminal may transmit a PSCCH (eg, Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling.
  • a PSCCH eg., Sidelink Control Information (SCI) or 1st-stage SCI
  • the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • HARQ feedback information eg, NACK information or ACK information
  • the first terminal may transmit/report HARQ feedback information to the base station through PUCCH or PUSCH.
  • the HARQ feedback information reported to the base station may be information that the first terminal generates based on HARQ feedback information received from the second terminal.
  • the HARQ feedback information reported to the base station may be information that the first terminal generates based on preset rules.
  • the DCI may be a DCI for scheduling of SL.
  • the format of the DCI may be DCI format 3_0 or DCI format 3_1.
  • the terminal can determine the SL transmission resource within the SL resource set by the base station/network or within the preset SL resource.
  • the set SL resource or preset SL resource may be a resource pool.
  • the terminal can autonomously select or schedule resources for SL transmission.
  • the terminal can self-select a resource from a set resource pool and perform SL communication.
  • the terminal may perform sensing and resource (re)selection procedures to select resources on its own within the selection window.
  • the sensing may be performed on a subchannel basis.
  • the first terminal that has selected a resource within the resource pool may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1 st -stage SCI) to the second terminal using the resource.
  • a PSCCH e.g., Sidelink Control Information (SCI) or 1 st -stage SCI
  • the first terminal may transmit a PSSCH (e.g., 2 nd -stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • the first terminal may transmit an SCI to the second terminal on the PSCCH.
  • the first terminal may transmit two consecutive SCIs (eg, 2-stage SCI) on the PSCCH and/or PSSCH to the second terminal.
  • the second terminal can decode two consecutive SCIs (eg, 2-stage SCI) to receive the PSSCH from the first terminal.
  • the SCI transmitted on the PSCCH may be referred to as 1 st SCI, 1st SCI, 1 st -stage SCI, or 1 st -stage SCI format
  • the SCI transmitted on the PSSCH may be referred to as 2 nd SCI, 2nd SCI, 2 It can be referred to as nd -stage SCI or 2 nd -stage SCI format.
  • the 1 st -stage SCI format may include SCI format 1-A
  • the 2 nd -stage SCI format may include SCI format 2-A and/or SCI format 2-B.
  • SCI format 1-A is used for scheduling of PSSCH and 2nd -stage SCI on PSSCH.
  • the following information is transmitted using SCI format 1-A.
  • Time resource allocation - 5 bits if the value of the upper layer parameter sl-MaxNumPerReserve is set to 2; Otherwise, 9 bits if the value of the upper layer parameter sl-MaxNumPerReserve is set to 3.
  • N rsv_period is the number of entries in the upper layer parameter sl-ResourceReservePeriodList when the upper layer parameter sl-MultiReserveResource is set; Otherwise, bit 0
  • N pattern is the number of DMRS patterns set by the upper layer parameter sl-PSSCH-DMRS-TimePatternList
  • Additional MCS Table indicator - 1 bit if one MCS table is set by the upper layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are set by the upper layer parameter sl-Additional-MCS-Table; Otherwise bit 0
  • SCI format 2-A is used for decoding of PSSCH. It is used.
  • the following information is transmitted via SCI format 2-A.
  • SCI format 2-B is used for decoding of PSSCH and is used with HARQ operation when HARQ-ACK information includes only NACK or when there is no feedback of HARQ-ACK information.
  • the following information is transmitted via SCI format 2-B.
  • the first terminal can receive the PSFCH.
  • the first terminal and the second terminal may determine PSFCH resources, and the second terminal may transmit HARQ feedback to the first terminal using the PSFCH resource.
  • the first terminal may transmit SL HARQ feedback to the base station through PUCCH and/or PUSCH.
  • Figure 9 shows three cast types, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.
  • Figure 9(a) shows broadcast type SL communication
  • Figure 9(b) shows unicast type SL communication
  • Figure 9(c) shows groupcast type SL communication.
  • a terminal can perform one-to-one communication with another terminal.
  • the terminal can perform SL communication with one or more terminals within the group to which it belongs.
  • SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, etc.
  • Terminal power saving techniques include terminal adaptation to traffic and power consumption characteristics, adaptation to changes in frequency/time, adaptation to antennas, adaptation to DRX (discontinuous reception) settings, and adaptation to terminal processing capabilities. , adaptation to reduce PDCCH monitoring/decoding, power saving signal/channel/procedure to trigger adaptation to UE power consumption, power consumption reduction in RRM measurement, etc. can be considered.
  • DRX Discontinuous Reception
  • Type of signals UE procedure Step 1 RRC signaling (MAC-CellGroupConfig) - Receive DRX settings information Step 2 MAC CE ((Long) DRX command MAC CE) - Receive DRX command Step 3 - PDCCH monitoring during the on-duration of the DRX cycle
  • Figure 10 shows an example of a DRX cycle, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.
  • the terminal uses DRX in RRC_IDLE state and RRC_INACTIVE state to reduce power consumption.
  • DRX When DRX is configured, the terminal performs DRX operations according to the DRX configuration information.
  • a terminal operating as a DRX repeatedly turns reception tasks on and off.
  • the terminal when DRX is set, the terminal attempts to receive PDCCH, a downlink channel, only within a preset time interval and does not attempt to receive PDCCH within the remaining time interval.
  • the time interval in which the terminal must attempt to receive PDCCH is called on-duration, and the on-duration interval is defined once per DRX cycle.
  • the UE can receive DRX configuration information from the gNB through RRC signaling and operate as DRX through reception of a (long) DRX command MAC CE.
  • DRX configuration information may be included in MAC-CellGroupConfig .
  • IE MAC-CellGroupConfig can be used to set MAC parameters for a cell group, including DRX.
  • the DRX command MAC CE or long DRX command MAC CE is identified by a MAC PDU subheader with a logical channel ID (LCID). It has a fixed size of 0 bits.
  • LCID logical channel ID
  • Table 9 illustrates the LCID values for DL-SCH.
  • DRX Bandwidth Adaptation
  • - Inactivity timer This is the time period in which the terminal waits for successful PDCCH decoding from the last successful PDCCH decoding, and in case of failure, the terminal goes back to sleep.
  • the UE must restart the inactivity timer after a single successful decoding of the PDCCH for only the first transmission (i.e. not for retransmission).
  • Retransmission timer This is the time period during which retransmission is expected.
  • the MAC entity may be expressed as a terminal or a terminal's MAC entity.
  • the MAC entity is a DRX that controls the PDCCH monitoring activities of the terminal for the C-RNTI (radio network temporary identifier), CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, and TPC-SRS-RNTI of the MAC entity. Can be set by RRC with function.
  • the MAC entity When using DRX operation, the MAC entity must monitor the PDCCH. In the RRC_CONNECTED state, if DRX is configured, the MAC entity can monitor the PDCCH discontinuously using DRX operation. Otherwise, the MAC entity must continuously monitor the PDCCH.
  • RRC controls DRX operation by setting parameters of DRX configuration information.
  • the active time includes the following times.
  • Type-0-triggered SRS is not transmitted.
  • the MAC entity Regardless of whether the MAC entity monitors the PDCCH or not, the MAC entity transmits HARQ feedback and type-1-triggred SRS when expected.
  • the MAC entity does not need to monitor the PDCCH.
  • the conventional NR-U (unlicensed spectrum) supports a communication method between a terminal and a base station in an unlicensed band.
  • Rel-18 plans to support a mechanism that can support communication in the unlicensed band even between sidelink terminals.
  • a channel may refer to a set of frequency axis resources that perform Listen-Before-Talk (LBT).
  • LBT Listen-Before-Talk
  • a channel may mean a 20 MHz LBT bandwidth and may have the same meaning as an RB set.
  • the RB set may be defined in section 7 of 3GPP TS 38.214 V17.0.0.
  • CO channel occupancy
  • CO channel occupancy
  • COT channel occupancy time
  • COT sharing may refer to time axis resources acquired by a base station or terminal after successful LBT.
  • CO can be shared between the base station (or terminal) that acquired the CO and the terminal (or base station), and this can be referred to as COT sharing.
  • this may be referred to as gNB-initiated COT or UE-initiated COT.
  • Figure 11 shows an example of a wireless communication system supporting an unlicensed band, according to an embodiment of the present disclosure.
  • Figure 11 may include an unlicensed spectrum (NR-U) wireless communication system.
  • NR-U unlicensed spectrum
  • the embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.
  • a cell operating in a licensed band can be defined as an LCell, and the carrier of the LCell can be defined as a (DL/UL/SL) LCC.
  • a cell operating in an unlicensed band hereinafter referred to as U-band
  • U-band a cell operating in an unlicensed band
  • UCell a cell operating in an unlicensed band
  • U-band can be defined as UCell
  • the carrier of UCell can be defined as (DL/UL/SL) UCC.
  • the carrier/carrier-frequency of a cell may mean the operating frequency (e.g., center frequency) of the cell.
  • Cells/carriers e.g., CC are collectively referred to as cells.
  • the LCC may be set as a Primary CC (PCC) and the UCC may be set as a Secondary CC (SCC).
  • PCC Primary CC
  • SCC Secondary CC
  • the terminal and the base station can transmit and receive signals through one UCC or multiple UCCs combined with carrier waves. In other words, the terminal and the base station can transmit and receive signals only through UCC(s) without LCC.
  • PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supported in UCell.
  • the base station may be replaced by a terminal.
  • PSCCH, PSSCH, PSFCH, S-SSB transmission, etc. may be supported in UCell.
  • Consists of consecutive RBs on which a channel access procedure is performed in a shared spectrum may refer to a carrier or part of a carrier.
  • CAP Channel Access Procedure
  • CAP may be referred to as Listen-Before-Talk (LBT).
  • Channel occupancy refers to the corresponding transmission(s) on the channel(s) by the base station/terminal after performing the channel access procedure.
  • COT Channel Occupancy Time
  • - DL transmission burst defined as a set of transmissions from the base station, with no gap exceeding 16us. Transmissions from the base station, separated by a gap exceeding 16us, are considered separate DL transmission bursts.
  • the base station may perform transmission(s) after the gap without sensing channel availability within the DL transmission burst.
  • - UL or SL transmission burst Defined as a set of transmissions from the terminal, with no gaps exceeding 16us. Transmissions from the terminal, separated by a gap exceeding 16us, are considered separate UL or SL transmission bursts. The UE may perform transmission(s) after the gap without sensing channel availability within the UL or SL transmission burst.
  • a discovery burst refers to a DL transmission burst containing a set of signal(s) and/or channel(s), defined within a (time) window and associated with a duty cycle.
  • a discovery burst is a transmission(s) initiated by a base station and includes PSS, SSS, and cell-specific RS (CRS), and may further include non-zero power CSI-RS.
  • a discovery burst is a transmission(s) initiated by a base station, comprising at least an SS/PBCH block, a CORESET for a PDCCH scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and/or a non-zero It may further include power CSI-RS.
  • Figure 12 shows a method of occupying resources within an unlicensed band, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.
  • a communication node within an unlicensed band must determine whether another communication node(s) is using a channel before transmitting a signal.
  • communication nodes within the unlicensed band may perform a Channel Attachment Procedure (CAP) to connect to the channel(s) on which the transmission(s) are performed.
  • CAP Channel Attachment Procedure
  • the channel access procedure may be performed based on sensing. For example, a communication node may first perform CS (Carrier Sensing) before transmitting a signal to check whether other communication node(s) is transmitting a signal.
  • CCA Cross Channel Assessment
  • the channel state can be judged as idle. If the channel state is determined to be dormant, the communication node can begin transmitting signals in the unlicensed band.
  • CAP can be replaced by LBT.
  • Table 10 illustrates the Channel Access Procedure (CAP) supported in NR-U.
  • Type Explanation DL Type 1 CAP CAP with random back-off - time duration spanned by the sensing slots that are sensed to be idle before a downlink transmission(s) is random Type 2 CAP -Type 2A, 2B, 2C CAP without random back-off - time duration spanned by sensing slots that are sensed to be idle before a downlink transmission(s) is deterministic UL or SL
  • Type 1 CAP CAP with random back-off - time duration spanned by the sensing slots that are sensed to be idle before an uplink or sidelink transmission(s) is random Type 2 CAP -Type 2A, 2B, 2C CAP without random back-off - time duration spanned by sensing slots that are sensed to be idle before an uplink or sidelink transmission(s) is deterministic
  • Type 1 also called Cat-4 LBT
  • Cat-4 LBT may be a random back-off based channel access procedure.
  • the contention window may change.
  • type 2 can be performed in case of COT sharing within COT acquired by gNB or UE.
  • LBT-SB (SubBand) (or RB set)
  • one cell (or carrier (e.g., CC)) or BWP set for the terminal may be configured as a wideband with a larger BW (BandWidth) than existing LTE.
  • BW requiring CCA based on independent LBT operation may be limited based on regulations, etc.
  • the sub-band (SB) in which individual LBT is performed is defined as LBT-SB
  • multiple LBT-SBs may be included in one wideband cell/BWP.
  • the RB set constituting the LBT-SB can be set through higher layer (eg, RRC) signaling. Therefore, based on (i) the BW of the cell/BWP and (ii) RB set allocation information, one cell/BWP may include one or more LBT-SBs.
  • Figure 13 shows a case where a plurality of LBT-SBs are included in an unlicensed band, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.
  • LBT-SB may be included in the BWP of a cell (or carrier).
  • LBT-SB may have a 20MHz band, for example.
  • LBT-SB consists of a plurality of consecutive (P)RBs in the frequency domain and may be referred to as a (P)RB set.
  • a guard band (GB) may be included between LBT-SBs. Therefore, BWP is ⁇ LBT-SB #0 (RB set #0) + GB #0 + LBT-SB #1 (RB set #1 + GB #1) + ... + LBT-SB #(K-1) It can be configured in the form (RB set (#K-1)) ⁇ .
  • the LBT-SB/RB index can be set/defined to start from a low frequency band and increase toward a high frequency band.
  • CAPC channel access priority class
  • the CAPCs of MAC CEs and radio bearers can be fixed or configurable to operate in FR1:
  • BSR Padding buffer status report
  • the base station When selecting the CAPC of a DRB, the base station considers the 5QI of all QoS flows multiplexed in the DRB and considers fairness between different traffic types and transmissions.
  • Table 9 shows which CAPC should be used for standardized 5QI, that is, the CAPC to use for a given QoS flow.
  • CAPC is defined as shown in the table below, and for non-standardized 5QI, the CAPC that best matches QoS characteristics should be used.
  • CAPC 5QI One 1, 3, 5, 65, 66, 67, 69, 70, 79, 80, 82, 83, 84, 85 2 2, 7, 71 3 4, 6, 8, 9, 72, 73, 74, 76 4 - NOTE: A lower CAPC value means higher priority.
  • a method of transmitting a downlink signal through an unlicensed band will be described.
  • a downlink signal transmission method through an unlicensed band can be applied to a sidelink signal transmission method through an unlicensed band.
  • the base station may perform one of the following channel access procedures (CAP) for downlink signal transmission in the unlicensed band.
  • CAP channel access procedures
  • Type 1 DL CAP the length of the time interval spanned by the sensing slot that is sensed as idle before transmission(s) is random.
  • Type 1 DL CAP can be applied to the following transmissions.
  • Figure 14 shows a CAP operation for downlink signal transmission through an unlicensed band of a base station, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.
  • the base station first senses whether the channel is in an idle state during the sensing slot period of the delay period (defer duration) T d , and then, when the counter N becomes 0, transmission can be performed (S134). At this time, counter N is adjusted by sensing the channel during the additional sensing slot period(s) according to the procedure below:
  • N init is a random value evenly distributed between 0 and CW p . Then move to step 4.
  • Step 3) (S150) Sensing the channel during the additional sensing slot section. At this time, if the additional sensing slot section is idle (Y), move to step 4. If not (N), move to step 5.
  • Step 5 (S160) Sensing the channel until a busy sensing slot is detected within the additional delay section T d or until all sensing slots within the additional delay section T d are detected as idle.
  • Step 6) If the channel is sensed as idle (Y) during all sensing slot sections of the additional delay section T d , the process moves to step 4. If not (N), move to step 5.
  • Table 12 shows m p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT) and allowed CW size applied to CAP according to channel access priority class. This illustrates that sizes change.
  • CWS content window size
  • maximum COT value etc. for each CAPC can be defined.
  • T d T f + m p * T sl .
  • the delay section T d consists of a section T f (16us) + m p consecutive sensing slot sections T sl (9us).
  • T f includes the sensing slot section T sl at the start of the 16us section.
  • CW p may be initialized to CW min,p , increased to the next higher allowed value, or left at the existing value, based on HARQ-ACK feedback for the previous DL burst.
  • Type 2 DL CAP the length of the time interval spanned by the sensing slot that is sensed as idle before transmission(s) is deterministic.
  • Type 2 DL CAP is divided into Type 2A/2B/2C DL CAP.
  • Type 2A DL CAP can be applied to the following transmissions.
  • T f includes a sensing slot at the start point of the section.
  • Type 2B DL CAP is applicable to transmission(s) performed by the base station after a 16us gap from transmission(s) by the terminal within the shared channel occupation time.
  • T f includes a sensing slot within the last 9us of the section.
  • Type 2C DL CAP is applicable to transmission(s) performed by the base station after a gap of up to 16us from transmission(s) by the terminal within the shared channel occupancy time. In Type 2C DL CAP, the base station does not sense the channel before transmitting.
  • a method for transmitting an uplink signal through an unlicensed band will be described.
  • a method of transmitting an uplink signal through an unlicensed band can be applied to a method of transmitting a sidelink signal through an unlicensed band.
  • the terminal performs type 1 or type 2 CAP for uplink signal transmission in the unlicensed band.
  • the terminal can perform CAP (eg, type 1 or type 2) set by the base station for uplink signal transmission.
  • the UE may include CAP type indication information in the UL grant (e.g., DCI format 0_0, 0_1) for scheduling PUSCH transmission.
  • Type 1 UL CAP the length of the time interval spanned by the sensing slot that is sensed as idle before transmission(s) is random.
  • Type 1 UL CAP can be applied to the following transmissions.
  • Figure 15 shows a type 1 CAP operation of a terminal for uplink signal transmission, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.
  • the terminal first senses whether the channel is in an idle state during the sensing slot period of the delay period (defer duration) T d , and then, when the counter N becomes 0, transmission can be performed (S234). At this time, counter N is adjusted by sensing the channel during the additional sensing slot period(s) according to the procedure below:
  • N init is a random value evenly distributed between 0 and CW p . Then move to step 4.
  • Step 3) Sensing the channel during the additional sensing slot section. At this time, if the additional sensing slot section is idle (Y), move to step 4. If not (N), move to step 5.
  • Step 5 (S260) Sensing the channel until a busy sensing slot is detected within the additional delay section T d or until all sensing slots within the additional delay section T d are detected as idle.
  • Step 6) If the channel is sensed as idle (Y) during all sensing slot sections of the additional delay section T d , the process moves to step 4. If not (N), move to step 5.
  • Table 13 illustrates that m p , minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW sizes applied to CAP vary depending on the channel access priority class. .
  • CWS content window size
  • maximum COT value etc. for each CAPC can be defined.
  • T d T f + m p * T sl .
  • the delay section T d consists of a section T f (16us) + m p consecutive sensing slot sections T sl (9us).
  • T f includes the sensing slot section T sl at the start of the 16us section.
  • Type 2 UL CAP the length of the time interval spanned by the sensing slot that is sensed as idle before transmission(s) is deterministic.
  • Type 2 UL CAP is divided into Type 2A/2B/2C UL CAP.
  • T short_dl 25us.
  • T f includes a sensing slot at the start of the section.
  • T f includes a sensing slot within the last 9us of the section.
  • type 2C UL CAP the terminal does not sense the channel before transmitting.
  • a terminal with uplink data to transmit can select a CAPC mapped to the 5QI of the data, and the terminal can select the parameters of the corresponding CACP (e.g., minimum contention window size (minimum contention window size) NR-U operation can be performed by applying contention window size, maximum contention window size, m p, etc.).
  • the terminal may select a random value between the minimum CW and maximum CW mapped to the CAPC and then select a Backoff Counter (BC).
  • BC may be a positive integer less than or equal to the random value.
  • the terminal that senses the channel decreases BC by 1 when the channel is idle.
  • T sl 9 usec
  • T f 16 usec
  • the terminal can perform data transmission by performing Type 2 LBT (e.g., Type 2A LBT, Type 2B LBT, Type 2C LBT) within the COT.
  • Type 2 LBT e.g., Type 2A LBT, Type 2B LBT, Type 2C LBT
  • Type 2A (also called Cat-2 LBT (one shot LBT) or one-shot LBT) may be a 25 usec one-shot LBT. In this case, transmission may begin immediately after idle sensing for a gap of at least 27 usec.
  • Type 2A can be used to initiate SSB and non-unicast DL information transmission. That is, the terminal can sense the channel for 25 usec within the COT, and if the channel is idle, the terminal can occupy the channel and attempt to transmit data.
  • Type 2B may be a 16 usec one-shot LBT.
  • transmission may begin immediately after idle sensing for a 16 usec gap. That is, the terminal can sense the channel for 16 usec within the COT, and if the channel is idle, the terminal can occupy the channel and attempt to transmit data.
  • LTB may not be performed.
  • transmission can start immediately after a gap of up to 16 usec and the channel may not be sensed before the transmission.
  • the duration of the transmission may be up to 584 usec.
  • the terminal can attempt to transmit after 16 usec without sensing, and the terminal can transmit for a maximum of 584 usec.
  • the terminal can perform LBT (Listen Before Talk)-based channel access operations. Before accessing a channel in an unlicensed band, the terminal determines whether the access channel is idle (e.g., the terminal does not occupy the channel, and terminals are able to connect to the channel and transmit data) or busy (e.g., , the channel is occupied and data transmission and reception operations are performed on the channel, and the terminal attempting to access the channel must check whether data transmission is not possible while the channel is busy. In other words, the operation of the terminal to check whether the channel is idle or busy can be called CCA (Clear Channel Assessment), and the terminal checks whether the channel is idle or busy during the CCA duration. ) You can check Hanji.
  • CCA Common Channel Assessment
  • NR-U Universal Terrestrial
  • a communication method between a terminal and a base station was supported in an unlicensed band.
  • a mechanism to support communication between SL (Sidelink) devices in the unlicensed band will be supported in Rel-18.
  • NR-U prior art may be as follows.
  • NR-U May refer to a set of frequency axis resources on which LBT is performed.
  • NR-U means 20 MHz LBT bandwidth and may have the same meaning as RB set.
  • CO Channel occupancy: This may refer to the time/frequency axis resources acquired by the base station or terminal after successful LBT.
  • COT Channel occupancy time
  • This may refer to the time axis resources acquired by the base station or terminal after successful LBT. Sharing is possible between the base station (or terminal) that acquired the CO and the terminal (or base station), and the operation may be referred to as COT sharing.
  • the initiating device it may be referred to as gNB-initiated COT or UE-initiated COT.
  • an LBT type (or channel access procedure) for DL/UL transmission is described.
  • Type 1 (can be referred to as Cat-4 LBT): Channel access procedure based on random back-off
  • Cat-4 This may mean that the contention window is variable.
  • Type 2 In case of COT sharing, it can be performed within the COT acquired by the gNB or UE.
  • Type 2A may be referred to as Cat-2 LBT (one-shot LBT) or one-shot LBT): 25 usec one-shot LBT
  • Type 2C may be referred to as Cat-1 LBT (LBT is not performed) or No LBT.
  • Transmission begins immediately after a gap of up to 16 usec, and the channel is not sensed before transmission.
  • the duration of transmission is up to 584 usec.
  • CAPC channel access priority class
  • the base station can set which CAPC corresponds to SRB0/1/3, and which CAPC corresponds to SRB2 or DRB.
  • CAPC is defined as shown in the table below, and for non-standardized 5QI, the CAPC that best matches QoS characteristics may be used.
  • Table 18 shows the mapping relationship between CAPC and 5QI.
  • CWS content window size
  • maximum COT value may be defined for each CAPC.
  • a terminal may perform a listen before talk (LBT)-based channel access operation in a sidelink unlicensed band.
  • LBT listen before talk
  • the terminal Before accessing a channel in an unlicensed band, the terminal must check whether the access channel is idle (a state in which the terminal does not occupy the channel, and terminals can access the channel and transmit data) or is busy (a state in which the channel is occupied and the corresponding channel is busy).
  • the terminal attempting to access the channel may need to check whether data transmission is not possible when the channel is busy. That is, the operation of the terminal checking whether the channel is idle or busy can be called CCA (Clear Channel Assessment), and the terminal can check whether the channel is idle or busy during the CCA period.
  • CCA Cross Channel Assessment
  • FIG. 16 shows contention operation for channels of LBE and FBE, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 16 may be combined with various embodiments of the present disclosure.
  • a dynamic channel access procedure (load based equipment, LBE) appears. For example, as soon as the channel becomes idle, the terminal competes with other unlicensed band terminals to immediately occupy the channel, and the terminal can transmit data after occupying the channel.
  • LBE load based equipment
  • a semi-static channel access procedure (frame based equipment, FBE) appears.
  • the terminal may operate at the last point within a synchronized frame boundary (or, Fixed Frame Period), e.g., at a certain time (or, at the starting point) before the next FFP starts. ) It competes with other unlicensed band terminals, and the terminal can transmit data after occupying the channel within a fixed frame period. Data transfer may need to complete before the next FFP begins.
  • type 2 LBT data transmission is possible when the channel is idle by sensing the channel for a certain short period of time without performing random backoff-based LBT
  • an operation of reporting COT information shared by a terminal to a base station or a counterpart terminal is proposed.
  • a terminal that generates a COT can share the COT it has secured with the other terminal.
  • a terminal that has created/secured a COT can deliver the COT it secured to the other terminal through an SCI, MAC CE, or PC5-RRC message.
  • the terminal when the terminal transmits the COT it has secured through SCI, it can transmit it to the terminal (a pair of L1 source ID and L1 destination ID) related to the unicast link. Or, for example, the terminal that created/secured the COT may transmit the COT it secured to the groupcast/broadcast destination terminal (groupcast/broadcast L1 destination ID).
  • the terminal when the terminal transmits the COT it has secured through MAC CE (e.g. SL COT (Channel Occupancy Time) information MAC CE), the destination for the unicast link (L1/L2 source ID and L1/L2 destination information) Pair of nation ID) can be transmitted to the terminal.
  • the terminal that created/secured the COT may transmit the COT it secured to the groupcast/broadcast destination terminal (groupcast/broadcast L1/L2 destination ID).
  • a terminal that has received a shared COT from the terminal that created the COT may perform a type 2 LBT operation after the transmission of the terminal that created the COT is completed within the shared COT.
  • the Type 2 LBT operation may include Type 2A, Type 2B LBT, and Type 2C LBT.
  • the terminal when the terminal performs a sensing operation and confirms that the channel is idle for a certain period of time, it can transmit the SL data to be transmitted within the shared COT.
  • the terminal can immediately transmit SL data without sensing for a certain period of time.
  • the COT generating terminal if the COT generating terminal generates the COT and the terminal receiving the shared COT does not successfully perform SL data transmission using the shared COT, it requests resetting of the COT, It is proposed that the terminal that has received a request to reset the COT resets the COT anew and shares it.
  • Figure 17 shows an example of an operation performed within a shared COT, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.
  • the terminal initiating the COT creates and shares the COT, and the terminal with the COT shared receives the COT and performs a short LBT within the COT to transmit SL data.
  • the short LBT may mean a type 2 series LBT, and the terminal performing short LBT performs sensing for a short period of time, rather than random backoff-based LBT, and immediately detects when the channel state is idle. SL data transmission can be performed.
  • the subsequent operation (COT reporting) of the terminal that has received the shared COT is proposed as follows.
  • terminal A can receive COT settings from its serving base station. Upon receiving the COT from the serving base station, terminal A can report COT information (via SCI, MAC CE, or PC5 RRC message) to terminal B with which it has unicast settings.
  • COT information via SCI, MAC CE, or PC5 RRC message
  • the counterpart terminal B (or the serving base station of terminal B) is a terminal that sets its own (terminal A) SL DRX settings
  • the counterpart terminal B (or the serving base station of terminal B) sets the COT and the terminal
  • the COT information can be referenced to align A's SL DRX settings (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer).
  • Terminal B when Terminal B receives COT information from Terminal A, Terminal B can report the COT information to its (Terminal B's) serving base station (Terminal B's serving base station that sets Terminal A's SL DRX settings).
  • Terminal B's serving base station records the received COT and UE A's SL DRX settings (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer). You can refer to the COT information above for sorting.
  • the base station or terminal can refer to the COT information not only for alignment between the COT and SL DRX settings, but also for alignment between the COT and other settings to be used by terminal A. there is.
  • the COT information reported by the terminal includes, in addition to the COT information, L2 source ID and destination ID information, QoS profile information, and/or SL-priority information of the terminal using the COT. may also be included.
  • terminal A when terminal A receives the COT to be used by itself (terminal A) from the base station (or terminal B), terminal A transfers the received COT information to another counterpart terminal C or terminal that has established a unicast connection with terminal A.
  • the other terminal can use its COT information.
  • the terminal that has received the COT information may perform its SL-U transmission with reference to the COT information of terminal A.
  • the terminal that received the COT information may not perform a transmission operation during the COT of terminal A.
  • the terminal that has received the COT information may perform a SL data transmission operation by performing random backoff-based LBT during the COT of terminal A.
  • the terminal that received the COT information is a terminal that sets the SL DRX settings of terminal A
  • the terminal that received the COT information may set the SL DRX settings of terminal A by referring to the COT information. .
  • the terminal receives (or sets) COT information to be used (for reception) from the other terminal (the other terminal that has established a unicast connection)
  • terminal A can receive a COT that it (terminal A) will use (for reception) from terminal B with which it has unicast settings. For example, when terminal A receives a COT configuration from terminal B, terminal A can report the configured COT information to its serving base station (via PUCCH, MAC CE, or RRC message: SidelinkUEInformation/UEAssistanceInformation).
  • the serving base station of terminal A refers to the COT information received from terminal A and sets the COT and SL DRX settings of terminal A (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset) , SL DRX retransmission timer), Uu DRX settings (e.g., DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) can be aligned.
  • SL DRX settings of terminal A e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, DRX slot offset, DRX retransmission timer
  • Uu DRX settings e.g., DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer
  • terminal A when terminal A receives the COT that it (terminal A) will use (for reception) from terminal B, terminal A sends its COT information to another terminal C or D that has established a unicast connection with terminal A.
  • the other terminal can use its COT information.
  • the terminal that has received the COT information may perform its SL-U transmission with reference to the COT information of terminal A.
  • the terminal that received the COT information may not perform a transmission operation during the COT of terminal A.
  • the terminal that has received the COT information may perform a SL data transmission operation by performing random backoff-based LBT during the COT of terminal A.
  • the terminal that received the COT information is a terminal that sets the SL DRX settings of terminal A
  • the terminal that received the COT information may set the SL DRX settings of terminal A by referring to the COT information. .
  • the COT information reported by the terminal may include, in addition to the COT information, L2 source ID and destination ID information, QoS profile information, and/or SL-priority information of the terminal using the COT. there is.
  • terminal A can receive the COT to be used (for reception) from the serving base station of terminal B (if terminal B is RRC CONNECTED with the serving base station) with which it has unicast settings. For example, if terminal B is in the RRC CONNECTED state with the serving base station, terminal B requests the base station to set terminal A's COT information (via PUCCH, MAC CE, Sidelink UE Information, UE Assistance Information, or other RRC message). You can. For example, when terminal B requests COT information of terminal A from the base station, the message transmitted includes the reason (COT request) value for requesting COT information and the L2 ID of the terminal using the COT (i.e., terminal A's COT information). L2 source ID or L2 source/destination of terminal B, or L2 source ID and destination ID of terminal B) may be included.
  • COT request the reason
  • the serving base station of terminal B can set the COT of terminal A, which has established a unicast configuration with terminal B, and transmit it to terminal B.
  • Terminal B can report (via SCI, MAC CE, and PC5 RRC messages) COT information to be used by Terminal A, received from the serving base station, to Terminal A.
  • terminal A can report the received COT information to its serving base station (via PUCCH, MAC CE, or RRC message: SidelinkUEInformation/UEAssistanceInformation). there is.
  • the serving base station of terminal A refers to the COT information of terminal A and sets the COT and SL DRX settings of terminal A (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, SL DRX retransmission timer), Uu DRX settings (e.g. DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) can be aligned.
  • SL DRX settings of terminal A e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset, SL DRX slot offset, DRX retransmission timer
  • Uu DRX settings e.g. DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer
  • the serving base station of terminal A may allocate a mode 1 grant (dynamic grant or configured grant) to terminal A by referring to the COT information of terminal A. That is, the serving base station can allocate a mode 1 grant (initial transmission grant or retransmission grant) within the COT section of UE A. Or, for example, the serving base station may allocate a mode 1 grant (initial transmission grant or retransmission grant) outside UE A's COT.
  • a mode 1 grant dynamic grant or configured grant
  • terminal A when terminal A receives a report from terminal B of the COT that it (terminal A) will use (for reception), terminal A sends its COT information to another terminal C or D that has established a unicast setting with terminal A.
  • the other terminal can use its COT information.
  • the terminal that has received the COT information may perform its SL-U transmission with reference to the COT information of terminal A.
  • the terminal that received the COT information may not perform a transmission operation during the COT of terminal A.
  • the terminal that has received the COT information may perform a SL data transmission operation by performing random backoff-based LBT during the COT of terminal A.
  • the terminal that received the COT information is a terminal that sets the SL DRX settings of terminal A
  • the terminal that received the COT information may set the SL DRX settings of terminal A by referring to the COT information. .
  • the COT information reported by the terminal may include, in addition to the COT information, L2 source ID and destination ID information, QoS profile information, and/or SL-priority information of the terminal using the COT. there is.
  • the terminal can secure the COT it will use by directly generating it and perform SL data transmission within the COT it has secured in the unlicensed band.
  • the terminal may report the COT to be used by the terminal to the base station (via PUCCH, MAC CE, and RRC messages).
  • the serving base station can finally decide and confirm whether or not to use the COT generated and secured by the terminal and inform the terminal (via PDCCH or RRC message).
  • the terminal performs type 2 LBT within the COT it has created and secured only when the base station allows its use, rather than performing random backoff-based LBT.
  • SL data transmission can be performed.
  • the terminal may perform SL data transmission by performing type 2 LBT within the COT it generates on its own without confirmation from the base station.
  • the COT information reported by the terminal may include, in addition to the COT information, L2 source ID and destination ID information, QoS profile information, and/or SL-priority information of the terminal using the COT. there is.
  • Figure 18 shows a procedure in which a terminal receiving COT sharing information uses COT, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.
  • the COT sharing terminal may mean a terminal that acquires (generates and/or receives from a base station) a COT.
  • the responding terminal may mean a terminal that receives COT sharing information.
  • the COT sharing terminal may transmit PSCCH and/or PSSCH to the responding terminal.
  • the COT sharing terminal may transmit COT sharing information to the responding terminal.
  • step S1810 may be performed before or after step S1820.
  • step S1810 may be performed simultaneously with step S1820. That is, COT sharing information, which is information about the COT interval, can be received by the responding terminal through the PSCCH and/or PSSCH transmission.
  • the source/destination ID of the COT sharing terminal may be transmitted to the responding terminal through the PSCCH and/or PSSCH transmission.
  • the responding terminal may determine whether to use the received COT interval for transmission of SL data. For example, the responding terminal may decide to use the COT section when the source ID of the COT sharing terminal and its destination ID are the same, and the destination ID of the COT sharing terminal and its source ID are the same. there is.
  • the responding terminal may perform channel sensing on transmission resources within the COT interval.
  • the channel sensing may include type 2 LBT operation described in this disclosure.
  • it is assumed that the result of the channel sensing is IDLE.
  • step S1850 since the result of the channel sensing is idle, the responding terminal may transmit SL data to the COT sharing terminal based on the transmission resources.
  • Figure 19 shows a procedure in which a terminal receiving COT sharing information uses COT, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 19 may be combined with various embodiments of the present disclosure.
  • the COT sharing terminal may mean a terminal that acquires (generates and/or receives from a base station) a COT.
  • the responding terminal may mean a terminal that receives COT sharing information.
  • the COT sharing terminal may transmit COT sharing information to the responding terminal.
  • the COT shared information may include the ID(s) of the terminal(s) that can use the COT in the COT shared information.
  • the ID(s) of the terminal(s) capable of using the COT may be a new ID that is different from the source/destination ID included in the SCI and/or MAC CE.
  • the ID(s) of the terminal(s) capable of using the COT is indicated through the source/destination ID field on the SCI. It may be a new ID that is different from the current ID.
  • the responding terminal may determine whether to use the received COT interval for transmission of SL data. For example, the responding terminal checks whether its ID is included in the ID(s) of the terminal(s) capable of using the COT, and determines whether its ID is the ID(s) of the terminal(s) capable of using the COT ( s), it may be decided to use the COT section.
  • the responding terminal may perform channel sensing on transmission resources within the COT interval.
  • the channel sensing may include type 2 LBT operation described in this disclosure.
  • it is assumed that the result of the channel sensing is IDLE.
  • step S1940 since the result of the channel sensing is idle, the responding terminal may transmit SL data to the COT sharing terminal based on the transmission resources.
  • a COT initiator may mean a COT generating terminal and/or a COT sharing terminal.
  • a responding terminal may mean a terminal that obtains information about the COT and uses the COT for SL communication.
  • a responding terminal associated with a shared COT may be a receiving terminal that is the target of the COT initiator's PSCCH/PSSCH transmission.
  • the responding terminal is a receiving terminal that is the target of the PSCCH/PSSCH transmission of the COT initiator: i) In the case of unicast from the COT initiator, the source and destination included in the SCI of the COT initiator When the ID is the same as the destination and source ID of the receiving terminal of the same unicast within the same COT; ii) In the case of group cast and broadcast, this may include a case where the destination ID included in the SCI of the COT initiator is the same as the destination ID of the receiving terminal.
  • a responding terminal associated with a shared COT may, if an additional ID in the COT shared information is supported in addition to the source and destination ID of the PSCCH/PSSCH transmission, add an additional ID included in the COT shared information from the COT initiator. It may be a terminal identified by ID.
  • the serving base station of the terminal refers to the COT information generated by the terminal and sets the terminal's COT and the terminal's SL DRX settings (e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset ( startoffset), SL DRX slot offset, SL DRX retransmission timer), Uu DRX settings (e.g. DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer) can be aligned.
  • SL DRX settings e.g., SL DRX cycle, SL on-duration timer, SL DRX start offset ( startoffset), SL DRX slot offset, SL DRX retransmission timer
  • Uu DRX settings e.g. DRX cycle, on-duration timer, DRX start offset, DRX slot offset, DRX retransmission timer
  • the terminal's serving base station may allocate a mode 1 grant (dynamic grant or configured grant) to the terminal by referring to the terminal's COT information. That is, the terminal's serving base station can allocate a mode 1 grant (initial transmission grant or retransmission grant) within the terminal's COT duration. Alternatively, the terminal's serving base station may allocate a mode 1 grant (initial transmission grant or retransmission grant) outside the terminal's COT interval.
  • a mode 1 grant dynamic grant or configured grant
  • the proposal of this disclosure is a solution that can be equally applied not only when the terminal receives COT settings from the base station or the counterpart terminal, but also when the terminal receives FBE setting (FFP information, FFP start offset) information from the base station or the counterpart terminal. You can.
  • the SL DRX Configuration mentioned in this disclosure may include at least one of the following parameters.
  • Uu DRX Configuration mentioned in this disclosure may include at least one of the following parameters.
  • the Uu DRX timer below mentioned in this disclosure can be used for the following purposes.
  • a transmitting terminal (a terminal supporting Uu DRX operation) performing sidelink communication based on sidelink resource allocation mode 1 receives PDCCH (or, DCI) can indicate a section where monitoring is not performed.
  • drx-RetransmissionTimerSL Timer A transmitting terminal that performs sidelink communication based on sidelink resource allocation mode 1 (a terminal that supports Uu DRX operation) monitors PDCCH (or DCI) from the base station for sidelink mode 1 resource allocation. It can indicate the section being performed.
  • the SL DRX timer below mentioned in this disclosure can be used for the following purposes.
  • SL DRX on-duration timer May indicate a period in which a terminal performing SL DRX operation must basically operate as an active time to receive the PSCCH/PSSCH of the other terminal.
  • SL DRX inactivity timer May indicate a section that extends the SL DRX on-duration section, which is a section in which a terminal performing SL DRX operation must basically operate as an active time to receive the PSCCH/PSSCH of the other terminal. That is, the SL DRX on-duration timer can be extended by the SL DRX inactivity timer period.
  • the terminal receives a PSCCH (1 st SCI and 2 nd SCI) for a new TB or a new packet (new PSSCH transmission) from the other terminal, the terminal starts the SL DRX inactivity timer to turn SL DRX on-
  • the duration timer can be extended.
  • SL DRX HARQ RTT Timer May indicate a period in which a terminal performing SL DRX operation operates in sleep mode until it receives a retransmission packet (or PSSCH assignment) transmitted by the other terminal. That is, when the terminal starts the SL DRX HARQ RTT timer, the terminal determines that the other terminal will not transmit an SL retransmission packet to itself until the SL DRX HARQ RTT timer expires and operates in sleep mode during the timer. You can. Alternatively, the terminal may not perform monitoring of the SL channel/signal transmitted by the transmitting terminal until the other terminal's SL DRX HARQ RTT timer expires.
  • SL DRX retransmission timer May indicate a section in which a terminal performing SL DRX operation operates as an active time to receive a retransmission packet (or PSSCH allocation) transmitted by the other terminal. For example, when the SL DRX HARQ RTT timer expires, the SL DRX retransmission timer may be started. During the timer period, the terminal can monitor the reception of a retransmitted SL packet (or PSSCH allocation) transmitted by the other terminal.
  • SL-CAPC SL-CAPC
  • SL-LBT types e.g. Type 1 LBT, Type 2A LBT, Type 2B LBT, Type It may be set specifically (or differently or independently) depending on whether 2C LBT), FBE (Frame Based LBT) is applied, LBE (Load Based LBT) is applied, etc.
  • whether to apply (some) of the proposed schemes/rules of this disclosure and/or related parameters may be determined by: resource pool (e.g., resource pool with PSFCH set, resource pool without PSFCH set); congestion, service priority (and/or type), QoS requirements (e.g. delay, reliability) or PQI, traffic type (e.g. (a)periodic generation), SL transmission resource allocation mode (mode 1, Mode 2), depending on the Tx profile (e.g., a Tx profile indicating that the service supports SL DRX operation, a Tx profile indicating that the service does not need to support SL DRX operation), etc., specifically (or differently, or can be set independently).
  • resource pool e.g., resource pool with PSFCH set, resource pool without PSFCH set
  • congestion e.g., service priority (and/or type), QoS requirements (e.g. delay, reliability) or PQI
  • traffic type e.g. (a)periodic generation
  • whether to apply the proposed rules of this disclosure depends on whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured), resource pool, and service/packet type.
  • QoS profile or QoS requirements e.g., URLLC/EMBB traffic, reliability, delay
  • PQI, PFI cast type (e.g., unicast, groupcast, broadcast), (resource pool) congestion level (e.g., CBR)
  • SL HARQ feedback method e.g., NACK Only feedback, ACK/NACK feedback
  • HARQ feedback enabled MAC PDU and/or HARQ feedback disabled)
  • pre-emption and/or re-evaluation
  • whether the proposals and proposed rules of this disclosure are applied may also be applied to mmWave SL operations.
  • additional IDs in addition to the L2 source/destination ID can be used for COT sharing operations, which has the effect of allowing more terminals to receive COT sharing.
  • Figure 20 shows a procedure in which a first device performs wireless communication, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 20 may be combined with various embodiments of the present disclosure.
  • the first device may receive COT (channel occupancy time) sharing information for the COT (channel occupancy time) section, including the first ID (identifier), from the second device.
  • COT channel occupancy time
  • the first device may decide to use the COT section based on the fact that the first ID is the same as the second ID of the first device.
  • the first device may perform channel sensing on transmission resources within the COT interval.
  • the first device may perform sidelink (SL) communication based on the result of the channel sensing.
  • SL sidelink
  • the COT sharing information and sidelink control information are received by a third device, and based on the third ID included in the SCI and the fourth ID of the third device, the third device It may be decided whether to use the COT section.
  • SCI sidelink control information
  • the SL communication may be the transmission of SL data.
  • the SL communication may be resource reselection or resource drop.
  • the first device reports the COT sharing information to the first base station; Obtain SL DRX (discontinuous reception) settings set based on the COT section; And the SL DRX settings may be transmitted to the second device.
  • SL DRX discontinuous reception
  • the COT section may be set from a second base station to the second device.
  • the SL DRX setting may be set to align with the COT section.
  • the activation time of the SL DRX setting may be the same as the COT section.
  • the DRX cycle of the SL DRX setting may be the same as the COT section.
  • the operation of obtaining the SL DRX settings may include: setting the SL DRX settings based on the COT interval.
  • the SL communication may be performed for the second device.
  • the COT sharing information may be received through a SCI, medium access control (MAC) control element (CE), or PC5 radio resource control (RRC) message.
  • SCI SCI
  • MAC medium access control
  • CE CE
  • RRC radio resource control
  • the COT sharing information may be received through SCI, and the first ID may not be included in the source ID field or destination ID field of the SCI.
  • the processor 102 of the first device 100 receives COT sharing information for the COT (channel occupancy time) section, including the first ID (identifier), from the second device 200.
  • the transceiver 106 can be controlled.
  • the processor 102 of the first device 100 may decide to use the COT section based on the fact that the first ID is the same as the second ID of the first device 100.
  • the processor 102 of the first device 100 may perform channel sensing on transmission resources within the COT section.
  • the processor 102 of the first device 100 may control the transceiver 106 to perform sidelink (SL) communication based on the results of the channel sensing.
  • SL sidelink
  • a first device that performs wireless communication may be provided.
  • the first device may include at least one transceiver; at least one processor; and at least one memory executable coupled to the at least one processor and recording instructions that cause the first device to perform operations based on execution by the at least one processor.
  • the operations include: receiving, from a second device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier); determining to use the COT section based on the first ID being the same as the second ID of the first device; Performing channel sensing on transmission resources within the COT section; And it may include performing sidelink (SL) communication based on the result of the channel sensing.
  • COT channel occupancy time
  • identifier a first ID
  • SL sidelink
  • the COT sharing information and sidelink control information are received by a third device, and based on the third ID included in the SCI and the fourth ID of the third device, the third device It may be decided whether to use the COT section.
  • SCI sidelink control information
  • the SL communication may be the transmission of SL data.
  • the SL communication may be resource reselection or resource drop.
  • the operations may include: reporting the COT sharing information to a first base station; Obtaining SL DRX (discontinuous reception) settings set based on the COT section; And it may further include transmitting the SL DRX settings to the second device.
  • the COT section may be set from a second base station to the second device.
  • the SL DRX setting may be set to align with the COT section.
  • the activation time of the SL DRX setting may be the same as the COT section.
  • the DRX cycle of the SL DRX setting may be the same as the COT section.
  • Obtaining the SL DRX settings may include: setting the SL DRX settings based on the COT interval.
  • the SL communication may be performed for the second device.
  • the COT sharing information may be received through a SCI, medium access control (MAC) control element (CE), or PC5 radio resource control (RRC) message.
  • SCI SCI
  • MAC medium access control
  • CE CE
  • RRC radio resource control
  • the COT sharing information may be received through SCI, and the first ID may not be included in the source ID field or destination ID field of the SCI.
  • a device configured to control a first terminal.
  • the device may include at least one processor; and at least one memory executable connectable to the at least one processor and recording instructions that cause the first terminal to perform operations based on execution by the at least one processor.
  • the operations include: receiving, from a second device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier); determining to use the COT section based on the first ID being the same as the second ID of the first device; Performing channel sensing on transmission resources within the COT section; And it may include performing sidelink (SL) communication based on the result of the channel sensing.
  • COT channel occupancy time
  • identifier a first ID
  • SL sidelink
  • a non-transitory computer readable storage medium recording instructions may be provided.
  • the above instructions when executed, cause a first device to: receive, from a second device, COT sharing information for a channel occupancy time (COT) interval, including a first identifier (ID); do; determine to use the COT section based on the first ID being the same as the second ID of the first device; Perform channel sensing on transmission resources within the COT section; And sidelink (SL) communication can be performed based on the results of the channel sensing.
  • COT channel occupancy time
  • ID first identifier
  • SL sidelink
  • Figure 21 shows a procedure in which a second device performs wireless communication, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 21 may be combined with various embodiments of the present disclosure.
  • the second device may transmit COT (channel occupancy time) sharing information for the COT (channel occupancy time) section, including the first ID (identifier), to the first device.
  • COT channel occupancy time
  • the COT section may be determined to be used for the first device.
  • the COT sharing information may be transmitted through sidelink control information (SCI), and the first ID may not be included in the source ID field or destination ID field of the SCI.
  • SCI sidelink control information
  • the processor 202 of the second device 200 transmits COT (channel occupancy time) sharing information for the COT (channel occupancy time) section, including the first ID (identifier), to the first device 100.
  • the transceiver 206 can be controlled. For example, based on the fact that the first ID is the same as the second ID of the first device 100, the COT section may be determined to be used for the first device 100.
  • a second device that performs wireless communication may be provided.
  • the second device may include at least one transceiver; at least one processor; and at least one memory executable coupled to the at least one processor and recording instructions that cause the second device to perform operations based on execution by the at least one processor.
  • the operations include: transmitting, to a first device, COT (channel occupancy time) sharing information for a COT (channel occupancy time) interval, including a first ID (identifier), wherein the first ID Based on that is the same as the second ID of the first device, the COT section may be determined to be used for the first device.
  • the COT sharing information may be transmitted through sidelink control information (SCI), and the first ID may not be included in the source ID field or destination ID field of the SCI.
  • SCI sidelink control information
  • Figure 22 shows a communication system 1, according to one embodiment of the present disclosure.
  • the embodiment of FIG. 22 may be combined with various embodiments of the present disclosure.
  • a communication system 1 to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network.
  • a wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication/wireless/5G device.
  • wireless devices include robots (100a), vehicles (100b-1, 100b-2), XR (eXtended Reality) devices (100c), hand-held devices (100d), and home appliances (100e). ), IoT (Internet of Thing) device (100f), and AI device/server (400).
  • vehicles may include vehicles equipped with wireless communication functions, autonomous vehicles, vehicles capable of inter-vehicle communication, etc.
  • the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
  • UAV Unmanned Aerial Vehicle
  • XR devices include AR (Augmented Reality)/VR (Virtual Reality)/MR (Mixed Reality) devices, HMD (Head-Mounted Device), HUD (Head-Up Display) installed in vehicles, televisions, smartphones, It can be implemented in the form of computers, wearable devices, home appliances, digital signage, vehicles, robots, etc.
  • Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., laptops, etc.).
  • Home appliances may include TVs, refrigerators, washing machines, etc.
  • IoT devices may include sensors, smart meters, etc.
  • a base station and network may also be implemented as wireless devices, and a specific wireless device 200a may operate as a base station/network node for other wireless devices.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of this specification may include Narrowband Internet of Things for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is limited to the above-mentioned names. no.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of the present specification may perform communication based on LTE-M technology.
  • LTE-M technology may be an example of LPWAN technology, and may be called various names such as enhanced Machine Type Communication (eMTC).
  • eMTC enhanced Machine Type Communication
  • LTE-M technologies include 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine. It can be implemented in at least one of various standards such as Type Communication, and/or 7) LTE M, and is not limited to the above-mentioned names.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of the present specification may include at least ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low power communication. It may include any one, and is not limited to the above-mentioned names.
  • ZigBee technology can create personal area networks (PAN) related to small/low-power digital communications based on various standards such as IEEE 802.15.4, and can be called by various names.
  • PAN personal area networks
  • Wireless devices 100a to 100f may be connected to the network 300 through the base station 200.
  • AI Artificial Intelligence
  • the network 300 may be configured using a 3G network, 4G (eg, LTE) network, or 5G (eg, NR) network.
  • Wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but may also communicate directly (e.g. sidelink communication) without going through the base station/network.
  • vehicles 100b-1 and 100b-2 may communicate directly (e.g.
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • an IoT device eg, sensor
  • another IoT device eg, sensor
  • another wireless device 100a to 100f
  • Wireless communication/connection may be established between the wireless devices (100a to 100f)/base station (200) and the base station (200)/base station (200).
  • wireless communication/connection includes various wireless connections such as uplink/downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g. relay, IAB (Integrated Access Backhaul)).
  • uplink/downlink communication 150a
  • sidelink communication 150b
  • inter-base station communication 150c
  • This can be achieved through technology (e.g., 5G NR).
  • a wireless device and a base station/wireless device, and a base station and a base station can transmit/receive wireless signals to each other.
  • wireless communication/connection (150a, 150b, 150c) can transmit/receive signals through various physical channels.
  • various signal processing processes e.g., channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.
  • resource allocation processes etc.
  • Figure 23 shows a wireless device according to an embodiment of the present disclosure.
  • the embodiment of FIG. 23 may be combined with various embodiments of the present disclosure.
  • the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various wireless access technologies (eg, LTE, NR).
  • ⁇ first wireless device 100, second wireless device 200 ⁇ refers to ⁇ wireless device 100x, base station 200 ⁇ and/or ⁇ wireless device 100x, wireless device 100x) in FIG. 22. ⁇ can be responded to.
  • the first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and/or one or more antennas 108.
  • Processor 102 controls memory 104 and/or transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein.
  • the processor 102 may process information in the memory 104 to generate first information/signal and then transmit a wireless signal including the first information/signal through the transceiver 106.
  • the processor 102 may receive a wireless signal including the second information/signal through the transceiver 106 and then store information obtained from signal processing of the second information/signal in the memory 104.
  • the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, memory 104 may perform some or all of the processes controlled by processor 102 or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. Software code containing them can be stored.
  • the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • Transceiver 106 may be coupled to processor 102 and may transmit and/or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and/or receiver. The transceiver 106 can be used interchangeably with an RF (Radio Frequency) unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • the second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
  • Processor 202 controls memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein.
  • the processor 202 may process the information in the memory 204 to generate third information/signal and then transmit a wireless signal including the third information/signal through the transceiver 206.
  • the processor 202 may receive a wireless signal including the fourth information/signal through the transceiver 206 and then store information obtained from signal processing of the fourth information/signal in the memory 204.
  • the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, memory 204 may perform some or all of the processes controlled by processor 202 or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein. Software code containing them can be stored.
  • the processor 202 and memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • Transceiver 206 may be coupled to processor 202 and may transmit and/or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and/or receiver. Transceiver 206 may be used interchangeably with an RF unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed herein. can be created.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors 102, 202 may generate messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein.
  • One or more processors 102, 202 generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and/or methods disclosed herein. , can be provided to one or more transceivers (106, 206).
  • One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • PDU, SDU, message, control information, data or information can be obtained.
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer.
  • One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc.
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204). It may be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.
  • One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions, and/or instructions.
  • One or more memories 104, 204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • One or more memories 104, 204 may be located internal to and/or external to one or more processors 102, 202. Additionally, one or more memories 104, 204 may be connected to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
  • One or more transceivers 106, 206 may transmit user data, control information, wireless signals/channels, etc. mentioned in the methods and/or operation flowcharts of this document to one or more other devices.
  • One or more transceivers 106, 206 may receive user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed herein, etc. from one or more other devices. there is.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and may transmit and receive wireless signals.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be connected to the description and functions disclosed in this document through one or more antennas (108, 208). , may be set to transmit and receive user data, control information, wireless signals/channels, etc.
  • one or more antennas may be multiple physical antennas or multiple logical antennas (eg, antenna ports).
  • One or more transceivers (106, 206) process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202), and convert the received wireless signals/channels, etc. from the RF band signal. It can be converted to a baseband signal.
  • One or more transceivers (106, 206) may convert user data, control information, wireless signals/channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals.
  • one or more transceivers 106, 206 may comprise (analog) oscillators and/or filters.
  • Figure 24 shows a signal processing circuit for a transmission signal, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 24 may be combined with various embodiments of the present disclosure.
  • 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 Figure 24 may be performed in the processors 102, 202 and/or transceivers 106, 206 of Figure 23.
  • the hardware elements of Figure 24 may be implemented in the processors 102, 202 and/or transceivers 106, 206 of Figure 23.
  • blocks 1010 to 1060 may be implemented in processors 102 and 202 of FIG. 23.
  • blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 23, and block 1060 may be implemented in the transceivers 106 and 206 of FIG. 23.
  • the codeword can be converted into a wireless signal through the signal processing circuit 1000 of FIG. 24.
  • a codeword is an encoded bit sequence of an information block.
  • the information block may include a transport block (eg, UL-SCH transport block, DL-SCH transport block).
  • Wireless signals may be transmitted through various physical channels (eg, PUSCH, PDSCH).
  • the codeword may be converted into a scrambled bit sequence by the scrambler 1010.
  • the scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device.
  • the scrambled bit sequence may be modulated into a modulation symbol sequence by the modulator 1020.
  • Modulation methods may include pi/2-BPSK (pi/2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc.
  • the complex modulation symbol sequence may be mapped to one or more transport layers by the layer mapper 1030.
  • the modulation symbols of each transport layer may be mapped to the corresponding antenna port(s) by the precoder 1040 (precoding).
  • the output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 with the precoding matrix W of N*M.
  • N is the number of antenna ports and M is the number of transport layers.
  • the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transformation) on complex modulation symbols. Additionally, the precoder 1040 may perform precoding without performing transform precoding.
  • the resource mapper 1050 can map the modulation symbols of each antenna port to time-frequency resources.
  • a time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbol, DFT-s-OFDMA symbol) in the time domain and a plurality of subcarriers in the frequency domain.
  • the signal generator 1060 generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna.
  • the signal generator 1060 may include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc. .
  • IFFT Inverse Fast Fourier Transform
  • CP Cyclic Prefix
  • DAC Digital-to-Analog Converter
  • the signal processing process for the received signal in the wireless device may be configured as the reverse of the signal processing process (1010 to 1060) of FIG. 24.
  • a wireless device eg, 100 and 200 in FIG. 23
  • the received wireless signal can be converted into a baseband signal through a signal restorer.
  • the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module.
  • ADC analog-to-digital converter
  • FFT Fast Fourier Transform
  • the baseband signal can be restored to a codeword through a resource de-mapper process, postcoding process, demodulation process, and de-scramble process.
  • a signal processing circuit for a received signal may include a signal restorer, resource de-mapper, postcoder, demodulator, de-scrambler, and decoder.
  • FIG. 25 shows a wireless device, according to an embodiment of the present disclosure.
  • Wireless devices can be implemented in various forms depending on usage-examples/services (see FIG. 22).
  • the embodiment of FIG. 25 may be combined with various embodiments of the present disclosure.
  • the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 23 and include various elements, components, units/units, and/or modules. ) can be composed of.
  • the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140.
  • the communication unit may include communication circuitry 112 and transceiver(s) 114.
  • communication circuitry 112 may include one or more processors 102, 202 and/or one or more memories 104, 204 of FIG. 23.
  • transceiver(s) 114 may include one or more transceivers 106, 206 and/or one or more antennas 108, 208 of FIG. 23.
  • the control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls overall operations of the wireless device. For example, the control unit 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to the outside (e.g., another communication device) through the communication unit 110 through a wireless/wired interface, or to the outside (e.g., to another communication device) through the communication unit 110. Information received through a wireless/wired interface from another communication device may be stored in the memory unit 130.
  • the outside e.g., another communication device
  • Information received through a wireless/wired interface from another communication device may be stored in the memory unit 130.
  • the additional element 140 may be configured in various ways depending on the type of wireless device.
  • the additional element 140 may include at least one of a power unit/battery, an input/output unit (I/O unit), a driving unit, and a computing unit.
  • wireless devices include robots (FIG. 22, 100a), vehicles (FIG. 22, 100b-1, 100b-2), XR devices (FIG. 22, 100c), portable devices (FIG. 22, 100d), and home appliances. (FIG. 22, 100e), IoT device (FIG.
  • digital broadcasting terminal digital broadcasting terminal
  • hologram device public safety device
  • MTC device medical device
  • fintech device or financial device
  • security device climate/environment device
  • It can be implemented in the form of an AI server/device (FIG. 22, 400), a base station (FIG. 22, 200), a network node, etc.
  • Wireless devices can be mobile or used in fixed locations depending on the usage/service.
  • various elements, components, units/parts, and/or modules within the wireless devices 100 and 200 may be entirely interconnected through a wired interface, or at least a portion may be wirelessly connected through the communication unit 110.
  • the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130 and 140) are connected through the communication unit 110.
  • the control unit 120 and the first unit e.g., 130 and 140
  • each element, component, unit/part, and/or module within the wireless devices 100 and 200 may further include one or more elements.
  • the control unit 120 may be comprised of one or more processor sets.
  • control unit 120 may be comprised of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, and a memory control processor.
  • memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.
  • Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smartglasses), and portable computers (e.g., laptops, etc.).
  • a mobile device may be referred to as a Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), or Wireless terminal (WT).
  • MS Mobile Station
  • UT user terminal
  • MSS Mobile Subscriber Station
  • SS Subscriber Station
  • AMS Advanced Mobile Station
  • WT Wireless terminal
  • the portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ) may include.
  • the antenna unit 108 may be configured as part of the communication unit 110.
  • Blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 in FIG. 25, respectively.
  • the communication unit 110 can transmit and receive signals (eg, data, control signals, etc.) with other wireless devices and base stations.
  • the control unit 120 can control the components of the portable device 100 to perform various operations.
  • the control unit 120 may include an application processor (AP).
  • the memory unit 130 may store data/parameters/programs/codes/commands necessary for driving the portable device 100. Additionally, the memory unit 130 can store input/output data/information, etc.
  • the power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, etc.
  • the interface unit 140b may support connection between the mobile device 100 and other external devices.
  • the interface unit 140b may include various ports (eg, audio input/output ports, video input/output ports) for connection to external devices.
  • the input/output unit 140c may input or output video information/signals, audio information/signals, data, and/or information input from the user.
  • the input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.
  • the input/output unit 140c acquires information/signals (e.g., touch, text, voice, image, video) input from the user, and the obtained information/signals are stored in the memory unit 130. It can be saved.
  • the communication unit 110 may convert the information/signal stored in the memory into a wireless signal and transmit the converted wireless signal directly to another wireless device or to a base station. Additionally, the communication unit 110 may receive a wireless signal from another wireless device or a base station and then restore the received wireless signal to the original information/signal.
  • the restored information/signal may be stored in the memory unit 130 and then output in various forms (eg, text, voice, image, video, haptics) through the input/output unit 140c.
  • FIG. 27 shows a vehicle or autonomous vehicle, according to an embodiment of the present disclosure.
  • a vehicle or autonomous vehicle can be implemented as a mobile robot, vehicle, train, manned/unmanned aerial vehicle (AV), ship, etc.
  • the embodiment of FIG. 27 may be combined with various embodiments of the present disclosure.
  • the vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit. It may include a portion 140d.
  • the antenna unit 108 may be configured as part of the communication unit 110. Blocks 110/130/140a to 140d respectively correspond to blocks 110/130/140 in FIG. 25.
  • the communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g. base stations, road side units, etc.), and servers.
  • the control unit 120 may control elements of the vehicle or autonomous vehicle 100 to perform various operations.
  • the control unit 120 may include an Electronic Control Unit (ECU).
  • the driving unit 140a can drive the vehicle or autonomous vehicle 100 on the ground.
  • the driving unit 140a may include an engine, motor, power train, wheels, brakes, steering device, etc.
  • the power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and may include a wired/wireless charging circuit, a battery, etc.
  • the sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc.
  • the sensor unit 140c includes an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight sensor, a heading sensor, a position module, and a vehicle forward sensor. / May include a reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illuminance sensor, pedal position sensor, etc.
  • the autonomous driving unit 140d provides technology for maintaining the driving lane, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a set route, and technology for automatically setting and driving when a destination is set. Technology, etc. can be implemented.
  • the communication unit 110 may receive map data, traffic information data, etc. from an external server.
  • the autonomous driving unit 140d can create an autonomous driving route and driving plan based on the acquired data.
  • the control unit 120 may control the driving unit 140a so that the vehicle or autonomous vehicle 100 moves along the autonomous driving path according to the driving plan (e.g., speed/direction control).
  • the communication unit 110 may acquire the latest traffic information data from an external server irregularly/periodically and obtain surrounding traffic information data from surrounding vehicles.
  • the sensor unit 140c can obtain vehicle status and surrounding environment information.
  • the autonomous driving unit 140d may update the autonomous driving route and driving plan based on newly acquired data/information.
  • the communication unit 110 may transmit information about vehicle location, autonomous driving route, driving plan, etc. to an external server.
  • An external server can predict traffic information data in advance using AI technology, etc., based on information collected from vehicles or self-driving vehicles, and provide the predicted traffic information data to the vehicles or self-driving vehicles.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2023/005135 2022-04-14 2023-04-14 Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치 Ceased WO2023200312A1 (ko)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020237030068A KR20250001855A (ko) 2022-04-14 2023-04-14 Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치
US18/549,160 US20250324451A1 (en) 2022-04-14 2023-04-14 Method and device for operating shared cot reporting in sl-u
JP2023554349A JP7759957B2 (ja) 2022-04-14 2023-04-14 Ｓｌ－ｕにおける共有ｃｏｔの通知動作方法及び装置
EP23761413.6A EP4510754A4 (de) 2022-04-14 2023-04-14 Verfahren und vorrichtung zur meldung des betriebs eines gemeinsamen cot in sl-u
CN202380010781.XA CN117242890A (zh) 2022-04-14 2023-04-14 Sl-u中操作共享cot报告的方法和设备

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263331236P 2022-04-14 2022-04-14
US63/331,236 2022-04-14

Publications (1)

Publication Number Publication Date
WO2023200312A1 true WO2023200312A1 (ko) 2023-10-19

Family

ID=88330072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/005135 Ceased WO2023200312A1 (ko) 2022-04-14 2023-04-14 Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치

Country Status (6)

Country Link
US (1) US20250324451A1 (de)
EP (1) EP4510754A4 (de)
JP (1) JP7759957B2 (de)
KR (1) KR20250001855A (de)
CN (1) CN117242890A (de)
WO (1) WO2023200312A1 (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240314834A1 (en) * 2023-03-16 2024-09-19 Samsung Electronics Co., Ltd. Channel access procedures for multiple sl transmissions

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021041020A1 (en) * 2019-08-23 2021-03-04 Qualcomm Incorporated Ranging signal transmission in unlicensed band
WO2022026141A1 (en) * 2020-07-30 2022-02-03 Qualcomm Incorporated Channel occupancy time (cot) sharing propagation
CN114051747A (zh) * 2021-09-23 2022-02-15 北京小米移动软件有限公司 一种共享信道占用时间的方法及其装置
US20220070925A1 (en) * 2020-08-28 2022-03-03 Qualcomm Incorporated Resource reservation for nr-u sl

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12127252B2 (en) * 2019-02-12 2024-10-22 Telefonaktiebolaget Lm Ericsson (Publ) Control signalling for transmission in a channel occupancy time (COT) period in unlicensed frequency spectrum
CN115443705B (zh) 2020-04-22 2025-12-02 联想(北京)有限公司 用于共享信道占用时间的方法及设备
CN115669171A (zh) * 2020-05-29 2023-01-31 奥罗佩法国有限责任公司 用户设备及其在共享频谱中进行传输的方法
EP4169344A1 (de) * 2020-06-17 2023-04-26 Lenovo (Singapore) Pte. Ltd. Gemeinsame nutzung der kanalbelegungszeit
US12016052B2 (en) 2021-06-29 2024-06-18 Qualcomm Incorporated Transmission of channel occupancy time-sharing information (COT-SI) reserving a COT for sidelink communications in unlicensed bands

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021041020A1 (en) * 2019-08-23 2021-03-04 Qualcomm Incorporated Ranging signal transmission in unlicensed band
WO2022026141A1 (en) * 2020-07-30 2022-02-03 Qualcomm Incorporated Channel occupancy time (cot) sharing propagation
US20220070925A1 (en) * 2020-08-28 2022-03-03 Qualcomm Incorporated Resource reservation for nr-u sl
CN114051747A (zh) * 2021-09-23 2022-02-15 北京小米移动软件有限公司 一种共享信道占用时间的方法及其装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.214
MODERATOR (QUALCOMM INCORPORATED): "FL summary of channel access mechanism for 52.6GHz-71GHz band, ver02", 3GPP DRAFT; R1-2202685, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. 20220221 - 20220303, 2 March 2022 (2022-03-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052119558 *
See also references of EP4510754A4

Also Published As

Publication number Publication date
US20250324451A1 (en) 2025-10-16
JP2024517054A (ja) 2024-04-19
KR20250001855A (ko) 2025-01-07
EP4510754A1 (de) 2025-02-19
CN117242890A (zh) 2023-12-15
JP7759957B2 (ja) 2025-10-24
EP4510754A4 (de) 2026-01-28

Similar Documents

Publication Publication Date Title
WO2023204662A1 (ko) Sl-u에서 cot 정보 기반 자원 재선택 동작 방법 및 장치
WO2023195815A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2023200317A1 (ko) Sl-u에서 자원 선택 동작 방법 및 장치
WO2023200224A1 (ko) Sl-u에서 타이머를 기반으로 cot 정보를 전송하는 방법 및 장치
WO2024071974A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2024071977A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2023200312A1 (ko) Sl-u에서 공유 cot의 리포팅 동작 방법 및 장치
WO2024136478A1 (ko) 비면허 대역 상 nr 사이드링크 전송에 대한 cp 확장 방법 및 장치
WO2024058542A1 (ko) Sl-u에서 공유 cot와 관련된 정보 수신 시 sl drx 타이머 동작 방법 및 장치
WO2024080665A1 (ko) 비면허 대역에서 sl capc를 기반으로 채널 액세스를 수행하는 방법 및 장치
WO2024035227A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2023211206A1 (ko) Lbt와 관련된 무선 통신을 수행하는 방법 및 장치
WO2023211208A1 (ko) Lbt와 관련된 무선 통신을 수행하는 방법 및 장치
WO2023200307A1 (ko) Cap를 기반으로 무선 통신을 수행하는 방법 및 장치
WO2023191544A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2024063631A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2024005594A1 (ko) Sl-u에서 단말의 cot 생성을 위해 기지국이 단말에 보조 정보를 전송하는 동작 방법 및 장치
WO2023211203A1 (ko) Sl-u에서 공유 cot 및 공유 ffp에 대한 필터링 동작 방법 및 장치
WO2024058622A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2023195771A1 (ko) Sl-u에서 sl drx를 고려한 cot 공유 동작 방법 및 장치
WO2023191562A1 (ko) Cap를 기반으로 무선 통신을 수행하는 방법 및 장치
WO2024096669A1 (ko) Sl-u에서 mcst를 위한 sl drx 동작 방법 및 장치
WO2024010311A1 (ko) Sl-u에서 cot을 고려한 전송 단말의 자원 선택 동작 방법 및 장치
WO2024096664A1 (ko) 비면허 대역에서 사이드링크 통신을 수행하는 방법 및 장치
WO2024019528A1 (ko) Lbt와 관련된 무선 통신을 수행하는 방법 및 장치

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2023554349

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202380010781.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23761413

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023761413

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023761413

Country of ref document: EP

Effective date: 20241114

WWP Wipo information: published in national office

Ref document number: 18549160

Country of ref document: US