Simple terminal, network device, radio communication system, and radio communication method

By incorporating control units and energy status reporting in Ambient IoT devices, the network can accurately determine device states, enhancing communication efficiency and reducing miscommunication.

WO2026084058A1PCT designated stage Publication Date: 2026-04-23NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-10-17
Publication Date
2026-04-23

AI Technical Summary

Technical Problem

Existing technologies struggle to accurately determine the status of Ambient IoT devices, particularly in states like sleep or off, leading to inefficiencies and potential miscommunication between the network and the devices.

Method used

Implementing a control unit in the simple terminal to manage a sleep state that does not support transmission and a transmission unit to send energy status reports based on uplink permissions or random access procedures, along with a network device that activates timers to determine device states and potential failures.

Benefits of technology

Enables the network to understand the status of Ambient IoT devices effectively, even in the absence of direct communication, by utilizing energy status reports and timers, thereby improving network efficiency and reducing miscommunication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025036660_23042026_PF_FP_ABST
    Figure JP2025036660_23042026_PF_FP_ABST
Patent Text Reader

Abstract

This simple terminal comprises: a control unit that controls a sleep state in which at least transmission is not supported; and a transmitting unit that transmits, to a network device, a report indicating an energy state on the basis of an uplink grant received from the network device, or transmits the report to the network device using a message used in a random access procedure.
Need to check novelty before this filing date? Find Prior Art

Description

Simple Terminal, Network Device, Wireless Communication System, and Wireless Communication Method

[0006] ,

[0005] ,

[0001] The present disclosure relates to a simple terminal, a network device, a wireless communication system, and a wireless communication method that support Ambient IoT.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is standardizing the 5th generation mobile communication system (also called 5G, New Radio (NR), or Next Generation (NG)). Furthermore, 3GPP is also proceeding with the standardization of the next generation, called Beyond 5G, 5G Evolution, or 6G.

[0003] Furthermore, in 3GPP Release-19, technologies related to a simple terminal (hereinafter referred to as an Ambient IoT device) having a simpler configuration than that of a UE (Ambient IoT) have been studied in order to support IoT (Internet of Things) (for example, Non-Patent Document 1).

[0004] 3GPP TR38.848 V18.0.0, September 2023

[0005] By the way, regarding the states of the Ambient IoT device, discussions are underway about states such as the ON state, OFF state, and SLEEP state. For example, the ON state is a state that supports at least transmission and reception. The OFF state is a state that does not support at least transmission and reception. The SLEEP state is a state that does not support at least transmission. Furthermore, discussions are also underway about using an Energy status report transmitted from the Ambient IoT device to the Reader when the Ambient IoT device does not have the energy to transmit subsequent messages.

[0006] Against this backdrop, the inventors, after diligent study, found a need to clarify the mechanism for the network (Reader) to understand the status of an Ambient IoT device in Ambient IoT.

[0007] Therefore, this disclosure was made to solve the above-mentioned problems and aims to provide a simple terminal, network device, wireless communication system, and wireless communication method that enable the network (Reader) side to understand the status of an Ambient IoT device in Ambient IoT.

[0008] The disclosed aspect is a simple terminal comprising: a control unit that controls a sleep state that does not support transmission; and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

[0009] The disclosed aspect is a network device comprising: a communication unit that communicates with a simple terminal that controls at least one of either a sleep state that does not support transmission or an off state that does not support transmission and reception; and a control unit that activates a timer in response to the transmission of a second message used in a paging or random access procedure, wherein the control unit determines, upon the expiration of the timer, that the state of the simple terminal is the sleep state or the off state, or that a failure has occurred due to a poor radio environment.

[0010] The disclosed aspect is a wireless communication system comprising a simple terminal and a network device, wherein the simple terminal comprises a control unit that controls a sleep state that does not support transmission, and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

[0011] The disclosed aspect is a wireless communication method comprising the steps of controlling a sleep state that does not support transmission, and transmitting a report indicating the energy state to a network device based on an uplink permission received from the network device, or transmitting the report to the network device using a message used in a random access procedure.

