Method and apparatus for configuring common SL DRX settings in NR V2X

Abstract

A method for operating a first device 100 in a wireless communication system is proposed, which may include obtaining information on an SL DRX configuration associated with at least one QoS profile and information on a basic SL DRX configuration, and determining the basic SL DRX configuration as the SL DRX configuration for SL communication based on no SL DRX configuration mapped to a QoS profile associated with a MAC PDU.

Description

[Technical Field]

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

[0002] Sidelink (SL) refers to a communication method that establishes a direct link between User Equipment (UE) devices, allowing for the direct exchange of voice or data between devices without going through a Base Station (BS). SL is considered one solution to address the burden on base stations caused by rapidly increasing data traffic. V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure 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] On the other hand, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. This has led to discussions about communication systems that take into account reliability and latency-sensitive services or terminals, and next-generation radio connectivity technologies that consider improved mobile broadband communication, massive MTC (Machine Type Communication), URLLC (Ultra-Reliable and Low Latency Communication), etc., can be referred to as new RATs (new radio access technology) or NRs (new radio). NRs can also support vehicle-to-everything (V2X) communication. [Overview of the project] [Means for solving the problem]

[0004] In one embodiment of the present disclosure, a method is proposed in which a first device performs wireless communication. For example, the method may include the steps of: obtaining information regarding an SL (sidelink) DRX (discontinuous reception) setting and a default SL DRX setting associated with at least one QoS (quality of service) profile; generating a MAC (medium access control) PDU (protocol data unit) associated with SL communication; determining an SL DRX setting for the SL communication, but determining the default SL DRX setting as the SL DRX setting for the SL communication based on the fact that there is no SL DRX setting mapped to a QoS profile associated with the MAC PDU; transmitting SCI (sidelink control information) for scheduling a PSCCH (physical sidelink control channel) to a second device based on the active time of the SL DRX setting for SL communication; and transmitting the MAC PDU to the second device via the PSCCH based on the active time.

[0005] According to one embodiment of the present disclosure, a first device for performing wireless communication may be provided. For example, the first device may include one or more memories for storing instruction words, one or more transceivers, and one or more processors connecting the one or more memories and the one or more transceivers. For example, one or more processors execute the instruction word, obtain information regarding the SL (sidelink) DRX (discontinuous reception) setting and the default SL DRX setting associated with at least one QoS (quality of service) profile, generate a MAC (medium access control) PDU (protocol data unit) associated with SL communication, and determine the SL DRX setting for SL communication. However, based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for SL communication. Based on the active time of the SL DRX setting for SL communication, the processors may transmit SCI (sidelink control information) for scheduling the PSSCH (physical sidelink shared channel) to a second device via the PSCCH (physical sidelink control channel), and transmit the MAC PDU to the second device via the PSSCH based on the active time.

[0006] In one embodiment of the present disclosure, an apparatus configured to control a first terminal may be provided. For example, the apparatus may include one or more processors executablely connected to the one or more processors and one or more memories for storing instructions. For example, one or more processors execute the instruction to obtain information regarding sidelink DRX (discontinuous reception) settings and default SL DRX (discontinuous reception) settings associated with at least one quality of service (QoS) profile, generate a medium access control (MAC) PDU (protocol data unit) associated with SL communication, and determine the SL DRX settings for SL communication. However, based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for SL communication. Based on the active time of the SL DRX setting for SL communication, the processors may transmit sidelink control information (SCI) for scheduling a physical sidelink shared channel (PSSCH) to a second terminal via a physical sidelink control channel (PSCCH), and transmit the MAC PDU to a second device via the PSSCH based on the active time.

[0007] In one embodiment of the present disclosure, a non-temporary computer-readable storage medium recording instructions can be provided. For example, when executed, the instructions may cause a first device to obtain information regarding the settings of a sidelink DRX (discontinuous reception) associated with at least one quality of service (QoS) profile and information regarding a default SL DRX setting, generate a medium access control (MAC) PDU (protocol data unit), determine the SL DRX setting for the SL communication, but based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for the SL communication, transmit sidelink control information (SCI) for scheduling a physical sidelink shared channel (PSSCH) to a second device via a physical sidelink control channel (PSCCH) based on the active time of the SL DRX setting for the SL communication, and transmit the MAC PDU to the second device via the PSSCH# based on the active time.

[0008] One embodiment of the present disclosure may provide a method for a second device to perform wireless communication. For example, the method includes the steps of: obtaining information regarding a sidelink DRX (discontinuous reception) setting and a default SL DRX setting associated with at least one quality of service (QoS) profile; receiving sidelink control information (SCI) for scheduling a physical sidelink shared channel (PSSCH) from a first device via a physical sidelink control channel (PSCCH) based on the active time of the default SL DRX setting; and receiving a medium access control (MAC) PDU (protocol data unit) from the first device via the PSSCH based on the active time, wherein the MAC PDU may be received based on the active time of the default SL DRX setting, on the basis that there is no SL DRX setting mapped to a QoS profile associated with the MAC PDU.

[0009] According to an embodiment of the present disclosure, a second device capable of performing wireless communication may be provided. For example, the second device may include one or more memories for storing instruction words, one or more transceivers, and one or more processors for connecting the one or more memories and the one or more transceivers. For example, the one or more processors execute the instruction words to obtain information on SL (sidelink) DRX (discontinuous reception) settings related to at least one QoS (quality of service) profile and information on basic (default) SL DRX settings, and based on the active time of the basic SL DRX settings, receive SCI (sidelink control information) for scheduling of PSSCH (physical sidelink shared channel) from a first device via PSCCH (physical sidelink control channel), and based on the active time, receive a MAC (medium access control) PDU (protocol data unit) from the first device via the PSSCH, where the MAC PDU may be received based on the active time of the basic SL DRX settings based on the fact that there is no SL DRX setting mapped to the QoS profile related to the MAC PDU.

Advantages of the Invention

[0010] The terminal can efficiently perform SL communication.

Brief Description of the Drawings

[0011] [Figure 1] Shows the structure of an NR system according to an embodiment of the present disclosure.

[0012] [Figure 2] Shows a radio protocol architecture according to an embodiment of the present disclosure.

[0013] [Figure 3] Shows the structure of an NR radio frame according to an embodiment of the present disclosure.

[0014] [Figure 4] Shows the slot structure of an NR frame according to an embodiment of the present disclosure.

[0015] [Figure 5] Shows an example of a BWP according to an embodiment of the present disclosure.

[0016] [Figure 6] Shows the procedure for a terminal to perform V2X or SL communication in the transmission mode according to an embodiment of the present disclosure.

[0017] [Figure 7] Shows three cast types according to an embodiment of the present disclosure.

[0018] [Figure 8] Shows an embodiment of the setting of the basic / common SL DRX setting according to an embodiment of the present disclosure.

[0019] <000012I>Shows the procedure for a power-saving terminal to perform wireless communication based on the basic SL DRX setting according to an embodiment of the present disclosure.

[0020] [Figure 10] Shows the procedure for a first device to perform wireless communication according to an embodiment of the present disclosure.

[0021] [Figure 11] Shows the procedure for a second device to perform wireless communication according to an embodiment of the present disclosure.

[0022] [Figure 12] Shows communication system 1 according to an embodiment of the present disclosure.

[0023] [Figure 13]This document shows a wireless device according to one embodiment of the present disclosure.

[0024] [Figure 14] This document shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0025] [Figure 15] This document shows a wireless device according to one embodiment of the present disclosure.

[0026] [Figure 16] This document shows a portable device according to one embodiment of the present disclosure.

[0027] [Figure 17] This shows a vehicle or autonomous vehicle according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0028] In this specification, “A or B” may mean “just A,” “just B,” or “both A and B.” Also, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “just A,” “just B,” “just C,” or “any combination of A, B and C.”

[0029] In this specification, slashes ( / ) and commas can mean "and / or". For example, "A / B" can mean "A and / or B". Thus, "A / B" can mean "just A", "just B", or "both A and B". For example, "A, B, C" can mean "A, B or C".

[0030] In this specification, “at least one of A and B” may mean “just A,” “just B,” or “both A and B.” Furthermore, in this specification, the expressions “at least one of A or B” and “at least one of A and / or B” may be interpreted in the same way as “at least one of A and B.”

[0031] Furthermore, in this specification, “at least one of A, B and C” may mean “just A,” “just B,” “just C,” or “any combination of A, B and C.” Also, “at least one of A, B or C” or “at least one of A, B and / or C” may mean “at least one of A, B and C.”

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

[0033] In the following explanation, "when, if, in case of" can be replaced with "based on".

[0034] In this specification, technical features described individually within a single drawing may be represented individually or simultaneously.

[0035] In this specification, higher layer parameters may be parameters that are set, pre-configured, or predefined for a terminal. For example, a base station or network may transmit higher layer parameters to a terminal. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0036] The following technologies can be used in a variety of wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented using wireless technologies such as UTRA (universal terrestrial radio access) and CDMA2000. TDMA can be implemented using wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented using wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) (registered trademark) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA (Evolved-UMTS Terrestrial Radio Access), employing OFDMA for downlink and SC-FDMA for uplink. LTE-A (Advanced) is an evolution of 3GPP LTE.

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

[0038] To clarify the explanation, the description will focus on 5G NR, but the technical concept relating to one embodiment of this disclosure is not limited thereto.

[0039] For terms and techniques used in this specification that are not specifically described herein, refer to the standard documents on radio communications published prior to the filing of this specification.

[0040] Figure 1 shows the structure of an NR system according to one embodiment of the present disclosure. The embodiment in Figure 1 can be combined with various embodiments of the present disclosure.

[0041] Referring to Figure 1, the NG-RAN (Next Generation-Radio Access Network) may include a base station 20 that provides user-plane and control-plane protocol termination to the terminal 10. For example, the base station 20 may include a gNB (next generation-NodeB) and / or an eNB (evolved-NodeB). For example, the terminal 10 may be fixed or mobile, and is also referred to by other terms such as MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), Wireless Device, etc. For example, the base station is a fixed station that communicates with the terminal 10, and is also referred to by other terms such as BTS (Base Transceiver System), Access Point, etc.

[0042] The embodiment in Figure 1 illustrates a case that includes only gNBs. The base stations 20 can be connected to each other via Xn interfaces. The base stations 20 can be connected to the 5th generation core network (5G Core Network: 5GC) via NG interfaces. More specifically, the base stations 20 can be connected to the AMF (access and mobility management function) 30 via the NG-C interface and to the UPF (user plane function) 30 via the NG-U interface.

[0043] The layers of the Radio Interface Protocol (RRC) between a terminal and a network can be divided into L1 (First Layer), L2 (Second Layer), and L3 (Third Layer) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Of these, the physical layer, which belongs to the first layer, provides information transfer services using physical channels, while the RRC (Radio Resource Control) layer, located in the third layer, plays the role of controlling radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0044] Figure 2 shows a radio protocol architecture according to one embodiment of the present disclosure. The embodiment in Figure 2 can be combined with various embodiments of the present disclosure. Specifically, Figure 2(a) shows a user-plane radio protocol stack for Uu communication, Figure 2(b) shows a control-plane radio protocol stack for Uu communication, Figure 2(c) shows a user-plane radio protocol stack for SL communication, and Figure 2(d) shows a control-plane radio protocol stack for SL communication.

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

[0046] Data travels between different physical layers, i.e., between the physical layers of the transmitter and receiver, via a physical channel. This physical channel can be modulated using the OFDM (Orthogonal Frequency Division Multiplexing) method, utilizing time and frequency as wireless resources.

[0047] The MAC layer provides services to the higher-level RLC (radio link control) layer via logical channels. The MAC layer provides mapping functionality from multiple logical channels to multiple transport channels. Furthermore, the MAC layer provides logical channel multiplexing functionality through mapping from multiple logical channels to a single transport channel. The MAC sub-layer provides data transfer services on logical channels.

