Communication device and communication method

Abstract

This communication device to which power is supplied by environmental power generation includes: a reception unit for receiving a downlink signal; and a control unit for switching the communication device from one of an on-state, a sleep-state, and an off-state to another state on the basis of the downlink signal.

Description

Communication device and communication method

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

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

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

[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.7.0 (2021-09)"New SID: Study on solutions for Ambient IoT (Internet of Things) in NR ", RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] However, there has been insufficient consideration given to the switching behavior of A-IoT devices between on, off, and sleep states, which can result in improper communication.

[0006] One aspect of the present disclosure is to provide a communication device and a communication method that clarify the switching operations between states such as on, off, and sleep, and that enable appropriate communication.

[0007] A communication device according to one aspect of the present disclosure is a communication device that receives power from environmental power generation, and includes a receiving unit that receives a downlink signal, and a control unit that switches the communication device from one of an on state, a sleep state, and an off state to another state based on the downlink signal.

[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 support. FIG. 3 is a diagram illustrating Topology 3 in UL support. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating device states. FIG. 7 is a diagram illustrating Proposals 1-1, 1-2, and 1-3. FIG. 8 is a diagram illustrating Proposal 2-1: Option 1: Option 1-1. FIG. 9 is a diagram illustrating Proposal 2-1: Option 1: Option 1-2. FIG. 10 is a diagram illustrating Proposal 2-1: Option 2: Option 2-1. FIG. 11 is a diagram illustrating Proposal 2-1: Option 2: Option 2-2. FIG. 12 is a diagram illustrating Proposal 2-1: Option 3: Option 3-1. FIG. 13 is a diagram illustrating Proposal 2-1: Option 3: Option 3-2. FIG. 14 is a diagram illustrating Proposal 2-1: Option 4. FIG. 15 is a diagram illustrating Proposal 2-1: Option 5. FIG. 16 is a diagram illustrating Proposal 3: Option 1: Option 1-1. FIG. 17 is a diagram illustrating Proposal 3: Option 1: Option 1-2. FIG. 1 is a diagram illustrating Proposal 3: Option 1: Options 1-3. FIG. 2 is a diagram illustrating Proposal 3: Option 1: Options 1-4. FIG. 3 is a diagram illustrating Proposal 3: Option 2: Option 2-1. FIG. 4 is a diagram illustrating Proposal 3: Option 2: Option 2-2. FIG. 5 is a diagram illustrating Proposal 3: Option 3: Option 3-1. FIG. 6 is a block diagram illustrating an example of the configuration of a reader according to an embodiment. FIG. 7 is a block diagram illustrating an example of the configuration of a device according to an embodiment. FIG. 8 is a diagram illustrating an example of the hardware configuration of a reader and a device according to an embodiment. FIG. 9 is a diagram illustrating an example of the configuration of a vehicle.

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

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

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

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

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

[0014] <Wireless Communication System> FIG. 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. As illustrated in FIG. 1, the wireless communication system 1 includes a base station 10 and a device 20. While FIG. 1 illustrates one base station 10 and one device 20, this is merely an example, and multiple base stations and devices may exist. 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.

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

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

[0018] As will be described later, the wireless communication system may include an intermediate node, an assisting node, and / or a terminal (UE) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be simply written 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 or an A-IoT device.

[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, or the like 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] For Ambient IoT, the following deployment scenarios and characteristics can 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 the device

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

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

[0026] <Device 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 that of RFID (Radio frequency identification).

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

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

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

[0031] Fig. 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 an ambient IoT device and a base station.

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

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

[0036] Figure 6 illustrates Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device communicates with the UE bidirectionally. The communication related to Topology 4 may be considered as sidelink (SL) communication.

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

[0038] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE in 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. Furthermore, the A-IoT device may be used interchangeably with the A-IoT UE or the A-IoT terminal. The A-IoT device may be referred to as the A-IoT or the device.

[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 field 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, the intermediate node, the support node, and other nodes by switching the reflection coefficient of the antenna of the ambient IoT device, and transmits information to the base station, the intermediate node, the support node, and other nodes. The RF signals may also be referred to as carrier waves.

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

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

[0043] Additionally, several issues for A-IoT DL and UL will be discussed under the leadership of RAN 1. These include: Frame structure, synchronization and timing, and random access; Numerology, bandwidth, and multiple access; Waveform and modulation; Channel coding; DL channel / signal aspects; UL channel / signal aspects; Relationship with scheduling and timing. A-IoT has been approved as a topic for Rel. 19. In the discussion of A-IoT, the following 1. traffic flow, 2. device assumptions, and 3. topology can be considered.

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

[0045] 1a. DT (device terminated) Traffic includes transmission to the A-IoT UE (DL), but not transmission from the A-IoT UE (UL). 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, which includes instructions such as commands or instructions to the A-IoT UE.

[0046] 1b. 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, transmitting information corresponds to transmitting a signal containing information or transmitting a signal. In this disclosure, transmitting to a certain device X corresponds to transmitting a signal (or information) to device X. In addition, transmitting from a certain device X and transmitting by a certain device X correspond to device X transmitting a signal (or information). In addition, receiving from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, receiving by a certain device X corresponds to device X receiving a signal (or information).

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

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

[0050] 2b. 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, this 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 an intermediate node. Note that the base station in Topology 1 may correspond to a microcell.

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

[0056] For A-IoT UEs, the signal design is common to Topology 1 and Topology 2. Hereinafter, the intermediate node may be referred to as int. UE (intermediate UE). The intermediate node may also be referred to as a base station, a communication device, a network device, or a network node.

[0057] <R2D and D2R> At the RAN1#116 meeting, it was agreed to consider the physical channels for R2D data transmission and D2R data transmission.

[0058] R2D stands for "reader to device." D2R stands for "device to reader." A "reader" corresponds to a base station or intermediate node. A "device" corresponds to A-IoT.

[0059] R2D may be considered as DL in an A-IoT wireless communication system. R2D data transmission may be performed on a physical channel such as the physical reader to device channel (PRDCH). R2D control transmission may be performed on the same physical channel as R2D data transmission or on a different physical channel from R2D data transmission.

[0060] D2R can be considered as the UL in an A-IoT wireless communication system. D2R data transmission can be performed on a physical channel such as a physical device to reader channel (PDRCH). D2R control transmission can be performed on the same physical channel as D2R data transmission or on a physical channel separate from D2R.

[0061] R2D, R2D transmission, R2D signal, DL, and DL signal may be used interchangeably. D2R, D2R transmission, R2D signal, UL, and UL signal may be used interchangeably. R2D control transmission may be referred to as R2D control information or control information. D2R control transmission may be referred to as D2R control information or control information. Signal, data, and information may be used interchangeably.

[0062] <Device Types in RAN1> In RAN1, for the purpose of the study, the following terms are used for device types:

[0063] Device 1: Device 1 (which may be referred to as Type 1) is a type of device that consumes a peak power of 1 μW or less. Device 1 has an energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million) (Z is 10 to the power x, where x is an integer greater than or equal to 0). Device 1 does not have any DL / UL amplifiers. UL transmission in Device 1 is performed by backscattering with an externally provided carrier wave (CW). Note that SFO indicates the difference in sampling back frequencies between the transmitting side and the receiving side. SFO may be interpreted as representing, for example, the accuracy of time synchronization between the transmitting side and the receiving side.

[0064] Device 2a Device 2a (which may be referred to as type 2a) is a type of device that consumes a peak power of several hundred μW. Device 2a has energy storage and has an initial SFO of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). DL / UL amplification is also performed in device 2a. UL transmission in device 2a is performed by backscattering with an externally provided carrier wave (carrier wave (CW)).

