Method and apparatus for performing SL DRX operation in NR V2X

Abstract

A method for a first device to perform wireless communication and a device supporting the same are provided, the method may include obtaining a default sidelink (SL) discontinuous reception (DRX) configuration, obtaining a profile indicating whether SL DRX is compatible, and performing a first SL transmission based on the default SL DRX configuration based on the profile indicating that the SL DRX is compatible, establishing a PC5 radio resource control (RRC) connection with a second device, obtaining a SL DRX configuration, transmitting information related to the SL DRX configuration to the second device, and performing a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems. [Background technology]

[0002] Sidelink (SL) is a communication method that establishes a direct link between terminals (User Equipment, UE) and directly exchanges voice or data between terminals without going through a base station (BS). SL is being considered as a solution to alleviate the burden on base stations due to the rapidly increasing data traffic. V2X (vehicle-to-everything) is a communication technology that exchanges information with other vehicles, pedestrians, infrastructure, etc. via wired or 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 can be provided via the PC5 interface and / or Uu interface.

[0003] Meanwhile, as more communication devices require larger communication capacities, there is an emerging need for improved mobile broadband communication compared to existing radio access technologies (RATs). Accordingly, communication systems that take into account reliability- and latency-sensitive services or terminals are being discussed, and next-generation wireless access technologies that take into account improved mobile broadband communication, massive machine-type communication (MTC), ultra-reliable and low latency communication (URLLC), etc. can be called new radio access technology (RAT) or new radio (NR). NR can also support vehicle-to-everything (V2X) communication.

[0004] 1 is a diagram illustrating a comparison between V2X communication based on a pre-NR RAT and V2X communication based on NR. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.

[0005] In relation to V2X communication, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) have been mainly discussed in RATs prior to NR. V2X messages can include location information, dynamic information, attribute information, etc. For example, a terminal can send a periodic message type CAM and / or an event-triggered message type DENM to another terminal.

[0006] Since then, various V2X scenarios have been proposed in NR in relation to V2X communication, including vehicle platooning, advanced driving, extended sensors, remote driving, etc. Summary of the Invention [Problem to be solved by the invention]

[0007] On the other hand, even if UE#X (e.g., TX UE) and UE#Y (e.g., RX UE) are performing unicast-based SL communication, UE#X can simultaneously perform other SL communication with UE#Z. Under such circumstances, when UE#X determines / configures the SL DRX setting for UE#Y, UE#X can minimize its own battery consumption by considering not only the generation pattern of packets transmitted to UE#Y but also the generation pattern of packets transmitted to UE#Z. For example, after UE#X turns on its RF, it can perform packet transmission to UE#Y and UE#Z as continuously as possible, thereby minimizing its own battery consumption. On the other hand, for example, if, after UE#X establishes a unicast link with UE#Y, packet transmission from UE#X to UE#Y is performed based on the SL DRX setting associated with information such as a packet-related TX profile (and / or QoS profile) rather than based on the SL DRX setting linked to the unicast link, battery consumption minimization from the perspective of UE#X (as described above) cannot be achieved. [Means for solving the problem]

[0008] In one embodiment, a method for a first device to perform wireless communication may be provided, the method including the steps of: obtaining a default sidelink (SL) discontinuous reception (DRX) configuration, obtaining a profile indicating whether SL DRX is compatible, and performing a first SL transmission based on the default sidelink (SL DRX) configuration based on the profile indicating that the SL DRX is compatible, establishing a PC5 radio resource control (RRC) connection with a second device, obtaining the SL DRX configuration, transmitting information related to the SL DRX configuration to the second device, and performing a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.

[0009] In one embodiment, a first device configured to perform wireless communication may be provided. The first device may include one or more memories for storing instructions, one or more transceivers, and one or more processors connecting the one or more memories to the one or more transceivers. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, and, based on the profile indicating that the SL DRX is compatible, control the one or more transceivers to perform a first SL transmission based on the default SL DRX setting, establish a PC5 radio resource control (RRC) connection with a second device, obtain a SL DRX setting, control the one or more transceivers to transmit information related to the SL DRX setting to the second device, and control the one or more transceivers to perform a second SL transmission to the second device based on the SL DRX setting regardless of the profile.

[0010] In one embodiment, a processing device configured to control a first device performing wireless communication may be provided. The processing device may include one or more processors and one or more memories executable by the one or more processors and configured to store instructions. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, and, based on the profile indicating that the SL DRX is compatible, perform a first SL transmission based on the default SL DRX setting, establish a PC5 radio resource control (RRC) connection with a second device, obtain a SL DRX setting, transmit information related to the SL DRX setting to the second device, and perform a second SL transmission to the second device based on the SL DRX setting regardless of the profile. [Effects of the Invention]

[0011] The energy saving benefits of the terminal can be maximized. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram for explaining a comparison between V2X communication based on a RAT prior to NR and V2X communication based on NR. [Figure 2] 1 illustrates the structure of an NR system according to one embodiment of the present disclosure. [Figure 3] 1 illustrates a radio protocol architecture according to one embodiment of the present disclosure. [Figure 4] 1 illustrates a structure of an NR radio frame according to one embodiment of the present disclosure. [Figure 5] 1 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure. [Figure 6]1 illustrates an example of a BWP according to an embodiment of the present disclosure. [Figure 7] 1 illustrates a terminal performing V2X or SL communication according to one embodiment of the present disclosure. [Figure 8] According to one embodiment of the present disclosure, a procedure for a terminal to perform V2X or SL communication depending on a transmission mode is shown. [Figure 9] 1 illustrates three cast types according to one embodiment of the present disclosure. [Figure 10] 1 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure. [Figure 11] 1 illustrates a method for a second device to perform wireless communication, according to one embodiment of the present disclosure. [Figure 12] 1 illustrates a communication system 1 according to one embodiment of the present disclosure. [Figure 13] 1 illustrates a wireless device according to one embodiment of the present disclosure. [Figure 14] 1 illustrates a signal processing circuit for a transmit signal according to one embodiment of the present disclosure. [Figure 15] 1 illustrates a wireless device according to one embodiment of the present disclosure. [Figure 16] 1 illustrates a mobile device according to one embodiment of the present disclosure. [Figure 17] 1 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Also, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0014] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0015] As used herein, "at least one of A and B" can mean "only A," "only B," or "both A and B." Additionally, as used herein, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted as "at least one of A and B."

[0016] Furthermore, in this specification, "at least one of A, B and C" can mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" can mean "at least one of A, B and C."

[0017] Furthermore, parentheses used herein may mean "for example." Specifically, when "control information (PDCCH)" is used, "PDCCH" is proposed as an example of "control information." Furthermore, "control information" in this specification is not limited to "PDCCH," and "PDCCH" is proposed as an example of "control information." Furthermore, when "control information (i.e., PDCCH)" is used, "PDCCH" is proposed as an example of "control information."

[0018] In this specification, technical features individually described in one drawing may be embodied individually or simultaneously.

[0019] The following technologies can be used in various wireless communication systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented in wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000. TDMA can be implemented in wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), and enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and evolved UTRA (E-UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (registered trademark) 3rd generation partnership project (LTE) long term evolution (LTE) employs OFDMA on the downlink and SC-FDMA on the uplink as part of evolved UMTS (E-UMTS) that uses evolved-UMTS terrestrial radio access (E-UTRA). LTE-A (advanced) is an evolution of 3GPP LTE.

[0020] 5G NR is a successor technology to LTE-A and is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, including low-frequency bands below 1 GHz, intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0021] For clarity of explanation, the description will be centered on 5G NR, but the technical idea according to an embodiment of the present disclosure is not limited thereto.

[0022] 2 illustrates an NR system architecture according to one embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure.

[0023] Referring to FIG. 2, a Next Generation Radio Access Network (NG-RAN) may include a base station 20 that provides user plane and control plane protocol termination for a terminal 10. For example, the base station 20 may include a next generation NodeB (gNB) and / or an evolved NodeB (eNB). For example, the terminal 10 may be fixed or mobile, and may be referred to as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, or other terms. For example, a base station is a fixed station that communicates with the terminal 10, and may be referred to as a base transceiver system (BTS), an access point, or other terms.

[0024] The embodiment of Figure 2 illustrates a case where only gNBs are included. Base stations 20 may be connected to each other via an Xn interface. Base stations 20 may be connected to a 5G Core Network (5GC) via an NG interface. More specifically, base stations 20 may be connected to an access and mobility management function (AMF) 30 via an NG-C interface and to a user plane function (UPF) 30 via an NG-U interface.

[0025] The radio interface protocol layers between a terminal and a network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the bottom three layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems. Among these, the physical layer, which belongs to the first layer, provides an information transfer service using a physical channel, and the Radio Resource Control (RRC) layer, which is located in the third layer, controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0026] FIG. 3 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure. Specifically, (a) of FIG. 3 illustrates a user plane radio protocol stack for Uu communication, and (b) of FIG. 3 illustrates a control plane radio protocol stack for Uu communication. (c) of FIG. 3 illustrates a user plane radio protocol stack for SL communication, and (d) of FIG. 3 illustrates a control plane radio protocol stack for SL communication.

[0027] Referring to Figure 3, the physical layer provides information transfer services to higher layers using physical channels. The physical layer is connected to the higher layer, the Medium Access Control (MAC) layer, via transport channels. Data moves between the MAC layer and the physical layer via the transport channels. Transport channels are classified according to how and what characteristics data is transmitted over the radio interface.

[0028] Data is transferred between different physical layers, i.e., between the physical layers of a transmitter and a receiver, via a physical channel, which can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0029] The MAC layer provides services to the higher-level radio link control (RLC) layer via logical channels. The MAC layer provides a mapping function from multiple logical channels to multiple transport channels. The MAC layer also provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. The MAC sublayer provides data transfer services on the logical channels.

[0030] The RLC layer performs concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To guarantee various Quality of Service (QoS) requirements for Radio Bearers (RBs), the RLC layer provides three operation modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction via automatic repeat request (ARQ).

