Device and communication method

Abstract

Provided is a technology for appropriately discriminating between a control information portion and / or a data portion of a signal and a preamble, midamble, and / or postamble portion thereof. This device has a lower complexity than a narrow band Internet of Things (NB-IoT) device and comprises: a control unit that determines a border position in a temporal region, in a signal which includes a timing acquisition information portion and a control information portion or a data portion and is transmitted to the device, between the timing acquisition information portion and the control information portion or the data portion, on the basis of a bit sequence used for the timing acquisition information portion and a bit sequence used for the control information portion or the data portion; and a reception unit that starts or ends reception of the timing acquisition information portion at the border position.

Description

Device and communication method

[0001] The present disclosure relates to devices and communication methods.

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

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

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

[0005] In a communication system including an ambient IoT device, synchronization accuracy in the time and frequency domains is low. To compensate for this, it is expected that a preamble, a midamble, and / or a postamble are added to a control signal and / or a data signal before transmission and reception. However, it is unclear how to determine the boundary (especially in the time domain) between the control information portion and / or the data portion and the preamble, midamble, and / or the postamble portion. If the ambient IoT device cannot determine such a boundary, it may not be able to properly transmit and receive the channel and / or the signal, which may result in degradation of system performance. Therefore, a technology for determining the control information portion and / or the data portion and the preamble, midamble, and / or the postamble portion during signal transmission and reception is desired.

[0006] One aspect of the present disclosure provides a device and a communication method that can distinguish between a control information portion and / or a data portion and a preamble, midamble, and / or postamble portion in a signal in a communication system including an ambient IoT device.

[0007] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes: a control unit that determines a boundary position in the time domain between a timing acquisition information portion and a control information portion or a data portion in a signal including the timing acquisition information portion and the control information portion or the data portion, the boundary position being transmitted to the device, based on a bit sequence used for the timing acquisition information portion and a bit sequence used for the control information portion or the data portion; and a receiving unit that starts or ends reception of the timing acquisition information portion at the boundary position.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL assistance. FIG. 3 is a diagram illustrating Topology 4 in UL assistance. FIG. 4 is a diagram illustrating backscatter transmission. FIG. 1 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in Topology 1. FIG. 2 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in Topology 2. FIG. 3 is a diagram illustrating an example of a configuration of a preamble, control / data, and midamble used in R2D / D2R transmission. FIG. 4 is a diagram illustrating an example of a configuration of a control / data and postamble used in R2D / D2R transmission. FIG. 5 is a diagram illustrating an example of an R2D midamble sequence. FIG. 6 is a diagram illustrating an example of constraints that an R2D midamble should satisfy. FIG. 7 is a diagram illustrating an example of constraints that an R2D midamble should satisfy. FIG. 8 is a diagram illustrating an example of R2D control / data signaled by an R2D midamble. FIG. 9 is a diagram illustrating an example of a reference point relative to the start of the time domain position of an R2D midamble. 1 is a diagram illustrating an example of a reference point relative to the start of an R2D midamble's time domain location. 2 is a diagram illustrating an example of a reference point relative to the start of an R2D midamble's time domain location. 3 is a diagram illustrating an example of a reference point relative to the start of an R2D midamble's time domain location. 4 is a diagram illustrating a duration of an R2D or D2R control / data transmission. 5 is a diagram illustrating an example of an A-IoT device's operation according to an embodiment of the present disclosure. 6 is a diagram illustrating an example of an A-IoT device's operation according to an embodiment of the present disclosure. 7 is a diagram illustrating a boundary between a midamble and control / data. 8 is a diagram illustrating an example of a Manchester coded "0" indicating or signaling the preamble itself. 9 is a diagram illustrating an example of a Manchester coded "1" indicating or signaling the start of a midamble. 10 is a diagram illustrating an example of an NRZ coded "0" applied to the end of a preamble, with Manchester coding applied to the (remaining) previous portion of the preamble. 11 is a diagram illustrating an example of an NRZ coded "0" applied to the start of a midamble, with Manchester coding applied to the (remaining) subsequent portion of the midamble.FIG. 1 is a diagram showing an example in which a certain (specific) bit sequence by NRZ encoding is applied to a midamble. FIG. 2 is a diagram showing an example in which "1" by NRZ encoding is applied to a postamble. FIG. 3 is a diagram showing an example in which different amplitudes are applied to a preamble / midamble / postamble and a control / data portion when ASK is applied. FIG. 4 is a diagram showing an example in which different CP values ​​are applied to a preamble / midamble / postamble and a control / data portion when OFDM is applied. FIG. 5 is a block diagram showing an example of a configuration of a base station according to an embodiment of the present disclosure. FIG. 6 is a block diagram showing an example of a configuration of a device according to an embodiment of the present disclosure. FIG. 7 is a diagram showing an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure. FIG. 8 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] In this embodiment, DL and R2D (reader to device) may be interchangeable, and UL and D2R (device to reader) may be interchangeable, where the reader corresponds to a BS and / or an intermediate UE, and the device corresponds to an 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 that transmits the CW (CW node) is different from the node that transmits the R2D communication signal (BS). Also, in topology 1C, the node that transmits the CW is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in topology 1C, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR (network-controlled repeater) node / relay node / other type of node.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] Postambles are also considered. Postambles may be used to signal the end of R2D / D2R transmissions in the time domain. As shown in Figure 11, the R2D postamble may be placed at the end of the R2D control / data transmission (after the last R2D control / data), and the D2R postamble may be placed at the end of the R2D control / data transmission (after the last D2R control / data).

[0083] <Analysis> As mentioned above, the use of midambles for timing acquisition is being considered. However, the details of the time resources (or time domain resources) of the R2D midamble and D2R midamble have not been clarified. If an A-IoT device cannot properly determine the time resources of the R2D midamble / D2R midamble, it may not be able to maintain timing as accurately as if there were no R2D midamble / D2R midamble. As a result, R2D / D2R may not be transmitted or received properly, which may result in degradation of system performance.

[0084] Furthermore, when an A-IoT device receives a PRDCH or other R2D channel / signal, it is unclear how it determines or identifies the boundaries between the control information and / or data portions and the preamble, midamble, and / or postamble portions in the R2D (more specifically, how it determines the start / end of the control information and / or data portions and the start / end of the preamble, midamble, and / or postamble) (see FIG. 24). Similarly, when a base station / intermediate UE receives a PRDCH or other D2R channel / signal, it is unclear how it determines or identifies the boundaries between the control information and / or data portions and the preamble, midamble, and / or postamble portions in the D2R (more specifically, how it determines the start / end of the control information and / or data portions and the start / end of the preamble, midamble, and / or postamble) (see FIG. 24). If the ambient IoT device / base station / intermediate UE cannot determine such boundaries, it may not be able to transmit and receive R2D / D2R properly, resulting in degraded system performance.

[0085] Therefore, below we will explain proposals related to the time resources of R2D midambles and D2R midambles communicated in communication systems including A-IoT devices (Proposal 1 regarding R2D (Proposals 1-1 to 1-3) and Proposal 2 regarding D2R (Proposals 2-1 to 2-3)), and Proposal 3 (Proposals 3-1 to 3-3) for distinguishing the control information portion and / or data portion in R2D / D2R from the preamble, midamble and / or postamble.

[0086] The items explained in the following Proposals 1-1 to 1-3, Proposals 2-1 to 2-3, and Proposals 3-1 to 3-3 may be combined as appropriate, provided that no contradictions arise.

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

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

[0089] In the following, notifications may be carried in the physical (PHY) layer / MAC (Medium Access Control) layer / RRC (Radio Resource Control) layer / a new layer defined for A-IoT.

[0090] In the following, a "time unit" may be 1 symbol / multiple symbols / 1 slot / multiple slots / 1 microsecond / multiple microseconds / 1 millisecond / multiple milliseconds / or any other time unit defined for A-IoT.

[0091] Proposal 1 regarding R2D transmission will now be described.

[0092] <Proposal 1-1> First, a proposal (Proposal 1-1) regarding the design and constraints of the R2D midamble will be described.

[0093] The A-IoT device does not know the exact time domain position of the R2D midamble before detection. That is, the A-IoT device can know the exact time domain position of the R2D midamble by blind decoding the R2D midamble. The R2D midamble will be described in detail below.