[0065] Device 2b Device 2b (which may be referred to as type 2b) is a type of device that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial SFO of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). DL / UL amplification is also performed in device 2b. UL transmission in device 2b is performed internally within device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering with an externally provided carrier wave (carrier wave (CW)).

[0066] <Device States> In low power A-IoT, at least one of the following device states may be defined: ON state / duration: In the ON state / duration, the device receives PRDCH / transmits PDRCH. OFF state / duration: In the OFF state / duration, the device does not receive PRDCH / transmit PDRCH. SLEEP state / duration: In the SLEEP state / duration, the device does not receive PRDCH / transmit PDRCH, but retains timing count / memory from the previous ON state.

[0067] Hereinafter, an on state / period may be referred to as an on or on state, an off state / period may be referred to as an off or off state, and a sleep state / period may be referred to as a sleep or sleep state.

[0068] Fig. 8 is a diagram illustrating the device state. As shown in Fig. 8, the device has a charging period and a de-charging period.

[0069] During the charging period, the device may store power in the power storage device by an external RF signal, and may be in an off state during the charging period, as indicated by arrow A8a in FIG.

[0070] During the charge release period, the device may use the power stored in the power storage device. During the charge release period, the device may be in an off, sleep, or on state, as shown by arrow A8b in FIG.

[0071] The device may have an opportunity to receive the R2D signal during the charging release period, as shown by arrow A8c in Figure 8. The device may receive the R2D signal at T R2D During this period, the device may be in an off, sleep or on state.

[0072] The device may receive the R2D synchronization signal during the charging release period, as shown by arrow A8d in Figure 8. After receiving the R2D synchronization signal, the device D2R During this period, the device may be in an off, sleep or on state.

[0073] The definition of the device state may differ from the above description. For example, in the sleep state, the device may perform PRDCH reception / PDRCH transmission, or may sleep (stop) functions other than PRDCH reception / PDRCH transmission. Also, the device may be in the sleep state during a charging period.

[0074] <Considerations> It is desirable that the state of the device be controlled / recognized / understood by the reader. For example, if the reader cannot understand the state of the device, communication between the reader and the device may fail. For example, if the reader transmits a signal when the device is off, R2D Rx / D2R Tx in the device may fail.

[0075] Therefore, this disclosure proposes a technology that clarifies and defines the switching operations of device states such as on, off, and sleep in a device, allowing the reader to control, recognize, and understand the state of the device, thereby enabling the device and reader to communicate appropriately.

[0076] <Proposal 1-1> Proposal 1-1 provides a technique for when a device switches its device state from off to on. Proposal 1-1 provides the following techniques, Option 1 to Option 5.

[0077] <Proposal 1-1: Option 1> When switching the device state from off to on, the device monitors the R2D and determines whether the conditions are met. That is, the device monitors the R2D and, if the conditions are met, switches the device state from off to on.

[0078] R2D may be the following signal: R2D is a timing acquisition / synchronization signal followed by a PRDCH R2D is a timing acquisition / synchronization signal not followed by a PRDCH R2D is a PRDCH R2D is a carrier for backscatter transmission

[0079] The conditions may be the following: ・When the device performs energy detection / when the detected power exceeds a threshold. ・When the device performs envelope detection of an on-off-keying (OOK) signal and detects a specific signal / sequence. This condition does not need to apply to Proposal 1-1 / Proposal 1-3 (described later), but may apply to Proposal 1-2 (described later). ・When the device decodes an R2D signal / PRDCH and the decoded content (information) indicates that the device state should be switched on. This condition does not need to apply to Proposal 1-1 / Proposal 1-3, but may apply to Proposal 1-2. ・When the device decodes an R2D signal / PRDCH and the decoded content indicates that the device is an R2D target device / device group. This condition does not need to apply to Proposal 1-1 / Proposal 1-3, but may apply to Proposal 1-2.

[0080] For example, when a device in an off state receives an R2D synchronization signal, it switches to an on state if a condition is met, such as the detected power exceeding a threshold.

[0081] <Proposal 1-1: Option 2> When switching the device state from off to on, the timing of the switch is indicated by the previous sleep / on state (see Proposal 3 for details).

[0082] For example, the device is instructed to switch from off to on by an R2D signal / PRDCH indicated in the previous sleep / on state, as shown by arrow A9a in Fig. 9 or arrow A10a in Fig. 10. The instruction to switch from off to on may be indicated, for example, by the duration of the off state. The duration of the off state may be indicated by a count value / timer.

[0083] <Proposal 1-1: Option 3> Regarding switching the device state from off to on, the device switches the device state from off to on when the power storage is charged. The device may switch the device state from off to on in the following cases: - When the power storage is fully charged - When the charged energy exceeds a threshold - When power has been received for a predetermined period of time

[0084] Note that the device must change the device state as ON, or may switch the device state as ON after charging. The device may implement either of the above conditions.

[0085] <Proposal 1-1: Option 4> Regarding switching of the device state from off to on, the device switches the device state from off to on immediately before the D2R Tx timing.

[0086] The timing immediately before the D2R Tx timing may be x chips / modulation symbols / slots / ms (msec) / us (usec) before the start timing of the D2R Tx.

[0087] As an example of option 4, the device switches the device state from OFF to ON at the timing indicated by arrow A10c in FIG. 10, which is earlier than the timing indicated by arrow A10b.

[0088] <Proposal 1-1: Option 5> Regarding switching the device state from off to on, the device switches the device state from off to on immediately before the R2D timing acquisition / synchronization signal Rx, which is transmitted immediately before the D2R Tx.

[0089] The timing immediately before the R2D timing acquisition / synchronization signal Rx may be x chips / modulation symbols / slots / ms / us before the start timing of the R2D Rx.

[0090] As an example of option 5, the device switches its device state from OFF to ON at the timing indicated by arrow A10c in FIG. 10, which is earlier than the timing indicated by arrow A10d.

[0091] <Proposal 1-2> Proposal 1-2 provides a technique for when a device switches its device state from sleep to on. Proposal 1-2 provides the following techniques, Option 1 to Option 5.

[0092] <Proposal 1-2: Option 1> In the above-described <Proposal 1-1: Option 1>, "off" is replaced with "sleep." In other words, when the device state switches from sleep to on, the device monitors the R2D and determines whether the conditions are met.

[0093] The technology (operation, etc.) of <Proposal 1-2: Option 1> is the same as <Proposal 1-1: Option 1>, with "off" replaced with "sleep," so further explanation will be omitted.

[0094] As an example of option 1, a device in a sleep state switches to an on state when it receives an R2D synchronization signal and meets a condition that the detected power exceeds a threshold.

[0095] <Proposal 1-2: Option 2> The "off" in the above-described <Proposal 1-1: Option 2> is replaced with "sleep." In other words, when the device state switches from sleep to on, the timing of the switch is determined by the previous sleep / on state (see Proposal 3 for details).

[0096] The technology of <Proposal 1-2: Option 2> is the same as <Proposal 1-1: Option 2>, except that "off" is replaced with "sleep", so further explanation will be omitted.

[0097] As an example of option 2, the device is instructed to switch from sleep to on by an R2D signal / PRDCH indicating the previous sleep / on state, as shown by arrow A9a in Figure 9 or arrow A10a in Figure 10 (in <Proposal 1-2: Option 2>, "OFF" in Figures 9 and 10 is rewritten to "SLEEP").

[0098] <Proposal 1-2: Option 3> In the above-described <Proposal 1-1: Option 3>, "off" is replaced with "sleep." That is, with regard to switching the device state from sleep to on, the device switches the device state from sleep to on when the power storage is charged.

[0099] The technology of <Proposal 1-2: Option 3> is the same as <Proposal 1-1: Option 3>, except that "off" is replaced with "sleep", so further explanation will be omitted.

[0100] In addition, since the device may not be able to charge power in the sleep state, the technology in <Proposal 1-2: Option 3> may not be applied to the device.

[0101] <Proposal 1-2: Option 4> The "off" in <Proposal 1-1: Option 4> explained above can be read as "sleep." In other words, regarding the switching of the device state from sleep to on, the device switches its device state from sleep to on immediately before the D2R Tx timing.

[0102] The technology of <Proposal 1-2: Option 4> is the same as <Proposal 1-1: Option 4>, except that "off" is replaced with "sleep", so further explanation will be omitted.

[0103] As an example of option 4, the device switches the device state from sleep to on at the timing indicated by arrow A10c, which is earlier than the timing indicated by arrow A10b in Figure 10 (in <Proposal 1-2: Option 4>, "OFF" in Figure 10 is rewritten to "SLEEP").

[0104] <Proposal 1-2: Option 5> The word "off" in <Proposal 1-1: Option 5> explained above can be read as "sleep." That is, with regard to switching the device state from sleep to on, the device switches its device state from sleep to on immediately before the R2D timing acquisition / synchronization signal Rx, which is transmitted immediately before the D2R Tx.

[0105] The technology of <Proposal 1-2: Option 5> is the same as <Proposal 1-1: Option 5>, except that "off" is replaced with "sleep", so further explanation will be omitted.

[0106] As an example of option 5, the device switches the device state from sleep to on at the timing indicated by arrow A10c, which is earlier than the timing indicated by arrow A10d in Figure 10 (in <Proposal 1-2: Option 5>, "OFF" described in Figures 9 and 10 is rewritten to "SLEEP").

[0107] <Proposal 1-3> Proposal 1-3 provides a technique for when a device switches its device state from off to sleep. Proposal 1-3 provides the following techniques, Option 1 to Option 5.

[0108] <Proposal 1-3: Option 1> In the above-described <Proposal 1-1: Option 1>, "On" can be read as "Sleep." In other words, the device monitors the R2D and, if certain conditions are met, switches the device state from Off to Sleep.

[0109] The technology of <Proposal 1-3: Option 1> is the same as <Proposal 1-1: Option 1>, except that "on" is replaced with "sleep", so further explanation will be omitted.

[0110] As an example of option 1, when a device in an off state receives an R2D synchronization signal, it switches to a sleep state if a condition is met, such as the detected power exceeding a threshold.

[0111] <Proposal 1-3: Option 2> The "on" in <Proposal 1-1: Option 2> explained above will be read as "sleep." In other words, when the device state switches from off to sleep, the timing of the switch will be determined by the previous sleep / on state (see Proposal 3 for details).

[0112] The technology of <Proposal 1-3: Option 2> is the same as <Proposal 1-1: Option 2>, except that "on" is replaced with "sleep", so further explanation will be omitted.

[0113] As an example of option 2, the device is instructed to switch from off to sleep by an R2D signal / PRDCH indicating the previous sleep / on state, as shown by arrow A9a in Figure 9 or arrow A10a in Figure 10 (in <Proposal 1-3: Option 2>, "ON" in Figure 9 and "ON" on the right side in Figure 10 are rewritten to "SLEEP").

[0114] <Proposal 1-3: Option 3> The word "on" in the above-described <Proposal 1-1: Option 3> can be read as "sleep." That is, with regard to switching the device state from off to sleep, the device switches the device state from off to sleep when the power storage is charged.

[0115] The technology of <Proposal 1-3: Option 3> is the same as <Proposal 1-1: Option 3>, except that "on" is replaced with "sleep", so further explanation will be omitted.

[0116] <Proposal 1-3: Option 4> The "on" in <Proposal 1-1: Option 4> explained above can be read as "sleep." In other words, regarding the switching of the device state from off to sleep, the device switches its device state from off to sleep immediately before the D2R Tx timing.

[0117] The technology of <Proposal 1-3: Option 4> is the same as <Proposal 1-1: Option 4>, except that "on" is replaced with "sleep", so further explanation will be omitted.

[0118] As an example of option 4, the device switches the device state from off to sleep at the timing indicated by arrow A10c, which is earlier than the timing indicated by arrow A10b in Figure 10 (in <Proposal 1-3: Option 4>, "ON" on the right side of Figure 10 is rewritten to "SLEEP").

[0119] <Proposal 1-3: Option 5> The word "on" in <Proposal 1-1: Option 5> explained above should be read as "sleep." That is, with regard to switching the device state from off to sleep, the device switches its device state from off to sleep immediately before the R2D timing acquisition / synchronization signal Rx, which is transmitted immediately before the D2R Tx.

[0120] The technology of <Proposal 1-3: Option 5> is the same as <Proposal 1-1: Option 5>, except that "on" is replaced with "sleep", so further explanation will be omitted.

[0121] As an example of option 5, the device switches the device state from off to sleep at the timing indicated by arrow A10c, which is earlier than the timing indicated by arrow A10d in Figure 10 (in <Proposal 1-3: Option 5>, "ON" on the right side of Figure 10 is rewritten to "SLEEP").

[0122] <Proposal 2-1> Proposal 2-1 provides techniques for when a device switches its device state from on to sleep. Proposal 2-1 provides the following techniques, Option 1 to Option 8.

[0123] <Proposal 2-1: Option 1> Regarding switching of the device state from ON to sleep, the device switches from ON to sleep state when scheduled PRDCH reception is completed, i.e., the device switches from ON to sleep state based on the timing of receiving the scheduled PRDCH.

[0124] Option 1 also provides the following techniques: Option 1-1 and Option 1-2.

[0125] <Proposal 2-1: Option 1: Option 1-1> The device switches from on to sleep state immediately after receiving a PRDCH. For example, the device switches from on to sleep state immediately after receiving a PRDCH, as shown in FIG.

[0126] <Proposal 2-1: Option 1: Option 1-2> The device switches from an on state to a sleep state after receiving a PRDCH. For example, the device switches from on state to a sleep state X time units after receiving a PRDCH, as shown in Fig. 12. The time unit may be a chip, a symbol, a slot, a subframe, or a frame.

[0127] The device may switch from on to sleep after x chips / symbols / slots / ms / us after PRDCH reception.

[0128] <Proposal 2-1: Option 2> Regarding switching of the device state from on to sleep, the device switches from on to sleep when the scheduled PDRCH transmission is completed, i.e., the device switches from on to sleep based on the transmission timing of the scheduled PDRCH.

[0129] Option 2 also provides the following techniques: Option 2-1 and 2-2.

[0130] <Proposal 2-1: Option 2: Option 2-1> The device switches from on to sleep state immediately after transmitting the PDRCH. For example, the device switches from on to sleep state immediately after transmitting the PDRCH, as shown in FIG.

[0131] <Proposal 2-1: Option 2: Option 2-2> The device switches from an on state to a sleep state after a PDRCH transmission. For example, the device switches from on state to a sleep state X time units after a PDRCH transmission, as shown in FIG. 14 .

[0132] The device may switch from on to sleep after x chips / modulation symbols / slots / ms / us after a PDRCH transmission.

[0133] <Proposal 2-1: Option 3> Regarding the switching of the device state from on to sleep, the device switches from on to sleep when the time window for D2R transmission ends. In other words, the device switches from on to sleep based on the timing of the end of the time window for D2R transmission.

[0134] Option 3 also provides the following techniques, Options 3-1 and 3-2. Before explaining Options 3-1 and 3-2, we will explain resources for D2R transmission.

[0135] The time-domain resources for D2R transmission (D2R TX) can be assumed to be allocated at two levels, as in the RFID (Radio Frequency Identification) specification: 1. Long-level 2. Short-level

[0136] At the long level, it can be determined whether a response will be performed within a time window, and at the short level, the actual time resource within the time window can be determined.

[0137] For example, the thick-lined frames in Figures 15 and 16 indicate long-level time resources, and the thin-lined frames in Figures 15 and 16 indicate short-level time resources.

[0138] For example, a device may decide to perform D2R transmission based on the queries (signals transmitted from a reader) shown in Figures 15 and 16. A device that has decided to perform D2R transmission may first determine time domain resources at the long level in a two-level resource allocation, and then determine time domain resources (actual time resources) at the short level.

[0139] A plurality of consecutive (or non-consecutive) short level resources constitute one long level resource. In other words, one long level resource has a plurality of consecutive (or non-consecutive) short level resources. In the examples of Figures 15 and 16, four consecutive short level resources sandwiched between queries constitute one long level resource.

[0140] <Proposal 2-1: Option 3: Option 3-1> The time window includes one or more short level D2R Tx timings. For example, the device switches from on to sleep when the time window for D2R transmission at one or more short levels (four short levels in FIG. 15) ends, as shown in FIG. 15.

[0141] <Proposal 2-1: Option 3: Option 3-2> The time window includes one or more long level D2R Tx timings. For example, the device switches from on to sleep when the time window for D2R transmission at one or more long levels (three long levels in FIG. 16) ends, as shown in FIG. 16.

