[go: up one dir, main page]

WO2023038482A1 - Procédé de transmission et de réception d'informations de coordination entre ue dans un système de communication sans fil, et dispositif associé - Google Patents

Procédé de transmission et de réception d'informations de coordination entre ue dans un système de communication sans fil, et dispositif associé Download PDF

Info

Publication number
WO2023038482A1
WO2023038482A1 PCT/KR2022/013581 KR2022013581W WO2023038482A1 WO 2023038482 A1 WO2023038482 A1 WO 2023038482A1 KR 2022013581 W KR2022013581 W KR 2022013581W WO 2023038482 A1 WO2023038482 A1 WO 2023038482A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal
inter
coordination
supported
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2022/013581
Other languages
English (en)
Korean (ko)
Inventor
황대성
이승민
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2023038482A1 publication Critical patent/WO2023038482A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present specification relates to a method and apparatus for transmitting/receiving coordination information between terminals in a wireless communication system.
  • a wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (eg, bandwidth, transmission power, etc.).
  • multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency (SC-FDMA) system.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency
  • MC-FDMA division multiple access
  • MC-FDMA multi carrier frequency division multiple access
  • SL refers to a communication method in which a direct link is established between user equipments (UEs) and voice or data is directly exchanged between the terminals without going through a base station (BS).
  • UEs user equipments
  • BS base station
  • the SL is being considered as a method for solving the burden of the base station due to rapidly increasing data traffic.
  • V2X vehicle-to-everything refers to a communication technology that exchanges information with other vehicles, pedestrians, infrastructure-built objects, etc. through wired/wireless communication.
  • V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian).
  • V2X communication may be provided through a PC5 interface and/or a Uu interface.
  • next-generation radio access technology taking into account the above may be referred to as new radio access technology (RAT) or new radio (NR).
  • RAT new radio access technology
  • NR new radio
  • V2X vehicle-to-everything
  • UE-A may provide UE-B with a set of resources that can be used in a resource (re)selection procedure of UE-B.
  • UE-A may provide UE-B with resource collision-related information about a resource indicated by UE-B's sidelink control information (SCI).
  • SCI sidelink control information
  • UE-B may avoid resource collision by reselecting some of the resources indicated by the SCI of UE-B.
  • the resource set usable for the resource (re)selection procedure of the UE-B may include preferred resources and/or non-preferred resources.
  • UE-A may determine a preferred resource or a non-preferred resource using its own sensing result.
  • information indicating a collision of resources reserved by the UE-B may be transmitted to the UE-B.
  • the coordination information between terminals may include information related to any one of collisions between preferred resources, non-preferred resources, and reserved resources.
  • the type of inter-device coordination information supported may be different according to the capability of each terminal.
  • UE-to-UE coordination information without considering the performance of the receiving terminal (UE-B)
  • UE-to-UE coordination information that is not supported/unavailable/cannot be received by the corresponding UE may be transmitted.
  • reliability improvement of sidelink communication through inter-device coordination cannot be expected, and only signaling overhead increases.
  • the following problems may occur.
  • the transmitting terminal UE-A
  • inaccurate inter-device coordination information may be delivered or inter-device coordination information itself may not be delivered. That is, the UE-B adjustment information according to the performance of the UE-B affects the operation of the UE-B expected to be received, and rather, the sidelink communication performance may be deteriorated.
  • An object of this specification is to propose a method for solving the above problems.
  • a method for a first terminal to transmit inter-UE coordination information in a wireless communication system is related to sidelink communication supported by the second terminal from a second terminal.
  • the method includes receiving first capability information and transmitting the inter-device coordination information to the second terminal based on the first capability information.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • inter-device coordination information Based on the type of inter-device coordination information supported by the second terminal, i) information related to scheme 1 (scheme 1) for coordination between terminals or ii) information related to scheme 2 (scheme 2) for coordination between terminals It is characterized in that the inter-device coordination information including information is transmitted.
  • Information related to scheme 1 for inter-device coordination may include information indicating preferred resources related to transmission of the second terminal or information indicating non-preferred resources related to transmission of the second terminal.
  • Information related to scheme 2 for coordination between terminals may include information indicating a collision of resources reserved by the second terminal.
  • the method may further include transmitting second capability information related to sidelink communication supported by the first terminal to the second terminal.
  • the inter-device coordination information may be transmitted based on the first performance information and the second performance information.
  • the second capability information may include second information indicating whether transmission of the inter-device coordination information is supported by the first terminal.
  • a type of inter-device coordination information supported by the first terminal may be determined based on the second information.
  • the inter-device coordination information may be transmitted.
  • the first information may be determined based on sensing capability of the second terminal.
  • the sensing performance of the second terminal may be related to a sensing operation for a resource selection window.
  • the sensing performance of the second terminal is i) no sensing operation for the resource selection window, ii) full sensing support for the resource selection window, iii) PARTIAL SENSING support for the resource selection window, or iv) the resource selection window It can be based on any one of FULL SENSING and PARTIAL SENSING support for.
  • a first terminal transmitting inter-UE coordination information includes one or more transceivers, one or more processors controlling the one or more transceivers, and the one or more processors. and one or more memories operably connected to the
  • the one or more memories store instructions for performing operations, based on being executed by the one or more processors.
  • the operations include receiving, from a second terminal, first capability information related to sidelink communication supported by the second terminal, and in the second terminal, based on the first capability information, and transmitting coordination information between terminals.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • inter-device coordination information Based on the type of inter-device coordination information supported by the second terminal, i) information related to scheme 1 (scheme 1) for coordination between terminals or ii) information related to scheme 2 (scheme 2) for coordination between terminals It is characterized in that the inter-device coordination information including information is transmitted.
  • An apparatus for controlling a first terminal to transmit inter-UE coordination information in a wireless communication system includes one or more processors and operably connected to the one or more processors. Contains one or more memories.
  • the one or more memories store instructions for performing operations, based on being executed by the one or more processors.
  • the operations include receiving, from a second terminal, first capability information related to sidelink communication supported by the second terminal, and in the second terminal, based on the first capability information, and transmitting coordination information between terminals.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • inter-device coordination information Based on the type of inter-device coordination information supported by the second terminal, i) information related to scheme 1 (scheme 1) for coordination between terminals or ii) information related to scheme 2 (scheme 2) for coordination between terminals It is characterized in that the inter-device coordination information including information is transmitted.
  • One or more non-transitory computer readable media stores one or more instructions.
  • the one or more instructions upon being executed by the one or more processors, perform operations.
  • the operations include receiving, from a second terminal, first capability information related to sidelink communication supported by the second terminal, and in the second terminal, based on the first capability information, and transmitting coordination information between terminals.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • inter-device coordination information Based on the type of inter-device coordination information supported by the second terminal, i) information related to scheme 1 (scheme 1) for coordination between terminals or ii) information related to scheme 2 (scheme 2) for coordination between terminals It is characterized in that the inter-device coordination information including information is transmitted.
  • a method for receiving inter-UE coordination information by a second terminal in a wireless communication system includes, in a first terminal, sidelink communication supported by the second terminal and Transmitting related first capability information and receiving, from the first terminal, the inter-device coordination information based on the first capability information.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • the second terminal for receiving inter-UE coordination information includes one or more transceivers
  • processors for controlling the one or more transceivers and one or more memories operatively connected to the one or more processors.
  • the one or more memories store instructions for performing operations, based on being executed by the one or more processors.
  • the operations include transmitting, to a first terminal, first capability information related to sidelink communication supported by the second terminal and, from the first terminal, the terminal based on the first capability information. and receiving liver coordination information.
  • the first capability information includes first information indicating whether reception of the inter-device coordination information is supported by the second terminal. Based on the first information, a type of inter-device coordination information supported by the second terminal is determined.
  • inter-device coordination information is transmitted based on first capability information of a second terminal (eg, UE-B).
  • the type of inter-device coordination information supported by the second terminal may be determined based on the first information included in the first capability information. Accordingly, inter-device coordination information that is most suitable for the performance of the receiving terminal can be delivered while minimizing signaling overhead.
  • inter-device coordination information may be transmitted based on the first capability information and the second capability information of the first UE (eg, UE-A).
  • a type of inter-device coordination information supported by the first terminal may be determined based on the second information included in the second capability information.
  • Signaling of coordination information between terminals is performed only within a range in which the performance of the transmitting/receiving terminal is permitted. Accordingly, signaling overhead due to transmission of coordination information between terminals can be additionally reduced, and communication performance degradation due to inaccurate utilization of coordination information between terminals can be prevented.
  • FIG. 1 shows the structure of an NR system according to an embodiment of the present specification.
  • FIG. 2 shows the structure of a radio frame of NR according to an embodiment of the present specification.
  • FIG 3 shows a slot structure of an NR frame according to an embodiment of the present specification.
  • FIG. 4 shows a terminal performing V2X or SL communication according to an embodiment of the present specification.
  • FIG. 5 shows a resource unit for V2X or SL communication according to an embodiment of the present specification.
  • FIG. 6 illustrates a procedure for a terminal to perform V2X or SL communication according to a transmission mode according to an embodiment of the present specification.
  • FIG. 8 shows a plurality of BWPs according to an embodiment of the present specification.
  • FIG. 10 shows a resource unit for CBR measurement according to an embodiment of the present specification.
  • 11 is a diagram illustrating a resource pool related to CBR measurement.
  • FIG. 12 illustrates a procedure for UE-A to transmit auxiliary information to UE-B according to an embodiment of the present specification.
  • FIG. 13 is a flowchart for explaining a method for a first terminal to transmit inter-UE coordination information in a wireless communication system according to an embodiment of the present specification.
  • FIG. 14 is a flowchart illustrating a method for a second terminal to receive inter-UE coordination information in a wireless communication system according to another embodiment of the present specification.
  • 15 shows a communication system 1, according to an embodiment of the present specification.
  • FIG. 16 illustrates a wireless device according to an embodiment of the present specification.
  • FIG. 17 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present specification.
  • FIG. 19 illustrates a portable device according to an embodiment of the present specification.
  • FIG. 20 illustrates a vehicle or autonomous vehicle according to an embodiment of the present specification.
  • a or B may mean “only A”, “only B”, or “both A and B”.
  • a or B (A or B)" in the present specification may be interpreted as “A and/or B (A and/or B)”.
  • A, B or C as used herein means “only A”, “only B”, “only C”, or “any and all combinations of A, B and C ( any combination of A, B and C)”.
  • a slash (/) or a comma (comma) used in this specification may mean “and/or”.
  • A/B can mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”.
  • A, B, C may mean “A, B or C”.
  • At least one of A and B may mean “only A”, “only B”, or “both A and B”. Also, in this specification, the expression “at least one of A or B” or “at least one of A and/or B” means “at least one It can be interpreted the same as "A and B (at least one of A and B) of
  • At least one of A, B and C means “only A”, “only B”, “only C", or “A, B and C” It may mean “any combination of A, B and C”. Also, “at least one of A, B or C” or “at least one of A, B and/or C” means It can mean “at least one of A, B and C”.
  • control information may be suggested as an example of “control information”.
  • control information in this specification is not limited to “PDCCH”, and “PDCCH” may be suggested as an example of “control information”.
  • PDCCH control information
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented with a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be implemented with a wireless technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like.
  • IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with a system based on IEEE 802.16e.
  • UTRA is part of the universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) that uses evolved-UMTS terrestrial radio access (E-UTRA), adopting OFDMA in downlink and SC in uplink -Adopt FDMA.
  • LTE-A (advanced) is an evolution of 3GPP LTE.
  • 5G NR a successor to LTE-A, is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability.
  • 5G NR can utilize all available spectrum resources, including low-frequency bands below 1 GHz, medium-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.
  • LTE-A or 5G NR is mainly described, but the technical idea according to an embodiment of the present specification is not limited thereto.
  • FIG. 1 shows the structure of an NR system according to an embodiment of the present specification.
  • a Next Generation-Radio Access Network may include a next generation-Node B (gNB) and/or an eNB that provides user plane and control plane protocol termination to a UE.
  • gNB next generation-Node B
  • eNB that provides user plane and control plane protocol termination to a UE.
  • . 1 illustrates a case including only gNB.
  • gNB and eNB are connected to each other through an Xn interface.
  • the gNB and the eNB are connected to a 5G Core Network (5GC) through an NG interface.
  • 5GC 5G Core Network
  • AMF access and mobility management function
  • UPF user plane function
  • FIG. 2 shows the structure of a radio frame of NR according to an embodiment of the present specification.
  • radio frames can be used in uplink and downlink transmission in NR.
  • a radio frame has a length of 10 ms and may be defined as two 5 ms half-frames (Half-Frame, HF).
  • a half-frame may include five 1ms subframes (Subframes, SFs).
  • a subframe may be divided into one or more slots, and the number of slots in a subframe may be determined according to a subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).
  • CP cyclic prefix
  • each slot may include 14 symbols.
  • each slot may include 12 symbols.
  • the symbol may include an OFDM symbol (or CP-OFDM symbol), a Single Carrier-FDMA (SC-FDMA) symbol (or a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).
  • OFDM symbol or CP-OFDM symbol
  • SC-FDMA Single Carrier-FDMA
  • DFT-s-OFDM Discrete Fourier Transform-spread-OFDM
  • Table 1 below shows the number of symbols per slot (N slot symb ), the number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe, u slot ) is exemplified.
  • Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when the extended CP is used.
  • OFDM A numerology
  • SCS SCS
  • CP length CP length
  • TU Time Unit
  • multiple numerologies or SCSs to support various 5G services can be supported. For example, when the SCS is 15 kHz, wide area in traditional cellular bands can be supported, and when the SCS is 30 kHz/60 kHz, dense-urban, lower latency latency and wider carrier bandwidth may be supported. When the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.
  • An NR frequency band may be defined as two types of frequency ranges.
  • the two types of frequency ranges may be FR1 and FR2.
  • the number of frequency ranges may be changed, and for example, the two types of frequency ranges may be shown in Table 3 below.
  • FR1 may mean "sub 6 GHz range”
  • FR2 may mean “above 6 GHz range” and may be called millimeter wave (mmW).
  • mmW millimeter wave
  • FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, and may be used, for example, for vehicle communication (eg, autonomous driving).
  • FIG 3 shows a slot structure of an NR frame according to an embodiment of the present specification.
  • a slot includes a plurality of symbols in the time domain. For example, in the case of a normal CP, one slot includes 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot includes 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.
  • a carrier includes a plurality of subcarriers in the frequency domain.
  • a resource block (RB) may be defined as a plurality of (eg, 12) consecutive subcarriers in the frequency domain.
  • a bandwidth part (BWP) may be defined as a plurality of consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and may correspond to one numerology (eg, SCS, CP length, etc.) there is.
  • a carrier may include up to N (eg, 5) BWPs. Data communication may be performed through an activated BWP.
  • Each element may be referred to as a resource element (RE) in the resource grid, and one complex symbol may be mapped.
  • RE resource element
  • a radio interface between a terminal and a terminal or a radio interface between a terminal and a network may be composed of an L1 layer, an L2 layer, and an L3 layer.
  • the L1 layer may mean a physical layer.
  • the L2 layer may mean at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer.
  • the L3 layer may mean an RRC layer.
  • SL synchronization signal (Sidelink Synchronization Signal, SLSS) and synchronization information
  • the SLSS is a SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS).
  • PSSS may be referred to as a sidelink primary synchronization signal (S-PSS)
  • S-SSS sidelink secondary synchronization signal
  • S-SSS sidelink secondary synchronization signal
  • length-127 M-sequences can be used for S-PSS
  • length-127 Gold-sequences can be used for S-SSS.
  • the UE can detect an initial signal using S-PSS and acquire synchronization.
  • the terminal may obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.
  • PSBCH Physical Sidelink Broadcast Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the basic information includes information related to SLSS, duplex mode (DM), TDD UL/Time Division Duplex Uplink/Downlink (TDD UL/DL) configuration, resource pool related information, type of application related to SLSS, It may be a subframe offset, broadcast information, and the like.
  • the payload size of PSBCH may be 56 bits including a 24-bit CRC.
  • S-PSS, S-SSS, and PSBCH may be included in a block format (eg, SL SS (Synchronization Signal) / PSBCH block, hereinafter, S-SSB (Sidelink-Synchronization Signal Block)) supporting periodic transmission.
  • the S-SSB may have the same numerology (ie, SCS and CP length) as a Physical Sidelink Control Channel (PSCCH)/Physical Sidelink Shared Channel (PSSCH) in a carrier, and the transmission bandwidth may be a (pre)set SL Sidelink BWP (Sidelink Channel). BWP).
  • the bandwidth of the S-SSB may be 11 Resource Blocks (RBs).
  • PSBCH may span 11 RBs.
  • the frequency position of the S-SSB may be set (in advance). Therefore, the UE does not need to perform hypothesis detection in frequency to discover the S-SSB in the carrier.
  • the transmitting terminal may transmit one or more S-SSBs to the receiving terminal within one S-SSB transmission period according to the SCS.
  • the number of S-SSBs that the transmitting terminal transmits to the receiving terminal within one S-SSB transmission period may be pre-configured or configured for the transmitting terminal.
  • the S-SSB transmission period may be 160 ms.
  • an S-SSB transmission period of 160 ms may be supported.
  • FIG. 4 shows a terminal performing V2X or SL communication according to an embodiment of the present specification.
  • terminal in V2X or SL communication may mainly mean a user's terminal.
  • the base station may also be regarded as a kind of terminal.
  • terminal 1 may be the first device 100 and terminal 2 may be the second device 200 .
  • terminal 1 may select a resource unit corresponding to a specific resource in a resource pool representing a set of a series of resources. And, terminal 1 can transmit an SL signal using the resource unit.
  • terminal 2 which is a receiving terminal, can receive a resource pool through which terminal 1 can transmit a signal, and can detect a signal of terminal 1 within the resource pool.
  • the base station may inform the terminal 1 of the resource pool.
  • another terminal may inform terminal 1 of a resource pool, or terminal 1 may use a previously set resource pool.
  • a resource pool may be composed of a plurality of resource units, and each terminal may select one or a plurality of resource units to use for its own SL signal transmission.
  • FIG. 5 shows a resource unit for V2X or SL communication according to an embodiment of the present specification.
  • all frequency resources of the resource pool may be divided into N F number, and all time resources of the resource pool may be divided into N T number. Accordingly, a total of N F * N T resource units may be defined within the resource pool. 5 shows an example of a case in which a corresponding resource pool is repeated with a period of N T subframes.
  • one resource unit (eg, Unit #0) may appear periodically and repeatedly.
  • an index of a physical resource unit to which one logical resource unit is mapped may change according to a predetermined pattern over time.
  • a resource pool may mean a set of resource units that can be used for transmission by a terminal desiring to transmit an SL signal.
  • Resource pools can be subdivided into several types. For example, according to the content of the SL signal transmitted in each resource pool, the resource pool may be classified as follows.
  • SA Scheduling Assignment
  • MCS Modulation and Coding Scheme
  • MIMO Multiple Input Multiple Output
  • SA can also be multiplexed and transmitted together with SL data on the same resource unit.
  • the SA resource pool may mean a resource pool in which SA is multiplexed with SL data and transmitted.
  • SA may also be referred to as an SL control channel.
  • SL data channel Physical Sidelink Shared Channel, PSSCH
  • PSSCH Physical Sidelink Shared Channel
  • SL data channel may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted together with SL data on the same resource unit, only the SL data channel in a form excluding SA information can be transmitted in the resource pool for the SL data channel.
  • Resource Elements (REs) used to transmit SA information on individual resource units in the SA resource pool may still be used to transmit SL data in the resource pool of the SL data channel.
  • the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.
  • a discovery channel may be a resource pool for a transmitting terminal to transmit information such as its own ID. Through this, the transmitting terminal can allow neighboring terminals to discover themselves.
  • resource pools may be used according to transmission/reception properties of the SL signals. For example, even for the same SL data channel or discovery message, a method for determining the transmission timing of the SL signal (eg, whether it is transmitted at the reception time of the synchronization reference signal or transmitted by applying a certain timing advance at the reception time), resource Allocation method (eg, whether the base station assigns individual signal transmission resources to individual transmission terminals or whether individual transmission terminals select individual signal transmission resources within the resource pool), signal format (eg, each SL Depending on the number of symbols occupied by a signal in one subframe or the number of subframes used for transmission of one SL signal), signal strength from a base station, transmit power strength of an SL terminal, etc., resource pools may be divided into different resource pools.
  • resource Allocation method eg, whether the base station assigns individual signal transmission resources to individual transmission terminals or whether individual transmission terminals select individual signal transmission resources within the resource pool
  • signal format eg, each SL Depending on the number of symbols occupied by a
  • FIG. 6 illustrates a procedure for a terminal to perform V2X or SL communication according to a transmission mode according to an embodiment of the present specification.
  • the transmission mode may be referred to as a mode or a resource allocation mode.
  • a transmission mode in LTE may be referred to as an LTE transmission mode
  • a transmission mode in NR may be referred to as an NR resource allocation mode.
  • (a) of FIG. 6 shows a terminal operation related to LTE transmission mode 1 or LTE transmission mode 3.
  • (a) of FIG. 6 shows UE operation related to NR resource allocation mode 1.
  • LTE transmission mode 1 may be applied to general SL communication
  • LTE transmission mode 3 may be applied to V2X communication.
  • (b) of FIG. 6 shows a terminal operation related to LTE transmission mode 2 or LTE transmission mode 4.
  • (b) of FIG. 6 shows UE operation related to NR resource allocation mode 2.
  • the base station may schedule SL resources to be used by the terminal for SL transmission.
  • the base station may transmit information related to SL resources and/or information related to UL resources to the first terminal.
  • the UL resource may include a PUCCH resource and/or a PUSCH resource.
  • the UL resource may be a resource for reporting SL HARQ feedback to the base station.
  • the first terminal may receive information related to dynamic grant (DG) resources and/or information related to configured grant (CG) resources from the base station.
  • CG resources may include CG type 1 resources or CG type 2 resources.
  • the DG resource may be a resource set/allocated by the base station to the first terminal through downlink control information (DCI).
  • the CG resource may be a (periodic) resource configured/allocated by the base station to the first terminal through a DCI and/or RRC message.
  • the base station may transmit an RRC message including information related to the CG resource to the first terminal.
  • the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station transmits a DCI related to activation or release of the CG resource. It can be transmitted to the first terminal.
  • the first terminal may transmit a PSCCH (eg, Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling.
  • a PSCCH eg, Sidelink Control Information (SCI) or 1st-stage SCI
  • the first terminal may transmit a PSSCH (eg, 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • HARQ feedback information eg, NACK information or ACK information
  • the first terminal may transmit/report HARQ feedback information to the base station through PUCCH or PUSCH.
  • the HARQ feedback information reported to the base station may be information that the first terminal generates based on the HARQ feedback information received from the second terminal.
  • the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance.
  • the DCI may be a DCI for SL scheduling.
  • the format of the DCI may be DCI format 3_0 or DCI format 3_1. Table 5 below shows an example of DCI for SL scheduling.
  • the terminal can determine an SL transmission resource within an SL resource set by the base station / network or a preset SL resource there is.
  • the configured SL resource or the preset SL resource may be a resource pool.
  • the terminal may autonomously select or schedule resources for SL transmission.
  • the terminal may perform SL communication by selecting a resource by itself within a configured resource pool.
  • the terminal may select a resource by itself within a selection window by performing a sensing and resource (re)selection procedure.
  • the sensing may be performed in units of subchannels.
  • a first terminal that selects a resource within a resource pool by itself can transmit a PSCCH (eg, Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal using the resource.
  • a PSCCH eg, Sidelink Control Information (SCI) or 1st-stage SCI
  • the first terminal may transmit a PSSCH (eg, 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • UE 1 may transmit SCI to UE 2 on PSCCH.
  • UE 1 may transmit two consecutive SCI (eg, 2-stage SCI) to UE 2 on PSCCH and/or PSSCH.
  • UE 2 may decode two consecutive SCIs (eg, 2-stage SCI) in order to receive the PSSCH from UE 1.
  • SCI transmitted on PSCCH may be referred to as a 1st SCI, 1st SCI, 1st-stage SCI or 1st-stage SCI format
  • SCI transmitted on PSSCH is 2nd SCI, 2nd SCI, 2nd-stage SCI or It may be referred to as a 2nd-stage SCI format
  • the 1st-stage SCI format may include SCI format 1-A
  • the 2nd-stage SCI format may include SCI format 2-A and/or SCI format 2-B.
  • Table 6 below shows an example of a 1st-stage SCI format.
  • Table 7 below shows an example of a 2 nd -stage SCI format.
  • the first terminal may receive the PSFCH based on Table 8.
  • UE 1 and UE 2 may determine PSFCH resources based on Table 8, and UE 2 may transmit HARQ feedback to UE 1 using the PSFCH resource.
  • the first terminal may transmit SL HARQ feedback to the base station through PUCCH and / or PUSCH based on Table 9.
  • SCI Sidelink Control Information
  • Control information transmitted from the base station to the terminal through the PDCCH is referred to as downlink control information (DCI), whereas control information transmitted from the terminal to other terminals through the PSCCH may be referred to as SCI.
  • DCI downlink control information
  • SCI control information transmitted from the terminal to other terminals through the PSCCH
  • the UE may know the start symbol of the PSCCH and/or the number of symbols of the PSCCH before decoding the PSCCH.
  • SCI may include SL scheduling information.
  • a UE may transmit at least one SCI to another UE in order to schedule a PSSCH.
  • one or more SCI formats may be defined.
  • the transmitting terminal may transmit SCI to the receiving terminal on the PSCCH.
  • the receiving terminal may decode one SCI in order to receive the PSSCH from the transmitting terminal.
  • the transmitting terminal may transmit two consecutive SCI (eg, 2-stage SCI) to the receiving terminal on the PSCCH and/or the PSSCH.
  • the receiving terminal may decode two consecutive SCI (eg, 2-stage SCI) in order to receive the PSSCH from the transmitting terminal.
  • the SCI composition fields are divided into two groups in consideration of the (relatively) high SCI payload size
  • the SCI including the first SCI composition field group is classified as the first SCI or the first SCI.
  • an SCI including the second SCI configuration field group may be referred to as a second SCI or a 2 nd SCI.
  • the transmitting terminal may transmit the first SCI to the receiving terminal through the PSCCH.
  • the transmitting terminal may transmit the second SCI to the receiving terminal on PSCCH and/or PSSCH.
  • the second SCI may be transmitted to the receiving terminal through an (independent) PSCCH or may be piggybacked and transmitted along with data through the PSSCH.
  • two consecutive SCIs may be applied for different transmissions (eg, unicast, broadcast, or groupcast).
  • the PSCCH may include the SCI, the first SCI, and/or the second SCI. It can be replaced / substituted with at least one of the 2 SCI. And/or, for example, the SCI may be replaced/substituted with at least one of the PSCCH, the first SCI, and/or the second SCI. And/or, for example, since the transmitting terminal may transmit the second SCI to the receiving terminal through the PSSCH, the PSSCH may be replaced/substituted with the second SCI.
  • FIG. 7 shows three cast types according to an embodiment of the present specification.
  • FIG. 7(a) shows broadcast type SL communication
  • FIG. 7(b) shows unicast type SL communication
  • FIG. 7(c) shows groupcast type SL communication.
  • a terminal may perform one-to-one communication with another terminal.
  • SL communication of the group cast type a terminal may perform SL communication with one or more terminals in a group to which it belongs.
  • SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, and the like.
  • the transmitting terminal may need to establish a (PC5) RRC connection with the receiving terminal.
  • the terminal may obtain a V2X-specific SIB (V2X-specific SIB).
  • V2X-specific SIB V2X-specific SIB
  • the terminal may establish an RRC connection with another terminal. For example, when an RRC connection is established between a transmitting terminal and a receiving terminal, the transmitting terminal may perform unicast communication with the receiving terminal through the established RRC connection.
  • the transmitting terminal may transmit an RRC message to the receiving terminal.
  • the receiving terminal may perform antenna/resource demapping, demodulation, and decoding on the received information.
  • Corresponding information may be delivered to the RRC layer via the MAC layer, the RLC layer and the PDCP layer. Accordingly, the receiving terminal can receive the RRC message generated by the transmitting terminal.
  • V2X or SL communication may be supported for a terminal in RRC_CONNECTED mode, a terminal in RRC_IDLE mode, and a terminal in (NR) RRC_INACTIVE mode. That is, a terminal in RRC_CONNECTED mode, a terminal in RRC_IDLE mode, and a terminal in (NR) RRC_INACTIVE mode may perform V2X or SL communication.
  • a terminal in RRC_INACTIVE mode or a terminal in RRC_IDLE mode can perform V2X or SL communication by using a cell-specific configuration included in a SIB specific to V2X.
  • RRC can be used to exchange at least UE capabilities and AS layer settings.
  • a first terminal may transmit UE capabilities and AS layer settings of the first terminal to a second terminal, and the first terminal may receive the UE capabilities and AS layer settings of the second terminal from the second terminal.
  • the information flow can be triggered during or after PC5-S signaling for direct link setup.
  • SL measurement and reporting may be considered in SL.
  • a receiving terminal may receive a reference signal from a transmitting terminal, and the receiving terminal may measure a channel state of the transmitting terminal based on the reference signal. And, the receiving terminal may report channel state information (CSI) to the transmitting terminal.
  • CSI channel state information
  • SL-related measurement and reporting may include measurement and reporting of CBR and reporting of location information.
  • CSI Channel Status Information
  • CQI Channel Quality Indicator
  • PMI Precoding Matrix Index
  • RI Rank Indicator
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • Path Gain pathgain/pathloss
  • SRI Sounding Reference Symbols
  • Resource Indicator Resource Indicator
  • CRI CSI-RS Resource Indicator
  • interference condition vehicle motion, and the like.
  • CQI, RI and PMI or some of them may be supported in a non-subband-based aperiodic CSI report assuming four or fewer antenna ports. there is.
  • the CSI procedure may not depend on a standalone reference signal (standalone RS).
  • CSI reporting can be activated and deactivated according to settings.
  • a transmitting terminal may transmit a CSI-RS to a receiving terminal, and the receiving terminal may measure CQI or RI using the CSI-RS.
  • the CSI-RS may be referred to as an SL CSI-RS.
  • the CSI-RS may be confined within PSSCH transmission.
  • the transmitting terminal may transmit the CSI-RS to the receiving terminal by including the CSI-RS on the PSSCH resource.
  • HARQ hybrid automatic repeat request
  • An error compensation scheme for securing communication reliability may include a Forward Error Correction (FEC) scheme and an Automatic Repeat Request (ARQ) scheme.
  • FEC Forward Error Correction
  • ARQ Automatic Repeat Request
  • an error in a receiving end can be corrected by adding an extra error correction code to information bits.
  • the FEC method has an advantage of having a small time delay and not requiring separate exchange of information between a transmitter and a receiver, but has a disadvantage of low system efficiency in a good channel environment.
  • the ARQ method can increase transmission reliability, but has a disadvantage in that time delay occurs and system efficiency decreases in a poor channel environment.
  • HARQ Hybrid Automatic Repeat Request
  • Performance can be improved by checking whether the data received by the physical layer contains an error that cannot be decoded, and requesting retransmission if an error occurs.
  • HARQ feedback and HARQ combining in the physical layer may be supported.
  • the receiving terminal when the receiving terminal operates in resource allocation mode 1 or 2, the receiving terminal may receive a PSSCH from the transmitting terminal, and the receiving terminal may receive sidelink feedback control information (SFCI) through a physical sidelink feedback channel (PSFCH).
  • SFCI sidelink feedback control information
  • PSFCH physical sidelink feedback channel
  • SL HARQ feedback can be enabled for unicast.
  • non-Code Block Group (non-CBG) operation if the receiving terminal decodes a PSCCH targeting the receiving terminal, and the receiving terminal successfully decodes a transport block related to the PSCCH, the receiving terminal HARQ-ACK can be generated. And, the receiving terminal may transmit HARQ-ACK to the transmitting terminal.
  • the receiving terminal may generate HARQ-NACK. And, the receiving terminal may transmit HARQ-NACK to the transmitting terminal.
  • SL HARQ feedback may be enabled for groupcast.
  • two HARQ feedback options can be supported for groupcast.
  • Groupcast Option 1 If the receiving terminal fails to decode a transport block related to the PSCCH after the receiving terminal decodes the PSCCH targeting the receiving terminal, the receiving terminal transmits HARQ-NACK through the PSFCH. It can be transmitted to the transmitting terminal. On the other hand, if the receiving terminal decodes a PSCCH targeting the receiving terminal and the receiving terminal successfully decodes a transport block related to the PSCCH, the receiving terminal may not transmit HARQ-ACK to the transmitting terminal.
  • Groupcast option 2 If the receiving terminal fails to decode a transport block related to the PSCCH after the receiving terminal decodes the PSCCH targeting the receiving terminal, the receiving terminal transmits HARQ-NACK through the PSFCH. It can be transmitted to the transmitting terminal. And, when the receiving terminal decodes the PSCCH targeting the receiving terminal and the receiving terminal successfully decodes the transport block related to the PSCCH, the receiving terminal may transmit HARQ-ACK to the transmitting terminal through the PSFCH.
  • all terminals performing groupcast communication may share PSFCH resources.
  • UEs belonging to the same group may transmit HARQ feedback using the same PSFCH resource.
  • each terminal performing groupcast communication may use different PSFCH resources for HARQ feedback transmission.
  • UEs belonging to the same group may transmit HARQ feedback using different PSFCH resources.
  • HARQ-ACK may be referred to as ACK, ACK information, or positive-ACK information
  • HARQ-NACK may be referred to as NACK, NACK information, or negative-ACK information.
  • bandwidth part BWP
  • resource pool a bandwidth part (BWP) and a resource pool
  • the reception bandwidth and transmission bandwidth of the terminal do not need to be as large as the cell bandwidth, and the reception bandwidth and transmission bandwidth of the terminal can be adjusted.
  • the network/base station may notify the terminal of bandwidth adjustment.
  • the terminal may receive information/configuration for bandwidth adjustment from the network/base station.
  • the terminal may perform bandwidth adjustment based on the received information/configuration.
  • the bandwidth adjustment may include reducing/expanding the bandwidth, changing the location of the bandwidth, or changing the subcarrier spacing of the bandwidth.
  • bandwidth may be reduced during periods of low activity to save power.
  • the location of the bandwidth may move in the frequency domain.
  • the location of the bandwidth can be moved in the frequency domain to increase scheduling flexibility.
  • subcarrier spacing of the bandwidth may be changed.
  • the subcarrier spacing of the bandwidth can be changed to allow for different services.
  • a subset of the total cell bandwidth of a cell may be referred to as a Bandwidth Part (BWP).
  • BA may be performed by the base station/network setting a BWP to the terminal and notifying the terminal of the currently active BWP among the set BWPs of the base station/network.
  • the BWP may be at least one of an active BWP, an initial BWP, and/or a default BWP.
  • the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell).
  • the UE may not receive PDCCH, PDSCH or CSI-RS (except for RRM) outside of active DL BWP.
  • the UE may not trigger Channel State Information (CSI) reporting for inactive DL BWP.
  • the UE may not transmit a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH) outside of an active UL BWP.
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • the initial BWP may be given as a set of consecutive RBs for remaining minimum system information (RMSI) control resource set (CORESET) (set by PBCH).
  • RMSI remaining minimum system information
  • CORESET control resource set
  • the initial BWP may be given by a system information block (SIB) for a random access procedure.
  • SIB system information block
  • a default BWP may be set by higher layers.
  • the initial value of the default BWP may be an initial DL BWP.
  • DCI downlink control information
  • BWP may be defined for SL.
  • the same SL BWP can be used for transmit and receive.
  • a transmitting terminal can transmit an SL channel or SL signal on a specific BWP
  • a receiving terminal can receive an SL channel or SL signal on the specific BWP.
  • SL BWP may be defined separately from Uu BWP, and SL BWP may have separate configuration signaling from Uu BWP.
  • the terminal may receive configuration for SL BWP from the base station/network.
  • SL BWP may be set (in advance) for an out-of-coverage NR V2X terminal and an RRC_IDLE terminal within a carrier. For a UE in RRC_CONNECTED mode, at least one SL BWP may be activated within a carrier.
  • FIG. 8 shows a plurality of BWPs according to an embodiment of the present specification.
  • BWP1 having a bandwidth of 40 MHz and subcarrier spacing of 15 kHz
  • BWP2 having a bandwidth of 10 MHz and subcarrier spacing of 15 kHz
  • BWP3 having a bandwidth of 20 MHz and subcarrier spacing of 60 kHz
  • FIG. 9 shows BWP according to an embodiment of the present specification. In the embodiment of FIG. 9 , it is assumed that there are three BWPs.
  • a common resource block may be a carrier resource block numbered from one end of a carrier band to the other end.
  • a PRB may be a numbered resource block within each BWP.
  • Point A may indicate a common reference point for the resource block grid.
  • BWP may be set by point A, an offset from point A (N start BWP ), and a bandwidth (N size BWP ).
  • point A may be the external reference point of the carrier's PRB to which subcarrier 0 of all numerologies (eg, all numerologies supported by the network on that carrier) are aligned.
  • the offset may be the PRB interval between point A and the lowest subcarrier in a given numerology.
  • the bandwidth may be the number of PRBs in a given numerology.
  • BWP may be defined for SL.
  • the same SL BWP can be used for transmit and receive.
  • a transmitting terminal can transmit an SL channel or SL signal on a specific BWP
  • a receiving terminal can receive an SL channel or SL signal on the specific BWP.
  • SL BWP may be defined separately from Uu BWP, and SL BWP may have separate configuration signaling from Uu BWP.
  • the terminal may receive configuration for SL BWP from the base station/network.
  • SL BWP may be set (in advance) for out-of-coverage NR V2X terminals and RRC_IDLE terminals within the carrier. For a UE in RRC_CONNECTED mode, at least one SL BWP may be activated within a carrier.
  • a resource pool may be a set of time-frequency resources that may be used for SL transmission and/or SL reception. From the point of view of the terminal, the time domain resources in the resource pool may not be contiguous.
  • a plurality of resource pools may be (in advance) configured for a UE within one carrier. From a physical layer point of view, a terminal may perform unicast, groupcast, and broadcast communication using a set or previously set resource pool.
  • SL congestion control sidelink congestion control
  • the terminal determines the SL transmission resource by itself
  • the terminal also determines the size and frequency of the resource used by itself.
  • the terminal needs to observe the channel condition. If it is determined that an excessive amount of resources are being consumed, it is preferable that the terminal take an action of reducing its own resource use. In this specification, this may be defined as congestion control (Congestion Control, CR). For example, the terminal determines whether the energy measured in a unit time/frequency resource is equal to or higher than a certain level, and determines the amount and frequency of its own transmission resources according to the ratio of the unit time/frequency resource in which energy equal to or higher than a certain level is observed. can be adjusted In the present specification, a ratio of time/frequency resources in which energy of a certain level or higher is observed may be defined as a channel busy ratio (CBR). The UE may measure the CBR for each channel/frequency. Additionally, the UE may transmit the measured CBR to the network/base station.
  • CBR channel busy ratio
  • FIG. 10 shows a resource unit for CBR measurement according to an embodiment of the present specification.
  • CBR is a result of a UE measuring a Received Signal Strength Indicator (RSSI) in units of subchannels for a specific period (eg, 100 ms), and a sub-received RSSI measurement result having a value greater than or equal to a preset threshold. It may mean the number of channels. Alternatively, the CBR may mean a ratio of subchannels having a value equal to or greater than a preset threshold among subchannels during a specific period. For example, in the embodiment of FIG.
  • RSSI Received Signal Strength Indicator
  • the CBR may mean a ratio of hatched subchannels during a 100 ms interval. Additionally, the terminal may report the CBR to the base station.
  • 11 is a diagram illustrating a resource pool related to CBR measurement.
  • the UE can perform one CBR measurement for one resource pool.
  • the PSFCH resource may be excluded from the CBR measurement.
  • the terminal may measure channel occupancy ratio (CR). Specifically, the terminal measures the CBR, and the terminal measures the maximum value (CRlimitk) of the channel occupancy ratio (Channel occupancy ratio k, CRk) that traffic corresponding to each priority (eg, k) can occupy according to the CBR. ) can be determined. For example, the terminal may derive the maximum value (CRlimitk) of the channel occupancy for the priority of each traffic based on a predetermined table of CBR measurement values. For example, in the case of traffic having a relatively high priority, the terminal may derive a maximum value of a relatively large channel occupancy.
  • CR channel occupancy ratio
  • the UE may perform congestion control by limiting the sum of channel occupancy rates of traffics whose priority k is lower than i to a predetermined value or less. According to this method, a stronger channel occupancy limit may be applied to traffic having a relatively lower priority.
  • the terminal may perform SL congestion control using methods such as transmission power size adjustment, packet drop, retransmission decision, and transmission RB size adjustment (MCS adjustment).
  • MCS adjustment transmission RB size adjustment
  • Table 10 shows an example of SL CBR and SL RSSI.
  • the slot index may be based on a physical slot index.
  • Table 11 shows an example of SL CR (Channel Occupancy Ratio).
  • the wording "configuration or definition” may be interpreted as being (pre)configured (via predefined signaling (eg, SIB, MAC signaling, RRC signaling)) from a base station or network.
  • predefined signaling eg, SIB, MAC signaling, RRC signaling
  • “A may be configured” may include "(pre)setting/defining or notifying A of the base station or network for the terminal”.
  • the wording “set or define” may be interpreted as being previously set or defined by the system.
  • “A may be set” may include “A is set/defined in advance by the system”.
  • the base station may allocate resources used for transmission and reception of SL channels/signals (hereinafter, SL resources) to the terminal. For example, the base station may transmit information related to the resource to the terminal.
  • SL resources resources used for transmission and reception of SL channels/signals
  • the base station may transmit information related to the resource to the terminal.
  • a method in which a base station allocates SL resources to a UE may be referred to as mode 1 method, mode 1 operation, or resource allocation mode 1.
  • the terminal may select an SL resource within the resource pool based on sensing.
  • a method for selecting an SL resource by a UE may be referred to as a mode 2 method, a mode 2 operation, or a resource allocation mode 2.
  • the terminal can detect SCI transmitted by another terminal, the terminal can identify a resource reserved by another terminal based on the SCI, and the terminal can RSRP measurement value can be obtained.
  • the terminal can select a resource to be used for SL transmission excluding a specific resource within the resource selection window.
  • the terminal may refer to resource allocation information received through the first SCI.
  • the amount of information that the UE can acquire on the first SCI may be limited.
  • the second terminal may transmit additional auxiliary information.
  • the first terminal may use auxiliary information received from the second terminal to improve PSSCH detection performance and/or half-duplex limit reduction and/or select a reserve resource for transmitting and receiving a specific signal.
  • UE-A transmits auxiliary information to UE-B.
  • UE-B selects a resource for PSCCH/PSSCH to be transmitted to UE-A and/or a resource for PSCCH/PSSCH to be transmitted to UE-C (ie, a third UE) based on the auxiliary information received from UE-A.
  • UE-C ie, a third UE
  • FIG. 12 illustrates a procedure for UE-A to transmit auxiliary information to UE-B according to an embodiment of the present specification.
  • the embodiment of FIG. 12 may be combined with various embodiments of the present specification.
  • UE-A may transmit auxiliary information to UE-B.
  • UE-B may select a resource for a PSCCH/PSSCH to be transmitted to UE-A based on auxiliary information received from UE-A, and UE-B may perform SL transmission using the resource.
  • UE-B may select a resource for a PSCCH/PSSCH to be transmitted to UE-C based on auxiliary information received from UE-A, and UE-B may perform SL transmission using the resource.
  • auxiliary information may be referred to as side information or inter-UE coordination information.
  • auxiliary information/additional information/coordination information may mean inter-UE coordination information.
  • the type of coordination information may be related to information based on scheme 1 (Scheme 1) for coordination between terminals or information based on scheme 2 (Scheme 2) for coordination between terminals. More specifically, the type of coordination information is i) information indicating preferred resources related to transmission of UE-B, ii) information indicating non-preferred resources related to transmission of UE-B, or iii) information indicating resources reserved by UE-B. It may be related to any one of conflict information (eg, PSFCH with conflict information).
  • the reserved resource may mean a resource reserved by a first stage SCI (SCI) transmitted by UE-B.
  • the information indicating the conflict of the reserved resources may be referred to as conflict information, a resource conflict indicator, or a resource reselection indicator.
  • the collision of the reserved resources may mean a collision between resources reserved by UEs (eg, UE-B and UE-C).
  • UE-A when UE-A transmits a preferred or non-preferred resource for transmission to assist UE-A in selecting a resource, it may be transmitted through PSCCH/PSSCH according to the amount of information. In this case, UE-A may perform resource (re)selection by itself to secure the PSCCH/PSSCH resource, which may reduce the efficiency of the resource reselection method using auxiliary information.
  • PSCCH/PSSCH transmission including the auxiliary information may cause problems such as increasing congestion again or causing a HALF-DUPLEX problem due to the transmission.
  • UE-A may transmit information or an indicator triggering reselection for selection/reservation resources for UE-B transmission to UE-B.
  • the resource reselection indicator or the resource collision indicator may be transmitted from UE-A to UE-B through PSFCH resources or in the form of a PSFCH format.
  • the PSFCH resource for the resource collision indicator or its candidate set may be set (in advance) independently of the PSFCH resource configuration for SL HARQ-ACK, or PC5-RRC terminal It may be that it is set in between.
  • the PSFCH resource or its candidate set for the resource collision indicator may inherit all or part of the PSFCH resource configuration for SL HARQ-ACK (eg, PSFCH resource period), , and/or PSFCH state (ACK or NACK, m_CS value) may be set separately (in advance) or set to PC5-RRC.
  • the PSFCH resource period for the resource collision indicator may be equal to and/or larger than the PSFCH resource period for SL HARQ-ACK.
  • a specific terminal may not support the SL reception operation for all or part of the SL channel.
  • a specific terminal may not support a reception operation for all SL channels, but may support a transmission operation for all or part of the SL channels.
  • a specific terminal may support PSFCH and/or S-SSB reception, but may not support other SL reception operations.
  • a specific terminal may not support a sensing operation for all or some (transmission) resource pools.
  • the sensing operation may include both FULL SENSING and PARTIAL SENSING.
  • the sensing operation may include only FULL SENSING or PARTIAL SENSING.
  • the sensing operation (FULL SENSING/PARTIAL SENSING) may be supported or not depending on UE capability.
  • the terminal may report UE capability information related to sidelink communication supported by the terminal i) to the base station (via RRC) or ii) instruct / report to another terminal (via PC5 RRC).
  • UE capability information related to sidelink communication supported by the terminal i) to the base station (via RRC) or ii) instruct / report to another terminal (via PC5 RRC).
  • another terminal may receive the UE capability information from a base station while communicating with the terminal.
  • the UE may indicate the UE capability information to another UE based on at least one of the first SCI, the second SCI, the PSSCH, the PSFCH, and/or the S-SSB.
  • a specific terminal can transmit inter-device coordination information to another terminal, and the terminal receiving the coordination information again can use it when (re)selecting its own resource.
  • a terminal may perform a sensing operation.
  • the sensing result performed by the terminal may be used together or only the adjustment information may be used.
  • Adjustment information may include information related to any one of the following i) to iii).
  • the adjustment information based on i) may include preferred resources for transmission of UE-B.
  • the adjustment information based on ii) may include non-preferred resources for UE-B transmission.
  • the adjustment information based on iii) may include information indicating a collision of resources reserved by UE-B.
  • a UE (hereinafter referred to as UE-A) that transmits the adjustment information, based on UE capability information, i) the type of the adjustment information, ii) a method for generating the adjustment information, and/or iii) adjustment You can decide whether or not to transmit information.
  • the UE capability information may be related to at least one of i) capability of UE-A to transmit coordination information and/or ii) capability of UE-B to receive and use coordination information.
  • UE-A may transmit UE-to-UE coordination information based on UE-B's capability (eg, first capability information).
  • UE-B's capability eg, first capability information
  • the type of UE-to-UE coordination information that can be supported/received/used by the UE-B can be determined.
  • UE-A Adjustment information may not be generated (sent).
  • UE-A may transmit inter-device coordination information based on UE-A's capability (eg, second capability information). At this time, based on the second capability information, the type of inter-UE coordination information that can be supported/generated/transmitted by UE-A can be determined. UE-A may transmit UE-to-UE coordination information based on the type of UE-to-UE coordination information that can be supported (transmitted) by UE-A. As a specific example, if there is no type of inter-device coordination information that can be supported (transmitted) by UE-A based on the second capability information, UE-A may not generate (transmit) inter-device coordination information. .
  • UE-A may transmit inter-device coordination information based on the first capability information and the second capability information.
  • UE-A provides inter-device communication based on i) the type of inter-device coordination information that can be supported (received) by UE-B and ii) the type of inter-device coordination information that can be supported (transmitted) by UE-A. Adjustment information can be transmitted.
  • UE-A/UE-B transmission of adjustment information based on the aforementioned UE capability will be described in detail, focusing on the sensing capability and reception capability of UE-A/UE-B.
  • the sensing capability and reception capability described below are only examples of UE capabilities related to the transmission (and/or reception) of coordination information, and the signaling of UE capability-based coordination information between UEs is limited to sensing capability and reception capability. This does not mean that it is applied.
  • UE capability related to transmission (and/or reception) of adjustment information may be determined based on other capabilities other than the UE's sensing capability and reception capability.
  • UE capability related to transmission (and/or reception) of coordination information may be determined based on a combination of sensing capabilities, reception capabilities, and other capabilities of the UE.
  • UE capability related to transmission (and/or reception) of coordination information may be determined based on previously set information.
  • UE-A may use i) preferred resources, ii) non-preferred resources, and/or iii) resource reselection indication based on UE-A's capabilities. In other words, whether UE-A can use all of the adjustment information generation methods may be determined based on UE-A capabilities.
  • the capability of UE-A may be determined based on at least one of i) PSCCH and/or PSSCH reception capability, ii) FULL SENSING operation capability, and/or iii) PARTIAL SENSING operation capability.
  • the type of inter-UE coordination information that can be generated/supported/transmitted by UE-A based on UE-A's capabilities e.g. i) preferred resource, ii) non-preferred resource and/or iii) resource reselection
  • An indication an indication of collision of reserved resources
  • UE-A may use a resource that cannot perform SL reception by generating adjustment information. That is, UE-A may transmit adjustment information generated based on a resource that cannot perform SL reception. For example, UE-A may not be able to generate adjustment information based on a sensing operation when it does not have FULL SENSING and/or PARTIAL SENSING capabilities. That is, UE-A may not be able to transmit adjustment information generated based on a sensing operation.
  • UE-A when UE-A does not have FULL SENSING and/or PARTIAL SENSING capabilities, it may select a non-preferred resource and/or a resource reselection indication as an adjustment information type. That is, UE-A may generate (transmit) inter-device coordination information including a non-preferred resource or resource reselection indication (collision indication of reserved resources). For example, when UE-A does not have FULL SENSING and/or PARTIAL SENSING capabilities, it may not be able to select a preferred resource as an adjustment information type. That is, UE-A may not be able to generate (transmit) inter-device coordination information including preferred resources.
  • UE-A may use a resource in which UE-A cannot perform SL reception by generating adjustment information. That is, UE-A may transmit adjustment information generated based on a resource that cannot perform SL reception. For example, UE-A may not be able to generate adjustment information based on a sensing operation when it has no PSCCH and/or PSSCH reception capability. That is, UE-A may not be able to transmit adjustment information generated based on a sensing operation.
  • UE-A may not be able to use information about reception resources of UE-A as a method of generating coordination information. That is, UE-A may not be able to generate (transmit) adjustment information based on information on reception resources of UE-A. For example, UE-A may select a non-preferred resource and/or a resource reselection indication as the adjustment information type when there is no PSCCH and/or PSSCH reception capability. That is, UE-A may generate (transmit) inter-device coordination information including a non-preferred resource or resource reselection indication (collision indication of reserved resources).
  • UE-A may not be able to select a preferred resource as an adjustment information type when it has no PSCCH and/or PSSCH reception capability. That is, UE-A may not be able to generate (transmit) inter-device coordination information including preferred resources.
  • UE-A may select a preferred resource and/or a non-preferred resource when UE-B supports full sensing operation capability and/or PARTIAL SENSING operation capability. That is, UE-A may generate (transmit) inter-device coordination information including preferred resources and/or non-preferred resources.
  • UE-A determines the type of UE-to-UE coordination information that can be supported/used/received by UE-B based on UE-B's capabilities (eg i) preferred resources, ii) non-preferred resources and/or iii) resource resources.
  • One of the selection indications can be determined.
  • UE-A may select only preferred resources as the type of adjustment information when UE-B does not support full sensing and/or partial sensing operation capabilities. That is, UE-A may transmit UE-to-UE coordination information including preferred resources to UE-B.
  • UE-A may not select a non-preferred resource as a type of adjustment information when UE-B does not support FULL SENSING and/or PARTIAL SENSING capability. That is, UE-A may not transmit UE-to-UE coordination information including non-preferred resources to UE-B.
  • UE-A may not use PSFCH TX/RX collision and/or PSFCH TX/TX collision as a method of generating coordination information when it has no PSFCH reception capability. That is, the UE-A may not be able to generate (transmit) inter-device coordination information including information (resource collision indicator/resource reselection indicator) indicating a collision of reserved resources.
  • UE-A may not be able to select a resource reselection indication as an adjustment information type when UE-B has no PSFCH reception capability. That is, UE-A may not transmit inter-terminal coordination information including information indicating collision of reserved resources (resource collision indicator/resource reselection indicator) to UE-B.
  • UE-A may not be able to select a resource reselection indication as an adjustment information type when UE-A does not have a PSFCH reception capability. That is, the UE-A may not be able to generate (transmit) inter-device coordination information including information (resource collision indicator/resource reselection indicator) indicating a collision of reserved resources.
  • UE-A may not use PSFCH TX/RX collision and/or PSFCH TX/TX collision as a method of generating coordination information when UE-B has no PSFCH reception capability.
  • UE-A may receive UE capabilities of UE-B from UE-B (eg, PC5 RRC message/PSCCH/PSSCH).
  • UE-A may receive UE-B's terminal capabilities from a third node different from UE-B.
  • the third node may be a terminal different from UE-B or a base station.
  • a UE (hereinafter referred to as UE-B) that receives and uses coordination information transmits coordination information received from a UE (hereinafter referred to as UE-A) that transmits coordination information according to its own terminal capability (hereinafter referred to as UE-B's capability) to its resource You can decide whether to use it for (re)selection operation.
  • UE-B when UE-B does not have FULL SENSING and/or PARTIAL SENSING capabilities, it may ignore or discard adjustment information of a non-preferred resource type when (re)selecting a resource.
  • UE-B when UE-B does not have FULL SENSING and/or PARTIAL SENSING capabilities, it may ignore or discard adjustment information of a preferred resource type when (re)selecting a resource.
  • UE-B when UE-B does not have FULL SENSING and/or PARTIAL SENSING capabilities, and it is indicated that the received adjustment information is determined based on a sensing operation of UE-A, UE-B transmits the adjustment information Can be ignored or discarded when (re)selecting a resource.
  • UE-B when UE-B has at least PSCCH and/or PSSCH reception capability, it may receive coordination information and perform resource (re)selection using the coordination information.
  • the UE-B may transmit whether or not a resource collision indicator has been received and/or whether reception capability is available for reserved resources through the second SCI and/or the PSSCH.
  • this is only an example of a capability signaling method of the UE (UE-A and/or UE-B), and does not mean that the UE's capability signaling method is limited only to the aforementioned second SCI and/or PSSCH.
  • the capabilities of the UE may be transmitted based on PC5 RRC connection between UEs.
  • UE-B (UE-A) may transmit a PC5 RRC message (eg, UECapabilityInformationSidelink) including capability information related to the above-described inter-device coordination information to UE-A (UE-B).
  • PC5 RRC message eg, UECapabilityInformationSidelink
  • Capability information related to the above-described inter-UE coordination information is i) first information related to the type of inter-UE coordination information that can be received (supported) by the terminal and / or ii) by the terminal It may include second information (tx-IUC-Scheme1-Mode2Sidelink, tx-IUC-Scheme2-Mode2Sidelink) related to the type of inter-device coordination information (IUC information) that can be transmitted (supported).
  • the first information is a type of coordination information between terminals that can be received (supported) by a terminal (eg, UE-B) (i) a preferred resource, ii) a non-preferred resource, iii) a resource collision indicator (reservation resource conflicts)).
  • the first information includes i) information indicating capability for a preferred resource (eg rx-IUC-Scheme1-PreferredMode2Sidelink), ii) information indicating capability for a non-preferred resource (eg rx-IUC-Scheme1-NonPreferredMode2Sidelink) ) and / or iii) information indicating capability for collision of reserved resources (eg, rx-IUC-Scheme2-Mode2Sidelink).
  • a preferred resource eg rx-IUC-Scheme1-PreferredMode2Sidelink
  • ii information indicating capability for a non-preferred resource
  • iii) information indicating capability for collision of reserved resources
  • rx-IUC-Scheme1-PreferredMode2Sidelink and rx-IUC-Scheme1-NonPreferredMode2Sidelink may indicate whether inter-device coordination information including information related to a scheme (scheme 1) for inter-device coordination can be received (supported). .
  • rx-IUC-Scheme1-PreferredMode2Sidelink may indicate whether the terminal can receive (support) inter-terminal coordination information including preferred resources.
  • rx-IUC-Scheme1-NonPreferredMode2Sidelink may indicate whether the terminal can receive inter-terminal coordination information including non-preferred resources.
  • rx-IUC-Scheme2-Mode2Sidelink may indicate whether inter-device coordination information including information related to a scheme (scheme2) for inter-device coordination can be received (supported). Specifically, rx-IUC-Scheme2-Mode2Sidelink may indicate whether a terminal can receive (support) inter-terminal coordination information including information indicating a collision of reserved resources (resource conflict indicator/resource reselection indicator). there is.
  • the second information is a type of coordination information between terminals that can be transmitted (supported) by a terminal (eg, UE-A) (i) a preferred resource, ii) a non-preferred resource, iii) a resource collision indicator (reservation resource conflicts)).
  • a terminal eg, UE-A
  • a preferred resource e.g. a preferred resource
  • a non-preferred resource e.g., a resource collision indicator (reservation resource conflicts)
  • the second information is i) information indicating capability for preferred resources and / or non-preferred resources (eg, tx-IUC-Scheme1-Mode2Sidelink) and / or ii) information indicating capability for collision of reserved resources ( Example: tx-IUC-Scheme2-Mode2Sidelink).
  • tx-IUC-Scheme1-Mode2Sidelink may indicate whether inter-device coordination information including information related to a scheme (scheme 1) for inter-device coordination can be transmitted (supported). Specifically, tx-IUC-Scheme1-Mode2Sidelink may indicate whether the terminal can transmit (support) inter-terminal coordination information including preferred resources and/or non-preferred resources.
  • tx-IUC-Scheme2-Mode2Sidelink may indicate whether inter-device coordination information including information related to a scheme (scheme2) for inter-device coordination can be transmitted (supported).
  • UE capability information related to inter-device coordination information is only an example for convenience of description, and the implementation method of capability information for performing operations according to the embodiments described in this specification is shown as the above-described example. It is not meant to be limiting.
  • UE capability information related to inter-device coordination information may be configured in a different way. Specifically, a lookup table indicating whether the type of coordination information between each terminal is supported (whether it can be transmitted/whether it can be received) can be defined. At this time, each column of the lookup table indicates whether the type of coordination information between each terminal is supported (whether transmission/reception is possible), and each row of the lookup table represents coordination information between terminals of each terminal It may correspond to capabilities related to.
  • the UE capability information related to the inter-device coordination information may be composed of information indicating one row in the lookup table.
  • the UE-A may select UE-B from among UEs capable of receiving a resource collision indicator and transmit a resource collision indicator (including inter-device coordination information or PSFCH).
  • the second SCI may be a second SCI format (eg, SCI format 2-C) used to transmit preferred resources and/or non-preferred resources.
  • a field indicating a set of preferred resources and/or non-preferred resources in the second SCI format may be reserved and not used or its value may be set to 0.
  • the second SCI format may include an indicator indicating at least one of i) a preferred resource, ii) a non-preferred resource, iii) whether a resource collision indicator can be received, and/or iv) a request for additional information.
  • the UE-A succeeds in receiving the first SCI (first stage SCI) and recognizes that a collision has occurred between resources reserved by a plurality of terminals (ie, SCI format 1-A of the plurality of terminals) can be assumed. At this time, UE-A may fail to receive capability information (eg, second SCI, PSSCH, or UECapabilityInformationSidelink) transmitted by the plurality of terminals, and thus may not recognize whether the corresponding terminals can receive resource collision indicators. . In this case, the following embodiments may be considered as an operation of UE-A.
  • capability information eg, second SCI, PSSCH, or UECapabilityInformationSidelink
  • UE-A when UE-A fails to receive capability information on whether resource collision indicators can be received from each UE, it may operate as follows. UE-A may assume that the UE that has transmitted the first SCI supports and activates reception of a resource collision indicator (including UE-to-UE coordination information). UE-A may transmit a resource conflict indicator (eg, PSFCH with conflict information) to the corresponding terminal.
  • a resource conflict indicator eg, PSFCH with conflict information
  • UE-A when UE-A selects a UE-B to receive a resource collision indicator, UE-A may first select UE-B from among terminals for which reception of a resource collision indicator is activated (ie terminals for which reception of a resource collision indicator is supported). UE-A may additionally include terminals that have not obtained information on whether resource collision indicators are received as resource collision indicator reception targets.
  • the UE-A determines that the terminal does not support resource collision indicator reception ( resource conflict indicator reception is disabled). UE-A may not transmit a resource collision indicator to the corresponding UE.
  • operations of the first UE (UE-A)/second UE (UE-B) may be processed by the devices of FIGS. 15 to 20 (eg, the processors 102 and 202 of FIG. 16) to be described later.
  • inter-UE coordination based on UE capability related to the operation of the first UE (UE-A)/second UE (UE-B) according to the above-described embodiment (eg, Inter-UE Coordination information)
  • Operations related to transmission and reception of information are memory (eg, 104, 204 of FIG. 16) in the form of instructions/programs (eg, instructions, executable code) for driving at least one processor (eg, 102 and 202 of FIG. 16).
  • instructions/programs eg, instructions, executable code
  • FIG. 13 is a flowchart for explaining a method for a first terminal to transmit inter-UE coordination information in a wireless communication system according to an embodiment of the present specification.
  • a method for a first terminal to transmit inter-UE coordination information in a wireless communication system includes a terminal performance information receiving step (S1310) and inter-terminal coordination information.
  • a step of transmitting adjustment information (S1320) may be included.
  • the first terminal may mean UE-A of FIG. 12 and the second terminal may mean UE-B of FIG. 12 .
  • the first terminal may be a terminal that transmits inter-UE coordination information to the second terminal based on UE capability information of the first terminal and/or the second terminal. .
  • the second terminal may be a terminal that receives inter-UE coordination information from the first terminal based on the first terminal and/or UE capability information of the second terminal. .
  • the first terminal receives first capability information related to sidelink communication supported by the second terminal from the second terminal.
  • the first capability information may be based on capability information related to the aforementioned inter-device coordination information.
  • the first capability information may be based on a PC5 RRC message (eg, UECapabilityInformationSidelink) including capability information related to inter-device coordination information.
  • the first capability information may include first information indicating whether reception of the inter-device coordination information is supported by the second terminal.
  • a type of inter-device coordination information supported by the second terminal may be determined based on the first information.
  • the first information includes i) information indicating capability for a preferred resource (eg rx-IUC-Scheme1-PreferredMode2Sidelink), ii) information indicating capability for a non-preferred resource (eg rx-IUC-Scheme1-NonPreferredMode2Sidelink) ) and / or iii) information indicating capability for collision of reserved resources (eg, rx-IUC-Scheme2-Mode2Sidelink).
  • a preferred resource eg rx-IUC-Scheme1-PreferredMode2Sidelink
  • ii information indicating capability for a non-preferred resource
  • iii) information indicating capability for collision of reserved resources
  • the first information may be determined based on sensing capability of the second terminal.
  • the sensing performance of the second terminal may be related to a sensing operation for a resource selection window.
  • the sensing performance of the second terminal is i) no sensing operation for the resource selection window, ii) full sensing support for the resource selection window, iii) PARTIAL SENSING support for the resource selection window, or iv) the resource selection window It can be based on any one of FULL SENSING and PARTIAL SENSING support for.
  • a first terminal (100/200 of FIGS. 15 to 20) is connected to a second terminal (100/200 of FIGS. 15 to 20) related to sidelink communication supported by the second terminal.
  • An operation of receiving first capability information may be implemented by the devices of FIGS. 15 to 20 .
  • one or more processors 102 are configured to receive first capability information related to sidelink communication supported by the second terminal from the second terminal 200. It may control one or more transceivers 106 and/or one or more memories 104.
  • the first terminal transmits the inter-device coordination information to the second terminal based on the first capability information.
  • the type of inter-device coordination information supported by the second terminal may be determined based on the first capability information.
  • the type of inter-device coordination information supported by the second terminal includes i) a preferred resource related to transmission of the second terminal (scheme 1), ii) a non-preferred resource related to transmission of the second terminal (scheme 1), and / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • inter-device coordination information including information related to scheme 2 (eg, collision of the reserved resources) may be transmitted. That is, the first terminal may transmit inter-terminal coordination information including information based on a type that can be supported/received by the second terminal.
  • Information related to scheme 1 for inter-device coordination may include information indicating preferred resources related to transmission of the second terminal or information indicating non-preferred resources related to transmission of the second terminal.
  • Information related to scheme 2 for coordination between terminals may include information indicating a collision of resources reserved by the second terminal.
  • the inter-device coordination information may be transmitted through a physical sidelink shared channel (PSSCH).
  • PSSCH physical sidelink shared channel
  • the first terminal may transmit the coordination information between terminals to the second terminal.
  • a request related to the inter-device coordination information may be based on the above-described additional information request.
  • a request related to the inter-device coordination information may be received through PSSCH (eg, MAC-CE and/or second SCI).
  • the inter-device coordination information may be transmitted based on a second stage SCI (SCI) and/or a Medium Access Control-Control Element (MAC-CE).
  • SCI second stage SCI
  • MAC-CE Medium Access Control-Control Element
  • the inter-device coordination information may be included in the second SCI and transmitted.
  • the first terminal may transmit the second SCI including the inter-terminal coordination information to the second terminal.
  • the inter-UE coordination information may be included in the MAC-CE (eg, Inter-UE Coordination Information MAC CE).
  • the first terminal may transmit the MAC-CE including the inter-device coordination information to the second terminal.
  • the first terminal (100/200 of FIGS. 15 to 20) transmits the inter-device coordination information to the second terminal (100/200 of FIGS. 15 to 20) based on the first performance information.
  • the transmitting operation may be implemented by the devices of FIGS. 15 to 20 .
  • one or more processors 102 may use one or more transceivers 106 and/or one or more transceivers 106 to transmit the inter-device coordination information to a second terminal 200 based on the first capability information.
  • the above memory 104 can be controlled.
  • the method may further include transmitting second capability information.
  • the first terminal transmits second capability information related to sidelink communication supported by the first terminal to the second terminal.
  • the second capability information may be based on capability information related to the aforementioned inter-device coordination information.
  • the second capability information may be based on a PC5 RRC message (eg, UECapabilityInformationSidelink) including capability information related to inter-device coordination information.
  • the "second" capability information is a term used to distinguish the capability information of the first terminal from the capability information of the second terminal, and is not intended to limit the order in which capability signaling is performed.
  • the transmitting of the second performance information may be performed before S1310 or after S1310.
  • the inter-device coordination information may be transmitted based on the first performance information and the second performance information. That is, inter-device coordination information allowed based on the capabilities of the first terminal and the capabilities of the second terminal may be transmitted.
  • the second capability information may include second information indicating whether transmission of the inter-device coordination information is supported by the first terminal.
  • a type of inter-device coordination information supported by the first terminal may be determined based on the second information.
  • the second information is i) information indicating capability for preferred resources and / or non-preferred resources (eg, tx-IUC-Scheme1-Mode2Sidelink) and / or ii) information indicating capability for collision of reserved resources ( Example: tx-IUC-Scheme2-Mode2Sidelink).
  • the type of inter-device coordination information supported by the first terminal includes i) a preferred resource related to transmission of the second terminal (scheme 1), ii) a non-preferred resource related to transmission of the second terminal (scheme 1), and / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • a preferred resource related to transmission of the second terminal Scheme 1
  • a non-preferred resource related to transmission of the second terminal (scheme 1)
  • / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • inter-terminal coordination information supported by the second terminal Based on the type of inter-terminal coordination information supported by the second terminal and the type of inter-terminal coordination information supported by the first terminal: i) information related to scheme 1 for inter-terminal coordination ( Example: the preferred resource/non-preferred resource) or ii) the inter-device coordination information including information related to scheme 2 (eg, collision of the reserved resources) for inter-device coordination may be transmitted.
  • scheme 1 for inter-terminal coordination
  • scheme 2 eg, collision of the reserved resources
  • inter-device coordination information including one of information indicating, ii) information indicating a non-preferred resource related to transmission of the second terminal, or iii) information indicating a collision of resources reserved by the second terminal may be transmitted.
  • information based on the type of inter-device coordination information that can be transmitted/supported by the first terminal can be transmitted.
  • information based on a type of inter-device coordination information that can be received/supported by a second terminal can be transmitted.
  • the first terminal when there is no type of inter-device coordination information that can be transmitted/supported by the first terminal among the types of inter-device coordination information that can be received/supported by the second terminal, the first terminal performs end-to-end coordination information. Information may not be transmitted. For example, when there is no type of inter-device coordination information that can be received/supported by a second terminal among the types of inter-device coordination information that can be transmitted/supported by a first terminal, the first terminal performs end-to-end coordination information. Information may not be transmitted.
  • a first terminal (100/200 of FIGS. 15 to 20) sends a second terminal (100/200 of FIGS. 15 to 20) a first terminal related to sidelink communication supported by the first terminal.
  • An operation of transmitting second capability information may be implemented by the devices of FIGS. 15 to 20 .
  • one or more processors 102 transmit second capability information related to sidelink communication supported by the first terminal to the second terminal 200; may control one or more transceivers 106 and/or one or more memories 104.
  • the method may further include receiving a request for coordination information between terminals.
  • the first terminal may receive a request for inter-device coordination information from the second terminal.
  • the requested type of inter-device coordination information may be based on the first capability information and/or the second capability information.
  • a first terminal may receive a request for a type of inter-device coordination information supported by a second terminal based on the first capability information.
  • the first terminal may receive a request for a type of inter-device coordination information supported by the first terminal based on the second capability information.
  • the first terminal is a type of inter-device coordination information that can be supported by the first terminal and the second terminal based on the first capability information and the second capability information. You can receive a request for
  • one or more processors 102 may include one or more transceivers 106 and/or one or more memories 104 to receive a request for the inter-device coordination information from a second terminal 200. can control.
  • the first terminal may transmit coordination information between terminals based on any one of the following 1) to 6).
  • FIG. 14 is a flowchart for explaining a method for a second terminal to receive inter-UE coordination information in a wireless communication system according to another embodiment of the present specification.
  • a method for receiving inter-UE coordination information by a second terminal in a wireless communication system includes a terminal performance information transmission step (S1410) and inter-UE coordination An information receiving step (S1420) may be included.
  • the first terminal may mean UE-A of FIG. 12 and the second terminal may mean UE-B of FIG. 12 .
  • the first terminal may be a terminal that transmits inter-UE coordination information to the second terminal based on UE capability information of the first terminal and/or the second terminal. .
  • the second terminal may be a terminal that receives inter-UE coordination information from the first terminal based on the first terminal and/or UE capability information of the second terminal. .
  • the second terminal transmits first capability information related to sidelink communication supported by the second terminal to the first terminal.
  • the first capability information may be based on capability information related to the aforementioned inter-device coordination information.
  • the first capability information may be based on a PC5 RRC message (eg, UECapabilityInformationSidelink) including capability information related to inter-device coordination information.
  • the first capability information may include first information indicating whether reception of the inter-device coordination information is supported by the second terminal.
  • a type of inter-device coordination information supported by the second terminal may be determined based on the first information.
  • the first information includes i) information indicating capability for a preferred resource (eg rx-IUC-Scheme1-PreferredMode2Sidelink), ii) information indicating capability for a non-preferred resource (eg rx-IUC-Scheme1-NonPreferredMode2Sidelink) ) and / or iii) information indicating capability for collision of reserved resources (eg, rx-IUC-Scheme2-Mode2Sidelink).
  • a preferred resource eg rx-IUC-Scheme1-PreferredMode2Sidelink
  • ii information indicating capability for a non-preferred resource
  • iii) information indicating capability for collision of reserved resources
  • the first information may be determined based on sensing capability of the second terminal.
  • the sensing performance of the second terminal may be related to a sensing operation for a resource selection window.
  • the sensing performance of the second terminal is i) no sensing operation for the resource selection window, ii) full sensing support for the resource selection window, iii) PARTIAL SENSING support for the resource selection window, or iv) the resource selection window It can be based on any one of FULL SENSING and PARTIAL SENSING support for.
  • the second terminal (100/200 of FIGS. 15 to 20) sends the first terminal (100/200 of FIGS. 15 to 20) a second terminal related to sidelink communication supported by the second terminal.
  • An operation of transmitting first capability information may be implemented by the devices of FIGS. 15 to 20 .
  • one or more processors 202 transmit first capability information related to sidelink communication supported by the second terminal to a first terminal 100; may control one or more transceivers 206 and/or one or more memories 204.
  • the second terminal receives the inter-device coordination information based on the first capability information from the first terminal.
  • the type of inter-device coordination information supported by the second terminal may be determined based on the first capability information.
  • the type of inter-device coordination information supported by the second terminal includes i) a preferred resource related to transmission of the second terminal (scheme 1), ii) a non-preferred resource related to transmission of the second terminal (scheme 1), and / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • inter-device coordination information including information related to scheme 2 (eg, collision of the reserved resources) may be received. That is, the second terminal can receive inter-terminal coordination information including information based on a type that can be supported/received by the second terminal.
  • Information related to scheme 1 for inter-device coordination may include information indicating preferred resources related to transmission of the second terminal or information indicating non-preferred resources related to transmission of the second terminal.
  • Information related to scheme 2 for coordination between terminals may include information indicating a collision of resources reserved by the second terminal.
  • the inter-device coordination information may be received through a physical sidelink shared channel (PSSCH).
  • PSSCH physical sidelink shared channel
  • the second terminal may receive the inter-device coordination information from the first terminal based on transmission of a request related to the inter-device coordination information to the first terminal.
  • a request related to the inter-device coordination information may be based on the above-described additional information request.
  • the request related to the inter-device coordination information may be transmitted through PSSCH (eg, MAC-CE and/or second SCI).
  • the inter-device coordination information may be received based on a second stage SCI (SCI) and/or a Medium Access Control-Control Element (MAC-CE).
  • SCI second stage SCI
  • MAC-CE Medium Access Control-Control Element
  • the inter-device coordination information may be included in the second SCI and received.
  • the second terminal may receive the second SCI including the inter-terminal coordination information from the first terminal.
  • the inter-UE coordination information may be included in the MAC-CE (eg, Inter-UE Coordination Information MAC CE).
  • the second terminal may receive a MAC-CE including the inter-device coordination information from the first terminal.
  • the second terminal receives the inter-device coordination information based on the first performance information from the first terminal (100/200 of FIGS. 15 to 20).
  • the operation may be implemented by the device of FIGS. 15 to 20.
  • one or more processors 202 may use one or more transceivers 206 and/or one or more terminals to receive the inter-device coordination information based on the first capability information from a first terminal 100 .
  • the memory 204 can be controlled.
  • the method may further include receiving second performance information.
  • the second terminal receives second capability information related to sidelink communication supported by the first terminal from the first terminal.
  • the second capability information may be based on capability information related to the aforementioned inter-device coordination information.
  • the second capability information may be based on a PC5 RRC message (eg, UECapabilityInformationSidelink) including capability information related to inter-device coordination information.
  • the "second" capability information is a term used to distinguish the capability information of the first terminal from the capability information of the second terminal, and is not intended to limit the order in which capability signaling is performed.
  • the second performance information receiving step may be performed before S1410 or after S1410.
  • the inter-device coordination information may be transmitted based on the first performance information and the second performance information. That is, inter-device coordination information allowed based on the capabilities of the first terminal and the capabilities of the second terminal may be received.
  • the second capability information may include second information indicating whether transmission of the inter-device coordination information is supported by the first terminal.
  • a type of inter-device coordination information supported by the first terminal may be determined based on the second information.
  • the second information is i) information indicating capability for preferred resources and / or non-preferred resources (eg, tx-IUC-Scheme1-Mode2Sidelink) and / or ii) information indicating capability for collision of reserved resources ( Example: tx-IUC-Scheme2-Mode2Sidelink).
  • the type of inter-device coordination information supported by the first terminal includes i) a preferred resource related to transmission of the second terminal (scheme 1), ii) a non-preferred resource related to transmission of the second terminal (scheme 1), and / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • a preferred resource related to transmission of the second terminal Scheme 1
  • a non-preferred resource related to transmission of the second terminal (scheme 1)
  • / or iii) may be related to at least one of resource collisions (scheme 2) reserved by the second terminal.
  • inter-terminal coordination information supported by the second terminal Based on the type of inter-terminal coordination information supported by the second terminal and the type of inter-terminal coordination information supported by the first terminal: i) information related to scheme 1 for inter-terminal coordination ( Example: the preferred resource/non-preferred resource) or ii) the inter-device coordination information including information related to scheme 2 (eg, collision of the reserved resources) for inter-device coordination may be received.
  • scheme 1 for inter-terminal coordination
  • scheme 2 eg, collision of the reserved resources
  • inter-device coordination information including one of information indicating, ii) information indicating non-preferred resources related to transmission of the second terminal, or iii) information indicating a collision of resources reserved by the second terminal may be received.
  • inter-device coordination information that can be received/supported by the second terminal information based on the type of inter-device coordination information that can be transmitted/supported by the first terminal can be received.
  • information based on a type of inter-device coordination information that can be received/supported by a second terminal can be received.
  • the second terminal when there is no type of inter-device coordination information that can be transmitted/supported by the first terminal among the types of inter-device coordination information that can be received/supported by the second terminal, the second terminal performs inter-device coordination information may not be received. For example, when there is no type of inter-device coordination information that can be received/supported by a second terminal among the types of inter-device coordination information that can be transmitted/supported by a first terminal, the second terminal performs inter-terminal coordination information. information may not be received.
  • the second terminal (100/200 of FIGS. 15 to 20) is connected to the first terminal (100/200 of FIGS. 15 to 20) related to sidelink communication supported by the first terminal.
  • An operation of receiving second capability information may be implemented by the devices of FIGS. 15 to 20 .
  • one or more processors 202 are configured to receive second capability information related to sidelink communication supported by the first terminal from the first terminal 100. may control one or more transceivers 206 and/or one or more memories 204.
  • the method may further include transmitting a request for coordination information between terminals.
  • the second terminal may transmit a request for inter-device coordination information to the first terminal.
  • the requested type of inter-device coordination information may be based on the first capability information and/or the second capability information.
  • the second terminal may transmit a request for the type of inter-device coordination information supported by the second terminal based on the first capability information.
  • the second terminal may transmit a request for the type of inter-device coordination information supported by the first terminal based on the first capability information.
  • the second terminal is a type of inter-device coordination information that can be supported by the first terminal and the second terminal based on the first capability information and the second capability information. You can send a request for
  • one or more processors 202 may include one or more transceivers 206 and/or one or more memories 204 to transmit a request for the inter-device coordination information to a first terminal 100 . can control.
  • the second terminal may receive inter-terminal coordination information based on one of the following 1) to 6).
  • 15 shows a communication system 1, according to an embodiment of the present specification.
  • a communication system 1 to which various embodiments of the present specification are applied includes a wireless device, a base station, and a network.
  • the wireless device means a device that performs communication using a radio access technology (eg, 5G New RAT (NR), Long Term Evolution (LTE)), and may be referred to as a communication/wireless/5G device.
  • wireless devices include robots 100a, vehicles 100b-1 and 100b-2, XR (eXtended Reality) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400.
  • IoT Internet of Thing
  • the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like.
  • the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
  • UAV Unmanned Aerial Vehicle
  • XR devices include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) installed in vehicles, televisions, smartphones, It may be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like.
  • a portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, a smart glass), a computer (eg, a laptop computer, etc.), and the like.
  • Home appliances may include a TV, a refrigerator, a washing machine, and the like.
  • IoT devices may include sensors, smart meters, and the like.
  • a base station and a network may also be implemented as a wireless device, and a specific wireless device 200a may operate as a base station/network node to other wireless devices.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200 .
  • AI Artificial Intelligence
  • the network 300 may be configured using a 3G network, a 4G (eg LTE) network, or a 5G (eg NR) network.
  • the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but may also communicate directly (eg, sidelink communication) without going through the base station/network.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle to vehicle (V2V)/vehicle to everything (V2X) communication).
  • IoT devices eg, sensors
  • IoT devices may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.
  • Wireless communication/connection 150a, 150b, and 150c may be performed between the wireless devices 100a to 100f/base station 200 and the base station 200/base station 200.
  • wireless communication/connection refers to various wireless connections such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g. relay, Integrated Access Backhaul (IAB)).
  • IAB Integrated Access Backhaul
  • Wireless communication/connection (150a, 150b, 150c) allows wireless devices and base stations/wireless devices, and base stations and base stations to transmit/receive radio signals to/from each other.
  • the wireless communication/connection 150a, 150b, and 150c may transmit/receive signals through various physical channels.
  • various signal processing processes eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.
  • resource allocation processes e.g., resource allocation processes, and the like.
  • FIG. 16 illustrates a wireless device according to an embodiment of the present specification.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive radio signals through various radio access technologies (eg, LTE and NR).
  • ⁇ the first wireless device 100, the second wireless device 200 ⁇ is the ⁇ wireless device 100x, the base station 200 ⁇ of FIG. 15 and/or the ⁇ wireless device 100x, the wireless device 100x.
  • ⁇ can correspond.
  • the first wireless device 100 includes one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and/or one or more antennas 108.
  • the processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or flowcharts of operations disclosed herein.
  • the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a radio signal including the first information/signal through the transceiver 106 .
  • the processor 102 may receive a radio signal including the second information/signal through the transceiver 106, and then store information obtained from signal processing of the second information/signal in the memory 104.
  • the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102 .
  • memory 104 may perform some or all of the processes controlled by processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them.
  • the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (eg, LTE, NR).
  • the transceiver 106 may be coupled to the processor 102 and may transmit and/or receive wireless signals via one or more antennas 108 .
  • the transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
  • RF radio frequency
  • a wireless device may mean a communication modem/circuit/chip.
  • the second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
  • Processor 202 controls memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein.
  • the processor 202 may process information in the memory 204 to generate third information/signal, and transmit a radio signal including the third information/signal through the transceiver 206.
  • the processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 and store information obtained from signal processing of the fourth information/signal in the memory 204 .
  • the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202 .
  • memory 204 may perform some or all of the processes controlled by processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them.
  • the processor 202 and memory 204 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (eg, LTE, NR).
  • the transceiver 206 may be coupled to the processor 202 and may transmit and/or receive wireless signals via one or more antennas 208 .
  • the transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be used interchangeably with an RF unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) in accordance with the descriptions, functions, procedures, proposals, methods and/or operational flow charts disclosed herein.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • processors 102, 202 may generate messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams disclosed herein.
  • One or more processors 102, 202 generate PDUs, SDUs, messages, control information, data or signals (e.g., baseband signals) containing information according to the functions, procedures, proposals and/or methods disclosed herein , can be provided to one or more transceivers 106, 206.
  • One or more processors 102, 202 may receive signals (eg, baseband signals) from one or more transceivers 106, 206, and descriptions, functions, procedures, proposals, methods, and/or flowcharts of operations disclosed herein PDUs, SDUs, messages, control information, data or information can be obtained according to these.
  • signals eg, baseband signals
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor or microcomputer.
  • One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • firmware or software may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like.
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and It can be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.
  • One or more memories 104, 204 may be coupled with one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions.
  • One or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • One or more memories 104, 204 may be located internally and/or external to one or more processors 102, 202. Additionally, one or more memories 104, 204 may be coupled to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
  • One or more transceivers 106, 206 may transmit user data, control information, radio signals/channels, etc., as referred to in the methods and/or operational flow charts herein, to one or more other devices.
  • One or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in descriptions, functions, procedures, proposals, methods and/or operational flow charts, etc. disclosed herein from one or more other devices. there is.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive wireless signals.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Additionally, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled with one or more antennas 108, 208, and one or more transceivers 106, 206 via one or more antennas 108, 208, as described herein, function. , procedures, proposals, methods and / or operation flowcharts, etc. can be set to transmit and receive user data, control information, radio signals / channels, etc.
  • one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers (106, 206) convert the received radio signals/channels from RF band signals in order to process the received user data, control information, radio signals/channels, etc. using one or more processors (102, 202). It can be converted into a baseband signal.
  • One or more transceivers 106 and 206 may convert user data, control information, and radio signals/channels processed by one or more processors 102 and 202 from baseband signals to RF band signals.
  • one or more of the transceivers 106, 206 may include (analog) oscillators and/or filters.
  • FIG. 17 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present specification.
  • the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060.
  • the operations/functions of FIG. 17 may be performed by processors 102 and 202 and/or transceivers 106 and 206 of FIG. 16 .
  • the hardware elements of FIG. 17 may be implemented in processors 102 and 202 and/or transceivers 106 and 206 of FIG. 16 .
  • blocks 1010-1060 may be implemented in processors 102 and 202 of FIG. 16 .
  • blocks 1010 to 1050 may be implemented in processors 102 and 202 of FIG. 16
  • block 1060 may be implemented in transceivers 106 and 206 of FIG. 16 .
  • the codeword may be converted into a radio signal through the signal processing circuit 1000 of FIG. 17 .
  • a codeword is an encoded bit sequence of an information block.
  • Information blocks may include transport blocks (eg, UL-SCH transport blocks, DL-SCH transport blocks).
  • Radio signals may be transmitted through various physical channels (eg, PUSCH, PDSCH).
  • the codeword may be converted into a scrambled bit sequence by the scrambler 1010.
  • a scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of a wireless device.
  • the scrambled bit sequence may be modulated into a modulation symbol sequence by modulator 1020.
  • the modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), and the like.
  • the complex modulation symbol sequence may be mapped to one or more transport layers by the layer mapper 1030.
  • Modulation symbols of each transport layer may be mapped to corresponding antenna port(s) by the precoder 1040 (precoding).
  • the output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the N*M precoding matrix W.
  • N is the number of antenna ports and M is the number of transport layers.
  • the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transformation) on complex modulation symbols. Also, the precoder 1040 may perform precoding without performing transform precoding.
  • the resource mapper 1050 may map modulation symbols of each antenna port to time-frequency resources.
  • the time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain.
  • the signal generator 1060 generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices through each antenna.
  • the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), a frequency uplink converter, and the like.
  • IFFT inverse fast Fourier transform
  • CP cyclic prefix
  • DAC digital-to-analog converter
  • the signal processing process for the received signal in the wireless device may be configured in reverse to the signal processing process 1010 to 1060 of FIG. 17 .
  • wireless devices eg, 100 and 200 of FIG. 16
  • the received radio signal may be converted into a baseband signal through a signal restorer.
  • the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module.
  • ADC analog-to-digital converter
  • FFT fast Fourier transform
  • the baseband signal may be restored to a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scramble process.
  • a signal processing circuit for a received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.
  • a wireless device may be implemented in various forms according to use-case/service (see FIG. 15).
  • wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 16, and include various elements, components, units/units, and/or modules. ) can be configured.
  • the wireless devices 100 and 200 may include a communication unit 110 , a control unit 120 , a memory unit 130 and an additional element 140 .
  • the communication unit may include communication circuitry 112 and transceiver(s) 114 .
  • communication circuitry 112 may include one or more processors 102, 202 of FIG. 16 and/or one or more memories 104, 204.
  • transceiver(s) 114 may include one or more transceivers 106, 206 of FIG. 16 and/or one or more antennas 108, 208.
  • the control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls overall operations of the wireless device. For example, the control unit 120 may control electrical/mechanical operations of the wireless device based on programs/codes/commands/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to the outside (eg, another communication device) through the communication unit 110 through a wireless/wired interface, or transmits the information stored in the memory unit 130 to the outside (eg, another communication device) through the communication unit 110. Information received through a wireless/wired interface from other communication devices) may be stored in the memory unit 130 .
  • the additional element 140 may be configured in various ways according to the type of wireless device.
  • the additional element 140 may include at least one of a power unit/battery, an I/O unit, a driving unit, and a computing unit.
  • the wireless device may be a robot (Fig. 15, 100a), a vehicle (Fig. 15, 100b-1, 100b-2), an XR device (Fig. 15, 100c), a mobile device (Fig. 15, 100d), a home appliance. (FIG. 15, 100e), IoT device (FIG.
  • digital broadcasting terminal digital broadcasting terminal
  • hologram device public safety device
  • MTC device medical device
  • fintech device or financial device
  • security device climate/environmental device
  • It may be implemented in the form of an AI server/device (Fig. 15, 400), a base station (Fig. 15, 200), a network node, and the like.
  • Wireless devices can be mobile or used in a fixed location depending on the use-case/service.
  • various elements, components, units/units, and/or modules in the wireless devices 100 and 200 may be entirely interconnected through a wired interface or at least partially connected wirelessly through the communication unit 110.
  • the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first units (eg, 130 and 140) are connected through the communication unit 110.
  • the control unit 120 and the first units eg, 130 and 140
  • each element, component, unit/unit, and/or module within the wireless device 100, 200 may further include one or more elements.
  • the control unit 120 may be composed of one or more processor sets.
  • the controller 120 may include a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, a memory control processor, and the like.
  • the memory unit 130 may include random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.
  • a portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, a smart glass), and a portable computer (eg, a laptop computer).
  • a mobile device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).
  • MS mobile station
  • UT user terminal
  • MSS mobile subscriber station
  • SS subscriber station
  • AMS advanced mobile station
  • WT wireless terminal
  • a portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ) may be included.
  • the antenna unit 108 may be configured as part of the communication unit 110 .
  • Blocks 110 to 130/140a to 140c respectively correspond to blocks 110 to 130/140 of FIG. 18 .
  • the communication unit 110 may transmit/receive signals (eg, data, control signals, etc.) with other wireless devices and base stations.
  • the controller 120 may perform various operations by controlling components of the portable device 100 .
  • the control unit 120 may include an application processor (AP).
  • the memory unit 130 may store data/parameters/programs/codes/commands necessary for driving the portable device 100 .
  • the memory unit 130 may store input/output data/information.
  • the power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, and the like.
  • the interface unit 140b may support connection between the portable device 100 and other external devices.
  • the interface unit 140b may include various ports (eg, audio input/output ports and video input/output ports) for connection with external devices.
  • the input/output unit 140c may receive or output image information/signal, audio information/signal, data, and/or information input from a user.
  • the input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.
  • the input/output unit 140c obtains information/signals (eg, touch, text, voice, image, video) input from the user, and the acquired information/signals are stored in the memory unit 130.
  • the communication unit 110 may convert the information/signal stored in the memory into a wireless signal, and directly transmit the converted wireless signal to another wireless device or to a base station.
  • the communication unit 110 may receive a radio signal from another wireless device or a base station and then restore the received radio signal to original information/signal. After the restored information/signal is stored in the memory unit 130, it may be output in various forms (eg, text, voice, image, video, haptic) through the input/output unit 140c.
  • Vehicles or autonomous vehicles may be implemented as mobile robots, vehicles, trains, manned/unmanned aerial vehicles (AVs), ships, and the like.
  • AVs manned/unmanned aerial vehicles
  • a vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit.
  • a portion 140d may be included.
  • the antenna unit 108 may be configured as part of the communication unit 110 .
  • Blocks 110/130/140a to 140d respectively correspond to blocks 110/130/140 of FIG. 18 .
  • the communication unit 110 may transmit/receive signals (eg, data, control signals, etc.) with external devices such as other vehicles, base stations (e.g. base stations, roadside base stations, etc.), servers, and the like.
  • the controller 120 may perform various operations by controlling elements of the vehicle or autonomous vehicle 100 .
  • the controller 120 may include an Electronic Control Unit (ECU).
  • the driving unit 140a may drive the vehicle or autonomous vehicle 100 on the ground.
  • the driving unit 140a may include an engine, a motor, a power train, a wheel, a brake, a steering device, and the like.
  • the power supply unit 140b supplies power to the vehicle or autonomous vehicle 100, and may include a wired/wireless charging circuit, a battery, and the like.
  • the sensor unit 140c may obtain vehicle conditions, surrounding environment information, and user information.
  • the sensor unit 140c includes an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, and a vehicle forward.
  • IMU inertial measurement unit
  • /Can include a reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illuminance sensor, pedal position sensor, and the like.
  • the autonomous driving unit 140d includes a technology for maintaining a driving lane, a technology for automatically adjusting speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and a technology for automatically setting a route when a destination is set and driving. technology can be implemented.
  • the communication unit 110 may receive map data, traffic information data, and the like from an external server.
  • the autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the acquired data.
  • the controller 120 may control the driving unit 140a so that the vehicle or autonomous vehicle 100 moves along the autonomous driving path according to the driving plan (eg, speed/direction adjustment).
  • the communicator 110 may non-/periodically obtain the latest traffic information data from an external server and obtain surrounding traffic information data from surrounding vehicles.
  • the sensor unit 140c may acquire vehicle state and surrounding environment information.
  • the autonomous driving unit 140d may update an autonomous driving route and a driving plan based on newly acquired data/information.
  • the communication unit 110 may transmit information about a vehicle location, an autonomous driving route, a driving plan, and the like to an external server.
  • the external server may predict traffic information data in advance using AI technology based on information collected from the vehicle or self-driving vehicles, and may provide the predicted traffic information data to the vehicle or self-driving vehicles.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention, selon un mode de réalisation, concerne un procédé par lequel un premier terminal transmet des informations de coordination entre UE dans un système de communication sans fil comprenant les étapes consistant à : recevoir, en provenance d'un second terminal, des premières informations de capacité relatives à une communication de liaison latérale prise en charge par le second terminal ; et transmettre, au second terminal, les informations de coordination entre UE sur la base des premières informations de capacité. Le procédé est caractérisé en ce que les informations de coordination entre UE, comprenant (i) des informations relatives à un schéma 1 de coordination entre UE ou (ii) des informations relatives à un schéma 2 de coordination entre UE, sont transmises sur la base des premières informations de capacité.
PCT/KR2022/013581 2021-09-09 2022-09-08 Procédé de transmission et de réception d'informations de coordination entre ue dans un système de communication sans fil, et dispositif associé Ceased WO2023038482A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163242479P 2021-09-09 2021-09-09
US63/242,479 2021-09-09
KR20220002883 2022-01-07
KR10-2022-0002883 2022-01-07

Publications (1)

Publication Number Publication Date
WO2023038482A1 true WO2023038482A1 (fr) 2023-03-16

Family

ID=85506822

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/013581 Ceased WO2023038482A1 (fr) 2021-09-09 2022-09-08 Procédé de transmission et de réception d'informations de coordination entre ue dans un système de communication sans fil, et dispositif associé

Country Status (1)

Country Link
WO (1) WO2023038482A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170188391A1 (en) * 2015-12-28 2017-06-29 Samsung Electronics Co., Ltd Methods and apparatus for resource collision avoidance in vehicle to vehicle communication

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170188391A1 (en) * 2015-12-28 2017-06-29 Samsung Electronics Co., Ltd Methods and apparatus for resource collision avoidance in vehicle to vehicle communication

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Feasibility and benefits of mode 2 enhancements for inter-UE coordination", 3GPP DRAFT; R1-2108137, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052033804 *
LENOVO, MOTOROLA MOBILITY: "Discussion on sidelink resource allocation enhancements", 3GPP DRAFT; R2-2107918, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210809 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034521 *
MITSUBISHI ELECTRIC: "Inter-UE coordination for enhanced resource allocation", 3GPP DRAFT; R1-2106570, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 2 August 2021 (2021-08-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052044138 *
PANASONIC: "Inter-UE coordination for Mode 2 enhancements", 3GPP DRAFT; R1-2107303, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052033549 *

Similar Documents

Publication Publication Date Title
WO2021221363A1 (fr) Procédé et appareil permettant de réaliser une communication sl sur la base d'un surdébit de psfch dans v2x de nr
WO2023287224A1 (fr) Procédé de transmission et de réception d'un canal physique partagé de liaison latérale dans un système de communication sans fil, et dispositif associé
WO2022139491A1 (fr) Procédé et dispositif pour effectuer une opération drx sl sur la base d'une configuration drx par défaut dans nr v2x
WO2021101308A1 (fr) Procédé et dispositif de transmission de signal de référence dans nr v2x
WO2021086163A1 (fr) Procédé et dispositif de réalisation de transmission sl en nr v2x
WO2022235082A1 (fr) Procédé et appareil de détermination d'une ressource non préférée dans un système de communication sans fil
WO2022220615A1 (fr) Procédé et dispositif pour transmettre ou recevoir un canal physique de rétroaction de liaison latérale dans un système de communication sans fil
WO2023043283A1 (fr) Procédé de transmission et de réception d'informations de coordination inter-équipements utilisateurs dans un système de communication sans fil et appareil associé
WO2023022576A1 (fr) Procédé pour transmettre/recevoir des informations de coordination inter-ue dans un système de communication sans fil, et dispositif associé
WO2022203438A1 (fr) Procédé et dispositif de transmission d'une rétroaction harq sl dans nr v2x
WO2022235095A1 (fr) Procédé et appareil pour déterminer une ressource candidate pour une détection partielle dans v2x nr
WO2022131761A1 (fr) Procédé et dispositif de réalisation d'opération drx sl dans v2x nr sur la base d'informations d'attribution de ressources
WO2021230695A1 (fr) Procédé et dispositif pour signaler un retour harq de sl à une station de base en nr v2x
WO2023038483A1 (fr) Procédé d'émission et de réception d'informations relatives à un conflit de ressources réservées dans un système de communication sans fil, et dispositif associé
WO2023033628A1 (fr) Procédé de transmission et de réception de données de liaison latérale dans un système de communication sans fil, et appareil associé
WO2022154512A1 (fr) Procédé et appareil de réalisation d'une détection partielle sur la base de la priorité dans un système nr v2x
WO2022154550A1 (fr) Procédé et appareil de mesure de cbr associé à une détection partielle dans nr v2x
WO2022154413A1 (fr) Procédé et dispositif permettant de réaliser une drx sl d'après la mobilité d'un terminal en nr v2x
WO2022131831A1 (fr) Procédé et dispositif de sélection de ressources sur la base d'un canal logique dans un système nr v2x
WO2021101329A1 (fr) Procédé et appareil permettant d'effectuer des communications par liaison latérale à base de dci dans nr v2x
WO2023063668A1 (fr) Procédé et dispositif de communication sur la base d'information de coordination entre équipements utilisateurs dans une communication de technologie nr v2x
WO2023008823A1 (fr) Procédé et appareil pour effectuer une communication sans fil associée à un rapport de csi de sl dans un v2x de nr
WO2023033620A1 (fr) Procédé de transmission et de réception de données sur la base de drx de sl dans un système de communication sans fil, et appareil associé
WO2023022488A1 (fr) Procédé et dispositif d'exploitation drx sl basés sur une indication d'état de transmission de liaison latérale dans la v2x nr
WO2022197060A1 (fr) Procédé de transmission et de réception de pssch dans un système de communication sans fil, et dispositif correspondant

Legal Events

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

Ref document number: 22867750

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22867750

Country of ref document: EP

Kind code of ref document: A1