WO2023282663A2

WO2023282663A2 - Method and device for scheduling physical sidelink channel in wireless communication system

Info

Publication number: WO2023282663A2
Application number: PCT/KR2022/009851
Authority: WO
Inventors: 황대성; 이승민
Original assignee: 엘지전자 주식회사
Priority date: 2021-07-09
Filing date: 2022-07-07
Publication date: 2023-01-12
Also published as: WO2023282663A3

Abstract

A method performed by a first terminal for scheduling of a physical sidelink channel in a wireless communication system according to an embodiment of the present specification comprises the steps of: receiving configuration information related to a search space from a base station; receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from the base station; and transmitting the physical sidelink channel to a second terminal on the basis of the DCI. The DCI is received on the basis of monitoring of a physical downlink control channel (physical downlink channel) (PDCCH) related to the search space. The configuration information includes information on an SL carrier related to the search space. The DCI includes information related to an SL carrier related to the scheduling, on the basis of the search space related to one or more SL carriers.

Description

Method and apparatus for scheduling physical sidelink channel in wireless communication system

The present specification relates to a method and apparatus for scheduling a physical sidelink channel 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.). Examples of 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. There is a division multiple access (MC-FDMA) system and a multi carrier frequency division multiple access (MC-FDMA) system.

Sidelink (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). 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.

Meanwhile, as more and more communication devices require greater communication capacity, a need for improved mobile broadband communication compared to conventional radio access technology (RAT) has emerged. Accordingly, communication systems considering reliability and latency-sensitive services or terminals are being discussed, such as improved mobile broadband communication, massive MTC (Machine Type Communication), and URLLC (Ultra-Reliable and Low Latency Communication). The next-generation radio access technology taking into account the above may be referred to as new radio access technology (RAT) or new radio (NR). Even in NR, vehicle-to-everything (V2X) communication may be supported.

According to the related art, the following operation/configuration is performed in relation to scheduling of a sidelink carrier and a sidelink channel.

1) In existing sidelink communication, it is considered that there is only one carrier, and thus sidelink carrier-related information is not delivered to the UE during SL scheduling. 2) UE capability related to limitations of BD (Blind Decoding)/CCE (Control Channel Element) for PDCCH reception is defined based on a DL carrier rather than a sidelink carrier. If the BD/CCE is out of the limit, monitoring of the PDCCH in units of search spaces (Search Spaces, SS) may be omitted.

According to the operation/configuration of 1) according to the prior art, the following problems may occur when one or more SL carriers are supported. Specifically, a UE receiving SL scheduling information (DCI) based on SL mode 1 (ie, SL resource allocation mode 1) cannot know which SL carrier the corresponding scheduling is for.

An object of the present specification is to propose a method for resolving ambiguity related to identification of a carrier for a terminal to perform sidelink communication in a scheduling operation based on one or more sidelink carriers.

According to the operation/configuration of 2) according to the prior art, the following problems may occur when one or more SL carriers are supported. When the number of SL carriers is different from the number of DL carriers, an operation for receiving scheduling information (DCI) based on SL mode 1 (ie, PDCCH monitoring) may not be normally performed. For example, it may be assumed that the number of DL carriers is one but the number of SL carriers is two or more. At this time, a case may occur in which the UE cannot monitor the PDCCH related to the SL carrier due to the BD/CCE restriction set based on the DL carrier.

Another object of the present specification is to propose a method for solving the problem that PDCCH monitoring related to scheduling based on one or more sidelink carriers is not normally performed due to BD/CCE limitation based on DL carriers. .

The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

A method performed by a first terminal for scheduling of a physical sidelink channel in a wireless communication system according to an embodiment of the present specification includes receiving configuration information related to a search space from a base station. , receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station, and transmitting the physical sidelink channel to a second terminal based on the DCI.

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space. The setting information includes information on an SL carrier associated with the search space. Based on that the search space is related to one or more SL carriers, the DCI may include information on the SL carrier related to the scheduling.

Monitoring of the PDCCH may be omitted for a predefined SL carrier among the one or more SL carriers.

The predefined SL carrier may be determined based on a value of a carrier indicator field among the one or more SL carriers.

A value of a carrier indicator field of the predefined SL carrier may be greater than 0.

Omission of monitoring of the PDCCH may be performed based on UE capability.

The terminal performance is related to at least one of i) the maximum number of PDCCH candidates related to monitoring of the PDCCH and / or ii) the maximum number of control channel elements (CCEs) related to monitoring of the PDCCH It can be.

The payload of the DCI may include padding added based on a predefined DCI format size.

The predefined DCI format size may be based on the largest value among DCI format sizes related to the one or more SL carriers.

The padding may be added based on the fact that the number of DCI format sizes for the serving cell related to the DCI is greater than a preset number. The number of DCI format sizes based on the preset number is 4, and among the 4 DCI format sizes, the number of DCI format sizes related to C-RNTI (Cell-Radio Network Temporary Identifier) may be 3.

The configuration information may include information on SL carriers for each search space related to DCI format 3_0 or DCI format 3_1.

The information on the SL carrier for each search space may include i) a value of a carrier indicator field and/or ii) a value for resource mapping of a PDCCH candidate related to the DCI.

The information on the SL carrier related to the scheduling may be based on i) a carrier indicator field and/or ii) a field for indicating a resource pool.

In a wireless communication system according to another embodiment of the present specification, a first terminal operating for scheduling of a physical sidelink channel includes one or more transceivers, one or more processors controlling the one or more transceivers, and 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 receiving configuration information related to a search space from a base station, receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station, and a second terminal. and transmitting the physical sidelink channel based on the DCI.

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space. The setting information includes information on an SL carrier related to the search space. Based on that the search space is related to one or more SL carriers, the DCI may include information on the SL carrier related to the scheduling.

In a wireless communication system according to another embodiment of the present specification, an apparatus for controlling a first terminal to operate for scheduling of a physical sidelink channel is operable with one or more processors and the one or more processors. It contains one or more memories that are connected.

One or more non-transitory computer readable media according to another embodiment of the present specification stores one or more instructions.

The one or more instructions, upon being executed by the one or more processors, perform operations.

The above operations include receiving configuration information related to a search space from a base station, receiving downlink control information (DCI) related to scheduling of a physical sidelink channel from a base station, and transmitting to a second terminal. Transmitting the physical sidelink channel based on the DCI.

A method performed by a base station for scheduling of a physical sidelink channel in a wireless communication system according to another embodiment of the present specification includes transmitting configuration information related to a search space to a first terminal. and transmitting downlink control information (DCI) related to scheduling of the physical sidelink channel to the first terminal.

Reception of the DCI by the first terminal is performed based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space. The setting information includes information on an SL carrier associated with the search space. Based on that the search space is related to one or more SL carriers, the DCI may include information on the SL carrier related to the scheduling.

In a wireless communication system according to another embodiment of the present specification, a base station operating for scheduling of a physical sidelink channel 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 operations include transmitting configuration information related to a search space to a first terminal and transmitting downlink control information (DCI) related to scheduling of the physical sidelink channel to the first terminal. Include steps.

Reception of the DCI by the first terminal is performed based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space. The setting information includes information on an SL carrier related to the search space. Based on that the search space is related to one or more SL carriers, the DCI may include information on the SL carrier related to the scheduling.

According to an embodiment of the present specification, when setting a search space, information on an SL carrier related to the search space is also set, and when the search space is associated with one or more SL carriers, the DCI includes information on the SL carrier.

Accordingly, a UE receiving scheduling information (DCI) based on one or more SL carriers can identify an SL carrier to be scheduled. Also, reliability of SL mode 1 scheduling operation based on one or more SL carriers can be improved.

According to an embodiment of the present specification, monitoring of a PDCCH associated with a predefined SL carrier is omitted. The omission may be performed based on restrictions related to BD/CCE. Accordingly, even when the number of SL carriers and the number of DL carriers are different from each other, monitoring of the SL mode 1 related PDCCH can be normally performed. In addition, since the omission of PDCCH monitoring is performed in a range (ie, SL carrier) that is more subdivided than the search space (SS), the efficiency of PDCCH monitoring operation can be improved.

The effects obtainable in the present specification are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

The accompanying drawings, which are included as part of the detailed description to aid understanding of the present invention, provide examples of the present invention and describe technical features of the present invention together with the detailed description.

1 shows the structure of an NR system according to an embodiment of the present specification.

2 shows the structure of a radio frame of NR according to an embodiment of the present specification.

3 shows a slot structure of an NR frame according to an embodiment of the present specification.

4 shows a terminal performing V2X or SL communication according to an embodiment of the present specification.

5 shows a resource unit for V2X or SL communication according to an embodiment of the present specification.

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.

7 shows three cast types according to an embodiment of the present specification.

8 shows a plurality of BWPs according to an embodiment of the present specification.

9 shows BWP according to an embodiment of the present specification.

10 is a flowchart for explaining a method performed by a first terminal for scheduling of a physical sidelink channel in a wireless communication system according to an embodiment of the present specification.

11 is a flowchart for explaining a method performed by a base station for scheduling of a physical sidelink channel in a wireless communication system according to another embodiment of the present specification.

12 shows a communication system 1, according to an embodiment of the present specification.

13 shows a wireless device according to an embodiment of the present specification.

14 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present specification.

15 illustrates a wireless device according to an embodiment of the present specification.

16 illustrates a portable device according to an embodiment of the present specification.

17 illustrates a vehicle or autonomous vehicle according to an embodiment of the present specification.

In various embodiments of the present specification, "/" and "," should be interpreted as indicating "and/or". For example, "A/B" can mean "A and/or B". Furthermore, "A, B" may mean "A and/or B". Furthermore, "A/B/C" may mean "at least one of A, B and/or C". Furthermore, "A, B, C" may mean "at least one of A, B and/or C".

In various embodiments of this specification, “or” should be construed as indicating “and/or”. For example, "A or B" can include "only A", "only B", and/or "both A and B". In other words, "or" should be construed to indicate "in addition or alternatively."

The following technologies include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and the like. It can be used in various wireless communication systems. 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). 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.

For clarity of description, LTE-A or 5G NR is mainly described, but the technical idea according to an embodiment of the present specification is not limited thereto.

The layers of the Radio Interface Protocol between the terminal and the network are based on the lower 3 layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems, It can be divided into L2 (second layer) and L3 (third layer). Among them, the physical layer belonging to the first layer provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in the third layer provides radio resources between the terminal and the network. plays a role in controlling To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

The MAC layer provides a service to a radio link control (RLC) layer, which is an upper layer, through a logical channel. The MAC layer provides a mapping function from multiple logical channels to multiple transport channels. In addition, the MAC layer provides a logical channel multiplexing function by mapping a plurality of logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.

The RLC layer performs concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). In order to guarantee various Quality of Service (QoS) required by the radio bearer (RB), the RLC layer has transparent mode (TM), unacknowledged mode (UM) and acknowledged mode , AM) provides three operation modes. AM RLC provides error correction through automatic repeat request (ARQ).

The Radio Resource Control (RRC) layer is defined only in the control plane. The RRC layer is responsible for control of logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers. RB means a logical path provided by the first layer (physical layer or PHY layer) and the second layer (MAC layer, RLC layer, Packet Data Convergence Protocol (PDCP) layer) for data transfer between the UE and the network.

The functions of the PDCP layer in the user plane include delivery of user data, header compression and ciphering. The functions of the PDCP layer in the control plane include delivery of control plane data and encryption/integrity protection.

Establishing an RB means a process of defining characteristics of a radio protocol layer and a channel and setting specific parameters and operation methods to provide a specific service. RBs can be further divided into two types: Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB). The SRB is used as a path for transmitting RRC messages in the control plane, and the DRB is used as a path for transmitting user data in the user plane.

When an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC_CONNECTED state, otherwise it is in the RRC_IDLE state. In the case of NR, the RRC_INACTIVE state is additionally defined, and the UE in the RRC_INACTIVE state can release the connection with the base station while maintaining the connection with the core network.

A downlink transmission channel for transmitting data from a network to a terminal includes a broadcast channel (BCH) for transmitting system information and a downlink shared channel (SCH) for transmitting user traffic or control messages. Traffic or control messages of a downlink multicast or broadcast service may be transmitted through a downlink SCH or may be transmitted through a separate downlink multicast channel (MCH). Meanwhile, an uplink transmission channel for transmitting data from a terminal to a network includes a random access channel (RACH) for transmitting an initial control message and an uplink shared channel (SCH) for transmitting user traffic or control messages.

Logical channels located above transport channels and mapped to transport channels include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), MTCH (Multicast Traffic Channel) Channel), etc.

A physical channel is composed of several OFDM symbols in the time domain and several sub-carriers in the frequency domain. One sub-frame is composed of a plurality of OFDM symbols in the time domain. A resource block is a resource allocation unit and is composed of a plurality of OFDM symbols and a plurality of sub-carriers. In addition, each subframe may use specific subcarriers of specific OFDM symbols (eg, a first OFDM symbol) of the corresponding subframe for a Physical Downlink Control Channel (PDCCH), that is, an L1/L2 control channel. TTI (Transmission Time Interval) is a unit time of subframe transmission.

Referring to FIG. 1, a Next Generation-Radio Access Network (NG-RAN) may include a next generation-Node B (gNB) and/or an 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. More specifically, an access and mobility management function (AMF) is connected through an NG-C interface, and a user plane function (UPF) is connected through an NG-U interface.

Referring to FIG. 2, 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). Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

When a normal CP is used, each slot may include 14 symbols. When an extended CP is used, each slot may include 12 symbols. Here, 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).

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.

In the NR system, OFDM (A) numerology (eg, SCS, CP length, etc.) may be set differently among a plurality of cells merged into one UE. Accordingly, (absolute time) intervals of time resources (e.g., subframes, slots, or TTIs) (for convenience, collectively referred to as TU (Time Unit)) composed of the same number of symbols can be set differently between merged cells.

In NR, 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. Among the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range" and FR2 may mean "above 6 GHz range" and may be called millimeter wave (mmW).

As described above, the number of frequency ranges of the NR system can be changed. For example, 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).

Referring to FIG. 3, 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.

Meanwhile, 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. In various embodiments of the present specification, the L1 layer may mean a physical layer. Also, for example, the L2 layer may mean at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Also, for example, the L3 layer may mean an RRC layer.

Referring to FIG. 4, the term terminal in V2X or SL communication may mainly mean a user's terminal. However, when network equipment such as a base station transmits and receives signals according to a communication method between terminals, the base station may also be regarded as a kind of terminal. For example, terminal 1 may be the first device 100 and terminal 2 may be the second device 200 .

For example, 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. For example, 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.

Here, when the terminal 1 is within the connection range of the base station, the base station may inform the terminal 1 of the resource pool. On the other hand, when terminal 1 is outside the connection range of the base station, another terminal may inform terminal 1 of a resource pool, or terminal 1 may use a previously set resource pool.

In general, 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.

Referring to FIG. 5 , 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.

As shown in FIG. 5, one resource unit (eg, Unit #0) may appear periodically and repeatedly. Alternatively, in order to obtain a diversity effect in a time or frequency dimension, an index of a physical resource unit to which one logical resource unit is mapped may change according to a predetermined pattern over time. In the structure of such a resource unit, 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.

(1) Scheduling Assignment (SA) is the location of the resource used by the transmitting terminal for transmission of the SL data channel, MCS (Modulation and Coding Scheme) or MIMO (Multiple Input Multiple Output) required for demodulation of other data channels ) may be a signal including information such as a transmission method and TA (Timing Advance). SA can also be multiplexed and transmitted together with SL data on the same resource unit. In this case, 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.

(2) SL data channel (Physical Sidelink Shared Channel, PSSCH) 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. In other words, 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. For example, the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.

(3) 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.

Even when the contents of the SL signals described above are the same, different 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 in SL

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. In various embodiments of the present specification, the transmission mode may be referred to as a mode or a resource allocation mode. Hereinafter, for convenience of description, a transmission mode in LTE may be referred to as an LTE transmission mode, and a transmission mode in NR may be referred to as an NR resource allocation mode.

For example, (a) of FIG. 6 shows a terminal operation related to LTE transmission mode 1 or LTE transmission mode 3. Or, for example, (a) of FIG. 6 shows UE operation related to NR resource allocation mode 1. For example, LTE transmission mode 1 may be applied to general SL communication, and LTE transmission mode 3 may be applied to V2X communication.

For example, (b) of FIG. 6 shows a terminal operation related to LTE transmission mode 2 or LTE transmission mode 4. Or, for example, (b) of FIG. 6 shows UE operation related to NR resource allocation mode 2.

Referring to (a) of FIG. 6, in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, the base station may perform resource scheduling to terminal 1 through PDCCH (more specifically, downlink control information (DCI)), and terminal 1 may perform V2X or SL communication with terminal 2 according to the resource scheduling there is. For example, device 1 may transmit sidelink control information (SCI) to device 2 through physical sidelink control channel (PSCCH), and then transmit data based on the SCI to device 2 through physical sidelink shared channel (PSSCH). there is.

For example, in NR resource allocation mode 1, a UE may be provided or allocated resources for one or more SL transmissions of one transport block (TB) from a base station through a dynamic grant. For example, the base station may provide resources for transmission of the PSCCH and/or PSSCH to the terminal using a dynamic grant. For example, the transmitting terminal may report SL HARQ (Hybrid Automatic Repeat Request) feedback received from the receiving terminal to the base station. In this case, PUCCH resources and timing for reporting SL HARQ feedback to the base station may be determined based on an indication in the PDCCH for the base station to allocate resources for SL transmission.

For example, DCI may indicate a slot offset between DCI reception and the first SL transmission scheduled by DCI. For example, the minimum gap between the DCI scheduling the SL transmission resource and the first scheduled SL transmission resource may not be smaller than the processing time of the corresponding UE.

For example, in NR resource allocation mode 1, a UE may be periodically provided or allocated a resource set from a base station for a plurality of SL transmissions through a configured grant. For example, the grant to be configured may include configured grant type 1 or configured grant type 2. For example, the terminal may determine a TB to transmit in each occurrence indicated by a given configured grant.

For example, the base station may allocate SL resources to the terminal on the same carrier, and may allocate SL resources to the terminal on different carriers.

For example, the NR base station can control LTE-based SL communication. For example, the NR base station may transmit NR DCI to the terminal to schedule LTE SL resources. In this case, for example, a new RNTI for scrambling the NR DCI may be defined. For example, the terminal may include an NR SL module and an LTE SL module.

For example, after the terminal including the NR SL module and the LTE SL module receives the NR SL DCI from the gNB, the NR SL module may convert the NR SL DCI to LTE DCI type 5A, and the NR SL module may convert the NR SL DCI to X ms LTE DCI type 5A may be delivered to the LTE SL module in units. For example, after the LTE SL module receives LTE DCI format 5A from the NR SL module, the LTE SL module may apply activation and/or release to the first LTE subframe after Z ms. For example, the X may be dynamically displayed using a DCI field. For example, the minimum value of X may be different according to UE capability. For example, a terminal may report a single value according to terminal capabilities. For example, the X may be a positive number.

Referring to (b) of FIG. 6, in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, 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. For example, the set SL resource or the preset SL resource may be a resource pool. For example, the terminal may autonomously select or schedule resources for SL transmission. For example, the terminal may perform SL communication by selecting a resource by itself within a configured resource pool. For example, the terminal may select a resource by itself within a selection window by performing a sensing and resource (re)selection procedure. For example, the sensing may be performed in units of subchannels. In addition, terminal 1, which has selected a resource within the resource pool, transmits SCI to terminal 2 through PSCCH, and then transmits data based on the SCI to terminal 2 through PSSCH.

A re-evaluation operation may be performed for the resource (re-)selection. Immediately before performing transmission on the reserved resource, the terminal re-evaluates the selectable resource set in order to determine whether or not the transmission intended by the terminal is still appropriate. Based on the sensing result, the re-evaluation may be performed in a slot based on a preset value T3. For example, the re-evaluation operation may be performed in a slot (eg, m-T3) prior to slot m in which the SCI indicating the reserved resource(s) is first signaled.

The preset value T3 may be related to pre-emption and/or re-evaluation of SL resources. Specifically, the terminal may perform operations related to pre-emption and/or re-evaluation based on Table 5 below.

The preset value T3 is a processing time set for resource selection of the terminal (eg:

) can be set to the same value as Table 6 below shows the subcarrier spacing setting of the sidelink bandwidth (SL BWP) (

) Illustrates the processing time determined based on (processing time). For example, the processing time (

) may be set to determine the starting point (T1) of the resource selection window.

For example, a UE can help select SL resources for other UEs. For example, in NR resource allocation mode 2, the UE may receive a configured grant for SL transmission. For example, in NR resource allocation mode 2, a UE may schedule SL transmission of another UE. For example, in NR resource allocation mode 2, the terminal may reserve SL resources for blind retransmission.

For example, in NR resource allocation mode 2, UE 1 may indicate the priority of SL transmission to UE 2 using SCI. For example, the second terminal may decode the SCI, and the second terminal may perform sensing and/or resource (re)selection based on the priority. For example, the resource (re)selection procedure includes identifying a candidate resource in a resource selection window by a second terminal and selecting a resource for (re)transmission from among the identified candidate resources. can do. For example, the resource selection window may be a time interval in which the terminal selects a resource for SL transmission. For example, after the second terminal triggers resource (re)selection, the resource selection window may start at T1 ≥ 0, and the resource selection window is determined by the remaining packet delay budget of the second terminal. may be limited. The T1 is the processing time set for resource selection (e.g., Table 6 above).

) can be determined as a value less than or equal to. For example, when the slot in which the resource (re)selection is triggered is n, the resource selection window may be determined as a time interval from n+T1 to n+T2. The T2 may indicate a number of slots that is less than or equal to the number of slots corresponding to the remaining packet delay budget.

For example, in the step of identifying a candidate resource in the resource selection window by the second terminal, a specific resource is indicated by the SCI received by the second terminal from the first terminal, and the L1 SL RSRP measurement value for the specific resource is If the SL RSRP threshold is exceeded, the second terminal may not determine the specific resource as a candidate resource. For example, the SL RSRP threshold may be determined based on the priority of SL transmission indicated by the SCI received by the second terminal from the first terminal and the priority of the SL transmission on a resource selected by the second terminal.

For example, the L1 SL RSRP may be measured based on SL Demodulation Reference Signal (DMRS). For example, one or more PSSCH DMRS patterns may be set or previously set in the time domain for each resource pool. For example, PDSCH DMRS configuration type 1 and/or type 2 may be identical to or similar to the frequency domain pattern of PSSCH DMRS. For example, the exact DMRS pattern may be indicated by SCI. For example, in NR resource allocation mode 2, the transmitting terminal may select a specific DMRS pattern from DMRS patterns set or previously set for a resource pool.

For example, in NR resource allocation mode 2, based on the sensing and resource (re)selection procedures, the transmitting terminal may perform initial transmission of a TB (Transport Block) without reservation. For example, based on the sensing and resource (re)selection procedure, the transmitting terminal may reserve SL resources for initial transmission of the second TB using the SCI associated with the first TB.

For example, in NR resource allocation mode 2, the terminal may reserve resources for feedback-based PSSCH retransmission through signaling related to previous transmission of the same transport block (TB). For example, the maximum number of SL resources reserved by one transmission including the current transmission may be 2, 3 or 4. For example, the maximum number of SL resources may be the same regardless of whether HARQ feedback is enabled. For example, the maximum number of HARQ (re)transmissions for one TB may be limited by setting or presetting. For example, the maximum number of HARQ (re)transmissions may be up to 32. For example, if there is no setting or presetting, the maximum number of HARQ (re)transmissions may not be specified. For example, the setting or presetting may be for a transmission terminal. For example, in NR resource allocation mode 2, HARQ feedback for releasing resources not used by the UE may be supported.

For example, in NR resource allocation mode 2, a UE may use SCI to indicate one or more subchannels and/or slots used by the UE to other UEs. For example, a UE may indicate to another UE one or more subchannels and/or slots reserved by the UE for PSSCH (re)transmission using SCI. For example, a minimum allocation unit of SL resources may be a slot. For example, the size of a subchannel may be set for a UE or preset.

Sidelink Control Information (SCI)

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. For example, the UE may know the start symbol of the PSCCH and/or the number of symbols of the PSCCH before decoding the PSCCH. For example, SCI may include SL scheduling information. For example, a UE may transmit at least one SCI to another UE in order to schedule a PSSCH. For example, one or more SCI formats may be defined.

For example, 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.

For example, 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. For example, when 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 . , and the SCI including the second SCI composition field group may be referred to as a second SCI or a 2 ^nd SCI. For example, the transmitting terminal may transmit the first SCI to the receiving terminal through the PSCCH. For example, the transmitting terminal may transmit the second SCI to the receiving terminal on the PSCCH and/or the PSSCH. For example, 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. For example, two consecutive SCIs may be applied for different transmissions (eg, unicast, broadcast, or groupcast).