[0031] The Radio Resource Control (RRC) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. RB refers to the logical path provided by layer 1 (physical layer or PHY layer) and layer 2 (MAC layer, RLC layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer) for data transmission between the terminal and the network.

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

[0033] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. The SDAP layer performs mapping between QoS flows and data radio bearers, QoS flow identifier (ID) marking in downlink and uplink packets, etc.

[0034] RB configuration refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service and setting their specific parameters and operation methods. RBs are divided into two types: SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer). SRB is used as a path to transmit RRC messages in the control plane, and DRB is used as a path to transmit user data in the user plane.

[0035] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state; otherwise, it is in the RRC_IDLE state. In the case of NR, an RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state maintains its connection with the core network and can release its connection with the base station.

[0036] Downlink transport channels for transmitting data from a network to a terminal include a Broadcast Channel (BCH) for transmitting system information and a Downlink Shared Channel (SCH) for transmitting user traffic and control messages. Traffic or control messages of downlink multicast or broadcast services can be transmitted via the Downlink SCH or via a separate Downlink Multicast Channel (MCH). Meanwhile, uplink transport channels for transmitting data from a terminal to a network include a Random Access Channel (RACH) for transmitting initial control messages and an Uplink Shared Channel (SCH) for transmitting user traffic and control messages.

[0037] Above the transport channels, logical channels that are mapped to the transport channels include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0038] 4 illustrates a radio frame structure for NR according to one embodiment of the present disclosure. The embodiment of FIG. 4 can be combined with various embodiments of the present disclosure.

[0039] Referring to Figure 4, in NR, radio frames can be used for uplink and downlink transmission. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame can include five 1 ms subframes (SF). A subframe can be divided into one or more slots, and the number of slots in a subframe can be determined by the subcarrier spacing (SCS). Each slot can include 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP).

[0040] When a normal CP is used, each slot can contain 14 symbols. When an extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols) or Single Carrier-FDMA (SC-FDMA) symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).

[0041] Table 1 below shows the number of symbols per slot (N) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown below.

[0042] [Table 1]

[0043] 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.

[0044] [Table 2]

[0045] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) can be set to be different between multiple cells merged into one terminal, thereby allowing the (absolute time) duration of time resources (e.g., subframes, slots, or TTIs) (commonly referred to as TUs (Time Units) for convenience) consisting of the same number of symbols to be set to be different between the merged cells.

[0046] In NR, multiple numerologies or SCSs can be supported to support various 5G services. For example, if the SCS is 15 kHz, wide areas in traditional cellular bands can be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban areas, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0047] The NR frequency band can be defined as two types of frequency ranges. The two types of frequency ranges are FR1 and FR2. The values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges are shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," and can be called millimeter wave (mmW).

[0048] [Table 3]

[0049] As mentioned above, the numerical values ​​of the frequency range of the NR system may be changed. For example, FR1 may include the band from 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as communications for vehicles (e.g., autonomous driving).

[0050] [Table 4]

[0051] 5 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure. The embodiment of FIG. 5 can be combined with various embodiments of the present disclosure.

[0052] 5, a slot includes a plurality of symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, and in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, and in the case of an extended CP, one slot may include 6 symbols.

[0053] A carrier includes multiple subcarriers in the frequency domain. A Resource Block (RB) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) can be defined as multiple (P)RBs (Physical Resource Blocks) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed via activated BWPs. Each element is called a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0054] The following explains BWP (Bandwidth Part) and carriers.

[0055] A Bandwidth Part (BWP) is a contiguous set of physical resource blocks (PRBs) in a given numerology. PRBs can be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

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

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

[0058] 6 shows an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 6, it is assumed that there are three BWPs.

[0059] Referring to Figure 6, CRBs (common resource blocks) are carrier resource blocks numbered from one end of a carrier band to the other end, and PRBs are resource blocks numbered within each BWP. Point A can indicate a common reference point for the resource block grid.

[0060] BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP) For example, point A is the external reference point of the PRB of the carrier to which subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on the carrier) is aligned. For example, the offset is the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth is the number of PRBs in a given numerology.

[0061] The following describes V2X or SL communication.

[0062] The Sidelink Synchronization Signal (SLSS) is a SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may perform initial signal detection and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and S-SSS.

[0063] The PSBCH (Physical Sidelink Broadcast Channel) is a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information includes information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, for evaluating PSBCH performance, in NR V2X, the size of the PSBCH payload is 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0064] The S-PSS, S-SSS, and PSBCH can be included in a block format (e.g., an S-SS (Synchronization Signal) / PSBCH block, hereinafter referred to as an S-SSB (Sidelink-Synchronization Signal Block)) that supports periodic transmission. The S-SSB can have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in a carrier, and the transmission bandwidth is within a (pre-) configured S-BWP (Sidelink Bandwidth Part). For example, the bandwidth of the S-SSB is 11 RBs (Resource Blocks). For example, the PSBCH spans 11 RBs. The frequency location of the S-SSB can be (pre-) configured. Therefore, the terminal does not need to perform hypothesis detection in frequency to find the S-SSB in the carrier.

[0065] 7 illustrates a terminal performing V2X or SL communication according to one embodiment of the present disclosure. The embodiment of FIG. 7 can be combined with various embodiments of the present disclosure.

[0066] 7, the term "terminal" in V2X or SL communication may primarily refer to a user terminal. However, when network equipment such as a base station transmits and receives signals through a terminal-to-terminal communication method, the base station may also be considered a type of terminal. For example, terminal 1 is a first device 100, and terminal 2 is a second device 200.

[0067] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which means a collection of resources. Then, 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 setting from which terminal 1 can transmit a signal and can detect the signal of terminal 1 within the resource pool.

[0068] Here, when the terminal 1 is within the connection range of the base station, the base station can inform the terminal 1 of a resource pool. On the other hand, when the terminal 1 is outside the connection range of the base station, another terminal can inform the terminal of a resource pool, or the terminal 1 can use a pre-configured resource pool.

[0069] Generally, a resource pool can be configured with a plurality of resource units, and each terminal can select one or more resource units to use for transmitting its own SL signal.

[0070] The following describes resource allocation in SL.

[0071] 8 illustrates a procedure in which a terminal performs V2X or SL communication according to a transmission mode according to an embodiment of the present disclosure. The embodiment of FIG. 8 can be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be referred to as a mode or a resource allocation mode. Hereinafter, for convenience of description, in LTE, the transmission mode may be referred to as an LTE transmission mode, and in NR, the transmission mode may be referred to as an NR resource allocation mode.

[0072] For example, (a) of Figure 8 illustrates terminal operation associated with LTE transmission mode 1 or LTE transmission mode 3. Alternatively, for example, (a) of Figure 8 illustrates terminal operation associated with 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.

[0073] For example, (b) of FIG. 8 illustrates terminal operation associated with LTE transmission mode 2 or LTE transmission mode 4. Or, for example, (b) of FIG. 8 illustrates terminal operation associated with NR resource allocation mode 2.

[0074] Referring to (a) of FIG. 8, in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, a base station can schedule SL resources used by a terminal for SL transmission. For example, the base station can perform resource scheduling for terminal 1 via a PDCCH (e.g., Downlink Control Information (DCI)) or RRC signaling (e.g., Configured Grant Type 1 or Configured Grant Type 2), and terminal 1 can perform V2X or SL communication with terminal 2 through the resource scheduling. For example, terminal 1 can transmit sidelink control information (SCI) to terminal 2 via a physical sidelink control channel (PSCCH), and then transmit data based on the SCI to terminal 2 via a physical sidelink shared channel (PSSCH).

[0075] Referring to (b) of FIG. 8, in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, a terminal may determine SL transmission resources within SL resources configured by a base station / network or preconfigured SL resources. For example, the configured SL resources or preconfigured SL resources are a resource pool. For example, a terminal may autonomously select or schedule resources for SL transmission. For example, a terminal may independently select resources within a configured resource pool to perform SL communication. For example, a terminal may perform sensing and resource (re)selection procedures and independently select resources within a selection window. For example, the sensing may be performed on a subchannel basis. Then, terminal 1, which independently selects resources within a resource pool, may transmit SCI to terminal 2 via a PSCCH and then transmit data based on the SCI to terminal 2 via a PSSCH.

[0076] FIG. 9 illustrates three cast types according to an embodiment of the present disclosure. The embodiment of FIG. 9 can be combined with various embodiments of the present disclosure. Specifically, (a) of FIG. 9 illustrates broadcast-type SL communication, (b) of FIG. 9 illustrates unicast-type SL communication, and (c) of FIG. 9 illustrates groupcast-type SL communication. In the case of unicast-type SL communication, a terminal can perform one-to-one communication with another terminal. In the case of groupcast-type SL communication, a terminal can perform SL communication with one or more terminals in a group to which the terminal belongs. In various embodiments of the present disclosure, SL groupcast communication can be replaced with SL multicast communication, SL one-to-many communication, etc.

[0077] The Hybrid Automatic Repeat Request (HARQ) procedure will now be described.

[0078] For SL unicast and groupcast, HARQ feedback and HARQ combining in the physical layer can be supported. For example, when a receiving terminal operates in resource allocation mode 1 or 2, the receiving terminal can receive a PSSCH from a transmitting terminal and can transmit HARQ feedback for the PSSCH to the transmitting terminal using a sidelink feedback control information (SFCI) format via a physical sidelink feedback channel (PSFCH).

[0079] For example, SL HARQ feedback can be enabled for unicast. In this case, in non-CBG (non-Code Block Group) operation, if a receiving terminal decodes a PSCCH targeted at the receiving terminal and successfully decodes a transmission block associated with the PSCCH, the receiving terminal can generate a HARQ-ACK. The receiving terminal can then transmit the HARQ-ACK to the transmitting terminal. On the other hand, if the receiving terminal cannot successfully decode a transmission block associated with the PSCCH after decoding a PSCCH targeted at the receiving terminal, the receiving terminal can generate a HARQ-NACK. The receiving terminal can then transmit the HARQ-NACK to the transmitting terminal.

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