[0094] The R2D midamble may be a sequence. Here, the R2D midamble sequence should be distinguishable from the R2D control / data information bits, the R2D preamble, and the R2D postamble. That is, the A-IoT device does not (falsely) detect the R2D midamble as the R2D control / data information, the R2D preamble, or the R2D postamble, and does not (falsely) detect the R2D control / data information, the R2D preamble, or the R2D postamble as the R2D midamble. Such distinction may be based on the coding scheme / design of the information bits "0" and "1" / design of the R2D preamble, the R2D midamble, and the R2D postamble (including the sequence type / format, sequence length, etc.). That is, the A-IoT device may identify or detect the R2D midamble based on the coding scheme / design of the information bit "0" and information bit "1" / design of the R2D preamble, R2D midamble, and R2D postamble. Note that this may also apply to the R2D preamble / R2D postamble. That is, each of the R2D midamble, R2D preamble, R2D postamble, and R2D control / data information bits should be able to be distinguished from one another.

[0095] 12 is a diagram illustrating an example of an R2D midamble sequence. As shown in FIG. 12, the R2D midamble sequence (e.g., "x", "x", "y", "x") may be different from the R2D control / data ("0", "1") and may be different from the R2D preamble and R2D postamble sequences (not shown).

[0096] However, the R2D midamble may be the same as or similar to the R2D preamble, and may be the same as or similar to the R2D postamble. For example, in one design, an A-IoT device may not need to distinguish between an R2D midamble and an R2D preamble, and in another design, an A-IoT device may not need to distinguish between an R2D midamble and an R2D postamble.

[0097] The sequence of the R2D midamble may be specified in the specifications, may be notified to the A-IoT device by the base station 10, intermediate UE, etc., or may be set in advance. As a variation of this, multiple sequences of the R2D midamble may be specified in the specifications or may be set, and one sequence of the multiple sequences may be notified to the A-IoT device by the base station 10, intermediate UE, etc.

[0098] Several constraints (or limitations or requirements) may be specified in the specification, and the A-IoT device may assume that the transmission of the R2D midamble satisfies one or more of these constraints (e.g., all of the constraints). Examples of constraints are: - Minimum duration in the time domain of R2D control / data transmission between the R2D preamble and the R2D midamble #1a - Maximum duration in the time domain of R2D control / data transmission between the R2D preamble and the R2D midamble #1b - Minimum duration in the time domain of R2D control / data transmission between two R2D midambles #2a - Maximum duration in the time domain of R2D control / data transmission between two R2D midambles #2b - Minimum duration in the time domain of R2D control / data transmission between the R2D midamble and the R2D postamble #3a - Maximum duration in the time domain of R2D control / data transmission between the R2D midamble and the R2D postamble #3b

[0099] With respect to minimum duration #1a and maximum duration #1b, "between the R2D preamble and the R2D midamble" may be from the end of the R2D preamble / start of the R2D control / data to the end of the R2D midamble / R2D control / data, or from the end of the R2D preamble / start of the R2D control / data to the end of the R2D midamble / R2D control / data. Note that the end of the R2D preamble and the start of the R2D control / data may be the same or different. Similarly, the start of the R2D midamble and the end of the R2D control / data may be the same or different. Similarly, the end of the R2D midamble and the start of the R2D control / data may be the same or different. 13 is a diagram showing an example of constraints that the R2D midamble must satisfy, and an example of the temporal relationship between the R2D preamble and the R2D midamble. As shown in FIG. 13, for example, the end of the R2D midamble may be located between minimum duration #1a and maximum duration #1b from the end of the R2D preamble.

[0100] With respect to minimum duration #2a and maximum duration #2b, "between two R2D midambles" may be from the end point / R2D control / data of the earlier (earlier) of the two R2D midambles to the start point / R2D control / data of the later (later) of the two R2D midambles, or from the end point / R2D control / data of the earlier (earlier) of the two R2D midambles to the start point / R2D control / data of the later (later) of the two R2D midambles. Figure 14 is a diagram showing examples of constraints that R2D midambles must satisfy, and is a diagram showing an example of the temporal relationship between two R2D midambles. As shown in FIG. 14, for example, the end point of the later of the two R2D midambles may be located between minimum duration #2a and maximum duration #2b from the end point of the earlier of the two R2D midambles.

[0101] With respect to minimum duration #3a and maximum duration #3b, "between the R2D midamble and the R2D postamble" may mean from the end of the R2D midamble / start of the R2D control / data to the start of the R2D postamble / R2D control / data, or from the end of the R2D midamble / start of the R2D control / data to the end of the R2D postamble. Note that the start of the R2D postamble and the end of the R2D control / data may be the same or different. Figure 15 is a diagram showing an example of constraints that the R2D midamble must satisfy, and is a diagram showing an example of the temporal relationship between the R2D midamble and the R2D postamble. As shown in Figure 15, for example, the start of the R2D postamble may be located between the end of the R2D midamble and the minimum duration #3a and the maximum duration #3b.

[0102] Minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b may be determined according to the A-IoT device type (e.g., Device 1 / 2a / 2b described above), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., Topology 1 or Topology 2 described above)), band used for R2D transmission, etc. That is, the A-IoT device may determine minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b according to the A-IoT device type / device capability / connection topology / band used for R2D transmission, etc.

[0103] Minimum duration #1a / minimum duration #2a / minimum duration #3a may be the same or different values. Minimum duration #1b / minimum duration #2b / minimum duration #3b may be the same or different values.

[0104] Whether or not the R2D midamble is included in the R2D may be determined according to rules defined in the specifications, or may be notified to the A-IoT device by the base station 10, an intermediate UE, or the like, or may be set in advance. For example, whether or not the R2D midamble is included in the R2D may be (implicitly) notified via the R2D preamble by using a different preamble sequence / format, or the like. As a more specific example, if the R2D midamble is included in the R2D, sequence A may be used for the R2D preamble, and if the R2D midamble is not included in the R2D, a sequence other than sequence A may be used for the R2D preamble. For example, the A-IoT device may determine whether or not the R2D midamble is included in the R2D based on a notification from the base station 10, an intermediate UE, or the like (the notified information may be referred to as information regarding the presence or absence of the R2D midamble, or the like).

[0105] [Variation of Proposal 1-1] As described above, the start point of the R2D midamble and the end point of the R2D control / data may be the same or different. Similarly, the end point of the R2D midamble and the start point of the R2D control / data may be the same or different. If the start point and end point are different, the A-IoT device may not be able to identify the R2D control / data. Therefore, as shown in FIG. 16, the R2D midamble may notify the end point of the R2D control / data immediately before the R2D midamble, or may notify the start point of the R2D control / data immediately after the R2D midamble. Such notification of the R2D midamble allows the A-IoT device to identify the R2D control / data.

[0106] <Proposal 1-2> Next, a proposal (Proposal 1-2) regarding the time domain position of the R2D midamble will be described.

[0107] The time domain location of the R2D midamble may be notified to the A-IoT device by the base station 10, intermediate UE, etc., or may be determined by the A-IoT device according to rules defined in the specification.

[0108] The time domain position of the R2D midamble will be described in detail below. Note that the offset and duration of the R2D midamble described below may be referred to as a period (first period) (from a reference point described below) for starting reception of the R2D midamble and a period (second period) for receiving the R2D midamble, respectively. For example, an A-IoT device may start receiving the R2D midamble after the first period from the reference point, or may receive the R2D midamble within the second period after the first period.

[0109] [Option 1] The duration of the R2D midamble in the time domain may be specified in the specification.

[0110] [Option 2] The duration of the R2D midamble may be signaled to the A-IoT device by the base station 10, an intermediate UE, etc. as a number of time units. The signaled information may be referred to as information about the R2D midamble, information about the R2D midamble transmission time, etc. For example, the duration of the R2D midamble may be signaled to the A-IoT device via an R2D preamble (e.g., a preamble sequence / format, etc.). For example, when the A-IoT device receives an R2D preamble of a certain sequence / format, it may determine or identify the duration of the R2D midamble associated with the certain sequence / format. As another example, the duration of the R2D midamble may be signaled to the A-IoT device via R2D control / data. That is, the A-IoT device may determine or identify the duration of the R2D midamble by decoding the R2D control / data.

[0111] [Option 3] Each sequence of the R2D midamble may have a fixed duration defined by the specification. The A-IoT device may determine or specify the duration of the R2D midamble based on the sequence used.

[0112] [Option 4] A correspondence (or mapping) between the duration of the R2D midamble and the duration of the R2D control / data transmission may be specified, signaled to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or specify the duration of the R2D midamble based on the correspondence. The duration of the R2D control / data transmission is described below in Proposals 1-3.

[0113] [Option 5] A correspondence between the duration of the R2D midamble and the type / format (e.g., a format similar to the DCI format, etc.) / size (number of bits) of the R2D control / data transmission may be specified in a specification, or may be notified to the A-IoT device by the base station 10, an intermediate UE, etc., or may be set in advance. The A-IoT device may determine or specify the duration of the R2D midamble based on the correspondence. For example, the correspondence may be such that the larger the size of the R2D control / data transmission, the longer the duration of the R2D midamble.

[0114] Note that which of options 1 to 5 to apply may be determined according to the A-IoT device type (e.g., the above-mentioned device 1 / 2a / 2b), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., the above-mentioned topology 1 or topology 2)), etc. In other words, the A-IoT device may determine and apply an option according to the A-IoT device type, device capability, or connection topology.

[0115] Next, the reference point at the beginning of the time domain position of the R2D midamble will be described.

[0116] [Option 1] The reference point may be the beginning or end of a unit of time, for example the reference point may be the beginning of a particular or predetermined frame, slot, symbol, etc.

[0117] [Option 2] The reference point may be the beginning or end of the R2D preamble. For example, the reference point may be the beginning of the R2D preamble, as shown in Figure 17.

[0118] [Option 3] Assuming that the entire R2D control / data transmission consists of multiple parts and the R2D midamble may be transmitted between two parts, the reference point may be the beginning or end of the first R2D control / data transmission part after the R2D preamble (the part of the R2D control / data transmission immediately after the R2D preamble). For example, as shown in Figure 18, the reference point may be the beginning of the first R2D control / data transmission part (#1) after the R2D preamble.

[0119] [Option 4] Assuming that the entire R2D control / data transmission consists of multiple parts and the R2D midamble may be transmitted between two parts, the reference point may be the beginning or end of the part of the R2D control / data transmission immediately preceding the R2D midamble. For example, as shown in Figure 19, the reference point may be the beginning of the part (#2) of the R2D control / data transmission immediately preceding the R2D midamble.

[0120] [Option 5] The reference point may be the beginning or end of the previous R2D midamble in time. For example, as shown in Figure 20, the reference point may be the beginning of the immediately previous R2D midamble.

[0121] Next, the offset between the reference point and the beginning of the time domain position of the R2D midamble (see Figures 17 to 20) will be described.

[0122] The offset may be a number of time units, for example, the offset may be 2 slots, etc.

[0123] Multiple offsets may be determined, and multiple R2D midambles corresponding to the multiple offsets may be transmitted.

[0124] The offset may be defined / signaled as described in options 1-3 below.

[0125] [Option 1] The offset may be specified in the specification.

[0126] [Option 2] The offset may be signaled to the A-IoT device by the base station 10, intermediate UE, etc.

[0127] [Option 3] A mapping between the offset and the duration of the R2D control / data transmission may be specified, signaled to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or identify the offset based on the mapping. The duration of the R2D control / data transmission is described below in Proposals 1-3.

[0128] [Option 4] A mapping between the offset and the type / format / size (number of bits) of the R2D control / data transmission may be specified, communicated to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or identify the offset based on the mapping. For example, the mapping may be such that the offset increases with increasing size of the R2D control / data transmission.

[0129] The constraints described in Proposal 1-1 may also be applied. That is, several constraints such as those shown below may be specified in the specification, and the A-IoT device may assume that the time-domain position of the R2D midamble reported satisfies one or more of these constraints (e.g., all of the constraints). Examples of the constraints are as follows: - minimum duration in the time domain of R2D control / data transmission between the R2D preamble and the R2D midamble #1a - maximum duration in the time domain of R2D control / data transmission between the R2D preamble and the R2D midamble #1b - minimum duration in the time domain of R2D control / data transmission between two R2D midambles #2a - maximum duration in the time domain of R2D control / data transmission between two R2D midambles #2b - minimum duration in the time domain of R2D control / data transmission between the R2D midamble and the R2D postamble #3a - maximum duration in the time domain of R2D control / data transmission between the R2D midamble and the R2D postamble #3b

[0130] Minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b may be determined according to the A-IoT device type (e.g., Device 1 / 2a / 2b described above), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., Topology 1 or Topology 2 described above)), band used for R2D transmission, etc. That is, the A-IoT device may determine minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b according to the A-IoT device type / device capability / connection topology / band used for R2D transmission, etc.

[0131] Minimum duration #1a / minimum duration #2a / minimum duration #3a may be the same or different values. Minimum duration #1b / minimum duration #2b / minimum duration #3b may be the same or different values.

[0132] <Proposal 1-3> Finally, we describe proposals (Proposal 1-3) regarding the duration of R2D control / data transmissions, which may be associated with the duration of the R2D midamble or an offset relative to the beginning of the time domain position of the R2D midamble.

[0133] The duration of the R2D control / data transmission may be specified, signaled to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured.

[0134] Assuming that the entire R2D control / data transmission consists of multiple parts and that the R2D midamble may be transmitted between two parts, the duration of the R2D control / data transmission as specified / signaled / pre-configured may be as described in Alt. 1 below or as described in Alt. 2 below. An example of the duration of the R2D control / data transmission is shown below with reference to Figure 21.

[0135] [Alt. 1] L2+L4 as shown in Figure 21 (i.e., the duration of the R2D preamble, R2D midamble, and R2D postamble is not counted); L1+L2+L3+L4+L5 as shown in Figure 21 (i.e., the duration of the R2D preamble, R2D midamble, and R2D postamble is counted); L1+L2+L3+L4 as shown in Figure 21 (i.e., the duration of the R2D preamble and R2D midamble is counted, and the duration of the R2D postamble is not counted); L2+L3+L4 as shown in Figure 21 (i.e., the duration of the R2D midamble is counted, and the duration of the R2D preamble and R2D postamble is not counted); L1+L2+L4 as shown in Figure 21 (i.e., the duration of the R2D preamble is counted, and the duration of the R2D midamble and R2D postamble is not counted). - L2 + L3 + L4 + L5 as shown in Figure 21 (i.e., the duration of the R2D midamble and R2D postamble is counted, and the duration of the R2D preamble is not counted) - L1 + L2 + L4 + L5 as shown in Figure 21 (i.e., the duration of the R2D preamble and R2D postamble is counted, and the duration of the R2D midamble is not counted) - L2 + L4 + L5 as shown in Figure 21 (i.e., the duration of the R2D postamble is counted, and the duration of the R2D preamble and R2D midamble is not counted) Thus, in Alt. 1, the duration of an R2D control / data transmission includes at least L2 and L4.

[0136] [Alt. 2] L2 or L4 as shown in Figure 21 (i.e. the duration of the R2D preamble, R2D midamble and R2D postamble are not counted) L1 + L2 as shown in Figure 21 (i.e. the duration of the R2D preamble is counted, and the duration of the R2D midamble (immediately following the R2D control / data) is not counted) L2 + L3 as shown in Figure 21 (i.e. the duration of the R2D preamble is not counted, and the duration of the R2D midamble (immediately following the R2D control / data) is counted) L1 + L2 + L3 as shown in Figure 21 (i.e. the duration of the R2D preamble and the R2D midamble (immediately following the R2D control / data) is counted) L3 + L4 as shown in Figure 21 (i.e. the R2D midamble (immediately preceding the R2D control / data) is counted, and the R2D postamble is not counted) - L4 + L5 as shown in Figure 21 (i.e., the R2D midamble (immediately preceding the R2D control / data) is not counted, but the R2D postamble is counted) - L3 + L4 + L5 as shown in Figure 21 (i.e., the R2D midamble and R2D postamble (immediately preceding the R2D control / data) are counted) Thus, in Alt. 2, the duration of an R2D control / data transmission includes at least L2 or L4.

[0137] <Example of Operation According to Proposal> Next, an example of operation of the A-IoT device according to Proposal 1 will be described with reference to FIG.

[0138] In step S11, the A-IoT device determines a time-domain location of a first midamble of a signal to be transmitted to the A-IoT device based on a predetermined time unit, a preamble of the signal, a second midamble of the first signal after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or a data portion of the signal immediately before the first midamble. The signal may be R2D, each midamble may be an R2D midamble, and the preamble may be an R2D preamble.

[0139] In step S12, the A-IoT device receives the first midamble at the time domain position determined in step S11.

[0140] Note that steps S11 and S12 may be performed in accordance with suggestions 1-1 to 1-3, including the above-mentioned options, Alt, variations, etc.

[0141] [Variation of Proposal 1] In the case of R2D transmission in Topology 2, the intermediate UE should be aware of the time domain location of the R2D midamble. Therefore, the time domain location of the R2D midamble may be notified to the intermediate UE by the base station 10, or may be determined by the intermediate UE according to rules defined in the specifications. In this case, the contents of Proposal 1 (Proposals 1-1 to 1-3) above may be applied, in which "A-IoT device" is replaced with "intermediate UE."

[0142] As described above, according to Proposal 1, an A-IoT device can appropriately determine the time domain position (i.e., time resource) at which to receive the first midamble based on a predetermined time unit, the preamble of the signal, the second midamble of the first signal after the preamble, the third midamble of the signal immediately before the first midamble, or the control information portion or data portion of the signal immediately before the first midamble.

[0143] Next, Proposal 2 regarding D2R transmission will be described.

[0144] <Proposal 2-1> First, a proposal (Proposal 2-1) regarding the design and constraints of the D2R midamble will be described.

[0145] The exact time domain position of the D2R midamble is determined by the A-IoT device. That is, the base station 10, the reader of the intermediate UE, etc., can recognize the exact time domain position of the D2R midamble by blind decoding the D2R midamble. The D2R midamble will be described in detail below.

[0146] The D2R midamble may be a sequence. Here, the D2R midamble sequence should be distinguishable from D2R control / data information bits, D2R preambles, and D2R postambles. That is, a reader does not (mis)detect a D2R midamble as a D2R control / data, D2R preamble, or D2R postamble, and does not (mis)detect a D2R control / data, D2R preamble, or D2R postamble as a D2R midamble. Such distinction may be based on the coding scheme / design of information bits "0" and "1" / design of the D2R preamble, D2R midamble, and D2R postamble (including sequence type / format, sequence length, etc.). That is, a reader may identify a D2R midamble based on the coding scheme / design of information bits "0" and "1" / design of the D2R preamble, D2R midamble, and D2R postamble. Note that this may also apply to the D2R preamble / postamble, i.e., the D2R midamble, D2R preamble, D2R postamble, and D2R control / data information bits should be distinguishable from each other.

[0147] As described with respect to R2D transmission with reference to FIG. 12, the sequence of the D2R midamble (e.g., "x", "x", "y", "x") may be different from the D2R control / data ("0", "1") and may be different from the sequences of the D2R preamble and D2R postamble (not shown).

[0148] However, the D2R midamble may be the same as or similar to the D2R preamble, and may be the same as or similar to the D2R postamble. For example, in one design, the reader may not need to distinguish between the D2R midamble and the D2R preamble, and in another design, the reader may not need to distinguish between the D2R midamble and the D2R postamble.

[0149] The sequence of the D2R midamble may be specified in the specifications, may be notified to the A-IoT device by the base station 10, intermediate UE, etc., or may be set in advance. As a variation of this, multiple sequences of the D2R midamble may be specified in the specifications or may be set, and one sequence of the multiple sequences may be notified to the A-IoT device by the base station 10, intermediate UE, etc.

[0150] Several constraints may be specified in the specification, and an A-IoT device may transmit a D2R midamble subject to one or more of these constraints (e.g., all of the constraints). Examples of constraints are as follows: Minimum duration in the time domain of D2R control / data transmission between a D2R preamble and a D2R midamble #1a Maximum duration in the time domain of D2R control / data transmission between a D2R preamble and a D2R midamble #1b Minimum duration in the time domain of D2R control / data transmission between two D2R midambles #2a Maximum duration in the time domain of D2R control / data transmission between two D2R midambles #2b Minimum duration in the time domain of D2R control / data transmission between a D2R midamble and a D2R postamble #3a Maximum duration in the time domain of D2R control / data transmission between a D2R midamble and a D2R postamble #3b

[0151] With respect to minimum duration #1a and maximum duration #1b, "between the D2R preamble and the D2R midamble" may be from the end of the D2R preamble / start of the D2R control / data to the end of the D2R midamble / D2R control / data, or from the end of the D2R preamble / start of the D2R control / data to the end of the D2R midamble / D2R control / data. Note that the end of the D2R preamble and the start of the D2R control / data may be the same or different. Similarly, the start of the D2R midamble and the end of the D2R control / data may be the same or different. Similarly, the end of the D2R midamble and the start of the D2R control / data may be the same or different. For example, the end of the D2R midamble may be located between minimum duration #1a and maximum duration #1b from the end of the D2R preamble, as described with respect to R2D transmission with reference to Figure 13. Note that for D2R transmission, "R2D" may be replaced with "D2R" in Figure 13.

[0152] With respect to minimum duration #2a and maximum duration #2b, "between two D2R midambles" may be from the end of the earlier (earlier) of the two D2R midambles / D2R control / data to the start of the later (later) of the two D2R midambles / D2R control / data, or from the end of the earlier (earlier) of the two D2R midambles / D2R control / data to the start of the later (later) of the two D2R midambles / D2R control / data. As described with respect to R2D transmission with reference to FIG. 14, for example, the end of the later of the two D2R midambles may be located between minimum duration #2a and maximum duration #2b from the end of the earlier of the two D2R midambles. Regarding D2R transmission, "R2D" may be replaced with "D2R" in FIG.

[0153] With respect to minimum duration #3a and maximum duration #3b, "between the D2R midamble and the D2R postamble" may refer to the period from the end of the D2R midamble / start of the D2R control / data to the end of the D2R postamble / D2R control / data, or from the end of the D2R midamble / start of the D2R control / data to the end of the D2R postamble. Note that the start of the D2R postamble and the end of the D2R control / data may be the same or different. As described with reference to FIG. 15 regarding R2D transmission, for example, the start of the D2R postamble may be located between the end of the D2R midamble and minimum duration #3a and maximum duration #3b. Note that with respect to D2R transmission, "R2D" may be replaced with "D2R" in FIG. 15.

[0154] Minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b may be determined according to the A-IoT device type (e.g., Device 1 / 2a / 2b described above), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., Topology 1 or Topology 2 described above)), band used for D2R transmission, etc. That is, the A-IoT device may determine minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b according to the A-IoT device type / device capability / connection topology / band used for D2R transmission, etc.

[0155] Minimum duration #1a / minimum duration #2a / minimum duration #3a may be the same or different values. Minimum duration #1b / minimum duration #2b / minimum duration #3b may be the same or different values.

[0156] Whether a D2R midamble is included in the D2R may be determined according to rules defined in the specifications, may be notified to the reader device by the A-IoT device, or may be set in advance. For example, whether a D2R midamble is included in the D2R may be (implicitly) notified via the D2R preamble by using a different preamble sequence / format, etc. As a more specific example, if a D2R midamble is included in the D2R, sequence A may be used for the D2R preamble, and if a D2R midamble is not included in the D2R, a sequence other than sequence A may be used for the D2R preamble. For example, the reader may determine whether a D2R midamble is included in the D2R based on a notification from the A-IoT device (the notified information may be referred to as information regarding the presence or absence of a D2R midamble, etc.).

[0157] [Variation of Proposal 2-1] As described above, the start point of a D2R midamble and the end point of the D2R control / data may be the same or different. Similarly, the end point of a D2R midamble and the start point of the D2R control / data may be the same or different. If the start point and end point are different, the reader may not be able to identify the D2R control / data. Therefore, as described with reference to FIG. 16 regarding R2D transmission, the D2R midamble may notify the end point of the D2R control / data immediately before the D2R midamble, or may notify the start point of the D2R control / data immediately after the D2R midamble. Note that, with regard to D2R transmission, "R2D" may be replaced with "D2R" in FIG. 16. Such notification of the D2R midamble allows the reader to identify the D2R control / data.

[0158] <Proposal 2-2> Next, a proposal (Proposal 2-2) regarding the time domain position of the D2R midamble will be described.

[0159] The time domain position of the D2R midamble may be notified to the A-IoT device by the base station 10, intermediate UE, etc., or may be determined by the A-IoT device according to rules defined in the specifications.

[0160] The time domain position of the D2R midamble will be described in detail below. Note that the offset and the duration of the D2R midamble described below may be referred to as a period (first period) (from a reference point described later) for starting transmission of the D2R midamble and a period (second period) for transmitting the D2R midamble, respectively. For example, an A-IoT device may start transmitting a D2R midamble after the first period from the reference point, or may transmit a D2R midamble within the second period after the first period.

[0161] [Option 1] The duration of the D2R midamble in the time domain may be specified in the specification.

