Wireless communication device and communication method

Abstract

This wireless communication device is provided with: a reception unit that receives a signal including control information and data transmitted to the wireless communication device; and a control unit that, after the time required to decode at least a portion of the control information from the end of said portion of the control information has elapsed, applies the portion to at least one operation from among reception, detection, and decoding with respect to the data.

Description

Wireless communication device and communication method

[0001] The present disclosure relates to a wireless communication device and a communication method.

[0002] For NR (New Radio) (also called "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, low power consumption, etc. (see, for example, Non-Patent Document 1).

[0003] Furthermore, in Release 18 (Rel-18) of 3GPP (registered trademark), ambient IoT (A-IoT: Ambient Internet of Things) is being considered (see, for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations for low-end IoT applications that operate with extremely low power consumption.

[0004] 3GPP TS 38.300 V17.3.0 (2022-12)”Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 20233GPP TR 38.848 V1.0.0 (2023-09)3GPP TS 36.211 V16.8.0 (2023-09)”Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] In a communication system including an ambient IoT device, synchronization accuracy in the time and frequency domains is low. To compensate for this, it is assumed that at least a preamble (and even a midamble and / or a postamble) is added to control information and / or data before transmission and reception. Furthermore, it is assumed that the ambient IoT device (or intermediate node) receives / detects / decodes data based on the control information. However, if the control information does not properly indicate or notify information for receiving / detecting / decoding data, wireless communication devices such as the ambient IoT device and the intermediate node may not be able to properly receive / detect / decode data, which may result in degradation of system performance.

[0006] In view of the above, one aspect of the present disclosure provides a wireless communication device and a communication method that can appropriately receive, detect, and / or decode data based on control information.

[0007] A wireless communication device according to one aspect of the present disclosure includes a receiving unit that receives a signal including control information and data transmitted to the wireless communication device, and a control unit that applies the portion to at least one of receiving, detecting, and decoding the data after a time required to decode at least a portion of the control information has elapsed from the end of at least a portion of the control information.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL assistance. FIG. 3 is a diagram illustrating Topology 3 in UL assistance. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in Topology 1. FIG. 7 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in Topology 2. FIG. 8 is a diagram illustrating an example of a configuration of a preamble, control / data, and midamble used in R2D / D2R transmission. FIG. 9 is a diagram illustrating an example of a configuration of a control / data and postamble used in R2D / D2R transmission. FIG. 10 is a diagram illustrating an example of a relationship between control information and data included in a single R2D transmission to an A-IoT device. FIG. 11 is a diagram illustrating an example of a relationship between reception / decoding of control information and reception / decoding of data included in a single R2D transmission to an A-IoT device. FIG. 12 is a diagram illustrating an example of an R2D transmission according to Proposal 2. FIG. 13 is a diagram illustrating an example of an R2D transmission according to Proposal 3'. FIG. 14 is a diagram illustrating an example of an R2D transmission according to Proposal 4. FIG. 1 is a diagram illustrating an example of R2D transmission according to proposal 5. FIG. 2 is a diagram illustrating an example of operation of a wireless communication device according to an embodiment of the present disclosure. FIG. 3 is a block diagram illustrating an example of the configuration of a base station according to an embodiment of the present disclosure. FIG. 4 is a block diagram illustrating an example of the configuration of a device according to an embodiment of the present disclosure. FIG. 5 is a diagram illustrating an example of the hardware configuration of a base station and a device according to an embodiment of the present disclosure. FIG. 6 is a diagram illustrating an example of the configuration of a vehicle according to an embodiment of the present disclosure.

[0009] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present disclosure is applied is not limited to the following embodiment.

[0010] In the operation of the wireless communication system according to the embodiment of the present disclosure, existing technology is used as appropriate. The existing technology is, for example, the existing LTE or NR, but is not limited to the existing LTE or NR. In addition, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced, unless otherwise specified.

[0011] In addition, in the embodiments of the present disclosure described below, terms such as SS (synchronization signal), PSS (primary SS), SSS (secondary SS), PBCH (physical broadcast channel), PRACH (physical random access channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), and PUSCH (physical uplink shared channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0012] Furthermore, in the embodiments of the present disclosure, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0013] Furthermore, in the embodiments of the present disclosure, "configuring" radio parameters, etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station, a device, a terminal, etc. are set.

[0014] (Embodiment) <Wireless Communication System> FIG. 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. As illustrated in FIG. 1, the wireless communication system 1 includes a base station 10 and a device 20. While FIG. 1 illustrates one base station 10 and one device 20, this is merely an example, and multiple base stations and devices may exist. The base station may also be referred to as a BS (Base Station), gNB, or the like. The device 20 may be a form of terminal (UE: User Equipment) and may be an ambient IoT device, which is a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device. The ambient IoT device may also be referred to as an ambient IoT terminal, ambient IoT UE, or the like.

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the device 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols. The frequency domain may be defined by the number of subcarriers or the number of resource blocks (RBs).

[0016] The base station 10 transmits DL signals such as control information, setting information, and data via DL (Downlink) to the device 20. The base station 10 receives UL signals such as control information, information related to the processing capability of the device 20 (device capability (information) or A-IoT capability (information); for example, capability, device capability, A-IoT capability, A-IoT device capability, etc.), and data via UP (Uplink) from the device 20.

[0017] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the base station 10 transmits control information to the device 20 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel or a data channel, and the PDCCH is an example of a downlink control channel. The PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.

[0018] As will be described later, the wireless communication system may include intermediate nodes, assisting nodes, and / or terminals (UEs) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be written simply as " / ".

[0019] The device 20 is a communication device equipped with a wireless communication function, and may be an ambient IoT device (e.g., a sensor, etc.) as described above. Hereinafter, the ambient IoT device will also be referred to as an A-IoT UE.

[0020] The device 20 receives DL signals such as control signals, setting information, and data from the base station 10 via DL, and transmits UL signals such as control signals, capability information of the device 20, and data to the base station 10 via UL.

[0021] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a physical uplink shared channel (PUSCH), and the control channel may include a physical uplink control channel (PUCCH). For example, the device 20 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel or a data channel, and the PUCCH is an example of an uplink control channel. Note that the PUSCH or the PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or the PUCCH.

[0022] <Ambient IoT> Rel-18 approved the study of ambient IoT, which is even lower-end than the existing NB-IoT (see, for example, Section 10 of Non-Patent Document 4) (see, for example, Non-Patent Document 2). Ambient IoT targets ultra-low power consumption and ultra-low complexity devices.

[0023] In Ambient IoT, for example, the following deployment scenarios and characteristics may be considered for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment Connectivity topology, e.g., which nodes communicate with Ambient IoT devices, such as base stations, terminals (UE), relays and repeaters Duplexing method, TDD or FDD, licensed or unlicensed frequency band Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies Assumptions of traffic originating from / terminating to devices

[0024] Based on the above deployment scenarios and characteristics, for example, the following RAN design targets can be formulated: Power consumption Complexity Coverage Data rate Positioning accuracy

