Method and apparatus for performing SL DRX operation based on default DRX settings in NR V2X

Abstract

In one embodiment, a method for a first device to perform wireless communication is proposed. The method includes the steps of: acquiring a SL DRX configuration including information related to a SL DRX cycle and information related to an active time; transmitting a first sidelink control information (SCI) for scheduling a first physical sidelink shared channel (PSSCH) via a first physical sidelink control channel (PSCCH) to a second device; transmitting a second SCI and a first medium access control (MAC) protocol data unit (PDU) via the first PSSCH to the second device; determining a first physical sidelink feedback channel (PSFCH) resource within a first PSFCH slot based on a slot index and a subchannel index related to the first PSSCH; and receiving a first hybrid automatic repeat request (HARQ) feedback for the first MAC PDU based on the first PSFCH resource from the second device. For example, the first PSFCH slot is included in an inactive time at the time of transmitting the first MAC PDU. For example, the first PSFCH slot is included in the active time at the time of receiving the first HARQ feedback.

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 larger communication capacities, 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 Initiative] [Problems that the invention aims to solve]

[0004] On the other hand, in sidelink communication, terminals can perform SL DRX (sidelink discontinuous reception) operation to conserve power. For example, before establishing a unicast connection, it may be important to consider what DRX settings the terminal uses to receive broadcast messages for establishing a unicast connection. [Means for solving the problem]

[0005] According to one embodiment of the present disclosure, a method is proposed in which a first device performs wireless communication. The method includes obtaining a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting including information related to the SL (sidelink) DRX cycle and information related to the activation time, and receiving a message from the second device for establishing a unicast connection with the second device. For example, the message for establishing a unicast connection with the second device is received based on the default DRX setting.

[0006] According to one embodiment of the present disclosure, a first device for performing wireless communication is provided. For example, the first device includes one or more memories for storing instruction words, one or more transceivers, and one or more processors that connect the one or more memories and the one or more transceivers. For example, the one or more processors execute the instruction words, obtain a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting includes information related to the SL (sidelink) DRX cycle and information related to the activation time, and receive a message from the second device for establishing a unicast connection with the second device. For example, the message for establishing a unicast connection with the second device is received based on the default DRX setting.

[0007] According to one embodiment of the present disclosure, an apparatus is provided configured to control a first terminal. For example, it includes one or more processors and one or more memories executablely linked by the one or more processors and storing instruction words. For example, the one or more processors execute the instruction words, obtain a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting includes information related to the SL (sidelink) DRX cycle and information related to the activation time, and receive a message from the second terminal for establishing a unicast connection with the second terminal. For example, the message for establishing a unicast connection with the second terminal is received based on the default DRX setting.

[0008] According to one embodiment of the present disclosure, a storage medium readable by a non-temporary computer recording instructions is provided. For example, the instructions, when executed, cause a first device to obtain a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting including information related to the SL (sidelink) DRX cycle and information related to the activation time, and causing the first device to receive a message from the second device for establishing a unicast connection with the second device. For example, the message for establishing a unicast connection with the second device is received based on the default DRX setting.

[0009] According to one embodiment of the present disclosure, a method is proposed in which a second device performs wireless communication. The method includes the step of sending a message to the first device for establishing a unicast connection with the first device. For example, the message for establishing a unicast connection with the first device is sent based on a default DRX (discontinuous reception) setting for groupcast or broadcast. For example, the default DRX setting is obtained, and the default DRX setting includes information related to the SL (sidelink) DRX cycle and information related to the activation time.

[0010] According to one embodiment of the present disclosure, a second device for performing wireless communication is provided. For example, the second device includes one or more memories for storing instruction words, one or more transceivers, and one or more processors that connect the one or more memories and the one or more transceivers. For example, the one or more processors execute the instruction words and send a message to the first device for establishing a unicast connection with the first device. For example, the message for establishing a unicast connection with the first device is sent based on a default DRX (discontinuous reception) setting for groupcast or broadcast. For example, the default DRX setting is obtained and includes information related to the SL (sidelink) DRX cycle and information related to the activation time. [Effects of the Invention]

[0011] The terminal can maintain smooth SL communication and conserve power by receiving broadcast messages based on the default DRX settings even before a unicast connection is established. [Brief explanation of the drawing]

[0012] [Figure 1] The structure of an NR system according to one embodiment of this disclosure is shown. [Figure 2]This document shows a radio protocol architecture according to one embodiment of the present disclosure. [Figure 3] The structure of a wireless frame for NR according to one embodiment of the present disclosure is shown. [Figure 4] This shows the slot structure of an NR frame according to one embodiment of the present disclosure. [Figure 5] An example of a BWP according to one embodiment of this disclosure is shown. [Figure 6] One embodiment of this disclosure illustrates a procedure for a terminal to perform V2X or SL communication by transmission mode. [Figure 7] Three cast types relating to one embodiment of the present disclosure are shown. [Figure 8] This invention provides a procedure for a terminal to perform SL DRX operation based on basic / common SL DRX settings, according to one embodiment of this disclosure. [Figure 9] This invention describes a procedure for a transmitting terminal to establish a unicast connection with a receiving terminal, according to one embodiment of this disclosure. [Figure 10] This invention describes an embodiment of how a first device receives a message from a second device for establishing a unicast connection. [Figure 11] This invention describes a method by which a second device sends a message to a first device to establish a unicast connection, according to one embodiment of the present disclosure. [Figure 12] This document shows a communication system 1 according to one embodiment of the present disclosure. [Figure 13] This document shows a wireless device according to one embodiment of the present disclosure. [Figure 14] This document shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. [Figure 15] This document shows a wireless device according to one embodiment of the present disclosure. [Figure 16] This document shows a portable device according to one embodiment of the present disclosure. [Figure 17] This shows a vehicle or autonomous vehicle according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0013] In this specification, “A or B” may mean “just A,” “just B,” or “both A and B.” Furthermore, 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.”

[0014] 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".

[0015] 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.”

[0016] 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.”

[0017] Furthermore, parentheses used in this specification can mean "for example." Specifically, when "control information (PDCCH)" is shown, "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 shown, "PDCCH" is proposed as an example of "control information."

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

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

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

[0021] 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) 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.

[0022] 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 spectrum 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.

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

[0024] For terms and techniques used herein that are not specifically described, refer to the radio communication standards documents published prior to the filing of this specification.

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

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

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

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

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

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

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

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

[0033] 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).

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

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

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

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

[0038] 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 can maintain its connection with the core network and, conversely, can terminate (release) its connection with the base station.

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

[0040] 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).

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

[0042] 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).

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

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

[0045] [Table 1]

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

[0047] [Table 2]

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

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

[0050] 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).

[0051] [Table 3]

[0052] 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).

[0053] [Table 4]

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

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

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

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

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

[0059] 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 a CSI (Channel State Information) report for an inactive DL BWP. 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 (downlink control information) for a certain period of time, the terminal can switch its active BWP to the default BWP.

[0060] On one hand, the BWP can be defined with respect to the 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. For 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 a terminal in the RRC_CONNECTED mode, at least one SL BWP can be activated within a carrier.

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

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

[0063] 1] The BWP is based on 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.

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

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

[0066] 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).

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

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

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

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

[0071] 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 are resources for reporting SL HARQ feedback to the base station.

[0072] 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 is a resource that the base station configures / assigns to the first terminal via DCI (downlink control information). In this specification, a CG resource is 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.

[0073] 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 is 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 is information generated by the first terminal based on pre-configured rules. For example, the DCI is a DCI for scheduling SLs. For example, the format of the DCI is DCI format 3_0 or DCI format 3_1.

[0074] The following is an example of DCI Format 3_0.

[0075] DCI format 3_0 is used for scheduling NR PSCCH and NR PSSCH in a single cell.

[0076] The following information is transmitted via DCI format 3_0 with a CRC scrambled by SL-RNTI or SL-CS-RNTI.

[0077] -Resource pool index -ceiling(log2I) bit, where I is the number of resource pools for transmission set by the higher-level parameter sl-TxPoolScheduling.

[0078] -Time gap-3 bits determined by the higher-level parameter sl-DCI-ToSL-Trans

[0079] -HARQ process number-4 bits

[0080] - New data indicator - 1 bit

[0081] -The lowest index of subchannel allocation for initial transmission -ceiling(log2(N SL subChannel ))bit

[0082] -SCI Format 1-A Field: Frequency Resource Allocation, Time Resource Allocation