[0012] Figure 1 is an overall schematic diagram of the wireless communication system 10. Figure 2 is a diagram showing the frequency range used in the cellular network. Figure 3 is a diagram showing an example configuration of wireless frames, subframes, and slots used in the cellular network. Figure 4 is a functional block configuration diagram of the UE200. Figure 5 is a functional block configuration diagram of the network device 50. Figure 6 is a diagram for explaining Ambient IoT. Figure 7 is a diagram for explaining operation example 1. Figure 8 is a diagram for explaining operation example 1. Figure 9 is a diagram for explaining operation example 2. Figure 10 is a diagram for explaining operation example 2. Figure 11 is a diagram for explaining operation example 3. Figure 12 is a diagram for explaining operation example 3. Figure 13 is a diagram showing an example of the hardware configuration of the network device 50 and UE200. Figure 14 is a diagram showing an example configuration of the vehicle 2001.

[0013] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0014] (1) Overall schematic diagram 1 of the wireless communication system is an overall schematic diagram of the wireless communication system 10 according to the embodiment. The wireless communication system 10 has a terminal 200 (hereinafter referred to as UE (User Equipment) 200), a first network 10A and a second network 10B.

[0015] The first network 10A includes a radio access network 20A and a core network 30A. The radio access network 20A includes a base station 100A that performs wireless communication with the UE200. However, the first network 10A may not have the radio access network 20A but may have the base station 100A. The first network 10A may not have the core network 30A. The base station 100A may consist of a DU (Distributed Unit) and a CU (Central Unit). The DU may perform processing at the MAC layer or lower. The CU may perform processing at the PDCP layer or higher.

[0016] The first network 10A may be a network conforming to new technology (6G). 6G may be referred to as Beyond 5G or 5G Evolution. The first network 10A may be a network conforming to existing technology (5G). 5G may be referred to as 5G New Radio (NR).

[0017] The second network 10B includes a radio access network 20B and a core network 30B. The radio access network 20B includes a base station 100B that performs wireless communication with the UE 200. However, the second network 10B may not have the radio access network 20B but may have the base station 100B. The second network 10B may not have the core network 30B. The base station 100B may be composed of a DU and a CU.

[0018] The second network 10B may be a network that conforms to existing technology (5G). 5G may also be called 5G New Radio (NR). The second network 10B may be a network that conforms to new technology (6G). 6G may also be called Beyond 5G or 5G Evolution.

[0019] Here, the first network 10A and the second network 10B only need to have different wireless access methods. For example, the wireless access method may be a cellular network wireless access method such as 5G, Beyond 5G, 5G Evolution, or 6G.

[0020] In the following, base stations 100A and 100B may be collectively referred to as base station 100 or gNB100. Core networks 30A and 30B may be collectively referred to as core network 30.

[0021] Firstly, the cellular network may support multiple frequency ranges (FRs) as shown in Figure 2. For example, as shown in Figure 2, the cellular network supports FR1, FR2-1, and FR2-2. The frequency bands for each FR are as follows:

[0022] FR1: 410 MHz to 7.125 GHz FR2-1: 24.25 GHz to 52.6 GHz FR2-2: Over 52.6 GHz to 71 GHz In FR1, 15, 30, or 60 kHz Sub-Carrier Spacing (SCS) may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and 60 kHz or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0023] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0024] Furthermore, cellular networks may support higher frequency bands than those used by FR2. Specifically, cellular networks may support frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz.

[0025] Secondly, the cellular network may correspond to the wireless frames, subframes, and slots shown in Figure 3.

[0026] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol duration (and slot duration). In addition to 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz, 480kHz, 960kHz, etc., may also be used for the SCS.

[0027] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols, 56 symbols). In addition, the number of slots per subframe may differ depending on the SCS.

[0028] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0029] (2) Functional block configuration of the wireless communication system The functional block configuration of the wireless communication system 10 will be described below.

[0030] First, we will describe the functional block configuration of the UE200.

[0031] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.

[0032] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with 5G or 6G. The wireless signal transceiver unit 210 supports Massive MIMO, CA using multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.

[0033] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0034] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0035] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0036] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

[0037] The control signal / reference signal processing unit 240 performs processing using reference signals (RS) such as the Demodulation Reference Signal (DM-RS) and the Phase Tracking Reference Signal (PT-RS).

[0038] DM-RS is a terminal-specific reference signal (pilot signal) between the base station and the terminal used to estimate the fading channel used for data demodulation. PT-RS is a terminal-specific reference signal intended to estimate phase noise, which is a problem in the high-frequency band.

[0039] In addition to DM-RS and PT-RS, the reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

[0040] Furthermore, channels include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH), among others.

[0041] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel may also be interpreted as a shared channel.

[0042] Here, the control signal / reference signal processing unit 240 may receive downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

[0043] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI is applied. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI is applied. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI is applied. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI is applied. The time domain resource is identified by the value stored in the TDRA field and an information element (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI is applied. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by the RRC message or may be identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which the DCI is applied. The value stored in the NDI is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

[0044] The encoding / decoding unit 250 performs data segmentation / concatenation, channel coding / decoding, etc. for each predetermined communication destination (gNB100 or another gNB).

[0045] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into a predetermined size, and performs channel coding on the divided data. Further, the encoding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230, and concatenates the decoded data.

[0046] The data transmission / reception unit 260 performs transmission and reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDU / SDU in a plurality of layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). Further, the data transmission / reception unit 260 performs error correction and retransmission control of data based on Hybrid Automatic Repeat Request (HARQ).

[0047] The control unit 270 controls each functional block constituting the UE 200.

[0048] In an embodiment, when the UE 200 is a simple terminal (hereinafter, Ambient IoT device) having a simpler configuration than a general UE, the control unit 270 may constitute a control unit that controls a sleep state that does not support at least transmission. In addition to the sleep state (hereinafter, SLEEP state), the control unit 270 may control an on state (hereinafter, ON state), or may control an off state (OFF state). For example, the SLEEP state is at least a state that does not support transmission. The ON state is at least a state that supports at least transmission and reception. The OFF state is at least a state that does not support transmission and reception.

[0049] In this embodiment, when the UE200 is an Ambient IoT device, the wireless signal transmission / reception unit 210 may be configured as a transmission unit that transmits an Energy status report to the network device based on an uplink grant (hereinafter referred to as UL grant) received from the network device, or transmits an Energy status report to the network device using a message used in a random access procedure.

[0050] In this embodiment, when the UE200 is an Ambient IoT device, the wireless signal transmission / reception unit 210 may be configured as a receiving unit that receives an uplink grant (UL grant) from a network device by sending a scheduling request or a random access procedure.

[0051] Secondly, the functional block configuration of the network device 50 will be described. The network device 50 is a device that communicates directly with a simple terminal (Ambient IoT device) which has a simpler configuration than the UE200 in the Ambient IoT described later. For example, in Ambient IoT Topology 1, the network device 50 may be a base station (gNB100), in Ambient IoT Topology 2, the network device 50 may be an Intermediate node, in Ambient IoT Topology 3, the network device 50 may be an Assisting node, and in Ambient IoT Topology 4, the network device 50 may be a UE200. The network device 50 may also be called a Reader.

[0052] As shown in Figure 5, the network device 50 includes a receiving unit 51, a transmitting unit 52, and a control unit 53.

[0053] The receiving unit 51 receives various signals from the Ambient IoT device. For example, the receiving unit 51 may receive an uplink signal from the Ambient IoT device. The uplink signal may include an uplink control signal or an uplink data signal. The uplink signal may be received via the PDRCH (Physical Device Reader Channel).

[0054] The receiving unit 51 may receive various signals from the gNB100 or the core network 30.

[0055] The transmitter 52 transmits various signals to the Ambient IoT device. For example, the transmitter 52 may transmit a downlink signal to the Ambient IoT device. The downlink signal may include a downlink control signal or a downlink data signal. The downlink signal may be transmitted via PRDCH (Physical Reader Device Channel).

[0056] The transmitting unit 52 may transmit various signals to the gNB100 or the core network 30.

[0057] The control unit 53 controls each block that makes up the network device 50.

[0058] In this embodiment, the receiving unit 51 and the transmitting unit 52 may constitute a communication unit that communicates with an Ambient IoT device that controls at least one of the following states: a sleep state that does not support transmission, or an off state that does not support transmission or reception. The Ambient IoT device may be referred to as an A-IoT device.

[0059] In this embodiment, the control unit 53 may be configured to activate a timer in response to the transmission of a second message (hereinafter referred to as Msg.2) used in paging or a random access procedure. The control unit 53 determines, upon the expiration of the timer, that the state of the simple terminal (A-IoT device) is either sleep state or off state.

[0060] (3) Ambient IoT Firstly, A-IoT devices may be classified into types such as Device A, Device B, Device C, etc.

[0061] Device A may be a device that does not have storage for accumulating energy (e.g., power) and performs backscattering transmission without performing its own signal generation / amplification.

[0062] Device B may be a device that has storage for accumulating energy (e.g., power) and performs backscattering transmission without generating its own signals. For example, the energy stored in the storage may be used to amplify the reflected signal.

[0063] Device C may not have storage for storing energy (e.g., power) and may be a device that generates its own signals.

[0064] An A-IoT device may be a device defined in 3GPP TR38.848 V18.0.0. An A-IoT device has a simpler configuration than a typical UE configuration. The characteristics of an A-IoT device may be defined by the following elements:

[0065] - The output and complexity of the A-IoT device are simpler than those of a typical UE. - The coverage of the A-IoT device is achieved with a simpler configuration than that of a typical UE. - The data rate of the A-IoT device is achieved with a simpler protocol stack than that of a typical UE. - The maximum message size of the A-IoT device is achieved with a simpler protocol stack than that of a typical UE. - The delay of the A-IoT device is set to meet the target delay using a different access method and signaling procedure than that of a typical UE. - The positioning method for the A-IoT device is a method applicable to the topology described later in order to meet the required accuracy.

[0066] - Regarding the connection density of A-IoT devices, multiple efficient access methods different from those of a typical UE will be introduced. - Regarding the movement speed of A-IoT devices, a physical layer configuration different from that of a typical UE will be introduced. Secondly, the topology of the A-IoT device may be as shown in Figure 6.

[0067] In Topology 1, the A-IoT device may perform UL transmission and DL reception with the base station (BS in Figure 6).

[0068] In Topology 2, the A-IoT device may perform UL transmission and DL reception with the base station (BS in Figure 6) via an Intermediate node. The Intermediate node may be an IAB (Integrated Access and Backhaul) node or a general UE. The Intermediate node may also be a DU. The general UE may be a UE defined separately from the A-IoT device. The general UE may have a more complex configuration than the A-IoT device.

[0069] In Topology 3, the A-IoT device may perform DL reception with the base station (BS in Figure 6) and UL transmission with the base station (BS in Figure 6) via the Assisting node. The Intermediate node may be an IAB node or a general UE. The Intermediate node may also be a DU.

[0070] Topology 4 may perform general UE and UL transmission and DL reception. Topology 4 may also assume D2D communication between a general UE and an A-IoT device.

[0071] Note that the term "UE" (Unified End User) is used to distinguish it from A-IoT devices, and may also be referred to as an existing UE or a standard UE.

[0072] (4) Issues Against the backdrop of the introduction of the A-IoT device described above, discussions are underway regarding the states of the A-IoT device, such as ON state, OFF state, and SLEEP state. For example, the ON state is a state that supports at least transmission and reception. The OFF state is a state that does not support at least transmission and reception. The SLEEP state is a state that does not support transmission. Furthermore, consideration is being given to using the Energy status report sent from the A-IoT device to the Reader when the A-IoT device does not have the energy to send a subsequent message.

[0073] Against this backdrop, the inventors, after diligent study, found a need to clarify the mechanism for the network (Reader) to understand the status of an A-IoT device in Ambient IoT.

[0074] (5) Example of operation In order to solve the above-mentioned problems, the following operations may be performed.

[0075] (5-1) Operation Example 1 In Operation Example 1, the A-IoT device may send an Energy status report to the network device 50 (Reader) based on the uplink grant received from the network device 50. The following options are possible for Operation Example 1.

[0076] In Option 1-1, the A-IoT device may receive a UL grant from network 50 to send an Energy status report by sending a scheduling request.

[0077] For example, as shown in Figure 7, in step S10, the A-IoT device sends a scheduling request to the Reader. In step S11, the Reader sends a UL grant to the A-IoT device. In step S12, the A-IoT device uses the UL grant to send an Energy status report to the Reader.

[0078] In option 1-2, the A-IoT device may receive a UL grant from network 50 to send an Energy status report via a random access procedure.

[0079] For example, as shown in Figure 8, in step S20, the A-IoT device sends Msg.1 to the Reader. Msg.1 may also be called a PRACH Preamble or a RA (Random Access) Preamble. In step S21, the Reader sends Msg.2, which includes a UL grant, to the A-IoT device. Msg.2 may also be called a RAR (Random Access Response). In step S22, the A-IoT device sends an Energy status report to the Reader using the UL grant.

[0080] While not strictly required, sending and receiving Msg.3 and Msg.4 may be omitted. Msg3 may be referred to as RRC Connection Request. Msg4 may be referred to as RRC Connection Setup.

[0081] In options 1-3, the A-IoT device may send an Energy status report to the Reader using a pre-configured UL resource (UL Configured Grant).

[0082] In Operation Example 1, the Energy status report may include a value (e.g., %) indicating the percentage of the battery remaining capacity relative to the battery capacity of the A-IoT device, or a value (e.g., mAh) indicating the remaining battery capacity of the A-IoT device. The Energy status report may also include a value (e.g., msec) indicating the time taken to transition from the ON state to the SLEEP state.

[0083] In Operation Example 1, UL grant or UL Configured Grant may be permission to send an Energy status report. In other words, UL grant or UL Configured Grant does not have to be used to send uplink signals other than the Energy status report.

[0084] (5-2) Operation Example 2 In Operation Example 2, the network device 50 (Reader) may start the timer in response to the transmission of a second message (Msg.2) used in paging or random access procedures. The network device 50 (Reader) may determine that the state of the A-IoT is SLEEP state or OFF state upon the expiration of the timer. The timer may be a timer newly introduced for the A-IoT device. In Operation Example 2, the timer is referred to as New timer #1. The following options are possible for Operation Example 2.

[0085] In Option 2-1, New timer #1 is a timer that is activated by sending a Paging message. New timer #1 stops upon receiving Msg.1 (PRACH Preamble or RA Preamble). The Reader activates New timer #1 by sending a Paging message, and determines that the A-IoT state is ON if it receives Msg.1 before New timer #1 expires. The Reader activates New timer #1 by sending a Paging message, and determines that the A-IoT state is SLEEP state or OFF state if New timer #1 expires without receiving Msg.1.

[0086] For example, as shown in Figure 9, in step S30, the Reader sends Paging to the A-IoT device. In step S31, the Reader starts New timer #1. In step S32, the Reader waits for Msg.1 to be sent from the A-IoT device. Msg.1 may also be called PRACH Preamble or RA Preamble. In step S33, the Reader determines the state of the A-IoT device. Specifically, if the Reader receives Msg.1 before New timer #1 expires, it determines that the A-IoT is in the ON state. On the other hand, if New timer #1 expires without receiving Msg.1, the Reader determines that the A-IoT is in the SLEEP state or OFF state.

[0087] In Option 2-1, possible reasons for not receiving Msg.1 before New timer #1 expires include the A-IoT being in the SLEEP state or OFF state, and failure due to a poor radio environment. In Option 2-1, the operation that determines the A-IoT is in the SLEEP state or OFF state may be rephrased as the operation that assumes the A-IoT is in the SLEEP state or OFF state.

[0088] In Option 2-2, New timer #1 is a timer that is activated by the transmission of Msg.2. New timer #1 stops upon receipt of Msg.3. The Reader activates New timer #1 by transmitting Msg.2, and determines that the A-IoT state is ON if Msg.3 is received before New timer #1 expires. The Reader activates New timer #1 by transmitting Msg.2, and determines that the A-IoT state is SLEEP state or OFF state if New timer #1 expires without receiving Msg.3.

[0089] For example, as shown in Figure 10, in step S40, the Reader sends Paging to the A-IoT device. In step S41, the A-IoT device sends Msg.1 to the Reader. Msg.1 may also be called PRACH Preamble or RA Preamble. In step S42, the Reader sends Msg.2 to the A-IoT device. Msg.2 may also be called RAR. In step S43, the Reader starts New timer #1. In step S44, the Reader waits for Msg.3 to be sent from the A-IoT device. Msg.3 may also be called RRC Connection Request. In step S45, the Reader determines the state of the A-IoT device. Specifically, the Reader determines that the state of the A-IoT is ON if it receives Msg.3 before New timer #1 expires. On the other hand, if New timer #1 expires without receiving Msg.3, the Reader determines that the A-IoT state is either SLEEP state or OFF state.

[0090] In Option 2-2, since Msg.1 has been received, the reason why Msg.3 cannot be received before New timer #1 expires does not need to be considered as failure due to a poor radio environment. However, since it is possible that the radio environment may deteriorate after receiving Msg.1, the reason for failure due to a poor radio environment may be considered. In such cases, the operation of determining that the state of A-IoT is SLEEP state or OFF state may be reinterpreted as the operation of assuming that the state of A-IoT is SLEEP state or OFF state.

[0091] In the case where Topology 2 is assumed in Operation Example 2 (i.e., the Reader is an Intermediate node), New timer #1 may be set on the Intermediate node (e.g., UE200) by a gNB connected to the Intermediate node. For example, the setting may include the setting of New timer #1 in Option 2-1 (such as the time to be set for New timer #1), or it may include the setting of New timer #1 in Option 2-2 (such as the time to be set for New timer #1).

[0092] (5-3) Operation Example 3 In Operation Example 3, the network device 50 (Reader) may start the timer in response to the transmission of a second message (Msg.2) used in paging or random access procedures. The network device 50 (Reader) may determine that the failure was due to a poor radio environment upon the timer's expiration. The timer may be a timer newly introduced for the A-IoT device. In Operation Example 3, the timer is referred to as New timer #2.

[0093] In Operation Example 3, we focus on the case where the A-IoT device is charging. For example, we consider a case where the A-IoT device is charging in the SLEEP state, and a transition from the SLEEP state to the ON state is expected due to the charging. The time set in New timer #2 is determined based on the charging time of the A-IoT device.

[0094] The time set for New timer #2 may be the charging time of the A-IoT device, a shorter time (e.g., 80% of the charging time of the A-IoT device), or a longer time (e.g., 120% of the charging time of the A-IoT device).

[0095] The charging time for the A-IoT device may be the time it takes for the battery level to go from 0% to full. The charging time for the A-IoT device may also be notified to the Reader by the A-IoT device.

[0096] Operation Example 3 differs from Operation Example 2 in that New timer #2 is set based on the charging time of the A-IoT device and the failure is determined to be due to a poor radio environment. The following options are possible for Operation Example 3.

[0097] In Option 3-1, New timer #2 is a timer that is activated by the transmission of Paging. New timer #2 stops upon receipt of Msg.1 (PRACH Preamble or RA Preamble). The Reader activates New timer #2 by transmitting Paging, and determines that the A-IoT state is ON if Msg.1 is received before New timer #2 expires. The Reader activates New timer #2 by transmitting Paging, and determines that the failure is due to a poor radio environment if New timer #2 expires without receiving Msg.1.

[0098] For example, as shown in Figure 11, in step S50, the Reader sends Paging to the A-IoT device. In step S51, the Reader starts New timer #2. The Reader may consider the A-IoT device to be charging while New timer #2 is running, or it may consider the A-IoT device to be in SLEEP state or OFF state while New timer #2 is running. In step S52, the Reader waits for Msg.1 to be sent from the A-IoT device. Msg.1 may be called PRACH Preamble or RA Preamble. In step S53, the Reader determines the state of the A-IoT device. Specifically, if the Reader receives Msg.1 before New timer #2 expires, it determines that the A-IoT is in ON state. On the other hand, if New timer #2 expires without receiving Msg.1, the Reader determines that the reason is a failure due to a poor radio environment.

[0099] In Option 3-2, New timer #2 is a timer that is activated by the transmission of Msg.2. New timer #2 stops upon receipt of Msg.3. The Reader activates New timer #2 by transmitting Msg.2, and determines that the A-IoT state is ON if Msg.3 is received before New timer #2 expires. The Reader activates New timer #2 by transmitting Msg.2, and determines that the failure is due to a poor radio environment if New timer #2 expires without receiving Msg.3.

[0100] For example, as shown in Figure 12, in step S60, the Reader sends Paging to the A-IoT device. In step S61, the A-IoT device sends Msg.1 to the Reader. Msg.1 may be called PRACH Preamble or RA Preamble. In step S62, the Reader sends Msg.2 to the A-IoT device. Msg.2 may be called RAR. In step S63, the Reader starts New timer #2. The Reader may consider the A-IoT device to be charging while New timer #2 is running, or it may consider the A-IoT device to be in SLEEP state or OFF state while New timer #2 is running. In step S64, the Reader waits for Msg.3 to be sent from the A-IoT device. Msg.3 may be called RRC Connection Request. In step S65, the Reader determines the state of the A-IoT device. Specifically, the Reader determines that the A-IoT state is ON if it receives Msg.3 before New timer #2 expires. On the other hand, if New timer #2 expires without receiving Msg.3, the Reader determines that the failure is due to a poor radio environment.

[0101] In Operation Example 3, the Reader may maintain the UL resource that allows A-IoT to access the Reader from the start to the end of New timer #2.

[0102] In Operation Example 3, in the case where Topology 2 is assumed (i.e., the Reader is an Intermediate node), New timer #2 may be set on the Intermediate node (e.g., UE200) by a gNB connected to the Intermediate node. For example, the setting may include the setting of New timer #2 in Option 3-1 (such as the time to be set for New timer #2), or it may include the setting of New timer #2 in Option 3-2 (such as the time to be set for New timer #2).

[0103] (5-4) Two or more operation examples selected from operation example 1, operation example 2, and operation example 3 may be combined.

[0104] For example, option 2-1 from operation example 2 and option 3-1 from operation example 3 may be combined. In such a case, the time set for New timer #2 may be longer than the time set for New timer #1. The Reader may determine that the state of A-IoT is SLEEP state or OFF state between the expiration of New timer #1 and the start of New timer #2.

[0105] For example, option 2-2 from operation example 2 and option 3-2 from operation example 3 may be combined. In such a case, the time set for New timer #2 may be longer than the time set for New timer #1. The Reader may determine that the state of A-IoT is SLEEP state or OFF state between the expiration of New timer #1 and the start of New timer #2.

[0106] For example, option 2-1 from operation example 2 and option 3-2 from operation example 3 may be combined, or option 2-2 from operation example 2 and option 3-1 from operation example 3 may be combined.

[0107] (6) Operation and Effects In one embodiment, the A-IoT device may send an Energy status report to the network device 50 (Reader) based on an UL grant received from the network device 50 (Reader) (for example, an UL grant for an Energy status report) (Operation Example 1). With this configuration, the mechanism for the network (Reader) to understand the status of the A-IoT device is clarified, and even if there is no communication between the A-IoT device and the Reader, the network (Reader) can understand the status of the Ambient IoT device through the Energy status report.

[0108] In this embodiment, the network device 50 (Reader) may start a timer in response to the transmission of a second message (Msg.2) used in paging or random access procedures, and determine or consider the state of the A-IoT to be SLEEP state or OFF state upon the expiration of the timer (Operation Example 2). With this configuration, the mechanism for the network (Reader) to grasp the state of the A-IoT device is clarified, and even if there is no communication between the A-IoT device and the Reader, the state of the Ambient IoT device can be grasped on the network (Reader) side by whether or not the timer (New timer #1) has expired.

[0109] In this embodiment, the network device 50 (Reader) starts a timer in response to the transmission of a second message (Msg.2) used in paging or random access procedures, and determines that the failure is due to a poor radio environment when the timer expires. With this configuration, the mechanism for the network (Reader) to understand the status of the A-IoT device is clarified, and even if there is no communication between the A-IoT device and the Reader, a failure due to a poor radio environment can be detected by whether or not the timer (New timer #2) has expired.

[0110] (7) Other Embodiments Although the contents of the present invention have been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0111] Although not specifically mentioned in the disclosure above, the choice of which of Operation Examples 1 to 3 to use (which mode to use) may be set by a higher-layer parameter. The choice of which of each option in Operation Examples 1 to 3 to use (which mode to use) may be set by a higher-layer parameter. Which mode to support may be reported by the A-IoT device as UE capability(ies). Which mode to use may be predefined in the wireless communication system 20. Which mode to use may be set by a higher-layer parameter and reported by the A-IoT device as UE capability(ies).

[0112] Although not specifically mentioned in the disclosure above, the following UE capability(ies) may be defined. UE capability(ies) may be defined for each A-IoT device, for each FR (e.g., FR1, FR2, FR2-1, FR2-2, FR3), for each SCS, for each band, for each BC (Bandwidth Combination), or for each FC (Frequency Combination). UE capability(ies) may be included in the signals reported from the A-IoT device to the network device 50, or in the signals (RRC configuration) set from the network device 50 to the A-IoT device.

[0113] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0114] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0115] Furthermore, the network device 50 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 13 shows an example of the hardware configuration of the device. As shown in Figure 13, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0116] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0117] Each functional block of the device (see Figures 4 and 5) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0118] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0119] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0120] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0121] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc., that can execute a method according to one embodiment of this disclosure.

[0122] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., a card, stick, key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0123] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0124] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0125] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0126] 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 different buses may be configured for each device.

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

[0128] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0129] Each aspect / embodiment described herein may be applied to at least one of the following: Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0130] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0131] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0132] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0133] The input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0134] The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0135] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0136] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0137] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0138] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0139] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0140] The terms “system” and “network” as used in this disclosure are interchangeable.

[0141] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0142] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0143] In this disclosure, terms such as "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0144] A base station can house one or more (e.g., three) cells (also called sectors). When a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0145] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

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

[0147] 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 several other appropriate terms.

[0148] At least one of the base station and the mobile station may be called 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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0149] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0150] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0151] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.

