Communication method and apparatus

Abstract

The present application belongs to the field of communications. Provided are a communication method and apparatus, such that a service-related operation can be executed by an applicable reader. The method comprises: receiving a first message, and sending a second message to a first access and mobility management network element, wherein the first message indicates a first service, the second message indicates a first operation, the first operation is related to the first service, the second message further comprises information indicating at least one reader, the at least one reader is used for executing the first service, and the at least one reader is connected to the first access and mobility management network element.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411600022.1, filed with the State Intellectual Property Office of China on November 8, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT). A-IoT is also known as Ambient Power-enabled IoT or Passive IoT (P-IoT). A-IoT can be applied to various business scenarios, such as warehousing / transportation / materials management or fixed asset management. In A-IoT business scenarios, the requesting party can send a service request to the core network to request the corresponding reader to execute A-IoT services, such as inventory, read / write, and deactivation.

[0004] However, how to ensure that A-IoT services can be executed by applicable readers is a problem currently under research. Summary of the Invention

[0005] This application provides a communication method and apparatus to enable business-related operations to be executed by an applicable reader.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] In a first aspect, a communication method is provided, applied to a first network element. The method includes: receiving a first message and sending a second message to a first access and mobility management network element. The first message indicates a first service, and the second message indicates a first operation related to the first service. The second message also includes information indicating at least one reader, the at least one reader being used to execute the first service, and the at least one reader being connected to the first access and mobility management network element.

[0008] Therefore, upon receiving a request for the first service, such as a first message, the first network element can determine at least one reader capable of executing the first service and send a second message to the first access and mobility management network element connected to the at least one reader, instructing the at least one reader to perform an operation related to the first service, such as a first operation, that is, to enable the operation to be performed by the applicable reader.

[0009] In one possible design, the method further includes: determining a first access and mobility management network element based on a first message, that is, the first network element can determine the corresponding access and mobility management network element according to the request of the first service, so as to achieve on-demand determination.

[0010] Optionally, determining the first access and mobility management network element according to the first message includes: determining N readers suitable for executing the first service, and determining K access and mobility management network elements corresponding to the N readers. N is an integer greater than or equal to 1, and the N readers include at least one reader; K is an integer greater than or equal to 1, and the K access and mobility management network elements include the first access and mobility management network element. In other words, the first network can first determine the readers suitable for executing the first service, or in other words, all readers capable of executing the first service, based on the first service, and then determine the access and mobility management network elements corresponding to each of these readers. This ensures that the information of the first service can be routed to all readers capable of executing the first service through these access and mobility management network elements, ensuring that the operation corresponding to the first service can be successfully executed.

[0011] Optionally, the method further includes: receiving information from M readers from X access and mobility management network elements, and obtaining the correspondence between the X access and mobility management network elements and the M readers based on the information from the M readers. X and M are integers greater than or equal to 1; the X access and mobility management network elements include the K access and mobility management network elements, the M readers include the N readers, and the correspondence includes the correspondence between the N readers and the K access and mobility management network elements. That is, the first network can dynamically establish the correspondence between access and mobility management network elements and readers in advance to ensure that when determining the readers suitable for performing the operation corresponding to the first service, the access and mobility management network elements connected to these readers can be found based on this correspondence, thereby achieving correct data routing. Furthermore, since the correspondence between access and mobility management network elements and readers is dynamically established through information reported by the access and mobility management network elements to the readers, it can be dynamically updated according to the actual connection situation.

[0012] Furthermore, the reader information mentioned above includes at least one of the following: a reader identifier, information indicating the reader's service area, an access network device identifier, or information indicating the access network device's service area. The reader is connected to the access network device (e.g., the reader is a terminal), or the access network device contains the reader (i.e., the reader is part of the access network device). In other words, based on the relationship between the reader and the access network device, the reader information can not only be information about the reader itself, such as an identifier or service area, to explicitly indicate these readers, but it can also be information about the access network device, to implicitly indicate these readers through the access network device's identifier or service area.

[0013] Furthermore, the information of the aforementioned reader is carried in the service-oriented message corresponding to the first network element. This could be a newly defined service-oriented message to decouple it from existing messages, allowing for more flexible information transmission. Alternatively, existing messages could be reused, with no specific restrictions.

[0014] Optionally, the first network element pre-configures a correspondence between X access and mobility management network elements and M readers, where X and M are integers greater than or equal to 1. The X access and mobility management network elements include K access and mobility management network elements, and the M readers include N readers. This correspondence includes the correspondence between the N readers and the K access and mobility management network elements. It can be seen that compared to the above method of dynamically establishing the correspondence by reporting reader information, this saves communication overhead.

[0015] Optionally, determining the K access and mobility management network elements corresponding to the N readers includes: determining the K access and mobility management network elements corresponding to the N readers based on the identifiers of the N readers. For example, the identifier of the reader contains information about the access and mobility management network element corresponding to the reader. That is, constructing the access and mobility management network element information in the identifier of the reader can implicitly indicate that the reader corresponds to the access and mobility management network element, and can avoid the overhead caused by the pre-configuration or dynamic establishment of the above-mentioned correspondence in the first network element.

[0016] Optionally, the first network element is pre-configured with identifiers for N readers.

[0017] Furthermore, the reader's identifier also includes information about the access network device. The reader is connected to the access network device, or the access network device contains the reader, so that the access and mobility management network element can find the corresponding access network device based on the reader's identifier. This eliminates the need for the access and mobility management network element to pre-configure or dynamically establish the correspondence between the reader and the access network device, thereby reducing the overhead of the access and mobility management network element.

[0018] Optionally, the second message is a service-oriented message corresponding to the first access and mobility management network element. For example, it can be a newly defined service-oriented message to achieve decoupling from existing messages and make information transmission more flexible, or it can reuse existing messages. There are no specific restrictions.

[0019] In one possible design, the method further includes: receiving a response to a first operation sent by a first access and mobility management network element to indicate whether the first operation was successful or failed, so as to avoid subsequent process errors due to not knowing the execution status of the first operation, such as the first operation being successful but being re-executed, or the first operation failing but not being re-executed.

[0020] In one possible design, the first service is any of the following: inventory management, read service, write service, or deactivation service, that is, the service that enables AIoT can be executed by the applicable reader.

[0021] In one possible design, the first network element is the Environmental Internet of Things (AIoTF) function, or there may be other names, without limitation.

[0022] Secondly, a communication method is provided, applied to a first access and mobility management network element. The method includes: receiving first information from an access network device, determining a first network element corresponding to at least one reader, and sending information about the at least one reader to the first network element. The first information includes information about at least one reader, wherein the at least one reader is a reader associated with the access network device.

[0023] Therefore, when the first access and mobility management network element obtains information about at least one reader, it can correctly route the information of at least one reader to the corresponding network element, such as the first network element corresponding to at least one reader. This allows the first network element to determine that the first access and mobility management network element corresponds to at least one reader, which can then be used for subsequent service execution. For details, please refer to the relevant technical effects of the first aspect mentioned above, which will not be elaborated further.

[0024] In one possible design, the first information further includes information about a first network element. Determining the first network element corresponding to at least one reader includes: determining the first network element corresponding to at least one reader based on the information about at least one reader and the information about the first network element contained in the first information.

[0025] or;

[0026] In another possible design, determining the first network element corresponding to at least one reader includes: sending a network function discovery request to the network repository function; and receiving information about the first network element corresponding to at least one reader sent by the network repository function according to the network function discovery request.

[0027] This demonstrates that access network devices can proactively report information about the first network element. Alternatively, the first access and mobility management network elements can also obtain information about the first network element through network function discovery. In other words, regardless of the method, the first access and mobility management network elements can identify the first network element, preventing subsequent service information from being routed from the first network element to the corresponding reader due to the first access and mobility management network elements' inability to identify the first network element.

[0028] Optionally, the network function discovery request includes information indicating that the network function type is an Internet of Things (IoT) function and / or service area information, wherein the network function type of the first network element is an IoT function, and the service area indicated by the service area information includes the service area of ​​at least one reader, so that the network warehousing function can discover the first network element corresponding to at least one reader.

[0029] Optionally, the first access and mobility management network element pre-configures the information of the first network element, which can avoid the communication overhead caused by the access network device reporting or the first access and mobility management network element performing network function discovery.

[0030] Optionally, sending first information to the first network element includes: sending at least one reader's information to the first network element based on the information of the first network element, so as to avoid information transmission errors, such as sending to other network elements and causing communication redundancy.

[0031] In one possible design, the first information further includes instruction information, which instructs the sending of reader information to the first network element. Sending at least one reader information to the first network element includes: sending at least one reader information to the first network element according to the instruction information.

[0032] In other words, if the first access and mobility management network element (AMI) has not been enhanced / upgraded, it may not know how to process the reader's information. Therefore, its processing logic can be enhanced by sending additional indication information to enable the AMI to send the reader's information to the AMI. Of course, the indication information can also be implicit, such as the first information carrying information about the first AMI, which implicitly indicates that the reader's information should be sent to that AMI.

[0033] In one possible design, the information of the reader includes at least one of the following: the reader's identifier, information indicating the reader's service area, the identifier of the access network device, or information indicating the service area of ​​the access network device.

[0034] In one possible design, the method further includes: receiving a second message from a first network element, determining at least one access network device associated with a reader, and sending a third message to the access network device, the third message indicating the execution of a first service. The second message indicates a first operation related to the first service, and the second message includes information indicating at least one reader for executing the first service.

[0035] Optionally, the second message is a service-oriented message corresponding to the first access and mobility management network element.

[0036] Optionally, the information indicating at least one reader includes the identifier of at least one reader. Determining the access network device associated with at least one reader includes: determining the access network device associated with at least one reader based on the identifier of at least one reader. For example, the identifier of the reader contains information about the access network device. That is, constructing the access network device information in the identifier of the reader can implicitly indicate the association between the reader and the access network device, avoiding the overhead of pre-configuring or dynamically establishing the association between the reader and the access network device in the first access and mobility management network elements.

[0037] Optionally, the reader's identifier may also include information about the first access and mobility management network element.

[0038] Optionally, the method further includes: receiving a fourth message sent by the access network device, and sending a response to the first operation to the first network element. The fourth message includes a response to the first operation.

[0039] Optionally, the third message also includes information about the first network element and sends a response to the first operation to the first network element, including: sending a response to the first operation to the first network element based on the information about the first network element contained in the fourth message, i.e., performing routing, without the need for additional processing operations, which can reduce the overhead of the first access and mobility management network element.

[0040] In one possible design, at least one reader is connected to an access network device, or the access network device contains at least one reader.

[0041] In one possible design, the first network element is the Environmental Internet of Things (AIoTF).

[0042] In one possible design, the information of the first network element includes one or more of the following: identifier, address, domain name information, or port number, or any other information that can be used to indicate the first network element, without any specific limitation.

[0043] In one possible design, the first business is any of the following: inventory management, read operation, write operation, or deactivation operation.

[0044] It is understood that other technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0045] Thirdly, a communication method is provided, applied to an access network device. The method includes: acquiring first information and sending the first information to a first access and mobility management network element. The first information includes information about at least one reader, wherein the at least one reader is a reader associated with the access network device, and the first access and mobility management network element is connected to the at least one reader.

[0046] In one possible design, the reader information includes at least one of the following: a reader identifier, information indicating the reader's service area, an access network device identifier, or information indicating the access network device's service area.

[0047] Optionally, the reader's identifier includes at least one of the following: information about the access and mobility management function corresponding to the reader, information about the access network device associated with the reader, or information about the first network element corresponding to the reader.

