WO2023013851A1 - Procédé et dispositif de mise en œuvre de drx sl sur la base d'un profil de transmission dans nr v2x - Google Patents

Procédé et dispositif de mise en œuvre de drx sl sur la base d'un profil de transmission dans nr v2x Download PDF

Info

Publication number
WO2023013851A1
WO2023013851A1 PCT/KR2022/006309 KR2022006309W WO2023013851A1 WO 2023013851 A1 WO2023013851 A1 WO 2023013851A1 KR 2022006309 W KR2022006309 W KR 2022006309W WO 2023013851 A1 WO2023013851 A1 WO 2023013851A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
release
information
transmission
profile
Prior art date
Application number
PCT/KR2022/006309
Other languages
English (en)
Korean (ko)
Inventor
홍종우
백서영
박기원
이승민
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2023013851A1 publication Critical patent/WO2023013851A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present disclosure relates to a wireless communication system.
  • SL Sidelink
  • UEs user equipments
  • BS base station
  • V2X vehicle-to-everything
  • V2X vehicle-to-everything
  • V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian).
  • V2X communication may be provided through a PC5 interface and/or a Uu interface.
  • next-generation radio access technology taking into account the above may be referred to as new radio access technology (RAT) or new radio (NR).
  • RAT new radio access technology
  • NR new radio
  • V2X vehicle-to-everything
  • a timer (eg, T400) may run.
  • T400 sidelink discontinuous reception cycle
  • SL DRX cycle sidelink discontinuous reception cycle
  • RLF Radio Link Failure
  • a terminal interlocked with a release that supports SL DRX identifies a terminal interlocked with a release that does not support SL DRX in advance, and an SL with a terminal interlocked with a release that does not support SL DRX.
  • a terminal interlocked with a release that supports SL DRX identifies a terminal interlocked with a release that does not support SL DRX in advance, and an SL with a terminal interlocked with a release that does not support SL DRX.
  • a method for performing wireless communication by a first device may include receiving settings related to sidelink discontinuous reception (SL DRX) from a second device, and performing the SL DRX based on settings related to the SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of the SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • a first device performing wireless communication includes one or more memories storing instructions, one or more transceivers, and one or more processors connecting the one or more memories and the one or more transceivers, the one or more processors executing the instructions to generate a second It may receive settings related to sidelink discontinuous reception (SL DRX) from a device, and perform the SL DRX based on settings related to the SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of the SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • the UE may turn on/off DRX in consideration of UEs interlocked with other releases according to a transmission profile.
  • FIG. 1 shows the structure of an NR system according to an embodiment of the present disclosure.
  • FIG. 2 shows a radio protocol architecture, according to an embodiment of the present disclosure.
  • FIG. 3 shows a structure of a radio frame of NR according to an embodiment of the present disclosure.
  • FIG. 4 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure.
  • FIG 5 shows an example of BWP according to an embodiment of the present disclosure.
  • FIG. 6 illustrates a procedure for a terminal to perform V2X or SL communication according to a transmission mode according to an embodiment of the present disclosure.
  • FIG 7 illustrates three cast types according to an embodiment of the present disclosure.
  • FIG 8 illustrates an example of performing a PC5 RRC connection between a UE and a peer UE according to an embodiment of the present disclosure.
  • FIG 9 illustrates a procedure in which a receiving terminal performs SL DRX based on a transmission-related profile according to an embodiment of the present disclosure.
  • FIG. 10 illustrates a method in which a first device performs SL DRX based on a profile related to transmission, according to an embodiment of the present disclosure.
  • FIG 11 illustrates a method in which a second device performs SL DRX based on a profile related to transmission, according to an embodiment of the present disclosure.
  • FIG. 12 illustrates a communication system 1, according to an embodiment of the present disclosure.
  • FIG 13 illustrates a wireless device according to an embodiment of the present disclosure.
  • FIG. 14 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure.
  • FIG. 15 illustrates a wireless device according to an embodiment of the present disclosure.
  • FIG. 16 illustrates a portable device according to an embodiment of the present disclosure.
  • FIG 17 illustrates a vehicle or autonomous vehicle according to an embodiment of the present disclosure.
  • a or B may mean “only A”, “only B”, or “both A and B”.
  • a or B (A or B)" in the present specification may be interpreted as “A and/or B (A and/or B)”.
  • A, B or C as used herein means “only A”, “only B”, “only C”, or “any and all combinations of A, B and C ( any combination of A, B and C)”.
  • a slash (/) or a comma (comma) used in this specification may mean “and/or”.
  • A/B can mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”.
  • A, B, C may mean “A, B or C”.
  • At least one of A and B may mean “only A”, “only B”, or “both A and B”. Also, in this specification, the expression “at least one of A or B” or “at least one of A and/or B” means “at least one It can be interpreted the same as "A and B (at least one of A and B) of
  • At least one of A, B and C means “only A”, “only B”, “only C", or “A, B and C” It may mean “any combination of A, B and C”. Also, “at least one of A, B or C” or “at least one of A, B and/or C” means It can mean “at least one of A, B and C”.
  • control information may be suggested as an example of “control information”.
  • control information in this specification is not limited to “PDCCH”, and “PDCCH” may be suggested as an example of “control information”.
  • PDCCH control information
  • a higher layer parameter may be a parameter set for a terminal, previously set, or previously defined.
  • the base station or network may transmit higher layer parameters to the terminal.
  • higher layer parameters may be transmitted through radio resource control (RRC) signaling or medium access control (MAC) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented with a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be implemented with a wireless technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like.
  • IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with a system based on IEEE 802.16e.
  • UTRA is part of the universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) that uses evolved-UMTS terrestrial radio access (E-UTRA), adopting OFDMA in downlink and SC in uplink -Adopt FDMA.
  • LTE-A (advanced) is an evolution of 3GPP LTE.
  • 5G NR a successor to LTE-A, is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability.
  • 5G NR can utilize all available spectrum resources, including low-frequency bands below 1 GHz, medium-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.
  • 5G NR is mainly described, but the technical idea according to an embodiment of the present disclosure is not limited thereto.
  • FIG. 1 shows the structure of an NR system according to an embodiment of the present disclosure.
  • the embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.
  • a Next Generation - Radio Access Network may include a base station 20 that provides user plane and control plane protocol termination to a terminal 10 .
  • the base station 20 may include a next generation-Node B (gNB) and/or an evolved-NodeB (eNB).
  • the terminal 10 may be fixed or mobile, and other terms such as MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), and wireless device (Wireless Device) can be called
  • a base station may be a fixed station that communicates with the terminal 10, and may be called other terms such as a base transceiver system (BTS) and an access point.
  • BTS base transceiver system
  • the embodiment of FIG. 1 illustrates a case including only gNB.
  • the base stations 20 may be connected to each other through an Xn interface.
  • the base station 20 may be connected to a 5G Core Network (5GC) through an NG interface.
  • the base station 20 may be connected to an access and mobility management function (AMF) 30 through an NG-C interface, and may be connected to a user plane function (UPF) 30 through an NG-U interface.
  • AMF access and mobility management function
  • UPF user plane function
  • the layers of the Radio Interface Protocol between the terminal and the network are L1 (layer 1, 1st) based on the lower 3 layers of the Open System Interconnection (OSI) standard model widely known in communication systems. layer), L2 (layer 2, 2nd layer), and L3 (layer 3, 3rd layer).
  • OSI Open System Interconnection
  • layer 1 layer 1, 1st
  • L2 layer 2, 2nd layer
  • L3 layer 3, 3rd layer
  • the physical layer belonging to the first layer provides an information transfer service using a physical channel
  • the RRC (Radio Resource Control) layer located in the third layer provides radio resources between the terminal and the network. plays a role in controlling To this end, the RRC layer exchanges RRC messages between the terminal and the base station.
  • FIG. 2 shows a radio protocol architecture, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 2 may be combined with various embodiments of the present disclosure.
  • (a) of FIG. 2 shows a radio protocol stack of a user plane for Uu communication
  • (b) of FIG. 2 shows a radio protocol of a control plane for Uu communication. represents a stack.
  • (c) of FIG. 2 shows a radio protocol stack of a user plane for SL communication
  • (d) of FIG. 2 shows a radio protocol stack of a control plane for SL communication.
  • a physical layer provides an information transmission service to an upper layer using a physical channel.
  • the physical layer is connected to a medium access control (MAC) layer, which is an upper layer, through a transport channel.
  • MAC medium access control
  • Data moves between the MAC layer and the physical layer through the transport channel.
  • Transmission channels are classified according to how and with what characteristics data is transmitted through the air interface.
  • the physical channel may be modulated using OFDM (Orthogonal Frequency Division Multiplexing) and utilizes time and frequency as radio resources.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the MAC layer provides a service to a radio link control (RLC) layer, which is an upper layer, through a logical channel.
  • RLC radio link control
  • the MAC layer provides a mapping function from multiple logical channels to multiple transport channels.
  • the MAC layer provides a logical channel multiplexing function by mapping a plurality of logical channels to a single transport channel.
  • the MAC sublayer provides data transmission services on logical channels.
  • the RLC layer performs concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs).
  • SDUs RLC Service Data Units
  • the RLC layer has transparent mode (TM), unacknowledged mode (UM) and acknowledged mode , AM) provides three operation modes.
  • AM RLC provides error correction through automatic repeat request (ARQ).
  • the Radio Resource Control (RRC) layer is defined only in the control plane.
  • the RRC layer is responsible for control of logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers.
  • RB is a first layer (physical layer or PHY layer) and second layer (MAC layer, RLC layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer) for data transfer between the terminal and the network means the logical path provided by
  • the functions of the PDCP layer in the user plane include delivery of user data, header compression and ciphering.
  • the functions of the PDCP layer in the control plane include delivery of control plane data and encryption/integrity protection.
  • the Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane.
  • SDAP layer performs mapping between QoS flows and data radio bearers, marking QoS flow identifiers (IDs) in downlink and uplink packets, and the like.
  • IDs QoS flow identifiers
  • Establishing an RB means a process of defining characteristics of a radio protocol layer and a channel and setting specific parameters and operation methods to provide a specific service.
  • RBs can be further divided into two types: Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB).
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the terminal When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state, otherwise it is in the RRC_IDLE state.
  • the RRC_INACTIVE state is additionally defined, and the UE in the RRC_INACTIVE state can release the connection with the base station while maintaining the connection with the core network.
  • a downlink transmission channel for transmitting data from a network to a terminal includes a broadcast channel (BCH) for transmitting system information and a downlink shared channel (SCH) for transmitting user traffic or control messages.
  • Traffic or control messages of a downlink multicast or broadcast service may be transmitted through a downlink SCH or may be transmitted through a separate downlink multicast channel (MCH).
  • an uplink transmission channel for transmitting data from a terminal to a network includes a random access channel (RACH) for transmitting an initial control message and an uplink shared channel (SCH) for transmitting user traffic or control messages.
  • RACH random access channel
  • Logical channels located above transport channels and mapped to transport channels include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), MTCH (Multicast Traffic Channel) Channel), etc.
  • BCCH Broadcast Control Channel
  • PCCH Paging Control Channel
  • CCCH Common Control Channel
  • MCCH Multicast Control Channel
  • MTCH Multicast Traffic Channel
  • FIG. 3 shows a structure of a radio frame of NR according to an embodiment of the present disclosure.
  • the embodiment of FIG. 3 may be combined with various embodiments of the present disclosure.
  • radio frames can be used in uplink and downlink transmission in NR.
  • a radio frame has a length of 10 ms and may be defined as two 5 ms half-frames (Half-Frame, HF).
  • a half-frame may include five 1ms subframes (Subframes, SFs).
  • a subframe may be divided into one or more slots, and the number of slots in a subframe may be determined according to a subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).
  • CP cyclic prefix
  • each slot may include 14 symbols.
  • each slot may include 12 symbols.
  • the symbol may include an OFDM symbol (or CP-OFDM symbol), a Single Carrier-FDMA (SC-FDMA) symbol (or a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).
  • OFDM symbol or CP-OFDM symbol
  • SC-FDMA Single Carrier-FDMA
  • DFT-s-OFDM Discrete Fourier Transform-spread-OFDM
  • Table 1 below shows the number of symbols per slot (N slot symb ), the number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe, u slot ) is exemplified.
  • Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when the extended CP is used.
  • OFDM A numerology
  • SCS SCS
  • CP length CP length
  • TU Time Unit
  • multiple numerologies or SCSs to support various 5G services can be supported. For example, when the SCS is 15 kHz, wide area in traditional cellular bands can be supported, and when the SCS is 30 kHz/60 kHz, dense-urban, lower latency latency and wider carrier bandwidth may be supported. When the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.
  • An NR frequency band may be defined as two types of frequency ranges.
  • the two types of frequency ranges may be FR1 and FR2.
  • the number of frequency ranges may be changed, and for example, the two types of frequency ranges may be shown in Table 3 below.
  • FR1 may mean "sub 6 GHz range”
  • FR2 may mean “above 6 GHz range” and may be called millimeter wave (mmW).
  • mmW millimeter wave
  • FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, and may be used, for example, for vehicle communication (eg, autonomous driving).
  • FIG. 4 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure.
  • the embodiment of FIG. 4 may be combined with various embodiments of the present disclosure.
  • a slot includes a plurality of symbols in the time domain. For example, in the case of a normal CP, one slot includes 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot includes 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.
  • a carrier includes a plurality of subcarriers in the frequency domain.
  • a resource block (RB) may be defined as a plurality of (eg, 12) consecutive subcarriers in the frequency domain.
  • a bandwidth part (BWP) may be defined as a plurality of consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and may correspond to one numerology (eg, SCS, CP length, etc.) there is.
  • a carrier may include up to N (eg, 5) BWPs. Data communication may be performed through an activated BWP.
  • Each element may be referred to as a resource element (RE) in the resource grid, and one complex symbol may be mapped.
  • RE resource element
  • bandwidth part BWP
  • carrier a bandwidth part (BWP) and a carrier
  • a bandwidth part may be a contiguous set of physical resource blocks (PRBs) in a given numerology.
  • PRB physical resource blocks
  • a PRB may be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.
  • CRBs common resource blocks
  • the BWP may be at least one of an active BWP, an initial BWP, and/or a default BWP.
  • the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell).
  • the UE may not receive a PDCCH, a physical downlink shared channel (PDSCH), or a reference signal (CSI-RS) (except RRM) outside the active DL BWP.
  • the UE may not trigger Channel State Information (CSI) reporting for inactive DL BWP.
  • the UE may not transmit a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) outside the active UL BWP.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the initial BWP may be given as a set of consecutive RBs for a remaining minimum system information (RMSI) control resource set (CORESET) (set by a physical broadcast channel (PBCH)).
  • RMSI remaining minimum system information
  • CORESET control resource set
  • PBCH physical broadcast channel
  • SIB system information block
  • a default BWP may be set by higher layers.
  • the initial value of the default BWP may be an initial DL BWP.
  • DCI downlink control information
  • BWP may be defined for SL.
  • the same SL BWP can be used for transmit and receive.
  • a transmitting terminal can transmit an SL channel or SL signal on a specific BWP
  • a receiving terminal can receive an SL channel or SL signal on the specific BWP.
  • SL BWP may be defined separately from Uu BWP, and SL BWP may have separate configuration signaling from Uu BWP.
  • the terminal may receive configuration for SL BWP from the base station/network.
  • the terminal may receive configuration for Uu BWP from the base station/network.
  • SL BWP may be set (in advance) for an out-of-coverage NR V2X terminal and an RRC_IDLE terminal within a carrier. For a UE in RRC_CONNECTED mode, at least one SL BWP may be activated within a carrier.
  • FIG. 5 shows an example of BWP according to an embodiment of the present disclosure.
  • the embodiment of FIG. 5 may be combined with various embodiments of the present disclosure.
  • a common resource block may be a carrier resource block numbered from one end of a carrier band to the other end.
  • a PRB may be a numbered resource block within each BWP.
  • Point A may indicate a common reference point for the resource block grid.
  • BWP may be set by point A, an offset from point A (N start BWP ), and a bandwidth (N size BWP ).
  • point A may be the external reference point of the carrier's PRB to which subcarrier 0 of all numerologies (eg, all numerologies supported by the network on that carrier) are aligned.
  • the offset may be the PRB interval between point A and the lowest subcarrier in a given numerology.
  • the bandwidth may be the number of PRBs in a given numerology.
  • V2X or SL communication will be described.
  • the Sidelink Synchronization Signal is a SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS).
  • PSSS Primary Sidelink Synchronization Signal
  • SSSS Secondary Sidelink Synchronization Signal
  • the PSSS may be referred to as a sidelink primary synchronization signal (S-PSS)
  • S-SSS sidelink secondary synchronization signal
  • S-SSS sidelink secondary synchronization signal
  • length-127 M-sequences can be used for S-PSS
  • length-127 Gold-sequences can be used for S-SSS.
  • the terminal can detect an initial signal using S-PSS and acquire synchronization.
  • the terminal may obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.
  • PSBCH Physical Sidelink Broadcast Channel
  • the basic information includes information related to SLSS, duplex mode (DM), TDD UL/Time Division Duplex Uplink/Downlink (TDD UL/DL) configuration, resource pool related information, type of application related to SLSS, It may be a subframe offset, broadcast information, and the like.
  • the payload size of the PSBCH may be 56 bits including a 24-bit Cyclic Redundancy Check (CRC).
  • S-PSS, S-SSS, and PSBCH may be included in a block format (eg, SL SS (Synchronization Signal) / PSBCH block, hereinafter, S-SSB (Sidelink-Synchronization Signal Block)) supporting periodic transmission.
  • the S-SSB may have the same numerology (ie, SCS and CP length) as a Physical Sidelink Control Channel (PSCCH)/Physical Sidelink Shared Channel (PSSCH) in a carrier, and the transmission bandwidth may be a (pre)set SL Sidelink BWP (Sidelink Channel). BWP).
  • the bandwidth of the S-SSB may be 11 Resource Blocks (RBs).
  • PSBCH may span 11 RBs.
  • the frequency position of the S-SSB may be set (in advance). Therefore, the UE does not need to perform hypothesis detection in frequency to discover the S-SSB in the carrier.
  • the transmission mode may be referred to as a mode or a resource allocation mode.
  • a transmission mode in LTE may be referred to as an LTE transmission mode
  • a transmission mode in NR may be referred to as an NR resource allocation mode.
  • (a) of FIG. 6 shows a terminal operation related to LTE transmission mode 1 or LTE transmission mode 3.
  • (a) of FIG. 6 shows UE operation related to NR resource allocation mode 1.
  • LTE transmission mode 1 may be applied to general SL communication
  • LTE transmission mode 3 may be applied to V2X communication.
  • (b) of FIG. 6 shows a terminal operation related to LTE transmission mode 2 or LTE transmission mode 4.
  • (b) of FIG. 6 shows UE operation related to NR resource allocation mode 2.
  • the base station may schedule SL resources to be used by the terminal for SL transmission.
  • the base station may transmit information related to SL resources and/or information related to UL resources to the first terminal.
  • the UL resource may include a PUCCH resource and/or a PUSCH resource.
  • the UL resource may be a resource for reporting SL HARQ feedback to the base station.
  • the first terminal may receive information related to dynamic grant (DG) resources and/or information related to configured grant (CG) resources from the base station.
  • CG resources may include CG type 1 resources or CG type 2 resources.
  • the DG resource may be a resource set/allocated by the base station to the first terminal through downlink control information (DCI).
  • the CG resource may be a (periodic) resource configured/allocated by the base station to the first terminal through a DCI and/or RRC message.
  • the base station may transmit an RRC message including information related to the CG resource to the first terminal.
  • the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station transmits a DCI related to activation or release of the CG resource. It can be transmitted to the first terminal.
  • the first terminal may transmit a PSCCH (eg, Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling.
  • a PSCCH eg, Sidelink Control Information (SCI) or 1st-stage SCI
  • the first terminal may transmit a PSSCH (eg, 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • HARQ feedback information eg, NACK information or ACK information
  • the first terminal may transmit/report HARQ feedback information to the base station through PUCCH or PUSCH.
  • the HARQ feedback information reported to the base station may be information that the first terminal generates based on the HARQ feedback information received from the second terminal.
  • the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance.
  • the DCI may be a DCI for SL scheduling.
  • the format of the DCI may be DCI format 3_0 or DCI format 3_1.
  • DCI format 3_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell.
  • the following information is transmitted through DCI format 3_0 having a CRC scrambled by SL-RNTI or SL-CS-RNTI.
  • N fb_timing is the number of entries of the upper layer parameter sl-PSFCH-ToPUCCH.
  • - configuration index - 0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI; Otherwise, it is 3 bits. If the UE is configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI.
  • the terminal can determine an SL transmission resource within an SL resource set by the base station / network or a preset SL resource there is.
  • the configured SL resource or the preset SL resource may be a resource pool.
  • the terminal may autonomously select or schedule resources for SL transmission.
  • the terminal may perform SL communication by selecting a resource by itself within a configured resource pool.
  • the terminal may select a resource by itself within a selection window by performing a sensing and resource (re)selection procedure.
  • the sensing may be performed in units of subchannels.
  • the first terminal that selects a resource within the resource pool by itself can transmit a PSCCH (eg, Sidelink Control Information (SCI) or 1 st -stage SCI) to the second terminal using the resource.
  • a PSCCH eg, Sidelink Control Information (SCI) or 1 st -stage SCI
  • the first terminal may transmit a PSSCH (eg, 2nd -stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal.
  • the first terminal may receive the PSFCH related to the PSCCH/PSSCH from the second terminal.
  • UE 1 may transmit SCI to UE 2 on PSCCH.
  • UE 1 may transmit two consecutive SCI (eg, 2-stage SCI) to UE 2 on PSCCH and/or PSSCH.
  • UE 2 may decode two consecutive SCIs (eg, 2-stage SCI) in order to receive the PSSCH from UE 1.
  • SCI transmitted on PSCCH may be referred to as 1st SCI, 1st SCI, 1st -stage SCI or 1st -stage SCI format
  • SCI transmitted on PSSCH is 2nd SCI, 2nd SCI, 2 It may be referred to as nd -stage SCI or 2 nd -stage SCI format
  • the 1st -stage SCI format may include SCI format 1-A
  • the 2nd -stage SCI format may include SCI format 2-A and/or SCI format 2-B.
  • SCI format 1-A is used for scheduling of PSSCH and 2nd -stage SCI on PSSCH.
  • the following information is transmitted using SCI format 1-A.
  • N rsv_period is the number of entries of the upper layer parameter sl-ResourceReservePeriodList when the higher layer parameter sl-MultiReserveResource is set; otherwise, 0 bit
  • N pattern is the number of DMRS patterns set by the upper layer parameter sl-PSSCH-DMRS-TimePatternList
  • Additional MCS table indicator - 1 bit if one MCS table is set by the upper layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are set by upper layer parameter sl- Additional-MCS-Table; 0 bit otherwise
  • HARQ-ACK information when HARQ-ACK information includes ACK or NACK, or when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information, SCI format 2-A is used for PSSCH decoding used
  • the following information is transmitted via SCI format 2-A.
  • SCI format 2-B is used for PSSCH decoding and is used with HARQ operation when HARQ-ACK information includes only NACK or there is no feedback of HARQ-ACK information.
  • SCI format 2-B is used for PSSCH decoding.
  • the following information is transmitted via SCI format 2-B.
  • the first terminal may receive the PSFCH.
  • UE 1 and UE 2 may determine a PSFCH resource, and UE 2 may transmit HARQ feedback to UE 1 using the PSFCH resource.
  • the first terminal may transmit SL HARQ feedback to the base station through PUCCH and/or PUSCH.
  • FIG. 7 illustrates three cast types according to an embodiment of the present disclosure.
  • the embodiment of FIG. 7 may be combined with various embodiments of the present disclosure.
  • FIG. 7(a) shows broadcast type SL communication
  • FIG. 7(b) shows unicast type SL communication
  • FIG. 7(c) shows groupcast type SL communication.
  • a terminal may perform one-to-one communication with another terminal.
  • SL communication of the group cast type a terminal may perform SL communication with one or more terminals in a group to which it belongs.
  • SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, and the like.
  • HARQ hybrid automatic repeat request
  • SL HARQ feedback can be enabled for unicast.
  • non-Code Block Group (non-CBG) operation if the receiving terminal decodes a PSCCH targeting the receiving terminal, and the receiving terminal successfully decodes a transport block related to the PSCCH, the receiving terminal HARQ-ACK can be generated. And, the receiving terminal may transmit HARQ-ACK to the transmitting terminal.
  • the receiving terminal may generate HARQ-NACK. And, the receiving terminal may transmit HARQ-NACK to the transmitting terminal.
  • SL HARQ feedback may be enabled for groupcast.
  • two HARQ feedback options can be supported for groupcast.
  • Groupcast Option 1 If the receiving terminal fails to decode a transport block related to the PSCCH after the receiving terminal decodes the PSCCH targeting the receiving terminal, the receiving terminal transmits HARQ-NACK through the PSFCH. It can be transmitted to the transmitting terminal. On the other hand, if the receiving terminal decodes a PSCCH targeting the receiving terminal and the receiving terminal successfully decodes a transport block related to the PSCCH, the receiving terminal may not transmit HARQ-ACK to the transmitting terminal.
  • Groupcast option 2 If the receiving terminal fails to decode a transport block related to the PSCCH after the receiving terminal decodes the PSCCH targeting the receiving terminal, the receiving terminal transmits HARQ-NACK through the PSFCH. It can be transmitted to the transmitting terminal. And, when the receiving terminal decodes the PSCCH targeting the receiving terminal and the receiving terminal successfully decodes the transport block related to the PSCCH, the receiving terminal may transmit HARQ-ACK to the transmitting terminal through the PSFCH.
  • all terminals performing groupcast communication may share PSFCH resources.
  • UEs belonging to the same group may transmit HARQ feedback using the same PSFCH resource.
  • each terminal performing groupcast communication may use different PSFCH resources for HARQ feedback transmission.
  • UEs belonging to the same group may transmit HARQ feedback using different PSFCH resources.
  • HARQ-ACK may be referred to as ACK, ACK information, or positive-ACK information
  • HARQ-NACK may be referred to as NACK, NACK information, or negative-ACK information.
  • Table 8 shows an example of SL CBR (channel busy ratio) and SL RSSI (received signal strength indicator).
  • Table 9 shows an example of SL CR (Channel Occupancy Ratio).
  • the UE may perform a DRX operation based on Tables 10 to 12. Operations/procedures described in Tables 10 to 12 may be combined with various embodiments of the present disclosure.
  • FIG. 8 illustrates an example of performing a PC5 RRC connection between a UE and a peer UE according to an embodiment of the present disclosure.
  • the embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.
  • a peer UE may be a UE configured with PC5 RRC connection/PC5-signaling for unicast communication.
  • a peer UE may be a UE attempting setup for PC5 RRC connection/PC5-signaling for unicast communication.
  • a peer UE may be a UE in progress of setup for PC5 RRC connection/PC5-signaling for unicast communication.
  • a UE may perform transmission/reception for sidelink (SL) data transmission, and a peer UE may perform transmission/reception. Therefore, the UE may allocate SL DRX configuration to the peer UE, and conversely, the peer UE may also allow SL DRX configuration to the UE.
  • SL sidelink
  • the operation of the UE mentioned in this disclosure can be applied to the peer UE as it is.
  • the TX UE and RX UE mentioned in this disclosure can be applied to both the UE and the peer UE.
  • all operations and procedures applied by a UE to a peer UE may be directly applied by a peer UE to the UE.
  • a timer (eg, T400) may run.
  • T400 the timer value of T400 and T400 expires.
  • the UE may declare RLF.
  • a UE may attempt to transmit SL data (eg, a TX UE), and a peer UE may attempt to transmit SL data (eg, a TX UE). , RX UE).
  • SL data eg, a TX UE
  • peer UE may attempt to transmit SL data (eg, a TX UE).
  • RX UE RX UE
  • the UE may want to configure the SL DRX configuration to the peer UE.
  • the UE may configure SL DRX for the peer UE and may perform a sidelink RRC reconfiguration procedure.
  • HARQ feedback may be enabled for the UE.
  • the UE may run a timer (eg, T400).
  • the UE may transmit a time stamp when transmitting an RRC reconfiguration sidelink message.
  • the peer UE can know when T400 was activated based on the time stamp.
  • step 3 the UE or peer UE may operate in consideration of the following cases.
  • the UE may maintain active time without operating SL DRX.
  • the peer UE may consider a minimum time. For example, the peer UE may transmit an RRC reset-related completion message (RRCReconfigurationCompleteSidelink) or an RRC reset-related failure message (RRCReconfigurationFailureSidelink) to the UE before the minimum time.
  • the minimum time may be determined based on the duration of the DRX cycle. For example, the minimum time may be determined based on T400.
  • the UE may declare the sidelink RLF considering the minimum time.
  • the UE may determine a sidelink radio link failure (RLF) based on the minimum time.
  • RLF sidelink radio link failure
  • a transmission profile (hereinafter referred to as a TX profile) may be expressed as follows.
  • the TX profile may express on/off of interlocked release and SL DRX.
  • the TX profile may be associated with service type/type.
  • the TX profile may include information on interlocked releases and information on on/off of SL DRX.
  • profile #1 may include at least one of release 16 information and SL DRX off information.
  • profile #2 may include information on release 17 and information on SL DRX on.
  • profile #3 may include information about release 17 and SL DRX off.
  • the TX profile may express an interlocked release and a QoS flow ID. That is, information on SL DRX on/off may be preset for each QoS flow ID, for example.
  • the TX profile may be associated with service type/type.
  • the TX profile may include information about an interlocked release and information about a QoS flow ID.
  • profile #1 may include information on release 16 and information on QoS Flow #1 (eg, QoS Flow #1 is set to SL DRX off).
  • Profile #2 may include information on Release 16 and information on QoS Flow #2 (eg, QoS Flow #2 is set to SL DRX Off).
  • Profile #3 may include information on Release 17 and information on QoS Flow #3 (eg, QoS Flow #3 is set to SL DRX On).
  • Profile #4 may include information on Release 17 and information on QoS Flow #4 (eg, QoS Flow #4 is set to SL DRX Off).
  • the TX profile may represent a QoS flow ID to which information on SL DRX on/off is linked. That is, information on SL DRX on/off may be preset for each QoS flow ID, for example.
  • the TX profile may be associated with service type/type.
  • the TX profile may include information on a QoS flow ID to which information on SL DRX on/off is linked.
  • profile #1 may include information about QoS Flow #1 (eg, QoS Flow #1 is set to SL DRX On).
  • profile #2 may include information about QoS Flow #2 (eg, QoS Flow #2 is set to SL DRX off).
  • the TX profile may represent a logical channel ID to which information on SL DRX on/off is linked. That is, information on SL DRX on/off may be preset for each logical channel ID, for example.
  • the TX profile may be associated with service type/type.
  • the TX profile may include information on a logical channel ID to which information on SL DRX on/off is linked.
  • profile #1 may include information about logical channel #1 (eg, logical channel #1 is set to SL DRX on).
  • profile #2 may include information about logical channel #2 (eg, logical channel #2 is set to SL DRX off).
  • a TX profile may be preset for the UE.
  • a UE may receive a TX profile from a base station/network.
  • a UE may receive a TX profile from a base station/network through a system information block (SIB).
  • SIB system information block
  • Various embodiments of the present disclosure may solve a problem of loss due to interruption occurring during Uu BWP switching.
  • various embodiments of the present disclosure solve the problem of loss due to interruption occurring during SL BWP switching when the terminal supports a plurality of SL BWPs (Multiple Bandwidth Part) can be solved
  • Timers included in common (Default/Common) SL DRX settings as well as parameters included in UE-pair specific SL DRX settings, UE-pair specific SL DRX patterns, UE-pair specific SL DRX settings, It can be applied to the timer included in the UE-pair specific SL DRX configuration.
  • 'Onduration' may be an active time interval.
  • the active time may be a period in which a radio signal is received/transmitted in a wake up state (RF module is “on”).
  • 'Offduration' may be a sleep time period.
  • the sleep time period may be a period operating in a sleep mode state (RF module is “off”) for power saving.
  • the transmitting UE may not operate in the sleep mode compulsorily during the sleep time period.
  • the terminal may be permitted to operate in an active time for a sensing operation/transmission operation even during the sleep time.
  • parameters (eg, threshold values) related to various embodiments of the present disclosure include resource pool, congestion level, service priority, service type, QoS requirements (eg, latency ), reliability), PQI, traffic type (eg, periodic generation, aperiodic generation), or SL transmission resource allocation mode (mode 1, mode 2), it can be set differently or independently .
  • a resource pool eg, a resource pool in which PSFCH is configured, a resource pool in which PSFCH is not configured
  • service/packet type e.g, URLLC/EMBB traffic, reliability, latency
  • PQI e.g., PQI
  • PFI cast type
  • congestion level e.g CBR
  • 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, PUCCH-based SL HARQ feedback reporting operation Whether to set, whether to perform pre-emption, whether to perform re-evaluation, re-selection of resources based on pre-emption, if necessary, re-selection of resources based on re-evaluation, L1 source identifier, L1 destination identifier, L2 source
  • parameter setting values related to various embodiments of the present disclosure may include a resource pool (eg, a resource pool in which PSFCH is set, a resource pool in which PSFCH is not set), service / packet type, priority, QoS requirements ( For example, URLLC/EMBB traffic, reliability, latency), PQI, PFI, cast type (eg unicast, groupcast, broadcast), congestion level (eg CBR), resource pool congestion level, SL HARQ feedback scheme (eg, NACK only feedback scheme, ACK/NACK feedback scheme), MAC PDU transmission with HARQ feedback enabled, MAC PDU transmission with HARQ feedback disabled, PUCCH-based SL HARQ feedback Whether to set reporting operation, whether to perform pre-emption, whether to perform re-evaluation, re-selection of resources based on pre-emption, if necessary, re-selection of resources based on re-evaluation, L1 source identifier, L1 Destination identifier, L2 source identifier,
  • a certain amount of time may be a time during which a UE operates as an active time for a predefined time to receive a sidelink signal or sidelink data from a counterpart UE.
  • a certain amount of time is a timer (SL DRX retransmission timer, SL DRX inactivity timer, active time in the DRX operation of the RX UE) for the UE to receive the sidelink signal or sidelink data from the other UE. It can be a time that operates as an active time as much as the timer) time.
  • Various embodiments of the present disclosure may be applied to millimeter wave (mmWave) SL operation. Applicability of various embodiments of the present disclosure may be applied to a silver millimeter wave (mmWave) SL operation. Parameter setting values related to various embodiments of the present disclosure may be applied to millimeter wave (mmWave) SL operation.
  • FIG. 9 illustrates a procedure in which a receiving terminal performs SL DRX based on a transmission-related profile according to an embodiment of the present disclosure.
  • the embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.
  • the receiving terminal may receive SL DRX-related settings from the transmitting terminal.
  • the receiving terminal may perform SL DRX based on a configuration related to SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on that the information related to the release is the first release and (ii) that the SL DRX is on.
  • a first release may be Rel-17 and a second release may be Rel-16.
  • a profile related to transmission may be preset for a receiving terminal.
  • a receiving terminal may receive a profile related to transmission from a base station or a network.
  • a profile related to transmission may be transmitted from an upper layer of a receiving terminal to a lower layer.
  • information related to release and information about on or off of SL DRX may be linked to a quality of service (QoS) flow ID.
  • QoS quality of service
  • on or off of the SL DRX may be determined based on the QoS flow ID.
  • information related to release and information on on or off of the SL DRX may be linked to a logical channel ID.
  • on or off of the SL DRX may be determined based on the logical channel ID.
  • the SL DRX may be turned off.
  • configuration related to the SL DRX may be received through an RRC reconfiguration message.
  • the timer associated with the RRC resetting message may operate based on the fact that the RRC resetting message is transmitted by the transmitting terminal and the transmitting terminal receives an ACK from the receiving terminal. For example, based on whether a timer related to the RRC reset message is running, the active time of the transmitting terminal may be maintained.
  • the RRC reset message may include information about the timer.
  • radio link failure (RLF) may be determined based on expiration of a timer related to the RRC reset message.
  • FIG. 10 illustrates a method in which a first device performs SL DRX based on a profile related to transmission, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.
  • the first device 100 may receive settings related to SL DRX from the second device 200.
  • the first device 100 may perform SL DRX based on a configuration related to SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on that the information related to the release is the first release and (ii) that the SL DRX is on.
  • a profile related to transmission may be preset for the first device 100 .
  • the first device 100 may receive a profile related to transmission from a base station or a network.
  • a profile related to transmission may be transferred from an upper layer of the first device 100 to a lower layer.
  • information related to release and information about on or off of SL DRX may be linked to a quality of service (QoS) flow ID.
  • QoS quality of service
  • on or off of the SL DRX may be determined based on the QoS flow ID.
  • information related to release and information on on or off of the SL DRX may be linked to a logical channel ID.
  • on or off of the SL DRX may be determined based on the logical channel ID.
  • the SL DRX may be turned off.
  • configuration related to the SL DRX may be received through an RRC reconfiguration message.
  • the timer associated with the RRC reset message is dependent on transmission of the RRC reset message by the second device 200 and receipt of an ACK from the first device 100 by the second device 200. based on which it can operate.
  • the active time of the second device 200 may be maintained based on whether a timer related to the RRC reset message is running.
  • the RRC reset message may include information about the timer.
  • radio link failure (RLF) may be determined based on expiration of a timer related to the RRC reset message.
  • the processor 102 of the first device 100 may control the transceiver 106 to receive settings related to SL DRX from the second device 200 . And, for example, the processor 102 of the first device 100 may perform SL DRX based on a configuration related to SL DRX and a profile related to transmission.
  • a first device for performing wireless communication may include one or more memories for storing instructions; one or more transceivers; and one or more processors connecting the one or more memories and the one or more transceivers.
  • the one or more processors execute the instructions to receive settings related to SL DRX (sidelink discontinuous reception) from the second device, and configure the SL DRX based on a configuration related to the SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of the SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • an apparatus configured to control a first terminal.
  • one or more processors and one or more memories executablely coupled by the one or more processors and storing instructions.
  • the one or more processors execute the instructions to receive settings related to SL DRX (sidelink discontinuous reception) from a second terminal, and configure the SL DRX based on a configuration related to the SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of the SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • a non-transitory computer readable storage medium recording instructions may be provided.
  • the instructions when executed, cause a first device to: receive settings related to sidelink discontinuous reception (SL DRX) from a second device, based on settings related to the SL DRX and a profile related to transmission
  • the SL DRX may be performed.
  • a profile related to transmission may include information related to release and information about on or off of the SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • FIG. 11 illustrates a method in which a second device performs SL DRX based on a profile related to transmission, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.
  • the second device 200 may transmit settings related to SL DRX to the first device 100.
  • the second device 200 may perform SL DRX based on a configuration related to SL DRX and a profile related to transmission.
  • a profile related to transmission may include information related to release and information about on or off of SL DRX.
  • release-related information may include a first release or a second release.
  • the SL DRX may be performed based on that the information related to the release is the first release and (ii) that the SL DRX is on.
  • a profile related to transmission may be preset for the second device 200 .
  • the second device 200 may receive a profile related to transmission from a base station or a network.
  • a profile related to transmission may be transferred from an upper layer of the second device 200 to a lower layer.
  • information related to release and information about on or off of SL DRX may be linked to a quality of service (QoS) flow ID.
  • QoS quality of service
  • on or off of the SL DRX may be determined based on the QoS flow ID.
  • information related to release and information on on or off of the SL DRX may be linked to a logical channel ID.
  • on or off of the SL DRX may be determined based on the logical channel ID.
  • the SL DRX may be turned off.
  • configuration related to the SL DRX may be received through an RRC reconfiguration message.
  • the timer associated with the RRC reset message is dependent on transmission of the RRC reset message by the second device 200 and receipt of an ACK from the first device 100 by the second device 200. based on which it can operate.
  • the active time of the second device 200 may be maintained based on whether a timer related to the RRC reset message is running.
  • the RRC reset message may include information about the timer.
  • radio link failure (RLF) may be determined based on expiration of a timer related to the RRC reset message.
  • the processor 202 of the second device 200 may control the transceiver 206 to transmit settings related to SL DRX to the first device 100 .
  • the processor 202 of the second device 200 may control the transceiver 206 to perform SL DRX based on settings related to SL DRX and profiles related to transmission.
  • a second device performing wireless communication may be provided.
  • a first device may include one or more memories for storing instructions; one or more transceivers; and one or more processors connecting the one or more memories and the one or more transceivers.
  • the one or more processors execute the instructions to transmit settings related to sidelink discontinuous reception (SL DRX) to the first device, and to configure the SL DRX based on a profile related to settings and transmission related to the SL DRX.
  • the profile related to the transmission may include information related to release and information about on or off of the SL DRX.
  • information related to the release may include a first release or a second release.
  • the SL DRX may be performed based on (i) that the information related to the release is the first release and (ii) that the SL DRX is on.
  • FIG. 12 illustrates a communication system 1, according to an embodiment of the present disclosure.
  • the embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.
  • a communication system 1 to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network.
  • the wireless device means a device that performs communication using a radio access technology (eg, 5G New RAT (NR), Long Term Evolution (LTE)), and may be referred to as a communication/wireless/5G device.
  • wireless devices include robots 100a, vehicles 100b-1 and 100b-2, XR (eXtended Reality) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400.
  • IoT Internet of Thing
  • the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like.
  • the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
  • UAV Unmanned Aerial Vehicle
  • XR devices include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) installed in vehicles, televisions, smartphones, It may be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like.
  • a portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, a smart glass), a computer (eg, a laptop computer, etc.), and the like.
  • Home appliances may include a TV, a refrigerator, a washing machine, and the like.
  • IoT devices may include sensors, smart meters, and the like.
  • a base station and a network may also be implemented as a wireless device, and a specific wireless device 200a may operate as a base station/network node to other wireless devices.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of the present specification may include Narrowband Internet of Things for low power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. no.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of the present specification may perform communication based on LTE-M technology.
  • LTE-M technology may be an example of LPWAN technology, and may be called various names such as eMTC (enhanced machine type communication).
  • LTE-M technologies are 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) It may be implemented in at least one of various standards such as LTE M, and is not limited to the above-mentioned names.
  • the wireless communication technology implemented in the wireless devices 100a to 100f of the present specification includes at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low power communication. It may include any one, and is not limited to the above-mentioned names.
  • 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 can be called various names.
  • PANs personal area networks
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200 .
  • AI Artificial Intelligence
  • the network 300 may be configured using a 3G network, a 4G (eg LTE) network, or a 5G (eg NR) network.
  • the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but may also communicate directly (eg, sidelink communication) without going through the base station/network.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle to vehicle (V2V)/vehicle to everything (V2X) communication).
  • IoT devices eg, sensors
  • IoT devices may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.
  • Wireless communication/connection 150a, 150b, and 150c may be performed between the wireless devices 100a to 100f/base station 200 and the base station 200/base station 200.
  • wireless communication/connection refers to various wireless connections such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g. relay, Integrated Access Backhaul (IAB)).
  • IAB Integrated Access Backhaul
  • Wireless communication/connection (150a, 150b, 150c) allows wireless devices and base stations/wireless devices, and base stations and base stations to transmit/receive radio signals to/from each other.
  • the wireless communication/connection 150a, 150b, and 150c may transmit/receive signals through various physical channels.
  • various signal processing processes eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.
  • resource allocation processes etc.
  • FIG. 13 illustrates a wireless device according to an embodiment of the present disclosure.
  • the embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive radio signals through various radio access technologies (eg, LTE, NR).
  • ⁇ the first wireless device 100 and the second wireless device 200 ⁇ refer to the ⁇ wireless device 100x and the base station 200 ⁇ of FIG. 12 and/or the ⁇ wireless device 100x and the wireless device 100x. ⁇ can correspond.
  • the first wireless device 100 includes one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and/or one or more antennas 108.
  • the processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or flowcharts of operations disclosed herein.
  • the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a radio signal including the first information/signal through the transceiver 106 .
  • the processor 102 may receive a radio signal including the second information/signal through the transceiver 106, and then store information obtained from signal processing of the second information/signal in the memory 104.
  • the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102 .
  • memory 104 may perform some or all of the processes controlled by processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them.
  • the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (eg, LTE, NR).
  • the transceiver 106 may be coupled to the processor 102 and may transmit and/or receive wireless signals via one or more antennas 108 .
  • the transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • the second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
  • Processor 202 controls memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein.
  • the processor 202 may process information in the memory 204 to generate third information/signal, and transmit a radio signal including the third information/signal through the transceiver 206.
  • the processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 and store information obtained from signal processing of the fourth information/signal in the memory 204 .
  • the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202 .
  • memory 204 may perform some or all of the processes controlled by processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein. It may store software codes including them.
  • the processor 202 and memory 204 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (eg, LTE, NR).
  • the transceiver 206 may be coupled to the processor 202 and may transmit and/or receive wireless signals via one or more antennas 208 .
  • the transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be used interchangeably with an RF unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) in accordance with the descriptions, functions, procedures, proposals, methods and/or operational flow charts disclosed herein.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • processors 102, 202 may generate messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams disclosed herein.
  • One or more processors 102, 202 generate PDUs, SDUs, messages, control information, data or signals (e.g., baseband signals) containing information according to the functions, procedures, proposals and/or methods disclosed herein , can be provided to one or more transceivers 106, 206.
  • One or more processors 102, 202 may receive signals (eg, baseband signals) from one or more transceivers 106, 206, and descriptions, functions, procedures, proposals, methods, and/or flowcharts of operations disclosed herein PDUs, SDUs, messages, control information, data or information can be obtained according to these.
  • signals eg, baseband signals
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor or microcomputer.
  • One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • firmware or software may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like.
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed herein may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and It can be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.
  • One or more memories 104, 204 may be coupled with one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions.
  • One or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • One or more memories 104, 204 may be located internally and/or external to one or more processors 102, 202. Additionally, one or more memories 104, 204 may be coupled to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
  • One or more transceivers 106, 206 may transmit user data, control information, radio signals/channels, etc., as referred to in the methods and/or operational flow charts herein, to one or more other devices.
  • One or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in descriptions, functions, procedures, proposals, methods and/or operational flow charts, etc. disclosed herein from one or more other devices. there is.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive wireless signals.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Additionally, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled with one or more antennas 108, 208, and one or more transceivers 106, 206 via one or more antennas 108, 208, as described herein, function. , procedures, proposals, methods and / or operation flowcharts, etc. can be set to transmit and receive user data, control information, radio signals / channels, etc.
  • one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers (106, 206) convert the received radio signals/channels from RF band signals in order to process the received user data, control information, radio signals/channels, etc. using one or more processors (102, 202). It can be converted into a baseband signal.
  • One or more transceivers 106 and 206 may convert user data, control information, and radio signals/channels processed by one or more processors 102 and 202 from baseband signals to RF band signals.
  • one or more of the transceivers 106, 206 may include (analog) oscillators and/or filters.
  • FIG. 14 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure.
  • the embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.
  • the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060.
  • the operations/functions of FIG. 14 may be performed by processors 102 and 202 and/or transceivers 106 and 206 of FIG. 13 .
  • the hardware elements of FIG. 14 may be implemented in processors 102 and 202 and/or transceivers 106 and 206 of FIG. 13 .
  • blocks 1010-1060 may be implemented in processors 102 and 202 of FIG. 13 .
  • blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 13
  • block 1060 may be implemented in the transceivers 106 and 206 of FIG. 13 .
  • the codeword may be converted into a radio signal through the signal processing circuit 1000 of FIG. 14 .
  • a codeword is an encoded bit sequence of an information block.
  • Information blocks may include transport blocks (eg, UL-SCH transport blocks, DL-SCH transport blocks).
  • Radio signals may be transmitted through various physical channels (eg, PUSCH, PDSCH).
  • the codeword may be converted into a scrambled bit sequence by the scrambler 1010.
  • a scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of a wireless device.
  • the scrambled bit sequence may be modulated into a modulation symbol sequence by modulator 1020.
  • the modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), and the like.
  • the complex modulation symbol sequence may be mapped to one or more transport layers by the layer mapper 1030.
  • Modulation symbols of each transport layer may be mapped to the corresponding antenna port(s) by the precoder 1040 (precoding).
  • the output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the N*M precoding matrix W.
  • N is the number of antenna ports and M is the number of transport layers.
  • the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transformation) on complex modulation symbols. Also, the precoder 1040 may perform precoding without performing transform precoding.
  • the resource mapper 1050 may map modulation symbols of each antenna port to time-frequency resources.
  • the time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain.
  • the signal generator 1060 generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices through each antenna.
  • the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), a frequency uplink converter, and the like.
  • IFFT inverse fast Fourier transform
  • CP cyclic prefix
  • DAC digital-to-analog converter
  • the signal processing process for the received signal in the wireless device may be configured in reverse to the signal processing process 1010 to 1060 of FIG. 14 .
  • wireless devices eg, 100 and 200 of FIG. 13
  • the received radio signal may be converted into a baseband signal through a signal restorer.
  • the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module.
  • ADC analog-to-digital converter
  • FFT fast Fourier transform
  • the baseband signal may be restored to a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scramble process.
  • a signal processing circuit for a received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.
  • FIG. 15 illustrates a wireless device according to an embodiment of the present disclosure.
  • a wireless device may be implemented in various forms according to use-case/service (see FIG. 12).
  • the embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.
  • wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 13, and include various elements, components, units/units, and/or modules. ) can be configured.
  • the wireless devices 100 and 200 may include a communication unit 110 , a control unit 120 , a memory unit 130 and an additional element 140 .
  • the communication unit may include communication circuitry 112 and transceiver(s) 114 .
  • communication circuitry 112 may include one or more processors 102, 202 of FIG. 13 and/or one or more memories 104, 204.
  • transceiver(s) 114 may include one or more transceivers 106, 206 of FIG. 13 and/or one or more antennas 108, 208.
  • the control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls overall operations of the wireless device. For example, the control unit 120 may control electrical/mechanical operations of the wireless device based on programs/codes/commands/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to the outside (eg, another communication device) through the communication unit 110 through a wireless/wired interface, or transmits the information stored in the memory unit 130 to the outside (eg, another communication device) through the communication unit 110. Information received through a wireless/wired interface from other communication devices) may be stored in the memory unit 130 .
  • the additional element 140 may be configured in various ways according to the type of wireless device.
  • the additional element 140 may include at least one of a power unit/battery, an I/O unit, a driving unit, and a computing unit.
  • the wireless device may be a robot (Fig. 12, 100a), a vehicle (Fig. 12, 100b-1, 100b-2), an XR device (Fig. 12, 100c), a mobile device (Fig. 12, 100d), a home appliance. (FIG. 12, 100e), IoT device (FIG.
  • digital broadcast terminal digital broadcast terminal
  • hologram device public safety device
  • MTC device medical device
  • fintech device or financial device
  • security device climate/environmental device
  • It may be implemented in the form of an AI server/device (Fig. 12, 400), a base station (Fig. 12, 200), a network node, and the like.
  • Wireless devices can be mobile or used in a fixed location depending on the use-case/service.
  • various elements, components, units/units, and/or modules in the wireless devices 100 and 200 may be entirely interconnected through a wired interface or at least partially connected wirelessly through the communication unit 110.
  • the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first units (eg, 130 and 140) are connected through the communication unit 110.
  • the control unit 120 and the first units eg, 130 and 140
  • each element, component, unit/unit, and/or module within the wireless device 100, 200 may further include one or more elements.
  • the control unit 120 may be composed of one or more processor sets.
  • the controller 120 may include a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, a memory control processor, and the like.
  • the memory unit 130 may include random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.
  • a portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, a smart glass), and a portable computer (eg, a laptop computer).
  • a mobile device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).
  • MS mobile station
  • UT user terminal
  • MSS mobile subscriber station
  • SS subscriber station
  • AMS advanced mobile station
  • WT wireless terminal
  • a portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ) may be included.
  • the antenna unit 108 may be configured as part of the communication unit 110 .
  • Blocks 110 to 130/140a to 140c respectively correspond to blocks 110 to 130/140 of FIG. 15 .
  • the communication unit 110 may transmit/receive signals (eg, data, control signals, etc.) with other wireless devices and base stations.
  • the controller 120 may perform various operations by controlling components of the portable device 100 .
  • the control unit 120 may include an application processor (AP).
  • the memory unit 130 may store data/parameters/programs/codes/commands necessary for driving the portable device 100 .
  • the memory unit 130 may store input/output data/information.
  • the power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, and the like.
  • the interface unit 140b may support connection between the portable device 100 and other external devices.
  • the interface unit 140b may include various ports (eg, audio input/output ports and video input/output ports) for connection with external devices.
  • the input/output unit 140c may receive or output image information/signal, audio information/signal, data, and/or information input from a user.
  • the input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.
  • the input/output unit 140c obtains information/signals (eg, touch, text, voice, image, video) input from the user, and the acquired information/signals are stored in the memory unit 130.
  • the communication unit 110 may convert the information/signal stored in the memory into a wireless signal, and directly transmit the converted wireless signal to another wireless device or to a base station.
  • the communication unit 110 may receive a radio signal from another wireless device or a base station and then restore the received radio signal to original information/signal. After the restored information/signal is stored in the memory unit 130, it may be output in various forms (eg, text, voice, image, video, haptic) through the input/output unit 140c.
  • Vehicles or autonomous vehicles may be implemented as mobile robots, vehicles, trains, manned/unmanned aerial vehicles (AVs), ships, and the like.
  • AVs manned/unmanned aerial vehicles
  • the embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.
  • a vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit.
  • a portion 140d may be included.
  • the antenna unit 108 may be configured as part of the communication unit 110 .
  • Blocks 110/130/140a to 140d respectively correspond to blocks 110/130/140 of FIG. 15 .
  • the communication unit 110 may transmit/receive signals (eg, data, control signals, etc.) with external devices such as other vehicles, base stations (e.g. base stations, roadside base stations, etc.), servers, and the like.
  • the controller 120 may perform various operations by controlling elements of the vehicle or autonomous vehicle 100 .
  • the controller 120 may include an Electronic Control Unit (ECU).
  • the driving unit 140a may drive the vehicle or autonomous vehicle 100 on the ground.
  • the driving unit 140a may include an engine, a motor, a power train, a wheel, a brake, a steering device, and the like.
  • the power supply unit 140b supplies power to the vehicle or autonomous vehicle 100, and may include a wired/wireless charging circuit, a battery, and the like.
  • the sensor unit 140c may obtain vehicle conditions, surrounding environment information, and user information.
  • the sensor unit 140c includes an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, and a vehicle forward.
  • IMU inertial measurement unit
  • /Can include a reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illuminance sensor, pedal position sensor, and the like.
  • the autonomous driving unit 140d includes a technology for maintaining a driving lane, a technology for automatically adjusting speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and a technology for automatically setting a route when a destination is set and driving. technology can be implemented.
  • the communication unit 110 may receive map data, traffic information data, and the like from an external server.
  • the autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the acquired data.
  • the controller 120 may control the driving unit 140a so that the vehicle or autonomous vehicle 100 moves along the autonomous driving path according to the driving plan (eg, speed/direction adjustment).
  • the communicator 110 may non-/periodically obtain the latest traffic information data from an external server and obtain surrounding traffic information data from surrounding vehicles.
  • the sensor unit 140c may acquire vehicle state and surrounding environment information.
  • the autonomous driving unit 140d may update an autonomous driving route and a driving plan based on newly acquired data/information.
  • the communication unit 110 may transmit information about a vehicle location, an autonomous driving route, a driving plan, and the like to an external server.
  • the external server may predict traffic information data in advance using AI technology based on information collected from the vehicle or self-driving vehicles, and may provide the predicted traffic information data to the vehicle or self-driving vehicles.