[0083] -PSFCH-to-HARQ feedback timing instructioner-ceiling(log2N) fb_timing ) bits, where N fb_timing This is the number of entries for the higher-level parameter sl-PSFCH-ToPUCCH.

[0084] -PUCCH resource directive-3 bits

[0085] -Configuration Index- This field is 0 bits if the UE is not configured to monitor DCI format 3_0 with scrambled CRC by SL-CS-RNTI, and 3 bits otherwise. If the UE is configured to monitor DCI format 3_0 with scrambled CRC by SL-CS-RNTI, this field is reserved for DCI format 3_0 with scrambled CRC by SL-RNTI.

[0086] - Counterside link assignment index - 2 bits, 2 bits if UE is set to pdsch-HARQ-ACK-Codebook=dynamic, 2 bits if UE is set to pdsch-HARQ-ACK-Codebook=semi-static

[0087] - Padding bit if necessary

[0088] Referring to Figure 6(b), in LTE transmission mode 2, LTE transmission mode 4, or NR resource allocation mode 2, the terminal can determine an SL transmission resource from SL resources set by the base station / network or from pre-configured SL resources. For example, the set SL resources or pre-configured SL resources are a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can autonomously select resources from the set resource pool and perform SL communication. For example, the terminal can perform sensing and resource (re)selection procedures and autonomously select resources within the selection window. For example, the sensing can be performed on a subchannel basis. For example, in step S610, the first terminal that autonomously 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 step S620, the first terminal transmits the PSSCH associated with the PSCCH (e.g., 2 nd -stage SCI, MAC PDU, data, etc. can be transmitted to the second terminal. In step S630, the first terminal can receive a PSFCH associated with the PSCCH / PSSCH from the second terminal. Referring to Figure 6(a) or (b), for example, the first terminal can transmit an SCI on the PSCCH to the second terminal. Or, for example, the first terminal can transmit two consecutive SCIs (e.g., 2-stage SCIs) on the PSCCH and / or PSSCH to the second terminal. In this case, the second terminal can decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, the SCI transmitted on 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 the -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.

[0089] The following is an example of SCI format 1-A.

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

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

[0092] -Priority-3 bits

[0093] -Frequency resource allocation-If the value of the higher-level parameter sl-MaxNumPerReserve is set to 2, ceiling(log2(N SL subChannel (N SL subChannel +1) / 2)) bits, otherwise, if the value of the higher-level parameter sl-MaxNumPerReserve is set to 3, then ceiling log2(N SL subChannel (N SL subChannel +1)(2N SL subChannel +1) / 6) bits

[0094] -Time resource allocation- 5 bits if the value of the higher-level parameter sl-MaxNumPerReserve is set to 2, otherwise 9 bits if the value of the higher-level parameter sl-MaxNumPerReserve is set to 3.

[0095] -Resource reservation cycle-ceiling(log2N) rsv_period ) bits, where N rsv_period This represents the number of entries in the higher-level parameter sl-ResourceReservePeriodList if the higher-level parameter sl-MultiReserveResource is set, otherwise it is 0 bits.

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

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

[0098] -Beta_Offset Indicator- 2 bits as provided by the higher-level parameter sl-BetaOffsets2ndSCI

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

[0100] -Modulation and coding method- 5-bit

[0101] - Additional MCS Table Instructor - 1 bit if one MCS table is set by the higher-level parameter sl-Additional-MCS-Table, 2 bits if two MCS tables are set by the higher-level parameter sl-Additional-MCS-Table, and 0 bits otherwise.

[0102] -PSFCH overhead directive- Higher level parameter sl-PSFCH-Period = 1 bit if 2 or 4, otherwise 0 bits

[0103] -Reserved bits- The number of bits determined by the higher-level parameter sl-NumReservedBits, and its value is set to 0.

[0104] [Table 5]

[0105] [Table 6]

[0106] The following describes an example of SCI format 2-A. In HARQ operation, if the HARQ-ACK information contains ACK or NACK, or if the HARQ-ACK information contains only NACK, or if there is no feedback of HARQ-ACK information, SCI format 2-A is used for decoding PSSCH.

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

[0108] -HARQ process number-4 bits

[0109] - New data indicator - 1 bit

[0110] -Redundancy version-2 bits

[0111] -Source ID-8bit

[0112] - Destination ID - 16 bits

[0113] -HARQ Feedback Activate / Deactivate Indicator - 1 bit

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

[0115] -CSI Request-1 bit

[0116] [Table 7]

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

[0118] If the HARQ operation contains only a NACK in the HARQ-ACK information, or if there is no feedback of the HARQ-ACK information, SCI format 2-B is used for PSSCH decoding.

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

[0120] -HARQ process number-4 bits

[0121] - New data indicator - 1 bit

[0122] -Redundancy version-2 bits

[0123] -Source ID-8bit

[0124] - Destination ID - 16 bits

[0125] -HARQ Feedback Activate / Deactivate Indicator - 1 bit

[0126] - Zone ID - 12 bits

[0127] -Communication range requirements-4 bits determined by the higher-level parameter sl-ZoneConfigMCR-Index

[0128] Referring to Figure 6(a) or (b), in step S630, the first terminal can receive the PSFCH. For example, the first and second terminals can determine the PSFCH resource, and the second terminal can use the PSFCH resource to send HARQ feedback to the first terminal. Referring to Figure 6(a), in step S640, the first terminal can send SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0129] The following describes the UE procedure for reporting HARQ-ACK via sidelinks.

[0130] In response to receiving a PSSCH, the UE sends a PSFCH containing HARQ-ACK information. PSSCH subchThe SCI format can be used to schedule PSSCH reception on one or more subchannels from a given subchannel. The UE provides HARQ-ACK information containing ACK, NACK, or NACK only.

[0131] The UE can receive the number of slots in the resource pool for PSFCH transmission occasion resources via sl-PSFCH-Period-r16. If the number is 0, PSFCH transmission from the UE is deactivated in the resource pool. The UE is k mod N PSFCH PSSCH If = 0, slot t ′ k SL (0≦k <T ′ max ) Expect that there is a PSFCH transmission opportunity resource, and here, t ′ k SL is a slot belonging to the resource pool, and T ′ max This is the number of slots belonging to the resource pool within 10240 msec, and N PSFCH PSSCH This is provided in sl-PSFCH-Period-r16. The UE may be instructed by a higher level not to send a PSFCH in response to a PSSCH reception. If the UE receives a PSSCH in the resource pool and the HARQ feedback activate / deactivate indicator field contained in the associated SCI format 2-A or SCI format 2-B has a value of 1, the UE provides HARQ-ACK information via a PSFCH transmission in the resource pool. The UE transmits a PSFCH in a first slot, where the first slot is a slot after the last slot containing the PSFCH resource and receiving the PSSCH, after the minimum number of slots provided by sl-MinTimeGapPSFCH-r16 in the resource pool.

[0132] The UE receives a set M of PRBs within a resource pool for PSFCH transmission in the resource pool of PRBs PSFCH PRB,set from sl-PSFCH-RB-Set-r16. The number N of subchannels for the resource pool provided by sl-NumSubchannel subch and N PSFCH PSSCH For the number of PSSCH slots associated with a PSFCH slot that is smaller than or equal to, the UE has M PRB,set PSFCH Of the PRBs [(i + j · N PSFCH PSSCH ) · M PSFCH subch,slot , (i + 1 + j · N PSFCH PSSCH ) · M PSFCH subch,slot -1] PRBs are assigned to slot i and subchannel j among the PSSCH slots associated with the PSFCH slot. Here, M PSFCH subch,slot = M PSFCH PRB,set / (N subch · N PSFCH PSSCH ), 0 ≤ i < N PSFCH PSSCH , 0 ≤ j < N subch and the assignment starts in ascending order of i and continues in ascending order of j. The UE expects M PSFCH PRB,set to be a multiple of N subch · N PSFCH PSSCH .

[0133] The UE determines the number R of PSFCH resources available for multiplexing the HARQ-ACK information included in the PSFCH transmission PSFCH PRB,CS = N PSFCH type · M PSFCH subch,slot · N PSFCH CS Here, N PSFCH CSis the number of cyclic shift pairs for a resource pool, and based on an instruction from a higher layer,

[0134] -N PSFCH type = 1 and M PSFCH subch,slot PRB is associated with the start subchannel of the corresponding PSSCH,

[0135] -N PSFCH type = N PSSCH subch and N PSSCH subch ·M PSFCH subch,slot PRB is associated with one or more subchannels among the N PSSCH subch subchannels of the corresponding PSSCH.

[0136] The PSFCH resource is first indexed in ascending order of the PRB index among N PSFCH type ·M PSFCH subch,slot PRBs, and then indexed in ascending order of the cyclic shift pair index among N PSFCH CS cyclic shift pairs.

[0137] The UE determines the index of the PSFCH resource for PSFCH transmission as a response to PSSCH reception to be (P ID + M ID ) mod R PSFCH PRB,CS . Here, P ID is the physical layer source ID provided by the SCI format 2-A or 2-B that schedules PSSCH reception, M ID is the ID of the UE that receives the PSSCH indicated by the higher layer when the UE detects the SCI format 2-A with the cast type indicator field value of "01", and otherwise, M ID is 0.

[0138] UE uses Table 8 for N PSFCH CS The m0 value is determined to calculate the cyclic shift α value from the cyclic shift pair index corresponding to the PSFCH resource index.

[0139] [Table 8]

[0140] If the UE detects an SCI format 2-A with a cast type indicator field value of "01" or "10", as shown in Table 9, or if the UE detects an SCI format 2-B or SCI format 2-A with a cast type indicator field value of "11", as shown in Table 10, the UE calculates the value m for calculating the cyclic shift α value. cs The UE determines this. It applies one of the cyclic shift pairs to the sequence used for PSFCH transmission.

[0141] [Table 9]

[0142] [Table 10]

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

[0144] For example, the SL DRX configuration may include one or more of the following pieces of information:

[0145] For example, SL DRX-onDurationTimer is information about the duration at the beginning of a DRX cycle. For example, the duration of a DRX cycle is information about the period during which the terminal operates in active mode to transmit or receive sidelink data.

[0146] For example, SL DRX-SlotOffset is information about the delay before starting the DRX-onDurationTimer.

[0147] For example, the SL DRX-InactivityTimer is information about the duration after the PSCCH occurrence in which a PSCCH indicates a new sidelink transmission and reception for the MAC entity. For example, if a transmitting terminal instructs a PSSCH transmission via a PSCCH, the transmitting terminal can transmit the PSSCH to the receiving terminal by operating in active mode while the SL DRX-InactivityTimer is running. Also, for example, if a receiving terminal receives an instruction from the transmitting terminal to transmit a PSSCH via PSCCH reception, the receiving terminal can receive the PSSCH from the transmitting terminal by operating in active mode while the SL DRX-InactivityTimer is running.

[0148] For example, SL DRX-RetransmissionTimer is information about the maximum duration until a retransmission is received. For example, SL DRX-RetransmissionTimer can be set per HARQ process.

[0149] For example, SL DRX-LongCycleStartOffset is information about the Long DRX cycle and DRX-StartOffset, which defines the subframe where the Long and Short DRX cycles begin.

[0150] For example, SL DRX-ShortCycle is information about the Short DRX cycle. For example, SL DRX-ShortCycle is optional information.

[0151] For example, SL DRX-ShortCycleTimer is information about the duration the UE shall follow the Short DRX cycle. For example, SL DRX-ShortCycleTimer is optional information.

[0152] For example, SL DRX-HARQ-RTT-Timer is information about the minimum duration before an assignment for HARQ retransmission is expected by the MAC entity. For example, SL DRX-HARQ-RTT-Timer can be configured per HARQ process.

[0153] On the other hand, NR V2X release 16 does not support power saving operation for UE (user equipment), while NR V2X release 17 can support power saving operation for UE (e.g., power saving UE). Therefore, an SL DRX configuration must be defined for terminal power saving operation (e.g., SL (sidelink) DRX operation).

[0154] In various embodiments of this disclosure, SL DRX settings for terminal power-saving operations are defined, and methods are proposed to enable the terminal to smoothly perform SL DRX operations using the defined SL DRX settings. In the following description, 'when, if, in case of' may be replaced with 'based on'.

[0155] In the following descriptions, the timer names (such as Uu DRX HARQ RTT TimerSL, Uu DRX Retransmission TimerSL, SL DRX Ondulation Timer, SL DRX Inactdivity Timer, SL DRX HARQ RTT Timer, SL DRX Retransmission Timer, etc.) are for illustrative purposes only, and timers that perform the same or similar functions based on the description of each timer can be considered the same or similar timers regardless of their names.

[0156] Figure 8 illustrates a procedure in which a terminal performs SL DRX operation based on basic / common SL DRX settings, according to one embodiment of the present disclosure. The embodiment in Figure 8 can be combined with various embodiments of the present disclosure.

[0157] Referring to Figure 8, an embodiment is disclosed in which a single default / common SL DRX setting for a terminal is configured based on the QoS requirements of a V2X service or a sidelink service. For example, (step 1) the terminal's V2X layer can generate and transmit SL DRX pattern information (e.g., SL DRX cycle, SL DRX on-duration) for the terminal's SL DRX operation to the AS layer, or generate and transmit SL DRX settings to the AS layer, based on the QoS requirements of the V2X service generated in the application layer.

[0158] (Step 2) The AS layer of the terminal then generates a default / common SL DRX setting based on the SL DRX pattern information received in the V2X layer (length of SL DRX cycle and SL DRX duration, or length of SL DRX duration and SL DRX off-duration), and the default / common SL DRX setting can be used for SL DRX operation.

[0159] (Step 3) The terminal can then transmit to the base station the QoS requirements information (PFI, PDB) for the terminal's V2X service and its preferred default / 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 transmit to the terminal the common SL DRX settings information to be used by the terminal based on that information.

[0160] (step 4) The terminal can then perform SL DRX operation and sidelink transmission / reception using the common SL DRX settings transmitted from the base station.

[0161] According to one embodiment of this disclosure, if only one default / common SL DRX configuration is permitted based on the QoS requirements of a V2X service or SL service, a problem can arise where the probability of resource collisions and congestion / interference levels between different terminals increase on the SL DRX on-duration interval of the SL DRX configuration. Therefore, this embodiment proposes the following method to reduce the probability of resource collisions between different terminals on the SL DRX on-duration interval of a common SL DRX configuration.

[0162] For example, the wake-up start time for a common SL DRX configuration, the start time of an SL DRX cycle, the wake-up duration (SL DRX duration length), or the period during which the wake-up duration (e.g., SL DRX duration) of a common SL DRX configuration is repeated (common SL DRX cycle) can be defined to be determined based on parameters such as the application / service ID (and / or (L1 or L2) (source / destination) ID). This can reduce the probability of resource collisions between different terminals performing SL DRX operations. For example, the wake-up time can include the start time of the SL DRX duration. For example, the method for determining the wake-up start time for a common SL DRX configuration, the start time of an SL DRX cycle, the wake-up duration, or the period during which the wake-up duration of a common SL DRX configuration is repeated can include a method that determines it via hopping / randomization.

[0163] Furthermore, for example, multiple common SL DRX settings may be allowed specifically for a V2X or SL service / QoS. Here, the terminal can randomly select one of these (or make a terminal-specific selection), or preferentially select a common SL DRX setting with a relatively low interference level based on (past) measured interference levels on the receiving slot associated with the wake-up interval (e.g., common SL DRX duration) of the common SL DRX setting. Alternatively, for example, the terminal can randomly select one of the common SL DRX settings that are below a threshold set in advance specifically for the service / QoS.

[0164] According to one embodiment of the present disclosure, in addition to randomly setting the default / common SL DRX settings (or default / common SL DRX patterns) or the SL DRX-related parameters included in the default / common SL DRX settings, a terminal may increase the SL DRX duration (or active time interval) or apply a pre-configured SL DRX timer value (e.g., a relatively large value) if conditions such as those described in the proposal are met. That is, for example, to select a resource with less interference, a terminal may increase the time domain of a candidate resource. For example, the conditions described in the proposal may include the probability of resource collision between different terminals, situations where the congestion / interference level is high, when the probability of resource collision between different terminals exceeds a threshold, or when the congestion / interference level between different terminals exceeds a threshold. For example, the pre-configured SL DRX timer may include the SL DRX timer included in the SL DRX settings mentioned in the present disclosure, or other SL DRX-related timers defined to support SL DRX operation.

[0165] According to one embodiment of this disclosure, when switching to another default / common SL DRX setting (or default / common SL DRX pattern) or SL DRX-related parameter included in a selected default / common SL DRX setting, congestion / interference level hysteresis can be set. For example, a terminal may be allowed to switch to a new common SL DRX setting, common SL DRX pattern, or common SL DRX setting parameter only if the congestion / interference level difference on the existing / new setting or pattern is greater than a pre-set hysteresis value, and at the same time, the congestion / interference level on the new setting or pattern is lower than a pre-set threshold. Furthermore, switching to other settings or patterns can be configured to be permitted only in limited circumstances, such as when resource reselection is triggered, when TB-related retransmission is complete, when the terminal operates in long DRX mode, or when the timer expires and the terminal operates based on SL duration.

[0166] According to one embodiment of the present disclosure, if a high-priority / required service-related SL DRX onduration or active interval (partially) overlaps with a low-priority / required service-related SL DRX onduration or active interval, the (maximum, minimum, or average) transmit power values ​​used for transmitting the low-priority / required service, the TB-related (maximum) retransmission count, the upper bound value of the channel occupancy ratio (CR), etc., can be limited and set to reduce interference to the high-priority / required service (within the overlapping interval). For example, the active interval may mean an interval in which the terminal is in a wake-up state to receive or transmit a sidelink signal, including the SL DRX onduration.

[0167] According to one embodiment of the present disclosure, when the zone region in which the terminal is located changes (or when the zone ID in which the terminal is located changes), randomization of the selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters and timers included in the common SL DRX settings, settings, patterns and / or DRX operating parameters included in the settings can be triggered or permitted.

[0168] According to one embodiment of the present disclosure, when a terminal changes from an In-Coverage state to an Out-Of-Coverage state or when a terminal changes from an Out-Of-Coverage state to an In-Coverage state, randomization of selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters and timers included in the common SL DRX settings, settings, patterns, and DRX operating parameters included in the settings can be triggered or permitted.

[0169] According to one embodiment of the present disclosure, when the Cell ID to which the terminal is located changes, randomization of the selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters and timers included in the common SL DRX settings, settings, patterns, and DRX operating parameters included in the settings can be triggered or permitted.

[0170] According to one embodiment of the present disclosure, when the carrier type of a terminal (e.g., licensed carrier, ITS-dedicated carrier) is changed, randomization of selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters and timers included in the common SL DRX settings, settings, patterns, and DRX operating parameters included in the settings can be triggered or permitted.

[0171] According to one embodiment of the present disclosure, when the communication type / direction of the terminal (e.g., V2P, P2P, P2V) is changed, randomization of the selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters included in the common SL DRX settings, and timers, settings, patterns, and DRX operating parameters included in the settings can be triggered or permitted.

[0172] According to one embodiment of the present disclosure, when the remaining battery amount of the terminal changes, randomization of the selection of at least one of the common SL DRX setting, common SL DRX pattern, SL DRX operating parameters and timers included in the common SL DRX setting, setting, pattern, and DRX operating parameters included in the setting can be triggered or permitted.

[0173] According to one embodiment of the present disclosure, when the terminal's V2X (or SL) service ID / type changes, randomization of the selection of at least one of the common SL DRX settings, common SL DRX patterns, SL DRX operating parameters and timers included in the common SL DRX settings, settings, patterns, and DRX operating parameters included in the settings can be triggered or permitted.

[0174] According to one embodiment of this disclosure, when (default / common) SL DRX pattern / configuration information is exchanged via higher-level signaling, a mechanism is needed to ensure that terminals have a common understanding of the start time of the (default / common) SL DRX pattern / configuration (e.g., the start time of the SL DRX onduration). Therefore, this 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 when a terminal receives it is considered a reference timing (e.g., the start time of the SL DRX onduration), or a method in which information regarding the SL DRX pattern-related reference timing is signaled via additional higher-level signaling, or a method in which the time when a pre-configured / exchanged slot offset value is applied from the synchronized source-based DFN (direct frame number) 0 is considered a reference timing. For example, the SL DRX pattern / configuration information may include SL DRX cycles, SL DRX onduration interval information, etc. For example, the higher-level signaling may include MAC CE and PC5 RRC. For example, the additional higher-level signaling may include SL DRX acknowledgment messages, SIB, DL-only RRC messages, and / or PC5 RRC messages.

[0175] In various embodiments of this disclosure, the common sidelink DRX settings / parameters are DRX settings / parameters used in common with all terminals regardless of the cast type (e.g., unicast, groupcast, or broadcast). Alternatively, for example, the common sidelink DRX settings / parameters are DRX settings / parameters configured separately for a specific cast type (e.g., unicast, groupcast, or broadcast). Here, for example, the common sidelink DRX settings are the basic (default) sidelink DRX settings. For example, the common sidelink DRX settings / parameters are DRX settings / parameters used in common by terminals belonging to or subscribing to the same groupcast service. For example, the same groupcast service may include groupcast services having the same groupcast destination layer 2 ID. For example, the common sidelink DRX settings / parameters are DRX settings / parameters used in common by terminals belonging to or subscribing to the same unicast service. For example, the same unicast service may include unicast services having the same source layer 2 ID / destination layer 2 ID pair. For example, common sidelink DRX settings / parameters are DRX settings / parameters that are commonly used by terminals belonging to or joining the same broadcast service. For example, the same broadcast service may include broadcast services that have the same broadcast destination Layer 2 ID.

[0176] Alternatively, for example, common sidelink DRX settings / parameters are DRX settings / parameters configured separately for specific cast types (e.g., unicast, groupcast, or broadcast). For example, common sidelink DRX settings / parameters are DRX settings / parameters commonly used by terminals interested in a service. Here, for example, a service is at least one of the following: a groupcast service with the same groupcast destination layer 2 ID, a unicast service is at least one of the following: a unicast service with the same source layer 2 ID / destination layer 2 ID pair, or a broadcast service is at least one of the following: a broadcast service with the same broadcast destination layer 2 ID. For example, if a terminal is not subscribed to or linked to a service associated with a cast type, terminals interested in a service may be interested in subscribing to a service associated with a cast type and may monitor signals associated with that service. Here, for example, DRX settings / parameters may include UE service-specific DRX settings commonly used by terminals interested in a service.

[0177] For example, if a terminal is not connected to a service associated with unicast, the terminal can monitor the signals associated with said service. In this case, for example, the terminal can use the default / common sidelink DRX setting to monitor the signals associated with said service. Here, for example, the default / common sidelink DRX setting is the default / common sidelink DRX setting for groupcast or broadcast. Additionally, here, for example, a service associated with unicast may include a service associated with a QoS profile that cannot be mapped to a DRX setting configured for a dedicated QoS profile. Here, for example, the signals associated with said service may include messages for establishing a unicast connection (e.g., a DCR (direct communication request) message). Here, for example, a service associated with a QoS profile that is not mapped to a non-default DRX setting may include messages for establishing a unicast connection (e.g., a DCR message).

[0178] Additionally, for example, a common DRX configuration for groupcasts and / or broadcasts can be used to receive messages for establishing a unicast link.

[0179] For example, a common default DRX setting between groupcast and broadcast can be used for QoS profiles that are not mapped to non-basic DRX settings.

[0180] For example, for groupcasts and broadcasts, the default DRX setting can be used for QoS profiles that cannot be mapped to the DRX setting configured for a dedicated QoS profile.

[0181] For example, parameters associated with the default DRX configuration (e.g., the sl-DRX-ConfigCommon-GC-BC field) can indicate sidelink DRX configuration for groupcast and broadcast communication. Here, for example, parameters associated with the default DRX configuration can be received from the base station.

[0182] For example, the common sidelink DRX settings mentioned above, or the UE service-specific sidelink DRX settings used commonly by terminals, can be configured or set up in the following combinations:

[0183] For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a per-cast type basis. For example, cast types can include unicast services, groupcast services, and broadcast services.

[0184] For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a source / destination pair basis. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a source L1 or L2 ID / destination L1 or L2 ID pair basis. Here, for example, L1 can mean Layer 1 and L2 can mean Layer 2.

[0185] For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a per-service basis. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a per-PQI (PC5 5QI (5G QoS Indicator)) basis. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured on a per-PDB (packet delay budget) basis.

[0186] For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured per PS ID (Provider Service Identifier).

[0187] For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured based on the service and cast type. Here, for example, the service may include PQI and PS ID. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured for each combination of service and cast type.

[0188] For example, a common sidelink DRX setting or a UE service-specific sidelink DRX setting can be configured based on the service and destination. For example, the service may include the PQI and PS ID. For example, a common sidelink DRX setting or a UE service-specific sidelink DRX setting can be configured for each combination of service and destination. For example, the destination may include the group cast ID or broadcast ID. For example, in the case of group cast or broadcast, the common sidelink DRX setting or the UE service-specific sidelink DRX setting can be configured based on the service and destination, using the group cast ID or broadcast ID.

[0189] For example, since the destination Layer 2 ID can be used as an identifier to distinguish groupcast / broadcast services, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured for each destination Layer 2 ID. In this case, for example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured that reflect the PQI of the sidelink data for each destination Layer 2 ID.

[0190] For example, in the case of groupcast or broadcast, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured based on service and source / destination pairs. For example, a service may include a PQI and a PS ID. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured for each combination of service and source / destination pairs. For example, a source / destination pair may include a source L1 or L2 ID / destination L1 or L2 ID pair.

[0191] Furthermore, for example, the sidelink DRX setting is DRX setting information applied by the receiving terminal that receives sidelink data. Therefore, from the perspective of the receiving terminal, the source Layer 2 ID is the destination Layer 2 ID of the transmitting terminal, and the destination Layer 2 ID is the source Layer 2 ID of the transmitting terminal. That is, for example, from the perspective of the receiving terminal, the sidelink DRX setting can be set for each pair of source L2 ID / destination L2 ID, and the receiving terminal can use the said sidelink DRX setting. Also, for example, a transmitting terminal can perform the role of a receiving terminal that receives SL data transmitted by other terminals, just like a receiving terminal. That is, for example, a transmitting terminal can also perform the role of a receiving terminal while setting the sidelink DRX setting for each pair of source L2 ID / destination L2 ID, and can use the said sidelink DRX setting. That is, for example, the sidelink DRX setting can be set and used for each pair of source L2 ID / destination L2 ID depending on the transmission / reception direction of the sidelink data (e.g., from transmitting terminal to receiving terminal, receiving terminal to transmitting terminal).

[0192] For example, in the case of unicast, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured based on service and source / destination pairs. For example, common sidelink DRX settings or UE service-specific sidelink DRX settings can be configured for each combination of service and source / destination pairs. Here, for example, a service may include a PQI and a PS ID. For example, a source / destination pair may include a source L1 or L2 ID / destination L1 or L2 ID pair.

[0193] For example, since a source L2 ID / destination L2 ID pair can be used as an identifier to distinguish PC5 unicast links, terminals can configure UE service-specific sidelink DRX settings separately for PC5 unicast links or PC5 RRC connections. Here, for example, a PC5 RRC connection may include a source L2 ID / destination L2 ID pair. In this case, for example, UE service-specific sidelink DRX settings can be configured that reflect the PQI of the sidelink data transmitted and received between terminals over a PC5 unicast link or PC5 RRC connection.

[0194] For example, since a source L2 ID / destination L2 ID pair can be used as an identifier to distinguish PC5 unicast links, terminals can configure UE service-specific sidelink DRX settings separately for PC5 unicast links or PC5 RRC connections. Here, for example, a PC5 RRC connection may include a source L2 ID / destination L2 ID pair. In this case, for example, UE service-specific sidelink DRX settings can be configured that reflect the PQI of the sidelink data transmitted and received between terminals over a PC5 unicast link or PC5 RRC connection.

[0195] For example, a common sidelink DRX configuration or a UE service-specific sidelink DRX configuration can be set to at least two combinations of the following: service, source / destination pair, destination Layer 1 ID or Layer 2 ID, source Layer 1 ID or source Layer 2 ID, cast type or PDB. For example, a service may include a PQI or PS ID. For example, a source / destination pair may include a source Layer 1 ID or source Layer 2 ID / destination Layer 1 ID or Layer 2 ID pair.

[0196] According to one embodiment of the present disclosure, a dedicated common SL DRX configuration can be defined for a terminal that has established a PC5 unicast connection or a PC5 RRC connection. For example, a dedicated common SL DRX configuration can be defined for a terminal that wishes to establish a PC5 unicast connection or a PC5 RRC connection.

[0197] For example, a terminal using a VoIP (Voice over Internet Protocol) service (e.g., a unicast service) and a terminal using an autonomous driving service may have different requirement times to establish a PC5 unicast connection and use the service. Here, for example, an autonomous driving service may include a message sending and receiving service for swarm driving, and an autonomous driving service may include a broadcast service. That is, for example, the SL DRX settings used to receive messages to be exchanged between terminals do not need to be the same before establishing a PC5 unicast connection or a PC5 RRC connection. Here, for example, the SL DRX settings may include at least one of the DRX cycle or SL DRX duration timer. For example, a PC5 unicast specific common SL DRX setting used for a service that requires a fast PC5 unicast connection or PC5 RRC connection may have a short value for the DRX cycle or SL DRX duration timer.

[0198] For example, the PC5 unicast-specific common SL DRX configuration proposed in this disclosure is a common SL DRX configuration that can be used in common by all terminals that have established a PC5 unicast connection or a PC5 RRC connection. For example, terminals that have established a PC5 unicast connection or a PC5 RRC connection may include terminals that wish to establish a PC5 unicast connection or a PC5 RRC connection.

[0199] Alternatively, for example, the PC5 unicast-specific common SL DRX setting proposed in this disclosure is a common SL DRX setting specific to a PC5 unicast connection or PC5 RRC connection, which can be used by a terminal that has established a specific PC5 unicast connection or PC5 RRC connection. For example, a terminal that has established a PC5 unicast connection or PC5 RRC connection may include terminals that wish to establish a PC5 unicast connection or PC5 RRC connection. That is, for example, the PC5 unicast-specific common SL DRX setting proposed in this disclosure is a common SL DRX setting for terminals that have established a PC5 unicast connection or PC5 RRC connection having the same source Layer 2 ID / destination Layer 2 ID pair. For example, since unicast communication is bidirectional communication, the SL DRX setting applied from the receiving terminal's perspective may be applied to different values ​​for each direction of unicast communication. Therefore, for example, the PC5 unicast-specific common SL DRX setting proposed in this disclosure may be set on a direction-by-direction basis for the source Layer 2 ID / destination Layer 2 ID pair.

[0200] The PC5 unicast specific common SL DRX configuration or PC5 RRC connection specific common SL DRX configuration proposed in this disclosure can be used in a variety of applications, such as those listed below.

[0201] For example, before establishing a PC5 unicast or PC5 RRC connection, UEs can use a common SL DRX configuration to send / receive messages exchanged between UEs. Here, for example, the common SL DRX configuration is a common SL DRX configuration specific to a PC5 unicast connection or a common SL DRX configuration specific to a PC5 RRC connection. For example, UEs can include power-saving UEs that perform SL DRX operations. For example, messages exchanged between UEs can include PC5-S Direct Communication Request / response messages, other PC5-S messages exchanged to establish a PC5 unicast link, and PC5 RRC messages exchanged for UE capability negotiation.

[0202] For example, before a UE that has established a PC5 unicast or PC5 RRC connection establishes a new PC5 unicast or PC5 RRC connection with another UE, the UEs can use a common SL DRX configuration to send / receive messages exchanged between UEs. Here, for example, the common SL DRX configuration is a common SL DRX configuration specific to a PC5 unicast connection or a common SL DRX configuration specific to a PC5 RRC connection. For example, the UEs may include UEs that perform SL DRX operations, power-saving UEs. For example, messages exchanged between UEs may include PC5-S Direct Communication Request / response messages, other PC5-S messages exchanged to establish a PC5 unicast link, and PC5 RRC messages exchanged for UE capability negotiation.

[0203] For example, a UE that has configured a PC5 unicast connection or a PC5 RRC connection can use a common SL DRX configuration to monitor a channel or signal of another UE. Here, for example, the common SL DRX configuration is a common SL DRX configuration specific to a PC5 unicast connection or a common SL DRX configuration specific to a PC5 RRC connection. For example, the UE may include a UE performing SL DRX operation, a power-saving UE. For example, the channel may include at least one of PSCCH, PSSCH, PSFCH, or PSBCH. For example, the signal may include S-SSB.

[0204] Through various embodiments of this disclosure, settings for the sidelink DRX timer for power saving operations of a terminal are defined, and a method is proposed to enable the terminal to efficiently perform sidelink DRX operations by using the defined sidelink DRX timer settings.

[0205] According to one embodiment of the present disclosure, the values ​​of the sidelink DRX timers used for sidelink unicast communication (e.g., sidelink DRX duration timer, sidelink DRX inactivity timer, sidelink DRX HARQ RTT timer, sidelink DRX retransmission timer) can be set as follows.

[0206] In other words, for example, the sidelink DRX timer used for SL unicast can be configured to use independent values ​​for each unicast. Here, for example, the sidelink DRX timer used for SL unicast can include at least one of the following: sidelink DRX duration timer, sidelink DRX inactivity timer, sidelink DRX HARQ RTT timer, or sidelink DRX retransmission timer. For example, the sidelink DRX timer used for SL unicast can be configured to use independent values ​​for each PC5 unicast link identifier. For example, the sidelink DRX timer used for SL unicast can be configured to use independent values ​​for each pair of the same source Layer 1 ID or Layer 2 ID / destination Layer 1 ID or Layer 2 ID. For example, the sidelink DRX timer used for SL unicast can be configured to use independent values ​​for each unicast service. Here, for example, the unicast service can include PQI and PDB. For example, the sidelink DRX timer used for SL unicast can be configured to use independent values ​​for each destination Layer 1 ID or Layer 2 ID. For example, the sidelink DRX timer used for SL unicasts can be configured to use independent values ​​for each source Layer 1 ID or Layer 2 ID. In such cases, the sidelink DRX timer setting for a specific unicast can be communicated to the peer unicast UE via a PC5 RRC message or MAC CE.

[0207] Alternatively, for example, the sidelink DRX timer used for SL unicast can be configured to use a value common to all unicast services. In such a case, for example, the base station can communicate the configured unicast common sidelink DRX timer setting to the terminal via SIB (System Information Block) or Dedicated RRC message. Alternatively, for example, the unicast common sidelink DRX timer setting can be pre-configured, and the terminal can use the pre-configured unicast common sidelink DRX timer setting.

[0208] According to one embodiment of the present disclosure, the value of the sidelink DRX timer used for sidelink groupcast communication can be set as follows.

[0209] For example, the sidelink DRX timers used for SL groupcasts can be configured to use independent values ​​for each groupcast. For example, the sidelink DRX timers used for SL groupcasts can include at least one of the following: a sidelink DRX duration timer, a sidelink DRX inactivity timer, a sidelink DRX HARQ RTT timer, or a sidelink DRX retransmission timer. For example, the sidelink DRX timers used for SL groupcasts can be configured to use independent values ​​for each groupcast destination Layer 2 ID. For example, the sidelink DRX timers used for SL groupcasts can be configured to use independent values ​​for each pair of the same source layer Layer 2 ID / groupcast destination Layer 2 ID. For example, the sidelink DRX timers used for SL groupcasts can be configured to use independent values ​​for each groupcast service. Here, for example, a groupcast service can include PQI and PDB. In such cases, the configured sidelink DRX timer settings for a particular groupcast group can be propagated to the UEs belonging to the other groupcast group via MAC CE.

[0210] Alternatively, for example, the sidelink DRX timer used for SL groupcast can be configured to use a common value for all groupcast services. In such a case, for example, the base station can communicate the configured groupcast common sidelink DRX timer setting to the terminal via SIB or dedicated RRC message. Alternatively, for example, the groupcast common sidelink DRX timer setting can be pre-configured, and the terminal can use the pre-configured groupcast common sidelink DRX timer setting.

[0211] According to one embodiment of the present disclosure, the value of the sidelink DRX timer used for sidelink broadcast communication can be set as follows.

[0212] For example, the sidelink DRX timers used for SL broadcasts can be configured to use independent values ​​for each broadcast. For example, the sidelink DRX timers used for SL broadcasts can include at least one of the following: sidelink DRX duration timer, sidelink DRX inactivity timer, sidelink DRX HARQ RTT timer, or sidelink DRX retransmission timer. For example, the sidelink DRX timers used for SL broadcasts can be configured to use independent values ​​for each broadcast destination Layer 2 ID. For example, the sidelink DRX timers used for SL broadcasts can be configured to use independent values ​​for each pair of the same source layer 2 ID / broadcast destination layer 2 ID. For example, the sidelink DRX timers used for SL broadcasts can be configured to use independent values ​​for each broadcast service. Here, for example, broadcast services can include PQI and PDB. In such cases, the sidelink DRX timer settings for a particular broadcast group can be propagated to the UEs belonging to the peer broadcast group via MAC CE.

[0213] Alternatively, for example, the sidelink DRX timer used for SL broadcasts can be configured to use a common value for all broadcast services. In such a case, for example, the base station can communicate the configured broadcast common sidelink DRX timer setting to the terminal via SIB or dedicated RRC message. Alternatively, for example, the broadcast common sidelink DRX timer setting can be pre-configured, and the terminal can use the pre-configured broadcast common sidelink DRX timer setting.

[0214] In the various embodiments of this disclosure, the SL DRX timers mentioned below can be used for the following applications:

[0215] For example, the SL DRX duration timer can be used in intervals where a UE performing SL DRX operation should essentially operate in an active time state for receiving the other UE's PSCCH / PSSCH.

[0216] For example, the SL DRX deactivation timer can be used to extend the SL DRX onduration interval, which is the interval during which a UE performing SL DRX operation should basically operate at the active time in order to receive a PSCCH / PSSCH from a remote UE. In other words, the SL DRX onduration timer can be extended by the length of the SL DRX deactivation timer interval, for example. Also, when a UE receives a new packet (e.g., a new PSSCH) from a remote UE, it can start the SL DRX deactivation timer to extend the SL DRX onduration timer.

[0217] For example, the SL DRX HARQ RTT timer can be used during a period when a UE performing SL DRX operation operates in sleep mode until it receives a retransmit packet (or PSSCH assignment) from the other UE. That is, for example, if a UE starts the SL DRX HARQ RTT timer, it can assume that the other UE will not send it a sidelink retransmit packet until the SL DRX HARQ RTT timer expires, and the UE can operate in sleep mode during that timer period.

[0218] For example, the SL DRX retransmission timer can be used during periods when a UE performing SL DRX operation is active to receive retransmission packets (or PSSCH assignments) transmitted by the other UE. For instance, during an SL DRX retransmission timer interval, the UE can monitor for the reception of retransmission sidelink packets (or PSSCH assignments) transmitted by the other UE.

[0219] Various embodiments of this disclosure can be used to solve the problem of loss caused by interruptions that occur when switching UuBWPs.

[0220] Furthermore, for example, if a terminal supports multiple SL BWP, it can be used to solve the problem of loss caused by interference that occurs when switching SL BWP.

[0221] The various embodiments of this disclosure can be applied not only to Default / Common SL DRX settings, Default / Common SL DRX patterns, parameters included in Default / Common SL DRX settings, or timers included in Default / Common SL DRX settings, but also to UE-Pair Specific SL DRX settings, UE-Pair Specific SL DRX patterns, parameters included in UE-Pair Specific SL DRX settings, and timers included in UE-Pair Specific SL DRX settings.

[0222] Furthermore, in this disclosure, for example, 'Onduration' refers to an Active Time interval. For example, Active Time is the interval in which the device operates in a wakeup state (RF module is "on") to receive / transmit radio signals. For example, 'Offduration' refers to a Sleep Time interval. For example, Sleep Time is the interval in which the device operates in a sleep mode state (RF module is "off") for power saving. For example, it does not mean that a transmitting UE is obligated to operate in sleep mode during Sleep Time intervals. For example, if necessary, a terminal may be permitted to operate in Active Time for a period of time for sensing / transmitting operations, even during Sleep Time.

[0223] For example, the applicability of the various embodiments of this disclosure can be set independently or differently by at least one of the following: resource pool, congestion level, service priority, service type, requirements (e.g., latency, reliability), traffic type (e.g., periodic generation, aperiodic generation), and SL transmission resource allocation mode (e.g., mode 1, mode 2).

[0224] For example, the parameters associated with the various embodiments of this disclosure (e.g., thresholds) can be set independently or differently by at least one of the following: resource pool, congestion level, service priority, service type, requirements (e.g., latency, reliability), traffic type (e.g., periodic generation, aperiodic generation), and SL transmission resource allocation mode (e.g., mode 1, mode 2).

[0225] For example, the applicability of various embodiments of this disclosure depends on resource pools, service / packet types, priorities, QoS requirements (e.g., reliability, latency, URLLC / EMBB), whether HARQ feedback is enabled, whether HARQ feedback is disabled, LCH, MAC PDU, cast type (e.g., unicast, groupcast, broadcast), resource pool congestion level (e.g., CBR), SL HARQ feedback scheme (e.g., NACK-only feedback scheme, ACK / NACK feedback scheme), MAC PDU transmission with HARQ feedback enabled, MAC PDU transmission with HARQ feedback disabled, configurability of PUCCH-based SL HARQ feedback reporting behavior, preemption execution, re-evaluation execution, resource re-selection, L1 or L2 source identifier, L1 or L2 destination identifier, combination of source layer ID and destination layer ID, direction of source layer ID and destination layer ID pair, combination of source layer ID and destination layer ID pair and cast type, PC5 For RRC connections / links and SL DRX execution, the SL mode type (e.g., resource allocation mode 1, resource allocation mode 2), and at least one of periodic resource reservation execution or non-periodic resource reservation execution can be configured independently or differently.