[0025] Based on deployment scenarios appropriate for the relevant use cases, compare and evaluate the feasibility of meeting design targets and identify supporting features.

[0026] <Device Types and Topologies> Based on the results of the study items, TR 38.848 (Non-Patent Document 3) was approved. TR 38.848 considers the following categories of ambient IoT devices: Device A: Device A has no power (energy) storage, no independent signal generation or signal amplification functions, and performs backscattering transmission. Device B: Device B has power storage, no independent signal generation function, and performs backscattering transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, independent signal generation function, and an active RF (radio frequency) component for transmission.

[0027] The complexity of device A is assumed to be about the same as RFID (Frequency Frequency Identification).

[0028] TR 38.848 defines the following topologies 1 to 4 in an ambient IoT network.

[0029] Fig. 2 is a diagram illustrating Topology 1. As shown in Fig. 2, Topology 1 is a configuration in which a base station (BS) and an ambient IoT device communicate with each other. The ambient IoT device directly communicates with the base station in a two-way manner.

[0030] 3 is a diagram illustrating Topology 2. As shown in FIG. 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate with each other via an intermediate node. The ambient IoT device performs bidirectional communication with the intermediate node located between the base station and the ambient IoT device. The intermediate node may be, for example, a relay, an integrated access and backhaul (IAB) node, a UE, a repeater, or the like.

[0031] 4 is a diagram illustrating Topology 3 in DL assistance. As shown in FIG. 4, Topology 3 is a configuration including communication between a base station and an assisting node, communication between the assisting node and an ambient IoT device, and communication between the ambient IoT device and a base station.

[0032] The support node supports DL communication. For example, as shown in Figure 4, the support node receives DL signals from the base station and transmits the received DL signals to the ambient IoT device. For UL communication, the ambient IoT device transmits UL signals directly to the base station.

[0033] Fig. 5 is a diagram illustrating Topology 3 in UL support. As shown in Fig. 5, Topology 3 is a configuration including communication between a base station and a support node, communication between a support node and an ambient IoT device, and communication between the ambient IoT device and a base station.

[0034] The support node supports UL communication. For example, as shown in Figure 5, the support node receives UL signals from the ambient IoT device and transmits the received UL signals to the base station. For DL ​​communication, the ambient IoT device receives DL signals directly from the base station.

[0035] The supporting nodes shown in FIGS. 4 and 5 may be, for example, relays, IAB nodes, UEs, repeaters, etc.

[0036] 6 is a diagram illustrating Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device performs bidirectional communication with the UE. Communication related to Topology 4 may be considered as side link (SL) communication.

[0037] In the above topologies 1 to 4, the ambient IoT device may be provided with a carrier wave from another node inside or outside the topology (see Section 4.2.1 of Non-Patent Document 3).

[0038] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE of Topology 4) in addition to the device 20. In this specification, the base station, the support node, the intermediate node, and the terminal may be read as a network or a (network) node. Also, an A-IoT device may be simply referred to as A-IoT.

[0039] Backscatter Transmission Base stations, intermediate nodes, support nodes, and other nodes transmit RF signals to ambient IoT devices that are activated and obtain power from the RF operating fields from the base stations, intermediate nodes, support nodes, and other nodes via inductive coupling.

[0040] The ambient IoT device backscatters and modulates the RF signals received from the base station, intermediate node, support node, and other nodes by switching the reflection coefficient of the device's antenna, and transmits information to the base station, intermediate node, support node, and other nodes.

[0041] FIG. 7 is a diagram illustrating backscatter transmission. In FIG. 7, an example is shown in which an ambient IoT device transmits information using ON-OFF keying (OOK). The dashed line area in FIG. 7 indicates an OFF section, which may correspond to information (bit) "0." A sinusoidal signal may correspond to information "1."

[0042] <Rel-19 SID> The Rel-19 SID (Study Item Description) examined solutions necessary and feasible for A-IoT (see Section 4.1 of Non-Patent Document 5). The examined solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

[0043] Additionally, for the DL and UL of A-IoT, several issues will be discussed under the leadership of RAN 1. One of the issues to be discussed is the scheduling and timing relationship between DL and UL in A-IoT. In discussing the scheduling and timing relationship, the following 1. traffic flow, 2. device assumptions, and 3. topology may be considered.

[0044] 1. Traffic Flow The following DT and DO-DTT are being considered as traffic flows for A-IoT.

[0045] DT (device terminated) Traffic includes transmission (DL) to the A-IoT UE, but no transmission (UL) from the A-IoT UE. In other words, there is information to be transmitted to the A-IoT UE, but no information to be transmitted from the A-IoT UE. DT corresponds to a command type in which there is an instruction such as a command or instruction to the A-IoT UE.

[0046] DO-DTT (device originated - device terminated triggered) Traffic includes a trigger from the network (NW) and a transmission (UL) from the A-IoT UE. In other words, traffic includes information transmitted from the A-IoT UE. DO-DTT corresponds to, for example, a sensor information report type in which the A-IoT UE transmits sensor information collected by the A-IoT UE.

[0047] In this disclosure, transmission of information corresponds to transmission of a signal containing information or transmission of a signal. In this disclosure, transmission to a certain device X corresponds to transmission of a signal (or information) to device X. In addition, transmission from a certain device X and transmission by a certain device X correspond to device X transmitting a signal (or information). In addition, reception from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, reception by a certain device X corresponds to device X receiving a signal (or information).

[0048] 2. Device Assumptions The following TX (transmission) and FR (frequency range) 1-FDD are assumed for A-IoT UE.

[0049] TX TX is a backscatter UL transmission without amplification or a general amplified UL transmission. Alternatively, an amplified backscatter UL transmission may be performed.

[0050] FR1-FDD FR1-FDD is applied to the A-IoT UE. That is, the A-IoT UE can switch carrier frequencies between DL carriers and UL carriers. However, the present disclosure is not limited to FR1-FDD and may be applied to TDD, FR2, or FR3.

[0051] The frequency bands of each FR are, for example, as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz FR3: 7.125 GHz to 24.25 GHz

[0052] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0053] 3. Topology Among the topologies shown in FIGS. 2 to 6, attention is focused on Topology 1 and Topology 2.

[0054] In Topology 1, UL and / or DL ​​communication is performed between a base station and an A-IoT UE without passing through an intermediate node. Note that the base station in Topology 1 may correspond to a microcell.

[0055] In Topology 2, communication is performed between a base station and an A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with an intermediate node located between the base station and the A-IoT UE. Note that the base station in the case of Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as an intermediate UE, int. UE (intermediate UE), etc.

[0056] <Device Types> The following three device types, Device 1, Device 2a, and Device 2b, are defined for A-IoT devices.

[0057] Device 1 (may be referred to as Type 1) Device 1 is a device type that consumes a peak power of 1 μW or less. Device 1 has energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million) (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Device 1 does not have any amplification in either DL or UL. UL transmission in Device 1 is performed by backscattering an externally provided carrier wave (CW), i.e., an unmodulated wave.

[0058] Device 2a (may be referred to as type 2a) Device 2a is a device type that consumes a peak power of several hundred μW. Device 2a has energy storage and has an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Furthermore, DL and / or UL amplification is performed in device 2a. UL transmission in device 2a is performed by backscattering in CW provided from an external device.

[0059] Device 2b (may be referred to as type 2b) Device 2b is a device type that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Furthermore, DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed inside device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering in CW provided from an external source.

[0060] <Candidate Topologies> Next, candidate topologies for CW / R2D / D2R transmission will be described.

[0061] Fig. 8 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. Fig. 8 shows Topology 1A, Topology 1B, Topology 1C, Topology 1D, and Topology 1E as examples of candidate topologies.

[0062] As shown in FIG. 8, in topologies 1A to 1E, CW / R2D communication signals (sometimes referred to as "R2D" in FIG. 8 and below) / D2R communication signals (sometimes referred to as "D2R" in FIG. 8 and below) can be transmitted and received to A-IoT devices.

[0063] In this embodiment, DL and R2D (reader to device) may be interchangeable, and UL and D2R (device to reader) may be interchangeable. Here, reader corresponds to a BS and / or an intermediate UE, and device corresponds to an A-IoT device. That is, in the embodiments of the present disclosure, "base station" may be interchangeable with "reader," and device does not need to identify the type of reader.

[0064] In Topology 1A, the node (first BS) that transmits the CW is different from the node (second BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0065] In Topology 1B, the node (BS) that transmits the CW, the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0066] In topology 1C, the node that transmits the CW (CW node) is different from the node that transmits the R2D communication signal (BS). Also, in topology 1C, the node that transmits the CW is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in topology 1C, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR (network-controlled repeater) node / relay node / other type of node.

[0067] In Topology 1D, the node (BS) that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication generated and transmitted by the A-IoT device, i.e., R in R2D and R in D2R are the same.

[0068] In Topology 1E, the node (first BS) that transmits the R2D communication signal is different from the node (second BS) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, the R in R2D is different from the R in D2R.

[0069] Fig. 9 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 2. Fig. 9 shows Topology 2A, Topology 2B, Topology 2C, Topology 2D, and Topology 2E as examples of candidate topologies.

[0070] As shown in Figure 9, in topologies 2A to 2E, CW / R2D communication signals (denoted as "R2D" in Figure 9) / D2R communication signals (denoted as "D2R" in Figure 9) can be sent and received to A-IoT devices.