[0048] In one possible design, the first information also includes information about at least one first network element corresponding to a reader.

[0049] In one possible design, the method further includes: receiving a third message from a first access and mobility management network element; executing a first service through at least one reader based on the third message; and sending a fourth message to the first access and mobility management network element; the third message requests the execution of the first service, and the fourth message includes a response to the first operation.

[0050] In one possible design, the first business is any of the following: inventory management, read operation, write operation, or deactivation operation.

[0051] Optionally, if the third message includes information about the first network element, then the fourth message also includes information about the first network element.

[0052] In one possible design, the information of the first network element includes one or more of the following: identifier, address, domain name information, or port number.

[0053] In one possible design, the first network element is the Environmental Internet of Things (AIoTF).

[0054] In one possible design, at least one reader is connected to an access network device, or the access network device contains at least one reader.

[0055] It is understandable that the technical effects of the method described in the third aspect can also refer to the relevant introductions of the methods described in the first and second aspects above, and will not be repeated here.

[0056] Fourthly, a communication device is provided. This communication device is used to execute the communication method described in any implementation of any one of the first to third aspects.

[0057] In this application, the communication device described in the fourth aspect can be a network device, a chip (system) or other component or assembly, or a device containing a network device. The aforementioned chip (system) or other component or assembly can all be disposed within the network device.

[0058] It should be understood that the communication apparatus described in the fourth aspect includes modules, units, or means that implement the communication method described in any one of the first to third aspects above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication method.

[0059] Fifthly, a communication device is provided. The communication device includes a processor configured to execute the communication method described in any possible implementation of any of the first to third aspects.

[0060] In one possible design, the communication device described in the fifth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.

[0061] In one possible design, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the communication method described in any of the first to third aspects.

[0062] In this application, the communication device described in the fifth aspect can be a network device, a chip (system) or other component or assembly, or a device containing a network device. The aforementioned chip (system) or other component or assembly can all be disposed within the network device.

[0063] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory, such that the communication device performs the communication method described in any possible implementation of any of the first to third aspects.

[0064] In one possible design, the communication device described in the sixth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the sixth aspect and other communication devices.

[0065] In this application, the communication device described in the sixth aspect can be a network device, a chip (system) or other component or assembly, or a device containing a network device. The aforementioned chip (system) or other component or assembly can all be disposed within the network device.

[0066] A seventh aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the implementations of the first to third aspects.

[0067] In one possible design, the communication device described in the seventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.

[0068] In this application, the communication device described in the seventh aspect can be a network device, a chip (system) or other component or assembly, or a device containing a network device. The aforementioned chip (system) or other component or assembly can all be disposed within the network device.

[0069] Eighthly, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading a computer program from the memory, to execute a communication method as described in any implementation of any one of the first to third aspects.

[0070] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0071] In this application, the communication device described in the eighth aspect can be a network device, a chip (system) or other component or assembly, or a device containing a network device. The aforementioned chip (system) or other component or assembly can all be disposed within the network device.

[0072] A ninth aspect provides a processor. The processor is configured to execute the communication method described in any possible implementation of any of the first to third aspects.

[0073] A tenth aspect provides a communication system. The communication system includes at least one of the following: a first network element for performing the method described in the first aspect, a first access and mobility management network element for performing the method described in the second aspect, or an access network device for performing the method described in the third aspect.

[0074] Eleventhly, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, causing the computer to perform the communication method described in any possible implementation of any one of the first to third aspects.

[0075] In a twelfth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any possible implementation of any of the first to third aspects. Attached Figure Description

[0076] Figure 1 is a schematic diagram of the AIoT architecture;

[0077] Figure 2 is a schematic diagram of the AIoT process.

[0078] Figure 3 is a schematic diagram of the AIoT process (II).

[0079] Figure 4 is a schematic diagram of the AIoT architecture (II).

[0080] Figure 5 is a schematic diagram of the architecture of a communication system provided in this application;

[0081] Figure 6 is a flowchart illustrating a communication method provided in this application;

[0082] Figure 7 is a schematic flowchart of a communication method provided in this application (II).

[0083] Figure 8 is a flowchart illustrating one of the communication methods provided in this application;

[0084] Figure 9 is a flowchart illustrating a communication method provided in this application.

[0085] Figure 10 is a schematic diagram of the structure of a communication device provided in this application;

[0086] Figure 11 is a schematic diagram of the structure of a communication device provided in this application. Detailed Implementation

[0087] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0088] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0089] 1. Ambient IoT (A-IoT):

[0090] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined A-IoT. A-IoT is also known as ambient power-enabled IoT or passive IoT (P-IoT). A-IoT can be applied to a variety of valuable scenarios.

[0091] For example, in warehousing / transportation / materials: by embedding or attaching passive or semi-passive IoT tags to goods stored in warehouses, shopping malls, etc., the relevant information of the goods is automatically collected by the reader during the logistics process. Managers can quickly query the information of the goods in the system, reducing the risk of loss or theft, improving the speed of goods handover, increasing accuracy, and preventing cross-selling and counterfeiting.

[0092] For example, 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 remind the administrator to handle the relevant situation.

[0093] Figure 1 is a schematic diagram of the A-IoT architecture. As shown in Figure 1, the architecture may include: a server, an ambient IoT function (AIoTF), a reader, and A-IoT devices, or terminals that support A-IoT.

[0094] The server can be an application function (AF), an application server (AS), or an environmental IoT / passive IoT application function (A-IoT / P-IoT AF), etc., and there are no restrictions on the specific name.

[0095] AIoTMF can process service requests from service requesters (AFs) and execute corresponding service operations (such as instructing the reader to perform inventory procedures for AIoT terminals) and transmit instructions (such as read operations, write operations, and deactivation operations). AIoTMF can also manage IoT devices and perform security authentication processes.

[0096] A-IoT devices can be categorized into three types: Device A (also known as Device 1), Device B (also known as Device 2), or Device C (also known as Device 3). Device A or Device 1a can be understood as similar to passive A-IoT devices. Passive A-IoT devices can be in the form of tags or any other terminal form, without restriction. Device B or Device 1b can be understood as similar to semi-passive A-IoT devices. Semi-passive A-IoT devices can obtain energy through solar, radio frequency, wind, hydro, or tidal power, without restriction on the energy acquisition method. These nodes do not have their own power supply devices such as batteries, but obtain energy from the environment to support data sensing, transmission, and distributed computing. Device C or Device 1c can be understood as similar to active A-IoT devices. For ease of understanding, A-IoT devices and tags can be used interchangeably in terms of terminology. Alternatively, A-IoT devices can also be considered as A-IoT terminals or tags, etc.

[0097] A reader can be an access network (RAN) device, such as a base station, pole station, micro base station, or macro station, or it can be a terminal device, such as a mobile phone, IoT device, or handheld reader. Readers can conduct contactless two-way data communication via radio frequency (RF) to read and write tags, thereby achieving target identification and data exchange. For example, for passive tags, when they enter the effective identification range of the reader, they can receive the RF signal emitted by the reader and transmit the information stored in the chip using the energy obtained from the induced current. Alternatively, for semi-passive or active tags, they can actively transmit signals at a specific frequency. The reader receives and decodes the information and sends it to the central information system for relevant data processing. Furthermore, a reader can also be called a reader-writer.

[0098] Specifically, when a server (or service requester, such as an application function (AF) or application server (AS)) operates on a tag, it can send operation instructions through the core network (CN). These instructions can include, but are not limited to: obtaining tag information, inventory operations (or storage operations), read operations, write operations, expiration operations, and interacting with the tag. Operation instructions may include area location information, tag identification information, etc. The reader sends an access instruction to the tag. After a tag successfully connects randomly, the reader sends instructions to the tag, such as forwarding the aforementioned operation instructions. The tag obtains or sends corresponding information according to the instructions. For example, when the operation instruction is an inventory instruction or an inventory operation, the tag sends its identification information; when the operation instruction is a read instruction or a read operation, the tag sends the data information stored in its storage area; when the operation instruction is a write instruction or a write operation, the tag stores the data information to be written to the tag, included in the operation instruction, in its storage area. The reader then sends (or forwards) the information sent by the tag to the core network, which in turn sends it to the server.

[0099] It should be understood that the server can send operation commands via the control plane channel. For example, the AF / AS / A-IoT / P-IoT AF sends operation commands to the AIoTF (or ambient IoT management function, AIoTMF), which then sends the operation commands to the reader via the access and mobility management function (AMF). Alternatively, the A-IoT / P-IoT AF sends operation commands to the AIoTMF via network function elements, which then send them to the reader. These network function elements can include, but are not limited to, network exposure functions (NEF), session management functions (SMF), policy control functions (PCF), user plane functions (UPF), unified data management (UDM), and network slice-specific and SNPN authentication and authorization functions (NSSAAF). Alternatively, the server can also send operation commands via the user plane channel. For example, the server sends the operation command to the reader via UPF. If the reader is a terminal device, the server also sends the operation command to the RAN device via the user plane device first, and the RAN device forwards it to the reader.

[0100] The server or the requesting party can perform different operations on the A-IoT device. The following are some common business operations.

[0101] Inventory processing, or taking stock of existing A-IoT devices, can also be understood as acquiring the identifiers of A-IoT devices. Each A-IoT device has a unique identifier. These identifiers can be assigned by the enterprise (i.e., written into the A-IoT device when it's printed) or by the operator. In one possible implementation, the A-IoT device identifier can be a globally unique code, such as an electronic product code (EPC), or it can be a temporary identifier or a non-globally unique identifier. During the inventory process, the server can issue inventory instructions. Typically, these instructions include information such as the A-IoT device identifier range, reader identifier, and location information. Upon receiving the inventory instruction, the reader will perform an inventory check on the A-IoT devices according to the instructions and send the A-IoT device identifiers to the server. Alternatively, the server can send the inventory instruction, and the reader can transmit the instruction transparently to the A-IoT devices. The A-IoT device recognizes the inventory operation based on the content of the inventory instruction. The A-IoT device sends its identifier to the reader, and the reader sends the identifier to the server; alternatively, the A-IoT device sends its identifier to the core network through the reader, and the core network then sends the identifier to the server.

[0102] A read operation involves reading data from an A-IoT device. A-IoT devices can have storage capabilities, and their storage areas can store data. If a server wants to perform a read operation on an A-IoT device, it sends a read command. The reader or core network then performs the read operation according to the command, retrieving data from the A-IoT device's storage area and sending the data back to the server. A write operation involves writing data to an A-IoT device. The server can send a write command, and the reader or core network then performs a write operation according to the command, writing data into the A-IoT device's storage area.

[0103] The deactivation operation can disable or deactivate an A-IoT device. The server can send a deactivation command, which may include the A-IoT device identifier (i.e., the identifier of the A-IoT device to be deactivated or disabled). The reader or core network performs the deactivation operation on the A-IoT device according to the command. After the operation is completed, the A-IoT device will be disabled or deactivated and cannot be inventoried or subjected to other operations.

[0104] Obtaining A-IoT device information can be understood as a higher-level description of the various operations mentioned above (such as a higher-level description of inventory and read operations). It does not distinguish whether the server is inventorying A-IoT devices or reading A-IoT device data. This operation will obtain A-IoT device information, which may be the identification information of the A-IoT device or the information stored in the A-IoT device's storage area.

[0105] The message interaction operation with A-IoT devices 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 A-IoT devices by exchanging information or messages and sends information from the A-IoT devices back to the server. This operation is primarily relevant when the reader does not examine the instruction content but only forwards messages from the server to the A-IoT devices and messages from the A-IoT devices to the server. Therefore, in this scenario, the operations performed by the reader on the A-IoT devices can be understood as message interaction operations with the A-IoT devices.

[0106] 2. A-IoT Operation Process:

[0107] As shown in Figure 2, one of its processes is as follows.

[0108] S200, the core network sends inventory messages to the reader.

[0109] Inventory messages contain instructions, such as read / write / storage instructions, without specific restrictions. The following text uses read instructions as an example; other instructions can be understood by referring to this example. Furthermore, inventory messages can contain inventory sessions, actions, masks, etc.

[0110] 1) The session and the subsequent flag are bound together. Each flag corresponds to a session. The disk storage session will specify which session's flag is set.