For example, the transmitting terminal may transmit some or all of the following information to the receiving terminal through SCI. Here, for example, the transmitting terminal may transmit some or all of the following information to the receiving terminal through the first SCI and/or the second SCI.

- PSSCH and / or PSCCH related resource allocation information, eg, time / frequency resource location / number, resource reservation information (eg, period), and / or

- SL CSI report request indicator or SL (L1) RSRP (and / or SL (L1) RSRQ and / or SL (L1) RSSI) report request indicator, and / or

- SL CSI transmission indicator (on PSSCH) (or SL (L1) RSRP (and/or SL (L1) RSRQ and/or SL (L1) RSSI) information transmission indicator), and/or

- MCS information, and/or

- transmit power information, and/or

- L1 destination ID information and/or L1 source ID information, and/or

-SL HARQ process ID information, and/or

- New Data Indicator (NDI) information, and/or

- RV (Redundancy Version) information, and/or

- QoS information (related to transport traffic/packets), e.g., priority information, and/or

- Information on the number of SL CSI-RS transmission indicators or (transmitted) SL CSI-RS antenna ports

-Location information of a transmitting terminal or location (or distance area) information of a target receiving terminal (for which SL HARQ feedback is requested), and/or

- Reference signal (eg, DMRS, etc.) information related to decoding and / or channel estimation of data transmitted through PSSCH, eg, information related to the pattern of (time-frequency) mapping resources of DMRS, rank ) information, antenna port index information;

For example, the first SCI may include information related to channel sensing. For example, the receiving terminal may decode the second SCI using the PSSCH DMRS. A polar code used for PDCCH may be applied to the second SCI. For example, in a resource pool, the payload size of the first SCI may be the same for unicast, groupcast and broadcast. After decoding the first SCI, the receiving terminal does not need to perform blind decoding of the second SCI. For example, the first SCI may include scheduling information of the second SCI.

Meanwhile, in various embodiments of the present specification, since the transmitting terminal may transmit at least one of the SCI, the first SCI, and/or the second SCI to the receiving terminal through the PSCCH, 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.

Meanwhile, FIG. 7 shows three cast types according to an embodiment of the present specification.

Specifically, FIG. 7(a) shows broadcast type SL communication, FIG. 7(b) shows unicast type SL communication, and FIG. 7(c) shows groupcast type SL communication. . In the case of unicast type SL communication, a terminal may perform one-to-one communication with another terminal. In the case of 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. In various embodiments of the present specification, SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, and the like.

Hereinafter, a Cooperative Awareness Message (CAM) and a Decentralized Environmental Notification Message (DENM) will be described.

In vehicle-to-vehicle communication, a CAM of a periodic message type, a DENM of an event triggered message type, and the like may be transmitted. CAM can include vehicle dynamic state information such as direction and speed, vehicle static data such as dimensions, and basic vehicle information such as exterior lighting conditions and route details. The size of a CAM may be 50-300 bytes. CAM is broadcast, and the latency must be less than 100 ms. DENM may be a message generated in an unexpected situation such as vehicle breakdown or accident. The size of DENM can be smaller than 3000 bytes, and all vehicles within transmission range can receive the message. At this time, DENM may have a higher priority than CAM.

Hereinafter, carrier reselection will be described.

In V2X or SL communication, a UE may perform carrier reselection based on a Channel Busy Ratio (CBR) of configured carriers and/or a Prose Per-Packet Priority (PPPP) of a V2X message to be transmitted. For example, carrier reselection may be performed by the MAC layer of the UE. In various embodiments of the present specification, PPPP (ProSe Per Packet Priority) may be replaced with PPPR (ProSe Per Packet Reliability), and PPPR may be replaced with PPPP. For example, a smaller PPPP value may mean a higher priority, and a larger PPPP value may mean a lower priority. For example, a smaller PPPR value may mean higher reliability, and a larger PPPR value may mean lower reliability. For example, a PPPP value associated with a service, packet, or message related to a high priority may be smaller than a PPPP value related to a service, packet, or message related to a low priority. For example, a PPPR value related to a service, packet, or message related to high reliability may be smaller than a PPPR value related to a service, packet, or message related to low reliability.

The CBR may refer to the portion of sub-channels in a resource pool in which a sidelink-received signal strength indicator (S-RSSI) measured by the UE exceeds a preset threshold. A PPPP associated with each logical channel may exist, and the setting of the PPPP value should reflect the latency required for both the terminal and the base station. Upon carrier reselection, the terminal may select one or more carriers among the candidate carriers in an increasing order from the lowest CBR.

Hereinafter, physical layer processing will be described.

According to an embodiment of the present specification, a data unit may be subject to physical layer processing at a transmitting side before being transmitted through an air interface. According to an embodiment of the present specification, a radio signal carrying a data unit may be subject to physical layer processing at a receiving side.

Table 7 may indicate a mapping relationship between uplink transport channels and physical channels, and Table 8 may indicate a mapping relationship between uplink control channel information and physical channels.

Table 9 may indicate a mapping relationship between a downlink transport channel and a physical channel, and Table 10 may indicate a mapping relationship between downlink control channel information and a physical channel.

Table 11 may indicate a mapping relationship between SL transport channels and physical channels, and Table 12 may indicate a mapping relationship between SL control channel information and physical channels.

In the physical layer processing at the transmit/receive side described above, time and frequency domain resources (e.g., OFDM symbols, subcarriers, carrier frequencies) related to subcarrier mapping, OFDM modulation, and frequency up/down conversion are resource allocation (e.g. For example, uplink grant, downlink allocation).

Bandwidth Part and Resource Pool

Hereinafter, a bandwidth part (BWP) and a resource pool will be described.

When BA (Bandwidth Adaptation) is used, 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. For example, the network/base station may notify the terminal of bandwidth adjustment. For example, the terminal may receive information/configuration for bandwidth adjustment from the network/base station. In this case, the terminal may perform bandwidth adjustment based on the received information/configuration. For example, the bandwidth adjustment may include reducing/expanding the bandwidth, changing the location of the bandwidth, or changing the subcarrier spacing of the bandwidth.

For example, bandwidth may be reduced during periods of low activity to save power. For example, the location of the bandwidth may move in the frequency domain. For example, the location of the bandwidth can be moved in the frequency domain to increase scheduling flexibility. For example, subcarrier spacing of the bandwidth may be changed. For example, 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.

Referring to FIG. 8, 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, and BWP3 having a bandwidth of 20 MHz and subcarrier spacing of 60 kHz can be set. .

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.

Referring to FIG. 9, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other end. And, 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 ). For example, 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. For example, the offset may be the PRB interval between point A and the lowest subcarrier in a given numerology. For example, 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. For example, a transmitting terminal can transmit an SL channel or SL signal on a specific BWP, and a receiving terminal can receive an SL channel or SL signal on the specific BWP. In a licensed carrier, SL BWP may be defined separately from Uu BWP, and SL BWP may have separate configuration signaling from Uu BWP. For example, 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.

In this specification, 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. For example, "A may be configured" may include "(pre)setting/defining or notifying A of the base station or network for the terminal". Alternatively, the wording “set or define” may be interpreted as being previously set or defined by the system. For example, “A may be set” may include “A is set/defined in advance by the system”.

Meanwhile, in this specification, SL MODE 1 is a resource allocation method or communication method in which a base station directly schedules sidelink transmission (SL TX) resources of a terminal through predefined signaling (eg, DCI). Can mean there is. Also, for example, SL MODE 2 may mean a resource allocation method or communication method in which a terminal independently selects SL TX resources from a base station or a network or within a previously set resource pool.

The base station may allocate resources used for transmission and reception of SL channels/signals (hereinafter referred to as SL resources) to the terminal. For example, the base station may transmit information related to the resource to the terminal. In this specification, 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.

Blind Decoding

Hereinafter, matters related to blind decoding (BD) to which the method proposed in this specification can be applied will be described.

The PDCCH is transmitted on an aggregation of one or more Control Channel Elements (CCEs). CCE is a logical allocation unit used to provide a PDCCH of a predetermined coding rate according to the state of a radio channel. A CCE corresponds to a plurality of resource element groups (REGs).

Table 13 below illustrates the number of CCEs for each aggregation level supported for PDCCH.