[0162] [Option 2] The duration of the D2R midamble may be signaled to the A-IoT device as a number of time units by the base station 10, an intermediate UE, etc. The signaled information may be referred to as information about the D2R midamble, information about the D2R midamble transmission time, etc.

[0163] [Option 3] Each sequence of the D2R midamble may have a fixed duration defined in the specification. The A-IoT device may determine or specify the duration of the D2R midamble based on the sequence used.

[0164] [Option 4] A mapping between the duration of the D2R midamble and the duration of the D2R control / data transmission may be specified, signaled to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or specify the duration of the D2R midamble based on the mapping. The duration of the D2R control / data transmission is described below in Proposal 2-3.

[0165] [Option 5] A mapping between the duration of the D2R midamble and the type / format / size (number of bits) of the D2R control / data transmission may be specified, signaled to the A-IoT device by the base station 10, an intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or specify the duration of the D2R midamble based on the mapping. For example, the mapping may be such that the larger the size of the D2R control / data transmission, the longer the duration of the D2R midamble.

[0166] Note that which of options 1 to 5 to apply may be determined according to the A-IoT device type (e.g., the above-mentioned device 1 / 2a / 2b), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., the above-mentioned topology 1 or topology 2)), etc. In other words, the A-IoT device may determine and apply an option according to the A-IoT device type, device capability, or connection topology.

[0167] Next, the reference point for the beginning of the time domain position of the D2R midamble will be described.

[0168] [Option 1] The reference point may be the beginning or end of a unit of time, for example the reference point may be the beginning of a particular or predetermined frame, slot, symbol, etc.

[0169] [Option 2] The reference point may be the beginning or end of the D2R preamble. For example, the reference point may be the beginning of the D2R preamble, as described for R2D transmission with reference to Figure 17. Note that for D2R transmission, "R2D" may be replaced with "D2R" in Figure 17.

[0170] [Option 3] Assuming that the entire D2R control / data transmission consists of multiple parts and the D2R midamble may be transmitted between the two parts, the reference point may be the beginning or end of the first part of the D2R control / data transmission after the D2R preamble (the part of the D2R control / data transmission immediately after the D2R preamble). As described with reference to Figure 18 for the R2D transmission, for example, the reference point may be the beginning of the first part of the D2R control / data transmission (#1) after the D2R preamble. Note that for D2R transmission, "R2D" may be replaced with "D2R" in Figure 18.

[0171] [Option 4] Assuming that the entire D2R control / data transmission consists of multiple parts and that a D2R midamble may be transmitted between two parts, the reference point may be the beginning or end of the part of the D2R control / data transmission immediately preceding the D2R midamble. As described with respect to the R2D transmission with reference to Figure 19, for example, the reference point may be the beginning of the part (#2) of the D2R control / data transmission immediately preceding the D2R midamble. Note that for D2R transmissions, "R2D" may be replaced with "D2R" in Figure 19.

[0172] [Option 5] The reference point may be the beginning or end of the previous D2R midamble in time. As explained with respect to R2D transmission with reference to Figure 20, for example, the reference point may be the beginning of the immediately preceding D2R midamble. Note that for D2R transmission, "R2D" may be replaced with "D2R" in Figure 20.

[0173] Next, the offset between the reference point and the beginning of the time domain position of the D2R midamble (see FIGS. 17-20) will be described.

[0174] The offset may be a number of time units, for example, the offset may be 2 slots, etc.

[0175] Multiple offsets may be determined, and multiple D2R midambles may be transmitted corresponding to the multiple offsets, respectively.

[0176] The offset may be defined / signaled as described in options 1-3 below.

[0177] [Option 1] The offset may be specified in the specification.

[0178] [Option 2] The offset may be signaled to the A-IoT device by the base station 10, intermediate UE, etc.

[0179] [Option 3] A mapping between the offset and the duration of the D2R control / data transmission may be specified, signaled to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or identify the offset based on the mapping. The duration of the D2R control / data transmission is described below in Proposal 2-3.

[0180] [Option 4] A mapping between the offset and the type / format / size (number of bits) of the D2R control / data transmission may be specified, communicated to the A-IoT device by the base station 10, intermediate UE, etc., or may be pre-configured. The A-IoT device may determine or identify the offset based on the mapping. For example, the mapping may be such that the offset increases with increasing size of the D2R control / data transmission.

[0181] The constraints described in Proposal 2-1 may also be applied. That is, several constraints such as those shown below may be specified in the specification, and the A-IoT device may assume that the time-domain position of the D2R midamble notified satisfies one or more of these constraints (e.g., all of the constraints). Examples of constraints are as follows: - Minimum duration in the time domain of D2R control / data transmission between a D2R preamble and a D2R midamble #1a - Maximum duration in the time domain of D2R control / data transmission between a D2R preamble and a D2R midamble #1b - Minimum duration in the time domain of D2R control / data transmission between two D2R midambles #2a - Maximum duration in the time domain of D2R control / data transmission between two D2R midambles #2b - Minimum duration in the time domain of D2R control / data transmission between a D2R midamble and a D2R postamble #3a - Maximum duration in the time domain of D2R control / data transmission between a D2R midamble and a D2R postamble #3b

[0182] Minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b may be determined according to the A-IoT device type (e.g., Device 1 / 2a / 2b described above), device capability, connection topology (whether the A-IoT device connects to the base station 10 or to an intermediate UE (e.g., Topology 1 or Topology 2 described above)), band used for D2R transmission, etc. In other words, the A-IoT device may determine minimum duration #1a / maximum duration #1b / minimum duration #2a / maximum duration #2b / minimum duration #3a / maximum duration #3b according to the A-IoT device type / device capability / connection topology / band used for D2R transmission, etc.

[0183] Minimum duration #1a / minimum duration #2a / minimum duration #3a may be the same or different values. Minimum duration #1b / minimum duration #2b / minimum duration #3b may be the same or different values.

[0184] <Proposal 2-3> Finally, we describe a proposal (Proposal 2-3) regarding the duration of D2R control / data transmission, which may be associated with the duration of the D2R midamble or an offset relative to the beginning of the time domain position of the D2R midamble.

[0185] The duration of the D2R control / data transmission may be specified in a specification, may be notified to the A-IoT device by the base station 10, intermediate UE, etc., or may be set in advance.

[0186] Assuming that the entire D2R control / data transmission consists of multiple parts and that a D2R midamble may be transmitted between two parts, the duration of the specified / signaled / preconfigured D2R control / data transmission may be as described in Alt. 1 below or as described in Alt. 2 below. An example of the duration of a D2R control / data transmission is shown below with reference to FIG. 21.

[0187] [Alt. 1] L2+L4 as shown in Figure 21 (i.e., the duration of the D2R preamble, D2R midamble, and D2R postamble is not counted); L1+L2+L3+L4+L5 as shown in Figure 21 (i.e., the duration of the D2R preamble, D2R midamble, and D2R postamble is counted); L1+L2+L3+L4 as shown in Figure 21 (i.e., the duration of the D2R preamble and D2R midamble is counted, and the duration of the D2R postamble is not counted); L2+L3+L4 as shown in Figure 21 (i.e., the duration of the D2R midamble is counted, and the duration of the D2R preamble and D2R postamble is not counted); L1+L2+L4 as shown in Figure 21 (i.e., the duration of the D2R preamble is counted, and the duration of the D2R midamble and D2R postamble is not counted). - L2 + L3 + L4 + L5 as shown in Figure 21 (i.e., the duration of the D2R midamble and D2R postamble is counted, and the duration of the D2R preamble is not counted) - L1 + L2 + L4 + L5 as shown in Figure 21 (i.e., the duration of the D2R preamble and D2R postamble is counted, and the duration of the D2R midamble is not counted) - L2 + L4 + L5 as shown in Figure 21 (i.e., the duration of the D2R postamble is counted, and the duration of the D2R preamble and D2R midamble is not counted) Thus, in Alt. 1, the duration of a D2R control / data transmission includes at least L2 and L4.

[0188] [Alt. 2] L2 or L4 as shown in Figure 21 (i.e. the duration of the D2R preamble, D2R midamble and D2R postamble are not counted) L1 + L2 as shown in Figure 21 (i.e. the duration of the D2R preamble is counted, the duration of the D2R midamble (immediately following the D2R control / data) is not counted) L2 + L3 as shown in Figure 21 (i.e. the duration of the D2R preamble is not counted, the duration of the D2R midamble (immediately following the D2R control / data) is counted) L1 + L2 + L3 as shown in Figure 21 (i.e. the duration of the D2R preamble and the D2R midamble (immediately following the D2R control / data) is counted) L3 + L4 as shown in Figure 21 (i.e. the D2R midamble (immediately preceding the D2R control / data) is counted, the D2R postamble is not counted) - L4 + L5 as shown in Figure 21 (i.e., the D2R midamble (immediately before the D2R control / data) is not counted, but the D2R postamble is counted) - L3 + L4 + L5 as shown in Figure 21 (i.e., the D2R midamble and D2R postamble (immediately before the D2R control / data) are counted) Thus, in Alt. 2, the duration of a D2R control / data transmission includes at least L2 or L4.

[0189] <Example of Operation According to Proposal> Next, an example of operation of the A-IoT device according to Proposal 2 will be described with reference to FIG.

[0190] In step S21, the A-IoT device determines a time-domain location of a first midamble of a signal transmitted from the A-IoT device based on a predetermined time unit, a preamble of the signal, a second midamble of the first signal after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or a data portion of the signal immediately before the first midamble. The signal may be D2R, each midamble may be a D2R midamble, and the preamble may be a D2R preamble.

[0191] In step S22, the A-IoT device transmits the first midamble at the time domain position determined in step S21.

[0192] Note that steps S21 and S22 may be performed in accordance with suggestions 2-1 to 2-3, including the above-mentioned options, Alt, variations, etc.

[0193] [Variation of Proposal 2] In the case of D2R reception in Topology 2, the intermediate UE should recognize the time domain position of the D2R midamble. Therefore, the time domain position of the D2R midamble may be notified to the intermediate UE by the base station 10, or may be determined by the intermediate UE according to rules defined in the specifications. In this case, the contents of Proposal 2 (Proposals 2-1 to 2-3) above, in which "A-IoT device" is replaced with "intermediate UE," may be applied.

[0194] As described above, according to Proposal 2, an A-IoT device can appropriately determine the time domain position (i.e., time resource) for transmitting the first midamble based on a predetermined time unit, the preamble of the signal, the second midamble of the first signal after the preamble, the third midamble of the signal immediately before the first midamble, or the control information portion or data portion of the signal immediately before the first midamble.

[0195] Finally, Proposal 3 for distinguishing between the control information part and / or the data part and the preamble, midamble and / or postamble in R2D / D2R will be described.

[0196] <Proposal 3-1> A-IoT devices / base stations / intermediate UEs may distinguish or identify the control / data portion from the preamble / midamble / postamble by decoding the modulation method or line coding or line coding processing.

[0197] [Alt. 1] A specific bit sequence may be used for the preamble / midamble / postamble using the same line encoding scheme as the control / data portion.

[0198] Option 1: As option 1, a particular bit sequence using the same line encoding as the control / data portion may be "0" for a certain duration.

[0199] (Option 1-1) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the start timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the first "0") as the start timing of the preamble / midamble / postamble.

[0200] (Option 1-2) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the end timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the last "0") as the end timing of the preamble / midamble / postamble.