[0111] 2) The behavior specifies how to set the flag, such as the behavior indicator 1 or 0. If the mask matches after the A-IoT device receives it, it will set the flag corresponding to the session, such as A (action=1) or B (action=0).

[0112] 3) A mask can be understood as a prefix of the identifier of an A-IoT device. The mask is used to filter which A-IoT devices are selected. For example, if an A-IoT device stores a complete 96-bit identifier, the mask can indicate that A-IoT devices whose first 16 bits are 111…111 are selected.

[0113] After determining that an A-IoT service operation (such as a read / write / disk operation) needs to be performed, the core network can send a disk storage request message to the reader. In one possible implementation, the reader can send a disk storage response message to the core network, indicating that it has successfully received the disk storage request message and performs the service operation according to the disk storage request message.

[0114] S201, the reader sends a select message or a paging message.

[0115] Select messages or paging messages are used to select a group of A-IoT devices. Select messages or paging messages can contain the information in the inventory messages mentioned above.

[0116] When an A-IoT device receives a selection message, matching A-IoT devices set the selection message and corresponding flags. For example, if the session indication is S0 and the behavior indication is 0, and the mask matches, the A-IoT device sets the flag for session S0 to A (initial flag setting). Afterward, the device identifier (e.g., EPC) success flag will be flipped to B. Thus, A represents A-IoT devices that haven't yet transmitted EPC, and B represents A-IoT devices that have successfully transmitted. If the mask matches, the A-IoT device can further set flags according to the session indication and then listen for subsequent paging messages (queries).

[0117] S202, the reader sends a query message or a query duplicate message (queryRep).

[0118] Query messages can carry Q-values, session information, or flags.

[0119] Suppose that the session carried in the query message is S0 and the flag bit is A. The session and flag bit of the A-IoT device are matched with it, so a random number between 0 and 2^Q-1 is randomly generated according to Q as the initial value of the counter.

[0120] Querying duplicate messages does not require carrying content, has no Q value or session, and can be sent multiple times.

[0121] If no A-IoT device sends a response, such as RN16, the reader continues to send duplicate query messages. If an A-IoT device receives a duplicate query message, it decrements the counter value by 1, e.g., Counter = Counter - 1.

[0122] S203, A-IoT device sends RN16.

[0123] If the count value generated by the A-IoT device is 0, the A-IoT device will respond with RN16; otherwise, it will not respond. RN16 is a 16-bit random number (or it could be 16 bits or 8 bits) used for contention resolution. For example, after the A-IoT device receives (potentially multiple) duplicate query messages, its count value decreases to 0, and the A-IoT device will respond with RN16; otherwise, it will not respond. For example, each duplicate query message corresponds to the start or end of an access time slot. Each duplicate query message received by the A-IoT device signifies the end of the previous time slot and the start of the next time slot. The A-IoT device can randomly select an access time slot to initiate access, send uplink data (EPC), or receive downlink data.

[0124] S204, the reader returns an acknowledgment message (ACK).

[0125] When the reader receives an RN16 from an A-IoT device, if there is no collision (e.g., only one A-IoT device's RN16 is received), it sends an ACK, which includes the received RN16 and indicates that the contention has been successfully resolved.

[0126] S205, A-IoT devices send device ID.

[0127] If an A-IoT device receives an ACK and its RN16 matches, it will send back the device identifier; otherwise, it will not. In one possible implementation, the device identifier can be carried in an uplink (UL) non-access-stratum (NAS) message. The UL NAS message can also carry data, such as data read according to a read command.

[0128] S206, the reader sends a query duplicate message (queryRep).

[0129] If an A-IoT device sends its device identifier and receives a duplicate query message, it indicates successful transmission and flips the flag bit to B. For example, the flag bit can be used to prevent an A-IoT device that has already been stored from being stored again. If a subsequent paging message carries the flag bit A, and the A-IoT device's flag bit is flipped to B, it will not respond.

[0130] S207, the reader sends an inventory response message to the core network (if the reader did not send an inventory response message in step S200), or sends an inventory report (if the reader has sent an inventory response message in step S200). The inventory response message or inventory report message can be an N2 message.

[0131] The N2 message includes the aforementioned UL NAS message. Furthermore, the execution order of S206 and S207 is not limited. In one possible implementation, if the interface between the reader and the core network is not a Next Generation Application Protocol (NGAP) interface, the N2 message can be replaced with other message types, i.e., messages corresponding to the interface between the reader and the core network, such as AIoT NGAP. This application does not impose any limitations.

[0132] As can be seen from the process shown in Figure 2 above, the A-IoT device only needs to report the device identifier and / or the data to be read together through a single UL NAS message, without any subsequent signaling interaction. Therefore, when the reader receives the UL NAS message from the A-IoT device, it can continue to trigger the random access process of other A-IoT devices, such as continuing to broadcast paging messages or repeating queries, without waiting for other instructions from the core network elements.

[0133] As shown in Figure 3, taking the A-IoT terminal as an example of an A-IoT device, another process is as follows.

[0134] In S300, the core network sends inventory messages to the reader.

[0135] Inventory messages can contain inventory sessions, actions, or masks. Unlike S200 described above, inventory messages do not carry instructions.

[0136] S301, the reader sends a selection message or a paging message.

[0137] S302, the reader sends a query message or queries for duplicate messages.

[0138] S303, A-IoT devices send RN16.

[0139] S304, the reader returns ACK.

[0140] S305, A-IoT devices send device identifiers.

[0141] The device identifier is carried in the UL NAS message.

[0142] In one possible implementation, the device identifier is carried in the UL NAS message, but unlike S206 above, the UL NAS message in S306 does not carry data.

[0143] S306, the reader sends a duplicate query message.

[0144] S307, the reader sends an N2 message to the core network.

[0145] The N2 message includes the UL NAS message in S306. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced with other message types, i.e., messages corresponding to the interface between the reader and the core network, such as AIoT NGAP. This application does not impose any limitations.

[0146] It is understandable that the relevant introductions of S200-S207 can be referred to for S300-S308, and will not be repeated here.

[0147] At this point, the random connection of A-IoT devices is complete.

[0148] S308, the core network sends instructions to the reader.

[0149] In one possible implementation, the core network sends downlink (DL) NAS messages to the reader.

[0150] DL NAS messages carry instructions, such as read instructions.

[0151] S309, the reader sends instructions to the A-IoT device.

[0152] This instruction can be a read instruction.

[0153] In one possible implementation, the reader sends a DL NAS message from the core network to the A-IoT device, and the DL NAS message includes instructions.

[0154] S310, A-IoT devices send data to the reader.

[0155] This data is read according to a read command. In one possible implementation, this data is carried in a UL NAS message.

[0156] S311, the reader sends an N2 message to the core network.

[0157] The N2 message in S311 includes the UL NAS message in S310. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced with another message type, i.e., a message corresponding to the interface between the reader and the core network, such as an AIoT NGAP message. This application does not impose any limitations.

[0158] S312, the core network sends an inventory message to the reader.

[0159] Among them, the inventory message in S312 can carry an instruction to continue inventory.

[0160] Thus, compared to the process shown in Figure 2, the process shown in Figure 3 differs in that the device identifier (such as EPC) and data transmission are decoupled. The A-IoT device reports information through multiple messages. For example, after the A-IoT device receives the ACK sent by the reader, the A-IoT device first sends the EPC, which is then forwarded to the core network by the reader. Afterward, once the core network determines that the A-IoT device is the one requiring a read operation, it sends a read command to the A-IoT device through the reader. The A-IoT device then sends the data to be read to the core network element through the reader. Because the A-IoT device and the core network need to interact at least twice during this process, the reader cannot determine whether it can continue to inventory other A-IoT devices after receiving the first uplink message from the A-IoT device, such as a user plane (UP) NAS message carrying EPC, thus triggering the random access procedure for other A-IoT devices. Therefore, in this process, the reader needs to receive an instruction from the core network element to continue executing the inventory instruction information, i.e., S312, before it can continue to trigger the random access procedure for other A-IoT devices, such as continuing to broadcast query messages or repeating queries.

[0161] 3. A-IoT Architecture:

[0162] Please refer to Figure 4, where (a) illustrates a direct-connect architecture for A-IoT. Specifically, network functions with IoT capabilities in the core network, such as AIoTF, can have direct connection interfaces with base stations that have reader capabilities, enabling direct communication. A base station with reader capabilities, which can be called an AIoT RAN or other designations, contains one or more readers, which can be referred to as a base station reader. This architecture enables rapid commercial deployment in campus-wide scenarios, without requiring co-deployment with network elements from other existing large networks (such as public land mobile networks, PLMNs).

[0163] Please refer to Figure 4, where (b) illustrates a non-directly connected architecture for A-IoT. Specifically, the AIoTF and AIoT RAN are not directly connected; instead, the AIoTF communicates with the AIoT RAN through the AMF. That is, the AIoT RAN and AMF are directly connected, while the AIoTF communicates with the AMF through a service-oriented interface. Under this architecture, the AIoT RAN still reuses the existing NGAP interface to communicate with the AMF, reducing network modifications. This architecture is also suitable for wide-area scenarios, allowing a small number of AIoTFs to be deployed in operator networks to perform AIoT services.

[0164] As can be seen, in a direct-connection A-IoT network architecture, the AIoTF receives service requests sent by the AF through the NEF. This service request includes the service (AIoT service) operation to be performed, and optionally, may also include the area information corresponding to the service operation, and / or the range of the A-IoT devices used to perform the service operation. Based on the service request, the AIoTF instructs the reader to perform the service operation. No AMF is involved in this process. Therefore, when the network architecture is a non-direct-connection A-IoT architecture, it is necessary to design the service process so that the AIoTF function can use the same service processing logic when facing two different architectures, reducing development costs. Otherwise, differences in AIoTF functionality under the two architectures will occur, leading to incompatibility between the process design scheme and different deployment architectures. Among these, how to achieve correct transmission of service data under a non-direct-connection architecture is a current research problem.

[0165] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0166] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0167] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0168] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0169] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

[0170] As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In specific implementation, the required indication method can be selected according to specific needs. This application embodiment does not limit the selection of the indication method. Therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to know the information to be indicated.

[0171] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, a MAC control element (CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0172] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different indication information.

[0173] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0174] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0175] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0176] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0177] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG5 as an example. For example, FIG5 is a schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application applies.

[0178] Figure 5 is a schematic diagram of the architecture of the communication system, which mainly includes: the first network element, the access network equipment, and the access and mobility management network element.

[0179] The first network element can be a core network element, such as a core network element whose name can be an IoT function, with no specific name limitation. For example, an IoT function can be an ambient IoT function (AIoTF), an ambient IoT management function (AIoTMF), an IoT device management function (IDMF), an IoT management function (IoTMF), a tag management function (TMF), or an ambient IoT device management function (AIDMF). This application does not limit the naming of the network element performing the IoT function; it can have other names. This application uses AIoTF as an abbreviation for the IoT function network element as an example. AIoTF can process service requests from service requesters (e.g., AF) and execute corresponding service operations (e.g., instructing the reader to perform an inventory process for IoT devices) and transmission instructions (e.g., read operations, write operations, deactivation operations, etc.). It manages IoT devices, performs security authentication processes, and transmits data.

[0180] Access network equipment, also known as radio access network (RAN) nodes, or network equipment with core network logical functions, can be 3GPP-related cellular systems, such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN nodes can also be open RAN (O-RAN or ORAN), cloud radio access network (CRAN), or wireless fidelity (WiFi) systems. RAN nodes can also be communication systems that integrate two or more of these systems. RAN nodes are sometimes also referred to as access network equipment, RAN entities, or access nodes, forming part of the communication system to help terminals achieve wireless access. Multiple RAN nodes in a communication system can be of the same type or different types.

[0181] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station, a micro base station or indoor station, a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions. The equipment form of the RAN node can be a pole station, micro base station, base station, small station, macro station, etc., and there are no specific restrictions.

[0182] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing some of the functions of the base station. For example, RAN nodes can be central units (CU), distributed units (DU), or radio units (RU), etc.

[0183] In some examples, the CU is a logical node carrying the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., PDCP layer and higher layers) connects to the DU (e.g., RLC layer and lower layers) through interfaces, which can be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., F1 interfaces) can provide control plane (C-plane) and user plane (U-plane) functions (e.g., interface management, system information management, user equipment (UE) context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0184] In some examples, the CU can be split into the CU control plane (CU-CP) and the CU user plane (CU-UP). The CU-CP is a logical node carrying the RRC layer and the PDCP control plane (PDCP-C) layer, used to implement the CU's control plane functions. The CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements, such as the AMF in a 5G system. The AMF is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. The CU-UP is a logical node carrying the SDAP layer and the PDCP user plane (PDCP-U) layer, used to implement the CU's user plane functions. The CU-UP can interact with network elements in the core network used to implement user plane functions.

[0185] The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0186] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the higher physical layer includes parts of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0187] In some examples, the RU (Remote Utility Unit) may be included in radio frequency (RF) equipment or units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). The RU is a logical node carrying both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU may be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar functionalities. In some examples, the Low-PHY includes PHY processing components such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0188] The DU and RU may or may not be co-located. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces, respectively providing the control plane (C-plane) and user plane (U-plane). In some examples, the control plane (C-plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface; the management plane (M-plane) refers to non-real-time management operations between the DU and RU.

[0189] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

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

[0191] In the ORAN system, RAN nodes communicate with the core network (CN) via backhaul links and with terminals via air interfaces. The ORAN system also includes RAN intelligent controllers (RICs), which can be further divided into non-real-time (Non-RT) RICs and near-real-time (Near-RT) RICs. Non-RT RICs are used for non-real-time intelligent management of RAN functions and are located within the Service Management and Orchestration Framework (SMO) module. Near-RT RICs are used for near-real-time intelligent management of the RAN, achieving near-real-time control and optimization of ORAN modules and resources through data collection and related operations on the E2 interface.

[0192] It is understood that in one possible implementation, the access network device in this application embodiment is also a device that supports AIoT functions, such as the AIoT-RAN mentioned above. The access network device may include a reader. In this case, the reader can also be called the base station reader mentioned above, that is, as part of the access network device, such as a component / entity / function / device that supports AIoT functions in the access network device, or it is the access network device itself. Alternatively, in another possible implementation, the access network device may also be connected to the reader, for example, the reader is deployed remotely and connected to the access network device through a backhaul link. In one example, the reader may be a pole station, eNodeB, gNodeB, integrated access and backhaul (IAB) node, RRU, AAU, RRH, etc.

[0193] Specifically, the reader interacts with A-IoT devices via radio frequency signals or wireless signals. It should be understood that this application does not limit the name of the reader; it can also be called a reader-writer or other names, meaning the terms "reader" and "writer" are interchangeable. The reader-writer here possesses the functions described in this application, such as the ability to perform the operations described in this application on the terminal (e.g., A-IoT device) (e.g., acquiring A-IoT device information, inventory operations, read operations, write operations, failure operations, or message interaction operations with the A-IoT device), the ability to acquire billing-related information and / or billing information, and the ability to send billing information to the charging function (CHF). In one possible implementation, the reader can send instructions from a server or application function to the A-IoT device, or the reader can send messages from the A-IoT device to a server or application function. In another possible implementation, the reader can acquire information stored in a specified A-IoT device based on instructions issued by the server. For example, in the case of an inventory operation (or storage operation), the reader obtains the identification information of the A-IoT device; this identification information can be a unique identifier for the A-IoT device or a temporary identifier. In the case of a read operation, the reader reads the data from the A-IoT device's storage area. Optionally, in situations where it is necessary to rewrite the information stored within the A-IoT device, the reader can also have a write function; for example, in the case of a write operation, the reader writes the data to the A-IoT device's storage area. In addition, the reader can also perform a failure operation on the A-IoT device. After a failure operation is performed, the A-IoT device becomes invalid and cannot be used for operations such as obtaining A-IoT device information, inventory operations, read operations, message interaction operations with the A-IoT device, or write operations. In one possible implementation, the inability to obtain A-IoT device information after a device failure can be understood as the reader being unable to obtain the A-IoT device information of the failed A-IoT device. In another possible implementation, the inability to perform message interaction operations with the A-IoT device due to its failure can be understood as the reader being unable to interact with the failed A-IoT device after the device fails. In this application, the reader can also be a terminal device; this application does not limit the form of the reader.

[0194] The access and mobility management network element can also be referred to as an access and mobility management device, an access and mobility management function entity, an access and mobility management function network element, a mobility management device, a mobility management network element, or a mobility management entity. This device can be used to manage the access control and mobility of the user equipment. In practical applications, it includes the access and mobility management functions 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 communication systems, the access and mobility management network element can still be an AMF, or it can have other names; this application does not limit this. When the access and mobility management network element is an AMF, the AMF can provide Namf services. Alternatively, the access and mobility management network element can be implemented in other ways. For example, in a distributed subnet architecture, the access and mobility management network element can include multiple entities / network elements, such as the non-access-stratum (NAS) management function (NMF) responsible for some functions of access control (NM for short) and the mobility management function (MMF) responsible for some functions of mobility management (MM for short).

[0195] In this communication system, upon receiving a request for a first service, the first network element can determine at least one reader capable of executing the first service and send a message to the first access and mobility management network element connected to the at least one reader, instructing the at least one reader to execute the first service. Correspondingly, the first access and mobility management network element can determine the access network device associated with the at least one reader and send an instruction to that access network device to trigger the at least one reader to perform an operation related to the first service, such as a first operation, i.e., enabling the operation to be performed by an applicable reader.

[0196] It should be understood that the communication method provided in this application embodiment can be applied to the device shown in FIG5. For specific implementation, please refer to the following method embodiment, which will not be repeated here. The solution in this application embodiment can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0197] It should also be understood that Figure 5 is a simplified schematic diagram for ease of understanding only, and the communication system may also include other network devices and / or other terminal devices, which are not shown in Figure 5.

[0198] The interaction process between devices in the above-described communication system will be specifically described below with reference to Figures 6-9 through method embodiments. The communication method provided in this application embodiment can be applied to the above-described communication system, such as the interaction between the first network element, the first access and mobility management network element, and access network devices, which will be described in detail below.

[0199] As shown in Figure 6, the flow of this communication method is as follows:

[0200] S601, the first network element receives the first message.

[0201] The first message can direct the first business.

[0202] The primary business can be A-IoT business, or any other possible business, without restriction.

[0203] For example, the first business can be a business related to the application scenario of A-IoT, such as including at least one of the following: inventory business, command business, positioning business, sensing business, proximity determination, reading business, writing business, deactivation business, locking business, or security business (such as authentication, certification, registration, etc.), or it can be a newly defined business type in the future, and there are no restrictions on the specific naming.

[0204] For example, the first service can also be a service related to the A-IoT process, such as including at least one of the following: access process, or data transmission process, etc., which can be understood as performing the first service being performing the corresponding process. The access process can be random access, such as contention-based random access or contention-free random access. Optionally, the access process may include reporting the device identifier of the A-IoT device. The data transmission process can be device (e.g., A-IoT device) - reader (device-to-reader, D2R) / uplink data transmission, reader-to-device (reader-to-device, R2D) / downlink data transmission, etc. Optionally, the data transmission process may also include reporting the device identifier. Optionally, the access process and the data transmission process are not strictly distinguished, and the two can be combined. For example, data transmission can also occur within the access process, such as contention-free random access, where the A-IoT device can send D2R / uplink data in the first message.

[0205] In one possible implementation, the first message may contain information corresponding to the first service. For example, the information corresponding to the first service may include at least one of the following: the type of the first service, the identifier of the first service, the data of the first service, or information for selecting a reader, which will be described below.

[0206] 1) The type of the first service can indicate the type of the first service, such as inventory service, command service, positioning service, sensing service, proximity determination, read service, write service, deactivation service, lock service, or security service (such as authentication, certification, registration, etc.), or it can be a newly defined service type in the future, and there are no restrictions on the specific naming.

[0207] 2) The identifier for the first service can be used to uniquely identify the first service, and the specific identifier type is not limited. In one possible implementation, the identifier for the first service can identify the type of the first service. In another possible implementation, the identifier for the first service can identify the service request, such as a service identifier (transaction ID) and / or application function identifier (AF ID).

[0208] 3) The data for the first service can be the data that needs to be sent to the A-IoT device. For example, for the write service, the data is the data to be written to the A-IoT device.

[0209] 4) The information used to select a reader may include information indicating the service area, signifying that the first service needs to be performed by a reader within that service area. The information indicating the service area can specify one or more areas, such as represented by geometric (geographical) location information, like province, city, district, or coordinate values, latitude and longitude ranges, etc., or it may be represented by topological (network) location information recognizable by network elements within the core network, such as data network access identifier (DNAI), track area identifier (TAI), TAI list, area identifier (ID), area ID list, reader identifier, reader identifier list, cell ID, or cell ID list, etc. The information used to select a reader may also include information indicating the range of A-IoT devices, such as at least one of the following for AIoT devices: device identifier, device identifier prefix, or device identifier range, etc.

[0210] The first message can be a business request message, such as an A-IoT business request (NAIoT_AIoTService) message, or other named messages, without any restrictions.

[0211] The first network element can receive the first message sent by the third network element through the second network element. For example, the second network element can be a network exposure function (NEF) network element, or other types / names of network elements, without restriction. The third network element can be an application function (AF) or an application server (AS), specifically it can be a third-party application function or application server, or it can be an application function or application server within the operator's network, without restriction. The message type of the first message received by the first network element from the second network element can be the same as or different from the message type of the first message received by the second network element from the third network element. That is, the second network element can transparently transmit the first message sent by the third network element to the first network element; or process the received first message (such as changing the message type) before sending it to the first network element.

[0212] S602, the first network element sends a second message to the first access and mobility management network element, and the first access and mobility management network element receives the second message from the first network element.

[0213] The second message can instruct the first action.