Table 14 below illustrates the CCE aggregation level for CSS sets configured by searchSpaceSIB1 and the number of PDCCH candidates for each CCE aggregation level.

For example, when one PDCCH is transmitted in 4 CCEs (CCE aggregation level is 4), the number of PDCCH candidates is 4.

The base station determines the PDCCH format according to the DCI to be transmitted to the terminal, and adds a cyclic redundancy check (CRC) to the control information. The CRC is masked with a unique identifier (referred to as radio network temporary identifier (RNTI)) according to the owner or usage of the PDCCH. If the PDCCH is for a specific terminal, the unique identifier (eg, C-RNTI (cell-RNTI)) of the corresponding terminal is masked to the CRC. As another example, if the PDCCH is for a paging message, a paging indication identifier (eg, P-RNTI (paging-RNTI)) is masked in the CRC. If the PDCCH is related to system information (eg, system information block (SIB)), the system information identifier (eg, system information RNTI (SI-RNTI)) is masked to the CRC. A random access-RNTI (RA-RNTI) is masked in the CRC to indicate a random access response, which is a response to transmission of the random access preamble of the UE.

A limited set of CCE locations where the PDCCH can be located can be defined for each UE. A limited set of CCE locations where the UE can find its PDCCH may be referred to as a search space (Search Space, SS).

The UE searches for its own PDCCH by monitoring a set of PDCCH candidates within a subframe. Here, monitoring includes the UE attempting to decode PDCCH candidates according to each DCI format. This is called blind decoding (BD). Through BD, a UE simultaneously performs identification of a PDCCH transmitted to it and decoding of control information transmitted through the corresponding PDCCH. For example, when PDCCH is de-masked with C-RNTI, if there is no CRC error, the terminal detects its own PDCCH.

Monitoring of the PDCCH is performed based on UE capability. The UE performance related to PDCCH monitoring is defined by i) the maximum number of PDCCH candidates and ii) the maximum number of CCEs that the corresponding UE can monitor.

The UE performance may be applied/determined for each predefined unit (eg slot, slot group, span (symbols)) for the activated DL BWP of the serving cell. For example, the terminal is downlink cells (eg:

The maximum number of PDCCH candidates (eg, maximum number of PDCCH candidates) and the maximum number of CCEs (eg, maximum number of non-overlapped CCEs) per slot corresponding to downlink cells are determined as UE performance. .

Table 15 below illustrates the maximum number of PDCCH candidates.

Referring to Table 15, the maximum number of candidates of the PDCCH (

) is the numerology related to the subcarrier spacing (

) may be different. The maximum number of PDCCH candidates may be applied for each slot in the serving cell.

Table 16 below illustrates the maximum number of CCEs.

Referring to Table 16, the maximum number of CCEs (

) is the numerology related to the subcarrier spacing (

) may be different. The maximum number of CCEs may be applied for each slot in the serving cell.

For example, the UE may perform PDCCH monitoring as follows based on the maximum number of PDCCH candidates and the maximum number of CCEs.

The UE does not monitor more PDCCH candidates than the maximum number of PDCCH candidates for each slot (slot group or span (symbols)) in the active DL BWP(s) of the scheduling cell(s).

The UE does not monitor CCEs greater than the maximum number of CCEs per slot (slot group or span (symbols)) in the active DL BWP(s) of the scheduling cell(s).

The UE does not expect that search space sets (eg Common Search Space sets, CSS sets) in which the total number of PDCCH candidates and the total number of CCEs exceed the maximum number of PDCCH candidates and the maximum number of CCEs are configured. .

The UE may perform PDCCH monitoring for a plurality of SSs satisfying the maximum number of PDCCH candidates and the maximum number of CCEs. Specifically, the terminal monitors the PDCCH for set CSSs (sets), but for the UE-specific search space (USS), the range according to the terminal performance (range of candidate PDCCHs/number of CCEs) PDCCH monitoring can be performed within. For example, the UE may not perform PDCCH monitoring for the USS outside the range according to the UE performance.

Meanwhile, in the next system, the terminal may perform SL transmission and/or reception operations in a plurality of carriers. On the other hand, the SL transmission resource may be provided by the terminal from the base station, and the number of DL carriers or cells for receiving the DL signal by the terminal is less than or equal to the number of SL carriers or cells for SL transmission and / or reception. can In this case, the terminal may receive SL resource allocation information for a plurality of SL carriers from the base station through a specific DL carrier or cell.

In an embodiment of the present disclosure, when a terminal performs an SL Mode 1 operation (eg, an operation based on resource allocation mode 1 in (a) of FIG. 6), the terminal receives SL resource allocation information from the base station by DCI and/or We propose a method of receiving information through RRC signaling. Technical challenges related to the above embodiment are as follows. It may be necessary to organize the relationship between blind decoding (BD) and/or Control Channel Element (CCE) restrictions for PDCCH monitoring of the UE and the number of SL carriers to be scheduled. In addition, a method of efficiently managing a plurality of SL carriers of scheduling targets in a single DL carrier or serving cell may be required.

The BD/CCE restriction may mean the maximum number of PDCCH candidates and the maximum number of CCEs based on UE capability related to the PDCCH monitoring operation described above.

The terminal may receive configuration information related to the SL carrier from the base station. The configuration information may be received based on a DCI, MAC-CE or RRC message. The setting information may be transmitted based on a newly defined Information Element (IE). The configuration information may be transmitted based on a previously defined IE (eg, SEARCH SPACE-related configuration information). A detailed example will be described below.

For example, the terminal may receive configuration information about the SL carrier from the base station. The configuration information may include information on scheduling cells and/or information on SEARCH SPACE for each SL carrier. For example, the configuration information for the SL carrier may include information on a resource pool to be used when operating in Mode 1. For example, when receiving information on a scheduling cell for each SL carrier, the terminal may receive a CIF value and/or n_CI value to be used when scheduling the SL carrier from the base station. For example, information on the scheduling cell (eg, schedulingCellInfo) may be set to 'own' or 'other'. 1) When the information on the scheduling cell is set to own, the serving cell related to the corresponding SL carrier is the scheduling cell. In this case, the serving cell performs scheduling for the corresponding SL carrier. 2) When the information on the scheduling cell is set to other, the serving cell related to the corresponding SL carrier is a scheduled cell. In this case, the serving cell does not directly perform scheduling for the corresponding SL carrier, and the scheduling is performed by a serving cell configured as a scheduling cell.

For example, the terminal may receive configuration information related to SEARCH SPACE from the base station. The configuration information may include information on an SL carrier to be scheduled (eg, SL carrier configuration index / ID and / or frequency location information for the SL carrier and / or information about a resource pool within the SL carrier). there is.

For example, setting related to the SEARCH SPACE may include monitoring SL DCI (eg, DCI FORMAT 3_0 and/or 3_1). Specifically, the setting related to the SEARCH SPACE may include information indicating which DCI format is monitored. For example, SL carriers that can be scheduled for each SEARCH SPACE for monitoring a DCI for scheduling and/or configuring SL resources or groups thereof may be different. For example, the terminal may receive a CIF value and/or n_CI value to be used when scheduling an SL carrier to be scheduled for each SEARCH SPACE from the base station. In other words, the configuration information related to the SEARCH SPACE may include a CIF value and/or n_CI value to be used for scheduling of an SL carrier related to each SEARCH SPACE.

For example, when a plurality of SL carriers can be scheduled in SEARCH SPACE for SL DCI monitoring (ie, PDCCH monitoring for reception of SL DCI), the following operation/configuration may be considered. For example, the number of PDCCH candidates for each aggregation level (AL) may be the same regardless of (the number of) SL carriers. For example, the DCI format for SL and/or the number of PDCCH candidates for each AL (aggregation level) can be set by the base station to the terminal through RRC signaling for each SL carrier.

For example, whether a carrier indicator field (CIF) exists in the SL DCI may be set by the base station to the terminal through RRC signaling for a scheduling cell corresponding to the SL carrier. For example, presence or absence of CIF in DCI may be set for each DCI format (eg, a DCI format for Uu link and a format for SL). For example, whether a CIF exists in the SL DCI may be configured by the base station to the terminal for a SEARCH SPACE for monitoring the SL DCI. For example, the presence or absence of a CIF of the SL DCI and/or the size of the field may be different according to the SEARCH SPACE for the SL DCI. For example, in the case of an SL carrier sharing resources with a scheduling cell corresponding to a SEARCH SPACE, the CIF value and/or the n_CI value may be 0. For example, in the case of an SL carrier existing in an Intelligent Transportation System (ITS) band, the CIF value and/or the n_CI value may be 0. For example, when the index and/or ID for the SL carrier is the smallest or 0, the CIF value and/or n_CI value may be 0.