[0142] <Proposal 2-1: Option 4> Regarding the switching of the device state from on to sleep, the device switches from on to sleep state when it does not receive an R2D within a certain time window. For example, as shown by arrow A17a in Figure 17, when the device does not receive an R2D within the certain time window, it switches from on to sleep state at the end of the certain time window.

[0143] The device remains in the on state for a predetermined time window.

[0144] If the device does not receive an R2D during a given time window, it goes to sleep; otherwise, the time window time count is initialized.

[0145] The R2D may be at least one of the following: - An R2D for the device itself. For example, the device / device group ID indicated in the R2D may be the ID of the device receiving the R2D. For example, a device switches from an on to a sleep state when it does not receive an R2D containing the device's device / device group ID within a predetermined time window. The R2D for the device may be, for example, a query for the device / device group. The R2D for the device may be, for example, a unicast of a PRDCH for the device / device group. The R2D for the device may be, for example, a paging (Msg0) for the device / device group. The R2D for the device may be, for example, an uplink transmission (Msg3) for the device / device group. - Any timing acquisition / synchronization signal - Any PRDCH - A carrier wave for backscatter transmission

[0146] The start timing / window size of the time window may be specified in a specification, pre-configured in the device, or instructed by the R2D.

[0147] For example, the start timing of the time window may be the end timing of R2D (PRDCH, R2D timing acquisition / synchronization signal, etc.) reception or D2R (PDRCH, timing acquisition / synchronization signal, etc.) transmission.

[0148] For example, the start of the time window may be X chips / symbols / slots / ms / us after the end of the last R2D (e.g., PRDCH, R2D timing acquisition / synchronization signal) reception or the last D2R (e.g., PDRCH, timing acquisition / synchronization signal) transmission.

[0149] For example, the start of the time window may be the time when the device changes to the ON state.

[0150] For example, the window size may be defined / set / indicated in units of chips / symbols / slots / ms / us.

[0151] For example, the window size may differ depending on the device type. For example, the window size for device type 2 may be longer than that for device type 1.

[0152] <Proposal 2-1: Option 5> Regarding switching the device state from on to sleep, the device switches from on to sleep when it does not receive an R2D until the timer expires. The device remains in the on state until the timer expires.

[0153] If the device does not receive an R2D during the time window, it goes to sleep, otherwise the timer is initialized.

[0154] For example, in Fig. 18, device #1 receives an R2D indicated by arrow A18a in the on state and initializes a timer. Device #1 receives an R2D indicated by arrow A18b in the on state and initializes a timer. After device #1 receives an R2D indicated by arrow A18b and initializes the timer, it does not receive an R2D during the time window and the timer expires. After the timer expires, device #1 switches from on to sleep, as indicated by double arrow A18c in Fig. 18.

[0155] For example, in Fig. 18, device #2 receives an R2D indicated by arrow A18a in the on state and initializes a timer. After receiving the R2D indicated by arrow A18a and initializing the timer, device #2 does not receive an R2D during the time window and the timer expires. After the timer expires, device #2 switches from on to sleep, as indicated by double arrow A18d in Fig. 18.

[0156] The R2D in Option 5 is the same as the R2D explained in <Proposal 2-1: Option 4>, so its explanation will be omitted.

[0157] The start timing / length of the timer may be specified in the specification, pre-set in the device, or instructed by the R2D.

[0158] The start timing / length of the timer is the same as that of the "time window start timing / window size" described in <Proposal 2-1: Option 4>, where the time window is replaced with "timer", and the explanation thereof is omitted.

[0159] <Proposal 2-1: Option 6> Regarding the switching of the device state from on to sleep, the device switches from on to sleep state at the end of the R2D reception window. The device remains on during the time window, regardless of whether it has received an R2D during that time window.

[0160] The R2D in Option 6 is the same as the R2D explained in <Proposal 2-1: Option 4>, so its explanation will be omitted.

[0161] The start timing / length of the timer may be specified in the specification, pre-set in the device, or instructed by the R2D.

[0162] The start timing / length of the timer is the same as that of the "time window start timing / window size" described in <Proposal 2-1: Option 4>, where the time window is replaced with "timer", and the explanation thereof is omitted.

[0163] <Proposal 2-1: Option 7> When the device state changes from on to sleep, the switching timing is instructed to the device (see Proposal 3 for details). In other words, the time duration of the on state is instructed by the R2D.

[0164] <Proposal 2-1: Option 8> When the remaining energy is insufficient for switching the device state from on to sleep, the device switches from on to sleep.

[0165] For example, a device may switch from an on state to a sleep state when the remaining energy is below a threshold value. The threshold value may be specified in a specification, pre-configured in the device, or instructed by the R2D. The threshold value may vary depending on the type of device.

[0166] <Proposal 2-2> Proposal 2-2 provides a technique for when a device switches its device state from on to off. Proposal 2-2 provides the following techniques, Option 1 to Option 8.

[0167] <Proposal 2-2: Option 1> "Sleep" in <Proposal 2-1: Option 1> described above is replaced with "off." That is, regarding the switching of the device state from on to off, the device switches from on to off state when scheduled PRDCH reception is completed.

[0168] Option 1 also provides the following techniques: Option 1-1 and Option 1-2.

[0169] <Proposal 2-2: Option 1: Option 1-1> The device switches from the on state to the off state immediately after receiving the PRDCH.

[0170] <Proposal 2-2: Option 1: Option 1-2> The device switches from ON to OFF state after PRDCH reception. The device may switch from ON to OFF state after x chips / symbols / slots / ms / us after PRDCH reception.

[0171] <Proposal 2-2: Option 2> "Sleep" in <Proposal 2-1: Option 2> described above is replaced with "off." That is, with regard to switching the device state from on to off, the device switches from on to off state when scheduled PDRCH transmission is completed.

[0172] Option 2 also provides the following techniques: Option 2-1 and 2-2.

[0173] <Proposal 2-2: Option 2: Option 2-1> The device switches from the on state to the off state immediately after transmitting the PDRCH.

[0174] <Proposal 2-1: Option 2: Option 2-2> The device switches from ON to OFF state after PDRCH transmission. The device may switch from ON to OFF state x chips / modulation symbols / slots / ms / us after PDRCH transmission.