[0081] (1) Groupcast Option 1: After a receiving terminal decodes a PSCCH targeted at the receiving terminal, if the receiving terminal fails to decode a transmission block associated with the PSCCH, the receiving terminal can transmit a HARQ-NACK to the transmitting terminal via a PSFCH. On the other hand, if the receiving terminal decodes a PSCCH targeted at the receiving terminal and successfully decodes a transmission block associated with the PSCCH, the receiving terminal does not transmit a HARQ-ACK to the transmitting terminal.

[0082] (2) Groupcast Option 2: After a receiving terminal decodes a PSCCH targeted at the receiving terminal, if the receiving terminal fails to decode a transmission block associated with the PSCCH, the receiving terminal can transmit a HARQ-NACK to the transmitting terminal via a PSFCH. If the receiving terminal decodes a PSCCH targeted at the receiving terminal and successfully decodes a transmission block associated with the PSCCH, the receiving terminal can transmit a HARQ-ACK to the transmitting terminal via a PSFCH.

[0083] For example, when groupcast option 1 is used for SL HARQ feedback, all terminals performing groupcast communication can share the PSFCH resource, e.g., terminals belonging to the same group can transmit HARQ feedback using the same PSFCH resource.

[0084] For example, when groupcast option 2 is used for SL HARQ feedback, each terminal performing groupcast communication can use different PSFCH resources for transmitting HARQ feedback. For example, terminals belonging to the same group can transmit HARQ feedback using different PSFCH resources.

[0085] For example, when SL HARQ feedback is enabled for groupcast, the receiving terminal can decide whether to send HARQ feedback to the transmitting terminal based on the TX-RX (Transmission-Reception) distance and / or RSRP (Reference Signal Received Power).

[0086] For example, in groupcast option 1, in the case of TX-RX distance-based HARQ feedback, if the TX-RX distance is smaller than or equal to the communication range requirement, the receiving terminal may transmit HARQ feedback for the PSSCH to the transmitting terminal. On the other hand, if the TX-RX distance is larger than the communication range requirement, the receiving terminal may not transmit HARQ feedback for the PSSCH to the transmitting terminal. For example, the transmitting terminal may inform the receiving terminal of the location of the transmitting terminal via the SCI associated with the PSSCH. For example, the SCI associated with the PSSCH is a second SCI. For example, the receiving terminal may estimate or obtain the TX-RX distance based on the location of the receiving terminal and the location of the transmitting terminal. For example, the receiving terminal may decode the SCI associated with the PSSCH to determine the communication range requirement used for the PSSCH.

[0087] For example, in the case of resource allocation mode 1, the time (offset) between the PSFCH and the PSSCH can be configured or preset. In the case of unicast and groupcast, if retransmission is necessary on the SL, this can be indicated to the base station by a terminal within the coverage using the PUCCH. The transmitting terminal may send an indication to the serving base station of the transmitting terminal in the form of a Scheduling Request (SR) / Buffer Status Report (BSR) rather than in the form of a HARQ ACK / NACK. Also, even if the base station does not receive the indication, the base station can schedule retransmission resources for the SL to the terminal. For example, in the case of resource allocation mode 2, the time (offset) between the PSFCH and the PSSCH can be configured or preset.

[0088] For example, in a carrier, from the perspective of terminal transmission, TDM between PSCCH / PSSCH and PSFCH is permitted for a PSFCH format for SL in a slot. For example, a sequence-based PSFCH format having one symbol is supported. Here, the one symbol may not be an automatic gain control (AGC) period. For example, the sequence-based PSFCH format is applicable to unicast and groupcast.

[0089] For example, within a slot associated with a resource pool, the PSFCH resource may be periodically configured or preconfigured for an N-slot interval. For example, N may be configured to one or more values ​​greater than or equal to 1. For example, N may be 1, 2, or 4. For example, HARQ feedback for transmissions on a particular resource pool may be transmitted only via the PSFCH on that particular resource pool.

[0090] For example, when a transmitting terminal transmits a PSSCH from slot #X to slot #N to a receiving terminal, the receiving terminal can transmit HARQ feedback for the PSSCH to the transmitting terminal in slot #(N+A). For example, slot #(N+A) may include a PSFCH resource. Here, for example, A may be the smallest integer greater than or equal to K. For example, K may be the number of logical slots. In this case, K is the number of slots in a resource pool. Or, for example, K may be the number of physical slots. In this case, K is the number of slots inside and outside the resource pool.

[0091] For example, when a receiving terminal transmits HARQ feedback on a PSFCH resource in response to a PSSCH transmitted from a transmitting terminal to the receiving terminal, the receiving terminal may determine the frequency domain and / or code domain of the PSFCH resource based on an implicit mechanism within a configured resource pool. For example, the receiving terminal may determine the frequency domain and / or code domain of the PSFCH resource based on at least one of a slot index associated with the PSCCH / PSSCH / PSFCH, a subchannel associated with the PSCCH / PSSCH, and / or an identifier for distinguishing each receiving terminal in a group for groupcast option 2-based HARQ feedback. And / or, for example, the receiving terminal may determine the frequency domain and / or code domain of the PSFCH resource based on at least one of SL RSRP, SINR, L1 source ID, and / or location information.

[0092] For example, when a terminal's transmission of HARQ feedback via the PSFCH and its reception of HARQ feedback via the PSFCH overlap, the terminal may select either the transmission of HARQ feedback via the PSFCH or the reception of HARQ feedback via the PSFCH based on a priority rule. For example, the priority rule may be based on at least a priority indication of the associated PSCCH / PSSCH.

[0093] For example, if HARQ feedback transmissions via PSFCH for multiple terminals of a terminal overlap, the terminal may select a particular HARQ feedback transmission based on a priority rule, which may be based at least on a priority indication of the associated PSCCH / PSSCH.

[0094] On the other hand, in this specification, for example, a transmitting terminal (TX UE) is a terminal that transmits data to a (target) receiving terminal (RX UE). For example, the TX UE is a terminal that performs PSCCH and / or PSSCH transmission. For example, the TX UE is a terminal that transmits SL CSI-RS and / or SL CSI report request indicator to the (target) RX UE. For example, the TX UE is a terminal that transmits (predefined) reference signals (e.g., PSSCH demodulation reference signals (DM-RS)) and / or SL (L1) RSRP report request indicators used for SL (L1) RSRP measurement to the (target) RX UE. For example, the TX UE is a terminal that transmits (control) channels (e.g., PSCCH, PSSCH, etc.) and / or reference signals on the (control) channels (e.g., DM-RS, CSI-RS, etc.) used for SL radio link monitoring (RLM) operation and / or SL radio link failure (RLF) operation of the (target) RX UE.

[0095] On the other hand, in this specification, a receiving terminal (RX UE) is a terminal that transmits SL HARQ feedback to a transmitting terminal (TX UE) according to whether it has successfully decoded data received from the TX UE and / or whether it has successfully detected / decoded a PSCCH (related to PSSCH scheduling) transmitted by the TX UE. For example, the RX UE is a terminal that performs SL CSI transmission to the TX UE based on an SL CSI-RS and / or an SL CSI report request indicator received from the TX UE. For example, the RX UE is a terminal that transmits SL (L1) RSRP measurement values ​​measured based on a (predefined) reference signal and / or an SL (L1) RSRP report request indicator received from the TX UE to the TX UE. For example, the RX UE is a terminal that transmits its own data to the TX UE. For example, the RX UE is a terminal that performs SL RLM operation and / or SL RLF operation based on a (preconfigured) (control) channel and / or a reference signal on the (control) channel received from the TX UE.

[0096] Meanwhile, in this specification, for example, a TX UE can transmit at least one of the following information to a RX UE via an SCI: Here, for example, a TX UE can transmit at least one of the following information to a RX UE via a first SCI and / or a second SCI:

[0097] -PSSCH (and / or PSCCH) related resource allocation information (e.g., location / number of time / frequency resources, resource reservation information (e.g., periodicity))

[0098] -SL CSI report request indicator or SL (L1) RSRP (and / or SL (L1) RSRQ and / or SL (L1) RSSI) report request indicator

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

[0100] -MCS (Modulation and Coding Scheme) information

[0101] -Transmission power information

[0102] -L1 destination ID information and / or L1 source ID information

[0103] -SL HARQ process ID information

[0104] -NDI (new data indicator) information

[0105] -RV (redundancy version) information

[0106] -(Transmission traffic / packet related) QoS information (e.g., priority information)

[0107] -SL CSI-RS transmission indicator or (transmitted) SL CSI-RS antenna port number information

[0108] Location information of the TX UE or location (or distance area) information of the target RX UE (for which SL HARQ feedback is required)

[0109] Reference signal (e.g., DM-RS, etc.) information related to decoding and / or channel estimation of data transmitted via PSSCH. For example, the reference signal information may be information related to the (time-frequency) mapping resource pattern of DM-RS, RANK information, antenna port index information, antenna port number information, etc.

[0110] Meanwhile, in this specification, for example, a PSCCH is substituted / replaced with at least one of an SCI, a first SCI (1st-stage SCI), and / or a second SCI (2nd-stage SCI). For example, an SCI is substituted / replaced with at least one of a PSCCH, a first SCI, and / or a second SCI. For example, a PSSCH is substituted / replaced with a second SCI and / or a PSCCH.

[0111] On the other hand, in this specification, for example, if the SCI configuration fields are divided into two groups in consideration of a (relatively) high SCI payload size, the first SCI including the first SCI configuration field group can be referred to as the 1st SCI, and the second SCI including the second SCI configuration field group can be referred to as the 2nd SCI. For example, the 1st SCI and the 2nd SCI are transmitted via different channels. For example, the 1st SCI is transmitted to the receiving terminal via the PSCCH. For example, the 2nd SCI is transmitted to the receiving terminal via an (independent) PSCCH or piggybacked with data via the PSSCH.

[0112] Meanwhile, in this specification, for example, "setting" or "definition" refers to (pre)setting from a base station or a network. For example, "setting" or "definition" refers to (pre)setting of a specific resource pool from a base station or a network. For example, a base station or a network may transmit information related to the "setting" or "definition" to a terminal. For example, a base station or a network may transmit information related to the "setting" or "definition" to a terminal via predefined signaling. For example, the predefined signaling may include at least one of RRC signaling, MAC signaling, PHY signaling, and / or SIB.

[0113] On the other hand, in this specification, for example, "setting" or "definition" means being specified or set through pre-established signaling between terminals. For example, information related to "setting" or "definition" is transmitted and received through pre-established signaling between terminals. For example, the pre-defined signaling is PC5 RRC signaling.

[0114] On the other hand, in this specification, for example, RLF is interchangeable / substituted with OOS (Out-of-Synch) and / or IS (In-Synch).

[0115] Meanwhile, in this specification, for example, a resource block (RB) can be substituted / replaced with a subcarrier. For example, a packet or traffic can be substituted / replaced with a transport block (TB) or a medium access control protocol data unit (MAC PDU) depending on the layer to be transmitted. For example, a code block group (CBG) can be substituted / replaced with a TB. For example, a source ID can be substituted / replaced with a destination ID. For example, an L1 ID can be substituted / replaced with an L2 ID. For example, an L1 ID is an L1 source ID or an L1 destination ID. For example, an L2 ID is an L2 source ID or an L2 destination ID.

[0116] Meanwhile, in this specification, for example, the operation of a TX UE reserving / selecting / determining a retransmission resource means the operation of a TX UE reserving / selecting / determining a potential retransmission resource, the actual use or non-use of which is determined based on SL HARQ feedback information received from a RX UE.

[0117] Meanwhile, in this specification, resources may be substituted / replaced with slots or symbols. For example, resources include slots and / or symbols. For example, PSSCH may be substituted / replaced with PSCCH.

[0118] On the other hand, in this specification, SL MODE 1 refers to a resource allocation method or communication method in which a base station directly schedules SL transmission resources for a TX UE via predefined signaling (e.g., DCI or RRC message). For example, SL MODE 2 refers to a resource allocation method or communication method in which a terminal independently selects SL transmission resources within a resource pool configured by a base station or a network or configured in advance. For example, a terminal performing SL communication based on SL MODE 1 may be referred to as a MODE 1 UE or MODE 1 TX UE, and a terminal performing SL communication based on SL MODE 2 may be referred to as a MODE 2 UE or MODE 2 TX UE.

[0119] Meanwhile, in this specification, for example, a dynamic grant (DG) can be substituted / replaced with a configured grant (CG) and / or a semi-persistent scheduling grant (SPS grant). For example, a DG can be substituted / replaced with a combination of a CG and an SPS grant. For example, a CG includes at least one of configured grant type 1 (CG type 1) and / or configured grant type 2 (CG type 2). For example, in CG type 1, a grant is provided by RRC signaling and stored as a configured grant. For example, in CG type 2, a grant is provided by PDCCH and stored or deleted as a configured grant based on L1 signaling indicating grant activation or deactivation. For example, in CG type 1, a base station can allocate periodic resources to a TX UE via an RRC message. For example, in CG type 2, a base station can allocate periodic resources to a TX UE via an RRC message, and can dynamically activate or deactivate the periodic resources via DCI.

[0120] Meanwhile, in this specification, a channel may be substituted / replaced with a signal. For example, transmission and reception of a channel may include transmission and reception of a signal. For example, transmission and reception of a signal may include transmission and reception of a channel. For example, a cast may be substituted / replaced with at least one of a unicast, a groupcast, and / or a broadcast. For example, a cast type may be substituted / replaced with at least one of a unicast, a groupcast, and / or a broadcast. For example, a cast or a cast type may include unicast, a groupcast, and / or a broadcast.

[0121] However, in this specification, resources may be substituted / replaced with slots or symbols, for example, resources may include slots and / or symbols.

[0122] Meanwhile, in this specification, priority is interchangeable / replaced with at least one of LCP (Logical Channel Prioritization), latency, reliability, minimum required communication range, PPPP (Prose Per-Packet Priority), SLRB (Sidelink Radio Bearer), QoS profile, QoS parameter, and / or requirement.

[0123] On the other hand, in this specification, for convenience of explanation, for example, a (physical) channel used when an RX UE transmits at least one of the following information to a TX UE may be referred to as a PSFCH:

[0124] -SL HARQ feedback, SL CSI, SL(L1) RSRP

[0125] Meanwhile, SL DRX (discontinuous reception) operation may be supported for UEs. For example, for SL DRX operation, TX UE and RX UE may acquire SL DRX configuration. For example, the SL DRX configuration may be configured or pre-configured for the TX UE and RX UE. For example, the TX UE may transmit the SL DRX configuration to the RX UE. For example, the SL DRX configuration may include at least one of information related to an SL DRX timer, information related to an SL DRX slot offset, information related to an SL DRX start offset, and / or information related to an SL DRX cycle.

[0126] For example, the SL DRX timer may include at least one of an SL DRX on-duration timer, an SL DRX inactivity timer, an SL DRX retransmission timer, and / or an SL DRX HARQ RTT timer. For example, the SL DRX on-duration timer is the duration at the beginning of an SL DRX cycle. For example, the SL DRX inactivity timer is the duration after the first slot of SCI reception in which an SCI indicates a new SL transmission for the MAC entity. For example, the SL DRX retransmission timer is the maximum duration until an SL retransmission is received. For example, the SL DRX HARQ RTT timer is the minimum duration before an SL HARQ retransmission is expected by the MAC entity. For example, the SL DRX retransmission timer and the SL DRX HARQ RTT timer can be configured separately for each sidelink process. For example, the SL DRX inactivity timer, the SL DRX retransmission timer, and the SL DRX HARQ RTT timer do not apply to broadcast transmissions. For example, the UE may start the SL DRX retransmission timer after the SL DRX HARQ RTT timer expires.

[0127] For example, the SL DRX slot offset is the delay before the start of the SL DRX on duration timer, and the SL DRX start offset is the slot where the SL DRX cycle starts.

[0128] For example, the time during which at least one of the SL DRX on-duration timer, the SL DRX inactivity timer, and / or the SL DRX retransmission timer is running is the active time. However, in various embodiments of the present disclosure, the active time is not limited to the time during which at least one of the SL DRX on-duration timer, the SL DRX inactivity timer, and / or the SL DRX retransmission timer is running. For example, even if the SL DRX on-duration timer, the SL DRX inactivity timer, and the SL DRX retransmission timer are not running, the RX UE can operate in the active time and can monitor the PSCCH from the TX UE.

[0129] On the other hand, even if UE#X (e.g., TX UE) and UE#Y (e.g., RX UE) are performing unicast-based SL communication, UE#X can simultaneously perform other SL communication with UE#Z. Under such circumstances, when UE#X determines / configures the SL DRX setting for UE#Y, UE#X can minimize its own battery consumption by considering not only the generation pattern of packets transmitted to UE#Y but also the generation pattern of packets transmitted to UE#Z. For example, after UE#X turns on its RF, it can perform packet transmission to UE#Y and UE#Z as continuously as possible, thereby minimizing its own battery consumption. On the other hand, for example, if, after UE#X establishes a unicast link with UE#Y, packet transmission from UE#X to UE#Y is performed based on the SL DRX setting associated with information such as a packet-related TX profile (and / or QoS profile) rather than based on the SL DRX setting linked to the unicast link, battery consumption minimization from the perspective of UE#X (as described above) cannot be achieved.

[0130] Various embodiments of the present disclosure propose a method for a UE to perform SL communication based on an SL DRX configuration and a device supporting the method. In the present disclosure, for example, a TX profile may be referred to as a profile or an SL DRX profile. For example, a TX profile, a profile, or an SL DRX profile may indicate SL DRX ON (i.e., SL DRX compatible) or SL DRX OFF (i.e., SL DRX incompatible).

[0131] For example, it may be configured (in advance) whether data transmission / reception assuming application of SL DRX is to be performed (e.g., this may be designated as SL DRX ON) or whether data transmission / reception not assuming application of SL DRX is to be performed (e.g., this may be designated as SL DRX OFF). For example, whether data transmission / reception assuming application of SL DRX is to be performed or whether data transmission / reception not assuming application of SL DRX is to be performed may be configured or configured in advance for a TX UE and / or a RX UE. For example, whether data transmission / reception assuming application of SL DRX is to be performed or whether data transmission / reception not assuming application of SL DRX is to be performed may be configured (in advance) for each service type / type. For example, whether data transmission / reception assuming application of SL DRX is to be performed or whether data transmission / reception not assuming application of SL DRX is to be performed may be configured (in advance) for each QoS requirement / profile. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each radio bearer. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each logical channel. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each release. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each QoS flow ID. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each (L2) source ID.For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each (L2) destination ID. For example, whether data transmission / reception assuming application of SL DRX or data transmission / reception not assuming application of SL DRX should be performed can be configured (in advance) for each SL session / link. In the present disclosure, for convenience of explanation, such configuration information can be referred to as an SL DRX profile, a TX profile, or a profile.

[0132] Here, for example, in the case of a TX UE, when an upper layer (e.g., V2X layer) of the TX UE delivers a packet to a lower layer (e.g., PHY layer, MAC layer, RLC layer, RRC layer, PDCP layer, SDAP layer), the SL DRX profile can also be delivered. In this case, if the SL DRX profile is specified as SL DRX ON, the TX UE can select candidate resources within the SL DRX active time interval applied by RX UEs interested in the associated service type / type to perform packet transmission. On the other hand, if the SL DRX profile is specified as SL DRX OFF, the TX UE can select candidate resources related to packet transmission, assuming that RX UEs interested in the associated service type / type are always awake-up. Also, for example, in the case of a RX UE, the upper layer of the RX UE can deliver the SL DRX profile for the service type / type in which it is interested to the lower layer. In this case, if the SL DRX profile is specified as SL DRX ON, the RX UE can wake up within the SL DRX active time and perform related packet reception operations, whereas if the SL DRX profile is specified as SL DRX OFF, the RX UE can always wake up and perform related packet reception operations.