[0048] The RLC hierarchy performs concatenation, segmentation, and reassembly of RLC SDUs (Service Data Units). To ensure the diverse Quality of Service (QoS) requirements of radio bearers (RBs), the RLC hierarchy provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction via ARQ (automatic repeat request).

[0049] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmit channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. RB refers to the logical path provided by the first layer (physical layer or PHY layer) and the second layer (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.

[0050] The functions of the PDCP hierarchy on the user plane include the transmission of user data, header compression, and encryption. The functions of the PDCP hierarchy on the control plane include the transmission of control plane data and encryption / integrity protection.

[0051] The SDAP (Service Data Adaptation Protocol) layer is defined only at the user level. The SDAP layer performs tasks such as mapping QoS flows to data radio bearers and marking QoS flow identifiers (IDs) in downlink and uplink packets.

[0052] Setting up a Radio Bearing (RB) refers to the process of defining the characteristics of the radio protocol hierarchy and channel in order to provide a specific service, and setting the specific parameters and operating methods for each. Furthermore, RBs are divided into two types: SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer). The SRB is used as a channel for transmitting RRC messages in the control plane, while the DRB is used as a channel for transmitting user data in the user plane.

[0053] When an RRC connection is established between the terminal's RRC layer and the base station's RRC layer, the terminal enters the RRC_CONNECTED state; otherwise, it enters the RRC_IDLE state. In the case of NR, an additional RRC_INACTIVE state is defined, in which a terminal in the RRC_INACTIVE state maintains its connection to the core network, while being able to release its connection to the base station.

[0054] Downlink transport channels, which transmit data from the network to terminals, include BCH (Broadcast Channel) for transmitting system information and Downlink SCH (Shared Channel) for transmitting user traffic and control messages. Downlink multicast or broadcast service traffic or control messages can be transmitted via Downlink SCH or via a separate Downlink MCH (Multicast Channel). On the other hand, uplink transport channels, which transmit data from terminals to the network, include RACH (Random Access Channel) for transmitting initial control messages and Uplink SCH (Shared Channel) for transmitting user traffic and control messages.

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

[0056] Figure 3 shows the structure of a wireless frame of NR according to one embodiment of the present disclosure. The embodiment in Figure 3 can be combined with various embodiments of the present disclosure.

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

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

[0059] Table 1 below shows the number of symbols per slot (N) depending on the SCS setting (u) when a 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 an example.

[0060] [Table 1]

[0061] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe when the extended CP is used, as determined by the SCS.

[0062] [Table 2]

[0063] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured to differ between multiple cells merged into a single terminal. This allows the (absolute time) intervals of time resources (e.g., subframes, slots, or TTIs) (commonly referred to as TUs (Time Units) for convenience), which consist of the same number of symbols, to be configured differently between the merged cells.

[0064] In NR, a number of numerologies or SCSs can be supported to support a variety of 5G services. For example, if the SCS is 15kHz, wide area coverage on traditional cellular bands can be supported, and if the SCS is 30kHz / 60kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0065] An NR frequency band can be defined as two types of frequency ranges. These two types of frequency ranges are FR1 and FR2. The numerical values ​​of the frequency ranges can be changed; for example, the two types of frequency ranges are as shown in Table 3 below. Among the frequency ranges used in NR systems, FR1 can mean the “sub 6GHz range,” and FR2 can mean the “above 6GHz range,” which can be called millimeter wave (mmW).

[0066] [Table 3]

[0067] As mentioned above, the numerical values ​​of the frequency range of the NR system can be changed. For example, FR1 can include a bandwidth of 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 can include frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 can include unlicensed bands. Unlicensed bands can be used for a variety of applications, for example, for vehicle communications (e.g., autonomous driving).

[0068] [Table 4]

[0069] Figure 4 shows a slot structure of an NR frame according to one embodiment of the present disclosure. The embodiment in Figure 4 can be combined with various embodiments of the present disclosure.

[0070] Referring to Figure 4, a slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot can contain 14 symbols, and in the case of an extended CP, one slot can contain 12 symbols. Alternatively, in the case of a normal CP, one slot can contain 7 symbols, and in the case of an extended CP, one slot can contain 6 symbols.

[0071] A carrier wave contains 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 consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier wave can contain 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 can be mapped to a single complex symbol.

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

[0073] A Bandwidth Part (BWP) is a contiguous set of Physical Resource Blocks (PRBs) for a given numerology. PRBs can be selected from a contiguous subset of Common Resource Blocks (CRBs) for a given numerology on a given carrier.

[0074] For example, a BWP is at least one of the active BWP, initial BWP, and / or default BWP. For example, a terminal may not monitor downlink radiolink quality on DL BWPs other than the active DL BWP on the PCell (primary cell). For example, a terminal does not receive PDCCH, PDSCH (physical downlink shared channel), or CSI-RS (reference signal) (except RRM) outside of an active DL BWP. For example, a terminal does not trigger CSI (Channel State Information) reports for inactive DL BWPs. For example, a terminal does not transmit PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel) outside of an active UL BWP. For example, when downlink, the initial BWP is given as a continuous RB set for the RMSI (remaining minimum system information) CORESET (control resource set) (set by the PBCH (physical broadcast channel)). For example, in the case of an uplink, the initial BWP is provided by the SIB (system information block) for random access procedures. For example, the default BWP is set by the upper layer. For example, the initial value of the default BWP is the initial DL BWP. For energy saving purposes, if a terminal is unable to detect DCI for a certain period of time, the terminal can switch its active BWP to the default BWP.

[0075] On one hand, a BWP can be defined for an 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 the SL channel or the SL signal on the said specific BWP. In a licensed carrier, the SL BWP can be defined separately from the Uu BWP, and the SL BWP can have separate configuration signalling from the Uu BWP. For example, a terminal can receive the configuration for the SL BWP from a base station / network. For example, a terminal can receive the configuration for the Uu BWP from a base station / network. The SL BWP can be (pre-)configured for out-of-coverage NR V2X terminals and RRC_IDLE terminals within a carrier. For terminals in the RRC_CONNECTED mode, at least one SL BWP can be activated within a carrier.

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

[0077] Referring to FIG. 5, a CRB (common resource block) is a carrier resource block numbered from one end of a carrier band to the other end. And a PRB is a resource block numbered within each BWP. Point A can indicate a common reference point for a resource block grid.

[0078] A BWP is defined by point A, the offset (N start BWP ) from point A, and the bandwidth (N size BWPIt can be set by the following: For example, point A is the outer 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 in question) is aligned. For example, offset is the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth is the number of PRBs in a given numerology.

[0079] The following explanation applies to V2X or SL communication.

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

[0081] The PSBCH (Physical Sidelink Broadcast Channel) is a broadcast channel that transmits fundamental (system) information that terminals should know first before transmitting or receiving SL signals. For example, this fundamental information includes information related to SLSS, duplex mode (DM), TDDUL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, application types related to SLSS, subframe offset, and broadcast information. For example, to evaluate PSBCH performance, in NR V2X, the size of the PSBCH payload is 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

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

[0083] Figure 6 illustrates a procedure in which a terminal performs V2X or SL communication by transmission mode according to one embodiment of the present disclosure. The embodiment in Figure 6 can be combined with various embodiments of the present disclosure. In the various embodiments of the present disclosure, the transmission mode may be referred to as a mode or resource allocation mode. Hereinafter, for convenience of explanation, in LTE, the transmission mode may be referred to as the LTE transmission mode, and in NR, the transmission mode may be referred to as the NR resource allocation mode.

[0084] For example, Figure 6(a) shows terminal operation associated with LTE transmission mode 1 or LTE transmission mode 3. Alternatively, for example, Figure 6(a) shows terminal operation associated with NR resource allocation mode 1. For example, LTE transmission mode 1 can be applied to general SL communication, and LTE transmission mode 3 can be applied to V2X communication.

[0085] For example, Figure 6(b) shows terminal operation associated with LTE transmission mode 2 or LTE transmission mode 4. Alternatively, for example, Figure 6(b) shows terminal operation associated with NR resource allocation mode 2.

[0086] Referring to Figure 6(a), in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, the base station can schedule SL resources to be used by the terminal for SL transmission. For example, in step S600, the base station can transmit information related to the SL resources and / or information related to the UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0087] For example, the first terminal can receive from the base station information related to a DG (dynamic grant) resource and / or information related to a CG (configured grant) resource. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that the base station configures / assigns to the first terminal via DCI (downlink control information). In this specification, a CG resource may be a (periodic) resource that the base station configures / assigns to the first terminal via DCI and / or RRC messages. For example, in the case of a CG type 1 resource, the base station may send an RRC message containing information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may send an RRC message containing information related to the CG resource to the first terminal, and the base station may send DCI related to the activation or release of the CG resource to the first terminal.

[0088] In step S610, the first terminal can transmit a PSCCH (e.g., SCI (Sidelink Control Information) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S620, the first terminal can transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) associated with the PSCCH to the second terminal. In step S630, the first terminal can receive a PSFCH associated with the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) can be received from the second terminal via the PSFCH. In step S640, the first terminal can transmit / report the HARQ feedback information to the base station via PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on pre-configured rules. For example, the DCI may be a DCI for scheduling SLs. For example, the format of the DCI may be DCI format 3_0 or DCI format 3_1.

[0089] Referring to Figure 6(b), in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, the terminal can determine the SL transmission resource from the SL resources set by the base station / network or from the pre-configured SL resources. For example, the set SL resources or pre-configured SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can select resources from the configured resource pool and perform SL communication. For example, the terminal can perform sensing and resource (re)selection procedures and select resources from the selection window. For example, the sensing may be performed in units of subchannels. For example, in step S610, the first terminal that has selected resources from the resource pool can use those resources to perform PSCCH (e.g., SCI (Sidelink Control Information) or 1 st -stage SCI) can be transmitted to the second terminal. In stage S620, the first terminal can transmit a PSSCH (for example, 2) associated with the PSCCH. nd -Stage SCI, MAC PDU, data, etc. can be transmitted to the second terminal. In stage S630, the first terminal can receive PSFCH associated with PSCCH / PSSCH from the second terminal.

[0090] Referring to Figure 6(a) or (b), for example, the first terminal can transmit an SCI over the PSCCH to the second terminal. Alternatively, for example, the first terminal can transmit two consecutive SCIs (e.g., a 2-stage SCI) over the PSCCH and / or PSSCH to the second terminal. In this case, the second terminal can decode the two consecutive SCIs (e.g., a 2-stage SCI) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted over the PSCCH is 1 st SCI, 1st SCI, 1 st -stage SCI or 1 st -Stage SCI format, which can be called the SCI format, is transmitted over PSSCH. nd SCI, 2nd SCI, 2 nd-stage SCI or 2 nd - This can be called a stage SCI format. For example, 1 st -stage SCI format can include SCI format 1-A, 2 nd -The stage SCI format may include SCI format 2-A and / or SCI format 2-B.

[0091] The following describes an example of SCI format 1-A.

[0092] SCI format 1-A is PSSCH and 2 on PSSCH nd - Used for scheduling SCI stages

[0093] The following information will be transmitted using SCI Format 1-A.

[0094] - Priority - 3 bits

[0095] - Frequency resource allocation - When the value of the upper layer parameter sl-MaxNumPerReserve is set to 2, ceiling (log2(N SL subChannel (N SL subChannel +1) / 2)) bit: Otherwise, if the value of the upper layer parameter sl-MaxNumPerReserve is set to 3, ceiling log2(N SL subChannel (N SL subChannel +1)(2N SL subChannel +1) / 6) bits

[0096] - Time resource allocation - 5 bits if the value of the upper-layer parameter sl-MaxNumPerReserve is set to 2. Otherwise, Upper layer parameters If the value of sl-MaxNumPerReserve is set to 3, 9 bits

[0097] - Resource reservation cycle - ceiling (log2N rsv_period ) bits. Here, N rsv_period This is the number of entries in the upper-layer parameter sl-ResourceReservePeriodList, if the upper-layer parameter sl-MultiReserveResource is set. Otherwise, it is 0 bits.