Landscapes

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

Abstract

Sont divulgués un procédé permettant à un premier dispositif de mettre en œuvre une communication sans fil, et un dispositif le prenant en charge. Le procédé peut comprendre les étapes consistant à : recevoir une configuration relative à une réception discontinue de liaison latérale (DRX SL) provenant d'un second dispositif, et mettre en œuvre la DRX SL sur la base de la configuration relative à la DRX SL et d'un profil relatif à la transmission. Par exemple : le profil relatif à la transmission peut comprendre des informations relatives à la libération, et des informations indiquant si la DRX SL est activée ou n'est pas activée ; les informations relatives à la libération peuvent comprendre une première libération et une seconde libération ; et (i) les informations relatives à la libération représentent la première libération, et (Ii) la DRX SL pouvant être mise en œuvre sur la base du fait que la DRX SL est activée.
PCT/KR2022/006309 2021-08-04 2022-05-03 Procédé et dispositif de mise en œuvre de drx sl sur la base d'un profil de transmission dans nr v2x WO2023013851A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163229478P 2021-08-04 2021-08-04
US63/229,478 2021-08-04

Publications (1)

Publication Number Publication Date
WO2023013851A1 true WO2023013851A1 (fr) 2023-02-09

Family

ID=85155847

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/006309 WO2023013851A1 (fr) 2021-08-04 2022-05-03 Procédé et dispositif de mise en œuvre de drx sl sur la base d'un profil de transmission dans nr v2x