For example, a field indicating a resource pool in the SL DCI may be extended to indicate an SL carrier to be scheduled. A resource pool indicated by the SL DCI (eg, resource pool index field) may be associated with a specific SL carrier. For example, resource pools that can be indicated in the SL DCI may all correspond to the same SL carrier or may correspond to different SL carriers.

For example, SEARCH SPACEs may be classified according to SL carriers to be scheduled. In other words, SL carriers may be classified for each SEARCH SPACE. More specifically, if the SEARCH SPACE in which monitoring of the PDCCH is performed is changed, the SL carrier to be scheduled may also be changed. For example, the number of SL carriers that can be scheduled for each SEARCH SPACE may be limited to one at most. For example, SL DCIs transmitted in different SEARCH SPACEs may allocate and/or configure SL resources for different SL carriers.

For example, RNTI (Radio Network Temporary Indentifier) values for SL DCI may be different according to SL carriers to be scheduled. In this case, for example, the UE can identify scheduling SL carriers using the RNTI. For example, different CRC MASKINGs may be applied to CRCs for SL DCI according to SL carriers to be scheduled. For example, the CRC MASKING may use information about the SL carrier in addition to the RNTI.

For example, SL DCIs may have the same size for the same scheduling cell. For example, after configuring the required size for the SL DCI for each SL carrier to be scheduled for the same scheduling cell, all SL DCIs have the same size through PADDING (eg, through the addition of PADDING bits) based on the largest value. can be set to have. For example, the PADDING may be performed based on the entire requested size of the SL DCI and may be added to the LSB (Least Significant Bit) of the SL DCI. For example, the PADDING may be performed based on the requested size of each field of the SL DCI and may be added for each field of the SL DCI. For example, the total request size of the SL DCI for each SL carrier may be determined based on the largest request size among the total request sizes for each resource pool within the SL carrier.

For example, the size of the SL DCI for each SL carrier depending on whether the DCI format size budget of the scheduling cell is satisfied (eg, the total DCI format size for the cell is 4 and the DCI format size masked with C-RNTI is 3) may be different. The DCI format size budget is the number of sizes of DCI format(s) that can be monitored maximally by the UE when the UE monitors PDCCH candidates for each serving cell (or DCI format size used by one serving cell). The maximum number of) may mean. As an example, the UE expects to monitor PDCCH candidates for up to 4 DCI format sizes per serving cell (including up to 3 DCI format sizes with CRC scrambled by C-RNTI).

For example, in a situation where the DCI format size budget (of the scheduling cell) for the UE is satisfied, the size of the SL DCI for each SL carrier may be different for the same scheduling cell. In a situation where the DCI format size budget is not satisfied, the base station can equally match the size of SL DCIs for different SL carriers. That is, in a situation where the DCI format size budget of the scheduling cell for the UE is not satisfied, the base station can add the PADDING so that the size of the SL DCI for different SL carriers is the same.

Meanwhile, BD/CCE restrictions may be determined according to UE CAPABILITY. According to the BD/CCE restriction, the UE may omit PDCCH monitoring for some SEARCH SPACEs at a specific PDCCH monitoring time point. For example, UE CAPABILITY for BD/CCE restrictions may be set/defined separately for SL DCI monitoring. That is, the UE may transmit UE capability information for the BD/CCE restriction related to the SL DCI monitoring to the eNB.

For example, the BD/CCE restriction for SL DCI detection may be applied only to SEARCH SPACE for SL DCI. For example, the BD/CCE restriction for SL DCI detection may be applied at a PDCCH monitoring time point derived by SEARCH SPACE for SL DCI or a slot including the same. For example, the UE CAPABILITY for the BD/CCE restriction may be to keep the same for PDCCHs other than PDCCH for SL. Specifically, a BD/CCE restriction related to PDCCH monitoring for reception of SL DCI is not separately defined, and UE CAPABILITY related to a previously defined BD/CCE restriction may be utilized.

For example, at the PDCCH monitoring time point for the SL DCI, in order to satisfy the BD/CCE restriction, PDCCH monitoring for some SL carriers to be scheduled may be omitted in the SEARCH SPACE for the SL DCI. For example, the SL carrier corresponding to the PDCCH for which the monitoring is omitted may have a corresponding CIF value exceeding 0. Specifically, the UE may perform PDCCH monitoring only for an SL carrier having a CIF value of 0, and may omit PDCCH monitoring for an SL carrier having a CIF value greater than 0.

For example, the UE may omit PDCCH monitoring in units of a PDCCH candidate set corresponding to an SL carrier to be scheduled. In this case, for example, the UE may omit PDCCH monitoring from the PDCCH candidate group for SL carriers having a large CIF value. For example, the UE may omit PDCCH monitoring from the PDCCH candidate group corresponding to the smallest priority value or the largest priority value supported in the SL carrier.

In an embodiment of the present disclosure, an SL carrier may be limited to including a resource pool for SL Mode 1 operation (a method for allocating/setting SL resources from a base station). Specifically, an SL carrier may be based on one or more resource pools.

In an embodiment of the present disclosure, SL carriers may be limited to activated carriers excluding deactivated carriers. Specifically, the SL carrier may be based on an activated carrier.

In an embodiment of the present disclosure, an SL carrier may be a carrier configured for a UE regardless of activation. Specifically, the SL carrier may be based on a carrier configured in the terminal (activated carrier + deactivated carrier).

In an embodiment of the present disclosure, CIF may be used to indicate which SL carrier to be scheduled in DCI or which SL carrier each field of DCI corresponds to. In an embodiment of the present disclosure, the n_CI value may be used when mapping a PDCCH candidate used to transmit a DCI for scheduling an SL to a logical resource and/or a physical resource.

The proposed method can be applied to devices described below (eg, FIGS. 12 to 17). For example, referring to FIG. 13 , the processor 202 of the receiving terminal may set at least one BWP. In addition, the processor 202 of the receiving terminal 200 may control the transceiver 206 to receive a sidelink-related physical channel and/or a sidelink-related reference signal from the transmitting terminal 100 on at least one BWP.

As long as the above-described embodiments are not mutually exclusive, two or more embodiments may be combined and applied to the operation of the terminal/base station.

From an implementation point of view, operations of the terminal/base station (e.g., configuration and/or signaling related to the SL carrier) according to the above-described embodiments may be performed by the devices of FIGS. 12 to 17 (e.g., the

processors

102 and 202 of FIG. 13) )) can be processed by

In addition, operations of the terminal/base station (eg, setting and/or signaling related to SL carriers) according to the above-described embodiments are commands/programs (eg, 102 and 202 of FIG. 13) for driving at least one processor : It may be stored in a memory (eg, 104, 204 in FIG. 13) in the form of an instruction or executable code.

Hereinafter, the above-described embodiments will be described in detail with reference to FIG. 10 in terms of operation of the terminal. The methods described below are only classified for convenience of explanation, and it is of course possible that some components of one method may be substituted with some components of another method, or may be applied in combination with each other, unless mutually excluded.

Referring to FIG. 10, a method performed by a first terminal for scheduling a physical sidelink channel in a wireless communication system according to an embodiment of the present specification includes a setting information receiving step (S1010), a DCI receiving step (S1020), and A physical sidelink channel transmission step (S1030) may be included.

In S1010, the first terminal receives configuration information related to a search space from the base station. The first terminal may be terminal 1 operating based on NR resource allocation mode 1 in FIG. 6 (a). A second terminal to be described later may be terminal 2 operating based on NR resource allocation mode 1 in FIG. 6 (a).

According to an embodiment, the setting information may include information on an SL carrier related to the search space. This embodiment may be based on the above-described embodiment related to configuration information related to the SL carrier. The setting information related to the search space is an example of setting information related to the SL carrier. Configuration information related to the SL carrier may be based on previously defined configuration information (eg, SEARCH SPACE-related configuration information, PDCCH-config IE transmitted through RRC signaling) for configuration of a search space. Alternatively, the configuration information related to the SL carrier may be based on configuration information newly defined for the SL carrier.

For example, the setting information may include information for monitoring the SL DCI. Specifically, the configuration information may include information on SL carriers for each search space related to DCI format 3_0 or DCI format 3_1. The information on the SL carrier for each search space may include i) a value of a carrier indicator field and/or ii) a value for resource mapping of a PDCCH candidate related to the DCI (eg, n_CI value). .

