Device

Abstract

To provide a device that can properly set the midamble of an upstream signal.SOLUTION: A device powered by energy harvesting includes a receiving unit that receives control information, and a control unit that determines the transmission of a midamble of an uplink signal on the basis of a combination of at least the following conditions, explicit instruction of the control information, transport block size and / or number of information bits and / or period and / or number of chips of the uplink signal, message type of the uplink signal, and error correction settings for the uplink signal.SELECTED DRAWING: Figure 23

Description

[Technical Field]

[0001] The present disclosure relates to a device. [Background technology]

[0002] For NR (New Radio) (also known as "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, and low power consumption (see, for example, Non-Patent Document 1).

[0003] Furthermore, Release 18 (Rel-18) of 3GPP (registered trademark) is considering Ambient Internet of Things (A-IoT) (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. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V17.3.0 (2022-12) [Non-patent document 2] “Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 2023 [Non-patent document 3] 3GPP TR 38.848 V1.0.0 (2023-09) [Non-patent document 4] 3GPP TS 36.211 V16.8.0 (2023-09) [Non-Patent Document 5] “Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023 [Non-patent document 6] “New Work Item: Solutions for Ambient IoT (Internet of Things) in NR”, RP-243326, 3GPP TSG RAN Meeting #106, December 2024 [Non-Patent Document 7] 3GPP TR 38.769 V19.0.0 (2024-12) Summary of the Invention

[0005] However, the setting of the midamble of an uplink signal such as a PDRCH has not been sufficiently studied, and further study is required.

[0006] One aspect of the present disclosure is to provide a device that can appropriately set the midamble of an uplink signal. [Means for solving the problem]

[0007] A device according to one aspect of the present disclosure is a device that receives power from energy harvesting, and includes a receiver that receives control information and a power supply that supplies power to the device. The receiver receives control information and at least one power supply that satisfies the following conditions: Explicit indication of said control information Transport block size and / or number of information bits and / or period and / or number of chips of the uplink signal Message type of the upstream signal -Error correction settings for the upstream signal and a control unit that determines whether to transmit a midamble of the uplink signal based on any combination of the above. [Brief explanation of the drawings]

[0008] [Figure 1]1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating Topology 1. [Figure 3] FIG. 10 is a diagram illustrating Topology 2. [Figure 4] FIG. 10 is a diagram illustrating topology 3 in DL support. [Figure 5] FIG. 10 is a diagram illustrating Topology 3 in UL support. [Figure 6] FIG. 10 is a diagram illustrating Topology 4. [Figure 7] FIG. 1 is a diagram illustrating backscatter transmission. [Figure 8] 1A and 1B are diagrams illustrating examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. [Figure 9] FIG. 10 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 2. [Figure 10] A diagram showing an example of an access procedure for an A-IoT device. [Figure 11] A diagram showing steps in the access procedure for an A-IoT device. [Figure 12] A diagram showing an example of a four-step (or three-step) random access procedure for an A-IoT device. [Figure 13] A diagram showing an example of a two-step random access procedure for an A-IoT device. [Figure 14] FIG. 1 is a diagram illustrating a D2R preamble and a D2R midamble in a D2R transmission. [Figure 15] FIG. 1 is a diagram illustrating a type 1 D2R midamble and a type 2 D2R midamble. [Figure 16] FIG. 1 is a diagram illustrating a type 1 D2R midamble and a type 1 D2R midamble. [Figure 17] FIG. 10 is a diagram illustrating Proposal 2. [Figure 18] FIG. 10 is a diagram illustrating Proposal 5. [Figure 19] FIG. 10 is a diagram illustrating Proposal 6. [Figure 20] FIG. 10 is a diagram illustrating Proposal 6. [Figure 21] FIG. 10 is a diagram illustrating Proposal 6. [Figure 22] FIG. 2 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 23] FIG. 1 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. [Figure 24] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure. [Figure 25] 1 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[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 operation of the wireless communication system according to the embodiment of the present disclosure, existing technologies are used as appropriate. The existing technologies are, for example, existing LTE or NR, but are not limited to existing LTE or NR. Furthermore, the term "LTE" as used in this specification has a broad meaning including LTE-Advanced and systems beyond LTE-Advanced, unless otherwise specified.

[0011] Furthermore, in the embodiments of the present disclosure described below, terms used in existing LTE, 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), 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, device, terminal, etc. are set.

[0014] <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. A base station may also be referred to as a BS (Base Station), gNB, or the like. The device 20 may be considered 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 to the device 20 via DL (Downlink). 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 from the device 20 via UP (Uplink).

[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, 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 PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or PUCCH.

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

[0023] Ambient IoT may consider, for example, the following deployment scenarios and characteristics for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment The connectivity topology, e.g., which nodes (e.g., base stations, terminals (UE), relays, and repeaters) communicate with the ambient IoT devices - Duplexing method: TDD or FDD, frequency band: licensed or unlicensed Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies - Traffic assumptions for outgoing / incoming traffic from the device

[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 type and topology> 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 and amplification functions, and performs backscattering transmission. Device B: Device B has power storage, does not have the capability of independent signal generation, and performs backscatter transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, is capable of independent signal generation, and has active RF (radio frequency) components for transmission.

[0027] The complexity of device A is assumed to be about the same as that of RFID (radio frequency identification).

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

[0029] Figure 2 is a diagram illustrating Topology 1. As shown in Figure 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 communicates directly with the base station in both directions.

[0030] Figure 3 is a diagram illustrating Topology 2. As shown in Figure 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate 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, etc.

[0031] Figure 4 is a diagram illustrating Topology 3 in DL assistance. As shown in Figure 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] Figure 5 is a diagram illustrating Topology 3 in UL support. As shown in Figure 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 an 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 Figures 4 and 5 may be, for example, relays, IAB nodes, UEs, repeaters, etc.

[0036] Figure 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 sidelink (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, which 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. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area in FIG. 7 indicates an OFF section, which may correspond to the information (bit) "0." A sine wave signal may correspond to the 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 can 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) As for traffic, there is transmission (DL) to the A-IoT UE, but there is no transmission (UL) from the A-IoT UE. In other words, there is information to be transmitted to the A-IoT UE, but there is no information to be transmitted from the A-IoT UE. DT corresponds to a command type, for example, in which there is an instruction such as a command to the A-IoT UE.

[0046] ·DO-DTT(device originated - device terminated triggered) Traffic includes triggers from the network (NW) and transmissions (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, transmitting information corresponds to transmitting a signal containing information or transmitting a signal. In this disclosure, transmitting to a certain device X corresponds to transmitting a signal (or information) to device X. In addition, transmitting from a certain device X and transmitting by a certain device X correspond to device X transmitting a signal (or information). In addition, receiving from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, receiving by a certain device X corresponds to device X receiving a signal (or information).

[0048] 2. Device Prerequisites For A-IoT UE, the following TX (transmission) and FR (frequency range) 1-FDD are assumed:

[0049] ·TX TX can be an unamplified backscatter UL transmission, an amplified backscatter UL transmission, or a general amplified UL transmission.

[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: 410MHz~7.125GHz FR2: 24.25GHz~52.6GHz FR3: 7.125GHz~24.25GHz

[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 the case of 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 the intermediate node located between the base station and the A-IoT UE. Note that the base station in Topology 2 may correspond to a macrocell. The Topology 2 case may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as intermediate UE, int.UE (intermediate UE), etc.

[0056] <Device Type> Three device types are defined for A-IoT devices: Device 1, Device 2a, and Device 2b.

[0057] Device 1 (may also 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 an energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million), where Z is 10 to the power of x (x is an integer greater than or equal to 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 (also referred to as Type 2a) The device 2a is a device type that consumes a peak power of several hundred μW. The device 2a has an energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). The device 2a also performs DL and / or UL amplification. The UL transmission in the device 2a is performed by backscattering in a CW provided from an external device.

[0059] Device 2b (also called 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 power x (x is an integer equal to or greater than 0)). DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed internally within 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 Topology> Next, we describe candidate topologies for CW / R2D / D2R transmission.

[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 Figure 8, in topologies 1A to 1E, CW / R2D communication signals (sometimes referred to as "R2D" in Figure 8 and below) / D2R communication signals (sometimes referred to as "D2R" in Figure 8 and below) can be sent 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, where reader corresponds to BS and / or intermediate UE, and device corresponds to A-IoT device.

[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 transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (BS). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). 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, or other type of node.

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

[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. In other words, R in R2D is different from 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 (referred to as "R2D" in Figure 9) / D2R communication signals (referred to as "D2R" in Figure 9) can be sent and received to A-IoT devices.

[0071] In Topology 2A, the node transmitting the CW (first intermediate UE) is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (second intermediate UE), and the node transmitting the CW is the same as the node transmitting the R2D communication signal. Also, the node transmitting the R2D communication signal is different from the node receiving 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 transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (intermediate UE). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving 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 R2D communication signal is the same as the node that receives the D2R communication signal generated and transmitted by the A-IoT device, i.e., R in R2D is the same as R in D2R.

[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] <Terminology> Here, we will explain the terms used in relation to the A-IoT mentioned above.

[0077] A-IoT device or device: a device included in an A-IoT system, having any of the multiple device types as described above.

[0078] Reader: D2R receiver The leader can be either a BS or a UE. The leader UE can be called an intermediate UE. The R2D transmitter and D2R receiver may be the same node or different nodes.

[0079] ·R2D: Abbreviation for Reader-to-Device Link. PRDCH: Physical R2D channel. D2R: Abbreviation for Device-to-Reader Link. PDRCH: Physical D2R channel.

[0080] ·DT traffic: Abbreviation for Device Terminated traffic. DT traffic is, for example, traffic that sends commands from a reader to a device and terminates at the device.

[0081] DO-DTT traffic: Device Originated-Device Terminated Trigger DO-DTT traffic is, for example, "inventory" traffic.

[0082] Timing acquisition signal / preamble / midamble / postamble / synchronization signal can be replaced with each other.

[0083] At least one of the following may be applied to each proposal in this embodiment, and to each alternative / option if each proposal includes an alternative / option. Multiple proposals may be combined. Multiple options may be combined. Multiple alternatives may be combined. Different options / alternatives may be applied on a case-by-case basis. The instruction / setting may be transmitted in the control information of the physical layer or in the payload of a higher layer. For example, the instruction / setting may be transmitted in at least one of the control information of the MAC layer, Msg0 (paging), Msg2 (RAR), Msg4, and unicast. The same applies when the instruction / setting is indicated by R2D. The instruction / setting may be transmitted by the PRDCH, by an R2D timing acquisition signal (e.g., preamble / midamble / postamble), or by a synchronization signal. A slot may be a time interval of 1 millisecond. A slot may be one slot in Orthogonal Frequency Division Multiplexing (OFDM). A slot may be a slotted-ALOHA slot. A slot may be any other time domain unit consisting of one or more symbols. A symbol may be one OFDM symbol, M chips (M is an integer greater than or equal to 1) of on-off-keying (OOK), or one modulation symbol of phase shift keying (PSK) and / or frequency shift keying (FSK). · Different alternatives / options may apply to R2D and D2R. Different alternatives / options may apply to different device types. · Different alternatives / options may be applied to different connection topologies. Different alternatives / options may be applied to different R2D channels or D2R channels. The R2D channel may be, for example, either a PRDCH or a PHY channel for R2D control. The D2R channel may be either a PDRCH or a PHY channel for D2R control. Different alternatives / options may be applied to different R2D information or different D2R information. Also, different alternatives / options may be applied to different R2D formats or different D2R formats. Also, different alternatives / options may be applied to different R2D commands or different D2R commands. For example, different alternatives / options may be applied to any of the following. In other words, the alternatives / options applied may differ between two of the following: -R2D Data -R2D control -R2D system information -R2D information triggering contention based access -D2R data -D2R control -D2R ACK / NACK response -D2R response in contention based access (Msg1 / Msg3)

[0084] R2D, R2D transmission, R2D signal, DL, and DL signal may be used interchangeably. D2R, D2R transmission, R2D signal, UL, and UL signal may be used interchangeably. R2D control transmission may be referred to as R2D control information or control information. D2R control transmission may be referred to as D2R control information or control information. Signal, channel, data, and information may be used interchangeably. The leader corresponds to a base station or an intermediate node.

[0085] <Rel-19 compliant WID> A new WID (Work Item Description), "New Work Item: Solutions for Ambient IoT (Internet of Things) in NR" (RP-243326) (Non-Patent Document 6), was approved in Rel-19. This WID shows the guidelines for promoting the standardization of A-IoT technology in NR, and Chapter 4 is described as follows.

[0086] General scope Definitions provided in TR 38.848, TR 38.769, and decisions in the RAN working group in Rel-19 SI in the RAN working group are incorporated into this WI, and the following are exclusive general scopes: A. The overall goal is to standardize the following ambient IoT devices: Device 1: Peak power consumption ~1μW, energy storage, RF envelope detector receiver, initial sampling frequency offset (SFO) up to 10 X ppm, no R2D and D2R amplification within the device, the device's D2R transmission is backscattered relative to the externally provided carrier B. Deployment Scenario 1 using Topology 1 according to D1T1-B The licensed spectrum in C.FR1 operates in a frequency division duplex (FDD) scheme, with R2D being used in the downlink (DL) spectrum and D2R and CW being used in the uplink (UL) spectrum. D. Spectrum deployment in the band for NR and standalone spectrum deployment, A-IoT base station (BS) is installed indoors E. Traffic types DO-DTT, DT for rUC1 (indoor inventory) and rUC4 (indoor command) Waveform 1 carrier transmission only, no hopping, for the following cases based on F.TR 38.769 Regarding D1T1-B cases 1 to 4 G.Proximity determination only according to Solution 1 of TR 38.769 (Un)availability of devices via H.TR 38.769 direction 1 only

[0087] Within a general scope, the following objectives are set: RAN1 range: PRDCH and PDRCH are the only physical channels in R2D and D2R, respectively. R2D and D2R signals Multiplexing / multiple connections in R2D are only TDMA (Time Division Multiple Access), while D2R is only TDMA and FDMA (Frequency Division Multiple Access). R2D supports only OOK (on-off keying)-4 modulation and provides one solution for CP processing. D2R backscattering supports only OOK and BPSK (binary phase shift keying) modulation. R2D transmission supports only the Manchester line code in TR 38.769 D2R transmission supports the following: · Manchester line code in TR 38.769, or no line code (either can be selected) · Corresponding small frequency shift method according to the options of TR 38.769 R2D does not support FEC (forward error correction). D2R supports only convolutional coding with a generating polynomial according to TS 36.212 (unless RAN1 decides to use other generating polynomials according to RAN1#120bis). PRDCH and PDRCH support transmission without CRC (cyclic redundancy check) and support transmission with CRC according to the generating polynomials of 6-bit CRC and 16-bit CRC in TS 38.212 (unless RAN1 decides to use other generating polynomials according to RAN1#120bis). Which CRC length to use, or whether to use no CRC, is determined by RAN1. D2R supports physical layer repeated transmission (repetition). R2D does not support physical layer repeated transmission.

[0088] <Access Procedure for A-IoT Devices> In the A-IoT communication session, the access procedure for A-IoT devices (hereinafter simply referred to as devices) is executed. As the access procedure for A-IoT devices, two approaches, namely the two-step approach and the four-step approach, are being considered.

[0089] Fig. 10 is a diagram showing an example of an access procedure for an A-IoT device. Fig. 10 shows signal exchange between one reader and one device. The horizontal axis of Fig. 10 indicates the time axis. Fig. 10 shows exchanges including a two-step access procedure and a four-step access procedure.

[0090] In the two-step access procedure, the reader sends an A-IoT paging message. The A-IoT paging message corresponds to the first R2D transmission in an A-IoT communication session. The device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the two-step access procedure, A-IoT Msg1 contains information that identifies the device (e.g., device ID). A-IoT Msg1 may be considered a device ID report. The reader that receives A-IoT Msg1 sends a message called A-IoT Msg2 to the device. For example, the reader that receives A-IoT Msg1 sends A-IoT Msg2 addressed to the device identified by the device ID included in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The two-step access procedure is then completed.

[0091] In the four-step access procedure, the reader sends an A-IoT paging message. A device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the four-step access procedure, A-IoT Msg1 contains a random ID. A-IoT Msg1 may be considered a random ID report. The reader that receives A-IoT Msg1 sends a message called A-IoT Msg2 to the device. For example, the A-IoT reader sends A-IoT Msg2, which contains the random ID contained in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The device receives A-IoT Msg2 and sends A-IoT Msg3 to the reader. For example, if the random ID of the received A-IoT Msg2 matches the random ID of the sent A-IoT Msg1, the device sends A-IoT Msg3 to the reader. In the four-step access procedure, A-IoT Msg3 contains information that identifies the device (e.g., device ID). A-IoT Msg3 may be considered a device ID report. A reader that receives A-IoT Msg3 sends a response (e.g., R2D response). The four-step access procedure is then completed. However, in the four-step access procedure, a reader that receives A-IoT Msg3 does not have to send a response (e.g., R2D response).

[0092] For example, in an "inventory" use case such as checking the presence of an A-IoT device, each communication session includes only the above two-step access procedure or four-step access procedure. Note that the "inventory" use case is not limited to checking the presence of an A-IoT device.

[0093] For example, in the "inventory + command" use case, which includes checking the presence of an A-IoT device and issuing instructions to the A-IoT device, as shown in Figure 10, each communication session involves sending an R2D command message and a D2R response after the above two-step or four-step access procedure.

[0094] In addition, in exchanges including the access procedures shown in Figure 10, etc., a contention-based access procedure such as slotted-ALOHA may be applied at least to A-IoT Msg1.

[0095] In an A-IoT communication session, one A-IoT page may be sent to multiple devices. After receiving one A-IoT page, the multiple devices may continue with subsequent transmission / reception in the communication session. Note that the subsequent transmission / reception in the device may be at least one of sending A-IoT Msg1, receiving A-IoT Msg2, sending A-IoT Msg3, receiving an R2D response, receiving an R2D command message, and sending a D2R response, as shown in Figure 10.

[0096] In addition, in the exchanges including the access procedures shown in Figure 10 etc., A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be abbreviated as Paging, Msg1, Msg2, Msg3, respectively. Furthermore, A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be associated with names different from these names.

[0097] The message type may be any of A-IoT paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3, R2D response, R2D command message, and D2R response. The R2D response may be omitted. The message type may be interchangeably referred to as message. The message may be interchangeably referred to as signal or information. For example, message transmission / reception may be interchangeably referred to as signal transmission / reception. The R2D command message may be referred to as R2D data.

[0098] The following description will mainly focus on an example of a four-step access procedure and "inventory+command" communication. However, the present disclosure is not limited to this. The present disclosure may be applied to a two-step access procedure or to "inventory" communication. An example of "inventory+command" communication corresponds to an example in which a four-step access procedure is followed by transmission / reception of an R2D command message and a D2R response.

[0099] Also, in the following description, one or more steps (e.g., processes) may be omitted (or skipped). For example, as described above, in the case of a two-step approach, the transmission / reception of A-IoT Msg3 may be omitted. Also, as described above, in the case of "inventory" communication, the R2D command message and D2R response may be omitted.

[0100] It should be noted that any of the above message types may be transmitted by unicast, multicast, broadcast, or groupcast.

[0101] <Procedures based on the agreement> Rel-19 considers inventory and command use cases as well as DO-DTT and DT traffic, and for these use cases / traffic types, steps 1 and 2 below are considered.

[0102] 1. Inventory only Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA).

[0103] 2. Inventory and command Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA). Step C1: The reader sends data to the device (e.g., R2D command). Step C2: The corresponding device sends data (e.g., feedback) to the reader. Note that it is unclear whether step C2 is optional.

[0104] FIG. 11 is a related diagram in TR 38.769 (Non-Patent Document 7).

[0105] <Random Access (RA) based on agreements> Regarding random access, the following steps 1 and 2 are being considered:

[0106] 1. 4 steps (or 3 steps) (see Figure 12) A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device. The size of the random ID is fixed, 16 bits. A-IoT Msg2: The reader echoes the ID received in Msg1. A-IoT Msg3: The device sends its device ID and / or other upper layer data (upon upper layer request). If the device receives Msg2 containing the same random ID as Msg1, it considers the conflict resolution successful. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be sent with random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons).

[0107] Step 2.2 (See Figure 13) A-IoT Msg1: The device transmits its device ID and / or other upper layer data (as requested by the upper layer). A random ID (fixed 16 bits) may additionally be included in Msg1. A-IoT Msg2: If Msg1 contains a random ID, the reader echoes the ID received in Msg1.

[0108] In addition, at the 3GPP RAN2#126 and #127 meetings, the following procedures were agreed upon in relation to the above procedures.

[0109] [3GPP RAN2#126 Agreement on "4-Step" RA] 1. A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device (how it is generated is undetermined, e.g. randomly or based on the device ID). The ID size is undetermined. This does not exclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader echoes the ID received in Msg1. Msg2 may contain further information based on the agreement of RAN1. 3. A-IoT Msg3: The device sends its device ID and / or other upper layer data (as requested by the upper layer). 4. If the device receives Msg2 containing the same random ID as Msg1, it considers the contention resolution successful. RAN2 assumes that the size of the random ID in Msg1 is sufficient for contention resolution purposes. 5. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be transmitted via random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons). The use / existence of "Msg4" can be further discussed. RAN2 does not use the term "Msg4" for further discussion of random access.

[0110] [3GPP RAN2#126 Agreement on 2-Step CB RA] 1. A-IoT Msg1: The device sends its device ID and / or other higher layer data (as required by the higher layer). It is undetermined what the device ID will be. It is undetermined whether an additional random ID is required. This does not preclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader may echo some information from Msg1. It is undetermined what that some information is. The usage / existence of "Msg2" can be further discussed.

[0111] [3GPP RAN2#127 Agreement (3-step CBRA)] For 3-step CBRA (Contention-Based Random Access) support, the fixed random ID size is 16 bits. The ID is generated randomly. -Indication of D2R failure / success will be considered. It is not yet decided whether the indication of D2R failure / success will be implicitly or explicitly indicated, and in what cases it will be required. It is also not yet decided whether the indication of D2R failure / success will only be applied in some cases.

[0112] [3GPP RAN2#127 Agreement (2-step CBRA)] For 2-step CBRA, the RAN2 specification supports Msg2. Whether it is required is up to the reader. It is not yet decided when it is required. For 2-step CBRA (when Msg2 is required), the random ID (fixed 16 bits) is also included in A-IoT Msg1 and echoed in A-IoT Msg2. If there are devices that only support 2-step RA, it is not yet decided whether other optimizations will be required for such devices. In contention-free access, A-IoT devices will directly send higher layer data (e.g., device ID) in the first D2R message after being triggered (i.e., skipping contention resolution Msg1 / 2). It remains to be determined whether short AS IDs will also be included in the message, and what type of IDs will be included for scheduling purposes. · It is yet to be determined if the leader will assign AS IDs for scheduling purposes.

[0113] <Preamble and midamble> 14 is a diagram illustrating a D2R preamble and a D2R midamble. The D2R preamble and the D2R midamble in a D2R transmission are used, for example, for synchronization in the time direction between a device and a reader.

[0114] As shown in Figure 14, the D2R preamble is transmitted before (at the beginning of) the PDRCH, the D2R midamble is transmitted in the middle of the PDRCH, and the D2R midamble may also be transmitted at the end of the PDRCH.

[0115] Figure 15 is a diagram illustrating type 1 D2R midambles and type 2 D2R midambles. As shown by arrows A15a and A15b in Figure 15, a D2R midamble in the middle of a PDRCH may be referred to as a type 1 D2R midamble. As shown by arrow A15c in Figure 15, a D2R midamble at the end of a PDRCH may be referred to as a type 2 D2R midamble.

[0116] A midamble may be inserted between different PDRCHs as shown in Figures 14 and 15. A midamble may also be inserted between two PDRCHs as shown in Figure 16. Note that PDRCHs divided by midambles as shown in Figures 14 and 15 may be grouped together to represent one PDRCH, and the same applies to Figures 17 and onwards.

[0117] The midamble may also be referred to as a non-preamble, a secondary preamble, or a secondary-amble.

[0118] <Considerations> There is no specific consideration for the configuration of D2R midambles, such as their existence, number, time resource, and time location. As a result, devices may not be able to properly configure the D2R preambles, and the devices and readers may not be synchronized.

[0119] Therefore, this disclosure provides a technique for configuring a D2R midamble. In this disclosure, the terms "configure" and "transmit" may be used interchangeably.

[0120] <Proposal 1> The device determines whether to transmit a D2R midamble based on a combination of the following options: In the present disclosure, options may be interpreted as conditions or rules.

[0121] <Proposal 1: Option 1> Whether a D2R midamble is transmitted is explicitly indicated in the R2D control information.

[0122] <Proposal 1: Option 2> Whether a D2R midamble is transmitted or not depends on the TBS (Transport Block Size) / number of information bits / duration / number of chips of the PDRCH.

[0123] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is equal to or greater than X, a D2R midamble is transmitted.

[0124] For example, if the PDRCH TBS / number of information bits / period / number of chips is less than X, then the D2R midamble is not transmitted.

[0125] <Proposal 1: Option 3> Whether the D2R midamble is transmitted depends on the message type of the PDRCH, such as Msg.1 / Msg.3 / D2R in step C2.

[0126] For example, a D2R midamble is transmitted for a certain message type A of the PDRCH.

[0127] For example, a D2R midamble is not transmitted for a certain message type B of the PDRCH.

[0128] <Proposal 1: Option 4> Whether a D2R midamble is transmitted depends on whether FEC (Forward Error Correction) is configured.

[0129] For example, if FEC is not configured in the PDRCH, the midamble is transmitted.

[0130] <Proposal 1: Notes> Only some of the options may be specified. Also, the options are not limited to those listed above. Other options may be added. Different options may be defined for Type 1 D2R midambles and Type 2 D2R midambles.

[0131] <Proposal 1: Detailed example of combination> As detailed examples of combinations, the following alt.1-alt.3 are provided.

[0132] <Proposal 1: Combination details: alt.1> If all options indicate that the D2R midamble is / is not transmitted, the D2R midamble is / is not transmitted. That is, if all options indicate that the D2R midamble is / is to be transmitted, the D2R midamble may be transmitted. Alternatively, if all options indicate that the D2R midamble is not to be transmitted, the D2R midamble may not be transmitted.

[0133] For example, if the R2D control information indicates D2R midamble transmission, and the TBS / number of information bits / period / number of chips of the PDRCH is X or more, and the D2R message type is message type A, then the D2R midamble is transmitted.

[0134] <Proposal 1: Combination details: alt.2> If at least one of the options indicates that the D2R midamble is / is not transmitted, the D2R midamble is / is not transmitted. That is, if at least one of the options indicates that the D2R midamble is / is to be transmitted, the D2R midamble may be transmitted. Alternatively, if at least one of the options indicates that the D2R midamble is not to be transmitted, the D2R midamble may not be transmitted.

[0135] For example, if the R2D control information indicates D2R midamble transmission, or the TBS / number of information bits / period / number of chips of the PDRCH is greater than or equal to X, or the D2R message type is message type A, then the D2R midamble is transmitted.

[0136] <Proposal 1: Combination details: alt.3> If different options determine whether a D2R midamble is to be transmitted, the device follows the option with the higher priority. For example, if different options indicate that the R2D control information should transmit a D2R midamble and the TBS / message type does not, the device follows the option with the higher priority.

[0137] The priority of options may be defined in the specification. For example, the order of options may be 3>2>1, 3>1>2, 1>2>3, 1>3>2, 2>1>3, or 2>3>1. · The priority of options may be different for different TBS / number of information bits / period / number of chips of PDRCH. · For different message types of D2R, the priority of options may be different. If option 2 / 3 is applied with high priority, the indication of R2D control information may be absent / ignored / reserved / used for other purposes.

[0138] Different substitutions may be applied to Type 1 and Type 2 D2R midambles.

[0139] A different priority of alt.3 may be applied to type 1 D2R midambles and type 2 D2R midambles.

[0140] <Proposal 1: Summary> The device determines whether to transmit a D2R midamble based on a combination of options 1 to 4. This allows the device to appropriately transmit a D2R midamble.

[0141] <Proposal 2> The device determines the gap between the D2R midamble and the D2R preamble (see double arrow A17a in Figure 17) / the gap between two adjacent D2R midambles (see double arrow A17b in Figure 17) based on a combination of the following options:

[0142] <Proposal 2: Option 1> The gap is explicitly indicated in the R2D control information, or may be indicated from a set of predefined values.

[0143] <Proposal 2: Option 2> The gap is based on the TBS / number of information bits / period / number of chips of the PDRCH.

[0144] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is equal to or less than X1, the gap is Y1.

[0145] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the gap is Y2.

[0146] <Proposal 2: Option 3> The gap is based on the message type of the PDRCH, such as Msg.1 / Msg.3 / D2R in step C2.

[0147] For example, the gap is Y1 for a certain message type A of the PDRCH.

[0148] For example, the gap is Y2 for a certain message type B of the PDRCH.

[0149] <Proposal 2: Option 4> The gap is based on the number of midambles.

[0150] <Proposal 2: Notes> Only some of the options may be specified. Also, the options are not limited to those listed above. Other options may be added. Different options may be defined for Type 1 D2R midambles and Type 2 D2R midambles.

[0151] <Proposal 2: Detailed example of combination> As detailed examples of combinations, the following alt.1-alt.3 are provided.

[0152] <Proposal 2: Combination details: alt.1> If different gap indications are determined from different options, the device follows the indication of the option with the higher priority. For example, if different gaps are indicated, such as R2D control information indicating one gap and TBS / message type indicating another gap, the device follows the indication of the option with the higher priority.

[0153] The priority of options may be defined in the specification. · The priority of options may be different for different TBS / number of information bits / period / number of chips of PDRCH. · For different message types of D2R, the priority of options may be different. If options 2 / 3 / 4 are applied with high priority, the R2D control information indication may be absent / ignored / reserved / used for other purposes.

[0154] Different substitutions may be applied to Type 1 and Type 2 D2R midambles.

[0155] A different priority of alt.1 may be applied to type 1 D2R midambles and type 2 D2R midambles.

[0156] <Proposal 2: Combination details: alt.2> The gap is explicitly indicated in the R2D control information. alt.2 can be seen as a variation of option 1.

[0157] The gap may be dictated from a predefined set of values. · Different sets of values ​​may be predefined for different TBS / number of information bits / period / number of chips of the PDRCH. · Different sets of values ​​may be predefined for different message types of the PDRCH.

[0158] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is equal to or less than X1, the gap is indicated by {Y1, Y2}.

[0159] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the gap is indicated by {Y3, Y4}.

[0160] For example, a gap is indicated from {Y1, Y2} for a certain message type A of the PDRCH.

[0161] For example, a gap is indicated from {Y3, Y4} for a certain message type B of the PDRCH.

[0162] <Proposal 2: Details of Option 4 1> The following alt.1 and alt.2 are provided regarding whether the number of midambles indicated by <Proposal 2: Option 4> above includes a Type 2 D2R midamble.

[0163] <Proposal 2:Details of Option 4 1:alt.1> The number of midambles indicated is the number of type 1 D2R midambles.

[0164] <Suggestion 2: Option 4 Details 1: alt.2> The number of midambles indicated is the number of "type 1 D2R midambles + type 2 D2R midambles."

[0165] <Proposal 2: Details of Option 4 2> The gap between a D2R midamble and a D2R preamble / the gap between two adjacent D2R midambles is calculated based on the number of midambles and the TBS / number of information bits / period / number of chips of the PDRCH.

[0166] In the following equations (1) and (2), "G" indicates a gap. "N" indicates the number of midambles. "D" indicates the TBS / number of information bits / period / number of chips of the PDRCH. Note that "N" is the number of Type 1 D2R midambles, and Type 2 D2R midambles may be added.

[0167] <Proposal 2:Details of Option 4 2:alt.1>

number

[0168] <Suggestion 2: Option 4 Details 2: alt.2>

number

[0169] <Proposal 2: Summary> The device determines the gap of the D2R midamble based on a combination of options 1 to 4. This allows the device to appropriately set the gap of the D2R midamble.

[0170] <Proposal 3> Devices determine the number of midambles by combining options: Proposal 3 replaces "gap" in Proposal 2 with "number", and Proposal 2 option 4 replaces "number" with "gap".

[0171] <Proposal 3: Option 1> The number of midambles is explicitly indicated in the R2D control information, or may be indicated from a set of predefined values.

[0172] <Proposal 3: Option 2> The number of midambles is based on the TBS / number of information bits / period / number of chips of the PDRCH.

[0173] For example, if the number of TBS / information bits / period / chips of the PDRCH is X1 or less, the number of midambles is Y1.

[0174] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the number of midambles is Y2.

[0175] <Proposal 3: Option 3> The number of midambles depends on the message type of the PDRCH, such as Msg.1 / Msg.3 / D2R in step C2.

[0176] For example, the number of midambles is Y1 for a certain message type A of the PDRCH.

[0177] For example, the number of midambles is Y2 for a certain message type B of the PDRCH.

[0178] <Proposal 3: Option 4> The number of midambles is based on the gap.

[0179] <Proposal 3: Notes> Only some of the options may be specified. Also, the options are not limited to those listed above. Other options may be added. Different options may be defined for Type 1 D2R midambles and Type 2 D2R midambles.

[0180] <Proposal 3: Detailed example of combination> As detailed examples of combinations, the following alt.1-alt.3 are provided.

[0181] <Proposal 3: Combination details: alt.1> If different options indicate different numbers of midambles, the device follows the instruction of the option with the higher priority. For example, if different numbers of midambles are indicated, such as R2D control information indicating one number of midambles and TBS / message type indicating another number of midambles, the device follows the instruction of the option with the higher priority.

[0182] The priority of options may be defined in the specification. · The priority of options may be different for different TBS / number of information bits / period / number of chips of PDRCH. · For different message types of D2R, the priority of options may be different. If options 2 / 3 / 4 are applied with high priority, the indication of R2D control information may be absent / ignored / reserved / used for other purposes.

[0183] Different substitutions may be applied to Type 1 and Type 2 D2R midambles.

[0184] A different priority of alt.1 may be applied to type 1 D2R midambles and type 2 D2R midambles.

[0185] <Proposal 3: Combination details: alt.2> The number of midambles is explicitly indicated in the R2D control information. alt.2 can be seen as a variation of option 1.

[0186] The number of midambles may be dictated from a predefined set of values. · Different sets of values ​​may be predefined for different TBS / number of information bits / period / number of chips of the PDRCH. Different sets of values ​​may be predefined for different message types of the PDRCH.

[0187] For example, if the number of TBS / information bits / period / chips of the PDRCH is equal to or less than X1, the number of midambles is indicated by {Y1, Y2}.

[0188] For example, if the number of TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the number of midambles is indicated by {Y3, Y4}.

[0189] For example, the number of midambles is indicated by {Y1, Y2} for a certain message type A of the PDRCH.

[0190] For example, the number of midambles is indicated by {Y3, Y4} for a certain message type B of the PDRCH.

[0191] <Proposal 3: Details of Option 4 1> Regarding whether the number of midambles determined by <Proposal 3: Option 4> above includes a Type 2 D2R midamble, the following alt.1 and alt.2 are provided.

[0192] <Proposal 3: Option 4 Details 1: alt.1> The number of gaps indicated is the number of Type 1 D2R midambles.

[0193] <Proposal 3: Option 4 Details 1: alt.2> The number of gaps indicated is the number of "type 1 D2R midambles + type 2 D2R midambles."

[0194] <Proposal 3: Details of Option 4 2> The number of D2R midambles is determined based on the gap and the TBS / number of information bits / period / number of chips of the PDRCH.

[0195] <Proposal 3: Summary> The device determines the number of D2R midambles based on a combination of options 1 to 4. This allows the device to appropriately set the number of D2R midambles.

[0196] <Suggestion 4> Devices determine the length / sequence / pattern of the D2R midamble by a combination of options. In proposal 4, the "gap" of proposal 2 is replaced by "length / sequence / pattern."

[0197] <Proposal 4: Option 1> The length / sequence / pattern of the D2R midamble is explicitly indicated in the R2D control information. The length / sequence / pattern of the D2R midamble may be indicated from a set of predefined values.

[0198] <Proposal 4: Option 2> The length / sequence / pattern of the D2R midamble is based on the TBS / number of information bits / duration / number of chips of the PDRCH.

[0199] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is less than or equal to X1, the length / sequence / pattern of the D2R midamble is Y1.

[0200] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the length / sequence / pattern of the D2R midamble is Y2.

[0201] <Proposal 4: Option 3> The length / sequence / pattern of the D2R midamble is based on the message type of the PDRCH, such as Msg.1 / Msg.3 / D2R in step C2.

[0202] For example, the length / sequence / pattern of the D2R midamble is Y1 for a certain message type A of the PDRCH.

[0203] For example, the length / sequence / pattern of the D2R midamble is Y2 for a certain message type B of the PDRCH.

[0204] <Proposal 4: Option 4> The length / sequence / pattern of the D2R midamble is based on the number of midambles.

[0205] <Proposal 4: Notes> Only some of the options may be specified. Also, the options are not limited to those listed above. Other options may be added. Different options may be defined for Type 1 D2R midambles and Type 2 D2R midambles.

[0206] <Proposal 4: Detailed example of combination> As detailed examples of combinations, the following alt.1-alt.3 are provided.

[0207] <Proposal 4: Combination details: alt.1> If different options determine different D2R midamble length / sequence / pattern instructions, the device follows the instruction of the option with the higher priority. For example, if different D2R midamble length / sequence / patterns are indicated, such as R2D control information indicating one D2R midamble length / sequence / pattern and TBS / message type indicating another D2R midamble length / sequence / pattern, the device follows the instruction of the option with the higher priority.

[0208] The priority of options may be defined in the specification. · The priority of options may be different for different TBS / number of information bits / period / number of chips of PDRCH. · For different message types of D2R, the priority of options may be different. If options 2 / 3 / 4 are applied with high priority, the R2D control information indication may be absent / ignored / reserved / used for other purposes.

[0209] Different substitutions may be applied to Type 1 and Type 2 D2R midambles.

[0210] A different priority of alt.1 may be applied to type 1 D2R midambles and type 2 D2R midambles.

[0211] <Proposal 4: Combination details: alt.2> The length / sequence / pattern of the D2R midamble is explicitly indicated in the R2D control information. alt.2 can be seen as a variation of option 1.

[0212] The length / sequence / pattern of the D2R midamble may be dictated from a predefined set of values. · Different sets of values ​​may be predefined for different TBS / number of information bits / period / number of chips of the PDRCH. Different sets of values ​​may be predefined for different message types of the PDRCH.

[0213] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is less than or equal to X1, the length / sequence / pattern of the D2R midamble is indicated by {Y1, Y2}.

[0214] For example, if the TBS / number of information bits / period / number of chips of the PDRCH is greater than X1 and less than or equal to X2, the length / sequence / pattern of the D2R midamble is indicated by {Y3, Y4}.

[0215] For example, the length / sequence / pattern of the D2R midamble is indicated by {Y1, Y2} for a certain message type A of the PDRCH.

[0216] For example, the length / sequence / pattern of the D2R midamble is indicated by {Y3, Y4} for a certain message type B of the PDRCH.

[0217] <Proposal 4: Details of Option 4 1> Regarding whether the number of D2R midambles indicated by <Proposal 4: Option 4> above includes a Type 2 D2R midamble, the following alt.1 and alt.2 are provided.

[0218] <Proposal 4:Details of Option 4 1:alt.1> The number of midambles indicated is the number of type 1 D2R midambles.

[0219] <Proposal 4:Details of Option 4 1:alt.2> The number of midambles indicated is the number of "type 1 D2R midambles + type 2 D2R midambles."

[0220] <Proposal 4: Details of Option 4 2> The length / sequence / pattern of the D2R midamble is determined based on the number of midambles and the TBS / number of information bits / duration / number of chips of the PDRCH.

[0221] <Proposal 4: Summary> The device determines the length / sequence / pattern of the D2R midamble based on a combination of options 1 to 4. This allows the device to appropriately set the length / sequence / pattern of the D2R midamble.

[0222] <Suggestion 5> The following parameters are jointly indicated in the R2D control information:

[0223] Whether the D2R midamble is transmitted Gap between D2R midamble and D2R preamble / Gap between two adjacent midambles Number of midambles D2R midamble length / sequence / pattern Other parameters such as TBS / number of information bits / period / number of chips / message type

[0224] <Proposal 5: Notes> Only some of the parameters (information) may be indicated. Furthermore, the jointly indicated parameters are not limited to those listed above. Other parameters may be added. Different parameters may be defined for Type 1 D2R midambles and Type 2 D2R midambles.

[0225] Regarding parameter indication, the following alt.1 to alt.3 are provided.

[0226] <Proposal 5:alt.1> The indication field in the R2D control information is used for joint indication. Each code point in the indication field in the R2D control information is mapped to multiple parameters (see, for example, FIG. 18).

[0227] <Proposal 5: alt.2> A specific code point in the indication field for gap / number / length / sequence of D2R midambles in the R2D control information is used to indicate that "D2R midambles are not transmitted."

[0228] For example, if gap / number / length is indicated as "0", no D2R midamble is transmitted.

[0229] For example, if the code point value is "Z", the D2R midamble is not transmitted.

[0230] <Proposal 5:alt.3> A fixed association / relationship is defined between the two parameters.

[0231] For example, if the value / value range of one parameter (e.g., gap / number) is designated as X, the device will assume that the value / value range of another parameter (e.g., length / sequence) is Y.

[0232] <Proposal 5: Summary> The parameters described in each proposal are jointly indicated in the R2D control information. This is expected to balance the overhead and flexibility of the R2D control information. The overhead of the R2D control information can be reduced.

[0233] <Suggestion 6> Depending on the gap between two adjacent midambles and the length of the PDRCH, the length of the last PDRCH segment transmitted after the last D2R midamble may be short. For example, assuming that the gap between two adjacent midambles is 100 chips and the duration of the PDRCH is 806 chips, the last PDRCH segment will be 6 chips (see arrow A19a in FIG. 19). Thus, if the length of the last segment of the PDRCH is short, the last D2R midamble (see arrow A19b in FIG. 19) may not be as long for SFO (sampling frequency offset) calibration of the last segment of the PDRCH.

[0234] Therefore, the device determines whether to insert a D2R midamble between the last segment of the PDRCH and the previous segment of the PDRCH based on the length (chips) of the last segment of the PDRCH.

[0235] For example, let "D" be the TBS / number of information bits / period / number of chips of the PDRCH, and "G" be the gap between two adjacent D2R midambles. If mod(D, G) is equal to or greater than a threshold, the last D2R midamble is transmitted before the last PDRCH of mod(D, G) (see arrow A20a in FIG. 20). In this case, the number of D2R midambles "N" is given by the following equation (3):

[0236]

number

[0237]

number

[0238] <Suggestion 6: Notes> "D2R midamble" in Proposal 6 refers to "Type 1 D2R midamble", but a Type 2 D2R midamble may be added to the end of the PDRCH.

[0239] <Proposal 6: Summary> The device determines whether to insert a D2R midamble between the last segment of the PDRCH and the previous segment of the PDRCH based on the length (chips) of the last segment of the PDRCH. This allows the device to transmit the PDRCH properly. The device can also reduce the PDRCH overhead caused by the D2R midamble.

[0240] <Variations> The above proposals, options, and alts may be combined. Proposal 2 to Proposal 4 may include Option 4 of Proposal 1. For example, the gap / number of midambles / length / sequence / pattern of D2R midamble may be based on FEC.

[0241] <Base station configuration> 22 is a block diagram showing an example of a configuration of a base station 10 according to an embodiment of the present disclosure. 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. 23) wirelessly. The base station 10 may be an intermediate node or a CW node.

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

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

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

[0245] The reference signals 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.

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

[0247] 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. For example, the control unit 103 performs operations other than the transmission and reception described in the above embodiment (note that these operations may be performed by the reception unit 102 and / or the transmission unit 101).

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

[0249] 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 a signal (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.

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

[0251] Here, the transmitting unit 101 may transmit control information. The control information may be R2D control information. The control information may include an explicit instruction as to whether or not to transmit a midamble of an uplink signal. The uplink signal may be a PDRCH or a D2R.

[0252] The control unit 103 may consider transmitting an uplink signal based on the conditions described below. In other words, the control unit 103 may decide to receive an uplink signal based on the conditions described below.

[0253] <Device configuration> 23 is a block diagram illustrating an example of a configuration of a device 20 according to an embodiment of the present disclosure. The device 20 is a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, such as an A-IoT UE. The device 20 may be considered to be a device that receives power through energy harvesting. For example, the device 20 may be considered to be a device that receives power through a CW supplied from the base station 10.

[0254] The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with, for example, the base station 10 wirelessly. The device 20 may be, for example, an A-IoT device.

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

[0256] The transmitter 202 transmits the UL signal to the base station 10. For example, the transmitter 202 transmits the UL signal under the control of the controller 203.

[0257] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capabilities of the device 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

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

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

[0260] The control unit 203 controls the communication operations of the device 20, including the reception process in the reception unit 201 and the transmission process in the transmission unit 202.

[0261] For example, the control unit 203 acquires information such as data and control information from a higher 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 higher layer.

[0262] 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, 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 in the resources of the PUCCH.

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

[0264] 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 Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0265] Here, the receiving unit 201 may receive control information. The control information may be R2D control information.

[0266] The control unit 203 may determine whether to transmit the midamble of the uplink signal based on at least any combination of the following conditions.

[0267] Explicit indication of control information Transport block size and / or number of information bits and / or period and / or number of chips of the uplink signal Upstream signal message type Error correction settings for upstream signals

[0268] The uplink signal may be a PDRCH or a D2R. The conditions are not limited to the above. The control unit 203 may determine whether to transmit the midamble of the uplink signal based on one of the above conditions.

[0269] The control unit 203 may decide to transmit a midamble when all of the combinations of conditions indicate that a midamble should be transmitted.

[0270] The control unit 203 may decide to transmit a midamble if one of the combinations of conditions indicates that a midamble should be transmitted.

[0271] When a combination of conditions indicates different instructions regarding the transmission of a midamble, the control unit 203 may determine the transmission of the midamble based on the priority assigned to the conditions.

[0272] The control unit 203 may determine the gap between the preamble and midamble of the uplink signal and / or the gap between adjacent midambles based on a combination of conditions.

[0273] The control unit 203 may determine the number of midambles based on a combination of conditions.

[0274] The control unit 203 may determine the length / sequence / pattern of the D2R midamble based on a combination of conditions.

[0275] In the control information, the following parameters may be jointly indicated:

[0276] Whether the D2R midamble is transmitted Gap between D2R midamble and D2R preamble / Gap between two adjacent midambles Number of midambles D2R midamble length / sequence / pattern Other parameters such as TBS / number of information bits / period / number of chips / message type

[0277] The control unit 203 may determine whether to insert a midamble between the last segment of the uplink signal and the previous segment of the uplink signal based on the length of the last segment of the uplink signal, which may be in chips.

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

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

[0280] <Hardware configuration> 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 (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0281] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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.

[0282] For example, a base station (reader), 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. 24 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. 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.

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

[0284] Each function in the base station 10 and the device 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the 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 the storage 1003.

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

[0286] 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 these. 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 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 made 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.

[0287] The memory 1002 is a computer-readable recording medium and may be configured, for example, by 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.

[0288] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy 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.

[0289] 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, or a communication module. 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.

[0290] The input device 1005 is an input device (for example, 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 (for example, 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 (for example, a touch panel).

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

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

[0293] <Information notification, signaling> The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the 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.

[0294] <Applicable systems> Each aspect / embodiment described in the present disclosure may be any of the following: 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 decimal number)), 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 The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate 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 at least one of LTE and LTE-A with 5G).

[0295] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.

[0296] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may 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, but not limited to, an MME or an S-GW). 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.

[0297] <Input / output direction> Information, etc. (see the section on information and signals) 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.

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

[0299] <Judgment 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 numerical comparison (e.g., comparison with a predetermined value).

[0300] <Variations in form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, 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).

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

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

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

[0304] <Information, Signals> The 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. that 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.

[0305] Note that terms explained 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.

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

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

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

[0309] <Base station> In this 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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0310] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

[0312] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

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

[0314] <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 a mobile object that moves autonomously 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.

[0315] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the aspects / 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.

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

[0317] Fig. 25 shows an example configuration of a vehicle 2001. As shown in Fig. 25, 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.

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

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

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

[0321] 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 information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

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

[0323] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

[0326] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-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-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.

[0327] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices 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)).

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

[0329] <Terminology and interpretation> 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 in a table, database, or other data structure), ascertaining, 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. 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.

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

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

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

[0333] <"First", "Second"> As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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 in some way precede the second element.

[0334] <Means> In the configuration of each of the above-described devices, the "means" may be replaced with a "section", "circuit", "device", or the like.

[0335] <Open format> In the present disclosure, when the terms "include", "including", and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is intended not to be an exclusive disjunction.

[0336] <Time units such as TTI, frequency units such as RB, 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 referred to as a subframe. A subframe may further be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

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

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

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

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

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

[0342] 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. However, the definition of TTI is not limited to this.

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

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

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

[0346] 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 equal to or greater than 1 ms.

[0347] A resource block (RB) is a resource allocation unit in the time domain and 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 also be determined based on numerology.

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

[0349] 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, or the like.

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

[0351] 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 given BWP and numbered within that BWP.

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

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

[0354] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, 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. may be changed in various ways.

[0355] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0356] <Article> 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.

[0357] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." 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." [Industrial Applicability]

[0358] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0359] 10 base station 20 devices 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. 1. A device powered by energy harvesting, comprising: a receiving unit for receiving control information; At least the following conditions: - Explicit indication of the control information Transport block size and / or number of information bits and / or period and / or number of chips of uplink signal Message type of the upstream signal - Setting of error correction for the upstream signal a control unit that determines whether to transmit a midamble of the uplink signal based on any combination of the above; A device having

2. the control unit determines to transmit the midamble when all of the combinations of conditions indicate transmission of the midamble. The device of claim 1 .

3. the control unit determines to transmit the midamble when at least one of the combinations of conditions indicates transmission of the midamble. The device of claim 1 .

4. When the combination of conditions indicates different instructions regarding the transmission of the midamble, the control unit determines to transmit the midamble based on priorities assigned to the conditions. The device of claim 1 .

5. the control unit determines a gap between the preamble and the midamble of the uplink signal and / or a gap between adjacent midambles based on the combination of conditions. The device of claim 1 .

6. the control unit determines the number of midambles based on the combination of conditions. The device of claim 1 .

Images