[0098] - DMRS pattern - ceiling (log2N pattern ) bits, where N pattern This is the number of DMRS patterns set by the upper-level parameter sl-PSSCH-DMRS-TimePatternList.

[0099] - 2 nd -stage SCI format - 2 bits as defined in Table 5

[0100] - Beta_Offset Indicator - 2 bits as provided by the upper layer parameter sl-BetaOffsets2ndSCI

[0101] - Number of DMRS ports - 1 bit as defined in Table 6

[0102] - Modulation and coding scheme - 5-bit

[0103] - Additional MCS Table Indicator - 1 bit if one MCS table is set by the upper layer parameter sl-Additional-MCS-Table. 2 bits if two MCS tables are set by the upper layer parameter sl-Additional-MCS-Table. 0 bits otherwise.

[0104] - PSFCH overhead indicator - 1 bit if upper layer parameter sl-PSFCH-Period = 2 or 4, 0 bits otherwise

[0105] - Reserved bits - The number of bits determined by the upper layer parameter sl-NumReservedBits, which is set to 0.

[0106] [Table 5]

[0107] [Table 6]

[0108] The following describes an example of SCI format 2-A.

[0109] In HARQ operation, if the HARQ-ACK information contains either an ACK or a NACK, or if the HARQ-ACK information contains only a NACK, or if there is no feedback of the HARQ-ACK information, SCI format 2-A is used for decoding the PSSCH.

[0110] The following information will be transmitted via SCI Format 2-A.

[0111] - HARQ process number - 4 bits

[0112] - New data indicator - 1 bit

[0113] - Redundancy version - 2 bits

[0114] - Source ID - 8 bits

[0115] - Destination ID - 16 bits

[0116] - HARQ Feedback Enable / Disable Indicator - 1 bit

[0117] - Cast type indicator - 2 bits as defined in Table 7

[0118] - CSI request - 1 bit

[0119] [Table 7]

[0120] The following describes an example of SCI format 2-B. SCI format 2-B is used for decoding PSSCH and is used with HARQ operation when HARQ-ACK information contains only NACK or when there is no feedback of HARQ-ACK information.

[0121] The following information will be transmitted via SCI Format 2-B.

[0122] - HARQ process number - 4 bits

[0123] - New data indicator - 1 bit

[0124] - Redundancy version - 2-bit

[0125] - Source ID - 8 bits

[0126] - Destination ID - 16-bit

[0127] - HARQ Feedback Enable / Disable Indicator - 1 bit

[0128] - Zone ID - 12 bits

[0129] - Communication range requirements - 4 bits determined by the upper layer parameter sl-ZoneConfigMCR-Index

[0130] Referring to Figure 6(a) or (b), in step S630, the first terminal may receive the PSFCH. For example, the first and second terminals may determine the PSFCH resource, and the second terminal may use the PSFCH resource to send HARQ feedback to the first terminal.

[0131] Referring to Figure 6(a), in step S640, the first terminal can transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0132] Figure 7 shows three cast types relating to one embodiment of the present disclosure. The embodiment in Figure 7 can be combined with various embodiments of the present disclosure. Specifically, Figure 7(a) shows broadcast-type SL communication, Figure 7(b) shows unicast-type SL communication, and Figure 7(c) shows groupcast-type SL communication. In the case of unicast-type SL communication, a terminal can perform one-to-one communication with other terminals. In the case of groupcast-type SL communication, a terminal can perform SL communication with one or more terminals within the group to which it belongs. In various embodiments of the present disclosure, SL groupcast communication can be replaced with SL multicast communication, SL one-to-many communication, etc.

[0133] In this specification, the wording “configuration or definition” may be interpreted as “configuration (in advance) by a base station or network (via predefined signaling (e.g., SIB, MAC signaling, RRC signaling)). For example, “A can be configured” may include “the base station or network configures / defines or informs the terminal of A in advance.” Alternatively, the wording “configuration or definition” may be interpreted as “configuration or definition in advance by the system.” For example, “A can be configured” may include “A is configured / defined in advance by the system.”

[0134] Referring to standard documentation, some procedures and technical specifications related to this disclosure may be as follows:

[0135] [Table 8]

[0136] [Table 9]

[0137] [Table 10]

[0138] [Table 11]

[0139] On the other hand, NR V2X in Release 16 does not support power saving operation for terminals, but power saving operation for terminals (e.g., pedestrian terminals) is scheduled to be supported from Release 17 NR V2X onwards.

[0140] For example, you may need to define an SL DRX configuration for a terminal's power-saving operation (e.g., SL DRX operation).

[0141] Accordingly, embodiments of this disclosure define SL DRX settings for terminal power saving operations, and propose a method for enabling the terminal to smoothly perform SL DRX operations using the defined SL DRX settings. In the following description, "when, if, in case of" can be replaced with "based on".

[0142] In one embodiment of this disclosure, (Proposal 1.) a method is proposed to enable terminals to perform SL DRX operations using a common SL DRX configuration by defining a single default / common SL DRX configuration based on the QoS requirements of a V2X service or SL service (e.g., PCI (PC5 QoS flow identifier), PDB (packet delay budget)).

[0143] Figure 8 shows an embodiment of the basic / common SL DRX setting configuration according to one embodiment of the present disclosure. The embodiment in Figure 8 can be combined with various embodiments of the present disclosure.

[0144] Referring to Figure 8, an embodiment is shown in which a single basic / common SL DRX configuration is set for a terminal based on the QoS requirements (e.g., PQI, PDB) of a V2X service or SL service. First, (Step 1) the terminal's V2X layer may create SL DRX pattern (e.g., SL DRX cycle, SL DRX on-duration) information for the terminal's SL DRX operation (e.g., SL DRX cycle, SL DRX on-duration) based on the QoS requirements (e.g., PDB) of the V2X service generated in the application layer and transmit it to the AS layer, or generate and transmit an SL DRX configuration to the AS layer.

[0145] [Table 12]

[0146] Then, (Stage 2) the terminal's AS layer generates a basic / common SL DRX configuration based on the SL DRX pattern information received in the V2X layer ("SL DRX cycle and SL DRX duration length" or "SL DRX duration length and SL DRX off-duration length"), which can be used for SL DRX operation.

[0147] Then, (Step 3) the terminal can transmit to the base station QoS requirements information (PFI, PDB) for the terminal's V2X service and preferred basic / common SL DRX settings. For example, if steps 1 and 2 are omitted, only the QoS requirements information for the V2X service can be transmitted to the base station, and the base station can generate and inform the terminal of the common SL DRX settings to be used based on that information.

[0148] Then, (Stage 4) the terminal can perform SL DRX operation and sidelink transmission / reception using the common SL DRX settings transmitted from the base station.

[0149] In one embodiment of this disclosure, (Proposal 2.) if only one basic / common SL DRX configuration is permitted based on the QoS requirements (e.g., PQI, PDB) of a V2X service or SL service, a problem may arise where the probability of resource collisions between different terminals and the level of congestion / interference between terminals on the SL DRX onduration interval of the SL DRX configuration increase. Therefore, this disclosure proposes the following method to reduce the probability of resource collisions between different terminals on the SL DRX onduration interval of a common SL DRX configuration.

