Method and apparatus for broadcast type based sidelink communication in shared COT

Abstract

Methods and apparatus for broadcast type based sidelink communications in a shared COT are disclosed. The method performed by a first UE comprises the steps of: receiving a first SL transmission of a first broadcast type from a second UE; and performing a second SL transmission on the basis of the first broadcast type in the shared COT, where the first SL transmission and the second SL transmission are performed on the basis of the same first broadcast type.

Description

Technical Field

[0001] The present invention relates to a sidelink communication technology in an unlicensed band, and more particularly, to a cast-type-based sidelink communication technology in a shared channel occupancy time (COT). Background Art

[0002] Communication networks (e.g., 5G communication networks or 6G communication networks) are being developed to provide enhanced communication services compared to existing communication networks (e.g., Long Term Evolution (LTE), Advanced LTE-A (LTE-A), etc.). 5G communication networks (e.g., New Radio (NR) communication networks) can support frequency bands below 6 GHz and above 6 GHz. In other words, 5G communication networks can support frequency region (FR 1) and / or FR 2 bands. Compared with LTE communication networks, 5G communication networks can support various communication services and scenarios. For example, usage scenarios of 5G communication networks may include enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), massive Machine Type Communication (mMTC), etc.

[0003] Compared to 5G networks, 6G networks can support a wider range of communication services and scenarios. They can meet requirements for ultra-performance, ultra-bandwidth, ultra-space, ultra-precision, ultra-intelligence, and / or ultra-reliability. They can support multiple broadband frequencies and be applied to a variety of scenarios, such as terrestrial communications, non-terrestrial communications, and sidelink communications.

[0004] On the other hand, to improve sidelink communication, carrier aggregation (CA) operation, unlicensed band operation, FR2 band operation, and / or operation for coexistence between LTE and NR may be considered. In particular, when sidelink communication is performed in an unlicensed band, a method for supporting sidelink communication may be required. For operation in an unlicensed band, it may be necessary to implement a channel occupancy time (COT) method, a shared COT method, and / or a sidelink communication method in a shared COT. Summary of the Invention

[0005] Technical issues

[0006] In order to solve the above problems, an object of the present invention is to provide a method and apparatus for broadcast-type based sidelink communication in a shared channel occupation time (COT).

[0007] Technical Solution

[0008] A method for achieving the above-mentioned object by a first user equipment (UE) according to an embodiment of the present invention includes: receiving a first sidelink (SL) transmission using a first broadcast type from a second UE, and performing a second SL transmission based on the first broadcast type within a shared channel occupation time (COT). The first SL transmission and the second SL transmission are performed based on the first broadcast type, which is the same broadcast type.

[0009] The first broadcast type may be unicast, multicast, or broadcast.

[0010] The second UE may be a COT initiating UE that initiates a COT, the first SL transmission may include COT sharing information, and the shared COT may be configured based on the COT sharing information.

[0011] The COT sharing information may include at least one of a source identifier (ID), a destination ID, a channel access priority class (CAPC), a remaining COT duration, frequency domain information of a resource block (RB) set of the COT, an additional ID, or an associated broadcast type.

[0012] The source ID of the second SL transmission may match the destination ID included in the COT shared information, and the destination ID of the second SL transmission may match the source ID included in the COT shared information.

[0013] The source ID and destination ID of the second SL transmission may match a pair of additional IDs included in the COT shared information.

[0014] The first SL transmission may include sidelink control information (SCI), and the SCI may include an information element indicating a first broadcast type.

[0015] If the first broadcast type is unicast, the reception target of the second SL transmission may be the second UE, and if the first broadcast type is groupcast, the reception target of the second SL transmission may include the second UE.

[0016] A first broadcast type may be applied, the first broadcast type being the same broadcast type within a shared COT belonging to one COT initiated by the second UE.

[0017] A first user equipment (UE) according to an embodiment of the present invention for achieving the above-mentioned objective includes at least one processor. The at least one processor causes the first UE to receive a first sidelink (SL) transmission from a second UE using a first broadcast type, and to perform a second SL transmission based on the first broadcast type within a shared channel occupation time (COT). The first and second SL transmissions are performed based on the first broadcast type, which is the same broadcast type.

[0018] The first broadcast type may be unicast, multicast, or broadcast.

[0019] The second UE may be a COT initiating UE that initiates a COT, the first SL transmission may include COT sharing information, and the shared COT may be configured based on the COT sharing information.

[0020] The COT sharing information may include at least one of a source identifier (ID), a destination ID, a channel access priority class (CAPC), a remaining COT duration, frequency domain information of a resource block (RB) set of the COT, an additional ID, or an associated broadcast type.

[0021] The source ID of the second SL transmission may match the destination ID included in the COT shared information, and the destination ID of the second SL transmission may match the source ID included in the COT shared information.

[0022] The source ID and destination ID of the second SL transmission may match a pair of additional IDs included in the COT shared information.

[0023] The first SL transmission may include sidelink control information (SCI), and the SCI may include an information element indicating a first broadcast type.

[0024] If the first broadcast type is unicast, the reception target of the second SL transmission may be the second UE, and if the first broadcast type is groupcast, the reception target of the second SL transmission may include the second UE.

[0025] A first broadcast type may be applied, the first broadcast type being the same broadcast type within a shared COT belonging to one COT initiated by the second UE.

[0026] Beneficial effects

[0027] According to the present invention, a user equipment (UE) initiating a channel occupancy time (COT) can transmit COT shared information having a broadcast type. The UE can receive the COT shared information and identify a shared COT based on the COT shared information. The UE can perform SL transmission based on the broadcast type associated with the COT shared information within the shared COT (e.g., the broadcast type indicated by the COT shared information). Consequently, SL transmission within the shared COT can be performed efficiently, and communication system performance can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 This is a conceptual diagram showing a scenario of vehicle-to-everything (V2X) communication.

[0029] Figure 2 is a conceptual diagram illustrating a first exemplary embodiment of a communication system.

[0030] Figure 3 is a conceptual diagram illustrating an exemplary embodiment of communication nodes constituting a communication system.

[0031] Figure 4 is a block diagram illustrating an example embodiment of a communication node performing communications.

[0032] Figure 5a is a block diagram illustrating an exemplary embodiment of a transmit path.

[0033] Figure 5b is a block diagram illustrating an exemplary embodiment of a receive path.

[0034] Figure 6 is a block diagram illustrating an exemplary embodiment of a user plane protocol stack of a UE performing sidelink communications.

[0035] Figure 7 is a block diagram illustrating a first exemplary embodiment of a control plane protocol stack of a UE performing sidelink communication.

[0036] Figure 8 is a block diagram illustrating a second exemplary embodiment of a control plane protocol stack of a UE performing sidelink communication.

[0037] Figure 9 is a timing diagram illustrating an embodiment of a communication method in an unlicensed band.

[0038] Figure 10 is a flow chart illustrating a first embodiment of the SL-U communication method.

[0039] Figure 11 is a flow chart illustrating a second embodiment of the SL-U communication method. DETAILED DESCRIPTION

[0040] Since the present invention is susceptible to various modifications and may have a variety of forms, specific exemplary embodiments will be shown in the drawings and described in detail in the detailed description. However, it should be understood that it is not intended to limit the present invention to specific exemplary embodiments, but on the contrary, the present invention covers all modifications and alternative forms that fall within the spirit and scope of the present invention.

[0041] Relational terms such as first, second, etc. can be used to describe various elements, but these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the present invention, a first component can be named a second component, and a second component can be similarly named a first component. The term "and / or" means any one or combination of multiple related and described matters.

[0042] In the present invention, “at least one of A and B” may mean “at least one of A or B” or “at least one of a combination of one or more of A and B”. In addition, “one or more of A and B” may mean “one or more of A or B” or “one or more of a combination of one or more of A and B”.

[0043] In the present invention, "(re)transmission" may refer to "transmission", "retransmission" or "transmission and retransmission", "(re)configuration" may refer to "configuration", "reconfiguration" or "configuration and reconfiguration", "(re)connection" may refer to "connection", "reconnection" or "connection and reconnection", and "(re)access" may refer to "access", "reaccess" or "access and reaccess".

[0044] When it is mentioned that a certain component is “coupled” or “connected” to another component, it should be understood that the certain component is directly “coupled” or “connected” to the other component, or another component may be provided therebetween. Conversely, when it is mentioned that a certain component is “directly coupled” or “directly connected” to another component, it should be understood that no other component is provided therebetween.

[0045] The terms used in the present invention are only used to describe specific exemplary embodiments and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In the present invention, terms such as "including" or "having" are intended to indicate the presence of features, quantities, steps, operations, components, parts, or combinations thereof described in the specification, but it should be understood that these terms do not exclude the presence or addition of one or more features, quantities, steps, operations, components, parts, or combinations thereof.

[0046] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those skilled in the art to which the present invention belongs. Terms commonly used in dictionaries and already in dictionaries should be interpreted as having meanings that match the contextual meanings in the art. In this specification, unless explicitly defined, terms are not necessarily interpreted as having formal meanings.

[0047] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate a comprehensive understanding of the present invention, the same reference numerals refer to the same elements throughout the description of the accompanying drawings, and repeated descriptions thereof will be omitted. Operations according to the exemplary embodiments explicitly described in the present invention, as well as combinations of the exemplary embodiments, extensions of the exemplary embodiments, and / or variations of the exemplary embodiments may be performed. Some operations may be omitted, and the sequence of operations may be changed.

[0048] Even when describing a method (e.g., signal transmission or reception) performed at a first communication node among the communication nodes in the exemplary embodiment, the corresponding second communication node may also perform a method (e.g., signal reception or transmission) corresponding to the method performed at the first communication node. In other words, when describing the operation of a user equipment (UE), the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when describing the operation of a base station, the corresponding UE may perform an operation corresponding to the operation of the base station.

[0049] A base station may be referred to by various terms, such as Node B, evolved Node B, next generation node B (gNodeB), gNB, device, apparatus, node, communication node, base transceiver station (BTS), radio remote head (RRH), transmission reception point (TRP), radio unit (RU), roadside unit (RSU), radio transceiver, access point, access node, etc. A user equipment (UE) may be referred to by various terms, such as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, on-board unit (OBU), etc.

[0050] In the present invention, signaling may be one of higher layer signaling, MAC signaling, and physical (PHY) signaling, or a combination of two or more. A message used for higher layer signaling may be referred to as a "higher layer message" or a "higher layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Higher layer signaling may refer to the operation of sending and receiving system information (e.g., a master information block (MIB), a system information block (SIB)) and / or an RRC message. MAC signaling may refer to the operation of sending and receiving a MAC control element (CE). PHY signaling may refer to the operation of sending and receiving control information (e.g., downlink control information (DCI), uplink control information (UCI), or sidelink control information (SCI)). Signaling may be signaling between a base station and a terminal and / or signaling between multiple terminals.

[0051] In the present invention, "configuration of an operation (e.g., a sending operation)" may refer to configuration information (e.g., information elements, parameters) required for the operation and / or signaling of information indicating the execution of the operation. "Configuration of information elements (e.g., parameters)" may refer to signaling of information elements. In the present invention, "signal and / or channel" may refer to a signal, a channel, or both a signal and a channel, and "signal" may be used to mean "signal and / or channel."

[0052] The communication network to which the exemplary embodiment is applied is not limited to the communication network described below, and the exemplary embodiment can be applied to various communication networks (e.g., 4G communication network, 5G communication network and / or 6G communication network). Here, "communication network" can be used interchangeably with the term "communication system".

[0053] Figure 1 This is a conceptual diagram showing a scenario of vehicle-to-everything (V2X) communication.

[0054] like Figure 1As shown, V2X communication can include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-network (V2N) communication, etc. V2X communication can be supported by a communication system (e.g., a communication network) 140. V2X communication supported by the communication system 140 can be referred to as "cellular-V2X (C-V2X) communication." Here, the communication system 140 can include a 4G communication system (e.g., an LTE communication system or an LTE-A communication system), a 5G communication system (e.g., a NR communication system), etc.

[0055] V2V communication may include communication between a first vehicle 100 (e.g., a communication node located in the vehicle 100) and a second vehicle 110 (e.g., a communication node located in the vehicle 110). Various driving information such as speed, heading, time, location, etc. may be exchanged between the vehicle 100 and the vehicle 110 through V2V communication. For example, autonomous driving (e.g., platooning) may be supported based on the driving information exchanged through V2V communication. V2V communication supported by the communication system 140 may be performed based on a sidelink communication technology (e.g., based on Proximity Based Services (ProSe) and Device-to-Device (D2D) communication technology, etc.). In this case, communication between the vehicle 100 and the vehicle 110 may be performed using at least one sidelink channel.

[0056] V2I communication may include communication between the first vehicle 100 and an infrastructure (e.g., a roadside unit (RSU)) 120 located on the roadside. The infrastructure 120 may include a traffic light or streetlight located on the roadside. For example, when performing V2I communication, communication may be performed between a communication node located in the first vehicle 100 and a communication node located in a traffic light. Traffic information, driving information, and the like may be exchanged between the first vehicle 100 and the infrastructure 120 through V2I communication. The V2I communication supported by the communication system 140 may be performed based on a sidelink communication technology (e.g., ProSe and D2D communication technology, etc.). In this case, communication between the vehicle 100 and the infrastructure 120 may be performed using at least one sidelink channel.

[0057] V2P communication may include communication between a first vehicle 100 (e.g., a communication node located in the vehicle 100) and a person 130 (e.g., a communication node carried by the person 130). Driving information of the first vehicle 100 and movement information of the person 130, such as speed, heading, time, and location, may be exchanged between the vehicle 100 and the person 130 via V2P communication. By determining a dangerous situation based on the obtained driving information and movement information, the communication node located in the vehicle 100 or the communication node carried by the person 130 may generate an alert indicating the danger. V2P communication supported by the communication system 140 may be performed based on sidelink communication technologies (e.g., ProSe and D2D communication technologies, etc.). In this case, communication between the communication node located in the vehicle 100 and the communication node carried by the person 130 may be performed using at least one sidelink channel.

[0058] V2N communication can be communication between the first vehicle 100 (e.g., a communication node located in the vehicle 100) and the communication system (e.g., a communication network) 140. V2N communication can be performed based on 4G communication technology (e.g., LTE or LTE-A as specified by the 3GPP standard) or 5G communication technology (e.g., NR as specified by the 3GPP standard). In addition, V2N communication can be performed based on Wireless Access in Vehicular Environments (WAVE) communication technology, Wireless Local Area Network (WLAN) communication technology defined in Institute of Electrical and Electronics Engineers (IEEE) 802.11, Wireless Personal Area Network (WPAN) communication technology defined in IEEE 802.15, and the like.

[0059] On the other hand, the communication system 140 supporting V2X communication may be configured as follows.

[0060] Figure 2 is a conceptual diagram illustrating an exemplary embodiment of a communication system.

[0061] like Figure 2 As shown, the communication system may include an access network, a core network, etc. The access network may include a base station 210, a relay station 220, user equipments (UEs) 231 to 236, etc. UEs 231 to 236 may include Figure 1 The communication nodes in the vehicle 100 and the vehicle 110 are located Figure 1 The communication nodes in the infrastructure 120 are Figure 1 When the communication system supports 4G communication technology, the core network may include a serving gateway (S-GW) 250, a packet data network (PDN) gateway (P-GW) 260, a mobility management entity (MME) 270, and the like.

[0062] When the communication system supports 5G communication technology, the core network may include a user plane function (UPF) 250, a session management function (SMF) 260, an access and mobility management function (AMF) 270, etc. Alternatively, when the communication system operates in non-standalone (NSA) mode, the core network composed of the S-GW 250, the P-GW 260, and the MME 270 may support 5G communication technology as well as 4G communication technology, and the core network composed of the UPF 250, the SMF 260, and the AMF 270 may support 4G communication technology as well as 5G communication technology.

[0063] In addition, when the communication system supports network slicing technology, the core network can be divided into multiple logical network slices. For example, network slices supporting V2X communication (e.g., V2V network slices, V2I network slices, V2P network slices, V2N network slices, etc.) can be configured, and V2X communication can be supported by the V2X network slices configured in the core network.

[0064] The communication nodes (e.g., base stations, relay stations, UEs, S-GWs, P-GWs, MMEs, UPFs, SMFs, AMFs, etc.) constituting a communication system may perform communication by utilizing at least one of the following communication technologies: code division multiple access (CDMA) technology, time division multiple access (TDMA) technology, frequency division multiple access (FDMA) technology, orthogonal frequency division multiplexing (OFDM) technology, filtered OFDM technology, orthogonal frequency division multiple access (OFDMA) technology, single carrier FDMA (SC-FDMA) technology, non-orthogonal multiple access (NOMA) technology, generalized frequency division multiplexing (GFDM) technology, filter bank multi-carrier (FBMC) technology, universal filtered multi-carrier (UFMC) technology, and space division multiple access (SDMA). access, SDMA) technology.

[0065] The communication nodes (e.g., base stations, relay stations, UE, S-GW, P-GW, MME, UPF, SMF, AMF, etc.) that constitute the communication system can be configured as follows.

[0066] Figure 3 is a conceptual diagram illustrating an exemplary embodiment of communication nodes constituting a communication system.

[0067] like Figure 3 As shown, the communication node 300 may include at least one processor 310, a memory 320, and a transceiver 330 connected to a network for performing communication. In addition, the communication node 300 may further include an input interface device 340, an output interface device 350, a storage device 360, etc. Each component included in the communication node 300 can communicate with each other when connected through a bus 370.

[0068] However, each component included in the communication node 300 may be connected to the processor 310 via a separate interface or a separate bus instead of the common bus 370. For example, the processor 310 may be connected to at least one of the memory 320, the transceiver 330, the input interface device 340, the output interface device 350, and the storage device 360 via a dedicated interface.

[0069] The processor 310 can execute at least one program instruction stored in at least one of the memory 320 and the storage device 360. The processor 310 can refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the method according to the exemplary embodiment of the present invention is executed. Each of the memory 320 and the storage device 360 can include at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 320 can include at least one of a read-only memory (ROM) and a random access memory (RAM).

[0070] Reference again Figure 2 In the communication system, base station 210 may form a macro cell or a small cell and may be connected to a core network via an ideal backhaul or a non-ideal backhaul. Base station 210 may transmit signals received from the core network to UEs 231 to 236 and relay station 220, and may transmit signals received from UEs 231 to 236 and relay station 220 to the core network. UE#1 231, UE#2 232, UE#4 234, UE#5 235, and UE#6 236 may belong to the cell coverage of base station 210. UE#1 231, UE#2 232, UE#4 234, UE#5 235, and UE#6 236 may connect to base station 210 by performing a connection establishment procedure with base station 210. UE#1 231 , UE#2 232 , UE#4 234 , UE#5 235 , and UE#6 236 may communicate with the base station 210 after being connected to the base station 210 .

[0071] Relay station 220 may be connected to base station 210 and may relay communications between base station 210 and UE#3 233 and UE#4 234. Specifically, relay station 220 may transmit signals received from base station 210 to UE#3 233 and UE#4 234, and may transmit signals received from UE#3 233 and UE#4 234 to base station 210. UE#4 234 may be within both the cell coverage of base station 210 and the cell coverage of relay station 220, and UE#3 233 may be within the cell coverage of relay station 220. In other words, UE#3 233 may be outside the cell coverage of base station 210. UE#3 233 and UE#4 234 may connect to relay station 220 by performing a connection establishment procedure with relay station 220. After connecting to relay station 220, UE#3 233 and UE#4 234 may communicate with relay station 220.

[0072] The base station 210 and the relay station 220 can support multiple-input multiple-output (MIMO) technology (e.g., single-user (SU)-MIMO, multi-user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (COMP) communication technology, carrier aggregation (CA) communication technology, unlicensed band communication technology (e.g., Licensed Assisted Access (LAA), enhanced LAA (eLAA), etc.), sidelink communication technology (e.g., ProSe communication technology, D2D communication technology), etc. UE#1 231, UE#2 232, UE#5 235, and UE#6 236 can perform operations corresponding to the base station 210 and operations supported by the base station 210. UE#3 233 and UE#4 234 can perform operations corresponding to the relay station 220 and operations supported by the relay station 220.

[0073] Here, the base station 210 may refer to a Node B (NB), an evolved Node B (eNB), a base transceiver station (BTS), a radio remote head (RRH), a transmit / receive point (TRP), a radio unit (RU), a roadside unit (RSU), a radio transceiver, an access point, an access node, etc. The relay station 220 may refer to a small base station, a relay node, etc. Each of the UEs 231 to 236 may refer to a terminal, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, a node, a device, an onboard unit (OBU), etc.

[0074] On the other hand, a communication node that performs communication in a communication network may be configured as follows. Figure 4The communication nodes shown may be Figure 3 A specific exemplary embodiment of a communication node is shown.

[0075] Figure 4 is a block diagram illustrating an example embodiment of a communication node performing communications.

[0076] like Figure 4 As shown, each of the first communication node 400a and the second communication node 400b can be a base station or a UE. The first communication node 400a can send a signal to the second communication node 400b. The transmission processor 411 included in the first communication node 400a can receive data (e.g., data units) from the data source 410. The transmission processor 411 can receive control information from the controller 416. The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0077] The transmit processor 411 may generate data symbols by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmit processor 411 may generate control symbols by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). In addition, the transmit processor 411 may generate synchronization / reference symbols for synchronization signals and / or reference signals.

[0078] The Tx MIMO processor 412 may perform spatial processing operations (e.g., precoding operations) on data symbols, control symbols, and / or synchronization / reference symbols. The output of the Tx MIMO processor 412 (e.g., a symbol stream) may be provided to a modulator (MOD) included in transceivers 413a to 413t. The modulator may generate modulation symbols by performing processing operations on the symbol stream and may generate signals by performing additional processing operations (e.g., analog-to-analog conversion operations, amplification operations, filtering operations, upconversion operations, etc.) on the modulation symbols. The signals generated by the modulators of transceivers 413a to 413t may be transmitted via antennas 414a to 414t.

[0079] The signal transmitted by the first communication node 400a can be received at the antenna 464a to the antenna 464r of the second communication node 400b. The signal received at the antenna 464a to the antenna 464r can be provided to the demodulator (DEMOD) included in the transceiver 463a to the transceiver 463r. The demodulator (DEMOD) can obtain samples by performing processing operations on the signal (e.g., filtering operations, amplification operations, down-conversion operations, digital conversion operations, etc.). The demodulator can perform additional processing operations on the samples to obtain symbols. The MIMO detector 462 can perform MIMO detection operations on the symbols. The receiving processor 461 can perform processing operations on the symbols (e.g., deinterleaving operations, decoding operations, etc.). The output of the receiving processor 461 can be provided to the data sink. 460 and controller 466. For example, data may be provided to data sink 460, and control information may be provided to controller 466.

[0080] On the other hand, the second communication node 400b can transmit a signal to the first communication node 400a. The transmit processor 468 included in the second communication node 400b can receive data (e.g., data units) from the data source 467 and perform processing operations on the data to generate data symbols. The transmit processor 468 can receive control information from the controller 466 and perform processing operations on the control information to generate control symbols. In addition, the transmit processor 468 can generate reference symbols by performing processing operations on reference signals.

[0081] The Tx MIMO processor 469 may perform spatial processing operations (e.g., precoding operations) on data symbols, control symbols, and / or reference symbols. The output of the Tx MIMO processor 469 (e.g., a symbol stream) may be provided to a modulator (MOD) included in transceivers 463a to 463t. The modulator may generate modulation symbols by performing processing operations on the symbol stream and may generate signals by performing additional processing operations (e.g., analog-to-analog conversion operations, amplification operations, filtering operations, and up-conversion operations) on the modulation symbols. The signals generated by the modulators of transceivers 463a to 463t may be transmitted via antennas 464a to 464t.

[0082] The signal transmitted by the second communication node 400b can be received at antennas 414a to 414r of the first communication node 400a. The signals received at antennas 414a to 414r can be provided to a demodulator (DEMOD) included in transceivers 413a to 413r. The demodulator can obtain samples by performing processing operations (e.g., filtering, amplification, down-conversion, and digital conversion) on the signal. The demodulator can perform additional processing operations on the samples to obtain symbols. The MIMO detector 420 can perform MIMO detection operations on the symbols. The receive processor 419 can perform processing operations (e.g., deinterleaving, decoding, etc.) on the symbols. The output of the receive processor 419 can be provided to the data sink 418 and the controller 416. For example, data can be provided to the data sink 418, and control information can be provided to the controller 416.

[0083] Memory 415 and memory 465 may store data, control information, and / or program codes. Scheduler 417 may perform scheduling operations for communications. Figure 4 The processors 411, 412, 419, 461, 468, and 469 and the controllers 416 and 466 shown may be Figure 3 The processor 310 shown can be used to execute the methods described in the present invention.

[0084] Figure 5a is a block diagram illustrating an exemplary embodiment of a transmit path, Figure 5b is a block diagram illustrating an exemplary embodiment of a receive path.

[0085] like Figure 5a and Figure 5b As shown, a transmission path 510 may be implemented in a communication node transmitting a signal, and a reception path 520 may be implemented in a communication node receiving a signal. The transmission path 510 may include a channel coding and modulation block 511, a serial-to-parallel (S to P) block 512, an N-point inverse fast Fourier transform (N-point IFFT) block 513, a parallel-to-serial (P to S) block 514, a cyclic prefix (CP) addition block 515, and an up-converter (UC) 516. The reception path 520 may include a down-converter (DC) 521, a CP removal block 522, an S to P block 523, an N-point FFT block 524, a P to S block 525, and a channel decoding and demodulation block 526. Here, N may be a natural number.

[0086] In the transmit path 510, information bits may be input to a channel coding and modulation block 511. The channel coding and modulation block 511 may perform encoding and decoding operations (e.g., low-density parity check (LDPC) encoding and decoding operations, polar encoding and decoding operations, etc.) and modulation operations (e.g., quadrature phase shift keying (OPSK), quadrature amplitude modulation (QAM), etc.) on the information bits. The output of the channel coding and modulation block 511 may be a modulation symbol sequence.

[0087] The S-to-P block 512 may convert the frequency-domain modulation symbols into parallel symbol streams to generate N parallel symbol streams. N may be the IFFT size or the FFT size. The N-point IFFT block 513 may generate a time-domain signal by performing an IFFT operation on the N parallel symbol streams. The P-to-S block 514 may convert the output of the N-point IFFT block 513 (e.g., the parallel signal) into a serial signal to generate a serial signal.

[0088] The CP adding block 515 may insert a CP into the signal. The UC 516 may up-convert the frequency of the output of the CP adding block 515 to a radio frequency (RF) frequency. In addition, the output of the CP adding block 515 may be filtered in baseband before up-conversion.

[0089] The signal transmitted from the transmit path 510 can be input to the receive path 520. The operations in the receive path 520 can be the inverse of the operations in the transmit path 510. The DC 521 can down-convert the frequency of the received signal to the baseband frequency. The CP removal block 522 can remove the CP from the signal. The output of the CP removal block 522 can be a serial signal. The S to P block 523 can convert the serial signal into a parallel signal. The N-point FFT block 524 can generate N parallel signals by performing an FFT algorithm. The P to S block 525 can convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block 526 can perform a demodulation operation on the modulation symbols and can recover the data by performing a decoding operation on the result of the demodulation operation.

[0090] exist Figure 5a and Figure 5b In the present invention, discrete Fourier transform (DFT) and inverse DFT (IDFT) can be used instead of FFT and IFFT. Figure 5a and Figure 5bEach of the blocks (eg, components) in the embodiment may be implemented by at least one of hardware, software, or firmware. For example, Figure 5a and Figure 5b Some blocks in the may be implemented by software, and other blocks may be implemented by hardware or a combination of hardware and software. Figure 5a and Figure 5b In the , a block can be subdivided into multiple blocks, multiple blocks can be integrated into one block, some blocks can be omitted, and blocks that support other functions can be added.

[0091] On the other hand, the communication between UE#5 235 and UE#6 236 may be performed based on a sidelink communication technology (e.g., ProSe communication technology, D2D communication technology). The sidelink communication may be performed based on a one-to-one scheme or a one-to-many scheme. When V2V communication is performed using the sidelink communication technology, UE#5 235 may refer to a UE located at Figure 1 The communication node in the first vehicle 100, and UE#6 236 may refer to a communication node located at Figure 1 When performing V2I communication using the sidelink communication technology, UE#5 235 may refer to a communication node located in the second vehicle 110. Figure 1 The communication node in the first vehicle 100, and UE#6236 may refer to a communication node located at Figure 1 When performing V2P communication using the sidelink communication technology, UE#5 235 may refer to a communication node located in the infrastructure 120. Figure 1 The communication node in the first vehicle 100 and UE#6 236 may refer to a communication node carried by the person 130.

