Communication method and related apparatus

Abstract

Embodiments of the present application provide a communication method and a related apparatus. The method is applied to a first core network device or a chip in the first core network device. The method comprises: receiving a first message, the first message comprising an inventory result or a first command response, and the first command response being a response to a first command; and when identifiers in a first range are all included in the inventory result or a first set, sending a second message, wherein the second message indicates termination of the inventory operation or termination of execution of the first command, the first range comprises identifiers used for identifying ambient Internet of Things (A-IoT) devices, the first range is determined on the basis of information provided by an application server, the application server communicates with the first core network device, and identifiers in the first set correspond to the first command response. The embodiments of the present application enable prompt termination of an inventory operation or prompt termination of execution of a first command, thereby reducing communication overhead.

Description

Communication methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 202510381834.X, filed on March 27, 2025, entitled "Communication Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to communication methods and related apparatus. Background Technology

[0003] Ambient IoT (A-IoT, or Ambient Power-enabled IoT, or Passive IoT, P-IoT) refers to network nodes that can be passive, obtaining energy from sources such as solar, radio frequency, wind, hydro, or tidal power. These nodes do not have their own power supply devices (such as batteries) but instead draw energy from the environment to support data sensing, transmission, and distributed computing. Nodes can also store the energy they acquire. These nodes are called A-IoT devices. An Ambient IoT architecture can include nodes such as A-IoT devices, readers, and servers. The network requires inventory management of A-IoT devices, and several solutions for this purpose have been proposed, illustrated below.

[0004] For example, a command process (such as read or write operations) for an A-IoT device requires inventory to be performed first, followed by the command. Furthermore, the reader can perform inventory operations continuously without waiting for one A-IoT device's command process to finish before executing the next. As shown in Figure 1, after A-IoT device 2 is paged (i.e., after completing a random access operation with the reader), the reader can immediately begin inventorying A-IoT device 1, without waiting for the read result from A-IoT device 2 to be sent to the network before inventorying subsequent tags.

[0005] For example, when a reader performs an inventory of A-IoT devices within a mask range, the mask sent can be a partial device ID or the complete device ID of the A-IoT device, as shown in Figure 2. When the mask is a partial device ID, it may inventory more A-IoT devices than the actual device list requested for operation. For instance, the application function (AF) requires operation on A-IoT devices with device IDs ID1, ID3, and ID6, but the reader actually inventoryes A-IoT devices with device IDs ID1-ID10 using the mask. Among these, A-IoT devices with device IDs ID2, ID4, ID5, ID7, ID8, ID9, and ID10 are actually devices that do not need to be operated on, as shown in Figure 3.

[0006] It can be seen that in the current design for storing A-IoT devices, the Reader will store a lot more information about A-IoT devices than the actual device information. Summary of the Invention

[0007] This application discloses a communication method and related apparatus that can promptly stop inventorying or stop executing the first command, saving signaling and time slot resources on the air interface side.

[0008] In a first aspect, embodiments of this application provide a communication method, which is applied to a first core network device or a chip in the first core network device, the method comprising:

[0009] Receive a first message, the first message including inventory result or a first command response, the first command response being a response to a first command;

[0010] When all the identifiers in the first range are included in the inventory results or the first set, a second message is sent, wherein the second message indicates to stop inventory or stop executing the first command, the first range includes identifiers used to identify environmental Internet of Things (A-IoT) devices, the first range is determined based on information provided by the application server, the application server communicates with the first core network device, and the identifiers in the first set correspond to the first command response.

[0011] In the above method, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results or first command responses to complete a specific task, the second message explicitly instructs to stop inventorying or stop executing the first command. This allows the reading device (such as Reader) to stop inventorying or stop executing the first command in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0012] In one alternative implementation, the second message further instructs the release of the A-IoT device's context information. It is understood that using the A-IoT device's context information can reduce data storage and computational overhead.

[0013] In another optional implementation, the first message includes the inventory result, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier. The first part of the identifier includes identifiers outside the first range included in the inventory result. In this step, only the context information of the A-IoT device corresponding to the first part of the identifier is released, while the context information of the first A-IoT device is retained. This reduces data storage and computational overhead while ensuring the smooth operation of subsequent operations related to the first A-IoT device.

[0014] In another alternative implementation, the second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers.

[0015] In another alternative implementation, the second message is further used to instruct the execution of the first command, and the method further includes:

[0016] Receive a first command response from a first A-IoT device of the reading device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range;

[0017] Send the first command response from the first A-IoT device to the application server.

[0018] In this approach, after inventorying, the system continues to acquire the first command response from the first A-IoT device and feeds that first command response back to the application server, thereby meeting the business needs of the application server.

[0019] Another alternative implementation includes:

[0020] Send a third message, wherein the third message is used to indicate the release of the context information of the first A-IoT device.

[0021] In this approach, once the first command response of the first A-IoT device is sent to the application server, the first A-IoT device is no longer in use. Therefore, its context information is released in the final stage, further reducing data storage and computational overhead.

[0022] In another implementation, the aforementioned third message is used to instruct the reader to stop executing the first command. However, upon receiving this third message, the reader will not only stop executing the first command but also release the context information of the first A-IoT device. Alternatively, after the first core network device sends the second message to the reader, the reader may stop storing the data, but it will not release the context information of the A-IoT devices immediately. Instead, it will wait until it receives the third message before stopping the execution of the first command and releasing all stored context information of the A-IoT devices.

[0023] In another optional implementation, the first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result. In this approach, after the first command response of the first A-IoT device is sent to the application server, the first core network device releases the context information of all A-IoT devices related to the current task at once.

[0024] In another alternative implementation, before receiving the first message containing the first command response, the method further includes receiving the inventory result.

[0025] Another alternative implementation includes:

[0026] A fourth message is received from the application server, wherein the fourth message is used to indicate that inventory should be stopped.

[0027] In another alternative implementation, it further includes: determining that all identifiers in the first range are included in the first set.

[0028] Secondly, embodiments of this application provide a communication method, the method comprising:

[0029] Send a first message, wherein the first message includes inventory results or a first command response, and the first command response is a response to a first command;

[0030] Receive a second message, wherein the second message indicates to stop inventory or stop executing the first command;

[0031] Stop inventorying the A-IoT device or stop instructing the A-IoT device to execute the first command.

[0032] In the above method, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results or first command responses to complete a specific task, the second message explicitly instructs to stop inventorying or stop executing the first command. This allows the reading device (such as Reader) to stop inventorying or stop executing the first command in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0033] In one alternative implementation, the second message also indicates the release of the A-IoT device's context information. It is understood that using the A-IoT device's context information can reduce data storage and computational overhead.

[0034] In another alternative implementation, the first message includes the inventory result, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier, wherein the first part of the identifier includes identifiers outside the first range included in the inventory result; the method further includes: releasing the context information of the A-IoT device corresponding to the first part of the identifier.

[0035] In this step, only the context information of the A-IoT device corresponding to the first part of the identifier is released, while the context information of the first A-IoT device is retained. This reduces data storage and computation overhead and ensures that subsequent operations related to the first A-IoT device can proceed smoothly.

[0036] In another alternative implementation, the second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers.

[0037] Another alternative implementation includes:

[0038] Receive a third message, the third message being used to instruct the release of the context information of the first A-IoT device;

[0039] Release the context information of the first A-IoT device.

[0040] In this approach, once the first command response of the first A-IoT device is sent to the application server, the first A-IoT device is no longer in use. Therefore, its context information is released in the final stage, further reducing data storage and computational overhead.

[0041] In another implementation, the aforementioned third message is used to instruct the reader to stop executing the first command. However, upon receiving this third message, the reader will not only stop executing the first command but also release the context information of the first A-IoT device. Alternatively, after the first core network device sends the second message to the reader, the reader may stop storing the data, but it will not release the context information of the A-IoT devices immediately. Instead, it will wait until it receives the third message before stopping the execution of the first command and releasing all stored context information of the A-IoT devices.

[0042] In another alternative implementation, the second message is further used to instruct the execution of the first command, and the method further includes:

[0043] Send the first command to the first A-IoT device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range;

[0044] Receive a first command response from the first A-IoT device;

[0045] Send the first command response from the first A-IoT device.

[0046] In this approach, after inventorying, the system continues to acquire the first command response from the first A-IoT device and feeds that first command response back to the application server, thereby meeting the business needs of the application server.

[0047] In another optional implementation, the first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result; the method further includes:

[0048] Release the context information of the A-IoT device corresponding to the received inventory results.

[0049] In this approach, after the first command response of the first A-IoT device is sent to the application server, the first core network device releases the context information of all A-IoT devices related to the current task at once.

[0050] In another alternative implementation, the method further includes receiving a fifth message, wherein the fifth message is used to instruct the execution of the first command.

[0051] In this approach, the first core network device notifies the reading device to stop executing the first command via a separate message. Therefore, the reading device will no longer instruct the A-IoT device to execute the first command, and the immediate cessation of executing the first command can reduce unnecessary overhead.

[0052] Thirdly, embodiments of this application provide a communication device, which can be a first core network device or a device (such as a chip) or functional module in the first core network device, wherein:

[0053] The communication device includes a module for performing the method described in the first aspect or any possible implementation thereof;

[0054] Alternatively, the communication device includes a processor for performing the method described in the first aspect or any possible implementation thereof.

[0055] Fourthly, embodiments of this application provide a communication device, which can be a reading device or a component (such as a chip) or functional module within the reading device, wherein:

[0056] The communication device includes a module for performing the method described in the second aspect or any possible implementation thereof;

[0057] Alternatively, the communication device may include a processor for performing the method described in the second aspect or any possible implementation thereof.

[0058] Fifthly, embodiments of this application provide a communication device, characterized in that it includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used for inputting and / or outputting information, wherein:

[0059] The logic circuit is used to perform the method described in the first aspect or any possible implementation thereof, or...

[0060] The logic circuit is used to perform the method described in the second aspect or any possible implementation thereof.

[0061] Sixthly, embodiments of this application provide a computer-readable storage medium for storing a computer program, wherein:

[0062] When the computer program is executed, it is capable of implementing the first aspect or any possible implementation of the first aspect, or...

[0063] When the computer program is executed, it is capable of implementing the second aspect or any possible implementation of the second aspect.

[0064] In a seventh aspect, embodiments of this application provide a communication system, which includes a first core network device and a reading device, wherein:

[0065] The first core network device is used to perform the method described in the first aspect or any possible implementation thereof, and the reading device is used to perform the method described in the second aspect or any possible implementation thereof. Attached Figure Description

[0066] The accompanying drawings used in the embodiments of this application are described below.

[0067] Figure 1 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0068] Figure 2 is a schematic diagram of a mask structure provided in an embodiment of this application;

[0069] Figure 3 is a schematic diagram of a device identifier provided in an embodiment of this application;

[0070] Figure 4 is a schematic diagram of an A-IoT architecture provided in an embodiment of this application;

[0071] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0072] Figure 6 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0073] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

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

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

[0076] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0077] The embodiments of this application are described below with reference to the accompanying drawings.

[0078] Ambient IoT (A-IoT) architecture is widely used in various industries. Below are two simple application scenarios:

[0079] 1. Warehouse / Transportation / Materials: Embed or attach passive or semi-passive IoT tags to goods stored in warehouses, shopping malls, etc. During the logistics process, the relevant information of the goods is automatically collected by the reader. Managers can quickly query the information of the goods in the system, reduce the risk of loss or theft, improve the speed of goods handover, improve accuracy, and prevent cross-selling and counterfeiting.

[0080] 2. Fixed Asset Management: Places with large assets or valuable items, such as libraries, art galleries, and museums, need complete management procedures or rigorous protection measures. When there are abnormal changes in the storage information of books or valuable items, the system will immediately alert the administrator to handle the relevant situation.

[0081] Please refer to Figure 4, which is a schematic diagram of an A-IoT architecture provided in an embodiment of this application. The A-IoT architecture includes an A-IoT device 401, a reader 402, an environmental IoT function AIoTF 403, a network open function NEF 404, and an application server (such as an environmental IoT application function A-IoT AF) 405. This embodiment of the application can be applied to various communication architectures, such as Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) mobile communication systems, new radio access technology (NR), 6th Generation (6G) mobile communication systems, or other wireless access technologies. The above communication technologies can be non-standalone (NSA) and / or standalone (SA) network architectures. For example, taking a 5G mobile communication system as an example, the A-IoT architecture of this application embodiment may also include one or more of the core network elements such as AMF, AUSF, UDM, NSSAAF, SMF, UPF, and UDR, which are not shown in Figure 4.

[0082] A-IoT devices, also known as environmental IoT terminals or passive IoT terminals, can be in tag form, such as passive tags, semi-passive tags, semi-active tags, and active tags. Of course, the A-IoT device can also be any other terminal form without restriction. Many types of terminal devices can serve as A-IoT devices, such as user equipment (UE), terminals, access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, wireless communication equipment, user agents, or user devices. The UE can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN) or non-terrestrial networks (NTN), etc. It can also be an end device, logical entity, smart device, such as a mobile phone, smart terminal, or other terminal device; or a server, gateway, base station, controller, or other communication device; or an Internet of Things (IoT) device, such as tags, passive tags, active tags, semi-active tags, sensors, electricity meters, water meters, etc. It can also be an unmanned aerial vehicle (UAV) with communication capabilities. When the terminal device is a passive or semi-active terminal or tag, it can acquire energy to receive or transmit data. Energy can be obtained through radio waves, solar energy, light energy, wind energy, hydropower, thermal energy, kinetic energy, etc. This application does not limit the energy acquisition method for passive or semi-active terminal devices.

[0083] Reading device: This can be a reader or a component within a reader (such as a chip). We will primarily use readers as an example here. A reader can be an access network device, such as a radio access network (RAN), base station, pole station, micro base station (such as eNodeB, gNodeB, etc.), macro station, integrated access and backhaul (IAB) node, etc.; a reader can also be a terminal device, such as a mobile phone, IoT device, handheld reader, etc. The reader conducts contactless, two-way data communication via wireless radio frequency. It should be understood that this application does not limit the name of the reader. The reader can also be named "reader" or other names. That is, it can be understood that the names "reader" and "reader" are interchangeable. The reader here has the functions involved in the reader in this application. For example, the reader has the function of performing the operations described in this application on the terminal (such as tag) (such as obtaining tag information, inventory operation, read operation, write operation, or invalidation operation or message interaction operation with tag, etc.), and has the function of obtaining billing-related information and / or billing information, and sending billing information to CHF, etc.

[0084] In one possible implementation, the reader can send instructions from the server or application function to the tag, or the reader can send messages from the tag to the server or application function.

[0085] In one possible implementation, the reader can retrieve information stored in a specified tag based on instructions issued by the server. For example, in the case of an inventory operation (or stocktaking operation), the reader retrieves the tag's identification information; this identification information can be a unique identifier for the tag or a temporary identifier. In the case of a read operation, the reader reads the data from the tag's storage area. Optionally, in situations where it is necessary to rewrite the information stored within the tag, the reader can also have a write function; for example, in the case of a write operation, the reader writes data to the tag's storage area. In addition, the reader can also perform an invalidation operation on the tag. After an invalidation operation is performed, the tag becomes invalid and cannot be used for operations such as retrieving tag information, inventory operations, read operations, message interaction operations with the tag, or write operations.

[0086] In one possible implementation, the inability to retrieve tag information due to tag invalidation can be understood as the reader being unable to retrieve the tag information of the invalidated tag after it becomes invalid.

[0087] In one possible implementation, the inability to perform message interaction operations with a tag after it expires can be understood as the reader being unable to interact with the expired tag after it expires.

[0088] At present, there are at least two ways for readers to work. One is that when the tag enters the effective identification range of the reader, it receives the radio frequency signal emitted by the reader and uses the energy obtained by the induced current to emit the information stored in the chip (corresponding to passive tags). The other is that the tag can store some electrical energy through solar energy or other means, so that it can actively send a signal of a certain frequency (this can also be called a semi-passive or semi-active tag). After the reader receives the information and decodes it, it sends it to the central information system for relevant data processing.

[0089] An Ambient IoT Function (AIoTF), also known as an IoT function, IoT management function, or Ambient IoT Management Function, is primarily responsible for transmitting business data from IoT devices, managing IoT terminals, handling security authentication processes for IoT terminals, and instructing readers to perform IoT business operations (e.g., instructing readers to perform AIoT terminal inventory processes) and transmitting commands (such as read operations, write operations, and deactivation operations) based on business operations indicated by the requesting party. This application does not limit the naming of the IoT management function.

[0090] Network Exposure Function (NEF): Also known as network exposure equipment, it is a type of core network equipment. This equipment enables 3GPP to securely provide network service capabilities to third-party AFs (e.g., services capability servers (SCS), application servers (AS), etc.). For example, in 5G, the network exposure element can be a network exposure function (NEF) element. In future communication systems, such as 6G, the network exposure element can still be a NEF element, or it may have other names; this application does not limit this. When the network exposure element is a NEF, the NEF can provide NEF services to other network function elements.

[0091] Server: This refers to the operation requester (i.e., the server or application function (AF) that issues the command; it can be called the operation requester or a third party). For example, the operation requester can be a server, application function (AF), application server (AS), environmental IoT / passive IoT application function (A-IoT / P-IoT AF), or other device sending operation commands. The operation requester can correspond to a certain type of user, which can include enterprises, tenants, third parties, or companies, without restriction. The fact that the operation requester corresponds to a certain type of user means that the operation requester belongs to that type of user and is managed by that type of user.

[0092] The Access and Mobility Management Function (AMF), also known as Access and Mobility Management Equipment, Access and Mobility Management Function Entity, Access and Mobility Management Function Network Element, Mobility Management Equipment, Mobility Management Network Element, or Mobility Management Entity, is a type of core network equipment. This equipment is used to manage the access control and mobility of user equipment. In practical applications, it includes the Access and Mobility Management Function within the Mobility Management Entity (MME) of the Long Term Evolution (LTE) network framework, and incorporates access management functions. Specifically, it can be responsible for user equipment registration, mobility management, tracking area update procedures, reachability detection, selection of session management network elements, and mobility state transition management. For example, in 5G, the Access and Mobility Management Network Element can be an Access and Mobility Management Function (AMF) network element. In future communications, such as 6G, the Access and Mobility Management Network Element can still be an AMF network element, or it may have other names; this application does not limit this. When the access and mobility management network element is an AMF network element, the AMF can provide Namf services.

[0093] Authentication Server Function (AUSF): Responsible for processing user authentication data, it is the authentication service network element of 5GC. It is mainly responsible for the home network authentication of the terminal (such as UE), receiving authentication requests from AMF, and initiating subscription information queries to UDM to complete the authentication of the terminal (such as UE). It is also responsible for signing the information sent from the home network to the terminal (such as UE) to protect the information from being modified and monitored.

[0094] Unified data management (UDM): also known as unified data management equipment, unified data management network element, data management device, or unified data management entity. The unified data management network element is used to handle terminal device identification, access authentication, registration, and mobility management. In 5G communication systems, unified data management can be either a UDM or a unified data management equipment. In future communication systems, unified data management can also be a UDM network element, or it can have other names; this application does not limit this. The unified data management equipment can be a core network device. The unified data management equipment can be a control plane device.

[0095] Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF): Primarily responsible for authentication and authorization of network slices, it can interact with the Authentication, Authorization, and Accounting Server (AAA-S) through the Authentication, Authorization, and Accounting Proxy (AAA-P).

[0096] Session Management Function (SMF): Also known as session management device, it is a type of core network equipment. This device is responsible for session management of the user equipment (including session establishment, modification, and release), selection and reselection of user plane function network elements, allocation of Internet Protocol (IP) addresses for the user equipment, and quality of service (QoS) control. For example, in 5G, the session management network element can be a session management function (SMF) network element. In future communication systems, such as 6G, the session management network element can still be an SMF network element, or it may have other names; this application does not limit this. When the session management network element is an SMF network element, the SMF can provide NSMF services.

[0097] User plane function (UPF): Also known as user plane equipment, it is a type of core network equipment. This device is responsible for forwarding and receiving user data from user equipment. It can receive user data from the data network and transmit it to the user equipment through access network elements; the UPF element can also receive user data from the user equipment through access network elements and forward it to the data network. The transmission resources and scheduling functions providing services to user equipment within the UPF element are managed and controlled by the session management function element.

[0098] User Data Repository (UDR): Also known as user database device, user database entity, or user database network element, it can be understood as the naming convention for unified data storage network elements in the 5G architecture. The user database primarily includes the following functions: storage and retrieval of data types such as subscription data, policy data, and application data.