[0214] The first operation is related to the first service, such as operations required to complete the first service, like inventory operations, inventory and command transmission operations, or any other possible operations, without specific limitations. For example, the second message can contain a service request. If the first service is an inventory service, the service request can be an inventory request to indicate an inventory operation; the first operation includes the inventory operation. Another example is a command service, such as a read service. The service request can include an inventory request and a command indication. This command indication can indicate that the first service includes a command, such as a read command, or that after inventorying into the A-IoT device, there will be subsequent commands sent to the A-IoT device, such as read commands. In this case, the first operation includes the inventory operation, and it can also be considered that the first operation includes operations corresponding to subsequent commands, such as read operations. Of course, other cases, such as write services and deactivation services, are similar and can be understood with reference to this.

[0215] In addition, the service request may also include at least one of the following: an identifier or mask used to identify the service request.

[0216] The identifier used to identify the service request can be a task ID, transaction ID, AIoT session ID, event ID, etc., and there is no specific limitation. This application embodiment takes the task ID as an example. The identifier used to identify the service request can be assigned by the first network element, and there is no limitation on the specific assignment method.

[0217] A mask is information used to identify one or more A-IoT devices. The mask can be at least one of the following for an A-IoT device: device identifier, a prefix of the device identifier, a range of device identifiers, etc., used to filter which A-IoT devices are selected. For example, if the device identifier is a complete 96-bit identifier, the mask can indicate that A-IoT devices whose first 16 bits are 111…111 are selected. The mask can be determined by the first network element based on the information indicating the range of A-IoT devices. This can be done by using the information indicating the range of A-IoT devices as the mask, selecting a portion of the information (such as a portion of the device identifier range) as the mask, or allowing the first network element to determine it independently; the specific implementation is not limited.

[0218] The second message also includes information instructing at least one reader.

[0219] At least one reader is capable of performing the first service, such as within the aforementioned service area. At least one reader is capable of connecting to the first access and mobility management network element, or in other words, at least one reader is capable of being managed by the first access and mobility management network element.

[0220] For example, if at least one reader is connected to an access network device, or if the access network device contains at least one reader (i.e., the reader belongs to the access network device, that is, it is part of the access network device, such as the base station reader mentioned above, or the access network device is considered to be the at least one reader), and if there is a connection between the access network device and the first access and mobility management network element, then at least one reader can be considered to be a reader managed or connected to the first access and mobility management network element.

[0221] The information indicating at least one reader may include at least one identifier for each reader, such as a reader ID. In the case of a base station (BS) reader, the reader identifier may also be a BS reader ID, or any other information that can identify the reader, without any specific limitation.

[0222] Optionally, the reader's identifier may include at least one of the following: information about the access and mobility management function (AMAC) to which the reader corresponds (or is connected), information about the access network device associated with the reader (i.e., information about the access network device to which the reader is connected or belongs), or information about the first network element to which the reader corresponds, i.e., the above information is constructed into the reader's identifier. The access and mobility management network element information may indicate the access and mobility management network element, such as one or more of the following: the access and mobility management network element's identifier, Internet Protocol (IP) address, port number, fully qualified domain name (FQDN), etc. The access network device information indicates the access network device, such as one or more of the following: the access network device's identifier, IP address, port number, FQDN, etc. The first network element information may also indicate the first network element, such as one or more of the following: the first network element's identifier, IP address, port number, FQDN, etc. The first network element corresponding to at least one reader also means that at least one reader is connected to or managed by the first network element. The principle is similar to that of the first access and mobility management network element mentioned above. Please refer to it for understanding, and it will not be repeated here.

[0223] It is understandable that the service request needs to be sent from the first network element to the reader through the first access and mobility management network element. Therefore, the second message is mainly used to transmit messages or information sent by the first network element to the reader, such as service requests and / or information instructing at least one reader. In this case, the first access and mobility management network element may not be aware of / understand the meaning of the service-related messages or information carried in the second message and can simply perform routing, or it may be aware of / understand them without restriction.

[0224] In this embodiment of the application, the first network element can determine the first access and mobility management network element according to the first message. That is, the first network element can determine the corresponding access and mobility management network element according to the request of the first service, so as to achieve on-demand determination.

[0225] For example, the first network element can determine N readers suitable for performing the first service based on the first message, where N is an integer greater than or equal to 1, and the N readers include at least one of the aforementioned readers. In one possible implementation, the first network element can select a suitable reader based on the information for selecting readers in the first message, such as selecting a reader located within the service area. Alternatively, the first network element can also select the reader corresponding to the third network element based on pre-configured information, such as selecting a reader located within the area where the third-party application is allowed to perform service operations, i.e., selecting N readers. The area where the third-party application is allowed to perform service operations can be an area pre-negotiated between the third-party application and the operator's network, and the first network element can pre-configure information indicating this area.

[0226] The first network element can also determine the K access and mobility management network elements corresponding to the N readers, such as the access and mobility management network elements each of the N readers connects to, for a total of K access and mobility management network elements. K is an integer greater than or equal to 1, and the K access and mobility management network elements include the first access and mobility management network element. For example, taking the access and mobility management network element as AMF as an example, the N readers include reader #1, reader #2, reader #3, and reader #4. Reader #1 and reader #2 are connected to AMF #1, reader #2 and reader #3 are connected to AMF #2, and reader #4 is connected to AMF #3. The K access and mobility management network elements are AMF #1, AMF #2, and AMF #3. In other words, the first network can first determine the readers suitable for executing the first service, or all readers capable of executing the first service, and then determine the access and mobility management network elements corresponding to each of these readers, so as to ensure that the information of the first service can be routed to all readers capable of executing the first service through these access and mobility management network elements, and to ensure that the operation corresponding to the first service can be successfully executed.

[0227] In some possible implementations, the first network element can determine the K access and mobility management network elements corresponding to N readers based on the correspondence between access and mobility management network elements and readers (as described in Method 1 below), or it can determine the K access and mobility management network elements corresponding to N readers based on the reader's identifier (as described in Method 2 below). These will be described separately below.

[0228] Method 1:

[0229] The first network element can obtain the correspondence between the access and mobility management network elements and the reader in advance based on the information reported by the access and mobility management network elements. The specific process is shown in steps 1-6 below.

[0230] Step 1: Access network devices obtain the first information.

[0231] The first information can contain information from at least one reader.

[0232] For example, at least one reader is a reader associated with an access network device, meaning that the aforementioned access network device connects to or includes at least one of these readers. In at least one reader, the information of any reader may include at least one of the following: information indicating the reader, such as the reader's identifier (see above for details, which will not be repeated here), information indicating the reader's service area, information indicating the access network device, such as the access network device's identifier, or information indicating the access network device's service area, which will be described below.

[0233] The service area of ​​a reader can be its coverage area or at least a portion of the service area of ​​an access network device, such as at least one cell of the access network device. Accordingly, information indicating the reader's service area can be the identifier of that cell, such as a cell ID or a list of cell IDs, or the reader's location information (e.g., coordinates or latitude and longitude). The service area of ​​an access network device can be one of its cells. In this case, information indicating the access network device's service area can be the identifiers of those cells, such as cell IDs or a list of cell IDs. It should be understood that the service area of ​​an access network device can include the service area of ​​at least one reader. That is, based on the above relationship between the reader and the access network device, the reader's information can not only be information about the reader itself, such as its identifier or service area, to explicitly indicate these readers, but it can also be information about the access network device, to implicitly indicate these readers through the access network device's identifier or service area.

[0234] The access network device can obtain its own information from at least one reader, i.e., the information of at least one reader. Alternatively, the information of at least one reader can also be pre-configured locally on the access network device, and the access network device can obtain the information of at least one reader locally.

[0235] Optionally, the first information may also include information about at least one first network element corresponding to the reader, such as one or more of the first network element's identifier, IP address, port number, FQDN, etc. The information of the first network element can be pre-configured locally on the access network device, and the access network device can obtain the information of the first network element locally.

[0236] Optionally, the first information may further include indication information, which may indicate sending reader information to the first network element, or, since the network function type of the first network element is an IoT function, the indication information may indicate sending reader information to a network element with an IoT function. It is understood that the indication information may be an explicit information element, such as 1 bit, where 1 indicates sending reader information to a network element with an IoT function, and 0 indicates a null value. Alternatively, the indication information may be implicit, such as the first information carrying information about the first network element, i.e., indicating sending reader information to the first network element, or the first information carrying information in a newly defined container (e.g., an AIoT container), information element (e.g., AIoT reader information), or message (message name or type, e.g., an AIoT AP setup message) to indicate sending reader information to the first network element.

[0237] It should be understood that if an access network device obtains information from at least one reader, and optionally also obtains information from a first network element, then it can be considered that the access network device has obtained the first information.

[0238] Step 2: The access network device sends the first information to the first access and mobility management network element, and correspondingly, the first access and mobility management network element receives the first information from the access network device.

[0239] The first information can be carried in an existing message, such as an NGAP Setup message, that is, reusing an existing message to send the first information to the first access and mobility management network element. Alternatively, the first information can also be carried in a newly defined container, information element (IE), or message. In one example, the newly defined container can be an AIoT container, the newly defined information element can be an AIoT information element, and the newly defined message can be an AIoT request message, an AIoT capability report message, or an AIoT application protocol setup request message, etc. Alternatively, the newly defined container, information element, or message can also have other names. This application embodiment does not limit the names of the container, information element, or message.

[0240] Step 3: The first access and mobility management network element determines at least one first network element corresponding to the reader.

[0241] In one possible implementation, if the first information contains information about a first network element, then the first access and mobility management network element can determine that at least one reader corresponds to the first network element based on the information of at least one reader contained in the first information and the information of the first network element. Alternatively, if the identifier of the reader contains information about the first network element, then the first access and mobility management network element can also determine that at least one reader corresponds to the first network element based on the information of the first network element contained in the identifier of at least one reader.

[0242] In another possible implementation, the first access and mobility management network element can also find the first network element through network function discovery.

[0243] For example, if the first access and mobility management network element determines that it has not obtained information about a network element with a network function type of IoT from the information reported by the access network device, it can send a network function discovery request to a network repository function (such as an NRF), including information indicating that the network function type is IoT and / or service area information. The service area indicated by the service area information can include the service area of ​​at least one reader / access network device mentioned above, to discover the first network element corresponding to at least one reader. The network repository function can determine that the network function to be discovered is an IoT function based on the information indicating that the network function type is IoT, and select one or more IoT functions (including the first network element) based on the service area indicated by the service area information. In one example, when an IoT function registers a network function (NF) policy (NF profile) with the network repository function, it can report the area it serves. Therefore, the network repository function can select IoT functions whose service area includes the service area indicated by the service area information, and obtain the information of each of these IoT functions (i.e., information including the first network element). Taking the first network element as an example, the network repository function can send the information of the first network element to the first access and mobility management network element. The first access and mobility management network element receives the information of the first network element sent by the network repository function according to the network function discovery request, and determines that at least one reader corresponds to the first network element.

[0244] It is understandable that the network repository function, according to the protocol's pre-defined / pre-configured structure, provides the first access and mobility management network element's information by default. In this case, the network function discovery request may not carry service area information. For example, the network repository function can configure the mapping relationship between access and mobility management network elements and IoT functions, and discover the access and mobility management network element information (such as identifier, address, or FQDN) of the IoT function based on the request, thereby determining the IoT function corresponding to that access and mobility management network element.

