Communication method, apparatus and system

Abstract

The present disclosure relates to the technical field of mobile communications. Provided are a communication method, apparatus and system. The communication method is executed by a first core network device, and comprises: receiving, from a second core network device, a subscription data acquisition request for an ambient Internet of Things (AIoT) terminal to be subjected to access, wherein the acquisition request carries an identifier of said AIoT terminal, and the second core network device and the first core network device are located in an operator network to be accessed; on the basis of the identifier of said AIoT terminal and a location information table of AIoT subscription data, determining a storage location of subscription data of said AIoT terminal; and sending to the second core network device indication information of the storage location or the subscription data of said AIoT terminal that is acquired from the storage location.

Description

Communication methods, devices and systems

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to CN application No. 202411456667.2, filed on October 18, 2024, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to the field of mobile communication technology, and in particular to a communication method, apparatus and system. Background Technology

[0004] According to the 3rd Generation Partnership Project (3GPP), an Ambient IoT (AIoT) terminal is an Internet of Things (IoT) device with extremely low energy consumption and no SIM card. Furthermore, based on whether it has an amplifier, AIoT terminals can be divided into weak terminals that only support backscatter communication and strong terminals that can generate signals themselves or use backscatter communication.

[0005] In related technologies, traditional user equipment (UE) can store subscription data (or contract data) or related data. The UE can report the subscription data to the operator network so that the operator network can perform access authentication for the UE based on the subscription data. Summary of the Invention

[0006] This disclosure provides a communication method, apparatus, and system.

[0007] According to a first aspect of this disclosure, a communication method is provided, executed by a first core network device, comprising: receiving from a second core network device a subscription data acquisition request for a passive Internet of Things (AIoT) terminal to be accessed, the acquisition request carrying an identifier of the AIoT terminal to be accessed, wherein the second core network device and the first core network device are located in the network of the operator to be accessed;

[0008] Based on the identifier of the AIoT terminal to be connected and the location information table of pre-stored AIoT subscription data, the storage location of the subscription data of the AIoT terminal to be connected is determined; the indication information of the storage location or the subscription data of the AIoT terminal to be connected obtained from the storage location is sent to the second core network device.

[0009] In some embodiments, the location information table of the AIoT subscription data includes a correspondence between the identifier of the AIoT terminal and the information of a third-party server, wherein the third-party server is used to store the subscription data of the AIoT terminal.

[0010] In some embodiments, determining the storage location of the subscription data of the AIoT terminal to be connected based on the identifier of the AIoT terminal to be connected and a pre-stored location information table of AIoT subscription data includes: querying the location information table of AIoT subscription data based on the identifier of the AIoT terminal to be connected; and if the location information table of AIoT subscription data contains information about a third-party server corresponding to the identifier of the AIoT terminal to be connected, using the third-party server corresponding to the identifier of the AIoT terminal to be connected as the storage location of the subscription data of the AIoT terminal to be connected.

[0011] In some embodiments, sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device includes: when the storage location is a third-party server, sending the information of the third-party server as the indication information of the storage location to the second core network device, so that the second core network device can obtain the subscription data of the AIoT terminal to be accessed from the third-party server according to the information of the third-party server.

[0012] In some embodiments, the acquisition request further carries the home network identifier of the AIoT terminal to be accessed. The step of determining the storage location of the subscription data of the AIoT terminal to be accessed based on the identifier of the AIoT terminal to be accessed and the pre-stored location information table of AIoT subscription data further includes: if the location information table of AIoT subscription data does not contain information about the third-party server corresponding to the identifier of the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is the same as the identifier of the operator network to be accessed, then the operator network to be accessed is used as the storage location of the subscription data of the AIoT terminal to be accessed.

[0013] In some embodiments, sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device further includes: if the storage location is the network of the operator to be accessed, sending the subscription data of the AIoT terminal to be accessed obtained from the network of the operator to be accessed to the second core network device.

[0014] In some embodiments, the acquisition request further carries the home network identifier of the AIoT terminal to be accessed. The step of determining the storage location of the subscription data of the AIoT terminal to be accessed based on the identifier of the AIoT terminal to be accessed and the pre-stored location information table of AIoT subscription data further includes: if the location information table of AIoT subscription data does not contain information of the third-party server corresponding to the identifier of the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is different from the identifier of the operator network to be accessed, then the third-party operator network indicated by the home network identifier is used as the storage location of the subscription data of the AIoT terminal to be accessed.

[0015] In some embodiments, sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device further includes: if the storage location is a third-party operator network indicated by the home network identifier, sending the information of the third-party operator network as the indication information of the storage location to the second core network device, so that the second core network device can obtain the subscription data of the AIoT terminal to be accessed from the third-party operator network according to the information of the third-party operator network.

[0016] In some embodiments, the identifier of the AIoT terminal in the location information table of the AIoT subscription data is either the unique identifier of the AIoT terminal or the identifier of the group to which the AIoT terminal belongs.

[0017] In some embodiments, the identifier of the group to which the AIoT terminal belongs includes the identifier of the manufacturer to which the AIoT terminal belongs, or the identifier of the application to which the AIoT terminal belongs.

[0018] In some embodiments, the information of the third-party server in the location information table of the AIoT subscription data includes the address information of the third-party server.

[0019] In some embodiments, the information of the third-party server in the location information table of the AIoT subscription data also includes the deployment type information of the third-party server, and sending the information of the third-party server as the indication information of the storage location to the second core network device includes: sending the address information of the third-party server and the deployment type information of the third-party server to the second core network device.

[0020] In some embodiments, the deployment type of the third-party server includes a server in a standalone non-public network (SNPN) or a server in a data network.

[0021] In some embodiments, the first core network device is a unified data management (UDM) device, and the second core network device is a passive Internet of Things management function (AIoTMF) device or an access and mobility management function (AMF) device.

[0022] According to a second aspect of this disclosure, a communication apparatus is provided, disposed in a first core network device, comprising: a module for performing the communication method as described above.

[0023] According to a third aspect of this disclosure, a communication apparatus is provided, disposed in a first core network device, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the communication method as described above based on instructions stored in the memory.

[0024] According to a fourth aspect of this disclosure, a communication system is provided, comprising: a first core network device including the communication apparatus as described above; and a second core network device configured to: send a subscription data acquisition request for an AIoT terminal to be accessed to the first core network device; receive an indication of a storage location from the first core network device or subscription data of the AIoT terminal to be accessed acquired from the storage location; and, upon receiving the indication of the storage location, acquire the subscription data of the AIoT terminal to be accessed from the storage location according to the indication of the storage location.