[0150] In one embodiment of the present disclosure, (Proposal 2.1) the probability of resource collisions between different terminals operating SL DRX can be reduced by defining the wake-up start time (SL DRX duration start time) or wake-up interval (SL DRX duration length) of a common SL DRX setting or the period in which the wake-up interval (e.g., SL DRX duration) of a common SL DRX setting is repeated (common SL DRX cycle) to be hopped or randomized based on parameters such as the application / service ID (and / or (L(layer)1 or L2) (source / destination ID).

[0151] In one embodiment of the present disclosure, (Proposal 2.2) a V2X or SL service / QoS may be allowed to have multiple common SL DRX settings, one of which may be randomly selected (or selected by the terminal implementation), or a common SL DRX setting with a relatively low interference level may be preferentially selected (or one of a common SL DRX setting below a predetermined service / QoS-specific threshold) based on the (past) measured interference level on the receiving slot associated with the wake interval (e.g., common SL DRX onduration) of the common SL DRX setting.

[0152] In one embodiment of this disclosure, in addition to randomizing the basic / common SL DRX settings (or basic / common SL DRX patterns) or SL DRX-related parameters included in the basic / common SL DRX settings (Proposal 3), when the conditions described in the proposal (e.g., the probability of resource collision between different terminals, situations where the degree of congestion / interference is high, when the probability of resource collision between different terminals exceeds a threshold, or when the degree of congestion / interference between different terminals exceeds a threshold) are met, a terminal may increase its SL DRX duration (or active time interval) or apply a pre-configured SL DRX timer value (e.g., a relatively large value) (e.g., an SL DRX timer included in the SL DRX settings referred to in this disclosure, or an SL DRX-related timer defined to support other SL DRX operations). (i.e., a form in which the time domain of candidate resources is increased in order to select resources with less interference).

[0153] In one embodiment of the present disclosure, (Proposal 4) when switching to another basic / common SL DRX setting (or basic / common SL DRX pattern) or SL DRX-related parameter included in a basic / common SL DRX setting, a congestion / interference level hysteresis may be set. For example, a terminal may be allowed to switch to a new common SL DRX setting or common SL DRX pattern or common SL DRX setting parameter only if the difference in congestion / interference levels on the existing / new setting or pattern is greater than a preset hysteresis value, and at the same time, the congestion / interference level on the new setting or pattern is lower than a preset threshold. Furthermore, switching to other settings or patterns may be configured to be permitted only when resource reselection is triggered, or when TB-related retransmissions are complete, or when the terminal is operating in long DRX mode, or when the terminal's timer expires, thereby operating on an SL on-duration basis.

[0154] In one embodiment of the present disclosure, (Proposal 5) if a high-priority / required service-related SL DRX onduration or active interval (an interval in which the terminal operates in an awake state to receive or transmit sidelink signals including SL DRX onduration) overlaps (partially) with a low-priority / required service-related SL DRX onduration or active interval, the (maximum, minimum, or average) transmit power value used for transmitting the low-priority / required service, the TB-related (maximum) retransmission count, the upper limit of the channel occupancy ratio (CR) value, etc., can be set to reduce interference to the high-priority / required service (within the overlapping interval).

[0155] In one embodiment of the present disclosure, (Proposal 6) when the zone area in which the terminal is located is changed (or when the zone ID in which the terminal is located is changed), randomization of the SL DRX operating parameters and timers / settings, patterns, and DRX operating parameter selections included in the common SL DRX settings / common SL DRX patterns / common SL DRX settings may be triggered or enabled.

[0156] In one embodiment of the present disclosure, (Proposal 7) when a terminal changes from an INC (in-coverage) state to an OOC (out-of-coverage) state, or when a terminal changes from an OOC state to an INC state, it is possible to trigger or allow randomization of the SL DRX operating parameters included in the common SL DRX setting / common SL DRX pattern / common SL DRX setting and the selection of DRX operating parameters included in the timer / setting, pattern, and setting.

[0157] In one embodiment of the present disclosure, (Proposal 8) when the cell ID on which the terminal is located changes, randomization of the selection of SL DRX operating parameters and timers / settings, patterns, and DRX operating parameters included in the common SL DRX setting / common SL DRX pattern / common SL DRX setting may be triggered or permitted.

[0158] In one embodiment of the present disclosure, (Proposal 9) when the carrier type of the terminal (e.g., licensed carrier, ITS-dedicated carrier) is changed, randomization of the SL DRX operating parameters and timer / settings, patterns, and DRX operating parameter selections included in the common SL DRX setting / common SL DRX pattern / common SL DRX setting may be triggered or permitted.

[0159] In one embodiment of the present disclosure, (Proposal 10) when the communication type / direction of the terminal (e.g., V2P, P2P, P2V) is changed, randomization of the SL DRX operating parameters and timers / settings, patterns, and DRX operating parameter selections included in the common SL DRX setting / common SL DRX pattern / common SL DRX setting may be triggered or permitted.

[0160] According to one embodiment of the present disclosure, (Proposal 11) when the remaining battery level of the terminal is changed, randomization of the selection of SL DRX operating parameters and timers / settings, patterns, and settings included in the common SL DRX setting / common SL DRX pattern / common SL DRX setting may be triggered or permitted.

[0161] According to one embodiment of this disclosure, (Proposal 12) V2X (or SL) service of a terminal If the ID / type is changed, randomization of the SL DRX operating parameters and timers / settings, patterns, and DRX operating parameter selections included in the common SL DRX settings / common SL DRX patterns / common SL DRX settings may be triggered or tolerated.

[0162] Furthermore, when (basic / common) SL DRX pattern / configuration information (e.g., SL DRX cycle, SL DRX duration interval information) is exchanged through higher-level signaling (e.g., MAC CE, PC5 RRC), a mechanism may be needed to ensure that terminals have a common understanding of the "(basic / common) SL DRX pattern / configuration start time (e.g., SL DRX duration start time)."

[0163] Accordingly, according to one embodiment of the present disclosure, (Proposal 13) the present disclosure proposes a method in which an SL DRX confirmation message (e.g., a message reporting SL DRX pattern / configuration information or an ACK message for an SL DRX pattern / configuration report message) is defined and the time at which the terminal receives it is considered a reference timing (e.g., the start of the SL DRX duration), or a reference timing is considered to be the time at which a reference timing is considered to be the time at which a pre-configured / exchanged slot offset value from a SYNC source-based DFN0 is applied.

[0164] In one embodiment of this disclosure (Proposal 14), the common SL DRX settings / parameters proposed in this disclosure may be DRX settings used in common with all terminals, regardless of the cast type (unicast, groupcast, or broadcast). Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings configured separately for a specific cast type (unicast, groupcast, or broadcast). Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings used in common by terminals belonging to (subscribing to) the same groupcast (groupcast services with the same groupcast destination L2 ID), the same unicast (unicasts with the same source L2 ID / destination L2 ID pair), or the same broadcast (broadcast services with the same broadcast destination L2 ID).

[0165] Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings configured separately for specific cast types (unicast, groupcast, or broadcast). For example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings commonly used by terminals interested in the same groupcast, unicast, or broadcast service. For example, terminals interested in the same groupcast, unicast, or broadcast service may be terminals that have not yet subscribed to or connected (in the case of unicast) the service of the relevant cast type, are interested in subscribing to the service of the relevant cast type, and are in a state to monitor the signal of the service. Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be terminal service-specific DRX settings commonly used by terminals.

[0166] In one embodiment of this disclosure, (Proposal 15) the common SL DRX settings / parameters proposed in this disclosure may be DRX settings used in common with all terminals, regardless of the cast type (unicast, groupcast, or broadcast). Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings configured separately for a specific cast type (unicast, groupcast, or broadcast). Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings used in common by terminals belonging to (subscribing to) the same groupcast, the same unicast, or the same broadcast service.

[0167] Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be DRX settings configured separately for specific cast types (unicast, groupcast, or broadcast). For example, the common SL DRX settings / parameters proposed in this disclosure may be common DRX settings used in common by terminals interested in the same groupcast, unicast, or broadcast service. For example, a terminal interested in the same groupcast, unicast, or broadcast service may be a terminal that has not yet subscribed to or connected (in the case of unicast) the service of the relevant cast type, is interested in subscribing to the service of the relevant cast type, and is in a state to monitor the signal of the service. Alternatively, for example, the common SL DRX settings / parameters proposed in this disclosure may be terminal service specific DRX settings used in common by terminals.

[0168] In one embodiment of the present disclosure, the common SL DRX setting used by terminals in common or the terminal service specific SL DRX setting used by terminals in common, as specified in Proposal 15, may be configured and set in the following combinations:

[0169] For example, (Method 1) Common SL DRX settings or terminal service specific SL DRX settings can be configured separately for each cast type (unicast service, groupcast service, or broadcast service).

[0170] For example, (Method 2) Common SL DRX settings or terminal service-specific SL DRX settings can be configured on a per-source / destination pair (a pair of source (L2 or LI ID) / destination (L2 or LI ID)).

[0171] For example, (Method 3) Common SL DRX settings or terminal service-specific SL DRX settings can be configured on a service-by-service (or PQI or PDB) basis.

[0172] For example, (Method 4) Common SL DRX settings or terminal service specific SL DRX settings can be configured on a service-by-service basis (or PSID (provider service identifier)).

[0173] For example, (Method 5) Common SL DRX settings or terminal service-specific SL DRX settings can be configured for each service (or PQI or PSID) and each cast type (unicast, groupcast, or broadcast) (or in combination).

[0174] For example, (Method 6) (for groupcast or broadcast) a common SL DRX setting or a terminal service-specific SL DRX setting may be configured per service (or PQI or PSID) per destination (groupcast ID or broadcast ID) (or in combination).

[0175] For example, since the destination L2ID can be used as an identifier to distinguish groupcast / broadcast services, a common SL DRX setting or a terminal service-specific SL DRX setting can be configured for each destination L2ID. In this case, a common SL DRX setting or a terminal service-specific SL DRX setting that reflects the PQI of the SL data can be configured for each destination.

[0176] For example, (Method 7) (for groupcast or broadcast) common SL DRX settings or terminal service-specific SL DRX settings can be configured per service (or PQI or PSID) source / destination pair (a pair of source (L2 or LI ID) / destination (L2 or LI ID)) (or in combination).

[0177] For example, since the destination L2ID can be used as an identifier to distinguish groupcast / broadcast services, a common SL DRX setting or a terminal service-specific SL DRX setting can be configured for each destination L2ID. In this case, a common SL DRX setting or a terminal service-specific SL DRX setting reflecting the PQI of the SL data can be configured for each pair of source L2ID / destination L2ID between the sending terminal that sends the groupcast / broadcast service and the terminal that receives the groupcast / broadcast service.

[0178] Furthermore, for example, a source L2 ID / destination L2 ID pair can be interpreted as follows:

[0179] For example, SL DRX settings can be DRX setting information applied by a receiving terminal that receives SL data. Therefore, from the perspective of the receiving terminal, the source L2ID can be the destination L2ID of the transmitting terminal, and the destination L2ID can be the source L2ID of the transmitting terminal. That is, for example, from the perspective of the receiving terminal, SL DRX settings can be set and used for each source L2ID / destination L2ID pair. Also, for example, a transmitting terminal can perform the role of a receiving terminal, receiving SL data transmitted by other terminals, just like a receiving terminal. That is, while the transmitting terminal is performing the role of a receiving terminal, SL DRX settings can be set and used for each source L2ID / destination L2ID pair. In other words, for each source L2ID / destination L2ID pair, SL DRX settings can be set and used according to the direction of reception / transmission of SL data (direction from the transmitting terminal to the receiving terminal, and direction from the receiving terminal to the transmitting terminal).

[0180] For example (Method 8) (in the case of unicast), a common SL DRX setting or a terminal service-specific SL DRX setting can be configured on a service-by-service (or PQI, or PSID) source / destination pair (a pair of source (L2 or LI ID) / destination (L2 or LI ID)) basis (or in combination).

[0181] For example, since a source L2ID / destination L2ID pair can be used as an identifier for a PC5 unicast link, a terminal service specific SL DRX setting can be configured for each PC5 unicast link or PC5RRC connection (source L2ID / destination L2ID pair). In this case, a terminal service specific SL DRX setting can be configured that reflects the PQI of the SL data transmitted and received between terminals in the PC5 unicast link or PC5RRC connection (source L2ID / destination L2ID pair).

[0182] Furthermore, for example, a source L2 ID / destination L2 ID pair can be interpreted as follows:

[0183] For example, SL DRX settings can be DRX setting information applied by a receiving terminal that receives SL data. Therefore, from the perspective of the receiving terminal, the source L2ID can be the destination L2ID of the transmitting terminal, and the destination L2ID can be the source L2ID of the transmitting terminal. That is, for example, from the perspective of the receiving terminal, SL DRX settings can be set and used for each source L2ID / destination L2ID pair. Also, for example, a transmitting terminal can also act as a receiving terminal, receiving SL data transmitted by other terminals. That is, while acting as a receiving terminal, a transmitting terminal can set and use SL DRX settings for each source L2ID / destination L2ID pair. In other words, SL DRX settings can be set and used for each source L2ID / destination L2ID pair according to the reception / transmission direction of the SL data (from transmitting terminal to receiving terminal, and from receiving terminal to transmitting terminal).

[0184] Alternatively, for example, (Method 9) the common SL DRX configuration or the terminal service-specific SL DRX configuration can be set to two or more combinations of the following: service (PQI, or PSID), source / destination pair (a pair of source (L2 or L1 ID) / destination (L2 or LI ID)), destination L1 or L2 ID, source L1 or L2 ID, cast type (unicast, groupcast, or broadcast), and PDB.

[0185] The basic / common SL DRX settings proposed in this disclosure may be SL DRX settings defined for the purpose of monitoring messages / data that are not associated with a service, and messages / data that do not have a QoS profile (e.g., PC5-S messages: PC5-S DCR (direct communication request), PC5-S DCA (direct communication accept), etc.).

[0186] Figure 9 illustrates a procedure in which a power-saving terminal performs wireless communication based on a basic SL DRX setting, according to one embodiment of the present disclosure. The embodiment of Figure 9 can be combined with various embodiments of the present disclosure.

[0187] Referring to Figure 9, in step S910, the transmitting and receiving terminals may obtain information regarding at least one SL DRX setting and a basic SL DRX setting associated with at least one QoS profile. For example, the at least one SL DRX setting may be related to the at least one QoS profile. For example, the basic SL DRX setting may be an SL DRX setting that the terminal can use for SL DRX operation in the various cases described herein.

[0188] In step S920, the transmitting terminal may generate a MAC PDU containing a DCR message. For example, the DCR message may not have an associated QoS profile. For example, the DCR message may be a message unrelated to any service.

[0189] In step S930A, the transmitting terminal may determine which of the at least one SL DRX setting and the basic SL DRX setting to use for SL DRX operation. For example, the transmitting terminal may decide to use the basic SL DRX setting based on the fact that the MAC PDU to be transmitted contains a DCR message. Alternatively, for example, the transmitting terminal may decide to use the basic SL DRX setting based on the fact that there is no QoS profile associated with the MAC PDU to be transmitted. Alternatively, for example, the transmitting terminal may decide to use the basic SL DRX setting based on the fact that the MAC PDU to be transmitted is not associated with any service. In step S930B, the receiving terminal may decide to perform SL DRX operation based on the basic SL DRX setting.

[0190] In step S940A, the transmitting terminal can transmit the MAC PDU based on the determined SL DRX setting. For example, the transmitting terminal may transmit the MAC PDU based on the SL DRX setting, based on the decision made in step S930A to use the basic SL DRX setting. In step S940B, The receiving terminal can receive the MAC PDU based on the basic SL DRX settings.

[0191] On the other hand, the NRV2X in Release 16 does not support terminal power saving operation, but it is planned that terminal power saving operation (for example, power saving terminals) will be supported from the NRV2X in Release 17 onwards.

[0192] This disclosure proposes a method for a terminal to select an SL DRX timer value based on SCI information in sidelink groupcasts and broadcasts. In the following description, "when, if, in case of" can be replaced with "based on".

[0193] Proposal 1. Method for selecting timer values

[0194] In one embodiment of this disclosure, if there are multiple PQI-based timer values ​​(e.g., duration timer value / inactivity timer value / retransmission timer value), the receiving terminal may select one timer value to use based on the SL priority included in the SCI. When the transmitting terminal has multiple flows for the same group cast / broadcast (same L2 destination ID for the group cast / broadcast) as the receiving terminal, the transmitting terminal can receive an SCI associated with each TB when it sends a TB for each flow. Furthermore, there may be multiple PQIs for the same group cast / broadcast (same L2 destination ID for the group cast / broadcast), and there may be SL DRX settings mapped to each PQI. In the following proposal, when the receiving terminal receives an SCI associated with TBs for multiple flows sent by the transmitting terminal, it is proposed that it selects the value of the SL DRX timer to use (e.g., SL DRX duration timer / inactivity timer / retransmission timer / HARQRTT timer) based on the information included in the SCI.

[0195] For example, a receiving terminal can determine which PQI is mapped to which SL priority by tracing the PQI backward based on the SL priority included in the SCI. Alternatively, for example, a receiving terminal can determine which single or multiple PQIs are mapped to a groupcast or broadcast L2 destination ID by checking the remaining destination ID of the groupcast or broadcast L1 destination ID and MAC subheader included in the SCI, and thus determine which SL DRX settings are mapped to which PQI. For example, if the PQI values ​​mapped to the priority included in each SCI are independent values, the receiving terminal can select the one with the highest SL priority and use the timer value of the SL DRX setting mapped to the PQI associated with that SL priority. Alternatively, the receiving terminal may select the PQI with the lowest (or highest) PQI index and select the timer value of the SL DRX setting associated with that PQI.

[0196] Alternatively, for example, a receiving terminal may determine the PQI mapped per SL priority by tracing the PQI backward based on the SL priority included in the SCI. Alternatively, for example, a receiving terminal may determine the single or multiple PQIs mapped to the groupcast or broadcast L2 destination ID by checking the groupcast or broadcast L1 destination ID included in the SCI and the remaining destination ID in the MAC subheader, and thus determine the SL DRX settings mapped per PQI. For example, if the PQI values ​​mapped to the SL priority included in each SCI are not independent values, but rather the same PQI values ​​are found together for a single SL priority (for example, PQI1 is associated with SL priority 1, PQI2 is associated with SL priority 2, and PQI1 is associated with SL priority 3), the terminal may select and use the longest timer value of the settings mapped to the duplicate PQI with the highest SL priority. Alternatively, the terminal may select and use the timer value of the SL DRX setting associated with the PQI with the highest SL priority. Alternatively, for example, the terminal can select the PQI with the lowest (or highest) PQI index and then select a timer value for the SL DRX setting linked to that PQI. Alternatively, for example, the terminal can select the highest SL priority and then select a timer value for the SL DRX setting linked to that priority.

[0197] Alternatively, for example, the terminal may select the longest (or shortest) timer value for the SL DRX configuration mapped to the PQI.

[0198] In one embodiment of the present disclosure, a receiving terminal receives an SCI but can select one of several PQIs mapped to the groupcast or broadcast L2 destination ID without using SL priority. For example, the receiving terminal can select the PQI with the highest priority among the mapped PQIs, independently of the received SCI. Here, the receiving terminal may select and use the SL DRX timer value of the SL DRX setting mapped to the selected PQI. This can be interpreted as the receiving terminal being able to select the SL DRX setting (e.g., SL DRX timer value) of a PQI that maps to a different SL priority value (e.g., priority "b") than the SL priority value (e.g., priority "a") indicated in the received SCI.

[0199] In one embodiment of the present disclosure, a method is proposed for transmitting an SCI that includes an index value mapped to a PQI value. For example, if there are multiple timer values ​​based on PQI (e.g., an on-duration timer value, an inactive timer value, a retransmission timer value), the receiving terminal can select one timer value to use based on the PQI index included in the SCI.

[0200] For example, the receiving terminal can select and use the timer value of the setting mapped to the PQI with the highest (or lowest) priority among the SL priorities mapped to each PQI index contained in each received SCI.

[0201] For example, if duplicate SL priorities are found among the SL priorities mapped to each PQI index contained in each received SCI, the receiving terminal can select and use the longest timer value among the settings mapped to each duplicate PQI that has the highest priority.

[0202] For example, if the PQI index values ​​included in each SCI are not independent values ​​but the same PQI values ​​are found together (e.g., PQI 1, PQI 2, PQI 1), the terminal can select a timer value for the SL DRX setting that maps to the PQI with the highest (or lowest) SL priority. Alternatively, for example, the terminal may select a timer value for the SL DRX setting that maps to the PQI with the highest (or lowest) SL priority for PQIs with the same PQI index. Alternatively, for example, the terminal may select and use a longer (or shorter) timer value for PQIs with the same PQI index and the same SL priority.

[0203] Alternatively, for example, a receiving terminal may select and use the longest (or shortest) timer value from among multiple SL DRX settings mapped to multiple PQIs.

[0204] In one embodiment of the present disclosure, the following operation is also proposed as an alternative method for selecting the values ​​of the SL DRX timers (e.g., duration timer / inactive timer / retransmission timer):

[0205] For example, if the terminal has multiple SL DRX timers mapped to multiple PQIs as a result of the aforementioned operation, the terminal can select all the values ​​of all the SL DRX timers mapped to each individual PQI and operate the SL DRX timers.

[0206] In one embodiment of this disclosure, the following operation is also proposed in a different manner.

[0207] For example, once a receiving terminal successfully completes decoding of sidelink data, it may derive the logical channel ID of the successfully decoded MAC PDU. This is because the MAC subheader contains the logical channel ID. Furthermore, the terminal may track the QoS profile (e.g., PQI or PFI) mapped to the logical channel via the obtained logical channel ID. If the successfully decoded MAC PDU is multiplexed only with SDUs corresponding to the same LC ID, the terminal can select the value of the SL DRX timer mapped to the PQI (e.g., QoS profile) derived based on the LC ID and operate the SL DRX timer accordingly.

[0208] Alternatively, for example, if a successfully decoded MAC PDU is MUXed with an SDU corresponding to multiple LC IDs, the terminal can select all values ​​of the SL DRX timer mapped to multiple PQIs (e.g., QoS profiles) derived based on the LC IDs and apply them to the SL DRX timer operation. Or, for example, if a successfully decoded MAC PDU is MUXed with an SDU corresponding to multiple LC IDs, the terminal can select the longest value among the SL DRX timer values ​​mapped to multiple PQIs (e.g., QoS profiles) derived based on the LC IDs and operate the SL DRX timer.

[0209] In one embodiment of this disclosure, the following operation is also proposed in a different manner:

[0210] For example, if a receiving terminal successfully decodes sidelink data, it can derive the 24-bit destination ID of the successfully decoded MAC PDU. Furthermore, the terminal can track the QoS profile (e.g., PQI or PFI) mapped to the acquired groupcast / broadcast 24-bit destination ID. This is possible because, since the groupcast / broadcast 24-bit L2 destination ID is generated based on the service ID, it is possible to derive a QoS profile (PQI) mapped to the groupcast / broadcast service via the groupcast / broadcast 24-bit L2 destination ID. For example, the terminal can select the derived QoS profile (PQI) and the corresponding SL DRX timer value to activate the SL DRX timer.

[0211] In one embodiment of the present disclosure, a receiving terminal may derive a linked QoS profile of a sidelink radio associated with a logical channel ID (logical null group ID) mapped to HARQ feedback enabled or disabled, according to the HARQ feedback mode (HARQ feedback enabled mode or HARQ feedback disabled mode) instructed via the SCI. A method is then proposed in which the terminal uses the derived QoS profile and the mapped SL DRX inactive timer (or SL DRX duration timer or SL DRX retransmission timer).

[0212] 2. Cycle Selection Method

[0213] In one embodiment of this disclosure, if multiple PQI-based DRX cycle values ​​exist, the receiving terminal may select one cycle value to use based on the SL priority contained in the SCI. For example, if a transmitting terminal has multiple flows (to the receiving terminal) for the same groupcast / broadcast (same L2 destination ID for the groupcast / broadcast), the receiving terminal may receive an SCI associated with each TB when a TB is transmitted for each flow. Furthermore, for example, there may be multiple PQIs for the same groupcast / broadcast (same L2 destination ID for the groupcast / broadcast), and there may be an SL DRX setting mapped to each PQI. The following proposal describes how, when a receiving terminal receives an SCI associated with TBs for multiple flows transmitted by a transmitting terminal, it selects the SL DRX cycle value to use based on the information contained in the SCI.

[0214] For example, a receiving terminal can trace back the PQIs based on the SL priority included in the received SCI, and if the PQIs mapped per SL priority are individual PQI values, the PDB can select and use the SL DRX cycle of the SL DRX setting mapped to the shortest (or longest) PQI. For example, the tracing operation could involve the receiving terminal checking the groupcast or broadcast L1 destination ID included in the SCI and the remaining destination ID in the MAC subheader, and checking the single or multiple PQIs mapped to the groupcast or broadcast L2 destination ID and the SL DRX settings mapped to each PQI. If, for example, multiple PQIs with the same PQI value are found, the terminal can select and use the SL DRX cycle of the SL DRX setting mapped to the shortest (or longest) PQI in the PDB.

[0215] Alternatively, for example, the receiving terminal can trace back the PQIs based on the SL priority included in the received SCI, and if the PQIs mapped to each SL priority are individual PQI values, it can select and use the SL DRX cycle of the SL DRX setting mapped to the highest (or lowest) priority PQI. For example, the tracing operation may involve the receiving terminal checking the groupcast or broadcast L1 destination ID included in the SCI and the remaining destination ID in the MAC subheader, and checking the single or multiple PQIs mapped to the groupcast or broadcast L2 destination ID and the SL DRX settings mapped to each of the PQIs.

[0216] Alternatively, for example, the receiving terminal can trace back the PQIs based on the SL priority included in the received SCI, and if there are duplicate PQIs among those mapped for each SL priority, it can select and use the SL DRX cycle of the SL DRX setting mapped to the highest (or lowest) priority PQI. For example, the said tracing operation could involve the receiving terminal checking the group cast or broadcast L1 destination ID and the remaining destination ID in the MAC subheader included in the SCI, and checking the single or multiple PQIs mapped to the group cast or broadcast L2 destination ID and the SL DRX setting mapped to each PQI. Alternatively, for example, if there are duplicate PQIs among those mapped per SL priority, the receiving terminal can select and use the SL DRX cycle of the SL DRX setting mapped to the PDB shortest (or longest) PQI (or select the one with the shortest SL DRX cycle value).

[0217] In one embodiment of the present disclosure, a method is proposed for transmitting an SCI including an index value mapped to a PQI value. For example, if there are multiple PQI-based DRX cycles, a receiving terminal can select one DRX cycle value to use based on the PQI index included in the SCI.

[0218] For example, the receiving terminal may select and use an SL DRX cycle with an SL DRX setting that maps to the shortest (or longest) PDB from among the PDBs mapped to each PQI index contained in each received SCI.

[0219] Alternatively, for example, the receiving terminal can select and use the shortest (or longest) DRX cycle of the SL DRX setting mapped to each PQI index contained in each received SCI.

[0220] Alternatively, for example, the receiving terminal may select and use the SL DRX cycle of the SL DRX setting mapped to the PQI with the highest priority (or longest duration) from among the SL priorities mapped to each PQI index contained in each received SCI.

[0221] The process proposed in this disclosure for a receiving terminal to select an SL DRX cycle value can be extended to operate based on information contained in an RRC message (a Uu RRC message sent by a base station to a terminal), or based on pre-configured information, after receiving an RRC message (a Uu RRC message sent by a base station to a terminal) that is not information-based, received from the SCI. For example, the information contained in the RRC message may include PQI index information mapped to a groupcast or broadcast L2 destination ID, SL priority information mapped to a groupcast or broadcast L2 destination ID, and SL DRX configuration information mapped to a PQI. To this end, a terminal performing SL groupcast / broadcast communication can transmit to the base station the groupcast or broadcast L2 destination ID, the PQI of the groupcast / broadcast flow, and SL priority information for the groupcast / broadcast service (or, the groupcast, or the broadcast L2 destination ID, and the SL DRX configuration / PQI of the groupcast / broadcast flow).

[0222] In one embodiment of this disclosure, another method for selecting the value of the SL DRX cycle is proposed, which is as follows:

[0223] For example, with the previously proposed operation, when there are values ​​for each SL DRX cycle mapped to multiple PQIs, the terminal can perform SL DRX operation by selecting / applying the values ​​of all SL DRX cycles mapped to each individual PQI. That is, for example, the terminal can perform active time (operation that monitors PSCCH / PSSCH, or operation that transmits PSCCH / PSSCH, active mode) operation / inactive time (operation that does not monitor PSCCH / PSSCH, or operation that does not transmit PSCCH / PSSCH, sleep mode) operation for all SL DRX cycles.

[0224] In one embodiment of this disclosure, the following operation is also proposed in a different manner.

[0225] For example, once a receiving terminal successfully completes decoding of sidelink data, the receiving terminal may derive the logical channel ID of the successfully decoded MAC PDU. This may be because the MAC subheader contains the logical channel ID. Alternatively, the terminal may track the QoS profile (e.g., PQI or PFI) mapped to the logical channel via the acquired logical channel ID. For example, if the successfully decoded MAC PDU is muxed with only SDUs corresponding to the same LC ID, the terminal can select the value of the SL DRX cycle mapped to the PQI (e.g., QoS profile) derived based on the LC ID to operate the SL DRX timer. If the successfully decoded MAC PDU is muxed with SDUs corresponding to multiple LC IDs, the terminal can select all the values ​​of the SL DRX cycle mapped to the multiple PQIs (e.g., QoS profiles) derived based on the LC ID and apply them to the SL DRX operation. In other words, for example, a terminal can perform active time (monitoring or transmitting PSCCH / PSSCH, active mode) or inactive time (not monitoring or transmitting PSCCH / PSSCH, sleep mode) operations for every SL DRX cycle. Alternatively, for example, if a successfully decoded MAC PDU is MUXed with SDUs corresponding to multiple LCIDs, the terminal is mapped to multiple PQIs (e.g., QoS profiles) derived based on the LCIDs. The longest value among the SL DRX cycle values ​​can be selected to operate SL DRX.

[0226] In one embodiment of this disclosure, the following operation is also proposed in a different manner:

[0227] For example, once the receiving terminal successfully completes decoding of the sidelink data, it may derive the 24-bit destination ID of the successfully decoded MAC PDU. Alternatively, the terminal may track a QoS profile (e.g., PQI or PFI) mapped to the acquired Groupcast / Broadcast 24-bit destination ID. This is possible because, for example, the Groupcast / Broadcast 24-bit L2 destination ID is generated based on the service ID, making it possible to derive a QoS profile (PQI) mapped to the Groupcast / Broadcast service via the Groupcast / Broadcast 24-bit L2 destination ID. For example, the terminal may select SL DRX cycle values ​​mapped to the derived QoS profile (PQI) to operate the SL DRX.

[0228] In one embodiment of this disclosure, a method is proposed in which a receiving terminal selects the value of the SL DRX timer and the value of the SL DRX cycle based on the following information.

[0229] i) 24-bit L2 destination ID for groupcast / broadcast

