Method for transmitting information related to termination of pdrch transmission in ambient IoT communication, and device supporting same
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-02-04
- Publication Date
- 2026-08-13
Smart Images

Figure KR2026002081_13082026_PF_FP_ABST
Abstract
Description
Method for transmitting information related to the termination of PDRCH transmission in ambient IoT communication and device supporting the same
[0001] The present disclosure relates to a method and apparatus for wireless communication. More specifically, the present disclosure may relate to a method for transmitting information related to the termination of PDRCH transmission in ambient IoT communication and an apparatus supporting the same.
[0002] 5G NR is a successor technology to LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.
[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy requirements such as those shown in Table 1 below. For example, Table 1 may represent an example of the requirements for a 6G system.
[0004] Maximum data rate per device 1 Tbps E2E latency 1 ms Maximum spectral efficiency 100 bps / Hz Mobility support up to 1000 km / hr Satellite integration Fully AI Fully autonomous driving Fully XR Fully haptic communication Fully
[0005] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step in which a device receives information for scheduling a PDRCH (physical D2R (device to reader) channel) from a reader; a step in which the device transmits the PDRCH to the reader based on the information for scheduling the PDRCH; and a step in which the device transmits a postamble of the PDRCH to the reader based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0006] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the device to: receive information for scheduling a physical D2R (device to reader) channel from a reader based on execution by the at least one processor; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble of the PDRCH to the reader based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0007] According to one embodiment of the present disclosure, a processing device (configured to control the device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the device to: receive information for scheduling a physical D2R (device to reader) channel from a reader based on execution by the at least one processor; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble to the reader after transmission of the PDRCH based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0008] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the device may: receive information for scheduling a physical D2R (device to reader) channel (PDRCH) from a reader; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble to the reader after transmission of the PDRCH based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0009] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step in which a reader transmits information for scheduling a physical D2R (device to reader) channel (PDRCH) to a device; a step in which the reader receives the PDRCH from the device based on the information for scheduling the PDRCH; and a step in which the reader receives a postamble of the PDRCH from the device based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0010] According to one embodiment of the present disclosure, a reader may be provided. For example, the reader may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the reader may: transmit information for scheduling a physical D2R (device to reader) channel to a device; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0011] According to one embodiment of the present disclosure, a processing device (configured to control a reader) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the reader to: transmit information for scheduling a physical D2R (device to reader) channel to a device based on execution by the at least one processor; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0012] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the reader may: transmit information for scheduling a physical D2R (device to reader) channel (PDRCH) to a device; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0013] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure.
[0014] FIG. 2 shows a radio protocol architecture according to one embodiment of the present disclosure.
[0015] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure.
[0016] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure.
[0017] FIG. 5 shows an example of a BWP according to one embodiment of the present disclosure.
[0018] FIG. 6 shows a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.
[0019] FIG. 7 shows an example of basic topologies according to one embodiment of the present disclosure.
[0020] FIG. 8 shows an example of a physical layer frame structure for R2D (reader-to-device) transmission according to one embodiment of the present disclosure.
[0021] FIG. 9 shows an example of a physical layer frame structure for D2R (device-to-reader) transmission according to one embodiment of the present disclosure.
[0022] FIG. 10 shows an example of reader-to-device (R2D) transmission based on orthogonal frequency division multiplexing (OFDM) symbols according to one embodiment of the present disclosure.
[0023] FIG. 11 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure.
[0024] FIG. 12 shows an example of six sensing scenarios for a sensing service according to one embodiment of the present disclosure.
[0025] FIG. 13 shows a functional framework for AI / ML (artificial intelligence and machine learning) according to one embodiment of the present disclosure.
[0026] FIG. 14 shows an example of a physical layer frame structure for D2R (device-to-reader) transmission according to one embodiment of the present disclosure.
[0027] FIG. 15 shows an example of a physical layer frame structure for D2R (device-to-reader) transmission according to one embodiment of the present disclosure.
[0028] FIG. 16 illustrates a procedure performed by an apparatus according to one embodiment of the present disclosure.
[0029] FIG. 17 illustrates a procedure performed by a reader according to one embodiment of the present disclosure.
[0030] FIG. 18 shows a communication system (1) according to one embodiment of the present disclosure.
[0031] FIG. 19 shows a wireless device according to one embodiment of the present disclosure.
[0032] FIG. 20 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.
[0033] FIG. 21 shows a wireless device according to one embodiment of the present disclosure.
[0034] FIG. 22 shows a portable device according to one embodiment of the present disclosure.
[0035] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."
[0036] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."
[0037] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."
[0038] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."
[0039] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (e.g., PDCCH)," "PDCCH" may be proposed as an example of "control information."
[0040] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.
[0041] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.
[0042] In the present disclosure, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.
[0043] In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from a base station or network (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.). In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from another device (e.g., MAC, RRC, SCI (sidelink control information), control information signaled between devices, etc.). In the present disclosure, "configured or defined" may be interpreted as being pre-configured to a device.
[0044] In the present disclosure, user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.
[0045] The technology proposed in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.
[0046] The technology proposed in this disclosure can be implemented as 6G wireless technology and can be applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.
[0047] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.
[0048] Referring to FIG. 1, in step S101, the first device and the second device can perform synchronization. For example, the first device may be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device may be a base station, a network, a RAN node, an NTN node / cell, a TRP, a terminal and / or at least one of the devices proposed in the present disclosure. For example, the first device may perform an initial cell search operation. For example, the first device may detect at least one synchronization signal transmitted according to a rule predefined by the second device. Here, for example, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal, etc.) classified according to structure or use. Through this, the first device can identify the boundaries of the frame, subframe, time unit, slot, and / or symbol of the second device, and the first device can obtain information about the second device (e.g., cell identifier).
[0049] In step S103, the first device may obtain system information transmitted by the second device. For example, the system information may include information related to the attributes, characteristics, and / or capabilities of the second device that are necessary to connect to the second device and use the service. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the first device may transmit a signal requesting the system information prior to receiving the system information. For example, the request and provision of the system information may be performed after a random access procedure described later.
[0050] In step S105, the first device and the second device may perform a random access procedure. For example, the first device may transmit and / or receive at least one message for the random access procedure (e.g., random access preamble, random access response message, etc.) based on information related to the random access channel of the second device obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the first device may transmit a preamble (e.g., Msg1) through the random access channel, and the first device may receive a random access response message (e.g., Msg2). The first device may transmit a message (e.g., Msg3) containing information related to the first device (e.g., identification information) to the second device using scheduling information included in the random access response message, and the first device may receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be transmitted and received as a single message (e.g., MsgA), and / or Msg2 and Msg4 can be transmitted and received as a single message (e.g., MsgB).
[0051] In step S107, the first device and the second device may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer controlling the connection (e.g., a radio resource control (RRC) layer), a layer handling mapping between a logical channel and a transmission channel (e.g., a media access control (MAC) layer), and a layer handling a physical channel (e.g., a physical (PHY) layer). For example, the first device and the second device may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and / or signaling to indicate allocated resources. For example, the control information may be signaled / transmitted through a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.
[0052] In step S109, the first device and the second device may transmit and / or receive data. For example, the first device and the second device may process data based on signaling of control information and transmit and / or receive it. For example, when transmitting data, the first device or the second device may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the first device or the second device may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.
[0053] For example, the layers of the radio interface protocol between the first device and the second device can be classified into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, the physical layer belonging to layer 1 can provide an information transfer service using a physical channel, and the radio resource control (RRC) layer located at layer 3 can perform the role of controlling radio resources between the first device and the second device. For example, to this end, the RRC layer can exchange RRC messages between the first device and the second device.
[0054] FIG. 2 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, FIG. 2(a) may represent a radio protocol stack in the user plane for uplink communication or downlink communication, and FIG. 2(b) may represent a radio protocol stack in the control plane for uplink communication or downlink communication. For example, FIG. 2(c) may represent a radio protocol stack in the user plane for device-to-device communication, and FIG. 2(d) may represent a radio protocol stack in the control plane for device-to-device communication.
[0055] For example, the physical layer can provide information transmission services to upper layers using a physical channel. For example, the physical layer can be connected to the upper layer, the MAC (medium access control) layer, through a transport channel. For example, data can be transmitted between the MAC layer and the physical layer through a transport channel. For example, transport channels can be classified according to how and with what characteristics data is transmitted through a wireless interface. For example, data can be transmitted through a physical channel between different physical layers, for example, between the physical layers of a first device and a second device. For example, the physical channel can be modulated using the OFDM (orthogonal frequency division multiplexing) method, and time and frequency can be utilized as wireless resources.
[0056] For example, the MAC layer can provide services to the upper layer, the RLC (radio link control) layer, through logical channels. For example, the MAC layer can provide mapping functions from multiple logical channels to multiple transmission channels. For example, the MAC layer can provide logical channel multiplexing functions through mapping from multiple logical channels to a single transmission channel. For example, the MAC sublayer can provide data transmission services over logical channels.
[0057] For example, the RLC layer can perform concatenation, segmentation, and reassembly of RLC service data units (SDUs). For example, to guarantee various quality of service (QoS) required by a radio bearer (RB), the RLC layer can provide three modes of operation: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). For example, AM RLC can provide error correction through automatic repeat requests (ARQ).
[0058] For example, the RRC (radio resource control) layer may be defined only in the control plane. For example, the RRC layer may be responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. For example, RB may refer to a logical path provided by the first layer (e.g., physical layer) and the second layer (e.g., MAC layer, RLC layer, PDCP (packet data convergence protocol) layer, SDAP (service data adaptation protocol) layer, etc.) for data transfer between a first device and a second device.
[0059] For example, the functions of the PDCP layer in the user plane may include the delivery of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include the delivery of control plane data and encryption / integrity protection.
[0060] For example, the establishment of an RB can mean the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting each specific parameter and method of operation. For example, an RB can be divided into two types: an SRB (signaling radio bearer) and a DRB (data radio bearer). For example, an SRB can be used as a channel to transmit RRC messages in the control plane, and a DRB can be used as a channel to transmit user data in the user plane.
[0061] For example, if 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, and if not, it may be in the RRC_IDLE state. For example, in the case of NR, an additional RRC_INACTIVE state is defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network while releasing the connection with the base station.
[0062] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) that transmits system information and / or a shared channel (SCH) that transmits user traffic or control messages. For example, traffic or control messages for a downlink multicast or broadcast service may be transmitted via a downlink SCH or via a separate multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) that transmits initial control messages and / or a shared channel (SCH) that transmits user traffic or control messages. For example, a logical channel located above the transmission channel and mapped to the transmission channel may include at least one of a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and / or a multicast traffic channel (MTCH).
[0063] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.
[0064] Referring to FIG. 3, radio frames may be used, for example, in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may contain five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by subcarrier spacing (SCS). For example, each slot may contain 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).
[0065] For example, when normal CP is used, each slot may contain 14 symbols. For example, when extended CP is used, each slot may contain 12 symbols. Here, for example, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).
[0066] Table 2 below shows the number of symbols per slot (N) according to the SCS setting (u) when Normal CP or Extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) exemplifies.
[0067] CP Type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slotNormal CP 15kHz (u=0) 1410 130kHz (u=1) 1420 260kHz (u=2) 1440 4120kHz (u=3) 1480 8240kHz (u=4) 14160 16 Extended CP 60kHz (u=2) 1240 4
[0068] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among multiple cells merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI (transmit time interval)) composed of the same number of symbols may be configured differently among the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTI, etc. may be referred to as time units.
[0069] For example, multiple numerologies or SCSs may be supported to support various services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. For example, if the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.
[0070] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure. The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.
[0071] Referring to FIG. 4, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain and may correspond to a single numerology (e.g., SCS, CP length, etc.). For example, a carrier may include up to N BWPs (where N is a positive integer). For example, data communication may be performed through an active BWP. For example, each element may be referred to as a resource element (RE) in a resource grid and may be mapped to a single complex symbol.
[0072] For example, a BWP can be a continuous set of PRBs in a given numerology. For example, a PRB can be selected from a continuous subset of common resource blocks (CRBs) for a given numerology on a given carrier.
[0073] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the terminal may not monitor downlink radio link quality on DL BWPs other than the active DL BWP on the PCell (primary cell). For example, the terminal may not receive PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), or CSI-RS (channel state information-reference signal) (except for RRM (radio resource management)) outside of the active DL BWP. For example, the terminal may not trigger CSI (channel state information) reporting for an inactive DL BWP. For example, the terminal may not transmit PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel) outside of the active UL (uplink) BWP. For example, for the downlink, the initial BWP can be given as a consecutive set of resource blocks (RBs) for the remaining minimum system information (RMSI) CORESET (control resource set) (set by the physical broadcast channel (PBCH)). For example, for the uplink, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by the upper layer. For example, the initial value of the default BWP can be the initial DL BWP.For energy saving, if the terminal fails to detect DCI (downlink control information) for a certain period, the terminal can switch the active BWP of the terminal to the default BWP.
[0074] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. In the embodiment of FIG. 5, it is assumed that there are three BWPs.
[0075] Referring to FIG. 5, for example, a common resource block (CRB) may be a numbered carrier resource block from one end of the carrier band to the other, and a PRB may be a numbered resource block within each BWP. For example, point A may indicate a common reference point for the resource block grid.
[0076] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP It can be set by ). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network in that carrier) are aligned. For example, offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth may be the number of PRBs in a given numerology.
[0077] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0078] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optical transmission (FSO) backhaul networks, large-scale MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.
[0079] Below, Ambient IoT (A-IoT) will be explained.
[0080] A-IoT can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT can refer to a new class of Internet of Things devices that operate by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy.
[0081] For example, active signal generation and / or backscattering may be one of the communication technologies considered to achieve low-power operation of A-IoT devices. For example, backscattering is a widely used technique in radio frequency identification (RFID) that can enable a device to communicate with a network by reflecting incident waves after modulating them with information to be transmitted. For example, the device may be powered by an incident RF signal or stored energy.
[0082] For example, A-IoT devices can be classified into various device types, such as passive, semi-passive, and active, depending on the energy storage and transmission signal generation methods. For example, a passive device does not have an energy storage device (e.g., a capacitor) and can communicate based on backscatter communication technology. For example, a semi-passive device has an energy storage device and can communicate using backscatter communication technology with the assistance of the energy storage device. For example, an active device has an energy storage device and can communicate by actively generating signals using active RF components and stored energy. For example, in the present disclosure, the following three types of IoT devices may be considered. For example, device A may be a device without energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). For example, device B may be a device with energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). In this case, for example, the use of the stored energy may include amplification of the reflected signal. For example, device C may be a device with energy storage and independent signal generation (e.g., a device with an active RF component for transmission).
[0083] For example, the types of A-IoT devices can be classified into two as follows. For example, a Type 1 device has a maximum power consumption of approximately 1 uW, is capable of energy storage, has no amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device has a maximum power consumption of approximately several hundred uW, is capable of energy storage, has an amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node) or by using a signal generated internally.
[0084] For example, in addition to the classification methods described above, the type / class of an A-IoT device may be distinguished based on parameters associated with device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of parameters. Here, for example, the BPF capability may be distinguished by the 3-dB bandwidth of the supported BPF, sharpness, etc., and the UL transmission methods may be distinguished by, for example, backscattered UL transmission, UL transmission by internal signal generation, etc.
[0085] In addition, the type / class of an A-IoT device may be subdivided based on parameters associated with the above device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of such parameters. For example, the above-described Type 2 device may be classified into Type 2a when it performs transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node), and Type 2b when it performs transmission using a signal generated internally. In this case, Types 2a and 2b may be identical in that they have a maximum power consumption of approximately several hundred uW, are capable of energy storage, and have amplification capabilities.
[0086] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection between a base station and an A-IoT device, a connection between a base station, an intermediate node, and an A-IoT device, support for connection by an auxiliary node, and / or a connection between a terminal and an A-IoT device. The basic topologies proposed in this disclosure are merely examples, and the proposals of this disclosure may be extended and applied to other topologies.
[0087] FIG. 7 illustrates examples of basic topologies according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiment may be omitted.
[0088] FIG. 7(a) illustrates a topology (e.g., Topology 1) in which a base station and an A-IoT device are directly connected according to one embodiment of the present disclosure. Referring to FIG. 7(a), the A-IoT device can communicate directly and bidirectionally with the base station. For example, communication between the base station and the A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 7(a), the base station transmitting to the A-IoT device and the base station receiving from the A-IoT device may be different. For example, in Topology 1, the base station and the A-IoT device in a micro-cell environment may communicate directly with each other. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology.
[0089] FIG. 7(b) illustrates a topology (e.g., Topology 2) in which a base station and an A-IoT device are connected through an intermediate node (IN) according to one embodiment of the present disclosure. Referring to FIG. 7(b), the A-IoT device can communicate bidirectionally with the intermediate node between the device and the base station. Here, for example, the intermediate node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc. For example, the intermediate node may transmit A-IoT data and / or signals between the base station and the A-IoT device. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or data channel (e.g., shared channel). In the embodiment of FIG. 7(b), the intermediate node transmitting to the A-IoT device and the intermediate node receiving from the A-IoT device may be different. For example, in the above topology 2, an intermediate node may exist between the base station in the macro-cell environment and the A-IoT device. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology. For example, the intermediate node may be limited to a terminal, and the intermediate node may be located indoors. For example, in the above topology 2, IN may act as a leader.
[0090] FIG. 7(c) and / or FIG. 7(d) illustrates a topology (e.g., Topology 3) supported by an assisting node (AN) according to one embodiment of the present disclosure. Referring to FIG. 7(c), the assisting node may be supported for downlink reception. For example, an A-IoT device may transmit data / signals to a base station, and the A-IoT device may receive data / signals from the assisting node. Referring to FIG. 7(d), the assisting node may be supported for uplink transmission. For example, the A-IoT device may receive data / signals from a base station, and the A-IoT device may transmit data / signals to the assisting node. Here, for example, the assisting node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc.
[0091] FIG. 7(e) illustrates a topology (e.g., Topology 4) in which a terminal and an A-IoT device are directly connected according to one embodiment of the present disclosure. Referring to FIG. 7(e), the A-IoT device can communicate bidirectionally with the terminal. For example, communication between the terminal and the A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel).
[0092] For example, CW waveforms can be supported in various types. For instance, the type of CW waveform can be a single-tone CW waveform or a somewhat complex multi-tone CW waveform. For instance, single-tone CW may be advantageous over multi-tone CW in terms of the multiplexing capacity of tags or readers and in terms of interference, as it uses fewer resources. On the other hand, multi-tone CW has advantages, such as the ability to deliver more energy when transmitting CW over DL and to secure greater coverage on a single device.
[0093] Considering the advantages of these different CW waveform types, multiple CW waveform types may be supported in an A-IoT system, and the base station / IN / AN / UE may configure the CW waveform type. For example, one or more CW waveform types supported in the A-IoT communication system may be pre-configured / defined, and the base station / IN / AN / UE may select one of the one or more supported CW waveform types and transmit it to an A-IoT device. For example, the base station / IN / AN / UE may configure / instruct / display the selected CW waveform type to the A-IoT device in the form of a command / message transmitted as a preamble / frame-sync or payload.
[0094] FIG. 8 illustrates an example of a physical layer frame structure for R2D (reader-to-device) transmission according to one embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0095] Referring to FIG. 8, an R2D transmission may include at least one of a start indicator part (SIP), a clock acquisition part (CAP), a physical reader-to-device channel (PRDCH), and / or an R2D postamble. For example, the SIP and / or CAP may be included in the R-TAS (R2D timing acquisition signal). For example, the SIP may be the start indicator part of the R-TAS. For example, the CAP may be the clock acquisition part of the R-TAS. For example, the SIP may be a signal for the reader to explicitly notify the device of the start of transmission. For example, the CAP may be a signal for providing clock information necessary to interpret the subsequent channel. For example, the PRDCH may be a physical layer channel through which data and / or control information that the reader intends to convey to the device is transmitted. For example, the PRDCH may include a transmission block received from an upper layer (e.g., MAC). For example, the R2D postamble can be located at the very end of the frame and can indicate that the PRDCH transmission is complete.
[0096] FIG. 9 illustrates an example of a physical layer frame structure for device-to-reader (D2R) transmission according to one embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0097] Referring to FIG. 9, the D2R transmission may include at least one of a preamble, a midamble, a postamble, and / or a physical device-to-reader channel (PDRCH). In the embodiment of FIG. 9, the midamble located after the PDRCH may be referred to as the postamble.
[0098] FIG. 10 illustrates an example of reader-to-device (R2D) transmission based on orthogonal frequency division multiplexing (OFDM) symbols according to one embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0099] Referring to FIG. 10(a), M chips can be mapped within a single OFDM symbol. For example, consecutive chips with indices from 0 to M-1 can be mapped within a single OFDM symbol. For example, M can be a positive integer.
[0100] Referring to FIG. 10(b), for example, the number of chips within an OFDM symbol for SIP may be 4. For example, in the segment after SIP (e.g., CAP, PRDCH, postamble, and / or padding), the number of chips per OFDM symbol may be selected by the reader. For example, the reader may select one value from the set {2, 6, 12, 24}. In the embodiment of FIG. 10(b), M is assumed to be 12. For example, to align the R2D transmission by symbol, padding may be included in the last part of the R2D transmission.
[0101] In the present disclosure, for example, the following terms may be defined to describe AI / ML.
[0102] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for ML model training, data analysis, and inference.
[0103] - ML Model: A data-driven algorithm that applies machine learning techniques to generate a set of outputs containing predictive information based on a set of inputs.
[0104] - ML Training: An online or offline process of training an ML model by learning features and patterns that best represent the data and acquire an ML model trained for inference.
[0105] - ML Inference: A process of making predictions or deriving decisions based on collected data and ML models using a trained ML model.
[0106] FIG. 11 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted.
[0107] Referring to FIG. 11, NTN communication can be performed based on a satellite network, HIBS (high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS)), and an aeronautical communication-capable terminal (e.g., AAM). For example, to improve coverage, devices such as a satellite network, HIBS, and an aeronautical communication-capable terminal (e.g., AAM) can act as relays. For example, an AAM can communicate with a base station, a satellite network, etc., and / or an AAM can communicate directly with a terminal, another AAM, etc.
[0108] For example, a terminal can obtain information about the characteristics of the environment and / or objects within the environment by using radio frequency sensing to determine the instantaneous linear velocity, angle, distance (range), etc. of an object. Since radio frequency sensing capabilities do not require connecting to an object via a device within the network, they can provide services for object location determination without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Radio sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, radio sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, e.g., sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.
[0109] Conventionally, NR positioning up to Release 17 only supported network-based Uu positioning, which performed location search based on a connection between the target UE and the network (gNB / LMF). Meanwhile, starting with NR Release 18, sidelink positioning (SL positioning) using sidelink communication can be supported. Sidelink positioning is a new method that allows positioning operations to be performed by exchanging positioning reference signals through direct connections with anchor UEs surrounding the target UE, rather than with base stations. Positioning operations at the physical layer can be performed by determining the location through the transmission and measurement of the SL PRS (sidelink positioning reference signal) between the target UE and the anchor UE.
[0110] Uu positioning may use the LPP protocol. An LPP session can be a point-to-point communication protocol between a target UE and an LMF. Through the LPP protocol, the target UE can receive information necessary for positioning from the LMF. The LMF can establish the target UE and the base station (gNB) respectively, exchange positioning-related messages, and perform positioning operations through the LPP protocol and the NRPPa protocol. Meanwhile, in Release 18's sidelink positioning, positioning operations can be performed by exchanging sidelink positioning protocol messages with the target UE, server UE (or LMF), and anchor UE. In sidelink positioning, the sidelink positioning protocol (SLPP) can be used for establishing and exchanging messages between UEs.
[0111] Positioning methods (e.g., sidelink positioning) have the disadvantage that the target must possess a communication terminal and that signaling messages for location measurement must be exchanged between the transmitter and the target. This leads to increased overhead for signal processing between the target and the transmitter, and presents a fundamental limitation in that positioning itself is impossible if the target does not possess a separate communication terminal.
[0112] In contrast, the Integrated Sensing and Communication (ISAC) method can accurately detect the presence and movement of a target regardless of whether the target is carrying a communication terminal, and furthermore, can reliably acquire detailed sensing information such as the target's distance, speed, and angle. The ISAC method can estimate the characteristics of a target simply by analyzing the information reflected from the target after the signal radiated by the transmitter, without requiring a separate response signal or message from the target. Accordingly, ISAC has the advantage of significantly reducing the amount of signaling compared to positioning methods, thereby drastically lowering overhead, and simultaneously supporting more efficient and flexible sensing and communication operations.
[0113] Examples of various application fields where ISAC can be applied are illustrated. Specifically, ISAC can support predictive maintenance and employee localization and authorization in the fields of smart manufacturing and industrial IoT, and can provide weather prediction, pollution monitoring, rain monitoring, and insect monitoring in the field of environmental monitoring.
[0114] In addition, in the field of Sensing as a Service, it can be utilized for drone monitoring and management, mobile crowd sensing, channel knowledge map construction, and cooperative localization and imaging.
[0115] Furthermore, in the field of remote sensing, it can support satellite imaging and broadcasting and drone swarm SAR imaging, and in the field of smart home, it can be utilized for human proximity detection, spatial-aware control, sensing-aided wireless charging, fall detection, vital signal monitoring, etc.
[0116] In addition, in the field of human-computer interaction (HCI), it enables gesture recognition, keystroke recognition, and arm / head activity recognition, and in the field of vehicle-to-everything communication (V2X), it enables the provision of various services such as high precision location, vehicle platooning, extended sensor, simultaneous localization and mapping, and secure hand-free access.
[0117] Recently, Integrated Sensing and Communication (ISAC) technology, which integrates target sensing and user communication functions in 6th generation (6G) mobile communication systems, is attracting attention as a key standardization target. Based on advantages such as efficient frequency usage, reuse of existing communication infrastructure, and cost savings resulting from integrated sensing and communication sensors, ISAC technology is emerging as an essential technology in various industries, including autonomous driving, smart factories, unmanned aerial vehicles, and healthcare.
[0118] For example, a support scenario for sensing services in an ISAC could be as follows. Here, for example, the network could be a gNB.
[0119] FIG. 12 illustrates an example of six sensing scenarios for a sensing service according to an embodiment of the present disclosure. Specifically, FIG. 12(a) illustrates an example of gNB monostatic, FIG. 12(b) illustrates an example of gNB bistatic, and FIG. 12(c) illustrates an example of gNB-UE bistatic. Additionally, FIG. 12(d) illustrates an example of UE-gNB bistatic, FIG. 12(e) illustrates an example of UE monostatic, and FIG. 12(f) illustrates an example of UE bistatic. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.
[0120] Referring to Fig. 12, for example, six sensing scenarios for a sensing service in an ISAC may be as follows.
[0121] For example, six principal sensing modes:
[0122] - gNB monostatic (the same gNB performs both the transmitter (Tx) and receiver (Rx)
[0123] - gNB bi-static (one gNB is the transmitter (Tx) and the other gNB is the receiver (Rx)
[0124] - gNB-to-UE bi-static (gNB is the transmitter (Tx) and UE is the receiver (Rx)
[0125] - UE-to-gNB bi-static (UE is the transmitter (Tx) and gNB is the receiver (Rx)
[0126] - UE Monostatic (The same UE performs both the transmitter (Tx) and receiver (Rx)
[0127] - UE bi-static (One UE is the transmitter (Tx) and the other UE is the receiver (Rx)
[0128] FIG. 13 illustrates a functional framework for artificial intelligence and machine learning (AI / ML) according to one embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0129] Referring to FIG. 13, for example, data collection may be a function that provides input data to model training and model inference functions. AI / ML algorithm-specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) may not be performed in the data collection function. Examples of input data may include measurements from terminals or other network entities, feedback from actors, and outputs from AI / ML models.
[0130] For example, training data may be data required as input for the training function of an AI / ML model.
[0131] For example, inference data may be data required as input for the inference function of an AI / ML model.
[0132] For example, model training may be a function that performs ML model training, validation, and testing to generate model performance metrics as part of the model testing procedure. If necessary, the model training function may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data provided by the data collection function.
[0133] For example, model deployment / update can be used to initially deploy trained, validated, and tested AI / ML models to the model inference function, or to provide updated models to the model inference function.
[0134] For example, model inference can be a function that provides AI / ML model inference outputs (e.g., predictions or decisions). Where applicable, the model inference function can provide model performance feedback to the model training function. If necessary, the model inference function can also handle data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on the inference data provided by the data collection function.
[0135] For example, the output may be the inference output of an AI / ML model generated by the model inference function. Note that the details of the inference output may vary depending on the use case.
[0136] For example, model performance feedback can be used to monitor the performance of AI / ML models.
[0137] For example, an actor can be a function that receives output from a model inference function and triggers or performs the corresponding action. An actor can trigger actions on other entities or on itself.
[0138] For example, feedback may be information that is necessary to derive training or inference data or performance feedback.
[0139] For example, in datasets used in AI / ML, the definitions of training, validation, and test data can be as follows. For instance, training data may be a dataset for training a model. For instance, validation data may be a dataset for validating a model that has already been trained. For instance, validation data is typically used to prevent overfitting of the training dataset. For instance, validation data may be a dataset for selecting the best model among several models trained during the learning process. Therefore, this can be viewed as a type of training. For instance, test data may be a dataset for final evaluation, and test data may be unrelated to training. For instance, regarding the above datasets, if the training set is divided, the training and validation data within the entire training set can typically be split in a ratio of approximately 8:2 or 7:3; if tests are included, the ratio can be split as 6:2:2 (training:validation:test).
[0140] Table 3 shows examples of use cases for A-IoT.
[0141] Smart labeling / identification sensors in warehouses, supply chains, airport cargo transport, manufacturing, logistics, retail, etc. Environmental sensing in smart farms, smart cities, smart homes, smart grids, etc. Location positioning: Indoor / outdoor location tracking and distance measurement for tracking assets, products, and personal items, etc. Command actuators, device activation / deactivation, electronic labeling, etc.
[0142] The following shows matters related to IoT communication discussed in the 3GPP RAN.
[0143] This study targets new 3GPP IoT technologies for very-low-end IoT applications based on devices with ultra-low complexity and ultra-low power consumption, and aims for technologies that can be deployed in 3GPP systems. This study must provide clear differentiation by targeting use cases and scenarios that cannot be achieved based on existing 3GPP LPWA IoT technologies (e.g., NB-IoT, including cases where peak transmit power reduction is applied).
[0144] - In terms of energy storage, this study considers the following device characteristics:
[0145] A pure batteryless device with absolutely no energy storage capacity, relying entirely on the availability of an external energy source.
[0146] - - A device with limited energy storage capacity that does not require manual replacement or manual recharging
[0147] Device classification based on relevant characteristics (e.g., energy source, energy storage capacity, passive / active transmission, etc.) may be discussed during the study in relation to applicable use cases. The peak power consumption of the device must be limited by the practical form factor for the intended use case, and the device's energy source must be taken into account.
[0148] Identify suitable deployment scenarios and their characteristics, including at least the following. This targets use cases / services agreed upon in SA1’s “Study on Ambient Power-Enabled Internet of Things.”
[0149] - - - Indoor / Outdoor Environment
[0150] - - - Base station characteristics (e.g., macro / micro / pico cell-based deployment)
[0151] - - - Connection topology (e.g., which node among base station, UE, relay, repeater, etc. can communicate with the target device)
[0152] - - - TDD / FDD and frequency bands in licensed or unlicensed bands
[0153] - - - Coexistence with UEs and infrastructure in frequency bands for existing 3GPP technologies
[0154] - - - Assumption of device originated and / or device terminated traffic
[0155] - NOTE: One or more deployment scenarios can be identified for a single use case, and a single deployment scenario can be applied commonly to two or more use cases.
[0156] - NOTE: If more than one deployment scenario is identified for a single use case, the trade-offs between them must also be studied.
[0157] - NOTE: This study does not prioritize deployment aspects requiring coordination with SA (e.g., public or private network, presence or absence of CN connection, etc.).
[0158] - NOTE: For groups of use cases with similar requirements, a representative use case can be studied.
[0159] Based on the identified deployment scenarios and their characteristics, RAN design targets are derived for relevant use cases that include at least the following:
[0160] - - - Power consumption
[0161] - - - Complexity
[0162] - - - Coverage
[0163] - - - Data transfer rate
[0164] - - - Location accuracy
[0165] - NOTE: SA1 requirements for relevant use cases must be considered.
[0166] - NOTE: This study aims to provide better coverage for relevant use cases compared to existing non-3GPP technologies.
[0167] - NOTE: Other RAN design goals related to connection density, mobility, security, latency, reliability, etc., may be discussed if necessary for relevant use cases.
[0168] - NOTE: The detailed definition of RAN design objectives should be discussed during the study.
[0169] Based on deployment scenarios suitable for relevant use cases, compare and evaluate the feasibility of meeting design goals and identify assumptions regarding the features to be supported.
[0170] - NOTE: This does not require a detailed analysis at the WG level.
[0171] - NOTE: This study targets IoT in a much lower segment than existing 3GPP IoT technologies (e.g., NB-IoT, eMTC, RedCap, etc.). This study does not aim to replace existing 3GPP LPWA technologies.
[0172] Meanwhile, a study item titled "Study on solutions for Ambient IoT (Internet of Things) in NR" was approved in 3GPP NR release 19. Specifically, the study item is scheduled to proceed in 3GPP NR release 19 based on the contents shown in the table below.
[0173] This study targets an additional RAN WG-level evaluation of ambient IoT, which is a new 3GPP IoT technology deployable in 3GPP systems that supports very-low-end IoT applications by relying on ultra-low complexity devices and ultra-low power consumption. This study must provide clear differentiations targeting use cases and scenarios that cannot be achieved based on existing 3GPP LPWA IoT technologies (e.g., NB-IoT, including cases where peak transmit power reduction is applied).
[0174] - General range
[0175] The definitions provided in TR 38.848 shall apply to this SI, and the following shall be the exclusive general scope.
[0176] - - A. The overall objective is to research a harmonized wireless interface design with minimized differences (where necessary) for ambient IoT, enabling the following devices.
[0177] - - - i. Approx. 1 μW peak power consumption, possesses energy storage capability, initial sampling frequency offset (SFO) up to 10X ppm, no DL and UL amplification within the device. The device's UL transmission is backscattering for externally provided carrier waveforms.
[0178] - - - ii. Peak power dissipation of less than a few hundred μW (≤ a few hundred μW), energy storage capacity, initial SFO up to 10X ppm, presence of DL and / or UL amplification within the device. The UL transmission of the device may be generated internally within the device or backscattering of a carrier waveform provided externally.
[0179] - - - X is determined by WGs.
[0180] - - - Coverage design goal: Maximum indoor distance of 10-50 m according to TR 38.848, e.g., “range that WGs can sub-select”.
[0181] - - - For topology 1 & topology 2 according to TR 38.848 (where UE acts as an intermediate node under network control), no RRC state, no mobility (e.g., no function similar to cell selection / reselection), no HARQ, no ARQ.
[0182] - NOTE 1: “≤ a few hundred μW” does not mean that WGs must set a specific value, but rather that whether the proposed design satisfies this requirement at the power consumption level is determined through WG discussions.
[0183] - - B. Referring to the table in Section 4.2.2 of TR 38.848, deployment scenarios having the following characteristics:
[0184] - - - Deployment Scenario 1 (Topology 1)
[0185] - - - - Base Station and Coexistence Characteristics: Microcell, Co-site
[0186] - - - Deployment Scenario 2 (Topology 2, UE as intermediate node under network control)
[0187] - - - - Base Station and Coexistence Characteristics: Macrocell, Co-site
[0188] - - - - The location of the intermediate node is indoors
[0189] - - C. FR1 License Band, FDD.
[0190] - - D. Frequency allocation in NR in-band, LTE / NR guard-band, and standalone band(s).
[0191] - - E. Focus on traffic types DO-DTT, DT, rUC1 (indoor stock) and rUC4 (indoor command).
[0192] Following RAN#104, this study evaluates whether the harmonized wireless interface design of item A above can support DO-A (Device-originated autonomous) use cases, but aims only to identify which design parts are insufficient for DO-A use cases.
[0193] - Transmissions from ambient IoT devices (including backscattering if used) may occur in at least the UL frequency band.
[0194] - The following goals are set within the general range.
[0195] - - 1. Evaluation Assumptions
[0196] - - - a) At least conclude the following design goal items assigned to the WGs in Section 5 (RAN Design Goals) of TR 38.848 [RAN1].
[0197] - - - - Section 5.3: Applicable Maximum Distance Target Value
[0198] - - - - Section 5.6: Specifying a Latency Definition Suitable for Use in RAN WGs
[0199] - - - - Section 5.8: Two-dimensional distribution of devices
[0200] - - - b) Define additional mandatory evaluation assumptions for deployment scenarios for coverage and coexistence evaluation [RAN1, RAN4].
[0201] - - - c) Identify the basic blocks / components of a possible ambient IoT device architecture by considering the state-of-the-art implementations of low-power, low-complexity devices that satisfy RAN design goals for power consumption and complexity [RAN1].
[0202] - - - d) Defines the calculation of the link budget for coverage evaluation, including whether and how to model carrier waveforms from nodes inside or outside the connection topology.
[0203] - NOTE: Performance evaluation of design objectives falls within the scope of feasibility and necessity studies for subsequent objectives, and can be performed, for example, through a review of field reference implementation, simulation, or analytical analysis.
[0204] - NOTE: RAN1 aims to minimize evaluation cases.
[0205] - - 2. Research necessary and feasible solutions for ambient IoT defined in a general scope, including determining which functions and procedures are necessary or unnecessary, and ensure the minimum functions required in Section 6.2 of TR 38.848.
[0206] - Positioning studies in Rel-19 are led by RAN3 and are limited to functions with no or minimal specification impact.
[0207] (Note: This does not imply any decision regarding WI generation).
[0208] - Investigate the feasibility and necessary functions for proximity determination (coordination with SA3 is required regarding privacy aspects).
[0209] - - - RAN1 Lead:
[0210] - Research the following regarding DL and UL of ambient IoT.
[0211] - - - - Frame structure, synchronization, timing, random access
[0212] - - - - Numericology, Bandwidth, Multiple Access
[0213] - - - - Waveform and Modulation
[0214] - - - - Channel Coding
[0215] - - - - Downlink Channel / Signal Characteristics
[0216] - - - - Uplink Channel / Signal Characteristics
[0217] Scheduling and Timing Relationships
[0218] Research on the necessary characteristics of carrier waveforms provided externally to ambient IoT devices, particularly including interference processing in ambient IoT UL receivers and NR base stations
[0219] - - For topology 2, the physical layer design is no different from topology 1.
[0220] - - - RAN2 Lead:
[0221] We study the functions required for a compact protocol stack and lightweight signaling procedures for ambient IoT to enable DO-DTT and DT data transmission, and determine what functions are needed.
[0222] - for example:
[0223] - - - - - Paging
[0224] - - - - - Random Access
[0225] - - - - - Data transmission (including essential RRC aspects complying with general range constraints)
[0226] - - - - - Interaction with upper layers
[0227] Functions not listed above are studied only when essential.
[0228] - - - RAN3 Lead:
[0229] Identify the signaling and procedural impacts on the CN-RAN interface to enable the following.
[0230] - - - - - Paging
[0231] Device Context Management
[0232] - - - - - Data transmission
[0233] Identify RAN architecture aspects, including whether partitioned architecture support is required.
[0234] Identify ambient IoT device location identification methods with no or minimal specification impact (e.g., reusing existing user location reports, or minimum specification impact for transmitting location information to the core network).
[0235] - - - RAN4 Lead:
[0236] Research on Coexistence between Ambient IoT and NR / LTE.
[0237] Research on RF Requirements for Ambient IoT:
[0238] - - - - - Ambient IoT Base Station Transmission and Reception
[0239] - - - - - Ambient IoT Device Transmission and Reception Based on General Range
[0240] - - - - - Intermediate Node (UE) Transmission and Reception Based on General Range
[0241] - RAN2 and RAN3 are expected to identify RAN-CN functional splits in coordination with SA2.
[0242] - NOTE: This study targets IoT in a much lower segment than existing 3GPP IoT technologies (e.g., NB-IoT, eMTC, RedCap, etc.). This study does not aim to replace existing 3GPP LPWA technologies.
[0243] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.
[0244] For example, in the present disclosure, a message may be interpreted as being replaced by at least one of a control message, a data message, a signal, a data signal, and / or a control signal.
[0245] In the following description, various names are exemplary and may be considered to perform the same or similar functions (regardless of their names) based on the content described in each step.
[0246] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).
[0247] For example, technical terms used in this disclosure may be as follows.
[0248] - FR1: Frequency Range 1. Refers to the frequency range of 6 GHz or lower (e.g., 450 MHz ~ 6000 MHz).
[0249] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) region above 24 GHz (e.g., 24,250 MHz ~ 52,600 MHz).
[0250] - BW: Bandwidth
[0251] - BWP: Bandwidth part
[0252] - RNTI: Radio network temporary identifier
[0253] - CRC: Cyclic redundancy check
[0254] - SCS: Subcarrier Spacing
[0255] - TB: Transport block
[0256] - FDRA: Frequency Domain Resource Allocation
[0257] - TDRA: Time Domain Resource Allocation
[0258] - RA: Random access
[0259] - MSGA: Preamble and payload transmissions of the random access procedure for 2-step random access (RA) type.
[0260] - MSGB: Response to MSGA in the 2-step random access procedure. MSGB is a response to MSGA in the 2-step random access procedure for contention resolution(s). MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.
[0261] - RO-N: RO (RACH Occasion) for normal UE 4-step RACH and 2-step RACH (if configured)
[0262] - RO-N1, RO-N2: When separate ROs are configured for normal UE 2-step RACH, they are distinguished as RO-N1 (4-step) and RO-N2 (2-step).
[0263] - RO-R: RO (RACH Occasion) configured separately from RO-N for redcap UE 4-step RACH and 2-step RACH (if configured)
[0264] - RO-R1, RO-R2: When separate ROs are configured for redcap UE 2-step RACH, they are distinguished as RO-R1 (4-step) and RO-R2 (2-step).
[0265] - PG-R: Group of MsgA-preambles for redcap UEs
[0266] - RAR: Random access response
[0267] - RAR window: A time window for monitoring RA responses.
[0268] - FH: Frequency hopping
[0269] - iBWP: Initial BWP
[0270] - iBWP-DL(-UL): Initial DL(UL) BWP
[0271] - iBWP-DL(-UL)-R: (separate) initials DL(UL) BWP for redcap
[0272] - CS: Cyclic shift
[0273] - NB: Narrowband
[0274] - TO: Traffic offloading
[0275] - mMTC; Massive machine-type communications
[0276] - eMBB: Enhanced mobile broadband communication
[0277] - URLLC: Ultra-reliable and low-latency communication
[0278] - RedCap: Reduced capability
[0279] - eRedCap: Enhanced Redcap
[0280] - FDD: Frequency Division Duplex
[0281] - HD-FDD: Half-duplex FDD
[0282] - DRX: Discontinuous reception
[0283] - RRC: Radio resource control
[0284] - RRM: Radio resource management
[0285] - MM: Mobility Management
[0286] - IWSN: Industrial wireless sensor network
[0287] - LPWA: Low power wide area
[0288] - RB: resource block
[0289] - CCE: Control Channel Element
[0290] - AL: Aggregation level
[0291] - PRG: Physical resource-block group
[0292] - DFT-s-OFDM: DFT-spread OFDM
[0293] - PBCH: Physical broadcast channel
[0294] - A-PBCH: Additional PBCH
[0295] - BD: Blind detection
[0296] - EPRE: RE star(per) energy(energy)
[0297] - SNR: Signal-to-Noise ratio
[0298] - TDM: Time Duplex Multiplexing
[0299] - FDM: Frequency duplex multiplexing
[0300] - DMRS: Demodulation reference signal
[0301] - TDD: Time Division Duplex
[0302] - PCI: Physical layer cell ID
[0303] - EH: Energy harvesting
[0304] - EH device: A device that operates based on EH. It may include all of the devices A / B / C currently under discussion by 3GPP. Additionally, while the present disclosure primarily considers RF EH, the EH device does not necessarily have to be RF EH-based.
[0305] - ES: Energizing signal. A signal / channel transmitted by a base station / IN / AN / UE for the purpose of supplying RF energy to a device operating on an RF-based energy harvesting basis. (Modulated) CW, NR / LTE DL / UL signals, etc. can be ES, and a dedicated signal / channel for ES can also be designed to support it.
[0306] - ET: Energy transfer
[0307] - CW: Carrier wave. Ambient IoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering an “externally provided” CW. Ambient IoT devices supporting independent signal generation-based UL transmission transmit information by modulating an “internally generated” CW. Unless otherwise noted, it is assumed to refer to an “externally provided” CW for backscattering. The CW can be used as an ES (energizing signal) for RF energy transfer.
[0308] - CWN: Carrier Wave Node. A node that provides the above CW. It may be a base station, IN, AN, or UE, and a separate CWN may exist for the purpose of providing CW.
[0309] - R: Reader / Interrogator. An RFID standard term. In the 3GPP ambient IoT context, depending on the topology, gNBs / eNBs, intermediate / assisting nodes, UEs, etc., can serve as readers. Additionally, since ambient IoT is not limited to 4G / 5G communication systems, it may include base stations, intermediate / assisting nodes, and UEs of next-generation communication systems. It may also refer to an ambient IoT reader.
[0310] - T: Tag / ambient IoT device. An RFID standard term. It may be interchangeable with EH device in this disclosure, and in the 3GPP ambient IoT context, it primarily refers to an ambient IoT device, device A / B / C.
[0311] - D: Ambient IoT device (may have the same meaning as T above)
[0312] - R=>T: Reader-to-Tag or Reader-to-Tag communication link. It may have the same meaning as a DL or forward link when a base station or intermediate / assisting node is the reader.
[0313] - R2D: R-to-D link (Can be synonymous with R=>T. Can be denoted as R=>D.)
[0314] - CW2D: CWN-to-D link (CW node to ambient IoT device link)
[0315] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / assisting node is the reader, it may have the same meaning as a UL or reverse / backward link.
[0316] - D2R: May have the same meaning as T=>R. Can be written as D=>R.
[0317] - R<=>T: Includes cases of R=>T and T=>R, or R=>T or T=>R. May apply to both R=>T and T=>R.
[0318] - R<=>D: Includes cases of R2D and D2R, or R2D or D2R. May apply to both R2D and D2R. (May have the same meaning as R<=>T)
[0319] - RF-EH: RF energy harvesting
[0320] - PRDCH: Physical R2D channel (may be denoted as PR2DCH). A physical channel for R2D communication.
[0321] - PDRCH: Physical D2R channel (may be denoted as PD2RCH). A physical channel for D2R communication.
[0322] - BS: Base station
[0323] - IN: Intermediate node. In Topology 2 (BS ↔ IN ↔ Ambient IoT device), IN acts as the reader. Relays, IABs, UEs, repeaters, etc. can be INs.
[0324] - AN: Assisting node. It can assist in DL transmission in topology 3-1 (BS→AN→ambient IoT device→BS) or assist in UL transmission in topology 3-2 (BS→ambient IoT device→AN→BS). Relays, IABs, UEs, repeaters, etc. can be ANs.
[0325] - UE: User Equipment. In the case of LTE, NR, or next-generation communication systems, it refers to the LTE, NR, or next-generation communication system UE / terminal, respectively. It is a form of general wireless communication terminal distinct from ambient IoT devices or devices A / B / C. In Topology 4 (UE ↔ ambient IoT device), the UE acts as the reader.
[0326] - Device: Unless otherwise noted, and when used alone, it refers to the EH device, ambient IoT device, or device A / B / C without distinction.
[0327] - AmIoT: Ambient IoT
[0328] - F-gap: Frequency gap
[0329] - T-gap: time gap
[0330] - TD: Time Domain
[0331] - FD: Frequency domain
[0332] - PEI: Paging Early Indication
[0333] - LP-WUS: Low-power wake-up signal
[0334] - LP-SS: Low-power synchronization signal
[0335] - RSRP: Reference signal received power
[0336] - ESRP: ES received power. May refer to RSRP measured using ES. May be synonymous with ES-RSRP.
[0337] - PRB: Physical resource block
[0338] - EH circuit: A circuit that performs EH operations. An EH device can be viewed as including an EH circuit in the form of a component.
[0339] - PHR: Power Headroom Report
[0340] - EHR: Energy headroom report
[0341] - BPF: Band-pass filter
[0342] - SM: Subcarrier modulation
[0343] For example, the methods proposed in this disclosure can be applied commonly to topology 1 and topology 2, and UE1 as gNB and IN can be referred to as a reader for convenience. For example, the disclosed content can be extended to cases where a reader receiving the BSS directly generates and transmits a CW, or where the node transmitting the CW is a separate node from the reader.
[0344] For example, an ambient IoT BS (base station) (e.g., reader) used in this disclosure may be a gNB in topology 1 and a specific UE in topology 2. For example, an ambient IoT device (e.g., tag) used in this disclosure may be interpreted as an ambient IoT device in both topology 1 and / or topology 2.
[0345] For example, the present disclosure may propose preamble, midamble, and postamble design methods that can be used for ambient IoT transmission and reception. For example, the expression "x-amble" in the present disclosure may be used as a term referring to preamble, midamble, and postamble. For example, preamble may mean transmission at the very beginning of a specific D2R or R2D transmission, midamble in the middle, and postamble at the very end.
[0346] For example, the preamble, midamble, and postamble mentioned in the present disclosure may be transmitted together with D2R, R2D transmissions (e.g., PDRCH, PRDCH), etc., or included in said D2R, R2D transmissions.
[0347] For example, the device ID mentioned in this disclosure may refer to a unique ID embedded within each device. For example, however, instead of the device ID used in this disclosure, a method of using an ID such as a C-RNTI that can be exchanged between a device / reader during an inventory round may also be considered.
[0348] For example, the state mentioned in the present disclosure may refer to states such as ON / SLEEP / OFF to increase the available time of a device in an ambient IoT system. Here, for example, the ON state can be defined as a state in which the device can perform TX / RX while consuming energy, the SLEEP state can be defined as a state in which the device can perform energy harvesting without performing TX / RX while maintaining memory content or timer / clock, etc., from the ON state, and finally, the OFF state can be defined as a state in which the device can perform energy harvesting without maintaining memory content or timer / clock, etc., from the ON state and without performing TX / RX.
[0349] In the present disclosure, ' / ' may mean 'and', 'or', or 'and / or' depending on the context.
[0350] FIG. 14 illustrates an example of a physical layer frame structure for device-to-reader (D2R) transmission according to one embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0351] Referring to FIG. 14, the D2R transmission may include at least one of a preamble, a midamble, a postamble, and / or a physical device-to-reader channel (PDRCH). For example, as a way to indicate the end of a PDRCH transmission in an ambient IoT system, a reader may provide the payload size of the PDRCH (e.g., TBS information).
[0352] FIG. 15 illustrates an example of a physical layer frame structure for device-to-reader (D2R) transmission according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0353] Referring to FIG. 15, the D2R transmission may include at least one of a preamble, a midamble, a postamble, and / or a physical device-to-reader channel (PDRCH). For example, as a way to indicate the end of a PDRCH transmission in an ambient IoT system, a device may transmit a D2R postamble attached immediately after the PDRCH transmission.
[0354] In ambient IoT systems, particularly in Rel-19 A-IoT, only methods for directly specifying the TBS size for D2R (data) transmission are defined, and D2R postambles are not introduced. As a result, the reader can indirectly determine when to end the PDRCH transmission only if it knows the PDRCH payload size (e.g., TBS) in advance.
[0355] However, if a D2R postamble is introduced after Rel-20 A-IoT, the following technical problems may occur.
[0356] - The method for indicating the termination of a PDRCH transmission can be redundantly determined by (i) a termination judgment based on TBS information and (ii) a termination judgment based on D2R postamble.
[0357] - When a reader instructs a device to transmit a D2R postamble along with a D2R preamble for fine timing acquisition, it may be unclear how the device should process the previously instructed TBS information.
[0358] - Consequently, there is a possibility of inconsistency in the PDRCH termination determination method, conflicts in control signaling between the reader and the device, unnecessary postamble transmission, or unnecessary padding.
[0359] Therefore, a clear definition of a method may be required for how the device indicates the end of a PDRCH transmission based on whether TBS information is included, for example, how to determine whether to send a postamble.
[0360] For example, as a method to indicate the end of a PDRCH transmission in an ambient IoT system, a method in which a device transmits a D2R postamble immediately after the PDRCH transmission (e.g., FIG. 14) and a method in which a reader provides the size of the PDRCH payload (e.g., TBS information) (e.g., FIG. 15) may be considered. Here, for example, in order to obtain the timing of the PDRCH transmitted by the device with precision from the perspective of the reader receiving, the device needs to be instructed to transmit the D2R postamble together with the D2R preamble. Here, for example, it needs to be defined how the instructed TBS information should be handled from the perspective of the device. For example, thus, the present disclosure may propose a method for indicating the termination of a PDRCH transmission based on whether TBS information and / or a D2R postamble is used in an ambient IoT system. For example, if a reader can indicate whether a D2R postamble may be used and / or whether to use a D2R postamble, or can indicate the TBS information of the PDRCH, the following methods may be proposed. For example, the reader may indicate whether to use a D2R postamble based on whether TBS information is provided. For example, the reader may indicate to use a D2R postamble based on not providing TBS information (e.g., FIG. 15).For example, the reader may instruct not to use the D2R postamble as a basis for providing TBS information (e.g., Fig. 14).
[0361] For example, [Method #1] A method that can be applied when considering providing TBS information as the default behavior.
[0362] For example, it may be defined that the reader provides the PDRCH's TBS information by default through the PRDCH control and / or data area that schedules the PDRCH. Here, for example, the reader may indicate whether to use a D2R postamble through R2D signaling separate from the TBS information (e.g., L1 / L2 control or data). For example, the reader may indicate whether to use a D2R postamble based on whether the reader provides the PDRCH's TBS information (through the PRDCH control and / or data area that schedules the PDRCH). For example, the reader may instruct to use a D2R postamble based on the fact that the reader does not provide TBS information of the PDRCH (e.g., FIG. 15). For example, the reader may instruct not to use a D2R postamble based on the fact that the reader provides TBS information of the PDRCH (e.g., FIG. 14). Here, for example, the device may be considered to operate as one of the following options.
[0363] For example, option 1-1: Since the default behavior is for TBS information for PDRCH transmission to be provided by the reader, the device can normally be defined to transmit PDRCH in accordance with the TBS information provided by the reader. For example, if the device is subsequently instructed to use a D2R postamble via separate R2D signaling from the reader, the device can be defined to transmit a D2R postamble after the PDRCH transmission ends, expecting that no further TBS information will be provided by the reader. For example, the device can be defined to ignore the TBS information provided by the reader and transmit a D2R postamble after the PDRCH transmission ends.
[0364] For example, option 1-2: Since the default operation is for TBS information for PDRCH transmission to be provided by the reader, the device can normally be defined to transmit PDRCH in accordance with the TBS information provided by the reader. For example, if TBS information for PDRCH transmission is subsequently not provided by the reader, the device can be defined to transmit a D2R postamble after the PDRCH transmission ends (e.g., FIG. 15).
[0365] According to the present disclosure, the following technical effects can be achieved.
[0366] (1) Clarification of the PDRCH transmission termination indication method
[0367] - Only when TBS information is not included in the PDRCH scheduling information is the device configured to send a postamble after the PDRCH transmission, thereby allowing the reader to clearly recognize the end of the PDRCH transmission solely by the presence or absence of the postamble.
[0368] (2) Improvement in timing acquisition performance on the reader reception side
[0369] Even in the absence of TBS information, since a postamble is explicitly transmitted after the PDRCH, the reader can accurately obtain the PDRCH end time and frame boundaries.
[0370] - It can be particularly advantageous in ultra-low power / low complexity environments such as ambient IoT.
[0371] (3) Prevent unnecessary postamble transmission
[0372] - If TBS information is provided, the reader knows the payload size, so it can determine the end of PDRCH without a postamble.
[0373] - By clearly defining only the opposite case, the present disclosure can provide a basis for distinguishing between cases where postamble transmission is necessary and cases where it is unnecessary.
[0374] (4) Ensure compatibility between Rel-19 / Rel-20 and later
[0375] - It provides control logic that enables the conflict-free coexistence of the Rel-19 method (TBS-based) and the D2R postamble method available from Rel-20 onwards, thereby minimizing design changes for existing devices / readers during the standard evolution process.
[0376] For example, [Method #2] A method that can be applied when considering the operation of sending a D2R postamble attached to PDRCH as the default operation.
[0377] For example, when a device transmits a PDRCH, using a D2R postamble can be defined as the default behavior. For example, additional TBS information may subsequently be provided through the PRDCH control and / or data area for scheduling the PDRCH as needed by the reader. For example, the reader may indicate whether to use a D2R postamble based on whether the reader provides the PDRCH's TBS information (through the PRDCH control and / or data area for scheduling the PDRCH). For example, the reader may instruct to use a D2R postamble based on the fact that the reader does not provide TBS information of the PDRCH (e.g., FIG. 15). For example, the reader may instruct not to use a D2R postamble based on the fact that the reader provides TBS information of the PDRCH (e.g., FIG. 14). Here, for example, the device may be considered to operate as one of the following options.
[0378] For example, option 2-1: Since the default behavior is to always transmit a D2R postamble after a PDRCH transmission, the device can normally be defined to transmit a D2R postamble immediately after the PDRCH transmission ends. For example, if PDRCH TBS information is subsequently provided by the reader through the PRDCH control and / or data area for scheduling the PDRCH, the device can be defined to transmit the PDRCH in accordance with the TBS information received from the reader and not transmit a D2R postamble (e.g., FIG. 14).
[0379] For example, option 2-2: Since the default behavior is to always send a D2R postamble after a PDRCH transmission, the device may normally be defined to send a D2R postamble immediately after the PDRCH transmission ends. For example, if the reader is subsequently configured / instructed not to use a D2R postamble, the device can expect to be provided with TBS information for the PDRCH transmission from the reader. For example, if TBS information for the PDRCH is provided from the reader through the PDRCH control and / or data area for scheduling the PDRCH, the device may transmit the PDRCH in accordance with said TBS information. For example, if the PDRCH TBS information is not provided by the reader through the PDRCH control and / or data area for scheduling the PDRCH, the device may transmit the PDRCH according to the TBS information that is pre-configured / instructed / defined (e.g., indicated via paging-related signals / channels and / or pre-defined as default values in the spec). Here, for example, the device may be defined not to transmit the D2R postamble after transmitting the PDRCH according to the instructions of the reader.
[0380] For example, [Method #3] A method for configuring a TBS table for PDRCH that includes TBS information and / or whether a D2R postamble is available.
[0381] For example, it can be defined to indicate whether to use a D2R postamble and TBS information for PDRCH through a single signaling. For example, a TBS table for PDRCH can be configured using the following examples.
[0382] For example, when configuring a TBS table for PDRCH, a specific index (e.g., index 0) may be defined as an index that instructs the use of D2R postamble, and TBS values may be defined using other indexes excluding that index. For example, subsequently, the reader may instruct the use of D2R postamble by instructing a specific index (e.g., index 0) of the TBS table through the PRDCH control and / or data area that schedules PDRCH, and may instruct the actual TBS information for PDRCH by instructing other values excluding that specific index (e.g., index 0) of the table. For example, if configured in this way, the device may be defined to transmit a D2R postamble after transmitting a PDRCH when a specific index of the TBS table (e.g., index 0) is indicated by the reader, and may be defined to transmit a PDRCH according to the corresponding TBS information when an index other than a specific index of the TBS table (e.g., index 0) is indicated by the reader.
[0383] For example, multiple indexes of a TBS table for PDRCH (e.g., indices from 0 to N / 2-1, or even number indexes, etc., when there are N total indexes) may be defined as indexes that indicate TBS information for PDRCH and allow the use of D2R postamble if the device is required, and the remaining multiple indexes excluding these (e.g., indices from N / 2 to N-1, or odd number indexes, etc., when there are N total indexes) may be defined as indexes that indicate only TBS information for PDRCH and are configured so that D2R postamble cannot be used. For example, if configured as such, and if the device checks the index value of the TBS table transmitted from the reader and indicates an index where a D2R postamble is available, it operates by default to transmit a PDRCH according to the indicated TBS information, but may also be permitted to use a D2R postamble according to predefined rules and the needs of the device. For example, as an example of the aforementioned predefined rule, if the device fills up all the D2R data to be transmitted and there is less than or equal to X bits remaining up to the configured TBS information, the device may be defined to perform zero padding after (or before) the D2R data by the number of remaining bits and not transmit a D2R postamble.For example, if the device has filled all the D2R data to be transmitted and there is still more than X bits remaining for the TBS information, the device may be defined to transmit the D2R postamble immediately after the PDRCH (without any zero padding or timing gap). For example, if the device checks the index value of the TBS table transmitted from the reader and the index indicated is defined as one that cannot use the D2R postamble, the device may be defined to transmit the PDRCH according to the indicated TBS information.
[0384] For example, when configuring a TBS table for PDRCH, a specific index (e.g., index 0) can be used to indicate transmission without actual D2R data. For example, subsequently, if the reader indicates a specific index (e.g., index 0) of the table through the PRDCH control and / or data area that schedules the PDRCH, the device may be defined to transmit only L1 D2R control information to the PDRCH. For example, the L1 D2R control information may include feedback (e.g., ACK / NACK) regarding the R2D signal / channel or device reports (e.g., energy state). For example, if the L1 D2R control size is always fixed, the device may be defined to transmit only L1 D2R control information without transmitting a D2R postamble, and if the L1 D2R control size is variable, the device may be defined to transmit L1 D2R control information and then immediately transmit a D2R postamble. For example, another specific index of the TBS table (e.g., index 1 (or index N-1, where the total number of indices is N)) may be defined as an index that instructs the use of a D2R postamble.For example, subsequently, the reader may instruct the use of a D2R postamble by indicating a specific index of the corresponding TBS table (e.g., index 1 or index N-1) through the PRDCH control and / or data area that schedules the PDRCH. For example, TBS information for the actual PDRCH may be indicated by indicating other index values excluding the specific index.
[0385] For example, if configured in this way, the device may be defined to transmit only L1 D2R control information to PDRCH when a specific index of the TBS table (e.g., index 0) is indicated by the reader, the device may be defined to transmit D2R postamble after PDRCH transmission when another specific index of the TBS table (e.g., index 1 (or index N-1)) is indicated by the reader, and when an index other than the aforementioned specific indices of the TBS table (e.g., index 0 or index 1 (or index N-1)) is indicated by the reader, the device may be defined to transmit PDRCH according to the corresponding TBS information.
[0386] For example, in the proposed methods above, when a device must perform a PDRCH transmission based on TBS information provided (or predefined) from a reader (e.g., when the device is configured / instructed / defined not to use a D2R postamble), a case may also be considered where the D2R data to be transmitted by the device is smaller than the configured TB size. For example, in such a situation, it may be defined that the device first fills the D2R data to be transmitted and then performs zero padding until the entire TB size instructed by the reader is filled.
[0387] For example, in the proposed methods above, the predefined timing and / or timing value set / instructed by the reader may be set in units of chip(s) / codeword(s) / NR OFDM(s) / NR slot (chip(s) / codeword(s) / NR OFDM(s) symbol / NR slot), or after defining a time unit for ambient IoT (e.g., T c ) It may be set / instructed in units of the corresponding time unit, or set / instructed as a multiple of the corresponding time unit, etc.
[0388] For example, in an ambient IoT system, the time from when a device completes the transmission of a D2R signal / channel until the reader starts transmitting an R2D signal / channel is T D2R It can be defined as. Here, for example, T D2RThe min / max values of the value can also be defined separately and set / instructed by the reader, or predefined in the specification. For example, however, depending on whether the D2R signal / channel transmitted by the device includes a D2R postamble and / or the length of the D2R x-amble and / or whether the D2R signal / channel is repeated, T D2R_min , T D2R_max The value needs to be set differently. For example, therefore, in the present disclosure, T according to the D2R signal / channel transmission type in an ambient IoT system D2R_min , T D2R_max Methods for setting the value differently can be suggested.
[0389] For example, [Method #1] T depending on whether D2R postamble is transmitted D2R How to set different values.
[0390] For example, if a device transmits a D2R preamble and a D2R postamble together when transmitting a PDRCH, the reader can use both the D2R preamble and the D2R postamble to perform time acquisition and / or channel estimation, etc. For example, however, when performing time acquisition and / or channel estimation using both the D2R preamble and D2R postamble in this manner, additional processing time may be required from the reader's perspective compared to the case where time acquisition and / or channel estimation are performed using only the D2R preamble, because the reader must receive the entire D2R postamble first, utilize it to perform time acquisition and / or channel estimation, and then decode the previously received PDRCH. For example, or, even if the TBS is large during D2R transmission and the D2R midamble is included in the D2R transmission, the reader can perform time acquisition and / or channel estimation using both the D2R postamble transmitted by the device and the immediately preceding D2R midamble, and subsequently decode the previously received PDRCH; therefore, similar to the previous case, additional processing time may be required from the reader's perspective.For example, therefore, compared to when the device does not transmit a D2R postamble, T when it transmits a D2R postamble. D2R_min and / or T D2R_max It can be defined to set the value larger. For example, or depending on the M value used for D2R transmission (e.g., D2R chip duration), T D2R_min and / or T D2R_max Methods of setting different values may also be considered. For example, as the value of M used for D2R transmission increases (e.g., as the D2R chip duration decreases), T D2R_min and / or T D2R_max The value can be set small.
[0391] For example, T that can be applied when the device does not transmit a D2R postamble. D2R_min and / or T D2R_max A value that the reader can set / instruct, and which the device can apply independently when transmitting a D2R postamble T D2R_min and / or T D2R_max value (e.g., T D2R_min_postamble and / or T D2R_max_postamble The reader can set / instruct )
[0392] For example, T that can be applied when the device does not transmit a D2R postamble. D2R_min and / or T D2R_max The reader can set / instruct the value, and when the device transmits the D2R postamble, the above T D2R_min and / or T D2R_maxA time offset value that can be commonly added to the value (e.g., T D2R_offset The reader can set / instruct ). For example, if the device has transmitted a D2R postamble, the T set / instructed by the reader D2R_min and / or T D2R_max T additionally set / instructed to the value D2R_offset Add the values respectively (e.g., T D2R_min + T D2R_offset and / or T D2R_max + T D2R_offset ) It can be defined to be calculated as the final timing.
[0393] For example, T that can be applied when the device does not transmit a D2R postamble. D2R_min and / or T D2R_max The reader can set / instruct the value, and when the device transmits the D2R postamble, the above T D2R_min and / or T D2R_max A time offset value that can be applied individually to the value (e.g., T D2R_min_offset and / or T D2R_max_offset The reader can set / instruct ). For example, if the device has transmitted a D2R postamble, the T set / instructed by the reader D2R_min and / or T D2R_max T additionally set / instructed to the value D2R_min_offset , T D2R_max_offset Add the values respectively (e.g., T D2R_min + T D2R_min_offset and / or T D2R_max + T D2R_max_offset ) can be defined to be calculated as the final timing. Here, for example, the reader [uses] the two values above (e.g., T D2R_min_offsetand / or T D2R_max_offset If only one of ) is provided, the device sets the indicated value to T D2R_min and / or T D2R_max It can be defined as being applied commonly to both sides.
[0394] For example, [Method #2] T according to the D2R x-amble length D2R How to set different values.
[0395] For example, multiple formats may be considered for D2R x-ambles (e.g., preamble, midamble, postamble). For instance, the sequence length constituting the extended preamble may be defined as longer than that of the normal preamble, or the extended preamble may be constructed by adding zero padding to the normal preamble. Here, for instance, if a device transmits a relatively longer extended preamble, the reader may require more processing time compared to when transmitting a relatively shorter normal preamble. For example, therefore, when the sequence length of the D2R x-amble transmitted by the device and / or the duration required for transmission (e.g., if Manchester encoding is considered, applying a relatively large value of M shortens the transmission duration) is relatively larger, T D2R_min and / or T D2R_maxIt can be defined to set the value larger. Here, for example, using the specific examples proposed in Method 1, it can be applied similarly as follows.
[0396] For example, T that can be applied when a device transmits a normal (short) x-amble (or when the duration required to transmit the x-amble is relatively short). D2R_min and / or T D2R_max T that can be applied when the reader can set / instruct the value, and independently when the device transmits an extended (long) x-amble (or when the duration required to transmit the x-amble is relatively long). D2R_min and / or T D2R_max value (e.g., T D2R_min_extended and / or T D2R_max_extended The reader can set / instruct )
[0397] For example, T that can be applied when a device transmits a normal (short) x-amble (or when the duration required to transmit the x-amble is relatively short). D2R_min and / or T D2R_max The reader can set / instruct the value, and when the device transmits an extended (long) x-amble (or when the duration required to transmit the x-amble is relatively long), the above T D2R_min and / or T D2R_max A time offset value that can be commonly added to the value (e.g., T D2R_offsetThe reader can set / instruct ). For example, if the device transmits an extended (long) x-amble, the T set / instructed by the reader D2R_min and / or T D2R_max T additionally set / instructed to the value D2R_offset Add the values respectively (e.g., T D2R_min + T D2R_offset and / or T D2R_max + T D2R_offset ) It can be defined to be calculated as the final timing.
[0398] For example, T that can be applied when a device transmits a normal (short) x-amble (or when the duration required to transmit the x-amble is relatively short). D2R_min and / or T D2R_max The reader can set / instruct the value, and when the device transmits an extended (long) x-amble (or when the duration required to transmit the x-amble is relatively long), the above T D2R_min and / or T D2R_max A time offset value that can be applied individually to the value (e.g., T D2R_min_offset and / or T D2R_max_offset The reader can set / instruct ). For example, if the device transmits an extended (long) x-amble, the T set / instructed by the reader D2R_min and / or T D2R_max T additionally set / instructed to the value D2R_min_offset , T D2R_max_offset Add the values respectively (e.g., T D2R_min + T D2R_min_offsetand / or T D2R_max + T D2R_max_offset ) can be defined to be calculated as the final timing. Here, for example, the reader [uses] the two values above (e.g., T D2R_min_offset and / or T D2R_max_offset If only one of ) is provided, the device sets the indicated value to T D2R_min and / or T D2R_max It can be defined as being applied commonly to both sides.
[0399] For example, depending on the D2R chip duration (or the M value of PDRCH, or the range of the M value, etc.), T D2R_min and / or T D2R_max A time offset value that can be applied commonly or individually to values (e.g., T D2R_min_offset and / or T D2R_max_offset One can also consider how ) is determined. For example, if the D2R chip duration value is large (or the PDRCH M value is small), from the reader's perspective, the D2R chip rate is relatively slow compared to the channel estimation and sync processing capacity, so separate processing timing may not be required. For example, therefore, if the D2R chip duration value is large (or the PDRCH M value is small), the reader T D2R_min and / or T D2R_max A time offset value that can be applied commonly or individually to values (e.g., T D2R_min_offset and / or T D2R_max_offsetIt can be defined as not setting ). For example, if the D2R chip duration value is small (or the PDRCH M value is large), from the reader's perspective, the D2R chip rate is relatively fast compared to the channel estimation and sync processing capacity, so separate processing timing may be required. For example, or, the smaller the D2R chip duration value (or the larger the PDRCH M value), the more the reader T D2R_min and / or T D2R_max A time offset value that can be applied commonly or individually to values (e.g., T D2R_min_offset and / or T D2R_max_offset ) can be set to a small value. For example, therefore, if the D2R chip duration value is small (or if the PDRCH M value is large, the reader T D2R_min and / or T D2R_max A time offset value that can be applied commonly or individually to values (e.g., T D2R_min_offset and / or T D2R_max_offset It can be defined as setting / instructing ).
[0400] For example, in the proposed methods above, when a device must perform a PDRCH transmission based on TBS information provided (or predefined) from a reader (e.g., when the device is configured / instructed / defined not to use a D2R postamble), a case may also be considered where the D2R data to be transmitted by the device is smaller than the configured TB size. For example, in such a situation, it may be defined that the device first fills the D2R data to be transmitted and then performs zero padding until the entire TB size instructed by the reader is filled.
[0401] For example, in the proposed methods above, the predefined timing and / or timing value set / instructed by the reader may be set in units of chip(s) / codeword(s) / NR OFDM(s) / NR slot (chip(s) / codeword(s) / NR OFDM(s) symbol / NR slot), or after defining a time unit for ambient IoT (e.g., T c ) It may be set / instructed in units of the corresponding time unit, or set / instructed as a multiple of the corresponding time unit, etc.
[0402] For example, the base station can use BS monostatic sensing mode. For example, the base station can use UE-BS bistatic sensing mode. For example, the base station can use a combination of BS monostatic sensing mode and UE-BS bistatic sensing mode (e.g., joint / hybrid).
[0403] For example, the sensing results used in the present disclosure (e.g., LOS information obtained by sensing measurement) may utilize sensing results obtained from non-3GPP sensing, such as radar / camera / lidar, as well as 3GPP sensing using 3GPP signals. For example, parameters such as thresholds and specific times used in the procedure may also be set differently depending on the type of sensor used (e.g., 3GPP sensing or non-3GPP sensing).
[0404] For example, in the above procedure, the serving base station may trigger a 3GPP sensing operation based on non-3GPP sensing results. For example, if the LOS probability decreases based on the non-3GPP sensing results, a 3GPP sensing operation may be performed to obtain more accurate sensing results. For example, conversely, a non-3GPP sensing operation may be triggered based on 3GPP sensing results. For example, this may be configured by considering the difference in accuracy between the 3GPP sensing operation and the non-3GPP sensing operation, as well as the required current consumption. For example, additionally, this operation may be used as a trigger condition for a sensing operation between the serving base station and the neighbor base station.
[0405] Combinations of various embodiments of the present disclosure may be applied differently depending on the payload type of the satellite (e.g., regenerative payload or transparent payload).
[0406] Combinations of various embodiments of the present disclosure may be applied differently to the type of non-geostational network node (e.g., GEO (geostationary earth orbit), NGEO (non-geostationary earth orbit), LEO (low earth orbit), MEO (medium earth orbit), HASP (high altitude satellite platform), drone) or altitude or fixed beam footprint or cell-moving beam footprint.
[0407] For example, in the embodiments of the present disclosure, the TDD setting and utilization are not limited to the TDD band, and can be extended to combinations of the FDD band and / or specific DL band and / or UL band.
[0408] For example, in an embodiment of the present disclosure, a base station or network node may be a satellite. For example, a base station or network node may be associated with a transparent payload. For example, a base station or network node may be associated with a regenerated payload.
[0409] A combination of embodiments of the present disclosure may operate in conjunction with each other.
[0410] Various embodiments of the present disclosure may be applied differently depending on the link type (DL, UL, SL) and / or the data type (SIB, group cast, unicast) and / or the search space type (CSS (common search space), USS (UE-specific search space)) where the scheduling PDCCH is detected and / or the base station node type and / or altitude and / or whether there is a power constraint. For example, a combination of various embodiments of the present disclosure may be applied only when involved in SIB transmission.
[0411] For example, in the present disclosure, the machine learning model may be an AI / ML model.
[0412] For example, in the present disclosure, a base station or network may be a TRP and / or an NB and / or an AMF and / or a (system) core. For example, in the present disclosure, an NB may be an AMF and / or a (system) core. For example, in the present disclosure, a system core may be an AMF and / or a (system) core.
[0413] For example, in the present disclosure, a sensing signal may be interpreted as having the same meaning as a sensing reference signal.
[0414] For example, in the present disclosure, sensing data may be interpreted as having the same meaning as sensing measurement data or sensing measurement report.
[0415] For example, the embodiments of the present disclosure may be extended to all of the above six sensing scenarios. For example, the embodiments of the present disclosure may be applicable to all of the above six sensing scenarios.
[0416] For example, the methods proposed in this disclosure can be applied to both 3GPP sensing data and non-3GPP sensing data.
[0417] For example, in the present disclosure, sensing data may be data derived by a sensing radio measurement entity based on radio signals (e.g., reflected, refracted, diffracted) affected by an object or environment of interest for the purpose of sensing. For example, this data may be raw measurements and may optionally be further processed within the sensing radio measurement entity. For example, the sensing data may include at least one of 3GPP sensing data or non-3GPP sensing data.
[0418] For example, in the present disclosure, 3GPP sensing data is data obtained from 3GPP radio signals that have been affected (e.g., reflected, refracted, diffracted) by an object or environment of interest for the purpose of sensing, and may optionally be processed within a 5G system.
[0419] For example, in the present disclosure, non-3GPP sensing data may be data provided by a non-3GPP sensor (e.g., video, LiDAR, sonar) regarding an object or environment of interest for the purpose of sensing.
[0420] For example, in the present disclosure, 5G / 6G radio sensing may be a 5GS / 6GS function that provides a function to acquire information about the characteristics of an environment and / or objects within the environment (e.g., shape, size, orientation, speed, location, distance, relative movement between objects, etc.) using NR radio frequency signals, and may, in some cases, be extended by information generated through a previously defined function in the EPC and / or E-UTRAN.
[0421] For example, in the present disclosure, sensing auxiliary information may be information provided to a 5G system from a trusted third party and may be used to support the derivation of sensing results. This information may not include 3GPP sensing data. For example, examples of sensing auxiliary information may include map information, location information, a UE identifier (ID) attached to or located near a sensing target, UE location information, UE velocity information, etc.
[0422] For example, in the present disclosure, sensing context information may be information that a 5G / 6G system exposes to a trusted third party along with the sensing results, and may provide context regarding the conditions under which the sensing results were derived. This information may not include 3GPP sensing data. For example, examples of sensing context information may include map information, location information, time of capture, UE location, and ID. This context information may be required in scenarios where the sensing results need to be combined with data from other sources outside of 5GS.
[0423] For example, in the present disclosure, a sensing group may be a set of sensing transmitters and sensing receivers whose locations are known and capable of synchronously collecting sensing data.
[0424] For example, in the present disclosure, a sensing receiver may be an entity that receives a sensing signal used by a sensing service in operation. The sensing receiver may be a RAN node or part of a UE. The sensing receiver may be located in the same entity as the sensing transmitter or in a different entity.
[0425] For example, in the present disclosure, the sensing result may be processed 3GPP sensing data requested by a service consumer.
[0426] For example, in the present disclosure, a sensing signal may be a transmission signal on a 3GPP radio interface that can be used for sensing purposes. For example, this definition may refer to NR radio frequency signals and, in some cases, may be extended to information generated from existing functions of the EPC and / or E-UTRAN.
[0427] For example, a sensing transmitter may be an entity that transmits a sensing signal used by a sensing service in an operation. A sensing transmitter may be part of a RAN node or a UE. A sensing transmitter may be located in the same entity as a sensing receiver or in a different entity.
[0428] For example, the target sensing service area may be an orthogonal coordinate location area that satisfies a specific sensing service quality and is to be sensed by deriving the characteristics of the environment and / or objects within the environment from 3GPP radio signals that have been affected (e.g., reflected, refracted, diffracted). This may include both indoor and outdoor environments.
[0429] For example, the present disclosure may be applied to base stations (e.g., TRP) and / or terminal monostatics. For example, the present disclosure may also be applied to base station-base station (e.g., TRP-TRP), base station-UE (e.g., TRP-UE), UE-base station (e.g., UE-TRP), and / or UE-UE bistatics.
[0430] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.
[0431] For example, in the present disclosure, a message may be interpreted as being replaced by at least one of a control message, a data message, a signal, a data signal, and / or a control signal.
[0432] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).
[0433] For example, in the present disclosure, the bandwidth part (BWP) may be replaced with a bandwidth setting set or a wireless resource set, etc.
[0434] For example, in the present disclosure, the wireless resource profile exemplified may be applied as a BWP (bandwidth part), a bandwidth setting set, a wireless resource set, etc.
[0435] For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the resource pool (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the congestion level (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the service priority (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the service type (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to QoS requirements (e.g., latency, reliability) (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to PQI (5QI (5G QoS identifier) for PC5). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to traffic types (e.g., periodic generation or non-periodic generation). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to SL transmission resource allocation modes (e.g., Mode 1 or Mode 2).For example, whether the proposed method / rule of the present disclosure applies and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not support sidelink DRX operation).
[0436] For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set depending on whether PUCCH setting is supported (e.g., when a PUCCH resource is set or when a PUCCH resource is not set). For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set for a resource pool (e.g., a resource pool where PSFCH is set or a resource pool where PSFCH is not set). For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set for the type of service / packet. For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set for the priority of the service / packet. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be set specifically (or differently or independently) to a QoS profile or QoS requirements (e.g., URLLC / EMBB traffic, reliability, latency). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be set specifically (or differently or independently) to a PQI. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be set specifically (or differently or independently) to a PFI. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be set specifically (or differently or independently) to a cast type (e.g., unicast, groupcast, broadcast). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be set specifically (or differently or independently) to a (resource pool) congestion level (e.g., CBR).For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to an SL HARQ feedback method (e.g., NACK-only feedback, ACK / NACK feedback). For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to HARQ Feedback Enabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to HARQ Feedback Disabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether a PUCCH-based SL HARQ feedback reporting operation is enabled. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set depending on whether pre-emption or pre-emption-based resource reselection is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set depending on whether re-evaluation or re-evaluation-based resource reselection is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set to the (L2 or L1) (source and / or destination) identifier. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values may be specifically (or differently or independently) set to the (L2 or L1) (combination of source ID and destination ID) identifier.For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the identifier (L2 or L1) (combination of the pair of source ID and destination ID and cast type). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the direction of the pair of source layer ID and destination layer ID. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the PC5 RRC connection / link. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether SL DRX is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether SL DRX is supported. For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values may be set specifically (or differently or independently) to an SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values may be set specifically (or differently or independently) to cases where (non)periodic resource reservation is performed. For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values may be set specifically (or differently or independently) to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not support sidelink DRX operation).
[0437] The applicability of the proposals and proposal rules of the present disclosure (and / or related parameter setting values) may also apply to mmWave sidelink operations.
[0438] For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the service type (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the priority (LCH or service) (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to QoS requirements (e.g., latency, reliability, minimum communication range) (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the PQI parameter (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL HARQ feedback ENABLED LCH / MAC PDU (transmission) (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL HARQ feedback DISABLED LCH / MAC PDU (transmission). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to CBR measurement values of the resource pool. For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL cast type (e.g., unicast, groupcast, broadcast).For example, the application status of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL GroupCast HARQ feedback options (e.g., NACK only feedback, ACK / NACK feedback, TX-RX distance-based NACK only feedback). For example, the application status of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL Mode 1 CG type (e.g., SL CG type 1 or SL CG type 2). For example, the application status of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL Mode type (e.g., Mode 1 or Mode 2). For example, the application status of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to resource pool. For example, the parameter values regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on whether the PSFCH resource is a resource pool where it is configured. For example, the parameter values regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the source (L2) ID. For example, the parameter values regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the destination (L2) ID. For example, the parameter values regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the PC5 RRC connection link.For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL link (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the connection status (e.g., RRC CONNECTED status, IDLE status, INACTIVE status) (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL HARQ process (ID) (or differently or independently). For example, the applicability of the above rule and / or parameter values related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL DRX operation (of the TX UE or RX UE) (or differently or independently). For example, the parameter values regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the power saving (TX or RX) UE. For example, the parameter values regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the case where PSFCH TX and PSFCH RX overlap (and / or multiple PSFCH TXs exceeding the UE's capability) (and / or where PSFCH TX (and / or PSFCH RX) are omitted) from the perspective of a specific UE. For example, the parameter values regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the case where the RX UE actually (successfully) receives a PSCCH (and / or PSSCH) (re)transmission from the TX UE.
[0439] For example, the setting (or designation) wording in the present disclosure may be interpreted in an extended manner, such as a form in which a base station informs a terminal through a predefined (physical layer or upper layer) channel / signal (e.g., SIB, RRC, MAC CE) (and / or a form provided through pre-configuration and / or a form in which a terminal informs another terminal through a predefined (physical layer or upper layer) channel / signal (e.g., SL MAC CE, PC5 RRC)).
[0440] For example, the PSFCH wording in the present disclosure may be extended to (NR or LTE) PSSCH (and / or (NR or LTE) PSCCH) (and / or (NR or LTE) SL SSB (and / or UL channel / signal)). Additionally, the proposed methods of the present disclosure may be combined with each other and extended (in a new form).
[0441] For example, in the present disclosure, a specific threshold value may refer to a threshold value that is predefined or set (in advance) by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, a specific setting value may refer to a value that is predefined or set (in advance) by an upper layer (including the application layer) of a network, base station, or terminal. For example, an operation set by a network / base station may refer to an operation in which the base station sets (in advance) to the UE through upper layer RRC signaling, sets / signals to the UE through MAC CE, or signals to the UE through DCI.
[0442] The operation of the present disclosure can be applied to all side-link unicast / group cast / broadcast operations.
[0443] In an embodiment of the present disclosure, the message may be interpreted as being replaced with a control message or a data message or a signal or a data signal or a control signal.
[0444] In an embodiment of the present disclosure, a beam management operation may be interpreted as being replaced by beam selection or spatial filter selection or beam pairing or spatial filter pairing or beam failure recovery or spatial filter recovery or beam sweeping or spatial filter sweeping or beam switching or spatial filter switching or measurement of a reference signal resource or measurement of a reference signal resource reporting operation or beam reporting or spatial filter reporting, etc.
[0445] In an embodiment of the present disclosure, the beam may be interpreted by being replaced with an RS or an RS resource or a spatial filter resource.
[0446] In an embodiment of the present disclosure, RS can be interpreted as being replaced by an RS resource or a spatial filter resource.
[0447] In an embodiment of the present disclosure, the transmission terminal may be interpreted as being replaced with a terminal that transmits a beam, a terminal that transmits a beam RS, or a terminal that transmits a beam RS resource, etc.
[0448] In an embodiment of the present disclosure, the receiving terminal may be interpreted as being replaced with a terminal receiving a beam, a terminal receiving a beam RS, or a terminal receiving a beam RS resource.
[0449] In an embodiment of the present disclosure, the transmission beam or reception beam information transmitted and received by the terminal may be interpreted as being replaced with resource information of a reference signal (RS) associated with the transmission beam and resource information of a reference signal (RS) associated with the reception beam.
[0450] In the embodiments of the present disclosure, the DCR (direct communication request) and / or DCA (direct communication accept) messages may be interpreted as being replaced by the PC5-S DCR and / or PC5-S DCA messages, etc.
[0451] In embodiments of the present disclosure, spatial setting and / or transmission configuration indication (TCI) information and / or quasi-co-location (QCL) information and / or beams, etc., may refer to each other and / or may be interpreted as being replaced by beam-related information, beam direction, spatial domain transmission or reception filter, etc.
[0452] In an embodiment of the present disclosure, the beam may be interpreted as being replaced by a transmitting beam or a receiving beam or a spatial filter or a spatial transmission (TX) filter or a spatial area transmission (TX) filter or a spatial reception (RX) filter or a spatial area reception (RX) filter.
[0453] In an embodiment of the present disclosure, the transmit / transmit beam may be interpreted as being replaced by a spatial transmission (TX) filter or a spatial area transmission (TX) filter.
[0454] In an embodiment of the present disclosure, the receiving beam may be interpreted as being replaced by a spatial receiving (RX) filter or a spatial area receiving (RX) filter.
[0455] In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for transmission is identical may mean that the spatial area TX filter of the terminal is identical for two different transmission signals. In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for reception is identical may mean that two different reception signals are in a QCL 'TypeD' relationship and / or have a relationship using the same spatial RX parameter.
[0456] For example, the control message (or signal) and / or data message (or signal) in the present disclosure may mean a control message (or signal) and / or data message (or signal) for wireless communication (e.g., LTE communication, NR communication, 6G communication, Wi-Fi communication, Bluetooth communication, and / or other wireless communication) that is not a radar signal.
[0457] For example, the source ID and destination ID disclosed in the present disclosure may mean a source layer 1 ID and a destination layer 1 ID and / or a source layer 2 ID and a destination layer 2 ID.
[0458] FIG. 16 illustrates a procedure performed by an apparatus according to one embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.
[0459] Referring to FIG. 16, at step S1610, the device may receive information for scheduling a PDRCH (physical D2R (device to reader) channel) from the reader. At step S1620, the device may transmit the PDRCH to the reader based on the information for scheduling the PDRCH. At step S1630, the device may transmit a postamble of the PDRCH to the reader based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information.
[0460] For example, based on the transmission of the above postamble, the transmission of the above PDRCH may be terminated.
[0461] For example, the above post-ambble may be a D2R post-ambble.
[0462] For example, the information for the scheduling of the above PDRCH can be received through the PRDCH (physical reader to device (R2D) channel).
[0463] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the above postamble may not be transmitted after the above transmission of the above PDRCH.
[0464] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the transmission of the above PDRCH may be based on the above TBS information.
[0465] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the transmission of the above PDRCH may be based on the payload size of the above PDRCH included in the above TBS information.
[0466] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, and based on the fact that the size of the data to be transmitted by the device on the above PDRCH is smaller than the payload size of the above PDRCH included in the above TBS information, zero padding may be performed after the data up to the payload size.
[0467] For example, based on the device acquiring a TBS table related to the postamble and the TBS information, and based on the information for scheduling the PDRCH including a first index related to the TBS table, the device may transmit the postamble to the reader after the transmission of the PDRCH.
[0468] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a second index associated with the TBS table, the postamble may not be transmitted after the transmission of the PDRCH.
[0469] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including the second index associated with the TBS table, the transmission of the PDRCH may be based on the payload size of the PDRCH included in the TBS information.
[0470] For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being smaller than or equal to the payload size of the PDRCH included in the TBS information, zero padding may be performed after the data up to the payload size without the transmission of the postamble. For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being larger than the payload size of the PDRCH included in the TBS information, the postamble may be transmitted after the transmission of the PDRCH.
[0471] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a fourth index associated with the TBS table, only control information may be transmitted on the PDRCH without data transmission.
[0472] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (102) of a device (100) may receive information for scheduling a PDRCH (physical D2R (device to reader) channel) from a reader (for example, the processor (102) of the device (100) may control a transceiver (106) to receive information for scheduling a PDRCH (physical D2R (device to reader) channel) from a reader). For example, the processor (102) of the device (100) may transmit the PDRCH to the reader based on the information for scheduling the PDRCH (for example, the processor (102) of the device (100) may control a transceiver (106) to transmit the PDRCH to the reader based on the information for scheduling the PDRCH). For example, the processor (102) of the device (100) can transmit the post-transmission post-amble of the PDRCH to the reader based on the fact that the information for the scheduling of the PDRCH does not include TBS (transport block size) information (for example, the processor (102) of the device (100) can control the transceiver (106) to transmit the post-transmission post-amble of the PDRCH to the reader based on the fact that the information for the scheduling of the PDRCH does not include TBS (transport block size) information).
[0473] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the device to: receive information for scheduling a physical D2R (device to reader) channel from a reader based on execution by the at least one processor; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble of the PDRCH to the reader based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0474] For example, based on the transmission of the above postamble, the transmission of the above PDRCH may be terminated.
[0475] For example, the above post-ambble may be a D2R post-ambble.
[0476] For example, the information for the scheduling of the above PDRCH can be received through the PRDCH (physical reader to device (R2D) channel).
[0477] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the above postamble may not be transmitted after the above transmission of the above PDRCH.
[0478] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the transmission of the above PDRCH may be based on the above TBS information.
[0479] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the transmission of the above PDRCH may be based on the payload size of the above PDRCH included in the above TBS information.
[0480] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, and based on the fact that the size of the data to be transmitted by the device on the above PDRCH is smaller than the payload size of the above PDRCH included in the above TBS information, zero padding may be performed after the data up to the payload size.
[0481] For example, based on the device acquiring a TBS table related to the postamble and the TBS information, and based on the information for scheduling the PDRCH including a first index related to the TBS table, the device may transmit the postamble to the reader after the transmission of the PDRCH.
[0482] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a second index associated with the TBS table, the postamble may not be transmitted after the transmission of the PDRCH.
[0483] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including the second index associated with the TBS table, the transmission of the PDRCH may be based on the payload size of the PDRCH included in the TBS information.
[0484] For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being smaller than or equal to the payload size of the PDRCH included in the TBS information, zero padding may be performed after the data up to the payload size without the transmission of the postamble. For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being larger than the payload size of the PDRCH included in the TBS information, the postamble may be transmitted after the transmission of the PDRCH.
[0485] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a fourth index associated with the TBS table, only control information may be transmitted on the PDRCH without data transmission.
[0486] According to one embodiment of the present disclosure, a processing device (configured to control the device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the device to: receive information for scheduling a physical D2R (device to reader) channel from a reader based on execution by the at least one processor; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble to the reader after transmission of the PDRCH based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0487] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the device may: receive information for scheduling a physical D2R (device to reader) channel (PDRCH) from a reader; transmit the PDRCH to the reader based on the information for scheduling the PDRCH; and transmit a postamble to the reader after transmission of the PDRCH based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0488] FIG. 17 illustrates a procedure performed by a reader according to one embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.
[0489] Referring to FIG. 17, in step S1710, the reader may transmit information for scheduling a PDRCH (physical D2R (device to reader) channel) to the device. In step S1720, the reader may receive the PDRCH from the device based on the information for scheduling the PDRCH. In step S1730, the reader may receive the post-received postamble of the PDRCH from the device based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information.
[0490] For example, based on the reception of the above postamble, the reception of the above PDRCH may be terminated.
[0491] For example, the above post-ambble may be a D2R post-ambble.
[0492] For example, the information for the scheduling of the above PDRCH can be transmitted via the PRDCH (physical reader to device (R2D) channel).
[0493] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the above postamble may not be received after the above reception of the above PDRCH.
[0494] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the reception of the above PDRCH may be based on the above TBS information.
[0495] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the reception of the above PDRCH may be based on the payload size of the above PDRCH included in the above TBS information.
[0496] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, and based on the fact that the size of the data to be received by the reader on the above PDRCH is smaller than the payload size of the above PDRCH included in the above TBS information, zero padding may be performed after the data up to the payload size.
[0497] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a first index associated with the TBS table, the ladder can receive the postamble after receiving the PDRCH from the device.
[0498] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a second index associated with the TBS table, the postamble of the PDRCH may not be received after reception.
[0499] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including the second index associated with the TBS table, the reception of the PDRCH may be based on the payload size of the PDRCH included in the TBS information.
[0500] For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be received by the reader on the PDRCH being smaller than or equal to the payload size of the PDRCH included in the TBS information, zero padding may be performed after the data up to the payload size without receiving the postamble. For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be received by the reader on the PDRCH being larger than the payload size of the PDRCH included in the TBS information, the postamble may be received after receiving the PDRCH.
[0501] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a fourth index associated with the TBS table, only control information may be received on the PDRCH without receiving data.
[0502] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (202) of a reader (200) may transmit information for scheduling a PDRCH (physical D2R (device to reader) channel) to a device (for example, the processor (202) of the reader (200) may control a transceiver (206) to transmit information for scheduling a PDRCH (physical D2R (device to reader) channel) to a device). For example, the processor (202) of the reader (200) may receive the PDRCH from the device based on the information for scheduling the PDRCH (for example, the processor (202) of the reader (200) may control a transceiver (206) to receive the PDRCH from the device based on the information for scheduling the PDRCH). For example, the processor (202) of the reader (200) can receive the post-received post-embled of the PDRCH from the device based on the fact that the information for the scheduling of the PDRCH does not include TBS (transport block size) information (for example, the processor (202) of the reader (200) can control the transceiver (206) to receive the post-received post-embled of the PDRCH from the device based on the fact that the information for the scheduling of the PDRCH does not include TBS (transport block size) information).
[0503] According to one embodiment of the present disclosure, a reader may be provided. For example, the reader may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the reader may: transmit information for scheduling a physical D2R (device to reader) channel to a device; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0504] For example, based on the reception of the above postamble, the reception of the above PDRCH may be terminated.
[0505] For example, the above post-ambble may be a D2R post-ambble.
[0506] For example, the information for the scheduling of the above PDRCH can be transmitted via the PRDCH (physical reader to device (R2D) channel).
[0507] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the above postamble may not be received after the above reception of the above PDRCH.
[0508] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the reception of the above PDRCH may be based on the above TBS information.
[0509] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, the reception of the above PDRCH may be based on the payload size of the above PDRCH included in the above TBS information.
[0510] For example, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, and based on the fact that the size of the data to be received by the reader on the above PDRCH is smaller than the payload size of the above PDRCH included in the above TBS information, zero padding may be performed after the data up to the payload size.
[0511] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a first index associated with the TBS table, the ladder can receive the postamble after receiving the PDRCH from the device.
[0512] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a second index associated with the TBS table, the postamble of the PDRCH may not be received after reception.
[0513] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including the second index associated with the TBS table, the reception of the PDRCH may be based on the payload size of the PDRCH included in the TBS information.
[0514] For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be received by the reader on the PDRCH being smaller than or equal to the payload size of the PDRCH included in the TBS information, zero padding may be performed after the data up to the payload size without receiving the postamble. For example, based on the device acquiring the TBS table related to the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index related to the TBS table, and based on the size of the data to be received by the reader on the PDRCH being larger than the payload size of the PDRCH included in the TBS information, the postamble may be received after receiving the PDRCH.
[0515] For example, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a fourth index associated with the TBS table, only control information may be received on the PDRCH without receiving data.
[0516] According to one embodiment of the present disclosure, a processing device (configured to control a reader) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the reader to: transmit information for scheduling a physical D2R (device to reader) channel to a device based on execution by the at least one processor; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the information for scheduling the PDRCH not including transport block size (TBS) information.
[0517] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the reader may: transmit information for scheduling a physical D2R (device to reader) channel (PDRCH) to a device; receive the PDRCH from the device based on the information for scheduling the PDRCH; and receive a postamble of the PDRCH from the device based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.
[0518] According to the present disclosure, the following technical effects can be achieved.
[0519] (1) Clarification of the PDRCH transmission termination indication method
[0520] - Only when TBS information is not included in the PDRCH scheduling information is the device configured to send a postamble after the PDRCH transmission, thereby allowing the reader to clearly recognize the end of the PDRCH transmission solely by the presence or absence of the postamble.
[0521] (2) Improvement in timing acquisition performance on the reader reception side
[0522] Even in the absence of TBS information, since a postamble is explicitly transmitted after the PDRCH, the reader can accurately obtain the PDRCH end time and frame boundaries.
[0523] - It can be particularly advantageous in ultra-low power / low complexity environments such as ambient IoT.
[0524] (3) Prevent unnecessary postamble transmission
[0525] - If TBS information is provided, the reader knows the payload size, so it can determine the end of PDRCH without a postamble.
[0526] - By clearly defining only the opposite case, the present disclosure can provide a basis for distinguishing between cases where postamble transmission is necessary and cases where it is unnecessary.
[0527] (4) Ensure compatibility between Rel-19 / Rel-20 and later
[0528] - It provides control logic that enables the conflict-free coexistence of the Rel-19 method (TBS-based) and the D2R postamble method available from Rel-20 onwards, thereby minimizing design changes for existing devices / readers during the standard evolution process.
[0529] Various embodiments of the present disclosure may be combined with one another. For example, various embodiments of the present disclosure may be combined with one another, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the various embodiments may be omitted.
[0530] The present disclosure describes a 5G wireless communication system as an example. This can be similarly applied and used in 6G wireless communication systems, etc.
[0531] The proposed method above may be applied to the device described below. First, the processor (202) of the receiving terminal may set at least one partial bandwidth (e.g., BWP; bandwidth part). Then, the processor (202) of the receiving terminal may control the transceiver (206) of the receiving terminal to receive a physical channel related to terminal-to-terminal communication (e.g., SL communication) and / or a reference signal related to terminal-to-terminal communication (e.g., SL communication) from the transmitting terminal on at least one partial bandwidth (e.g., BWP).
[0532] The following describes an apparatus to which various embodiments of the present disclosure may be applied.
[0533] Although not limited to, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G, 6G, etc.) between devices.
[0534] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.
[0535] FIG. 18 shows a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.
[0536] Referring to FIG. 18, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution), 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., Advanced Air Mobility). The XR device includes an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.
[0537] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include LTE, NR, and 6G, as well as NB-IoT (Narrowband Internet of Things) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.
[0538] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. Wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
[0539] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR, 6G, etc.), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.
[0540] FIG. 19 shows a wireless device according to one embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.
[0541] Referring to FIG. 19, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 18.
[0542] 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 transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the 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). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0543] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0544] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.
[0545] 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. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.
[0546] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.
[0547] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless 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 wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.
[0548] FIG. 20 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.
[0549] Referring to FIG. 20, 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). Although not limited thereto, the operation / function of FIG. 20 may be performed in the processor (102, 202) and / or transceiver (106, 206) of FIG. 19. The hardware elements of FIG. 20 may be implemented in the processor (102, 202) and / or transceiver (106, 206) of FIG. 19. For example, blocks 1010 through 1060 may be implemented in the processor (102, 202) of FIG. 19. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 19, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 19.
[0550] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 20. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transmission block (e.g., UL-SCH transmission block, DL-SCH transmission block). The wireless signal can be transmitted through various physical channels (e.g., PUSCH, PDSCH).
[0551] Specifically, a codeword can be converted into a scrambled bit sequence by a scrambler (1010). The scrambled sequence used for scrambling is generated based on an initialization value, which may include ID information of a wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by an N*M precoding matrix W. Here, N is the number of antenna ports and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on the complex modulation symbols. Additionally, the precoder (1040) can perform precoding without performing transform precoding.
[0552] A resource mapper (1050) can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource may include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. A signal generator (1060) generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to another device through each antenna. To this end, 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, etc.
[0553] The signal processing process for a received signal in a wireless device can be configured as the inverse of the signal processing process (1010–1060) of FIG. 20. For example, a wireless device (e.g., 100, 200 in FIG. 19) can receive a wireless signal from the outside through an antenna port / transceiver. The received wireless signal can be converted into a baseband signal through a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Subsequently, the baseband signal can be restored into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scrambling process. The codeword can be restored to the original information block through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.
[0554] FIG. 21 illustrates a wireless device according to one embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 18). The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.
[0555] Referring to FIG. 21, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 19 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 19. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 19. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).
[0556] The additional element (140) can be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 18, 100a), a vehicle (Fig. 18, 100b-1, 100b-2), an XR device (Fig. 18, 100c), a portable device (Fig. 18, 100d), a home appliance (Fig. 18, 100e), an IoT device (Fig. 18, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 18, 400), a base station (Fig. 18, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.
[0557] In FIG. 21, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least a portion may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory and / or a combination thereof.
[0558] Hereinafter, an implementation example of FIG. 21 will be described in more detail with reference to the drawings.
[0559] FIG. 22 illustrates a portable device according to one embodiment of the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a portable computer (e.g., a laptop, etc.). The portable 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). The embodiment of FIG. 22 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.
[0560] Referring to FIG. 22, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 to 130 / 140a to 140c each correspond to blocks 110 to 130 / 140 of FIG. 21.
[0561] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control the components of the portable device (100) to perform various operations. The control unit (120) may include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / code / commands required for the operation of the portable device (100). Additionally, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the portable device (100) and may include wired / wireless charging circuits, batteries, etc. The interface unit (140b) can support the connection between the portable device (100) and other external devices. The interface unit (140b) may include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can receive or output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker and / or a haptic module, etc.
[0562] For example, in the case of data communication, the input / output unit (140c) acquires information / signals (e.g., touch, text, voice, image, video) input from the user, and the acquired information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals and can directly transmit the converted wireless signals to another wireless device or to a base station. Additionally, the communication unit (110) can receive wireless signals from another wireless device or base station and then restore the received wireless signals to their original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).
[0563] The claims described in this disclosure may be combined in various ways. For example, the technical features of the method claims of this disclosure may be combined to be implemented as a device, and the technical features of the device claims of this disclosure may be combined to be implemented as a method. Additionally, the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a device, and the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a method.
Claims
In terms of the method, A step in which the device receives information for scheduling a PDRCH (physical D2R (device to reader) channel) from a reader; Based on the information for scheduling the above PDRCH, the device transmits the PDRCH to the reader; and A method comprising the step of the device transmitting a postamble of the PDRCH to the reader based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. In paragraph 1, A method in which the transmission of the PDRCH is terminated based on the transmission of the above postamble. In paragraph 1, The above post-amble is a D2R post-amble, method. In paragraph 1, A method in which the information for the scheduling of the above PDRCH is received through the PRDCH (physical reader to device (R2D) channel). In paragraph 1, A method in which the postamble is not transmitted after the transmission of the PDRCH, based on the fact that the information for scheduling the PDRCH includes the TBS information. In paragraph 5, A method in which the information for scheduling the above PDRCH includes the above TBS information, and the transmission of the above PDRCH is based on the above TBS information. In paragraph 6, A method in which the information for scheduling the above PDRCH includes the above TBS information, and the transmission of the above PDRCH is based on the payload size of the above PDRCH included in the above TBS information. In Paragraph 7, A method in which zero padding is performed after the data up to the payload size, based on the fact that the information for scheduling the above PDRCH includes the above TBS information, and based on the fact that the size of the data to be transmitted by the device on the above PDRCH is smaller than the payload size of the above PDRCH included in the above TBS information. In paragraph 1, A method further comprising the step of the device transmitting the postamble to the reader after the transmission of the PDRCH, based on the device obtaining a TBS table related to the postamble and the TBS information, and based on the information for the scheduling of the PDRCH including a first index related to the TBS table. In Paragraph 9, A method in which a postamble is not transmitted after the transmission of the PDRCH, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a second index associated with the TBS table. In Paragraph 10, A method in which the device obtains the TBS table associated with the postamble and the TBS information, and the information for scheduling the PDRCH includes the second index associated with the TBS table, wherein the transmission of the PDRCH is based on the payload size of the PDRCH included in the TBS information. In Paragraph 11, Based on the device acquiring the TBS table associated with the postamble and the TBS information, based on the information for scheduling the PDRCH including a third index associated with the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being smaller than or equal to the payload size of the PDRCH included in the TBS information, zero padding is performed after the data up to the payload size without transmitting the postamble, and A method in which the postamble is transmitted after the transmission of the PDRCH, based on the device acquiring the TBS table associated with the postamble and the TBS information, based on the information for scheduling the PDRCH including the third index associated with the TBS table, and based on the size of the data to be transmitted by the device on the PDRCH being larger than the payload size of the PDRCH included in the TBS information. In Paragraph 12, A method in which only control information is transmitted without data transmission on the PDRCH, based on the device acquiring the TBS table associated with the postamble and the TBS information, and based on the information for scheduling the PDRCH including a fourth index associated with the TBS table. In the first device, At least one transmitter / receiver; At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Receive information for scheduling the PDRCH (physical D2R (device to reader) channel) from the reader; Based on the information for scheduling the above PDRCH, the reader is instructed to transmit the above PDRCH; and A first device that causes the reader to transmit a postamble after the transmission of the PDRCH, based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. In a processing device, At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Receive information for scheduling the PDRCH (physical D2R (device to reader) channel) from the reader; Based on the information for scheduling the above PDRCH, the reader is instructed to transmit the above PDRCH; and A processing device that causes the reader to transmit a postamble after the transmission of the PDRCH, based on the fact that the information for the scheduling of the PDRCH does not include TBS (transport block size) information. As a non-transient computer-readable storage medium recording instructions, When executed, the above instructions cause the first device: Receive information for scheduling the PDRCH (physical D2R (device to reader) channel) from the reader; Based on the information for scheduling the above PDRCH, the reader is instructed to transmit the above PDRCH; and A non-transient computer-readable storage medium that causes the reader to transmit a postamble after the transmission of the PDRCH, based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. In terms of the method, A step in which the reader transmits information for scheduling the PDRCH (physical D2R (device to reader) channel) to the device; Based on the information for scheduling the above PDRCH, the reader receives the PDRCH from the device; and A method comprising the step of the reader receiving the post-received postamble of the PDRCH from the device, based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. In the second device, At least one transmitter / receiver; At least one processor; and The second device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Instruct the device to transmit information for scheduling the PDRCH (physical D2R (device to reader) channel); Based on the information for scheduling the above PDRCH, the device receives the PDRCH; and A second device that receives a postamble of the PDRCH from the device, based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. In a processing device, At least one processor; and A second device comprising at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Instruct the device to transmit information for scheduling the PDRCH (physical D2R (device to reader) channel); Based on the information for scheduling the above PDRCH, the device receives the PDRCH; and A processing device that receives a postamble of the PDRCH from the device based on the fact that the information for scheduling the PDRCH does not include TBS (transport block size) information. As a non-transient computer-readable storage medium recording instructions, When executed, the above commands cause the second device: Instruct the device to transmit information for scheduling the PDRCH (physical D2R (device to reader) channel); Based on the information for scheduling the above PDRCH, the device receives the PDRCH; and A non-transient computer-readable storage medium that receives a postamble of the PDRCH from the device, based on the fact that the information for scheduling the PDRCH does not include transport block size (TBS) information.