[0092] The scenarios in which side link communication is applied can be classified according to the locations of the UEs (e.g., UE#5 235 and UE#6 236) participating in the side link communication, as shown in Table 1 below. For example, Figure 2 The sidelink communication scenario shown between UE#5 235 and UE#6 236 may be sidelink communication scenario #C.

[0093] [Table 1]

[0094] Sidelink communication scenario UE#5 235 location Location of UE#6 236 #A Outside the coverage of base station 210 Outside the coverage of base station 210 #B Within the coverage area of base station 210 Outside the coverage of base station 210 #C Within the coverage area of base station 210 Within the coverage area of base station 210 #D Within the coverage area of base station 210 Within the coverage area of other base stations

[0095] On the other hand, the user plane protocol stack of the UEs (eg, UE#5 235 and UE#6 236) performing sidelink communication may be configured as follows.

[0096] Figure 6 is a block diagram illustrating an exemplary embodiment of a user plane protocol stack of a UE performing sidelink communications.

[0097] like Figure 6As shown, UE#5 235 can be Figure 2 UE#5 235 is shown, and UE#6 236 may be Figure 2 UE#6 236 is shown. The sidelink communication scenario between UE#5 235 and UE#6 236 can be one of the sidelink communication scenarios #A to #D in Table 1. The user plane protocol stack of each of UE#5 235 and UE#6 236 can include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.

[0098] Sidelink communication between UE#5 235 and UE#6 236 may be performed using a PC5 interface (e.g., a PC5-U interface). A Layer 2 identifier (ID) (e.g., a source Layer 2 ID, a destination Layer 2 ID) may be used for sidelink communication, and the Layer 2 ID may be an ID configured for V2X communication. Furthermore, in sidelink communication, hybrid automatic repeat request (HARQ) feedback operation may be supported, and RLC acknowledged mode (AM) or RLC unacknowledged mode (UM) may be supported.

[0099] On the other hand, the control plane protocol stack of the UEs (eg, UE#5 235 and UE#6 236) performing sidelink communication may be configured as follows.

[0100] Figure 7 is a block diagram illustrating a first exemplary embodiment of a control plane protocol stack of a UE performing sidelink communication, Figure 8 is a block diagram illustrating a second exemplary embodiment of a control plane protocol stack of a UE performing sidelink communication.

[0101] like Figure 7 and Figure 8 As shown, UE#5 235 can be Figure 2 UE#5 235 is shown, and UE#6 236 may be Figure 2 UE#6 236 is shown. The sidelink communication scenario between UE#5 235 and UE#6 236 can be one of the sidelink communication scenarios #A to #D in Table 1. Figure 7The control plane protocol stack shown may be a control plane protocol stack for sending and receiving broadcast information (eg, Physical Sidelink Broadcast Channel (PSBCH)).

[0102] Figure 7 The control plane protocol stack shown may include a PHY layer, a MAC layer, an RLC layer, and a radio resource control (RRC) layer. Sidelink communication between UE#5 235 and UE#6 236 may be performed using a PC5 interface (eg, a PC5-C interface). Figure 8 The control plane protocol stack shown may be a control plane protocol stack for one-to-one sidelink communication. Figure 8 The control plane protocol stack shown may include a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and a PC5 signaling protocol layer.

[0103] On the other hand, channels utilized in sidelink communications between UE#5 235 and UE#6 236 may include a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH). The PSSCH may be used to transmit and receive sidelink data and may be configured in the UE (e.g., UE#5 235 or UE#6 236) through higher layer signaling. The PSCCH may be used to transmit and receive sidelink control information (SCI) and may also be configured in the UE (e.g., UE#5 235 or UE#6 236) through higher layer signaling.

[0104] The PSDCH may be used for the discovery process. For example, a discovery signal may be transmitted via the PSDCH. The PSBCH may be used to send and receive broadcast information (e.g., system information). In addition, a demodulation reference signal (DM-RS), synchronization signal, etc. may be utilized in the sidelink communication between UE#5 235 and UE#6 236. The synchronization signal may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS).

[0105] On the other hand, the sidelink transmission modes (TM) can be divided into sidelink TM#1 to TM#4, as shown in Table 2 below.

[0106] [Table 2]

[0107] SidelinkTM illustrate #1 Transmission using resources scheduled by the base station #2 UE automatic transmission without base station scheduling #3 Transmission using resources scheduled by base stations in V2X communications #4 UE automatic transmission in V2X communication without base station scheduling

[0108] When sidelink TM#3 or TM#4 is supported, each of UE#5 235 and UE#6 236 may perform sidelink communication using a resource pool configured by base station 210. A resource pool may be configured for each of sidelink control information and sidelink data.

[0109] The resource pool for sidelink control information can be configured based on an RRC signaling process (e.g., a dedicated RRC signaling process, a broadcast RRC signaling process). The resource pool for receiving sidelink control information can be configured through a broadcast RRC signaling process. When sidelink TM#3 is supported, the resource pool for transmitting sidelink control information can be configured through a dedicated RRC signaling process. In this case, the sidelink control information can be transmitted via resources scheduled by the base station 210 within the resource pool configured through the dedicated RRC signaling process. When sidelink TM#4 is supported, the resource pool for transmitting sidelink control information can be configured through a dedicated RRC signaling process or a broadcast RRC signaling process. In this case, the sidelink control information can be transmitted via resources automatically selected by the UE (e.g., UE#5 235 or UE#6 236) within the resource pool configured through the dedicated RRC signaling process or the broadcast RRC signaling process.

[0110] When sidelink TM#3 is supported, a resource pool for transmitting and receiving sidelink data may not be configured. In this case, sidelink data may be transmitted and received using resources scheduled by base station 210. When sidelink TM#4 is supported, a resource pool for transmitting and receiving sidelink data may be configured using a dedicated RRC signaling procedure or a broadcast RRC signaling procedure. In this case, sidelink data may be transmitted and received using resources automatically selected by a UE (e.g., UE#5 235 or UE#6 236) within a resource pool configured using a dedicated RRC signaling procedure or a broadcast RRC signaling procedure.

[0111] In the following, the side link communication method will be described. Even when describing a method performed at a first communication node in a communication node (e.g., sending or receiving a signal), the corresponding second communication node may also perform a method corresponding to the method performed at the first communication node (e.g., receiving or sending a signal). That is, when describing the operation of UE#1 (e.g., vehicle #1), the corresponding UE#2 (e.g., vehicle #2) may perform an operation corresponding to the operation of UE#1. Conversely, when describing the operation of UE#2, the corresponding UE#1 may perform an operation corresponding to the operation of UE#2. In the exemplary embodiment described below, the operation of the vehicle may be the operation of a communication node located in the vehicle.

[0112] The sidelink signal may be a synchronization signal and a reference signal used for sidelink communication. For example, the synchronization signal may be a synchronization signal / physical broadcast channel (SS / PBCH) block, a sidelink synchronization signal (SLSS), a primary sidelink synchronization signal (PSSS), a secondary sidelink synchronization signal (SSSS), etc. The reference signal may be a channel state information-reference signal (CSI-RS), a DM-RS, a phase tracking-reference signal (PT-RS), a cell specific reference signal (CRS), a sounding reference signal (SRS), a discovery reference signal (DRS), etc.

[0113] The sidelink channel may be a PSSCH, PSCCH, PSDCH, PSBCH, physical sidelink feedback channel (PSFCH), etc. In addition, the sidelink channel may refer to a sidelink channel including a sidelink signal mapped to specific resources in the corresponding sidelink channel. Sidelink communication may support broadcast services, multicast services, groupcast services, and unicast services.

[0114] The base station may transmit system information (e.g., SIB12, SIB13, SIB14) and RRC messages including configuration information for sidelink communication (i.e., sidelink configuration information) to the UE. The UE may receive the system information and RRC messages from the base station, identify the sidelink configuration information included in the system information and RRC messages, and perform sidelink communication based on the sidelink configuration information. SIB12 may include sidelink communication / discovery configuration information. SIB13 and SIB14 may include configuration information for V2X sidelink communication.

[0115] Sidelink communications can be performed within the SL bandwidth part (BWP). The base station can configure the SL BWP for the UE using higher-layer signaling. The higher-layer signaling can include SL-BWP-Config and / or SL-BWP-ConfigCommon. SL-BWP-Config can be used to configure the SL BWP for UE-specific sidelink communications. SL-BWP-ConfigCommon can be used to configure cell-specific configuration information.

[0116] In addition, the base station may configure a resource pool for the UE using higher-layer signaling. The higher-layer signaling may include SL-BWP-PoolConfig, SL-BWP-PoolConfigCommon, SL-BWP-DiscPoolConfig, and / or SL-BWP-DiscPoolConfigCommon. SL-BWP-PoolConfig may be used to configure a sidelink communication resource pool. SL-BWP-PoolConfigCommon may be used to configure a cell-specific sidelink communication resource pool. SL-BWP-DiscPoolConfig may be used to configure a resource pool dedicated to UE-specific sidelink discovery. SL-BWP-DiscPoolConfigCommon may be used to configure a resource pool dedicated to cell-specific sidelink discovery. The UE may perform sidelink communication within the resource pool configured by the base station.

[0117] Sidelink communication can support SL discontinuous reception (DRX) operation. The base station can send a higher layer message (e.g., SL-DRX-Config) including parameters related to SL DRX to the UE. The UE can perform SL DRX operation based on the SL-DRX-Config received from the base station. Sidelink communication can support inter-UE coordination operation. The base station can send a higher layer message (e.g., SL-InterUE-CoordinationConfig) including inter-UE coordination parameters to the UE. The UE can perform inter-UE coordination operation based on the SL-InterUE-CoordinationConfig received from the base station.

[0118] The side link communication can be performed based on a single SCI scheme or a multi-SCI scheme. When the single SCI scheme is used, the side link communication can be performed based on one SCI (e.g., the first phase SCI (1 st -stage SCI)) to perform data transmission (e.g., sidelink data transmission, sidelink shared channel (SL-SCH) transmission). When a multi-SCI scheme is used, two SCIs (e.g., first-stage SCI and second-stage SCI (2 nd-stage SCI)) to perform data transmission. SCI can be transmitted on PSCCH and / or PSSCH. When a single SCI scheme is utilized, SCI (e.g., first-stage SCI) can be transmitted on PSCCH. When a multi-SCI scheme is utilized, first-stage SCI can be transmitted on PSCCH, and second-stage SCI can be transmitted on PSCCH or PSSCH. The first-stage SCI can be referred to as "first-stage SCI (first-stage SCI)", and the second-stage SCI can be referred to as "second-stage SCI (second-stage SCI)". The format of the first-stage SCI may include SCI format 1-A, and the format of the second-stage SCI may include SCI format 2-A, SCI format 2-B, and SCI format 2-C.

[0119] SCI format 1-A can be used to schedule PSSCH and second-stage SCI. SCI format 1-A may include at least one of priority information, frequency resource allocation information, time resource allocation information, resource reservation period information, demodulation reference signal (DMRS) pattern information, second-stage SCI format information, beta_offset indicator, number of DMRS ports, modulation and coding scheme (MCS) information, additional MCS table indicator, PSFCH overhead indicator, or conflicting information receiver flag.

[0120] SCI format 2-A can be used for decoding PSSCH. SCI format 2-A can include the HARQ process number At least one of a new data indicator (NDI), a redundancy version (RV), a source ID, a destination ID, a HARQ feedback enable / disable indicator, a cast type indicator, or a CSI request.

[0121] SCI format 2-B may be used for decoding of PSSCH. SCI format 2-B may include at least one of a HARQ process number, NDI, RV, source ID, destination ID, HARQ feedback enable / disable indicator, zone ID, or communication range requirement.

[0122] SCI format 2-C can be used for decoding the PSSCH. In addition, SCI format 2-C can be used to provide or request inter-UE coordination information. SCI format 2-C may include at least one of a HARQ process number, NDI, RV, source ID, destination ID, HARQ feedback enable / disable indicator, CSI request, or provide / request indicator.

[0123] When the value of the provision / request indicator is set to 0, this may indicate that SCI format 2-C is used to provide inter-UE coordination information. In this case, SCI format 2-C may include at least one of a resource combination, a first resource position, a reference time slot position, a resource set type, or a lowest subchannel index.

[0124] When the value of the offer / request indicator is set to 1, this may indicate that SCI format 2-C is used to request inter-UE coordination information. In this case, SCI format 2-C may include at least one of a priority, a number of subchannels, a resource reservation period, a resource selection window position, a resource set type, or a padding bit.

[0125] On the other hand, sidelink communication can be performed in a licensed band and / or an unlicensed band. Sidelink communication performed in an unlicensed band can be referred to as sidelink-unlicensed band (SL-U) communication or unlicensed band-sidelink (U-SL) communication. In SL-U communication, the first terminal can perform communication with the second terminal according to mode 1 or mode 2. When mode 1 is used, the first terminal can perform communication with the second terminal based on the scheduling of the base station. When mode 2 is used, the first terminal can perform communication with the second terminal without the scheduling of the base station. Mode 1 can be the sidelink TM#1 or TM#3 disclosed in Table 2 above. Mode 2 can be the sidelink TM#2 or TM#4 disclosed in Table 2 above.

[0126] Figure 9 is a timing diagram illustrating an embodiment of a communication method in an unlicensed band.

[0127] refer to Figure 9, the base station may perform a listen before talk (LBT) operation to perform downlink (DL) transmission, and if the result of the LBT operation is an idle state (e.g., a clean state) of the channel, the base station may perform DL transmission. The terminal may perform an LBT operation to perform uplink (UL) transmission, and if the result of the LBT operation is an idle state of the channel, the terminal may perform UL transmission. If the result of the LBT operation is a busy state of the channel, DL transmission and / or UL transmission may not be performed. DL transmission and / or UL transmission may be performed within the channel occupancy time (COT). The COT may be initiated by the base station or the terminal. The LBT operation may be performed based on the categories disclosed in Table 3 below.

[0128] [Table 3]

[0129]

[0130] LBT operation may mean clear channel assessment (CCA) operation. The CCA operation may be performed during the CCA period. When performing the CCA operation, the communication node (e.g., a base station and / or a terminal) may check the channel state based on an energy detection (ED) method. In other words, the communication node may check whether there is another signal in the channel. If the energy detected during the CCA period is less than a threshold value (e.g., an ED threshold value), the communication node may determine that the channel state is an idle state. In other words, the communication node may determine that there are no other signals in the channel. If the channel state is an idle state, the communication node may access a channel within the COT. If the energy detected during the CCA period is greater than or equal to a threshold value, the communication node may determine that the channel state is a busy state. In other words, the communication node may determine that there is another signal in the channel. If the channel state is a busy state, the communication node will not access a channel within the COT.

[0131] In an unlicensed band, a communication node may perform an LBT operation and transmit data when the result of the LBT operation is an idle state of the channel. In this case, the base station may transmit a DL transmission burst within the COT, and the terminal may transmit an UL transmission burst within the COT. The COT may be set within the maximum COT (maximum COT, MCOT). The time slot duration of the CCA may be 5μs to 9μs. The duration of the MCOT may be 8ms. The base station may initiate and / or configure the COT based on a higher layer parameter SemiStaticChannelAccessConfig. SemiStaticChannelAccessConfig may include period information of the COT. The terminal may identify the COT initiated by the base station based on the SemiStaticChannelAccessConfig.

[0132] The terminal can initiate and / or configure COT based on the higher-layer parameter SemiStaticChannelAccessConfigUE. SemiStaticChannelAccessConfigUE can include period information and offset information of COT. The base station can identify COT initiated by the terminal based on SemiStaticChannelAccessConfigUE.

[0133] The terminal can initiate and / or configure COT based on SemiStaticChannelAccessConfigUE in the unlicensed band. Alternatively, the base station can signal the terminal SemiStaticChannelAccessConfigSL-U of the COT for SL-U communication. The COT for SL-U communication can be called sidelink (SL)-COT. SemiStaticChannelAccessConfigSL-U may include period information and offset information of SL-COT. The terminal can configure SL-COT based on SemiStaticChannelAccessConfigSL-U. Other terminals can recognize the COT initiated based on SemiStaticChannelAccessConfigSL-U.

[0134] In an unlicensed band, a terminal may perform an LBT operation before SL communication (e.g., transmission of SL data) to enable SL communication. If the LBT operation is successful, a COT may be initiated in the unlicensed band, and SL communication may be performed within the COT. "Successful LBT operation" may mean that "the result of the LBT operation is an idle state."

[0135] In an unlicensed band, a channel access procedure may be classified into a DL channel access procedure and a UL channel access procedure. The DL channel access procedure may be classified into a Type 1 DL channel access procedure and a Type 2 DL channel access procedure. A Type 1 DL channel access procedure may be performed for initiation of a COT. A Type 2 DL channel access procedure may be performed for transmission within a COT (e.g., a shared COT). The channel access procedure may imply an LBT operation. A Type 1 DL channel access procedure may be performed for "at least one of a physical downlink shared channel (PDSCH) transmission, a physical downlink control channel (PDCCH) transmission, and an enhanced PDCCH (EPDCCH) transmission initiated by an eNB" and / or "any transmission initiated by a gNB." An eNB may mean a base station in a 4G communication system, and a gNB may mean a base station in a 5G communication system.

[0136] A Type 2 DL channel access procedure may be performed for "at least one of an eNB-initiated discovery burst transmission or a transmission not including a PDSCH" and / or "a gNB-initiated discovery burst transmission or a discovery transmission multiplexed with non-unicast information." The Type 2 DL channel access procedure may be categorized as a Type 2A DL channel access procedure, a Type 2B DL channel access procedure, and a Type 2C DL channel access procedure. The length of the sensing period (e.g., sensing interval) in each of the Type 2A DL channel access procedure, the Type 2B DL channel access procedure, and the Type 2C DL channel access procedure may differ. The length of the sensing interval in the Type 2A DL channel access procedure may be 25 μs. The length of the sensing interval in the Type 2B DL channel access procedure may be 16 μs. No sensing operation may be performed in the Type 2C DL channel access procedure.

[0137] The UL channel access procedure can be categorized as a Type 1 UL channel access procedure and a Type 2 UL channel access procedure. The Type 1 UL channel access procedure can be performed for initiating a Coordinated Transmission (COT). The Type 2 UL channel access procedure can be performed for transmissions within a Coordinated Transmission (COT) (e.g., a shared COT). The Type 1 UL channel access procedure can be performed for "at least one of a physical uplink shared channel (PUSCH) transmission or a sounding reference signal (SRS) transmission scheduled or configured by the eNB," "at least one of a PUSCH transmission or an SRS transmission scheduled or configured by the gNB," "PUCCH transmission scheduled or configured by the gNB," and / or "transmissions related to a random access (RA) procedure."

[0138] The Type 2 UL channel access procedure can be classified into a Type 2A UL channel access procedure, a Type 2B UL channel access procedure, and a Type 2C UL channel access procedure. The length of the sensing period (e.g., sensing interval) in each of the Type 2A UL channel access procedure, the Type 2B UL channel access procedure, and the Type 2C UL channel access procedure may be different. The length of the sensing period in the Type 2A UL channel access procedure may be 25 μs. The length of the sensing period in the Type 2B UL channel access procedure may be 16 μs. No sensing operation may be performed in the Type 2C UL channel access procedure.

[0139] A Type 1 DL channel access procedure, a Type 2 DL channel access procedure, a Type 1 UL channel access procedure, and / or a Type 2 UL channel access procedure may be used for SL-U communication. In this case, in the description of the Type 1 DL channel access procedure, the Type 2 DL channel access procedure, the Type 1 UL channel access procedure, and / or the Type 2 UL channel access procedure, the downlink channel and / or the uplink channel may be interpreted as a sidelink channel. The LBT operation may be interpreted as a Type 1 DL channel access procedure, a Type 2 DL channel access procedure, a new DL channel access procedure, a Type 1 UL channel access procedure, a Type 2 UL channel access procedure, and / or a new UL channel access procedure.

[0140] The UE may perform a SL channel access procedure. The SL channel access procedure may be performed to access a channel in an unlicensed frequency band. The SL channel access procedure may be classified into a type 1 SL channel access procedure and a type 2 SL channel access procedure. The type 2 SL channel access procedure may be classified into a type 2A SL channel access procedure, a type 2B SL channel access procedure, and a type 2C SL channel access procedure. The type 1 SL channel access procedure may be performed to initiate a COT. The type 2 SL channel access procedure may be performed for SL transmission within a COT (e.g., a shared COT, an initiated COT). In the type 1 SL channel access procedure, the UE may perform a random backoff operation. In the type 2 SL channel access procedure, the UE may perform a channel sensing operation. The channel sensing operation may be performed within a sensing period. In the type 2A DL channel access procedure, the length of the sensing period may be 25 μs. In the type 2B DL channel access procedure, the length of the sensing interval may be 16 μs. In the type 2C DL channel access procedure, no sensing operation may be performed.

[0141] The UE may initiate COT. COT may stand for channel occupancy (CO). The UE that initiates COT may be referred to as a COT initiating UE or an initiating UE. The signal initially sent by the COT initiating UE for initiating COT may be referred to as a COT initiating signal. The COT initiation signal may include a PSCCH, a PSSCH, a sidelink (S)-synchronization signal block (SSB) and / or a reference signal. The COT initiation signal may include COT shared information. Alternatively, the COT shared information may be sent independently of the COT initiation signal. The COT shared information (e.g., a COT initiation signal including COT shared information) may be sent to the UE via signaling. In the present invention, the signaling may be at least one of higher layer signaling (e.g., transmission of an RRC message), MAC signaling (e.g., transmission of a MAC CE), or PHY signaling (e.g., transmission of an SCI).

[0142] The COT sharing information may include a source identifier (ID) (e.g., a Layer 1 source ID), a destination ID (e.g., a Layer 1 destination ID), a channel access priority class (CAPC) (e.g., a CAPC level), a remaining COT duration, a total COT duration, a maximum COT, frequency domain information of a resource block (RB) set (e.g., an applicable RB set) for the COT, additional IDs (e.g., additional source IDs, additional destination IDs), or at least one of an associated broadcast type. The remaining COT duration and the total COT duration may each be indicated in units of time slots or milliseconds (ms). The additional IDs may include a pair of a Layer 1 source ID and a Layer 1 destination ID. The source ID (e.g., a Layer 1 source ID) may be set to the source ID of the UE initiating the COT for unicast. The source ID (e.g., a Layer 1 source ID) may be set to a reserved bit for multicast and broadcast.

[0143] The destination ID of SL transmissions performed in a COT shared by COT sharing information may match the source ID (e.g., additional source ID) included in the COT sharing information, and the source ID of SL transmissions performed in a COT shared by COT sharing information may match the destination ID (e.g., additional destination ID) included in the COT sharing information. SL transmissions in a COT shared by COT sharing information may be performed within the frequency resources (e.g., RB set) indicated by the "frequency domain information for RB set" included in the COT sharing information. SL transmissions having the same CAPC as the CAPC included in the COT sharing information may be performed in a COT shared by COT sharing information. Alternatively, SL transmissions associated with a CAPC having a higher priority than the CAPC included in the COT sharing information may be performed in a COT shared by COT sharing information. SL transmissions in a COT shared by COT sharing information may be performed based on the broadcast type (e.g., unicast, multicast, and / or broadcast) indicated by the "associated broadcast type" included in the COT sharing information.

[0144] A target RX-UE may refer to an RX-UE that is a reception target (e.g., destination) of a transmission signal (e.g., SL transmission) for a TX-UE. A non-target RX-UE may refer to an RX-UE that attempts (e.g., can attempt) to receive the transmission signal of the TX-UE in a UE other than the reception target of the transmission signal of the TX-UE. In other words, the non-target RX-UE is not a reception target of the transmission signal of the TX-UE, but can decode the transmission signal of the TX-UE.

[0145] Within the shared COT, the UE may receive SL transmission from the COT-initiated UE. When receiving SL transmission from the COT-initiated UE, the UE may perform SL transmission after performing a Type 1 SL channel access procedure or a Type 2 SL channel access procedure within the shared COT. In the present invention, SL transmission may mean transmission of an SL channel and / or an SL signal. The SL channel may be a PSSCH, PSCCH, PSDCH, PSBCH, and / or PSFCH. The SL signal may be an S-SSB and / or a reference signal. The SL transmission from the COT-initiated UE may include COT shared information.

[0146] UEs that have received SL transmissions from a COT-initiating UE (e.g., UEs that perform SL transmissions within a shared COT) may be restricted to target RX-UEs for the COT-initiating UE. In other words, target RX-UEs that have successfully decoded SL transmissions from a COT-initiating UE may use the shared COT, and non-target RX-UEs that have successfully decoded SL transmissions from a COT-initiating UE may not use the shared COT. Alternatively, UEs that receive SL transmissions from a COT-initiating UE (e.g., UEs that perform SL transmissions within a shared COT) may include target RX-UEs and non-target RX-UEs for the COT-initiating UE.

[0147] Depending on the broadcast type (e.g., unicast, groupcast, broadcast) of the SL transmission transmitted by the COT-initiating UE, the UE (e.g., a UE that has received the SL transmission of the COT-initiating UE) can perform a channel access procedure (e.g., a type 1 SL channel access procedure and / or a type 2 SL channel access procedure) for a specific broadcast type or a specific SL transmission (e.g., transmission of a specific SL channel and / or a specific SL signal) within a shared COT (e.g., a COT shared by the COT-initiating UE).

[0148] If predefined conditions are met, the UE can perform the channel access procedure for SL transmission within the shared COT. A UE that can perform the channel access procedure for SL transmission within the shared COT may be referred to as a "connectable UE." In other words, a UE that meets the predefined conditions for performing the channel access procedure within the shared COT may be a connectable UE. The predefined conditions may be as follows.

[0149] - Condition 1: The UE is the UE that initiates the COT and has received the COT sharing information

[0150] -Condition 2: The UE is the target RX-UE for the COT initiation signal

[0151] -Condition 3: UE has successfully decoded the COT initiation signal

[0152] In addition to the above conditions, various conditions may be used to determine whether the channel access procedure for SL transmission is allowed within the shared COT. In the absence of predefined conditions (eg, no conditions are set in the UE), all UEs may be connectable UEs.

[0153] Depending on the broadcast type of the SL transmission (e.g., COT shared information) transmitted by the COT-initiating UE, a UE that has received the SL transmission may be allowed to perform a channel access procedure for a specific broadcast type and / or a specific SL transmission within the shared COT. In this case, the occurrence of conflicts caused by channel access procedures for UEs within a COT (e.g., a shared COT) may be reduced, and resource efficiency in the unlicensed band may be improved.

[0154] The broadcast type of the SL transmission transmitted by the COT initiated UE may be indicated by a field (e.g., an information element) included in the SCI. For example, a broadcast type indicator included in SCI format 1-B and / or SCI format 2-A may indicate the broadcast type of the SL transmission. Alternatively, a combination of fields (e.g., a hybrid automatic repeat request (HARQ) feedback enable / disable indicator and / or a broadcast type indicator) included in the first stage SCI (e.g., SCI format 1-A and / or 1-B) and / or the second stage SCI (e.g., SCI format 2-A, 2-B, 2-C and / or 2-D) may indicate the broadcast type of the SL transmission transmitted by the COT initiated UE. Alternatively, the COT shared information included in the SL transmission transmitted by the COT initiated UE may include an information element (e.g., a 2-bit indicator) indicating the broadcast type of the SL transmission. For example, the associated broadcast type (e.g., additional ID and associated broadcast type) included in the COT shared information may indicate the broadcast type of the SL transmission including the COT shared information. Alternatively, the associated broadcast type included in the COT shared information may indicate the broadcast type allowed in the shared COT according to the COT shared information.

[0155] [Implementation 1] Based on COT shared information, specific broadcast types and / or specific SL transmissions can be allowed within the shared COT.

[0156] The COT sharing information may mean a COT initiation signal. For example, the COT initiation signal may include the COT sharing information. The COT initiating UE may transmit the COT sharing information with a specific broadcast type. In other words, the COT sharing information may be associated with a specific broadcast type transmission. For example, the COT initiating UE may transmit the COT sharing information based on a specific broadcast type (e.g., unicast, multicast, broadcast). Alternatively, the COT initiating UE may transmit the COT sharing information including information indicating a specific broadcast type. The UE may receive the COT sharing information from the COT initiating UE and perform SL transmission with a specific broadcast type based on the COT sharing information within the shared COT. Depending on the broadcast type of the COT sharing information, a specific broadcast type and / or a specific SL transmission may be allowed within the shared COT. Unicast SL transmission may mean SL transmission based on a unicast method (e.g., SL transmission with unicast). Multicast SL transmission may mean SL transmission based on a multicast method (e.g., SL transmission with multicast). Broadcast SL transmission may mean SL transmission based on a broadcast method (e.g., SL transmission with broadcast). Transmission of SLs within the shared COT based on the COT shared information may be performed based on the same broadcast type (e.g., unicast, multicast, broadcast) as the broadcast type used for transmission of the COT shared information (e.g., the broadcast type applied to transmission of the COT shared information). Alternatively, transmission of SLs within the shared COT based on the COT shared information may be performed based on the broadcast type indicated by information included in the COT shared information.

[0157] Transmission of COT shared information using broadcasting (e.g., transmission of COT shared information based on a broadcasting method)

[0158] When a UE initiating from a COT receives COT sharing information utilizing broadcast (e.g., COT sharing information associated with broadcast transmission), the UE may perform SL transmission within the shared COT based on the following method. In other words, when the following conditions are met, the UE may perform a channel access procedure for SL transmission (e.g., a type 2 SL channel access procedure) within the shared COT. "Utilizing broadcast COT sharing information" may mean "applying broadcast to the shared COT according to the COT sharing information." The "associated broadcast type" included in the COT sharing information and / or the "broadcast type indicator" included in the SCI containing the COT sharing information (e.g., the SCI associated with the COT sharing information) may be set to 00 indicating broadcast.

[0159] (Method 1) The UE may perform broadcast SL transmission within a shared COT. In other words, the UE may be allowed to perform a channel access procedure for broadcast SL transmission within the shared COT. The source ID of the broadcast SL transmission may match the destination ID included in the COT shared information (e.g., COT shared information associated with the broadcast transmission), and the destination ID of the broadcast SL transmission may match the source ID included in the COT shared information (e.g., COT shared information associated with the broadcast transmission). Alternatively, the source ID and destination ID of the broadcast SL transmission may match a pair of additional IDs included in the COT shared information (e.g., COT shared information associated with the broadcast transmission).

[0160] (Method 2) Regardless of the broadcast type, all UEs can perform SL transmission within the shared COT. In other words, regardless of the broadcast type, all UEs can be allowed to perform the channel access procedure for SL transmission within the shared COT.

[0161] (Method 3) If the reception target (e.g., target RX-UE) for SL transmission of a UE is a COT-initiating UE, the UE can perform SL transmission within the shared COT regardless of the broadcast type. In other words, regardless of the broadcast type, the UE can be allowed to perform the channel access procedure for SL transmission to the COT-initiating UE within the shared COT.

[0162] (Method 4) If the receiving target (e.g., target RX-UE) of the unicast SL transmission for a UE is a COT-initiating UE, the UE may perform unicast SL transmission within the shared COT. In other words, the UE may be allowed to perform the channel access procedure for unicast SL transmission to the COT-initiating UE within the shared COT.

[0163] (Method 5) If the reception target (e.g., target RX-UE group) for a UE's multicast SL transmission includes a COT-initiating UE, the UE may perform multicast SL transmission within a shared COT. In other words, the UE may be allowed to perform a channel access procedure within the shared COT for multicast SL transmission to the reception target including the COT-initiating UE.

[0164] (Method 6) The UE may perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission. In other words, the UE may be allowed to perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission.

[0165] (Method 7) The UE may perform multicast SL transmission within the shared COT without placing any restrictions on the reception targets for multicast SL transmission. In other words, the UE may be allowed to perform multicast SL transmission within the shared COT without placing any restrictions on the reception targets for multicast SL transmission.

[0166] (Method 8) If the reception target of the PSFCH transmission for the UE is a COT-initiating UE, the UE may perform PSFCH transmission to the COT-initiating UE within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for PSFCH transmission to the COT-initiating UE within the shared COT.

[0167] (Method 9) Regardless of the reception target of the UE's PSFCH transmission, the UE can perform PSFCH transmission within the shared COT. In other words, regardless of the reception target of the PSFCH transmission, the UE can be allowed to perform the channel access procedure for PSFCH transmission within the shared COT.

[0168] A combination of one or more of the above-mentioned methods 1 to 9 may be applied. For example, in the case of applying a combination of methods 1, 4, and 5, upon receiving COT sharing information (e.g., a COT initiation signal) using broadcast, the UE may perform broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or multicast SL transmission to a receiving target including the COT initiating UE within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or multicast SL transmission to a receiving target including the COT initiating UE within the shared COT.

[0169] For another example, when a combination of Method 1, Method 7, and Method 9 is applied, if broadcast COT sharing information (e.g., a COT initiation signal) is received, the UE may perform broadcast SL transmission, multicast SL transmission, and / or PSFCH transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for broadcast SL transmission, multicast SL transmission, and / or PSFCH transmission within the shared COT.

[0170] Transmission of COT shared information using multicast (e.g., transmission of COT shared information based on a multicast method)

[0171] When COT sharing information utilizing multicast (e.g., a COT initiation signal) is received from a COT initiating UE, the UE may perform SL transmission within the shared COT based on the following method. In other words, when the following conditions are met, the UE may perform a channel access procedure for SL transmission (e.g., a type 2 SL channel access procedure) within the shared COT. "COT sharing information utilizing multicast" may mean "applying multicast to the shared COT according to the COT sharing information." The "associated broadcast type" included in the COT sharing information and / or the "broadcast type indicator" included in the SCI containing the COT sharing information (e.g., the SCI associated with the COT sharing information) may be set to 01 or 11 indicating multicast.

[0172] (Method 10) The UE may perform multicast SL transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for multicast SL transmission within the shared COT. The source ID of the multicast SL transmission may match the destination ID included in the COT shared information (e.g., COT shared information associated with the multicast transmission), and the destination ID of the multicast SL transmission may match the source ID included in the COT shared information (e.g., COT shared information associated with the multicast transmission). Alternatively, the source ID and destination ID of the multicast SL transmission may match a pair of additional IDs included in the COT shared information (e.g., COT shared information associated with the multicast transmission).

[0173] (Method 11) Regardless of the broadcast type, all UEs can perform SL transmission within the shared COT. In other words, regardless of the broadcast type, all UEs can be allowed to perform the channel access procedure for SL transmission within the shared COT.

[0174] (Method 12) If the reception target (e.g., target RX-UE) for SL transmission of a UE is a COT-initiating UE, the UE may perform SL transmission within the shared COT regardless of the broadcast type. In other words, regardless of the broadcast type, the UE may be allowed to perform a channel access procedure for SL transmission to the COT-initiating UE within the shared COT.

[0175] (Method 13) If the receiving target (e.g., target RX-UE) of the unicast SL transmission for a UE is a COT-initiating UE, the UE may perform unicast SL transmission within the shared COT. In other words, the UE may be allowed to perform the channel access procedure for unicast SL transmission to the COT-initiating UE within the shared COT.

[0176] (Method 14) If the reception target (e.g., target RX-UE group) for multicast SL transmission for a UE includes a COT-initiating UE, the UE may perform multicast SL transmission within a shared COT. In other words, the UE may be allowed to perform a channel access procedure for multicast SL transmission to the reception target including the COT-initiating UE within the shared COT.

[0177] (Method 15) The UE may perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission. In other words, the UE may be allowed to perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission.

[0178] (Method 16) The UE may perform multicast SL transmission within the shared COT without placing any restrictions on the reception targets for multicast SL transmission. In other words, the UE may be allowed to perform multicast SL transmission within the shared COT without placing any restrictions on the reception targets for multicast SL transmission.

[0179] (Method 17) If the reception target of the PSFCH transmission for the UE is a COT-initiating UE, the UE may perform PSFCH transmission to the COT-initiating UE within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for PSFCH transmission to the COT-initiating UE within the shared COT.

[0180] (Method 18) Regardless of the reception target of the UE's PSFCH transmission, the UE can perform PSFCH transmission within the shared COT. In other words, regardless of the reception target of the PSFCH transmission, the UE can be allowed to perform the channel access procedure for PSFCH transmission within the shared COT.

[0181] (Method 19) The UE may perform broadcast SL transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for broadcast SL transmission within the shared COT.

[0182] A combination of one or more of the above-described methods 10 to 19 may be applied. For example, when a combination of methods 13, 17, and 19 is applied, upon receiving COT sharing information (e.g., a COT initiation signal) using multicast, the UE may perform broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or PSFCH transmission to the COT initiating UE within the shared COT. In other words, the UE may be allowed to perform channel access procedures for broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or PSFCH transmission to the COT initiating UE within the shared COT.

[0183] Transmission of COT shared information using unicast (e.g., transmission of COT shared information based on a unicast method)

[0184] When COT sharing information utilizing unicast (e.g., a COT initiation signal) is received from a COT initiating UE, the UE may perform SL transmission within the shared COT based on the following method. In other words, when the following conditions are met, the UE may perform a channel access procedure for SL transmission (e.g., a type 2 SL channel access procedure) within the shared COT. "COT sharing information utilizing unicast" may mean "applying unicast to the shared COT according to the COT sharing information." The "associated broadcast type" included in the COT sharing information and / or the "broadcast type indicator" included in the SCI containing the COT sharing information (e.g., the SCI associated with the COT sharing information) may be set to 10 indicating unicast.

[0185] (Method 20) The UE may perform unicast SL transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for unicast SL transmission within the shared COT. The source ID of the unicast SL transmission may match the destination ID included in the COT shared information (e.g., COT shared information associated with the unicast transmission), and the destination ID of the unicast SL transmission may match the source ID included in the COT shared information (e.g., COT shared information associated with the unicast transmission). Alternatively, the source ID and destination ID of the unicast SL transmission may match a pair of additional IDs included in the COT shared information (e.g., COT shared information associated with the unicast transmission).

[0186] (Method 21) Regardless of the broadcast type, all UEs can perform SL transmission within the shared COT. In other words, regardless of the broadcast type, all UEs can be allowed to perform the channel access procedure for SL transmission within the shared COT.

[0187] (Method 22) If the reception target (e.g., target RX-UE) for SL transmission of a UE is a COT-initiating UE, the UE may perform SL transmission within the shared COT regardless of the broadcast type. In other words, regardless of the broadcast type, the UE may be allowed to perform a channel access procedure for SL transmission to the COT-initiating UE within the shared COT.

[0188] (Method 23) If the receiving target (e.g., target RX-UE) of the unicast SL transmission for a UE is a COT-initiating UE, the UE may perform unicast SL transmission within the shared COT. In other words, the UE may be allowed to perform the channel access procedure for unicast SL transmission to the COT-initiating UE within the shared COT.

[0189] (Method 24) If the reception target (e.g., target RX-UE group) of the multicast SL transmission for the UE includes the COT initiating UE, the UE may perform the multicast SL transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for the multicast SL transmission to the reception target including the COT initiating UE within the shared COT.

[0190] (Method 25) The UE may perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission. In other words, the UE may be allowed to perform unicast SL transmission within the shared COT without placing any restrictions on the reception target for unicast SL transmission.

[0191] (Method 26) The UE may perform multicast SL transmission within the shared COT without placing any restrictions on the reception target for multicast SL transmission. In other words, the UE may be allowed to perform multicast SL transmission within the shared COT without placing any restrictions on the reception target for multicast SL transmission.

[0192] (Method 27) If the reception target of the PSFCH transmission for the UE is a COT-initiating UE, the UE may perform PSFCH transmission to the COT-initiating UE within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for PSFCH transmission to the COT-initiating UE within the shared COT.

[0193] (Method 28) Regardless of the reception target for the UE's PSFCH transmission, the UE can perform PSFCH transmission within the shared COT. In other words, regardless of the reception target for the PSFCH transmission, the UE can be allowed to perform the channel access procedure for PSFCH transmission within the shared COT.

[0194] (Method 29) The UE may perform broadcast SL transmission within the shared COT. In other words, the UE may be allowed to perform a channel access procedure for broadcast SL transmission within the shared COT.

[0195] A combination of one or more of the above methods 20 to 29 may be applied. For example, when a combination of methods 23, 27, and 29 is applied, upon receiving COT sharing information (e.g., a COT initiation signal) using unicast, the UE may perform broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or PSFCH transmission to the COT initiating UE within the shared COT. In other words, the UE may be allowed to perform channel access procedures for broadcast SL transmission, unicast SL transmission to the COT initiating UE, and / or PSFCH transmission to the COT initiating UE within the shared COT.

[0196] A combination of one or more of the above methods 1 to 29 may be applied. The combination of one or more methods may be configured and / or operated specifically for a resource pool (RP). Alternatively, the combination of one or more methods may be configured and / or operated specifically for a COT. Configuration information for a combination of one or more methods may be sent to the UE via signaling. The signaling may be at least one of system information (SI) signaling (e.g., transmission of an MIB and / or SIB), RRC signaling (e.g., transmission of an RRC message), MAC signaling (e.g., transmission of a MAC CE), or PHY signaling (e.g., transmission of an SCI). Configuration information for a combination of one or more methods may be included in COT shared information. The COT shared information may be included in a COT initiation signal. Each of the COT shared information and the COT initiation signal may be a MAC CE.

[0197] Figure 10 is a flow chart illustrating a first embodiment of the SL-U communication method.

[0198] refer to Figure 10 , the COT initiating UE may transmit SL transmission #1 including a COT initiation signal (e.g., COT sharing information). The UE may receive SL transmission #1 from the COT initiating UE and identify the COT initiation signal (e.g., COT sharing information) included in SL transmission #1. The UE may identify the shared COT (e.g., the COT initiated by the COT initiating UE) based on the COT sharing information. The UE may perform SL transmission utilizing a specific broadcast type and / or a specific SL transmission depending on the broadcast type of SL transmission #1 (e.g., COT initiation signal, COT sharing information) within a channel accessible area (e.g., a shared COT). In other words, the UE may be allowed to perform a channel access procedure for SL transmission utilizing a specific broadcast type and / or a specific SL transmission depending on the broadcast type of SL transmission #1 (e.g., COT initiation signal, COT sharing information) within the channel accessible area.

[0199] The above operations can be performed on a COT basis. In other words, the specific broadcast type transmissions and / or specific SL transmissions allowed in each COT can be independently configured. For example, the broadcast type transmissions allowed in a first COT can be different from the broadcast type transmissions allowed in a second COT. Channel access procedures can be performed for the same broadcast type transmission and / or the same SL transmission within the same COT.

[0200] [Implementation 2] The method and / or channel of SL transmission within a shared COT can be controlled or restricted based on the broadcast type of SL transmission initiated by the UE transmitted by the COT.

[0201] Figure 11 is a flow chart illustrating a second embodiment of the SL-U communication method.

[0202] refer to Figure 11 The method and / or channel for SL transmission within a shared COT may be determined based on the broadcast type of the SL transmission transmitted by the COT initiating UE (e.g., SL transmission other than the COT initiation signal and / or COT shared information). The COT initiating UE may transmit SL transmission #1 that includes the COT initiation signal and / or COT shared information, and may also transmit SL transmission #2 and SL transmission #3. SL transmission #2 and SL transmission #3 may not include the COT initiation signal and / or COT shared information.

[0203] The broadcast types of SL transmission #1, SL transmission #2, and SL transmission #3 may be the same. Alternatively, the broadcast types of SL transmission #1, SL transmission #2, and SL transmission #3 may be different. For example, SL transmission #1 may be a unicast SL transmission, SL transmission #2 may be a multicast SL transmission, and SL transmission #3 may be a broadcast SL transmission. In this case, in the channel accessible area #1 after SL transmission #1 using unicast, the UE may perform SL transmission based on a combination of one or more of the above-mentioned methods 20 to 29. Channel accessible area #1 may belong to a shared COT. In the channel accessible area #2 after SL transmission #2 using multicast, the UE may perform SL transmission based on a combination of one or more of the above-mentioned methods 10 to 19. Channel accessible area #2 may belong to a shared COT. In the channel accessible area #3 after SL transmission #3 using broadcast, the UE may perform SL transmission based on a combination of one or more of the above-mentioned methods 1 to 9. Channel accessible area #3 may belong to a shared COT.

[0204] Even when the broadcast type of SL transmission #1 to SL transmission #3 is the same, a combination of different methods may be used in the channel accessibility area. For example, when the broadcast type of SL transmission #1 to SL transmission #3 is multicast, the UE may perform SL transmission based on a first combination of one or more methods from Methods 10 to 19 in Channel Accessibility Area #1, the UE may perform SL transmission based on a second combination of one or more methods from Methods 10 to 19 in Channel Accessibility Area #2, and the UE may perform SL transmission based on a third combination of one or more methods from Methods 10 to 19 in Channel Accessibility Area #3. The methods included in the first combination, the second combination, and the third combination may be different from each other.

[0205] The methods proposed in Implementation 1 (e.g., Method 1 to Method 29), modifications of the methods, and / or extensions of the methods may be applied to each channel accessible area. Configuration information of a combination of methods for each channel accessible area may be sent to the UE via signaling. The signaling may be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling. For example, a MAC CE (e.g., COT shared information) included in SL transmission #1 may include configuration information of a combination of methods applied in channel accessible area #1 (e.g., part or all of the configuration information), a MAC CE (e.g., COT shared information) included in SL transmission #2 may include configuration information of a combination of methods applied in channel accessible area #2 (e.g., part or all of the configuration information), and a MAC CE (e.g., COT shared information) included in SL transmission #3 may include configuration information of a combination of methods applied in channel accessible area #3 (e.g., part or all of the configuration information).

[0206] As another example, the MAC CE (e.g., COT sharing information) included in SL transmission #1 may include configuration information of a combination of methods applied in channel accessible area #1 (e.g., part or all of the configuration information), configuration information of a combination of methods applied in channel accessible area #2 (e.g., part or all of the configuration information), and / or configuration information of a combination of methods applied in channel accessible area #3 (e.g., part or all of the configuration information).

[0207] Unlike Embodiment 1, according to Embodiment 2, the application method may vary depending on the SL transmission of the COT-initiating UE within one COT (eg, according to a channel accessible area of the SL transmission).

[0208] In embodiments 1 and 2, depending on the broadcast type of SL transmission transmitted by the COT-initiating UE, UEs that meet certain conditions may be allowed to perform a channel access procedure for SL transmission within the shared COT. Alternatively, depending on the broadcast type of SL transmission transmitted by a UE other than the COT-initiating UE, UEs that meet certain conditions may be allowed to perform a channel access procedure for SL transmission within the shared COT. In order to support the above operations, the embodiments proposed in the present invention (e.g., embodiments 1 and / or 2), variations of the proposed embodiments, extensions of the proposed embodiments, and / or combinations of the proposed embodiments may be applied.

[0209] The operation of the method according to the exemplary embodiment of the present invention can be implemented as a computer-readable program or code in a computer-readable recording medium. The computer-readable recording medium may include all types of recording devices storing data that can be read by a computer system. In addition, the computer-readable recording medium can store and execute programs or codes, which can be distributed among computer systems connected via a network and read by computers in a distributed manner.

[0210] Computer readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, or flash memory. Program instructions may include not only machine language codes created by a compiler, but also high-level language codes that can be executed by a computer using an interpreter.

[0211] Although some aspects of the present invention have been described in the context of an apparatus, these aspects can be indicated according to the corresponding description of the method, and a block or apparatus can correspond to the steps of the method or the features of the steps. Similarly, the aspects described in the context of the method can be represented as the features of the corresponding blocks or items or corresponding apparatus. Some or all steps of the method can be performed by (or using) a hardware device such as a microprocessor, a programmable computer or an electronic circuit. In some embodiments, one or more of the most important steps of the method can be performed by such an apparatus.

[0212] In some exemplary embodiments, a programmable logic device, such as a field programmable gate array, can be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, the field programmable gate array can be operated with a microprocessor to perform one of the methods described herein. Typically, the methods are preferably performed by specific hardware devices.

[0213] The description of the present invention is merely exemplary in nature, and therefore variations that do not depart from the essence of the present invention are intended to be within the scope of the present invention. Such variations should not be considered to depart from the spirit and scope of the present invention. Therefore, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope defined by the appended claims.

Claims

1. A method of a first user equipment (UE), the method comprising: receiving a first sidelink (SL) transmission from a second UE using a first broadcast type; as well as performing a second SL transmission based on the first broadcast type within a shared channel occupation time (COT), The first SL transmission and the second SL transmission are performed based on the first broadcast type which is the same broadcast type.

2. The method according to claim 1, wherein The first broadcast type is unicast, multicast or broadcast.

3. The method according to claim 1, wherein The second UE is a COT initiating UE that initiates COT, the first SL transmission includes COT sharing information, and the shared COT is configured based on the COT sharing information.

4. The method according to claim 3, wherein: The COT sharing information includes at least one of a source identifier (ID), a destination ID, a channel access priority class (CAPC), a remaining COT duration, frequency domain information of a resource block (RB) set of the COT, an additional ID, or an associated broadcast type.

5. The method according to claim 4, wherein The source ID of the second SL transmission matches the destination ID included in the COT shared information, and the destination ID of the second SL transmission matches the source ID included in the COT shared information.

6. The method according to claim 4, wherein: The source ID and destination ID of the second SL transmission match a pair of additional IDs included in the COT shared information.

7. The method according to claim 1, wherein The first SL transmission includes sidelink control information (SCI), and the SCI includes an information element indicating a first broadcast type.

8. The method according to claim 1, wherein If the first broadcast type is unicast, the reception target of the second SL transmission is the second UE, and if the first broadcast type is multicast, the reception target of the second SL transmission includes the second UE.

9. The method according to claim 1, wherein: A first broadcast type that is the same broadcast type is applied within a shared COT belonging to a COT initiated by the second UE.

10. A first user equipment (UE), comprising: at least one processor, The at least one processor causes the first UE to: receiving a first sidelink (SL) transmission from a second UE using a first broadcast type; and performing a second SL transmission based on the first broadcast type within a shared channel occupation time (COT), The first SL transmission and the second SL transmission are performed based on the first broadcast type which is the same broadcast type. The first UE according to claim 10 , wherein: The first broadcast type is unicast, multicast or broadcast.

12. The first UE according to claim 10, wherein: The second UE is a COT initiating UE that initiates COT, the first SL transmission includes COT sharing information, and the shared COT is configured based on the COT sharing information.

13. The first UE according to claim 12, wherein: The COT sharing information includes at least one of a source identifier (ID), a destination ID, a channel access priority class (CAPC), a remaining COT duration, frequency domain information of a resource block (RB) set of the COT, an additional ID, or an associated broadcast type.

14. The first UE according to claim 13, wherein: The source ID of the second SL transmission matches the destination ID included in the COT shared information, and the destination ID of the second SL transmission matches the source ID included in the COT shared information.

15. The first UE according to claim 13, wherein: The source ID and destination ID of the second SL transmission match a pair of additional IDs included in the COT shared information.

16. The first UE according to claim 10, wherein: The first SL transmission includes sidelink control information (SCI), and the SCI includes an information element indicating a first broadcast type.

17. The first UE according to claim 10, wherein: If the first broadcast type is unicast, the reception target of the second SL transmission is the second UE, and if the first broadcast type is multicast, the reception target of the second SL transmission includes the second UE.

18. The first UE according to claim 10, wherein: A first broadcast type that is the same broadcast type is applied within a shared COT belonging to a COT initiated by the second UE.

Images