[0230] ii) 16-bit L1 destination ID in SCI for group cast / broadcast

[0231] iii) The remaining 8 bits of the destination ID for groupcast / broadcast within the MAC subheader.

[0232] Iv) PQI

[0233] v)SL priority

[0234] vi) PQI and mapped SL DRX configuration

[0235] In one embodiment of the present disclosure, when there are multiple SL DRX cycles mapped to multiple QoS profiles associated with the same L2 destination ID, the receiving terminal can select one SL DRX cycle to apply SL DRX operation to. In this case, for example, the present disclosure proposes a method in which the receiving terminal derives the least common multiple of multiple SL DRX cycle values ​​and applies the derived least common multiple as the SL DRX cycle.

[0236] For example, multiple cycles may have an inclusion (or subset) relationship with one another, or the shortest cycle (and / or a least common multiple-based cycle derived from multiple cycles) may contain the longest cycle (or all the remaining cycles) (and / or the shortest cycle (and / or a least common multiple-based cycle derived from multiple cycles) may contain the longest cycle (or all the remaining cycles) as a subset). Here, for example, multiple cycles may be interpreted as multiple QoS profile-related cycles linked to a single (L2 or L1) destination ID (and / or source ID).

[0237] For example, the proposed solution in this disclosure can be extended to HARQ feedback-enabled and HARQ feedback-disabled transmissions as follows:

[0238] In other words, for example, if a receiving terminal selects an SL DRX timer value via the method proposed in this disclosure, and the receiving terminal confirms a HARQ feedback-allowed transmission via SCI, the receiving terminal is proposed to extend the timer value by the HARQ RTT time from the selected timer value and apply it.

[0239] This disclosure proposes a method from the perspective of the operation of the receiving terminal. The values ​​of the SL DRX timer and SL DRX cycle used by the receiving terminal as proposed in this disclosure. The procedure for selecting the values ​​is to synchronize with the procedure for selecting the SL DRX timer and SL DRX cycle values ​​used by the receiving terminal (SL DRX operation synchronization). To achieve this synchronization, the transmitting terminal also performs the same procedure (information base included in the transmitted SCI: SL priority, PQI index, or PQI information base mapped to the L2 destination ID included in the transmitted SCI).

[0240] The SL DRX configuration referred to in this disclosure may include one or more of the following parameters:

[0241] [Table 13]

[0242] For example, the following SL DRX timers mentioned in this disclosure may be used for the following applications:

[0243] SL DRX On-Duration Timer: Indicates the period during which a terminal performing SL DRX operation must operate in an active time mode in order to receive PSCCH / PSSCH signals from the other terminal.

[0244] SL DRX Inactivity Timer: This can represent a period that extends the SL DRX duration period, which is the period during which a terminal performing SL DRX operation must essentially operate in active time to receive PSCCH / PSSCH from the other terminal. In other words, the SL DRX duration timer can be extended only by the SL DRX inactivity timer period. Also, when a terminal receives a PSCCH (first SCI and / or second SCI) for a new TB from the other terminal or receives a new packet (new PSSCH transmission), the terminal may extend the SL DRX duration timer by starting the SL DRX inactivity timer.

[0245] SL DRX HARQ RTT Timer: This can indicate a period in which a terminal performing SL DRX operation will operate in sleep mode until it receives a retransmitted packet (or PSSCH assignment) from the other terminal. In other words, when a terminal starts the SL DRX HARQ RTT timer, it can determine that the other terminal will not send it SL retransmitted packets until the SL DRX HARQ RTT timer expires, and can operate in sleep mode during that timer. Alternatively, the terminal may not monitor the SL channels / signals transmitted by the other terminal until the SL DRX HARQ RTT timer expires.

[0246] SL DRX Retransmission Timer: This can indicate a period of time during which a terminal performing SL DRX operation operates to receive retransmission packets (or PSSCH assignments) transmitted by the other terminal. For example, when the SL DRX HARQRTT timer expires, the SL DRX retransmission timer may be started. During this timer period, the terminal may monitor for the reception of retransmission SL packets (or PSSCH assignments) transmitted by the other terminal.

[0247] In the following explanation, the timer names (SL DRX Ondulation Timer, SL DRX Inactive Timer, SL DRX HARQ RTT Timer, SL DRX Retransmission Timer, etc.) are illustrative examples, and timers that perform the same / similar functions based on the content described for each timer can be considered the same / similar timers regardless of their names.

[0248] The proposed solution in this disclosure is also applicable and extendable as a way to solve the problem of loss caused by interference that occurs during Uu BWP (bandwidth part) switching.

[0249] Furthermore, this solution can be applied and extended to address the problem of data loss caused by interference during SLBWP switching, for example, when a terminal supports multiple SLs (Single Line Batteries).

[0250] The proposals in this disclosure can be extended to include not only the parameters (and timers) included in the default / common SL DRX configuration or the default / common SL DRX pattern or the default / common SL DRX configuration, but also the parameters (and timers) included in the pair-specific SL DRX configuration or the pair-specific SL DRX pattern or the pair-specific SL DRX configuration.

[0251] Furthermore, for example, the onduration term used in the proposals of this disclosure may be extended to include active time intervals, and the offduration term may be extended to include sleep time intervals. For example, active time may mean the interval in which the terminal operates in a wake-up state (with the RF module turned on) to receive / transmit radio signals. For example, sleep time may mean the interval in which the terminal operates in sleep mode (with the RF module turned off) for power saving. For example, even during sleep time intervals, the transmitting terminal is not obligated to operate in sleep mode. That is, if necessary, even during sleep time intervals, the terminal may be allowed to operate in active time for a while to perform sensing / transmitting operations.

[0252] Furthermore, for example, the applicability of (partially) proposed schemes / rules and / or related parameters (e.g., thresholds) of this disclosure may be set specifically (or differently or independently) depending on the resource pool, congestion level, service priority (and / or type), QoS requirements (e.g., delay, reliability) or PQI, traffic type (e.g., (non)periodic generation), SL transport resource allocation mode (mode 1, mode 2), etc.

[0253] For example, whether the proposed rules of the present disclosure are applicable (and / or related parameter setting values) depends on the resource pool (e.g., the resource pool with PSFCH set, the resource pool without PSFCH set), service / packet type (and / or priority), QoS profile, or QoS requirements (e.g., URLLC / EMBB traffic, reliability, latency), PQI, PFI, cast type (e.g., unicast, group cast, broadcast), (resource pool) congestion level (e.g., CBR), SL HARQ feedback method (e.g., NACK Only feedback, ACK / NACK feedback), HARQ feedback enabled MAC PDU (and / or HARQ feedback disabled MAC PDU) transmission, whether PUCCH-based SL HARQ feedback reporting operation can be set, pre-emption (and / or re-evaluation) (non-)execution (or, base resource reselection), (L2 or L1) (source and / or destination) identifier, (L2 or L1) (combination of source layer ID and destination layer ID) identifier, (L2 or L1) (pair of source layer ID and destination layer ID, and combination of cast type) identifier, direction of the pair of source layer ID and destination layer ID, PC5 RRC connection / ring·SL DRX (non-)execution (or support), SL mode type (resource allocation mode 1, resource allocation mode 2), (non-)periodic resource reservation execution, Tx profile (e.g., Tx profile indicating that the service supports SL DRX operation, Tx profile indicating that the service may not support SL DRX operation), and can be specifically (and / or, independently and / or, differently) set for at least one of them.

[0254] For example, the fixed time term mentioned in the proposal of the present disclosure can indicate the time when the terminal operates in an active time for a predefined time for receiving an SL signal or SL data from a peer terminal, or the time when the terminal operates in an active time for a time or a specific timer (SL DRX retransmission timer, SL DRX inactive timer, or a timer that guarantees the terminal can operate in an active time in the DRX operation of the receiving terminal).

[0255] Furthermore, for example, the applicability of the proposal and proposal rules of the present disclosure (and / or related parameter setting values) can also be applied to mmWave SL operations.

[0256] FIG. 10 shows the procedure for a first device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure.

[0257] Referring to Figure 10, in step S1010, the first device can obtain information regarding the SL (sidelink) DRX (discontinuous reception) setting associated with at least one QoS (quality of service) profile and information regarding the default SL DRX setting. In step S1020, the first device can generate a MAC (medium access control) PDU (protocol data unit) related to SL communication. In step S1030, the first device can determine the SL DRX setting for the SL communication. For example, based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting may be determined as the SL DRX setting for the SL communication. In step S1040, based on the active time of the SL DRX setting for the SL communication, the first device can transmit SCI (sidelink control information) for scheduling the PSSCH (physical sidelink shared channel) to the second device via the PSCCH (physical sidelink control channel). In step S1050, the first device can transmit the MAC PDU to the second device via the PSSCH based on the active time.

[0258] For example, a QoS profile associated with the MAC PDU may exist.

[0259] For example, a QoS profile associated with the MAC PDU may not exist.

[0260] For example, based on the fact that the MAC PDU is related to data for a groupcast service or broadcast service, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0261] For example, based on the fact that the MAC PDU is related to a control signal for establishing a unicast connection that is not related to data for a groupcast service or broadcast service, the basic SL DRX setting can be determined in the SL DRX setting for SL communication.