[0175] <Proposal 2-2: Option 3> The word "sleep" in <Proposal 2-1: Option 3> explained above should be read as "off." That is, with regard to switching the device state from on to off, the device switches from on to off when the time window for D2R transmission ends.

[0176] Option 3 also provides the following technologies: Option 3-1 and 3-2.

[0177] <Proposal 2-2: Option 3: Option 3-1> The time window includes one or more short-level D2R Tx timings.

[0178] <Proposal 2-1: Option 3: Option 3-2> The time window includes one or more long level D2R Tx timings.

[0179] <Proposal 2-2: Option 4> In the above-described <Proposal 2-1: Option 4>, "sleep" is replaced with "off." That is, with regard to the switching of the device state from on to off, the device switches from on to off when it does not receive an R2D signal within a predetermined time window.

[0180] The technology of <Proposal 2-2: Option 4> is the same as <Proposal 2-1: Option 4>, except that "sleep" is replaced with "off", so further explanation will be omitted.

[0181] <Proposal 2-2: Option 5> The word "sleep" in <Proposal 2-1: Option 5> explained above should be read as "off." That is, regarding the switching of the device state from on to off, the device switches from on to off when it does not receive an R2D until the timer expires.

[0182] The technology of <Proposal 2-2: Option 5> is the same as <Proposal 2-1: Option 5>, except that "sleep" is replaced with "off", so further explanation will be omitted.

[0183] <Proposal 2-2: Option 6> In the above-described <Proposal 2-1: Option 6>, "Sleep" is replaced with "Off." In other words, regarding the switching of the device state from On to Off, the device switches from On to Off at the end of the R2D receive window.

[0184] The technology of <Proposal 2-2: Option 6> is the same as <Proposal 2-1: Option 6>, except that "sleep" is replaced with "off", so further explanation will be omitted.

[0185] <Proposal 2-2: Option 7> In the above-described <Proposal 2-1: Option 7>, "sleep" is replaced with "off." In other words, the switching timing for switching the device state from on to off is instructed to the device (for details, see Proposal 3).

[0186] The technology of <Proposal 2-2: Option 7> is the same as <Proposal 2-1: Option 7>, except that "sleep" is replaced with "off", so further explanation will be omitted.

[0187] <Proposal 2-2: Option 8> The word "sleep" in the above-described <Proposal 2-1: Option 8> can be read as "off." That is, when the remaining energy is insufficient to switch the device state from on to off, the device switches from on to off.

[0188] The technology of <Proposal 2-2: Option 8> is the same as <Proposal 2-1: Option 8>, except that "sleep" is replaced with "off", so further explanation will be omitted.

[0189] <Proposal 2-3> Proposal 2-3 provides techniques for when a device switches its device state from sleep to off. Proposal 2-3 provides the following techniques, Option 1 to Option 8.

[0190] <Proposal 2-3: Option 1> In the above-described <Proposal 2-1: Option 1>, "on" is replaced with "sleep" and "sleep" is replaced with "off." That is, regarding the switching of the device state from sleep to off, the device switches from sleep to the off state when scheduled PRDCH reception is completed.

[0191] Option 1 also provides the following techniques: Option 1-1 and Option 1-2.

[0192] <Proposal 2-3: Option 1: Option 1-1> The device switches from sleep to off state immediately after receiving PRDCH.

[0193] <Proposal 2-3: Option 1: Option 1-2> The device switches from sleep to off state after receiving PRDCH. The device may switch from sleep to off state x chips / symbols / slots / ms / us after receiving PRDCH.

[0194] <Proposal 2-3: Option 2> In the above-described <Proposal 2-1: Option 2>, "on" is replaced with "sleep" and "sleep" is replaced with "off." That is, with regard to switching the device state from sleep to off, the device switches from sleep to the off state when scheduled PDRCH transmission is completed.

[0195] Option 2 also provides the following techniques: Option 2-1 and 2-2.

[0196] <Proposal 2-2: Option 2: Option 2-1> The device switches from sleep to off state immediately after transmitting the PDRCH.

[0197] <Proposal 2-1: Option 2: Option 2-2> The device switches from sleep to off state after PDRCH transmission. The device may switch from sleep to off state x chips / modulation symbols / slots / ms / us after PDRCH transmission.

[0198] <Proposal 2-3: Option 3> In the above-described <Proposal 2-1: Option 3>, "on" is replaced with "sleep" and "sleep" is replaced with "off." That is, with regard to switching the device state from sleep to off, the device switches from sleep to the off state when the time window for D2R transmission ends.

[0199] Option 3 also provides the following technologies: Option 3-1 and 3-2.

[0200] <Proposal 2-2: Option 3: Option 3-1> The time window includes one or more short-level D2R Tx timings.

[0201] <Proposal 2-1: Option 3: Option 3-2> The time window includes one or more long level D2R Tx timings.

[0202] <Proposal 2-3: Option 4> In the above-described <Proposal 2-1: Option 4>, "on" is replaced with "sleep" and "sleep" is replaced with "off." That is, regarding the switching of the device state from sleep to off, the device switches from sleep to off when it does not receive R2D within a predetermined time window.

[0203] The technology of <Proposal 2-3: Option 4> is the same as <Proposal 2-1: Option 4>, except that "on" is replaced with "sleep" and "sleep" is replaced with "off", so further explanation will be omitted.

[0204] <Proposal 2-3: Option 5> In the above-described <Proposal 2-1: Option 5>, "on" will be read as "sleep" and "sleep" will be read as "off." That is, regarding the switching of the device state from sleep to off, the device will switch from sleep to off if it does not receive an R2D until the timer expires.

[0205] The technology of <Proposal 2-3: Option 5> is the same as <Proposal 2-1: Option 5>, except that "on" is replaced with "sleep" and "sleep" is replaced with "off", so further explanation will be omitted.

[0206] <Proposal 2-3: Option 6> In the above-described <Proposal 2-1: Option 6>, "on" will be read as "sleep" and "sleep" will be read as "off." In other words, regarding the switching of the device state from sleep to off, the device will switch from sleep to off at the end of the R2D receive window.

