Communication method and communication apparatus

CN122534468APending Publication Date: 2026-08-07HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2025-08-11
Publication Date
2026-08-07

Smart Images

  • Figure CN122534468A_ABST
    Figure CN122534468A_ABST
Patent Text Reader

Abstract

The application provides a communication method and a communication device. The method can include: receiving a first message from a first reader-writer, the first message indicating a first AIoT device to execute a first command; and sending a second message to the first reader-writer, the second message indicating that the first AIoT device is executing the first command. Based on this, after the AIoT device receives the command, by sending the second message to indicate that the AIoT device is executing the command, the waiting time of the reader-writer can be avoided to be too long, so that the probability of misjudging that the command execution fails can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to Chinese Patent Application No. 202510145210.8, filed on February 7, 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 communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0003] An ambient internet of things (A-IoT) system typically includes a reader and A-IoT devices (also known as tags). The reader can interact with the A-IoT devices to manage them. Specifically, the reader sends commands to the A-IoT devices, which can include read commands, write commands, disable commands, etc. After executing the command, the A-IoT device sends the execution result back to the reader.

[0004] However, in the above implementation process, there is a problem of misjudging command execution failure. Therefore, how to reduce the probability of misjudging business failure in communication between the reader and A-IoT devices is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a communication method or communication device that can avoid excessive waiting time for reader devices and reduce the probability of misjudging command failures.

[0006] Firstly, a communication method is provided. This method can be applied to AIoT devices, or to components of AIoT devices (such as chips or circuits, which can be modem chips, also known as baseband chips, or system-on-chip (SoC) or system-in-package (SIP) chips containing modem cores, etc.), or to logic modules or software capable of implementing some or all of the functions of AIoT devices, etc. This application does not limit this application.

[0007] The method may include: receiving a first message from a first reader / writer, the first message instructing a first AIoT device to execute a first command; and sending a second message to the first reader / writer, the second message instructing the first AIoT device to execute the first command.

[0008] Based on the above technical solution, after receiving a command, the AIoT device sends a second message to indicate that the AIoT device is executing the command. The reader device can know that the AIoT device is executing the command by receiving the second message, thereby avoiding excessive waiting time for the reader and reducing the probability of misjudging command execution failure.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the second message further includes first indication information, which indicates whether the first AIoT device still has data to send.

[0010] Based on the above technical solution, by sending a second message to indicate that the AIoT device is executing the command and that there is still data to be sent, the reader device can know that the AIoT device is executing the command and that there is still data to be sent when it receives the second message. This can avoid the reader waiting time being too long and reduce the probability of misjudging that the command execution has failed.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, before sending the second message, the method further includes: sending a third message to the first reader / writer, the third message indicating that the first AIoT device has received the first message.

[0012] Based on the above technical solution, when an AIoT device receives a command, a third message is sent to indicate that the AIoT device has received the first message. This can further reduce the waiting time of the reader / writer for the command, allowing the reader / writer to know that the writing task is proceeding normally, thereby reducing the probability of misjudging business failure.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first message also instructs the first resource; sending a second message to the first reader includes: sending a second message to the first reader on the first resource.

[0014] Based on the above technical solution, the AIoT device can send a second message on the first resource, and the reader / writer device can receive the second message based on the first resource, which facilitates the reader / writer device to manage the feedback message of the command.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: sending a fourth message to the first reader / writer, the fourth message indicating whether the first command was executed successfully or failed.

[0016] Based on the above technical solution, the AIoT device sends a fourth message to the reader device, which can indicate whether the first command was executed successfully or failed. The reader can then know whether the execution status of the command has changed from "in execution" to "execution successful" or "execution failed," facilitating the reader's management of the first command.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first message also instructs the second resource; sending a fourth message to the first reader includes: sending the fourth message to the first reader on the second resource.

[0018] Based on the above technical solution, the AIoT device can send a fourth message to the reader device on the second resource, and the reader device can receive the fourth message based on the second resource, which facilitates the reader device to manage the feedback message of the command.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the method includes: sending a fifth message to a first reader / writer, the fifth message indicating that the first AIoT device is executing a first command.

[0020] Based on the above technical solution, the AIoT device can provide feedback that the command is being executed again. That is, when the command is long, the AIoT device can provide feedback on the execution status multiple times, which can avoid the reader waiting time being too long and reduce the probability of misjudging the command execution failure.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the first message also instructs the third resource; sending a fifth message to the first reader includes: sending the fifth message to the first reader on the third resource.

[0022] Based on the above technical solution, AIoT devices can send a fifth message to a reader device from a third resource, and the reader device can receive the fifth message based on the third resource, which facilitates the reader device's management of the feedback message of the command.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, after receiving the first message from the first reader / writer, the method further includes: receiving a sixth message from the first reader / writer, the sixth message indicating the fourth resource; and sending a second message to the first reader / writer, including: sending the second message to the first reader / writer on the fourth resource.

[0024] Based on the above technical solution, after receiving the first message from the first reader, the AIoT device can receive the resources indicated by the reader for the command. These resources can be used by the AIoT device to provide feedback on the current execution progress of the command. In this technical solution, the reader can send resource indications at any time after sending the command, so that the reader can know the execution progress of the command at any time.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, after sending the second message to the first reader / writer, the method further includes: receiving a seventh message from the first reader / writer, the seventh message indicating a fifth resource; and sending an eighth message to the first reader / writer, including: sending the eighth message to the first reader / writer on the fifth resource, the eighth message indicating that the first AIoT device is executing a first command.

[0026] Based on the above technical solution, the AIoT device can again report that the command is being executed on the resource indicated by the reader. That is, when the command is long, the AIoT device can report the execution status multiple times, which can avoid the reader waiting time being too long and thus reduce the probability of misjudging the command execution failure.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, after sending the second message to the first reader / writer, the method further includes: receiving a ninth message from the first reader / writer, the ninth message indicating a sixth resource; and sending a fourth message to the first reader / writer, including: sending a fourth message to the first reader / writer on the sixth resource, the fourth message indicating whether the first command was executed successfully or failed.

[0028] Based on the above technical solution, the AIoT device can send a fourth message to the reader device on the resource indicated by the reader. The fourth message can indicate whether the first command was executed successfully or failed. The reader can then know that the execution status of the command has changed from "in execution" to "execution successful" or "execution failed," facilitating the reader's management of the command.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the ninth message includes a Service Data Unit (SDU) of zero or a data indication offset of zero.

[0030] Based on the above technical solution, the reader / writer device can send a Service Data Unit (SDU) of 0 or a Data Indicator Offset of 0 to the first AIoT device to instruct the first AIoT device to perform subsequent operations. For example, if the first command is a write command, then the ninth message indicates that the SDU is 0, and the first AIoT device can continue to input data.

[0031] Secondly, a communication method is provided. This method can be applied to reader / writer devices, or to components of reader / writer devices (such as chips, chip systems, circuits, or communication modules, etc.). For example, it can be a terminal device, or a component used in a terminal device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of a terminal device, etc.; for example, it can also be a network device, or a component used in a network device (such as a chip, chip system, or circuit), or a logic module or software capable of implementing some or all of the functions of a network device, etc.; for further examples, it can also be a headend, a Pico Radio Unit (PRU), a transmission reception point (TRP), or other nodes that transmit signals. This application does not limit this.

[0032] The method may include: sending a first message to a first AIoT device, the first message instructing the first AIoT device to execute a first command; and receiving a second message from the first AIoT device, the second message instructing the first AIoT device to execute the first command.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the second message further includes first indication information, which indicates whether the first AIoT device still has data to send.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, before receiving the second message from the first AIoT device, the method further includes: receiving a third message from the first AIoT device, the third message indicating that the first AIoT device has received the first message.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the first message further indicates the first resource; receiving the second message from the first AIoT device includes: receiving the second message from the first AIoT device on the first resource.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: receiving a fourth message from the first AIoT device, the fourth message indicating whether the first command was executed successfully or failed.

[0037] In conjunction with the second aspect, in some implementations of the second aspect, the first message further instructs the second resource; receiving a fourth message from the first AIoT device includes: receiving the fourth message from the first AIoT device on the second resource.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, the method includes: receiving a fifth message from a first AIoT device, the fifth message indicating that the first AIoT device is executing a first command.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the first message also instructs a third resource; receiving a fifth message from the first AIoT device includes: receiving the fifth message from the first AIoT device on the third resource.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, after sending the first message to the first AIoT device, the method further includes: sending a sixth message to the first AIoT device, the sixth message indicating a fourth resource; and receiving a second message from the first AIoT device, including: receiving the second message from the first AIoT device on the fourth resource.

[0041] In conjunction with the first aspect, in some implementations of the first aspect, the step of sending a sixth message to the first AIoT device after sending the first message to the first AIoT device includes: determining to send the sixth message to the first AIoT device based on a security processing delay.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, after receiving the second message from the first AIoT device, the method further includes: sending a seventh message to the first AIoT device, the seventh message indicating the fifth resource;

[0043] Receiving an eighth message from a first AIoT device includes: receiving an eighth message from a first AIoT device on a fifth resource, the eighth message indicating that the first AIoT device is executing a first command.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, after receiving the second message from the first AIoT device, the method further includes: sending a ninth message to the first AIoT device, the ninth message indicating the sixth resource;

[0045] Receiving a fourth message from the first AIoT device includes: receiving a fourth message from the first AIoT device on the sixth resource, the fourth message indicating whether the first command was executed successfully or failed.

[0046] In conjunction with the second aspect, in some implementations of the second aspect, the step of sending a ninth message to the first AIoT device after receiving the second message from the first AIoT device includes: determining to send the sixth message to the first AIoT device based on a security processing delay.

[0047] The security processing delay can be predefined or indicated by the core network equipment.

[0048] In conjunction with the second aspect, in some implementations of the second aspect, the ninth message is either a Service Data Unit (SDU) of zero or a data indication offset of zero.

[0049] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: sending a tenth message to a core network (CN) device, the tenth message indicating that the first AIoT device has received the first message.

[0050] Based on the above technical solution, the reader device sends a tenth message, which indicates that the AIoT device has received the first message. This facilitates the core network device's management of the commands indicated by the first message.

[0051] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: sending an eleventh message to the core network device, the eleventh message indicating whether the first command was executed successfully or failed.

[0052] Based on the above technical solution, the reader device sends an eleventh message, which indicates whether the AIoT device executed the command successfully or failed. This facilitates the core network device's management of the command indicated in the first message.

[0053] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the second message further includes media access control padding bits; the second message indicates that the first AIoT device is executing the first command, including: the media access control padding bits indicate that the first AIoT device is executing the first command.

[0054] Based on the above technical solution, the reader device feeds back the media access control padding bits to the reader, so that the reader can know the current command execution progress. This can avoid the reader waiting for too long and reduce the probability of misjudging command execution failure.

[0055] In conjunction with the first or second aspect, in some implementations of the first or second aspect, when the fourth message indicates that the first command has failed to execute, the fourth message also indicates the reason for the failure.

[0056] Based on the above technical solution, when the reader device fails to execute a command, it not only reports the result of the failure, but also reports the reason for the failure to the reader device, so as to facilitate the reader device to manage the command.

[0057] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the fourth message is carried in a media access control control element or non-access stratum signaling.

[0058] Based on the above technical solution, the reader / writer device can receive the fourth message in two ways. The reader / writer device can choose the appropriate way to receive the message based on the actual situation, which facilitates the management of the reader / writer device.

[0059] Thirdly, a communication apparatus is provided for performing the methods of the first or second aspect and any possible implementation thereof. Specifically, the apparatus may include units and / or modules for performing the methods of the first or second aspect and any possible implementation thereof, such as processing units and / or communication units.

[0060] In one implementation, the device is a communication device (such as an AIoT device, or a reader / writer device). When the device is a communication device, the communication unit can be a transceiver, or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0061] In another implementation, the device is a chip, chip system, or circuit for a communication device (such as an AIoT device or a reader / writer device). When the device is a chip, chip system, or circuit for a communication device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0062] Fourthly, a communication device is provided. The device includes: at least one processor for executing a computer program or instructions stored in a memory to perform a method in any of the possible implementations of the first to second aspects described above. Optionally, the device further includes a memory for storing the computer program or instructions; correspondingly, at least one processor is used to execute the computer program or instructions in the memory. Optionally, the device further includes a communication interface coupled to the processor, which can be used to input information to the processor or output information from the processor. Optionally, the processor reads the computer program or instructions from the memory through the communication interface.

[0063] In one implementation, the device is a communication device (such as an AIoT device or a reader / writer device).

[0064] In another implementation, the device is a chip, chip system, circuit, or communication module for communication devices (such as AIoT devices or reader devices). Optionally, the chip is a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip.

[0065] Fifthly, a processor is provided, including a module for performing the methods provided in any one of the first to second aspects described above.

[0066] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0067] A sixth aspect provides a computer-readable storage medium. The computer-readable storage medium is located in a communication device and stores a computer program (e.g., program code) or instructions that, when executed, cause the methods of the first or second aspect and any possible implementation thereof to be performed or implemented.

[0068] A seventh aspect provides a computer program product comprising instructions. The computer program product includes a computer program or instructions for performing the methods in any possible implementation of the first or second aspect described above. In other words, when the computer program product is run, it causes the methods provided in any of the first to second aspects to be performed or implemented.

[0069] Eighthly, a chip is provided. The chip includes a processor and a communication interface, wherein the processor reads instructions from a memory via the communication interface and executes the methods provided in any one of the first to second aspects described above.

[0070] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the methods provided in any one of the first to second aspects described above.

[0071] Ninthly, a communication system is provided. The communication system includes a first communication device and a second communication device. The first communication device is used to execute the method provided in any implementation of the first aspect, and the second communication device is used to execute the method provided in any implementation of the second aspect. Attached Figure Description

[0072] Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application.

[0073] Figure 2 This is a schematic diagram of an AIoT device applicable to an embodiment of this application.

[0074] Figure 3 This is a schematic diagram of an AIoT topology applicable to embodiments of this application.

[0075] Figure 4 This is a schematic diagram of another AIoT topology applicable to embodiments of this application.

[0076] Figure 5 This is a schematic diagram of an open radio access network (O-RAN) system applicable to embodiments of this application.

[0077] Figure 6 This is a schematic diagram of the application framework involving RIC modules under the O-RAN architecture.

[0078] Figure 7 A schematic diagram of the core network (CN) architecture and protocol stack applicable to the above AIoT topology is shown.

[0079] Figure 8 A schematic diagram of the CN architecture and protocol stack applicable to the above AIoT topology is shown.

[0080] Figure 9 This is a flowchart illustrating a command processing method applicable to this application.

[0081] Figure 10 This is a schematic diagram of a communication method provided in an embodiment of this application.

[0082] Figure 11 This is a schematic diagram of another communication method provided in an embodiment of this application.

[0083] Figure 12 This is a schematic diagram of another communication method provided in an embodiment of this application.

[0084] Figure 13 This is a schematic diagram of another communication method provided in an embodiment of this application.

[0085] Figure 14 This is a schematic diagram of another communication method provided in an embodiment of this application.

[0086] Figure 15 This is a schematic diagram of a communication device provided in an embodiment of this application.

[0087] Figure 16 This is a schematic diagram of another communication device provided in an embodiment of this application.

[0088] Figure 17 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

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

[0090] Before introducing the scheme of this application, the following points should be noted.

[0091] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood that the instruction information carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, a statement such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

[0092] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0093] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

[0094] (3) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0095] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0096] (5) In this application, terms such as "first," "second," etc., are used for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that such described objects can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0097] (6) In this application, "predefined" can mean a standard protocol predefined, or it can mean a pre-agreed or pre-negotiated agreement between devices. Here, "protocol" can refer to a standard protocol in the field of communications, for example, it may include fourth-generation (4G) protocols. th Generation 4G network protocol, fifth generation (5G)th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR) protocols, 5.5G network protocols, and related protocols applied in future communication networks.

[0098] (7) In this application, the words “exemplary,” “for example,” “e.g.,” are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0099] (8) In this application, the configuration can be signaling configuration, such as radio resource control (RRC) messages, control information (such as downlink control information (DCI), uplink control information (UCI), or sidelink control information (SCI)), or medium access control (MAC) signaling (e.g., MAC control element (MAC CE / MAC-CE)). As an example, the signaling configuration can be configured by signaling to the device, for example, a second communication device configuration rule (or a second communication device configuration rule for a first communication device), which can be understood as the second communication device instructing the first communication device to use signaling.

[0100] First, let me introduce the communication system to which this application applies.

[0101] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication network systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication.

[0102] As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. Satellite base stations can also communicate with each other. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment.

[0103] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0104] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses a device as an example for description.

[0105] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) equipment, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control equipment, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3GPP standard. The device may be a wireless communication unit (RSU), or a device built into the aforementioned device (e.g., a communication module, modem, or chip in the aforementioned device), or other processing devices connected to the wireless modem.

[0106] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0107] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0108] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in future communication networks, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0109] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0110] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes.

[0111] In some deployments, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0112] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0113] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0114] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0115] Combination Figure 1 The communication system applicable to the embodiments of this application is briefly described below.

[0116] For example, Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application. For example... Figure 1 As shown, the wireless communication system includes a wireless access network 100. The wireless access network 100 can be a next-generation (e.g., future or later) wireless access network, or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 120) can be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) within the wireless access network 100. Network elements in the wireless communication system are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces.

[0117] When network devices and terminal devices communicate, the network device can manage one or more cells, and a cell can include at least one terminal device. A cell can be understood as an area within the wireless signal coverage range of the network device.

[0118] Figure 1 This is just an illustration; the wireless communication system may also include other devices, such as core network equipment, wireless relay equipment, and / or wireless backhaul equipment. Figure 1 It is not shown in the middle.

[0119] To facilitate understanding of the embodiments of this application, a brief explanation of the background and terminology involved in this application is provided.

[0120] 1. Environmental Internet of Things

[0121] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (AIoT or A-IoT) technology. AIoT can be based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active tags (in AIoT technology, tags are terminals within the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT terminals). Its main functions include inventory management, positioning, sensing, and command processing. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0122] AIoT technology can include network devices and Type I terminal devices; in other words, an AIoT-based communication system can include network devices and Type I terminal devices. The Type I terminal devices can be devices with tag-like functionality. In this case, both the reader / writer and the tag device can be implemented based on cellular network infrastructure. In other words, both the reader / writer and the tag device can be devices within a cellular network. For example, the reader / writer's functionality can be implemented by network devices (such as base stations) or terminals. The tag device can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. Non-contact data communication can be performed between the network device and the Type I terminal, thereby allowing the network device to read information from the Type I terminal and / or write information that needs to be stored into the Type I terminal.

[0123] The reader / writer involved in the embodiments of this application may include handheld or fixed devices for reading (and sometimes writing) tag information, as defined in the original definition. It can also be understood as a device that communicates with the tag, and its form can be a terminal, a base station, or a node that transmits signals such as a headend, a Pico Radio Unit (PRU), or a transmission reception point (TRP), or a device with read / write capabilities. It can also be an integrated access and backhaul (IAB) node, a smart repeater, or a relay node, etc.

[0124] The core network (CN) equipment involved in the embodiments of this application includes core network elements used to serve AIoT devices, which can be AIoTMF (Ambient IoT management function), AMF (access and mobility management function), SMF (session management function), UPF (User Plane Function), etc.

[0125] 2. AIoT Business

[0126] The main business of A-IoT includes one or more of the following: inventory, positioning, sensing, or command.

[0127] For example, the inventory management service can utilize a reader (which can be a base station / terminal) to access tags (AIoT devices) within its coverage area. Successfully connected devices need to send their unique identifier to the reader. This inventory management service can also be called an inventory operation, inventory process, etc., and the name is not limited to these terms. This inventory management service can obtain the tag's identification information. For example, the reader can use query and acknowledge (ACK) commands to obtain the tag's identification information. To facilitate tag inventory, tags include four session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessionInventoried flag. When the reader selects a tag, the select command sent to it carries a session identifier, and the tag stores this session identifier. When the reader performs the inventory management service on the tag, the query command sent to it includes this session identifier. At this time, the tag can flip the inventory state corresponding to this session identifier from A to B. If the reader sends a query command to perform inventory operations again, the tag will not respond to the reader because the inventory status of the tag is B, thus avoiding the same tag being inventoried multiple times in the same inventory cycle.

[0128] For example, location services use some location signals to locate the position of a tag.

[0129] For example, a sensing service involves tags reporting sensing data to a base station, such as temperature data.

[0130] For example, a command service can be a set of operation instructions, and for example, a command service can include at least one of the following services:

[0131] 1) Read service: It can read the electronic product code (EPC), tag identifier (TID) in the storage area of ​​the AIoT device, the content stored in the reserved area of ​​the AIoT device, or the content stored in the user storage area of ​​the AIoT device.

[0132] 2) Write service: This allows writing operations to the storage area of ​​AIoT devices. In other words, the reader (such as a base station or terminal) sends a downlink command and data to instruct the AIoT device to write the data into the storage area.

[0133] 3) Disable service: You can request AIoT devices to permanently or temporarily disable their radio frequency (RF) transmission capabilities.

[0134] 4) Enable service: You can request to enable AIoT devices that have been temporarily disabled.

[0135] 5) Kill Service: This service can make AIoT devices permanently unusable.

[0136] 6) Locking service: It can lock the information of AIoT devices to prevent read or write operations on the AIoT devices, or it can lock the storage area to prevent read or write operations on the storage area.

[0137] The above services are just examples. AIoT devices and readers can also perform other services or operations, which will not be listed here.

[0138] 3. AIoT devices

[0139] AIoT technology is an extremely low-power, low-complexity Internet of Things (IoT) technology defined at the 3GPP plenary meeting. It can be understood as an extension of passive radio frequency identification (RFID) within 3GPP. Although it shares some principles with RFID, such as similar inventory management processes, 3GPP introduces more value-added scenarios.

[0140] Tags, also known as electronic tags, are commonly referred to as RFID tags. RFID is an abbreviation for Radio Frequency Identification. RFID technology can be divided into three types: active, passive, and semi-active. Passive tags can also be called passive IoT, meaning passive Internet of Things devices. Therefore, they can also be considered a type of terminal.

[0141] For example, Figure 2 This is a schematic diagram of an AIoT device applicable to an embodiment of this application. The antenna receives incoming signals or carrier waves, and then, depending on the information to be carried, transmits the signal through the antenna by reflecting it onto the carrier wave or generating an uplink signal.

[0142] AIoT devices typically operate with no or low-power batteries, eliminating the need for manual battery replacements. Instead, they harvest energy from the environment to provide services and communicate. In some implementations, AIoT devices are also referred to as tags or AIoT labels. They are generally inexpensive, can be attached to items, and support inventory and location functions.

[0143] In AIoT systems and related systems, tags can also be called electronic tags, RFID tags, or tag devices. Alternatively, tags can also be called AIoT terminal devices or AIoT devices. In this application, tags can also be considered as a type of terminal device.

[0144] In one classification method, tags can be categorized into passive tags, semi-passive tags, and active tags. Passive and semi-passive tags can employ backscatter-based communication, while active tags utilize actively generated carrier waves.

[0145] Another classification method divides the tags into the following three types of devices: 1) Device A: No energy storage, cannot generate signals independently, and uses backscatter to transmit signals; 2) Device B: Has energy storage, but cannot generate signals independently, and uses backscatter to transmit signals. Its stored energy can amplify the reflected signal; 3) Device C: Has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0146] Another classification method can divide the tags into the following types: 1) Device 1: ~1μW peak power consumption, with energy storage function, and initial sampling frequency offset (SFO) of up to 10. X 1) ppm cannot amplify DL and UL signals; it requires an external carrier signal for backscatter communication to enable uplink transmission. 2) Device 2a has a peak power consumption of less than or equal to several hundred μW, possesses energy storage capabilities, and has an initial sampling frequency offset (SFO) of 10. Xppm, capable of DL and / or UL signal amplification, requires an external carrier signal for backscatter communication to enable uplink transmission. 3) Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset (SFO) reaching 10. X ppm can amplify DL and / or UL signals and can perform uplink transmission without relying on an externally provided carrier.

[0147] Another classification method involves classifying tags based on one or more of their reflectivity, energy storage capacity, signal amplification capability, or signal generation capability. This application does not limit the specific classification of tags in its embodiments.

[0148] The tag uses a low-precision, low-power mid-to-low frequency ring oscillator or a completely oscillator-less receiver to receive downlink signals. When the tag is working, the energy and carrier for communication are supplied by the reader, and communication is based on a reflected carrier.

[0149] 4. AIoT Topology

[0150] AIoT has various topologies, which can be divided into direct connection structures and relay structures. The following examples illustrate these structures.

[0151] For example, Figure 3 This is a schematic diagram of an AIoT topology 300 applicable to embodiments of this application. Figure 3 The AIoT topology shown is Topology 1. Topology 1 adopts a direct-connect architecture, allowing direct bidirectional communication between AIoT devices and network devices. Communication between network devices and AIoT devices includes environmental IoT data and / or signaling. The network device sending environmental IoT data and / or signaling to the AIoT device and the network device receiving environmental IoT data and / or signaling from the AIoT device can be the same network device or different network devices.

[0152] For example, Figure 4 This is a schematic diagram of another AIoT topology 400 applicable to embodiments of this application. Figure 4The AIoT topology shown is Topology 2. Topology 2 adopts a relay architecture, where AIoT devices communicate with network devices through intermediate nodes. In other words, there is bidirectional communication between AIoT devices and intermediate nodes, and bidirectional communication between intermediate nodes and network devices. Intermediate nodes transmit environmental IoT data and / or signaling between network devices and AIoT devices. Intermediate nodes can be A-IoT-enabled relays, integrated access and backhaul (IAB) nodes, user equipment (UE), repeaters, etc. Intermediate nodes act as readers / writers, executing A-IoT services.

[0153] It should be understood that the above Figure 3 and Figure 4 The AIoT topology shown is merely an example. The embodiments of this application can also be applied to AIoT topologies that include carrier wave (CW) nodes or assistant nodes. This application does not limit the scope of the application.

[0154] The embodiments of this application can also be applied to open RAN (O-RAN) system architecture.

[0155] like Figure 5 As shown, an O-RAN system can include core network (CN) equipment, access network (RAN) equipment, and user equipment (UE). Access network equipment communicates with core network equipment via a backhaul link and with UE via an air interface. For example, a BBU in the access network equipment communicates with the core network equipment via a backhaul link, and an RU in the access network equipment communicates with the UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, and the CU and DU can communicate via at least one midhaul link.

[0156] Figure 5 This is just an illustration; the wireless communication system may also include other devices. Figure 5 It is not shown in the middle.

[0157] Figure 6 This is a schematic diagram of the application framework involving RIC modules under the O-RAN architecture. For example... Figure 6As shown, the communication system includes a RAN intelligent controller (RIC). The RIC includes near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs). Non-real-time RICs primarily process non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. Real-time RICs primarily process near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0158] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in the OAM, cloud server, core network device, or other network device.

[0159] Figure 7 A schematic diagram of the CN architecture and protocol stack applicable to the AIoT topology 300 is shown.

[0160] like Figure 7 As shown in (a), A-IoT devices and the A-IoT RAN can exchange A-IoT data and / or signaling via the A-IoT radio interface, and the A-IoT RAN and the A-IoT CN can exchange A-IoT data and / or signaling via the XX interface. The XX interface can be a next-generation (NG) interface.

[0161] Figure 7 The A-IoT RAN shown in (a) has a common reader function and an A-IoT RAN node function. The common reader function refers to the ability to communicate with A-IoT devices via the A-IoT radio interface. The A-IoT RAN node function includes the ability to control A-IoT resources; in other words, it includes the ability to allocate time-frequency resources for communication between the UE or the A-IoT RAN and A-IoT devices. The A-IoT RAN can also be replaced by a gNB that supports A-IoT.

[0162] like Figure 7As shown in (b) and (c), there are two scenarios between the A-IoT RAN and the ambient IoT function (AIoTF) (another example of A-IoT CN): direct connection and indirect connection (indirect path via access and mobile management function, AMF). Figure 7 As shown in (b), when the A-IoT RAN is directly connected to the AIoTF, the A-IoT RAN can directly interact with the AIoTF via the NG interface to exchange A-IoT data and / or signaling. Figure 7 As shown in (c), when the A-IoT RAN and AIoTF are not directly connected, the A-IoT RAN can interact with the AIoTF via AMF to exchange A-IoT data and / or signaling.

[0163] like Figure 7 As shown in (d), the control plane protocol of the XX interface is the XX application protocol (XXAP). One possible implementation of XXAP is by including AIoTF information or cells in the next generation application protocol (NGAP). Another possible implementation of XXAP is by carrying a newly defined protocol layer on top of NGAP.

[0164] Figure 7 As shown in (d), the A-IoT device includes an A-IoT radio protocol layer, used to transmit A-IoT service-related information between the A-IoT device and the A-IoT RAN. The A-IoT RAN includes one or more of the following protocol layers: A-IoT radio protocol layer, XXAP, Stream Control Transmission Protocol (SCTP), Internet Protocol (IP), Layer 1 (L1), or Layer 2 (L2). The A-IoT CN includes one or more of the following protocol layers: XXAP, SCTP, IP, L1, or L2.

[0165] Figure 8 A schematic diagram of the CN architecture and protocol stack applicable to the aforementioned communication system 200 is shown.

[0166] like Figure 8As shown in (a), the A-IoT device and the A-IoT-enabled UE can exchange A-IoT data and / or signaling through the A-IoT wireless interface. The A-IoT-enabled UE can exchange A-IoT data and / or signaling with the A-IoT CN through the A-IoT-enabled gNB.

[0167] Figure 8 The A-IoT-enabled UE shown in (a) has general reader / writer functionality, and the A-IoT-enabled gNB has A-IoT RAN node functionality. The general reader / writer functionality and A-IoT RAN node functionality can be found in the above text. Figure 7 The description in the text.

[0168] Figure 8 The CN architecture shown in (a) supports three transmission methods: RRC-based solution, NAS-based solution, or UP-based solution.

[0169] The basic idea of ​​the RRC-based solution is as follows: After the base station (e.g., an A-IoT-enabled gNB) receives an A-IoT service-related request from the A-IoT CN via XXAP, the base station further sends the received relevant information to the A-IoT-enabled UE via an RRC message. When the base station receives A-IoT service-related data / signaling from the A-IoT-enabled UE via an RRC message, the base station transmits the relevant information to the A-IoT CN via XXAP / NGAP.

[0170] Figure 8 (b) shows a schematic diagram of a protocol stack corresponding to the RRC-based solution. Here, the XX interface is the NG control plane (NG-C) interface. One possible implementation of XXAP is to include AIoTF information / cells in the NGAP; another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.

[0171] like Figure 8As shown in (b), an A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, RRC, PDCP, RLC, MAC, or PHY. An A-IoT-enabled gNB includes one or more of the following protocol layers: RRC, PDCP, RLC, MAC, PHY, XXAP, SCTP, IP, L1, or L2. An A-IoT CN includes one or more of the following protocol layers: XXAP, SCTP, IP, L1, or L2.

[0172] like Figure 8 As shown in (c) and (d), for the RRC-based scheme, there are two scenarios between the A-IoT-enabled gNB and the A-IoT CN: direct connection and indirect connection (such as an indirect path via AMF). A direct connection between the A-IoT-enabled gNB and the A-IoT CN can be as follows: Figure 8 As shown in (c), AIoTF can be replaced with A-IoT CN, and Nx / XX are NG interfaces. A-IoT-enabled gNBs and A-IoT CNs can be non-directly connected as follows: Figure 8 As shown in (d), where AIoTF can be replaced by A-IoT CN, and the A-IoT data and / or signaling transmitted between AIoTF and A-IoT-enabled gNB are carried on NGAP.

[0173] The basic idea of ​​the NAS-based solution is as follows: The base station (e.g., an A-IoT-enabled gNB) does not see the A-IoT-related processes. The A-IoT CN and the A-IoT-enabled UE transmit A-IoT-related data / signaling through the DL / UL NAS packets of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits A-IoT-related data / signaling sent to and from the A-IoT-enabled UE). The base station can use the DL NAS transport and UL NAS transport procedures on the NGAP to process the DL / UL NAS packets of the A-IoT-enabled UE.

[0174] Figure 8 (e) in the diagram illustrates a protocol stack corresponding to a NAS-based solution. Figure 8As shown in (e), an A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, A-IoT application protocol (AP), NAS, or 5G access network (AN) protocol layer, etc. An A-IoT-enabled gNB includes one or more of the following protocol layers: 5G-AN protocol layer, NGAP, SCTP, IP, L1, or L2, etc. An AMF includes one or more of the following protocol layers: NAS, NGAP, SCTP, IP, L2, L1, or 5G internal protocol layer, etc. An AIoTF includes one or more of the following protocol layers: A-IoT AP or 5G internal protocol layer, etc.

[0175] The basic idea of ​​the UP-based solution is as follows: The base station (e.g., an A-IoT-enabled gNB) does not see the A-IoT-related processes. The A-IoT service-related data / signaling between the A-IoT CN and the A-IoT-enabled UE is transmitted on the PDU session of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits the A-IoT-related data / signaling sent to and from the A-IoT-enabled UE). The A-IoT-enabled gNB processes the user plane data of the A-IoT-enabled UE through the NG control plane (NG-U) interface general packet radio service (GPRS) tunneling protocol user plane (GTP-U) channel.

[0176] Figure 8 (f) shows a schematic diagram of a protocol stack corresponding to a NAS-based solution. Figure 8As shown in (f), an A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, A-IoT-AP, transport / IP, PDU layer, or 5G-AN protocol layer, etc. An A-IoT-enabled gNB includes one or more of the following protocol layers: 5G-AN protocol layer, GTP-U, user datagram protocol, IP, L1, or L2, etc. The user plane function (UPF) includes one or more of the following protocol layers: PDU layer, GTP-U, UDP, IP, L2, L1, or 5G internal protocol layer, etc. The AIoTF includes one or more of the following protocol layers: transport / IP, or 5G internal protocol layer, etc.

[0177] The above text Figure 7 or Figure 8 The A-IoT CN in the code can also be replaced with a core network element that supports A-IoT. A core network element that supports A-IoT can be one of the following: access and mobile management function (AMF), TMF element, ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), A-IoT aware CN, or other core network elements / nodes / devices that support or enable A-IoT.

[0178] The above text Figure 7 or Figure 8 The UE in this context can be called a UEreader, an A-IoT-enabled UE, or an intermediate node.

[0179] As an example, Figure 9 This is a flowchart illustrating a command processing method applicable to this application. The process in this example includes the following steps.

[0180] Step 1: Perform inventory checks. Please refer to the above text for an introduction to inventory checks.

[0181] Step 2: The CN sends a message to the A-IoT RAN, which instructs the AIoT device to execute a command.

[0182] Step 3: The A-IoT RAN sends DL Data (including Command) to the AIoT device; after receiving it, the AIoT device decodes the Command and executes it; the AIoT device sends UL Data (including Command feedback / response) to the A-IoT RAN through the A-IoT interface.

[0183] Step 4: The A-IoT RAN sends a Command Response to the CN. If the device has a result to return to the RAN after executing the command, the RAN will include the command result when sending the Command Response to the CN.

[0184] The above combination Figures 2 to 9 This application introduces the relevant background and technical terms. Figure 9 In the example described, the uncertainty of the write command size, such as a long write command, may cause the AIoT device to take a long time to execute the write task. This can lead to the reader not receiving timely feedback, resulting in the potential for misjudging the service as failed. Therefore, this application proposes instructing the AIoT device to report the writing status, allowing the reader to be aware of the current write task's progress and thus reducing the probability of misjudging the service as failed.

[0185] The method embodiments of this application are described below with reference to the accompanying drawings. The embodiments provided in this application can be applied to the scenarios shown in the above figures and are not limited thereto. Furthermore, the terms used below are as explained above and will not be repeated hereafter.

[0186] The device in this application mainly refers to an AIoT device located within the coverage area provided by the reader. The AIoT device can be an electronic tag, etc. An electronic tag can also be called a tag, RFID tag, etc. The AIoT device in this application can also be considered a terminal. RFID can be divided into three types: active, passive, and semi-active. Correspondingly, tags can also be divided into passive tags (also called passive tags), semi-passive tags (also called semi-active tags), and active tags (also called active tags). Semi-passive tags and active tags use a backscatter-based communication method, while passive tags use an active carrier wave generation technology. Tag types can be classified based on whether they use a backscatter-based communication method, whether they have energy storage capabilities, or a combination of both. For specific classification methods, please refer to the terminology explanation section.

[0187] The reader / writer in this application can be a handheld or fixed device that reads (and sometimes writes) tag information, or it can be understood as a device that communicates with the tag. It can be a terminal, a base station, a device with read / write capabilities, an IAB node, or a relay node. This application mainly relates to solutions where a terminal is used as a reader / writer.

[0188] The core network equipment in this application includes core network elements for serving AIoT devices. These network elements can be ambient IoT function (AIoTF) or ambient IoT management function (AIoTMF), access and mobility management function (AMF), session management function (SMF), or user plane function (UPF), etc.

[0189] Unless otherwise specified, the means for implementing the functions of the aforementioned devices or network elements in this application may refer to the devices or network elements themselves, or to means capable of supporting the implementation of the functions of the devices or network elements, such as a chip system or chip, specifically a SoC or modem, which may be installed in the devices or network elements. In the embodiments of this application, the chip system may be composed of chips, or may include chips and other discrete devices.

[0190] It should also be noted that some embodiments in this article use a 5G system as an example to introduce specific solution details. It is understood that when this solution is used in other communication systems, such as LTE systems, or future communication systems, the messages, channels, or information in the solution can be replaced with messages, channels, or information in other communication systems that can achieve the corresponding functions, and this application does not limit this.

[0191] As an example, Figure 10 This is a schematic diagram of a communication method 1000 provided in an embodiment of this application. Figure 10 The method 1000 shown may include the following steps.

[0192] Optionally, method 1000 includes S1001, performing inventory checks. Inventory checks, also known as stocktaking operations, can obtain tag identification information.

[0193] For example, the inventory process includes the following steps.

[0194] Step 1: The first core network element sends an inventory request to the first reader / writer. The inventory request includes the device ID of at least one AIoT device.

[0195] At least one AIoT device includes the first AIoT device.

[0196] Optionally, the inventory request may also include a command indication, which is used to instruct the execution of command operations after the inventory process.

[0197] Optionally, if the first reader / writer is a terminal, then in step 1, the first core network element sends an inventory request #1 to the first access network device, and then the first access network device sends an inventory request #2 to the first reader / writer based on the inventory request #1. Inventory request #1 and inventory request #2 include the identifier of at least one A-IoT device.

[0198] The following description uses the inventory of the first AIoT device as an example to illustrate the other steps in the inventory process.

[0199] Step 2: The first reader triggers the first AIoT device to access the network via the A-IoT interface between the first reader and the first AIoT device.

[0200] Step 3: The first AIoT device performs inventory and sends uplink data to the first reader / writer. The uplink data includes the device ID of the first AIoT device.

[0201] Step 4: The first reader sends an invention report message to the first core network element. The invention report message includes the device ID of the first AIoT device.

[0202] Optionally, the inventory report message may also include an identifier assigned by the first access network device to the first AIoT device (e.g., a device NGAP ID, where NGAP stands for Next Generation Application Protocol). The identifier assigned by the first access network device to the first AIoT device is used to identify the first AIoT device in the first access network device and the first core network element.

[0203] It should be noted that S1001 is an optional step. For example, if the command business executed by method 1000 is implemented through a "command only" process, then method 1000 may not include S1001.

[0204] Optionally, the method 1000 includes S1002, in which the first core network element sends message #A, and correspondingly, the first reader / writer receives message #A.

[0205] Among them, message #A instructs the first AIoT device to execute the first command, which may include write operations, read operations, etc.

[0206] Optionally, if the first reader is a terminal, then in S1002, the first reader sends message #1a (an example of message #A) to the first access network device, and then the first access network device sends message #1b (an example of message #A) to the first core network element based on the received message #1a.

[0207] S1010, the first reader sends the first message, and correspondingly, the first AIoT device receives the first message.

[0208] The first message instructs the first AIoT device to execute the first command. It should be understood that the name of the first command does not limit this application. For example, the first command may also be called a command service, service, or operation.

[0209] In one implementation, the first command can be a write command, which can also be called a write business, write task, or write operation. This application does not limit the name.

[0210] In another implementation, the first command can be a read command, which can also be called a read business, read task, or read operation. This application does not limit the name.

[0211] It should be noted that the following description uses the example of the first message instructing the first AIoT device to execute the write command #A (an example of the first command).

[0212] The first message can also indicate the resources used by the first AIoT device to send messages related to the write command #A. The first message can indicate one or more resources used by the first AIoT device to send messages related to the write command #A. For example, the first message can indicate a first resource, a second resource, a third resource, ..., the Nth resource (N is a positive integer). When N is 1, it means that the first message indicates one resource used by the first AIoT device to send messages related to the write command #A; when N is an integer greater than 1, it means that the first message indicates multiple resources used by the first AIoT device to send messages related to the write command #A. For ease of description, the following description uses resources #A, #B, ... as examples in the specific steps.

[0213] The resource indicated by the first message (i.e., the first resource, the second resource, ..., the Nth resource) can be used to send the current write command #A by the first AIoT device in one of the following states: the first AIoT device receives the first message, the first AIoT device is executing the write command #A, or the write command #A has been completed.

[0214] For example, a first message indicates that a first resource can be used by a first AIoT device to send the current write command #A when the first AIoT device has received the first message. At this time, the first AIoT device can send a third message based on the first resource, the third message indicating that the state of the write command #A is that the first AIoT device has received the first message.

[0215] For example, a first message indicates that a first resource can be used by a first AIoT device to send the current write command #A when the first AIoT device has received the first message, and a first message also indicates that a second resource can be used by the first AIoT device to send the current write command #A when the write command #A has been completed. In this case, the first AIoT device can send a third message based on the first resource, indicating that the write command #A has been received by the first AIoT device. The first AIoT device can also send a fourth message based on the second resource, indicating that the write command #A has been completed.

[0216] In one implementation, the time intervals between two adjacent resources are equal, meaning the resources can be periodic. In other words, the first AIoT device reports the execution status of the first command every time interval T.

[0217] Specifically, the time interval between the first resource and the second resource is T, the time interval between the second resource and the third resource is T, the time interval between the third resource and the fourth resource is T, ..., the time interval between the third resource and the fourth resource is T, ..., the time interval between the (N-1)th resource and the Nth resource is T. In other words, the first message can also indicate the periodic resources used by the first AIoT device to send and write command #A related messages. The time intervals between the first resource and the second resource ... and the Nth resource are the same. It should be understood that "first", "second" ... "Nth" does not limit this application. For example, the time interval between the first resource and the third resource is T, the time interval between the third resource and the second resource is T, the time interval between the second resource and the fourth resource is T, etc.

[0218] In another implementation, at least one of the time intervals between two adjacent resources differs from the remaining time intervals. In other words, the time intervals between two adjacent resources can be partially the same or completely different. In other words, the first AIoT device can report the execution status of the first command at regular intervals, where these intervals can be non-periodic.

[0219] Specifically, the time interval between the first resource and the second resource is T1, the time interval between the second resource and the third resource is T2, the time interval between the third resource and the fourth resource is T3, and so on, with the time interval between the (N-1)th resource and the Nth resource being T. N-1 Among them, T1, t2, T3...T N-1 The resources can be all different; they can be partially the same and partially different; they can also exhibit a certain regular distribution, such as an arithmetic sequence. In other words, the first message can also indicate the resources used by the first AIoT device to send N messages related to the write command #A, and the first resource is aperiodic with the second resource, ... and the Nth resource.

[0220] Optionally, the method 1000 further includes S1020, in which the first AIoT device sends Feedback1 (an example of a third message), and correspondingly, the first reader receives Feedback1.

[0221] Feedback1 indicates that the first AIoT device has received the first message, that is, Feedback1 indicates that the first AIoT device has received the write command #A.

[0222] In one implementation, the first message also indicates a seventh resource, which is used by the first AIoT device to send Feedback1. Therefore, the first AIoT device can send Feedback1 in resource #A (an example of the seventh resource) indicated by the first message, and correspondingly, the first reader / writer receives Feedback1 in resource #A.

[0223] Optionally, the method 1000 further includes S1030, in which the first reader sends a tenth message, and correspondingly, the first core network element receives the tenth message.

[0224] The tenth message indicates that the first AIoT device has received the first message. After receiving the tenth message, the first reader / writer can determine that the downlink data (first message) has been successfully sent.

[0225] Optionally, if the first reader / writer is a terminal, then in S1030, the first reader / writer sends message #10a (an example of the tenth message) to the first access network device, and then the first access network device sends message #10b (an example of the tenth message) to the first core network element based on the received message #10a. It should be understood that step S1020 is executed before step S1040.

[0226] S1040, the first AIoT device sends Feedback2#1 (an example of the second message), and correspondingly, the first reader receives Feedback2#1.

[0227] Feedback2#1 indicates that the first AIoT device is executing write command #A. In other words, Feedback2#1 indicates that the status of write command #A is in progress.

[0228] In one implementation, the first message may also indicate resource #B (an example of a first resource), which is used by the first AIoT device to send Feedback2#1. Therefore, the first AIoT device can send Feedback2#1 on resource #B, and correspondingly, the first reader / writer can receive Feedback2#1 on resource #B.

[0229] Optionally, the method 1000 further includes S1041, in which the first AIoT device sends Feedback2#2 (an example of the fifth message), and correspondingly, the first reader receives Feedback2#2.

[0230] Feedback2#2 indicates that the first AIoT device is executing write command #A. In other words, the fifth message indicates that the status of write command #A is in progress.

[0231] In one implementation, the first message may also indicate resource #C (an example of a third resource), which is used by the first AIoT device to send Feedback2#2. Therefore, the first AIoT device can send Feedback2#2 on resource #C, and correspondingly, the first reader / writer can receive Feedback2#2 on resource #C.

[0232] Optionally, the method 1000 may further include: the first AIoT device sending Feedback2#3, and correspondingly, the first reader receiving Feedback2#3.

[0233] Feedback2#3 indicates that the first AIoT device is executing write command #A. In other words, Feedback2#3 indicates that the status of write command #A is in progress.

[0234] In one implementation, the first message can also indicate resource #D, which is used by the first AIoT device to send Feedback2#3. Therefore, the first AIoT device can send Feedback2#3 on resource #D, and correspondingly, the first reader / writer can receive Feedback2#3 on resource #D.

[0235] It should be understood that Feedback2#1, Feedback2#2, and Feedback2#3 indicate that the first AIoT device is executing the write command #A. Feedback2#1, Feedback2#2, and Feedback2#3 can be collectively referred to as Feedback2.

[0236] It should be understood that steps S1040 to S1041 are merely examples. The first reader / writer can allocate resources to the first AIoT device to execute the write command #A based on the capabilities of the first AIoT device or the amount of data in the write command #A. The allocated resources may include the resources #A, #B, #C, and #D listed above, and may also include multiple resources, such as resources #E and #F. Of course, if the amount of data in the write command #A is small, the allocation of resources can be reduced. For example, resources #A and #B can be allocated to messages related to the write command #A.

[0237] It should also be understood that the time interval between resource #A and resource #B is T1, the time interval between resource #B and resource #C is T2, and the time interval between resource #C and resource #D is T3. T1, T2, and T3 can all be the same, all different, or partially the same and partially different. In other words, during the execution of write command #A, the first AIoT device can send Feedback2 at regular intervals, which can be the same or different. Correspondingly, the first reader receives Feedback2, allowing it to confirm that write command #A is being executed, thus avoiding excessive waiting time and reducing the possibility of falsely judging write command #A as failed.

[0238] Feedback2 can be implemented using at least one bit. If this one bit has the first value, it indicates that the first AIoT device is executing the task; in other words, the task is in a writing state. If this one bit has the second value, it indicates that the first AIoT device is not currently executing the task; in other words, the task is not in a writing state. The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1"; or the first value can be "1" and the second value can be "0".

[0239] S1050, the first AIoT device sends Feedback3 (an example of the fourth message), and correspondingly, the first reader receives Feedback3.

[0240] Feedback3 indicates the result of the write command #A. The result of the write command #A includes two cases: the write command #A was executed successfully or failed.

[0241] Feedback3 can be implemented using at least one bit. If this one bit has the first value, it indicates that the first AIoT device successfully executed the task; in other words, the task status is "write successful." If this one bit has the second value, it indicates that the first AIoT device failed to execute the task; in other words, the task status is "write failed." The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1," or the first value can be "1" and the second value can be "0."

[0242] Optionally, when Feedback3 indicates a write failure, it can also include the reason for the failure. The reason for the failure is not limited. For example, the first AIoT device may be out of power; or the first AIoT device may have insufficient battery power. In this case, Feedback3 is implemented through at least two fields. For example, the first field indicates whether the write was successful or failed; when the first field indicates a write failure, the second field indicates the reason for the failure; when the first field indicates a write success, the second field can be set to "0".

[0243] In one implementation, the first message may also indicate resource #E (an example of a second resource), which is used by the first AIoT device to send Feedback3. Therefore, the first AIoT device can send Feedback3 on resource #E, and correspondingly, the first reader / writer can receive Feedback3 on resource #E.

[0244] It should be understood that the time interval between resource #E and resource #D used by the first AIoT device to send Feedback2#3 is T4. T4 can be the same as T1, T2 and T3, or it can be the same as some of them, or it can be different from all of them.

[0245] The first reader receives Feedback3 and learns that there are two possible implementation methods for the execution result.

[0246] In the first possible implementation, Feedback3 is carried in upper-layer signaling, such as a device NAS protocol data unit (PDU). This means the execution result can be transparently transmitted to the first core network element via NAS, allowing the first core network element to explicitly write that command #A has finished execution. Then, the first core network element sends Feedback3 to the first reader / writer, allowing the reader / writer to explicitly write that command #A has finished execution. It should be understood that in this implementation, if the first reader / writer and the first core network element communicate via a non-direct connection (e.g., an AMF node), the AMF node does not obtain information from the upper-layer signaling messages; that is, the AMF node is unaware of the information in Feedback3. The AMF node will directly transparently transmit the Feedback3 received from the first reader / writer to the first core network element.

[0247] In the second possible implementation, Feedback3 is sent to the first reader / writer via medium access control (MAC) signaling. The first reader / writer receives Feedback3, thus confirming that the write command #A has been executed. Furthermore, in this method, the method 1000 also includes S1050, where the first reader / writer sends an eleventh message, which is received by the first core network element. The eleventh message indicates whether the write command #A was executed successfully or failed, so that the first core network element can know the result of the write command #A.

[0248] Optionally, if the first reader is a terminal, then in S1050, the first reader sends message #11a (an example of the eleventh message) to the first access network device, and then the first access network device sends message #11b (an example of the eleventh message) to the first core network element based on the received message #11a.

[0249] As an example, Figure 11 This is a schematic diagram of another communication method 1100 provided in an embodiment of this application. Figure 11 The method shown may include the following steps.

[0250] Optionally, method 1100 includes S1101, performing inventory operations. Inventory operations, also known as stocktaking operations, can obtain tag identification information. For details on the implementation, please refer to the description in method 1000, which will not be repeated here.

[0251] Optionally, the method 1100 includes S1102, in which the first core network element sends message #A, and correspondingly, the first reader / writer receives message #A.

[0252] Among them, message #A instructs the first AIoT device to execute the first command, which may include write operations, read operations, etc.

[0253] Optionally, if the first reader / writer is a terminal, then in S1102, the first reader / writer sends message #1a (an example of message #A) to the first access network device, and then the first access network device sends message #1b (an example of message #A) to the first core network element based on the received message #1a.

[0254] S1110, the first reader sends the first message, and correspondingly, the first AIoT device receives the first message.

[0255] The first message instructs the first AIoT device to execute the first command. It should be understood that the name of the first command does not limit this application. For example, the first command may also be called a command service, service, or operation.

[0256] In one implementation, the first command can be a write command, which can also be called a write business, write task, or write operation. This application does not limit the name.

[0257] In another implementation, the first command can be a read command, which can also be called a read business, read task, or read operation. This application does not limit the name.

[0258] It should be noted that the following description uses the example of the first message instructing the first AIoT device to execute the write command #A (an example of the first command).

[0259] S1120, the first reader sends the sixth message, and correspondingly, the first AIoT device receives the sixth message.

[0260] The sixth message can indicate the resource used by the first AIoT device to send the write command #A related message. The resource indicated by the sixth message for sending the write command #A related message by the first AIoT device can be one or multiple. For example, the sixth message can indicate a first resource, a second resource, a third resource, ..., the Nth resource (N is a positive integer). When N is 1, it indicates that the resource indicated by the sixth message for sending the write command #A related message by the first AIoT device is one; when N is an integer greater than 1, it indicates that the resource indicated by the sixth message for sending the write command #A related message by the first AIoT device is multiple. For ease of description, the following description uses resource #A, resource #B, ... as examples in the specific steps.

[0261] The resource indicated by the sixth message (i.e., the first resource, the second resource, ..., the Nth resource) can be used to send the current write command #A by the first AIoT device in one of the following states: the first AIoT device receives the sixth message, the first AIoT device is executing the write command #A, or the write command #A has been completed.

[0262] In one implementation, the time intervals between two adjacent resources are equal, meaning the resources can be periodic. In other words, the first AIoT device reports the execution status of the first command every time interval T.

[0263] Specifically, the time interval between the first resource and the second resource is T, the time interval between the second resource and the third resource is T, the time interval between the third resource and the fourth resource is T, ..., the time interval between the third resource and the fourth resource is T, ..., the time interval between the (N-1)th resource and the Nth resource is T. In other words, the first message can also indicate the periodic resources used by the first AIoT device to send and write command #A related messages. The time intervals between the first resource and the second resource ... and the Nth resource are the same. It should be understood that "first", "second" ... "Nth" does not limit this application. For example, the time interval between the first resource and the third resource is T, the time interval between the third resource and the second resource is T, the time interval between the second resource and the fourth resource is T, etc.

[0264] In another implementation, at least one of the time intervals between two adjacent resources differs from the remaining time intervals. In other words, the time intervals between two adjacent resources can be partially the same or completely different. In other words, the first AIoT device can report the execution status of the first command at regular intervals, where these intervals can be non-periodic.

[0265] Specifically, the time interval between the first resource and the second resource is T1, the time interval between the second resource and the third resource is T2, the time interval between the third resource and the fourth resource is T3, and so on, with the time interval between the (N-1)th resource and the Nth resource being T. N-1 Among them, T1, T2, T3...T N-1 The resources can be all different; they can be partially the same and partially different; they can also exhibit a certain regular distribution, such as an arithmetic sequence. In other words, the first message can also indicate the resources used by the first AIoT device to send N messages related to the write command #A, and the first resource is aperiodic with the second resource, ... and the Nth resource.

[0266] It should be understood that the sixth message is sent after the first reader sends the first message. In other words, the first reader may first indicate the write command #A and then send an indication message (such as the sixth message) indicating the resource related to the write command #A.

[0267] Optionally, the method 1100 further includes S1130, in which the first AIoT device sends Feedback1 (an example of a third message), and correspondingly, the first reader receives Feedback1.

[0268] Feedback1 indicates that the first AIoT device has received the first message, that is, Feedback1 indicates that the first AIoT device has received the write command #A.

[0269] In one implementation, the sixth message also indicates an eighth resource, which is used by the first AIoT device to send Feedback1. Therefore, the first AIoT device can send Feedback1 in resource #A (an example of the eighth resource) indicated by the sixth message, and correspondingly, the first reader / writer receives Feedback1 in resource #A.

[0270] Optionally, the method 1100 further includes S1140, in which the first reader sends a tenth message, and correspondingly, the first core network element receives the tenth message.

[0271] The tenth message indicates that the first AIoT device has received the first message. After receiving the tenth message, the first reader / writer can determine that the downlink data (first message) has been successfully sent.

[0272] Optionally, if the first reader is a terminal, then in S1140, the first reader sends message #10a (an example of the tenth message) to the first access network device, and then the first access network device sends message #10b (an example of the tenth message) to the first core network element based on the received message #10a.

[0273] It should be understood that step S1130 is performed before step S1150.

[0274] S1150, the first AIoT device sends Feedback2#1 (an example of the second message), and correspondingly, the first reader receives Feedback2#1.

[0275] Feedback2#1 indicates that the first AIoT device is executing write command #A. In other words, the second message indicates that the status of write command #A is in progress.

[0276] In one implementation, the sixth message may also indicate resource #B (an example of the first resource), which is used by the first AIoT device to send Feedback2#1. Therefore, the first AIoT device can send Feedback2#1 on resource #B, and correspondingly, the first reader / writer can receive Feedback2#1 on resource #B.

[0277] Optionally, the method 1100 further includes S1151, in which the first AIoT device sends Feedback2#2 (an example of the fifth message), and correspondingly, the first reader receives Feedback2#2.

[0278] Feedback2#2 indicates that the first AIoT device is executing write command #A. In other words, the fifth message indicates that the status of write command #A is in progress.

[0279] In one implementation, the sixth message may also indicate resource #C (an example of the third resource), which is used by the first AIoT device to send Feedback2#2. Therefore, the first AIoT device can send Feedback2#2 on resource #C, and correspondingly, the first reader / writer can receive Feedback2#2 on resource #C.

[0280] Optionally, the method 1100 may further include: the first AIoT device sending Feedback2#3, and correspondingly, the first reader receiving Feedback2#3.

[0281] Feedback2#3 indicates that the first AIoT device is executing write command #A. In other words, Feedback2#3 indicates that the status of write command #A is in progress.

[0282] In one implementation, the sixth message can also indicate resource #D, which is used by the first AIoT device to send Feedback2#3. Therefore, the first AIoT device can send Feedback2#3 on resource #D, and correspondingly, the first reader / writer can receive Feedback2#3 on resource #D.

[0283] It should be understood that Feedback2#1, Feedback2#2, and Feedback2#3 indicate that the first AIoT device is executing the write command #A. Feedback2#1, Feedback2#2, and Feedback2#3 can be collectively referred to as Feedback2.

[0284] It should be understood that steps S5110 to S1151 are merely examples. The first reader / writer can allocate resources to the first AIoT device to execute the write command #A based on the capabilities of the first AIoT device or the amount of data in the write command #A. The allocated resources may include the resources #A, #B, #C, and #D listed above, and may also include multiple resources, such as resources #E and #F. Of course, if the amount of data in the write command #A is small, the allocation of resources can be reduced. For example, resources #A and #B can be allocated to messages related to the write command #A.

[0285] It should also be understood that the time interval between resource #A and resource #B is T1, the time interval between resource #B and resource #C is T2, and the time interval between resource #C and resource #D is T3. T1, T2, and T3 can all be the same, all different, or partially the same and partially different. In other words, during the execution of write command #A, the first AIoT device can send Feedback2 at regular intervals, which can be the same or different. Correspondingly, the first reader receives Feedback2. This allows the first reader to confirm that write command #A is being executed, thereby avoiding excessive waiting time and reducing the possibility of falsely judging write command #A as failed.

[0286] Feedback2 can be implemented using at least one bit. If this one bit has the first value, it indicates that the first AIoT device is executing the task; in other words, the task is in a writing state. If this one bit has the second value, it indicates that the first AIoT device is not currently executing the task; in other words, the task is not in a writing state. The first and second values ​​can be different. For example, the first value can be "0" and the second value can be "1"; or the first value can be "1" and the second value can be "0".

[0287] S1160, the first AIoT device sends Feedback3 (an example of the fourth message), and correspondingly, the first reader receives Feedback3.

[0288] Feedback3 indicates the result of the write command #A. The result of the write command #A includes two cases: the write command #A was executed successfully or failed.

[0289] Feedback3 can be implemented using at least one bit. If this one bit has the first value, it indicates that the first AIoT device successfully executed the task; in other words, the task status is "write successful." If this one bit has the second value, it indicates that the first AIoT device failed to execute the task; in other words, the task status is "write failed." The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1," or the first value can be "1" and the second value can be "0."

[0290] Optionally, when Feedback3 indicates a write failure, it can also include the reason for the failure, which is not limited. For example, the first AIoT device may be out of power; or the first AIoT device may have insufficient battery power. In this case, Feedback3 is implemented through at least two fields. For example, the first field indicates whether the write was successful or failed. When the first field indicates a write failure, the second field indicates the reason for the failure; when the first field indicates a write success, the second field can be set to "0".

[0291] In one implementation, the sixth message may also indicate resource #E (an example of a second resource), which is used by the first AIoT device to send Feedback3. Therefore, the first AIoT device can send Feedback3 on resource #E, and correspondingly, the first reader / writer can receive Feedback3 on resource #E.

[0292] It should be understood that the time interval between resource #E and resource #D used by the first AIoT device to send Feedback2#3 is T4. T4 can be the same as T1, t2 and T3, or it can be the same as some of them, or it can be different from all of them.

[0293] The first reader receives Feedback3 and learns that there are two possible implementation methods for the execution result.

[0294] In the first possible implementation, Feedback3 is carried within the upper-layer signaling, such as a device NAS protocol data unit (PDU). This means the execution result can be transparently transmitted to the first core network element via NAS, allowing the first core network element to explicitly write that command #A has finished execution. Then, the first core network element sends Feedback3 to the first reader / writer, allowing the reader / writer to explicitly write that command #A has finished execution. It should be understood that in this implementation, if the first reader / writer and the first core network element communicate via a non-direct connection (e.g., an AMF node), the AMF node does not obtain information from the upper-layer signaling messages; that is, the AMF node is unaware of the information in Feedback3. The AMF node will directly transparently transmit the Feedback3 received from the first reader / writer to the first core network element.

[0295] In the second possible implementation, Feedback3 is sent to the first reader / writer via medium access control (MAC) signaling. The first reader / writer receives Feedback3, thus confirming that the write command #A has been executed. Furthermore, in this method, the method 1100 also includes S1170, where the first reader / writer sends an eleventh message. Correspondingly, the first core network element receives the eleventh message, which indicates whether the write command #A was executed successfully or failed. In this way, the first core network element can know the result of the write command #A.

[0296] Optionally, if the first reader is a terminal, then in S1170, the first reader sends message #11a (an example of the eleventh message) to the first access network device, and then the first access network device sends message #11b (an example of the eleventh message) to the first core network element based on the received message #11a.

[0297] It should be understood that the sixth message can be sent at any time after the first reader sends the first message and before receiving Feedback3. Each resource indicated by the sixth message—the first resource, the second resource, the third resource…the Nth resource—is a specific resource that can be used to provide feedback on the current status of the first AIoT device executing the first command. Figure 11 In the illustrated embodiment, the sixth message is sent before the first reader receives the third message, but this application does not limit this. For example, the sixth message may also be sent after the first reader receives the third message; or, for another example, the sixth message may be sent after the first reader receives the second message.

[0298] The above, combined with Figure 10 and Figure 11 Two implementation methods were introduced respectively. Figure 10 The embodiment shown in the figure instructs the first AIoT device to send multiple resources related to the first command at the same time as the first reader sends the first command. The first AIoT device can provide feedback on the execution progress of the first write command based on the multiple resources, so that the first reader can know the execution status of the first command according to the instructed resources. Figure 11 The embodiment shown is that after the first reader sends the first command, it sends a sixth message to instruct the first AIoT device to send multiple resources related to the first command. The first AIoT device can use these multiple resources to provide feedback on the execution progress of the first write command, so that the first reader can know the execution status of the first command according to the instructed resources.

[0299] The following is combined with Figure 12 This paper introduces a method for a first reader / writer to indicate a single resource, and a first AIoT device to provide feedback on the execution progress of the current first command based on that single resource.

[0300] As an example, Figure 12 This is a schematic diagram of another communication method 1200 provided in an embodiment of this application. Figure 12 The method shown may include the following steps.

[0301] Optionally, method 1200 includes S1201, performing inventory operations. Inventory operations, also known as stocktaking operations, can obtain tag identification information. For details on the implementation, please refer to the description in method 1000, which will not be repeated here.

[0302] Optionally, the method 1200 includes S1202, in which the first core network element sends message #A, and correspondingly, the first reader / writer receives the message #A.

[0303] Among them, message #A indicates a command service request, which may include write services, read services, etc.

[0304] Optionally, if the first reader is a terminal, then in S1202, the first reader sends message #1a (an example of message #A) to the first access network device, and then the first access network device sends message #1b (an example of message #A) to the first core network element based on the received message #1a.

[0305] S1210, the first reader sends the first message, and correspondingly, the first AIoT device receives the first message.

[0306] The first message instructs the first AIoT device to execute the first command. It should be understood that the name of the first command does not limit this application. For example, the first command may also be called a command service, service, or operation.

[0307] In one implementation, the first command can be a write command, which can also be called a write business, write task, or write operation. This application does not limit the name.

[0308] In another implementation, the first command can be a read command, which can also be called a read business, read task, or read operation. This application does not limit the name.

[0309] It should be noted that the following description uses the example of the first message instructing the first AIoT device to execute the write command #A (an example of the first command).

[0310] Optionally, the method 1200 further includes S1220, in which the first AIoT device sends Feedback1 (an example of second feedback information), and correspondingly, the first reader receives Feedback1.

[0311] Optionally, the method 1200 further includes S1230, whereby the first reader sends Feedback1, and correspondingly, the first core network element receives Feedback1.

[0312] Feedback1 instructs the first AIoT device to receive the first message. After receiving Feedback1, the first reader considers the downlink data (first message) to have been successfully sent.

[0313] Optionally, if the first reader is a terminal, then in S1230, the first reader sends message #10a (an example of the tenth message) to the first access network device, and then the first access network device sends message #10b (an example of the tenth message) to the first core network element based on the received message #10a.

[0314] S1240, the first reader sends the sixth message, and correspondingly, the first AIoT device receives the sixth message.

[0315] The sixth message indicates resource #F (an example of the fourth resource), which is used to send information related to the write command #A.

[0316] It should be understood that, Figure 12 In the described embodiment, the sixth message indicates that the resource used by the first AIoT device to send a message related to the write command #A is a resource, namely resource #F.

[0317] S1250, the first AIoT device sends feedback2#1 (an example of the second message), and correspondingly, the first reader receives feedback2#1.

[0318] Feedback2#1 indicates that the status of write command #A is in progress.

[0319] In one implementation, the first AIoT device sends feedback2#1 on resource #F.

[0320] Feedback2#1 is implemented using at least 1 bit. For details on its implementation, please refer to the description in method 1000.

[0321] Through steps S1240 and S1250, the first reader / writer can query the execution status of the write command #A at any time by sending a sixth message. In this way, the first AIoT device can send a second message based on the resource #F indicated by the sixth message to provide feedback on the current execution progress of the write command #A, indicating whether it is writing or executing, so that the first reader / writer can know the progress of the write task.

[0322] Optionally, the method 1200 further includes S1241, in which the first reader sends a seventh message, and correspondingly, the first AIoT device receives the seventh message.

[0323] The seventh message indicates resource #G (an example of the fifth resource), which is used to send information related to the write command #A.

[0324] It should be understood that, Figure 12 In the described embodiment, the seventh message indicates that the resource used by the first AIoT device to send a message related to the write command #A is a resource, namely resource #G.

[0325] In this implementation, the method 1200 further includes S1251, whereby the first AIoT device sends feedback2#2 (an example of the eighth message), and correspondingly, the first reader receives feedback2#1.

[0326] Feedback2#2 indicates that the status of write command #A is in progress.

[0327] In one implementation, the first AIoT device sends feedback2#2 on resource #G.

[0328] Feedback2#2 is implemented using at least 1 bit. For details on its implementation, please refer to the description in method 1000.

[0329] Optionally, the method 1200 may further include: the first reader sending a twelfth message, and correspondingly, the first AIoT device receiving the twelfth message.

[0330] The twelfth message indicates resource #H, which is used to send information related to the write command #A.

[0331] In this implementation, the method 1200 further includes: the first AIoT device sending feedback2#3, and correspondingly, the first reader / writer receiving feedback2#3.

[0332] Feedback2#3 indicates that the status of write command #A is in progress.

[0333] In one implementation, the first AIoT device sends feedback2#3 on resource #H.

[0334] Feedback2#3 is implemented using at least 1 bit. For details on its implementation, please refer to the description in method 1000.

[0335] It should be understood that Feedback2#1, Feedback2#2, and Feedback2#3 indicate that the first AIoT device is executing the write command #A. Feedback2#1, Feedback2#2, and Feedback2#3 can be collectively referred to as Feedback2.

[0336] It should be understood that the first reader / writer can allocate resources for the first AIoT device to execute the write command #A based on the capabilities of the first AIoT device or the amount of data in the write command #A. The allocated resources may include the resources #F, #G, and #H listed above, or multiple resources, such as resources #I and #G. Of course, if the amount of data in the write command #A is small, the allocation of resources can be reduced. For example, resources #F and #H can be allocated for messages related to the write command #A.

[0337] It should also be understood that before receiving the execution result of write command #A, the first reader / writer can periodically indicate resources for write command #A to obtain information about its execution progress. The time intervals can be predefined or configured. For example, the time interval between resources #F and #G is T1, between resources #G and #H is T2, between resources #H and #I is T3, and between resources #I and #G is T4. T1, T2, T3, and T4 can all be the same, all different, or partially the same and partially different. In other words, during the execution of write command #A, the first reader / writer can allocate resources for related messages of write command #A periodically. The intervals can be the same or different, and the first AIoT device provides feedback on the current progress of write command #A based on these resource allocations. This allows the first reader / writer to clearly know that write command #A is being executed, thus avoiding excessive waiting time and reducing the possibility of misjudging write command #A as failed.

[0338] S1243, the first reader sends the ninth message, and correspondingly, the first AIoT device receives the ninth message.

[0339] The ninth message indicates resource #I (an example of the sixth resource), which is used to send information related to the write command #A.

[0340] S1260, the first AIoT device sends Feedback3 (an example of the fourth message), and correspondingly, the first reader receives Feedback3.

[0341] Feedback3 indicates the task execution result to be written.

[0342] Feedback3 includes two scenarios: Scenario 1: Write successful; Scenario 2: Write failed.

[0343] Feedback3 is implemented using at least one bit. If this one bit has the first value, it indicates that the first AIoT device successfully executed the task; in other words, the task status is "write successful." If this one bit has the second value, it indicates that the first AIoT device failed to execute the task; in other words, the task status is "write failed." The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1," or the first value can be "1" and the second value can be "0."

[0344] Optionally, when Feedback3 indicates a write failure, it can also include the reason for the failure, which is not limited. For example, the first AIoT device may be out of power; or the first AIoT device may have insufficient battery power. In this case, Feedback3 is implemented through at least two fields. For example, the first field indicates whether the write was successful or failed. When the first field indicates a write failure, the second field indicates the reason for the failure; when the first field indicates a write success, the second field can be set to "0".

[0345] In one implementation, the first AIoT device can send Feedback3 on resource #I, and correspondingly, the first reader / writer can receive Feedback3 on resource #I.

[0346] It should be understood that the time interval between resource #I and resource #H used by the first AIoT device to send Feedback2#3 in S1242 above is T4. T4 can be the same as T1, T2 and T3, or it can be the same as some of them, or it can be different from all of them.

[0347] The first reader receives Feedback3 and learns that there are two possible implementation methods for the execution result.

[0348] In the first possible implementation, Feedback3 is carried within the upper-layer signaling, such as a device NAS protocol data unit (PDU). This means the execution result can be transparently transmitted to the first core network element via NAS, allowing the first core network element to explicitly write that command #A has finished execution. Then, the first core network element sends Feedback3 to the first reader / writer, allowing the reader / writer to explicitly write that command #A has finished execution. It should be understood that in this implementation, if the first reader / writer and the first core network element communicate via a non-direct connection (e.g., an AMF node), the AMF node does not obtain information from the upper-layer signaling messages; that is, the AMF node is unaware of the information in Feedback3. The AMF node will directly transparently transmit the Feedback3 received from the first reader / writer to the first core network element.

[0349] In a second possible implementation, Feedback3 is sent to the first reader / writer via medium access control (MAC) signaling. The first reader / writer receives Feedback3, thus confirming the completion of the write task. Further, in this implementation, method 1200 also includes step S1270, where the first reader / writer sends Feedback3, and the first core network element receives Feedback3, confirming the completion of the write task. Optionally, if the first reader / writer is a terminal, in step S1270, the first reader / writer sends message #11a (an example of the eleventh message) to the first access network device, and then the first access network device sends message #11b (an example of the eleventh message) to the first core network element based on the received message #11a.

[0350] The above Figure 12 The illustrated embodiment describes how a first AIoT device can provide feedback on the execution progress of the current write command #A based on a resource sent at any time by a first reader / writer. The following section combines... Figure 13 This paper introduces one possible implementation method for the first AIoT device to report execution progress.

[0351] As an example, Figure 13 This is a schematic diagram of another communication method 1300 provided in an embodiment of this application. Figure 13 The method shown may include the following steps.

[0352] Optionally, method 1300 includes S1301, performing inventory operations. For details on the implementation, please refer to the description in method 1000; it will not be repeated here.

[0353] Optionally, the method 1300 includes S1302, in which the first core network element sends message #A, and correspondingly, the first reader receives message #A.

[0354] Optionally, if the first reader is a terminal, then in S1302, the first reader sends message #1a (an example of message #A) to the first access network device, and then the first access network device sends message #1b (an example of message #A) to the first core network element based on the received message #1a.

[0355] Among them, message #A instructs the first AIoT device to execute the first command, which may include write operations, read operations, etc.

[0356] S1310, the first reader sends the first message, and correspondingly, the first AIoT device receives the first message.

[0357] The first message instructs the first AIoT device to execute a command service. It should be understood that the name of the command service is not limited in this application. For example, the first command can also be called a command or a service.

[0358] In one implementation, the first command can be a write command, which can also be called a write business, write task, or write operation. This application does not limit the name.

[0359] In another implementation, the first command can be a read command, which can also be called a read business, read task, or read operation. This application does not limit the name.

[0360] It should be noted that the following description uses the example of the first message instructing the first AIoT device to execute the write command #A (an example of the first command).

[0361] S1320, the first AIoT device sends a D2R data segment (an example of second information), and correspondingly, the first reader receives the D2R segment.

[0362] The D2R segment can indicate that the write command #A is in execution. The D2R segment can include MAC padding bits and / or remaining bit size, where the remaining bit size is non-zero.

[0363] S1330, the first reader sends the sixth message, and correspondingly, the first AIoT device receives the sixth message.

[0364] The sixth message indicates resource #F (an example of the fourth resource), which is used to send information related to the write command #A.

[0365] S1340, the first AIoT device sends a D2R segment (an example of the second message), and correspondingly, the first reader receives the D2R segment.

[0366] The first AIoT device can send a D2R segment on resource #F, where the D2R segment can indicate that the execution status of write command #A is in progress. The D2R segment can include Media Access Control padding bits and / or remaining bit size, where the remaining bit size is non-zero.

[0367] S1350, the first AIoT device sends a D2R segment (an example of the fourth message), and correspondingly, the first reader receives the D2R segment.

[0368] The D2R segment indicates that the execution status of write command #A is complete. At this point, the remaining bit size is 0, indicating a successful write.

[0369] It should be understood that prior to S1350, the first reader / writer could periodically indicate the resource for write command #A to obtain information about the execution progress of write command #A. The time interval can be predefined or configured. See [link to documentation] for details. Figure 12 The method described in 1200 will not be elaborated here.

[0370] Optionally, the method 1300 further includes S1360, whereby the first reader sends an eleventh message, and correspondingly, the first core network element receives the eleventh message, which indicates whether the write command #A was executed successfully or failed, so that the first core network element can know the execution result of the write command #A.

[0371] Optionally, if the first reader is a terminal, then in S1360, the first reader sends message #11a (an example of the eleventh message) to the first access network device, and then the first access network device sends message #11b (an example of the eleventh message) to the first core network element based on the received message #11a.

[0372] As an example, Figure 14 This is a schematic diagram of another communication method 1400 provided in an embodiment of this application. Figure 14 The method shown may include the following steps.

[0373] Optionally, method 1400 includes S1401, which performs inventory management. For details on the implementation, please refer to the description in method 1000; it will not be repeated here.

[0374] Optionally, method 1400 includes S1402, in which the first core network element sends message #A, and correspondingly, the first reader receives message #A.

[0375] Optionally, if the first reader / writer is a terminal, then in S1402, the first core network element sends message #1a (an example of message #A) to the first access network device, and then the first access network device sends message #1b (an example of message #A) to the first reader / writer based on the received message #1a.

[0376] Among them, message #A instructs the first AIoT device to execute the first command, which may include write operations, read operations, etc.

[0377] Optionally, message #A also indicates latency information. The latency information indicates the scheduling latency of the first command. In one implementation, the latency information includes the scheduling latency of the first command and the security processing latency. In another implementation, the latency information includes the scheduling latency of the first command, and optionally, message #A also indicates the security processing latency. In both implementations above, security processing refers to operations involving encryption, authentication, and authorization of communication data related to the first command to prevent data leakage, tampering, or forgery. Typically, keys are exchanged or authentication protocols are implemented between the device and the reader to ensure that only authorized devices can communicate. The security processing latency refers to the time required to perform the aforementioned security processing.

[0378] It should be understood that latency information can be indicated by core network equipment or it can be predefined and is not limited.

[0379] S1410, the first reader sends the first message, and correspondingly, the first AIoT device receives the first message.

[0380] The first message instructs the first AIoT device to execute a command service. It should be understood that the name of the command service is not limited in this application. For example, the first command can also be called a command or a service.

[0381] In one implementation, the first command can be a write command, which can also be called a write business, write task, or write operation. This application does not limit the name.

[0382] In another implementation, the first command can be a read command, which can also be called a read business, read task, or read operation. This application does not limit the name.

[0383] S1420, the first AIoT device sends the second message, and correspondingly, the first reader receives the second message.

[0384] The second message can indicate that the execution status of the first command is in progress; in other words, the second message indicates that the first AIoT device has received the first information.

[0385] In the first implementation, the second message may include first indication information, which indicates whether the first AIoT device still has data to send. The data may be data from the first command or data related to the first command.

[0386] The first indication information can be implemented using at least one bit. If the value of this one bit is the first value, it indicates that the first AIoT device has not completed data transmission; in other words, the first AIoT device still has data to transmit. If the value of this one bit is the second value, it indicates that the first AIoT device has completed data transmission; in other words, the first AIoT device has no data to transmit. The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1"; or the first value can be "1" and the second value can be "0".

[0387] In the second implementation, the second message may include a service data unit (SDU). When the SDU is zero, it indicates that the data carried by the MAC SDU is empty, meaning the first AIoT device has not completed data transmission; in other words, the first AIoT device still has data to send, or the first reader / writer is executing the first command. When the SDU is not zero, it indicates that the first AIoT device has completed data transmission; in other words, the first AIoT device has no data to send, or the first command has been executed.

[0388] In the third implementation, the second message may include Media Access Control padding bits (MAC padding bits) and / or the remaining bit size. That is, when the first AIoT device sends MAC padding bits to the reader and the remaining bit size is non-zero, it indicates that there are still remaining bits that have not been filled with valid data under the current schedule; that is, the first AIoT device has not completed data transmission, in other words, the first AIoT device still has data to send, and the first reader is executing the first command. When the first AIoT device sends MAC padding bits to the reader and the remaining bit size is zero, it indicates that the first AIoT device has completed data transmission; in other words, the first AIoT device has no data to send, and the first command has been executed.

[0389] Optionally, in S1431, the first reader determines the timing for sending the sixth message.

[0390] In the first implementation, the first reader determines the timing of sending the sixth message based on message #A. In one implementation, message #A indicates a scheduling delay, including the scheduling delay of the first command and a security processing delay; in another implementation, the delay information indicated by message #A includes the scheduling delay of the first command, and optionally, message #A also indicates a security processing delay. The first reader determines that the sixth message needs to be sent after the required duration of the security processing delay. For an introduction to the sixth message, please refer to [link to relevant documentation]. Figure 10 This will not be elaborated upon here.

[0391] In the second implementation, the first reader determines that the current data transmission is complete based on the second message, and sends the sixth message only after ensuring sufficient security processing delay.

[0392] S1430, the first reader sends the sixth message, and correspondingly, the first AIoT device receives the sixth message.

[0393] The sixth message indicates resource #F (an example of the fourth resource), which is used to send information related to the first command.

[0394] In one implementation, the sixth message can be an SDU. When the SDU is 0, it instructs the first AIoT device to perform subsequent processing. For example, when the first command is a write command, the sixth message SDU=0 can instruct the first AIoT device to transmit data.

[0395] In another implementation, the sixth message could be a data indication offset, indicating that the first AIoT device can fill from that offset position.

[0396] S1440, the first AIoT device sends the second message, and correspondingly, the first reader receives the second message.

[0397] The first AIoT device can send a second message on resource #F, wherein the second message can indicate that the execution status of the first command is "in progress". For a description of the second message, please refer to S1420, which will not be repeated here.

[0398] In one implementation, the second message can also indicate that the first AIoT device has successfully received the first message.

[0399] S1450, the first AIoT device sends the fourth message, and correspondingly, the first reader receives the fourth message.

[0400] The fourth message can indicate that the execution status of the write command #A is "execution completed".

[0401] In the first implementation, the fourth message may include a second indication message, which indicates whether the first command has been sent completely. In other words, the second indication message indicates whether the first AIoT device still has data to send, where the data can be the data from the first command or data related to the first command.

[0402] The second indication information can be implemented using at least one bit. If the value of this one bit is the first value, it indicates that the first AIoT device has not completed data transmission; in other words, the first AIoT device still has data to transmit. If the value of this one bit is the second value, it indicates that the first AIoT device has completed data transmission; in other words, the first AIoT device has no data to transmit. The first and second values ​​can be different; for example, the first value can be "0" and the second value can be "1"; or the first value can be "1" and the second value can be "0".

[0403] In the second implementation, the fourth message may include a Service Data Unit (SDU). When the SDU is not zero, it indicates that the first AIoT device has completed sending data; in other words, the first AIoT device has no data to send, or the first command has been executed successfully.

[0404] In the third implementation, the fourth message may include media access control padding bits and / or the remaining bit size. When the first AIoT device sends media access control padding bits to the reader and the remaining bit size is zero, it indicates that the first AIoT device has completed data transmission. In other words, the first AIoT device has no data to send, and the first command has been executed successfully.

[0405] It should be understood that prior to S1450, the first reader / writer can periodically indicate the resource for the first command (e.g., S1430) to obtain information on the execution progress of write command #A. The time interval can be predefined or configured. See [link / reference] for details. Figure 12 The method described in 1200 will not be elaborated here.

[0406] Optionally, method 1400 further includes S1460, whereby the first reader sends an eleventh message, and correspondingly, the first core network element receives the eleventh message, which indicates whether the write command #A was executed successfully or failed, so that the first core network element can know the execution result of the write command #A.

[0407] Optionally, if the first reader is a terminal, then in S1460, the first reader sends message #11a (an example of the eleventh message) to the first access network device, and then the first access network device sends message #11b (an example of the eleventh message) to the first core network element based on the received message #11a.

[0408] The above, combined with Figures 10 to 14 This paper introduces four methods for the first AIoT device to send feedback information to the reader device.

[0409] As mentioned above, the access network equipment involved in this embodiment can be an O-RAN architecture. The following is a brief introduction to the above-mentioned features under the O-RAN architecture. Figures 10 to 14 The application of the communication method shown.

[0410] In the O-RAN architecture, the RIC can directly control both the gNB-CU and the gNB-DU, requiring the above-mentioned... Figures 10 to 14 In the communication method steps shown, "access network device" is expanded to "CU" and "DU".

[0411] As one possible implementation, the access network device receives messages from the reader, including: the DU of the access network device receiving message #z1 from the reader (e.g., message #z1 is an RRC message); the DU of the access network device sending message #z2 to the CU of the access network device based on message #z1 (e.g., message #z2 is an F1 application protocol (F1AP) message). Furthermore, the CU of the access network device can send message #z3 to the core network element based on message #z2 (message #z3 can be an XXAP message or an NGAP message).

[0412] In this context, message #z2 contains information #z2 that is related to information #z1 contained in message #z1. For example, information #z1 and information #z2 are the same, or information #z2 is obtained by the DU of the access network device processing information #z1 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Similarly, message #z3 contains information #z3 that is related to information #z2 contained in message #z2. For example, information #z3 and information #z2 are the same, or information #z3 is obtained by the CU of the access network device processing information #z2 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).

[0413] For example, message #z1 can be message #10a, message #11a, etc. in the above embodiments.

[0414] In one possible implementation, the access network device receives messages from core network elements, including: the access network device's CU receiving message #z4 from the core network element (message #z4 can be an XXAP message or an NGAP message); the access network device's CU sending message #z5 to the access network device's DU based on message #z4 (for example, message #z2 is an F1AP message). Furthermore, the access network device's DU can send message #z6 to the reader based on the received message #z5.

[0415] Message #z5 contains information #z5 that is related to information #z4 contained in message #z4. For example, information #z4 and information #z5 are the same, or information #z5 is obtained by the CU of the access network device processing information #z4 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Message #z6 contains information #z6 that is related to information #z5 contained in message #z5. For example, information #z5 and information #z6 are the same, or information #z6 is obtained by the DU of the access network device processing information #z5 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).

[0416] For example, message #z4 can be message #1a, etc., as described in the above embodiments.

[0417] The following, combined with Figures 15 to 17 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0418] For example, Figure 15 This is a schematic diagram of a communication device 10 provided in an embodiment of this application. The communication device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can be used to implement corresponding communication functions. The transceiver unit 11 can also be referred to as a communication interface or a communication unit. The processing unit 12 can be used to perform processing, such as measuring the serving cell.

[0419] Optionally, the device 10 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 12 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0420] In a first possible design, the device 10 can be the AIoT device described in the foregoing embodiments. This device 10 can implement the steps or processes executed by the terminal device corresponding to those described in the above method embodiments. Specifically, the transceiver unit 11 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the terminal device described in the above method embodiments, and the processing unit 12 can be used to perform processing-related operations of the terminal device described in the above method embodiments, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0421] In one possible implementation, the transceiver unit 11 is configured to receive a first message, which instructs the AIoT device to execute a first command; the transceiver unit 11 is also configured to send a second message, which instructs the AIoT device to execute the first command.

[0422] Optionally, the transceiver unit 11 is configured to send a third message, the third message indicating that the first AIoT device has received the first message.

[0423] Optionally, the transceiver unit 11 is configured to send a fourth message, the fourth message indicating whether the first write command was executed successfully or failed.

[0424] Optionally, the transceiver unit 11 is configured to send a fifth message, the fifth message indicating that the first AIoT device is executing the first command.

[0425] Optionally, the transceiver unit 11 is used to receive a sixth message, which indicates the fourth resource.

[0426] Optionally, the transceiver unit 11 is used to receive a seventh message, and the sixth message indicates a fifth resource.

[0427] Optionally, the transceiver unit 11 is used to send an eighth message, which indicates that the first AIoT device is executing the first command.

[0428] Optionally, the transceiver unit 11 is used to receive a ninth message, which indicates a sixth resource.

[0429] In a second possible implementation, the transceiver unit 11 is used to send a first message, which instructs the first AIoT device to execute a first command; the transceiver unit 11 is also used to receive a second message, which instructs the first AIoT device to execute the first command.

[0430] Optionally, the transceiver unit 11 is used to receive a third message, which indicates that the first AIoT device has received the first message.

[0431] Optionally, the transceiver unit 11 is configured to receive a fourth message, the fourth message indicating whether the first write command was executed successfully or failed.

[0432] Optionally, the transceiver unit 11 is configured to receive a fifth message, the fifth message indicating that the first AIoT device is executing the first command.

[0433] Optionally, the transceiver unit 11 is used to send a sixth message, which indicates the fourth resource.

[0434] Optionally, the transceiver unit 11 is used to send a seventh message, and the sixth message indicates the fifth resource.

[0435] Optionally, the transceiver unit 11 is used to receive an eighth message, which indicates that the first AIoT device is executing a first command.

[0436] Optionally, the transceiver unit 11 is used to send a ninth message, which indicates the sixth resource.

[0437] Optionally, the transceiver unit 11 is used to send a tenth message, which indicates that the first AIoT device has received the first message.

[0438] Optionally, the transceiver unit 11 is used to send an eleventh message, which indicates whether the first write command was executed successfully or failed.

[0439] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0440] It should also be understood that the device 10 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 10 can be specifically the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0441] The apparatus 10 of each of the above-described solutions has the function of implementing the corresponding steps performed by the communication device (such as an AIoT device, or a reader / writer device) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each performing the transceiver operations and related processing operations in the respective method embodiments.

[0442] In addition, the transceiver unit 11 can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0443] It should be pointed out that, Figure 15 The device mentioned can be the communication device (such as an AIoT device or a reader / writer device) as described in the preceding embodiments, or it can be a chip or a chip system, such as a system-on-a-chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0444] For example, Figure 16 This is a schematic diagram of another communication device 20 provided in this application embodiment. The device 20 includes a processor 21, which is coupled to a memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used to execute the computer programs or instructions stored in the memory 22, or to read the data stored in the memory 22, so as to execute the methods in the above method embodiments.

[0445] Optionally, there may be one or more processors 21.

[0446] Optionally, the memory 22 may be one or more.

[0447] Alternatively, the memory 22 can be integrated with the processor 21, or it can be set separately.

[0448] Optionally, such as Figure 16 As shown, the device 20 also includes a transceiver 23 for receiving and / or transmitting signals. For example, the processor 21 controls the transceiver 23 to receive and / or transmit signals.

[0449] As an example, processor 21 may have Figure 15 The processing unit 12 shown has the function of a storage unit, the memory 22 can have the function of a storage unit, and the transceiver 23 can have the function of a storage unit. Figure 15The function of the transceiver unit 11 shown is illustrated.

[0450] As one approach, the device 20 is used to implement the operations performed by a communication device (such as an AIoT device or a reader / writer device) in the various method embodiments described above.

[0451] For example, processor 21 is used to execute computer programs or instructions stored in memory 22 to implement the relevant operations of the communication device in the various method embodiments described above.

[0452] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0453] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. 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. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: 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).

[0454] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0455] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0456] For example, Figure 17 This is a schematic diagram of a chip system 30 provided in an embodiment of this application. The chip system 30 (or processing system) includes logic circuitry 31 and an input / output interface 32.

[0457] The logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 30 to implement the methods and functions of the embodiments of this application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting processed information from the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.

[0458] As one approach, the chip system 30 is used to implement the operations performed by the communication device (such as an AIoT device or a reader / writer device) in the various method embodiments described above.

[0459] For example, logic circuit 31 is used to implement processing-related operations performed by the communication device (such as an AIoT device, or a reader / writer device) in the above method embodiments; input / output interface 32 is used to implement sending and / or receiving-related operations performed by the communication device (such as an AIoT device, or a reader / writer device) in the above method embodiments.

[0460] This application also provides a computer-readable storage medium storing a computer program or instructions for implementing the methods executed by a communication device (such as an AIoT device or a reader / writer device) in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, the communication device (such as an AIoT device or a reader / writer device) performs the above-described methods (such as method 1000, method 1100, method 1200, or method 1300).

[0461] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods described above as performed by a communication device (such as an AIoT device or a reader / writer device). For example, when the computer program or instructions are run on the communication device, the communication device (such as an AIoT device or a reader / writer device) performs the methods described above (such as method 1000, method 1100, method 1200, or method 1300).

[0462] This application also provides a communication system, which includes the AIoT device, reader / writer device, and core network device described in the above embodiments. For example, the system includes... Figure 10 , Figure 11 , Figure 12 or Figure 14 The AIoT device, reader / writer device, and core network device in the embodiment.

[0463] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0464] 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.

[0465] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0466] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0467] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0468] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0469] 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.

[0470] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0471] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0472] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0473] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, A chip used in a first-environment Internet of Things (AIoT) device or a first AIoT device, including: Receive a first message from the first reader / writer, the first message instructing the first AIoT device to execute a first command; A second message is sent to the first reader / writer, the second message indicating that the first AIoT device is executing the first command.

2. The method according to claim 1, characterized in that, The second message also includes a first indication, which indicates whether the first AIoT device has any more data to send.

3. The method according to claim 1 or 2, characterized in that, Before sending the second message, the method further includes: A third message is sent to the first reader / writer, the third message indicating that the first AIoT device has received the first message.

4. The method according to any one of claims 1 to 3, characterized in that, The first message also indicates the first resource; Sending a second message to the first reader / writer includes: sending a second message to the first reader / writer on the first resource.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: A fourth message is sent to the first reader / writer, the fourth message indicating whether the first command was executed successfully or failed.

6. The method according to claim 5, characterized in that, The first message also instructs on a second resource; Sending a fourth message to the first reader includes: sending a fourth message to the first reader on the second resource.

7. The method according to any one of claims 1 to 3, characterized in that, The method includes: A fifth message is sent to the first reader / writer, the fifth message indicating that the first AIoT device is executing the first command.

8. The method according to claim 7, characterized in that, The first message also instructs a third resource; Sending the fifth message to the first reader / writer includes: sending the fifth message to the first reader / writer on the third resource.

9. The method according to any one of claims 1 to 3, characterized in that, After receiving the first message from the first reader / writer, the method further includes: receiving a sixth message from the first reader / writer, the sixth message indicating a fourth resource; Sending the second message to the first reader / writer includes: sending the second message to the first reader / writer on the fourth resource.

10. The method according to claim 9, characterized in that, After sending the second message to the first reader / writer, the method further includes: receiving a seventh message from the first reader / writer, the seventh message indicating a fifth resource; Sending an eighth message to the first reader / writer includes: sending an eighth message to the first reader / writer on the fifth resource, the eighth message indicating that the first AIoT device is executing the first command.

11. The method according to claim 9 or 10, characterized in that, After sending the second message to the first reader / writer, the method further includes: receiving a ninth message from the first reader / writer, the ninth message indicating a sixth resource; Sending a fourth message to the first reader includes: sending a fourth message to the first reader on the sixth resource, the fourth message indicating whether the first command was executed successfully or failed.

12. The method according to claim 11, characterized in that, The ninth message includes either a Service Data Unit (SDU) of zero or a Data Indicator Offset of zero.

13. A communication method, characterized in that, A chip used in or in a first reader / writer device, including: Send a first message to the first AIoT device, the first message instructing the first AIoT device to execute a first command; A second message is received from the first AIoT device, the second message indicating that the first AIoT device is executing the first command.

14. The method according to claim 13, characterized in that, The second message also includes a first indication, which indicates whether the first AIoT device has any more data to send.

15. The method according to claim 13 or 14, characterized in that, Before receiving the second message from the first AIoT device, the method further includes: receiving a third message from the first AIoT device, the third message indicating that the first AIoT device has received the first message.

16. The method according to any one of claims 13 to 15, characterized in that, The first message also indicates the first resource; Receiving the second message from the first AIoT device includes: receiving the second message from the first AIoT device on the first resource.

17. The method according to any one of claims 11 to 16, characterized in that, The method further includes: A fourth message is received from the first AIoT device, the fourth message indicating whether the first command was executed successfully or failed.

18. The method according to claim 17, characterized in that, The first message also instructs on a second resource; Receiving the fourth message from the first AIoT device includes: receiving the fourth message from the first AIoT device on the second resource.

19. The method according to any one of claims 13 to 15, characterized in that, The method includes: A fifth message is received from the first AIoT device, the fifth message indicating that the first AIoT device is executing the first command.

20. The method according to claim 19, characterized in that, The first message also instructs a third resource; Receiving the fifth message from the first AIoT device includes: receiving the fifth message from the first AIoT device on the third resource.

21. The method according to any one of claims 13 to 15, characterized in that, After sending the first message to the first AIoT device, the method further includes: sending a sixth message to the first AIoT device, the sixth message indicating a fourth resource; Receiving a second message from the first AIoT device includes: receiving a second message from the first AIoT device on the fourth resource.

22. The method according to claim 21, characterized in that, The step of sending a sixth message to the first AIoT device after sending the first message includes: determining to send the sixth message to the first AIoT device based on a security processing delay.

23. The method according to claim 21 or 22, characterized in that, After receiving the second message from the first AIoT device, the method further includes: sending a seventh message to the first AIoT device, the seventh message indicating a fifth resource; Receiving an eighth message from the first AIoT device includes: receiving an eighth message from the first AIoT device on the fifth resource, the eighth message indicating that the first AIoT device is executing the first command.

24. The method according to any one of claims 21 to 23, characterized in that, After receiving the second message from the first AIoT device, the method further includes: sending a ninth message to the first AIoT device, the ninth message indicating a sixth resource; Receiving a fourth message from the first AIoT device includes: receiving a fourth message from the first AIoT device on the sixth resource, the fourth message indicating whether the first command was executed successfully or failed.

25. The method according to claim 24, characterized in that, The step of sending a ninth message to the first AIoT device after receiving the second message from the first AIoT device includes: determining to send the sixth message to the first AIoT device based on the security processing delay.

26. The method according to claim 25, characterized in that, The ninth message indicates that the Service Data Unit (SDU) is zero or the data indication offset is zero.

27. The method according to any one of claims 15 to 26, characterized in that, The method further includes: A tenth message is sent to the core network device, the tenth message indicating that the first AIoT device has received the first message.

28. The method according to claim 17 or 21, characterized in that, The method further includes: Send an eleventh message to the core network device, the eleventh message indicating whether the first command was executed successfully or failed.

29. The method according to any one of claims 1 to 28, characterized in that, The second message also includes media access control padding bits; The second message indicates that the first AIoT device is executing the first command, including: The media access control padding bits indicate that the first AIoT device is executing the first command.

30. The method according to any one of claims 5, 6, 12, 17, 18, or 24, characterized in that, When the fourth message indicates that the first command failed to execute, the fourth message also indicates the reason for the failure.

31. The method according to any one of claims 5, 6, 12, 17, 18, or 24, characterized in that, The fourth message is carried in a media access control element or non-access stratum signaling.

32. A communication device, characterized in that, Includes modules or units for implementing the method of any one of claims 1 to 31.

33. A communication device, characterized in that, It includes a processor and a memory coupled to the processor, the memory storing a computer program or instructions that, when executed by the processor, cause the method as described in any one of claims 1 to 31 to be performed or implemented.

34. A computer-readable storage medium, characterized in that, The computer-readable storage medium is stored on the communication device, and the computer-readable storage medium stores a computer program or instructions that, when the computer program or instructions are run, cause the method as described in any one of claims 1 to 31 to be executed or implemented.

35. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run, cause the method as described in any one of claims 1 to 31 to be performed or implemented.