[0201] (Options 1-3) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be a preamble / midamble / postamble itself. For example, as shown in FIG. 25, Manchester-encoded "0"s may indicate or signal a preamble itself. If an A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide that this is a preamble / midamble / postamble.

[0202] Note that a certain duration (e.g., "X") may be specified in a specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0203] Option 2: As option 2, a particular bit sequence using the same line encoding as the control / data portion may be "1" for a certain duration.

[0204] (Option 2-1) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the start timing of the preamble / midamble / postamble. For example, as shown in FIG. 26, a Manchester-encoded "1" may indicate or signal the start timing of the midamble. If an A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the first "1") as the start timing of the preamble / midamble / postamble.

[0205] (Option 2-2) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the end timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the last "1") as the end timing of the preamble / midamble / postamble.

[0206] (Option 2-3) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be a preamble / midamble / postamble itself. If an A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide that this is a preamble / midamble / postamble.

[0207] Note that a certain duration (e.g., "X") may be specified in a specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0208] Option 3: In option 3, the specific bit sequence using the same line encoding method as the control / data portion may be any known bit sequence other than options 1 and 2.

[0209] (Option 3-1) When a certain (specific) bit sequence is detected or identified, this may be the start timing of a preamble / midamble / postamble. When an A-IoT device / base station / intermediate UE detects, detects, or identifies a certain (specific) bit sequence, it may detect, identify, or decide this (e.g., the first bit) as the start timing of a preamble / midamble / postamble.

[0210] (Option 3-2) When a certain (specific) bit sequence is detected or identified, this may be the end timing of the preamble / midamble / postamble. When the A-IoT device / base station / intermediate UE detects, detects, or identifies a certain (specific) bit sequence, it may detect, identify, or determine this (e.g., the last bit) as the end timing of the preamble / midamble / postamble.

[0211] (Option 3-3) When a certain (specific) bit sequence is detected or identified, this may be a preamble / midamble / postamble itself. When an A-IoT device / base station / intermediate UE detects, detects, or identifies a certain (specific) bit sequence, it may detect, identify, or determine it as a preamble / midamble / postamble.

[0212] In addition, a certain (specific) bit sequence / its length may be specified in the specifications, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (for example, via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0213] In Alt. 1, the line encoding scheme may be PIE (pulse interval encoding), Manchester encoding, Miller encoding, FM0 encoding, NRZ encoding, RZ encoding, or other encoding schemes. Note that the line encoding scheme may be specified in the specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0214] [Alt. 2] Different line encoding schemes may be applied to the preamble / midamble / postamble and the control / data portion.

[0215] In Alt. 2, the line coding scheme may be PIE, Manchester coding, Miller coding, FM0 coding, NRZ coding, RZ coding, or other coding schemes. Note that the line coding schemes for the preamble / midamble / postamble and the line coding schemes for the control / data portion may be specified in specifications, or may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., or may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be preset.

[0216] In Alt. 2, multiple line encoding schemes may be used for the preamble / midamble / postamble. For example, a line encoding scheme of "X" may be applied to a certain (specific) portion (duration) at the beginning / end of the preamble / midamble / postamble, while a line encoding scheme of "Y" may be applied to the other portions of the preamble / midamble / postamble.

[0217] In Alt. 2, for the preamble / midamble / postamble bit sequence, the options in Alt. 1 may be applied, as described below.

[0218] Option 1: As option 1, the bit sequence using a given line encoding scheme may be "0" for a certain duration.

[0219] (Option 1-1) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the start timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the first "0") as the start timing of the preamble / midamble / postamble.

[0220] (Option 1-2) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the end timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the last "0") as the end timing of the preamble / midamble / postamble.

[0221] (Options 1-3) If all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be a preamble / midamble / postamble itself. If an A-IoT device / base station / intermediate UE detects, determines, or identifies that all "0"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide that this is a preamble / midamble / postamble.

[0222] Note that a certain duration (e.g., "X") may be specified in a specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0223] Option 2: As option 2, the bit sequence using a given line encoding scheme may be "1" for a certain duration.

[0224] (Option 2-1) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the start timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the first "1") as the start timing of the preamble / midamble / postamble.

[0225] (Option 2-2) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be the end timing of the preamble / midamble / postamble. If the A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide this (e.g., the last "1") as the end timing of the preamble / midamble / postamble.

[0226] (Option 2-3) If all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, this may be a preamble / midamble / postamble itself. If an A-IoT device / base station / intermediate UE detects, determines, or identifies that all "1"s continue for X bits / chips / milliseconds / symbols / or other time units, it may determine, identify, or decide that this is a preamble / midamble / postamble.

[0227] Note that a certain duration (e.g., "X") may be specified in a specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0228] Option 3: As option 3, the bit sequence using a predetermined line encoding method may be any known bit sequence other than options 1 and 2.

[0229] (Option 3-1) When a certain (specific) bit sequence is detected or identified, this may be the start timing of a preamble / midamble / postamble. When an A-IoT device / base station / intermediate UE detects, detects, or identifies a certain (specific) bit sequence, it may detect, identify, or decide this (e.g., the first bit) as the start timing of a preamble / midamble / postamble.

[0230] (Option 3-2) When a certain (specific) bit sequence is detected or identified, this may be the end timing of the preamble / midamble / postamble. When the A-IoT device / base station / intermediate UE detects, detects, or identifies a certain (specific) bit sequence, it may detect, identify, or determine this (e.g., the last bit) as the end timing of the preamble / midamble / postamble.