[0025] In some embodiments, the storage location indication information is information from a third-party server. The second core network device receiving the storage location indication information from the first core network device or obtaining the subscription data of the AIoT terminal to be accessed from the storage location includes: receiving the information from the third-party server from the first core network device; the second core network device obtaining the subscription data of the AIoT terminal to be accessed from the storage location according to the storage location indication information includes: when the third-party server is deployed as a server in an independent non-public network (SNPN), sending a data acquisition request to the third-party server via an authentication and authorization function device selected through network slicing to obtain the subscription data of the AIoT terminal to be accessed from the third-party server; when the third-party server is deployed as a server in a data network, sending a data acquisition request to the third-party server via a network open function device to obtain the subscription data of the AIoT terminal to be accessed from the third-party server.

[0026] In some embodiments, the second core network device receiving storage location indication information or subscription data of the AIoT terminal to be accessed obtained from the storage location from the first core network device includes: receiving the subscription data of the AIoT terminal to be accessed from the first core network device.

[0027] In some embodiments, the storage location indication information is information about a third-party operator network indicated by the home network identifier of the AIoT terminal to be accessed. The second core network device receiving the storage location indication information from the first core network device or obtaining the subscription data of the AIoT terminal to be accessed from the storage location includes: receiving information from the third-party operator network from the first core network device; the second core network device obtaining the subscription data of the AIoT terminal to be accessed from the storage location according to the storage location indication information includes: sending a data acquisition request to a device in the third-party operator network; and receiving the subscription data of the AIoT terminal to be accessed returned by the device in the third-party operator network.

[0028] In some embodiments, the second core network device is further configured to: receive a network access request for the AIoT terminal to be accessed sent by a wireless reader before sending a subscription data acquisition request for the AIoT terminal to be accessed to the first core network device; and after acquiring the subscription data of the AIoT terminal to be accessed, perform network access authentication on the AIoT terminal to be accessed based on the subscription data of the AIoT terminal to be accessed.

[0029] In some embodiments, the communication system further includes: a business operation support device configured to deploy the location information table of the AIoT subscription data to the first core network device.

[0030] According to a fifth aspect of this disclosure, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the communication method as described above.

[0031] According to a sixth aspect of this disclosure, a computer program product is provided having computer instructions stored thereon that, when executed by a processor, implement the communication method as described above.

[0032] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0033] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0034] Figure 1 is a flowchart illustrating a communication method according to some embodiments of the present disclosure;

[0035] Figure 2 is a flowchart illustrating a communication method according to some other embodiments of the present disclosure;

[0036] Figure 3 is a schematic diagram of the signing and information deployment sub-process in a communication method according to some embodiments of the present disclosure;

[0037] Figure 4 is a schematic diagram of a location information table of AIoT subscription data according to some embodiments of the present disclosure;

[0038] Figure 5 is a schematic diagram of a data acquisition sub-process in a communication method according to some embodiments of the present disclosure;

[0039] Figure 6 is a schematic diagram of information stored in an AIoT terminal according to some embodiments of the present disclosure;

[0040] Figure 7 is a schematic diagram of a data acquisition sub-process in a communication method according to some embodiments of the present disclosure;

[0041] Figure 8 is a schematic diagram of a data acquisition sub-process in a communication method according to some embodiments of the present disclosure;

[0042] Figure 9 is a schematic diagram of a data acquisition sub-process in a communication method according to some embodiments of the present disclosure;

[0043] Figure 10 is a schematic diagram of the structure of a communication device according to some embodiments of the present disclosure;

[0044] Figure 11 is a schematic diagram of the structure of a communication device according to some embodiments of the present disclosure;

[0045] Figure 12 is a schematic diagram of the structure of a communication system according to some embodiments of the present disclosure;

[0046] Figure 13 is a schematic diagram of the structure of a communication system according to some other embodiments of the present disclosure.

[0047] This disclosure can be more clearly understood with reference to the accompanying drawings and the following detailed description. Detailed Implementation

[0048] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0049] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0050] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0051] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0052] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0053] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0054] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0055] In related technologies, traditional user equipment (UE) stores subscription data at the UE. However, AIoT terminals, due to their extremely low power, cannot store large amounts of subscription data. This makes it impossible for the UE to obtain the subscription data between the AIoT terminal and the UE from the data reported by the AIoT terminal, thus making it difficult for the UE to authenticate the AIoT terminal and provide network access and other services.

[0056] Related research suggests two methods for storing AIoT terminal network subscription data: one is to store the AIoT terminal's network subscription data in the AIoT terminal's home network, and the other is to store the AIoT terminal's network subscription data on a third-party server.

[0057] Due to their unique device characteristics, AIoT terminals differ from traditional user devices and cannot store large amounts of dynamic data. This makes it difficult for the network to obtain the subscription data required for subsequent access authentication when an AIoT terminal connects to the network, thus hindering the authentication of the AIoT terminal and the provision of corresponding network access services.

[0058] Based on this, this disclosure proposes a communication method, apparatus, and system that can effectively locate and acquire subscription data of AIoT terminals, thereby facilitating access authentication for AIoT terminals and providing corresponding network access services.

[0059] Figure 1 is a schematic flowchart of a communication method according to some embodiments of the present disclosure. In these embodiments, the communication method is executed by a first core network device and includes steps S11 to S13.

[0060] Step S11: Receive a subscription data acquisition request for the AIoT terminal to be connected from the second core network device.

[0061] The first core network device and the second core network device are devices in the operator's network to be accessed. In some examples, the first core network device is a Unified Data Management (UDM) device, and the second core network device is an Access and Mobility Management Function (AMF) device.

[0062] In other examples, the first core network device is a UDM device (also known as a UDM entity or UDM network element), and the second core network device is an Ambient IoT Management Function (AIoTMF) device. The Ambient IoT Management Function device can also be referred to as an Ambient IoT Function (AIoTF) device. Furthermore, in specific implementations, the first and second core network devices can also be other devices within the operator's network to be accessed.

[0063] The subscription data acquisition request carries the identifier of the AIoT terminal to be connected. This identifier can be the entire device identifier read from the AIoT terminal, or a portion of the device identifier read from the AIoT terminal. In addition to the identifier of the AIoT terminal to be connected, the subscription data acquisition request may also carry the home network identifier of the AIoT terminal to be connected.

[0064] Step S12: Determine the storage location of the subscription data of the AIoT terminal to be connected based on the identifier of the AIoT terminal to be connected and the pre-stored location information table of AIoT subscription data.

[0065] The location information table for AIoT subscription data can take various forms. In some examples, the location information table includes the storage location information of all AIoT terminals corresponding to all Application Functions (AFs) subscribed to by the network to be accessed. For example, suppose the network to be accessed is subscribed to Application Function 1, and the AIoT terminals corresponding to Application Function 1 include AIoT Terminal 1 to AIoT Terminal 100. The subscription data of AIoT Terminal 1 to AIoT Terminal 50 is stored on a third-party server, and the subscription data of AIoT Terminal 51 to AIoT Terminal 100 is stored on the network to be accessed. Then, the location information table includes the storage location information of the subscription data of AIoT Terminal 1 to AIoT Terminal 100.