[0099] AIoT Data Management: Supports data management for AIoT devices, such as profile-type data management.

[0100] The operating mechanism of the A-IoT architecture in this application embodiment is as follows:

[0101] When a server (such as an AF) operates on a tag (such as an A-IoT device), it can send operation instructions through the core network. These instructions can include, but are not limited to, performing operations such as acquiring tag information, inventorying (or counting), reading, writing, invalidation, and interacting with the tag. Instructions can include area location information, tag identification information, etc. A reader (such as a base station) sends an access instruction to the tag (such as an A-IoT device). After a tag successfully connects randomly, the reader sends instructions to the tag (the reader can forward instructions sent by the core network to the tag). The tag acquires or sends corresponding information according to the instructions. For example, when the instruction is an inventory instruction or an inventory operation, the tag sends its identification information; when the instruction is a read instruction or a read operation, the tag sends the data information stored in its storage area; when the instruction is a write instruction or a write operation, the tag stores the data information to be written to the tag, included in the instruction, in its storage area. The reader sends (or forwards) the information sent by the tag to the core network; the core network then sends this information to the server.

[0102] The server can send commands through the control plane channel, for example, by sending commands to the AMF (Application Function). In this case, the server can be an application function (AF), an application server (AS), or an A-IoT / P-IoT application function (A-IoT / P-IoT AF). One possible implementation is that the A-IoT AF sends commands to the AIoTF. Another possible implementation is that the A-IoT AF sends commands to the AIoTF through a control plane device. This control plane device can be a network exposure function (NEF), session management function (SMF), policy control function (PCF), unified data management (UDM), or a Network Slice-specific and SNPN (Standalone Non-Public Network) authentication and authorization function (NSSAAF). Furthermore, the server can also send commands to the reader through the user plane channel. One possible implementation is that the server sends commands to the base station through a user plane function (UPF).

[0103] In one possible implementation, the server can send instructions to the AIoTF via the User Plane Equipment (UPF) and the SMF, and the AIoTF can then send the instructions to the tag via the RAN. In another possible implementation, the server sends instructions to the reader (when the reader is a terminal device) via the User Plane Equipment and the access network equipment, such as the radio access network (RAN).

[0104] In this embodiment of the application, the server (such as AF) can perform different operations on the tag (such as an A-IoT device), as illustrated below:

[0105] Inventory processing (also known as point-to-point processing) involves taking stock of existing tags (such as A-IoT devices), or retrieving tag identification information. Each tag has its own identifier. Tag identifiers can be assigned by the company (i.e., written into the tag when it's printed) or by the operator. In one possible implementation, the tag identifier can be a globally unique code—such as an EPC (Electronic Product Code)—or a temporary identifier or a non-globally unique identifier. During the inventory process, a server (such as an AF) can issue inventory instructions. Typically, these instructions include information such as the tag's identification range, reader identifier, and location information. Upon receiving the inventory instruction, the reader performs inventory processing on the tags according to the instructions and sends the tag's identification information to the server. Alternatively, the server sends an instruction, and the reader forwards the instruction to the tags. The tag, upon learning from the instruction that it is an inventory operation, sends its identification information to the reader, which in turn sends the tag's identification information to the server; alternatively, the tag sends its identification information to the core network through the reader, which in turn sends the tag's identification information to the server.

[0106] A read operation refers to the process of reading data from a tag (such as an A-IoT device). Tags may have storage capabilities, and their storage areas can store data. If a server (such as an auto-reader) wants to perform a read operation on a tag, it sends a read command. The reader or core network then performs the read operation according to the command, retrieving data from the tag's storage area and sending that data back to the server.

[0107] A write operation is the process of writing data to a tag. The server can send a write command, and the reader or core network will then perform the write operation on the tag according to the command, writing data to the tag's storage area.

[0108] The deactivation operation involves invalidating or deactivating a tag. The server can send a deactivation command, which may include the tag identifier (i.e., the identifier of the tag to be deactivated or invalidated). The reader or core network performs the deactivation operation on the tag according to the command. After the operation is completed, the tag is invalidated or deactivated and cannot be stored or subjected to other operations.

[0109] Obtaining tag information can be understood as a higher-level description of the various operations mentioned above (such as a higher-level description of disk storage and read operations). It does not distinguish whether the server is disk storing tags or reading tag data. This operation will obtain tag information, which can be the tag's identification information or information stored in the tag storage area.

[0110] The message interaction operation with the tag can be understood as a higher-level description of the various operations mentioned above. After receiving instructions from the server, the reader interacts with the tag to exchange information or messages and sends information from the tag back to the server. This operation is mainly applicable to scenarios where the reader does not view the content of the instructions, but only forwards messages sent by the server to the tag and messages sent by the tag to the server. Therefore, in this scenario, the operation performed by the reader on the tag can be understood as a message interaction operation with the tag.

[0111] Please refer to Figure 5, which is a flowchart illustrating a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4, or on other architectures. The method includes, but is not limited to, the following steps:

[0112] Step S501: The reading device receives the inventory results or first command response from the A-IoT device.

[0113] Specifically, the number of A-IoT devices here is generally multiple, that is, the reading device (such as a Reader) will generally continuously receive inventory results or first command responses from multiple A-IoT devices.

[0114] In this embodiment of the application, the inventory result is the result fed back by the A-IoT device (i.e., the tag) when the reading device performs an inventory operation on the A-IoT device (i.e., the tag). For example, the A-IoT device (i.e., the tag) learns from the content of the instruction of the reading device that it is an inventory operation, and the A-IoT device (i.e., the tag) sends the tag's identification information (i.e., the inventory result) to the reading device, such as the device ID of the A-IoT device.

[0115] In this embodiment, the first command response is a response to a first command. The first command can be a read operation, a write operation, a deactivation operation, an inventory operation, a tag information acquisition operation, a message interaction operation with the tag, etc. These operations have been described previously and will not be repeated here. The response generated by the A-IoT device after executing the first command is called the aforementioned first command response; however, it can also have other names, which are not limited here.

[0116] Optionally, before the reading device receives the inventory results or first command response from the A-IoT device, the A-IoT device may first execute a random access procedure to access the reading device. The triggering conditions for this random access procedure are not limited here.

[0117] After receiving the inventory results from an A-IoT device, the reading device generates a temporary identifier (such as the AIoT ReaderNGAP ID) between the reading device (e.g., Reader RAN) and the first core network device (e.g., AIoTF) to identify the A-IoT device, and maintains the context information of the A-IoT device. For each A-IoT device that has reported the inventory results, the context information maintained by the reading device may include the contents shown in Table 1 (one or more items).

[0118] Table 1

[0119] After that, the reading device will send the first message to the first core network device.

[0120] This temporary identifier can also be represented as A-IoT RAN NGAP ID, RAN assigned device handle, or RAN / CN ID pair, etc. The specific name is not limited here, and the following description will use A-IoT Reader NGAP ID as an example.

[0121] The first message includes inventory results or a first command response. When the first message includes inventory results, the reading device typically sends multiple inventory results from multiple A-IoT devices (e.g., one inventory result corresponding to one A-IoT device). When the first message includes a first command response, the reading device typically sends multiple command responses from multiple A-IoT devices (e.g., one command response corresponding to one A-IoT device). Optionally, the first message may also include a temporary identifier corresponding to the A-IoT device.

[0122] Step S502: The first core network device receives the first message from the reading device.

[0123] Specifically, the first core network device can also be replaced by a component (such as a chip) in the first core network device. Optionally, the first core network device can be A-IoTF or other core network devices, which are not limited here.

[0124] The reading device can send the first message to the first core network device in batches (e.g., sending inventory results or first command responses from one A-IoT device at a time), or it can send the first message to the first core network device in a package (e.g., sending inventory results or first command responses from multiple A-IoT devices at a time). The first core network device receives the first message accordingly. Whether sent in a package or in batches, after a period of time, the first core network device will receive inventory results or first command responses from multiple A-IoT devices.

[0125] If the first message is an inventory result, then after receiving the inventory result, the first core network device can maintain the context information of the A-IoT device corresponding to the inventory result. The context information of each A-IoT device maintained by the first core network device may include the contents shown in Table 2 (one or more).

[0126] Table 2

[0127] The identifier for the current task can be a correlation ID, a transaction ID, etc. The following descriptions will use the task ID as an example.

[0128] The AIoT Reader NGAP ID and AIOTFNGAPID form a pair of information that uniquely identifies the device between the Reader and the AIoTF. Step S503: When all the identifiers in the first range are included in the inventory results or the first set, the first core network device sends a second message to the reading device.

[0129] The first scope includes an identifier used to identify environmental Internet of Things (A-IoT) devices. If the first scope includes one identifier, it can identify one A-IoT device. If the first scope includes multiple identifiers, it can identify multiple A-IoT devices. For example, the identifier can be the device identifier (such as device ID) of the A-IoT device, or other identifiers that can identify A-IoT devices.

[0130] The first scope is determined based on information provided by an application server (such as an AF). The application server communicates directly or indirectly with the first core network device, thus providing relevant information to the first core network device. For example, this relevant information may directly include the A-IoT devices required to perform a specific task, and then determine the corresponding identifiers to identify these A-IoT devices, thereby determining the first scope. Of course, there are many other ways to determine the first scope, which will not be listed here. For another example, the relevant information may include information about a specific task. When the first core network device knows that it needs to complete the specific task, it can determine the A-IoT devices required to complete the specific task, and thus determine the corresponding identifiers to identify these A-IoT devices, thereby determining the first scope. Yet another example is that the relevant information may include information about a reading device (such as a RAN). When the first core network device receives this relevant information, it knows that it needs to use A-IoT devices within the communication range of the reading device to perform the current task, and thus determines the corresponding identifiers to identify these A-IoT devices, thereby determining the first scope.

[0131] The identifiers in the first set correspond to the first command response. Specifically, each first command response corresponds to an A-IoT device. The first core network device can also identify the A-IoT device corresponding to each first command response. In this embodiment, the set of identifiers of the A-IoT devices corresponding to the first command responses received by the first core network device is the first set.

[0132] In this embodiment, when all the identifiers in the first range are included in the inventory results or the first set, that is, when all the identifiers in the first range are included in the received inventory results or the first set for the first time, a second message is sent to the reading device. The second message indicates to stop (e.g., Stop, Cancel, or Skip) the inventory or to stop (e.g., Stop, Cancel, or Skip) the execution of the first command. It can be understood that the A-IoT devices identified by the identifiers in the first range are A-IoT devices that need to complete a specific task. When all the identifiers in the first range are included in the inventory results, it indicates that the inventory results of the A-IoT devices that need to complete a specific task have all been inventoried; when all the identifiers in the first range are included in the first set, it indicates that the A-IoT devices that need to complete a specific task have all executed the first command; therefore, it can indicate to stop inventory or stop the execution of the first command. It should be noted that in one alternative scheme, the first set is merely a code name introduced for ease of description. The actual scheme will not involve the processing or use of the "first set" during execution. For example, the previously mentioned "when all the identifiers in the first range are included in the first set" actually means "when all the identifiers in the first range appear in the first command response received for the first time". Therefore, the actual processing may not involve the "first set".

[0133] It should be noted that, in one optional case, each first command response corresponds to a temporary identifier (such as an NGAP ID). Therefore, the first core network device can identify a corresponding A-IoT device based on this temporary identifier (such as the NGAP ID). In other words, an A-IoT device can be identified based on each first command response. In another optional case, each first command response corresponds to a device identifier (such as a device ID). Therefore, the first core network device can identify a corresponding A-IoT device based on this device identifier (such as the device ID). In other words, an A-IoT device can be identified based on each first command response.

[0134] It can be seen that, regarding the combination of sending conditions for the first message, the second message, and the second message, at least the following situations exist:

[0135] In scenario one, the first message includes inventory results. When all the identifiers in the first range are included in the inventory results, a second message is sent to the reading device, indicating that inventory should be stopped.

[0136] In scenario two, the first message includes a first command response. When all the identifiers in the first range are included in the first set, a second message is sent to the reading device, and the second message indicates that inventory should be stopped.

[0137] Scenario 3: The first message includes a first command response. When all the identifiers in the first range are included in the first set, a second message is sent to the reading device. The second message indicates that the execution of the first command should be stopped.

[0138] Scenario 4: The first message includes a first command response. When all the identifiers in the first range are included in the first set, a second message is sent to the reading device. The second message indicates to stop executing the first command and to stop inventory.

[0139] Step S504: The reading device receives the second message.

[0140] Specifically, after receiving the second message, the reading device stops inventorying or stops executing the first command, as follows:

[0141] Case 1: If the second message indicates to stop inventorying, then the reading device will no longer inventory new A-IoT devices. There may be a stopping action to stop inventorying, or there may not be a corresponding action to stop inventorying. For example, stopping inventorying simply means not continuing to inventory new A-IoT devices, that is, skipping inventorying to perform other subsequent steps that need to be performed.

[0142] Case 2: If the second message indicates to stop executing the first command, then the reading device will no longer instruct new A-IoT devices to execute the first command. The reading device may take a stopping action to stop executing the first command, or it may not take a corresponding action to stop executing the first command. For example, as long as it does not continue to instruct new A-IoT devices to execute the first command, it means to stop executing the first command, that is, to skip the instruction to execute the first command and execute other subsequent steps that need to be executed.

[0143] The embodiments of this application may also contain some additional limitations and / or processes, which can be combined with the preceding solutions (or some features can be replaced) to form new solutions. For ease of understanding, examples are given below:

[0144] In one optional embodiment, the second message further instructs the release of the context information of the A-IoT devices. For example, the second message includes a first instruction and a second instruction, wherein the first instruction instructs the cessation of inventory or the cessation of execution of the first command, and the second instruction instructs the release of the context information of the A-IoT devices. This can instruct the release of the context information of all A-IoT devices corresponding to the already inventoryed results, or it can instruct the release of the context information of a portion of the already inventoryed results, depending on the actual application scenario and needs. Accordingly, the reading device determines which A-IoT devices' context information needs to be released from the second instruction in the second message, and then releases the context information of the corresponding A-IoT devices. This will be explained in detail below.

[0145] Option 1: When the first message includes the inventory results, the second indication information is specifically used to indicate the release of the context information of the A-IoT device corresponding to the first part of the identifier. The first part of the identifier includes identifiers outside the first range included in the inventory results. For example, the first range includes identifiers such as Device ID1, Device ID3, Device ID5, Device ID7, and Device ID9, and the identifiers of the A-IoT devices corresponding to the received inventory results are Device ID0, Device ID1, Device ID2, Device ID3, Device ID4, Device ID5, Device ID6, Device ID7, Device ID8, and Device ID9, respectively. Then, the first part of the identifier is Device ID0, Device ID2, Device ID4, Device ID6, and Device ID8. Specifically, the second instruction information in the second message includes a first identifier list, where the identifiers in the first identifier list are the identifiers in the first range, indicating that the context information of the A-IoT devices corresponding to the identifiers other than those in the first range needs to be released (i.e., a reverse instruction, with the final result to be deduced by the reading device itself); or, the identifiers in the first identifier list are the first part of the identifiers, indicating that the context information of the A-IoT devices corresponding to the first part of the identifiers needs to be released (i.e., a positive instruction, directly indicating the objects that need to be released).

[0146] In an optional embodiment, the second message further instructs the execution of the first command. For example, the second message may also include third instruction information, which instructs the execution of the first command. After receiving the second message, the reading device can transmit the first command to the first A-IoT device, and the first A-IoT device executes the first command accordingly. Optionally, the third instruction information carries an AIoT ReaderNGAPID and / or an AIoTFNGAPID generated by AIoTF. The first A-IoT device is the A-IoT device corresponding to the identifier in the first range. In this case, the following operation process may also be included:

[0147] The reading device sends the first command to the first A-IoT device; after receiving the first command, the first A-IoT device executes the first command to obtain the first command response, and then sends the first command response back to the reading device.

[0148] The reading device receives a first command response from the first A-IoT device and then sends the first command response to the first core network device.

[0149] The first core network device receives a first command response from the first A-IoT device of the reading device.

[0150] The first core network device sends (directly or indirectly) the first command response of the first A-IoT device to the application server, and the application server receives the first command response accordingly.

[0151] It should be noted that when there are multiple first A-IoT devices, the reading device can send the first command to each first A-IoT device individually, or it can broadcast the first command to multiple first A-IoT devices at once.

[0152] Optionally, after the first command response from the first A-IoT device is fed back to the first core network device, the first core network device can send a third message to the reading device, wherein the third message is used to indicate the release of the context information of the first A-IoT device. It can be understood that some of the A-IoT device's context information has already been released in the preceding steps, but because the first A-IoT device still needs to feed back the first command response, its context information has not yet been released. Now that the first A-IoT device has fed back the first command response, its context information can also be released. It should be noted that some first A-IoT devices may have their first command responses fed back to the first core network device earlier. In such cases, the context information of these first A-IoT devices can be released together with the context information of the A-IoT devices corresponding to the first part of the identifier mentioned earlier; that is, the context information of the first A-IoT device that fed back the first command response first can be released first.

[0153] Option 2: When the first message includes the first command response, the second indication information specifically indicates the release of the context information of the A-IoT device corresponding to the received inventory result. It should be noted that before the reading device receives the first command response, it will first receive inventory results sent by some A-IoT devices and send the received inventory results to the first core network device. For example, it receives inventory results sent by 10 A-IoT devices corresponding to Device ID0, Device ID1, Device ID2, Device ID3, Device ID4, Device ID5, Device ID6, Device ID7, Device ID8, and Device ID9 respectively, and sends them to the first core network device. During or after receiving the inventory results, the first core network device sends a fifth message to the reading device. The fifth message is used to instruct the first A-IoT device (i.e., the A-IoT device needed to complete a certain task) to execute the first command. For example, if the five A-IoT devices corresponding to Device ID1, Device ID3, Device ID5, Device ID7, and Device ID9 are all the first A-IoT devices, then the reading device sends (e.g., unicast or broadcast) the first command to the first A-IoT device. Correspondingly, the first A-IoT device executes the first command and sends a first command response to the reading device. After receiving the first command response, the reading device sends a first message (containing the first command response) to the first core network device. The first core network device will also further send (directly or indirectly) the first message to the application server.

[0154] As mentioned above, when all the identifiers in the first range are included in the first set, the first core network device sends a second message to the reading device. For example, when the A-IoT devices corresponding to the identifiers Device ID1, Device ID3, Device ID5, Device ID7, and Device ID9, i.e., all the first A-IoT devices, have responded to the first command, the first core network device sends a second message to the reading device to instruct to stop inventory and / or stop executing the first command, and to release the context information of the A-IoT devices corresponding to the received inventory results. For example, the context of the 10 A-IoT devices corresponding to the identifiers Device ID0, Device ID1, Device ID2, Device ID3, Device ID4, Device ID5, Device ID6, Device ID7, Device ID8, and Device ID9 is released.

[0155] In this embodiment, the decision to stop inventorying and / or stop executing the first command can be made by either the first core network device or the application server. The operation of determining that all identifiers in the first scope are included in the first set can be executed by either the first core network device or the application server. As described above, the response containing the first command will eventually be transmitted (e.g., via a first message) to the application server. The application server also knows which A-IoT devices need to provide the first command response to complete a certain task (also referred to as the first task, target task, current task, etc.). That is, the application server knows that the first A-IoT devices need to provide the first command response. When the first command responses from all the first A-IoT devices are received (i.e., all identifiers in the first scope are included in the first set), the application server can decide to stop inventorying and / or stop executing the first command. Therefore, the application server sends a fourth message to the first core network device, wherein the fourth message is used to indicate to stop inventorying and / or stop executing the first command. Only then will the first core network device send a second message to the reading device to implement the stop inventorying and / or stop executing the first command.

[0156] Optionally, after responding to the second message, stopping inventory and / or stopping the execution of the first command, the reading device may send an acknowledgment message (such as ACK) to the first core network device to notify that the response has been completed.

[0157] In this embodiment of the application, when the first communication device sends a second message to the reading device, it may send the second message to one reading device or to multiple reading devices. For example, to complete the first task, multiple first A-IoT devices need to report inventory results or first command responses. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by one reading device, then the first network device can subsequently send the second message only to that one reading device. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by multiple reading devices, then the first network device can subsequently send the second message to the multiple reading devices.

[0158] In this embodiment of the application, in order to identify the task corresponding to the currently sent / received message, optionally, the sent / received message can carry the task identifier (such as task ID) of the current task. For example, the first message, the second message, the third message, the fourth message, etc. can all carry the task identifier (such as task ID).

[0159] In the method described in Figure 5, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results or first command responses to complete a specific task, it explicitly instructs to stop inventorying or stop executing the first command through the second message. This allows the reading device (such as Reader) to stop inventorying or stop executing the first command in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0160] It should be noted that there are many specific implementation cases based on the principle of the method embodiment shown in Figure 5. For ease of understanding, two more specific application cases are listed below with reference to Figures 6 and 7. Of course, there are other cases as well, which will not be listed here.