[0231] (Option 3-3) When a certain (specific) bit sequence is determined or identified, it may be a preamble / midamble / postamble. When an A-IoT device / base station / intermediate UE detects, determines, or identifies a certain (specific) bit sequence, it may determine, identify, or decide it as a preamble / midamble / postamble.

[0232] In addition, a certain (specific) bit sequence / its length may be specified in the specifications, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (for example, via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0233] Below we will describe an example where NRZ coding is used for the preamble / midamble / postamble, while Manchester coding is used for the control / data portion.

[0234] (Example 1) For example, as shown in Figure 27, NRZ coding "0" may be applied to the end timing of the preamble (option 1-2), while Manchester coding may be applied to the (remaining) previous part of the preamble.

[0235] (Example 2) For example, as shown in FIG. 28, NRZ coded "0" may be applied to the start of the midamble (option 1-1), while Manchester coding may be applied to the (remaining) part of the midamble.

[0236] (Example 3) For example, as shown in FIG. 29, a certain (specific) bit sequence (including all "0"s and all "1"s) using NRZ coding may be applied to the midamble (Option 3-3).

[0237] (Example 4) For example, as shown in FIG. 30, an NRZ encoded "1" may be applied to the postamble (option 2-3).

[0238] It should be noted that in the above examples, NRZ encoding may be replaced with PIE, Manchester encoding, Miller encoding, FM0 encoding, RZ encoding or other encoding methods, and Manchester encoding may be replaced with PIE, Miller encoding, FM0 encoding, NRZ encoding, RZ encoding or other encoding methods.

[0239] <Proposal 3-2> The A-IoT device / base station / intermediate UE may distinguish or identify the control / data portion from the preamble / midamble / postamble through demodulation processing.

[0240] [Alt. 1] Different modulated values ​​may be applied to the preamble / midamble / postamble and the control / data part.

[0241] The applied modulation scheme may be On-Off Keying (OOK), Amplitude Shift Keying (ASK), Frequency Shift Keying (FSK), Phase Shift Keying (PSK) including Binary Phase Shift Keying (BPSK), or other modulation schemes.

[0242] The modulation scheme to be applied may be specified in the specifications, may be notified to the A-IoT device by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (or intermediate UE, etc.) to the base station 10, intermediate UE, etc. (e.g., via R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0243] For example, when applying ASK, different modulation depth / amplitude may be used for the preamble / midamble / postamble and the control / data part.

[0244] For example, as shown in Figure 31, amplitudes A1 and A2 may be used for the preamble / midamble / postamble, while amplitudes A3 and A4 may be used for the control / data portion. The amplitudes (A1, A2, A3, A4) may be specified in the specification, or may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., or may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (e.g., via R2D / D2R preamble / R2D / D2R control), or may be preset.

[0245] For example, when applying FSK, different frequency shifts may be used for the preamble / midamble / postamble and the control / data part.

[0246] For example, when 4-bit FSK is applied, frequency shift values ​​f1 and f3 may be used for the preamble / midamble / postamble, while frequency shift values ​​f2 and f4 may be used for the control / data portion. The frequency shift values ​​(f1, f2, f3, f4) may be specified in a specification, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (for example, via the R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0247] For example, when applying PSK, different phase shifts may be used for the preamble / midamble / postamble and the control / data part.

[0248] For example, when QPSK is applied, phase shift 1 and phase shift 3 may be used for the preamble / midamble / postamble, while phase shift 2 and phase shift 4 may be used for the control / data portion. The phase shifts may be specified in the specifications, may be notified to the A-IoT device (or intermediate UE, etc.) by the base station 10, intermediate UE, etc., may be notified to the base station 10, intermediate UE, etc. by the A-IoT device (for example, via the R2D / D2R preamble / R2D / D2R control), or may be set in advance.

[0249] [Alt. 2] Different modulation orders may be applied to the preamble / midamble / postamble and the control / data part.

[0250] When applying OOK, if M bits can be transmitted in a certain (specific) time unit (symbol / slot / other time unit), different values ​​of M may be used for the preamble / midamble / postamble and the control / data part.

[0251] The modulation schemes for the preamble / midamble / postamble and the control / data portion may be OOK, ASK, FSK, or PSK. For example, PSK may be applied to the preamble / midamble / postamble while OOK is applied to the control / data portion. Or, vice versa, OOK may be applied to the preamble / midamble / postamble while PSK is applied to the control / data portion.

[0252] <Proposal 3-3> When applying OFDM, an A-IoT device / base station / intermediate UE may distinguish or identify the control / data portion from the preamble / midamble / postamble by using a CP (Cyclic Prefix).

[0253] When applying an OFDM waveform, different CP values ​​may be applied to the preamble / midamble / postamble and the control / data portion.

[0254] For example, if a certain (particular) value (e.g., "0" (or "1") or any other bit sequence) is indicated or signaled in the CP duration (CP length), the corresponding OFDM symbol may be used for the preamble / midamble / postamble, and if another value is indicated or signaled in the CP duration, the corresponding OFDM symbol may be used for the control / data portion.

[0255] For example, as shown in FIG. 32, if the CP part is "00", the corresponding OFDM symbol part may be a midamble, and in other cases (for example, if the CP part is "11"), the corresponding OFDM symbol part may be a control / data part.

[0256] [Variations of Proposal 3] Different Alt / options may be applied to the preamble / midamble / postamble, respectively.

[0257] Different Alt / options may be applied to R2D / D2R respectively.

[0258] Different Alt / Options may apply to different device types.

[0259] Different Alt / Options may apply to different connection topologies.

[0260] Different Alt / Options may be applied to different R2D / D2R channels (e.g., PRDCH, a PHY (Physical Layer) channel for R2D control, PDRCH, a PHY (Physical Layer) channel for D2R control).

[0261] Different Alt / options may apply to different R2D / D2 information / formats / commands (e.g., 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 (Msg.1 / Msg.3)).

[0262] As described above, according to Proposal 3, the A-IoT device / base station / intermediate UE can distinguish or identify the control / data portion from the preamble / midamble / postamble.

[0263] <Additional Notes on Proposals 1 / 2 / 3> Regarding Proposals 1 / 2 / 3, the enabling / disabling of R2D / D2R preamble, midamble and / or postamble transmission may be notified to the A-IoT device / intermediate UE by the base station 10, intermediate UE, etc.

[0264] Also, with regard to Proposals 1 / 2 / 3, the capability (information) of an A-IoT device to support R2D / D2R preambles, midambles and / or postambles may be reported to the network or may be determined depending on the device type of the A-IoT device.

[0265] Also, for Proposals 1 / 2 / 3, R2D data transmission may be carried on the PRDCH, which is a physical channel.

[0266] Also, with respect to Proposals 1 / 2 / 3, the R2D control transmission may be carried on the PRDCH or on a separate physical R2D channel different from the PRDCH.

[0267] Also, for Proposals 1 / 2 / 3, D2R data transmission may be carried on the PDRCH, which is a physical channel.

[0268] Also, with respect to Proposals 1 / 2 / 3, D2R control transmissions may be carried on the PDRCH or on a separate physical D2R channel that is different from the PDRCH.

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

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

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

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

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

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

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

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

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

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

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

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

[0281] Furthermore, for example, the control unit 103 may determine a boundary position in the time domain between the timing acquisition information portion and the control information portion or the data portion in a signal including the timing acquisition information portion and the control information portion or the data portion, which is transmitted to the base station 10, based on the bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion, and the receiving unit 102 may start or end reception of the timing acquisition information portion at the determined boundary position. The bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion may be coded using the same coding method or different coding methods. The first bit in the bit sequence used for the timing acquisition information portion may represent the start of the timing acquisition information portion. The last bit in the bit sequence used for the timing acquisition information portion may represent the end of the timing acquisition information portion. The bit sequence used for the timing acquisition information portion may represent the timing acquisition information portion itself.

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

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

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

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

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

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

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

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

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

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

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

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

[0294] For example, the control unit 203 may determine the time domain position of a first midamble of a signal transmitted to the device 20 based on a predetermined time unit, a preamble of the signal, a second midamble of the first signal after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or data portion of the signal immediately before the first midamble, and the receiving unit 201 may receive the first midamble at the determined time domain position. The receiving unit 201 may start receiving the first midamble a first period after the predetermined time unit, the preamble, the second midamble, the third midamble, or the beginning or end of the control information portion or data portion. The control unit 203 may determine the first period based on part or all of the control information portion or data portion of the signal. The receiving unit 201 may receive the first midamble within a second period after the first period. The control unit 203 may determine the second period based on part or all of the control information portion or data portion of the signal.