[0133] For example, based on the following (part of) proposed schemes, a method for more efficiently managing the power consumption of a RX UE is proposed. Here, for example, the proposed rules of the present disclosure may be limited to a (pre-configured) cast type (e.g., unicast). For example, the proposed rules of the present disclosure may be limited to a (pre-configured) service type / kind. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) priority. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) QoS requirement / profile. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) radio bearer. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) logical channel. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) release. For example, the proposed rules of the present disclosure may be limited to a (pre-configured) QoS flow ID. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be expanded (and / or substituted) with a service type / kind. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be expanded (and / or substituted) with a cast type. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be expanded (and / or substituted) with a priority. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be expanded (and / or substituted) with a QoS requirement / profile.For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in the present disclosure can be extended (and / or replaced) with radio bearer. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in the present disclosure can be extended (and / or replaced) with logical channel. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in the present disclosure can be extended (and / or replaced) with release. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be extended (and / or replaced) with QoS Flow ID. For example, the "(L2) source ID and / or (L2) destination ID (pair / combination)" wording (and / or "SL session / link" wording) used in this disclosure can be extended (and / or replaced) with SL session / link.

[0134] According to one embodiment of the present disclosure, for example, an SL DRX configuration (hereinafter, ONGO_SLDRX) (configured by the TX UE based on a request / assistance information received from the RX UE) may exist / be configured for a (L2) source ID and / or (L2) destination ID (pair / combination). In this case, even if the SL DRX profile is specified as SL DRX OFF, for packets transmitted / received via an SL session / link associated with the (L2) source ID and / or (L2) destination ID (pair / combination), the TX UE may be configured to select transmission resources based on the SL DRX active time interval of the ONGO_SLDRX, and the RX UE may be configured to perform reception operations based on the SL DRX active time interval of the ONGO_SLDRX. And / or, when there are an SL DRX active time interval of the ONGO_SLDRX and other intervals (inactive time) (in the remaining PDB), the UE may be configured to select transmission resources within the active time interval with a (relatively) higher priority. Here, for example, when this rule is applied, SL DRX ON / OFF may be finally determined by whether an (L2) source ID and / or (L2) destination ID (pair / combination)-specific ONGO_SLDRX exists (rather than the SL DRX profile), and the ONGO_SLDRX may be interpreted as overriding the SL DRX profile. Also, for example, in the above example situation, if the SL DRX profile of a packet transmitted / received via an SL session / link associated with an (L2) source ID and / or (L2) destination ID (pair / combination) is specified as SL DRX ON, transmission resource selection and reception operations may be performed based on the SL DRX active time duration of the ONGO_SLDRX.

[0135] For example, when the above-described rule is applied, if an SL DRX profile-related packet designated as SL DRX OFF is transmitted / received during the SL DRX active time interval of ONGO_SLDRX, the UE may be configured not to start / operate the SL DRX timer. On the other hand, for example, if an SL DRX profile-related packet designated as SL DRX ON is transmitted / received during the SL DRX active time interval of ONGO_SLDRX, the UE may be configured to start / operate the SL DRX timer. Also, for example, related information may be transmitted via predefined signaling (e.g., PSCCH, SCI, etc.) so that a RX UE can know whether the packet-related SL DRX profile transmitted by a TX UE is SL DRX ON or SL DRX OFF (even if PSSCH decoding fails). Or, for example, when the above-described rules are applied, the UE can be configured to start / operate the SL DRX timer in all cases where an SL DRX profile related packet designated as SL DRX OFF and an SL DRX profile related packet designated as SL DRX ON are transmitted / received during the SL DRX active time period of ONGO_SLDRX.

[0136] For example, when the above-described rules are applied, when a TX UE transmits an SL DRX profile-related packet for which SL DRX OFF is specified, the TX UE can select resources (e.g., all resources for initial transmission and the required number of retransmissions) from among candidate resources within a currently running active time interval (hereinafter, RUN_ACTTIME) of ONGO_SLDRX, and the TX UE can perform packet transmission based on the selected resources. On the other hand, when a TX UE transmits an SL DRX profile-related packet for which SL DRX ON is specified, the TX UE can select resources (e.g., all resources for initial transmission and the required number of retransmissions) from among candidate resources within the RUN_ACTTIME of ONGO_SLDRX and candidate resources within an active time extended by the resources selected within RUN_ACTTIME, and the TX UE can perform packet transmission based on the selected resources.

[0137] According to an embodiment of the present disclosure, for example, a service type / type having the same characteristic of whether SL DRX is applicable / required may be (limitedly) configured for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination). For example, a QoS profile having the same characteristic of whether SL DRX is applicable / required may be (limitedly) configured for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination). For example, a radio bearer having the same characteristic of whether SL DRX is applicable / required may be (limitedly) configured for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination). For example, a logical channel having the same characteristic of whether SL DRX is applicable / required may be (limitedly) configured for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination). For example, a release with the same characteristic of whether SL DRX is applicable / required can be configured (limitedly) for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination). For example, a QoS flow ID with the same characteristic of whether SL DRX is applicable / required can be configured (limitedly) for each SL session / link related to a (L2) source ID and / or a (L2) destination ID (pair / combination).