[0245] This demonstrates that access network devices can proactively report information about the first network element. Alternatively, the first access and mobility management network elements can also obtain information about the first network element through network function discovery. In other words, regardless of the method, the first access and mobility management network elements can identify the first network element, preventing subsequent service information from being routed from the first network element to the corresponding reader due to the first access and mobility management network elements' inability to identify the first network element.

[0246] In another possible implementation, the first access and mobility management network element pre-configures its own information. For example, the first access and mobility management network element can pre-configure information about one or more IoT functions it is connected to (including information about the first network element). This avoids the communication overhead caused by access network devices reporting information or the first access and mobility management network element performing network function discovery. For ease of understanding, taking the first network element as an example, the first access and mobility management network element can determine at least one reader corresponding to the first network element based on the pre-configured information.

[0247] Step 4: The first access and mobility management network element sends information about at least one reader to the first network element.

[0248] The first access and mobility management network element (AMI) can send at least one reader's information to the first network element based on its own information to avoid information transmission errors, such as sending the information to other network elements and causing communication redundancy. Optionally, the first AMI can also send at least one reader's information to the first network element based on the aforementioned instruction information, such as sending at least one reader's information to the first network element based on the instruction information and the information of the first network element. That is, if the first AMI has not been enhanced / upgraded, it may not know how to process the reader's information. Therefore, it can enhance its processing logic by sending additional instruction information to enable it to send the reader's information to the first network element.

[0249] The reader information mentioned above can be carried in the service-oriented message corresponding to the first network element. That is, the first access and mobility management network element can send at least one reader information to the first network element through the service-oriented message (or service-oriented interface message). The service-oriented interface message can be a newly defined message that can be used to send reader information or update reader information, such as the Reader Capability Create / Update / Report message. In this embodiment, the name of the service-oriented interface message is not limited to achieve decoupling from existing messages, so that information transmission can be more flexible, or existing messages can be reused. There are no specific restrictions.

[0250] Step 5: The first network element receives information from M readers from X access and mobility management network elements.

[0251] Since steps 1-4 can be executed once or multiple times by different access network devices and access and mobility management network elements, the first network element can also receive information from M readers from at least one access and mobility management network element (such as X access and mobility management network elements), where X and M are integers greater than or equal to 1. That is, the X access and mobility management network elements include the aforementioned K access and mobility management network elements, and thus also include the aforementioned first access and mobility management network element. The M readers include the aforementioned N readers, and the information of the M readers also includes the information of the aforementioned N readers.

[0252] Step 6: The first network element obtains the correspondence between X access and mobility management network elements and M readers based on the information from M readers.

[0253] The aforementioned correspondence can include the correspondence between the N readers and the K access and mobility management network elements (AM elements). For example, when the first network element receives information about reader #1 and reader #2 from AMF#1, information about reader #2 and reader #3 from AMF#2, and information about reader #4 from AMF#1, the first network element determines that the correspondence includes reader #1, reader #2, and reader #4 corresponding to AMF#1, and reader #2 and reader #3 corresponding to AMF#2. In other words, the first network can dynamically establish the correspondence between AM elements and readers in advance to ensure that when determining which reader is suitable for performing the operation corresponding to the first service, the AM elements connected to these readers can be found based on this correspondence, thus achieving correct data routing. Furthermore, since the correspondence between AM elements and readers is dynamically established through information reported by AM elements, it can be dynamically updated according to the actual connection situation.

[0254] It should be understood that, according to steps 1-6 above, when the access and mobility management network element obtains the reader's information, it can correctly route the reader's information to the corresponding network element, such as the first network element, so that the first network element can obtain / update the above correspondence for use when performing services later.

[0255] Method 2:

[0256] The first network element can pre-configure the mapping relationship between access and mobility management network elements and readers, such as the mapping relationship between X access and mobility management network elements and M readers mentioned above. This mapping relationship includes the mapping relationship between N readers and K access and mobility management network elements. Therefore, compared to the method of dynamically establishing mapping relationships by reporting reader information, communication overhead can be saved.

[0257] Therefore, when the first network element determines N readers suitable for executing the first service, it can determine the K access and mobility management network elements corresponding to the N readers according to the correspondence in Method 1 or Method 2. It is understood that any one of the N readers typically does not correspond to multiple access and mobility management network elements among the K, to avoid signaling redundancy caused by sending the same reader's information to different access and mobility management network elements. For example, if readers #1, #2, and #4 correspond to AMF #1, and readers #2 and #3 correspond to AMF #2, and the N readers include readers #1, #2, and #3, then when determining the K access and mobility management network elements corresponding to the N readers, the first network element can choose to have reader #2 correspond to either AMF #1 or AMF #2, avoiding the situation where reader #2 corresponds to both AMF #1 and AMF #2 simultaneously.

[0258] Alternatively, if the reader's identifier contains information about the access and mobility management network element (AMI) corresponding to that reader, the first network element can also determine the K AMIs corresponding to the N readers based on the N reader identifiers. For example, when the first network element determines N readers suitable for performing the first service, it can obtain the identifiers of the N readers, such as obtaining the identifiers of pre-configured N readers locally or from other network elements (such as a third network element). For the identifier of any one of the N readers, the first network element can determine that the reader corresponds to that AMI based on the information about the AMI contained in the reader's identifier, ultimately determining the K AMIs corresponding to the N readers. In other words, constructing the AMI information in the reader's identifier implicitly indicates that the reader corresponds to that AMI, avoiding the overhead of the first network element pre-configuring or dynamically establishing the above-mentioned correspondence. Of course, in this case, any one of the N readers usually does not correspond to multiple access and mobility management network elements among the K access and mobility management network elements. For details, please refer to the above introduction, which will not be repeated here.

[0259] Subsequently, for any one of the K access and mobility management network elements, the first network element performs operations similar to those of the first access and mobility management network element. Taking the first access and mobility management network element as an example, the first network element sends a second message to the first access and mobility management network element. This second message can be a service-oriented message corresponding to the first access and mobility management network element, such as a newly defined service-oriented message (or service-oriented interface message). This service-oriented message can be a non-terminal granular message, such as a network element granular message, for example, an AIoT message transmission (Namf_AIoTmessageTransfer) message, or any other possible naming, to achieve decoupling from existing messages, making information transmission more flexible, or existing messages can be reused, without any specific restrictions.

[0260] In summary, upon receiving a request for the first service, such as a first message, the first network element can determine at least one reader capable of performing the first service and send a second message to the first access and mobility management network element connected to the at least one reader, instructing the at least one reader to perform an operation related to the first service, such as a first operation, i.e., to enable the operation to be performed by the applicable reader.

[0261] Optionally, in conjunction with the above S601-S602, the method may further include:

[0262] S603, the first access and mobility management network element identifies at least one access network device associated with the reader.

[0263] Since the second message can carry the aforementioned information indicating at least one reader, and this information can include the identifier of at least one reader, the first access and mobility management network element can determine the at least one reader associated access network device based on the identifier of at least one reader.

[0264] For example, the first access and mobility management network element can determine at least one access network device associated with a reader based on the association relationship between the reader and the access network device. This association relationship can be determined through the information sent by the access network device in step 3 above. For instance, if the first information sent by the access network device contains information about at least one reader, the first access and mobility management network element determines that the at least one reader is associated with the access network device that sent the first information, such as by obtaining the association relationship between the identifier of the at least one reader and the identifier of the access network device; or the association relationship can be pre-configured by the first access and mobility management network element or predefined by the protocol. In this way, the first access and mobility management network element can use the identifier of at least one reader carried in the second message to traverse this association relationship, thereby determining the access network device associated with at least one reader.

[0265] For example, if the reader's identifier contains information about the access network device associated with that reader, the first access and mobility management network element can also determine at least one access network device associated with the reader based on the access network device information contained in the identifier of at least one reader. This eliminates the need for the access and mobility management network element to pre-configure or dynamically establish a correspondence between readers and access network devices, reducing overhead. It can be understood that if the access network device information is the identifier of the access network device, the first access and mobility management network element can directly determine the access network device based on this information. If the access network device information is not an identifier, but other intermediate information, the first access and mobility management network element can pre-configure the correspondence between this intermediate information and the identifier of the access network device, and then determine at least one access network device associated with the reader based on this correspondence. In other words, constructing the access network device information in the reader's identifier implicitly indicates the association between the reader and the access network device, avoiding the overhead caused by the first access and mobility management network element pre-configuring or dynamically establishing the association between the reader and the access network device.

[0266] Optionally, the first access and mobility management network element can also obtain the task identifier in the second message and obtain the correspondence between the task identifier and the information of the first network element.

[0267] S604, the first access and mobility management network element sends a third message to the access network device (or reader), and the access network device receives the third message from the first access and mobility management network element.

[0268] The third message can be a query or paging message.

[0269] The third message can instruct the execution of the first operation.

[0270] For example, the third message may contain information from the aforementioned service request, such as at least one of the following: an identifier or mask used to identify the service request, and optionally, a command instruction.

[0271] Optionally, the third message may also include information about the first network element, such as at least one of the following: identifier, address, FQDN, or port number of the first network element. The first access and mobility management network element may save the information of the first network element obtained in step 3 above, and then encapsulate the previously saved information of the first network element into the third message when executing S604; or, the first access and mobility management network element may also obtain the information of the first network element from the second message, and the specific method of obtaining the information is not limited.

[0272] When the identifier of the access network device is determined in S603, the first access and mobility management network element can send a third message to the access network device based on the identifier of the access network device.

[0273] S605, the access network device performs the first operation through at least one reader.

[0274] If the first service is an inventory management service, the access network device can perform inventory management (i.e., the first operation) through at least one reader to obtain the device identifier of the AIoT terminal being inventoryed. If the first service is a command service (e.g., read, write, deactivation, etc.), the access network device can perform inventory management through at least one reader, and then, according to the command instruction, obtain the command corresponding to the first service (e.g., read command, write command, deactivation command, etc.) from the first network element and send the command to the AIoT terminal. For example, for a read command, the access network device can read data from the AIoT terminal through at least one reader; for a write command, the access network device can write the data to be written to the AIoT terminal through at least one reader. Alternatively, other commands are similar; please refer to the relevant documentation for understanding, and will not be elaborated further here.

[0275] S606, the access network device sends a fourth message to the first access and mobility management network element, and the first access and mobility management network element receives the fourth message sent by the access network device.

[0276] The fourth message can include a response to the first operation (or a report of the first operation).

[0277] The response to the first operation can be a response message or a report message. After receiving the first operation, any message related to the first operation sent by the reader to the first access and mobility management network element (or to the first network element through the first access and mobility management network element) can be regarded as a response to the first operation. This application does not limit the message type and format of the response to the first operation.

[0278] For example, the response to the first operation may be an indication that the first operation is accepted, or it may contain information about the A-IoT device to which the first operation is performed, or it may contain a message / information about the A-IoT device information obtained by the first operation. For example, if the first operation is a write operation, the response to the first operation may include a task identifier and the device identifier of the A-IoT device to which the write operation is performed; or, if the first operation is a read operation, the response to the first operation may include a task identifier and the data read from the A-IoT device; or, if the first operation is a write operation / deactivation, the response to the first operation may include a task identifier and an indication that the operation has been successfully accepted, or it may indicate whether the operation was successful or failed, such as indicating that the data was written successfully / failed, or that the device was deactivated successfully / failed, to avoid subsequent process errors due to not knowing the execution status of the first operation, such as the first operation succeeding but being re-executed, or the first operation failing but not being re-executed.

[0279] Optionally, if the third message also includes information about the first network element, then the fourth message can also include information about the first network element; otherwise, the fourth message may not include information about the first network element. In other words, if the first access and mobility management network element provides information about the first network element, then the access network device can also include this information in the returned message to facilitate routing.

[0280] For example, after receiving a third message, the access network device can store the correspondence between the task identifier and the information of the first network element, or store the correspondence between the task identifier, the information of the first access and mobility management network element, and the information of the first network element. Therefore, when completing a task / naming, the access network device can determine the corresponding first network element information based on the task identifier, and thus carry the information of the first network element in the fourth message sent to the first access and mobility management network element. Of course, if the first access and mobility management network element does not send its own information, the access network device stores the correspondence between the task identifier and the information of the first access and mobility management network element, and the fourth message sent by the access network device will not contain the information of the first network element.

[0281] Optionally, the fourth message may also include information indicating at least one reader, which can be referred to in the relevant description above and will not be repeated here.

[0282] It is understood that the fourth message can be any possible message that the access network device interacts with the first access and mobility management network element, without any specific limitation.

[0283] S607, the first access and mobility management network element sends a response to the first operation to the first network element, and the first network element receives the response to the first operation sent by the first access and mobility management network element.

[0284] When the fourth message contains information about the first network element, the first access and mobility management network element can send a response to the first operation to the first network element based on the information contained in the fourth message. This means it can simply perform routing, or in other words, transparently transmit the response to the first operation without requiring additional processing, thus reducing the overhead of the first access and mobility management network element. In this case, it can also be considered that the first access and mobility management network element sends a response to the first operation from the reader to the first network element. For example, the first access and mobility management network element forwards the response to the first operation.

[0285] Of course, if the fourth message does not contain information about the first network element, the first access and mobility management network element can send a response to the first network element for the first operation based on the task identifier in the fourth message and the correspondence between the task identifier and the information of the first network element; or, the first access and mobility management network element can also determine to provide feedback to the first network element that sent the second message based on the response of the fourth message to the second message (or based on the message returned by the second message), that is, send a response to the first operation to the first network element based on the information of the first network element obtained in advance.

[0286] Optionally, if the fourth message further includes information indicating at least one reader, the first access and mobility management network element can also send the information indicating at least one reader to the first network element.

[0287] The above description, with reference to Figure 6, outlines the communication method provided in the embodiments of this application. The specific flow of the communication method provided in the embodiments of this application will be described in detail below with reference to Figures 7-9.

[0288] Figure 7 is a schematic flowchart of the communication method provided in this embodiment of the application. As shown in Figure 7, the process involves the interaction between AF (such as the third network element), NEF (such as the second network element), A-IoTF (such as the first network element), AMF (such as the first access and mobility management network element), AIoT RAN (such as the access network device), and A-IoT device. For ease of understanding, the process shown in Figure 7 takes disk storage as an example. Other cases such as read / write / deactivation can also be understood by reference and will not be described in detail here.

[0289] Specifically, as shown in Figure 7, the communication method flow is as follows:

[0290] S701a, the AIoT RAN sends an NGAP Setup / AIoT Request message to the AMF.

[0291] The NGAP setup / AIoT request message may contain first information, specifically information about at least one reader (such as a BS reader) that is associated with the AIoT RAN, such as belonging to / being part of the AIoT RAN or being connected to the AIoT RAN. Optionally, it may also contain information about the A-IoTF (such as information about the first network element).

[0292] It is understandable that S701a can also refer to the relevant introduction in steps 1-2 above, which will not be repeated here.

[0293] S701b, AMF sends NGAP Setup / AIoT Response messages to AIoT RAN.

[0294] The NGAP establishment / AIoT request message reports the first information mentioned above to the AMF. In response, the AMF can return an NGAP establishment / AIoT response message to indicate whether the reporting or reception was successful or failed.

[0295] S702, AMF sends a Reader Capability Create / Update / Report message to AIoTF.

[0296] The reader capability establishment / update / report message can contain information about at least one reader. The AMF can send this message to the AIoTF based on the information from the A-IoTF. Correspondingly, the A-IoTF can obtain the correspondence between the AMF and the reader based on the reader information reported by each AMF.

[0297] It is understandable that the specific implementation of S702 can also refer to the relevant introduction in steps 3-6 above, and will not be repeated here.

[0298] S703, AF sends an AIoT service request (Nnef_AIoTService Request) message #1 to NEF.

[0299] S704, NEF sends an AIoT service request (Naiotf_AIoTService Request) message #2 to AIoTF.

[0300] AIoT service request message #1 and AIoT service request message #2 (as described in the first message above) can indicate the first service. If they contain information corresponding to the first service, please refer to the relevant introduction of the first message above. They will not be repeated here.

[0301] It should be understood that AIoT service request message #1 and AIoT service request message #2 can be the same message or different messages. If they are different messages, AIoT service request message #2 can contain the content of AIoT service request message #1. That is, the NEF network element obtains the content of AIoT service request message #1 and then carries it into AIoT service request message #2.

[0302] S705, AIoTF determines the reader and determines AMF based on the corresponding relationship.

[0303] The AIoTF can determine the reader suitable for instructing the first service (such as all readers suitable for executing the first service) based on the information corresponding to the first service, and determine the AMF corresponding to these readers based on the correspondence obtained in S702.

[0304] It should be understood that the specific implementation of S705 can also refer to the relevant introduction of S602 above, and will not be repeated here.

[0305] S706, AIoTF sends AIoT message transfer (Namf_AIoTmessageTransfer) message #1 to AMF.

[0306] AIoT message transmission message #1 (as described in the second message above) can indicate a first operation, such as including information indicating at least one reader (such as the identifier of at least one reader) and a service request (such as an inventory request). For details, please refer to the relevant introduction of the second message above, which will not be repeated here.

[0307] S707, AMF sends NGAP message #1 to AIoT RAN.

[0308] NGAP message #1 may contain information from the aforementioned service request, such as at least one of the following: task identifier or mask; optionally, it may also include command indication (such as a read command); optionally, it may also include AIoTF information. For specific implementation details, please refer to the relevant introduction of the third message above, which will not be repeated here.

[0309] S708, AIoT RAN initiates paging and random access.

[0310] It should be understood that the specific implementation of S708 can also refer to the relevant introductions of S201-S204 above, and will not be repeated here.

[0311] S709, A-IoT devices send AIoT NAS messages to the AIoT RAN.

[0312] In the context of read commands, the AIoT NAS message can contain the device identifier of the A-IoT device.

[0313] S710, AIoT RAN sends NGAP message #2 to AMF.

[0314] NGAP message #2 may contain a response / report of the first operation, such as an inventory report, which may include a task identifier and the device identifier of the A-IoT device. Optionally, NGAP message #2 may also contain information about the AIoTF. Optionally, NGAP message #2 may also contain information indicating at least one reader.

[0315] S711, AMF sends AIoT message transfer (Naiotf_AIoTmessageTransfer) message #2 to AIoTF.

[0316] AIoT message transmission message #2 (as described in the fourth message above) can include an inventory report, and optionally, it can also include information indicating at least one reader.

[0317] S712, AIoTF sends AIoT report (Nnef_AIoTReport) message #1 to NEF.

[0318] AIoTF can perform device identification verification for A-IoT devices, or record the correspondence between device identifications of A-IoT devices and readers. AIoTF can send the device identifications of A-IoT devices through the AIoT Reporting Message (NEF).

[0319] S713, NEF sends AIoT report (Naf_AIoTReport) message #2 to AF.

[0320] AIoT report message #2 also includes the device identifier of A-IoT devices.

[0321] It is understood that the interactive messages in Figure 7 above are examples for ease of understanding and are not intended to be limiting. For example, the interaction between S701a and S701b is not limited to NGAP establishment / AIoT request messages and NGAP establishment / AIoT response messages. Any message / signaling / information / cell that can be used to transmit information in S701a-S701b between the AIoT RAN and AMF is applicable to S701a-S701b. Similarly, S702 is not limited to reader capability establishment / update / report messages. Any message / signaling / information / cell that can be used to transmit information in S702 from AMF to AIoTF is applicable to S702. Furthermore, the messages involved in other steps are understood in a similar way and will not be elaborated here.

[0322] Figure 8 is a schematic flowchart of the communication method provided in this application embodiment. As shown in Figure 8, the process involves the interaction between AF (such as the third network element), NEF (such as the second network element), A-IoTF (such as the first network element), AMF (such as the first access and mobility management network element), AIoT RAN (such as the access network device), and A-IoT devices. For ease of understanding, the process shown in Figure 8 uses disk storage as an example; other cases such as read / write / deactivation can also be understood by reference and will not be elaborated here.

[0323] Specifically, as shown in Figure 8, the flow of this communication method is as follows:

[0324] S801a, the AIoT RAN sends an NGAP setup / AIoT request message to the AMF.

[0325] S801b, AMF sends an NGAP setup / AIoT response message to the AIoT RAN.

[0326] S801a-S801b are similar to S701a-S701b and can be understood by referring to them. The difference is that the NGAP establishment / AIoT request message of S801a does not carry AIoTF information.

[0327] S802, the correspondence between AIoTF pre-configured readers and AMF.

[0328] It should be understood that the specific implementation of S802 can also refer to the relevant introduction of Method 2 above, and will not be repeated here.

[0329] S803, AF sends AIoT service request message #1 to NEF.

[0330] S804, NEF sends AIoT service request message #2 to AIoTF.

[0331] S805, AIoTF determines the reader and determines AMF based on the corresponding relationship.

[0332] S806, AIoTF sends AIoT message transmission message #1 to AMF.

[0333] S807, AMF sends NGAP message #1 to AIoT RAN.

[0334] S808, AIoT RAN initiates paging and random access.

[0335] S809, the A-IoT device sends an AIoT NAS message to the AIoT RAN.

[0336] S810, AIoT RAN sends NGAP message #2 to AMF.

[0337] S811, AMF sends AIoT message transmission message #2 to AIoTF.

[0338] S812, AIoTF sends AIoT report message #1 to NEF.

[0339] S813, NEF sends AIoT report message #2 to AF.

[0340] S803-S813 are similar to S703-S713 and can be understood by referring to them, so they will not be elaborated on here.

[0341] It is understood that the interactive messages in Figure 8 above are examples for ease of understanding and are not intended to be limiting. For example, the interaction between S801a and S801b is not limited to NGAP establishment / AIoT request messages and NGAP establishment / AIoT response messages. Any message / signaling / information / cell that can be used to transmit information in S801a-S801b in the interaction between AIoT RAN and AMF is applicable to S801a-S801b. In addition, the messages involved in other steps are understood in a similar way and will not be elaborated here.

[0342] Figure 9 is a schematic flowchart of the communication method provided in this embodiment of the application. As shown in Figure 9, the process involves the interaction between AF (such as the third network element), NEF (such as the second network element), A-IoTF (such as the first network element), AMF (such as the first access and mobility management network element), AIoT RAN (such as the access network device), and A-IoT devices. For ease of understanding, the process shown in Figure 9 uses disk storage as an example; other cases such as read / write / deactivation can also be understood by reference and will not be elaborated here.

[0343] Specifically, as shown in Figure 9, the flow of this communication method is as follows:

[0344] S901a, the AIoT RAN sends an NGAP setup / AIoT request message to the AMF.

[0345] S901b, AMF sends NGAP setup / AIoT response messages to AIoT RAN.

[0346] S901a-S901b are similar to S701a-S701b and can be understood by referring to them. The difference is that the NGAP establishment / AIoT request message of S901a does not carry AIoTF information.