[0071] In Topology 2A, the node (first intermediate UE) that transmits the CW is different from the node (second intermediate UE) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0072] In Topology 2B, the node that transmits the CW (intermediate UE), the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0073] In Topology 2C, the node that transmits the CW (CW node) is different from the node that transmits the R2D communication signal (intermediate UE). Also, in Topology 1C, the node that transmits the CW is different from the node (BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering. Also, in Topology 1C, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR node / relay node / other type of node.

[0074] In Topology 2D, the node (intermediate UE) that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication generated and transmitted by the A-IoT device, i.e., R in R2D and R in D2R are the same.

[0075] In Topology 2E, the node (first intermediate UE) that transmits the R2D communication signal is different from the node (second intermediate UE) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is different from R in D2R.

[0076] <Timing acquisition in R2D / D2R transmission> In a communication system including A-IoT devices, the above-mentioned candidate topologies are possible, and R2D communication signals (hereinafter simply referred to as "R2D") and D2R communication signals (hereinafter simply referred to as "D2R") are transmitted and received.

[0077] It has been agreed to consider a timing acquisition signal for such R2D / D2R transmissions. Note that timing acquisition may be replaced with (time) synchronization. Hereinafter, the timing acquisition signal for R2D will be referred to as the R2D timing acquisition signal, and the timing acquisition signal for D2R will be referred to as the D2R timing acquisition signal.

[0078] For R2D transmissions, it has been agreed that an R2D timing acquisition signal will be included in the R2D for at least timing acquisition purposes and to indicate the beginning (or start or beginning or start timing) of the R2D transmission in the time domain, where the R2D timing acquisition signal may be, for example, an R2D preamble.

[0079] For D2R transmissions, it has been agreed that a D2R timing acquisition signal is included in the D2R at least for timing acquisition purposes and to indicate the beginning of the D2R transmission in the time domain, where the D2R timing acquisition signal may be, for example, a D2R preamble.

[0080] As shown in Figure 10, the R2D preamble may be placed temporally before the R2D control / data, and the D2R preamble may be placed temporally before the D2R control / data. Note that in this specification and drawings, control information and / or data (information) may be abbreviated and referred to as control / data.

[0081] As described above, A-IoT devices are expected to be devices with extremely simple configurations for low-end IoT applications that operate with extremely low power consumption, and therefore may not have a time synchronization function. In this case, the timing, i.e., synchronization, acquired by the R2D preamble or D2R preamble may be lost during communication, making it impossible to properly execute communication. Therefore, in addition to the preamble, a midamble is also being considered for timing acquisition. That is, in consideration of cases where the timing acquired from the preamble cannot be accurately maintained until the end (or termination, end point, or end timing) of the R2D / D2R transmission, a midamble may be used for timing acquisition. As shown in FIG. 10 , the R2D midamble may need to be placed in the middle of the R2D control / data transmission, and the D2R midamble may need to be placed in the middle of the D2R control / data transmission. The R2D midamble may also be referred to as a timing acquisition signal, an additional timing acquisition signal, an R2D timing acquisition signal, an additional R2D timing acquisition signal, etc. The D2R midamble may be referred to as a timing acquisition signal, an additional timing acquisition signal, a D2R timing acquisition signal, an additional D2R timing acquisition signal, etc.

[0082] Postambles are also considered. Postambles may be used to signal the end of R2D / D2R transmissions in the time domain. As shown in Figure 11, the R2D postamble may be located at the end of the R2D control / data transmission (after the last R2D control / data in time), and the D2R postamble may be located at the end of the R2D control / data transmission (after the last D2R control / data in time). The preamble, midamble, and postamble may be referred to as timing acquisition signals, timing acquisition information, etc.

[0083] As described above, R2D transmission may be composed of at least one of an R2D preamble (hereinafter also simply referred to as a preamble), R2D control information (hereinafter also simply referred to as control information), data (hereinafter also simply referred to as data), other synchronization signals (e.g., midamble, postamble, etc.), etc. The control information and data are transmitted from the base station to the A-IoT device via a PRDCH (a channel for R2D transmission). Note that the PRDCH carrying the control information and the PRDCH carrying the data may be the same (e.g., a joint PRDCH) or may be separate PRDCHs, but this point is not currently clarified.

[0084] FIG. 12 is a diagram showing an example of the relationship between control information and data included in a single R2D transmission to an A-IoT device. In FIG. 12, the single R2D transmission does not include a midamble or a postamble. It is assumed that the A-IoT device receives / detects / decodes subsequent data based on the control information following the preamble in the R2D transmission. Therefore, as shown in FIG. 12, the control information may notify (or instruct) the A-IoT device of information for the A-IoT device to receive / detect / decode data. That is, the control information may include such information or notification (or instruction).

[0085] <Analysis> In order for the A-IoT device to receive / detect / decode the data in the R2D transmission, processing time is required on the A-IoT device side to obtain notification from the control information following the preamble.

[0086] FIG. 13 is a diagram showing an example of the relationship between the reception / decoding of control information and the reception / decoding of data included in a single R2D transmission to an A-IoT device. Here, as shown in FIG. 13, after (transmission / reception of) the control information, it is assumed that time T is required to decode such information or notification. Note that time T may be interpreted as corresponding to the processing time described above. As shown in FIG. 13, when the control information and data are continuous in the time domain, the reception / decoding of data and the decoding of the above-mentioned information or notification overlap. Therefore, if the data reception / detection / decoding timing begins before the decoding of the above-mentioned information or notification is completed (in other words, before time T has elapsed from the end of the control information), there is a possibility that the information or notification for receiving / detecting / decoding the data may not be decoded, and therefore data reception / detection / decoding may not be performed properly. In this way, if the control information does not properly notify the information for receiving / detecting / decoding the data, the A-IoT device may not be able to properly receive / detect / decode the data, which may result in degradation of system performance. Note that the same problems as with A-IoT devices may also occur with intermediate UEs. The A-IoT device and the intermediate UE may also be referred to as wireless communication devices.

[0087] Therefore, below we will describe proposals (Proposal 1, Proposal 2, Proposal 3, Proposal 3', Proposal 4 and Proposal 5) for properly receiving / detecting / decoding R2D data based on R2D control information in R2D transmission in a communication system including A-IoT devices.

[0088] The matters explained in the following Proposal 1, Proposal 2, Proposal 3, Proposal 3', Proposal 4 and Proposal 5 may be combined as appropriate as long as no contradiction occurs.

[0089] Proposal 1, Proposal 2, Proposal 3, Proposal 3', Proposal 4, and Proposal 5 are described assuming R2D transmission in Topology 1, but may also be applied to Topology 2 in which an intermediate UE is interposed between a base station and an A-IoT device. That is, in Proposal 1, Proposal 2, Proposal 3A, Proposal 3B, Proposal 4, and Proposal 5, the base station may be read as an intermediate UE, and the device may be read as an intermediate UE.

[0090] Proposal 1, Proposal 2, Proposal 3A, Proposal 3′, Proposal 4 and Proposal 5 are described assuming R2D transmission in Topology 1, but may also be applied to D2R transmission.

[0091] In the following, "R2D control / data" and "R2D control / data transmission" may be interchangeable.

[0092] Hereinafter, "R2D / D2R transmission" may be referred to as communication in a wireless communication system including an A-IoT device, communication of an A-IoT device, communication with an A-IoT device, communication involving an A-IoT device, etc.

[0093] In the following, the PRDCH on which the R2D control information is carried and the PRDCH on which the R2D data is carried may be either together (e.g., a joint PRDCH or a joint channel) or separate (e.g., separate PRDCHs or separate channels).

[0094] Hereinafter, "chip" may refer to the ON and OFF periods (or OFF and ON periods) of an OOK (modulation) symbol. Alternatively, "chip" may refer to the ON or OFF period of an OOK (modulation) symbol. For example, "chip" may refer to the period of an OOK (modulation) symbol representing one bit, or half of that period.

[0095] <Proposal 1> First, proposal 1 regarding control information included in R2D transmission will be described.

[0096] The control information may include control information (referred to as control information X) corresponding to or necessary for data reception / detection / decoding, i.e., control information X for the A-IoT device to receive / detect / decode data. Note that information included in the control information other than the control information X is also referred to as remaining control information (or simply "remaining"). Note that the control information X may mean control information required for the A-IoT device to start receiving / detecting / decoding data. Furthermore, a CRC may be assigned separately to the control information X and the remaining information, and / or a CRC may be assigned collectively.

[0097] The control information X may include at least one of the following: (information indicating) a modulation scheme (information indicating) a modulation order (information indicating) a coding scheme (information indicating) a repetition-related information (e.g., (information indicating) a repetition unit, a repetition factor (coefficient), etc.) (information indicating) a chip length or chip duration (information indicating) a midamble-related information (e.g., (information indicating) a position, a sequence, etc.) (information indicating) a time domain information (e.g., (information indicating) a data length, etc.) (frequency / code domain information) (destination ID) (e.g., a device ID, a device group ID, a device type, a cast type, etc.) (information indicating) a length or duration of control information including the control information X (e.g., the number of chips, the number of OOK modulation symbols, etc.)

[0098] The control information X may include identification information or an index that identifies two or more of the above. For example, a correspondence relationship (e.g., a correspondence relationship in a table format) between two or more of the above and the identification information or an index that identifies the two or more may be defined in a specification, and one identification information or index may be set / notified (transmitted) to the A-IoT device by a base station, an intermediate UE, or the like in RRC / MAC CE / DCI. The A-IoT device may determine a modulation method, etc., based on the received identification information or index.

[0099] On the other hand, the control information X does not have to include, for example, a TBS (Transport Block Size), a reader ID, etc. For example, the remaining control information may include the TBS, the reader ID, etc.

[0100] As described above, the A-IoT device may receive / detect / decode control information including control information X from the base station, and may receive / detect / decode data from the base station based on the received / detected / decoded control information, for example, may start receiving / detecting / decoding data from the base station. Similarly, hereinafter, "receive / detect / decode" may be replaced with "start receiving / detecting / decoding."

[0101] <Proposal 2> Next, Proposal 2, which relates to mapping control information X before R2D control information transmission, will be described.

[0102] The control information X may be mapped at least a time T before (earlier in time) the beginning or start of the R2D data transmission. The A-IoT device may receive, from the base station, control information X (including control information, R2D including preamble, data, etc.) mapped at least a time T before the beginning of the R2D data transmission. Note that the time T may refer to the time required to decode the control information X, or may refer to its maximum value.

[0103] FIG. 14 is a diagram showing an example of R2D transmission according to Proposal 2. As shown in FIG. 14, the R2D control information includes control information X and the remaining control information, and the control information X may be mapped at least a time T before the beginning of the R2D data transmission. In other words, the end (or termination) of the control information X and the beginning of the data may be separated by at least a time T in the time domain. Also, as shown in FIG. 14, the control information X (notification for receiving / detecting / decoding the R2D data) may be used or applied from the beginning of the R2D data transmission. Also, as shown in FIG. 14, for example, the control information X may be a chip length. The R2D control information transmission and the R2D data transmission may be consecutive in the time domain. The A-IoT device may determine the beginning of the R2D data transmission based on the control information X (for example, based on (information indicating) the length of the control information including the control information X).

[0104] For example, T may be a specified value (e.g., specified in a specification), a fixed value, or a preset value. The base station and the A-IoT device may determine (the value of) T as a specified, fixed, or preset value.

[0105] Also, for example, T may depend on one or more of a device type, a message type, a (message) size of control information, a traffic type, a cast type, a PRDCH format, etc. The base station and the A-IoT device may determine (the value of) T according to one or more of a device type, a message type, a size of control information, a traffic type, a cast type, a PRDCH format, etc.

[0106] As described above, the base station may map the control information X at least a time T before the beginning or start of the R2D data transmission and perform R2D transmission to the A-IoT device. The A-IoT device may receive / detect / decode control information from the base station, including control information X mapped at least a time T before the beginning or start of the R2D data transmission, and receive / detect / decode the R2D data from the base station based on the received / detected / decoded control information. For example, the A-IoT device may receive a signal including control information and data transmitted to the A-IoT device, and may apply a portion of the control information from the beginning of the data to receive / detect / decode the R2D data after the time required to decode the portion of the control information has elapsed from the end of the portion of the control information (control information X).

[0107] According to Proposal 2, the A-IoT device can appropriately receive / detect / decode R2D data based on the control information X, taking into account the time required to decode the control information X.

[0108] <Proposal 3> Next, proposal 3 will be described, which relates to the use or application of control information X from the middle of R2D data transmission.

[0109] FIG. 15 is a diagram showing an example of R2D transmission according to Proposal 3. As shown in FIG. 15, the R2D control information includes control information X and the remaining control information. Unlike the example shown in FIG. 14, in Proposal 3, the control information X does not need to be mapped at least time T before the start of the R2D data transmission. Instead, as described above, the control information X may be used or applied midway through the R2D data transmission (time T after the start of the R2D data transmission). Also, as shown in FIG. 15, for example, the control information X may be chip-length. Note that the R2D control information transmission and the R2D data transmission may be continuous in the time domain. The A-IoT device may determine the start of the R2D data transmission not based on the notification content of the control information X (for example, based on information indicating the length of the control information). Also, the time T may refer to the time required to decode the control information, or may refer to its maximum value.

[0110] [Proposal 3a] Instead of the control information X, a parameter (prescribed parameter) of a specified value (e.g., specified in a specification), a parameter of a fixed value (fixed parameter), a parameter of a preset value (prescribed parameter), or a parameter (past parameter) related to an R2D transmission or D2R transmission prior to the R2D transmission may be used or applied until or before the time T has elapsed from the beginning of the R2D data transmission. The default chip length shown in FIG. 15 is an example of a specified parameter, fixed parameter, preset parameter, or past parameter. The A-IoT device may receive / detect / decode R2D data until or before the time T has elapsed from the beginning of the R2D data transmission based on the specified parameter, fixed parameter, preset parameter, or past parameter.

[0111] [Proposal 3b] The same parameters as for the R2D preamble transmission and / or control information transmission (e.g., a chip length corresponding to the default chip length shown in Figure 15) may be used or applied until or before the time T has elapsed from the beginning of the R2D data transmission. The A-IoT device may receive / detect / decode the R2D data until or before the time T has elapsed from the beginning of the R2D data transmission based on the same parameters as for the R2D preamble transmission and / or control information transmission.

[0112] [Proposal 3c] The A-IoT device may assume that there is no midamble (in the R2D transmission) until or before time T has elapsed from the beginning of the R2D data transmission (in other words, it may not assume that there is a midamble).

[0113] [Proposal 3d] When a time T has elapsed from the beginning of R2D data transmission, a synchronization signal (e.g., a sequence signal, a signal identical to the preamble / midamble / postamble, etc.) may be transmitted from the base station to the A-IoT device. Note that the synchronization signal may be based on, for example, control information X.

[0114] [Proposal 3e] For example, T may be a specified value (e.g., specified in a specification), a fixed value, or a preset value. The base station and the A-IoT device may determine (the value of) T as a specified, fixed, or preset value.

[0115] Also, for example, T may depend on one or more of a device type, a message type, a (message) size of control information, a traffic type, a cast type, a PRDCH format, etc. The base station and the A-IoT device may determine (the value of) T according to one or more of a device type, a message type, a size of control information, a traffic type, a cast type, a PRDCH format, etc.

[0116] As described above, the base station may transmit an R2D including control information including control information X and data to the A-IoT device. The A-IoT device may receive / detect / decode control information including control information X from the base station, and receive / detect / decode R2D data from the base station based on the received / detected / decoded control information. For example, the A-IoT device may receive a signal including control information and data transmitted to the A-IoT device, and may apply part of the control information (control information X) from the middle of the data to receive / detect / decode R2D data after the time required to decode the control information has elapsed from the end of the control information.

[0117] According to Proposal 3, the A-IoT device can properly receive / detect / decode the R2D data based on the control information X, taking into account the time required to decode the control information.

[0118] <Proposal 3'> Next, we will explain Proposal 3', which relates to dividing the R2D data into multiple parts or segments and using or applying control information X midway through the R2D data transmission. Proposal 3' may be positioned as a variation of Proposal 3.

[0119] FIG. 16 is a diagram illustrating an example of R2D transmission according to Proposal 3′. As illustrated in FIG. 16, the R2D control information includes control information X and the remaining control information, and the data includes the first to nth segments (n=4 in the illustrated example). It goes without saying that n is not limited to 4 and may be 2 or greater. Unlike the example illustrated in FIG. 14, in Proposal 3′, the control information X does not need to be mapped at least a time T before the beginning of the R2D data transmission. Instead, as described above, the control information X may be used or applied from the middle of the R2D data transmission (the first segment after the time T has elapsed from the beginning of the R2D data transmission; hereinafter, referred to as the kth segment, where k=2 in the illustrated example). Furthermore, as illustrated in FIG. 16, for example, the control information X may be chip-length. Note that the R2D control information transmission and the R2D data transmission may be continuous in the time domain. The A-IoT device may determine the beginning of the R2D data transmission not based on the notification content of the control information X (for example, based on (information indicating) the length of the control information). Furthermore, the time T may mean the time required to decode the control information, or may mean its maximum value.

[0120] [Proposal 3'a] Instead of the control information X, similar to Proposal 3a, a parameter (prescribed parameter) of a specified value (e.g., specified in a specification), a parameter (fixed parameter), a parameter of a fixed value (fixed parameter), a parameter of a preset value (preset parameter), or a parameter (past parameter) related to an R2D transmission or D2R transmission prior to the R2D transmission may be used or applied from the beginning (first segment) of the R2D data transmission to the k-1th segment. The default chip length shown in FIG. 16 is an example of a specified parameter, fixed parameter, preset parameter, or past parameter. The A-IoT device may receive / detect / decode R2D data from the beginning of the R2D data transmission to the k-1th segment based on the specified parameter, fixed parameter, preset parameter, or past parameter.

[0121] [Proposal 3'b] The same parameters as those for the R2D preamble transmission and / or control information transmission (e.g., chip length corresponding to the default chip length shown in FIG. 15) may be used or applied from the beginning (first segment) to the k-1th segment of the R2D data transmission. The A-IoT device may receive / detect / decode the R2D data from the beginning to the k-1th segment of the R2D data transmission based on the same parameters as those for the R2D preamble transmission and / or control information transmission.

[0122] [Proposal 3'c] The A-IoT device may assume that there is no midamble (in the R2D transmission) from the beginning (first segment) of the R2D data transmission to the k-1th segment (i.e., from the first segment to the k-1th segment) (in other words, it may not assume that there is a midamble).

[0123] [Proposal 3'd] At the boundary between the k-1th segment and the kth segment, a synchronization signal (e.g., a sequence signal, a signal identical to the preamble / midamble / postamble, etc.) may be transmitted from the base station to the A-IoT device. Note that the synchronization signal may be based on, for example, control information X.

[0124] [Proposal 3′e] For example, T may be a specified value (e.g., specified in a specification), a fixed value, or a preset value. The base station and the A-IoT device may determine (the value of) T as a specified, fixed, or preset value.

[0125] Also, for example, T may depend on one or more of a device type, a message type, a (message) size of control information, a traffic type, a cast type, a PRDCH format, etc. The base station and the A-IoT device may determine (the value of) T according to one or more of a device type, a message type, a size of control information, a traffic type, a cast type, a PRDCH format, etc.

[0126] [Proposal 3'f] For example, a "segment" may be (every) N chips / (every) N bits / (every) N repetitions / (every) N symbols, etc. (N is an integer equal to or greater than 1). N may be specified in a specification, or may be set / notified (transmitted) to an A-IoT device by a base station, an intermediate UE, etc., in RRC / MAC CE / DCI.

[0127] As described above, the base station may transmit an R2D including control information including control information X and data to the A-IoT device. The A-IoT device may receive / detect / decode control information including control information X from the base station, and receive / detect / decode R2D data from the base station based on the received / detected / decoded control information. For example, the A-IoT device may receive a signal including control information and data transmitted to the A-IoT device, and may perform reception / detection / decoding by applying a portion of the control information (control information X) from the first segment of the multiple segments constituting the data after the time required to decode the control information has elapsed from the end of the control information to the R2D data.

[0128] According to Proposal 3′, the A-IoT device can properly receive / detect / decode the R2D data based on the control information X, taking into account the time required to decode the control information.

[0129] <Proposal 4> Next, Proposal 4 will be described, which relates to ensuring or guaranteeing a time gap between R2D control information transmission and corresponding R2D data transmission.

[0130] FIG. 17 is a diagram showing an example of R2D transmission according to Proposal 4. As shown in FIG. 17, the R2D control information includes control information X and the remaining control information. Unlike the example shown in FIG. 14, in Proposal 4, the control information X does not need to be mapped at least time T ahead of the start of the R2D data transmission. Instead, as described above, a time gap T_gap may be secured or guaranteed between the R2D control information transmission and the corresponding R2D data transmission. The R2D control information transmission and the R2D data transmission do not need to be continuous in the time domain. Also, as shown in FIG. 17, for example, the control information X may be chip-length. The A-IoT device may determine the start of the R2D data transmission based on the time gap T_gap and / or the control information X (e.g., based on information indicating the time gap T_gap and / or the length of the control information including the control information X). The time gap T_gap may correspond to the time T described above. In other words, the time gap T_gap may refer to the time required to decode the control information.

[0131] [Proposal 4a] R2D transmission may not occur within the time gap T_gap. The A-IoT device may assume that no R2D transmission occurs (no R2D transmission is received) within the time gap T_gap (it may not assume that an R2D transmission occurs (receives an R2D transmission)).

[0132] [Proposal 4b] During the time gap T_gap, a synchronization signal (e.g., a sequence signal, a signal identical to the preamble / midamble / postamble, etc.) may be transmitted from the base station to the A-IoT device. Note that the synchronization signal may be based on, for example, control information X.

[0133] [Proposal 4c] For example, T_gap may be a specified value (e.g., specified in a specification), a fixed value, or a preset value. The base station and the A-IoT device may determine (the value of) T_gap as a specified value, a fixed value, or a preset value.

[0134] Also, for example, T_gap may depend on one or more of a device type, a message type, a (message) size of control information, a traffic type, a cast type, a PRDCH format, etc. The base station and the A-IoT device may determine (the value of) T_gap according to one or more of a device type, a message type, a size of control information, a traffic type, a cast type, a PRDCH format, etc.

[0135] As described above, the base station may transmit an R2D including control information including control information X and data to the A-IoT device. The A-IoT device may receive / detect / decode control information including control information X from the base station, and receive / detect / decode R2D data from the base station based on the received / detected / decoded control information. For example, the A-IoT device may receive a signal including control information and data transmitted to the A-IoT device, and may receive / detect / decode R2D data after the time required to decode the control information has elapsed from the end of the control information by applying a portion of the control information (control information X) from the beginning of the data. Here, data does not need to be transmitted from the base station to the A-IoT device until the time required to decode the control information has elapsed from the end of the control information.

[0136] According to Proposal 4, the A-IoT device can properly receive / detect / decode the R2D data based on the control information X, taking into account the time required to decode the control information.

[0137] <Proposal 5> Next, proposal 5 regarding a processing time parameter for determining when the decoding of control information is completed will be described.

[0138] Fig. 18 is a diagram showing an example of R2D transmission according to Proposal 5. As shown in Fig. 18, a processing time parameter T_proc may be introduced to take into account the time required to decode the control information. The A-IoT device may determine the start of the R2D data transmission based on the processing time parameter T_proc and the control information X (e.g., based on (information indicating) the length of the control information including the processing time parameter T_proc and the control information X).

[0139] The processing time parameter T_proc may represent the time required to decode the control information, or may represent the maximum value thereof. More specifically, for example, the processing time parameter T_proc may represent the period or length of time between the start point of the control information and the end timing of the decoding of the control information. Furthermore, for example, the processing time parameter T_proc may represent the period or length of time between the end point of the control information and the end timing of the decoding of the control information.

[0140] [Proposal 5a] The R2D transmission or R2D data excluding the postamble (if any) may be assumed to be longer than T_proc (or equal to or greater than T_proc). In this case, the A-IoT device may apply control information X included in the control information to the data after T_proc has elapsed from the end of the control information to perform reception / detection / decoding. Also, in this case, the A-IoT device may assume that the R2D transmission or R2D data excluding the postamble (if any) is longer than T_proc (or equal to or greater than T_proc) (or may not assume that it is equal to or less than T_proc (or shorter than T_proc)).

[0141] Proposal 5b: R2D transmission or R2D data, excluding postamble (if present), may be longer than (or greater than or equal to) T_proc or less than (or shorter than) T_proc.

[0142] Proposal 5b1 If the R2D transmission or R2D data, excluding the postamble (if any), is longer than T_proc (or equal to or greater than T_proc), the control information includes control information X; otherwise, the control information does not include control information X. For example, if the R2D transmission or R2D data, excluding the postamble (if any), is longer than T_proc (or equal to or greater than T_proc), the A-IoT device may interpret the control information as including control information X and apply control information X to data T_proc after the end of the control information to perform reception / detection / decoding; otherwise, the A-IoT device may interpret the control information as not including control information X.

[0143] Proposal 5b2 If the control information includes control information X, the R2D transmission or R2D data excluding the postamble (if present) is longer than (or equal to or longer than) T_proc; otherwise, the R2D transmission or R2D data excluding the postamble (if present) is shorter than (or equal to or shorter than) T_proc. For example, if the control information includes control information X, the A-IoT device may interpret the R2D transmission or R2D data excluding the postamble (if present) as being longer than (or equal to or longer than) T_proc and may apply control information X to receive / detect / decode data T_proc after the end of the control information; otherwise, the A-IoT device may interpret the R2D transmission or R2D data excluding the postamble (if present) as being shorter than (or equal to or shorter than) T_proc.

[0144] [Proposal 5c] For example, T_proc may be a specified value (e.g., specified in a specification), a fixed value, or a preset value. The base station and the A-IoT device may determine (the value of) T_proc as a specified value, a fixed value, or a preset value.

[0145] Also, for example, T_proc may depend on one or more of a device type, a message type, a (message) size of control information, a traffic type, a cast type, a PRDCH format, etc. The base station and the A-IoT device may determine (the value of) T_proc according to one or more of a device type, a message type, a size of control information, a traffic type, a cast type, a PRDCH format, etc.

[0146] As described above, the base station may transmit an R2D including control information and data, which may or may not include control information X, to the A-IoT device. The A-IoT device may receive / detect / decode the control information from the base station, and receive / detect / decode the R2D data from the base station based on the received / detected / decoded control information. For example, the A-IoT device may receive a signal including control information and data transmitted to the A-IoT device, and if the R2D transmission or R2D data excluding a postamble (if present) is longer than T_proc (or is equal to or greater than T_proc), the A-IoT device may apply a portion of the control information (control information X) to the R2D data after T_proc has elapsed from the end of the control information to perform reception / detection / decoding.

[0147] According to Proposal 5, the A-IoT device can properly receive / detect / decode the R2D data based on the control information X, taking into account the time required to decode the control information.

[0148] <Example of Operation According to Proposal> Next, an example of operation of the wireless communication device according to the present proposal will be described with reference to Fig. 19. The wireless communication device may be an A-IoT device or an intermediate UE.

[0149] In step S11, the wireless communication device receives a signal including control information and data transmitted to the wireless communication device. If the wireless communication device is an A-IoT device, the signal may be transmitted from a base station or an intermediate UE, and if the wireless communication device is an intermediate UE, the signal may be transmitted from a base station. The signal may be R2D, the control information may be R2D control information, and the data may be R2D data. Part of the control information may be the control information X described above.

[0150] In step S12, the wireless communication device applies the part of the control information in at least one of receiving, detecting, and decoding data after the time required to decode at least the part of the control information has elapsed from the end of at least the part of the control information. The time required to decode at least the part of the control information may be T, T_gap, or T_proc as described above.

[0151] Note that steps S11 and S12 may be performed in accordance with Proposal 1 to Proposal 5, which include the various options described above.

[0152] <Variations> Variation 1: In Proposal 3, it was explained that the time T may refer to the time required to decode the control information. However, in Proposal 3, as in Proposal 2, if the control information X is mapped before the R2D control information transmission, the time T may also refer to the time required to decode the control information X.

[0153] Variation 2: In Proposal 3′, it was explained that the time T may refer to the time required to decode the control information. However, in Proposal 3′, as in Proposal 2, if the control information X is mapped before the R2D control information transmission, the time T may also refer to the time required to decode the control information X.

[0154] Variation 3: In Proposal 4, it was explained that the time gap T_gap may refer to the time required to decode the control information. However, in Proposal 4, as in Proposal 2, if the control information X is mapped before the R2D control information transmission, the time gap T_gap may also refer to the time required to decode the control information X.

[0155] Variation 4: In Proposal 5, it was explained that the processing time parameter T_proc may refer to the time required to decode the control information. However, in Proposal 5, similar to Proposal 2, if the control information X is mapped before the R2D control information transmission, the processing time parameter T_proc may also refer to the time required to decode the control information X.

[0156] As described above, according to this proposal, an A-IoT device can appropriately receive / detect / decode R2D data based on R2D control information, taking into account the time required to decode the control information.

[0157] Next, the configurations of the base station 10 and the device 20 will be described. Note that the configurations of the base station 10 and the device 20 described below are examples of functions related to this embodiment. The base station 10 and the device 20 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0158] <Configuration of Base Station> Fig. 20 is a block diagram showing an example of the configuration of a base station 10 according to an embodiment. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates with a device 20 (see Fig. 21) wirelessly. The base station 10 may be a terminal (an intermediate UE that communicates with the device 20).

[0159] The transmitter 101 transmits a downlink (DL) signal to the device 20. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

[0160] The DL signal may include, for example, a downlink data signal and control information (e.g., DCI (Downlink Control Information)). The DL signal may also include information indicating scheduling related to signal transmission of the device 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of RRC (Radio Resource Control)). The DL signal may also include a reference signal.

[0161] The channels used for transmitting DL signals include, for example, a data channel and a control channel. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits control information to the device 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0162] The reference signal included in the DL signal may include at least one of, for example, a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as the DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0163] The receiving unit 102 receives an uplink (UL) signal transmitted from the device 20. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

[0164] The control unit 103 controls the communication operations of the base station 10 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0165] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0166] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the device 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the device 20.

[0167] The control unit 103 configures PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to the configuration of the PUCCH, such as a PUCCH cell timing pattern (PUCCH configuration information), may be notified to the device 20 by RRC.

[0168] Here, the transmitting unit 101 and the receiving unit 102 (which may be collectively referred to as a communication unit) communicate with the device 20 .

[0169] For example, the transmitter 101 may transmit a signal including control information and data to the A-IoT device. Alternatively, the transmitter 101 may not transmit the data until the time required for the A-IoT device to decode the control information has elapsed from the end of the control information.

[0170] <Device Configuration> Fig. 21 is a block diagram showing an example of the configuration of the device 20 according to the embodiment. The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with the base station 10 wirelessly, for example. The device 20 may be a terminal (an intermediate UE that communicates with the base station 10).

[0171] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

[0172] The transmitting unit 202 transmits the UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0173] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI (Uplink Control Information)). For example, information related to the processing capability of the device 20 (e.g., A-IoT capability) may be included. The UL signal may also include a reference signal.