[0207] The technology of <Proposal 2-3: Option 6> is the same as <Proposal 2-1: Option 6>, except that "on" is replaced with "sleep" and "sleep" is replaced with "off", so further explanation will be omitted.

[0208] <Proposal 2-3: Option 7> In the above-described <Proposal 2-1: Option 7>, "on" will be read as "sleep" and "sleep" will be read as "off." In other words, the switching timing for switching the device state from sleep to off will be instructed to the device (for details, see Proposal 3).

[0209] The technology of <Proposal 2-3: Option 7> is the same as <Proposal 2-1: Option 7>, except that "on" is replaced with "sleep" and "sleep" is replaced with "off", so further explanation will be omitted.

[0210] <Proposal 2-3: Option 8> In the above-described <Proposal 2-1: Option 8>, "on" will be read as "sleep" and "sleep" will be read as "off." That is, when the remaining energy is insufficient to switch the device state from sleep to off, the device will switch from sleep to off.

[0211] The technology of <Proposal 2-3: Option 8> is the same as <Proposal 2-1: Option 8>, except that "on" is replaced with "sleep" and "sleep" is replaced with "off", so further explanation will be omitted.

[0212] <Proposal 3> Proposal 3 provides a technique for instructing switching timing.

[0213] The instructions include at least off to on, sleep to on, off to sleep, on to sleep, on to off, and sleep to off.

[0214] A transition state may be indicated. For example, a transition to an ON state may be indicated. If the source state (the device state when the indication is received) is the same as the indicated state, the device may ignore the indication. For example, the device may ignore the indication if the transition to ON is indicated when the device state is ON.

[0215] For indicating the device status, the following techniques, Option 1 to Option 3, are provided.

[0216] <Proposal 3: Option 1> Regarding the indication of switching timing, aperiodic state switching timing is indicated. For example, the device state is indicated to the device each time.

[0217] The switching timing is instructed by the R2D. An acknowledgement signal such as ACK / NACK is sent for the R2D to instruct the state switching. In other words, the device sends an acknowledgement signal of the R2D reception to the reader.

[0218] Option 1 also provides the following technologies: Options 1-1 to 1-4.

[0219] <Proposal 3: Option 1: Option 1-1> The switching timing is the end timing of R2D (PRDCH, R2D timing acquisition / synchronization signal, etc.) reception, which indicates the state switching. For example, the device switches its state from on to sleep at the end timing of R2D reception, as shown by arrow A19a in Figure 19.

[0220] <Proposal 3: Option 1: Option 1-2> The switching timing is X chips / symbols / slots / ms / us after the end of R2D reception, which indicates the state switching. For example, the device switches from on to sleep state X time units after the end of R2D reception, as shown by arrow A20a in Figure 20.

[0221] <Proposal 3: Option 1: Option 1-3> The switching timing is the timing of the end of the transmission of a response acknowledgement signal such as an ACK / NACK for the R2D that indicates the state switching. For example, the device switches from the on state to the sleep state at the end of the ACK / NACK transmission, as shown by arrow A21a in Figure 21.

[0222] <Proposal 3: Option 1: Options 1-4> The switching timing is X chips / symbols / slots / ms / us after the end of the acknowledgement signal transmission, such as ACK / NACK, for the R2D indicating the state change. For example, the device switches from on to sleep state X time units after the end of the ACK / NACK transmission, as shown by arrow A22a in Figure 22.

[0223] <Proposal 3: Option 2> Regarding the switching timing, periodic state switching timing is specified. The switching timing is specified by R2D.

[0224] Option 2 also provides the following techniques: Option 2-1 and 2-2.

[0225] <Proposal 3: Option 2: Option 2-1> Regarding the timing instruction for periodic state switching, the instruction of the on / sleep / off period / periodicity from the period / offset is instructed. For example, as shown in Figure 23, the device is instructed of the offset from the R2D at which periodic switching will start, the switching state to be performed (on and off in the example of Figure 23), the period of at least one switching state (the on period in the example of Figure 23), and the period at which the state will be switched.

[0226] The period / offset from the indication / period may be indicated in time units such as chips / symbols / slots / ms / us.

[0227] <Proposal 3: Option 2: Option 2-2> With regard to timing instructions for periodic state switching, an on / off / sleep state pattern is applied (instructed).

[0228] The following patterns are defined in the specification, pre-configured in the device, or instructed by the R2D: ON / OFF pattern ON / SLEEP pattern OFF / SLEEP pattern ON / OFF / SLEEP pattern

[0229] For example, the device is notified of an ON / OFF pattern as shown in FIG.

[0230] The pattern application timing is defined in the specification, pre-configured in the device or instructed by the R2D. The pattern application timing may be: chip / symbol / slot x time units after receiving Msg0 / page

[0231] The duration of on / off / sleep is indicated in time units such as chip / symbol / slot / ms / us. For example, in the example of Figure 24, the on time unit is indicated as "3" and the off time unit is indicated as "4".

[0232] <Proposal 3: Option 3> Regarding the switching timing instruction, semi-persistent state switching timing is instructed. The switching timing is activated / deactivated by the R2D. A response confirmation signal such as ACK / NACK is sent for activating / deactivating the R2D. In other words, the device sends a response confirmation signal for receiving the activated / deactivated R2D to the reader.

[0233] Option 3 also provides the following technologies: Option 3-1 and 3-2.

[0234] <Proposal 3: Option 3: Option 3-1> With regard to the instruction of semi-persistent state switching timing, the instruction of on / sleep / off period / periodicity from the period / offset are instructed.

[0235] For example, the semi-persistent state switching of the device between on and sleep is activated by the R2D indicated by the arrow A25a in Fig. 25. The semi-persistent state switching of the device between on and sleep is deactivated by the R2D indicated by the arrow A25b in Fig. 25. The offset, cycle, and on period from the activation instruction by the R2D indicated by the arrow A25a are instructed to the device.

[0236] The details are the same as those in <Proposal 3: Option 2: Option 2-1>, and therefore will not be explained here.

[0237] <Proposal 3: Option 3: Option 3-2> The on / off / sleep state pattern is applied to semi-permanent state switching timing instructions. The details are the same as those in <Proposal 3: Option 2: Option 2-2>, so the explanation is omitted here.

