A-iot communication method, terminal, and network side device

By having the terminal report capability information to the network-side device and the network-side device configure A-IoT communication parameters, the problem of unstable communication between the terminal and A-IoT devices is solved, achieving stable and reliable A-IoT communication that is adaptable to various deployment scenarios.

WO2026237858A1PCT designated stage Publication Date: 2026-11-19VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/095961
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-13
Filing Date
2026-05-09
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In Ambient Internet of Things (A-IoT) communication, establishing stable and reliable communication between terminals and A-IoT devices faces challenges. In particular, the problem of how terminals can effectively communicate with A-IoT devices and network-side devices has not been effectively solved in various deployment scenarios.

Method used

The terminal reports its first information to the network-side device using terminal capability information or terminal auxiliary information. The network-side device then configures the A-IoT communication parameters accordingly to ensure stable communication between the terminal and the A-IoT device.

Benefits of technology

It achieves stable and reliable communication between the terminal and A-IoT devices, improves communication efficiency and reliability, and adapts to the needs of various deployment scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026095961_19112026_PF_FP_ABST
    Figure CN2026095961_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and discloses an A-IoT communication method, a terminal, and a network side device. The A-IoT communication method of embodiments of the present application comprises: a terminal reports first information to a network side device by means of terminal capability information or terminal assistance information, the first information being information related to A-IoT communication.
Need to check novelty before this filing date? Find Prior Art

Description

A-IoT communication methods, terminals and network-side devices

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510613946.3, filed in China on May 13, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to an A-IoT communication method, terminal, and network-side device. Background Technology

[0004] In related technologies, Ambient-Internet of Things (A-IoT) communication typically involves network-side devices sending queries, commands, and access instructions to communicate with A-IoT devices. However, with the continuous expansion of application scenarios, to adapt to more business needs, there may be scenarios where the terminal acts as an intermediary node to communicate with both A-IoT devices and network-side devices. Therefore, how to establish stable and reliable A-IoT communication between the terminal and A-IoT devices is an urgent problem to be solved. Summary of the Invention

[0005] This application provides an A-IoT communication method, a terminal, and a network-side device, which can ensure that a stable and reliable A-IoT communication is established between the terminal and the A-IoT device.

[0006] In a first aspect, an A-IoT communication method is provided, executed by a terminal, the method comprising: the terminal reporting first information to a network-side device through terminal capability information or terminal auxiliary information, the first information being information related to A-IoT communication.

[0007] Secondly, an A-IoT communication method is provided, executed by a network-side device. The method includes: the network-side device receiving terminal capability information or terminal auxiliary information from a terminal, wherein the terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication.

[0008] Thirdly, an A-IoT communication device is provided, comprising: a transmitting module, which is used to report first information to a network-side device through terminal capability information or terminal auxiliary information, the first information being information related to A-IoT communication.

[0009] Fourthly, an A-IoT communication device is provided, comprising: a receiving module, the receiving module being configured to receive terminal capability information or terminal auxiliary information from a terminal, the terminal capability information or terminal auxiliary information carrying first information, the first information being information related to A-IoT communication.

[0010] Fifthly, an A-IoT communication device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0011] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0012] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to report first information to a network-side device through terminal capability information or terminal auxiliary information, the first information being information related to A-IoT communication.

[0013] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0014] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive terminal capability information or terminal auxiliary information from a terminal, the terminal capability information or terminal auxiliary information carrying first information, the first information being information related to A-IoT communication.

[0015] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0016] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0017] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0018] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0019] In this embodiment, the terminal reports first information to the network-side device through terminal capability information or terminal auxiliary information. This first information is related to A-IoT communication. Thus, the terminal provides the network-side device with this first information related to A-IoT communication, enabling the network-side device to refer to the acquired information and appropriately configure the terminal's A-IoT communication parameters. This allows the terminal to use these A-IoT communication parameters to communicate with A-IoT devices. Attached Figure Description

[0020] Figure 1 is a schematic diagram of a communication system architecture between a network-side device and an A-IoT device provided in an embodiment of this application;

[0021] Figure 2 is a schematic diagram of a communication system architecture between a network-side device, an intermediate node, and an A-IoT device provided in an embodiment of this application.

[0022] Figure 3 is a flowchart illustrating an inventory / command service in A-IoT communication according to an embodiment of this application;

[0023] Figure 4 is a schematic diagram of a possible communication system architecture provided in an embodiment of this application;

[0024] Figure 5 is a flowchart illustrating an A-IoT communication method provided in an embodiment of this application;

[0025] Figure 6 is a schematic diagram of the interaction between a terminal, a network-side device, and an A-IoT device provided in an embodiment of this application;

[0026] Figure 7 is a schematic diagram of the structure of an A-IoT communication device provided in an embodiment of this application;

[0027] Figure 8 is a schematic diagram of the structure of an A-IoT communication device provided in an embodiment of this application;

[0028] Figure 9 is a schematic diagram of the structure of an A-IoT communication device provided in an embodiment of this application;

[0029] Figure 10 is a schematic diagram of the structure of an A-IoT communication device provided in an embodiment of this application;

[0030] Figure 11 is a schematic diagram of the structure of an A-IoT communication device provided in an embodiment of this application;

[0031] Figure 12 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0032] Figure 13 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0033] Figure 14 is a schematic diagram of the hardware structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0035] The following explains the technologies involved in the embodiments of this application:

[0036] 1) The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0037] 2) Ambient-Internet of Things (A-IoT): This refers to an intelligent system that uses Internet of Things (IoT) technology to sense, monitor, analyze, and manage environmental data in real time to support environmental protection, resource management, and sustainable ecological development. Its core objective is to improve environmental monitoring efficiency, optimize resource utilization, and provide data-driven solutions for addressing climate change and pollution control by connecting the physical environment with the digital world.

[0038] 3) Reader-to-Device (R2D) Messages

[0039] 4) A-IoT Device-to-Reader (D2R) Messages

[0040] 5) Reader or Reader-to-Writer

[0041] It should be noted that, in the embodiments of this application, the reader can be a network-side device or a terminal.

[0042] 6) A-IoT devices,

[0043] 7) Physical reader to device channel (PRDCH)

[0044] For example, a channel carrying R2D transmission messages.

[0045] 8) Physical device to reader channel (PDRCH), for example, a channel carrying D2R transmission messages.

[0046] 9) A-IoT device types:

[0047] In this application embodiment, the device can be an Internet of Things (IoT) device, such as an Ambient IoT (A-IoT) device. The A-IoT device can be characterized based on its energy storage capacity and its ability to generate and transmit radio frequency signals. A-IoT devices include the following types:

[0048] Device 1: No energy storage, no independent signal generation / amplification, i.e., backscatter transmission.

[0049] Device 2a: It has energy storage but no independent signal generation, i.e., backscatter transmission. The use of the stored energy may include amplification of the reflected signal.

[0050] Device 2b: It has energy storage and independent signal generation, i.e., an active radio frequency component for transmission.

[0051] For example, different devices may have the same or different energy storage capabilities, and the energy storage capability of a device also affects the transmission quality of the device. Generally, devices with higher energy storage capabilities also mean higher receiving sensitivity or higher transmitting power, which can better guarantee the reliability of the receiving or transmitting link.

[0052] A-IoT can be deployed in various scenarios, and two of them are introduced below.

[0053] As shown in Topology 1 of Figure 1, in this scenario, A-IoT base stations (BS) and A-IoT devices communicate directly to transmit A-IoT data and signaling. The base station sending A-IoT R2D transmissions (also known as R2D signals) and the base station receiving A-IoT D2R transmission signals can be the same or different.

[0054] As shown in Topology 2 of Figure 2, in this scenario, the A-IoT BS communicates with A-IoT devices through intermediate nodes. These intermediate nodes can be terminals, repeaters, relays, or Integrated Access and Backhaul (IAB) nodes. The BS can control the intermediate nodes via air interface signaling or other interfaces; for example, the BS can control the terminals through the NR Uu air interface.

[0055] 10) The main data in A-IoT communication includes:

[0056] 1. Device-originated (DO): In a communication system, the data transmission is initiated by an A-IoT device (such as sensors, smartphones, industrial equipment, etc.), rather than a network-side device (such as a base station or server). This type of communication is typically used for devices to proactively report data, trigger control commands, or request services.

[0057] 2. Device-terminated (DT): In a communication system, the data transmission is terminated by an A-IoT device (such as a sensor, smartphone, or industrial equipment). This means the A-IoT device completes the communication process as either a receiver or a responder. This type of communication is typically used for A-IoT devices to receive commands, download configuration parameters, or respond to requests from network-side devices.

[0058] For example, DO and DT data indicate that the data stream originates from or is transmitted to an A-IoT device (similar to a Radio Frequency Identification (RFID) tag). For a data stream originating from an A-IoT device, i.e., DO data,

[0059] It can also be classified into the following two types:

[0060] Device-originated access (DOA) means that the device autonomously initiates data transmission. For example, it connects a large number of various sensors, which collect and proactively report information about the environment, the device, and the organism when necessary.

[0061] Device-originated–device-terminated triggered (DO-DTT) refers to a data transfer service initiated by a device after data termination. Examples include asset identification, status reporting, and tracking, all of which involve downlink-triggered reporting. The reader collects data from the tag by triggering an inventory process. Since the data is generated or initiated within the A-IoT device, this service should be considered as a DO service initiated by the tag, triggered by a command sent by the reader.

[0062] 11) A-IoT communication service types include: inventory and command.

[0063] In some embodiments, A-IoT command types include inventory and commands.

[0064] Inventory is the most basic and important business of A-IoT, which enables A-IoT servers to learn about one or more known or unknown A-IoT devices within the reader's coverage area through the 3rd Generation Partnership Project (3GPP) network.

[0065] After learning that an A-IoT device has been identified by the network, the A-IoT server may be able to issue commands to the device via the network, such as those shown in Table 1 below:

[0066] Table 1

[0067] 12) In some embodiments, the general process of inventory / command services in A-IoT communication is shown in Figure 3, including the following steps A to C:

[0068] Step A, A-IoT paging:

[0069] For example, the above A-IoT paging is: the reader sends an A-IoT paging message to the device.

[0070] Step B, D2R data transmission:

[0071] Specifically, this includes D2R data transmission, and may also include the A-IoT random access procedure.

[0072] Step C, Data Transmission:

[0073] It can include R2D data transmission and D2R data transmission.

[0074] The inventory-only process includes step A and step B; the inventory and command process includes step A, step B, and step C.

[0075] 13) Table 2 below includes T chip T b The relationship between R and T can refer to the fact that a set of interrelated Ts can be identified in the table. chip T b The possible values ​​of R are shown in Table 2 below:

[0076] Table 2

[0077] In Table 2, T chip The duration or length of a D2R chip refers to T. chip T represents the duration or length of a D2R chip. chip The duration or length of a D2R bit refers to T. chip This indicates the duration or length of the D2R bit. T b The duration or length of a bit refers to T. b R represents the duration or length of a bit. R can also represent the number of times the codeword is repeated within the duration or length of an information bit, i.e., the codeword is repeated R times within the duration of an information bit.

[0078] It should be noted that Table 2 above may include multiple sets of relationships between Tb, Tchip, and R.

[0079] 14) D2R small frequency shift

[0080] The AIoT system supports multiple devices to perform frequency division multiplexing (FDM) D2R transmission, which can be performed on different frequency domain resources with a small frequency offset.

[0081] The D2R small frequency offset uses Manchester line codes and is implemented by repeating codewords (corresponding to one information bit) within a time duration Tb. Each Manchester codeword is repeated a number of times R. Where: R = Tb / (2 × chip length); therefore, the value of the small frequency offset (in Hz) can be expressed as: R / Tb = 1 / (2 × chip length).

[0082] 15) The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result based on the judgment result.

[0083] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0084] Figure 4 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11, a network-side device 12, and an A-IoT device. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0085] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0086] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0087] The A-IoT communication method, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0088] The execution subject of the A-IoT communication method provided in this application embodiment can be an A-IoT communication device. Exemplarily, the A-IoT communication device can be an electronic device, or a functional component or entity within that electronic device. The electronic device in this application embodiment can be a terminal; the following will use a terminal as the execution subject as an example to executor the A-IoT communication method provided in this application embodiment.

[0089] Figure 5 is a flowchart illustrating the A-IoT communication method provided in some embodiments of this application. As shown in Figure 5, the A-IoT communication method provided in some embodiments of this application may include the following step 201.

[0090] Step 201: The terminal reports the first information to the network-side device through terminal capability information or terminal auxiliary information.

[0091] In some embodiments of this application, the terminal described above acts as a reader or intermediate node in A-IoT communication, receiving, processing, or forwarding D2R information sent by A-IoT devices.

[0092] In some embodiments of this application, the aforementioned first information is information related to A-IoT communication.

[0093] In some embodiments of this application, the first information described above is used for communication between the terminal and the A-IoT device.

[0094] In some embodiments of this application, the aforementioned first information is information reported or recommended by the terminal to the network-side device.

[0095] Optionally, the terminal reports the first information to the network-side device through the first reporting method.

[0096] Optionally, the first reporting method mentioned above includes at least one of the following: terminal capability information and terminal auxiliary information.

[0097] In some embodiments of this application, the first information mentioned above includes at least one of the following:

[0098] Information 1: The value of M in the On-Off Keying (OOK) waveform.

[0099] For example, M above represents the number of OOK chips contained in an Orthogonal Frequency Division Multiplex (OFDM) symbol.

[0100] Information 2: The minimum number of resource blocks (RBs) corresponding to each M value.

[0101] Regarding information 1 and information 2:

[0102] Optionally, the above information 1 and information 2 can be related information transmitted in R2D.

[0103] For example, in R2D transmission, the M value in the OOK-4 waveform represents the number of OOK chips transmitted within a single OFDM symbol. Each chip corresponds to the time granularity of the "ON" or "OFF" state of the OOK symbol, and this value directly determines the correlation between transmission rate, symbol duration, and reception performance.

[0104] For example, in OOK-4 modulation, each information bit is converted into a sequence of multiple chips via OOK. For instance, Manchester coding might map "1" to "ON-OFF" and "0" to "OFF-ON". Each chip is the smallest unit of time in the modulation process, and its duration is determined by dividing the total time-domain resources of the OFDM symbol by the value of M.

[0105] For example, the physical meaning of the above M value is: when M=4, it means that a single OFDM symbol contains 4 chips. Therefore, the M value is strongly correlated with the OFDM symbol structure. A high M value compresses the duration of a single chip and increases the data rate, but may increase the risk of inter-symbol interference.

[0106] For example, the M value mentioned above determines the R2D transmission rate. A larger M value requires a larger bandwidth to ensure that R2D can achieve the corresponding transmission rate, while also ensuring that the ON / OFF waveform is relatively ideal and the detection performance is good.

[0107] For example, the mapping relationship between the above M value and the minimum number of transmission RBs is as follows:

[0108] It is understandable that when M is 1, the minimum number of transmission RBs is 1; when M is 2, the minimum number of transmission RBs is 1; when M is 4, the minimum number of transmission RBs is 1, ..., when M is 32, the minimum number of transmission RBs is 4.

[0109] It should be noted that 3GPP currently does not standardize the specific generation process of R2D OOK signals, i.e., generating OOK-4 with specific M values ​​based on a reader. Whether each M value can generate a waveform that meets the corresponding OOK waveform specifications depends on the reader's capabilities and also affects the transmission rate. Generally speaking, the larger the M value, the more difficult it is to generate a waveform that meets the specifications.

[0110] Optionally, when the terminal acts as a reader, the R2D resources for AIoT communication are configured by the network-side device. The terminal reports Information 1 and Information 2 to the network-side device, which can then determine the time and bandwidth resources allocated to the terminal based on this information.

[0111] For example, the maximum supported M value of 16 and the maximum supported M value of 24 will affect the performance of a given data payload.

[0112] Given the R2D transmission time (size), the terminal reports Information 1 and Information 2 to the network-side device, which allows the network-side device to reasonably configure the terminal as a reader for AIoT transmission time resources. The data payload size mentioned above can be protocol-defined, pre-configured by the network-side device, or indicated by the network-side device.

[0113] On the other hand, given a specific M value, for example, M=24, some terminals may be able to achieve the waveform specifications using 3 RBs, while others may require 4 RBs. The terminal reports Information 1 and Information 2 to the network-side device, enabling the network-side device to correctly configure the frequency domain resources for R2D transmission.

[0114] Information 3: Bit length of D2R transmission.

[0115] Information 4: Bit duration Tb of D2R transmission.

[0116] In one embodiment, information 3 and information 4 are equivalent.

[0117] For example, if the bit length and / or bit duration Tb of the aforementioned D2R transmission are large, the entire D2R transmission time will be long given transmission parameters such as payload size. Since the terminal's service requires data transmission with network-side devices, such as base stations, it may not allow for prolonged AIoT transmissions. Therefore, the terminal may not be able to support a large Tb. Thus, providing the aforementioned bit length and / or bit duration Tb of the D2R transmission as a capability to network-side devices allows them to configure D2R transmission parameters appropriately, avoiding negative impacts on the terminal's data service transmission.

[0118] For example, if the bit length and / or bit duration Tb of the aforementioned D2R transmission are small, the D2R transmission bandwidth is wide, resulting in a higher D2R transmission rate. This requires the terminal to employ additional complexity for high-data-rate demodulation. Therefore, by providing the aforementioned bit length and / or bit duration Tb of the D2R transmission as a capability to the network-side device, it can ensure that the network-side device correctly configures the D2R transmission parameters and resources, or selects a suitable terminal for higher-rate D2R data transmission.

[0119] Information 5: Chip length or chip duration Tchip.

[0120] For example, if the D2R chip length is long, the D2R spectrum is closer to the carrier frequency, which can be understood as a small frequency offset. In this case, the terminal acting as a reader needs strong hardware capabilities to successfully demodulate the D2R transmission. The terminal acting as a reader can report this chip length capability to the network-side device to avoid the network-side device configuring too low a D2R transmission bandwidth or too close to the carrier frequency, causing the terminal acting as a reader to be unable to demodulate.

[0121] For example, if the chip length of D2R is short, it generally means that the data transmission rate is high. The terminal, as a reader, can report the chip length capability to the network-side device, which can ensure that the network-side device correctly configures the D2R transmission parameters and resources, or selects a suitable terminal for higher-rate D2R data transmission.

[0122] It should be noted that if the chip length is short, the terminal needs a high sampling rate and good synchronization capability between the preamble and the intermediate preamble in order to accurately sample the short chip, and also needs additional terminal reporting capabilities.

[0123] Information 6: Minimum frequency offset for D2R transmission.

[0124] Message 7: Maximum frequency offset of D2R transmission.

[0125] For example, the terminal, acting as a reader, can report the minimum frequency offset of the D2R transmission to the network-side device to prevent the network-side device from configuring too low a D2R transmission bandwidth or being too close to the carrier frequency, which would cause the terminal, acting as a reader, to be unable to demodulate.

[0126] For example, the terminal, acting as a reader, can provide the network-side device with the maximum frequency offset capability of the D2R transmission, which can ensure that the network-side device correctly configures the D2R transmission parameters and resources, or selects a suitable terminal for higher-rate D2R data transmission.

[0127] Information 8: The number of codeword repetitions, R, in Manchester encoding;

[0128] Optionally, the number of repetitions R of the codeword in the Manchester encoding above can be a maximum value, i.e., the maximum number of repetitions, or a minimum value, i.e., the minimum number of repetitions.

[0129] For example, the R value mentioned above is the number of times the codeword is repeated within the same duration corresponding to one information bit.

[0130] For example, the terminal, acting as a reader, can provide the network-side device with the minimum R value, which can ensure that the network-side device correctly configures the D2R transmission parameters and resources, or selects a suitable terminal for higher-rate D2R data transmission.

[0131] For example, the terminal, acting as a reader, can report the maximum value of the R value to the network-side device to avoid the network-side device being configured with too low a D2R transmission bandwidth or too close to the carrier frequency, which would prevent the terminal, acting as a reader, from being unable to demodulate.

[0132] For example, the above R value can be expressed as the following formula (1): R = Tb / (2 * chip length) (1)

[0133] Message 9: The length or number of preamble sequences transmitted in D2R.

[0134] Message 10: The length or number of intermediate sequences transmitted in D2R.

[0135] For example, the number of leading or intermediate sequences can be 7 or 31, etc.

[0136] Message 11: Whether forward error correction (FEC) is supported.

[0137] It should be noted that FEC is an error control technology implemented through redundancy coding, which can automatically detect and correct errors during data transmission without relying on feedback from the receiver (such as retransmission requests).

[0138] Optionally, when the first information includes the aforementioned information 11, it is used to inform the network-side device terminal whether it supports FEC included in D2R transmission.

[0139] Information 12: Number of code block-level repetitions in D2R transmission.

[0140] It should be noted that the above-mentioned code block level repetition involves dividing the data into multiple code blocks, each of which is independently encoded or repeatedly transmitted to improve reliability or adapt to channel conditions.

[0141] Optionally, the above information 12 indicates the number of times each code block is repeatedly transmitted in the D2R transmission.

[0142] Message 13: Number of bit-level repetitions in D2R transmission.

[0143] It should be noted that the above-mentioned bit-level repetition refers to the repeated transmission of a single bit or a group of bits at the physical layer or data link layer to improve transmission reliability or combat channel interference.

[0144] Optionally, the above information 13 indicates the number of times each bit is repeated in the D2R transmission.

[0145] For example, bit level type 1: after adding a cyclic redundancy check (CRC) to the information bits, each bit is repeated according to the number of bit level repetitions.

[0146] For example, Bit level type 2: After adding CRC and FEC to the information bits, each bit is repeated according to the number of bit-level repetitions.

[0147] Information 14: The number of frequency division multiplexing D2R transmission resources.

[0148] For example, information 14 above indicates that the terminal supports less than or equal to four frequency division multiplexed D2R transmission resources.

[0149] Information 15: Frequency division multiplexing with small frequency offset combination.

[0150] Optionally, the frequency division multiplexing of the above-mentioned D2R transmission is achieved through different combinations of frequency offsets.

[0151] For example, the terminal supports combinations such as R = {1,4,8}, R = {2,4,8}, and R = {2,4,6}, depending on its capabilities. The key difference between {2,4,8} and {2,4,6} is that the latter is affected by the third harmonic, while the former consists entirely of integer powers of 2 and does not have this effect. Therefore, different combinations can indicate whether the terminal can handle the third harmonic effect. The difference between {1,4,8} and {2,4,8} is whether sufficient spacing needs to be provided between different small frequency shifts (SFS).

[0152] Information 16: Frequency division multiplexing small frequency offset mapping relationship.

[0153] Optionally, the frequency division multiplexing small frequency offset mapping relationship mentioned above includes at least one of the following: the mapping relationship between Tchip and R, and the mapping relationship between the set of values ​​of Tchip and R. For example, a Tchip may have a corresponding specific value of R.

[0154] Information 17: Transmission power of continuous wave (CW).

[0155] For example, when the terminal acts as a reader, the CW transmission power affects the D2R transmission coverage distance. Because the peak-to-average power ratio (PAPR) of CW transmission is relatively low, it is possible to transmit at higher power to improve D2R transmission coverage. After the terminal, acting as a reader, reports its CW transmission power capability to the network-side equipment, the network-side equipment can select a suitable UE reader to complete the corresponding inventory task.

[0156] For example, the information 17 above could include: 23dBm or 26dBm.

[0157] Information 18: Phase noise in CW transmission.

[0158] For example, when the terminal acts as a reader, the phase noise of CW transmission can severely affect the performance of D2R, especially when Tc is large or the frequency offset is small.

[0159] For example, if the phase noise of CW transmission is low, such as a terminal with a CW transmission phase noise capability of -120dBm at 100kHz acting as a reader, it can demodulate D2R transmissions with a frequency offset within 15kHz; while a terminal with a CW transmission phase noise capability of -90dBm at 100kHz acting as a reader can demodulate D2R transmissions with a frequency offset greater than 15kHz. The terminal reporting its CW transmission phase noise capability to the network-side device can help the network-side device correctly configure the resource allocation parameters for the terminal's D2R transmission.

[0160] For example, the terminal reports -x dBm at 100kHz or -y dBm at 100kHz.

[0161] Information 19: The number of time-domain resources used for D2R transmission in contention-based random access.

[0162] For example, the D2R mentioned above is msg 1. One time-domain resource is used to carry one Msg 1 transmission.

[0163] Information 20: D2R transmission uses either coherent or incoherent detection.

[0164] Optionally, for terminals with coherent detection capabilities, network-side devices can configure appropriate intermediate preamble resources for the terminal's D2R; while for terminals that only support non-coherent detection capabilities, network-side devices can reduce the configuration of preamble resources.

[0165] For example, the terminal, acting as a reader, reports D2R transmission to the network-side device using either coherent or non-coherent detection capabilities, and the network-side device can reasonably configure the terminal's D2R transmission parameters.

[0166] It should be noted that, generally speaking, coherent detection outperforms non-coherent detection. Network-side devices can select appropriate terminals for AIoT device inventory tasks based on their coherent or non-coherent detection capabilities, thus achieving a reasonable trade-off between coverage and resource overhead.

[0167] For example, the terminal, acting as a reader, reports the number of time-domain resources used for D2R transmission in contention-based random access to the network-side device. The network-side device can then determine the length, interval, and other relevant parameters of the DMRS configured for the terminal's D2R transmission.

[0168] Information 21: R2D transmission uses single-sideband modulation or double-sideband modulation.

[0169] It is understandable that using single-sideband modulation in R2D may reduce the terminal's requirement for the number of RBs, but at the same time, there will be a loss in the modulation depth of OOK.

[0170] For example, when a terminal, acting as a reader, reports R2D transmission to a network-side device using single-sideband modulation or double-sideband modulation, the network-side device can choose to perform AIoT transmission with lower bandwidth consumption to inventory target AIoT devices. Alternatively, depending on whether single-sideband modulation is used, a suitable terminal can be selected for inventory, achieving a better trade-off between resources and complexity.

[0171] In some embodiments, the terminal reports at least one of the following:

[0172] The terminal supports or recommends that D2R transmission use coherent detection or non-coherent detection;

[0173] The terminal supports or recommends that R2D transmission use single-sideband modulation or double-sideband modulation.

[0174] In other words, the terminal can report to either of the two terminals.

[0175] For example, the terminal reports support for coherent detection and support for double-sideband modulation; or, the terminal reports support for coherent detection and support for single-sideband modulation; or, the terminal reports support for incoherent detection and support for double-sideband modulation; or, the terminal reports support for incoherent detection and support for single-sideband modulation.

[0176] Information 22: The modulation depth satisfied by the OOK waveform generated by R2D transmission. For example, the level fluctuation index of the ON chip or OFF chip.

[0177] Information 23: The level fluctuation index satisfied by the OOK waveform generated by R2D transmission.

[0178] Optionally, different terminals generate OOK signals with varying modulation depths and level fluctuations. Clearly, a deeper modulation depth and lower level fluctuation in the OOK signal can provide AIoT devices with better detection performance and achieve better coverage.

[0179] For example, the ability of a terminal to report modulation depth and level fluctuation indicators to network-side devices as a reader can facilitate network-side devices in selecting appropriate terminals to complete inventory operations.

[0180] For example, a terminal with capability 1 generates a modulation depth of 80% and a level fluctuation of 10%, while a terminal with capability 2 generates a modulation depth of 90% and a level fluctuation of 5%.

[0181] Information 24: Interaction methods between A-IoT communication and NR communication.

[0182] For example, the terminal can support simultaneous AIoT transmission and NR transmission; or, the terminal can support which signals in NR transmission can be transmitted simultaneously with AIoT transmission.

[0183] In this way, the terminal informs the network-side device of its capabilities in A-IoT communication by reporting various first information to the network-side device, enabling the network-side device to configure appropriate configuration information.

[0184] Optionally, in some embodiments of this application, step 201 is specifically implemented by step 201a, and the A-IoT communication method provided in the embodiments of this application further includes step 201b.

[0185] Step 201a: The terminal sends the first information to the network-side device through terminal capability information or terminal auxiliary information.

[0186] Step 201b: The network-side device receives terminal capability information or terminal auxiliary information from the terminal.

[0187] In some embodiments of this application, the aforementioned terminal capability information or terminal auxiliary information carries the aforementioned first information.

[0188] In some embodiments of this application, the network-side equipment described above may be a base station or a core network device.

[0189] In the A-IoT communication method provided in this application embodiment, the terminal reports first information to the network-side device through terminal capability information or terminal auxiliary information. This first information is information related to A-IoT communication. Thus, the terminal provides the network-side device with the first information related to A-IoT communication, enabling the network-side device to refer to the obtained terminal A-IoT communication-related information and reasonably configure the terminal's A-IoT communication parameters. This allows the terminal to use these A-IoT communication parameters to communicate with A-IoT devices.

[0190] Optionally, in some embodiments of this application, the A-IoT communication method provided in this application embodiment further includes step 301.

[0191] Step 301: The terminal obtains A-IoT communication configuration information from the network-side device.

[0192] In some embodiments of this application, the above-mentioned A-IoT communication configuration information is determined with reference to the first information.

[0193] It should be noted that the initial information sent by the terminal to the network-side device is for the network-side device's reference only. In other words, the network-side device may not configure AIoT communication parameters for the terminal based on the initial information sent by the terminal. Of course, the network-side device can also configure AIoT communication parameters for the terminal based on the initial information sent by the terminal, depending on the implementation of the network-side device.

[0194] Optionally, the terminal communicates with the A-IoT device based on communication configuration information.

[0195] Optionally, in some embodiments of this application, the A-IoT communication method provided in this application embodiment further includes step 301a, and the above step 301 is specifically implemented through the following step 301b.

[0196] Step 301a: The network-side device sends A-IoT communication configuration information to the terminal.

[0197] In some embodiments of this application, the network-side device refers to the capability information contained in the first information received from the terminal to configure the corresponding configuration information for the terminal to perform A-IoT communication.

[0198] For example, the above configuration information includes, but is not limited to, at least one of the following: A-IoT communication transmission parameters and A-IoT communication transmission resources.

[0199] Step 301b: The terminal receives A-IoT communication configuration information from the network-side device.

[0200] In this way, the terminal can perform A-IoT communication based on the received A-IoT communication configuration information.

[0201] Optionally, in some embodiments of this application, the information in the first information above can be reported separately, or some information can be packaged into a configuration file for reporting.

[0202] Optionally, in some embodiments of this application, step 201 is specifically implemented by step 201c, and the A-IoT communication provided in the embodiments of this application further includes step 201d.

[0203] Step 201c: The terminal reports at least one configuration file to the network-side device through terminal capability information or terminal auxiliary information.

[0204] Step 201d: The network-side device receives at least one configuration file from the terminal.

[0205] In some embodiments of this application, the configuration file mentioned above includes at least one piece of information from the first information.

[0206] In some embodiments of this application, each configuration file includes a set of capability information, namely at least one of the information in the first information described above.

[0207] For example, configuration file 1 includes information 1, information 4, and information 6. Configuration file 2 includes information 1 to 7. The terminal can report configuration file 1 and configuration file 2 together to the network-side device, or it can report configuration file 1 or configuration file 2 separately to the network-side device.

[0208] It is understandable that the capability information in the first part of the information mentioned above could be a package of some capabilities together, reported as a single profile. Furthermore, this capability information could be divided into multiple profiles. For example, a capability information could be in one profile or multiple profiles.

[0209] In this way, the terminal can more flexibly select different capability information to report to the network-side device, enabling the network-side device to configure more reasonable configuration information for the terminal.

[0210] The following two specific embodiments illustrate the A-IoT communication method provided in this application.

[0211] Example 1: Referring to Figure 4, this example provides a topology diagram for AIoT communication.

[0212] In some real-life examples of this application, the aforementioned network-side devices, such as base station 12, communicate with A-IoT device 13 through intermediate nodes. These intermediate nodes can be terminals 11, repeaters, relay nodes, integrated access and backhaul nodes (IAB nodes), etc.

[0213] For example, the base station 12 can control intermediate nodes through air interface signaling or other interfaces. For instance, the base station controls the terminal through the air interface of NR Uu.

[0214] In this scenario, to better support AIoT communication, the terminal needs to report its capabilities as an AIoT communication intermediary node to the base station corresponding to the AIoT device. The base station can then configure appropriate AIoT communication parameters based on this information for communication between the terminal and the AIoT device. This improves the efficiency of AIoT communication.

[0215] Example 2:

[0216] Figure 6 is a flowchart illustrating an AIoT communication method provided in some embodiments of this application. As shown in Figure 6, taking the terminal as the reader and the network-side device as the base station as an example, the AIoT communication method provided in some embodiments of this application may include the following steps A1 to A6.

[0217] Step A1: The terminal sends capability information related to AIoT communication to the base station, namely the first information mentioned above.

[0218] Step A2: The base station receives capability information related to AIoT communication from the terminal.

[0219] Step A3: The base station refers to the AIoT communication-related capability information sent by the terminal to determine the AIoT communication configuration information.

[0220] Step A4: The base station sends AIoT communication configuration information to the terminal.

[0221] Step A5: The terminal receives AIoT communication configuration information from the base station.

[0222] Step A6: The terminal communicates with the AIoT device according to the AIoT communication configuration information.

[0223] Therefore, in scenarios where the terminal acts as a reader, to better support AIoT communication, the terminal needs to report its capabilities as an AIoT communication intermediary node to the base station corresponding to the AIoT device. The base station can then further configure appropriate AIoT communication parameters based on the terminal's capability information for AIoT communication between the terminal and the AIoT device. This improves the efficiency of AIoT communication.

[0224] The AIoT communication method provided in this application can be executed by an AIoT communication device. This application uses an AIoT communication device executing the AIoT communication method as an example to illustrate the AIoT communication device provided in this application.

[0225] This application provides an AIoT communication device. As an example, the AIoT communication device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0226] An AIoT communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0227] Specifically, referring to Figure 7, when the AIoT communication device is a terminal or a component in a terminal, the AIoT communication device 600 includes a sending module 601, which is used to report first information to the network-side device through terminal capability information or terminal auxiliary information. The first information is information related to A-IoT communication.

[0228] Optionally, in some embodiments of this application, as shown in FIG7 and FIG8, the above-mentioned device 600 further includes: a receiving module 602; the receiving module 602 is used to obtain A-IoT communication configuration information from the above-mentioned network-side device, wherein the A-IoT communication configuration information is determined with reference to the above-mentioned first information.

[0229] Optionally, in some embodiments of this application, as shown in FIG7 and FIG9, the above-mentioned device 600 further includes: a processing module 603; the processing module 603 is used to communicate with the A-IoT device according to the above-mentioned A-IoT communication configuration information.

[0230] Optionally, in some embodiments of this application, the A-IoT communication device is a reader or intermediate node in A-IoT communication, and the processing module 603 is specifically used to receive, process or forward the D2R transmission sent by the A-IoT device according to the A-IoT communication configuration information.

[0231] Optionally, in some embodiments of this application, the first information mentioned above includes at least one of the following parameters:

[0232] The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol;

[0233] The minimum number of resource blocks (RBs) corresponding to each M value;

[0234] Bit length of D2R transmission;

[0235] The bit duration Tb of D2R transmission;

[0236] Chip length or chip duration Tchip;

[0237] Minimum frequency offset for D2R transmission;

[0238] The maximum frequency offset of D2R transmission;

[0239] The number of codeword repetitions, R, in Manchester encoding;

[0240] The length or number of preamble sequences transmitted in D2R;

[0241] The length or number of intermediate sequences in D2R transmission;

[0242] Does it support FEC?

[0243] Number of code block-level repetitions in D2R transmission;

[0244] Number of bit-level repetitions in D2R transmission;

[0245] The number of frequency division multiplexing D2R transmission resources;

[0246] Frequency division multiplexing with small frequency offset combination;

[0247] Frequency division multiplexing small frequency offset mapping relationship, which includes at least one of the following: the mapping relationship between the above Tchip and the above R, and the mapping relationship between the set of values ​​of the above Tchip and the above R;

[0248] CW's transmission power;

[0249] Phase noise in CW transmission;

[0250] The amount of time-domain resources used for D2R transmission in contention-based random access;

[0251] D2R transmission uses either coherent or incoherent detection;

[0252] Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation;

[0253] The modulation depth satisfied by the OOK waveform generated by R2D transmission;

[0254] The OOK waveform generated by R2D transmission meets the level fluctuation index;

[0255] The interaction method between A-IoT communication and NR communication.

[0256] Optionally, in some embodiments of this application, the sending module 601 is specifically used to report at least one configuration file to the network-side device through terminal capability information or terminal auxiliary information; wherein the configuration file includes at least one of the first information.

[0257] In the A-IoT communication device provided in this application embodiment, the A-IoT communication device reports first information to the network-side device through terminal capability information or terminal auxiliary information. This first information is information related to A-IoT communication. Thus, the A-IoT communication device provides the network-side device with this first information related to A-IoT communication, enabling the network-side device to refer to the obtained information and reasonably configure the A-IoT communication parameters of the A-IoT communication device. This allows the A-IoT communication device to use these A-IoT communication parameters to communicate with other A-IoT devices.

[0258] Referring to Figure 10, when the AIoT communication device is a network-side device or a component in a network-side device, the AIoT communication device 700 includes a receiving module 701 for receiving terminal capability information or terminal auxiliary information from the terminal. The terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication.

[0259] Optionally, in some embodiments of this application, as shown in FIG10 and FIG11, the above-mentioned device 700 further includes: a sending module 702, which is used to send A-IoT communication configuration information to the above-mentioned terminal, wherein the A-IoT communication configuration information is determined with reference to the above-mentioned first information.

[0260] Optionally, in some embodiments of this application, the first information mentioned above includes at least one of the following parameters:

[0261] The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol;

[0262] The minimum number of RBs corresponding to each M value;

[0263] Bit length of D2R transmission;

[0264] The bit duration Tb of D2R transmission;

[0265] Chip length or chip duration Tchip;

[0266] Minimum frequency offset for D2R transmission;

[0267] The maximum frequency offset of D2R transmission;

[0268] The number of codeword repetitions, R, in Manchester encoding;

[0269] The length or number of preamble sequences transmitted in D2R;

[0270] The length or number of intermediate sequences in D2R transmission;

[0271] Does it support FEC?

[0272] Number of code block-level repetitions in D2R transmission;

[0273] Number of bit-level repetitions in D2R transmission;

[0274] The number of frequency division multiplexing D2R transmission resources;

[0275] Frequency division multiplexing with small frequency offset combination;

[0276] Frequency division multiplexing small frequency offset mapping relationship, which includes at least one of the following: the mapping relationship between the above Tchip and the above R, and the mapping relationship between the set of values ​​of the above Tchip and the above R;

[0277] CW's transmission power;

[0278] Phase noise in CW transmission;

[0279] The amount of time-domain resources used for D2R transmission in contention-based random access;

[0280] D2R transmission uses either coherent or incoherent detection;

[0281] Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation;

[0282] The modulation depth satisfied by the OOK waveform generated by R2D transmission;

[0283] The OOK waveform generated by R2D transmission meets the level fluctuation index;

[0284] The interaction method between A-IoT communication and NR communication.

[0285] Optionally, in some embodiments of this application, the receiving module 701 is specifically used to receive at least one configuration file from the terminal; wherein the configuration file includes at least one of the first information items.

[0286] In the A-IoT communication device provided in this application embodiment, the A-IoT communication device receives terminal capability information or terminal auxiliary information from a terminal. This terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication. Thus, the terminal provides the A-IoT communication device with the first information related to A-IoT communication, enabling the A-IoT communication device to refer to the obtained terminal-related A-IoT communication information and rationally configure the terminal's A-IoT communication parameters. This allows the terminal to use these A-IoT communication parameters to communicate with A-IoT devices.

[0287] The AIoT communication device provided in this application embodiment can implement all the processes implemented in the AIoT communication method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0288] As shown in Figure 12, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described AIoT communication method embodiment and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above-described AIoT communication method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0289] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG5. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the AIoT communication device shown in FIG7. Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0290] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0291] Those skilled in the art will understand that terminal 100 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 13 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0292] It should be understood that, in this embodiment, the input unit 104 may include a graphics processor 1041 and a microphone 1042. The graphics processor 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0293] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 101 can transmit it to the processor 110 for processing; in addition, the radio frequency unit 101 can send uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0294] The memory 109 can be used to store software programs or instructions and various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback function, image playback function, etc.), etc. Furthermore, the memory 109 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM).

[0295] Access Memory (RAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 109 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0296] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0297] The radio frequency unit 101 is used to report first information to the network-side device through terminal capability information or terminal auxiliary information, wherein the first information is information related to A-IoT communication.

[0298] Optionally, in some embodiments of this application, the radio frequency unit 101 is further configured to obtain A-IoT communication configuration information from the network-side device, wherein the A-IoT communication configuration information is determined with reference to the first information.

[0299] Optionally, in some embodiments of this application, the radio frequency unit 101 is further configured to communicate with the A-IoT device according to the A-IoT communication configuration information.

[0300] Optionally, in some embodiments of this application, the A-IoT communication device is a reader or intermediate node in A-IoT communication, and the processor 110 is specifically used to receive, process or forward D2R transmissions sent by the A-IoT device according to the A-IoT communication configuration information.

[0301] Optionally, in some embodiments of this application, the first information mentioned above includes at least one of the following parameters:

[0302] The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol;

[0303] The minimum number of resource blocks (RBs) corresponding to each M value;

[0304] Bit length of D2R transmission;

[0305] The bit duration Tb of D2R transmission;

[0306] Chip length or chip duration Tchip;

[0307] Minimum frequency offset for D2R transmission;

[0308] The maximum frequency offset of D2R transmission;

[0309] The number of codeword repetitions, R, in Manchester encoding;

[0310] The length or number of preamble sequences transmitted in D2R;

[0311] The length or number of intermediate sequences in D2R transmission;

[0312] Does it support FEC?

[0313] Number of code block-level repetitions in D2R transmission;

[0314] Number of bit-level repetitions in D2R transmission;

[0315] The number of frequency division multiplexing D2R transmission resources;

[0316] Frequency division multiplexing with small frequency offset combination;

[0317] Frequency division multiplexing small frequency offset mapping relationship, which includes at least one of the following: the mapping relationship between the above Tchip and the above R, and the mapping relationship between the set of values ​​of the above Tchip and the above R;

[0318] CW's transmission power;

[0319] Phase noise in CW transmission;

[0320] The amount of time-domain resources used for D2R transmission in contention-based random access;

[0321] D2R transmission uses either coherent or incoherent detection;

[0322] Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation;

[0323] The modulation depth satisfied by the OOK waveform generated by R2D transmission;

[0324] The OOK waveform generated by R2D transmission meets the level fluctuation index;

[0325] The interaction method between A-IoT communication and NR communication.

[0326] Optionally, in some embodiments of this application, the radio frequency unit 101 is specifically used to report at least one configuration file to the network-side device through terminal capability information or terminal auxiliary information; wherein the configuration file includes at least one of the first information.

[0327] In the terminal provided in this application embodiment, the terminal reports first information to the network-side device through terminal capability information or terminal auxiliary information. This first information is related to A-IoT communication. Thus, the terminal provides the network-side device with this first information related to A-IoT communication, allowing the network-side device to refer to the obtained information and appropriately configure the terminal's A-IoT communication parameters. This enables the terminal to use these A-IoT communication parameters to communicate with A-IoT devices.

[0328] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG5. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0329] Specifically, this application embodiment also provides a network-side device, which can be the AIoT communication device shown in FIG10. As shown in FIG14, the network-side device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be transmitted and sends it to the radio frequency device 92. The radio frequency device 92 processes the received information and transmits it through the antenna 91.

[0330] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 93, which includes a baseband processor.

[0331] The baseband device 93 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG14. One of the chips is, for example, a baseband processor, which is connected to the memory 95 via a bus interface to call the program or instructions in the memory 95 to execute the network-side device operation shown in the above method embodiment.

[0332] The network-side device may also include a network interface 96, such as a Common Public Radio Interface (CPRI).

[0333] The radio frequency device 92 is used to receive terminal capability information or terminal auxiliary information from the terminal. The terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication.

[0334] Optionally, in some embodiments of this application, the radio frequency device 92 is further configured to send A-IoT communication configuration information to the terminal, wherein the A-IoT communication configuration information is determined with reference to the first information.

[0335] Optionally, in some embodiments of this application, the first information mentioned above includes at least one of the following parameters:

[0336] The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol;

[0337] The minimum number of RBs corresponding to each M value;

[0338] Bit length of D2R transmission;

[0339] The bit duration Tb of D2R transmission;

[0340] Chip length or chip duration Tchip;

[0341] Minimum frequency offset for D2R transmission;

[0342] The maximum frequency offset of D2R transmission;

[0343] The number of codeword repetitions, R, in Manchester encoding;

[0344] The length or number of preamble sequences transmitted in D2R;

[0345] The length or number of intermediate sequences in D2R transmission;

[0346] Does it support FEC?

[0347] Number of code block-level repetitions in D2R transmission;

[0348] Number of bit-level repetitions in D2R transmission;

[0349] The number of frequency division multiplexing D2R transmission resources;

[0350] Frequency division multiplexing with small frequency offset combination;

[0351] Frequency division multiplexing small frequency offset mapping relationship, which includes at least one of the following: the mapping relationship between the above Tchip and the above R, and the mapping relationship between the set of values ​​of the above Tchip and the above R;

[0352] CW's transmission power;

[0353] Phase noise in CW transmission;

[0354] The amount of time-domain resources used for D2R transmission in contention-based random access;

[0355] D2R transmission uses either coherent or incoherent detection;

[0356] Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation;

[0357] The modulation depth satisfied by the OOK waveform generated by R2D transmission;

[0358] The OOK waveform generated by R2D transmission meets the level fluctuation index;

[0359] The interaction method between A-IoT communication and NR communication.

[0360] Optionally, in some embodiments of this application, the radio frequency device 92 is specifically used to receive at least one configuration file from the terminal; wherein the configuration file includes at least one of the first information items.

[0361] In the A-IoT communication method provided in this application embodiment, the network-side device receives terminal capability information or terminal auxiliary information from the terminal. This terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication. Thus, the terminal provides the network-side device with the first information related to A-IoT communication, enabling the network-side device to refer to the obtained terminal A-IoT communication-related information and reasonably configure the terminal's A-IoT communication parameters. This allows the terminal to use these A-IoT communication parameters to communicate with A-IoT devices.

[0362] In addition, the network-side device 900 of this application embodiment also includes: a program or instructions stored in a memory 95 and executable on a processor 94. The processor 94 calls the program or instructions in the memory 95 to execute the methods executed by each module shown in FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0363] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described AIoT communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0364] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0365] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described AIoT communication method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0366] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0367] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described AIoT communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0368] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the AIoT communication method described above, and the network-side device can be used to perform the steps of the AIoT communication method described above.

[0369] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, the presence of additional identical elements in the process, method, article, or apparatus that includes that element is not excluded. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0370] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0371] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An AIoT (Artificial Intelligence of Things) communication method, comprising: The terminal reports first information to the network-side device through terminal capability information or terminal auxiliary information, and the first information is information related to A-IoT communication.

2. The method according to claim 1, wherein, The method further includes: The terminal obtains A-IoT communication configuration information from the network-side device, and the A-IoT communication configuration information is determined with reference to the first information.

3. The method according to claim 2, wherein, The method further includes: The terminal communicates with the A-IoT device according to the A-IoT communication configuration information.

4. The method according to claim 2, wherein, The terminal is a reader or intermediate node in A-IoT communication. The terminal communicates with A-IoT devices according to the A-IoT communication configuration information, including: The terminal receives, processes, or forwards D2R transmissions from A-IoT devices to the reader based on the A-IoT communication configuration information.

5. The method according to any one of claims 1 to 4, wherein, The first information includes at least one of the following parameters: The value of M in the on / off key control OOK waveform is the number of OOK chips contained in an orthogonal frequency division multiplexing (OFDM) symbol. The minimum number of resource blocks (RBs) corresponding to each M value; Bit length of D2R transmission; The bit duration Tb of D2R transmission; Chip length or chip duration Tchip; Minimum frequency offset for D2R transmission; The maximum frequency offset of D2R transmission; The number of codeword repetitions, R, in Manchester encoding; The length or number of preamble sequences transmitted in D2R; The length or number of intermediate sequences in D2R transmission; Does it support Forward Error Correction (FEC)? Number of code block-level repetitions in D2R transmission; Number of bit-level repetitions in D2R transmission; The number of frequency division multiplexing D2R transmission resources; Frequency division multiplexing with small frequency offset combination; Frequency division multiplexing small frequency offset mapping relationship, the frequency division multiplexing small frequency offset mapping relationship includes at least one of the following: the mapping relationship between Tchip and R, and the mapping relationship between the value set of Tchip and R; Transmission power of continuous wave (CW); Phase noise in CW transmission; The amount of time-domain resources used for D2R transmission in contention-based random access; D2R transmission uses either coherent or incoherent detection; Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation; The modulation depth satisfied by the OOK waveform generated by R2D transmission; The OOK waveform generated by R2D transmission meets the level fluctuation index; The interaction method between A-IoT communication and NR communication.

6. The method according to claim 5, wherein, The terminal reports first information to the network-side device through terminal capability information or terminal auxiliary information, including: The terminal reports at least one configuration file to the network-side device through terminal capability information or terminal auxiliary information; The configuration file includes at least one of the first pieces of information.

7. An A-IoT communication method, comprising: The network-side device receives terminal capability information or terminal auxiliary information from the terminal. The terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication.

8. The method according to claim 7, wherein, The method further includes: The network-side device sends A-IoT communication configuration information to the terminal, and the A-IoT communication configuration information is determined with reference to the first information.

9. The method according to claim 7 or 8, wherein, The first information includes at least one of the following parameters: The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol; The minimum number of RBs corresponding to each M value; Bit length of D2R transmission; The bit duration Tb of D2R transmission; Chip length or chip duration Tchip; Minimum frequency offset for D2R transmission; The maximum frequency offset of D2R transmission; The number of codeword repetitions, R, in Manchester encoding; The length or number of preamble sequences transmitted in D2R; The length or number of intermediate sequences in D2R transmission; Does it support FEC? Number of code block-level repetitions in D2R transmission; Number of bit-level repetitions in D2R transmission; The number of frequency division multiplexing D2R transmission resources; Frequency division multiplexing with small frequency offset combination; Frequency division multiplexing small frequency offset mapping relationship, the frequency division multiplexing small frequency offset mapping relationship includes at least one of the following: the mapping relationship between Tchip and R, and the mapping relationship between the value set of Tchip and R; CW's transmission power; Phase noise in CW transmission; The amount of time-domain resources used for D2R transmission in contention-based random access; D2R transmission uses either coherent or incoherent detection; Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation; The modulation depth satisfied by the OOK waveform generated by R2D transmission; The OOK waveform generated by R2D transmission meets the level fluctuation index; The interaction method between A-IoT communication and NR communication.

10. The method according to claim 9, wherein, The network-side device receives terminal capability information or terminal assistance information from the terminal, including: The network-side device receives at least one configuration file from the terminal; The configuration file includes at least one of the first pieces of information.

11. An A-IoT communication device, comprising: Sending module; The sending module is used to report first information to the network-side device through terminal capability information or terminal auxiliary information, wherein the first information is information related to A-IoT communication.

12. The apparatus according to claim 11, wherein, The device further includes: a receiving module; The receiving module is used to obtain A-IoT communication configuration information from the network-side device, and the A-IoT communication configuration information is determined with reference to the first information.

13. The apparatus according to claim 12, wherein, The device further includes: a processing module; The processing module is used to communicate with A-IoT devices according to the A-IoT communication configuration information.

14. The apparatus according to claim 12, wherein, The A-IoT communication device is a reader or intermediate node in A-IoT communication. The processing module is specifically used to receive, process, or forward D2R transmissions sent by the A-IoT device according to the A-IoT communication configuration information.

15. The apparatus according to any one of claims 11 to 14, wherein, The first information includes at least one of the following parameters: The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol; The minimum number of resource blocks (RBs) corresponding to each M value; Bit length of D2R transmission; The bit duration Tb of D2R transmission; Chip length or chip duration Tchip; Minimum frequency offset for D2R transmission; The maximum frequency offset of D2R transmission; The number of codeword repetitions, R, in Manchester encoding; The length or number of preamble sequences transmitted in D2R; The length or number of intermediate sequences in D2R transmission; Does it support FEC? Number of code block-level repetitions in D2R transmission; Number of bit-level repetitions in D2R transmission; The number of frequency division multiplexing D2R transmission resources; Frequency division multiplexing with small frequency offset combination; Frequency division multiplexing small frequency offset mapping relationship, the frequency division multiplexing small frequency offset mapping relationship includes at least one of the following: the mapping relationship between Tchip and R, and the mapping relationship between the value set of Tchip and R; CW's transmission power; Phase noise in CW transmission; The amount of time-domain resources used for D2R transmission in contention-based random access; D2R transmission uses either coherent or incoherent detection; Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation; The modulation depth satisfied by the OOK waveform generated by R2D transmission; The OOK waveform generated by R2D transmission meets the level fluctuation index; The interaction method between A-IoT communication and NR communication.

16. The apparatus according to claim 15, wherein, The sending module is specifically used to report at least one configuration file to the network-side device through terminal capability information or terminal auxiliary information. The configuration file includes at least one of the first pieces of information.

17. An A-IoT communication device, comprising: Receiver module; The receiving module is used to receive terminal capability information or terminal auxiliary information from the terminal. The terminal capability information or terminal auxiliary information carries first information, which is information related to A-IoT communication.

18. The apparatus according to claim 17, wherein, The device further includes: a transmitting module; The sending module is used to send A-IoT communication configuration information to the terminal, wherein the A-IoT communication configuration information is determined with reference to the first information.

19. The apparatus according to claim 17 or 18, wherein, The first information parameter includes at least one of the following parameters: The value of M in the OOK waveform is the number of OOK chips contained in an OFDM symbol; The minimum number of RBs corresponding to each M value; Bit length of D2R transmission; The bit duration Tb of D2R transmission; Chip length or chip duration Tchip; Minimum frequency offset for D2R transmission; The maximum frequency offset of D2R transmission; The number of codeword repetitions, R, in Manchester encoding; The length or number of preamble sequences transmitted in D2R; The length or number of intermediate sequences in D2R transmission; Does it support FEC? Number of code block-level repetitions in D2R transmission; Number of bit-level repetitions in D2R transmission; The number of frequency division multiplexing D2R transmission resources; Frequency division multiplexing with small frequency offset combination; Frequency division multiplexing small frequency offset mapping relationship, the frequency division multiplexing small frequency offset mapping relationship includes at least one of the following: the mapping relationship between Tchip and R, and the mapping relationship between the value set of Tchip and R; CW's transmission power; Phase noise in CW transmission; The amount of time-domain resources used for D2R transmission in contention-based random access; D2R transmission uses either coherent or incoherent detection; Reader-to-A-IoT device R2D transmission uses single-sideband modulation or double-sideband modulation; The modulation depth satisfied by the OOK waveform generated by R2D transmission; The OOK waveform generated by R2D transmission meets the level fluctuation index; The interaction method between A-IoT communication and NR communication.

20. The apparatus according to claim 19, wherein, The receiving module is specifically used to receive at least one configuration file from the terminal; The configuration file includes at least one of the first pieces of information.

21. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the A-IoT communication method as claimed in any one of claims 1 to 6.

22. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the A-IoT communication method as claimed in any one of claims 7 to 10.

23. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the A-IoT communication method as claimed in any one of claims 1 to 6, or implement the steps of the A-IoT communication method as claimed in any one of claims 7 to 10.

24. A chip comprising a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the A-IoT communication method as claimed in any one of claims 1 to 6, or to implement the steps of the A-IoT communication method as claimed in any one of claims 7 to 10.

25. A computer program product, characterized in that, The program product is stored in a non-transient storage medium, and the program product is executed by at least one processor to implement the steps of the A-IoT communication method as claimed in any one of claims 1 to 6, or to implement the steps of the A-IoT communication method as claimed in any one of claims 7 to 10.