[0174] The channels used for transmitting UL signals include, for example, a data channel and a control channel. For example, the data channel may include a PUSCH (Physical Uplink Shared Channel), and the control channel may include a PUCCH (Physical Uplink Control Channel). For example, the device 20 transmits control information from the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.

[0175] The reference signal included in the UL signal may include, for example, at least one of a DMRS, a PTRS, a CSI-RS, an SRS, and a PRS. For example, the reference signal such as the DMRS or the PTRS is used for demodulating an uplink data signal and is transmitted using an uplink channel (for example, a PUSCH).

[0176] The control unit 203 controls the communication operations of the device 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0177] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

[0178] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ ACK / NACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted, for example, in PUCCH resources.

[0179] Control unit 203 configures PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern and / or DCI notified by RRC) received from base station 10. Control unit 203 determines PUCCH resources to be used for transmitting information to be fed back to base station 10. Under the control of control unit 203, transmission unit 202 transmits the information to be fed back to base station 10 in the PUCCH resources determined by control unit 203.

[0180] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0181] Here, the receiving unit 201 and the transmitting unit 202 (which may be collectively referred to as a communication unit) communicate with the network, such as the base station 10 and intermediate UEs.

[0182] For example, the receiving unit 201 may receive a signal including control information and data transmitted to the device 20, and the control unit 203 may apply a portion of the control information in at least one of receiving, detecting, and decoding operations on data after a time required to decode at least a portion of the control information has elapsed from the end of at least a portion of the control information. Furthermore, the control unit 203 may apply a portion of the control information from the beginning of the data in at least one of receiving, detecting, and decoding operations on data after a time required to decode at least a portion of the control information has elapsed from the end of the portion of the control information. Furthermore, the control unit 203 may apply a portion of the control information from the middle of the data in at least one of receiving, detecting, and decoding operations on data after a time required to decode the control information has elapsed from the end of the control information. Furthermore, the data may be composed of multiple segments of the same length, and the control unit 203 may apply a portion of the control information from the first segment of the multiple segments after a time required to decode the control information has elapsed in at least one of receiving, detecting, and decoding operations on data after a time required to decode the control information has elapsed from the end of the control information. In addition, data may not be transmitted until the time required to decode the control information has elapsed from the end of the control information, and the control unit 203 may apply part of the control information from the beginning of the data in at least one of the operations of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed from the end of the control information.

[0183] (Summary of the embodiment) A wireless communication device according to one aspect of the present disclosure includes a receiving unit that receives a signal including control information and data transmitted to the wireless communication device, and a control unit that applies the portion to at least one of receiving, detecting, and decoding the data after a time required to decode at least a portion of the control information has elapsed from the end of at least a portion of the control information.

[0184] With the above configuration, the wireless communication device can appropriately receive, detect, and / or decode data based on the control information, taking into account the time required to decode at least a portion of the control information.

[0185] In one example, the control unit applies the portion from the beginning of the data in at least one of receiving, detecting, and decoding the data after the time required to decode the portion has elapsed from the end of the portion.

[0186] With the above configuration, data can be received, detected and / or decoded appropriately from the beginning of the data, taking into consideration the time required to decode a portion of the control information.

[0187] In one example, the control unit applies the portion from the middle of the data in at least one of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed from the end of the control information.

[0188] With the above configuration, data can be appropriately received, detected and / or decoded from the middle of the data, taking into consideration the time required to decode the control information.

[0189] In one example, the data is composed of multiple segments of the same time length, and the control unit applies the portion from the first segment of the multiple segments after the time required to decode the control information has elapsed from the end of the control information in at least one of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed.

[0190] With the above configuration, it is possible to appropriately receive, detect and / or decode data from the middle of the data, taking into consideration the time required to decode at least a part of the control information.

