WO2023014129A1 - Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 - Google Patents
Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 Download PDFInfo
- Publication number
- WO2023014129A1 WO2023014129A1 PCT/KR2022/011596 KR2022011596W WO2023014129A1 WO 2023014129 A1 WO2023014129 A1 WO 2023014129A1 KR 2022011596 W KR2022011596 W KR 2022011596W WO 2023014129 A1 WO2023014129 A1 WO 2023014129A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- drx
- transmission
- profile
- default
- configuration
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 86
- 230000005540 biological transmission Effects 0.000 claims abstract description 148
- 238000004891 communication Methods 0.000 claims abstract description 143
- 230000015654 memory Effects 0.000 claims description 56
- 238000012545 processing Methods 0.000 claims description 22
- 230000008878 coupling Effects 0.000 claims 2
- 238000010168 coupling process Methods 0.000 claims 2
- 238000005859 coupling reaction Methods 0.000 claims 2
- 239000010410 layer Substances 0.000 description 78
- 238000005516 engineering process Methods 0.000 description 31
- 230000006870 function Effects 0.000 description 23
- 230000008569 process Effects 0.000 description 18
- 230000011664 signaling Effects 0.000 description 16
- 238000013468 resource allocation Methods 0.000 description 14
- 238000013473 artificial intelligence Methods 0.000 description 6
- 230000008685 targeting Effects 0.000 description 6
- 238000013507 mapping Methods 0.000 description 5
- 230000000737 periodic effect Effects 0.000 description 5
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 4
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 125000004122 cyclic group Chemical group 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 239000004984 smart glass Substances 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 108010002947 Connectin Proteins 0.000 description 1
- 230000027311 M phase Effects 0.000 description 1
- 108091029480 NONCODE Proteins 0.000 description 1
- 102100026260 Titin Human genes 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000010187 selection method Methods 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 239000010454 slate Substances 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000005477 standard model Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 208000037918 transfusion-transmitted disease Diseases 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
-
- 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
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/02—Selection of wireless resources by user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- 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
- H04W84/00—Network topologies
- H04W84/005—Moving wireless networks
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
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
- FIG. 1 is a diagram for explaining and comparing V2X communication based on RAT before NR and V2X communication based on NR.
- the embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.
- V2X communication RAT prior to NR provides safety services based on V2X messages such as BSM (Basic Safety Message), CAM (Cooperative Awareness Message), and DENM (Decentralized Environmental Notification Message) This has been mainly discussed.
- the V2X message may include location information, dynamic information, attribute information, and the like.
- a UE may transmit a CAM of a periodic message type and/or a DENM of an event triggered message type to another UE.
- V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, and the like.
- UE #X may simultaneously perform other SL communication with UE #Z.
- UE #X determines/configures the SL DRX configuration of UE #Y
- UE #X considers the generation pattern of packets to be transmitted to UE #Y as well as the generation pattern of packets to be transmitted to UE #Z. By doing so, you can minimize your own battery consumption. For example, after UE #X turns on its own RF, it can perform packet transmission to UE #Y and UE #Z as continuously as possible, and through this, UE #X can minimize its own battery consumption.
- packet transmission from UE #X to UE #Y is not performed based on the SL DRX setting associated with the unicast link, but , packet-related TX profile (and / or QoS profile), etc. If performed based on the SL DRX configuration associated with information, it may not be possible to achieve battery consumption minimization from the perspective of UE #X (described above).
- a method for performing wireless communication by the first device may be provided.
- the method may include obtaining a default sidelink (SL) discontinuous reception (DRX) setting; Acquiring a profile indicating whether the SL DRX is compatible; performing a first SL transmission based on the default SL DRX configuration based on the profile indicating that the SL DRX is compatible; Establishing a PC5 radio resource control (RRC) connection with a second device; obtaining SL DRX settings; Transmitting information related to the SL DRX configuration to the second device; and performing a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.
- RRC radio resource control
- a first device configured to perform wireless communication.
- the first device includes 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; based on the profile indicating that the SL DRX is compatible, controlling the one or more transceivers to perform a first SL transmission based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the second device; obtain SL DRX settings; controlling the one or more transceivers to transmit information related to the SL DRX configuration to the second device; and control the one or more transceivers to perform a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.
- RRC radio resource control
- a processing device configured to control a first device performing wireless communication.
- the processing device may include 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; based on the profile indicating that the SL DRX is compatible, performing a first SL transmission based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the second device; obtain SL DRX settings; transmits information related to the SL DRX configuration to the second device; and regardless of the profile, a second SL transmission may be performed to the second device based on the SL DRX configuration.
- RRC radio resource control
- FIG. 1 is a diagram for explaining and comparing V2X communication based on RAT before NR and V2X communication based on NR.
- FIG. 2 shows the structure of an NR system according to an embodiment of the present disclosure.
- FIG 3 illustrates a radio protocol architecture according to an embodiment of the present disclosure.
- FIG. 4 shows a structure of a radio frame of NR according to an embodiment of the present disclosure.
- FIG. 5 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure.
- FIG 6 shows an example of BWP according to an embodiment of the present disclosure.
- FIG. 7 shows a terminal performing V2X or SL communication according to an embodiment of the present disclosure.
- FIG. 8 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. 10 illustrates a method for performing wireless communication by a first device according to an embodiment of the present disclosure.
- FIG. 11 illustrates a method for a second device to perform wireless communication 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
- 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. 2 shows the structure of an NR system according to an embodiment of the present disclosure.
- the embodiment of FIG. 2 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. 2 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. 3 illustrates a radio protocol architecture according to an embodiment of the present disclosure.
- the embodiment of FIG. 3 may be combined with various embodiments of the present disclosure.
- (a) of FIG. 3 shows a radio protocol stack of a user plane for Uu communication
- (b) of FIG. 3 shows a radio protocol of a control plane for Uu communication. represents a stack.
- (c) of FIG. 3 shows a radio protocol stack of a user plane for SL communication
- (d) of FIG. 3 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. 4 shows a structure of a radio frame of NR according to an embodiment of the present disclosure.
- the embodiment of FIG. 4 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. 5 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure.
- the embodiment of FIG. 5 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. For energy saving, if the UE does not detect DCI for a certain period of time, the UE may switch the active BWP of the UE to a default BWP.
- 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. 6 shows an example of BWP according to an embodiment of the present disclosure.
- the embodiment of FIG. 6 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 UE 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.
- FIG. 7 shows a terminal performing V2X or SL communication according to an embodiment of the present disclosure.
- the embodiment of FIG. 7 may be combined with various embodiments of the present disclosure.
- terminal in V2X or SL communication may mainly mean a user's terminal.
- the base station may also be regarded as a kind of terminal.
- terminal 1 may be the first device 100 and terminal 2 may be the second device 200 .
- terminal 1 may select a resource unit corresponding to a specific resource in a resource pool representing a set of a series of resources. And, terminal 1 can transmit an SL signal using the resource unit.
- terminal 2 which is a receiving terminal, can receive a resource pool through which terminal 1 can transmit a signal, and can detect a signal of terminal 1 within the resource pool.
- the base station may inform the terminal 1 of the resource pool.
- another terminal may inform terminal 1 of a resource pool, or terminal 1 may use a previously set resource pool.
- a resource pool may be composed of a plurality of resource units, and each terminal may select one or a plurality of resource units to use for its own SL signal transmission.
- 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. 8 shows a terminal operation related to LTE transmission mode 1 or LTE transmission mode 3.
- (a) of FIG. 8 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. 8 shows a terminal operation related to LTE transmission mode 2 or LTE transmission mode 4.
- (b) of FIG. 8 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 perform resource scheduling to terminal 1 through PDCCH (eg, Downlink Control Information (DCI)) or RRC signaling (eg, Configured Grant Type 1 or Configured Grant Type 2), and terminal 1 may perform the resource scheduling.
- DCI Downlink Control Information
- RRC signaling eg, Configured Grant Type 1 or Configured Grant Type 2
- terminal 1 may perform the resource scheduling.
- V2X or SL communication with UE 2 may be performed according to resource scheduling.
- device 1 may transmit sidelink control information (SCI) to device 2 through physical sidelink control channel (PSCCH), and then transmit data based on the SCI to device 2 through physical sidelink shared channel (PSSCH).
- SCI sidelink control information
- PSCCH physical sidelink control channel
- PSSCH physical sidelink shared channel
- 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 set 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.
- terminal 1 which has selected a resource within the resource pool, transmits SCI to terminal 2 through PSCCH, and then transmits data based on the SCI to terminal 2 through PSSCH.
- FIG. 9 illustrates three cast types according to an embodiment of the present disclosure.
- the embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.
- FIG. 9(a) shows broadcast type SL communication
- FIG. 9(b) shows unicast type SL communication
- FIG. 9(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
- HARQ feedback and HARQ combining in the physical layer may be supported.
- the receiving terminal when the receiving terminal operates in resource allocation mode 1 or 2, the receiving terminal may receive a PSSCH from the transmitting terminal, and the receiving terminal may receive sidelink feedback control information (SFCI) through a physical sidelink feedback channel (PSFCH).
- SFCI sidelink feedback control information
- PSFCH physical sidelink feedback channel
- 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.
- RSRP reference signal received power
- the receiving terminal may transmit HARQ feedback for the PSSCH to the transmitting terminal.
- the receiving terminal may not transmit HARQ feedback for the PSSCH to the transmitting terminal.
- the transmitting terminal may inform the receiving terminal of the location of the transmitting terminal through SCI related to the PSSCH.
- the SCI associated with the PSSCH may be a second SCI.
- the receiving terminal may estimate or obtain a TX-RX distance based on the location of the receiving terminal and the location of the transmitting terminal.
- the receiving terminal decodes the SCI related to the PSSCH to know the communication range requirements used for the PSSCH.
- the time between PSFCH and PSSCH may be configured or preset.
- this may be indicated to the base station by a terminal within coverage using PUCCH.
- the transmitting terminal may transmit an indication to the serving base station of the transmitting terminal in a form such as Scheduling Request (SR)/Buffer Status Report (BSR) instead of HARQ ACK/NACK.
- SR Scheduling Request
- BSR Buffer Status Report
- the base station can schedule SL retransmission resources to the terminal.
- the time between PSFCH and PSSCH may be configured or preset.
- TDM between PSCCH/PSSCH and PSFCH may be allowed for the PSFCH format for SL in a slot.
- a sequence-based PSFCH format having one symbol may be supported.
- the one symbol may not be an automatic gain control (AGC) interval.
- the sequence-based PSFCH format can be applied to unicast and groupcast.
- PSFCH resources may be periodically configured in N slot intervals or may be configured in advance.
- N can be set to one or more values greater than or equal to 1.
- N can be 1, 2 or 4.
- HARQ feedback for transmission in a specific resource pool may be transmitted only through PSFCH on the specific resource pool.
- slot #(N + A) may contain PSFCH resources.
- A may be the smallest integer greater than or equal to K.
- K may be the number of logical slots. In this case, K may be the number of slots in the resource pool. Or, for example, K may be the number of physical slots. In this case, K may be the number of slots inside and outside the resource pool.
- the receiving terminal uses the PSFCH resource based on an implicit mechanism within a set resource pool. It is possible to determine the frequency domain and / or code domain of .
- the receiving terminal is selected from among a slot index related to PSCCH/PSSCH/PSFCH, a subchannel related to PSCCH/PSSCH, and/or an identifier for distinguishing each receiving terminal in a group for HARQ feedback based on groupcast option 2.
- the frequency domain and/or code domain of the PSFCH resource may be determined.
- the receiving terminal may determine the frequency domain and/or code domain of the PSFCH resource based on at least one of SL RSRP, SINR, L1 source ID, and/or location information.
- the UE when transmission of HARQ feedback through PSFCH and reception of HARQ feedback through PSFCH of the UE overlap, the UE transmits HARQ feedback through PSFCH or receives HARQ feedback through PSFCH based on a priority rule.
- the priority rule may be based on at least the priority indication of the relevant PSCCH/PSSCH.
- the terminal may select a specific HARQ feedback transmission based on a priority rule.
- the priority rule may be based on at least the priority indication of the relevant PSCCH/PSSCH.
- a transmitting terminal may be a terminal that transmits data to a (target) receiving terminal (RX UE).
- a TX UE may be a UE performing PSCCH and/or PSSCH transmission.
- a TX UE may be a UE that transmits an SL CSI-RS and/or SL CSI report request indicator to a (target) RX UE.
- the TX UE sends the (target) RX UE a (predefined) reference signal (e.g., PSSCH demodulation reference signal (DM-RS)) and/or SL (L1) RSRP to be used for SL (L1) RSRP measurement.
- DM-RS PSSCH demodulation reference signal
- the TX UE transmits a (control) channel (e.g., PSCCH, PSSCH, etc.) and/or It may be a terminal that transmits a reference signal (eg, DM-RS, CSI-RS, etc.) on the (control) channel.
- a control channel e.g., PSCCH, PSSCH, etc.
- a reference signal e.g, DM-RS, CSI-RS, etc.
- the receiving terminal determines whether decoding of data received from the transmitting terminal (TX UE) is successful and / or the detection / decoding success of the PSCCH (related to PSSCH scheduling) transmitted by the TX UE It may be a terminal that transmits SL HARQ feedback to the TX UE depending on whether or not.
- the RX UE may be a UE that transmits SL CSI to the TX UE based on the SL CSI-RS and/or the SL CSI report request indicator received from the TX UE.
- the RX UE transmits the SL (L1) RSRP measurement value measured based on the (predefined) reference signal and / or SL (L1) RSRP report request indicator received from the TX UE to the TX UE.
- the RX UE may be a terminal that transmits its own data to the TX UE.
- the RX UE is a terminal that performs an SL RLM operation and / or an SL RLF operation based on a (preset) (control) channel and / or a reference signal on the (control) channel received from the TX UE.
- the TX UE may transmit at least one of the following information to the RX UE through SCI.
- the TX UE may transmit at least one of the information below to the RX UE through a first SCI (SCI) and/or a second SCI (SCI).
- SCI first SCI
- SCI second SCI
- QoS information e.g., priority information
- the reference signal information may be information related to a pattern of (time-frequency) mapping resources of a DM-RS, RANK information, antenna port index information, antenna port number information, and the like.
- PSCCH may be mutually replaced/substituted with at least one of SCI, 1 st -stage SCI (SCI) and/or 2 nd -stage SCI (2 nd SCI).
- SCI 1 st -stage SCI
- 2 nd -stage SCI 2 nd SCI
- the SCI may be mutually replaced/substituted with at least one of the PSCCH, the first SCI, and/or the second SCI.
- the PSSCH may be mutually replaced/substituted with the second SCI and/or PSCCH.
- the first SCI including the first SCI configuration field group may be referred to as a 1st SCI
- a 2nd SCI including a 2nd SCI configuration field group may be referred to as a 2nd SCI.
- 1 st SCI and 2 nd SCI may be transmitted through different channels.
- 1 st SCI may be transmitted to a receiving terminal through PSCCH.
- the 2 nd SCI may be transmitted to the receiving terminal through an (independent) PSCCH or may be piggybacked and transmitted together with data through the PSSCH.
- configuration or “definition” may mean (pre)configuration from a base station or network.
- configuration or “definition” may mean resource pool specific (pre)configuration from a base station or network.
- a base station or a network may transmit information related to "configuration” or “definition” to a terminal.
- the base station or the network may transmit information related to "configuration” or “definition” to the terminal through predefined signaling.
- the predefined signaling may include at least one of RRC signaling, MAC signaling, PHY signaling, and/or SIB.
- configuration or “definition” may mean designation or configuration through pre-set signaling between terminals.
- information related to “configuration” or “definition” may be transmitted and received between terminals through preset signaling.
- the predefined signaling may be PC5 RRC signaling.
- RLF may be replaced/substituted with Out-of-Synch (OOS) and/or In-Synch (IS).
- OOS Out-of-Synch
- IS In-Synch
- a resource block may be mutually replaced/substituted with a subcarrier.
- a packet or traffic may be mutually replaced/substituted with a transport block (TB) or a medium access control protocol data unit (PDU) according to a transmission layer.
- a code block group CBG
- the source ID may be mutually replaced/substituted with the destination ID.
- the L1 ID may be mutually replaced/substituted with the L2 ID.
- the L1 ID may be an L1 source ID or an L1 destination ID.
- the L2 ID may be an L2 source ID or an L2 destination ID.
- the operation of reserving / selecting / determining retransmission resources by the TX UE is a potential (potential ) may mean an operation of reserving/selecting/determining a retransmission resource.
- a sub-selection window may be mutually replaced/substituted with a selection window and/or a preset number of resource sets within the selection window.
- SL MODE 1 is a resource allocation method or communication method in which a base station directly schedules SL transmission resources for a TX UE through predefined signaling (eg, DCI or RRC message).
- SL MODE 2 may mean a resource allocation method or communication method in which a terminal independently selects an SL transmission resource from a base station or a network or within a preset resource pool.
- a UE performing SL communication based on SL MODE 1 may be referred to as a MODE 1 UE or a MODE 1 TX UE
- a UE performing SL communication based on SL MODE 2 may be referred to as a MODE 2 UE or a MODE 2 TX It can be called UE.
- a dynamic grant may be mutually replaced/substituted with a configured grant (CG) and/or a semi-persistent scheduling grant (SPS grant).
- DG can be interchanged/substituted with a combination of CG and SPS grants.
- the CG may include at least one of configured grant type 1 (CG type 1) and/or configured grant type 2 (CG type 2).
- the grant may be provided by RRC signaling and may be stored as a configured grant.
- a grant may be provided by a PDCCH and may be stored or deleted as a configured grant based on L1 signaling indicating activation or deactivation of the grant.
- the base station may allocate periodic resources to the TX UE through an RRC message.
- the base station may allocate periodic resources to the TX UE through an RRC message, and the base station may dynamically activate or deactivate the periodic resources through DCI. there is.
- a channel may be replaced/substituted with a signal.
- transmission and reception of a channel may include transmission and reception of a signal.
- transmission and reception of a signal may include transmission and reception of a channel.
- a cast may be mutually replaced/substituted with at least one of unicast, group cast, and/or broadcast.
- the cast type may be mutually replaced/substituted with at least one of unicast, group cast, and/or broadcast.
- the cast or cast type may include unicast, group cast, and/or broadcast.
- resources may be interchanged/substituted with slots or symbols.
- a resource may include slots and/or symbols.
- priorities include Logical Channel Prioritization (LCP), latency, reliability, minimum required communication range, Prose Per-Packet Priority (PPPP), and Sidelink Radio (SLRB). Bearer), QoS profile, QoS parameter, and/or requirement may be mutually replaced/substituted with at least one.
- LCP Logical Channel Prioritization
- PPPP Prose Per-Packet Priority
- SLRB Sidelink Radio
- a (physical) channel used when an RX UE transmits at least one of the following information to a TX UE may be referred to as PSFCH.
- SL discontinuous reception (DRX) operation may be supported for the UE.
- TX UE and RX UE may obtain SL DRX configuration.
- the SL DRX configuration may be set for TX UE and RX UE or may be set in advance.
- the TX UE may transmit the SL DRX configuration to the RX UE.
- the SL DRX configuration includes information related to the SL DRX timer, information related to the SL DRX slot offset, information related to the SL DRX start offset, and/or information related to the SL DRX cycle At least one may be included.
- the SL DRX timer may include at least one of a SL DRX on-duration timer, a SL DRX inactivity timer, a SL DRX retransmission timer, and/or a SL DRX HARQ RTT timer.
- the SL DRX on-duration timer may be the duration at the beginning of an SL DRX cycle.
- the SL DRX inactivity timer is the duration after the first slot of SCI reception in which an SCI indicates a new SL transmission to the MAC entity. SL transmission for the MAC entity).
- the SL DRX retransmission timer may be the maximum duration until an SL retransmission is received.
- the SL DRX HARQ RTT timer may be the minimum duration before an SL HARQ retransmission is expected by the MAC entity.
- the SL DRX retransmission timer and the SL DRX HARQ RTT timer may be set for each sidelink process.
- the SL DRX inactivity timer, SL DRX retransmission timer, and SL DRX HARQ RTT timer may not be applied to broadcast transmission.
- the UE may start the SL DRX retransmission timer after the SL DRX HARQ RTT timer expires.
- the SL DRX slot offset may be a delay before the start of the SL DRX on-duration timer.
- the SL DRX start offset may be the slot where the SL DRX cycle starts.
- the running time of at least one of the SL DRX on-duration timer, the SL DRX inactivity timer, and/or the SL DRX retransmission timer may be the active time.
- the active time is not limited to a time during which at least one of the SL DRX on-duration timer, the SL DRX inactivity timer, and/or the SL DRX retransmission timer is running.
- the RX UE can operate in active time, and the RX UE can monitor the PSCCH from the TX UE. there is.
- UE #X may simultaneously perform other SL communication with UE #Z.
- UE #X determines/configures the SL DRX configuration of UE #Y
- UE #X considers the generation pattern of packets to be transmitted to UE #Y as well as the generation pattern of packets to be transmitted to UE #Z. By doing so, you can minimize your own battery consumption. For example, after UE #X turns on its own RF, it can perform packet transmission to UE #Y and UE #Z as continuously as possible, and through this, UE #X can minimize its own battery consumption.
- packet transmission from UE #X to UE #Y is not performed based on the SL DRX setting associated with the unicast link, but , packet-related TX profile (and / or QoS profile), etc. If performed based on the SL DRX configuration associated with information, it may not be possible to achieve battery consumption minimization from the perspective of UE #X (described above).
- a method for a UE to perform SL communication based on SL DRX configuration and an apparatus supporting the same are proposed.
- a TX profile may be referred to as a profile or a SL DRX profile.
- a TX profile, profile or SL DRX profile may indicate SL DRX ON (ie SL DRX compatible) or SL DRX OFF (ie SL DRX incompatible).
- whether data transmission / reception assuming SL DRX application should be performed (eg, SL DRX ON may be named), or whether data transmission / reception without SL DRX application should be performed (eg, SL DRX ON) SL DRX OFF) can be set (in advance).
- whether data transmission / reception assuming SL DRX application should be performed or data transmission / reception without SL DRX application should be performed may be set for the TX UE and / or RX UE or set in advance.
- whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each service type/type.
- whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each QoS requirement/profile. For example, whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each radio bearer. . For example, whether data transmission/reception assuming SL DRX application should be performed or data transmission/reception not assuming SL DRX application should be performed may be set (in advance) for each logical channel. .
- whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each release. For example, whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each QoS flow ID. For example, whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each (L2) source ID. For example, whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each (L2) destination ID. .
- SL DRX profile For example, whether data transmission/reception should be performed assuming SL DRX application or data transmission/reception without SL DRX application may be set (in advance) for each SL session/link.
- configuration information may be referred to as an SL DRX profile, a TX profile, or a profile.
- an upper layer (eg, V2X layer) of the TX UE sends a packet to a lower layer (eg, PHY layer, MAC layer, RLC layer, RRC layer, PDCP layer, SDAP layer)
- a lower layer eg, PHY layer, MAC layer, RLC layer, RRC layer, PDCP layer, SDAP layer
- the SL DRX profile may also be delivered.
- the TX UE selects a candidate resource within the SL DRX active time interval to which the RX UE interested in the related service type / type is applied, and transmits the packet. there is.
- the TX UE assumes that the RX UE interested in the related service type/type is always awake and selects a candidate resource related to packet transmission.
- an upper layer of the RX UE may deliver an SL DRX profile for a service type/type of interest to the lower layer.
- the SL DRX profile is designated as SL DRX ON, the RX UE wakes up within the SL DRX active time and can perform a related packet reception operation.
- the SL DRX profile is designated as SL DRX OFF, the RX UE can always wake up and perform a related packet reception operation.
- the proposed rule of the present disclosure may be limitedly applied to a (preset) cast type (eg, unicast).
- the proposed rules of the present disclosure may be limitedly applied to (preset) service types/types.
- the proposed rules of the present disclosure may be limitedly applied to priorities (set in advance).
- the proposed rules of the present disclosure may be limitedly applied to (preset) QoS requirements/profiles.
- the proposed rule of the present disclosure may be limitedly applied to a (preset) radio bearer.
- the proposed rules of the present disclosure may be limitedly applied to (preset) logical channels.
- the proposed rule of the present disclosure may be limitedly applied to a (preset) release.
- the proposed rule of the present disclosure may be limitedly applied to a (preset) QoS flow ID.
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure extends to Service Type/Type. (and/or replacement).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure extends to Cast Type (and / or alternative).
- the wording "(L2) Source ID and/or (L2) Destination ID (pair/combination)" (and/or "SL Session/Link” wording) as used in this disclosure expands (and / or alternative).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure is a QoS requirement/profile. may be extended (and/or replaced).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) used in this disclosure is a radio bearer can be extended (and/or replaced) by
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure extends to logical channels (and / or alternative).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure expands to release. (and/or replacement).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) used in this disclosure is extended to QoS Flow ID ( and/or replaced).
- the wording “(L2) Source ID and/or (L2) Destination ID (pair/combination)” (and/or “SL Session/Link” wording) as used in this disclosure extends to SL Session/Link (and/or replacement).
- SL DRX configuration (hereinafter referred to as ONGO_SLDRX) may be present/configured.
- the TX UE may be configured to select a transmission resource based on the SL DRX active time interval of ONGO_SLDRX, and the RX UE may be configured to perform a reception operation based on the SL DRX active time interval of ONGO_SLDRX.
- SL DRX ON/OFF depends on (not SL DRX profile) (L2) Source ID and/or (L2) Destination ID (pair/combination) presence or absence of specific ONGO_SLDRX It can be finally determined according to, and ONGO_SLDRX can be interpreted as overriding the SL DRX profile.
- the SL DRX profile of a packet transmitted/received through an SL session/link related to (L2) source ID and/or (L2) destination ID (pair/combination) is SL DRX ON If designated as , transmission resource selection and reception operations may be performed based on the SL DRX active time interval of ONGO_SLDRX.
- the UE when the above-described rule is applied, when a packet related to an SL DRX profile designated as SL DRX OFF is transmitted/received in the SL DRX active time period of ONGO_SLDRX, the UE may be configured not to start/operate the SL DRX timer. there is. On the other hand, for example, when an SL DRX profile related packet designated as SL DRX ON is transmitted/received in the SL DRX active time period of ONGO_SLDRX, the UE may be set to start/operate the SL DRX timer.
- predefined signaling eg , PSCCH, SCI, etc.
- the UE may be configured to start/run the SL DRX timer.
- the TX UE when the above-described rule is applied, when the TX UE transmits a packet related to the SL DRX profile designated as SL DRX OFF, the TX UE selects ONGO_SLDRX from among candidate resources within the currently running active time interval (hereinafter referred to as RUN_ACTTIME) Resources (eg, all resources for initial transmission and necessary number of retransmissions) may be selected, and the TX UE may transmit packets based on the selected resources.
- RUN_ACTTIME ONGO_SLDRX from among candidate resources within the currently running active time interval
- the TX UE when the TX UE transmits a packet related to the SL DRX profile designated as SL DRX ON, the TX UE selects a candidate resource within RUN_ACTTIME of ONGO_SLDRX and a candidate within active time to be extended due to a resource to be selected within RUN_ACTTIME.
- a resource eg, all resources for initial transmission and necessary number of retransmissions
- the TX UE may perform packet transmission based on the selected resource.
- services having the same characteristics as whether SL DRX is applied/required for each SL session/link related to (L2) source ID and/or (L2) destination ID (pair/combination) The kind/type can be (limitedly) configured.
- a QoS profile having the same characteristics as whether or not SL DRX is applied/required can be (limitedly) configured.
- a radio bearer having the same characteristics as whether or not SL DRX is applied/required (limitedly ) can be configured.
- a logical channel having the same characteristics as whether SL DRX is applied/required can be (limitedly) configured.
- a release of the same characteristics whether or not SL DRX is applied/required is (limitedly) configured It can be.
- a QoS flow ID having the same characteristics as whether SL DRX is applied/required is (limitedly) configured.
- (L2) source ID and/or (L2) destination ID (pair/combination) related SL session/link should be created.
- (L2) source ID and/or (L2) destination ID (pair/combination) related SL session/link should be created.
- the service type/type to be added does not require SL DRX application
- the service type/type includes a service type/type requiring SL DRX application and a service type/type not requiring SL DRX application.
- the QoS profile to be added does not require SL DRX application
- the QoS profile includes/supports both a QoS profile requiring SL DRX application and a QoS profile that does not require SL DRX application (current operating on-going) SL sessions/links
- the QoS profile may not be added to (currently operating) SL sessions/links that contain/support only QoS profiles requiring SL DRX application.
- the radio bearer when a radio bearer to be added does not require SL DRX application, the radio bearer includes/supports both a radio bearer requiring SL DRX application and a radio bearer that does not require SL DRX application (current operation current) SL session/link, whereas the radio bearer may not be added to a (currently operating) SL session/link that includes/supports only radio bearers requiring SL DRX application.
- the logical channel when a logical channel to be added does not require SL DRX application, the logical channel includes/supports both a logical channel requiring SL DRX application and a logical channel that does not require SL DRX application (current operation on-going) SL sessions/links, whereas the logical channels may not be added to (currently operating) SL sessions/links that contain/support only logical channels requiring SL DRX application.
- the release includes/supports both a release that requires SL DRX application and a release that does not require SL DRX application (currently in operation) SL session /link, whereas the release may not be added to (currently running) SL sessions/links that contain/support only releases that require SL DRX application.
- the QoS flow ID to be added does not require SL DRX application
- the QoS flow ID includes/supports both a QoS flow ID requiring SL DRX application and a QoS flow ID that does not require SL DRX application can be added to a (currently operating) SL session/link
- the QoS flow ID cannot be added to a (currently operating) SL session/link that includes/supports only QoS flow IDs requiring SL DRX application.
- the service type/type to be added does not require SL DRX application
- the service type/type includes a service type/type requiring SL DRX application and a service type/type not requiring SL DRX application.
- the QoS profile to be added does not require SL DRX application
- the QoS profile includes/supports both a QoS profile requiring SL DRX application and a QoS profile that does not require SL DRX application (current operating
- the QoS profile may be added to a (currently operating) SL session/link that includes/supports only QoS profiles requiring SL DRX application.
- the radio bearer when a radio bearer to be added does not require SL DRX application, the radio bearer includes/supports both a radio bearer requiring SL DRX application and a radio bearer that does not require SL DRX application (current operation current) SL session/link, and the radio bearer may be added to a (currently operating) SL session/link that includes/supports only radio bearers requiring SL DRX application.
- the logical channel when a logical channel to be added does not require SL DRX application, the logical channel includes/supports both a logical channel requiring SL DRX application and a logical channel that does not require SL DRX application (current operation (currently running) SL session/link, and the logical channel may be added to a (currently running) SL session/link that includes/supports only logical channels requiring SL DRX application.
- the release includes/supports both a release that requires SL DRX application and a release that does not require SL DRX application (currently in operation) SL session / link, and the release can be added to a (currently running) SL session / link that includes / supports only releases that require SL DRX application.
- the QoS flow ID to be added does not require SL DRX application
- the QoS flow ID includes/supports both a QoS flow ID requiring SL DRX application and a QoS flow ID that does not require SL DRX application can be added to a (currently operating) SL session/link
- the QoS flow ID can be added to a (currently operating) SL session/link that includes/supports only QoS flow IDs requiring SL DRX application.
- the service type/type to be added requires SL DRX application
- the service type/type includes a service type/type requiring SL DRX application and a service type/type that does not require SL DRX application cannot be added to the (currently operating) SL session/link containing/supporting
- the service type/type includes/supports only the service type/type requiring SL DRX application (currently operating) SL session/link Can be added to links.
- the QoS profile to be added requires SL DRX application
- the QoS profile includes/supports both a QoS profile requiring SL DRX application and a QoS profile that does not require SL DRX application (currently in operation ) cannot be added to an SL session/link
- the QoS profile can be added to a (currently running) SL session/link that includes/supports only QoS profiles requiring SL DRX application.
- the radio bearer includes/supports both a radio bearer requiring SL DRX application and a radio bearer not requiring SL DRX application (currently in operation). ) cannot be added to an SL session/link, whereas the radio bearer can be added to a (currently operating) SL session/link that includes/supports only radio bearers requiring SL DRX application.
- the logical channel includes/supports a logical channel requiring SL DRX application and a logical channel that does not require SL DRX application (currently in operation). ) cannot be added to an SL session/link, whereas the logical channel can be added to a (currently operating) SL session/link that contains/supports only logical channels requiring SL DRX application.
- the release includes/supports both a release requiring SL DRX application and a release that does not require SL DRX application (currently running) SL session/ It cannot be added to a link, whereas the release can be added to a (currently running) SL session/link that contains/supports only releases requiring SL DRX application.
- the QoS flow ID to be added requires SL DRX application
- the QoS flow ID includes/supports both a QoS flow ID requiring SL DRX application and a QoS flow ID that does not require SL DRX application It cannot be added to the (currently running) SL session/link, whereas the QoS flow ID can be added to the (currently running) SL session/link that contains/supports only QoS flow IDs requiring SL DRX application. .
- the service type/type to be added requires SL DRX application
- the service type/type includes a service type/type requiring SL DRX application and a service type/type that does not require SL DRX application It can be added to the included/supported (currently operating) SL session/link, and the service type/type includes/supports only the service type/type requiring SL DRX application to the (currently operating) SL session/link.
- the QoS profile to be added requires SL DRX application
- the QoS profile includes/supports both a QoS profile requiring SL DRX application and a QoS profile that does not require SL DRX application (currently in operation ) can be added to the SL session/link, and the QoS profile can be added to a (currently operating) SL session/link that includes/supports only QoS profiles requiring SL DRX application.
- the radio bearer includes/supports both a radio bearer requiring SL DRX application and a radio bearer not requiring SL DRX application (currently in operation). ) SL session/link, and the radio bearer may be added to a (currently operating) SL session/link that includes/supports only radio bearers requiring SL DRX application.
- the logical channel includes/supports a logical channel requiring SL DRX application and a logical channel that does not require SL DRX application (currently in operation). ) can be added to an SL session/link, and the logical channel can be added to a (currently operating) SL session/link that includes/supports only logical channels requiring SL DRX application.
- the release includes/supports both a release requiring SL DRX application and a release that does not require SL DRX application (currently running) SL session/ It can be added to a link, and the release can be added to a (currently running) SL session/link that includes/supports only releases that require SL DRX application.
- the QoS flow ID to be added requires SL DRX application
- the QoS flow ID includes/supports both a QoS flow ID requiring SL DRX application and a QoS flow ID that does not require SL DRX application It can be added to a (currently operating) SL session/link, and the QoS flow ID can be added to a (currently operating) SL session/link that includes/supports only QoS flow IDs requiring SL DRX application.
- type of service and/or (LCH or SERVICE) priority and/or QOS requirements (eg LATENCY, RELIABILITY, MINIMUM COMMUNICATION RANGE) and/or PQI parameters)
- HARQ FEEDBACK ENABLED and/or or DISABLED
- LCH/MAC PDU Transmission
- CBR measure of resource pool and/or SL CAST TYPE eg UNICAST, GROUPCAST, BROADCAST
- SL GROUPCAST HARQ FEEDBACK OPTION eg NACK ONLY FEEDBACK, ACK /NACK FEEDBACK, TX-RX DISTANCE BASED NACK ONLY FEEDBACK
- SL MODE 1 CG TYPE eg SL CG TYPE 1/2
- SL MODE TYPE eg MODE 1/2
- RRC CONNECTED state IDLE state, INACTIVE state
- SL HARQ PROCESS ID
- ID SL HARQ PROCESS
- PSFCH TX and PSFCH RX and / or multiple PSFCH TXs exceeding the UE CAPABILITY
- overlap and / or PSFCH TX (and / or PSFCH RX) are omitted case
- the RX UE actually (successfully) received the PSCCH (and/or PSSCH) (re)transmission from the TX UE.
- configuration is a form in which the base station informs the terminal through a predefined (physical layer or upper layer) channel / signal (eg, SIB, RRC, MAC CE) ( And/or a form provided through PRE-CONFIGURATION and/or a form in which a terminal informs other terminals through a predefined (physical layer or upper layer) channel/signal (eg, SL MAC CE, PC5 RRC), etc.
- PSFCH wording is “(NR or LTE) PSSCH (and/or (NR or LTE) PSCCH) (and/or (NR or LTE) SL SSB (and/or UL channel/signal)” It can also be interpreted as extended.
- the schemes proposed in the present disclosure may be combined with each other and extended (in a new type of scheme).
- UE #X eg, TX UE
- UE #Y eg, RX UE
- packet transmission from UE #X to UE #Y is related to Regardless of the TX profile (and/or QoS profile), it can be performed based on the SL DRX configuration associated with the unicast link. For example, before the unicast link is established between UE #X and UE #Y, for packet transmission to which the QoS profile is not mapped (based on the TX profile received from the upper layer indicating ON or compatible) to) default SL DRX settings may be applied.
- SL DRX configuration associated with the unicast link may be applied for packet transmission of the same characteristics.
- UE #X simultaneously performs unicast-based SL communication with UE #Y as well as SL communication with other UE(s)
- UE #X (after establishing a unicast link with UE #Y, By performing packet transmission to UE #Y based on the SL DRX configuration associated with the unicast link), its own battery consumption can be minimized.
- FIG. 10 illustrates a method for performing wireless communication by a first device 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 may acquire a default sidelink (SL) discontinuous reception (DRX) setting.
- the first device may obtain a profile indicating whether SL DRX is compatible.
- the first device may perform a first SL transmission based on the default SL DRX configuration based on the fact that the profile indicates that the SL DRX is compatible.
- the first device may establish a PC5 radio resource control (RRC) connection with the second device.
- the first device may acquire SL DRX settings.
- the first device may transmit information related to the SL DRX configuration to the second device.
- the first device may perform second SL transmission to the second device based on the SL DRX configuration regardless of the profile.
- the first device may select a first SL resource within an active time related to the default SL DRX configuration based on the profile indicating that the SL DRX is compatible. For example, the first SL transmission may be performed based on the first SL resource.
- the first device determines that the second device interested in the first SL transmission does not perform an SL DRX operation based on the profile indicating that the SL DRX is incompatible. can decide Additionally, for example, the first device may select the first SL resource without considering the default SL DRX configuration. For example, the first SL transmission may be performed based on the first SL resource.
- the first device establishes the PC5 RRC connection between the first device and the second device, within an active time related to the SL DRX configuration.
- SL resources can be selected.
- the second SL transmission may be performed based on the second SL resource.
- the profile may not be considered in the second SL transmission by the first device.
- the obtaining of the profile indicating whether the SL DRX is compatible may include: Prior to establishing the PC5 RRC connection with the second device, an upper layer of the first device is a lower layer of the first device. It may include delivering the profile to the layer. For example, after establishing the PC5 RRC connection with the second device, the upper layer of the first device may not be allowed to transfer the profile to the lower layer of the first device.
- the SL DRX configuration may be configured for a pair of a source identifier (ID) and a destination ID.
- ID source identifier
- destination ID destination ID
- the first device may receive assistance information from the second device.
- the SL DRX configuration may be configured for a pair of source ID and destination ID based on the auxiliary information.
- the PC5 RRC connection can support only transmission requiring SL DRX operation.
- the second SL transmission may include transmission for which the SL DRX operation is required and may not include transmission for which the SL DRX operation is not required.
- the first device may not be allowed to perform third SL transmission for which the SL DRX operation is not required through the PC5 RRC connection based on the SL DRX configuration.
- the PC5 RRC connection can support transmission requiring the SL DRX operation and transmission not requiring the SL DRX operation.
- the second SL transmission may include transmission for which the SL DRX operation is required or transmission for which the SL DRX operation is not required.
- the 1st SL transmission may include transmission of information for establishing the PC5 RRC connection
- the default SL DRX configuration is information related to the 1st SL DRX cycle and for the 1st SL DRX active time It may include information related to a timer
- the SL DRX configuration may include information related to a second SL DRX cycle and information related to a timer for a second SL DRX activation time.
- the processor 102 of the first device 100 may obtain a default sidelink (SL) discontinuous reception (DRX) setting. And, the processor 102 of the first device 100 may obtain a profile indicating whether SL DRX is compatible. Further, the processor 102 of the first device 100 controls the transceiver 106 to perform a first SL transmission based on the default SL DRX setting based on the profile indicating that the SL DRX is compatible. can And, the processor 102 of the first device 100 may establish a PC5 radio resource control (RRC) connection with the second device. And, the processor 102 of the first device 100 may obtain the SL DRX configuration.
- RRC radio resource control
- the processor 102 of the first device 100 may control the transceiver 106 to transmit information related to the SL DRX configuration to the second device. And, the processor 102 of the first device 100 controls the transceiver 106 to perform a second SL transmission to the second device based on the SL DRX setting regardless of the profile.
- 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; based on the profile indicating that the SL DRX is compatible, controlling the one or more transceivers to perform a first SL transmission based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the second device; obtain SL DRX settings; controlling the one or more transceivers to transmit information related to the SL DRX configuration to the second device; and control the one or more transceivers to perform a second SL transmission to the second device based on the SL DRX configuration regardless of the profile.
- RRC radio resource control
- a processing device configured to control a first device performing wireless communication
- a processing device may include 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; based on the profile indicating that the SL DRX is compatible, performing a first SL transmission based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the second device; obtain SL DRX settings; transmits information related to the SL DRX configuration to the second device; and regardless of the profile, a second SL transmission may be performed to the second device based on the SL DRX configuration.
- RRC radio resource control
- a non-transitory computer readable storage medium recording instructions may be provided.
- the instructions when executed, cause the first device to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; Based on the profile indicating that the SL DRX is compatible, perform a first SL transmission based on the default SL DRX configuration; establish a PC5 radio resource control (RRC) connection with the second device; obtain SL DRX settings; transmit information related to the SL DRX configuration to the second device; and regardless of the profile (regardless of), the second device may perform a second SL transmission based on the SL DRX configuration.
- SL sidelink
- DRX discontinuous reception
- FIG. 11 illustrates a method for a second device to perform wireless communication 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 may acquire a default sidelink (SL) discontinuous reception (DRX) setting.
- the second device may obtain a profile indicating whether SL DRX is compatible.
- the second device may perform first SL reception based on the default SL DRX configuration based on the fact that the profile indicates that the SL DRX is compatible.
- the second device may establish a PC5 radio resource control (RRC) connection with the first device.
- the second device may acquire SL DRX settings.
- the second device may receive information related to the SL DRX configuration from the first device.
- the second device may perform second SL reception from the first device based on the SL DRX configuration regardless of the profile.
- the processor 202 of the second device 200 may obtain a default sidelink (SL) discontinuous reception (DRX) setting. And, the processor 202 of the second device 200 may obtain a profile indicating whether SL DRX is compatible. Further, the processor 202 of the second device 200 controls the transceiver 206 to perform a first SL reception based on the default SL DRX setting based on the profile indicating that the SL DRX is compatible. can And, the processor 202 of the second device 200 may establish a PC5 radio resource control (RRC) connection with the first device. And, the processor 202 of the second device 200 may acquire the SL DRX configuration.
- RRC radio resource control
- the processor 202 of the second device 200 may control the transceiver 206 to receive information related to the SL DRX configuration from the first device. And, the processor 202 of the second device 200 controls the transceiver 206 to perform a second SL reception from the first device based on the SL DRX setting regardless of the profile.
- a second device performing wireless communication may be provided.
- the second 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; based on the profile indicating that the SL DRX is compatible, controlling the one or more transceivers to perform a first SL reception based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the first device; obtain SL DRX settings; controlling the one or more transceivers to receive information related to the SL DRX configuration from the first device; and controls the one or more transceivers to perform a second SL reception from the first device based on the SL DRX configuration regardless of the profile.
- RRC radio resource control
- a processing device configured to control a second device performing wireless communication
- a processing device may include 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 obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; if the profile indicates that the SL DRX is compatible, perform first SL reception based on the default SL DRX configuration; Establishing a PC5 radio resource control (RRC) connection with the first device; obtain SL DRX settings; receiving information related to the SL DRX configuration from the first device; And regardless of the profile (regardless of), a second SL reception may be performed from the first device based on the SL DRX configuration.
- RRC radio resource control
- a non-transitory computer readable storage medium recording instructions may be provided.
- the instructions when executed, cause the second device to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile indicating whether the SL DRX is compatible; if the profile indicates that the SL DRX is compatible, perform a first SL reception based on the default SL DRX configuration; establish a PC5 radio resource control (RRC) connection with the first device; obtain SL DRX settings; receive information related to the SL DRX configuration from the first device; and irrespective of the profile, based on the SL DRX configuration, a second SL reception may be performed from the first device.
- SL sidelink
- DRX discontinuous reception
- FIG. 12 illustrates a communication system 1, according to an embodiment 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 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 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.
- a wireless device may be implemented in various forms according to use-case/service (see FIG. 12).
- 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
- 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
Description
SCS (15*2u) | Nslot symb | Nframe,u slot | Nsubframe,u slot |
15KHz (u=0) | 14 | 10 | 1 |
30KHz (u=1) | 14 | 20 | 2 |
60KHz (u=2) | 14 | 40 | 4 |
120KHz (u=3) | 14 | 80 | 8 |
240KHz (u=4) | 14 | 160 | 16 |
SCS (15*2u) | Nslot symb | Nframe,u slot | Nsubframe,u slot |
60KHz (u=2) | 12 | 40 | 4 |
Frequency Range designation | Corresponding frequency range | Subcarrier Spacing (SCS) |
FR1 | 450MHz - 6000MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
Frequency Range designation | Corresponding frequency range | Subcarrier Spacing (SCS) |
FR1 | 410MHz - 7125MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
Claims (20)
- 제 1 장치가 무선 통신을 수행하는 방법에 있어서,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하는 단계;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하는 단계;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 전송을 수행하는 단계;제 2 장치와 PC5 RRC(radio resource control) 연결을 확립하는 단계;SL DRX 설정을 획득하는 단계;상기 SL DRX 설정과 관련된 정보를 상기 제 2 장치에게 전송하는 단계; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 2 장치에게 제 2 SL 전송을 수행하는 단계;를 포함하는, 방법.
- 제 1 항에 있어서,상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정과 관련된 활성 시간(active time) 내에서 제 1 SL 자원을 선택하는 단계;를 더 포함하되,상기 제 1 SL 전송은 상기 제 1 SL 자원을 기반으로 수행되는, 방법.
- 제 1 항에 있어서,상기 프로파일이 SL DRX가 비호환됨(incompatible)을 나타내는 것을 기반으로, 상기 제 1 SL 전송에 관심 있는 상기 제 2 장치가 SL DRX 동작을 수행하지 않는다고 결정하는 단계; 및상기 디폴트 SL DRX 설정을 고려하지 않고, 제 1 SL 자원을 선택하는 단계;를 더 포함하되,상기 제 1 SL 전송은 상기 제 1 SL 자원을 기반으로 수행되는, 방법.
- 제 1 항에 있어서,상기 PC5 RRC 연결이 상기 제 1 장치 및 상기 제 2 장치 사이에서 확립되는 것을 기반으로, 상기 SL DRX 설정과 관련된 활성 시간(active time) 내에서 제 2 SL 자원을 선택하는 단계;를 더 포함하되,상기 제 2 SL 전송은 상기 제 2 SL 자원을 기반으로 수행되는, 방법.
- 제 4 항에 있어서,상기 PC5 RRC 연결이 상기 제 1 장치 및 상기 제 2 장치 사이에서 확립되는 것을 기반으로, 상기 프로파일은 상기 제 1 장치에 의한 상기 제 2 SL 전송에서 고려되지 않는, 방법.
- 제 1 항에 있어서,상기 SL DRX가 호환되는지 여부를 나타내는 상기 프로파일을 획득하는 단계는: 상기 제 2 장치와 상기 PC5 RRC 연결을 확립하기 이전에, 상기 제 1 장치의 상위 계층이 상기 제 1 장치의 하위 계층에게 상기 프로파일을 전달하는 단계를 포함하는, 방법.
- 제 1 항에 있어서,상기 제 2 장치와 상기 PC5 RRC 연결을 확립한 이후에, 상기 제 1 장치의 상위 계층은 상기 제 1 장치의 하위 계층에게 상기 프로파일을 전달하도록 허용되지 않는, 방법.
- 제 1 항에 있어서,상기 SL DRX 설정은 소스 ID(identifier) 및 데스티네이션 ID의 페어에 대하여 설정되는, 방법.
- 제 1 항에 있어서,상기 제 2 장치로부터 보조 정보(assistance information)를 수신하는 단계;를 더 포함하되,상기 SL DRX 설정은 상기 보조 정보를 기반으로 소스 ID 및 데스티네이션 ID의 페어에 대하여 설정되는, 방법.
- 제 1 항에 있어서,상기 PC5 RRC 연결은 SL DRX 동작이 요구되는 전송만을 지원하는, 방법.
- 제 10 항에 있어서,상기 제 2 SL 전송은 상기 SL DRX 동작이 요구되는 전송을 포함하고 상기 SL DRX 동작이 요구되지 않는 전송을 포함하지 않고, 및상기 제 1 장치는 상기 SL DRX 설정을 기반으로 상기 SL DRX 동작이 요구되지 않는 제 3 SL 전송을 상기 PC5 RRC 연결을 통해서 수행하도록 허용되지 않는, 방법.
- 제 1 항에 있어서,상기 PC5 RRC 연결은 SL DRX 동작이 요구되는 전송 및 상기 SL DRX 동작이 요구되지 않는 전송을 지원하고, 및상기 제 2 SL 전송은 상기 SL DRX 동작이 요구되는 전송 또는 상기 SL DRX 동작이 요구되지 않는 전송을 포함하는, 방법.
- 제 1 항에 있어서,상기 제 1 SL 전송은 상기 PC5 RRC 연결을 확립하기 위한 정보의 전송을 포함하고,상기 디폴트 SL DRX 설정은 제 1 SL DRX 사이클과 관련된 정보 및 제 1 SL DRX 활성 시간을 위한 타이머와 관련된 정보를 포함하고, 및상기 SL DRX 설정은 제 2 SL DRX 사이클과 관련된 정보 및 제 2 SL DRX 활성 시간을 위한 타이머와 관련된 정보를 포함하는, 방법.
- 무선 통신을 수행하도록 설정된 제 1 장치에 있어서,명령어들을 저장하는 하나 이상의 메모리;하나 이상의 송수신기; 및상기 하나 이상의 메모리와 상기 하나 이상의 송수신기를 연결하는 하나 이상의 프로세서를 포함하되, 상기 하나 이상의 프로세서는 상기 명령어들을 실행하여,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 전송을 수행하도록 상기 하나 이상의 송수신기를 제어하고;제 2 장치와 PC5 RRC(radio resource control) 연결을 확립하고;SL DRX 설정을 획득하고;상기 SL DRX 설정과 관련된 정보를 상기 제 2 장치에게 전송하도록 상기 하나 이상의 송수신기를 제어하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 2 장치에게 제 2 SL 전송을 수행하도록 상기 하나 이상의 송수신기를 제어하는, 제 1 장치.
- 무선 통신을 수행하는 제 1 장치를 제어하도록 설정된 프로세싱 장치에 있어서,하나 이상의 프로세서; 및상기 하나 이상의 프로세서에 의해 실행 가능하게 연결되고, 및 명령어들을 저장하는 하나 이상의 메모리를 포함하되, 상기 하나 이상의 프로세서는 상기 명령어들을 실행하여,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 전송을 수행하고;제 2 장치와 PC5 RRC(radio resource control) 연결을 확립하고;SL DRX 설정을 획득하고;상기 SL DRX 설정과 관련된 정보를 상기 제 2 장치에게 전송하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 2 장치에게 제 2 SL 전송을 수행하는, 프로세싱 장치.
- 명령어들을 기록하고 있는 비일시적 컴퓨터 판독가능 저장 매체로서,상기 명령어들은, 실행될 때, 제 1 장치로 하여금:디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하게 하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하게 하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 전송을 수행하게 하고;제 2 장치와 PC5 RRC(radio resource control) 연결을 확립하게 하고;SL DRX 설정을 획득하게 하고;상기 SL DRX 설정과 관련된 정보를 상기 제 2 장치에게 전송하게 하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 2 장치에게 제 2 SL 전송을 수행하게 하는, 비일시적 컴퓨터 판독가능 저장 매체.
- 제 2 장치가 무선 통신을 수행하는 방법에 있어서,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하는 단계;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하는 단계;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 수신을 수행하는 단계;제 1 장치와 PC5 RRC(radio resource control) 연결을 확립하는 단계;SL DRX 설정을 획득하는 단계;상기 SL DRX 설정과 관련된 정보를 상기 제 1 장치로부터 수신하는 단계; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 1 장치로부터 제 2 SL 수신을 수행하는 단계;를 포함하는, 방법.
- 무선 통신을 수행하도록 설정된 제 2 장치에 있어서,명령어들을 저장하는 하나 이상의 메모리;하나 이상의 송수신기; 및상기 하나 이상의 메모리와 상기 하나 이상의 송수신기를 연결하는 하나 이상의 프로세서를 포함하되, 상기 하나 이상의 프로세서는 상기 명령어들을 실행하여,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 수신을 수행하도록 상기 하나 이상의 송수신기를 제어하고;제 1 장치와 PC5 RRC(radio resource control) 연결을 확립하고;SL DRX 설정을 획득하고;상기 SL DRX 설정과 관련된 정보를 상기 제 1 장치로부터 수신하도록 상기 하나 이상의 송수신기를 제어하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 1 장치로부터 제 2 SL 수신을 수행하도록 상기 하나 이상의 송수신기를 제어하는, 제 2 장치.
- 무선 통신을 수행하는 제 2 장치를 제어하도록 설정된 프로세싱 장치에 있어서,하나 이상의 프로세서; 및상기 하나 이상의 프로세서에 의해 실행 가능하게 연결되고, 및 명령어들을 저장하는 하나 이상의 메모리를 포함하되, 상기 하나 이상의 프로세서는 상기 명령어들을 실행하여,디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 수신을 수행하고;제 1 장치와 PC5 RRC(radio resource control) 연결을 확립하고;SL DRX 설정을 획득하고;상기 SL DRX 설정과 관련된 정보를 상기 제 1 장치로부터 수신하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 1 장치로부터 제 2 SL 수신을 수행하는, 프로세싱 장치.
- 명령어들을 기록하고 있는 비일시적 컴퓨터 판독가능 저장 매체로서,상기 명령어들은, 실행될 때, 제 2 장치로 하여금:디폴트(default) SL(sidelink) DRX(discontinuous reception) 설정을 획득하게 하고;SL DRX가 호환(compatible)되는지 여부를 나타내는 프로파일을 획득하게 하고;상기 프로파일이 상기 SL DRX가 호환됨을 나타내는 것을 기반으로, 상기 디폴트 SL DRX 설정을 기반으로 제 1 SL 수신을 수행하게 하고;제 1 장치와 PC5 RRC(radio resource control) 연결을 확립하게 하고;SL DRX 설정을 획득하게 하고;상기 SL DRX 설정과 관련된 정보를 상기 제 1 장치로부터 수신하게 하고; 및상기 프로파일과 무관하게(regardless of), 상기 SL DRX 설정을 기반으로 상기 제 1 장치로부터 제 2 SL 수신을 수행하게 하는, 비일시적 컴퓨터 판독가능 저장 매체.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280054234.7A CN117796139A (zh) | 2021-08-05 | 2022-08-05 | 用于在nr v2x中执行sl drx操作的方法和设备 |
KR1020247003126A KR20240038714A (ko) | 2021-08-05 | 2022-08-05 | Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 |
EP22853504.3A EP4369852A1 (en) | 2021-08-05 | 2022-08-05 | Method and device for performing sl drx operation in nr v2x |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202163229995P | 2021-08-05 | 2021-08-05 | |
US63/229,995 | 2021-08-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023014129A1 true WO2023014129A1 (ko) | 2023-02-09 |
Family
ID=85155925
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/011596 WO2023014129A1 (ko) | 2021-08-05 | 2022-08-05 | Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230053192A1 (ko) |
EP (1) | EP4369852A1 (ko) |
KR (1) | KR20240038714A (ko) |
CN (1) | CN117796139A (ko) |
WO (1) | WO2023014129A1 (ko) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11792841B2 (en) * | 2022-01-13 | 2023-10-17 | Qualcomm Incorporated | Sidelink intra-UE prioritization |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210195522A1 (en) * | 2019-12-24 | 2021-06-24 | Qualcomm Incorporated | Coordinated sidelink power savings configurations |
-
2022
- 2022-08-05 WO PCT/KR2022/011596 patent/WO2023014129A1/ko active Application Filing
- 2022-08-05 EP EP22853504.3A patent/EP4369852A1/en active Pending
- 2022-08-05 US US17/882,196 patent/US20230053192A1/en active Pending
- 2022-08-05 KR KR1020247003126A patent/KR20240038714A/ko unknown
- 2022-08-05 CN CN202280054234.7A patent/CN117796139A/zh active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210195522A1 (en) * | 2019-12-24 | 2021-06-24 | Qualcomm Incorporated | Coordinated sidelink power savings configurations |
Non-Patent Citations (4)
Title |
---|
APPLE: "Discussion on remaining issues on SL DRX Configuration", 3GPP DRAFT; R2-2100862, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200125 - 20200205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973959 * |
NOKIA, NOKIA SHANGHAI BELL: "Further Issues on Sidelink Traffic Pattern for SL DRX Configuration", 3GPP DRAFT; R2-2105958, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20210519 - 20210527, 10 May 2021 (2021-05-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052004003 * |
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 * |
ZTE CORPORATION, SANECHIPS: "Discussion on principle for Sidelink DRX", 3GPP DRAFT; R2-2100496, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973663 * |
Also Published As
Publication number | Publication date |
---|---|
CN117796139A (zh) | 2024-03-29 |
EP4369852A1 (en) | 2024-05-15 |
US20230053192A1 (en) | 2023-02-16 |
KR20240038714A (ko) | 2024-03-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022019540A1 (ko) | Nr v2x에서 보조 정보를 기반으로 sl 통신을 수행하는 방법 및 장치 | |
WO2021066599A1 (ko) | Nr v2x에서 harq 피드백을 기지국에게 보고하는 방법 및 장치 | |
WO2021230672A1 (ko) | Nr v2x에서 dtx 기반의 rlf 동작을 수행하는 방법 및 장치 | |
WO2021201432A1 (ko) | Nr v2x에서 psfch의 전송 전력을 결정하는 방법 및 장치 | |
WO2022080914A1 (ko) | Nr v2x에서 보조 정보를 송수신하는 방법 및 장치 | |
WO2021091289A1 (ko) | Nr v2x에서 사이드링크 자원을 할당하는 방법 및 장치 | |
WO2022154640A1 (ko) | Nr v2x에서 자원 할당을 향상시키는 방법 및 장치 | |
WO2022139510A1 (ko) | Nr v2x에서 sl drx mac ce를 전송하는 방법 및 장치 | |
WO2022030975A1 (ko) | Nr v2x에서 기지국에 의해 할당되는 자원을 기반으로 sl 통신을 수행하는 방법 및 장치 | |
WO2021075768A1 (ko) | Nr v2x에서 harq 피드백을 보고하는 방법 및 장치 | |
WO2022139541A1 (ko) | Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 | |
WO2022146105A1 (ko) | Nr v2x에서 전송 단말의 모드 1 동작을 고려한 sl drx 동작 방법 | |
WO2022086184A1 (ko) | Nr v2x에서 sl csi를 보고하는 방법 및 장치 | |
WO2022080843A1 (ko) | Nr v2x에서 자원을 결정하는 방법 및 장치 | |
WO2022086131A1 (ko) | Nr v2x에서 sl drx 활성 시간을 정렬하는 방법 및 장치 | |
WO2022086280A1 (ko) | Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 | |
WO2022014860A1 (ko) | 전력 절약 모드를 기반으로 통신을 수행하는 방법 및 장치 | |
WO2021206532A1 (ko) | Nr v2x에서 harq 프로세스를 운영하는 방법 및 장치 | |
WO2021215757A1 (ko) | Nr v2x에서 pucch 프로세싱 시간에 기반하여 사이드링크 전송을 수행하는 방법 및 장치 | |
WO2021040435A1 (ko) | Nr v2x에서 단말이 자원 예약을 수행하는 방법 및 장치 | |
WO2023014129A1 (ko) | Nr v2x에서 sl drx 동작을 수행하는 방법 및 장치 | |
WO2023075548A1 (ko) | Nr v2x에서 sl harq rtt 타이머를 설정하는 방법 및 장치 | |
WO2022235116A1 (ko) | Nr v2x에서 수신 장치의 sl drx harq rtt 타이머 동작을 기반으로 전송 자원을 선택하는 방법 및 장치 | |
WO2022240135A1 (ko) | Nr v2x에서 sl drx 설정을 결정하는 방법 및 장치 | |
WO2022154526A1 (ko) | Nr v2x에서 우선화 절차를 수행하는 방법 및 장치 |
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: 22853504 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20247003126 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2024506740 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280054234.7 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022853504 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022853504 Country of ref document: EP Effective date: 20240205 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |