Internet of Things signal sending method and device thereof

Abstract

The invention discloses an Internet of Things signal sending method and equipment thereof. Wherein the device may receive a configuration from the network node. The device may send a command to the Internet of Things device according to the configuration. Moreover, the device can receive a backscattering signal from the Internet of Things device. Wherein the backscatter signal is generated based on a carrier, and the carrier may be provided by a device or transmitter. The Internet of Things signal sending method and the device thereof provided by the invention can effectively execute an environmental / passive Internet of Things communication technology.

Description

Technical Field

[0001] The present invention generally relates to mobile communications, and more particularly to IoT signaling associated with reader devices and IoT devices in mobile communications. Background Art

[0002] Unless otherwise indicated, the approaches described in this section are not prior art to the claims listed below and are not admitted to be prior art by inclusion in this section.

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0004] These multiple access technologies have been adopted by various telecommunication standards, providing a common protocol that enables different wireless devices to communicate at a city, country, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (for example, leveraging the Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology requires further improvements. These improvements may also apply to other multiple access technologies and the telecommunication standards that adopt these technologies.

[0005] Ambient IoT (A-IoT) communications are a key component of future wireless communications. Generally, A-IoT devices require low complexity and low power consumption. Therefore, backscattering technology is a suitable method for A-IoT communications.

[0006] Therefore, how to perform A-IoT communication in a wireless communication environment such as 5G NR has become an important issue for newly developed wireless communication networks. Summary of the Invention

[0007] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, key points, benefits, and advantageous effects of the novel and non-obvious technologies described herein. Selected embodiments are further described in the detailed description below. Accordingly, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0008] An object of the present invention is to provide solutions, concepts, designs, systems, methods, and apparatuses related to IoT signaling for devices (e.g., readers and / or transmitters), network nodes, and IoT devices in mobile communications. It is believed that by implementing one or more of the proposed solutions described herein, the aforementioned problems will be avoided or otherwise mitigated.

[0009] In one aspect, a method may involve a device receiving a configuration from a network node. The method may also involve the device sending a command to an Internet of Things device based on the configuration. The method may also involve the device receiving a backscatter signal from the Internet of Things device. The backscatter signal may be generated based on a carrier wave.

[0010] In another aspect, a method may involve a network node transmitting a carrier wave to an IoT device via a transmitter. The method may also involve the network node transmitting a command to the IoT device. The method may also involve the network node receiving a backscattered signal from the IoT device, and generating the backscattered signal based on the command and the carrier wave.

[0011] In another aspect, a method may involve a network node determining a configuration for a user equipment (UE). The configuration may indicate an operating mode of the UE for communication between the UE and an Internet of Things device. The method may also involve the network node sending the configuration to the UE.

[0012] In another aspect, a method may involve an IoT device receiving a command from a reader. The method may also involve the IoT device receiving a carrier wave from a reader or transmitter. The method may also involve the IoT device sending a backscattered signal to the reader. The backscattered signal is generated based on the carrier wave.

[0013] The Internet of Things signal transmission method and device provided by the present invention can effectively implement environmental / passive Internet of Things communication technology.

[0014] It is worth noting that although the description provided herein may be in the context of certain radio access technologies, networks, and network topologies (e.g., fifth generation systems (5GS) and 4G EPS mobile networks), the concepts, solutions, and any variations / derivatives thereof may be implemented on, for, and through any other type of radio access technologies, networks, and network topologies, such as, but not limited to, Ethernet, Universal Terrestrial Radio Access Network (UTRAN), E-UTRAN, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS) / Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network (GERAN), Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial Internet of Things (IIoT), Narrowband Internet of Things (NB-IoT), 6G, and any future developed network technologies. Therefore, the scope of the present invention is not limited to the examples described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings are included to provide a further understanding of the invention and are incorporated into and constitute a part of this invention. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. It will be understood that the drawings are not necessarily drawn to scale in order to clearly illustrate the concepts of the invention, and some components shown may be shown at a scale that exceeds the dimensions of the actual embodiment.

[0016] Figure 1 is an example scenario diagram of a communication environment that describes various solutions and schemes that can be implemented in the present invention.

[0017] Figure 2 1 is an example scenario diagram describing an A-IoT topology structure according to an embodiment of the present invention.

[0018] Figure 3 FIG. 1 is an example scenario diagram describing another A-IoT topology according to an embodiment of the present invention.

[0019] Figure 4 FIG. 1 is an example scenario diagram describing another A-IoT topology according to an embodiment of the present invention.

[0020] Figure 5 FIG. 1 is an example scenario diagram describing another A-IoT topology according to an embodiment of the present invention.

[0021] Figure 6 is a block diagram illustrating an example communication system according to an embodiment of the present disclosure.

[0022] Figure 7 is a flowchart describing an example process according to an embodiment of the present disclosure.

[0023] Figure 8 is a flowchart describing an example process according to another embodiment of the present disclosure.

[0024] Figure 9 is a flowchart describing an example process according to another embodiment of the present disclosure.

[0025] Figure 10 is a flowchart describing an example process according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrations of the claimed subject matter, which can be implemented in various forms. However, the present invention can be implemented in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. On the contrary, these multiple exemplary embodiments and implementations are provided so that the description of the present invention is comprehensive and complete, and will fully convey the scope of the present invention to those with ordinary knowledge in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0027] Overview

[0028] Embodiments of the present invention relate to various technologies, methods, schemes, and / or solutions for IoT signal transmission related to user equipment and network devices in mobile communications. According to the present invention, multiple possible solutions may be implemented individually or in combination. That is, while these possible solutions are described below individually, two or more of these possible solutions may also be implemented in combination or in another manner.

[0029] Figure 1 FIG1 is a diagram illustrating an example scenario 100 of a communication environment that can be implemented according to various solutions and embodiments of the present invention. Scenario 100 involves a user equipment (UE) 110 wirelessly communicating with a network 120 (e.g., a wireless network including a non-terrestrial network (NTN) and a terrestrial network (TN)) via a terrestrial network node 125 (e.g., an evolved Node B (eNB), a next-generation Node B (gNB), or a transmit / receive point (TRP)) and / or a non-terrestrial network node 128 (e.g., a satellite). For example, the terrestrial network node 125 and / or the non-terrestrial network node 128 can form a non-terrestrial network (NTN) serving cell for wireless communication with the UE 110. In some implementations, the UE 110 can be an Internet of Things (IoT) device, such as a narrowband Internet of Things (NB-IoT) UE or an enhanced machine type communication (eMTC) UE (e.g., a bandwidth-reduced low complexity (BL) UE or a coverage-enhanced (CE) UE). In such a communication environment, UE 110, network 120, terrestrial network node 125, and non-terrestrial network node 128 can implement various solutions related to improving IoT signal transmission processes according to the present invention, as described below. It is worth noting that while various proposed solutions may be described separately below, in actual implementation, some or all of the proposed solutions may be used or implemented in conjunction with each other in other ways. Of course, each proposed solution may also be used or implemented separately or individually.

[0030] According to an embodiment of the present invention, in an IoT topology (e.g., Topology 1), a network node can transmit a carrier wave (CW) to an IoT device (e.g., an Ambient / Passive IoT (A-IoT) device) via a transmitter. The network node can also send commands to the IoT device. Furthermore, the network node can receive backscattered signals from the IoT device. A backscattered signal can be generated based on the command and the CW.

[0031] In one embodiment, the network node may include a transmitter. That is, the network node may function as both a reader and a transmitter in IoT communications, meaning the network node can directly send a CW to an IoT device. In another embodiment, the network node may only function as a reader in IoT communications, meaning the network node can send a CW to an IoT device via a transmitter. For example, the network node may send a command to the transmitter (e.g., via a wired or wireless signal) instructing the transmitter to send a CW to the IoT device.

[0032] Figure 2 A diagram depicting an example scenario 200 of an A-IoT topology according to an embodiment of the present disclosure. Scenario 200 involves a transmitter, an ambient / passive IoT device (e.g., a tag), and a network node (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 2 , the ambient / passive IoT topology may include a network node (i.e., a reader for IoT communication) and an ambient / passive IoT device. In addition, there may be a transmitter providing a carrier (CW) to the ambient / passive IoT device.

[0033] A network node can transmit an Ambient / Passive IoT (A-IoT) downlink (DL) (or forward link) signal to an Ambient / Passive IoT device. The Ambient / Passive IoT device can transmit an Ambient / Passive IoT uplink (UL) (or backward link) signal back to the network node via backscatter. Backscatter can be performed based on a CW provided by the transmitter. The Ambient / Passive IoT DL signal transmitted to the Ambient / Passive IoT device can be used to communicate with the Ambient / Passive IoT device or provide scheduling for the Ambient / Passive IoT device. The Ambient / Passive IoT DL signal can begin with a dedicated sequence. The dedicated sequence can be (pre-)defined, (pre-)configured, and / or indicated. The dedicated sequence can be used for synchronization of the Ambient / Passive IoT device.

[0034] Ambient / passive IoT devices can use CW for backscattering. Specifically, the ambient / passive IoT device can modulate the CW with its data. In addition, the network node can dispatch the data type through the ambient / passive IoT DL signal. Because the ambient / passive IoT device does not generate its own radio frequency (RF) energy, the ambient / passive IoT device can modulate and reflect the incident CW to send data. The network node can dispatch the operation (e.g., modulation, coding scheme) performed by the ambient / passive IoT device on the CW through the ambient / passive IoT DL signal. The ambient / passive IoT device can send the ambient / passive IoT UL signal back to the network node through backscattering of the modulated CW.

[0035] like Figure 2 As shown, there is a communication link between the network node and the transmitter. The communication link can be a wired link or a wireless link, used to transmit signals between the network node and the transmitter. The network node can send scheduling or control information provided by the CW via the communication link. For example, the network node can send a signal (e.g., scheduling or control information) to the transmitter via the Uu interface (i.e., the communication link) to schedule the resources and power for the CW transmission.

[0036] The transmitter may have different carrier provision modes. For example, depending on the trigger, the carrier provision may be continuous, periodic and / or on-demand. That is, depending on the trigger, the carrier may be transmitted continuously, periodically or on-demand. The trigger may be a configuration and / or scheduling from a network node via radio resource control signaling, a media access control control element and / or downlink control information. The carrier transmission resource allocation of the transmitter may be scheduled by the network node. For example, the network node may allocate a specific time slot, frequency block and / or code to the transmitter to provide the carrier and enable the A-IoT device to backscatter the incoming carrier. The time slot may be an NR Uu UL slot and / or an NR Uu DL slot. The frequency block may be a channel and / or subchannel in the frequency domain. In one example, the unique code may be a random or pseudo-random sequence (pre)defined, (pre)configured or indicated by the network node. In another example, the unique code may be generated by the A-IoT device.

[0037] In addition, the network node may send scheduling information to the transmitter. The scheduling information may indicate when to provide carriers to the A-IoT device. The scheduling information may be based on a predetermined pattern or a dynamic decision based on network conditions. For example, the network node may schedule the transmitter to transmit carriers immediately after an A-IoT DL signal is sent from the network node to the A-IoT device. In another example, the network node may schedule the transmitter to transmit carriers at least a period of time (e.g., T) before the time slot in which the A-IoT device performs backscattering. The network node may instruct the transmitter to adjust the power level of the carriers based on at least one of the distance between the transmitter and the A-IoT device, the distance between the transmitter and the network node, and the quality of the backscattered signal. The A-IoT device may backscatter information about channel conditions, which the network node may use to optimize communication strategies, such as adjusting scheduling or power control. If the backscattered signal from the A-IoT device is not correctly received, the network node may send error correction codes or request data retransmission. The network node may send configuration updates to the transmitter or A-IoT device, such as changes to the modulation / coding scheme, time division duplex (TDD) mode, resource allocation, or protocol parameters, to improve system performance.

[0038] Figure 3Another example scenario 300 for an A-IoT topology is described according to an embodiment of the present invention. Scenario 300 involves an A-IoT device (e.g., a tag) and a network node (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 3 , the A-IoT topology may include a network node (i.e., a reader for IoT communication) and an A-IoT device. In addition, in this A-IoT topology, the network node may provide a carrier to the A-IoT device (i.e., a network node including a transmitter function).

[0039] like Figure 3 As shown, the network node may send an A-IoT DL signal to the A-IoT device, and the A-IoT device may send an A-IoT UL signal to the network node via backscattering. Backscattering may be performed based on an incoming carrier provided by the network node. The A-IoT DL signal sent to the A-IoT device may include information or commands for the A-IoT device. The network node may send a carrier to the A-IoT device. The carrier may be sent at least for a period of time (e.g., T) before the backscatter reply from the A-IoT device. The A-IoT device may reflect the incident carrier from the network node. Specifically, the A-IoT device may add its own information (e.g., changing the reflection characteristics of its antenna / circuit, effectively modulating the signal) or data to the carrier and send the carrier to the network node via backscattering. The network node may receive the backscattered signal from the A-IoT device, i.e., the A-IoT UL signal containing data from the A-IoT device.

[0040] The carrier provided by the network node may be continuous, periodic and / or on-demand. That is, depending on the trigger, the carrier may be transmitted continuously, periodically or on demand. The carrier transmission and the resource allocation of the carrier may be scheduled by the network node. For example, the network node may allocate specific time slots for transmitting A-IoT DL signals and carrier transmission. In one example, if the A-IoT UL transmission is backscattered on an externally provided carrier, the A-IoT UL signal received from the A-IoT device may occur in the same time slot as the carrier transmission. In another example, if the A-IoT UL transmission is generated internally by the A-IoT device, the A-IoT UL signal received from the A-IoT device may occur in a time slot different from the carrier transmission timing. Alternatively, the network node may use one frequency for DL signals and another frequency for carrier transmission. For example, frequency division duplex (FDD) DL spectrum may be used for A-IoT DL transmission, while the FDD UL spectrum may be used for carrier transmission. If the A-IoT UL transmission is backscattered on an externally provided carrier, then the reception of the A-IoT UL signal from the A-IoT device can occur on the same frequency / channel as the carrier transmission frequency / channel. If the A-IoT UL transmission is generated internally by the A-IoT device, then the reception of the A-IoT UL signal from the A-IoT device can occur on a different frequency / channel than the carrier transmission frequency / channel. Network nodes can dynamically allocate resources based on the current network load, the number of active A-IoT devices, and the quality of the communication channel.

[0041] refer to Figure 3 , the network node can send scheduling information to the A-IoT device. The scheduling information can indicate when the A-IoT should backscatter its signal. The scheduling information may include a time slot counter. The network node can control the characteristics of the carrier, such as the power level, based on the distance between the network node and the A-IoT device. When communication is not required between the network node and the A-IoT device, the network node can instruct the A-IoT to activate or deactivate its backscatter function to save energy. The network node can confirm that the backscattered signal was successfully received. In addition, if the signal is not received correctly, the network node can request a retransmission. The network node can receive feedback from the A-IoT device about the channel quality. The network node can adjust resource allocation and signal strategy based on the feedback. The network node can instruct the A-IoT device to adjust its reflection characteristics to ensure that the backscattered signal is received with sufficient quality.

[0042] According to an embodiment of the present invention, in another IoT topology (e.g., topology 2), a reader device (e.g., user device 110) can receive a configuration from a network node (e.g., a (macro / micro) base station). The reader device can then send commands to the IoT device based on the configuration. Furthermore, the reader device can receive a backscattered signal from the IoT device. The backscattered signal can be generated based on a carrier wave. For example, the reader device can send a carrier wave to the IoT device based on the configuration. In another example, a transmitter can send a carrier wave to the IoT device.

[0043] Figure 4 Another example scenario 400 of an A-IoT topology is described according to an embodiment of the present invention. Scenario 400 involves a reader (e.g., a user device or a user device reader), an A-IoT device (e.g., a tag), a transmitter (e.g., a user device transmitter), and a network node (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 4 , the A-IoT topology may include network nodes, user equipment readers, and A-IoT devices. In addition, the user equipment transmitter may be configured to provide a carrier to the A-IoT device.

[0044] refer to Figure 4 , the network node may send a signal to the user equipment reader via the Uu interface. The signal may include scheduling information for the user equipment reader's behavior. For example, the network node may schedule resources for the user equipment reader to send A-IoT downlink signals to the A-IoT device. Scheduling may be performed via higher layer signaling (e.g., radio resource control, media access control control elements) or layer 1 signaling (e.g., downlink control information). In one example, the network node may send a configuration to the user equipment reader to indicate resources via higher layer signaling or layer 1 signaling for the user equipment reader to send A-IoT downlink signals to the IoT device and receive A-IoT uplink signals from the A-IoT device.

[0045] The A-IoT device can modulate the carrier wave by reflecting it and adjusting (or changing) its characteristics to encode the A-IoT device's information. The A-IoT device can transmit the A-IoT uplink signal back to the user device reader by backscattering the modulated carrier wave. The user device reader can receive the A-IoT uplink signal containing the A-IoT device data.

[0046] The link (e.g., wired or wireless) between the network node and the user device transmitter can be used to transmit signals between the network node and the user device transmitter. The signals between the network node and the user device transmitter can include coordination of providing carriers for A-IoT devices, such as resource allocation. The link between the user device reader and the user device transmitter can be used to transmit signals between the user device reader and the user device transmitter. The signals between the user device reader and the user device transmitter can coordinate the provision of carriers to A-IoT devices, such as resource allocation.

[0047] User equipment reader and user equipment transmitter can be two operating modes of the user equipment. The operating mode of the user equipment (for example, as a user equipment reader or a user equipment transmitter) can be configured and / or indicated by the network node according to a set of factors through radio resource control, media access control control elements and / or downlink control information. For example, a bit in the radio resource control, media access control control elements and / or downlink control information can be used for configuration and / or indication. The factor set can be the distance and / or link quality between the user equipment and the A-IoT device. That is, the network node can determine the configuration or indication based on the distance or link quality between the user equipment and the A-IoT device. For example, for a user equipment that is far away from the A-IoT device, the user equipment can be configured and / or indicated to operate in user equipment reader mode (i.e., the user equipment is a user equipment reader). For a user equipment that is close to the A-IoT device, the user equipment can be configured and / or indicated to operate in user equipment transmitter mode (i.e., the user equipment is a user equipment transmitter).

[0048] In addition, reference Figure 4, the user equipment transmitter can be configured and / or instructed to operate in different carrier provision modes. The carrier provision mode may include continuous, periodic and / or on-demand modes. That is, the carrier can be sent continuously, periodically or on demand. The configuration and / or instruction of the carrier provision can be transmitted by the network node via radio resource control, media access control control elements and / or downlink control information. Resource allocation can be scheduled by the network node. For example, the network node can allocate specific time slots for the user equipment reader and the user equipment transmitter to operate. Alternatively, different frequencies or channels or subchannels or resource pools can be allocated for the user equipment reader and the user equipment transmitter to operate. Alternatively, different codes (e.g., random and / or pseudo-random sequences) can be assigned to the user equipment reader and the user equipment transmitter for operation. The A-IoT device can backscatter the incident carrier provided by the external user equipment transmitter. A unique code (e.g., random and / or pseudo-random sequence) can be used to distinguish signals from different A-IoT devices. In one example, the unique code can be (pre)defined and / or (pre)configured by the network node and / or the user equipment reader. In another example, a unique code can be generated by an A-IoT device. The unique code can allow multiple A-IoT devices to communicate simultaneously without interfering with each other.

[0049] Furthermore, the network node may control the power level of signals transmitted by the user device reader and the user device transmitter based on a set of factors to optimize the backscattering process and ensure that the backscattered signal of the A-IoT device is received with sufficient quality. The set of factors may include at least one of the following: the distance between the user device reader and the A-IoT device, the distance between the user device transmitter and the A-IoT device, the distance between the network node and the user device reader, the distance between the network node and the user device transmitter, and the distance between the user device reader and the user device transmitter. In one embodiment, the user device transmitter may determine the power of the carrier based on at least one of the following: the distance between the user device reader and the user device transmitter, the distance between the A-IoT device and the user device transmitter, and the distance between the user device reader and the A-IoT device.

[0050] In addition, reference Figure 4, the network node can send scheduling information to the user device reader to indicate the resources for A-IoT downlink transmission and A-IoT uplink reception. The network node can send scheduling information to the user device transmitter to indicate the resources for carrier transmission. In addition, the network node can send commands to configure and / or instruct the user device operating mode. For example, a bit in the downlink control information and / or an information element (IE) in the radio resource control parameters can be used to instruct and / or configure the user device to act as a user device reader and / or a user device transmitter. The network node can also send commands regarding resource allocation, power level, and other operating parameters to the user device reader and user device transmitter. The user device reader can transmit status updates back to the network node. The status update of the user device reader can include some information, such as whether the backscattered signal from the A-IoT device was successfully received. For example, in one example, the network node can send information (i.e., status update) to the user device transmitter. In another example, the user device reader can send the status update directly to the user device transmitter. In addition, the user device transmitter can transmit status updates back to the network node to inform the network node of the current status, such as whether the carrier was successfully transmitted. After receiving the backscattered signal from the A-IoT device, the UE reader can send an acknowledgment (ACK) to the A-IoT device and / or the network node to confirm successful communication. Continuous signaling between the network node and the UE transmitter, and between the UE reader and the external UE transmitter, may be necessary to maintain link quality and synchronization. If an error is detected in the backscattered signal, a signaling protocol can be used to request a retransmission or adjust system parameters (e.g., transmit power) to improve communication quality.

[0051] Figure 5 Another example scenario 500 for an A-IoT topology is described according to an embodiment of the present invention. Scenario 500 involves a reader (e.g., a user device or a user device reader), an A-IoT device (e.g., a tag), and a network node (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 5 , the A-IoT topology may include network nodes, user equipment readers, and A-IoT devices. In addition, in the A-IoT topology, the user equipment reader may provide a carrier to the A-IoT device (i.e., the user equipment reader may include a transmitter function).

[0052] The network node can send a signal to the user device reader via the Uu interface to schedule the behavior of the user device reader. The scheduling signal may include information about when the user device reader should send a carrier to the A-IoT device, when it should listen to the A-IoT uplink signal from the A-IoT device, and when it should send an A-IoT downlink signal to the A-IoT device. The user device reader can send an A-IoT downlink signal to the A-IoT device. The sending of the A-IoT downlink signal can be based on the schedule determined by the network node or the decision of the user device reader itself. The A-IoT downlink signal may contain data or commands to the A-IoT device. After receiving the A-IoT downlink signal, the A-IoT device can transmit the A-IoT uplink signal back to the user device reader by backscattering the carrier provided by the user device reader. In backscatter communication, the A-IoT device can modulate the incident carrier with its own data and reflect the modulated carrier back to the user device reader.

[0053] In addition, reference Figure 5 , the user equipment reader may have different carrier provision modes. The carrier provision modes may include continuous, periodic and / or on-demand modes. That is, the carrier may be sent continuously, periodically or on demand. The carrier provision mode may be configured and / or scheduled by the network node through radio resource control, media access control control elements and / or downlink control information. In addition, resource allocation may be scheduled by the network node. For example, the network node may allocate specific time slots for the A-IoT downlink signal and the carrier to the user equipment reader. Alternatively, the network node may allocate different frequencies for the A-IoT downlink signal transmission and the carrier transmission. Alternatively, the network node may control the power levels of the A-IoT downlink transmission and the carrier transmission of the user equipment reader to ensure that the A-IoT device can effectively backscatter the signal and that the backscattered signal can be received with sufficient quality.

[0054] In addition, reference Figure 5, the network node can send scheduling information to the user device reader to indicate when to send downlink signals to the A-IoT device, when to send carriers to the A-IoT device, and when to listen for backscattered uplink signals from the A-IoT device. The network node can send configuration commands to the user device reader to set operating parameters, such as the power level, frequency, and time slot for communicating with the A-IoT device. The user device reader can send status messages to the network node to indicate the status of communication with the A-IoT device. In addition, the user device reader can receive control messages to adjust its operation as needed. The user device reader can send an acknowledgment (ACK) to the network node after successfully receiving the backscattered signal from the A-IoT device, or send a non-acknowledgment (NACK) to the network node if there is no transmission from the A-IoT device within a specific duration. If an error is detected, the signaling protocol can manage retransmission requests.

[0055] In embodiments of the present invention, configuration / scheduling signals may be carried via Radio Resource Control (RRC), Medium-Access-Control Control-Elements (MAC-CE), Downlink Control Information (DCI), Channel State Information (CSI), First Stage Sidelink Control Information (SCI), and / or Second Stage SCI. For example, RRC signaling may be used to process the configuration of a user equipment (UE) reader. The configuration may include the UE's operating mode (e.g., reader or transmitter), transmission mode (e.g., time division multiplexing (TDM) mode and / or frequency division multiplexing (FDM) configuration), and carrier wave (CW) provisioning mode (continuous mode, periodic mode, and / or on-demand mode). In another example, MAC-CE and / or DCI signaling may be used for dynamic resource allocation and to provide instructions regarding the timing and format of transmissions.

[0056] In an embodiment of the present invention, a command from a reader (e.g., a network node or a UE reader) to an Internet of Things (IoT) device (e.g., an A-IoT device) may include a synchronization acquisition signal, wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion. The command may start with at least one of a synchronization preamble and a frame synchronization sequence. The synchronization preamble may include at least one fixed length, a start delimiter (e.g., a start indication portion), a reader-to-tag calibration symbol (e.g., a clock acquisition portion), and a tag-to-reader calibration symbol. The frame synchronization sequence may include at least one fixed length start delimiter and a reader-to-tag calibration symbol.

[0057] In an embodiment of the present invention, a command from a reader (e.g., a network node or a UE reader) to an IoT device (e.g., an A-IoT device) may indicate an IoT UL type associated with an uplink (UL) timing. Specifically, the reader (e.g., a network node or a UE reader) may arrange the timing of the reply of the IoT device (e.g., an A-IoT device). For example, an indication may be carried in an A-IoT downlink (DL) signal from the reader to arrange the timing of the A-IoT UL signal from the IoT device (i.e., the reply of the IoT device). The timing of the A-IoT UL may be an instant / real-time A-IoT UL. This means that the IoT device may send an A-IoT UL signal within a period of time (e.g., T1) after receiving the A-IoT DL signal from the reader.

[0058] In another example, the timing of the A-IoT UL can be Delayed A-IoT UL. This means that the IoT device can send the A-IoT UL signal within a period of time (e.g., T2) after receiving the A-IoT DL signal from the reader. Furthermore, after the IoT device issues a schedule for a delayed reply (e.g., Delayed A-IoT UL), the reader can send a CW for at least the lesser of T3 or T2 (maximum). T3 is the duration between the reader schedule (i.e., A-IoT DL) and the IoT device's backscattered reply (i.e., A-IoT UL). The maximum value of T2 should not be less than the maximum value of T1.

[0059] The backscatter reply (or backscatter signal) of the IoT device may include a preamble, a header, a handle (e.g., a random number (e.g., a 16-bit random number) or a pseudo-random number generated by the IoT device at the beginning of a communication round), and a cyclic redundancy check (CRC) code calculated based on the header and the handle. The preamble may include one of a Manchester preamble, an FM0 preamble, a Miller preamble, a convolutional preamble, a Barker code, a frame synchronization sequence, and / or a synchronization preamble used in A-IoT DL. A bit in the header of the backscatter reply of the IoT device (e.g., A-IoT UL) may be used to indicate whether the reader's dispatch was successfully executed by the IoT device (e.g., a bit in the header is equal to 0), or whether the IoT device encountered an error (e.g., a bit in the header is equal to 1). If the reader receives the backscatter reply of the IoT device within T2 (maximum), the reader may send a subsequent sequence containing the IoT device handle to verify that the IoT device is still within the reader's active coverage.

[0060] In another example, the timing of an A-IoT UL can be a pending A-IoT UL. This means that the IoT device can send an A-IoT UL for a duration exceeding T2. Furthermore, for a pending schedule, the IoT device can send multiple backscatters. The first A-IoT UL can meet the T4 constraint. This means that the IoT device should send the first A-IoT UL within T4 after receiving the A-IoT DL from the reader. Subsequent A-IoT ULs can meet the T5 constraint. This means that subsequent A-IoT ULs should be sent within T5 immediately after the previous A-IoT UL. There should be at least one A-IoT UL from the IoT device within each T5.

[0061] A field in the reply of the IoT device can be used to indicate whether the reply of the IoT device is the last one. For example, a field "done" of 0 may mean that the corresponding A-IoT UL is not the last one. A field "done" of 1 may mean that the corresponding A-IoT UL is the last one. In one example, after issuing a reply schedule in progress, the reader may send a CW until the reader receives an A-IoT UL with "done" = 1. The A-IoT UL with "done" = 1 may indicate that the IoT device has completed the execution of the reader's schedule. In another example, the reader may send a CW until the reader does not receive an A-IoT UL for at least T4 (maximum) or T5 (maximum). This may mean that the IoT device has failed to execute the reader's schedule.

[0062] In an embodiment of the present invention, if the corresponding A-IoT UL is not the first A-IoT UL in an A-IoT UL burst (a series of A-IoT UL transmissions), a synchronization sequence (e.g., a Barker code) may be added to the backscatter modulated CW (i.e., the A-IoT UL) (e.g., located in front of the A-IoT UL).

[0063] In the present invention, a common procedure between the reader and the IoT device can be used for certain purposes. For example, the common procedure may include "in the initial stage," "before link establishment," and / or "for load control." Furthermore, a dedicated procedure between the reader and the IoT device can be used for certain purposes. For example, the dedicated procedure may include "after link establishment," "for data transmission," and / or "for transmission repetition."

[0064] In the present invention, six logical entities (functions) are defined. These six logical entities (functions) may include a controller, a carrier (CW) transmitter, an IoT command (CMD) generator, a reader, an IoT device, and an energy provider. The controller (e.g., a network node) may be used to control CW resources and corresponding backscatter resources / interference, and / or arrange and control operations to avoid interference. A carrier transmitter (e.g., a network node, a user equipment (UE), or an external transmitter) may be used to generate CW. The carrier transmitter may communicate with the controller to obtain an appropriate time to generate CW. The IoT command generator (e.g., a network node or UE) may be used to generate commands based on the resource allocation of the controller. The reader (e.g., a network node or UE) may be used to receive backscatter signals. The IoT device may be used to decode commands, collect energy from commands, CW, and / or external energy collection waveforms provided by the energy provider, and / or generate backscatter signals on CW (and / or commands). The energy provider (e.g., a reader, a controller, etc.) may be used to provide energy for the IoT device to decode commands. In the IoT topology (e.g., Figure 2 and Figure 3 In the topology 1 shown in Figure 1), the network nodes can play the roles of controller, CW transmitter and reader. In another IoT topology (e.g. Figure 4 and Figure 5 In topology 2 shown in FIG, the reader (e.g., UE reader) and the resource controller (e.g., network node) may be different physical entities. In addition, in topology 1 and topology 2, the transmitter may be an independent device compared to the network node and the UE (or UE reader).

[0065] Illustrative Embodiments

[0066] Figure 6According to an embodiment of the present invention, an example communication system 600 is described, which includes at least an example communication device 610 and an example network device 620. Each of the communication device 610 and the network device 620 can perform various functions to implement the solutions, technologies, processes, and methods described herein for IoT signal transmission, including the above descriptions of various proposed designs, concepts, solutions, and methods, as well as descriptions of user equipment and network devices in mobile communications, including the above scenarios / solutions and processes 700, 800, 900, and 1000 described below.

[0067] The communication device 610 may be part of an electronic device, which may be a UE, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 610 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing device, such as a tablet, a laptop, or a notebook computer. The communication device 610 may also be part of a machine type device, which may be an Internet of Things, NB-IoT, eMTC, IIoT UE, such as a fixed or static device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, the communication device 610 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 610 may be implemented in the form of one or more integrated circuit (IC) chips, such as one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors. The communication device 610 may include Figure 6 At least some of the components shown, such as processor 612. The communication device 610 may also include one or more other components not related to the solution proposed by the present invention (e.g., internal power supply, display device and / or user interface device), so for the sake of brevity and simplicity, these components of the communication device 610 are not shown in FIG. Figure 6 Not shown in the figure, nor described below.

[0068] The network device 620 may be part of an electronic device, which may be a network node, such as a satellite, a base station (BS), a small base station, a router, or a gateway of an IoT network. For example, the network device 620 may be implemented in an eNB / gNB / TRP in a satellite or 4G / 5G / B5G / 6G, NR, IoT, NB-IoT, or IIoT network. Alternatively, the network device 620 may be implemented in the form of one or more IC chips, such as one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. The network device 620 may include Figure 6At least some of the components shown, such as processor 622. Network device 620 may also include one or more other components not related to the solutions proposed by the present disclosure (e.g., internal power supply, display device and / or user interface device), so for the sake of brevity and simplicity, these components of network device 620 are not shown in FIG. Figure 6 Not shown in the figure, nor described below.

[0069] In one aspect, processor 612 and processor 622 can each be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even if the singular term "processor" is used herein to refer to processor 612 and processor 622, according to embodiments of the present invention, processor 612 and processor 622 can each include multiple processors in some embodiments and a single processor in other embodiments. In another aspect, processor 612 and processor 622 can each be implemented in the form of hardware (and, optionally, firmware), including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more variable capacitors, these electronic components configured and arranged to achieve specific purposes according to the present invention. In other words, in at least some embodiments, processor 612 and processor 622 are special-purpose machines specially designed, arranged and configured for performing specific tasks, including IoT signal transmission, in devices (e.g., represented by communication device 610) and network nodes (e.g., represented by network device 620) according to various embodiments of the present invention.

[0070] In certain embodiments, the communication device 610 may further include a transceiver 616 connected to the processor 612 and capable of wirelessly transmitting and receiving data. In certain embodiments, the transceiver 616 may be capable of wirelessly communicating with different types of user equipment (UE) and / or different wireless networks using different radio access technologies (RATs). In certain embodiments, the transceiver 616 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 616 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input, multiple-output (MIMO) wireless communications. In certain embodiments, the network device 620 may also include a transceiver 626 connected to the processor 622. The transceiver 626 may include a transceiver capable of wirelessly transmitting and receiving data. In certain embodiments, the transceiver 626 may be capable of wirelessly communicating with different types of UEs using different RATs. In certain embodiments, the transceiver 626 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 626 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

[0071] In some embodiments, the communication device 610 may further include a memory 614 connected to the processor 612, with the processor 612 being able to access the memory 614 and store data therein. In some embodiments, the network device 620 may further include a memory 624 connected to the processor 622, with the processor 622 being able to access the memory 624 and store data therein. Each of the memory 614 and the memory 624 may include a type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitance RAM (Z-RAM). Alternatively, each of the memory 614 and the memory 624 may further include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of the memory 614 and the memory 624 may further include a type of non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0072] Each of the communication device 610 and the network device 620 may be a communication entity capable of communicating with each other using various schemes proposed in the present disclosure. For illustrative purposes and not limitation, the following provides a description of the capabilities of the communication device 610 as a user equipment and the network device 620 as a network node (e.g., a TRP), in relation to processes 700, 800, 900, and 1000.

[0073] Illustrative Process

[0074] Figure 7 An example process 700 is described according to an embodiment of the present invention. Process 700 may be an example implementation of the above-described scenario / scheme, whether partial or complete, related to IoT signal transmission in the context of the present invention. Process 700 may represent one aspect of the functional implementation of communication device 610. Process 700 may include one or more operations, actions, or functions, as shown by one or more blocks 710, 720, and 730. Although shown as discrete blocks, the blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be arranged as follows: Figure 7 700. The process 700 may be performed in the order shown in FIG. 700, or, alternatively, in a different order. Process 700 may be implemented by communication device 710 or any suitable reader device. For purposes of illustration only and not limitation, process 700 is described below in the context of communication device 610. Process 700 may begin at block 710.

[0075] At block 710, the process 700 may involve the processor 612 of the communication device 610 receiving a configuration from a network node via the transceiver 616. From block 710, the process 700 may continue to block 720.

[0076] At block 720 , process 700 may involve processor 612 sending a command to the IoT device according to the configuration via transceiver 616 . From block 720 , process 700 may continue to block 730 .

[0077] At block 730 , the process 700 may involve the processor 612 receiving a backscatter signal from an IoT device via the transceiver 616 , wherein the backscatter signal is generated based on a carrier wave.

[0078] In some embodiments, the process 700 may involve the processor 612 transmitting a carrier wave to the IoT device via the transceiver 616 according to the configuration.

[0079] In some embodiments, the carrier wave is transmitted continuously, periodically, or on demand.

[0080] In some embodiments, the configuration may be determined based on the distance or link quality between the device and the IoT device.

[0081] In some embodiments, process 700 may involve processor 612 determining the power of the carrier based on at least one of: a distance between the device and the transmitter, a distance between the IoT device and the transmitter, and a distance between the device and the IoT device.

[0082] In some embodiments, the command may include a synchronization acquisition signal, and the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion.

[0083] In certain embodiments, the command may indicate an IoT uplink type associated with the uplink timing.

[0084] In certain embodiments, the backscatter signal may include a preamble, a header, a handle, and a cyclic redundancy check code.

[0085] In certain embodiments, the configuration may be received via at least one of radio resource control signaling, a medium access control control element, and downlink control information from the network node.

[0086] Figure 8An example process 800 is described according to another embodiment of the present invention. Process 800 may be an example implementation of the above-described scenario / scheme, whether partial or complete, related to IoT signal transmission in the context of the present invention. Process 800 may represent one aspect of the functional implementation of network device 620. Process 800 may include one or more operations, actions, or functions, as shown by one or more blocks 810, 820, and 830. Although shown as discrete blocks, the blocks of process 800 may be divided into additional blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 800 may be arranged as follows: Figure 8 800 may be performed in the order shown in FIG. 800 , or, alternatively, in a different order. Process 800 may be implemented by network device 620. For purposes of illustration only and not limitation, process 800 is described below in the context of network device 620. Process 800 may begin at block 810.

[0087] At block 810 , the process 800 may involve the processor 622 of the network device 620 transmitting a carrier wave to the IoT device via a transmitter via the transceiver 626 . The process 800 may continue from block 810 to block 820 .

[0088] At block 820, process 800 may involve processor 622 sending a command to the IoT device via transceiver 626. From block 820, process 800 may continue to block 830.

[0089] At block 830 , process 800 may involve processor 622 receiving a backscatter signal from an IoT device via transceiver 626 , wherein the backscatter signal is generated based on a command and a carrier wave.

[0090] In certain embodiments, a network node may include a transmitter.

[0091] In some embodiments, the command may include a synchronization acquisition signal, and wherein the synchronization acquisition signal may include at least a start indication portion and a clock acquisition portion.

[0092] Figure 9 An example process 900 is described according to another embodiment of the present invention. Process 900 may be an example implementation of the above-described scenario / scheme, whether partial or complete, regarding IoT signal transmission of the present invention. Process 900 may represent one aspect of a feature implementation of network device 620. Process 900 may include one or more operations, actions, or functions, as shown by one or more blocks 910 and 920. Although shown as discrete blocks, the various blocks of process 900 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 900 may be arranged in Figure 9The process 900 may be performed in the order shown, or may be performed in a different order. The process 900 may be implemented by the network device 620. For illustration purposes only and not limitation, the process 900 is described below in the context of the network device 620. The process 900 may begin at block 910.

[0093] At block 910 , process 900 may involve processor 622 of network device 620 determining a configuration for the user device, wherein the configuration indicates an operating mode of the user device for communication between the user device and an IoT device. Process 900 may continue from block 910 to block 920 .

[0094] At block 920 , process 900 may involve processor 622 of network device 620 sending the configuration to user equipment via transceiver 626 .

[0095] In some embodiments, the configuration may indicate that the user device is a reader for providing commands to the IoT device.

[0096] In some embodiments, the command may include a synchronization acquisition signal, and wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion.

[0097] In certain embodiments, the command indicates an IoT uplink type associated with the uplink timing.

[0098] In some embodiments, the configuration may indicate resources via higher layer signaling or layer 1 signaling for the user equipment to send IoT downlink signals to the IoT device and receive IoT uplink signals from the IoT device.

[0099] In some embodiments, the configuration may indicate that the user equipment is a transmitter for providing a carrier wave to the IoT device.

[0100] In some embodiments, the configuration may be determined based on the distance or link quality between the user device and the IoT device.

[0101] In some embodiments, the configuration may be sent via at least one of radio resource control signaling, a medium access control control element, and downlink control information.

[0102] Figure 10Example process 1000 according to another embodiment of the present invention. Process 1000 may be an example implementation of the above scenario / scheme, whether partial or complete, regarding the IoT signal transmission of the present invention. Process 1000 may represent one aspect of the feature implementation of communication device 610. Process 1000 may include one or more operations, actions, or functions, as shown by one or more blocks 1010, 1020, and 1030. Although shown as discrete blocks, the various blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 1000 may be arranged in Figure 10 The process 1000 is performed in the order shown, or may be performed in a different order. Process 1000 may be implemented by communication device 610 or any suitable IoT device. For illustrative purposes only and without limitation, process 1000 is described below in the context of communication device 610. Process 1000 may begin at block 1010.

[0103] At block 1010, process 1000 may involve processor 612 of communication device 610 receiving a command from a reader via transceiver 616. From block 1010, process 1000 may continue to block 1020.

[0104] At block 1020, process 1000 may involve processor 612 receiving a carrier wave from a reader or transmitter via transceiver 616. From block 1020, process 1000 may continue to block 1030.

[0105] At block 1030 , process 1000 may involve processor 612 sending a backscatter signal to a reader, wherein the backscatter signal is generated based on a carrier wave.

[0106] In some embodiments, the command may include a synchronization acquisition signal, wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion. The command may indicate an IoT uplink type associated with the uplink timing.

[0107] Additional Notes

[0108] The subject matter described herein sometimes illustrates different components contained within or connected to different other components. However, it should be understood that the multiple depicted architectures are merely examples, and that many other architectures that achieve the same functionality can be implemented. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively "associated" so that the desired functionality is achieved. Therefore, regardless of the architecture or intermediate components, any two components combined herein to achieve a particular functionality can be considered to be "associated" with each other so that the desired functionality is achieved. Similarly, any two components so associated can also be considered to be "operationally connected" or "operationally coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operationally connected" to each other to achieve the desired functionality. Specific examples of operationally coupleable components include, but are not limited to, components that are physically compatible and / or physically interactive and / or components that can wirelessly interact and / or wirelessly interact and / or components that logically interact and / or logically interactable.

[0109] Furthermore, with respect to any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate for the context and / or application. For the sake of clarity, various singular / plural interchanges may be explicitly set forth herein.

[0110] Furthermore, one of ordinary skill in the art will understand that, in general, the terms used herein, and particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be “open-ended” terms, e.g., the term “comprising” should be interpreted as “including, but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including, but not limited to,” and so forth. One of ordinary skill in the art will also understand that if a specific number of an introduced claim recitation is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation, no such intent is present. For example, to aid understanding, the appended claims may contain use of the introductory phrases “at least one” and “one or more.” However, the use of such phrases should not be construed as implying that a claim recitation, introduced by the indefinite article "a" or "an," will encompass any particular claim of such introduced claim recitation to embodiments containing only one such recitation, even when the same claim contains the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an," e.g., "a and / or an" should be construed to mean "at least one" or "one or more," and the same applies to the use of definite articles used to introduce claim recitations. Furthermore, even if a specific number of introduced claim recitations is explicitly recited, one of ordinary skill in the art will recognize that such recitation should be construed to mean at least the recited number, e.g., the unmodified recitation of "two recitations" without other modifiers means at least two recitations or two or more recitations. Furthermore, where a convention similar to “at least one of A, B, and C, etc.” is used, it is generally intended to be interpreted in the sense that one of ordinary skill in the art would understand this convention (e.g., “a system having at least one of A, B, and C” would include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Where a convention similar to “at least one of A, B, or C, etc.” is used, it is generally intended to be interpreted in the sense that one of ordinary skill in the art would understand this convention (e.g., “a system having at least one of A, B, or C” would include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). A person of ordinary skill in the art will also understand that any transitional words and / or phrases, whether in the specification, claims or drawings, that actually indicate two or more optional items should be understood to include the possibility of one, any or both of such items.For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

[0111] It will be appreciated that various embodiments of the present invention have been described herein for illustrative purposes and that various modifications may be made without departing from the scope and spirit of the invention. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are to be determined by the appended claims.

Claims

1. A method for sending an Internet of Things signal, comprising: The processor of the device receives the configuration from the network node; The processor sends a command to the IoT device according to the configuration; as well as The processor receives a backscatter signal from the Internet of Things device, wherein the backscatter signal is generated based on a carrier wave.

2. The method for sending an Internet of Things signal according to claim 1, wherein: Further including: The processor sends the carrier to the IoT device according to the configuration.

3. The method for sending an Internet of Things signal according to claim 2, wherein: The carrier is transmitted continuously, periodically, or on demand.

4. The method for sending an Internet of Things signal according to claim 1, wherein: The configuration is determined based on the distance or link quality between the device and the IoT device.

5. The method for sending an Internet of Things signal according to claim 1, wherein: Further including: The processor determines the power of the carrier according to at least one of the following: a distance between the device and a transmitter, a distance between the IoT device and the transmitter, and a distance between the device and the IoT device.

6. The method for sending an Internet of Things signal according to claim 1, wherein: The command includes a synchronization acquisition signal, and wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion.

7. The method for sending an Internet of Things signal according to claim 1, wherein: This command indicates the IoT uplink type associated with the uplink timing.

8. The method for sending an Internet of Things signal according to claim 1, wherein: The backscatter signal includes a preamble, a header, a handle, and a cyclic redundancy check code.

9. The method for sending an Internet of Things signal according to claim 1, wherein: The configuration is received via at least one of radio resource control signaling, a medium access control element, and downlink control information from the network node.

10. A method for sending an Internet of Things signal, comprising: The processor of the network node sends a carrier wave to the IoT device through the transmitter; The processor sends a command to the IoT device; as well as The processor receives a backscatter signal from the IoT device, wherein the backscatter signal is generated based on the command and the carrier.

11. The method for sending an Internet of Things signal according to claim 10, wherein: The network node includes the transmitter.

12. The method for sending an Internet of Things signal according to claim 10, wherein: The command includes a synchronization acquisition signal, and wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion.

13. A method for sending an Internet of Things signal, comprising: determining, by a processor of the network node, a configuration for a user equipment, wherein the configuration indicates an operating mode of the user equipment for communication between the user equipment and an Internet of Things device; and The processor sends the configuration to the user equipment.

14. The method for sending an Internet of Things signal according to claim 13, wherein: The configuration indicates that the user device is a reader for providing commands to the IoT device.

15. The method for sending an Internet of Things signal according to claim 14, wherein: The command includes a synchronization acquisition signal, and wherein the synchronization acquisition signal includes at least a start indication portion and a clock acquisition portion.

16. The method for sending an Internet of Things signal according to claim 14, wherein: This command indicates the IoT uplink type associated with the uplink timing.

17. The method for sending an Internet of Things signal according to claim 13, wherein: The configuration indicates that the user equipment is a transmitter, configured to provide a carrier wave to the IoT device.

18. The Internet of Things signal transmission method according to claim 13, wherein: The configuration is determined based on the distance or link quality between the user equipment and the IoT device.

19. The method for sending an Internet of Things signal according to claim 13, wherein: The configuration is sent via at least one of radio resource control signaling, a medium access control element, and downlink control information.

20. The Internet of Things signal transmission method according to claim 13, wherein: The configuration indicates resources through high-layer signaling or first-layer signaling, which are used by the user equipment to send an IoT downlink signal to the IoT device and receive an IoT uplink signal from the IoT device.

Images