[0191] In one example, the data is not transmitted until the time required to decode the control information has elapsed from the end of the control information, and the control unit applies the portion from the beginning of the data in at least one of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed from the end of the control information.

[0192] With the above configuration, data can be received, detected and / or decoded appropriately from the beginning of the data, taking into consideration the time required to decode the control information.

[0193] A communication method according to one aspect of the present disclosure includes a wireless communication device receiving a signal including control information and data transmitted to the wireless communication device, and applying the portion in at least one of receiving, detecting, and decoding the data after a time required to decode at least a portion of the control information has elapsed from the end of the at least a portion of the control information.

[0194] With the above configuration, the wireless communication device can appropriately receive, detect, and / or decode data based on the control information, taking into account the time required to decode at least a portion of the control information.

[0195] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

[0196] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0197] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0198] For example, a base station, a device, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 22 is a diagram showing an example of the hardware configuration of a base station and a device according to the embodiment. The above-described base station 10 and device 20 may be physically configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0199] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the device 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0200] Each function in the base station 10 and the device 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0201] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

[0202] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 103 of the base station 10 and the control unit 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be used for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0203] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0204] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0205] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

[0206] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0207] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0208] Furthermore, the base station 10 and the device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0209] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described in the present disclosure and may be performed using other methods. For example, notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0210] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0211] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0212] <Operation of Base Station> In the present disclosure, specific operations described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0213] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0214] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