[0152] A subframe may further consist 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.

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

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

[0155] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (or PUSCH) mapping type B.

[0156] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0157] 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. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 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.

[0158] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0159] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0160] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0161] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0162] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0164] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0165] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0166] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0167] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a given BWP.

[0168] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0169] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0170] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0171] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0173] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0174] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0175] Any reference to elements using the designations “first,” “second,” etc., as 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 way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed therein, or that the first element must precede the second element in any way.

[0176] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0177] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0178] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0179] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0180] Figure 14 shows an example of the configuration of vehicle 2001. As shown in Figure 14, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right 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.

[0181] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0182] 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, which is operated by the user.

[0183] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0185] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0186] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0188] 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

[0189] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0190] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, etc., installed in the vehicle 2001.

[0191] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0192] (Note) The disclosure described above may also be expressed as follows:

[0193] The first feature is a simple terminal comprising a control unit that controls a sleep state that does not support transmission, and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

[0194] The second feature is a simplified terminal that, in the first feature, includes a receiving unit that receives the uplink permission from the network device by sending a scheduling request or a random access procedure.

[0195] The third feature is that, in the first feature, the message used in the random access procedure is at least one of the first message or the third message, and is a simple terminal.

[0196] The fourth feature is a network device comprising: a communication unit that communicates with a simple terminal that controls at least one of the following states: a sleep state that does not support transmission, or an off state that does not support transmission and reception; and a control unit that starts a timer in response to the transmission of a second message used in paging or random access procedures, wherein the control unit determines, upon the expiration of the timer, that the state of the simple terminal is the sleep state or the off state, or that a failure has occurred due to a poor radio environment.

[0197] The fifth feature is a wireless communication system comprising a simple terminal and a network device, wherein the simple terminal comprises a control unit that controls a sleep state that does not support transmission, and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

[0198] The sixth feature is a wireless communication method comprising the steps of controlling a sleep state that does not support transmission, and transmitting a report indicating the energy state to the network device based on an uplink permission received from the network device, or transmitting the report to the network device using a message used in a random access procedure.

[0199] This patent application claims priority based on Japanese Patent Application No. 2024-181506, filed on 17 October 2024, and the entire contents of Japanese Patent Application No. 2024-181506 are incorporated herein by reference.

[0200] 10 Wireless Communication System 10A First Network 10B Second Network 20A, 20B Wireless Access Network 30A, 30B Core Network 50 Network Device 51 Receiving Unit 52 Transmitting Unit 53 Control Unit 100A, 100B Base Station 200 UE 210 Wireless Signal Transmitting / Receiving Unit 220 Amplifier Unit 230 Modulation / Demodulation Unit 240 Control Signal / Reference Signal Processing Unit 250 Encoding / Decoding Unit 260 Data Transmitting / Receiving Unit 270 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication Device 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Unit 2004 Accelerator Pedal 2005 Brake Pedal 2006 Shift Lever 2007 Front wheels (left and right) 2008 Rear wheels (left and right) 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A simple terminal comprising: a control unit that controls a sleep state that does not support transmission; and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

2. The simplified terminal according to claim 1, further comprising a receiving unit that receives the uplink permission from the network device by sending a scheduling request or a random access procedure.

3. The simplified terminal according to claim 1, wherein the message used in the random access procedure is at least one of the first message or the third message.

4. A network device comprising: a communication unit that communicates with a simple terminal that controls at least one of the following states: a sleep state that does not support transmission, or an off state that does not support transmission and reception; and a control unit that starts a timer in response to the transmission of a second message used in a paging or random access procedure, wherein the control unit determines, upon the expiration of the timer, that the state of the simple terminal is the sleep state or the off state, or that a failure has occurred due to a poor radio environment.

5. A wireless communication system comprising a simple terminal and a network device, wherein the simple terminal comprises a control unit that controls a sleep state that does not support transmission, and a transmission unit that transmits a report indicating the energy status to the network device based on an uplink permission received from the network device, or transmits the report to the network device using a message used in a random access procedure.

6. A wireless communication method comprising the steps of controlling a sleep state that does not support transmission, and transmitting a report indicating the energy state to a network device based on an uplink permission received from the network device, or transmitting the report to the network device using a message used in a random access procedure.

Citation Information

Patent Citations

  • D2D Connection Recovery Scheme

    JP2015515803A

  • Method and apparatus for terminal proximity monitoring in wireless communication system

    JP2017529763A