According to the above-described S1010, an operation in which the first terminal (100/200 of FIGS. 12 to 17) receives setting information related to a search space from the base station (100/200 of FIGS. 12 to 17) is shown in FIG. 12 to 17 may be implemented. For example, referring to FIG. 13 , one or more processors 102 may include one or more transceivers 106 and/or one or more memories 104 to receive configuration information related to a search space from a base station 200. can control.

In S1020, the first terminal receives downlink control information (DCI) related to scheduling of the physical sidelink channel from the base station.

The DCI may be based on a DCI format for scheduling SL resources for sidelink communication. The DCI format may be based on DCI format 3_0 or DCI format 3_1. The DCI may be received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space.

According to an embodiment, based on the fact that the search space is associated with one or more SL carriers, the DCI may include information on an SL carrier related to the scheduling. This embodiment may be based on the above-described embodiment related to fields in the SL DCI. For example, the information on the SL carrier related to the scheduling may be based on i) a carrier indicator field and/or ii) a field for indicating a resource pool. A field for indicating the resource pool (eg, a resource pool index field) may indicate a resource pool associated with an SL carrier. Specifically, the field for indicating the resource pool may indicate a resource pool configured to be associated with/mapped to an SL carrier.

According to an embodiment, monitoring of the PDCCH may be omitted for a predefined SL carrier among the one or more SL carriers. This embodiment may be based on the embodiment related to the BD/CCE limitation described above.

The predefined SL carrier may be determined based on a value of a carrier indicator field among the one or more SL carriers. A value of a carrier indicator field of the predefined SL carrier may be greater than 0.

Omission of monitoring of the PDCCH may be performed based on UE capability. The terminal performance is related to at least one of i) the maximum number of PDCCH candidates related to monitoring of the PDCCH and / or ii) the maximum number of control channel elements (CCEs) related to monitoring of the PDCCH It can be.

According to an embodiment, the payload of the DCI may include padding added based on a predefined DCI format size. The padding may mean padding bits set to a certain value. This embodiment may be based on the above-described embodiment related to the size of the SL DCI. The predefined DCI format size may be based on the largest value among DCI format sizes related to the one or more SL carriers. The padding may be added based on the fact that the number of DCI format sizes for the serving cell related to the DCI is greater than a preset number. The number of DCI format sizes based on the preset number is 4, and among the 4 DCI format sizes, the number of DCI format sizes related to C-RNTI (Cell-Radio Network Temporary Identifier) may be 3.

According to the above-described S1020, the first terminal (100/200 of FIGS. 12 to 17) receives downlink control information related to scheduling of the physical sidelink channel from the base station (100/200 of FIGS. 12 to 17). Information, DCI) may be implemented by the devices of FIGS. 12 to 17. For example, referring to FIG. 13 , one or more processors 102 may be configured to use one or more transceivers 106 to receive downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station 200. ) and/or control one or more memories 104 .

In S1030, UE 1 transmits the physical sidelink channel to UE 2 based on the DCI. The physical sidelink channel may refer to a channel transmitted based on NR resource allocation mode 1. For example, the physical sidelink channel may include a physical sidelink control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH).

In accordance with the above-described S1030, the first terminal (100/200 of FIGS. 12 to 17) transmits the physical sidelink channel to the second terminal (100/200 of FIGS. 12 to 17) based on the DCI. may be implemented by the devices of FIGS. 12 to 17 . For example, referring to FIG. 13, one or more processors 102 may transmit the physical sidelink channel to the second terminal 200 based on the DCI by using one or more transceivers 106 and/or one or more memories ( 104) can be controlled.

Hereinafter, the above-described embodiments will be described in detail with reference to FIG. 11 in terms of operation of a base station. The methods described below are only classified for convenience of explanation, and it is of course possible that some components of one method may be substituted with some components of another method, or may be applied in combination with each other, unless mutually excluded.

Referring to FIG. 11, a method performed by a base station for scheduling a physical sidelink channel in a wireless communication system according to another embodiment of the present specification may include a setting information transmission step (S1110) and a DCI transmission step (S1120). can

In S1110, the base station transmits configuration information related to a search space to the first terminal. The first terminal may be terminal 1 operating based on NR resource allocation mode 1 in FIG. 6 (a). A second terminal to be described later may be terminal 2 operating based on NR resource allocation mode 1 in FIG. 6 (a).

According to the above-described S1110, an operation in which the base station (100/200 of FIGS. 12 to 17) transmits setting information related to a search space to the first terminal (100/200 of FIGS. 12 to 17) is shown in FIG. 12 to 17 may be implemented. For example, referring to FIG. 13 , one or more processors 202 may include one or more transceivers 206 and/or one or more memories to transmit configuration information related to a search space to the first terminal 100 ( 204) can be controlled.

In S1120, the base station transmits downlink control information (DCI) related to scheduling of the physical sidelink channel to the first terminal.

The DCI may be based on a DCI format for scheduling SL resources for sidelink communication. The DCI format may be based on DCI format 3_0 or DCI format 3_1. Reception of the DCI by the first terminal is performed based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space.

According to an embodiment, based on that the search space is associated with one or more SL carriers, the DCI may include information on an SL carrier related to the scheduling. This embodiment may be based on the above-described embodiment related to fields in the SL DCI. For example, the information on the SL carrier related to scheduling may be based on i) a carrier indicator field and/or ii) a field for indicating a resource pool. A field for indicating the resource pool (eg, resource pool index field) may indicate a resource pool associated with an SL carrier. Specifically, the field for indicating the resource pool may indicate a resource pool configured to be associated with/mapped to an SL carrier.

According to the above-described S1120, the base station (100/200 of FIGS. 12 to 17) sends downlink control information related to scheduling of the physical sidelink channel to the first terminal (100/200 of FIGS. 12 to 17). Information, DCI) may be implemented by the devices of FIGS. 12 to 17. For example, referring to FIG. 13 , one or more processors 202 transmit downlink control information (DCI) related to scheduling of the physical sidelink channel to a first terminal 100 through one or more transceivers. 206 and/or one or more memories 204.

The first terminal transmits the physical sidelink channel to the second terminal based on the DCI. The physical sidelink channel may refer to a channel transmitted based on NR resource allocation mode 1. For example, the physical sidelink channel may include a physical sidelink control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH).

Hereinafter, a device to which various embodiments of the present specification can be applied will be described.

Although not limited thereto, various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document can be applied to various fields requiring wireless communication / connection (eg, 5G) between devices.

Hereinafter, it will be exemplified in more detail with reference to the drawings. In the following drawings/description, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks unless otherwise specified.

Referring to FIG. 12 , a communication system 1 to which various embodiments of the present specification are applied includes a wireless device, a base station, and a network. Here, 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. Although not limited thereto, 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. For example, 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. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone). 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. For example, a base station and a network may also be implemented as a wireless device, and a specific wireless device 200a may operate as a base station/network node to other wireless devices.

The wireless devices 100a to 100f may be connected to the network 300 through the base station 200 . AI (Artificial Intelligence) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300. 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. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle to vehicle (V2V)/vehicle to everything (V2X) communication). In addition, IoT devices (eg, sensors) 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. Here, 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)). This can be achieved through technology (eg, 5G NR) 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. For example, the wireless communication/

connection

150a, 150b, and 150c may transmit/receive signals through various physical channels.To this end, based on various proposals of the present specification, for transmission/reception of radio signals At least some of various configuration information setting processes, various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), resource allocation processes, and the like may be performed.