[0238] <Summary> As described above, in the present disclosure, the device state switching operation is clarified (defined). For example, the device state switching is instructed / conditions are defined. For example, the timing of the device state switching is defined. This allows the reader to control / recognize / understand the device state, and the device and the reader can communicate appropriately.

[0239] <Modifications> The suggestions / options described above may be combined.

[0240] Each of the suggestions / options discussed above may be applied on a case-by-case basis.

[0241] The indication / configuration may be carried in physical layer control information or higher layer payload. For example, the indication / configuration may be carried in MAC layer control information, Msg0 (paging) / Msg2 (RAR: Random Access Response) / Msg4, or unicast data. R2D may have the same meaning as above.

[0242] The instructions / configuration may be carried in the PRDCH or R2D timing acquisition signal (preamble / midamble / postamble) / synchronization signal.

[0243] A slot may have a time width of 1 ms (i.e., one slot in OFDM), for example. A slot may be a slotted-ALOHA slot.

[0244] A symbol may be one OFDM symbol, M chips in OOK, or one modulation symbol in PSK (Phase Shift Keying) / FSK (Frequency Shift Keying).

[0245] Different proposals / options may apply to R2D and D2R.

[0246] Different offers / options may apply to different device types.

[0247] Different suggestions / options may apply to different connection topologies.

[0248] Different proposals / options may apply to different R2D / D2R channels (PRDCH, PHY channel for R2D control, PDRCH, PHY channel for D2R control).

[0249] Different proposals / options may apply for different R2D / D2R information / formats / commands (R2D data, R2D control, R2D system information, R2D information triggering contention-based access, D2R data, D2R control, D2R ACK / NACK response, D2R response in contention-based access (Msg1 / Msg3)).

[0250] The device states may not be limited to the on state, the sleep state, and the off state. The device may have two of the on state, the sleep state, and the off state. The device may have four or more device states and may switch between four or more device states.

[0251] The timing of switching the device state may be the boundary of a time unit.

[0252] Terminology: A reader may be a D2R receiver. A reader may be either a BS or a UE.

[0253] The R2D transmitter and D2R receiver may be the same node or different nodes.

[0254] DT traffic is device terminated traffic, which may be traffic such as commands from the reader.

[0255] DO-DTT traffic is Device Originated-Device Terminated Trigger traffic, and may be traffic such as inventory.

[0256] Switch, change, set, and transition may be read interchangeably. Immediately before and previously may be read before. Immediately after may be read after.

[0257] <Reader Configuration> Fig. 26 is a block diagram showing an example of the configuration of a reader 10a according to an embodiment. The reader 10a includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The reader 10a communicates with the device 20 (see Fig. 27) wirelessly. The reader 10a may be an intermediate terminal or a terminal (for example, a SL terminal that communicates with the device 20).

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

[0259] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). 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 Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0260] 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 reader 10a transmits control information to the device 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0261] The reference signal included in the DL signal may include at least one of a demodulation reference signal (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 DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

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

[0263] The control unit 103 controls the communication operations of the reader 10 a, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102 .

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

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

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

[0267] Here, the control unit 103 may determine to transmit a downlink signal for switching the state. The transmission unit 101 may transmit the downlink signal to the device 20. The downlink signal may be R2D.

[0268] <Device Configuration> Fig. 27 is a block diagram showing an example of the configuration of a device 20 according to an embodiment. The device 20 is a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, for example, an A-IoT UE. The device 20 may be considered as a device that receives power through energy harvesting. For example, the device 20 may be considered as a device that receives power through CW supplied from the base station 10 or the reader 10a.

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

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

[0271] The transmitter 202 transmits the UL signal to the reader 10a. For example, the transmitter 202 transmits the UL signal under the control of the controller 203.

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

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

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

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

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

[0277] For example, the control unit 203 controls transmission of information to be fed back to the reader 10a. The information to be fed back to the reader 10a may include, for example, HARQ-ACK, channel state information (CSI), or a scheduling request (SR). The information to be fed back to the reader 10a may be included in UCI. The UCI is transmitted in the resources of the PUCCH.

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

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

[0280] Here, the receiving unit 201 may receive a downlink signal such as R2D. The control unit 203 may switch the device 20 from one of the on state, sleep state, and off state to another state based on the downlink signal. For example, the control unit 203 may switch the device state from the off state to the on state.

[0281] The control unit 203 may switch the state based on the downstream signal and further based on conditions.

[0282] The control unit 203 may switch the state based on a downlink signal received in the previous on state or sleep state.

[0283] When the control unit 203 receives a downlink signal in the on state, the control unit 203 may switch the state after completing reception of the downlink signal. The control unit 203 may switch the state immediately after completing reception of the downlink signal or every x time units.

[0284] The control unit 203 may switch the device 20 from one of the on state, sleep state, and off state to a state instructed by the downstream signal.

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

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

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

[0288] For example, a reader, a device, or the like 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. 28 is a diagram showing an example of the hardware configuration of a reader and a device according to this embodiment. The above-described reader 10a 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, and the like.

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

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

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

[0292] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these 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 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

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

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

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

[0298] The reader 10a and the device 20 may also 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0321] 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 reader 10a described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication device that receives power from energy harvesting, comprising: a receiving unit that receives a downstream signal; and a control unit that switches the communication device from one of an on state, a sleep state, and an off state to another state based on the downstream signal.

2. The communication device according to claim 1, wherein the control unit switches the state based on the downstream signal and conditions.

3. The communication device according to claim 1, wherein the control unit switches the state based on the downlink signal received in the previous on state or sleep state.

4. The communication device according to claim 1, wherein, when the control unit receives the downlink signal in an on state or a sleep state, the control unit switches the state after completing reception of the downlink signal.

5. The communication device according to claim 1, wherein the control unit switches the communication device from one of an on state, a sleep state, and an off state to a state instructed by the downlink signal.

6. A communication method in which a communication device powered by energy harvesting receives a downstream signal, and switches the communication device from one of an on state, a sleep state, and an off state to another state based on the downstream signal.

Images