[0161] Please refer to Figure 6, which is a flowchart illustrating a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4, or on other architectures. The method includes, but is not limited to, the following steps:

[0162] Step S601: The application server (e.g., AF) sends the first service request to the first core network device (e.g., A-IoTF).

[0163] Specifically, the first service request is used to request the execution of a first command on multiple first AIoT devices. For example, the first service request may include information about the first command, a list of identifiers corresponding to the multiple first AIoT devices, such as a list of device IDs, or filtering information associated with the multiple AIoT devices. Optionally, the first service request may include target operation area information.

[0164] The application server (such as AF) can send the first service request directly to the first core network device (such as A-IoTF), or it can send the first service request to the first core network device (such as A-IoTF) through other network elements. For example, the application server (such as AF) sends the first service request to NEF, and then NEF sends it to the first core network device (such as A-IoTF).

[0165] Accordingly, the first core network device (such as A-IoTF) receives the first service request.

[0166] Step S602: The first core network device (such as A-IoTF) generates a mask based on a list of identifiers of multiple first AIoT devices.

[0167] This mask is used to filter / select devices, or to make specific devices respond to broadcasts. The specific name is not limited; it can be called a mask or AIoT Device Identification information. This application embodiment uses the name mask as an example for description.

[0168] The first core network device (such as A-IoTF) will also determine the corresponding reading device (such as Reader) based on multiple first AIoT devices, that is, which reading device(s) can inventory and execute the first command for the multiple first AIoT devices. The first core network device can be determined.

[0169] Step S603: The first core network device (such as A-IoTF) sends a first inventory request to the identified reading device (such as Reader).

[0170] Accordingly, the reading device (such as a Reader) receives a first inventory request, which includes a previously generated mask. This first inventory request is used to request inventory of AIoT devices within the mask range. It is understood that the AIoT devices within the mask range include at least the aforementioned plurality of first AIoT devices, and may also include other AIoT devices within the mask range that are not among the first AIoT devices requested by the application server.

[0171] Optionally, the first service request may also include information about the first task (i.e., the current task), such as task ID, correlation ID, transaction ID, etc. The following description will use task ID as an example. This first task is the task that needs to be completed currently; it can also be a specific task or a target task. The information about the first task can be used to identify between the first core network and the reading device that the information exchanged is about the first task, in order to distinguish it from other tasks.

[0172] Step S604: The reading device (such as a Reader) broadcasts the mask.

[0173] Step S605: The first AIoT device performs random access based on the mask.

[0174] Specifically, after receiving the mask, AIoT devices within the mask range respond to the reading device (such as a reader) and execute a random access procedure. It should be noted that not only the first AIoT device performs random access, but other AIoT devices within the mask range also perform random access.

[0175] Step S606: The first AIoT device sends the inventory result to the reading device (such as a Reader).

[0176] Specifically, the inventory result includes the identifier of the first AIoT device, such as a device ID or a temporary identifier for the device, and the form of the identifier is not limited here.

[0177] Correspondingly, the reading device (such as a Reader) receives the inventory results from the first AIoT device.

[0178] The principle behind this part can be found in the description of the inventory results in step S501.

[0179] Step S607: The reading device (such as a Reader) generates a temporary identifier corresponding to the first AIoT device.

[0180] Specifically, the generated temporary identifier (such as the A-IoT Reader NGAP ID) is used by the reading device and the first core network device to identify (or distinguish) the first AIoT device, and is used to identify (or distinguish) the AIoT device corresponding to the information (or message) during subsequent information exchanges between the two parties. This temporary identifier can be represented as A-IoT Reader NGAP ID, A-IoT RAN NGAP ID, or RAN assigned device handle, etc. The specific name is not limited here, and the following description will use A-IoT Reader NGAP ID as an example.

[0181] Optionally, the reading device constructs a context for each AIoT device that completes random access. Accordingly, the temporary identifier corresponding to the first AIoT device (such as the A-IoT Reader NGAP ID) is saved in the context of the first AIoT device.

[0182] Step S608: The reading device (e.g., Reader) sends a first message to the first core network device (e.g., A-IoTF).

[0183] Specifically, the first message includes inventory results from the aforementioned first AIoT device.

[0184] Accordingly, the first core network device (such as A-IoTF) receives the first message.

[0185] The principle behind this part can be found in the description of the inventory results in step S502.

[0186] It should be noted that the above-described operations for providing inventory results (such as steps S605, S606, S607, and S608) are illustrated using a first AIoT device as an example. In reality, after the first AIoT device completes random access, the reading device will continue to broadcast request messages (such as Query Rep) to allow other AIoT devices within the request mask range that have not yet performed random access to perform random access. Therefore, inventory results will also be provided to other first AIoT devices, as well as to other AIoT devices within the aforementioned mask range. Furthermore, the timing of inventory feedback from different AIoT devices is not limited; that is, the feedback timing may be the same or different.

[0187] Steps 5a, 6a, 7a, and 8a in Figure 6 illustrate the operation process of feedback inventory results using another AIoT device as an example. The principles of steps 5a, 6a, 7a, and 8a are essentially the same as those of steps S605, S606, S607, and S608.

[0188] Step S609: The first core network device (such as A-IoTF) determines that all identifiers in the first range are included in the received inventory results.

[0189] For example, the list of identifiers corresponding to multiple first AIoT devices carried in the first business request covers the first range of identifiers, which is essentially the range of multiple first AIoT devices requested by the business server.

[0190] It is understandable that each inventory result contains the identifier of an AIoT device. Therefore, by analyzing the identifier in each received inventory result, it can be determined whether the identifiers in the first range are all included in the received inventory results. In essence, this is to determine whether the inventory results corresponding to the multiple first AIoT devices have been inventoried. Only after they have all been inventoried will the subsequent steps, namely step S610, be executed.

[0191] The principle behind this part can be found in the description of the meaning and function of the first range in step S503.

[0192] Step S610: The first core network device (such as A-IoTF) sends a second message to the reading device.

[0193] Accordingly, the reading device receives the second message, which instructs to stop inventory.

[0194] Optionally, the second message may include first indication information (such as Stop-Inventory Indication) to indicate a halt to inventory.

[0195] Optionally, the second message may further include second instruction information and / or third instruction information, wherein:

[0196] The second indication (such as Context Release Indication) is specifically used to instruct the release of the context information of the A-IoT device corresponding to the first part of the identifier. The first part of the identifier includes identifiers outside the first range included in the inventory result. That is, the second indication is used to instruct the release of the context of other A-IoT devices (i.e., A-IoT devices not within the application server's request range) that have completed inventory. The context of the first A-IoT devices that have not yet been used will not be released temporarily.

[0197] The third instruction information instructs the execution of a first command on the first A-IoT device. After receiving the second message, the reading device can send the first command to the first A-IoT device, or in other words, forward / transmit the first command to the first AIoT device. Accordingly, the first A-IoT device executes the first command. Optionally, the third instruction information carries AIoT ReaderNGAPID and / or AIoTFNGAPID generated by AIoTF.

[0198] It should be noted that the aforementioned second and third instruction messages can also be sent independently, i.e., not carried in the same message as the first instruction message. Of course, it's also possible that the second and / or third instruction messages do not need to be sent to the reading device, and the reading device determines, based on other mechanisms, the need for other A-IoT devices besides the aforementioned plurality of first A-IoT devices, and the need to execute the first command on the first A-IoT devices. The following examples will be described assuming that the first message includes the first, second, and third instruction messages.

[0199] Optionally, the second message also carries a temporary identifier for the first A-IoT device.

[0200] Step S611: The reading device responds to the second message and stops inventorying.

[0201] Specifically, responding to the second message, stopping inventory, can be for the current task, meaning no longer inventorying new A-IoT devices. There may be a stopping action to stop inventorying, or there may not be a corresponding action to stop inventorying. For example, stopping inventorying simply means not continuing to inventory new A-IoT devices (e.g., no longer sending Query Rep messages to request inventorying), or skipping inventorying to execute other subsequent steps that need to be performed.

[0202] Optionally, the reading device can also release the context information (such as UE context) of the A-IoT device corresponding to the first part of the identifier. Essentially, this means deleting the context of the A-IoT device that does not need to execute the first command in the current task. The first part of the identifier has already been described and will not be repeated here. The second message may contain explicit information (such as second indication information) to indicate the release of the context information of the A-IoT device corresponding to the first part of the identifier, or it may not contain explicit information. If there is no explicit information, then the reading device decides on its own whether to release the context information of the A-IoT device corresponding to the first part of the identifier. Optionally, the reading device can maintain an information list about the plurality of first A-IoT devices. This information list can be constructed based on temporary identifiers (such as AIOT Reader NGAP ID). The context information of A-IoT devices not in this information list will be released.

[0203] Optionally, after the reading device responds to the second message and stops storing and / or releasing the context information (such as UE context) of the A-IoT device corresponding to the first part of the identifier, it may send an acknowledgment message (such as ACK) to the first core network device to notify that the response has been completed.

[0204] In this embodiment of the application, when the first communication device sends a second message to the reading device, it may send the second message to one reading device or to multiple reading devices. For example, to complete the first task, multiple first A-IoT devices need to report inventory results or first command responses. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by one reading device, then the first network device can subsequently send the second message only to that one reading device. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by multiple reading devices, then the first network device can subsequently send the second message to the multiple reading devices.

[0205] Step S612: The reading device sends a first command to the first A-IoT device.

[0206] The characteristics and functions of the first command (e.g., Read) have been described previously and will not be repeated here. After receiving the first command, the first A-IoT device executes the first command to obtain the first command response (e.g., Read Result).

[0207] Optionally, the first command can be a downlink AIoT NAS message or a message in other formats, which is not limited here.

[0208] Step S613: The first A-IoT device sends the first command response.

[0209] The reading device receives a first command response from a first A-IoT device and then sends the first command response to a first core network device. Correspondingly, the first core network device receives the first command response.

[0210] It should be noted that, as mentioned earlier, there are multiple first A-IoT devices. Under normal circumstances, these multiple first A-IoT devices will send their own first command responses. Therefore, under normal circumstances, the first core network device will receive first command responses from multiple first A-IoT devices.

[0211] Step S614: The first core network device determines that it has received the first command response from the aforementioned plurality of first A-IoT devices.

[0212] Step S615: The first core network device sends a third message to the reading device.

[0213] In Case 1, the third message (such as Context-Release Indication) is used to indicate the release (or deletion) of the context information of the first A-IoT device (e.g., multiple first A-IoT devices), or to indicate the release of the context information of A-IoT devices associated with the current task that have not yet released their context information, or to indicate the release of the context information of all devices inventoried by the current task. Therefore, the third message may also include the task ID of the current task. It can be understood that some A-IoT device context information has already been released in the previous steps, but because the first A-IoT device still needs to respond to the first command, its context information has not yet been released. Now that the first A-IoT device has responded to the first command, its context information can also be released. Optionally, it is possible that some first A-IoT devices' first command responses were responded to by the first core network device earlier. In this case, the context information of these first A-IoT devices can be released together with the context information of the A-IoT devices corresponding to the first part of the identifier mentioned above; that is, the context information of the first A-IoT devices that responded to the first command first can be released first.

[0214] In Case 2, the third message (such as Context-Release Indication) is used to indicate the cessation of execution of the first command. Optionally, the third message may also include the task ID of the current task. Accordingly, upon receiving the third message, the reading device knows to stop executing the first command (e.g., stop sending the first command to the A-IoT device) and / or stop monitoring the network.

[0215] In Case 3, the third message (such as Context-Release Indication) follows the instructions in Case 2. However, the reading device will also release (or delete) the context information of the first A-IoT device (e.g., multiple first A-IoT devices), or release the context information of A-IoT devices associated with the current task that have not yet released their context information, or release the context information of all devices inventoried by the current task. For example, after receiving the second message, the reading device stops inventorying but does not release the context information of the A-IoT devices. The context information of all A-IoT devices related to the current task is released after receiving the third message.

[0216] In Case 4, the third message is instructed in the same way as in Case 1, but the reading device will also stop executing the first command.

[0217] In this embodiment of the application, when the first communication device sends a third message to the reading device, it may send the third message to one reading device or to multiple reading devices. For example, to complete the first task, multiple first A-IoT devices need to report inventory results or first command responses. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by one reading device, then the first network device can subsequently send the third message only to that one reading device. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by multiple reading devices, then the first network device can subsequently send the third message to the multiple reading devices.

[0218] Optionally, after the reading device completes the corresponding operation based on the third message, it can return a response message (such as ACK) to the first core network device to notify that the response has been completed, so that the first core network device can continue to perform subsequent operations.

[0219] Correspondingly, the first core network device can also release the context messages of the A-IoT devices associated with its stored previous tasks.

[0220] Step S616: The first core network device sends the first service response message to the application server.

[0221] The first service response message includes the first command responses from the plurality of first A-IoT devices. This first service response message can be seen as a response to the first service request sent by the application server. Optionally, the plurality of first command responses from the first A-IoT devices may be sent separately; for example, sending one first command response from one first A-IoT device at a time, in which case multiple first service response messages may be sent.

[0222] In this embodiment of the application, the steps listed above are merely illustrative examples. Some steps may be omitted or replaced with other steps, or new steps may be added, which can also constitute a new feasible solution. In addition, the order of the steps described above does not represent the order of execution of the steps. The order of execution of the steps may be the same as the order of description or different from the order of description (but the logic must be coherent and reasonable). For example, the order of steps S616 and S615 does not affect the implementation of the solution.

[0223] In the method described in Figure 6, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results to complete a specific task, it explicitly instructs to stop inventorying through the second message. This allows the reading device (such as Reader) to stop inventorying in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0224] Please refer to Figure 7, which is a flowchart illustrating a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4, or on other architectures. The method includes, but is not limited to, the following steps:

[0225] Step S701: The application server (e.g., AF) sends the first service request to the first core network device (e.g., A-IoTF).

[0226] Specifically, the first service request is used to request the execution of a first command on multiple first AIoT devices. For example, the first service request may include information about the first command, a list of identifiers corresponding to the multiple first AIoT devices, such as a list of device IDs, or filtering information associated with the multiple AIoT devices. Optionally, the first service request may include target operation area information.

[0227] The application server (such as AF) can send the first service request directly to the first core network device (such as A-IoTF), or it can send the first service request to the first core network device (such as A-IoTF) through other network elements. For example, the application server (such as AF) sends the first service request to NEF, and then NEF sends it to the first core network device (such as A-IoTF).

[0228] Accordingly, the first core network device (such as A-IoTF) receives the first service request.

[0229] Step S702: The first core network device (such as A-IoTF) generates a mask based on a list of identifiers of multiple first AIoT devices.

[0230] This mask is used to filter / select devices, or to make specific devices respond to broadcasts. The specific name is not limited; it can be called a mask or AIoT Device Identification information. This application embodiment uses the name mask as an example for description.

[0231] The first core network device (such as A-IoTF) will also determine the corresponding reading device (such as Reader) based on multiple first AIoT devices, that is, which reading device(s) can inventory and execute the first command for the multiple first AIoT devices. The first core network device can be determined.

[0232] Step S703: The first core network device (such as A-IoTF) sends a first inventory request to the identified reading device (such as Reader).

[0233] Accordingly, the reading device (such as a Reader) receives a first inventory request, which includes a previously generated mask. This first inventory request is used to request inventory of AIoT devices within the mask range. It is understood that the AIoT devices within the mask range include at least the aforementioned plurality of first AIoT devices, and may also include other AIoT devices within the mask range that are not among the first AIoT devices requested by the application server.

[0234] Optionally, the first service request may also include information about the first task (i.e., the current task), such as task ID, correlation ID, transaction ID, etc. The following description will use task ID as an example. This first task is the task that needs to be completed currently; it can also be a specific task or a target task. The information about the first task can be used to identify between the first core network and the reading device that the information exchanged is about the first task, in order to distinguish it from other tasks.

[0235] Step S704: The reading device (such as a Reader) broadcasts the mask.

[0236] Step S705: The first AIoT device performs random access based on the mask.

[0237] Specifically, after receiving the mask, AIoT devices within the mask range respond to the reading device (such as a reader) and execute a random access procedure. It should be noted that not only the first AIoT device performs random access, but other AIoT devices within the mask range also perform random access.

[0238] Step S706: The first AIoT device sends the inventory results to the reading device (such as a Reader).

[0239] Specifically, the inventory result includes the identifier of the first AIoT device, such as a device ID or a temporary identifier for the device, and the form of the identifier is not limited here.

[0240] Correspondingly, the reading device (such as a Reader) receives the inventory results from the first AIoT device.

[0241] The principle behind this part can be found in the description of the inventory results in step S501.

[0242] Step S707: The reading device (such as a Reader) generates a temporary identifier corresponding to the first AIoT device.

[0243] Specifically, the generated temporary identifier (such as the A-IoT Reader NGAP ID) is used by the reading device and the first core network device to identify (or distinguish) the first AIoT device, and is used to identify (or distinguish) the AIoT device corresponding to the information (or message) during subsequent information exchanges between the two parties. This temporary identifier can be represented as A-IoT Reader NGAP ID, A-IoT RAN NGAP ID, or RAN assigned device handle, etc. The specific name is not limited here, and the following description will use A-IoT Reader NGAP ID as an example.

[0244] Optionally, the reading device constructs a context for each AIoT device that completes random access. Accordingly, the temporary identifier corresponding to the first AIoT device (such as the A-IoT Reader NGAP ID) is saved in the context of the first AIoT device.

[0245] Step S708: The reading device (e.g., Reader) sends a sixth message to the first core network device (e.g., A-IoTF).

[0246] Specifically, the sixth message includes inventory results from the aforementioned first AIoT device.

[0247] Accordingly, the first core network device (such as A-IoTF) receives the sixth message.

[0248] The principle behind this part can be found in the description of the inventory results in step S502.

[0249] It should be noted that the above-described operations for providing inventory results (steps S705, S706, S707, and S708) are based on an example of a first AIoT device. In reality, after the first AIoT device completes random access, the reading device will continue to broadcast request messages (such as Query Rep) to allow other AIoT devices within the request mask range that have not yet performed random access to perform random access. Therefore, inventory results will also be provided to other first AIoT devices, as well as to other AIoT devices within the aforementioned mask range. Furthermore, the timing of inventory feedback from different AIoT devices is not limited; that is, the feedback timing may be the same or different.

[0250] Steps 5b, 6b, 7b, and 8b in Figure 7 illustrate the operation process of feedback inventory results using another AIoT device as an example. The principles of steps 5b, 6b, 7b, and 8b are essentially the same as those of steps S705, S706, S707, and S708.

[0251] Step S709: The first core network device sends the fifth message to the reading device.

[0252] The fifth message is used to instruct the first A-IoT device to execute the first command. Correspondingly, the reading device responds to the fifth message and sends the first command to the first A-IoT device. Optionally, the fifth message can be transparently transmitted on the reading device.

[0253] Optionally, the fifth message carries AIoT ReaderNGAPID, and / or AIoTFNGAPID generated by AIoTF.

[0254] The characteristics and functions of the first command (e.g., Read) have been described previously and will not be repeated here. After receiving the first command, the first A-IoT device executes the first command to obtain the first command response (e.g., Read Result).

[0255] Optionally, the first command can be a downlink AIoT NAS message or a message in other formats, which is not limited here.

[0256] It should be noted that the reading device may not send the first command to other A-IoT devices. As mentioned earlier, other A-IoT devices refer to the A-IoT devices other than the multiple first A-IoT devices among all the A-IoT devices corresponding to the inventory results received by the reading device.

[0257] Step S710: The first A-IoT device sends the first message.

[0258] Specifically, the first message includes the first command response obtained by the first A-IoT device executing the first command.

[0259] The reading device receives the first message from the first A-IoT device and sends the first message to the first core network device.

[0260] Step S711: The first core network device receives the first message.

[0261] Specifically, the first core network device receives the first message and obtains the first command response from the first A-IoT device. Optionally, as mentioned above, there are multiple first A-IoT devices. Under normal circumstances, these multiple first A-IoT devices will send their own first command responses. Therefore, under normal circumstances, the first core network device will receive multiple first messages, thereby obtaining the first command responses from multiple first A-IoT devices.