Country Status (1)

Country Link
WO (1) WO2023013851A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021119474A1 (fr) * 2019-12-13 2021-06-17 Convida Wireless, Llc Réception discontinue de liaison latérale nr
WO2021147011A1 (fr) * 2020-01-22 2021-07-29 Lenovo (Beijing) Limited Procédé et dispositif d'alignement de configuration drx de liaison latérale

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021119474A1 (fr) * 2019-12-13 2021-06-17 Convida Wireless, Llc Réception discontinue de liaison latérale nr
WO2021147011A1 (fr) * 2020-01-22 2021-07-29 Lenovo (Beijing) Limited Procédé et dispositif d'alignement de configuration drx de liaison latérale

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V16.5.0, 6 July 2021 (2021-07-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 959, XP052030220 *
OPPO: "Discussion on DRX configuration and DRX timers", 3GPP DRAFT; R2-2104835, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20210501, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052006585 *
QUALCOMM INCORPORATED: "Discussion on SL DRX Timers and Others", 3GPP DRAFT; R2-2105906, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20210519 - 20210527, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052007364 *

Similar Documents

Publication Publication Date Title
WO2022203413A1 (fr) Procédé et dispositif par lesquels un équipement utilisateur de réception réalise un fonctionnement d'économie d'énergie en fonction de psfch dans nr v2x
WO2022146105A1 (fr) Procédé de fonctionnement de drx en sl en tenant compte du fonctionnement en mode 1 du terminal de transmission dans v2x nr
WO2022149904A1 (fr) Procédé et dispositif pour prioriser une rétroaction harq dans un système nr v2x
WO2022086280A1 (fr) Procédé et dispositif de réalisation de fonctionnement de drx en sl dans une v2x de nr
WO2022086131A1 (fr) Procédé et dispositif d'alignement de temps actif de sl drx dans un nr v2x
WO2023075548A1 (fr) Procédé et appareil de réglage de temporisateur rtt harq sl dans nr v2x
WO2022240135A1 (fr) Procédé et dispositif pour déterminer des configurations drx sl dans v2x nr
WO2023014129A1 (fr) Procédé et dispositif de réalisation d'opération de drx de sl en v2x sous new radio
WO2022235116A1 (fr) Procédé et dispositif pour sélectionner une ressource de transmission sur la base d'une opération de temporisateur de rtt de harq de drx de sl d'un dispositif de réception dans v2x nr
WO2022191476A1 (fr) Procédé et dispositif pour réaliser une procédure lcp sur la base d'un temps actif dans une technologie v2x nr
WO2022149853A1 (fr) Procédé et dispositif de traitement de transition d'état dans un système de communication sans fil
WO2023013851A1 (fr) Procédé et dispositif de mise en œuvre de drx sl sur la base d'un profil de transmission dans nr v2x
WO2023277500A1 (fr) Procédé et dispositif permettant de savoir si une opération drx sl est prise en charge dans v2x nr
WO2022255788A1 (fr) Procédé et dispositif de réalisation d'opération drx sl dans v2x nr sur la base d'un état rrc
WO2023022491A1 (fr) Procédé et dispositif de configuration d'un paramètre relatif à une opération drx sl dans un v2x nr
WO2023043252A1 (fr) Procédé et dispositif de fonctionnement de mode 1 de sl compte tenu du temps actif de réception discontinue de sl d'un terminal de réception dans nr v2x
WO2022239958A1 (fr) Procédé et dispositif de demande à une station de base de ressource sl sur la base d'un temps actif relatif à une drx en nr v2x
WO2023033579A1 (fr) Procédé et dispositif pour réaliser une communication sl sur la base d'une comptabilité drx sl dans nr v2x
WO2023132708A1 (fr) Procédé et dispositif d'opération d'économie d'énergie sur la base d'une réservation de ressource périodique dans nr v2x
WO2022265419A1 (fr) Procédé et appareil pour faire fonctionner un temporisateur sl drx sur la base d'une destination de diffusion de groupe l2 id dans nr v2x
WO2023018279A1 (fr) Procédé et dispositif de génération d'une autorisation sur la base d'une sl drx dans nr v2x
WO2023080683A1 (fr) Procédé et dispositif d'initiation d'un temporisateur de drx en v2x nr
WO2023121306A1 (fr) Procédé et dispositif de fonctionnement de drx sl à base d'informations de ressource de réservation périodique dans v2x nr
WO2023132707A1 (fr) Procédé et dispositif pour faire fonctionner un temporisateur drx sl d'un terminal recevant un message dcr dans nr v2x
WO2023018283A1 (fr) Procédé et dispositif de mise en œuvre de communication sl sur la base d'une compatibilité de drx sl dans v2x nr

Legal Events

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

Ref document number: 22853231

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE