Method and apparatus for wireless communication

Abstract

The present invention provides a method and apparatus for wireless communication, the method may be performed by a reader, comprising: broadcasting a radio signal indicating a set of available time slots; sending a confirmation signal containing the decoded sequence to an environmental Internet of Things (A-IoT) device; and receiving an identifier from the A-IoT device, where the identifier is a reply of the A-IoT device when the decoded sequence matches a selected sequence, where the selected sequence is a random sequence that responds to the radio signal in a time slot randomly selected from the set of available time slots. According to the invention, wireless communication can be better carried out.

Description

Technical Field

[0001] The present invention relates to wireless communications, and more particularly to signal transmission and operation of a backscattering device in an Ambient Internet of Things (A-IoT) system. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not constitute prior art.

[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 are capable of supporting communications with multiple users by sharing available system resources. Examples of multiple-access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a municipal, national, regional, and even global level. An example of a telecommunication standard is the fifth generation (5G) New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (such as with the Internet of Things (IoT)) and other requirements. Some aspects of 5G NR may be based on the fourth generation (4G) Long Term Evolution (LTE) standard. 5G NR technology requires further improvements, which may also be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0005] The following content presents a brief summary of one or more aspects, with the purpose of providing a basic understanding of these aspects. The present invention summary is not an extensive overview of all considered aspects, and is neither intended to identify the key or important elements of all aspects, nor to outline the scope of any or all aspects. The purpose of the present invention summary is only to present some concepts of one or more aspects in a simplified form, as a preface to the more detailed description that will be presented below.

[0006] On the one hand, the present invention provides a method for wireless communication, performed by a reader, the method comprising: broadcasting a radio signal indicating a set of available time slots; sending a confirmation signal containing a decoded sequence to an ambient Internet of Things (A-IoT) device; and receiving an identifier from the A-IoT device, wherein the identifier is a reply of the A-IoT device when the decoded sequence matches a selected sequence, wherein the selected sequence is a random sequence that responds to the radio signal in a time slot randomly selected from the set of available time slots.

[0007] On the other hand, the present invention provides a method for wireless communication, which is performed by an ambient Internet of Things (A-IoT) device, and the method includes: receiving a radio signal indicating a set of available time slots from a reader; sending a random sequence in response to the radio signal in a time slot randomly selected from the set of available time slots; receiving a confirmation signal including a decoded sequence; and sending an identifier when the decoded sequence matches the random sequence.

[0008] By utilizing the present invention, wireless communication can be better performed.

[0009] To accomplish the foregoing and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following detailed description and accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of some of the various ways in which the principles of the various aspects can be employed, and the present invention is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system and access network.

[0011] Figure 2 is a schematic diagram illustrating communication between a BS and a UE in an access network.

[0012] Figure 3 An exemplary logical architecture of a distributed access network is illustrated.

[0013] Figure 4 An exemplary physical architecture of a distributed access network is illustrated.

[0014] Figure 5 is a schematic diagram showing exemplary time slots centered on DL.

[0015] Figure 6 is a schematic diagram showing exemplary time slots centered around the UL.

[0016] Figure 7 is a schematic diagram showing an example of a wireless communication system including a base station and a UE.

[0017] Figure 8 is a schematic diagram showing an example of a wireless link between a gNB and an A-IoT device.

[0018] FIG9(A) is a schematic diagram showing an example of a communication link between a gNB and an A-IoT device connected to a UE via a wired cable.

[0019] FIG9(B) is a schematic diagram showing an example of a communication link between a gNB and an A-IoT device connected to a UE via a wireless air interface.

[0020] FIG10(A) is a schematic diagram showing a first type of A-IoT device.

[0021] FIG10(B) is a schematic diagram showing the second type of A-IoT device.

[0022] FIG10(C) is a schematic diagram showing the third type of A-IoT device.

[0023] FIG11(A) is a schematic diagram showing an example of a communication link between a UE and an A-IoT device over an air interface.

[0024] FIG11(B) is a schematic diagram showing a timing example of a communication process between a UE and an A-IoT device through an air interface.

[0025] FIG11(C) is a schematic diagram showing an example of a communication process between a UE and an A-IoT device based on a selected time slot.

[0026] FIG11(D) is a schematic diagram showing an example of a communication process between a UE and an A-IoT device based on a selected duration.

[0027] FIG12(A) is a schematic diagram showing an example of a communication sequence between a UE and an A-IoT device.

[0028] FIG12(B) is a schematic diagram showing an example of the communication process among the gNB, UE, and A-IoT device.

[0029] Fig.13 It is a timing diagram outlining the interaction between UE and gNB regarding uplink power control.

[0030] FIG14(A) is a timing diagram outlining the interactions between the UE and the gNB in ​​the context of 5G NR uplink beam management for the R2D link.

[0031] FIG14(B) is a timing diagram outlining the interaction between the UE and the gNB in ​​the context of using a special type of measurement gap in R2D communication.

[0032] Figure 14(C) is a timing diagram outlining the interaction between the UE and the gNB in ​​the context of downlink beam measurements for R2D communication.

[0033] Fig.15 is a timing diagram outlining the interaction between the UE and the gNB in ​​the context of querying the Electronic Product Code (EPC) of an A-IoT device.

[0034] Figure 16(A) is a timing diagram showing the interactions between the gNB, UE and A-IoT devices during the configuration process, where the gNB controls the R2D link.

[0035] Figure 16(B) is a timing diagram showing the interactions between the gNB, UE and A-IoT devices during the configuration process, where the gNB controls the D2R link.

[0036] Fig.17An example communication system including an example communication device and an example network device is presented.

[0037] FIG. 18(A) is a flow chart describing the identification process of the reader and the A-IoT device.

[0038] FIG. 18(B) is a flow chart describing another identification process of a reader and an A-IoT device. DETAILED DESCRIPTION

[0039] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations, and are not intended to represent the only configurations that can practice the concepts described in the present invention. This specific embodiment part includes specific details, and the purpose is to provide a thorough understanding of various concepts. However, for those skilled in the art, these concepts can also be practiced without these specific details. In some cases, in order to avoid blurring these concepts, known structures and components are shown in block diagram form.

[0040] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. The apparatus and methods will be described in the detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). The elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

[0041] For example, an element, any part of an element, or any combination of elements may be implemented as a "processing system", where the processing system may include one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described in the present invention. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, codes, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, and functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0042] Therefore, in one or more exemplary aspects, the above functions can be implemented in hardware, software or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium, or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium can be any available medium that can be accessed by a computer. The above-mentioned computer-readable medium may include a random access memory (Random-Access Memory, RAM), a read-only memory (Read-Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable ROM, EEPROM), an optical disk storage, a magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer, which is used only as an example and is not intended to limit the present invention.

[0043] Figure 11 is a schematic diagram illustrating an exemplary wireless communication system and access network 100. The wireless communication system (also referred to as a Wireless Wide Area Network (WWAN)) includes a base station (BS) 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (such as a 5G core network (5G Core, 5GC)). BS 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a BS, and a small cell includes a femtocell, a picocell, and a microcell.

[0044] BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) can be connected to the EPC 160 interface via a backhaul link 132 (such as an SI interface). BS 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can be connected to the core network 190 interface via a backhaul link 184. Among other functions, BS 102 may perform one or more of the following functions: transfer of user data, radio channel cipher and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of warning messages. BS 102 may communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via a backhaul link 134 (e.g., an X2 interface). The backhaul link 134 may be wired or wireless.

[0045] BS 102 can communicate wirelessly with UE 104. Each BS 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110, for example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be called a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (Home eNB, HeNB), where the HeNB can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between BS 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to BS 102 and / or a downlink (DL) (also called a forward link) transmission from BS 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. BS102 / UE 104 may use a spectrum with a bandwidth of up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, where the carriers are allocated in carrier aggregation (CA) for transmission in each direction, where the carrier aggregation is up to Yx MHz (x component carriers) in total. The above carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0047] The wireless communication system may also include a Wi-Fi access point (AP) 150, wherein the Wi-Fi AP 150 communicates with a Wi-Fi station (STA) 152 via a communication link 154 in a 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

[0048] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as the 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may increase the coverage of the access network and / or improve the capacity of the access network.

[0049] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with the UE 104. When the gNB 180 operates at mmW or near-mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in the frequency band may be referred to as millimeter waves. Near mmW can extend down to frequencies of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also called centimeter waves. Communications using mmW / near mmW radio frequency bands (eg, 3 GHz-300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

[0050] The base station 180 may transmit beamformed signals in one or more transmit directions 108a to the UE 104. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each base station 180 / UE 104. The transmit and receive directions for the base station 180 may be the same or different. The transmit and receive directions for the UE 104 may be the same or different.

[0051] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transferred through the serving gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Service 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet-Switched Streaming Service (PSS), and / or other IP services. The BM-SC 170 may provide functionality for provisioning and delivery of MBMS user services. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to allocate MBMS traffic to the BS 102, and may be responsible for session management (start / end) and collection of charging information related to the evolved MBMS (eMBMS), where the BS 102 belongs to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services.

[0052] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with the Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the SMF 194 provides QoS flow and session management. All user Internet protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to the IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0053] The BS may also be referred to as a gNB, Node B (NB), eNB, access point, basic transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), transmit reception point (TRP), or some other suitable term. The BS 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (such as an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a medical device, an implant, a sensor / actuator, a display, or any other device with similar functions. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.) UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0054] Although the present invention may be described with reference to 5G NR, the present invention may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM or other wireless / radio access technologies.

[0055] Figure 22 is a block diagram of BS 210 and UE 250 communicating in an access network. In the DL, IP packets from EPC 160 may be provided to controller / processor 275. Controller / processor 275 implements layer 3 and layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and layer 2 includes the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 275 provides: RRC layer functions, wherein the RRC layer functions are associated with broadcasting of system information (such as Master Information Block (MIB), System Information Block (SIB)), RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions, wherein the PDCP layer functions are associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions, wherein the RLC layer functions are associated with transfer of higher layer Packet Data Unit (PDU), error correction through Automatic Repeat Request (ARQ), RLC Service Data Unit (SDU) The MAC layer functions are associated with the concatenation, segmentation and reassembly of RLC data PDU (SDU), the re-segmentation of RLC data PDU and the reordering of RLC data PDU; and MAC layer functions, wherein the MAC layer functions are associated with the mapping between logical channels and transport channels, the multiplexing of MAC SDU onto transport blocks (TB), the demultiplexing of MAC SDU from TB, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority processing and logical channel prioritization.

[0056] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functions associated with various signal processing functions. Layer 1 (including the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 processes the mapping to the signal constellation based on various modulation schemes (such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams, each of which can then be mapped to an Orthogonal Frequency Division Multiplexing (OFDM) subcarrier, multiplexed with a Reference Signal (RS) (such as a pilot) in the time domain and / or frequency domain, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from the channel estimator 274 can be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from RS and / or channel state feedback transmitted by the UE 250. Each spatial stream can then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX can modulate an RF carrier using each spatial stream for transmission.

[0057] At the UE 250, each receiver 254RX can receive a signal through each antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functions associated with various signal processing functions. The RX processor 256 can perform spatial processing on the information to recover any spatial stream to the UE 250. If there are multiple spatial streams to the UE 250, the multiple spatial streams can be combined into a single OFDM symbol stream by the RX processor 256. The RX processor 256 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes separate OFDM symbol streams for each subcarrier of the OFDM signal. The symbols and RS on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted by the BS 210. These soft decisions can be based on the channel estimates calculated by the channel estimator 258. These soft decisions may then be decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by BS 210. The data and control signals may then be provided to controller / processor 259, which implements layer 3 and layer 2 functions.

[0058] The controller / processor 259 may be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer readable medium. In the UL, the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an Acknowledgement (ACK) and / or Negative Acknowledgment (NACK) protocol to support HARQ operations.

[0059] Similar to the functions described in conjunction with DL transmission of BS210, the controller / processor 259 provides: RRC layer functions, wherein the RRC layer functions are associated with acquisition of system information (such as MIB, SIB), RRC connection and measurement reporting; PDCP layer functions, wherein the PDCP layer functions are associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions, wherein the RLC layer functions are associated with transfer of higher layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functions, wherein the MAC layer functions are associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing and logical channel prioritization.

[0060] The channel estimate derived from the RS or feedback transmitted by the channel estimator 258 from the BS 210 can be used by the TX processor 268 to select the appropriate codec and modulation scheme, and to facilitate spatial processing. The spatial stream generated by the TX processor 268 can be provided to different antennas 252 via separate transmitters 254TX. Each transmitter 254TX can modulate the RF carrier using each spatial stream for transmission. Similar to the description of the receiver function at the UE 250, UL transmission is processed in a similar manner at the BS 210. Each receiver 218RX receives a signal through each antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 270.

[0061] The controller / processor 275 may be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer readable medium. In the UL, the controller / processor 275 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 250. The IP packets from the controller / processor 275 may be provided to the EPC 160. The controller / processor 275 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0062] NR may refer to a radio configured to operate according to a new air interface (e.g., in addition to an OFDMA-based air interface) or a fixed transport layer (e.g., in addition to IP). NR may utilize OFDM with a cyclic prefix (CP) on both UL and DL, and may include support for half-duplex operation using time division duplexing (TDD). NR may include mission critical features such as Enhanced Mobile Broadband (eMBB) services targeting wide bandwidths (e.g., above 80 MHz), mmW targeting high carrier frequencies (e.g., 60 GHz), Massive Machine Type Communication (mMTC) targeting non-backward compatible Machine Type Communication (MTC) technologies, and / or Ultra-Reliable Low Latency Communication (URLLC) services targeting.

[0063] A single component carrier bandwidth of 100 MHz can be supported. In one example, an NR resource block (RB) can span 12 subcarriers, where the 12 subcarriers have a subcarrier bandwidth of 60 KHz over a duration of 0.25 ms or a bandwidth of 30 KHz over a duration of 0.5 ms (similarly, 50 MHz bandwidth is used for a 15 kHz subcarrier spacing (SCS) over a duration of 1 ms). Each radio frame may include 10 subframes (or 10, 20, 40, or 80 NR time slots) of length 10 ms. Each time slot may indicate the link direction (i.e., DL or UL) used for data transmission and the link direction for each time slot may be dynamically switched. Each time slot may contain DL / UL data and DL / UL control data. Please refer to the following Figure 5 and Figure 6 The UL and DL time slots for NR are described in more detail.

[0064] The NR RAN may include a central unit (CU) and a distributed unit (DU). The NR BS (such as gNB, 5G NB, NB, Transmission Reception Point (TRP), AP) may correspond to one or more BSs. The NR cell may be configured as an access cell (ACell) or a data-only cell (DCell). For example, the RAN (such as a CU or DU) may configure the above cells. The DCell may be a cell for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or switching. In some cases, the DCell may not transmit a synchronization signal (SS), and in some cases, the DCell may transmit an SS. The NR BS may transmit a DL signal to the UE to indicate the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine the NR BS based on the indicated cell type to consider cell selection, access, switching, and / or measurement.

[0065] Figure 3 An exemplary logical architecture of a distributed RAN 300 according to aspects of the present invention is illustrated. A 5G access node (AN) 306 may include an access node controller (ANC) 302. The ANC may be the CU of a distributed RAN. The backhaul interface to the Next Generation Core Network (NG-CN) 304 may terminate at the ANC. The backhaul interface to an adjacent next generation access node (NG-AN) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (TRPs may also be referred to as BSs, NR BSs, NBs, 5G NBs, APs, or some other terms). As described above, TRPs may be used interchangeably with "cells."

[0066] The TRP 308 may be a DU. The TRP may be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to independently (e.g., dynamically selected) or jointly (e.g., jointly transmitted) supply services to the UE.

[0067] The logical architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can be defined to support fronthaul solutions across different deployment types. For example, the architecture can be based on transmission network performance (such as bandwidth, latency and / or jitter). The architecture can share features and / or components with LTE. According to aspects of the present invention, the NG-AN310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0068] The architecture may enable collaboration between TRPs 308. For example, collaboration may be provisioned within and / or across TRPs via ANC 302. According to aspects of the invention, an inter-TRP interface may not be required / existent.

[0069] According to aspects of the present invention, dynamic configuration of separate logical functions may exist within the architecture of the distributed RAN 300. PDCP, RLC, MAC protocols may be adaptively located at the ANC or TRP.

[0070] Figure 4 An exemplary physical architecture of a distributed RAN 400 according to aspects of the present invention is illustrated. A centralized core network unit (C-CU) 402 can host core network functions. The C-CU can be centrally deployed. To handle peak capacity, C-CU functions can be offloaded (e.g., to Advanced Wireless Service (AWS)). A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have a distributed deployment. The C-RU can be closer to the edge of the network. The DU 406 can host one or more TRPs. The DU can be located at the edge of the network with RF functions.

[0071] Figure 55 is a schematic diagram of an exemplary DL-centric time slot. The DL-centric time slot may include a control portion 502. The control portion 502 may be present in an initial or starting portion of the DL-centric time slot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the DL-centric time slot. In some configurations, such as Figure 5 As shown, the control portion 502 can be a physical downlink control channel (Physical DL Control Channel, PDCCH). The DL-centric time slot can also include a DL data portion 504. The DL data portion 504 can sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 504 can include communication resources for communicating DL data from a scheduling entity (such as a UE or a BS) to a subordinate entity (such as a UE). In some configurations, the DL data portion 504 can be a physical downlink shared channel (Physical DL Shared Channel, PDSCH).

[0072] The DL-centric time slot may also include a common UL portion 506. The common UL portion 506 may sometimes be referred to as a UL burst, a common UL burst, and / or various other suitable terms. The common UL portion 506 may include feedback information corresponding to various other portions of the DL-centric time slot. For example, the common UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The common UL portion 506 may include additional or further information, such as information about a random access channel (RACH) process, a scheduling request, and various other suitable types of information.

[0073] like Figure 5As shown, the end of the DL data portion 504 can be separated in time from the start of the common UL portion 506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation provides time for a switch-over from DL communications (e.g., a reception operation performed by a subordinate entity (e.g., a UE)) to UL communications (e.g., a transmission performed by a subordinate entity (e.g., a UE)). It will be appreciated by those skilled in the art that the foregoing is merely an example of a DL-centric time slot, and that alternative structures having similar features may exist without necessarily departing from the aspects described herein.

[0074] Figure 6 600 is a diagram of an exemplary UL-centric timeslot. The UL-centric timeslot may include a control portion 602. The control portion 602 may be present in an initial or starting portion of the UL-centric timeslot. Figure 6 The control part 602 in the above reference Figure 5 The control portion 502 described is similar. The UL-centric time slot may also include a UL data portion 604. The UL data portion 604 may sometimes be referred to as the payload of the UL-centric time slot. The UL portion may refer to communication resources used to communicate UL data from a subordinate entity (such as a UE) to a scheduling entity (such as a UE or a BS). In some configurations, the control portion 602 may be a physical uplink control channel (PUCCH).

[0075] like Figure 6 As shown, the end of the control portion 602 can be separated in time from the beginning of the UL data portion 604. This time separation may sometimes be referred to as an interval, a guard period, a guard gap, and / or various other suitable terms. The separation provides time for switching from DL communications (such as reception operations performed by the scheduling entity) to UL communications (such as transmissions performed by the scheduling entity). The UL-centric timeslot may also contain a common UL portion 606. Figure 6 The common UL portion 606 in the embodiment may be similar to the above reference Figure 5The common UL portion 506 described herein. The common UL portion 606 may additionally or additionally include information about a channel quality indicator (CQI), a sounding reference signal (SRS), and various other suitable types of information. It will be appreciated by those skilled in the art that the foregoing is merely an example of a UL-centric time slot, and that alternative structures having similar features may exist without necessarily departing from the aspects described herein.

[0076] In some cases, two or more subordinate entities (such as UEs) can use sidelink signals to communicate with each other. The actual applications of such sidelink communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical meshes, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is communicated from one subordinate entity (such as UE1) to another subordinate entity (such as UE2) without relaying the communication through a scheduling entity (such as a UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, a sidelink signal may use a licensed spectrum to communicate (unlike wireless local area networks that typically use unlicensed spectrum).

[0077] Figure 7 700 is a diagram illustrating an example wireless communication system including a base station and a UE. In this example, a UE 704 is connected to a base station 702 located in a cell 706.

[0078] The Ambient Internet of Things (A-IoT) space currently faces challenges due to a lack of standardization in the signal transmission and operation processes of backscatter devices. This lack of standardization can lead to inconsistencies and inefficiencies in system operation.

[0079] In an A-IoT system, A-IoT devices are designed to communicate directly and bidirectionally with a base station. This communication includes the transmission and reception of A-IoT data and / or signals. Interestingly, the base station transmitting to an A-IoT device may be different from the base station receiving from it, which adds a layer of complexity to the system topology.

[0080] Figure 8800 is a schematic diagram illustrating an example wireless link between a next-generation NodeB (gNB) and an A-IoT device. One area of ​​ambiguity in the current A-IoT setup is the nature of the wireless link between the gNB and the A-IoT device. Specifically, it is unclear whether the link employs the New Radio User Plane (NR Uu) interface, which is typically used to connect the UE and gNB over the air. This ambiguity can lead to confusion and potential inefficiencies in the design and operation of A-IoT systems.

[0081] FIG9(A) is a schematic diagram 900 illustrating an example communication link between a gNB and an A-IoT device connected to a UE via a wired cable.

[0082] The present invention introduces a new A-IoT communication system topology. As shown in Figure 9 (A), the gNB establishes a connection with the UE or UE reader through a wired cable. This configuration eliminates the need for a new air interface between the gNB and the A-IoT device, and instead introduces a new air interface between the UE reader and the A-IoT device. Therefore, the effort required for gNB specification changes is significantly reduced. In this setup, the gNB can access the A-IoT device through the UE reader, which acts as an intermediate node between the device and the base station (gNB).

[0083] FIG9(B) is a schematic diagram 920 showing an example communication link between a gNB and an A-IoT device connected to a UE via a wireless air interface. As shown in FIG9(B), a wireless air interface is established between the gNB and the UE or UE reader. This air interface utilizes the NR-Uu interface to minimize specification changes on the UE side. A new air interface is required between the UE and the A-IoT device, and its specification can be determined based on the use case and its corresponding requirements.

[0084] The present invention may be particularly relevant to smart factories, a market that is expected to reach $143 billion by 2030. One of the main needs of this industry is inventory use cases. Requirements for these use cases include ultra-low power transceiver and device architectures, low complexity waveforms, modulation, coding, signaling, channel and synchronization schemes, indoor coverage and low mobility.

[0085] To meet these requirements, the present invention proposes to use backscatter-based transmission, including providing a carrier for backscattering. According to this approach, A-IoT devices are divided into three types.

[0086] FIG10(A) is a schematic diagram 1000 showing the first type of A-IoT device, device A. Device A is designed with specific goals in terms of power consumption (≤1μW or ≤10μW) and complexity during transmission / reception, aiming to be comparable to UHF RFID ISO18000-6C (EPC C1G2). Device A has no energy storage or independent signal generation / amplification capabilities and relies on backscatter transmission. It requires a backscatter activation power threshold, experiences reflection losses, and requires a long-distance carrier source to transmit the positioning signal.

[0087] The architecture of device A includes the following components:

[0088] 1) Low pass filter (LPF) to suppress adjacent sub-carrier interference (ASCI) and adjacent carrier interference (ACI)

[0089] 2) Envelope detector (ED) to support signals based on On-Off Keying (OOK)

[0090] 3) Analog to digital converter (ADC) for digital baseband processing

[0091] 4) Digital baseband (DBB), used for sequence matching

[0092] 5) A modulator (switch) controlled by the incoming signal to add payload data to the OOK modulation

[0093] 6) RF energy harvester, converting RF signals into energy

[0094] FIG10(B) is a schematic diagram 1020 showing a second type of A-IoT device, device B. Device B is designed to be between device A and device C in terms of power and complexity. It has energy storage but no independent signal generation, relying on backscatter transmission. The stored energy can be used for signal amplification. Device B also requires a backscatter activation power threshold, experiences reflection losses, and requires a long-distance carrier source for positioning.

[0095] The architecture of device B includes the following components:

[0096] 1) LPF, used to suppress ASCI and ACI

[0097] 2) ED to support OOK-based signals

[0098] 3)ADC, for digital baseband processing

[0099] 4) DBB, for sequence matching

[0100] 5) A modulator controlled by the incoming signal to add payload data to the OOK modulation

[0101] 6) RF energy harvester, converting RF signals into energy

[0102] 7) Additional energy harvesters for different types of ambient energy sources such as RF radio, solar, thermal, and piezoelectric

[0103] 8) Energy storage, such as capacitors and solid-state batteries

[0104] 9) Reflection amplifier, used to amplify the signal input to the tag and the backscattered signal sent to the reader

[0105] FIG10(C) is a schematic diagram 1040 showing a third type of A-IoT device, device C. Device C is designed to have power consumption of ≤1mW to ≤10mW during transmission / reception and complexity several orders of magnitude lower than that of NarrowBand IoT (NB-IoT). Device C has energy storage, independent signal generation, and active RF components for transmission. It also has mobility management capabilities, at least for cell selection / reselection.

[0106] The architecture of device C includes the following components:

[0107] 1) LPF, used to suppress ASCI and ACI

[0108] 2) ED to support OOK-based signals

[0109] 3) Analog-to-digital converter (ADC) for digital baseband processing

[0110] 4) Digital baseband (DBB), used for synchronization, payload decoding and cyclic redundancy check (CRC)

[0111] 5) RF energy harvester, converting RF signals into energy

[0112] 6) Additional energy harvesters for different types of ambient energy sources such as RF radio, solar, thermal, and piezoelectric

[0113] 7) Energy storage, such as capacitors and solid-state batteries

[0114] 8) Low-noise amplifier (LNA) and power amplifier (PA) for amplifying received and transmitted signals

[0115] FIG. 11(A) is a schematic diagram 1100 illustrating an example communication link between a user equipment (eg, UE 1104 ) and an A-IoT device (eg, A-IoT device 1106 ) over an air interface.

[0116] The present invention introduces a new air interface for communication between UE 1104 and A-IoT device 1106. The communication process begins with UE 1104 energizing A-IoT device 1106 and transmitting a command. The command specifies basic communication parameters such as tag rate, tag data encoding method, and the total number of available time slots.

[0117] After collecting enough energy, the A-IoT device 1106 activates and listens for commands from the UE. After decoding the command, the A-IoT device 1106 randomly selects a time slot from the available range and generates a random sequence. The sequence is then transmitted in the selected time slot, preceded by a known preamble sequence.

[0118] FIG11(B) is a schematic diagram 1120 showing an example timing of the communication process between the UE 1104 and the A-IoT device 1106 over the air interface.

[0119] In response to the A-IoT transmission, UE 1104 decodes the received preamble sequence and sends an ACK to A-IoT 1106 within a predetermined duration to confirm the system configuration of the A-IoT rate.

[0120] FIG11(C) is a schematic diagram 1140 illustrating an example communication process between a UE 1104 and an A-IoT device 1106 based on a selected time slot.

[0121] Inside the UE 1104, a new function called "A-IoT decoder" is responsible for frame synchronization, channel estimation, and detection of A-IoT responses. Synchronization of the A-IoT sequence is done by correlating the received signal with a known preamble sequence. After synchronization, channel estimation is performed using the preamble sequence.

[0122] In certain embodiments, the present invention proposes a new air interface for communication between UE 1104 and A-IoT device 1106. The communication process begins when UE 1104 powers on and transmits a command to A-IoT device 1106. The command outlines basic communication parameters such as tag rate, tag data encoding method, and total available duration.

[0123] Once the A-IoT device 1106 has collected enough energy, it can activate and listen for commands from the UE. After decoding the command, the A-IoT device 1106 randomly selects a duration from the available range and generates a random sequence. The sequence is then transmitted for the selected duration, preceded by a known preamble sequence.

[0124] In response to the A-IoT transmission, the UE 1104 decodes the received preamble sequence and sends an acknowledgment to the A-IoT device 1106 within a predetermined duration, aligned with the system configuration for the A-IoT rate.

[0125] 11(D) is a schematic diagram 1160 showing an example communication process between the UE 1104 and the A-IoT device 1106 based on a selected duration. The process is similar to the process depicted in FIG. 11(C) except that the time slot is replaced by the duration.

[0126] UE 1104 contains a new function called "A-IoT decoder" which is responsible for frame synchronization, channel estimation and detection of A-IoT responses. Synchronization of the A-IoT sequence is achieved by correlating the received signal with a known preamble sequence. After synchronization, channel estimation is performed using the preamble sequence.

[0127] Communication link from UE to A-IoT device (U2A link)

[0128] U2A (also known as Reader to Device (R2D)) links can use the following modulation schemes, such as Amplitude Shift Keying (ASK) or On-Off Keying (OOK), where OOK-1 is used for single chip per OFDM symbol transmission, OOK-4 is used for M chips per OFDM symbol transmission, and ASK includes Double Sideband Amplitude Shift Keying (DSB-ASK), Single Sideband Amplitude Shift Keying (SSB-ASK) and Partial Response Amplitude Shift Keying (PR-ASK):

[0129] Double Sideband Amplitude Shift Keying (DSB-ASK): A modulation technique in which both the upper and lower sidebands of the carrier signal are used to transmit data. It is less bandwidth efficient but simpler to implement.

[0130] Single Sideband Amplitude Shift Keying (SSB-ASK): A modulation technique in which one sideband (upper or lower) of the carrier signal is used to transmit data. It is more bandwidth efficient but requires more complex equipment to implement.

[0131] Partial Response Amplitude Keying (PR-ASK): A modulation scheme designed to increase data rates without increasing bandwidth. It involves switching between different amplitude levels within a few symbol periods, requiring more complex signal processing at the receiver.

[0132] The R2D link uses one of the above ASK modulation schemes to facilitate the use of Pulse Interval Encoding (PIE) in data transmission. PIE is a form of OOK modulation in which the duration of the gap between pulses represents the data. PIE is widely used due to its robustness to noise and interference.

[0133] UE 1104 may also use Manchester encoding for R2D communication. Manchester encoding, also known as Phase Encode (PE), is a synchronous clock encoding technique. It combines data and clock signals for self-synchronous transmission, which is common in Ethernet and local area networks (LANs).

[0134] In Manchester encoding, separate data and clock signals are combined into a self-synchronizing data stream. This data stream is suitable for transmission over a serial channel. In Manchester encoding, there is a transition in the middle of each bit, which serves as both a clock signal and a data signal. Specifically, a transition from low to high represents a "0", while a transition from high to low represents a "1". The opposite encoding scheme can also be applied.

[0135] The clock synchronization signal is embedded in the data waveform. This allows the receiver to extract the clock signal directly from the data. Since each bit in Manchester coding is represented by two voltage levels, the data transmission rate is half the modulation rate. Therefore, the coding efficiency is 50%.

[0136] On the other hand, PIE is a type of encoding that represents data by defining different time widths between the falling edges of a pulse. The specific time widths between these falling edges are used to distinguish different data values. In particular, PIE represents data by the time intervals between the falling edges of a pulse, and is suitable for applications where the timing of the pulse is critical.

[0137] The R2D link includes two known preamble sequences: a long R2D preamble sequence and a short R2D preamble sequence. The long R2D preamble sequence is used for the initial transmission between the UE 1104 and the A-IoT. Once synchronization is established, the short preamble sequence can be used at the beginning of all other signaling.

[0138] The UE 1104 transmits a long R2D preamble sequence and a control signal or command. The long R2D preamble sequence enables the A-IoT device 1106 to synchronize with the UE 1104, and the command may specify control parameters such as data rate, data coding, and the number of time slots N for the A-IoT device 1106 to select and transmit a response sequence.

[0139] The control signal or command includes parameters such as operating frequency range, operating channel, frequency hopping rate, frequency hopping sequence, occupied channel bandwidth, minimum receiver bandwidth, UE transmit maximum effective isotropic radiated power (EIRP), UE transmit spurious emissions, UE transmitter spectrum mask, timing, modulation, data coding, bit rate, UE transmit modulation accuracy, preamble, bit transmission order, wake-up process, polarization, and other communication parameters.

[0140] In another embodiment, in addition to double sideband amplitude keying (DSB-ASK), single sideband amplitude keying (SSB-ASK) and partial response amplitude keying (PR-ASK), other waveforms are available for diverse communication needs:

[0141] Quadrature Amplitude Modulation (QAM): A modulation scheme that combines ASK and phase shift keying (PSK) to increase the data rate without increasing the bandwidth.

[0142] Gaussian Frequency Shift Keying (GFSK): A modulation scheme that uses a Gaussian filter to shape the binary symbols before performing frequency shift keying, reducing the spectrum width.

[0143] Binary Frequency Shift Keying (BFSK): A modulation scheme in which the frequency of the digital information modulating the carrier signal varies between two predefined values.

[0144] Quadrature Frequency Shift Keying (QFSK): A modulation scheme that extends BFSK by using four different frequency values ​​to transmit two bits per symbol.

[0145] Minimum Shift Keying (MSK): A type of FSK in which the frequency shifts are as small as possible to minimize the required bandwidth.

[0146] Continuous Phase Frequency Shift Keying (CPFSK): A modulation scheme that continuously varies the phase of the carrier wave according to the input data.

[0147] Multi-Frequency Shift Keying (MFSK): A modulation scheme that uses more than two frequencies to transmit multiple bits per symbol.

[0148] Offset Quadrature Phase Shift Keying (OQPSK): A modulation scheme that extends QPSK by offsetting the carrier phase for each symbol, reducing the probability of error.

[0149] Gaussian Minimum Shift Keying (GMSK): A modulation scheme that combines the advantages of GFSK and MSK to efficiently utilize bandwidth.

[0150] Orthogonal Frequency Division Multiplexing (OFDM): A modulation scheme that divides the available spectrum into several orthogonal subcarriers, each of which carries a portion of the data.

[0151] These waveforms offer a balance between bandwidth efficiency, implementation complexity, and error performance, making them suitable for different RFID applications.

[0152] A-IoT device to UE communication link (A2U link)

[0153] The A2U (also known as Device to Reader (D2R)) link uses amplitude shift keying (ASK) or phase shift keying (PSK) modulation, and baseband modulation uses OOK and binary PSK, and minimum shift keying (MSK) as a variant of binary FSK. Under the control of UE 1104 or gNB over the D2R link, A-IoT encodes the backscattered data using FM0 baseband or Miller modulation. FM0 and Miller line codes can be provided for D2R transmission.

[0154] FM0 coding inverts the baseband phase at each symbol boundary, and for data-0 or information bit 0, there is also a mid-symbol phase inversion. FM0 coding has memory, so the choice of sequence depends on the previous transmission. At the end of the transmission, the FM0 signal always ends with a "dummy" data-1 bit or information bit 1.

[0155] The FM0 signal starts with one of two preamble sequences, depending on the configuration in the command or control signal. In some cases, A-IoT uses an extended preamble sequence regardless of the configuration, for example, the extended preamble sequence is used for delayed or in-process replies.

[0156] Miller coding inverts its phase between two consecutive data-0 symbols and in the middle of a data-1 symbol. The state diagram maps the data sequence to the baseband Miller basis function. The transmitted waveform is the baseband waveform multiplied by a square wave whose frequency is M times the symbol rate. Certain state transitions are not allowed to prevent phase inversion at inappropriate symbol boundaries.

[0157] D2R link signaling begins with one of two Miller subcarrier preamble sequences. The choice depends on the command or control signal. However, if the tag is replying to a command using a delayed or in-progress reply, it can use the extended preamble sequence regardless of the configuration.

[0158] A-IoT uses backscatter modulation to change the reflection coefficient of its antenna to transmit data, using at least a single-tone unmodulated sine waveform as a candidate waveform for the carrier waveform of D2R backscatter. A-IoT uses a fixed modulation format, data coding, and data rate. A-IoT selects the modulation format, and UE 1104 sets the data coding and data rate.

[0159] The D2R link transmits the Electronic Product Code (EPC) and Protocol-Control (PC). EPC can stand for product code, or any type of A-IoT data. PC is a control signal used to regulate the timing and format of the radio signal and data transmission.

[0160] Typical PCs include parameters such as operating frequency range, default operating frequency, operating channel, frequency accuracy, frequency hopping rate, frequency hopping sequence, occupied channel bandwidth, maximum EIRP, spectrum mask, unnecessary emission, switching time, dwell time, modulation, on-off ratio, subcarrier signal frequency, accuracy, Miller coding scheme modulation, nominal duty cycle, data representation, bit transmission rate, accuracy, preamble sequence, bit transmission order, polarization, and minimum tag receiver bandwidth. These parameters can be controlled by the UE or the gNB.

[0161] Cyclic Redundancy Check (CRC)

[0162] CRC is the method used by the tag to verify the validity of commands from the UE 1104, and by the reader to check the validity of replies from the A-IoT device 1106. The protocol uses two types of CRC: CRC-16 and CRC-5.

[0163] Link Timing

[0164] The communication timing between the UE 1104 and the A-IoT device 1106 can be classified as immediate, delayed, or in-process replies. The A-IoT device 1106 can respond immediately, in accordance with the T1 timing (e.g., 500us), provide a delayed reply according to the T2 timing (e.g., 20ms), or issue an in-process reply to periodically inform the UE 1104 that it is still processing the command.

[0165] Slotted Aloha Protocol

[0166] The slotted Aloha protocol is a four-step process:

[0167] 1. Query: The UE 1104 broadcasts a query and indicates the number of available time slots.

[0168] 2. RN16: If the A-IoT device 1106 decodes the query, it selects a random time slot and then responds with a 16-bit random sequence (RN16) using FM0 modulation in the selected time slot.

[0169] 3. ACK: In each time slot, if UE 1104 decodes RN16, it sends an acknowledgement (ACK) containing the same decoded RN16.

[0170] 4. EPC: Each tag that decodes the ACK compares the contained RN16 with the RN16 it previously selected and responds with its Electronic Product Code (EPC) when there is a match.

[0171] FIG. 12(A) is a schematic diagram 1200 illustrating an example communication timing diagram between a UE 1104 and an A-IoT device 1106 .

[0172] The A-IoT device 1106 selects a number between 1 and N, where N is the number of time slots provided by the command or control signal, and transmits a random 16-bit sequence (RN16) preceded by a known preamble sequence in the selected time slot.

[0173] UE 1104 confirms the A-IoT device 1106 by sending an ACK signal. If the tag receives an ACK containing the correct RN16, it sends a reply. After a successful ACK, UE 1104 can access the confirmed A-IoT device 1106 to obtain EPC or protocol control information (PC).

[0174] FIG12(B) is a schematic diagram 1220 showing an example communication process between the gNB, the UE 1104, and the A-IoT device 1106. As shown in FIG12(B):

[0175] UE 1104 broadcasts a command to the A-IoT device 1106 and indicates the number of time slots.

[0176] The A-IoT device 1106 decodes the command, selects a random time slot, and responds with a random sequence using FM0 modulation in the selected time slot.

[0177] UE 1104 forwards the random sequence to the gNB.

[0178] The gNB decodes the random sequence and prepares an ACK.

[0179] The gNB sends an ACK to UE 1104 within the specified duration.

[0180] UE 1104 forwards the ACK to A-IoT device 1106.

[0181] The A-IoT device 1106 matches the decoded sequence in the ACK with the selected sequence and replies with a unique identifier if there is a match.

[0182] UE 1104 forwards the unique identifier to the gNB.

[0183] In a first aspect, the UE 1104 may include:

[0184] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0185] If the UE 1104 is in the process of communicating with the A-IoT device 1106, a command is received from the base station, which is used to specify communication parameters such as tag rate, tag data encoding method and the total number of available time slots.

[0186] If the A-IoT device 1106 has collected enough energy and is activated, it determines a random sequence and a time slot from the available range for transmission.

[0187] If the UE 1104 has a new function called "A-IoT decoder", frame synchronization, channel estimation and detection of A-IoT response are performed.

[0188] If the UE 1104 has decoded the preamble sequence from the A-IoT transmission, then within a predetermined duration, an ACK for the A-IoT device 1106 is transmitted to the base station.

[0189] In a second aspect, the UE 1104 may include:

[0190] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0191] If the UE 1104 is in the process of communicating with the A-IoT device 1106, a command or control signal is received from the base station to specify control parameters, such as data rate, data coding, and the number of time slots N for the A-IoT device 1106 to select and transmit a response sequence.

[0192] If the A-IoT device 1106 adopts backscatter modulation and changes the reflection coefficient of its antenna to transmit data, the modulation format is determined, and the UE 1104 sets the data coding and data rate.

[0193] Executing the slotted Aloha protocol, if the A-IoT device 1106 decodes the query, it selects a random time slot and then responds with a 16-bit random sequence (RN16) in the selected time slot using FM0 modulation.

[0194] If each tag that decodes the ACK compares the contained RN16 with the RN16 it previously selected, and the decoded sequence in the ACK matches the selected sequence, an Electronic Product Code (EPC) is transmitted to the BS.

[0195] Uplink Power Control

[0196] To address inter-UE interference issues when UE 1104 uses uplink to connect to A-IoT device 1106, the gNB uses these mechanisms to control power. At the start of communication, UE 1104 stimulates A-IoT device 1106 and transmits a command that outlines basic communication parameters such as tag rate, data encoding method, and total number of available time slots.

[0197] To adapt the R2D link to the existing 5G NR power control mechanism, several adjustments can be made:

[0198] Open-loop and closed-loop power control: These mechanisms can be adjusted to take into account specific characteristics of A-IoT devices, such as their energy harvesting capabilities and their backscattering characteristics. Path loss calculations in open-loop control can include energy transfer from UE 1104 to A-IoT device 1106, and TPC commands in closed-loop control can be adjusted based on the quality of the signal backscattered from the A-IoT.

[0199] Power control for PUCCH, PUSCH, and SRS: Since the R2D link uses ASK or OOK modulation, the power control for these channels can be adjusted accordingly. For example, the power control offset provided by the base station can be adjusted to optimize the ASK or OOK modulation.

[0200] Power Ramping and Power Backoff: These mechanisms can be used to manage the power level of the R2D link. Power ramping can be used when the UE 1104 initially stimulates the A-IoT device 1106, and power backoff can be used when the UE 1104 transmits commands to the A-IoT device 1106 to avoid providing too much power to the A-IoT device 1106.

[0201] Timing Adjustment: The timing of the communication can be adjusted according to the specific requirements of the R2D link. For example, the transition time can be adjusted to accommodate the time required for the A-IoT device 1106 to harvest energy and respond to the UE command.

[0202] Modulation and data coding: The modulation and data coding used in the R2D link (e.g., DSB-ASK, SSB-ASK, PR-ASK, and PIE) can be integrated into the power control mechanism. The power level can be adjusted to optimize these modulation and data coding techniques.

[0203] Slotted Aloha protocol: This protocol can be used to manage the communication between UE 1104 and multiple A-IoTs. The power control mechanism can be adjusted to adapt to the random slot selection of A-IoT and the confirmation process of UE 1104.

[0204] Fig.13 is a timing diagram 1300 outlining the interaction between UE 1104 and gNB regarding uplink power control.

[0205] This sequence diagram provides a high-level overview of the interaction between the UE 1104, gNB, and A-IoT device 1106 in the context of uplink power control. It covers the main steps from the UE 1104 stimulating the A-IoT device 1106 and transmitting commands to the ongoing communication managed by the slotted Aloha protocol.

[0206] In a first aspect, a UE 1104 may include:

[0207] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0208] If the UE 1104 is in a communication process with the A-IoT device 1106 and the UE 1104 is transmitting a command to the A-IoT device 1106, a power control offset of ASK or OOK modulation is received from the base station.

[0209] If the A-IoT device 1106 has energy harvesting capability and backscattering characteristics, the appropriate power level of the R2D link is determined by adjusting the received power control offset.

[0210] If the UE 1104 needs to manage the power level of the R2D link, power ramping is performed when the A-IoT device 1106 is initially activated and power backoff is performed when commands are transmitted to the A-IoT device 1106.

[0211] If the UE 1104 has received a backscatter signal from the A-IoT device 1106 , the quality of the backscatter signal received from the A-IoT device 1106 is transmitted to the BS.

[0212] In a second aspect, the UE 1104 may include:

[0213] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0214] Receive a command from the base station specifying communication parameters such as tag rate, data encoding method, and the total number of available time slots if the UE 1104 is in the process of communicating with the A-IoT device 1106.

[0215] The timing of the communication is determined according to the specific requirements of the R2D link, if the A-IoT device 1106 needs time to collect energy and respond to the UE's commands.

[0216] If UE 1104 needs to adapt to the random time slot selection of A-IoT and the confirmation process of UE 1104, the time slotted Aloha protocol is executed to manage the communication between UE 1104 and multiple A-IoTs.

[0217] If the UE 1104 has decoded the preamble sequence from the A-IoT transmission, then within a predetermined duration, an acknowledgement to the A-IoT device 1106 is transmitted to the BS.

[0218] Uplink beam management

[0219] In the context of R2D links, 5G NR uplink beam management can be adjusted to save power in the UE and prevent interference with other UEs or A-IoT devices. Here are some possible modifications:

[0220] Beam determination: In the R2D context, the UE 1104 needs to determine the best beam to transmit to the A-IoT device 1106. This can be done by the UE 1104 sending a set of beam reference signals (BRS) to the A-IoT device 1106, and then the A-IoT device 1106 confirms the best communication beam. This process needs to be energy-efficient to save power in the UE.

[0221] Beam Measurement: The UE 1104 will measure the quality of the ACK from the A-IoT device 1106 to determine the best beam. The measurement criteria can be adjusted to take into account specific characteristics of the A-IoT device 1106, such as its energy harvesting capabilities and its backscattering characteristics.

[0222] Beam reporting: UE 1104 will report the best beam to the gNB. To prevent interference with other UEs or A-IoT devices, the report may include information about the beam direction and width so that the gNB can coordinate beam usage among multiple UEs.

[0223] Beam switching: The gNB may command the UE 1104 to switch to the reported beam for uplink transmission to the A-IoT device 1106. The switching needs to be done in a way that minimizes UE power consumption and avoids causing interference to other UEs or A-IoT devices.

[0224] Beam tracking: The UE 1104 and gNB will constantly track the channel status and switch to a different beam when necessary. This process needs to be energy-efficient and take into account potential interference to other UEs or A-IoT devices.

[0225] These adjustments will allow 5G NR uplink beam management to be used effectively for the R2D link, ensuring efficient use of UE power and minimizing interference.

[0226] FIG14(A) is a timing diagram 1400 outlining the interactions between the UE 1104 and the gNB in ​​the context of 5G NR uplink beam management for R2D links. FIG14(A) provides a high-level overview of the interactions between the UE 1104, the gNB, and the A-IoT device 1106 in the context of 5G NR uplink beam management for R2D links. It covers the main steps from sending a set of BRS from the UE 1104 to the A-IoT device 1106, to continuously tracking the channel status and potential beam switching.

[0227] In a first aspect, the UE 1104 may include:

[0228] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0229] A set of BRS is received from the base station if UE 1104 is in communication with the A-IoT device 1106 and UE 1104 is determining the best beam to transmit to the A-IoT device 1106.

[0230] If the A-IoT device 1106 has confirmed the best beam based on the received BRS, and the UE 1104 has measured the quality of the confirmation from the A-IoT device 1106, the best beam for communicating with the A-IoT device 1106 is determined.

[0231] If the BS has commanded UE 1104 to switch to the reported beam, and the switching is done in a manner that minimizes UE power consumption and avoids interference to other UEs or A-IoT devices, then switching to the reported beam for uplink transmission to A-IoT device 1106 is performed.

[0232] If the UE 1104 has determined the best beam and the report includes information about the beam direction and width to prevent interference with other UEs or A-IoT devices, the best beam for communicating with the A-IoT device 1106 is transmitted to the BS.

[0233] In a second aspect, the UE 1104 may include:

[0234] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0235] Receive a command from the base station to switch to the reported beam for uplink transmission to the A-IoT device if UE 1104 is in communication with the A-IoT device 1106 and UE 1104 has reported the best beam to the BS.

[0236] Determine the timing of beam switching if switching is required in a way that minimizes the UE’s power consumption and avoids interference to other UEs or A-IoT devices.

[0237] If the UE 1104 and the base station need to constantly monitor the channel status to efficiently use the UE's power and minimize interference, tracking of the channel status is performed and switching to a different beam when necessary.

[0238] If the UE 1104 has measured the quality of the ACK from the A-IoT device 1106 to determine the best beam, the quality of the ACK from the A-IoT device 1106 is transmitted to the base station.

[0239] Measuring gap

[0240] In the case where the UE 1104 needs to communicate with the A-IoT device 1106 and may not be able to receive signals from the gNB during this period, a special type of measurement gap can be configured. This measurement gap can be used specifically for R2D communication. Here is how it works:

[0241] Configuration: The gNB configures the measurement gap for the UE 1104 via RRC signaling. This measurement gap is specifically for R2D communication. The gNB specifies the gap pattern, which includes the gap length and the gap period. However, since the gNB may not know how much time the UE 1104 needs to communicate with A-IoT, it can provide a longer gap length or a flexible gap pattern that can be adjusted dynamically.

[0242] Activation: Once the R2D communication gap is configured, the UE 1104 activates the gap at the specified time. During the gap, the UE 1104 suspends normal transmission and reception with the gNB and switches to R2D communication mode.

[0243] R2D communication: During R2D communication gaps, the UE 1104 communicates with the A-IoT device 1106. This may involve sending commands to the A-IoT device 1106, receiving responses, stimulating the A-IoT device 1106, or performing other tasks related to R2D communication.

[0244] Resume: After the R2D communication gap, UE 1104 resumes normal transmission and reception with the gNB. UE 1104 can report the results of the R2D communication to the gNB, and the gNB can use this information to adjust the R2D communication gap pattern or perform other network management tasks.

[0245] Repeat: Repeat the R2D communication gaps according to the configured gap pattern. Based on the requirements of R2D communication, the gNB can adjust the gap pattern as needed.

[0246] This approach allows UE 1104 to communicate with A-IoT device 1106 without significantly affecting its communication with gNB. It also provides flexibility for UE 1104 and gNB to efficiently manage R2D communication even if the communication time is uncertain.

[0247] FIG14(B) is a timing diagram 1420 outlining the interaction between the UE 1104 and the gNB for R2D communication under a special type of measurement gap. FIG14(B) provides a high-level overview of the UE 1104, gNB, and A-IoT device 1106 for R2D communication under a special type of measurement gap. It covers the main steps from the UE 1104 requesting an R2D communication gap to the repetition of the R2D communication gap according to the configured pattern.

[0248] In a first aspect, the UE 1104 may include:

[0249] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0250] Receive measurement gaps configured through RRC signaling from the base station if the UE 1104 needs to communicate with the A-IoT device 1106 and may not be able to receive signals from the BS during this period.

[0251] Determine the activation time of the measurement gap, if the measurement gap is configured for R2D communication and the BS specifies the gap pattern, which includes the gap length and the gap period.

[0252] R2D communication is performed during a measurement gap if the UE 1104 activates the gap at a designated time and suspends normal transmission and reception with the BS.

[0253] If the UE 1104 resumes normal transmission and reception with the BS after the R2D communication gap, the result of the R2D communication is transmitted to the BS, and the BS can use this information to adjust the R2D communication gap pattern or perform other network management tasks.

[0254] In a second aspect, the UE 1104 may include:

[0255] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0256] A command to adjust the measurement gap pattern is received from the base station if the UE 1104 has reported the result of the R2D communication to the BS and the BS needs to efficiently manage the R2D communication even if the communication time is uncertain.

[0257] A new gap pattern of the measurement gaps is determined, if the BS can adjust the gap pattern as needed according to the requirements of the R2D communication, and the UE 1104 needs to follow the new gap pattern for further R2D communication.

[0258] R2D communication is performed according to the new gap pattern if the UE 1104 has determined the new gap pattern and the R2D communication gaps are repeated according to the configured gap pattern.

[0259] If the UE 1104 performs R2D communication according to the new gap pattern, the R2D communication result based on the new gap pattern is transmitted to the BS, and the BS can use this information to further adjust the R2D communication gap pattern or perform other network management tasks.

[0260] DL beam measurement

[0261] If the UE 1104 needs to estimate the angle of arrival (AoA) to determine the location of the A-IoT device, then beam management based on the uplink (UL) beam direction of the R2D link is indeed necessary. The following is its

[0262] Working principle:

[0263] Beam determination: UE 1104 forms multiple beams and uses different beams to send BRS to A-IoT device 1106. A-IoT device 1106 receives these signals and responds to UE 1104.

[0264] AoA estimation: UE 1104 estimates the AoA of the signal received from A-IoT device 1106. AoA estimation can be performed using techniques such as Multiple Signal Classification (MUSIC) or Estimation of Signal Parameters via Rotational Invariance Techniques (ESPRIT). The beam aligned with the estimated AoA is selected as the best beam for the R2D link.

[0265] Beam reporting: UE 1104 reports the best beam (i.e. the beam aligned with the estimated AoA) to the gNB. This report can be included in the regular CSI report.

[0266] Beam switching: Based on the CSI report, the gNB instructs the UE 1104 to switch to the reported R2D link beam. This is typically done using the beam indication in the uplink grant.

[0267] Beam tracking: The UE 1104 and gNB continuously track the channel status and AoA and switch to a different beam when necessary. This is especially important in a mobile environment because the relative positions of the UE 1104 and A-IoT device 1106 may change rapidly.

[0268] By using the UL beam direction of the R2D link, the UE 1104 can accurately estimate the AoA and therefore determine the location of the A-IoT device 1106. This can facilitate efficient beam management and communication between the UE 1104 and the A-IoT device 1106.

[0269] FIG14(C) is a timing diagram 1440 outlining the interaction between the UE 1104 and the gNB in ​​the context of downlink (DL) beam measurements for R2D communications. FIG14(C) provides a high-level overview of the interaction between the UE 1104, the gNB, and the A-IoT device 1106 in the context of DL beam measurements for R2D communications. It covers the main steps from the UE 1104 sending a BRS to the A-IoT device 1106, to continuously tracking the channel status and AoA, and switching to a different beam when necessary.

[0270] In a first aspect, a UE 1104 may include:

[0271] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0272] BRS is received from a base station using multiple beams if UE 1104 needs to estimate AoA to determine the location of A-IoT device 1106.

[0273] The AoA of the signal received from the A-IoT device 1106 is determined using a technique such as MUSIC or ESPRIT, and the beam that is aligned with the estimated AoA is selected as the best beam for the R2D link.

[0274] Beam switching is performed based on the CSI report if the gNB instructs the UE 1104 to switch to the reporting beam for the R2D link. This is typically done using the beam indication in the uplink grant.

[0275] If UE 1104 and gNB keep tracking the channel status and AoA, the best beam (i.e., the beam aligned with the estimated AoA) is transmitted to the BS and switched to a different beam if necessary.

[0276] In a second aspect, the UE 1104 may include:

[0277] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0278] A command to adjust the beam pattern is received from the base station if the UE 1104 has reported the result of the R2D communication to the BS and the BS needs to effectively manage the R2D communication even if the communication time is uncertain.

[0279] Determine a new beam pattern for the R2D link, if the BS can adjust the beam pattern according to the requirements of the R2D communication and the UE 1104 needs to follow the new beam pattern for further R2D communication.

[0280] If the UE 1104 has determined the new beam pattern, R2D communication is performed according to the new beam pattern, and the R2D communication is repeated according to the configured beam pattern.

[0281] If UE 1104 performs R2D communication according to the new beam pattern, the result of performing R2D communication according to the new beam pattern is transmitted to the BS, and the BS can use this information to further adjust the beam pattern of R2D communication or perform other network management tasks.

[0282] gNB requests and UE reports

[0283] In one scenario, if the gNB needs to query the electronic product code (EPC) result of the A-IoT device, the gNB may request the UE 1104 to perform the query. The following is a possible sequence of events:

[0284] gNB request: The gNB sends a request to the UE 1104 to query the EPC of a specific A-IoT device, such as the A-IoT device 1106. This request may be sent via a downlink control message.

[0285] UE Query: After receiving the request from the gNB, the UE 1104 sends a query command to the A-IoT device 1106. This command includes specific parameters so that the A-IoT device 1106 responds with its EPC.

[0286] A-IoT Response: The A-IoT device 1106 receives the query command from the UE 1104, decodes it, and responds with its EPC.

[0287] UE Reception and Reporting: UE 1104 receives the EPC from the A-IoT device 1106, decodes it, and sends a report back to the gNB. The report can be sent via an uplink control message and contains the EPC of the A-IoT device 1106.

[0288] gNB reception: The gNB receives the report from UE 1104, decodes it, and extracts the EPC of the A-IoT device 1106.

[0289] In order to reuse the current 5G NR signaling and channels in the communication between the gNB, UE 1104 and A-IoT device 1106, the following steps may be considered:

[0290] DCI: The gNB may use DCI to instruct the UE 1104 to perform specific tasks related to A-IoT communications. For example, the gNB may use DCI to send a request to the UE 1104 to query the EPC of a specific A-IoT device, such as the A-IoT device 1106. The DCI may be sent on the PDCCH.

[0291] UCI: After the UE 1104 performs a task (such as querying the EPC from the A-IoT device 1106), it can use UCI to report the results back to the gNB. The UCI may include the EPC or other relevant information of the A-IoT device 1106. If uplink data is also being sent, the UCI may be sent on the PUCCH or multiplexed on the PUSCH.

[0292] Physical channels: PUSCH and PDSCH can be used for data transmission between UE 1104 and gNB. UE 1104 can use these channels to relay data between gNB and A-IoT device 1106.

[0293] RRC signaling: The gNB and UE 1104 may use RRC signaling to establish and manage A-IoT communications. For example, the gNB may use RRC signaling to configure measurement gaps for UE 1104 to communicate with A-IoT device 1106.

[0294] By reusing current 5G NR signaling and channels, the communication between gNB, UE 1104, and A-IoT device 1106 can be integrated into the existing 5G NR framework. This can facilitate the deployment of A-IoT devices in 5G networks and enable efficient and reliable communication between these devices and the network.

[0295] Fig.15 is a timing diagram 1500 outlining the interaction between UE 1104 and gNB in ​​the context of querying the electronic product code (EPC) of an A-IoT device. Fig.15A high-level overview of the interaction between the UE 1104, gNB, and A-IoT device 1106 in the context of querying the EPC of the A-IoT device is provided. It covers the main steps from the gNB sending a request to the UE 1104 to query the EPC of the A-IoT device 1106 until the gNB receives the report from the UE 1104 and extracts the EPC of the A-IoT device 1106.

[0296] In a first aspect, the UE 1104 may include:

[0297] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0298] A request to query the electronic product code (EPC) of a specific A-IoT device, such as the A-IoT device 1106, is received from the base station via a downlink control message if the UE 1104 is in a scenario where the gNB needs to query the EPC result of the A-IoT device.

[0299] If UE 1104 receives a request from the gNB, it determines that the A-IoT device 1106 responds to specific parameters of its EPC and sends a query command to the A-IoT device 1106.

[0300] Perform the task of querying EPC from the A-IoT device 1106 if the UE 1104 receives a request from the gNB and uses DCI to perform specific tasks related to A-IoT communication.

[0301] If UE 1104 receives EPC from A-IoT device 1106, decodes it, and needs to report to gNB, a report including the EPC of A-IoT device 1106 is transmitted to BS via an uplink control message.

[0302] In a second aspect, the UE 1104 may include:

[0303] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0304] Receive a command from the base station to perform a specific task related to A-IoT communication using DCI if the UE 1104 is in a scenario where the gNB needs to query the EPC result of the A-IoT device.

[0305] If UE 1104 receives a command from the gNB, it determines that the A-IoT device 1106 responds to specific parameters of its EPC and needs to send a query command to the A-IoT device 1106.

[0306] If UE 1104 receives a command from the gNB, it performs the task of querying the EPC from the A-IoT device 1106 and performs specific tasks related to A-IoT communication using the UCI.

[0307] If UE 1104 receives EPC from A-IoT device 1106, decodes it, and needs to report back to gNB, it transmits a report to the base station via an uplink control message, which includes the EPC of A-IoT device 1106.

[0308] gNB controls the R2D link

[0309] The gNB may configure the A-IoT device 1106 using the R2D link over the Uu interface through a series of steps involving the UE 1104. The Uu interface is the air interface between the gNB and the UE 1104, while the R2D link is the communication link between the UE 1104 and the A-IoT device 1106. The following is a possible sequence of events:

[0310] gNB to UE command transmission: The gNB sends a command for the A-IoT device 1106 to the UE 1104. The command can be transmitted over the Uu interface using standard 5G NR signals and channels (e.g., PDCCH or PDSCH). The command includes the configuration parameters of the A-IoT device 1106.

[0311] R2D command relay: After receiving the command from the gNB, UE 1104 relays the command to the A-IoT device 1106 via the R2D link. The R2D link can use various modulation schemes, such as amplitude-shift keying (ASK) or frequency-shift keying (FSK), to transmit the command to the A-IoT device 1106.

[0312] IoT device configuration: The A-IoT device 1106 receives the command from the UE 1104, decodes it, and applies configuration parameters. The configuration parameters may include settings related to the operation of the A-IoT device, such as power management, data reporting intervals, and sensor calibration parameters.

[0313] IoT device to UE (D2R) confirmation transmission: Once the A-IoT device 1106 successfully applies the configuration parameters, it can send a confirmation message to the UE 1104 via the R2D link. This confirmation message indicates that the configuration has been successfully applied.

[0314] UE to gNB ACK relay: After receiving the ACK message from the A-IoT device 1106, the UE 1104 relays the ACK message back to the gNB via the Uu interface. This can be done via an uplink control message on a channel such as PUCCH or PUSCH.

[0315] gNB confirms reception: The gNB receives the confirmation message from UE 1104, decodes it, and confirms that the A-IoT device 1106 has been successfully configured.

[0316] This process allows the gNB to indirectly configure the A-IoT device 1106 through the Uu interface and R2D link using the UE 1104 as a relay. This is particularly useful in the case where the A-IoT device 1106 is a passive device with limited communication capabilities, and the UE 1104 acts as a communication bridge between the gNB and the A-IoT device 1106.

[0317] FIG16(A) is a timing diagram 1600 showing the interaction between the gNB, UE 1104, and A-IoT device 1106 during the configuration process of the gNB controlling the R2D link. It shows how commands and confirmations are relayed over the Uu interface and the R2D link, and how the A-IoT device 1106 applies the configuration parameters.

[0318] In a first aspect, the UE 1104 may include:

[0319] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0320] If UE 1104 acts as a communication bridge between the BS and the A-IoT device 1106, it receives a command for the A-IoT device 1106 from the base station through the Uu interface.

[0321] If the command is successfully received, the configuration parameters of the A-IoT device 1106 contained in the command are determined.

[0322] If the configuration parameters are successfully determined, command relay is performed to the A-IoT device 1106 via the R2D link.

[0323] If the A-IoT device 1106 successfully applies the configuration parameters and sends a confirmation message to the UE 1104, the confirmation message is transmitted back to the BS via the Uu interface.

[0324] In a second aspect, the UE 1104 may include:

[0325] one or more non-transitory computer-readable media having computer-executable instructions thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0326] If the UE 1104 is in a situation where the A-IoT device 1106 is a passive device and has limited communication capabilities, commands are received from the gNB using standard 5G NR signals and channels over the Uu interface.

[0327] If the command is for the A-IoT device 1106, a modulation scheme, such as amplitude shift keying (ASK) or frequency shift keying (FSK), is determined for transmitting the command to the A-IoT device 1106 via the R2D link.

[0328] If the command is successfully received from the gNB, command relay is performed to the A-IoT device 1106 via the R2D link using the determined modulation scheme.

[0329] If the A-IoT device 1106 successfully applies the configuration parameters and sends a confirmation message to the UE 1104, the confirmation message is transmitted back to the gNB via an uplink control message on a channel such as PUCCH or PUSCH through the Uu interface.

[0330] gNB controls the D2R link

[0331] FIG16(B) is a timing diagram 1620 showing the interaction between the gNB, UE 1104, and A-IoT device 1106 during the configuration process of the gNB controlling the D2R link.

[0332] The gNB may indirectly control the D2R link (the link between the UE 1104 and the A-IoT device 1106) by sending commands or requests to the UE 1104, which are then relayed over the D2R link to the A-IoT device 1106. Here is a possible sequence of events:

[0333] gNB to UE parameter request transmission: The gNB sends a parameter request for the A-IoT device 1106 to the UE 1104 over the Uu interface. The request can be transmitted using standard 5G NR signals and channels, such as PDCCH or PDSCH. The request includes specific parameters that the gNB wants to know from the A-IoT device 1106.

[0334] UE to A-IoT device parameter request relay: After receiving the parameter request from the gNB, the UE 1104 relays this request to the A-IoT device 1106 via the D2R link. The D2R link can use various modulation schemes, such as amplitude shift keying (ASK) or frequency shift keying (FSK), to transmit the request to the A-IoT device 1106.

[0335] A-IoT device parameter reporting: The A-IoT device 1106 receives the request from the UE 1104, retrieves the requested parameters, and sends these parameters back to the UE 1104 over the D2R link.

[0336] UE to gNB parameter reporting: The UE 1104, after receiving the parameters from the A-IoT device 1106, relays these parameters back to the gNB over the Uu interface. This can be transmitted via an uplink control message on the PUCCH or PUSCH.

[0337] gNB parameter reception: The gNB receives parameters from the UE 1104, decodes them, and uses them for further decision or control.

[0338] This process allows the gNB to use the UE 1104 as a relay to indirectly request and receive specific parameters from the A-IoT device 1106 through the Uu interface and the D2R link. This is particularly useful in scenarios where the A-IoT device 1106 is a passive device with limited communication capabilities and the UE 1104 acts as a communication bridge between the gNB and the A-IoT device 1106.

[0339] As shown in Figure 16(B), the gNB sends a parameter request to the UE 1104, which then relays the request to the A-IoT device 1106 via the D2R link. The A-IoT device 1106 retrieves the requested parameters and sends them back to the UE 1104, which then relays the parameters back to the gNB via the Uu interface. The gNB then uses these parameters for further decision making or control.

[0340] In a first aspect, a UE 1104 may include:

[0341] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0342] If UE 1104 acts as a communication bridge between the gNB and the A-IoT device 1106, it receives a parameter request for the A-IoT device 1106 from the gNB through the Uu interface.

[0343] If a parameter request is successfully received, the specific parameters included in the request are determined.

[0344] If specific parameters are determined, relaying of the parameter request to the A-IoT device 1106 is performed over the D2R link using an ASK or FSK modulation scheme.

[0345] If the A-IoT device 1106 sends parameters back to the UE 1104, the retrieved parameters are transmitted to the gNB over the Uu interface by using PUCCH or PUSCH.

[0346] In a second aspect, the UE 1104 may include:

[0347] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0348] If the A-IoT device 1106 has limited communication capabilities, a command for the A-IoT device 1106 is received from the gNB through the Uu interface by using a PDCCH or PDSCH channel.

[0349] If the command is successfully received, the command parameters for the A-IoT device 1106 are determined.

[0350] If the command parameters are determined, relaying of the command to the A-IoT device 1106 is performed over the D2R link using an ASK or FSK modulation scheme.

[0351] If the A-IoT device 1106 applies the command parameters and sends a confirmation message to the UE 1104, the confirmation message is transmitted back to the gNB through the Uu interface via an uplink control message on the PUCCH or PUSCH.

[0352] In a second aspect, the UE 1104 may include:

[0353] one or more non-transitory computer-readable media having computer-executable instructions embedded thereon, and at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to:

[0354] If the UE 1104 needs to estimate the AoA to determine the location of the A-IoT device 1106, the BRS is received from the base station by using multiple beams.

[0355] If the beam aligned with the estimated AoA is selected as the optimal beam for the R2D link, the AoA of the signal received from the A-IoT device 1106 is determined using a technique such as MUSIC or ESPRIT.

[0356] If the gNB instructs UE 1104 to switch to the reporting beam for the R2D link, beam switching is performed based on the CSI report. This is typically done using the beam indication in the uplink grant.

[0357] If UE 1104 and gNB keep tracking the channel status and AoA, the best beam (i.e., the beam aligned with the estimated AoA) is transmitted to the BS and switched to a different beam if necessary.

[0358] Fig.17 An example communication system 1700 is shown, which has an example communication device 1710 and an example network device 1720. The communication device 1710 and the network device 1720 can each perform various functions to implement the schemes, techniques, processes and methods described in the present invention, which are related to using on-demand reference signals in mobile communications for network energy saving, including the scenarios / schemes described above.

[0359] The communication device 1710 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 1710 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing device, such as a tablet, a laptop, or a notebook computer. The communication device 1710 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIoT device, such as a fixed or static device, a home device, a wired communication device, or a computing device. For example, the communication device 1710 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 1710 may be implemented in the form of one or more integrated-circuit (IC) chips, such as but not limited to 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 1710 may include Fig.17 The communication device 1710 may also include one or more other components not related to the solution proposed by the present invention (e.g., an internal power supply, a display device, and / or a user interface device). Therefore, for the sake of brevity, these components of the communication device 1710 are not shown in FIG. Fig.17 It is not shown in the figure and is not described below.

[0360] The network device 1720 may be part of a network device, which may be a network node, such as a satellite, a base station, a small base station, a router, or a gateway. For example, the network device 1720 may be implemented in an eNodeB in an LTE network, in a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or in a satellite or base station in a 6G network. Alternatively, the network device 1720 may be implemented in the form of one or more IC chips, such as but not limited to one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. The network device 1720 may include Fig.17 1720, such as processor 1722. Network device 1720 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, these components of network device 1720 are not shown in FIG. Fig.17 It is not shown in the figure and is not described below.

[0361] In one aspect, processor 1712 and processor 1722 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 though the singular term "a processor" may be used herein to refer to processor 1712 and processor 1722, in some embodiments, each processor 1712 and processor 1722 may include multiple processors, and in other embodiments, include a single processor. In another aspect, processor 1712 and processor 1722 can each be implemented in the form of hardware (and, optionally, firmware), including electronic components, such as and 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 memory resistors, and / or one or more variable capacitors, which can be configured and arranged in accordance with the present invention to achieve specific purposes. In other words, in at least some embodiments, each processor 1712 and processor 1722 is a special-purpose machine that is specially designed, arranged, and configured to perform specific tasks included in a device (e.g., represented by communication device 1710) and a network (e.g., represented by network device 1720), such as autonomous reliability enhancement according to various embodiments of the present invention.

[0362] In some embodiments, the communication device 1710 may further include a transceiver 1716 coupled to the processor 1712, capable of wirelessly sending and receiving data. In some embodiments, the communication device 1710 may further include a memory 1714 coupled to the processor 1712, capable of being accessed by the processor 1712 and storing data therein. In some embodiments, the network device 1720 may further include a transceiver 1726 coupled to the processor 1722, capable of wirelessly sending and receiving data. In some embodiments, the network device 1720 may further include a memory 1724 coupled to the processor 1722, capable of being accessed by the processor 1722 and storing data therein. Therefore, the communication device 1710 and the network device 1720 may perform wireless communication via the transceiver 1716 and the transceiver 1726, respectively. For better understanding, the following description of the operations, functions, and capabilities of the communication device 1710 and the network device 1720 is provided in a mobile communication environment, wherein the communication device 1710 is implemented as or serves as a communication device or UE, and the network device 1720 is implemented as or serves as a network node of a communication network.

[0363] 18(A) is a flow chart 1800 of the identification process of the reader and the A-IoT device. The process includes interactions between the gNB, the UE (e.g., UE 1104), and the A-IoT device (e.g., A-IoT device 1106).

[0364] At step 1802, a reader may broadcast a radio signal indicating a set of available time slots. The reader may be a UE 1104 or a gNB.

[0365] Then, at step 1804 , the reader, such as UE 1104 , may send an acknowledgement (ACK) signal containing the decoded sequence to the A-IoT device 1106 .

[0366] Finally, the reader may receive an identifier from the A-IoT device at step 1806. In some embodiments, the identifier may be a reply from the A-IoT device 1106 when the decoded sequence matches a selected sequence, which is a random sequence in response to a radio signal in a time slot randomly selected from a set of available time slots.

[0367] In some embodiments, when the reader is UE 1104, the method may further include: forwarding the identifier to a base station, such as a gNB. In addition, in some embodiments, the method may further include: forwarding the random sequence to the base station; and receiving an ACK signal from the base station. In some embodiments, the decoded sequence may be obtained by decoding the random sequence by the base station. In some embodiments, UE 1104 may also receive a control signal for specifying a control parameter from the base station during communication with the A-IoT device 1106. In some embodiments, the control parameter may include a set of available time slots.

[0368] In certain embodiments, the validity of the signal between the reader and the A-IoT device may be checked by using a CRC.

[0369] In some embodiments, the radio signal may include protocol control information (PCI) for regulating the timing and format of data transmission between the reader (eg, UE 1104 ) and the A-IoT device 1106 .

[0370] In some embodiments, the random sequence may be a modulation sequence using FM0 modulation and preceded by a preamble sequence.

[0371] In some embodiments, the R2D link from the reader (e.g., UE 1104) to the A-IoT device 1106 may employ a modulation scheme including amplitude-shift keying (ASK) or on-off keying (OOK). For example, ASK may include double-sideband amplitude-shift keying (DSB-ASK), single-sideband amplitude-shift keying (SSB-ASK), and partial response amplitude-shift keying (PR-ASK).

[0372] In some embodiments, the first R2D preamble sequence may be used for initial transmission between the UE 1104 and the A-IoT device 1106 to enable the A-IoT device 1106 to synchronize with the UE 1104, and the second R2D preamble sequence may be used to start signal transmission after synchronization between the UE 1104 and the A-IoT device 1106. The second R2D preamble sequence may be shorter than the first R2D preamble sequence.

[0373] In some embodiments, a reader (eg, UE 1104 ) may employ Manchester coding and pulse interval encoding (PIE) for R2D communication from UE 1104 to A-IoT device 1106 .

[0374] FIG. 18(B) is another flow chart 1850 regarding the identification process of the reader and the A-IoT device.

[0375] At step 1852, an A-IoT device, such as A-IoT device 1106, may receive a radio signal indicating a set of available time slots from a reader. The reader may be a UE, such as UE 1104, or a gNB.

[0376] Then, at step 1854, the A-IoT device 1106 may transmit a random sequence of responses to the radio signal in a time slot randomly selected from the set of available time slots.

[0377] Subsequently, at step 1856, the A-IoT device 1106 may receive an acknowledgment (ACK) signal including the decoded sequence.

[0378] Finally, at step 1856 , when the decoded sequence matches the random sequence, the A-IoT device 1106 may send an identifier.

[0379] In certain embodiments, the validity of the signal between the reader (eg, UE 1104) and the A-IoT device 1106 may be checked by using a CRC.

[0380] In certain embodiments, the radio signal may include protocol control information (PCI) for regulating the timing and format of data transmission between the reader and the A-IoT device.

[0381] In some embodiments, the random sequence may be a modulation sequence using FM0 modulation and preceded by a preamble sequence.

[0382] In certain embodiments, a device-to-reader (D2R) link from an A-IoT device 1106 to a reader (eg, UE 1104) may employ a modulation scheme including amplitude-shift keying (ASK) or phase-shift keying (PSK).

[0383] In some embodiments, the A-IoT device 1106 may reply to a command from the reader by using an immediate reply, a delayed reply, or a processing reply.

[0384] In some embodiments, the A-IoT device 1106 may use an extended preamble sequence for a delayed reply or an in-process reply.

[0385] In some embodiments, the A-IoT device 1106 may use backscatter modulation to change the reflection coefficient of the antenna to transmit data.

[0386] In some embodiments, the A-IoT device 1106 may select the modulation format, data encoding, and data rate based on the reader's settings.

[0387] It is understood that the specific order or hierarchy of blocks in the process / flowchart of the present invention is an example of an exemplary method. It should therefore be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged based on design preferences, and some blocks can be further combined or omitted. The attached method claims the elements presented by the various blocks in an exemplary order, but this does not mean that the present invention is limited to the specific order or hierarchy presented.

[0388] The previous description is provided to enable those skilled in the art to realize the various aspects described in the present invention. Those skilled in the art can easily make various modifications to these aspects, and can apply the general principles defined in the present invention to other aspects. Therefore, the claims are not intended to be limited to the aspects shown in the present invention, but should be given the full scope consistent with the claim language description. Wherein, unless otherwise specified, it is not intended to mean "one and only one" when referring to the singular element, but to mean "one or more". The word "exemplary" is used in the present invention to refer to "used as an example, example or illustration". Any aspect of the present invention described as "exemplary" is not necessarily understood to be preferred or advantageous over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may include only A, only B, only C, A and B, A and C, B and C, or A, B, and C, any of which may include one or more of A, B, or C. All structural and functional equivalents of the elements of the various aspects described in the present invention that are known or will become known to those skilled in the art may be expressly included in the present invention by reference and are intended to be covered by the claims. In addition, the content disclosed in the present invention is not intended to be donated to the public, regardless of whether such disclosure is explicitly stated in the claims. The words "module," "mechanism," "element," "device," etc. may not be substitutes for the word "means." Thus, unless an element in a claim is explicitly stated using the phrase "means for...", the element should not be understood as a functional limitation (means plus function).

Claims

1. A method for wireless communication, performed by a reader, the method comprising: broadcasting a radio signal indicating a set of available time slots; Sending a confirmation signal containing the decoded sequence to the A-IoT device; as well as An identifier is received from the A-IoT device, wherein the identifier is a reply of the A-IoT device when the decoded sequence matches a selected sequence, wherein the selected sequence is a random sequence that responds to the radio signal in a time slot randomly selected from the set of available time slots.

2. The method for wireless communication according to claim 1, wherein: The reader comprises a user equipment or a gNB.

3. The method for wireless communication according to claim 2, wherein: When the reader is the user equipment, the method further comprises: The identifier is forwarded to the base station.

4. The method for wireless communication according to claim 3, wherein: Further including: forwarding the random sequence to the base station; and A confirmation signal is received from the base station, wherein the decoded sequence is obtained by the base station decoding the random sequence.

5. The method for wireless communication according to claim 3, wherein: During the communication process between the user equipment and the A-IoT device, the user equipment receives a control signal for specifying a control parameter from the base station.

6. The method for wireless communication according to claim 5, wherein: The control parameters include the set of available time slots.

7. The method for wireless communication according to claim 1, wherein: The signal validity between the reader and the A-IoT device is checked by using a cyclic redundancy check.

8. The method for wireless communication according to claim 1, wherein: The radio signal includes protocol control information for regulating the timing and format of data transmission between the reader and the A-IoT device.

9. The method for wireless communication according to claim 1, wherein: The random sequence is a modulation sequence using FM0 modulation and is preceded by a preamble sequence.

10. The method for wireless communication according to claim 2, wherein: The modulation schemes employed by the R2D link from the reader to the A-IoT device include amplitude keying or on-off keying.

11. The method for wireless communication according to claim 10, wherein: The amplitude keying includes double sideband amplitude keying, single sideband amplitude keying and partial response amplitude keying.

12. The method for wireless communication according to claim 10, wherein: The first R2D preamble sequence is used for the initial transmission between the user equipment and the A-IoT device so that the A-IoT device can be synchronized with the user equipment, and the second R2D preamble sequence is used to start the signal transmission after synchronization between the user equipment and the A-IoT device, and the second R2D preamble sequence is shorter than the first R2D preamble sequence.

13. The method for wireless communication according to claim 1, wherein: The reader adopts Manchester coding and pulse interval coding for R2D communication from the reader to the A-IoT device.

14. A method for wireless communication, performed by an A-IoT device, the method comprising: receiving a radio signal from a reader indicating a set of available time slots; transmitting a random sequence in response to the radio signal in a time slot randomly selected from the set of available time slots; receiving an acknowledgment signal including the decoded sequence; and An identifier is sent when the decoded sequence matches the random sequence.

15. The method for wireless communication according to claim 14, wherein: The signal validity between the reader and the A-IoT device is checked by using a cyclic redundancy check.

16. The method for wireless communication according to claim 14, wherein: The radio signal includes protocol control information for regulating the timing and format of data transmission between the reader and the A-IoT device.

17. The method for wireless communication according to claim 14, wherein: The random sequence is a modulation sequence using FM0 modulation and is preceded by a preamble sequence.

18. The method for wireless communication according to claim 14, wherein: The modulation scheme adopted by the D2R link from the A-IoT device to the reader includes amplitude keying or phase keying.

19. The method for wireless communication according to claim 14, wherein: The A-IoT device replies to the command from the reader by using an immediate reply, a delayed reply, or a processing reply, wherein the A-IoT device uses an extended preamble sequence for the delayed reply or the processing reply.

20. The method for wireless communication according to claim 14, wherein: The A-IoT device uses backscatter modulation to change the reflection coefficient of the antenna to transmit data, wherein the A-IoT device selects the modulation format, data encoding and data rate according to the settings of the reader.

21. A device for wireless communication, comprising: A processor, the processor being configured to execute the method for wireless communication according to any one of claims 1 to 20.

22. A memory storing program instructions, wherein when the program instructions are executed by a processor, the processor executes the method for wireless communication according to any one of claims 1 to 20.

Images