Referring to FIG. 13 , the first wireless device 100 and the second wireless device 200 may transmit and receive radio signals through various radio access technologies (eg, LTE, NR). Here, {the first wireless device 100 and the second wireless device 200} refer to the {wireless device 100x and the base station 200} of FIG. 12 and/or the {wireless device 100x and 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. For example, 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 . In addition, 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 . For example, memory 104 may perform some or all of the processes controlled by processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them. Here, 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. In this specification, 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. For example, 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. In addition, 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 . For example, memory 204 may perform some or all of the processes controlled by processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them. Here, 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. In this specification, a wireless device may mean a communication modem/circuit/chip.

Hereinafter, hardware elements of the

wireless devices

100 and 200 will be described in more detail. Although not limited to this, one or more protocol layers may be implemented by one or

more processors

102, 202. For example, one or

more processors

102, 202 may implement one or more layers (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. can create One or

more 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.

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. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs). may be included in one or

more processors

102 and 202. The descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, 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. For example, one or

more transceivers

106 and 206 may be connected to one or

more processors

102 and 202 and transmit and receive wireless signals. For example, 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. In this document, 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. To this end, one or more of the

transceivers

106, 206 may include (analog) oscillators and/or filters.

Referring to FIG. 14 , 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. there is. Although not limited to this, the operations/functions of FIG. 14 may be performed by

processors

102 and 202 and/or

transceivers

106 and 206 of FIG. 13 . The hardware elements of FIG. 14 may be implemented in

processors

102 and 202 and/or

transceivers

106 and 206 of FIG. 13 . For example, blocks 1010-1060 may be implemented in

processors

102 and 202 of FIG. 13 . Also, blocks 1010 to 1050 may be implemented in the

processors

102 and 202 of FIG. 13 , and block 1060 may be implemented in the

transceivers

106 and 206 of FIG. 13 .

The codeword may be converted into a radio signal through the signal processing circuit 1000 of FIG. 14 . Here, 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).

Specifically, 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. Here, N is the number of antenna ports and M is the number of transport layers. Here, 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. To this end, 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. .

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. 14 . For example, wireless devices (eg, 100 and 200 of FIG. 13 ) may receive a wireless signal from the outside through an antenna port/transceiver. The received radio signal may be converted into a baseband signal through a signal restorer. To this end, 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. Thereafter, 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. The codeword may be restored to an original information block through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.

15 illustrates a wireless device according to an embodiment of the present specification. A wireless device may be implemented in various forms according to use-case/service (see FIG. 12).

Referring to FIG. 15,

wireless devices

100 and 200 correspond to the

wireless devices

100 and 200 of FIG. 13, and include various elements, components, units/units, and/or modules. ) can be configured. For example, 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 . For example, communication circuitry 112 may include one or

more processors

102, 202 of FIG. 13 and/or one or

more memories

104, 204. For example, transceiver(s) 114 may include one or

more transceivers

106, 206 of FIG. 13 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. For example, 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. Although not limited thereto, the wireless device may be a robot (Fig. 12, 100a), a vehicle (Fig. 12, 100b-1, 100b-2), an XR device (Fig. 12, 100c), a mobile device (Fig. 12, 100d), a home appliance. (FIG. 12, 100e), IoT device (FIG. 12, 100f), digital broadcast 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. 12, 400), a base station (Fig. 12, 200), a network node, and the like. Wireless devices can be mobile or used in a fixed location depending on the use-case/service.

In FIG. 15 , 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. For example, in the

wireless devices

100 and 200, 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. Can be connected wirelessly. Additionally, each element, component, unit/unit, and/or module within the

wireless device

100, 200 may further include one or more elements. For example, the control unit 120 may be composed of one or more processor sets. For example, the 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. As another example, 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.

Hereinafter, the implementation example of FIG. 15 will be described in more detail with reference to drawings.

16 illustrates a portable device according to an embodiment of the present specification. 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).

Referring to FIG. 16, 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. 15 .

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 . In addition, 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.

For example, in the case of data communication, 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. can be stored 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. In addition, 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.

17 illustrates a vehicle or autonomous vehicle according to an embodiment of the present specification. Vehicles or autonomous vehicles may be implemented as mobile robots, vehicles, trains, manned/unmanned aerial vehicles (AVs), ships, and the like.

Referring to FIG. 17, 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. 15 .

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. /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.

For example, 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). During autonomous driving, 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. In addition, during autonomous driving, 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.

The claims set forth herein can be combined in a variety of ways. For example, the technical features of the method claims of this specification may be combined to be implemented as a device, and the technical features of the device claims of this specification may be combined to be implemented as a method. In addition, the technical features of the method claims of the present specification and the technical features of the device claims may be combined to be implemented as a device, and the technical features of the method claims of the present specification and the technical features of the device claims may be combined to be implemented as a method.

Claims

In a method performed by a first terminal for scheduling of a physical sidelink channel in a wireless communication system,

Receiving setting information related to a search space from a base station;

Receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station; and

Transmitting the physical sidelink channel to a second terminal based on the DCI,

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on the search space being associated with one or more SL carriers, the DCI includes information on an SL carrier related to the scheduling.
According to claim 1,

Characterized in that monitoring of the PDCCH is omitted for a predefined SL carrier among the one or more SL carriers.
According to claim 2,

Wherein the predefined SL carrier is determined based on a value of a carrier indicator field among the one or more SL carriers.
According to claim 3,

The method characterized in that the value of the carrier indicator field (Carrier Indicator Field) of the predefined SL carrier is greater than 0.
According to claim 2,

Omission of monitoring of the PDCCH is characterized in that it is performed based on UE capability.
According to claim 5,

The UE performance is related to at least one of i) the maximum number of PDCCH candidates related to monitoring of the PDCCH and / or ii) the maximum number of control channel elements (CCEs) related to monitoring of the PDCCH characterized by a method.
According to claim 1,

The method characterized in that the payload of the DCI includes padding added based on a predefined DCI format size.
According to claim 7,

Wherein the predefined DCI format size is based on the largest value among DCI format sizes associated with the one or more SL carriers.
According to claim 7,

The padding is added based on the fact that the number of DCI format sizes for a serving cell related to the DCI is greater than a preset number,

The number of DCI format sizes based on the preset number is 4, and the number of DCI format sizes related to C-RNTI (Cell-Radio Network Temporary Identifier) among the 4 DCI format sizes is 3 Way.
According to claim 1,

The setting information includes information on an SL carrier for each search space related to DCI format 3_0 or DCI format 3_1.
According to claim 10,

The information on the SL carrier for each search space includes i) a value of a carrier indicator field and/or ii) a value for resource mapping of a PDCCH candidate related to the DCI.
According to claim 1,

The information on the SL carrier related to the scheduling is characterized in that it is based on i) a carrier indicator field and / or ii) a field for indicating a resource pool.
In a first terminal operating for scheduling of a physical sidelink channel in a wireless communication system,

one or more transceivers;

one or more processors controlling the one or more transceivers; and

one or more memories operably 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;

These actions are

Receiving setting information related to a search space from a base station;

Receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station; and

Transmitting the physical sidelink channel to a second terminal based on the DCI,

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on that the search space is related to one or more SL carriers, the DCI includes information on an SL carrier related to the scheduling.
In a device for controlling a first terminal to operate for scheduling of a physical sidelink channel in a wireless communication system,

one or more processors; and

one or more memories operably 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;

These actions are

Receiving setting information related to a search space from a base station;

Receiving downlink control information (DCI) related to scheduling of the physical sidelink channel from a base station; and

Transmitting the physical sidelink channel to a second terminal based on the DCI,

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on the search space being associated with one or more SL carriers, the DCI includes information on an SL carrier associated with the scheduling.
In one or more non-transitory computer readable media storing one or more instructions,

the one or more instructions, based on being executed by one or more processors, perform operations;

These actions are

Receiving setting information related to a search space from a base station;

Receiving downlink control information (DCI) related to scheduling of a physical sidelink channel from a base station; and

Transmitting the physical sidelink channel to a second terminal based on the DCI,

The DCI is received based on monitoring of a Physical Downlink Channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on the search space being associated with one or more SL carriers, the DCI includes information on an SL carrier related to the scheduling.
In a method performed by a base station for scheduling of a physical sidelink channel in a wireless communication system,

Transmitting setting information related to a search space to a first terminal; and

Transmitting downlink control information (DCI) related to scheduling of the physical sidelink channel to the first terminal; Including,

The reception of the DCI by the first terminal is performed based on monitoring of a physical downlink control channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on the search space being associated with one or more SL carriers, the DCI includes information on an SL carrier related to the scheduling.
In a base station operating for scheduling of a physical sidelink channel in a wireless communication system,

one or more transceivers;

one or more processors controlling the one or more transceivers; and

one or more memories operably 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;

These actions are

Transmitting setting information related to a search space to a first terminal; and

Transmitting downlink control information (DCI) related to scheduling of the physical sidelink channel to the first terminal; Including,

The reception of the DCI by the first terminal is performed based on monitoring of a physical downlink control channel (PDCCH) related to the search space,

The setting information includes information on an SL carrier related to the search space,

Based on the search space being associated with one or more SL carriers, the DCI includes information on an SL carrier related to the scheduling.