[0226] For example, parameter settings related to various embodiments of this disclosure include resource pool, service / packet type, priority, QoS requirements (e.g., reliability, latency, URLLC / EMBB), enable / disable HARQ feedback, LCH, MAC PDU, cast type (e.g., unicast, groupcast, broadcast), resource pool congestion level (e.g., CBR), SL HARQ feedback scheme (e.g., NACK-only feedback scheme, ACK / NACK feedback scheme), MAC PDU transmission with HARQ feedback enabled, MAC PDU transmission with HARQ feedback disabled, configurability of PUCCH-based SL HARQ feedback reporting operation, preemption execution, re-evaluation execution, resource re-selection, L1 or L2 source identifier, L1 or L2 destination identifier, source layer ID and destination layer ID combination, direction of source layer ID and destination layer ID pair, source layer ID and destination layer ID pair and cast type combination, PC5 For RRC connections / links and SL DRX execution, the SL mode type (e.g., resource allocation mode 1, resource allocation mode 2), and at least one of periodic resource reservation execution or non-periodic resource reservation execution can be configured independently or differently.

[0227] Furthermore, for example, “configuration” or “designation” in this disclosure may include a form in which a base station informs a terminal via a predefined physical layer channel / signal or a higher layer channel / signal (e.g., SIB, RRC, MAC CE). For example, “configuration” or “designation” may be provided via pre-configuration, or a form in which a terminal informs another terminal via a predefined physical layer channel / signal or a higher layer channel / signal (e.g., SL MAC CE, PC5 RRC). Also, the various embodiments of this disclosure can be combined with each other.

[0228] In the present disclosure, for example, "a certain period of time" is the time during which the UE operates in the active time (Active Time) for a predefined time for the UE to receive a sidelink signal or sidelink data from a peer UE. For example, "a certain period of time" is the time during which the UE operates in the active time for a timer (SL DRX retransmission timer, SL DRX inactivation (Inactivity) timer, timer to ensure that the RX UE can operate in the active time in the DRX operation) time for the UE to receive a sidelink signal or sidelink data from a peer UE.

[0229] Various embodiments of the present disclosure can be applied to millimeter wave (mmWave) SL operations. Whether various embodiments of the present disclosure can be applied can be applied to millimeter wave (mmWave) SL operations. Parameter setting values related to various embodiments of the present disclosure can be applied to millimeter wave (mmWave) SL operations.

[0230] FIG. 9 shows a procedure for a transmitting terminal to establish a unicast connection with a receiving terminal according to an embodiment of the present disclosure. The embodiment of FIG. 9 can be combined with various embodiments of the present disclosure.

[0231] Referring to FIG. 9, in step S910, the transmitting terminal can obtain a default DRX setting for groupcast or broadcast. For example, the default DRX setting can include information related to the sidelink DRX cycle and information related to the active time.

[0232] In step S920, the transmitting terminal can receive a message for establishing a unicast connection from the receiving terminal. For example, a message for establishing a unicast connection with the receiving terminal can be received based on the default DRX setting.

[0233] In step S930, the transmitting terminal can establish a unicast connection with the receiving terminal.

[0234] For example, the default DRX setting can be received via higher-level signaling.

[0235] For example, the default DRX setting can be received via a System Information Block (SIB).

[0236] For example, the default DRX setting can be configured based on the cast type.

[0237] For example, the default DRX settings can be configured based on source-destination pairs.

[0238] For example, the default DRX setting can be configured based on the service.

[0239] For example, the default DRX settings can be configured based on a combination of service and cast type.

[0240] For example, the default DRX settings can be configured based on the service and destination combination.

[0241] For example, the default DRX settings can be configured based on service and source-destination pair combinations.

[0242] For example, the reference timing can be determined to be the time when the default DRX setting is received. For example, the reference timing can include the start time of the SL DRX duration.

[0243] For example, information regarding the reference timing associated with the default DRX can be received.

[0244] For example, the reference timing related to the default DRX can be determined at a point after a preset offset value from the point when the synchronization source-based DFN (direct frame number) = 0.

[0245] FIG. 10 shows a method by which a first device receives a message for establishing a unicast connection from a second device according to an embodiment of the present disclosure. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure.

[0246] Referring to FIG. 10, in step S1010, the first device 100 can obtain a default DRX setting for groupcast or broadcast. For example, the default DRX setting can include information related to a sidelink DRX cycle and information related to an active time.

[0247] In step S1020, the first device 100 can receive a message for establishing a unicast connection from the second device 200. For example, the message for establishing a unicast connection with the second device 200 can be received based on the default DRX setting.

[0248] For example, the default DRX setting can be received via upper layer signaling.

[0249] For example, the default DRX setting can be received via an SIB (system information block).

[0250] For example, the default DRX setting can be set based on a cast type.

[0251] For example, the default DRX setting can be set based on a source and destination pair.

[0252] For example, the default DRX setting can be configured based on the service.

[0253] For example, the default DRX settings can be configured based on a combination of service and cast type.

[0254] For example, the default DRX settings can be configured based on the service and destination combination.

[0255] For example, the default DRX settings can be configured based on service and source-destination pair combinations.

[0256] For example, the reference timing can be determined to be the time when the default DRX setting is received. For example, the reference timing can include the start time of the SL DRX duration.

[0257] For example, information regarding a reference timing associated with the default DRX can be received.

[0258] For example, the reference timing associated with the default DRX can be determined to a point in time after a predetermined offset value from the point in time when DFN=0 on the synchronization source base.

[0259] The embodiments described above can be applied to a variety of devices as described below. For example, the processor 102 of the first device 100 can acquire default DRX settings for groupcast or broadcast. Then, for example, the processor 102 of the first device 100 can control the transceiver 106 to receive a message from the second device 200 to establish a unicast connection.

[0260] 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 that connect the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instruction words, obtain a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting including information related to the SL (sidelink) DRX cycle and information related to the activation time, and receive a message from the second device for establishing a unicast connection with the second device. For example, a message for establishing a unicast connection with the second device may be received based on the default DRX setting.

[0261] According to one embodiment of the present disclosure, an apparatus can be provided configured to control a first terminal. For example, it may include one or more processors and one or more memories executablely linked by the one or more processors and storing instruction words. For example, the one or more processors execute the instruction words and obtain a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting including information related to the SL (sidelink) DRX cycle and information related to the activation time, and can receive messages from the second terminal for establishing a unicast connection with the second terminal. For example, messages for establishing a unicast connection with the second terminal can be received based on the default DRX setting.

[0262] According to one embodiment of the present disclosure, a storage medium readable by a non-temporary computer recording instructions can be provided. For example, the instructions may cause a first device, when executed, to acquire a default DRX (discontinuous reception) setting for groupcast or broadcast, the default DRX setting including information related to the SL (sidelink) DRX cycle and information related to the activation time, and to receive a message from the second device for establishing a unicast connection with the second device. For example, the message for establishing a unicast connection with the second device may be received based on the default DRX setting.

[0263] Figure 11 illustrates a method, according to one embodiment of the present disclosure, in which a second device sends a message to a first device to establish a unicast connection. The embodiment in Figure 11 can be combined with various embodiments of the present disclosure.

[0264] Referring to Figure 11, in step S1110, the second device 200 can send a message to the first device 100 to establish a unicast connection with the first device 100.

[0265] For example, a message to establish a unicast connection with the first device 100 can be sent based on a default DRX (discontinuous reception) setting for groupcast or broadcast. For example, the default DRX setting can be retrieved. For example, the default DRX setting may include information related to the SL (sidelink) DRX cycle and information related to the activation time.

[0266] For example, the default DRX setting can be received via higher-level signaling.

[0267] For example, the default DRX setting can be received via a System Information Block (SIB).

[0268] For example, the default DRX setting can be configured based on the cast type.

[0269] For example, the default DRX settings can be configured based on source-destination pairs.

[0270] For example, the default DRX setting can be configured based on the service.

[0271] For example, the default DRX settings can be configured based on a combination of service and cast type.