[0066] In some of the examples above, step S12 may include: querying a location information table based on the identifier of the AIoT terminal to be accessed; if the location information table contains storage location information corresponding to the identifier of the AIoT terminal to be accessed, then determining the storage location of the subscription data based on the storage location information. For example, if the storage location information corresponding to the identifier of the AIoT terminal to be accessed is information of a third-party server, then the storage location of the subscription data is the third-party server; if the storage location information corresponding to the identifier of the AIoT terminal to be accessed is information of a local UDM device, then the storage location of the subscription data is the UDM device. Further, step S12 may also include: if the location information table does not contain storage location information corresponding to the identifier of the AIoT terminal to be accessed, then determining the storage location of the subscription data as the home network of the AIoT terminal to be accessed.

[0067] In other examples, the location information table for AIoT subscription data includes the storage location information of a subset of AIoT terminals corresponding to all application services (AFs) subscribed to by the network to be accessed. These AIoT terminals can be those whose subscription data is stored on a third-party server. For example, suppose the network to be accessed subscribes to application service 1, and the AIoT terminals corresponding to application service 1 include AIoT terminals 1 to 100. The subscription data for AIoT terminals 1 to 50 is stored on a third-party server, while the subscription data for AIoT terminals 51 to 100 is stored on the network to be accessed. In this case, the location information table only includes the storage location information of the subscription data for AIoT terminals 1 to 50.

[0068] In some other examples, the location information table for AIoT subscription data includes a mapping between the identifiers of AIoT terminals and information from third-party servers. This location information table may contain only the identifiers of AIoT terminals that have signed up with the network of the operator to be accessed, or it may contain both identifiers of AIoT terminals that have signed up with the network of the operator to be accessed and identifiers of AIoT terminals that have not signed up with the network of the operator to be accessed.

[0069] In this embodiment, by storing a location information table of AIoT subscription data on the network side, the storage location of the AIoT subscription data can be easily determined subsequently. Furthermore, deploying the location information table on the network side facilitates dynamic updates, thereby meeting the needs of different business customers and the future flow requirements of AIoT information. In addition, deploying the location information table on the network side eliminates the need to store dynamic information in the AIoT terminal, aligning with the low-power characteristics of AIoT terminals and facilitating widespread adoption. Moreover, by ensuring that the location information table only contains the storage location information of AIoT terminals whose subscription data is stored on a third-party server, the network side can minimize the amount of data required for storage and improve the query efficiency of the location information table, thereby enhancing the real-time performance of subscription data location and retrieval.

[0070] In some of the aforementioned examples, step S12 includes: querying a location information table based on the identifier of the AIoT terminal to be connected; if the location information table contains a third-party server corresponding to the identifier of the AIoT terminal to be connected, then using that third-party server as the storage location for the subscription data of the AIoT terminal to be connected. Through this process, the network side achieves data location functionality for scenarios where subscription data is stored on a third-party server.

[0071] In some of the aforementioned examples, step S12 may further include: if the location information table does not contain information about the third-party server corresponding to the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is the same as the identifier of the operator network to be accessed, then the operator network to be accessed is used as the storage location for the subscription data of the AIoT terminal to be accessed. Through the above process, the network side achieves data location functionality for two storage scenarios: subscription data stored on a third-party server and subscription data stored on the operator network to be accessed.

[0072] In some of the aforementioned examples, step S12 may further include: if the location information table does not contain information about the third-party server corresponding to the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is different from the identifier of the operator network to be accessed, then the third-party operator network indicated by the home network identifier shall be used as the storage location of the subscription data of the AIoT terminal to be accessed. Through the above process, the network side achieves data location functionality for three storage scenarios: subscription data stored on a third-party server, subscription data stored on the operator network to be accessed, and subscription data stored on a third-party operator network. This helps improve the scenario applicability and access flexibility of the AIoT terminal access process.

[0073] Step S13: Send the storage location indication information or the subscription data of the AIoT terminal to be connected obtained from the storage location to the second core network device.

[0074] Step S13 can be implemented in various ways. The following describes three examples of implementation methods.

[0075] In the first embodiment, step S13 includes sending the storage location indication information to the second core network device. In this embodiment, regardless of whether the storage location is a third-party server, the network of the operator to be accessed, or a third-party operator network, the storage location indication information is sent to the second core network device.

[0076] In the second embodiment, step S13 includes: sending the subscription data of the AIoT terminal to be accessed, obtained from the storage location, to the second core network device. In this embodiment, regardless of whether the storage location is a third-party server, the network of the operator to be accessed, or a third-party operator network, the subscription data of the AIoT terminal to be accessed is first obtained from the storage location, and then the subscription data is sent to the second core network device.

[0077] In the third implementation, step S13 includes: when the storage location of the subscription data of the AIoT terminal to be accessed is a first specified type, sending the storage location indication information to the second core network device; when the storage location of the subscription data of the AIoT terminal to be accessed is a second specified type, first obtaining the subscription data of the AIoT terminal to be accessed from the storage location, and then sending the subscription data to the second core network device.

[0078] In this embodiment of the disclosure, the above process can effectively locate and obtain the subscription data of the AIoT terminal, thereby facilitating subsequent access authentication of the AIoT terminal and provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0079] Figure 2 is a schematic flowchart of a communication method according to some other embodiments of the present disclosure. In these embodiments, the communication method is performed by a first core network device and includes steps S21 to S26.

[0080] Step S21: Receive a subscription data acquisition request for the AIoT terminal to be connected from the second core network device.

[0081] The first core network device can be a UDM device in the operator's network to be accessed, and the second core network device can be an AIoTF device in the operator's network to be accessed. The subscription data acquisition request received by the first core network device can carry the identifier of the AIoT terminal to be accessed and the home network identifier of the AIoT terminal to be accessed.

[0082] Step S22: Query the location information table of AIoT subscription data based on the identifier of the AIoT terminal to be connected.

[0083] The location information table includes the mapping between the identifiers of AIoT terminals and information from a third-party server. This third-party server is used to store the subscription data of the AIoT terminals.

[0084] Furthermore, the identifier for the AIoT terminal in the location information table can be either a unique identifier for the AIoT terminal or the identifier of the group to which the AIoT terminal belongs. The information for the third-party server in the location information table can be the address information of the third-party server, or information such as the address and deployment type of the third-party server.

[0085] In some examples, the identifier of the AIoT terminal to be connected differs from the type of the AIoT identifier in the location information table. In these examples, the identifier of the AIoT terminal to be connected can be type-converted first, and then the location information table can be queried based on the converted identifier. For example, suppose the identifier of the AIoT terminal to be connected is a whole consisting of a home network identifier, a vendor identifier, and an instance identifier, while the AIoT identifier in the location information table is a vendor identifier. Then, the vendor identifier of the AIoT terminal to be connected is extracted from the identifier of the AIoT terminal to be connected, and then the location information table is queried based on the vendor identifier of the AIoT terminal to be connected.

[0086] In other examples, the identifier of the AIoT terminal to be connected is of the same type as the AIoT identifier in the location information table. In these examples, the location information table can be queried directly based on the identifier of the AIoT terminal to be connected. For example, assuming that both the identifier of the AIoT terminal to be connected and the AIoT identifier in the location information table are a whole consisting of a home network identifier, a vendor identifier, and an instance identifier, the location information table can be queried directly based on the identifier of the AIoT terminal to be connected.

[0087] Step S23: Determine whether the table contains information about the third-party server corresponding to the identifier of the AIoT terminal to be connected.

[0088] In this step, the query results are used to determine whether the query contains information about the third-party server corresponding to the identifier of the AIoT terminal to be connected. If the result of step S23 is yes, step S25 is executed; if the result of step S23 is no, step S24 is executed.

[0089] Step S24: Determine whether the network of the operator to be accessed is the home network of the AIoT terminal.

[0090] In some examples, prior to step S24, the home network identifier of the AIoT terminal to be connected is obtained from the subscription data acquisition request. Then, the home network identifier of the AIoT terminal to be connected is compared with the identifier of the operator network to be connected. If they are the same, the operator network to be connected is determined to be the home network of the AIoT terminal to be connected; if they are different, the operator network to be connected is determined not to be the home network of the AIoT terminal to be connected.

[0091] If the result of the judgment in step S24 is negative, proceed to step S25; if the result of the judgment in step S24 is positive, proceed to step S26.

[0092] Step S25: Send the storage location indication information to the second core network device.

[0093] In some examples, step S25 includes: if the location information table contains information about a third-party server corresponding to the identifier of the AIoT terminal to be accessed, the information of the third-party server is used as an indication of the storage location and sent to the second core network device. Upon receiving the indication, the second core network device retrieves the subscription data of the AIoT terminal to be accessed from the third server based on the indication, and performs network access authentication on the AIoT terminal based on the subscription data. Through this process, the network side achieves data location and retrieval functionality for scenarios where subscription data is stored on a third-party server, facilitating subsequent access authentication of the AIoT terminal.

[0094] In some examples, step S25 includes: if the location information table does not contain information about the third-party server corresponding to the identifier of the AIoT terminal to be accessed, and the network of the operator to be accessed is not the home network of the AIoT terminal to be accessed, then the information of the third-party operator network indicated by the home network is used as the storage location indication information, and this information is sent to the second core network device. Upon receiving the indication information, the second core network device retrieves the subscription data of the AIoT terminal to be accessed from the third-party operator network based on the indication information, and performs network access authentication on the AIoT terminal to be accessed based on the subscription data. Through this process, the network side can also achieve data location and retrieval functions for storage scenarios where subscription data exists on a third-party operator network, facilitating subsequent access authentication of the AIoT terminal.

[0095] Step S26: Obtain subscription data and send the subscription data to the second core network device.

[0096] In step S26, the subscription data of the AIoT terminal to be accessed is first obtained from a device in the network of the operator to be accessed (such as the first core network device), and then the subscription data of the AIoT terminal to be accessed is sent to the second core network device. After receiving the subscription data of the AIoT terminal to be accessed, the second core network device performs network access authentication on the AIoT terminal to be accessed based on the subscription data. Through the above process, the network side realizes the data location and acquisition function for the storage scenario where subscription data exists in the network of the operator to be accessed, which facilitates the subsequent access authentication of the AIoT terminal.

[0097] In this embodiment of the disclosure, the above process enables the network side to realize data location and acquisition functions for three storage scenarios: subscription data exists on a third-party server, subscription data exists on a network to be accessed by an operator, and subscription data exists on a third-party operator network. This not only facilitates access authentication for AIoT terminals and provides corresponding network access services, but also helps to improve the scenario applicability and access flexibility of the AIoT terminal access process.

[0098] Figure 3 is a schematic diagram of a subscription and information deployment sub-process in a communication method according to some embodiments of the present disclosure. In these embodiments, the communication method includes the subscription and information deployment sub-process shown in Figure 3, and the subscription data acquisition sub-process shown in Figures 5, 7 to 9. The subscription and information deployment sub-process will be described first below.

[0099] Step 31: AF signs an AIoT network service agreement with BOSS.

[0100] Application Function (AF) devices are third-party devices responsible for AIoT-related business, and can also be called passive IoT application function devices.

[0101] The Business Operation Support System (BOSS) is a system to be connected to the operator's side. It is mainly responsible for signing AIoT network service contracts with AF and deploying AIoT-related business information.

[0102] Step 32: AF provides BOSS with a location information table of AIoT subscription data.

[0103] The location information table for AIoT subscription data includes the mapping between the identifiers of AIoT terminals and information from third-party servers. These third-party servers, also known as passive IoT subscription servers, are primarily used to store the network subscription data of AIoT terminals.

[0104] Location information tables can take various forms. As shown in Figure 4, the location information tables for AIoT subscription data include four types, a to d. Among them, table a can also be called a full table, and tables b to d can be called partial tables.

[0105] Location information table a includes the mapping between complete device identifiers of AIoT devices and the address information of third-party servers. For example, in location information table a, AIoT ID1 corresponds to Add1. Here, AIoT ID1 is the complete device identifier of the AIoT terminal, used to uniquely identify an AIoT terminal, and Add1 is the address information of the third-party server. In practical implementation, location information table a can be used for situations with complex business operations or numerous business types, a small number of deployed AIoT terminals, and high business management requirements, to facilitate fine-grained management of each AIoT terminal.

[0106] Location information tables b to d include the mapping between a portion of the AIoT device identifier and the address information of a third-party server. Specifically, location information table b includes the mapping between the vendor identifier of the AIoT device and the address information of the third-party server. For example, in location information table b, vendor ID1 corresponds to Add1. Vendor ID1 is the identifier of the vendor to which the AIoT terminal belongs, and Add1 is the address information of the third-party server. The vendor identifier can be information from an AIoT service provider, a public platform, or a manufacturer.

[0107] Location information table c includes the mapping between instance identifiers and the address information of third-party servers. For example, in location information table c, instance ID1 corresponds to Add1. Here, instance ID1 is the unique identifier of the AIoT terminal within the operator's network, and Add1 is the address information of the third-party server.

[0108] Location information table d includes the mapping between the identifier of the AIoT application and the address information of the third-party server. For example, in location information table d, application ID1 corresponds to Add1. Here, application ID1 is the identifier of the application to which the AIoT terminal belongs, defined by the third-party service, and Add1 is the address information of the third-party server.

[0109] Furthermore, the location information table may also include deployment type information for third-party servers. The deployment type of the third-party server includes servers in a stand-alone non-public network (SNPN) or servers in a data network (or simply application servers). For example, in location information table a, AIoT ID1 corresponds to Add1 of type SNPN, indicating that the deployment type of this third-party server is a server in an SNPN (or the deployment type can be simply referred to as SNPN).