[0347] S902, identifier for AIoTF pre-configured reader.

[0348] The reader's identifier can include at least one of the following: information about the AMF corresponding to the reader, information about the AIoT RAN associated with the reader, or information about the AIoTF corresponding to the reader. For details, please refer to the relevant introduction of the reader's identifier above, which will not be repeated here.

[0349] S903, AF sends AIoT service request message #1 to NEF.

[0350] S904, NEF sends AIoT service request message #2 to AIoTF.

[0351] S903-S904 are similar to S703-S704 and can be understood by referring to them, so they will not be elaborated on here.

[0352] S905, AIoTF identifies the reader and determines the AMF based on the reader's identifier.

[0353] The specific implementation of S905 can be found in the relevant description in Method 2 above, and will not be repeated here.

[0354] S906, AIoTF sends AIoT message transmission message #1 to AMF.

[0355] S907, AMF sends NGAP message #1 to AIoT RAN.

[0356] S908, AIoT RAN initiates paging and random access.

[0357] S909, A-IoT devices send AIoT NAS messages to the AIoT RAN.

[0358] S910, AIoT RAN sends NGAP message #2 to AMF.

[0359] S911, AMF sends AIoT message transmission message #2 to AIoTF.

[0360] S912, AIoTF sends AIoT report message #1 to NEF.

[0361] S913, NEF sends AIoT report message #2 to AF.

[0362] Among them, S906-S913 are similar to S706-S713 and can be understood by referring to them, so they will not be repeated here.

[0363] It is understood that the interactive messages in Figure 9 above are examples for ease of understanding and are not intended to be limiting. For example, the interaction between S901a and S901b is not limited to NGAP establishment / AIoT request messages and NGAP establishment / AIoT response messages. Any message / signaling / information / cell that can be used to transmit information in S901a-S901b in the interaction between AIoT RAN and AMF is applicable to S901a-S901b. In addition, the messages involved in other steps are understood in a similar way and will not be elaborated here.

[0364] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Exemplarily, as shown in Figure 10, the communication device 1000 includes a transceiver module 1002 and a processing module 1001. For ease of explanation, Figure 10 only shows the main components of the communication device.

[0365] The communication device 1000 can be applied to the communication methods shown in Figures 6-9 to achieve the corresponding functions. For example, the transceiver module 1002 can be used to implement the transceiver function in the communication methods shown in Figures 6-9, and the processing module 1001 can be used to implement other functions in the communication methods shown in Figures 6-9 besides the transceiver function.

[0366] Optionally, the transceiver module 1002 may include a transmitting module (not shown in FIG10) and a receiving module (not shown in FIG10). The transmitting module is used to implement the transmitting function of the communication device 1000, and the receiving module is used to implement the receiving function of the communication device 1000.

[0367] Optionally, the communication device 1000 may further include a storage module (not shown in FIG10) that stores programs or instructions. When the processing module 1001 executes the program or instructions, the communication device 1000 can perform the functions in the methods shown in FIG6-FIG9.

[0368] It is understood that the communication device 1000 may be a network device, or a chip (system) or other component or assembly that can be set in the network device, or a device that includes the network device. This application does not limit this.

[0369] Furthermore, the technical effects of the communication device 1000 can be referenced from the technical effects of the communication method described above, and will not be repeated here.

[0370] Figure 11 is a second schematic diagram of the structure of the communication device provided in an embodiment of this application. Exemplarily, the communication device can be a terminal, or a chip (system) or other component or assembly that can be disposed in the terminal. As shown in Figure 11, the communication device 1100 may include a processor 1101. Optionally, the communication device 1100 may further include a memory 1102 and / or a transceiver 1103. The processor 1101 is coupled to the memory 1102 and the transceiver 1103, for example, they can be connected via a communication bus.

[0371] The following is a detailed description of each component of the communication device 1100 with reference to Figure 11:

[0372] The processor 1101 is the control center of the communication device 1100. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1101 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0373] Optionally, the processor 1101 can execute various functions of the communication device 1100 by running or executing software programs stored in the memory 1102 and calling data stored in the memory 1102, such as executing the communication methods shown in Figures 6-9 above.

[0374] In a specific implementation, as one embodiment, processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG11.

[0375] In a specific implementation, as one embodiment, the communication device 1100 may also include multiple processors, such as processors 1101 and 1104 shown in FIG. 11. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0376] The memory 1102 is used to store the software program that executes the solution of this application, and is controlled by the processor 1101 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0377] Optionally, the memory 1102 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1102 may be integrated with the processor 1101 or may exist independently and be coupled to the processor 1101 through the interface circuit of the communication device 1100 (not shown in FIG. 11). This application embodiment does not specifically limit this.

[0378] Transceiver 1103 is used for communication with other communication devices. For example, if communication device 1100 is a terminal, transceiver 1103 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1100 is a network device, transceiver 1103 can be used to communicate with a terminal or with another network device.

[0379] Optionally, transceiver 1103 may include a receiver and a transmitter (not shown separately in Figure 11). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0380] Optionally, the transceiver 1103 can be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 through the interface circuit of the communication device 1100 (not shown in FIG11). This application embodiment does not specifically limit this.

[0381] It is understood that the structure of the communication device 1100 shown in Figure 11 does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0382] Furthermore, the technical effects of the communication device 1100 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

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

[0384] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0385] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0386] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication.

[0387] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.

[0388] This application also provides a communication system, which includes a first device and a second device for performing the communication method described above.

[0389] This application also provides a chip, which may include a processor that executes the communication method described above. Optionally, the chip may further include a memory coupled to the processor, the memory storing a program for executing the communication method described above.

[0390] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0391] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

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

[0393] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, Applied to the first network element, the method includes: Receive a first message, which indicates a first service; A second message is sent to a first access and mobility management network element. The second message indicates a first operation related to the first service. The second message includes information indicating at least one reader for executing the first service. The at least one reader is connected to the first access and mobility management network element.

2. The method according to claim 1, characterized in that, The method further includes: Based on the first message, the first access and mobility management network element is identified.

3. The method according to claim 2, characterized in that, The step of determining the first access and mobility management network element based on the first message includes: Based on the first message, N readers suitable for performing the first service are determined, where N is an integer greater than or equal to 1, and the N readers include the at least one reader; Determine K access and mobility management network elements corresponding to the N readers, where K is an integer greater than or equal to 1, and the K access and mobility management network elements include the first access and mobility management network element.

4. The method according to claim 3, characterized in that, The method further includes: The X access and mobility management network elements receive information from M readers, where X and M are integers greater than or equal to 1. Based on the information from the M readers, obtain the correspondence between the X access and mobility management network elements and the M readers. The X access and mobility management network elements include the K access and mobility management network elements, and the M readers include the N readers. The correspondence includes the correspondence between the N readers and the K access and mobility management network elements.

5. The method according to claim 4, characterized in that, The information of the reader includes at least one of the following: the identifier of the reader, information indicating the service area of ​​the reader, the identifier of the access network device, or information indicating the service area of ​​the access network device; the reader is connected to the access network device, or the access network device contains the reader.

6. The method according to claim 4 or 5, characterized in that, The information of the reader is carried in the service-oriented message corresponding to the first network element.

7. The method according to claim 3, characterized in that, The first network element pre-configures the correspondence between the X access and mobility management network elements and the M readers, where X and M are integers greater than or equal to 1. The X access and mobility management network elements include the K access and mobility management network elements, and the M readers include the N readers. The correspondence includes the correspondence between the N readers and the K access and mobility management network elements.

8. The method according to claim 3, characterized in that, The step of determining the K access and mobility management network elements corresponding to the N readers includes: Based on the identifiers of the N readers, determine the K access and mobility management network elements corresponding to the N readers.

9. The method according to claim 8, characterized in that, The identifier of the reader includes at least one of the following: information about the access and mobility management network element corresponding to the reader, or information about the access network device, wherein the reader is connected to the access network device, or the access network device contains the reader.

10. A communication method, characterized in that, Applied to the first access and mobility management network element, the method includes: Receive first information from an access network device, the first information containing information about at least one reader, the at least one reader being a reader associated with the access network device; Determine the first network element corresponding to the at least one reader; Send information about the at least one reader to the first network element.

11. The method according to claim 10, characterized in that, The first information also includes information about the first network element, and determining the first network element corresponding to the at least one reader includes: Based on the first information, which includes information about the at least one reader and information about the first network element, it is determined that the at least one reader corresponds to the first network element.

12. The method according to claim 10, characterized in that, Determining the first network element corresponding to the at least one reader includes: Send a network function discovery request to the network repository function; The network storage function receives information about the first network element corresponding to at least one reader, sent by the network function discovery request.

13. The method according to claim 12, characterized in that, The network function discovery request includes information indicating that the network function type is an Internet of Things (IoT) function and / or service area information, wherein the network function type of the first network element is an IoT function, and the service area indicated by the service area information includes the service area of ​​the at least one reader.

14. The method according to claim 10, characterized in that, The first access and mobility management network element pre-configures the information of the first network element.

15. The method according to any one of claims 11-14, characterized in that, Sending the first information to the first network element includes: Based on the information of the first network element, send information about at least one reader to the first network element.

16. The method according to any one of claims 10-14, characterized in that, The first information further includes indication information, which indicates sending reader information to the first network element, wherein sending the at least one reader information to the first network element includes: According to the instruction information, the information of the at least one reader is sent to the first network element.

17. The method according to any one of claims 10-16, characterized in that, The information of the reader includes at least one of the following: the identifier of the reader, information indicating the service area of ​​the reader, the identifier of the access network device, or information indicating the service area of ​​the access network device.

18. The method according to any one of claims 10-17, characterized in that, The method further includes: Receive a second message from the first network element, the second message indicating a first operation, the first operation being related to the first service, the second message including information indicating at least one reader, the at least one reader being used to execute the first service; Identify the access network device associated with the at least one reader; A third message is sent to the access network device, the third message instructing the execution of the first service.

19. The method according to any one of claims 1-9 and 18, characterized in that, The second message is a service-oriented message corresponding to the first access and mobility management network element.

20. The method according to claim 18 or 19, characterized in that, The information indicating at least one reader includes the identifier of the at least one reader, and the step of determining the access network device associated with the at least one reader includes: Based on the identifier of the at least one reader, it is determined that the at least one reader is associated with the access network device.

21. The method according to claim 20, characterized in that, The identifier of the reader includes at least one of the following: information of the access network device, or information of the first access and mobility management network element.

22. The method according to any one of claims 10-20, characterized in that, The at least one reader is connected to the access network device, or the access network device contains the at least one reader.

23. The method according to any one of claims 1-22, characterized in that, The first network element is the Environmental Internet of Things (AIoTF).

24. The method according to any one of claims 1-9, 18, characterized in that, The first service is any one of the following: inventory service, read service, write service, or deactivation service.

25. A communication device, characterized in that, The communication device is used to perform the method as described in any one of claims 1-24.

26. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-24.

27. A communication device, characterized in that, include: Processor and interface circuits; among which, The interface circuit is used to receive code instructions and transmit them to the processor; The processor is used to run the code instructions to perform the method as described in any one of claims 1-24.

28. A communication device, characterized in that, The communication device includes a processor and a transceiver, the transceiver being used for information exchange between the communication device and other communication devices, and the processor executing program instructions to perform the method as described in any one of claims 1-24.

29. The communication device according to any one of claims 25-28, characterized in that, The communication device is a chip.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-24.

31. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-24.

Images