[0272] For example, the default DRX settings can be configured based on the service and destination combination.

[0273] For example, the default DRX settings can be configured based on service and source-destination pair combinations.

[0274] For example, the reference timing can be determined to be the time when the default DRX setting is received. For example, the reference timing can include the start time of the SL DRX duration.

[0275] For example, information regarding a reference timing associated with the default DRX can be received.

[0276] For example, the reference timing associated with the default DRX can be determined to a point in time after a predetermined offset value from the point in time when DFN=0 on the synchronization source base.

[0277] The embodiments described above can be applied to a variety of devices as described below. First, for example, the processor 202 of the second device 200 can control the transceiver 206 to send a message to the first device 100 to establish a unicast connection with the first device 100.

[0278] 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 that connect the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instruction words and send a message to the first device for establishing a unicast connection with the first device. For example, the message for establishing a unicast connection with the first device may be sent based on a default DRX (discontinuous reception) setting for groupcast or broadcast. For example, the default DRX setting may be obtained and may include information related to the SL (sidelink) DRX cycle and information related to the activation time.

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

[0280] The various embodiments of this disclosure can be embodied independently, or they can be embodied in combination or merged with each other. For example, although the various embodiments of this disclosure have been described based on the 3GPP system for convenience of explanation, the various embodiments of this disclosure are extendable to other systems outside the 3GPP system. For example, the various embodiments of this disclosure are not limited to direct communication between terminals, but can also be used in uplink or downlink, in which case base stations, relay nodes, etc., can use the methods proposed by the various embodiments of this disclosure. For example, information on whether the methods relating to the various embodiments of this disclosure are applicable can be defined so that the base station informs the terminal or the second device 200 informs the receiving terminal via a predefined signal (e.g., a physical layer signal or a higher layer signal). For example, information on rules relating to the various embodiments of this disclosure can be defined so that the base station informs the terminal or the second device 200 informs the receiving terminal via a predefined signal (e.g., a physical layer signal or a higher layer signal).

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

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

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

[0284] Figure 12 shows a communication system 1 according to one embodiment of the present disclosure.

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

[0286] 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®, 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.

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

[0288] Wireless communication / connection 150a, 150b, and 150c can be performed between wireless devices 100a-100f / base station 200 and between base stations 200 / base station 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.

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

[0290] 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} can correspond to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in Figure 12.

[0291] 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 includes instructions for executing some or all of the processes controlled by processor 102, or 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.

[0292] 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 the 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 includes instructions for executing some or all of the processes controlled by processor 202, or 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.

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

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

[0295] One or more memory units 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 memory units 104, 204 can consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer read / store media, and / or combinations thereof. One or more memory units 104, 204 can be located inside and / or outside of one or more processors 102, 202. Furthermore, one or more memory units 104, 204 can be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0296] One or more transceivers 106, 206 can 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 can 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 can be connected to one or more processors 102, 202, and can transmit and receive radio signals. For example, one or more processors 102, 202 can 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 can 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.

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

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

[0299] 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).

[0300] 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 can perform precoding after performing transform precoding (e.g., DFT transformation) on the complex modulation symbols. Alternatively, the precoder 1040 can perform precoding without performing transform precoding.

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

[0302] In wireless equipment, the signal processing process for a received signal can be configured as the reverse of the signal processing processes 1010-1060 in Figure 17. For example, wireless equipment (e.g., 100, 200 in Figure 16) can receive wireless signals 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 decoded to restore the original information blocks. 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.

[0303] Figure 15 shows a wireless device according to one embodiment of the present disclosure. The wireless device can be embodied 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.

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

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

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

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

[0308] 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 glasses), or a portable computer (e.g., a notebook computer). The portable device is referred to as an 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.

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

[0310] 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 for driving the portable device 100. The memory unit 130 can 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.

[0311] 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).

[0312] Figure 17 shows a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle can be embodied in mobile robots, cars, trains, manned / unmanned aerial vehicles (AVs), ships, etc. The embodiment in Figure 17 can be combined with various embodiments of the present disclosure.

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

[0314] 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 system, 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.

[0315] 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 the 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 the newly acquired data / information. The communication unit 110 can transmit information such as vehicle position, autonomous driving route, and driving plan to the 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.

[0316] 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 a first device to perform wireless communication, A step of obtaining a first DRX (discontinuous reception) setting for groupcast or broadcast, wherein the first DRX setting is related to a default DRX setting and includes information for an SL (sidelink) DRX cycle and information for an SL DRX duration. The steps include monitoring signals to establish a unicast connection with a second device, The signal relates to a service of interest to the first device, The first DRX setting is used for the communication of the signal to establish the unicast connection with the second device. One or more second DRX settings for groupcasts or broadcasts other than the first DRX setting are mapped to one or more PC5 QoS (quality of service) identifiers. A method in which the first DRX setting is used for a PC5 QoS identifier that is not mapped to one or more second DRX settings.

2. The method according to claim 1, wherein the first DRX setting is received via higher-level signaling.

3. The method according to claim 1, wherein the first DRX setting is received via an SIB (system information block) or an RRC (radio resource control) reset message.

4. The method according to claim 1, wherein the first DRX setting is set based on the cast type.

5. The method according to claim 1, wherein the first DRX setting is set based on a source-destination pair.

6. The method according to claim 1, wherein the first DRX setting is set based on a service.

7. The method according to claim 1, wherein the first DRX setting is set based on a combination of service and cast type.

8. The method according to claim 1, wherein the first DRX setting is set based on a combination of service and destination.

9. The method according to claim 1, wherein the first DRX setting is configured based on a service and a combination of source-destination pairs.

10. The method according to claim 1, wherein the time at which the first DRX setting is received is determined as the reference timing.

11. The method according to claim 10, wherein the reference timing includes the start time of the SL DRX duration.

12. The method according to claim 10, wherein information relating to the reference timing associated with the first DRX setting is received.

13. The method according to claim 10, wherein the reference timing associated with the first DRX setting is determined as a time point of a predetermined offset value from the time point in which the DFN (direct frame number) of the synchronization source base = 0.

14. In a first device configured to perform wireless communication, One or more memory locations for storing instruction words, One or more transceivers, The system comprises one or more memory units and one or more processors connected to the one or more transceivers, The one or more processors execute the instruction word, Obtaining a first DRX (discontinuous reception) setting for groupcast or broadcast, wherein the first DRX setting is related to a default DRX setting and includes information for an SL (sidelink) DRX cycle and information for an SL DRX duration. Perform operations including monitoring signals to establish a unicast connection with a second device, The signal relates to a service of interest to the first device, The first DRX setting is used for the communication of the signal to establish the unicast connection with the second device. One or more second DRX settings for groupcasts or broadcasts other than the first DRX setting are mapped to one or more PC5 QoS (quality of service) identifiers. The first DRX setting is used for a first device, which is used for PC5 QoS identifiers that are not mapped to one or more second DRX settings.

15. In a device configured to control a first UE (user equipment), the device is configured to control a first UE. One or more processors, Includes one or more memory units that are operablely connected to one or more processors and store instruction words, The one or more processors execute the instruction word, Obtaining a first DRX (discontinuous reception) setting for groupcast or broadcast, wherein the first DRX setting is related to a default DRX setting and includes information for an SL (sidelink) DRX cycle and information for an SL DRX duration. Perform operations including monitoring signals to establish a unicast connection with a second device, The aforementioned signal relates to a service of interest to the first device, The first DRX setting is used for the communication of the signal to establish the unicast connection with the second device. One or more second DRX settings for groupcasts or broadcasts other than the first DRX setting are mapped to one or more PC5 QoS (quality of service) identifiers. The device wherein the first DRX setting is used for PC5 QoS identifiers that are not mapped to one or more second DRX settings.

16. A non-temporary computer-readable medium on which command words are recorded, When the aforementioned command is executed, the first device will, Obtaining a first DRX (discontinuous reception) setting for groupcast or broadcast, wherein the first DRX setting is related to a default DRX setting and includes information for an SL (sidelink) DRX cycle and information for an SL DRX duration. Perform an operation that includes monitoring signals to establish a unicast connection with a second device, The signal relates to a service of interest to the first device, The first DRX setting is used for the communication of the signal to establish the unicast connection with the second device. One or more second DRX settings for groupcasts or broadcasts other than the first DRX setting are mapped to one or more PC5 QoS (quality of service) identifiers. The first DRX setting is used for a medium that is not mapped to one or more second DRX settings, and is used for PC5 QoS identifiers.

Images