[0295] Furthermore, for example, the control unit 203 may determine the time domain position of the first midamble of the signal transmitted from the device 20 based on a predetermined time unit, the preamble of the signal, the second midamble of the first signal after the preamble, the third midamble of the signal immediately before the first midamble, or the control information portion or data portion of the signal immediately before the first midamble, and the transmitting unit 202 may transmit the first midamble at the determined time domain position. The transmitting unit 202 may start transmitting the first midamble a first period after the predetermined time unit, the preamble, the second midamble, the third midamble, or the beginning or end of the control information portion or data portion. The control unit 203 may determine the first period based on part or all of the control information portion or data portion of the signal. The transmitting unit 202 may transmit the first midamble within a second period after the first period. The control unit 203 may determine the second period based on part or all of the control information portion or the data portion of the signal.

[0296] Furthermore, for example, the control unit 203 may determine a boundary position in the time domain between the timing acquisition information portion and the control information portion or the data portion in a signal including the timing acquisition information portion and the control information portion or the data portion transmitted to the device 20 based on the bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion, and the receiving unit 201 may start or end reception of the timing acquisition information portion at the determined boundary position. The bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion may be coded using the same coding method or different coding methods. The first bit in the bit sequence used for the timing acquisition information portion may represent the start of the timing acquisition information portion. The last bit in the bit sequence used for the timing acquisition information portion may represent the end of the timing acquisition information portion. The bit sequence used for the timing acquisition information portion may represent the timing acquisition information portion itself.

[0297] (Summary of embodiment) A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes a control unit that determines the time domain position of a first midamble of a signal to be transmitted to the device based on a predetermined time unit, a preamble of the signal, a second midamble of the signal that is the first after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or a data portion of the signal immediately before the first midamble, and a receiving unit that receives the first midamble at the time domain position.

[0298] With the above configuration, the device can properly determine the time domain position (i.e., time resource) at which to receive the first midamble.

[0299] In one example, the receiving unit starts receiving the first midamble a first period after the predetermined time unit, the preamble, the second midamble, the third midamble, or the beginning or end of the control information portion or the data portion.

[0300] With the above configuration, the device can determine the timing to start receiving the first midamble.

[0301] In one example, the control unit determines the first period based on part or all of a control information portion or a data portion of the signal.

[0302] With the above configuration, the device can determine the timing to start receiving the first midamble depending on the control information portion or data portion (for example, size) of the signal.

[0303] In one example, the receiver receives the first midamble within a second period after the first period.

[0304] With the above configuration, the device can determine the time interval for receiving the first midamble.

[0305] In one example, the control unit determines the second period based on part or all of a control information portion or a data portion of the signal.

[0306] With the above configuration, the device can determine the time interval for receiving the first midamble depending on the control information portion or the data portion (eg, size) of the signal.

[0307] A communication method according to one aspect of the present disclosure is a method in which a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device determines the time domain position of a first midamble of a signal to be transmitted to the device based on a predetermined time unit, a preamble of the signal, a second midamble of the signal that is the first after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or data portion of the signal immediately before the first midamble, and receives the first midamble at the time domain position.

[0308] With the above configuration, the device can properly determine the time domain position (i.e., time resource) at which to receive the first midamble.

[0309] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and comprises: a control unit that determines the time domain position of a first midamble of a signal transmitted from the device based on a predetermined time unit, a preamble of the signal, a second midamble of the signal that is the first after the preamble, a third midamble of the signal immediately before the first midamble, or a control information portion or data portion of the signal immediately before the first midamble; and a transmitting unit that transmits the first midamble at the time domain position.

[0310] With the above configuration, the device can appropriately determine the time domain position (i.e., the time resource) at which to transmit the first midamble.

[0311] In one example, the transmitting unit starts transmitting the first midamble a first period after the predetermined time unit, the preamble, the second midamble, the third midamble, or the beginning or end of the control information portion or the data portion.

[0312] With the above configuration, the device can determine the timing to start transmitting the first midamble.

[0313] In one example, the control unit determines the first period based on part or all of a control information portion or a data portion of the signal.

[0314] With the above configuration, the device can determine the timing to start transmitting the first midamble depending on the control information portion or the data portion (for example, the size) of the signal.

[0315] In one example, the transmitter transmits the first midamble within a second period after the first period.

[0316] With the above configuration, the device can determine the time interval for transmitting the first midamble.

[0317] In one example, the control unit determines the second period based on part or all of a control information portion or a data portion of the signal.

[0318] With the above configuration, the device can determine the time interval for transmitting the first midamble depending on the control information portion or the data portion (eg, size) of the signal.

[0319] A communication method according to one aspect of the present disclosure involves a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device determining the time domain position of a first midamble of a signal to be transmitted from the device based on a predetermined time unit, the preamble of the signal, the first second midamble of the signal after the preamble, the third midamble of the signal immediately before the first midamble, or the control information portion or data portion of the signal immediately before the first midamble, and transmitting the first midamble at the time domain position.

[0320] With the above configuration, the device can appropriately determine the time domain position (i.e., the time resource) at which to transmit the first midamble.

[0321] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes: a control unit that determines a boundary position in the time domain between a timing acquisition information portion and a control information portion or a data portion in a signal including the timing acquisition information portion and the control information portion or the data portion, the boundary position being transmitted to the device, based on a bit sequence used for the timing acquisition information portion and a bit sequence used for the control information portion or the data portion; and a receiving unit that starts or ends reception of the timing acquisition information portion at the boundary position.

[0322] With the above configuration, the device can distinguish or discriminate between the control information portion or data portion and the timing acquisition information portion.

[0323] In one example, the bit sequence used in the timing acquisition information portion and the bit sequence used in the control information portion or the data portion are coded using the same coding method or different coding methods.

[0324] With the above configuration, there is no need to change the bit sequence between the timing acquisition information part and the control information part or the data part, or by changing the bit sequence between the timing acquisition information part and the control information part or the data part, it is easy to distinguish between the timing acquisition information part and the control information part or the data part.

[0325] In one example, the first bit in the bit sequence used for the timing acquisition information portion indicates the start of the timing acquisition information portion.

[0326] By having the above configuration, the device can determine or identify the start of the timing acquisition information portion.

[0327] In one example, the last bit in the bit sequence used for the timing acquisition information portion indicates the end of the timing acquisition information portion.

[0328] By having the above configuration, the device can determine or identify the end of the timing acquisition information portion.

[0329] In one example, the bit sequence used for the timing acquisition information portion represents the timing acquisition information portion itself.

[0330] A communication method according to one aspect of the present disclosure is a method in which a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device determines a boundary position in the time domain between a timing acquisition information portion and a control information portion or a data portion in a signal including the timing acquisition information portion and the control information portion or the data portion to be transmitted to the device, based on a bit sequence used for the timing acquisition information portion and a bit sequence used for the control information portion or the data portion, and starts or ends reception of the timing acquisition information portion at the boundary position.

[0331] With the above configuration, the device can distinguish or discriminate between the control information portion or data portion and the timing acquisition information portion.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0411] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-065631, filed April 15, 2024, are incorporated herein by reference in their entirety.

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

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

Claims

1. A device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device, comprising: a control unit that determines the boundary position in the time domain between a timing acquisition information portion and a control information portion or a data portion in a signal including the timing acquisition information portion and the control information portion or the data portion, the boundary position being transmitted to the device, based on a bit sequence used for the timing acquisition information portion and a bit sequence used for the control information portion or the data portion; and a receiving unit that starts or ends reception of the timing acquisition information portion at the boundary position.

2. The device of claim 1, wherein the bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion are coded using the same coding method or different coding methods.

3. The device of claim 1, wherein the first bit in the bit sequence used for the timing acquisition information portion indicates the start of the timing acquisition information portion.

4. The device of claim 1, wherein the last bit in the bit sequence used for the timing acquisition information portion indicates the end of the timing acquisition information portion.

5. The device of claim 1, wherein the bit sequence used for the timing acquisition information portion represents the timing acquisition information portion itself.

6. A communication method in which a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device determines the boundary position in the time domain between a timing acquisition information portion and a control information portion or a data portion in a signal containing the timing acquisition information portion and the control information portion or the data portion, based on the bit sequence used for the timing acquisition information portion and the bit sequence used for the control information portion or the data portion, and starts or ends reception of the timing acquisition information portion at the boundary position.

Images