[0262] For example, based on the fact that the MAC includes a DCR (direct communication request) message, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0263] For example, based on the fact that the MAC PDU is not mapped to a QoS profile, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0264] For example, the QoS profile associated with the MAC PDU is a first QoS profile mapped to the MAC PDU, and the first QoS profile may not be mapped to the SL DRX configuration.

[0265] For example, the parameters within the basic SL DRX configuration may be randomized, and this randomization of the parameters within the basic SL DRX configuration may be performed based on a change in the zone ID in which the first device is located.

[0266] For example, the parameters within the basic SL DRX configuration may be randomized, and this randomization of the parameters within the basic SL DRX configuration may be performed based on whether or not the first device is in coverage.

[0267] For example, the parameters within the basic SL DRX configuration can be randomized, and this randomization of the parameters within the basic SL DRX configuration can be performed based on a change in the service ID of the first device.

[0268] For example, the parameters in the basic SL DRX setting may be randomized, and the randomization of the parameters in the basic SL DRX setting may be performed based on the remaining battery power of the first device.

[0269] For example, the parameters within the basic SL DRX configuration may be randomized, and this randomization of the parameters within the basic SL DRX configuration may be performed based on a change in the type or direction of the SL communication.

[0270] The embodiments described above can be applied to various devices described below. First, the processor 102 of the first device 100 has at least one QoS (quality of service) Information regarding the SL (sidelink) DRX (discontinuous reception) setting associated with the profile and information regarding the default SL DRX setting can be obtained. The processor W2 of the first device 100 can then determine the SL DRX setting for the SL communication. For example, the default SL DRX setting may be determined as the SL DRX setting for the SL communication based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU. The processor 102 of the first device 100 can then control the transceiver 106 to transmit SCI (sidelink control information) to the second device 200 via the PSCCH (physical sidelink control channel) for scheduling of the PSSCH (physical sidelink shared channel) based on the active time of the SL DRX setting for the SL communication. The processor 102 of the first device 100 can then control the transceiver 106 to transmit the MAC PDU to the second device 200 via the PSSCH based on the active time.

[0271] According to one embodiment of the present disclosure, a first device for performing wireless communication can be provided. For example, the first device may include one or more memories for storing instruction words, one or more transceivers, and one or more processors connecting the one or more memories and the one or more transceivers. For example, one or more processors execute the instruction word, obtain information regarding the SL (sidelink) DRX (discontinuous reception) setting and the default SL DRX setting associated with at least one QoS (quality of service) profile, generate a MAC (medium access control) PDU (protocol data unit) associated with SL communication, and determine the SL DRX setting for SL communication. However, based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for SL communication. Based on the active time of the SL DRX setting for SL communication, the SCI (sidelink control information) for scheduling the PSSCH (physical sidelink shared channel) is sent to the second device via the PSCCH (physical sidelink control channel), and the MAC PDU is sent to the second device via the PSSCH based on the active time.

[0272] For example, a QoS profile associated with the MAC PDU may exist.

[0273] For example, a QoS profile associated with the aforementioned MAC PDU may not exist.

[0274] For example, based on the fact that the MAC PDU is related to data for a groupcast service or broadcast service, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0275] For example, based on the basic SL DRX setting being related to a control signal for setting up a unicast connection that is not related to data for a group cast service or a broadcast service, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0276] For example, based on the MAC including a DCR (direct communication request) message, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0277] For example, based on the MAC PDU not being mapped to a QoS profile, the basic SL DRX setting may be determined as the SL DRX setting for the SL communication.

[0278] For example, the QoS profile related to the MAC PDU is a first QoS profile mapped to the MAC PDU, and the first QoS profile may not be mapped to the SL DRX setting.

[0279] For example, the parameters within the basic SL DRX setting are randomized, and the randomization of the parameters within the basic SL DRX setting may be performed based on a change in the zone ID where the first device is located.

[0280] For example, the parameters within the basic SL DRX setting are randomized, and the randomization of the parameters within the basic SL DRX setting may be performed based on a change in whether the first device is in coverage.

[0281] For example, the parameters within the basic SL DRX setting are randomized, and the randomization of the parameters within the basic SL DRX setting may be performed based on a change in the service ID of the first device.

[0282] For example, the parameters within the basic SL DRX setting may be randomized, and the randomization of the parameters within the basic SL DRX setting may be performed based on the remaining battery of the first device.

[0283] For example, the parameters within the basic SL DRX configuration may be randomized, and this randomization of the parameters within the basic SL DRX configuration may be performed based on a change in the type or direction of the SL communication.

[0284] According to one embodiment of the present disclosure, an apparatus configured to control a first terminal can be provided. For example, the apparatus may include one or more processors and one or more memories executablely connected by the one or more processors and for storing instructions. For example, one or more processors execute the instruction word, obtain information regarding the SL (sidelink) DRX (discontinuous reception) setting and the default SL DRX setting associated with at least one QoS (quality of service) profile, generate a MAC (medium access control) PDU (protocol data unit) associated with SL communication, and determine the SL DRX setting for SL communication. However, based on the fact that there is no SL DRX setting mapped to the QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for SL communication. Based on the active time of the SL DRX setting for SL communication, the SCI (sidelink control information)# for scheduling the PSSCH (physical sidelink shared channel) can be sent via the second terminal PSCCH (physical sidelink control channel), and based on the active time, the MAC PDU can be sent to the second terminal via the PSSCH#.

[0285] In one embodiment of the present disclosure, a non-temporary computer-readable storage medium recording instructions can be provided. For example, when executed, the instructions cause a first device to obtain information regarding a sidelink DRX (discontinuous reception) setting and a default SL DRX setting associated with at least one quality of service (QoS) profile, generate a medium access control (MAC) PDU (protocol data unit) associated with SL communication, and determine the SL DRX setting for the SL communication, but based on the absence of an SL DRX setting mapped to a QoS profile associated with the MAC PDU, the default SL DRX setting is determined as the SL DRX setting for the SL communication, and based on the active time of the SL DRX setting for SL communication, the instructions send sidelink control information (SCI) for scheduling a physical sidelink shared channel (PSSCH) to a second device via a physical sidelink control channel (PSCCH), and based on the active time, the instructions send the MAC PDU to the second device via the PSSCH.

[0286] Figure 11 illustrates a procedure in which a second device performs wireless communication according to one embodiment of the present disclosure. The embodiment in Figure 11 can be combined with various embodiments of the present disclosure.

[0287] Referring to Figure 11, in step S1110, the second device can obtain information regarding the SL (sidelink) DRX (discontinuous reception) setting associated with at least one QoS (quality of service) profile and information regarding the default SL DRX setting. In step S1120, the second device can receive SCI (sidelink control information) for scheduling the PSSCH (physical sidelink shared channel) via the PSCCH (physical sidelink control channel) from the first device based on the active time of the default SL setting. In step S1130, the second device can receive a MAC (medium access control) PDU (protocol data unit) via the PSSCH# from the first device based on the active time. For example, the MAC PDU may be received based on the active time of the default SL DRX setting, based on the fact that there is no SL DRX setting mapped to the QoS profile associated with the MAC PDU.

[0288] For example, the QoS profile associated with the MAC PDU is a first QoS profile mapped to the MAC PDU, and based on the fact that the first QoS profile is not mapped to the SL DRX configuration, the MAC PDU can be received based on the active time of the basic SL DRX configuration.

[0289] The embodiments described above can be applied to various devices described below. First, the processor 202 of the second device 200 can obtain information regarding a sidelink DRX (discontinuous reception) setting associated with at least one QoS (quality of service) profile and information regarding a basic (default) SL DRX setting. In step S1120, the processor 202 of the second device 200 can control the transceiver 206 to receive SCI (sidelink control information)# for scheduling the PSSCH (physical sidelink shared channel) from the first device W0 via the PSCCH (physical sidelink control channel) based on the active time of the basic SL DRX setting. In step S1130, the processor 202 of the second device 200 can control the transceiver 206 to receive a MAC (medium access control) PDU (protocol data unit) from the first device W0 via the PSSCH based on the active time. For example, the MAC PDU may be received based on the active time of the base SL DRX setting, based on the absence of an SL DRX setting mapped to the QoS profile associated with the MAC PDU.

[0290] According to one embodiment of the present disclosure, a second device for performing wireless communication can be provided. For example, the second device may include one or more memories for storing instruction words, one or more transceivers, and one or more processors connecting the one or more memories and the one or more transceivers. For example, the one or more processors execute instruction words and are associated with at least one QoS (quality of service) profile. Information regarding SL (sidelink) DRX (discontinuous reception) settings and information regarding the default SL DRX settings is obtained, and based on the active time of the default SL DRX setting, from the first device The system receives SCI (sidelink control information) for scheduling the PSSCH (physical sidelink shared channel) via the PSCCH (physical sidelink control channel), and based on the active time, it receives a MAC (medium access control) PDU (protocol data unit) from the first device via the PSSCH#, and the MAC PDU can be received based on the active time of the basic SL DRX setting, since there is no SL DRX setting mapped to the QoS profile associated with the MAC PDU.

[0291] For example, the QoS profile associated with the MAC PDU is a first QoS profile mapped to the MAC PDU, and based on the fact that the first QoS profile is not mapped to the SL DRX setting, the MAC PDU can be received based on the active time of the basic SL DRX setting.

[0292] The various embodiments of this disclosure can be combined with each other.

[0293] The following describes devices to which various embodiments of this disclosure can be applied.

[0294] Without limiting itself, the various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document can be applied to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.

[0295] The following will provide more specific examples with reference to the drawings. In the following drawings / descriptions, the same drawing reference numerals may illustrate the same or corresponding hardware blocks, software blocks, or functional blocks unless otherwise specified.

[0296] Figure 12 shows a communication system 1 according to one embodiment of the present disclosure. The embodiment in Figure 12 can be combined with various embodiments of the present disclosure.

[0297] Referring to Figure 12, the communication system 1 to which various embodiments of this disclosure apply includes wireless equipment, base stations, and networks. Here, wireless equipment means equipment that performs communication using wireless connectivity technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)), and is referred to as communication / wireless / 5G equipment. However, wireless equipment can also include, but is not limited to, robots 100a, vehicles 100b-1, 100b-2, XR (eXtended Reality) equipment 100c, handheld devices 100d, home appliances 100e, IoT (Internet of Things) equipment 100f, and AI equipment / servers 400. For example, vehicles can include vehicles equipped with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Here, vehicles can also include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and can be embodied in forms such as HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, and robots. Portable devices can include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., notebooks). Home appliances can include TVs, refrigerators, and washing machines. IoT devices can include sensors and smart meters. For example, base stations and networks can be embodied in wireless devices, and specific wireless devices 200a can also operate as base stations / network nodes for other wireless devices.

[0298] Here, the wireless communication technologies implemented in the wireless devices 100a to 100f of this specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology and can be implemented as standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names mentioned above. Furthermore, or generally, the wireless communication technologies implemented in the wireless devices 100a to 100f of this specification can communicate based on LTE-M technology. In this case, for example, LTE-M technology is an example of LPWAN technology and is called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented in 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 names mentioned above. Furthermore, the wireless communication technologies implemented in the wireless devices 100a to 100f of this specification may include, or generally may not include, at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which take low-power communication into consideration. For example, Zigbee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and is known by various names.

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

[0300] Wireless communication / connection 150a, 150b, and 150c can be performed between wireless devices 100a to 100f and base stations 200, and between base stations 200. Here, wireless communication / connection can be performed via uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, IAB (Integrated Access Backhaul), or various other wireless connectivity technologies (e.g., 5G NR)). Wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals from each other via wireless communication / connection 150a, 150b, and 150c. For example, wireless communication / connection 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, at least some of the following can be performed based on the various proposals of this disclosure: 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.

[0301] Figure 13 shows a wireless device according to one embodiment of the present disclosure. The embodiment in Figure 13 can be combined with various embodiments of the present disclosure.

