Communication method and communication apparatus

Abstract

Provided are a communication method and a communication apparatus. The method is applied to the field of communications, such as ambient Internet of Things (AIoT) communication scenarios. The method comprises: a first device issuing a first message, wherein the first message is used for configuring resources for one or more AIoT devices (including at least a first AIoT device), such that the first AIoT device can obtain corresponding resource configuration parameters on the basis of the first message, thereby using configured resources to transmit AIoT data. In addition, the present application can reduce the number of bits occupied by resource information, reduce overheads, and help to save on transmission resources.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510378404.2, filed with the State Intellectual Property Office of China on March 26, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0003] Ambient Internet of Things (AIoT) technology is an emerging communication technology. With the rapid development of communication technology, applying AIoT to communication technologies has become a major trend in order to provide users with richer communication experiences. In communication systems using AIoT technology, data can be transmitted between the reader and AIoT devices. However, there is currently no specific solution on how to configure resources for AIoT devices. Summary of the Invention

[0004] In view of this, this application provides a communication method, communication device, chip system, computer-readable storage medium, computer program product, and communication system capable of configuring resources for AIoT devices.

[0005] In a first aspect, a communication method is provided. This method can be executed by, for example, a first AIoT device, or by a component (such as a circuit, chip, or chip system) configured in the first AIoT device, or by a logic module or software capable of implementing all or part of the functions of the AIoT device. This application does not limit this aspect.

[0006] Specifically, the method includes: a first AIoT device receiving a first message from a first device, the first message being used to configure resources for a first environment IoT AIoT device, the first message including at least first resource type information, the first resource type information being used to instruct the first AIoT device to adopt a first resource type; and sending a second message to the first device, the second message being determined at least based on the first resource type.

[0007] Based on the above technical solution, for AIoT data transmission, the first AIoT device receives a first message sent by another device, the first message being used to configure resources for one or more AIoT devices (including at least the first AIoT device). In this way, the first AIoT device can obtain the corresponding resource configuration parameters based on the first message, thereby utilizing the configured resources to transmit AIoT data.

[0008] In one possible implementation, the first resource type is any one of the following resource types: a first type, which is a resource type that includes all configuration parameters in a first configuration parameter set, the first configuration parameter set including one or more of the following: frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters used to indicate the amount of data to be transmitted or the size of the data packet; a second type, which is a resource type that includes some configuration parameters in the first configuration parameter set; and a third type, which is a resource type that does not include any configuration parameter in the first configuration parameter set.

[0009] In one possible implementation, the first message further includes resource information; the resource type corresponding to the resource information is the first resource type. That is, the first message may include not only resource type information but also resource information corresponding to the resource type information. In this way, the first AIoT device can determine the specific resource information configured so as to utilize the corresponding resource information for data transmission.

[0010] In one possible implementation, the first message is used to configure resources for a plurality of AIoT devices; the plurality of AIoT devices include at least the first AIoT device and the second AIoT device; the first message also includes first resource information and second resource information, wherein the first resource information is resource information configured for the first AIoT device and the second resource information is resource information configured for the second AIoT device.

[0011] Therefore, the first message can be directed to one or more AIoT devices, such as including resource configuration information for a first AIoT device and resource configuration information for a second AIoT device. Compared to configuring the resource information of one AIoT device at a time, the first message in this embodiment supports configuring the resource information of multiple AIoT devices at once, further reducing the number of messages used for resource configuration (such as R2D messages), thereby greatly reducing the overhead of resource information configuration and improving the efficiency of AIoT service data transmission.

[0012] In one possible implementation, the first message further includes: device identification information of the first AIoT device, and / or, device identification information of the second AIoT device. By introducing device identification information into the first message, the AIoT device corresponding to the device identification can use the corresponding resources allocated by the first device for data transmission.

[0013] It is understood that different AIoT devices may have the same or different resource types, and this application does not specifically limit this.

[0014] In one possible implementation, the resource type corresponding to both the second resource information and the first resource information is the first resource type.

[0015] In one possible implementation, the first resource type information is located in a first field of the first message, and the first resource information and the second resource information are located in a second field of the first message; wherein the first field and the second field are located in different parts of the first message; or, the first field and the second field are both located in the header of the first message, or both are located in the control field of the first message, or both are located in the payload field of the first message, or both are located in the sub-header portion of the first message; or, the first field and the second field are located in the Layer 1 control field and the Layer 2 data packet, respectively. That is, the embodiments of this application do not limit the position of resource information and / or resource type information in the first message, providing multiple possible design methods for the message body of the first message. Furthermore, to reduce the number of redundant bits, when the resource types are the same, only one resource type information needs to be included in the first message.

[0016] In one possible implementation, the first message may also include one or more of the following: device quantity information, resource quantity information, and successful reception bit SRB information.

[0017] Optionally, the device quantity information and the resource quantity information are located in the first domain.

[0018] In one possible implementation, the first message further includes second resource type information, which instructs the second AIoT device to adopt a second resource type; wherein the first resource type information instructs the first AIoT device to adopt a first resource type; and the second resource type is different from the first resource type. In other words, the first message also supports configuring resource information of different resource types for different AIoT devices, thereby meeting the needs of AIoT devices.

[0019] In one possible implementation, the first resource type information and the first resource information are located in the third domain as a first group of resource information; the second resource type information and the second resource information are located in the third domain as a second group of resource information; wherein the third domain is located in the header of the first message, or in the control domain of the first message, or in the payload domain of the first message, or in the subheader portion of the first message, or in the layer 1 control domain.

[0020] In one possible implementation, the device identification information of the first AIoT device is located in the first set of resource information; the first set of resource information also includes first successfully received bit (SRB) information; and / or, the device identification information of the second AIoT device is located in the second set of resource information, and the second set of resource information also includes second SRB information.

[0021] It should be noted that the length of the device identifier of the first AIoT device and the length of the device identifier of the second AIoT device can be the same or different, and there is no specific limitation on this. Alternatively, the allocation type of the device identifier of the first AIoT device and the allocation type of the device identifier of the second AIoT device can be the same or different, and there is no specific limitation on this.

[0022] In one possible implementation, the first message further includes device identifier length information; or, the first message further includes allocation type information. That is, the device identifiers of both the first AIoT device and the second AIoT device can use the device identifier length information. Alternatively, the device identifiers of both the first and second AIoT devices can use the allocation type information. By setting the identifier length information or allocation type information as a common part in a common domain, and making the information in the common domain applicable to multiple AIoT devices, it is unnecessary to include the identifier length information or allocation type information in the resource-related information of each device, thus further reducing redundant bits.

[0023] Alternatively, in another possible implementation, the device identifier length of the first AIoT device is a first length information, and the device identifier length of the second AIoT device is a second length information, with the first message also including the first length information and the second length information; or, the allocation type of the device identifier of the first AIoT device is a first allocation type, and the allocation type of the device identifier of the second AIoT device is a second allocation type, with the first message also including the first allocation type and the second allocation type. That is, when the lengths of the device identifiers of the first and second AIoT devices are different, the first message may also include the length information of the device identifier of each AIoT device, so that subsequent AIoT devices can accurately identify their corresponding resource information.

[0024] Based on the two implementation methods described above, introducing the device identifier length information or allocation type of the AIoT device into the first message helps to correctly identify the specific AIoT device. This allows the AIoT device to parse only its own data packets, achieving more accurate data packet parsing and improving parsing efficiency; it also reduces unnecessary data packet parsing of non-target devices, thereby helping to reduce unnecessary energy consumption and save power for the AIoT device.

[0025] In one possible implementation, the first message further includes first indication information; the first indication information is used to indicate whether the first message includes a data field. By adding the first indication information to the first message, the first AIoT device is assisted in determining whether a data field is included.

[0026] This application does not limit the specific implementation of the first indication information in the embodiments. Optionally, the first indication information is data field indication information; or, the first indication information is a successful reception bit (SRB) indication; or, the first indication information is a data length indication.

[0027] In one possible implementation, the first message is a reader-to-device R2D message; the second message is a device-to-reader D2R message.

[0028] Secondly, a communication method is provided, which may be executed by a first device, or by a component configured in the first device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the first device. This application does not limit this method.

[0029] Specifically, the method includes: a first device sending a first message, the first message being used to configure resources for an environmental Internet of Things (AIoT) device, the first message including at least first resource type information, the first resource type information being used to instruct the AIoT device to adopt a first resource type; and receiving a second message from the AIoT device, the second message being determined at least based on the first resource type.

[0030] In this embodiment of the application, for AIoT data transmission, the first device sends a first message, which is used to configure resources for one or more AIoT devices (including at least the first AIoT device), so that the first AIoT device can obtain the corresponding resource configuration parameters based on the first message, and then use the configured resources to transmit A-IoT data.

[0031] It should be noted that the second aspect is the implementation on the first device side corresponding to the first aspect. The explanations (such as the explanation of terminology and the description of specific implementation methods), supplements, and descriptions of beneficial effects of the first aspect also apply to the second aspect. For the sake of brevity, the various specific implementation methods will not be elaborated on in the second aspect.

[0032] Thirdly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the first aspect described above.

[0033] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0034] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0035] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0036] In another design, the communication device is used to perform the method in the first aspect or any possible implementation of the first aspect described above. The communication device may be configured in the first AIoT device, or the communication device itself may be the first AIoT device.

[0037] Fourthly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the second aspect described above.

[0038] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0039] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0040] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0041] In another design, the communication device is used to perform the method in any possible implementation of the first device described above. The communication device may be configured in the first device, or the communication device itself may be the first device.

[0042] Optionally, the first device may be a reader, an access network device (e.g., gNB), a core network device (e.g., AMF network element, AF network element, NEF network element), a device capable of providing data transmission functions for AIoT devices (e.g., relay node, auxiliary node, UE, etc.), an AIoT controller, or a device with AIoT functions.

[0043] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0044] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0045] In another implementation, the communication device is a chip configured in the first AIoT device. When the communication device is a chip configured in the first AIoT device, the communication interface can be an input / output interface.

[0046] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first device aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, to which the processor is coupled.

[0047] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0048] In another implementation, the communication device is a chip configured in the first device. When the communication device is a chip configured in the first device, the communication interface can be an input / output interface.

[0049] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0050] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0051] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0052] Optionally, the processor may be one or more, and the memory may be one or more.

[0053] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0054] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0055] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0056] The processing device mentioned in the eighth aspect above can be one or more chips. The processor in the processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0057] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0058] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0059] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0060] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0061] In a twelfth aspect, a communication system is provided, including the aforementioned first AIoT device and first device. Optionally, the communication system further includes one or more AIoT devices.

[0062] Optionally, the communication system may also include other devices that communicate with the first AIoT device and / or the first device. Attached Figure Description

[0063] Figure 1 is an example diagram of a communication system;

[0064] Figure 2 is an example diagram of various topologies shown in the embodiments of this application;

[0065] Figure 3 is an example diagram of an access network device;

[0066] Figure 4A is an example interaction diagram of a communication method according to an embodiment of this application;

[0067] Figure 4B is an example diagram of a message body format for a first message according to an embodiment of this application;

[0068] Figure 5A is an example diagram of an application scenario of an embodiment of this application;

[0069] Figures 5B to 5C are example diagrams of different message body formats of the first message according to embodiments of this application;

[0070] Figures 6A and 6B are example diagrams of different message body formats of the first message according to embodiments of this application;

[0071] Figures 7A and 7B are example diagrams of different message body formats of the first message according to embodiments of this application;

[0072] Figures 8A and 8B are example diagrams of different message body formats of the first message according to embodiments of this application;

[0073] Figures 9A to 9C are example diagrams of different message body formats of the first message according to embodiments of this application;

[0074] Figure 10 is an example diagram of a message body format for a first message according to an embodiment of this application;

[0075] Figure 11 is an example diagram of the message body format of the first message including data field indication information according to an embodiment of this application;

[0076] Figure 12 is another interactive example diagram of the communication method according to an embodiment of this application;

[0077] Figure 13 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0078] Figure 14 is another schematic block diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0079] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0080] In this application embodiment, "multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items".

[0081] This application can be applied to communication systems. Mobile communication systems include, but are not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or new radio (NR) systems, 5.5G systems, and future mobile communication systems; vehicle-to-X (V2X) systems, where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc.; Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V) communication; vehicle-to-everything (V2X) communication; machine-type communication (MTC); Internet of Things (IoT); Long Term Evolution-Machine (LTE-M) technology for machine-to-machine (M2M) communication; and machine-to-machine (M2M) communication. Machine (M2M), etc.

[0082] The technical solutions of this application are applicable to communication systems that provide ambient internet of things (AIoT) services. Optionally, in some embodiments, the communication system providing AIoT services may include an ambient IoT device (AIoT device), or an ambient IoT AIoT terminal (which can be understood as a terminal capable of providing AIoT services). An ambient IoT device is an IoT device powered by energy harvesting and has limited energy storage capacity. For example, some or all of the characteristics of an ambient IoT device can be found in the description in 3GPP standard TR 38.769.

[0083] For example, AIoT devices are a new type of Internet of Things (IoT) devices that harvest energy from radio waves, light, motion, heat, or any other available environmental energy source and use it as power. Since AIoT devices do not require additional power supply or battery replacement, their maintenance costs are extremely low, and they can be widely used in fields such as smart warehousing, smart logistics, smart agriculture, industrial wireless sensor networks, smart transportation, and smart healthcare. Among these, key applications for AIoT include any of the following: (1) Identification-based connectivity (asset identification), for example, applications in the management of goods or assets in the manufacturing and logistics industries. (2) Micro-sensor-based connectivity (sensor data acquisition), for example, applications in wireless sensor networks in the energy, power, animal husbandry, and industrial sectors. (3) Low-power downlink connectivity (data downlink push), for example, applications in electronic shelf labels (ESL) in industrial, supermarket retail, and office applications. As an environment-enabled IoT technology, A-IoT, combined with cellular networks, offers tag-type terminals with lower or even zero power consumption compared to existing NB-IoT, making passive cellular technology suitable for more IoT scenarios, enabling interconnection across all industry scenarios, and realizing a new market worth hundreds of billions of dollars in connectivity.

[0084] It should be understood that the description of some or all of the characteristics of environmental IoT devices herein, referring to the description in 3GPP standard TR 38.769, is only one possible example, and the embodiments of this application are not limited thereto. For instance, as communication standard protocol versions evolve or are updated, some or all of the characteristics of environmental IoT devices herein may refer to the evolved or updated versions; or some or all of the characteristics of environmental IoT devices may also refer to the descriptions in related technologies.

[0085] The technical solutions of this application embodiment are also applicable to Internet of Things (IoT) communication scenarios and communication scenarios relying on backscatter technology. The aforementioned IoT can be passive IoT, semi-passive IoT, or ambient IoT (AIoT) (or named A-IoT), etc.

[0086] It should be understood that environmental IoT devices may also have other names or definitions, and this application embodiment does not specifically limit them.

[0087] For example, AIoT services can be called Ambient IoT Services / AIoT service. Ambient IoT services are used to support the functions and processes of environmental IoT application scenarios. Currently, there is no clear solution for environmental IoT services.

[0088] Figure 1 shows an example diagram of a communication system according to this application. As shown in Figure 1, the communication system includes at least a first device and a first AIoT device.

[0089] The first device in this application embodiment can be a network device (such as a core network device or an access network device) or a terminal device. In this application embodiment, devices that provide data transmission services for AIoT devices (such as access network devices, relay nodes, UEs, etc.) are collectively referred to as the first device or a reader. It should also be noted that in the network architecture involving AIoT services, the role of a network device can be played not only by traditional network devices such as access network devices and core network devices; but also by terminal devices (such as UEs); and by devices with data forwarding functions (such as relay nodes, forwarding nodes, etc.). That is, in the network architecture of AIoT services, any device capable of providing data transmission services for AIoT devices can act as a network device. For ease of description or distinction, the following description uses the first device as an example.

[0090] The reader in this application embodiment can also be a tag reader / writer, or an RFID reader / writer, or simply a reader / writer. It can be a handheld or fixed device that reads (and sometimes writes) information from electronic tags. A tag reader / writer can also be understood as a device that communicates with electronic tags. As mentioned above, its form can be a terminal or an access network device. It should be understood that a tag reader / writer can also be considered a device with read and write functions.

[0091] The first AIoT device in this application embodiment can be the source device or the target device of the AIoT service data packet. This application embodiment does not specifically limit the form of the first AIoT device.

[0092] For example, the first AIoT device can be an AIoT device, a passive tag, a semi-passive tag, an active tag, an active tag, or an Ambient IoT terminal.

[0093] For example, the first AIoT device in this application embodiment can also be an electronic tag. An electronic tag can also be called a radio frequency identification (RFID) tag, RFID, or simply a tag. RFID technology can be further divided into active, passive, and semi-active types. Passive tags can also be called passive IoT, i.e., passive Internet of Things devices, or environmental IoT terminals. Therefore, an electronic tag can also be considered a type of terminal.

[0094] Optionally, the communication system in Figure 1 also includes network devices. For example, the first device is an access network device, and the network device shown in Figure 1 is a core network device. Alternatively, the first device may be a terminal device, and the network device shown in Figure 1 may be an access network device.

[0095] It should be understood that the devices included in the communication system shown in Figure 1 are merely illustrative examples, and the embodiments of this application are not limited thereto. In fact, the communication system shown in Figure 1 may include more or fewer devices than those in Figure 1. For example, Figure 1 also includes a greater number of AIoT devices.

[0096] In Figure 1, the first AIoT device can be connected to the first device. This application embodiment does not specifically limit the form of the first device. The first device may be a relay node, an auxiliary node, a UE, or other devices. The following description is in conjunction with Figure 2.

[0097] For example, Figure 2 illustrates several possible topologies. The following describes different topologies when the first device is an access network device or a relay node, in conjunction with Figure 2.

[0098] As shown in Figure 2(1), in topology 1, the access network device provides data transmission services to AIoT devices through the wireless interface.

[0099] As shown in Figure 2(2), in topology 2, the intermediate node provides data transmission services to AIoT devices through a wireless interface. The intermediate node can communicate with access network devices through the Uu port. The difference between topology 2 and topology 1 is that data transmission between AIoT devices and access network devices can be forwarded through relay nodes.

[0100] This application does not limit the specific form of the device (such as the intermediate node shown in Figure 2(2)) that provides relay forwarding function for environmental IoT devices. For example, the intermediate node can be a UE, an integrated access and backhaul (IAB) node, a relay node, a relay node, a repeater, or other devices with relay capabilities.

[0101] As shown in Figure 2(3), in topology 3, the access network device and the assisting node communicate through the Uu port. The AIoT device can send uplink data to the access device, such as device-to-network (D2R) data. Data sent by the access network device to the AIoT device can be forwarded through the assisting node.

[0102] As shown in Figure 2 (4), the UE provides data transmission services to AIoT devices through the wireless interface. For example, the transmission channel between the UE and the AIoT device may include the physical reader-to-device channel (PRDCH) and the physical device-to-reader channel (PDRCH).

[0103] It should be understood that the PRDCH and PDRCH between the UE and the AIoT device are merely illustrative descriptions of their transmission channels. In fact, the transmission between the UE and the AIoT device is also wireless, and the transmission channel between them can also be other possible forms, which are not specifically limited in this application embodiment.

[0104] It should be noted that in the above topologies, the air interface between the first device (e.g., access network device, relay node, auxiliary node, or UE) and the AIoT device can be named AIoT air interface or AIoT air interface, or other names are not specifically limited. Furthermore, when the first device and the AIoT device transmit data through the AIoT air interface, the content transmitted from the AIoT device to the first device (e.g., data or signaling) can be collectively referred to as device-to-reader (D2R) data; and the content transmitted from the first device to the AIoT device (e.g., data or signaling) can be collectively referred to as network device-to-AIoT device (R2D) data.

[0105] For example, the first device may specify the resources used for D2R data transmission. Correspondingly, the AIoT device may send D2R data on the resources specified by the first device; and / or, the first device may indicate the resources used for R2D data and inform the AIoT device so that the AIoT device can receive the R2D data.

[0106] It should also be understood that the topology shown in Figure 2 is merely an example description, and the embodiments of this application are not limited thereto.

[0107] It should also be understood that the Uu interface mentioned above can be an air interface or wireless interface of the 3GPP protocol specifications such as LTE air interface, NR air interface, RedCap air interface, 6G air interface, etc., and this application does not limit it.

[0108] As mentioned earlier, network devices can be access network devices or core network devices. For example, core network devices can be devices with AIoT functionality, such as AIoT controllers, ambient internet of things (AIoTF) network elements, access and mobility management (AMF) network elements, application function (AF) network elements, and network exposure function (NEF) network elements.

[0109] In addition, the access network device in this application embodiment is also referred to as an access node. The access network device has wireless transceiver capabilities for communicating with terminals. Access network devices include, but are not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in Open RAN (ORAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices can also be modules or units capable of implementing some of the functions of a base station. For example, access network devices can be the central unit (CU), distributed unit (DU), CU-control plane (CP), CU-user plane (UP), or radio unit (RU) described below. In the ORAN system, CU can also be called O-CU, DU can also be called open (O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU. The access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network equipment in the communication system can be base stations of the same type or different types. Base stations can communicate with terminals or through relay stations. Terminals can communicate with multiple base stations in different access technologies. The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment.

[0110] The UE in this application embodiment can also be referred to as: terminal device, station, mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0111] A UE can be a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connectivity. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals with cloud gaming capabilities, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0112] By way of example and not limitation, in this embodiment, the UE can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large size, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function that require interaction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0113] Furthermore, in this embodiment, the UE can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0114] In this embodiment, the UE may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device, or a functional module in the terminal device that can call and execute a program.

[0115] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.

[0116] In the embodiments of this application, the communication device with access network device function can be an access network device, or a module (such as a chip, chip system, or software module) in the access network device, or a control subsystem containing access network device function. For example, a control subsystem containing access network device function can be a control center in scenarios where terminals can be applied, such as smart grids, industrial control, intelligent transportation, or smart cities.

[0117] In the embodiments of this application, the communication device with terminal functionality can be a terminal, a module within a terminal (such as a chip, chip system, modem, or software model), or a device containing terminal functionality. For ease of description, the following embodiments will use a base station or BS, and a terminal or UE as examples.

[0118] Communication between access network devices and terminal devices can follow a specific protocol layer structure. For example, this protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For instance, the control plane protocol layer structure may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer. Similarly, the user plane protocol layer structure may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer.

[0119] Figure 3 is a schematic diagram of an access network device. As an implementation example, as shown in Figure 3, the access network device may include at least one CU and at least one DU. This design can be referred to as CU and DU separation. One CU can be connected to one or more DUs. CU and DU can be separated according to the protocol layer of the wireless network: for example, the functions of the PDCP layer and above (e.g., RRC layer and SDAP layer, etc.) are set in the CU, and the functions of the protocol layers below the PDCP layer (e.g., RLC layer, MAC layer, and PHY layer, etc.) are set in the DU; or, for another example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without limitation. When the CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the PDCP layer control plane functions, and CU-UP is used to implement the SDAP layer functions and the PDCP layer user plane functions. This application does not limit the names of CU and DU. The above division of CU and DU processing functions according to the protocol layer is just one example; other methods can also be used.

[0120] The CU can be connected to the core network. Optionally, the CU can have some of the functions of the core network.

[0121] Furthermore, some functions of the DU can be separated. As shown in Figure 3, this function can be implemented by a radio unit (RU). The RU can have radio frequency (RF) functionality. This application does not limit the name of the RU. The DU and RU can be split or separated at the PHY layer. For example, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions in the PHY layer, or implement both lower-level functions and RF functions. Higher-level functions in the PHY layer include functions closer to the MAC layer, and lower-level functions in the PHY layer include functions closer to the RF layer. For example, higher-level functions in the PHY layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling, or modulation / demodulation. Lower-level functions in the PHY layer include one or more of the following: fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT), beamforming, or extraction and filtering of the physical random access channel (PRACH), etc. The RU can communicate with the terminal device via the air interface using RF signals. The pre-coding function of the PHY layer code can be located in the DU or the RU. The separation between the DU and RU can be done in various ways without restriction. An interface exists between the DU and RU. For example, depending on the separation method, the interface between the DU and RU can be a Common Public Radio Interface (CPRI) interface or an Enhanced Common Public Radio Interface (eCPRI) interface.

[0122] Optionally, any one of CU, CU-CP, CU-UP, DU, and RU can be a software module, a hardware structure, or a combination of software and hardware structures, without limitation. The different entities can exist in the same or different forms. For example, CU, CU-CP, CU-UP, and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here. These modules and the methods they execute are also within the protection scope of the embodiments of this application. For example, when the method of the embodiments of this application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0123] Currently, there is no specific solution for configuring resources for AIoT devices in the data transmission process of environmental IoT scenarios.

[0124] In view of this, embodiments of this application provide a communication method and propose a specific solution for configuring resources for AIoT devices. Specifically, this includes adding relevant information for configuring resources for the AIoT device to a first message sent from a first device to the AIoT device, so that the AIoT device can obtain the configured resource information based on the first message and realize AIoT service data transmission. Furthermore, the resource configuration method of this application embodiment can reduce the number of bits occupied by resource information, reduce overhead, help save transmission resources, and also help improve the efficiency of AIoT data transmission.

[0125] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., the first device or the first AIoT device) as examples of the execution subjects of this interaction to illustrate the method, but this application does not limit the execution subjects of the interaction. For example, the device in the illustrative flowchart (e.g., the first device or the first AIoT device) can also be a chip, chip system, or processor that supports the device in implementing the method, or it can be a logic module or software that can implement all or part of the functions of the device.

[0126] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0127] Figure 4A is an example flowchart of a communication method according to an embodiment of this application. It can be understood that the first device in Figure 4A can be the first device in Figure 1 (e.g., a reader), or it can refer to a device within the first device (e.g., a processor, chip, or chip system, etc.). For example, the first device is a gNB, or a reader, or a UE, or a gNB and a UE; or, the first device in Figure 4A can be a device providing services to the AIoT device in the topology shown in Figure 2, or it can refer to a device within the device providing services to the AIoT device (e.g., a processor, chip, or chip system, etc.). The first environment IoT AIoT device can be any AIoT device in Figure 1 or Figure 2, or it can refer to a device within the AIoT device (e.g., a processor, chip, or chip system, etc.). As shown in Figure 4A, the method includes:

[0128] Step 410: The first device sends a first message to the first AIoT device. Correspondingly, the first AIoT device receives the first message. The first message is used to configure resources for the first AIoT device, and the first message includes at least first resource type information, which is used to instruct the first AIoT device to adopt a first resource type.

[0129] It should be noted that step 410 is described using the example of configuring resources for the first AIoT device, and the embodiments of this application are not limited thereto. On the one hand, the embodiments of this application do not specifically limit the number of AIoT devices to which the first message is addressed; that is, the first message can be addressed to one or more devices, meaning that the first message includes resource information configured for multiple AIoT devices. On the other hand, when the first message is addressed to one AIoT device, the above description is only an example of the first message being addressed to the first AIoT device. If the first message is subsequently addressed to other AIoT devices, the relevant implementation method of the first AIoT device can also be referred to.

[0130] Taking the first message used to configure resources for the first AIoT device as an example, the aforementioned first resource type information is used to instruct the first AIoT device to adopt the first resource type. This application embodiment does not specifically limit the specific type of resource type configured by the first device. A detailed description follows.

[0131] Alternatively, as a possible implementation, resource types include the following three main categories:

[0132] The first type is a resource type that includes all configuration parameters in the first set of configuration parameters. The first set of configuration parameters includes one or more of the following: frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters used to indicate the amount of data to be transmitted or the size of the data packet.

[0133] The second type is a resource type that includes some of the configuration parameters in the first set of configuration parameters;

[0134] The third type is a resource type that does not include any of the configuration parameters in the first set of configuration parameters.

[0135] As can be seen, the above three categories are divided according to different sets of configuration parameters. It should be understood that the above three categories are merely examples, and the embodiments of this application are not limited thereto.

[0136] The aforementioned first set of configuration parameters can be understood as a complete set of parameters related to resource configuration. For example, the first set of configuration parameters includes frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters indicating the amount of data to be transmitted or the size of the data packet.

[0137] The frequency domain configuration parameters are used to configure the frequency domain resources related to D2R transmission. Frequency domain configuration parameters can also be defined as frequency domain information, or simply frequency domain. They indicate the location of frequency domain resources for D2R transmission. Frequency domain configuration parameters include, but are not limited to, one or more of the following: center frequency and bandwidth. The center frequency refers to the center frequency of the channel in the wireless communication system. For example, bandwidth can refer to the system bandwidth or the frequency domain width occupied by this data transmission. This application does not specifically limit the bandwidth configuration method. Optionally, the bandwidth can be directly configured or calculated using other configuration parameters, such as frequency shift factor and bit rate.

[0138] It should be noted that, for cases where bandwidth is calculated using other configuration parameters, the bandwidth included in the aforementioned frequency domain configuration parameters can also be equivalently replaced by configuration parameters used to calculate bandwidth, such as the aforementioned frequency shift factor and bit rate; after receiving the configuration parameters used to calculate bandwidth, the AIoT device can calculate the bandwidth. It is understood that the configuration parameters shown here for calculating bandwidth are merely examples, and the embodiments of this application are not limited thereto.

[0139] Time-domain configuration parameters are used to configure time-domain resources related to D2R transmission. Time-domain configuration parameters can also be defined as time-domain information, or simply time domain. They indicate the location of time-domain resources for D2R transmission. Time-domain configuration parameters include, but are not limited to, one or more of the following: the transmission start time-domain location (or start point), the transmission duration, and the transmission end time-domain location (or end point). For example, the transmission duration can refer to the duration of the D2R transmission. The transmission duration can also be calculated in other ways, such as the number of bits per symbol (or other time unit).

[0140] It should be noted that, for cases where the transmission duration is calculated using other configuration parameters, the transmission duration included in the aforementioned time-domain configuration parameters can be equivalently replaced with configuration parameters used to calculate the transmission duration, such as the number of bits per symbol. After receiving the configuration parameters used to calculate the transmission duration, the AIoT device can calculate the transmission duration. It is understood that the parameters shown here for calculating the transmission duration are merely examples, and the embodiments of this application are not limited thereto.

[0141] The transmission mode configuration parameters are used to configure the transmission mode related to D2R transmission, including but not limited to one or more of the following: error correction mode, retransmission mode, and modulation information. For example, the transmission mode configuration parameters include one or more of the following: forward error correction (FEC) mode information, repetition information, and modulation information. For instance, repetition information is used to define the granularity or unit at which data is repeated. Optionally, the modulation information is used to indicate the modulation mode and / or the corresponding modulation parameters. This application embodiment does not specifically limit the specific content of the modulation mode and / or adjustment parameters.

[0142] Optionally, the first device can flexibly adjust the transmission method based on the coverage of AIoT devices.

[0143] Optionally, the configuration parameter used to indicate the amount of data to be transmitted or the size of the data packets is the transport block size (TBS). TBS indicates the size of the data packets that the AIoT device can transmit this time. Of course, this is just an example of TBS, and TBS can also be replaced with other configuration parameters used to measure the amount of data to be transmitted or the size of the data packets.

[0144] It should be understood that the above description is merely an example of the first configuration parameter set including the aforementioned configuration parameters, and the embodiments of this application are not limited thereto. In fact, the first configuration parameter set may include more or fewer resource-related configuration parameters than those described above. Those skilled in the art can add other reasonable resource configuration parameters to the first configuration parameter set.

[0145] For clarity, the parameter examples shown in the preceding configuration parameters are not intended to limit the embodiments of this application. Those skilled in the art can replace the above parameters with other parameters that have the same or similar functions based on their function or effect.

[0146] It should be noted that the above-mentioned introduction of the first configuration parameter set is only for the convenience of describing the three major categories of resource types, and the embodiments of this application are not limited to this. In fact, in specific implementations, the "first configuration parameter set" may not be defined.

[0147] The first type mentioned above can be understood as a resource type that includes all configuration parameters in the first configuration parameter set. In some scenarios, when configuring resources for an AIoT device, the first device can use some configuration parameters from the first configuration parameter set, while the remaining configuration parameters can be predefined parameters. Based on this, a second type can be introduced on top of the first type. The second type is a resource type that includes some configuration parameters from the first configuration parameter set. The second type can have multiple implementation methods.

[0148] One implementation involves a second type of resource type that includes basic configuration parameters. For example, the basic configuration parameters include time-domain configuration parameters, transmission mode configuration parameters, and configuration parameters indicating the amount of data to be transmitted or the size of the data packets.

[0149] Another implementation, the second type, is a resource type that includes configuration parameters with reuse indication information. The reuse indication information is used to instruct the AIoT device to use predefined configuration parameters. This application does not specifically limit which configuration parameters are predefined. For example, the transmission mode configuration parameter is predefined as FEC configuration; the first AIoT device uses the predefined FEC configuration to transmit AIoT service data when transmitting D2R.

[0150] For clarity, the specific implementation of "predefined" can include any of the following: protocol predefined, manufacturer-specified, operator-defined, pre-installed in the communication equipment at the time of manufacture, or agreed upon in advance through other conventions. Another implementation, the second type, includes resource types that include parameters to be updated or parameters that have changed. For example, configuration parameters included in the second type include M, transmission duration, TBS, etc.

[0151] Another implementation involves a second type of resource that includes a minimum set of configuration parameters. For example, the configuration parameters included in this second type could be TBS, etc.

[0152] It should be understood that the above examples of the second type are merely illustrative descriptions, and the embodiments of this application are not limited thereto.

[0153] The third type mentioned above is a resource type that does not include any configuration parameters. For example, the third type is represented as NA.

[0154] It should be noted here that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, technical terms may change as technology evolves, and other technical terms may also apply to this application if their technical meanings remain the same.

[0155] This application does not specifically limit the message body format of the first message. Furthermore, it does not specifically limit the number of bits occupied by the resource type and / or resource information included in the first message. For example, the first resource type information included in the first message occupies 2 bits.

[0156] In this embodiment, the first message is used to configure resources for the AIoT device. This embodiment does not limit the message body format and / or message type of the first message. Optionally, the first message is a reader-to-device (R2D) message.

[0157] For example, Figure 4B shows an example message structure of a first message according to an embodiment of this application. The first message is an R2D message. As shown in Figure 4B, the R2D message includes at least a MAC header and a resource configuration field (or resource configuration domain). The resource configuration field is used to implement resource configuration for AIoT devices. It should be understood that Figure 4B describes the resource configuration field as an example located after the MAC header, and the embodiments of this application are not limited thereto. For example, the resource configuration field may also be located in the MAC header, or in the control domain, or in the payload domain, or in the MAC subheader, or it may be a separate media access control element (MAC CE). For another example, the resource configuration field may also be located in the MT field of the MAC header.

[0158] It should also be understood that the resource configuration field is introduced only for the convenience of description, and in fact, this concept may not exist. That is, the resource configuration field in Figure 4B can be replaced by the content below it (such as resource type information).

[0159] The MAC header is the header field of the R2D message. The MAC header includes a message type (MT) field and / or a length field.

[0160] For example, the length field is used to indicate the length of R2D data, or to indicate the length of the message body in an R2D message excluding the padding field. In one possible implementation, the length field can be used to define the length of the data.

[0161] As shown in Figure 4B, the resource configuration field includes at least resource type information (such as the aforementioned first resource type information). This application embodiment does not specifically limit the location of the resource configuration field.

[0162] Optionally, the resource configuration field may also include resource information. This resource information corresponds to the resource type information mentioned above. In other words, the resource type corresponding to this resource information is the resource type indicated by the aforementioned resource type information. For example, if the resource type information indicates that the resource type is type one, then the resource information includes the configuration parameters corresponding to type one.

[0163] Optionally, the resource configuration field also includes an SRB indicator. The SRB indicator is used to indicate the number of bits successfully received by the first device. For example, the reader notifies the AIoT device of the number of bits it has received, so that the AIoT device can confirm or know the number of bits successfully received by the reader. For example, in a scenario of segmented data transmission, the first device can simultaneously inform the AIoT device of the number of bits successfully received via SRB when allocating resources, which helps the AIoT device understand the progress of AIoT data transmission. It should be noted that Figure 4B shows the SRB indicator located within the resource configuration field, but the embodiments of this application are not limited to this. For example, the SRB indicator can also be located in other positions outside the resource configuration field shown in Figure 4B. Or, for example, the SRB indicator and the resource configuration field are not in the same message.

[0164] This application does not impose a specific limitation on the number of bits occupied by resource configuration fields in a message (such as the first message).

[0165] Optionally, the R2D message shown in Figure 4B may also include R2D data. For example, the R2D data may be a MAC PDU.

[0166] Optionally, the R2D message shown in Figure 4B also includes a padding field. It should be understood that Figure 4B is described using the example of the resource configuration field being located at the MAC layer, and the embodiments of this application are not limited to this. For example, when the resource configuration field is located at a non-MAC layer or in other messages, the message body structure shown in Figure 4B does not include a MAC header.

[0167] It is hereby noted that the content of the dashed box portion included in the message body shown in the various figures of this application (Figures 4B to 11) may be optional.

[0168] For the first AIoT device, after receiving the first message, it can determine the corresponding resource type based on the first resource type information included in the first message, and construct a D2R data packet for AIoT data transmission.

[0169] It should be noted that the above lists various implementation methods for resource types. This application does not limit the application scenario to a particular resource type. For example, in practical applications, when the first device initially configures resources, it can configure resources of the first type, i.e., the entire set of the first configuration parameter set; when updating one or more configuration parameters subsequently, it can issue the corresponding configuration parameters that need to be updated, i.e., it does not need to issue all configuration parameters. In this way, the AIoT device updates the corresponding configuration parameters based on the configuration parameters that need to be updated issued by the first device. The methods for updating configuration parameters include, but are not limited to: directly replacing the value of the configuration parameter, or performing further calculations based on the issued configuration parameters. For example, the configuration parameters that need to be updated issued by the first device include a transmission duration parameter; the AIoT device changes the transmission duration based on the time point when it receives the configuration parameters that need to be updated, thereby using the latest transmission duration for AIoT data transmission.

[0170] Step 420: The first AIoT device sends a second message to the first device. Correspondingly, the first device receives the second message. The second message is determined at least based on the first resource type.

[0171] Similarly, the message body format and / or message type of the second message in this application embodiment are not limited. Optionally, the second message is a device-to-reader (D2R) message.

[0172] The aforementioned second message is determined by the first AIoT device based on the first resource type. Optionally, if the first message includes other configuration content, the second message can also be determined by the first AIoT device based on other content included in the first message. For example, the second message is a D2R data packet; the first AIoT device generates and sends a D2R data packet based on the first message. Alternatively, the second message may be a D2R message or a D2R data packet; the first AIoT device determines the corresponding resource information based on the content included in the first message and sends the D2R message or D2R data packet according to that resource information.

[0173] For example, when the first resource type is the aforementioned first type, the first message also includes corresponding resource information (all configuration parameters in the first configuration parameter set). The first AIoT device determines the corresponding resource information based on the content of the resource information included in the first message, and sends the second message based on the resource information.

[0174] For example, when the resource type is the aforementioned second type, the first message also includes corresponding resource information (partial configuration parameters in the first configuration parameter set). The first AIoT device determines the corresponding resource information based on the content of the resource information included in the first message and the stored resource information set, and sends the second message based on the resource information. The stored resource information includes, but is not limited to, one or more of the following: resource information used in the last message or data transmission, and resource information used in sending message 1 (MSG1) or message 3 (MSG3).

[0175] For example, when the first resource type is the aforementioned third type, i.e., the first message does not carry any resource information, the first AIoT device sends the second message using stored resource information, or sends the second message using predefined resource information. The description of the stored resource information can be found above and will not be repeated here. Alternatively, when the first resource type is the aforementioned third type, the first AIoT device does not send the second message.

[0176] For example, the first device sends an R2D message, which is used to allocate transmission resources for D2R data and / or D2R messages.

[0177] It should be noted that the embodiments in this application are described using the example of R2D messages including transmission resources for D2R, and the embodiments in this application are not limited to this. For example, R2D messages can also include transmission resources for R2D. That is, the various implementations of R2D messages including transmission resources for D2R described in the embodiments of this application (such as the design of the message body, the content included in the R2D message) can also be equivalently replaced by R2D messages including transmission resources for R2D.

[0178] In this embodiment of the application, for AIoT data transmission, the first device sends a first message, which is used to configure resources for one or more AIoT devices (including at least the first AIoT device), so that the first AIoT device can obtain the corresponding resource configuration parameters based on the first message, and then use the configured resources to transmit A-IoT data.

[0179] This application does not limit the effective duration of the first message or the applicable number of transmissions. Optionally, in one implementation, the first device can send a first message once, corresponding to the sending of multiple second messages; that is, the resource configuration information used by each of the multiple second messages subsequently sent by the AIoT device can be obtained from the most recent first message; or, in other words, when the AIoT device does not receive a new first message, the AIoT device can use the most recently received first message to obtain the resource configuration information.

[0180] The first message shown in Figure 4B above can be understood as being directed to a single AIoT device, meaning it includes the resource configuration information of that AIoT device. Furthermore, the first message can also be directed to multiple different AIoT devices. For example, as shown in Figure 5A, the first device is a reader / writer, and the first message sent by the reader / writer can be received by N AIoT devices; the first message includes the resource configuration information of all N AIoT devices.

[0181] For example, in an inventory + command scenario of environmental IoT, after receiving feedback information about inventory from an AIoT device, the reader sends a command message specifically to the AIoT device. This command message is addressed to the AIoT device that sent the feedback. If multiple AIoT devices have sent feedback information to the reader, the reader will send a command message to all of them. That is, all AIoT devices receive the same command message from the reader. In this scenario, the command message may include resource configuration information for all AIoT devices.

[0182] It should be understood that this description is merely an example of using a command message as the first message, or in other words, the above scenario is only an example description, and the embodiments of this application are not limited thereto.

[0183] When the first message is addressed to multiple AIoT devices, the message body structure of the first message may have several different implementations. The following describes each implementation in detail with reference to the message body structures shown in Figures 5B to 10.

[0184] Optionally, the first message is used to configure resources for multiple AIoT devices; the multiple AIoT devices include at least the aforementioned first AIoT device and second AIoT device; the first message also includes first resource information and second resource information, the first resource information being resource information configured for the first AIoT device, and the second resource information being resource information configured for the second AIoT device.

[0185] In other words, the first message includes resource configuration information for multiple AIoT devices. The resource type corresponding to the resource information of each AIoT device can be the same or different resource types; there is no specific limitation on this. Alternatively, in the resource configuration information of multiple AIoT devices, some AIoT devices may have resource information corresponding to the same resource type, while others may have resource information corresponding to different resource types. Compared to configuring the resource information of one AIoT device at a time, the first message in this embodiment supports configuring the resource information of multiple AIoT devices at once, further reducing the number of messages used for resource configuration (such as R2D messages), thereby greatly reducing the overhead of resource information configuration and improving the efficiency of AIoT service data transmission.

[0186] When the first message includes resource configuration information for multiple AIoT devices, the resource information corresponding to each AIoT device can be distinguished by introducing device identification information. Taking the multiple AIoT devices as an example, which includes at least a first AIoT device and a second AIoT device, the first message may further optionally include: device identification information of the first AIoT device, and / or, device identification information of the second AIoT device.

[0187] The device identification information in this application embodiment serves to indicate the object of data transmission or the object of resource allocation, that is, to identify the AIoT device to which resources are to be allocated, so as to ensure that the AIoT device corresponding to the device identification uses the resources allocated by the first device for data transmission during subsequent data transmission. This application embodiment does not specifically limit the naming or specific implementation of the device identification information. For example, the device identification can be represented as an access identifier (AS ID), a group identifier, or an access layer identifier.

[0188] The following describes the message body structure of the first message, taking as an example multiple AIoT devices, including at least the first AIoT device and the second AIoT device.

[0189] In scenario A, if the first message also includes first resource information and second resource information, the resource type corresponding to both the second resource information and the first resource information is the first resource type.

[0190] In other words, the first resource information configured by the first device for the first AIoT device and the second resource information configured for the second AIoT device correspond to the same resource type.

[0191] For case A, the embodiments of this application do not limit the resource type information to the domain where the first message body is located.

[0192] Optionally, as one implementation, the first resource type information is located in the first field of the first message, and the first resource information and the second resource information are located in the second field of the first message; wherein the first field and the second field are located in different parts of the first message; or, the first field and the second field are both located in the header of the first message, or both are located in the control field of the first message, or both are located in the payload field of the first message, or both are located in the sub-header portion of the first message.

[0193] Alternatively, as one implementation, the first field and the second field described above are located in the Layer 1 control field and the Layer 2 data packet, respectively. That is, the resource type is contained in Layer 1 (e.g., the control field and / or command field), while the resource information can be contained in the Layer 2 data packet (e.g., the MAC layer). The advantage of this is that the resource type can be resolved more quickly, improving data transmission efficiency.

[0194] Optionally, the first message may also include one or more of the following: device quantity information, resource quantity information, and successful reception bit SRB information. The device quantity information indicates the total number of AIoT devices to which the first message is addressed. The resource quantity information indicates the total number of resources included in the first message.

[0195] For example, Figure 5B shows a message body structure example when the resource types are the same. As shown in Figure 5B, the first message includes at least a MAC header and a resource configuration field. Optionally, the first message also includes R2D data. Optionally, the first message also includes a padding field. For an explanation of each part, please refer to Figure 4B above; for simplicity, it will not be repeated here.

[0196] Compared to Figure 4B, the first message in Figure 5B includes resource information for N AIoT devices, and the resource information for all N AIoT devices uses the same resource type. N is an integer greater than or equal to 2. Each AIoT device has a corresponding index and resource information. Optionally, each AIoT device also has corresponding SRB information. An explanation of SRB information can be found above and will not be repeated here. As can be seen, Figure 5B only includes a single resource type information element to indicate the resource types of N AIoT devices. This minimizes bit usage and saves overhead.

[0197] In the message body structure shown in Figure 5B, the resource type and multiple resource information items reside in the same field. This application embodiment does not specifically limit the field in which the resource type resides. Optionally, the resource type and multiple resource information items can also reside in different fields. The following description is in conjunction with Figure 5C.

[0198] For example, Figure 5C shows a message body structure example when the resource types are the same. Compared to Figure 5B, in Figure 5C, the resource type information is located in the MAC header, while the resource-related information of the N AIoT devices (including index information, resource information; optionally, also including SRB information) is located in a field after the MAC header.

[0199] For clarity, Figures 5B to 10 illustrate how each AIoT device's resource-related information includes its own SRB (or each set of resource data includes one SRB). However, the embodiments in this application are not limited to this. Optionally, each set of resource data may include an SRB; alternatively, multiple sets of resource data (or multiple sets of resource-related information from multiple AIoT devices) may correspond to the same SRB. In the case of multiple sets of resource data corresponding to the same SRB, if the resource types of the multiple sets of resource data are also the same, then the SRB information and the resource type can be located in the same domain as a common part. This common part can also be called a common domain, and the information included in the common domain can be applicable to N AIoT devices.

[0200] The following describes an example of a message body that includes a resource type and a first quantity in the first message, with reference to Figures 6A and 6B. The first quantity can be the number of resource information (e.g., represented as "num of resource") or the number of AIoT devices (e.g., represented as "num of device").

[0201] As shown in Figure 6A, the difference from Figure 5B is that a first quantity is added to the first message shown in Figure 6A. The first quantity can be the number of AIoT devices to which the first message is addressed; or it can be the number of resource information items configured in the first message. This application embodiment does not specifically limit the domain in which the first quantity resides. For example, the first quantity can be in the same domain as resource type information and resource information. Or, for example, the first quantity and resource type information can be located in the MAC header.

[0202] It should be noted that the embodiments of this application do not limit the order of the first quantity and resource type in the message body. The message body formats involving the first quantity and resource type in the various figures of this application, and the order of the first quantity and resource type shown, are merely examples and do not constitute a limitation on the embodiments of this application. For example, the first quantity can be before or after the resource type field.

[0203] As shown in Figure 6B, the difference from Figure 6A is that the first quantity and resource type information are located in the MAC header. It should be understood that the embodiments of this application do not limit the order of the first quantity and resource type information in the MAC header; the order in Figure 6B is merely an example.

[0204] It should also be understood that the fields containing the first quantity in Figures 6A and 6B are merely exemplary descriptions, and the embodiments of this application are not limited thereto. For example, the first quantity may also be located in the length field of the MAC header; or, it may be located in the MT field of the MAC header.

[0205] It should also be understood that the first quantity in Figures 6A and 6B can be replaced by two information cells, which are used to indicate the number of devices and the number of resources, respectively. Furthermore, there is no specific limitation as to whether these two information cells are located in the same field. For example, the information cell indicating the number of devices may be located in the MAC header, and the information cell indicating the number of resources may be located in the resource configuration field.

[0206] It is hereby noted that the illustrations of the message body structure provided in the embodiments of this application are merely exemplary descriptions, and the embodiments of this application are not limited thereto.

[0207] In Scenario B, if the first message also includes first resource information and second resource information, the first message further includes second resource type information, which is used to instruct the second AIoT device to adopt the second resource type; wherein, the first resource type information is used to instruct the first AIoT device to adopt the first resource type; and the second resource type is different from the first resource type.

[0208] In other words, the first resource information configured by the first device for the first AIoT device and the second resource information configured for the second AIoT device correspond to different resource types.

[0209] For scenario B, the first message may include resource type information for each AIoT device and resource information corresponding to that resource type. Furthermore, this application embodiment does not limit the domain or message structure of the resource-related information for multiple AIoT devices in the first message.

[0210] Optionally, as a possible implementation, the first resource type information and the first resource information are located in the third domain as a first group of resource information; the second resource type information and the second resource information are located in the third domain as a second group of resource information; wherein, the third domain is located in the header of the first message, or in the control domain of the first message, or in the payload domain of the first message, or in the subheader portion of the first message, or in the layer 1 control domain.

[0211] For example, Figure 7A shows a message body structure example when the resource types are different. As shown in Figure 7A, the first message includes at least a resource configuration field. Optionally, the first message also includes a MAC header and R2D data. Optionally, the first message also includes a padding field. For an explanation of each part, please refer to Figure 4B above; for simplicity, it will not be repeated here.

[0212] Compared to Figure 5B, the first message shown in Figure 7A includes resource information for N AIoT devices, and the resource information for the N AIoT devices can adopt different resource types. The first message also includes resource type information for each AIoT device. Alternatively, it can be understood that the first message shown in Figure 7A includes N sets of resource information, each set of resource information corresponding to one AIoT device, and includes the following information: index, resource type, and resource information. Optionally, each set of resource information also includes an SRB. Taking the first set of resource information as an example, the first set of resource information includes at least: resource type 1, index 1, resource information, and SRB. It should be understood that the order of the various information fields included in each set of resource information shown in Figure 7A is only an example, and the embodiments of this application are not limited thereto.

[0213] Optionally, the device identification information of the first AIoT device is located in the first group of resource information; the first group of resource information also includes first successfully received bit (SRB) information; and / or, the device identification information of the second AIoT device is located in the second group of resource information, and the second group of resource information also includes second SRB information. For example, each group of resource information in Figure 7A or Figure 7B includes SRB information. It should be noted that the embodiments of this application do not limit the order of the fields included in each group of resource information; the order shown in the figures is only an example description.

[0214] Alternatively, even if the resource information of multiple AIoT devices corresponds to different resource types, the first message can still include a first quantity (number of devices or number of resources). For example, in the message body structure shown in Figure 7B, the first quantity is located in the MAC header. A description of the first quantity can be found above; for brevity, it will not be repeated here.

[0215] Scenario A and Scenario B above can be implemented independently or in combination. In the case of combined implementation, the first message includes both resource configurations for multiple AIoT devices with the same resource type and resource configurations for multiple AIoT devices with different resource types. This is described below with reference to Figures 8A and 8B.

[0216] As shown in Figure 8A, the first message includes resource configurations for M AIoT devices with the same resource type; it also includes resource configurations for H AIoT devices with different resource types. For resource configurations with the same resource type, the domain or design method in which the resource type and corresponding resource information are located in the first message can be referred to the description of case A above. For resource configurations with different resource types, the domain or design method in which the resource type and corresponding resource information are located in the first message can be referred to the description of case B above.

[0217] Further optionally, as shown in Figure 8B, for resource configurations with the same resource type for M AIoT devices, the first message also includes a second quantity. This second quantity can represent the number of devices (M AIoT devices) or the number of resources (M AIoT devices). The value of the second quantity is M. Optionally, the MAC header in Figure 8B may also include a third quantity, which can be M+H, i.e., the total number of AIoT devices addressed in the first message, or the number of resources (M+H) of the AIoT devices addressed in the first message. This application embodiment does not limit the value of M or H.

[0218] It is understood that the message body structure shown in Figure 8A or Figure 8B is merely an exemplary description, and the embodiments of this application are not limited thereto.

[0219] In all the implementations described above, the first message can include the device identifier of the AIoT device, regardless of the specific implementation. This application does not specifically limit the specific form or determination method of the device identifier. Optionally, the device identifier of the AIoT device can be a device identifier assigned by the first device, an identifier of the resource corresponding to the AIoT device, frequency domain numbering information corresponding to the AIoT device, time domain numbering information corresponding to the AIoT device, the number (or index) of the device specified by the first device within a group of devices, or a group identifier. For example, the index in the previous illustration can be understood as the device identifier of the AIoT device. Taking the device identifier as an AS ID as an example, the length of the AS ID can vary. Therefore, an information element indicating the length of the AS ID can be introduced in the first message.

[0220] Optionally, as a possible implementation, the first message may also include length information. The length information refers to the length of the AS-ID.

[0221] For example, the length of the AS ID can be indicated by a 4-bit indicator; the 4-bit indicator can indicate an AS ID with a maximum length of 16 bits. That is, the value of the 4-bit indicator is used to indicate the length of the AS ID of each AIoT device, so as to distinguish different AIoT devices and thus achieve the purpose of distinguishing the resource information of different AIoT devices.

[0222] For example, the length of an AS ID can be implemented through AS-ID length indication information. For instance, the first AS-ID type occupies 16 bits; the second AS-ID type occupies 8 bits; the third AS-ID type occupies 2 bits, and so on.

[0223] Taking the AS-ID length indicator information that occupies 2 bits as an example, the values ​​are 00, 01, 10, and 11, representing different bit lengths, that is, it supports 4 AS ID lengths.

[0224] It should be understood that the above examples (number of bits occupied, examples of AS-ID types) are merely illustrative descriptions, and the embodiments of this application are not limited thereto.

[0225] Alternatively, as one possible implementation, the first message may also include allocation type information. Allocation type information refers to the allocation type of the AS-ID. The specific type of the AS-ID may depend on the allocation type information.

[0226] For example, the AS-ID allocation type includes a first allocation type and a second allocation type; the first allocation type reuses the random number RN16, which is 16 bits in length; the second allocation type is an allocated identifier (i.e., instead of reusing RN16, a newly allocated identifier is used). These two allocation types can be indicated by a 1-bit type indication information.

[0227] It is understood that different AIoT devices can use different length information or the same length information; there is no specific limitation on this. Similarly, different AIoT devices can use different AS-ID allocation types or the same AS-ID allocation type; there is no specific limitation on this.

[0228] To further reduce redundant bits, the length information or AS-ID allocation type can be made independent of each group of resource information when using the same length information or the same AS-ID allocation type; that is, it is not necessary to include it in each group of resource information. Figures 9A to 9C show examples of different message body structures.

[0229] As shown in Figure 9A, the resource configuration field in the first message includes resource information for n AS-IDs (corresponding to n AIoT devices), and the n AS-IDs use the same AS-ID length information or allocation type information. The AS-ID length information or allocation type information is located in the position illustrated in Figure 9A. Furthermore, the resource information for the n AIoT devices uses the same resource type, and Figure 9A also shows the resource type information. Furthermore, Figure 9A also shows the resource quantity information. It should be understood that the positions of the resource type information, resource quantity information, and AS-ID length information or allocation type information in Figure 9A are merely examples, and the positions of these three information elements can be adjusted accordingly; this is not a limitation.

[0230] The difference between Figure 9B and Figure 9A is that the AS-ID length information or allocation type information is located in the MAC header, while the resource type information, resource quantity information, and n sets of resource information are located in the resource configuration field.

[0231] The difference between Figure 9C and Figure 9A is that the resource type information, resource quantity information, and AS-ID length information or allocation type information are all located in the MAC header, while the n sets of resource information are located in the resource configuration field. Optionally, each set of resource information includes AS ID, resource information, and SRB.

[0232] It should be understood that the examples shown in Figures 9A to 9C are merely illustrative descriptions, and the embodiments of this application are not limited thereto.

[0233] Alternatively, as one possible implementation, the device identifier length of the first AIoT device is a first length information, the device identifier length of the second AIoT device is a second length information, and the first message further includes the first length information and the second length information; or, the allocation type of the device identifier of the first AIoT device is a first allocation type, the allocation type of the device identifier of the second AIoT device is a second allocation type, and the first message further includes the first allocation type and the second allocation type.

[0234] In other words, each AIoT device has a different device identifier length, or each AIoT device has a different allocation type. In this case, for each AIoT device, its corresponding length information or allocation information can be included. As shown in Figure 10, the index of each AIoT device can include AS-ID length information or allocation type information, as well as the AS-ID.

[0235] Introducing the device identifier length information or allocation type of the AIoT device in the first message helps to correctly identify the specific AIoT device. This allows the AIoT device to parse only its own data packets, achieving more accurate data packet parsing and improving parsing efficiency; it also reduces unnecessary data packet parsing of non-target devices, thereby helping to reduce unnecessary energy consumption and save power for the AIoT device.

[0236] In some embodiments, the first message further includes first indication information, which indicates whether the first message includes a data field. Adding the first indication information to the first message assists the AIoT device in determining whether a data field is included.

[0237] This application does not limit the specific implementation of the first indication information. The "first indication information is used to indicate whether the first message includes a data field" can be indicated explicitly or implicitly.

[0238] Optionally, the first indication information is data field indication information; or, the first indication information is a successful reception bit (SRB) indication; or, the first indication information is a data length indication.

[0239] As one possible implementation, the first indication information is a data indicator (DI) information (or data field indicator). Different values ​​of DI indicate whether a data portion is carried. For example, a DI value of 0 indicates that the first message does not carry a data portion; a DI value of 1 indicates that the first message carries a data portion. It should be understood that the meaning represented by the DI value here is merely an exemplary description, and the embodiments of this application are not limited thereto.

[0240] When data indication information is introduced, the embodiments of this application do not limit the position of the data indication information in the first message. Figure 11 illustrates three possible scenarios for the data indication information. As shown in Figure 11, the data indication information can be independent of the resource configuration field, for example, located after the resource configuration field; or, the data indication information can also be located within the resource configuration field; or, the data indication information can also be located in the MAC header, for example, after the length field in the MAC header.

[0241] It should be understood that the various situations shown in Figure 11 are merely exemplary, and the embodiments of this application are not limited thereto. For example, data indication information may also be located in other reasonable locations within the first message.

[0242] As another possible implementation, the first indication information is an SRB indication, that is, indirectly indicating whether to carry a data portion by multiplexing the SRB. Optionally, the value of the SRB indicates whether to carry a data portion. For example, if the value of the SRB is 0, it means that the first device has not received any field or has not successfully received any bits, thus indicating that a data portion is carried; if the value of the SRB is non-zero, it means that no data portion is carried. It should be understood that the meaning represented by the value of the SRB here is only an exemplary description, and the embodiments of this application are not limited thereto.

[0243] As another possible implementation, the first indication information is a data length indicator, which defines the data length by reusing the length in the MAC header field, thereby indicating whether a data portion is carried. Optionally, the value of L can be used to indicate whether a data portion is carried. For example, if L is 0, it means the data length is 0, indicating that no data portion is carried; if L is non-zero, it means the data length is non-zero, indicating that a data portion is carried.

[0244] It should be noted that the implementation method of the first instruction information can be independent of the aforementioned implementation methods of resource allocation information, or it can be combined with the aforementioned implementation methods of resource allocation information. No specific limitation is made in this regard.

[0245] Figure 12 illustrates another communication method according to an embodiment of this application. It should be understood that the method shown in Figure 12 can be implemented independently or in combination with other methods, and there is no specific limitation thereto. As shown in Figure 12, it includes at least the following steps:

[0246] Step 1201: The first device sends a third message to the first AIoT device. Correspondingly, the first AIoT device receives the third message. The third message includes at least data indication information, which is used to indicate whether a data field is carried.

[0247] For details on the various implementation methods of data indication information, please refer to the previous description. For the sake of brevity, they will not be repeated here.

[0248] Step 1202: The first AIoT device determines whether the third message includes a data field based on the data indication information.

[0249] In this embodiment, by introducing data indication information, which can be implemented by directly introducing indication information or by reusing the length field or SRB, the AIoT device can determine whether the R2D message includes a data field part, thereby reducing the occupation of the MT field in the R2D message and saving the number of bits of the MT field.

[0250] For clarity, the message body formats shown in Figures 4B to 11 of this application are exemplary descriptions, and the embodiments of this application are not limited thereto. For example, the order of the various fields included in the message body may be other sorting methods. Furthermore, the message body may include more or fewer fields than shown in the figures.

[0251] It should be understood that the flowcharts, scene diagrams, or message structure examples shown in Figures 1 to 12 are for ease of understanding only and are not intended to limit the embodiments of this application to the examples shown. In fact, those skilled in the art can make equivalent transformations based on the examples in Figures 1 to 12 to obtain more implementation methods.

[0252] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 1 to 12. The device embodiments of this application will be described in detail below with reference to Figures 13 and 14. It should be understood that the communication device of the embodiments of this application can execute the various communication methods of the foregoing embodiments of this application; that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0253] In the embodiments described above, the first AIoT device may execute some or all of the steps in each embodiment; the first device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations of various operations. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0254] Figure 13 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 13, the communication device 1300 may include a communication module 1320. The communication module 1320 can implement corresponding communication functions, which can be internal communication functions of the communication device 1300 or communication functions between the communication device 1300 and other devices. Optionally, the communication module 1320 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 1300 further includes a processing module 1310. The processing module 1310 can implement corresponding processing functions.

[0255] Optionally, the communication device 1300 further includes a storage module, which can be used to store instructions and / or data; the processing module 1310 can read the instructions and / or data in the storage module so that the communication device 1300 can implement the aforementioned method embodiments.

[0256] In one possible design, the communication device 1300 may correspond to the first AIoT device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the first AIoT device. The communication device 1300 may be used to perform the steps or processes performed by the first AIoT device in any of the above method embodiments.

[0257] In one possible design, the communication module 1320 is used to receive a first message from a first device, the first message being used to configure resources for a first environment Internet of Things (AIoT) device, the first message including at least first resource type information, the first resource type information being used to instruct the first AIoT device to adopt a first resource type;

[0258] The communication module 1320 is further configured to send a second message to the first device, the second message being determined at least based on the first resource type.

[0259] Optionally, the processing module 1310 is configured to determine the second message based on the first message.

[0260] Optionally, as an embodiment, the first resource type is any one of the following resource types:

[0261] The first type is a resource type that includes all configuration parameters in the first configuration parameter set, and the first configuration parameter set includes one or more of the following: frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters used to indicate the amount of data to be transmitted or the size of the data packet.

[0262] The second type is a resource type that includes some configuration parameters from the first set of configuration parameters;

[0263] The third type is a resource type that does not include any of the configuration parameters in the first set of configuration parameters.

[0264] Optionally, as an embodiment, the first message may further include resource information; the resource type corresponding to the resource information is the first resource type.

[0265] Optionally, as an embodiment, the first message is used to configure resources for multiple AIoT devices; the multiple AIoT devices include at least the first AIoT device and the second AIoT device;

[0266] The first message also includes first resource information and second resource information, wherein the first resource information is resource information configured for the first AIoT device and the second resource information is resource information configured for the second AIoT device.

[0267] Optionally, as an embodiment, the first message may further include: device identification information of the first AIoT device, and / or, device identification information of the second AIoT device.

[0268] Optionally, as an embodiment, the resource type corresponding to both the second resource information and the first resource information is the first resource type.

[0269] Optionally, as an embodiment, the first resource type information is located in the first field of the first message, and the first resource information and the second resource information are located in the second field of the first message;

[0270] Wherein, the first field and the second field are located in different parts of the first message; or, the first field and the second field are both located in the header of the first message, or both are located in the control field of the first message, or both are located in the payload field of the first message, or both are located in the subheader portion of the first message;

[0271] Alternatively, the first domain and the second domain may be located in the Layer 1 control domain and the Layer 2 data packet, respectively.

[0272] Optionally, as an embodiment, the first message may further include one or more of the following: device quantity information, resource quantity information, and successfully received bit SRB information.

[0273] Optionally, as an embodiment, the device quantity information and the resource quantity information are located in a first domain.

[0274] Optionally, as an embodiment, the first message further includes second resource type information, which is used to indicate that the second AIoT device adopts a second resource type;

[0275] The first resource type information is used to indicate that the first AIoT device adopts a first resource type; the second resource type is different from the first resource type.

[0276] Optionally, as an embodiment, the first resource type information and the first resource information are located in the third domain as a first group of resource information; the second resource type information and the second resource information are located in the third domain as a second group of resource information; wherein, the third domain is located in the header of the first message, or in the control domain of the first message, or in the payload domain of the first message, or in the sub-header portion of the first message, or in the layer 1 control domain.

[0277] Optionally, as an embodiment, the device identification information of the first AIoT device is located in the first group of resource information; the first group of resource information also includes first successfully received bit (SRB) information; and / or, the device identification information of the second AIoT device is located in the second group of resource information, and the second group of resource information also includes second SRB information.

[0278] Optionally, as an embodiment, the first message may further include device identifier length information; or, the first message may further include allocation type information.

[0279] Optionally, as an embodiment, the device identifier length of the first AIoT device is a first length information, the device identifier length of the second AIoT device is a second length information, and the first message further includes the first length information and the second length information; or, the allocation type of the device identifier of the first AIoT device is a first allocation type, the allocation type of the device identifier of the second AIoT device is a second allocation type, and the first message further includes the first allocation type and the second allocation type.

[0280] Optionally, as an embodiment, the first message further includes first indication information; the first indication information is used to indicate whether the first message includes a data field.

[0281] Optionally, as an embodiment, the first indication information is data field indication information; or, the first indication information is a successful reception bit (SRB) indication; or, the first indication information is a data length indication.

[0282] Optionally, as an embodiment, the first message is a reader-to-device R2D message; the second message is a device-to-reader D2R message.

[0283] It should be understood that the communication device 1300 may correspond to the first AIoT device in Figures 1 to 12 according to the embodiments of this application; the communication device 1300 may include modules or units for executing the methods performed by the first AIoT device in Figures 1 to 12. Furthermore, each module in the communication device 1300 and the other operations and / or functions described above are respectively for implementing the corresponding processes of Figures 1 to 12.

[0284] It should also be understood that when the communication device 1300 is the first AIoT device, the processing module 1310 in the communication device 1300 can be implemented by at least one processor, for example, it can correspond to the processor 1410 in the communication device 1400 shown in FIG. 14. For example, the communication module 1320 can correspond to the communication interface 1420 in the communication device 1400 shown in FIG. 14.

[0285] It should also be understood that when the communication device 1300 is a chip or chip system configured in the first AIoT device, the processing module 1310 of the communication device 1300 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0286] Alternatively, in one possible design, the communication device 1300 may correspond to the first device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the first device. The communication device 1300 may be used to perform the steps or processes performed by the first device in any of the above method embodiments.

[0287] In one possible design, the communication module 1320 is used to send a first message, the first message being used to configure resources for an environmental Internet of Things (AIoT) device, the first message including at least first resource type information, the first resource type information being used to instruct the AIoT device to adopt a first resource type;

[0288] The communication module 1320 is further configured to receive a second message, the second message being determined at least based on the first resource type.

[0289] Optionally, as an embodiment, the first resource type is any one of the following resource types:

[0290] The first type is a resource type that includes all configuration parameters in the first configuration parameter set, and the first configuration parameter set includes one or more of the following: frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters used to indicate the amount of data to be transmitted or the size of the data packet.

[0291] The second type is a resource type that includes some configuration parameters from the first set of configuration parameters;

[0292] The third type is a resource type that does not include any of the configuration parameters in the first set of configuration parameters.

[0293] Optionally, as an embodiment, the first message may further include resource information; the resource type corresponding to the resource information is the first resource type.

[0294] Optionally, as an embodiment, the first message is used to configure resources for multiple AIoT devices; the multiple AIoT devices include at least the first AIoT device and the second AIoT device;

[0295] The first message also includes first resource information and second resource information, wherein the first resource information is resource information configured for the first AIoT device and the second resource information is resource information configured for the second AIoT device.

[0296] Optionally, as an embodiment, the first message may further include: device identification information of the first AIoT device, and / or, device identification information of the second AIoT device.

[0297] Optionally, as an embodiment, the resource type corresponding to both the second resource information and the first resource information is the first resource type.

[0298] Optionally, as an embodiment, the first resource type information is located in the first field of the first message, and the first resource information and the second resource information are located in the second field of the first message;

[0299] Wherein, the first field and the second field are located in different parts of the first message; or, the first field and the second field are both located in the header of the first message, or both are located in the control field of the first message, or both are located in the payload field of the first message, or both are located in the subheader portion of the first message;

[0300] Alternatively, the first domain and the second domain may be located in the Layer 1 control domain and the Layer 2 data packet, respectively.

[0301] Optionally, as an embodiment, the first message may further include one or more of the following: device quantity information, resource quantity information, and successfully received bit SRB information.

[0302] Optionally, as an embodiment, the device quantity information and the resource quantity information are located in a first domain.

[0303] Optionally, as an embodiment, the first message further includes second resource type information, which is used to indicate that the second AIoT device adopts a second resource type;

[0304] The first resource type information is used to indicate that the first AIoT device adopts a first resource type; the second resource type is different from the first resource type.

[0305] Optionally, as an embodiment, the first resource type information and the first resource information are located in the third domain as a first group of resource information; the second resource type information and the second resource information are located in the third domain as a second group of resource information; wherein, the third domain is located in the header of the first message, or in the control domain of the first message, or in the payload domain of the first message, or in the sub-header portion of the first message, or in the layer 1 control domain.

[0306] Optionally, as an embodiment, the device identification information of the first AIoT device is located in the first group of resource information; the first group of resource information also includes first successfully received bit (SRB) information; and / or, the device identification information of the second AIoT device is located in the second group of resource information, and the second group of resource information also includes second SRB information.

[0307] Optionally, as an embodiment, the first message may further include device identifier length information; or, the first message may further include allocation type information.

[0308] Optionally, as an embodiment, the device identifier length of the first AIoT device is a first length information, the device identifier length of the second AIoT device is a second length information, and the first message further includes the first length information and the second length information; or, the allocation type of the device identifier of the first AIoT device is a first allocation type, the allocation type of the device identifier of the second AIoT device is a second allocation type, and the first message further includes the first allocation type and the second allocation type.

[0309] Optionally, as an embodiment, the first message further includes first indication information; the first indication information is used to indicate whether the first message includes a data field.

[0310] Optionally, as an embodiment, the first indication information is data field indication information; or, the first indication information is a successful reception bit (SRB) indication; or, the first indication information is a data length indication.

[0311] Optionally, as an embodiment, the first message is a reader-to-device R2D message; the second message is a device-to-reader D2R message.

[0312] It should be understood that the communication device 1300 may correspond to the first device in Figures 1 to 12 according to the embodiments of this application; the communication device 1300 may include modules or units for performing the methods performed by the first device in Figures 1 to 12. Furthermore, each module in the communication device 1300 and the other operations and / or functions described above are respectively for implementing the corresponding processes of Figures 1 to 12.

[0313] It should also be understood that when the communication device 1300 is the first device, the processing module 1310 in the communication device 1300 can be implemented by at least one processor, for example, it can correspond to the processor 1410 in the communication device 1400 shown in FIG. 14. For example, the communication module 1320 can correspond to the communication interface 1420 in the communication device 1400 shown in FIG. 14.

[0314] It should also be understood that when the communication device 1300 is a chip or chip system configured in the first device described above, the processing module 1310 of the communication device 1300 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0315] Figure 14 is another schematic block diagram of the communication device 1400 provided in an embodiment of this application. The communication device 1400 may be a first AIoT device or a first device; it may also be a chip, chip system, or processor that supports the first AIoT device or the first device in implementing the above methods. The communication device 1400 can be used to implement the methods described in the above method embodiments, and specific details can be found in the descriptions of the above method embodiments.

[0316] As shown in Figure 14, the communication device 1400 may include one or more processors 1410, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1410 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1400 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0317] In an alternative design, the processor 1410 may also store instructions and / or data that can be executed by the processor 1410 to cause the communication device 1400 to perform the methods described in the above method embodiments.

[0318] In another alternative design, the communication device 1400 may include a communication interface 1420 for implementing receiving and transmitting functions. For example, the communication interface 1420 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0319] Optionally, the communication device 1400 may include one or more memories 1430, which may store instructions that can be executed on the processor 1410, causing the communication device 1400 to perform the methods described in the above method embodiments. Optionally, the memories 1430 may also store data. Optionally, the processor 1410 may also store instructions and / or data. The processor 1410 and the memories 1430 may be provided separately or integrated together.

[0320] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0321] Optionally, if the communication device 1400 includes a processor 1410, a communication interface 1420, and a memory 1430, the processor 1410, the communication interface 1420, and the memory 1430 communicate with each other through internal connection paths.

[0322] Optionally, the memory 1430 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. The memory 1430 may be a separate device or integrated into the processor 1410.

[0323] In one implementation, the communication device 1400 may correspond to the first AIoT device in the above method embodiments and may be used to execute the various steps and / or processes executed by the first AIoT device in the above method embodiments. The processor 1410 may be used to execute instructions stored in the memory 1430, and when the processor 1410 executes the instructions stored in the memory, the processor 1410 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first AIoT device.

[0324] In another implementation, the communication device 1400 may correspond to the first device in the above method embodiments and may be used to execute the various steps and / or processes executed by the first device in the above method embodiments. The processor 1410 may be used to execute instructions stored in the memory 1430, and when the processor 1410 executes the instructions stored in the memory, the processor 1410 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first device.

[0325] Optionally, the communication interface 1420 is a transceiver, which may include a transmitter and a receiver. The transceiver may further include an antenna, which may be one or more. The processor 1410 and memory 1430, along with the communication interface 1420, may be integrated on different chips. For example, the processor 1410 and memory 1430 may be integrated in a baseband chip, and the communication interface 1420 may be integrated in a radio frequency chip. Alternatively, the processor 1410, memory 1430, and communication interface 1420 may be integrated on the same chip. This application does not limit this.

[0326] This application also provides a processing device, including a processor and an interface; the processor is used to execute the communication method in any of the above method embodiments.

[0327] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0328] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0329] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0330] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can 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 can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0331] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0332] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0333] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned first AIoT device and first device. Optionally, the communication system further includes a second AIoT device.

[0334] Optionally, the communication system also includes other devices that communicate with the first AIoT device.

[0335] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the first AIoT device and the various steps or processes executed by the first device in any of the foregoing method embodiments.

[0336] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the first AIoT device and the various steps or processes executed by the first device in any of the foregoing method embodiments.

[0337] The computer-readable storage medium can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory. The non-volatile memory can 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 can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0338] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0339] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0340] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0341] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0342] Furthermore, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this paper generally indicates that the preceding and following related objects have an "or" relationship. For example, A / B can represent A or B.

[0343] The terms (or numbers) "first," "second," etc., appearing in the embodiments of this application are for descriptive purposes only, that is, only to distinguish different objects, such as different "messages," etc., and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first," "second," etc., may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "at least one (item)" refers to one or more. "Multiple" means two or more. "At least one (item) below" or similar expressions refer to any combination of these items, including any combination of a single (item) or a plurality of (items).

[0344] For example, expressions like "the item includes at least one of the following: A, B, and C" appearing in the embodiments of this application generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above uses three elements, A, B, and C, as examples to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

[0345] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method, applied to an AIoT device in a first-environment Internet of Things (IoT) environment, includes: Receive a first message from a first device, the first message being used to configure resources for a first environment Internet of Things (AIoT) device, the first message including at least first resource type information, the first resource type information being used to instruct the first AIoT device to adopt a first resource type; Send a second message to the first device, the second message being determined at least based on the first resource type.

2. A communication method characterized by comprising: Applied to a first device, the method includes: Send a first message, the first message being used to configure resources for an environmental Internet of Things (AIoT) device, the first message including at least first resource type information, the first resource type information being used to instruct the AIoT device to adopt a first resource type; Receive a second message, which is determined at least based on the first resource type.

3. The method according to claim 1 or 2, characterized in that, The first resource type is any one of the following resource types: The first type is a resource type that includes all configuration parameters in the first configuration parameter set, and the first configuration parameter set includes one or more of the following: frequency domain configuration parameters, time domain configuration parameters, transmission mode configuration parameters, and configuration parameters used to indicate the amount of data to be transmitted or the size of the data packet. The second type is a resource type that includes some configuration parameters from the first set of configuration parameters; The third type is a resource type that does not include any of the configuration parameters in the first set of configuration parameters.

4. The method according to any one of claims 1 to 3, characterized in that, The first message also includes resource information; the resource type corresponding to the resource information is the first resource type.

5. The method according to any one of claims 1 to 4, characterized in that, The first message is used to configure resources for multiple AIoT devices; the multiple AIoT devices include at least the first AIoT device and the second AIoT device; The first message also includes first resource information and second resource information, wherein the first resource information is resource information configured for the first AIoT device and the second resource information is resource information configured for the second AIoT device.

6. The method according to claim 5, characterized in that, The first message also includes: device identification information of the first AIoT device, and / or, device identification information of the second AIoT device.

7. The method according to claim 5 or 6, characterized in that, The resource type corresponding to both the second resource information and the first resource information is the first resource type.

8. The method according to claim 7, characterized in that, The first resource type information is located in the first field of the first message, and the first resource information and the second resource information are located in the second field of the first message; Wherein, the first field and the second field are located in different parts of the first message; or, the first field and the second field are both located in the header of the first message, or both are located in the control field of the first message, or both are located in the payload field of the first message, or both are located in the subheader portion of the first message; Alternatively, the first domain and the second domain may be located in the Layer 1 control domain and the Layer 2 data packet, respectively.

9. The method according to any one of claims 5 to 8, characterized in that, The first message may also include one or more of the following: device quantity information, resource quantity information, and successfully received bit SRB information.

10. The method according to claim 5 or 6, characterized in that, The first message also includes second resource type information, which is used to indicate that the second AIoT device adopts the second resource type; The first resource type information is used to indicate that the first AIoT device adopts a first resource type; the second resource type is different from the first resource type.

11. The method according to claim 10, characterized in that, The first resource type information and the first resource information are located in the third domain as a first group of resource information; the second resource type information and the second resource information are located in the third domain as a second group of resource information. The third field is located in the header of the first message, or in the control field of the first message, or in the payload field of the first message, or in the sub-header portion of the first message, or in the layer 1 control field.

12. The method according to claim 11, characterized in that, The device identification information of the first AIoT device is located in the first group of resource information; the first group of resource information also includes the first successful reception bit (SRB) information; And / or, the device identification information of the second AIoT device is located in the second group of resource information, which also includes the second SRB information.

13. The method according to any one of claims 6 to 12, characterized in that, The first message also includes device identifier length information; or, The first message also includes allocation type information.

14. The method according to any one of claims 6 to 12, characterized in that, The device identifier length of the first AIoT device is a first length information, and the device identifier length of the second AIoT device is a second length information. The first message also includes the first length information and the second length information; or... The device identifier of the first AIoT device is assigned to a first assignment type, and the device identifier of the second AIoT device is assigned to a second assignment type. The first message also includes the first assignment type and the second assignment type.

15. The method according to any one of claims 1 to 14, characterized in that, The first message also includes first indication information; the first indication information is used to indicate whether the first message includes a data field.

16. The method according to claim 15, characterized in that, The first indication information is data field indication information; Alternatively, the first indication information is a successful reception bit SRB indication; Alternatively, the first indication information may be a data length indication.

17. The method according to any one of claims 1 to 16, characterized in that, The first message is a reader-to-device R2D message; the second message is a device-to-reader D2R message.

18. A communication system, characterized in that, Includes a first device, and one or more AIoT devices, wherein the one or more AIoT devices include at least the first AIoT device; Wherein, the first AIoT device is used to perform the method as described in any one of claims 1, 3-17; The first device is used to perform the method as described in any one of claims 2-17.

19. A communication device, characterized in that, The device includes at least one processor coupled to a memory for storing programs or instructions, the processor executing the programs or instructions such that the device is configured to perform the method as claimed in any one of claims 1, 3-17, or such that the device is configured to perform the method as claimed in any one of claims 2-17.

20. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1, 3-17, or cause the computer to perform the method as described in any one of claims 2-17.

21. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, such that the method as described in any one of claims 1, 3-17 is performed; or, such that the method as described in any one of claims 2-17 is performed.

Images