[0138] Here, for example, when the corresponding rule is applied, if the SL DRX applicability / requirement characteristics associated with a currently operating SL session / link differ from the SL DRX applicability / requirement characteristics associated with a service type / type to be added, it can be interpreted that a new (value different from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created. For example, when the corresponding rule is applied, if the SL DRX applicability / requirement characteristics associated with a currently operating SL session / link differ from the SL DRX applicability / requirement characteristics associated with a QoS profile to be added, it can be interpreted that a new (value different from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created. For example, when the relevant rule is applied, if the SL DRX application / requirement characteristics associated with a currently operating SL session / link differ from the SL DRX application / requirement characteristics associated with a radio bearer to be added, it can be interpreted that a new (value different from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created. For example, when the relevant rule is applied, if the SL DRX application / requirement characteristics associated with a currently operating SL session / link differ from the SL DRX application / requirement characteristics associated with a logical channel to be added, it can be interpreted that a new (value different from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created. For example, when the relevant rules are applied, when the SL DRX application / requirement characteristics associated with a currently operating SL session / link are different from the SL DRX application / requirement characteristics associated with a release to be added, it can be interpreted that a new (different value from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created.For example, when the relevant rule is applied, when the SL DRX application / requirement characteristics associated with a currently operating SL session / link are different from the SL DRX application / requirement characteristics associated with a QoS flow ID to be added, it can be interpreted that a new (different value from the existing) (L2) source ID and / or (L2) destination ID (pair / combination) associated SL session / link must be created.

[0139] For example, if the service type / type to be added does not require SL DRX application, the service type / type can be added to an SL session / link (currently in operation) that includes / supports both service types / types that require SL DRX application and service types / types that do not require SL DRX application, whereas the service type / type is not added to an SL session / link (currently in operation) that includes / supports only service types / types that require SL DRX application.

[0140] For example, if the QoS profile to be added does not require SL DRX application, the QoS profile can be added to a (currently operating) SL session / link that includes / supports both a QoS profile that requires SL DRX application and a QoS profile that does not require SL DRX application, whereas the QoS profile is not added to a (currently operating) SL session / link that includes / supports only a QoS profile that requires SL DRX application.

[0141] For example, if a radio bearer to be added does not require SL DRX application, the radio bearer can be added to a (currently operating) SL session / link that includes / supports both radio bearers that require SL DRX application and radio bearers that do not require SL DRX application, whereas the radio bearer is not added to a (currently operating) SL session / link that includes / supports only radio bearers that require SL DRX application.

[0142] For example, if the logical channel to be added does not require SL DRX application, the logical channel can be added to a (currently operating) SL session / link that includes / supports both logical channels that require SL DRX application and logical channels that do not require SL DRX application, whereas the logical channel is not added to a (currently operating) SL session / link that includes / supports only logical channels that require SL DRX application.

[0143] For example, if a release to be added does not require SL DRX application, the release can be added to a (currently operating) SL session / link that includes / supports both releases that require SL DRX application and releases that do not require SL DRX application, whereas the release is not added to a (currently operating) SL session / link that includes / supports only releases that require SL DRX application.

[0144] For example, if the QoS flow ID to be added does not require SL DRX application, the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports both QoS flow IDs that require SL DRX application and QoS flow IDs that do not require SL DRX application, whereas the QoS flow ID is not added to a (currently operating) SL session / link that includes / supports only QoS flow IDs that require SL DRX application.

[0145] For example, if the service type / type to be added does not require SL DRX application, the service type / type can be added to an SL session / link (currently in operation) that includes / supports both service types / types that require SL DRX application and service types / types that do not require SL DRX application, or the service type / type can be added to an SL session / link (currently in operation) that includes / supports only service types / types that require SL DRX application.

[0146] For example, if the QoS profile to be added does not require SL DRX application, the QoS profile can be added to a (currently operating) SL session / link that includes / supports both a QoS profile that requires SL DRX application and a QoS profile that does not require SL DRX application, or the QoS profile can be added to a (currently operating) SL session / link that includes / supports only a QoS profile that requires SL DRX application.

[0147] For example, if a radio bearer to be added does not require SL DRX application, the radio bearer can be added to an SL session / link (currently in operation) that includes / supports both radio bearers that require SL DRX application and radio bearers that do not require SL DRX application, or the radio bearer can be added to an SL session / link (currently in operation) that includes / supports only radio bearers that require SL DRX application.

[0148] For example, if the logical channel to be added does not require SL DRX application, the logical channel can be added to a (currently operating) SL session / link that includes / supports both logical channels that require SL DRX application and logical channels that do not require SL DRX application, or the logical channel can be added to a (currently operating) SL session / link that includes / supports only logical channels that require SL DRX application.

[0149] For example, if the release to be added does not require SL DRX application, the release can be added to an SL session / link (currently in operation) that includes / supports both releases that require SL DRX application and releases that do not require SL DRX application, or the release can be added to an SL session / link (currently in operation) that includes / supports only releases that require SL DRX application.

[0150] For example, if the QoS flow ID to be added does not require SL DRX application, the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports both QoS flow IDs that require SL DRX application and QoS flow IDs that do not require SL DRX application, or the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports only QoS flow IDs that require SL DRX application.

[0151] For example, if a service type / type to be added requires SL DRX application, the service type / type cannot be added to a (currently operating) SL session / link that includes / supports both service types / types that require SL DRX application and service types / types that do not require SL DRX application; conversely, the service type / type can be added to a (currently operating) SL session / link that includes / supports only service types / types that require SL DRX application.

[0152] For example, if a QoS profile to be added requires SL DRX application, the QoS profile cannot be added to a (currently operating) SL session / link that includes / supports both a QoS profile that requires SL DRX application and a QoS profile that does not require SL DRX application; conversely, the QoS profile can be added to a (currently operating) SL session / link that includes / supports only a QoS profile that requires SL DRX application.

[0153] For example, if a radio bearer to be added requires SL DRX application, the radio bearer cannot be added to a (currently operating) SL session / link that includes / supports both radio bearers that require SL DRX application and radio bearers that do not require SL DRX application; conversely, the radio bearer can be added to a (currently operating) SL session / link that includes / supports only radio bearers that require SL DRX application.

[0154] For example, if a logical channel to be added requires SL DRX application, the logical channel cannot be added to a (currently operating) SL session / link that includes / supports both logical channels that require SL DRX application and logical channels that do not require SL DRX application; conversely, the logical channel can be added to a (currently operating) SL session / link that includes / supports only logical channels that require SL DRX application.

[0155] For example, if a release to be added requires SL DRX application, the release cannot be added to a (currently operating) SL session / link that includes / supports both releases that require SL DRX application and releases that do not require SL DRX application; conversely, the release can be added to a (currently operating) SL session / link that includes / supports only releases that require SL DRX application.

[0156] For example, if a QoS flow ID to be added requests SL DRX application, the QoS flow ID cannot be added to a (currently operating) SL session / link that includes / supports both QoS flow IDs that request SL DRX application and QoS flow IDs that do not request SL DRX application; conversely, the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports only QoS flow IDs that request SL DRX application.

[0157] For example, if the service type / type to be added requires SL DRX application, the service type / type can be added to an SL session / link (currently operating) that includes / supports both service types / types that require SL DRX application and service types / types that do not require SL DRX application, or the service type / type can be added to an SL session / link (currently operating) that includes / supports only service types / types that require SL DRX application.

[0158] For example, if the QoS profile to be added requires SL DRX application, the QoS profile can be added to a (currently operating) SL session / link that includes / supports both a QoS profile that requires SL DRX application and a QoS profile that does not require SL DRX application, or the QoS profile can be added to a (currently operating) SL session / link that includes / supports only a QoS profile that requires SL DRX application.

[0159] For example, if a radio bearer to be added requires SL DRX application, the radio bearer can be added to an SL session / link (currently in operation) that includes / supports both radio bearers that require SL DRX application and radio bearers that do not require SL DRX application, or the radio bearer can be added to an SL session / link (currently in operation) that includes / supports only radio bearers that require SL DRX application.

[0160] For example, if the logical channel to be added requires SL DRX application, the logical channel can be added to a (currently operating) SL session / link that includes / supports both logical channels that require SL DRX application and logical channels that do not require SL DRX application, or the logical channel can be added to a (currently operating) SL session / link that includes / supports only logical channels that require SL DRX application.

[0161] For example, if the release to be added requires SL DRX application, the release can be added to an SL session / link (currently in operation) that includes / supports both releases that require SL DRX application and releases that do not require SL DRX application, or the release can be added to an SL session / link (currently in operation) that includes / supports only releases that require SL DRX application.

[0162] For example, if the QoS flow ID to be added requests SL DRX application, the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports both QoS flow IDs that request SL DRX application and QoS flow IDs that do not request SL DRX application, or the QoS flow ID can be added to a (currently operating) SL session / link that includes / supports only QoS flow IDs that request SL DRX application.

[0163] For example, service type (and / or (LCH or SERVICE) priority and / or QOS requirements (e.g., LATENCY, RELIABILITY, MINIMUM COMMUNICATION RANGE) and / or PQI parameters) (and / or HARQ FEEDBACK ENABLED (and / or DISABLED) LCH / MAC PDU (transmission) and / or CBR measurement of resource pool and / or SL CAST TYPE (e.g., UNICAST, GROUPCAST, BROADCAST) and / or SL GROUPCAST ​​HARQ FEEDBACK OPTION (e.g., NACK ONLY FEEDBACK, ACK / NACK FEEDBACK, TX-RX DISTANCE BASED NACK ONLY FEEDBACK) and / or SL MODE1 CG TYPE (e.g., SL CG TYPE1 / 2) and / or SL MODE TYPE (e.g., MODE1 / 2) and / or resource pool and / or whether the PSFCH resource is configured in the resource pool and / or SOURCE (L2) ID (and / or DESTINATION (L2) ID) and / or PC5 RRC CONNECTION LINK and / or SL LINK and / or CONNECTIN state (with the base station) (e.g., RRC CONNECTED state, IDLE state, INACTIVE state) and / or SL HARQ PROCESS (ID) and / or whether SL DRX operation (of the TX UE or RX UE) is executable and / or whether POWER SAVING (TX or RX) UE is enabled and / or (from a specific UE perspective) if PSFCH TX and PSFCH RX (and / or multiple PSFCH TXs (exceeding the UE CAPABILITY)) overlap (and / or if PSFCH TX (and / or PSFCH RX) is omitted) and / or if TX UE to RX The applicability of the rule (and / or the proposed method / rule-related parameter value of the present disclosure) may be specifically (or differently or independently) set / allowed for at least one of (or separately from) elements / parameters such as whether the UE actually (successfully) received a PSCCH (and / or PSSCH) (re)transmission.In addition, the wording "configuration" (or "designation") in the present disclosure may be expanded to include a form in which a base station notifies a terminal via a predefined (physical layer or higher layer) channel / signal (e.g., SIB, RRC, MAC CE) (and / or a form provided via PRE-CONFIGURATION and / or a form in which a terminal notifies other terminals via a predefined (physical layer or higher layer) channel / signal (e.g., SL MAC CE, PC5 RRC)). In addition, the wording "PSFCH" in the present disclosure may be expanded to include "(NR or LTE) PSSCH (and / or (NR or LTE) PSCCH) (and / or (NR or LTE) SL SSB (and / or UL channel / signal))." The proposed methods in the present disclosure may be combined with each other and used in an expanded manner (to form new methods).

[0164] According to various embodiments of the present disclosure, after UE#X (e.g., TX UE) establishes a unicast link with UE#Y (e.g., RX UE), packet transmission from UE#X to UE#Y can be performed based on the SL DRX configuration linked to the unicast link, regardless of the associated TX profile (and / or QoS profile). For example, before a unicast link is established between UE#X and UE#Y, a default SL DRX configuration can be applied to packet transmissions to which no QoS profile is mapped (based on the TX profile received from a higher layer indicating ON or compatible). In contrast, for example, after a unicast link is established between UE#X and UE#Y, the SL DRX configuration linked to the unicast link can be applied to packet transmissions with the same characteristics. Through this, when UE#X performs not only unicast-based SL communication with UE#Y but also SL communication with other UE(s) simultaneously, UE#X can minimize its own battery consumption (by establishing a unicast link with UE#Y and then transmitting packets to UE#Y based on the SL DRX setting linked to the unicast link).

[0165] 10 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure.

[0166] Referring to FIG. 10 , in step S1010, a first device may acquire a default sidelink (SL) discontinuous reception (DRX) configuration. In step S1020, the first device may acquire a profile indicating whether SL DRX is compatible. In step S1030, the first device may perform a first SL transmission based on the default sidelink (SL) DRX configuration based on the profile indicating that the SL DRX is compatible. In step S1040, the first device may establish a PC5 radio resource control (RRC) connection with a second device. In step S1050, the first device may acquire an SL DRX configuration. In step S1060, the first device may transmit information related to the SL DRX configuration to the second device. In step S1070, the first device may perform a second SL transmission to the second device based on the SL DRX configuration, regardless of the profile.

[0167] Additionally, for example, the first device may select a first SL resource within an active time associated with the default SL DRX configuration based on the profile indicating that the SL DRX is compatible. For example, the first SL transmission may be performed based on the first SL resource.

[0168] Additionally, for example, the first device may determine that the second device interested in the first SL transmission will not perform SL DRX operation based on the profile indicating that SL DRX is incompatible. Additionally, for example, the first device may select a first SL resource without considering the default SL DRX configuration. For example, the first SL transmission may be performed based on the first SL resource.

[0169] Additionally, for example, the first device may select a second SL resource within an active time associated with the SL DRX configuration based on the PC5 RRC connection being established between the first device and the second device. For example, the second SL transmission may be performed based on the second SL resource. For example, based on the PC5 RRC connection being established between the first device and the second device, the profile is not taken into account in the second SL transmission by the first device.

[0170] For example, obtaining the profile indicating whether the SL DRX is compatible may include transmitting the profile from an upper layer of the first device to a lower layer of the first device before establishing the PC5 RRC connection with the second device. For example, after establishing the PC5 RRC connection with the second device, the upper layer of the first device is not allowed to transmit the profile to a lower layer of the first device.

[0171] For example, the SL DRX configuration can be set for a pair of a source identifier (ID) and a destination ID.

[0172] Additionally, for example, the first device can receive assistance information from the second device, and the SL DRX configuration can be configured for a source ID and destination ID pair based on the assistance information.

[0173] For example, the PC5 RRC connection may support only transmissions for which SL DRX operation is required. For example, the second SL transmission includes a transmission for which the SL DRX operation is required and does not include a transmission for which the SL DRX operation is not required. For example, the first device is not allowed to perform a third SL transmission over the PC5 RRC connection for which the SL DRX operation is not required based on the SL DRX configuration.

[0174] For example, the PC5 RRC connection may support a transmission for which SL DRX operation is required and a transmission for which the SL DRX operation is not required. For example, the second SL transmission may include a transmission for which the SL DRX operation is required or a transmission for which the SL DRX operation is not required.

[0175] For example, the first SL transmission may include transmission of information for establishing the PC5 RRC connection, the default SL DRX configuration may include information associated with a first SL DRX cycle and information associated with a timer for a first SL DRX active time, and the SL DRX configuration may include information associated with a second SL DRX cycle and information associated with a timer for a second SL DRX active time.

[0176] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor 102 of the first device 100 may acquire a default SL (sidelink) DRX (discontinuous reception) configuration. Then, the processor 102 of the first device 100 may acquire a profile indicating whether SL DRX is compatible. Then, the processor 102 of the first device 100 may control the transceiver 106 to perform a first SL transmission based on the default SL DRX configuration, based on the profile indicating that the SL DRX is compatible. Then, the processor 102 of the first device 100 may establish a PC5 RRC (radio resource control) connection with a second device. Then, the processor 102 of the first device 100 may acquire the SL DRX configuration. Then, the processor 102 of the first device 100 may control the transceiver 106 to transmit information related to the SL DRX configuration to the second device. The processor 102 of the first device 100 can then control the transceiver 106 to perform a second SL transmission to the second device based on the SL DRX configuration, regardless of the profile.

[0177] According to an embodiment of the present disclosure, a first device that performs wireless communication may be provided. For example, the first device may include one or more memories that store instructions, one or more transceivers, and one or more processors that couple the one or more memories to the one or more transceivers. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) configuration, obtain a profile indicating whether SL DRX is compatible, control the one or more transceivers to perform a first SL transmission based on the default SL DRX configuration based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a second device, obtain a SL DRX configuration, control the one or more transceivers to transmit information related to the SL DRX configuration to the second device, and control the one or more transceivers to perform a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.

[0178] According to an embodiment of the present disclosure, a processing device configured to control a first device performing wireless communication may be provided. For example, the processing device may include one or more processors and one or more memories executable by the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, perform a first SL transmission based on the default sidelink (SL) DRX setting based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a second device, obtain a SL DRX setting, transmit information related to the SL DRX setting to the second device, and perform a second SL transmission to the second device based on the SL DRX setting regardless of the profile.

[0179] According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium having recorded thereon instructions may be provided. For example, the instructions, when executed, may cause a first device to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, perform a first SL transmission based on the default sidelink (SL DRX) setting based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a second device, obtain a sidelink (SL) DRX setting, transmit information related to the sidelink (SL) DRX setting to the second device, and perform a second SL transmission to the second device based on the sidelink (SL) DRX setting regardless of the profile.

[0180] 11 illustrates a method for a second device to perform wireless communication according to one embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure.

[0181] Referring to FIG. 11 , in step S1110, a second device may acquire a default sidelink (SL) discontinuous reception (DRX) configuration. In step S1120, the second device may acquire a profile indicating whether SL DRX is compatible. In step S1130, the second device may perform a first SL reception based on the default sidelink (SL) DRX configuration based on the profile indicating that the SL DRX is compatible. In step S1140, the second device may establish a PC5 radio resource control (RRC) connection with a first device. In step S1150, the second device may acquire an SL DRX configuration. In step S1160, the second device may receive information related to the SL DRX configuration from the first device. In step S1170, the second device may perform a second SL reception from the first device based on the SL DRX configuration, regardless of the profile.

[0182] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor 202 of the second device 200 may acquire a default SL (sidelink) DRX (discontinuous reception) configuration. Then, the processor 202 of the second device 200 may acquire a profile indicating whether SL DRX is compatible. Then, the processor 202 of the second device 200 may control the transceiver 206 to perform first SL reception based on the default SL DRX configuration, based on the profile indicating that the SL DRX is compatible. Then, the processor 202 of the second device 200 may establish a PC5 RRC (radio resource control) connection with a first device. Then, the processor 202 of the second device 200 may acquire the SL DRX configuration. Then, the processor 202 of the second device 200 may control the transceiver 206 to receive information related to the SL DRX configuration from the first device. The processor 202 of the second device 200 can then control the transceiver 206 to perform a second SL reception from the first device based on the SL DRX configuration, regardless of the profile.

[0183] According to an embodiment of the present disclosure, a second device that performs wireless communication may be provided. For example, the second device may include one or more memories that store instructions, one or more transceivers, and one or more processors that couple the one or more memories to the one or more transceivers. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) configuration, obtain a profile indicating whether SL DRX is compatible, control the one or more transceivers to perform first SL reception based on the default SL DRX configuration based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a first device, obtain an SL DRX configuration, control the one or more transceivers to receive information related to the SL DRX configuration from the first device, and control the one or more transceivers to perform second SL reception from the first device based on the SL DRX configuration regardless of the profile.

[0184] According to an embodiment of the present disclosure, a processing device configured to control a second device performing wireless communication may be provided. For example, the processing device may include one or more processors and one or more memories executable by the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, perform first SL reception based on the default SL DRX setting based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a first device, obtain a SL DRX setting, receive information related to the SL DRX setting from the first device, and perform second SL reception from the first device based on the SL DRX setting regardless of the profile.

[0185] According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium having recorded thereon instructions may be provided. For example, the instructions, when executed, may cause a second device to obtain a default sidelink (SL) discontinuous reception (DRX) setting, obtain a profile indicating whether SL DRX is compatible, perform a first SL reception based on the default SL DRX setting based on the profile indicating that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a first device, obtain an SL DRX setting, receive information related to the SL DRX setting from the first device, and perform a second SL reception from the first device based on the SL DRX setting regardless of the profile.

[0186] Various embodiments of the present disclosure may be interconnected.

[0187] Hereinafter, a description will be given of an apparatus to which various embodiments of the present disclosure can be applied.

[0188] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flow charts disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0189] Hereinafter, the present invention will be described in more detail with reference to the drawings. In the following drawings / descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise stated.

[0190] FIG. 12 illustrates a communication system 1 according to one embodiment of the present disclosure.

[0191] 12 , a communication system 1 to which various embodiments of the present disclosure are applied includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that perform communication using wireless connection technologies (e.g., 5G New RAT (NR) and Long Term Evolution (LTE)) and are referred to as communication / wireless / 5G devices. Without being limited thereto, the wireless devices may include a robot 100a, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI device / server 400. For example, the vehicles may include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of performing inter-vehicle communication, etc. Here, the vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) devices, and may be embodied in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. Mobile devices may include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., notebooks, etc.), etc. Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, a base station or network may be embodied as a wireless device, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0192] Here, the wireless communication technology implemented in the wireless devices 100a to 100f in this specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NIT) for low-power communication. Here, for example, NB-IoT technology is an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Furthermore, or generally, the wireless communication technology implemented in the wireless devices 100a to 100f in this specification may perform communication based on LTE-M technology. Here, for example, LTE-M technology is an example of LPWAN technology and is referred to by various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-mentioned names. Additionally, or generally, the wireless communication technology implemented in wireless devices 100a-100f herein may include, but is not limited to, at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which are considered low-power communications. As an example, ZigBee technology is based on various standards, such as IEEE 802.15.4, and can create personal area networks (PANs) related to small / low-power digital communications, and is referred to by various names.

[0193] The wireless devices 100a to 100f may be connected to a network 300 via a base station 200. Artificial Intelligence (AI) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to an AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f may communicate with each other via the base station 200 / network 300, or may communicate directly with each other (e.g., sidelink communication) without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 may communicate directly with each other (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). Furthermore, an IoT device (for example, a sensor) can directly communicate with another IoT device (for example, a sensor) or another wireless device 100a to 100f.

[0194] Wireless communication / connections 150a, 150b, and 150c can be established between the wireless devices 100a to 100f and the base station 200, and between the base stations 200. Here, the wireless communication / connections may be performed via various wireless connection technologies (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, Integrated Access Backhaul (IAB)). Through the wireless communication / connections 150a, 150b, and 150c, wireless devices and base stations, and base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0195] FIG. 13 illustrates a wireless device according to one embodiment of the present disclosure.

[0196] 13, a first wireless device 100 and a second wireless device 200 may transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} may correspond to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

[0197] 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 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information / signal and then transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may also receive a wireless signal including second information / signal via 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 coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. Here, the processor 102 and the memory 104 are part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., 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 referred to as a radio frequency (RF) unit. In this disclosure, a wireless device may also refer to a communications modem / circuit / chip.

[0198] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signal and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal via the transceiver 206 and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for executing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. Here, the processor 202 and the memory 204 are part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., 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 referred to as an RF unit. In this disclosure, a wireless device may also refer to a communications modem / circuit / chip.

[0199] The hardware elements of the wireless devices 100, 200 will be described in more detail below. Without limitation, 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 (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The 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, suggestions, methods, and / or operational flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed herein to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein.

[0200] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using 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 the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software configured to be executed by one or more processors 102, 202, or stored in one or more memories 104, 204 and run by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software in the form of code, instructions, and / or collections of instructions.

[0201] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may comprise ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. The one or more memories 104, 204 may also be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0202] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or operational flowcharts, etc., of this document to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts, etc., disclosed herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208 and configured to transmit and receive user data, control information, radio signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein via one or more antennas 108, 208. In this document, one or more antennas may refer to multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To this end, one or more transceivers 106, 206 may include an (analog) oscillator and / or a filter.

[0203] FIG. 14 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0204] Referring to FIG. 14, a 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. Without being limited thereto, the operations / functions of FIG. 14 may be performed by the processors 102 and 202 and / or the transceivers 106 and 206 of FIG. 13. The hardware elements of FIG. 14 may be embodied in the processors 102 and 202 and / or the transceivers 106 and 206 of FIG. 13. For example, blocks 1010 to 1060 may be embodied in the processors 102 and 202 of FIG. 13. Furthermore, blocks 1010 to 1050 may be embodied in the processors 102 and 202 of FIG. 13, and block 1060 may be embodied in the transceivers 106 and 206 of FIG. 13.

[0205] The codeword can be converted into a radio signal via the signal processing circuit 1000 of FIG. 14. Here, the codeword is an encoded bit sequence of an information block. The information block can include a transmission block (e.g., a transmission block of an UL-SCH, a transmission block of a DL-SCH). The radio signal can be transmitted via various physical channels (e.g., a PUSCH, a PDSCH).

[0206] Specifically, the codeword may be converted into a scrambled bit sequence by the scrambler 1010. The scrambling sequence used for scrambling may be generated based on an initialization value, which may include ID information of the wireless device. The scrambled bit sequence may be modulated into a modulation symbol sequence by the modulator 1020. Modulation schemes may include pi / 2-Binary Phase Shift Keying (pi / 2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), etc. The complex modulation symbol sequence may be mapped to one or more transmission layers by the layer mapper 1030. The modulation symbols of each transmission layer may be mapped to corresponding antenna port(s) by the precoder 1040 (precoding). The output z of the precoder 1040 is obtained by multiplying the output y of the layer mapper 1030 by an N*M precoding matrix W. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder 1040 may perform precoding after performing transform precoding (e.g., DFT) on complex modulation symbols. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

[0207] The resource mapper 1050 can map modulation symbols for each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator 1060 generates wireless signals from the mapped modulation symbols, and the generated wireless signals can be transmitted to other devices via each antenna. To this end, the signal generator 1060 can include an inverse fast fourier Transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), a frequency uplink converter, etc.

[0208] In a wireless device, the signal processing process for a received signal may be configured as the inverse of the signal processing processes 1010 to 1060 in FIG. 14. For example, a wireless device (e.g., 100 or 200 in FIG. 13) may receive a wireless signal from an external device via an antenna port / transceiver. The received wireless signal may be converted to a baseband signal by 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 demapper process, a postcoding process, a demodulation process, and a descrambling process. The codeword may be restored to the original information block through decoding. Therefore, a signal processing circuit (not shown) for the received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.

[0209] 15 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be embodied in various forms depending on the use case / service (see FIG. 12).

[0210] 15, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 13 and may be configured with various elements, components, units, and / or modules. 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 a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include one or more processors 102 and 202 and / or one or more memories 104 and 204 of FIG. 13. For example, the transceiver(s) 114 may include one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 of FIG. 13. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 can control the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. In addition, the control unit 120 can transmit information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or can store information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0211] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Without being limited thereto, the wireless device may be embodied in the form of a robot (100a in FIG. 12), a vehicle (100b-1, 100b-2 in FIG. 12), an XR device (100c in FIG. 12), a mobile device (100d in FIG. 12), a home appliance (100e in FIG. 12), an IoT device (100f in FIG. 12), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or a financial device), a security device, a climate / environment device, an AI server / device (400 in FIG. 12), a base station (200 in FIG. 12), a network node, etc. The wireless device may be mobile or fixed depending on the use case / service.

[0212] 15, various elements, components, units / sections, and / or modules within the wireless devices 100 and 200 may be interconnected entirely via a wired interface, or at least some of them may be connected wirelessly via the communication unit 110. For example, within the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected via a wire, and the control unit 120 and a first unit (e.g., 130, 140) may be connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / section, and / or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured as a set of one or more processors. For example, the control unit 120 may be configured as a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0213] The embodiment of FIG. 15 will now be described in more detail with reference to other drawings.

[0214] 16 illustrates a mobile device according to one embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a notebook). The 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).

[0215] 16, a portable device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input / output unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 in FIG. 15, respectively.

[0216] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 can control the components of the portable device 100 and perform various operations. The control unit 120 can include an AP (Application Processor). The memory unit 130 can store data, parameters, programs, codes, and instructions required to operate the portable device 100. The memory unit 130 can also store input / output data / information. The power supply unit 140a supplies power to the portable device 100 and can include a wired / wireless charging circuit, a battery, etc. The interface unit 140b can support connection between the portable device 100 and other external devices. The interface unit 140b can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 140c can receive and output video information / signals, audio information / signals, data, and / or information input by 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.

[0217] For example, in the case of data communication, the input / output unit 140c may acquire information / signals (e.g., touch, text, voice, image, video) input by a user, and the acquired information / signals may be stored in the memory unit 130. The communication unit 110 may convert the information / signals stored in the memory into wireless signals and transmit the converted wireless signals directly to another wireless device or to a base station. The communication unit 110 may also receive wireless signals from another wireless device or a base station and restore the received wireless signals to the original information / signals. The restored information / signals may be stored in the memory unit 130 and then output in various forms (e.g., text, voice, image, video, haptic) via the input / output unit 140c.

[0218] 17 illustrates a vehicle or an autonomous vehicle according to an embodiment of the present disclosure. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, or the like.

[0219] 17, a vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 15, respectively.

[0220] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 can control elements of the vehicle or autonomous vehicle 100 and perform various operations. The control unit 120 can include an ECU (Electronic Control Unit). The driving unit 140a can cause the vehicle or autonomous vehicle 100 to travel on the ground. The driving unit 140a can include an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and can include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane while driving, a technology for automatically adjusting speed like adaptive cruise control, a technology for automatically driving along a predetermined route, a technology for automatically setting a route and driving when a destination is set, etc.

[0221] For example, the communication unit 110 may receive map data, traffic information data, etc. 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 control unit 120 may control the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. During autonomous driving, the communication unit 110 may non-periodically acquire the latest traffic information data from an external server and acquire surrounding traffic information data from surrounding vehicles. Also, during autonomous driving, the sensor unit 140c may acquire vehicle status and surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and the driving plan based on the newly acquired data / information. The communication unit 110 may transmit information regarding the vehicle position, autonomous driving route, driving plan, etc. 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 autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0222] The claims described herein may be combined in various ways. For example, technical features of method claims herein may be combined and embodied in an apparatus, and technical features of apparatus claims herein may be combined and embodied in a method. Furthermore, technical features of method claims herein and technical features of apparatus claims herein may be combined and embodied in an apparatus, and technical features of method claims herein and technical features of apparatus claims herein may be combined and embodied in a method.

Claims

1. A method performed by a first device, obtaining a default sidelink (SL) discontinuous reception (DRX) setting; obtaining a profile indicating whether SL DRX is applicable; performing a first SL transmission to a second device based on the default SL DRX configuration based on the profile indicating that the SL DRX is applicable; establishing a PC5 radio resource control (RRC) connection with the second device; obtaining SL DRX configuration; transmitting information related to the SL DRX configuration to the second device; performing a second SL transmission to the second device based on the SL DRX configuration; The method, wherein the profile is not used for the second SL transmission by the first device based on the PC5 RRC connection being established between the first device and the second device.

2. selecting a first SL resource within an active time associated with the default SL DRX configuration based on the profile indicating that the SL DRX is applicable; The method of claim 1 , wherein the first SL transmission is performed based on the first SL resource.

3. determining, based on the profile indicating that the SL DRX is not applicable, that the second device interested in the first SL transmission not perform SL DRX operation; selecting a first SL resource without considering the default SL DRX configuration; The method of claim 1 , wherein the first SL transmission is performed based on the first SL resource.

4. selecting a second SL resource within an active time associated with the SL DRX configuration based on the PC5 RRC connection being established between the first device and the second device; The method of claim 1 , wherein the second SL transmission is performed based on the second SL resource.

5. The method described in claim 1, wherein the profile is transferred by an upper layer of the first device to a lower layer of the first device before establishing the PC5 RRC connection with the second device.

6. 2. The method of claim 1, wherein after establishing the PC5 RRC connection with the second device, the upper layer of the first device is not allowed to transfer the profile to the lower layer of the first device.

7. The method of claim 1 , wherein the SL DRX configuration is configured for a pair of a source identifier (ID) and a destination ID.

8. receiving auxiliary information from the second device; The method of claim 1 , wherein the SL DRX configuration is configured for a source ID and destination ID pair based on the auxiliary information.

9. The method of claim 1 , wherein the PC5 RRC connection supports only transmissions for which SL DRX operation is required.

10. the second SL transmission includes a transmission for which the SL DRX operation is required and does not include a transmission for which the SL DRX operation is not required; The method of claim 9 , wherein the first device is not permitted to perform a third SL transmission over the PC5 RRC connection for which the SL DRX operation is not required based on the SL DRX configuration.

11. The PC5 RRC connection supports transmissions for which SL DRX operation is required and transmissions for which SL DRX operation is not required; The method of claim 1 , wherein the second SL transmission comprises the transmission for which the SL DRX operation is required or the transmission for which the SL DRX operation is not required.

12. the first SL transmission includes transmitting information for establishing the PC5 RRC connection; The default SL DRX configuration includes information related to a first SL DRX cycle and information related to a timer for a first SL DRX active time; The method of claim 1 , wherein the SL DRX configuration includes information associated with a second SL DRX cycle and information associated with a timer for a second SL DRX active time.

13. In the first device, at least one transceiver; at least one processor; at least one memory coupled to the at least one processor and configured to store instructions; The instructions, upon being executed, cause the first device to: Obtaining a default sidelink (SL) discontinuous reception (DRX) setting; Obtaining a profile indicating whether SL DRX is applicable; performing a first SL transmission to a second device based on the default SL DRX configuration based on the profile indicating that the SL DRX is applicable; establishing a PC5 radio resource control (RRC) connection with the second device; Obtaining SL DRX settings; transmitting information related to the SL DRX configuration to the second device; causing the second device to perform a second SL transmission based on the SL DRX configuration; A first device, wherein the profile is not used for the second SL transmission by the first device based on the PC5 RRC connection being established between the first device and the second device.

14. At least one processor; at least one memory coupled to the at least one processor and configured to store instructions; The instructions, when executed, cause the first device to: Obtaining a default sidelink (SL) discontinuous reception (DRX) setting; Obtaining a profile indicating whether SL DRX is applicable; performing a first SL transmission to a second device based on the default SL DRX configuration based on the profile indicating that the SL DRX is applicable; establishing a PC5 radio resource control (RRC) connection with the second device; Obtaining SL DRX settings; transmitting information related to the SL DRX configuration to the second device; causing the second device to perform a second SL transmission based on the SL DRX configuration; A processing device, wherein the profile is not used for the second SL transmission by the first device based on the PC5 RRC connection being established between the first device and the second device.

Images