[0110] It should be noted that Figure 4 illustrates the one-to-one relationship between AIoT terminal identifiers and third-party server address information. In actual location information table design, the correspondence between AIoT terminal identifiers and third-party server address information can be varied. For example, multiple AIoT terminal identifiers can correspond to one third-party server address. Simultaneously, in actual location information table design, the deployment type (e.g., SNPN) tag of a third-party server can also correspond to one or more third-party servers.

[0111] Step 33: BOSS provides NEF with AF's contract and authorization information.

[0112] For example, the subscription and authorization information of the AF may include the server address information of the AF, the information required to authenticate the AF, and the subscription service information between the AF and the network of the operator to be accessed.

[0113] Network Exposure Function (NEF) devices are used to store AF's subscription and authorization information.

[0114] Step 34: NEF sends the deployment results to BOSS.

[0115] In some examples, step 34 includes: if the NEF device successfully saves the AF's subscription and authorization information, sending a deployment success notification to the BOSS device; if the NEF device fails to save the AF's subscription and authorization information, sending a deployment failure notification to the BOSS device.

[0116] Step 35: BOSS provides UDM with a location information table of AIOT subscription data.

[0117] In this step, the BOSS sends the location information table of the AIoT subscription data to the UDM devices in its network. The UDM devices save the location information table of the AIoT subscription data.

[0118] Step 36: UDM sends the deployment results to BOSS.

[0119] In some examples, step 36 includes: if the UDM device successfully saves the location information table, sending a deployment success notification to the BOSS device; if the UDM device fails to save the location information table, sending a deployment failure notification to the BOSS device.

[0120] In this embodiment of the disclosure, the above steps realize the sub-process of signing up for and deploying information for passive IoT services, which facilitates the subsequent location and acquisition of subscription data of AIoT terminals based on the deployed location information table, and the access management of AIoT terminals accordingly.

[0121] Figure 5 is a schematic diagram of a data acquisition sub-process in a communication method according to some embodiments of the present disclosure. As shown in Figure 5, the data acquisition sub-process includes steps 51 to 54, and steps 55a and 56a.

[0122] Step 51: Trigger AIoT terminal access, read the AIoT terminal ID and check the AIoT terminal ID.

[0123] In this step, the network access process can be initiated by the AIoT terminal itself, by the wireless reader / writer for the AIoT terminal, or by the application function (AF) device for the AIoT terminal. The wireless reader / writer can be a terminal reader / writer or a base station reader / writer.

[0124] After initiating the network access process, the wireless reader reads the identifier of the AIoT terminal from the AIoT terminal to be accessed and checks the identifier. For example, the check of the identifier may include: checking whether the AIoT terminal's identifier (ID) is complete, and checking whether the AIoT terminal's identifier conforms to the specification. Through the above checks, the possibility of incorrect AIoT terminal identifiers can be reduced, and the security and reliability of the overall process can be improved.

[0125] The device identifier stored in the AIoT terminal to be accessed can be flexibly configured. For example, as shown in Figure 6, the AIoT device identifier includes the home network identifier, vendor identifier, instance identifier, and application identifier. The home network identifier can be represented by the Mobile Network Code (MNC) and Mobile Country Code (MCC), or by the Public Land Mobile Network ID (PLMN ID). The vendor identifier can be information about the AIoT terminal manufacturer, or information about the service provider or public platform offering AIoT services. The instance identifier is a unique identifier for the AIoT terminal within the operator's network. The application identifier is an identifier defined by a third-party service, such as the identifier for a specific type of service.

[0126] Step 52: The wireless reader sends an AIoT terminal access request to the AMF or AIoTMF.

[0127] After the check on the identifier of the AIoT terminal to be connected passes, the wireless reader will send an access request for the AIoT terminal to the AMF or AIoTMF device in the network of the operator to be connected. This access request carries the identifier of the AIoT terminal to be connected.

[0128] Step 53: AMF or AIoTMF sends a subscription data retrieval request to UDM.

[0129] Upon receiving an access request from an AIoT terminal seeking to connect, the AMF or AIoTMF device sends a subscription data acquisition request to the UDM device. The UDM device, AMF device, and AIoTMF device are all located within the same operator's network.

[0130] Step 54: UDM queries the AIoT subscription data location information table.

[0131] The UDM device obtains the identifier of the AIoT terminal to be connected from the subscription data acquisition request, and then queries the location information table of the AIoT subscription data based on the identifier of the AIoT terminal to be connected. This location information table contains the correspondence between the identifiers of the AIoT terminals and the address information of the third-party servers. If the location information table does not contain the address information of the third-party server corresponding to the identifier of the AIoT terminal to be connected, step 55a is executed.

[0132] Step 55a: UDM compares the home network identifier of the AIoT terminal with the identifier of the operator network to be accessed to determine that the subscription data is located locally.

[0133] The UDM device obtains the home network identifier of the AIoT terminal to be connected from the subscription data acquisition request, and then compares the home network identifier with the identifier of the network to be connected. If the comparison result is the same, it is determined that the subscription data of the AIoT terminal to be connected is located locally, that is, the subscription data is located in the network of the operator to be connected.

[0134] Step 56a: UDM sends the subscription data of the AIoT terminal to AMF or AIoTMF.

[0135] The UDM device obtains the subscription data of the AIoT terminal to be connected from the local device (such as the UDM device) and sends the subscription data of the AIoT terminal to be connected to the AMF device or AIoTMF device.

[0136] In some examples, after receiving subscription data from the AIoT terminal to be connected, the AMF device or AIoTMF device performs network access authentication on the AIoT terminal to be connected based on the subscription data.

[0137] In other examples, after receiving the subscription data from the AIoT terminal to be connected, the AMF device or AIoTMF device sends the subscription data to other devices, and the other devices perform network access authentication on the AIoT terminal to be connected.

[0138] In this embodiment of the disclosure, the above steps can effectively locate and obtain the subscription data of the AIoT terminal, especially realizing the data location and acquisition function for the storage scenario where the subscription data is stored in the network of the operator to be accessed, thereby facilitating the subsequent access authentication of the AIoT terminal and the provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0139] Figure 7 is a schematic diagram of a subscription data acquisition sub-process in a communication method according to some embodiments of the present disclosure. In these embodiments, the subscription data acquisition sub-process includes steps 51 to 54 in Figure 5 and steps 55b to 59b in Figure 7. Since steps 51 to 54 have been described in the foregoing embodiments, the following description mainly focuses on steps 55b to 59b.

[0140] Step 55b: The UDM in the network to be accessed compares the home network identifier of the AIoT terminal with the identifier of the network to be accessed to determine that the subscription data is located in the third-party operator network.

[0141] If the UDM device determines that the location information table does not contain the address information of the third-party server corresponding to the identifier of the AIoT terminal to be accessed, it proceeds to step 55b. In step 55b, the UDM device obtains the home network identifier of the AIoT terminal to be accessed from the subscription data acquisition request, and then compares the home network identifier with the identifier of the network to be accessed. If the comparison result is different, it is determined that the subscription data of the AIoT terminal to be accessed is located in the third-party operator network indicated by the home network identifier.

[0142] Step 56b: The UDM in the operator network to be accessed sends the storage location indication information to the AMF or AIoTMF in the operator network to be accessed.

[0143] The storage location indication information is used to indicate that the subscription data of the AIoT terminal to be connected is located in a third-party operator. In some examples, this storage location indication information includes the home network identifier of the AIoT terminal.

[0144] Step 57b: The AMF or AIoTMF in the network to be accessed sends a data acquisition request to the UDM in the third-party network.

[0145] After receiving the storage location indication information, the AMF or AIoTMF device in the operator's network to be connected sends a data acquisition request to the UDM device in the third-party operator's network. This data acquisition request carries the identifier of the AIoT terminal to be connected.

[0146] In some examples, AMF or AIoTMF devices in the network to be accessed by the operator access the UDM devices in the third-party operator network through the Security Edge Protection Proxy (SEPP).

[0147] Step 58b: The UDM in the third-party operator network queries the subscription data of the AIoT terminal and requests the local AMF or AIoTMF to provide the historical service data or access information of the AIoT terminal.

[0148] The UDM device in the third-party operator's network queries the subscription data of the AIoT terminal to be connected from other devices (such as the UDM device) within that network, based on the identifier of the AIoT terminal to be connected. Additionally, the UDM device queries the historical service data or historical access information of the AIoT terminal from the AMF or AIoTMF devices within the same third-party operator's network, also based on the identifier of the AIoT terminal to be connected. This historical service data or historical access information can be used for subsequent network services such as mobility management.

[0149] Step 59b: The UDM in the third-party operator network sends the subscription data of the AIoT terminal, as well as the historical service data or access information of the AIoT terminal, to the AMF or AIoTMF in the operator network to be accessed.

[0150] The UDM device will send the information it obtains from the third-party operator's network to the AMF device or AIoTMF device in the network of the operator to be accessed, so that the AMF device or AIoTMF device can perform network access authentication for the AIoT terminal to be accessed based on this information.

[0151] In this embodiment of the disclosure, the above steps can effectively locate and obtain the subscription data of the AIoT terminal, especially realizing the data location and acquisition function for the storage scenario where the subscription data is stored in the network of a third-party operator, thereby facilitating the subsequent access authentication of the AIoT terminal and the provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0152] Figure 8 is a schematic diagram of a subscription data acquisition sub-process in a communication method according to some embodiments of the present disclosure. In these embodiments, the subscription data acquisition sub-process includes steps 51 to 54 in Figure 5 and steps 55c to 58c in Figure 8. Since steps 51 to 54 have been described in the foregoing embodiments, the following description mainly focuses on steps 55c to 58c.

[0153] Step 55c: UDM looks up the table to determine that the AIoT subscription data is located on a third-party server of the SNPN class.

[0154] In this embodiment, the UDM device, AMF device, and AIoTMF device are all devices in the operator's network to be accessed. If the location information table contains information about a third-party server corresponding to the terminal to be accessed in the AIoT network, and that third-party server is of the SNPN class, then the subscription data is determined to be located on a third-party server of the SNPN class.

[0155] Step 56c: UDM sends the storage location indication information to AMF or AIoTMF.

[0156] The storage location information may include the address information and deployment type information of the third-party server.

[0157] Step 57c: AMF or AIoTMF sends a data acquisition request to a third-party server via NSSAAF.

[0158] When the deployment type of the third-party server is SNPN, the AMF device or AIoTMF device can forward data acquisition requests to the third-party server through the Network Slice-Specific Authentication and Authorization Function (NSSAAF) device selected by the network slice.

[0159] It should be noted that Figure 8 is only an exemplary process. In real-world applications, since there are many specific deployment types of SNPN, whether or not it is necessary to use an NSSAAF device to locate a third-party server needs to be determined based on the actual situation.

[0160] Step 58c: The third-party server provides AIoT subscription data to AMF or AIoTMF through NSSAAF.

[0161] In this embodiment of the disclosure, the above steps can effectively locate and obtain the subscription data of the AIoT terminal, especially realizing the data location and acquisition function for the storage scenario where the subscription data is stored on a third-party server of the SNPN type. This facilitates the subsequent access authentication of the AIoT terminal and the provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0162] Figure 9 is a schematic diagram of a subscription data acquisition sub-process in a communication method according to some embodiments of the present disclosure. In these embodiments, the subscription data acquisition sub-process includes steps 51 to 54 in Figure 5 and steps 55d to 58d in Figure 7. Since steps 51 to 54 have been described in the foregoing embodiments, the following description mainly focuses on steps 55d to 58d.

[0163] Step 55d: UDM looks up the table to determine that the subscription data of the AIoT terminal is located on a third-party server that is not of the SNPN type.

[0164] If the location information table contains information about a third-party server corresponding to the terminal to be connected to AIoT, and the third-party server is not of the SNPN class, then the subscription data is determined to be located on a third-party server of the non-SNPN class.

[0165] Non-SNPN types can also be called ordinary application types. For example, a non-SNPN type third-party server is a server in a data network.

[0166] Step 56d: UDM sends the storage location indication information to AMF or AIoTMF.

[0167] Step 57d: AMF or AIoTMF sends a data acquisition request to a third-party server via NEF.

[0168] In some examples, after receiving a data acquisition request from an AMF or AIoTMF device, the NEF device directly forwards the request to a third-party server. In other examples, the NEF device may also verify the data acquisition request based on its pre-stored AF subscription and authorization information. Only after successful verification is the data acquisition request forwarded to the third-party server.

[0169] Step 58d: The third-party server provides AIoT subscription data to AMF or AIoTMF through NEF.

[0170] In this step, in addition to providing the subscription data of the AIoT terminal to be connected to the AMF device or AIoTMF device, the third-party server can also provide it with the historical service information or historical access information of the AIoT terminal to be connected.

[0171] In this embodiment of the disclosure, the above steps can effectively locate and obtain the subscription data of the AIoT terminal. In particular, it realizes the data location and acquisition function for the storage scenario where the subscription data is stored on a third-party server that is not of the SNPN type. This facilitates the subsequent access authentication of the AIoT terminal and the provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0172] Figure 10 is a schematic diagram of a communication device according to some embodiments of the present disclosure. In these embodiments, the communication device 100 is disposed in a first core network device and is used to perform the communication method as described above, including a receiving module 101, a determining module 102, and a sending module 103.

[0173] The receiving module 101 is configured to receive a subscription data acquisition request for the AIoT terminal to be accessed from the second core network device. The acquisition request carries the identifier of the AIoT terminal to be accessed. The second core network device and the first core network device are located in the network of the operator to be accessed.

[0174] The determination module 102 is configured to determine the storage location of the subscription data of the AIoT terminal to be connected based on the identifier of the AIoT terminal to be connected and a pre-stored location information table of AIoT subscription data.

[0175] The sending module 103 is configured to send the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device.

[0176] In this embodiment of the disclosure, the above-mentioned device can effectively locate and obtain the subscription data of the AIoT terminal, thereby facilitating subsequent access authentication of the AIoT terminal and provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0177] Figure 11 is a schematic diagram of a communication device according to some embodiments of the present disclosure. As shown in Figure 11, the communication device 110 includes a memory 111 and a processor 112 coupled to the memory 111. The memory 111 is used to store instructions for executing embodiments of the communication method. The processor 112 is configured to execute the communication method in any of the embodiments of the present disclosure based on the instructions stored in the memory 111.

[0178] Figure 12 is a schematic diagram of a communication system according to some embodiments of the present disclosure. As shown in Figure 12, the communication system includes a first core network device 121 and a second core network device 122.

[0179] The first core network device 121 includes the communication device as described above.

[0180] The second core network device 122 is configured to: send a request to the first core network device 121 for obtaining subscription data of the AIoT terminal to be accessed; receive an indication of the storage location from the first core network device 121 or obtain the subscription data of the AIoT terminal to be accessed from the storage location; and, upon receiving the indication of the storage location, obtain the subscription data of the AIoT terminal to be accessed from the storage location according to the indication of the storage location.

[0181] In some embodiments, the second core network device uses different methods to obtain the subscription data depending on the storage location of the subscription data. The following describes the steps of the second core network device in obtaining subscription data using three exemplary methods.

[0182] In the first exemplary approach, the subscription data is stored on a third-party server. In this exemplary approach, the second core network device 122 receives information from the third-party server from the first core network device and obtains the subscription data of the AIoT terminal to be connected accordingly.

[0183] Furthermore, in the above exemplary method, the second core network device 122 can obtain the subscription data of the AIoT terminal to be accessed in the following exemplary manner: when the third-party server is deployed as a server in an independent non-public network (SNPN), a data acquisition request is sent to the third-party server through the authentication and authorization function device selected by the network slicing to obtain the subscription data from the third-party server; when the third-party server is deployed as a server in a data network, a data acquisition request is sent to the third-party server through the network open function device to obtain the subscription data from the third-party server.

[0184] In the second exemplary approach, the subscription data is stored in the network of the operator to be accessed. In this exemplary approach, the second core network device 122 receives the subscription data of the AIoT terminal to be accessed from the first core network device.

[0185] In the third exemplary approach, the storage location of the subscription data is the third-party operator network indicated by the home network identifier of the AIoT terminal to be accessed. In this exemplary approach, the second core network device 122 receives information from the third-party operator network from the first core network device 121; sends a data acquisition request to a device in the third-party operator network; and receives the subscription data of the AIoT terminal to be accessed returned by the device in the third-party operator network.

[0186] In practical network access authentication scenarios, the second core network device 122 can also be configured to: receive a network access request for the AIoT terminal to be accessed from the wireless reader before sending a subscription data acquisition request to the first core network device; and, after acquiring the subscription data of the AIoT terminal to be accessed, perform network access authentication on the AIoT terminal to be accessed based on the subscription data. Furthermore, the communication system may also include a service operation support device. This device is configured to deploy a location information table of the AIoT subscription data to the first core network device.

[0187] In this embodiment of the disclosure, the above system can effectively locate and obtain the subscription data of AIoT terminals, thereby facilitating subsequent access authentication of AIoT terminals and provision of corresponding network access services based on the subscription data of AIoT terminals.

[0188] Figure 13 is a schematic diagram of the structure of a communication system according to some other embodiments of the present disclosure. As shown in Figure 13, the communication system includes an AIoT terminal 131, a wireless reader / writer 132, and devices in a service operator network. The devices in the service operator network include an AMF (or AIoTMF) 133 and a UDM 134.

[0189] AIoT terminal 131 stores the identification data of the AIoT terminal. This identification data can be the data shown in Figure 6.

[0190] The wireless reader 132 includes two types: a UE reader and a base station reader. The wireless reader 132 is mainly used to read the identification data of the AIoT terminal 131 and send the access request carrying the identification data of the AIoT terminal to the AMF (or AIoTMF) 133.

[0191] AMF (or AIoTMF) 133 is primarily responsible for working with UDM 134 to execute the subscription data acquisition and network access authentication process for AIoT terminals. UDM 134 is primarily responsible for working with AMF (or AIoTMF) 133 to execute the subscription data location and acquisition process.

[0192] The subscription data location and acquisition process for AIoT terminals includes three scenarios. In the first scenario, the subscription data is stored on a third-party server. Depending on the deployment type of the third-party server, this scenario can be further divided into two types: SNPN deployment and standard application service deployment. In the SNPN deployment scenario, AMF (or AIoTMF) 133 can obtain the AIoT terminal's subscription data from the third-party server (SNPN) 138 via NSSAAF 137. In the standard application service deployment scenario, AMF (or AIoTMF) 133 can obtain the AIoT terminal's subscription data from the third-party server (standard) 136 via NEF 135.

[0193] In the second scenario, the subscription data is stored locally, meaning it is stored on the service operator's network. In this case, the AMF (or AIoTMF) 133 obtains the AIoT terminal's subscription data from the UDM 134.

[0194] In the third scenario, the subscription data is stored in a roaming location, meaning the subscription data is stored in the home operator's network of the AIoT terminal. In this case, the AMF (or AIoTMF) 133 obtains the AIoT terminal's subscription data from the UDM 140 in the home operator's network via SEPP 139. Furthermore, the AMF (or AIoTMF) 133 can also obtain the AIoT terminal's historical service data or historical access information from the AMF (or AIoTMF) 141 in the home operator's network.

[0195] In this embodiment of the disclosure, the various devices in the communication system cooperate with each other to effectively locate and obtain the subscription data of the AIoT terminal, thereby facilitating the subsequent access authentication of the AIoT terminal and the provision of corresponding network access services based on the subscription data of the AIoT terminal.

[0196] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0197] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0198] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0199] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0200] The communication methods, apparatus, and systems according to this disclosure have now been described in detail. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art can fully understand how to implement the technical solutions disclosed herein based on the above description.

Claims

1. A communication method, executed by a first core network device, comprising: The second core network device receives a subscription data acquisition request for a passive AIoT terminal to be connected, the acquisition request carrying the identifier of the AIoT terminal to be connected, and the second core network device and the first core network device are located in the network of the operator to be connected; Based on the identifier of the AIoT terminal to be connected and the location information table of the pre-stored AIoT subscription data, the storage location of the subscription data of the AIoT terminal to be connected is determined; The storage location indication information or the subscription data of the AIoT terminal to be connected obtained from the storage location is sent to the second core network device.

2. The communication method according to claim 1, wherein, The location information table of the AIoT subscription data includes the correspondence between the identifier of the AIoT terminal and the information of the third-party server, which is used to store the subscription data of the AIoT terminal.