[0262] Step S712: The first core network device sends the first service response message to the application server.

[0263] The first service response message includes the first command responses from the plurality of first A-IoT devices. This first service response message can be seen as a response to the first service request sent by the application server. Optionally, the plurality of first command responses from the first A-IoT devices may be sent separately; for example, sending one first command response from one first A-IoT device at a time, in which case multiple first service response messages may be sent.

[0264] Optionally, the first business response includes the task identifier (such as task ID) of the current task.

[0265] Step S713: The application server sends the fourth message to the first core network device.

[0266] The fourth message (e.g., End Indication) is used to indicate a halt to inventory and / or a halt to the execution of the first command. Optionally, the fourth message may also include the task identifier (e.g., task ID) of the current task to indicate that inventory is being stopped for the current task.

[0267] Step S714: The first core network device responds to the fourth message, or the first core network device determines that all the identifiers in the first range are included in the first set.

[0268] There are two possible implementation methods:

[0269] Option 1: The first core network device responds to the fourth message and then executes subsequent steps S715.

[0270] Optionally, in the second implementation, it is determined that all identifiers in the first range are included in the first set, and then subsequent steps S715 are executed.

[0271] The identifier list corresponding to the multiple first AIoT devices carried in the first business request covers the first range of identifiers, which is essentially the range of multiple first AIoT devices requested by the business server.

[0272] The identifiers in the first set correspond to the first command response. Specifically, each first command response corresponds to an A-IoT device. The first core network device can also identify the A-IoT device corresponding to each first command response. In this embodiment, the set of identifiers of the A-IoT devices corresponding to the first command responses received by the first core network device is the first set.

[0273] The principle behind this part can be found in the description of the meaning and function of the first range in step S503.

[0274] In this second implementation, the subsequent step S715 will only be executed when all the identifiers in the first range are included in the first set, that is, when all the identifiers in the first range are included in the first set for the first time.

[0275] Alternatively, if optional method two is used, step S713 does not exist.

[0276] Step S715: The first core network device sends a second message to the reading device.

[0277] Accordingly, the reading device receives the second message, which indicates that the inventory should be stopped. Optionally, the second message may also include the task identifier (such as task ID) of the current task to indicate that the inventory should be stopped for the current task.

[0278] Optionally, the second message may include first indication information (such as Stop-Inventory Indication) to indicate a halt to inventory.

[0279] Optionally, the second message may also include a fourth indication (such as Context Release Indication), which is specifically used to indicate the release (or deletion) of the context information of the A-IoT devices corresponding to the received inventory results, such as the context information of the A-IoT devices corresponding to all received inventory results, or the context information of the A-IoT devices corresponding to all inventory results of the current task.

[0280] Optionally, the fourth indication information also carries the task identifier (such as task ID) of the current task.

[0281] Step S716: The reading device responds to the second message and stops executing the first command.

[0282] Specifically, responding to the second message and stopping the execution of the first command can be done for the current task by no longer executing the first command for new A-IoT devices (i.e., not sending the first command to new A-IoT devices). Alternatively, it can stop inventory management altogether. There might be a stopping action to halt inventory management, or there might not be. For example, simply ceasing inventory management for new A-IoT devices signifies stopping inventory management (e.g., no longer sending Query Rep messages to request inventory management), or skipping inventory management to execute other necessary subsequent steps. Optionally, a new message can also be used to indicate stopping inventory management.

[0283] Optionally, the reading device can also release (or delete) the context information of all A-IoT devices corresponding to all received inventory results, or the context information of A-IoT devices corresponding to all inventory results of the current task.

[0284] In this embodiment of the application, when the first communication device sends a second message to the reading device, it may send the second message to one reading device or to multiple reading devices. For example, to complete the first task, multiple first A-IoT devices need to report inventory results or first command responses. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by one reading device, then the first network device can subsequently send the second message only to that one reading device. If the inventory results or first command responses reported by the multiple first A-IoT devices are all aggregated (or sent) to the first core network device by multiple reading devices, then the first network device can subsequently send the second message to the multiple reading devices.

[0285] Step S717: The reading device sends a first response message to the first core network device.

[0286] Specifically, the first response message (ACK) is used to indicate that the execution of the first command has been stopped and / or the context information of the A-IoT device corresponding to all inventory results of the current task has been released.

[0287] Accordingly, upon receiving the first response message, the first core network device can learn that the reading device has stopped inventorying and / or has released the context information of all A-IoT devices corresponding to the inventory results of the current task.

[0288] Step S718: The first core network device releases the context information of all A-IoT devices corresponding to the inventory results of the current task.

[0289] Optionally, step S717 may not be present, meaning the first core network device may determine that the current task has ended and execute step S718.

[0290] In the embodiments of this application, the steps listed above are only illustrative examples. Some steps may be omitted or replaced with other steps, or new steps may be added, which can also constitute a new feasible solution. In addition, the order of description of the steps above does not represent the order of execution of the steps. The order of execution of the steps may be the same as the order of description or may be different from the order of description (but the logic must be coherent and reasonable).

[0291] In the method described in Figure 7, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to respond to the first command to complete a specific task, the second message explicitly instructs to stop inventory, so that the reading device (such as Reader) can stop inventory in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0292] The following describes the communication device provided in the embodiments of this application.

[0293] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0294] The communication device of the present application embodiment will now be described in detail with reference to Figures 8 to 10.

[0295] Figure 8 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 8, the communication device includes a processing module 801 and a transceiver module 802. The transceiver module 802 can implement corresponding communication functions, and the processing module 801 is used for data processing. The transceiver module 802 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0296] In some embodiments of this application, the communication device can be used to perform the actions performed by the terminal in the above method embodiments. For example, the communication device can be the reading device itself or a chip or functional module configurable in the reading device. In still other embodiments of this application, the communication device can be used to perform the actions performed by the first core network device in the above method embodiments. For example, the communication device can be the first core network device itself or a chip or functional module configurable in the first core network device. Specifically, the transceiver module 802 is used to perform the transceiver-related operations in the above method embodiments, and the processing module 801 is used to perform the processing-related operations in the above method embodiments. The processing module 801 can perform the corresponding operations by calling a computer program or by performing the corresponding operations through corresponding hardware circuits. The transceiver module 802 can perform the transceiver operations independently or under the control of the processing module 801.

[0297] For example, the communication device shown in FIG8 can be a first core network device or a device (e.g., a chip) in the first core network device. The processing module 801 and the transceiver module 802 in the communication device can respectively perform the following operations:

[0298] The transceiver module 802 is used to receive a first message, the first message including inventory results or a first command response, the first command response being a response to a first command;

[0299] When all the identifiers in the first range are included in the inventory results or the first set, the transceiver module 802 is further configured to send a second message, wherein the second message indicates to stop inventory or stop executing the first command, the first range includes identifiers, the identifiers are used to identify environmental Internet of Things (A-IoT) devices, the first range is determined based on information provided by the application server, the application server communicates with the first core network device, and the identifiers in the first set correspond to the first command response.

[0300] In the above method, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results or first command responses to complete a specific task, the second message explicitly instructs to stop inventorying or stop executing the first command. This allows the reading device (such as Reader) to stop inventorying or stop executing the first command in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0301] In one alternative implementation, the second message further instructs the release of the A-IoT device's context information. It is understood that using the A-IoT device's context information can reduce data storage and computational overhead.

[0302] In another optional implementation, the first message includes the inventory result, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier. The first part of the identifier includes identifiers outside the first range included in the inventory result. In this step, only the context information of the A-IoT device corresponding to the first part of the identifier is released, while the context information of the first A-IoT device is retained. This reduces data storage and computational overhead while ensuring the smooth operation of subsequent operations related to the first A-IoT device.

[0303] In another alternative implementation, the second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers.

[0304] In another alternative implementation, the second message is also used to instruct the execution of the first command:

[0305] The transceiver module 802 is further configured to receive a first command response from a first A-IoT device of the reading device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range;

[0306] The transceiver module 802 is also used to send the first command response of the first A-IoT device to the application server.

[0307] In this approach, after inventorying, the system continues to acquire the first command response from the first A-IoT device and feeds that first command response back to the application server, thereby meeting the business needs of the application server.

[0308] In yet another alternative implementation, the transceiver module 802 is also used for:

[0309] Send a third message, wherein the third message is used to indicate the release of the context information of the first A-IoT device.

[0310] In this approach, once the first command response of the first A-IoT device is sent to the application server, the first A-IoT device is no longer in use. Therefore, its context information is released in the final stage, further reducing data storage and computational overhead.

[0311] In another optional implementation, the first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result. In this approach, after the first command response of the first A-IoT device is sent to the application server, the first core network device releases the context information of all A-IoT devices related to the current task at once.

[0312] In another alternative implementation, the transceiver module 802 is also used to receive inventory results before receiving the first message containing the first command response.

[0313] In yet another alternative implementation, the transceiver module 802 is also used for:

[0314] A fourth message is received from the application server, wherein the fourth message is used to indicate that inventory should be stopped.

[0315] In another alternative implementation, the processing module 801 is used to determine that all identifiers in the first range are included in the first set.

[0316] Reusing Figure 8, in some other embodiments of this application, for example, the communication device shown in Figure 8 can be a reading device or a component within a reading device, and the processing module 801 and transceiver module 802 in the communication device can respectively perform the following operations:

[0317] The transceiver module 802 is used to send a first message, wherein the first message includes inventory results or a first command response, and the first command response is a response to a first command;

[0318] The transceiver module 802 is used to receive a second message, wherein the second message indicates to stop inventory or stop executing the first command;

[0319] The processing module 801 is used to stop inventorying the environmental Internet of Things (A-IoT) device or to stop instructing the A-IoT device to execute the first command.

[0320] In the above method, since the second message is sent by the first core network device to the reading device (such as Reader), and the first core network device knows which A-IoT devices need to provide inventory results or first command responses to complete a specific task, the second message explicitly instructs to stop inventorying or stop executing the first command. This allows the reading device (such as Reader) to stop inventorying or stop executing the first command in a timely manner while ensuring that the specific task can be completed, thus saving signaling and time slot resources on the air interface side.

[0321] In one alternative implementation, the second message also indicates the release of the A-IoT device's context information. It is understood that using the A-IoT device's context information can reduce data storage and computational overhead.

[0322] In another alternative implementation, the first message includes the inventory result, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier, wherein the first part of the identifier includes identifiers outside the first range included in the inventory result; the processing module 801 is used to release the context information of the A-IoT device corresponding to the first part of the identifier.

[0323] In this step, only the context information of the A-IoT device corresponding to the first part of the identifier is released, while the context information of the first A-IoT device is retained. This reduces data storage and computation overhead and ensures that subsequent operations related to the first A-IoT device can proceed smoothly.

[0324] In another alternative implementation, the second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers.

[0325] In another alternative implementation:

[0326] The transceiver module 802 is used to receive a third message, which is used to indicate the release of the context information of the first A-IoT device;

[0327] The processing module 801 is used to release the context information of the first A-IoT device.

[0328] In this approach, once the first command response of the first A-IoT device is sent to the application server, the first A-IoT device is no longer in use. Therefore, its context information is released in the final stage, further reducing data storage and computational overhead.

[0329] In another alternative implementation, the second message is further used to instruct the execution of the first command, wherein:

[0330] The transceiver module 802 is used to send the first command to the first A-IoT device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range;

[0331] The transceiver module 802 is used to receive a first command response from the first A-IoT device;

[0332] The transceiver module 802 is used to send the first command response from the first A-IoT device.

[0333] In this approach, after inventorying, the system continues to acquire the first command response from the first A-IoT device and feeds that first command response back to the application server, thereby meeting the business needs of the application server.

[0334] In another alternative implementation, the first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result; the processing module 801 is used for:

[0335] Release the context information of the A-IoT device corresponding to the received inventory results.

[0336] In this approach, after the first command response of the first A-IoT device is sent to the application server, the first core network device releases the context information of all A-IoT devices related to the current task at once.

[0337] In another alternative implementation, the transceiver module 802 is used to receive a fifth message, wherein the fifth message is used to instruct the execution of the first command.

[0338] In this approach, the first core network device notifies the reading device to stop executing the first command via a separate message. Therefore, the reading device will no longer instruct the A-IoT device to execute the first command, and the immediate cessation of executing the first command can reduce unnecessary overhead.

[0339] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0340] The communication device according to the embodiments of this application has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG8 above falls within the protection scope of the embodiments of this application.

[0341] The following description is merely an example and does not limit the product form of the communication device in the embodiments of this application to this.

[0342] In one possible implementation, in the communication device shown in FIG8, the processing module 801 can be one or more processors, and the transceiver module 802 can be a transceiver, or the transceiver module 802 can also be a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0343] As shown in Figure 9, the communication device 90 includes one or more processors 920 and transceivers 910. Exemplarily, the transceiver 910 is used to perform the functions or steps implemented by the transceiver module 802 shown in Figure 8, and the processor 920 is used to perform the functions or steps implemented by the processing module 801 shown in Figure 8. Detailed descriptions of the processor 920 and transceiver 910 can be found in Figure 8 or the method embodiments shown above, and will not be elaborated further here.

[0344] The descriptions of the relevant steps and information in the above embodiments can be found in the descriptions of the method embodiments above, and will not be detailed here.

[0345] In various implementations of the communication device shown in Figure 9, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0346] Optionally, the communication device 90 may further include one or more memories 930 for storing program instructions and / or data. The memories 930 are coupled to the processor 920. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 920 may operate in conjunction with the memories 930. The processor 920 may execute program instructions stored in the memories 930. Optionally, at least one of the aforementioned memories may be included in the processor.

[0347] This embodiment does not limit the specific connection medium between the transceiver 910, processor 920, and memory 930. In Figure 9, the memory 930, processor 920, and transceiver 910 are connected via a bus 940, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 9, but this does not indicate that there is only one bus or one type of bus.

[0348] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0349] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code having instruction or data structure forms, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0350] The processor 920 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 930 is primarily used for storing software programs and data. The transceiver 910 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0351] When the communication device is powered on, the processor 920 can read the software program in the memory 930, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 920 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 920. The processor 920 converts the baseband signal into data and processes the data.

[0352] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0353] The communication device shown in this application embodiment may also have more components than those in Figure 9, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above.

[0354] In another possible implementation, in the communication device shown in Figure 8, the processing module 801 can be one or more logic circuits, and the transceiver module 802 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 802 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface. As shown in Figure 10, the communication device shown in Figure 10 includes a logic circuit 1001 and an interface 1002. That is, the above-mentioned processing module 801 can be implemented using the logic circuit 1001, and the transceiver module 802 can be implemented using the interface 1002. Among them, the logic circuit 1001 can be a chip, a processing circuit, an integrated circuit, or a system-on-a-chip (SoC) chip, etc., and the interface 1002 can be a communication interface, an input / output interface, pins, etc. For example, Figure 10 uses the above-mentioned communication device as a chip, which includes the logic circuit 1001 and the interface 1002.

[0355] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1001 can be used to execute the functions or steps implemented by the processing module 801 shown in FIG8, and the interface 1002 can be used to execute the functions or steps implemented by the transceiver module 802 shown in FIG8. For a detailed description of the logic circuit 1001 and the interface 1002, please refer to FIG8 or the method embodiment shown above, which will not be detailed here.

[0356] The above description of the communication device is only an example. For a detailed description of the communication device shown in Figure 10, please refer to the above method embodiment or Figure 8 or Figure 9. It will not be described in detail here.

[0357] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0358] The descriptions of relevant steps and information in the above embodiments can be found in the method embodiments described above, and will not be detailed here. For the specific implementation methods of the embodiments shown in Figure 10, please also refer to the above embodiments, which will not be detailed here.

[0359] This application also provides a communication system, which includes a first core network device, a reading device, etc. The interaction between the first core network device, the reading device, etc., can be used to execute all or part of the steps in any of the foregoing method embodiments.

[0360] In addition, this application also provides a computer program for implementing the operations and / or processes performed by various communication devices in the method provided in this application.

[0361] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by various communication devices in the methods provided in this application.

[0362] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by various entities in the method provided in this application to be executed.

[0363] In the 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 modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0364] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0365] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0366] If the integrated module is implemented as a software functional module and sold or used as an independent product, it 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 all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable 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 readable 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.

[0367] 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

A communication method characterized by comprising: The method includes: (1) A chip applied to a first core network device or a chip in a first core network device. Receive a first message, the first message including inventory result or a first command response, the first command response being a response to a first command; When all the identifiers in the first range are included in the inventory results or the first set, a second message is sent, wherein the second message indicates to stop inventory or stop executing the first command, the first range includes identifiers used to identify environmental Internet of Things (A-IoT) devices, the first range is determined based on information provided by the application server, the application server communicates with the first core network device, and the identifiers in the first set correspond to the first command response. The method of claim 1, wherein The second message also instructs the release of the context information of the A-IoT device. The method according to claim 2, characterized in that The first message includes the inventory results, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier, wherein the first part of the identifier includes identifiers outside the first range contained in the inventory results. The method according to claim 3, characterized in that The second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers. The method according to claim 3 or 4, characterized in that The second message is also used to instruct the execution of the first command, and the method further includes: Receive a first command response from a first A-IoT device of the reading device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range; Send the first command response from the first A-IoT device to the application server. The method according to claim 5, characterized in that Also includes: Send a third message, wherein the third message is used to instruct the release of the context information of the first A-IoT device and / or instruct the cessation of execution of the first command. The method according to claim 2, characterized in that The first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result. The method of claim 7, wherein Also includes: Receive inventory results. The method according to claim 7 or 8, characterized in that Also includes: A fourth message is received from the application server, wherein the fourth message is used to indicate that inventory should be stopped. The method according to claim 7 or 8, characterized in that Also includes: It is determined that all identifiers in the first range are included in the first set. A communication method characterized by comprising: include: Send a first message, wherein the first message includes inventory results or a first command response, and the first command response is a response to a first command; Receive a second message, wherein the second message indicates to stop inventory or stop executing the first command; Stop inventorying the A-IoT device or stop instructing the A-IoT device to execute the first command. The method of claim 11, wherein The second message also indicates the release of context information for the A-IoT device. The method of claim 12, wherein The first message includes the inventory result, and the second message further indicates the release of the context information of the A-IoT device corresponding to the first part of the identifier, wherein the first part of the identifier includes identifiers outside the first range included in the inventory result; the method further includes: Release the context information of the A-IoT device corresponding to the first part of the identifier. The method of claim 13, wherein The second message includes a first identifier list, wherein the identifiers in the first identifier list are identifiers within the first range, or the identifiers in the first identifier list are the first subset of identifiers. The method of claim 13, wherein Also includes: Receive a third message, the third message being used to instruct the release of the context information of the first A-IoT device and / or instruct the cessation of execution of the first command; Release the context information of the first A-IoT device and / or stop executing the first command. The method according to any one of claims 13-15, characterized in that The second message is also used to instruct the execution of the first command, and the method further includes: Send the first command to the first A-IoT device, wherein the first A-IoT device is the A-IoT device corresponding to the identifier in the first range; Receive a first command response from the first A-IoT device; Send the first command response from the first A-IoT device. The method of claim 12, wherein The first message includes the first command response, and the second message further indicates the release of the context information of the A-IoT device corresponding to the received inventory result; the method also includes: Release the context information of the A-IoT device corresponding to the received inventory results. The method of claim 17, wherein Also includes: Receive a fifth message, wherein the fifth message is used to instruct the execution of the first command. A communication device characterized by comprising: The communication device includes a module for performing the method as described in any one of claims 1-10; or, the communication device includes a processor for performing the method as described in any one of claims 1-10. A reading device, characterized in that The reading device includes a module for performing the method as described in any one of claims 11-18; or, the reading device includes a processor for performing the method as described in any one of claims 11-18. A communication device characterized by comprising: Includes logic circuits and interfaces, wherein the logic circuits and interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 1-10. A reading device, characterized in that Includes logic circuits and interfaces, wherein the logic circuits and interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 11-18. A computer-readable storage medium, characterized by The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1-18. A communication system characterized by It includes a core network device and a reading device, wherein the core network device is configured to perform the method as described in any one of claims 1-10, and the reading device is configured to perform the method as described in any one of claims 11-18. A computer program product, characterized in that The computer program product includes a computer program or instructions that, when executed, cause the method as described in any one of claims 1-10 to be performed. A computer program product, characterized in that The computer program product includes a computer program or instructions that, when executed, cause the method as described in any one of claims 11-18 to be performed.

Images