[0302] Referring to Figure 13, the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals via various wireless connectivity technologies (e.g., LTE, NR). Here, {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 Figure 17.

[0303] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memories 104 and / or the transceivers 106 and be configured to embody 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 a first information / signal, and then transmit a wireless signal containing the first information / signal via the transceiver 106. Alternatively, the processor 102 may receive a wireless signal containing a 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 linked to the processor 102 and may store various information related to the operation of the processor 102. For example, memory 104 may store software code that executes some or all of the processes controlled by processor 102, or that includes instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. Here, processor 102 and memory 104 are part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 106 may be coupled with processor 102 and may transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be used in combination with an RF (Radio Frequency) unit. In this disclosure, wireless equipment may also mean a communication modem / circuit / chip.

[0304] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memories 204 and / or the transceivers 206 and be configured to embody 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 a third information / signal, and then transmit a wireless signal containing the third information / signal via the transceiver 206. Alternatively, the processor 202 may receive a wireless signal containing a 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 linked to the processor 202 and may store various information related to the operation of the processor 202. For example, memory 204 may store software code that executes some or all of the processes controlled by processor 202, or that includes instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. Here, processor 202 and memory 204 are part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 206 may be coupled with processor 202 and may transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver and may be used in combination with an RF unit. In this disclosure, wireless equipment may also mean a communication modem / circuit / chip.

[0305] The hardware elements of wireless devices 100 and 200 will be described in more detail below. However, one or more protocol layers can be embodied by one or more processors 102 and 202. For example, one or more processors 102 and 202 can embodied one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 can generate messages, control information, data, or information by means of the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. One or more processors 102, 202 can generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by means of the functions, procedures, suggestions, and / or methods disclosed in this document and provide them to one or more transceivers 106, 206. One or more processors 102, 202 can receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and can acquire PDUs, SDUs, messages, control information, data, or information by means of the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this document.

[0306] One or more processors 102, 202 are referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 can be embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be implemented by one or more processors 102, 202, or stored in one or more memories 104, 204 and driven by one or more processors 102, 202, with firmware or software configured to execute them. 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 sets of instructions.

[0307] One or more memories 104, 204 can be connected to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104, 204 can consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer read storage media and / or combinations thereof. One or more memories 104, 204 can be located inside and / or outside of one or more processors 102, 202. Furthermore, one or more memories 104, 204 can be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0308] One or more transceivers 106, 206 may transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or operational flowcharts, etc., described herein to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, radio signals / channels, etc., as referred to 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 may be connected to one or more processors 102, 202, and may transmit and receive radio signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. Furthermore, one or more transceivers 106, 206 can be connected to one or more antennas 108, 208 and configured to transmit and receive user data, control information, radio signals / channels, etc., as 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 be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 can convert received user data, control information, 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 can convert user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0309] Figure 14 shows a signal processing circuit for a transmitted signal according to one embodiment of the present disclosure. The embodiment in Figure 14 can be combined with various embodiments of the present disclosure.

[0310] Referring to Figure 14, the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. However, it is not limited to these, and the operation / function of Figure 14 can be performed by the processors 102, 202 and / or transceivers 106, 206 of Figure 13. The hardware elements of Figure 14 can be embodied by the processors 102, 202 and / or transceivers 106, 206 of Figure 13. For example, blocks 1010-1060 can be embodied by the processors 102, 202 of Figure 13. Also, blocks 1010-1050 can be embodied by the processors 102, 202 of Figure 13, and block 1060 can be embodied by the transceivers 106, 206 of Figure 13.

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

[0312] Specifically, the codeword can be converted into a scrambled bit sequence by the scrambler 1010. The scrambled sequence used for scrambling is generated based on an initialization value, which may include the ID information of the radio equipment. The scrambled bit sequence can be modulated into a modulated symbol sequence by the modulator 1020. The modulation scheme can include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulated symbol sequence can be mapped to one or more transmission layers by the layer mapper 1030. The modulated symbol of each transmission layer can be mapped to the corresponding antenna port (ra) 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. The precoder 1040 may perform precoding after performing transform precoding (e.g., DFT transformation) for the complex modulation symbols. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

[0313] The resource mapper 1050 can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource may include multiple symbols in the time domain (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) and multiple subcarriers in the frequency domain. The signal generator 1060 generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices via each antenna. To this end, the signal generator 1060 may include an IFFT (Inverse Fast Fourier Transform) module, a CP (Cyclic Prefix) inserter, a DAC (Digital-to-Analog Converter), a frequency uplink converter, and the like.

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

[0315] Figure 15 shows a wireless device according to one embodiment of the present disclosure. The wireless device can be implemented in a variety of forms depending on the use-example / service (see Figure 12). The embodiment in Figure 15 can be combined with various embodiments of the present disclosure.

[0316] Referring to Figure 15, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 in Figure 13 and can be composed of 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 transceivers (etc.) 114. For example, the communication circuit 112 may include one or more processors 102, 202 and / or one or more memories 104, 204 in Figure 13. For example, the transceivers (etc.) 114 may include one or more transceivers 106, 206 and / or one or more antennas 108, 208 in Figure 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 various operations of the wireless device. For example, the control unit 120 can control the electrical / mechanical operation of the wireless device based on the program / code / instructions / information stored in the memory unit 130. The control unit 120 can also transmit the information stored in the memory unit 130 to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit 110, or store information received from an external device (e.g., another communication device) via a wireless / wired interface through the communication unit 110 in the memory unit 130.

[0317] The additional element 140 can be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include at least one of the following: a power unit / battery, an input / output unit (I / O unit), a drive unit, and a computing unit. However, wireless devices can be embodied in forms such as robots (100a in Figure 12), vehicles (100b-1, 100b-2 in Figure 12), XR devices (100c in Figure 12), mobile devices (100d in Figure 12), home appliances (100e in Figure 12), IoT devices (100f in Figure 12), digital broadcasting terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, AI servers / devices (400 in Figure 12), base stations (200 in Figure 12), and network nodes. Depending on the use-example / service, wireless devices may be mobile or used in a fixed location.

[0318] In Figure 15, the various elements, components, units / parts, and / or modules within the wireless devices 100 and 200 can be interconnected as a whole via a wired interface, or at least some of them can 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 can be connected via a wired interface, and the control unit 120 and the first units (e.g., 130, 140) can be connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / part, and / or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may consist of a collection of one or more processors. For example, the control unit 120 may consist of a collection of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processing processor, a memory control processor, and so on. As another example, the memory unit 130 may consist of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0319] The following provides a more detailed explanation of the example shown in Figure 15, with reference to other drawings.

[0320] Figure 16 shows a portable device according to one embodiment of the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glass), or a portable computer (e.g., a laptop computer). The portable device may be referred to as MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), or WT (Wireless terminal). The embodiment in Figure 16 can be combined with various embodiments of the present disclosure.

[0321] Referring to Figure 16, the 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 composed of a part of the communication unit 110. Blocks 110-130 / 140a-140c correspond to blocks 110-130 / 140 in Figure 15, respectively.

[0322] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) with 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 may include an AP (Application Processor). The memory unit 130 can store data / parameters / programs / code / instructions necessary to operate the portable device 100. The memory unit 130 may also store input / output data / information, etc. The power supply unit 140a supplies power to the portable device 100 and may include wired / wireless charging circuits, batteries, etc. The interface unit 140b can support the connection of the portable device 100 with other external devices. The interface unit 140b may include various ports for connection with external devices (e.g., audio input / output ports, video input / output ports). The input / output unit 140c can receive and output video information / signals, audio information / signals, data, and / or information input from the user. The input / output section 140c may include a camera, microphone, user input section, display section 140d, speaker and / or haptic module, etc.

[0323] For example, in the case of data communication, the input / output unit 140c acquires information / signals input from the user (e.g., touch, text, voice, image, video), and the acquired information / signals can be stored in the memory unit 130. The communication unit 110 converts the information / signals stored in memory into a radio signal and can transmit the converted radio signal directly to other radio devices or to a base station. Furthermore, after receiving a radio signal from another radio device or base station, the communication unit 110 can restore the received radio signal to its original information / signal. The restored information / signal is stored in the memory unit 130 and can then be output via the input / output unit 140c in various forms (e.g., text, voice, image, video, haptic).

[0324] Figure 17 shows a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle can be realized as a mobile robot, a vehicle, a train, aerial vehicle (AV), ship, etc. The embodiment in Figure 17 can be combined with various embodiments of the present disclosure.

[0325] Referring to Figure 17, the 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 composed of part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in Figure 15, respectively.

[0326] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) with 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 may include an ECU (Electronic Control Unit). The drive unit 140a can make the vehicle or autonomous vehicle 100 travel on the ground. The drive unit 140a may include an engine, motor, powertrain, wheels, brakes, steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and may include a wired / wireless charging circuit, 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, collision sensor, wheel sensor, speed sensor, tilt sensor, weight detection sensor, heading sensor, position module, vehicle forward / reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illuminance sensor, pedal position sensor, etc. The autonomous driving unit 140d can implement technologies such as maintaining a lane while driving, automatically adjusting speed like adaptive cruise control, automatically driving along a predetermined route, and automatically setting a route and driving when a destination is set.

[0327] For example, the communication unit 110 can receive map data, traffic information data, etc., from an external server. The autonomous driving unit 140d can generate an autonomous driving route and driving plan based on the acquired data. The control unit 120 can control the drive unit 140a so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan (e.g., speed / direction adjustment). During autonomous driving, the communication unit 110 can acquire the latest traffic information data from an external server non-periodically and acquire surrounding traffic information data from surrounding vehicles. Also, during autonomous driving, the sensor unit 140c can acquire vehicle status and surrounding environment information. The autonomous driving unit 140d can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit 110 can transmit information such as vehicle position, autonomous driving route, and driving plan to an external server. The external server can predict traffic information data in advance using AI technology, etc., based on the information collected from the vehicle or autonomous vehicle, and can provide the predicted traffic information data to the vehicle or autonomous vehicle.

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

Claims

1. In a method for the first device to perform wireless communication, The steps include receiving information from the base station for at least one sidelink (SL) DRX (discontinuous reception) configuration for groupcast and broadcast communications, which is mapped from at least one quality of service (QoS) profile, The step of receiving information from the base station for basic SL DRX settings for groupcast and broadcast communication, The process includes the step of monitoring the reception of data using the base SL DRX setting for a QoS profile that is not mapped to the at least one SL DRX setting associated with the data, The QoS profile related to the aforementioned data exists, by method.

2. The method according to claim 1, wherein the basic SL DRX settings are used for the reception of the data, based on the fact that the data relates to a groupcast service or a broadcast service.

3. The method according to claim 1, wherein the basic SL DRX setting is used for the reception of the data, based on the fact that the data relates to a control signal for setting up a unicast connection that is not related to data for a groupcast service or broadcast service.

4. The QoS profile is a first QoS profile mapped to the data, The method according to claim 1, wherein the first QoS profile is not mapped to the at least one SL DRX setting.

5. In a first device for wireless communication, One or more memory locations for storing instructions, One or more transceivers, The system comprises one or more memory devices and one or more processors connected to one or more transceivers, The one or more processors execute the instruction, Information for at least one sidelink (SL) DRX (discontinuous reception) configuration for groupcast and broadcast communications, mapped from at least one quality of service (QoS) profile, is received from the base station. Information for basic SL DRX settings for groupcast and broadcast communication is received from the base station, and, The reception of data is monitored using the base SL DRX setting for a QoS profile that is not mapped to the at least one SL DRX setting associated with the data, The QoS profile related to the aforementioned data exists in the first device.

6. In a device adapted to control a first UE (user equipment), One or more processors, The system comprises one or more memories that are operablely connectable to one or more processors and that store instructions, The one or more processors execute the instruction, Information for at least one sidelink (SL) DRX (discontinuous reception) configuration for groupcast and broadcast communications, mapped from at least one quality of service (QoS) profile, is received from the base station. Information for basic SL DRX settings for groupcast and broadcast communication is received from the base station, and, The reception of data is monitored using the base SL DRX setting for a QoS profile that is not mapped to the at least one SL DRX setting associated with the data, The QoS profile associated with the aforementioned data exists for the device.

Images