[0215] <Determination method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0216] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0217] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0218] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0219] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0220] Information, Signals, etc., described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0221] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0222] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0223] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0224] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0225] <Base Station> In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0226] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0227] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0228] Mobile Station In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0229] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0230] <Base Station / Mobile Station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0231] Furthermore, the base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the device 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0232] Similarly, the term "terminal" in the present disclosure may be read as a base station. In this case, the base station 10 may be configured to have the functions of the device 20 described above.

[0233] Fig. 23 shows an example configuration of a vehicle 2001. As shown in Fig. 23, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0234] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0235] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0236] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0237] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0238] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0239] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0240] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0241] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0242] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0243] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0244] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0245] <Meaning and Interpretation of Terms> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), ascertaining something that is considered to be a "judging" or "determining," and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like that are considered to be a "judging" or "determining." Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0246] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0247] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.

[0248] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0249] "First," "Second" Any reference to an element using designations such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0250] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," or the like.

[0251] Open Format: When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0252] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0253] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0254] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.

[0255] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0256] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0257] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0258] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0259] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0260] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0261] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0262] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0263] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0264] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0265] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0266] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0267] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0268] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0269] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0270] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

[0271] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0272] Articles In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0273] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0274] One aspect of the present disclosure is useful in wireless communication systems.

[0275] 10 Base station 20 Device 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A wireless communication device comprising: a receiving unit that receives a signal including control information and data transmitted to the wireless communication device; and a control unit that applies the portion in at least one of receiving, detecting, and decoding the data after the time required to decode at least a portion of the control information has elapsed from the end of at least a portion of the control information.

2. The wireless communication device according to claim 1, wherein the control unit applies the portion of the data from the beginning of the data in at least one of receiving, detecting, and decoding the data after the time required to decode the portion has elapsed from the end of the portion.

3. The wireless communication device according to claim 1, wherein the control unit applies the portion from the middle of the data in at least one of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed from the end of the control information.

4. The wireless communication device of claim 1, wherein the data is composed of multiple segments of the same length, and the control unit applies the portion from the first segment of the multiple segments after the time required to decode the control information has elapsed from the end of the control information in at least one of receiving, detecting, and decoding the data after the time required to decode the control information has elapsed.

5. The wireless communication device of claim 1, wherein the data is not transmitted until the time required to decode the control information has elapsed from the end of the control information, and the control unit applies the portion from the beginning of the data in at least one of receiving, detecting, and decoding operations for the data after the time required to decode the control information has elapsed from the end of the control information.

6. A communication method in which a wireless communication device receives a signal including control information and data transmitted to the wireless communication device, and applies the portion in at least one of receiving, detecting, and decoding the data after the time required to decode at least a portion of the control information has elapsed from the end of the portion of the control information.

Images