3. The communication method according to claim 2, wherein, The step of determining the storage location of the subscription data of the AIoT terminal to be connected, based on the identifier of the AIoT terminal to be connected and the pre-stored location information table of AIoT subscription data, includes: Based on the identifier of the AIoT terminal to be connected, query the location information table of the AIoT subscription data; If the location information table of the AIoT subscription data contains information about the third-party server corresponding to the identifier of the AIoT terminal to be accessed, the third-party server corresponding to the identifier of the AIoT terminal to be accessed shall be used as the storage location of the subscription data of the AIoT terminal to be accessed.

4. The communication method according to claim 3, wherein, Sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device includes: In the case where the storage location is a third-party server, the information of the third-party server is sent to the second core network device as an indication of the storage location, so that the second core network device can obtain the subscription data of the AIoT terminal to be accessed from the third-party server according to the information of the third-party server.

5. The communication method according to claim 3 or 4, wherein, The acquisition request also carries the home network identifier of the AIoT terminal to be connected. Determining the storage location of the subscription data of the AIoT terminal to be connected based on the identifier of the AIoT terminal to be connected and a pre-stored location information table of AIoT subscription data further includes: If the location information table of the AIoT subscription data does not contain information about the third-party server corresponding to the identifier of the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is the same as the identifier of the operator network to be accessed, then the operator network to be accessed will be used as the storage location of the subscription data of the AIoT terminal to be accessed.

6. The communication method according to claim 5, wherein, The step of sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device further includes: If the storage location is the network of the operator to be accessed, the subscription data of the AIoT terminal to be accessed, obtained from the network of the operator to be accessed, will be sent to the second core network device.

7. The communication method according to any one of claims 3 to 6, wherein The acquisition request also carries the home network identifier of the AIoT terminal to be connected. Determining the storage location of the subscription data of the AIoT terminal to be connected based on the identifier of the AIoT terminal to be connected and a pre-stored location information table of AIoT subscription data further includes: If the location information table of the AIoT subscription data does not contain information about the third-party server corresponding to the identifier of the AIoT terminal to be accessed, and the home network identifier of the AIoT terminal to be accessed is different from the identifier of the operator network to be accessed, the third-party operator network indicated by the home network identifier shall be used as the storage location of the subscription data of the AIoT terminal to be accessed.

8. The communication method according to claim 7, wherein The step of sending the indication information of the storage location or the subscription data of the AIoT terminal to be accessed obtained from the storage location to the second core network device further includes: In the case where the storage location is a third-party operator network indicated by the home network identifier, the information of the third-party operator network is sent to the second core network device as indication information of the storage location, so that the second core network device can obtain the subscription data of the AIoT terminal to be accessed from the third-party operator network according to the information of the third-party operator network.

9. The communication method according to any one of claims 2 to 8, wherein The identifier of the AIoT terminal in the location information table of the AIoT subscription data is either the unique identifier of the AIoT terminal or the identifier of the group to which the AIoT terminal belongs.

10. The communication method according to claim 9, wherein The identifier of the group to which the AIoT terminal belongs includes the identifier of the manufacturer to which the AIoT terminal belongs, or the identifier of the application to which the AIoT terminal belongs.

11. The communication method according to any one of claims 4 to 10, wherein The location information table for the AIoT subscription data includes the address information of the third-party server.

12. The communication method according to claim 11, wherein, The location information table of the AIoT subscription data also includes information about the deployment type of the third-party server. Sending the information of the third-party server as an indication of the storage location to the second core network device includes: The address information and deployment type information of the third-party server are sent to the second core network device.

13. The communication method according to claim 12, wherein, The third-party server is deployed as a standalone server in a non-public network (SNPN) or a server in a data network.

14. The communication method according to any one of claims 1 to 13, wherein The first core network device is a unified data management (UDM) device, and the second core network device is a passive Internet of Things (AIoTMF) device or an access and mobility management (AMF) device.

15. A communication device, disposed in a first core network device, comprising: A module for performing the communication method as described in any one of claims 1 to 14.

16. A communication device, disposed in a first core network device, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the communication method as described in any one of claims 1 to 14 based on instructions stored in the memory.

17. A communication system, comprising: The first core network equipment includes the communication device as described in claim 15 or 16; The second core network device is configured as follows: Send a subscription data acquisition request for the AIoT terminal to be connected to the first core network device; Receive storage location indication information from the first core network device or subscription data of the AIoT terminal to be accessed obtained from the storage location; as well as Upon receiving the indication information of the storage location, the subscription data of the AIoT terminal to be connected is obtained from the storage location according to the indication information of the storage location.

18. The communication system of claim 17, wherein, The storage location indication information is information from a third-party server. The second core network device receives the storage location indication information from the first core network device or obtains the subscription data of the AIoT terminal to be accessed from the storage location, including: receiving the information from the third-party server from the first core network device. The second core network device obtains the subscription data of the AIoT terminal to be accessed from the storage location according to the indication information of the storage location, including: In the case where the deployment type of the third-party server is a server in an independent non-public network SNPN, the authentication and authorization function device selected through network slicing sends a data acquisition request to the third-party server in order to obtain the subscription data of the AIoT terminal to be accessed from the third-party server; When the deployment type of the third-party server is a server in a data network, a data acquisition request is sent to the third-party server through a network open function device to obtain the subscription data of the AIoT terminal to be connected from the third-party server.

19. The communication system of claim 17, wherein, The second core network device receives storage location indication information from the first core network device or subscription data of the AIoT terminal to be accessed from the storage location, including: Receive subscription data from the AIoT terminal to be connected from the first core network device.

20. The communication system of claim 17, wherein, The storage location indication information is the information of the third-party operator network indicated by the home network identifier of the AIoT terminal to be accessed. The second core network device receives the storage location indication information from the first core network device or obtains the subscription data of the AIoT terminal to be accessed from the storage location, including: receiving the information of the third-party operator network from the first core network device. The second core network device obtains the subscription data of the AIoT terminal to be accessed from the storage location according to the indication information of the storage location, including: Send a data acquisition request to the device in the third-party operator's network; Receive subscription data of the AIoT terminal to be connected from the device in the third-party operator network.

21. The communication system according to any one of claims 17 to 20, wherein, The second core network device is also configured as follows: Before sending a subscription data acquisition request for the AIoT terminal to be connected to the first core network device, the device receives a network access request for the AIoT terminal to be connected from the wireless reader / writer. After obtaining the subscription data of the AIoT terminal to be connected, network access authentication is performed on the AIoT terminal to be connected based on the subscription data.

22. The communication system according to any one of claims 17 to 20, further comprising: The business operation support equipment is configured to deploy the location information table of the AIoT subscription data to the first core network equipment.

23. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the communication method as described in any one of claims 1 to 14.

24. A computer program product having stored computer instructions thereon, which, when executed by a processor, implement the communication method as described in any one of claims 1 to 14.

25. A computer program comprising: Instructions, which, when executed by a processor, cause the processor to perform the communication method according to any one of claims 1 to 14.

Images