Communication method, communication apparatus, and communication system

By sending connection establishment requests and performing security verification to multiple AIoT devices through the terminal device, the problem of low connection efficiency between the reader and AIoT devices is solved, and efficient and secure data transmission is achieved.

WO2026152982A1PCT designated stage Publication Date: 2026-07-23HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
HONOR DEVICE CO LTD
Filing Date
2025-12-15
Publication Date
2026-07-23

AI Technical Summary

Technical Problem

How to securely connect readers to multiple AIoT devices to aggregate and transmit data is a problem that urgently needs to be solved.

Method used

By receiving request messages from the first network element through the terminal device, sending connection establishment requests to multiple AIoT devices, and performing security verification, simultaneous connection with multiple AIoT devices can be achieved.

Benefits of technology

It improves the efficiency of establishing connections between terminal devices and multiple AIoT devices, reduces device power consumption, and enhances the security and integrity of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025142386_23072026_PF_FP_ABST
    Figure CN2025142386_23072026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and provides a communication method, a communication apparatus, and a communication system. A first network element sends a first request message to a terminal device, such that the terminal device simultaneously establishes connections with multiple ambient Internet of Things (AIoT) devices. The communication method comprises: after a terminal device receives, from a first network element, a first request message for requesting the terminal device to establish connections with multiple AIoT devices, the terminal device respectively sends, on the basis of the first request message, connection establishment requests to the multiple AIoT devices, so as to request simultaneous establishment of connections with the multiple AIoT devices.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, communication devices and communication systems

[0001] This application claims priority to Chinese Patent Application No. 202510088305.0, filed on January 20, 2025, entitled "Communication Method, Communication Device and Communication System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, communication device and communication system. Background Technology

[0003] As an intermediate node in the ambient internet of things (AIoT) devices, the reader can aggregate data from multiple AIoT devices, such as inventory information and read / write control commands, and transmit the aggregated data from multiple AIoT devices to network devices and / or servers, thereby enabling network devices and / or servers to obtain the data from the AIoT devices.

[0004] Before a reader can aggregate and transmit data from multiple AIoT devices, it needs to discover and establish connections with these devices. However, how the reader can establish secure connections with the AIoT devices that require its services is a problem that urgently needs to be solved. Summary of the Invention

[0005] This application provides a communication method, communication device, and communication system. A first request message is sent to a terminal device through a first network element, requesting the terminal device to establish a connection with multiple AIoT devices, thereby enabling the terminal device to establish a connection with multiple AIoT devices simultaneously and improving the efficiency of establishing a connection between the terminal device and multiple AIoT devices.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, this application provides a communication method applied to a terminal device, which may include:

[0008] After receiving the first request message from the first network element, the terminal device sends connection establishment requests to multiple AIoT devices respectively according to the first request message.

[0009] The first request message is used to request the terminal device to establish a connection with multiple AIoT devices; the connection establishment request is used to request to establish a connection with AIoT devices.

[0010] In this implementation, the terminal device simultaneously sends connection establishment requests to multiple AIoT devices to establish connections with multiple devices that send connection establishment requests at the same time. This improves the efficiency of establishing connections between the terminal device and multiple AIoT devices and further reduces device power consumption.

[0011] In one possible implementation of the first aspect, the first request message includes security verification information; wherein the security verification information is used for security verification between the terminal device and multiple AIoT devices.

[0012] In this implementation, security verification is performed during the connection establishment process between the terminal device and multiple AIoT devices, which not only improves the security of AIoT devices, but also enhances the security and integrity of data transmission between the terminal device and multiple AIoT devices.

[0013] In another possible implementation of the first aspect, after receiving the first request message from the first network element, the method further includes:

[0014] Send a first response message to the first network element. The first response message is used to instruct the first network element to retransmit the first request message.

[0015] In this implementation, the terminal device sends a first response message to the first network element to instruct the first network element to retransmit the first request message to the terminal device. After the terminal device receives the first request message again, it attempts to establish a connection with multiple AIoT devices again, ensuring that the terminal device successfully establishes a connection with multiple AIoT devices.

[0016] In another possible implementation of the first aspect, sending a first response message to the first network element includes:

[0017] If the terminal device does not receive an end instruction, it sends a first response message to the first network element; wherein the end instruction is used to indicate that the first request information has been sent.

[0018] In this implementation, if the terminal device does not receive an end instruction, it means that the terminal device has not completely received the first request message sent by the first network element. The terminal device instructs the first network element to retransmit the first request message, thus avoiding the situation where the terminal device does not completely receive the first request message due to accidental reasons such as network disconnection between the first network element and the terminal device.

[0019] In another possible implementation of the first aspect, sending a first response message to the first network element includes:

[0020] If a terminal device fails to establish a connection with multiple AIoT devices, the terminal device sends a first response message to the first network element.

[0021] In this implementation, after the terminal device fails to establish a connection with multiple AIoT devices, it sends a first response message to the first network element to instruct the first network element to retransmit the first request information. This allows the terminal device to attempt to establish a connection with the multiple AIoT devices again, ensuring a successful connection between the terminal device and the multiple AIoT devices.

[0022] In another possible implementation of the first aspect, after sending connection establishment requests to multiple AIoT devices respectively, the method further includes:

[0023] The terminal device sends a second response message to the first network element. The second response message is used to indicate the AIoT device list, which includes the identification information of the AIoT devices that have successfully established a connection with the terminal device.

[0024] In this implementation, after the terminal device establishes a connection with multiple AIoT devices, the terminal device feeds back the identification information of the successfully connected AIoT devices to the first network element, so that the first network element can determine whether the terminal device has successfully connected with multiple AIoT devices at the same time.

[0025] In this implementation, the terminal device is the device that corresponds to the preset identification information among multiple terminal devices within the management scope of the first network element; or, the terminal device is the device among multiple terminal devices within the management scope of the first network element that is associated with multiple AIoT devices and whose distance from each AIoT device is less than a preset distance.

[0026] Secondly, this application provides a communication method applied to a first network element of a network device, the method including:

[0027] After receiving the second request message, the first network element sends a first request message to the terminal device according to the second request message.

[0028] The second request message is used to request data information from multiple environmental AIoT devices; the first request message is used to request the terminal device to establish a connection with multiple AIoT devices.

[0029] In this implementation, after the first network element determines the multiple AIoT devices for which data information is to be acquired, it sends a first request message to the terminal device to instruct the terminal device to establish a connection with the multiple AIoT devices, thereby enabling the terminal device to successfully establish a connection with multiple AIoT devices simultaneously and improving the efficiency of establishing a connection between the terminal device and multiple AIoT devices.

[0030] In one possible implementation of the second aspect, the first request message includes security verification information; wherein the security verification information is used for security verification between the terminal device and multiple AIoT devices.

[0031] In this implementation, when a terminal device establishes a connection with multiple AIoT devices, it uses security verification information for security verification, which improves the security of establishing a connection between the terminal device and multiple AIoT devices and ensures the security of subsequent data transmission.

[0032] In another possible implementation of the second aspect, the communication method may further include:

[0033] The first network element sends an end indication to the terminal device; wherein, the end indication is used to indicate that the first request message has been sent.

[0034] In this implementation, the end instruction is sent after the first request message is sent, and the end instruction and the first request message are either the same message or two separate messages.

[0035] In this implementation, after the first network element sends the first request message to the terminal device, it sends an end indication to indicate that the first request message has been sent. This avoids the situation where the terminal device cannot determine whether it has completely received the first request message, and ensures that the terminal device receives the complete first request message.

[0036] In another possible implementation of the second aspect, after sending the first request message to the terminal device, the method further includes:

[0037] The first network element receives a first response message from the terminal device; wherein the first response message is used to instruct the first network element to retransmit the first request message; according to the first response message, if the number of times the first request message is sent is less than a preset threshold, the first request message is retransmitted to the terminal device.

[0038] In this implementation, if the number of times the first network element sends the first request message to the terminal device does not reach a preset threshold, the first network element can retransmit the first request message to the terminal device. This avoids the situation where the terminal device fails to receive the first request message completely due to accidental reasons such as network disconnection between the first network element and the terminal device, thus preventing the terminal device from failing to connect with multiple AIoT devices.

[0039] In another possible implementation of the second aspect, after sending the first request message to the terminal device, the method further includes:

[0040] The first network element receives a second response message from the terminal device. The second response message is used to indicate an AIoT device list, which includes the identification information of AIoT devices that have successfully established a connection with the terminal device. If the identification information of the AIoT devices included in the AIoT device list is not completely the same as the identification information corresponding to multiple AIoT devices, and the number of times the first request message is sent is less than a preset threshold, the first network element retransmits the first request message to the terminal device.

[0041] In this implementation, if the first network element determines that the terminal device has not successfully established a connection with multiple AIoT devices and the number of times the first request message has been sent is less than a preset threshold, the first network element can retransmit the first request message to the terminal device to instruct the terminal device to try to establish a connection with multiple AIoT devices again, thus ensuring that the terminal device successfully establishes a connection with multiple AIoT devices.

[0042] In another possible implementation of the second aspect, the terminal device is the device that corresponds to the preset identification information among multiple terminal devices within the management scope of the first network element, or the terminal device is a device that is associated with multiple terminal device network devices within the management scope of the first network element and multiple AIoT devices, and the distance from each AIoT device is less than a preset distance.

[0043] In this implementation, the network device can instruct a preset terminal device to establish a connection with multiple AIoT devices to request data information from the multiple AIoT devices. Alternatively, the network device can dynamically select a terminal device from multiple terminal devices, improving the flexibility and accuracy of establishing connections between the terminal device and multiple AIoT devices.

[0044] In another possible implementation of the second aspect, before obtaining the first request message, the method further includes:

[0045] The first network element receives first information from multiple terminal devices; wherein, the first information of each terminal device is used to indicate the read and write capabilities of the terminal device and the AIoT devices associated with the terminal device.

[0046] In this implementation, after the first network element receives the first information from multiple terminal devices, the first network element can determine that the terminal devices and the AIoT devices associated with the terminal devices have been deployed. In this way, when the network device obtains data information from multiple AIoT devices, the network device can instruct the terminal device to establish a connection with multiple AIoT devices after determining the terminal device, so as to obtain data information from multiple AIoT devices through the terminal device.

[0047] In another possible implementation of the second aspect, before the network device receives the second request message, the method further includes: receiving the second request message from the application function network element via the second network element.

[0048] In another possible implementation of the second aspect, the second network element receives a second request message from the application function network element, including:

[0049] If the second network element successfully authenticates the application function network element, it receives a second request message from the application function network element.

[0050] In this implementation, the second network element authenticates the application function network element, preventing unauthorized application function network elements from obtaining data information from multiple AIoT devices, thereby improving the security of multiple AIoT devices.

[0051] In another possible implementation of the second aspect, the second request message includes the location information of multiple terminal devices, and the first network element is determined based on the tracking area (TA) list or cell identifier information of the multiple terminal devices.

[0052] In this implementation, the network device can determine the first network element serving multiple terminal devices by using the TA list or cell identification information of multiple terminal devices.

[0053] Thirdly, this application provides a communication device, including one or more processors, a memory, and a computer program stored in the memory, wherein the processor executes the computer program to implement the communication method described in the above embodiments.

[0054] Fourthly, this application provides a communication system, which includes a first network element and a terminal device.

[0055] The terminal device is used to execute the method described in the first aspect above, and the first network element is used to execute the method described in the second aspect above.

[0056] Fifthly, this application provides a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implements the communication method described in the above embodiments.

[0057] Sixthly, this application provides a chip system including a memory and a processor, wherein a program / instruction stored in the memory is executed by the processor to implement the communication method described in the above embodiments.

[0058] In a seventh aspect, this application provides a computer program product, which includes a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in the above embodiments.

[0059] Understandably, the communication device described in the third aspect, the communication system described in the fourth aspect, the computer-readable storage medium described in the fifth aspect, the chip system described in the sixth aspect, and the computer program product described in the seventh aspect are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0060] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0061] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0062] Figure 3 is a schematic diagram of the architecture of a network device provided in an embodiment of this application;

[0063] Figure 4 is a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0064] Figure 5 is a schematic diagram of the interaction flow of another communication method provided in an embodiment of this application;

[0065] Figure 6 is an example diagram of sending a first request message and an end indication provided in an embodiment of this application;

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

[0067] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application;

[0068] Figure 9 is a schematic diagram of another communication device provided in an embodiment of this application;

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

[0070] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the term "and / or" in this document 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, and B existing alone.

[0071] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this application, unless otherwise stated, "a plurality of" means two or more.

[0072] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0073] Exemplary embodiments of this application provide a communication method and a communication system. The communication method of this application embodiment can be applied to a communication system.

[0074] The communication system may include, but is not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or New Radio (NR) systems, 5.5G systems or 6th Generation (6G) systems, and future mobile communication systems; Vehicle-to-X (V2X), where V2X can include Vehicle-to-Network (V2N), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Pedestrian (V2P), etc.; Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V) communication; Vehicle-to-Everything (V2X) communication; Machine-Type Communication (MTC); Internet of Things (IoT); and Long Term Evolution-Vehicle (LTE-V) technology for machine-to-machine communication. Evolution-machine (LTE-M), machine-to-machine (M2M), etc. The applicable scenarios for this communication system include, but are not limited to: terrestrial cellular communication, non-terrestrial network (NTN), satellite communication, high altitude platform station (HAPS) communication, vehicle-to-everything (V2X) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication.

[0075] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. The communication system may include: an AIoT device 10, a network device 20, and a terminal device 30.

[0076] The aforementioned AIoT device 10 is a device for inventorying assets. Assets may include hardware assets, software assets, and data assets related to the AIoT device 10, which are not limited in this embodiment. In some embodiments, hardware assets may be the brand, model, quantity, or usage status of sensors, etc., which are not limited in this embodiment. In some embodiments, software assets may be the name, version, developer, functional description, or scope of use of application software, etc., which are not limited in this embodiment. In some embodiments, data assets may be user data of the AIoT device 10, such as user identity information, user usage habits, etc., which are not limited in this embodiment. For descriptions of some or all characteristics of the AIoT device 10, please refer to the existing standards of the 3rd Generation Partnership Project (3GPP).

[0077] It should be understood that the description of some or all of the characteristics of the AIoT device 10 described herein with reference to the existing 3GPP standards is only a possible example description, and the embodiments of this application are not limited thereto. As the communication standard protocol version evolves or is updated, some or all of the characteristics of the AIoT device 10 described herein may refer to the evolved or updated version; or some or all of the characteristics of the AIoT device 10 may also refer to the description in related technologies.

[0078] The network device 20 described above can be a device that provides wireless interface transmission services for the AIoT device 10. This application embodiment does not specifically limit the form of the network device 20.

[0079] The network device 20 can request the AIoT device 10 to report its own data information through the terminal device 30, thereby facilitating the network device 20 to manage the AIoT device 10.

[0080] As shown in Figure 1(a), network device 20 can be an access network device, such as a base station, or a core network device, such as an access and mobility management function (AMF). The base station provides various services to AIoT device 10 through a wireless interface, such as packet compression and packet transmission services.

[0081] The base station can be an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a next-generation 6G communication system, a base station in a future mobile communication system, an access point (AP) in a WiFi system, a radio controller, relay station, access point, vehicle-mounted equipment, wearable device, or network equipment 20 in other future communication systems. Alternatively, the network equipment 20 can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU) or a distributed unit (DU). This application does not limit the specific technology or equipment form used in the network equipment 20.

[0082] In some embodiments, the terminal device 30 can read the data information of the AIoT device 10 and send the data information to the network device 20, thereby enabling the network device 20 to obtain the data information of the AIoT device 10.

[0083] The terminal equipment involved in this application may be a device with wireless transceiver capabilities or a chip or chip system that can be installed in the device, which allows users to access the network and is a device used to provide voice and / or data connectivity to users. The terminal equipment may also be referred to as user equipment (UE), subscriber unit, terminal, mobile station (MS), or mobile terminal (MT), etc.

[0084] In other embodiments, the terminal device 30 may be the AIoT-radio access network (A-RAN) of the AIoT device 10. The A-RAN can read the data information of the AIoT device 10 and send the data to the network device 20, thereby enabling the network device 20 to obtain the data information of the AIoT device 10.

[0085] A-RAN can be an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a next-generation 6G communication system, a base station in a future mobile communication system, an access point (AP) in a WiFi system, a radio controller, relay station, access point, vehicle-mounted equipment, wearable devices, or network equipment in other future communication systems. For example, A-RAN can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU) or a distributed unit (DU). This application does not limit the specific technology or equipment form used in the intermediate nodes.

[0086] In other embodiments, the terminal device 30 may include a UE and an A-RAN. The UE can read the data information of the AIoT device 10 and send the data information to the A-RAN. After receiving the data information of the AIoT device 10 sent by the UE, the A-RAN sends the data information to the base station, thereby enabling the base station to obtain the data information of the AIoT device 10.

[0087] Optionally, in some embodiments, the transmission channel between the terminal device 30 and the AIoT device 10 may include a physical reader-to-device channel (PRDCH) and a physical device-to-reader channel (PDRCH).

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

[0089] In another possible topology, as shown in Figure 1(b), the communication system provided in this embodiment may include: an AIoT device 10, a network device 20, and a terminal device 30. The network device 20 communicates with the terminal device 30 via a wireless interface to provide paging services for the AIoT device 10. After the network device 20 pages the AIoT device 10, data information can be directly transmitted between the network device 20 and the AIoT device 10.

[0090] It should be understood that the topology shown in Figure 1 is merely an example description, and the embodiments of this application are not limited thereto. It should also be understood that the number of AIoT devices 10 or network devices 20 shown in Figure 1 is also merely an exemplary description, and the embodiments of this application are not limited thereto. For example, the number of AIoT devices 10 may be 5, 10, etc.

[0091] For example, as shown in Figure 2(a), the topology may also include: AIoT device 10 and network device 20, and data information can be transmitted between AIoT device 10 and network device 20.

[0092] In another possible topology, as shown in Figure 2(b), the UE directly provides various services to the AIoT device 10 via a wireless interface. Additionally, in a topology including the UE, the UE can communicate with the base station; embodiments of this application can also be applied to communication between the UE and the base station.

[0093] The aforementioned network device may include multiple network elements, which can exchange information through interfaces. The following section uses a network device comprising a first network element, a second network element, a third network element, a fourth network element, a fifth network element, and a sixth network element as an example to detail the network device architecture.

[0094] For example, Figure 3 is a schematic diagram of the architecture of a network device provided in an embodiment of this application. As shown in Figure 3, the first network element communicates with other network elements through interface Namf, the second network element communicates with other network elements through interface Nnef, the third network element communicates with other network elements through interface Naf, the fourth network element communicates with other network elements through interface Nudm, the fifth network element communicates with other network elements through interface Nnrf, and the sixth network element communicates with other network elements through interface Nausf. In addition, the second network element can also communicate with terminal devices through interfaces.

[0095] In some embodiments, assuming the terminal device is a UE, the first network element communicates with the UE through the N1 interface. In other embodiments, assuming the terminal device is a RAN, the first network element communicates with the RAN through the N2 interface. In still other embodiments, the terminal device includes both a UE and a RAN, the first network element communicates with the RAN through the N2 interface, and the RAN then communicates with the UE.

[0096] It should be understood that the types and number of network elements of the network device shown in Figure 3 are only an exemplary description. The network device may also include other network elements (not shown in Figure 3), and there may be multiple first, second, third, fourth, fifth, or sixth network elements. This application embodiment does not limit this.

[0097] The first network element can be responsible for the access and mobility management of terminal devices in the mobile network, such as the registration management of terminal devices. In some embodiments, the first network element can be an access point and an AMF (Access Module). In other embodiments, the first network element can be an ambient internet of things network function (AIOT-NF). The AIOT-NF can be set separately from the AMF in the network device, or it can be integrated into the AMF; this application does not limit this.

[0098] AMF / AIoTNF can collect and manage device data from AIoT devices, discover and select the terminal devices required for the AIoT devices to be read, forward read requests forwarded by NEF to the terminal devices, and perform related management and coordination of the terminal devices. For example, it can send control signals to terminal devices and transmit and collect data.

[0099] The second network element can be responsible for managing the network data exposed by the network device. The second network element can be located between the network elements of the server and the network device, thereby ensuring that the server can securely access the network device. The second network element can also be located between different network elements of the network device; this application embodiment does not limit this. In some embodiments, the second network element can be a network exposure function (NEF). In other embodiments,

[0100] The second network element can be an ambient internet of things-controller (AIOT-C). The AIOT-C can be installed separately from the NEF in the network device, or it can be integrated into the NEF; this application embodiment does not limit this.

[0101] The third network element can receive requests sent by the server to the network device, and it can also send data from the network device to the server. In some embodiments, the third network element can be an application function (AF).

[0102] For example, the third network element can be the ambient internet of things application function (AIoT AF).

[0103] The fourth network element can serve as a database for user data, providing services such as user authentication, user identification, access authorization, registration, mobility, subscription, and SMS management. For example, the fourth network element can store user account opening data and contract data. In some embodiments, the fourth network element can be a unified data management (UDM) function.

[0104] The fifth network element is used to register and obtain information related to network functions. In some embodiments, the fifth network element may be a network repository function (NRF).

[0105] The sixth network element can process user authentication data and provide user authentication and authorization services to other network elements. In some embodiments, the sixth network element can be an authentication server function (AUSF).

[0106] It should be understood that the above-mentioned network elements are all network elements in existing communication networks. The above-mentioned network elements can also be other network elements with corresponding functions. The embodiments of this application only provide a brief introduction to this. The functions and applications of the above-mentioned network elements are not limited to this.

[0107] Below, this application embodiment will take the AIoT device 10 and network device 20 with the structure shown in FIG1 as examples, and, in conjunction with the accompanying drawings and application scenarios, will describe in detail the communication method provided by this application embodiment.

[0108] This method is executed by multiple AIoT devices, terminal devices, and network devices. The AIoT device can be AIoT device 10 in Figure 1 or a device in AIoT device 10. The terminal device can be terminal device 30 in Figure 1. The network device can be network device 20 in Figure 1 or a device in network device 20.

[0109] Taking the structure shown in Figure 1(a) as an example, after the first network element of network device 20 receives a second request message indicating that it needs to obtain data information from AIoT device 10, the first network element sends a first request message to terminal device 30 to request that terminal device 30 establish a connection with AIoT device 10. After receiving the first request message, terminal device 30 sends connection establishment requests to multiple AIoT devices 10 to establish a connection with AIoT devices 10. After terminal device 30 successfully establishes a connection with multiple AIoT devices 10, terminal device 30 can obtain data information from multiple AIoT devices 10 and send the data information from multiple AIoT devices 10 to network device 20.

[0110] Taking the structure shown in Figure 1(b) as an example, after the first network element of network device 20 receives a second request message indicating that it needs to obtain data information from AIoT device 10, the first network element sends a first request message to terminal device 30 to request that terminal device 30 establish a connection with AIoT device 10. After receiving the first request message, terminal device 30 sends connection establishment requests to multiple AIoT devices 10 to establish a connection with AIoT device 10, enabling network device 20 to page AIoT device 10. Subsequently, AIoT device 10 and network device 20 can directly transmit data.

[0111] For example, please refer to Figure 4, which illustrates the method as being executed by multiple AIoT devices, terminal devices, and network devices.

[0112] Figure 4 is a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application. As shown in Figure 4, the communication method provided in this embodiment of the application may include:

[0113] S401, the first network element receives the second request message.

[0114] The second request message is used to request data information from one or more AIoT devices. The data information from the AIoT devices may include information from asset inventory checks, such as querying asset stock status; the data information may also include information obtained based on read / write commands performed on the AIoT devices, such as AIoT device status information or business data information, etc., which are not limited in this embodiment.

[0115] Optionally, the first network element can be an AMF or an AIOT-NF. The second request message can be a request message initiated by the AF network element, or it can be a request message initiated by the server to obtain data information from one or more AIoT devices. This application embodiment does not limit this. For example, when the AF network element determines that it needs to obtain data information from one or more AIoT devices, the AF network element sends a request message to the first network element through the second network element.

[0116] In some embodiments, the second request message may include identification information of one or more AIoT devices. In this case, the second request message can be specifically used to request data information of the one or more AIoT devices. When the second request message includes identification information of multiple AIoT devices, the identification information of the multiple AIoT devices can be carried in the second request message in the form of a list. For example, the second request message may include an AIoT device list 1, which includes the identification information of multiple AIoT devices.

[0117] In this application, the identification information of the AIoT device can be information used to uniquely identify the AIoT device. The identification information of the AIoT device can be its media access control (MAC) address, serial number, internet protocol (IP) address, etc.

[0118] Optionally, the second request message may further include location information of one or more terminal devices. Subsequently, the first network element can determine the terminal devices that have established connections with one or more AIoT devices based on the location information of the terminal devices.

[0119] In one example, the location information of the terminal device may include the tracking area (TA) of the terminal device and / or the cell location where the terminal device is located.

[0120] In another example, the location information of the terminal device can be represented by longitude and latitude coordinates. For example, the location information of the UE terminal device is 30 degrees north latitude and 10 degrees east latitude. In other embodiments, the location information of the terminal device can be represented by a range of longitude and latitude coordinates. For example, the location information of the terminal device is the range of latitude from 30 degrees north latitude to 50 degrees north latitude and from 10 degrees east latitude to 30 degrees east latitude.

[0121] In another example, the location information of the terminal device can indicate a specific location or range through pre-negotiated information. For example, the location information of the terminal device is the eighth region, which is a predefined location range from 30 degrees north latitude to 50 degrees north latitude and from 10 degrees east latitude to 30 degrees east latitude.

[0122] Optionally, the second request message may further include security verification information. This security verification information is used to perform security verification on multiple AIoT devices. In some embodiments, the security verification information may include certificate information, token information, or key information, etc. When the terminal device subsequently establishes a connection with one or more AIoT devices, the one or more AIoT devices can perform security verification based on the specific information included in the received security verification information. The specific verification process is described in section S403 below and will not be detailed here.

[0123] Optionally, the second request message may include preset identification information, wherein the preset identification information is used to uniquely identify the terminal device that has established a connection with multiple AIoT devices.

[0124] S402, the first network element sends a first request message to the terminal device based on the second request message. Correspondingly, the terminal device receives the first request message from the first network element.

[0125] The first request message is used to request the terminal device to establish a connection with one or more AIoT devices. These one or more AIoT devices are the AIoT devices corresponding to the identification information carried in the second request message.

[0126] After receiving a second request message from the AF carrying the identification information of one or more AIoT devices, the first network element can obtain the identification information of the one or more AIoT devices carried in the second request message. The first request message sent by the first network element to the terminal device may include the identification information of the one or more AIoT devices to be connected to the terminal device.

[0127] In other embodiments, the first request message may also be used to instruct the terminal device to obtain data information from multiple AIoT devices.

[0128] In other embodiments, the first request message may also carry a threshold number of times the terminal device sends second information to multiple AIoT devices and / or periodic indication information. The periodic indication information instructs the terminal device to send request information 1 to the multiple AIoT devices at preset intervals to request data information from the multiple AIoT devices.

[0129] For example, assuming that the periodic indication information carried in the first request message indicates a preset time of 1 hour and a threshold of 5 times, after the terminal device establishes a connection with multiple AIoT devices, the terminal device sends a third request message to the multiple AIoT devices once every 1 hour to obtain data information from the multiple AIoT devices once every 1 hour, until the number of times the terminal device sends the third request message to the multiple AIoT devices reaches 5 times.

[0130] In other embodiments, the first request message may also include the aforementioned security verification information to perform security verification during the process of establishing a connection between the terminal device and one or more AIoT devices.

[0131] In other embodiments, the first request message may also include second information, which is used to instruct the AIoT device to report data information.

[0132] In one example, the second information can be an instruction. When the second information is the first instruction, the second information can indicate that all AIoT devices that have successfully established a connection with the terminal device need to report data information.

[0133] In another example, when the second information is a second instruction, the second information can instruct AIoT devices that have not yet performed data reporting to report data information. For example, a newly added AIoT device among multiple AIoT devices that have successfully established a connection with the terminal device needs to report data information.

[0134] S403, the terminal device sends connection establishment requests to multiple AIoT devices based on the first request message.

[0135] The connection establishment request is used to request the establishment of a connection with an AIoT device.

[0136] In this embodiment of the application, after receiving the first request message, the terminal device can send a connection establishment request to each of the multiple AIoT devices to request the establishment of a connection with the AIoT device.

[0137] In some embodiments, after a terminal device sends connection establishment requests to multiple AIoT devices, none of the AIoT devices successfully establish a connection with the terminal device upon receiving the connection establishment requests. For example, multiple AIoT devices may fail to establish a connection with the terminal device due to hardware failure, lack of network connectivity, or other reasons.

[0138] In other embodiments, after the terminal device sends a connection establishment request to multiple AIoT devices, only some of the AIoT devices successfully establish a connection with the terminal device after receiving the connection establishment request.

[0139] If a terminal device fails to receive the identification information of multiple AIoT devices from the first request message sent by the first network element, resulting in the terminal device failing to establish a connection with any of the AIoT devices, the terminal device can instruct the first network element to resend the first request message to the terminal device, instructing the terminal device to attempt to establish a connection with the multiple AIoT devices again. Thus, by instructing the network device to resend the first request message to the terminal device, the terminal device avoids situations where connection failures occur due to network instability, temporary device malfunctions, or other reasons, thereby improving the reliability and stability of establishing connections between the terminal device and multiple AIoT devices.

[0140] In some other embodiments, after the terminal device sends a connection establishment request to multiple AIoT devices, the multiple AIoT devices, upon receiving the connection establishment request and successfully establishing a connection with the terminal device, can send a connection response message to the terminal device. Subsequently, the terminal device can send a third request message to the multiple AIoT devices. Upon receiving the third request message, the multiple AIoT devices can report their own data information to the terminal device, thereby enabling the terminal device to send the data information of the multiple AIoT devices to the network device.

[0141] When a terminal device receives a first request message from a first network element that includes security verification information, the terminal device can send connection establishment requests carrying the security verification information to multiple AIoT devices. Upon receiving these connection establishment requests, the multiple AIoT devices verify the security verification information based on its content. If the multiple AIoT devices successfully verify the security verification information, they are allowed to establish connections with the terminal device. This establishes secure connections between the terminal device and multiple AIoT devices, enhancing the security and accuracy of data transmission between them.

[0142] For example, assuming the security verification information includes token information, the terminal device sends connection establishment requests carrying the token information to multiple AIoT devices. Each AIoT device, upon receiving a connection establishment request carrying the token information, verifies the received token information. Optionally, the AIoT device first parses the token information, then verifies the token's signature to ensure the received token has not been tampered with during transmission, confirms the token information has not expired, and that the content included in the token information is consistent with the content stored in the AIoT device. If multiple AIoT devices successfully verify the token information, then multiple AIoT devices are allowed to establish connections with the terminal device.

[0143] For example, assuming the security verification information includes certificate information, the terminal device sends a connection establishment request carrying the certificate information to multiple AIoT devices. Each AIoT device, upon receiving the connection establishment request, verifies the received certificate information. Optionally, after receiving the certificate information, the AIoT device first verifies whether the certificate was issued by a trusted CA, whether the certificate has expired, and whether the certificate has been revoked. If the AIoT device determines that the certificate was issued by a trusted CA, that the certificate has not expired, and that the certificate has not been revoked, then the AIoT device uses the public key in the certificate information to verify the terminal device's signature. Once the AIoT device successfully verifies the certificate information, it uses the public key in the certificate information to exchange keys and generate a shared key for encryption during subsequent communication between the terminal device and the AIoT devices.

[0144] For example, assuming the security verification information includes key information, the terminal device sends a connection establishment request carrying the key information to multiple AIoT devices. Each AIoT device, upon receiving the connection establishment request, verifies the received key information. Optionally, after receiving the key information, the AIoT device first verifies whether the key information has been tampered with during transmission using a message authentication code or digital signature. If the AIoT device determines that the received key information matches the pre-set key, then the AIoT device has successfully verified the key information.

[0145] In one scenario, a connection establishment request sent by a terminal device to multiple AIoT devices can also be used to activate the connection between the terminal device and the multiple AIoT devices. It should be understood that a connection has been established between the terminal device and the multiple AIoT devices, but the connection is inactive. In this case, after the terminal device sends a connection establishment request to the multiple AIoT devices to activate the connection between the terminal device and the multiple AIoT devices, the connection between the terminal device and the multiple AIoT devices is in a connected state.

[0146] The communication method provided in this application embodiment involves a terminal device receiving a first request message from a first network element and then sending connection establishment requests to multiple AIoT devices to request connection establishment with them. When the network device sends the first request message to the terminal device, the terminal device successfully establishes connections with multiple AIoT devices, eliminating the need for the terminal device to sequentially send connection requests to each AIoT device, thus improving the efficiency of connection establishment between the terminal device and multiple AIoT devices. Furthermore, when the network device subsequently sends a third request message to the terminal device, data information from multiple AIoT devices can be obtained through the terminal device.

[0147] In one specific embodiment, taking a terminal device as the reader / writer, a first network element as AMF / AIoTNF, a second network element as NEF, and an application function network element as AIoTAF as an example, the specific process of the communication method of this application embodiment is described in detail. Figure 5 is a schematic diagram of the interaction flow of another communication method provided by this application embodiment. As shown in Figure 5, the communication method provided by this application embodiment may include:

[0148] S501, multiple readers send first information to AMF / AIoTNF, and correspondingly, AMF / AIoTNF receives the first information sent by multiple readers.

[0149] The first information of each reader / writer is used to indicate the reader / writer's read / write capabilities and the AIoT devices associated with the reader / writer. The first information of each reader / writer may include at least one of the following: the reader / writer's read / write capabilities, the reader / writer's location information, the AIoT devices associated with the reader / writer, and the identification information of a third-party server.

[0150] Each reader establishes a connection with multiple AIoT devices, meaning that the reader is connected to multiple AIoT devices.

[0151] The location information of the reader also refers to the geographical location information of the reader. For details, please refer to the detailed description in S401 above, which will not be repeated here.

[0152] In this embodiment, after the reader is powered on or restarted for the first time, it establishes a communication connection with the network device via a wireless interface. The reader then sends a first message to the AMF / AIoTNF to request a registration process with the network device. Upon receiving the first message from the first device, the network device can determine the AIoT device associated with the reader based on the first message, confirming that both the reader and the associated AIoT device have been deployed.

[0153] S502, AIoTAF sends a second request message to NEF; correspondingly, NEF receives the second request message sent by AIoTAF.

[0154] The second request message is used to request data information from multiple AIoT devices. Specifically, a description of the second request message can be found in section S401, and will not be repeated here.

[0155] In this embodiment of the application, after AMF / AIoTNF receives the first information sent by multiple readers, when AIoTAF needs to obtain data information of multiple AIoT devices, AIoTAF sends a second request message to NEF to request to obtain data information of multiple AIoT devices.

[0156] It should be understood that S502 is not executed immediately after S501 is executed. Instead, S502 is triggered when AIoTAF needs to obtain data information from multiple AIoT devices.

[0157] S503, NEF authenticates AIoTAF and converts the location information of multiple readers into a TA list or cell identification information.

[0158] In this embodiment of the application, after NEF receives the second request message sent by AIoTAF, NEF authenticates AIoTAF to determine whether to allow AIoTAF to access the network.

[0159] Optionally, after receiving the second request message, NEF verifies the authentication information included in the second request message. If NEF verifies the authentication information, then NEF's authentication of AIoTAF is successful. Otherwise, NEF's authentication of AIoTAF fails.

[0160] For example, assuming the authentication information is certificate information, if NEF receives the certificate information provided by AIoTAF and verifies that the certificate information is valid, then NEF's authentication of AIoTAF is successful.

[0161] Once NEF has successfully authenticated AIoTAF, it can convert the location information of multiple readers included in the second request message into a TA list or cell identification information.

[0162] Since the location information of multiple readers is geographic information, NEF can convert this geographic information into a TA list or cell identification information for easier network management. The TA list is used to track the location of multiple readers. The cell identification information is the identification information of the cell whose service area covers the geographic information of multiple readers.

[0163] Optionally, the NEF can determine the cell with which the reader communicates based on the reader's location information. Then, the NEF calculates the distance from the reader to the cell based on the reader's location information and the cell's location information, and determines the TA value based on the distance. Since different readers connect to different cells, the second network obtains different TA values ​​based on the distance between each reader and its connected cell, thus obtaining a TA list containing all TA values.

[0164] NEF obtains the cell identifier information based on the cell identifier corresponding to each TA value in the TA list.

[0165] If NEF fails to authenticate AIoTAF, AIoTAF will fail to access the network and will not execute subsequent procedures.

[0166] S504, NEF determines AMF / AIoTNF based on the TA list or cell identification information.

[0167] In some embodiments, the NEF can send a network function (NF) discovery request to the NRF, wherein the discovery request includes a TA list or cell identification information. Based on the TA list or cell identification information, the NRF searches for and returns information about the AMF / AIoTNF serving multiple readers, including the AMF / AIoTNF's identification information, network address, etc.

[0168] S505, NEF sends a second request message to AMF / AIoTNF; correspondingly, AMF / AIoTNF receives the second request message sent by NEF.

[0169] The second request information here may include at least one of the following: second information, AIoT device list 1, TA list, cell identification information, AIoTAF identification information, security verification information, a threshold for the number of times to send the second information to multiple AIoT devices and / or periodic indication information, and preset identification information.

[0170] S506, AMF / AIoTNF identifies the target reader from multiple readers.

[0171] For example, when AMF / AIoTNF needs to acquire data from multiple AIoT devices, such as to conduct asset inventory of AIoT devices, read the operating information of AIoT devices, or send control commands to AIoT devices, AMF / AIoTNF can determine the target reader from multiple readers and use the target reader as an intermediate node for multiple AIoT devices to aggregate and transmit asset inventory and read / write control commands for AIoT devices.

[0172] In one scenario, the target reader can be a device among multiple readers that corresponds to the preset identification information.

[0173] The preset identification information is used to uniquely identify a device that acts as an intermediate node among multiple AIoT devices. For example, the preset identification information can be the device's general public user identity (Group Paging Service Identity, GPSI). Of course, the preset identification information can also be other information used to uniquely indicate the device, and there are no restrictions here.

[0174] In some embodiments, the preset identification information can be forwarded by AIoTAF to AMF / AIoTNF via NEF. After receiving the preset identification information from AIoTAF, AMF / AIoTNF can determine the target reader corresponding to the preset identification information from multiple readers.

[0175] In another scenario, AMF / AIoTNF can determine the target reader from multiple readers based on the location information of multiple AIoT devices, the location information of multiple readers, and the management range.

[0176] For example, AMF / AIoTNF can identify the target reader as the device that is within the management range, associated with multiple AIoT devices, and whose distance from each AIoT device is less than a preset distance.

[0177] S507, AMF / AIoTNF sends the first request message to the target reader.

[0178] For details on the first request message sent by AMF / AIoTNF to the target reader, please refer to the specific description of S402 above, which will not be repeated here.

[0179] S508, AMF / AIoTNF sends an end instruction to the target reader.

[0180] The end indicator is used to indicate the end of the first request message transmission.

[0181] In this embodiment of the application, after the AMF / AIoTNF finishes sending the first request message to the target reader, it sends an end indication to the target reader.

[0182] For example, as shown in Figure 6(a), the AMF / AIoTNF can send an end indication after completely sending the first request message to the target reader. Alternatively, as shown in Figure 6(b), the AMF / AIoTNF can send an end indication after a preset time interval after completely sending the first request message to the target reader; this embodiment does not limit the specific implementation.

[0183] AMF / AIoTNF can send a first request message and an end indication to the target reader in a single instruction, or it can send the first request message and the end indication in different instructions. This application does not limit this.

[0184] S509, the target reader determines whether it has received an end instruction.

[0185] The end indicator is used to indicate the end of the first request message transmission.

[0186] Upon receiving the termination instruction, the target reader receives the first request message sent by AMF / AIoTNF. The target reader can then perform the process of establishing connections with multiple AIoT devices, i.e., execute S512 as described below.

[0187] If the target reader does not receive a termination instruction, it has not fully received the first request message sent by AMF / AIoTNF. In this case, the target reader cannot successfully establish a connection with multiple AIoT devices. The target reader can send a first response message to AMF / AIoTNF, i.e., execute S510, to request AMF / AIoTNF to retransmit the first request message.

[0188] S510, the target reader sends a first response message to the AMF / AIoTNF, and correspondingly, the AMF / AIoTNF receives the first response message from the target reader.

[0189] The first response message can be used to instruct AMF / AIoTNF to retransmit the first request message.

[0190] If the target reader does not receive the termination instruction sent by AMF / AIoTNF, the target reader may send a first response message to AMF / AIoTNF to instruct AMF / AIoTNF to retransmit the first request message to the target reader.

[0191] S511, AMF / AIoTNF determines whether the number of times the first request message is sent to the target reader is less than a preset threshold.

[0192] After receiving the first response message, AMF / AIoTNF can determine whether the number of times the first request message is sent to the target reader is less than a preset threshold.

[0193] In one scenario, if the AMF / AIoTNF determines that the number of times the first request message has been sent to the target reader is less than a preset threshold, the AMF / AIoTNF repeats step S507, meaning that the AMF / AIoTNF can retransmit the first request message to the target reader to instruct the target reader to try again to establish a connection with multiple AIoT devices.

[0194] For example, with a preset threshold of 5, after receiving the first response message, if AMF / AIoTNF determines that the number of times it has sent the first request message to the target reader is less than 5, then AMF / AIoTNF will send the first request message to the target reader again. If AMF / AIoTNF determines that the number of times it has sent the first request message to the target reader has reached 5, then AMF / AIoTNF will no longer send the first request message to the target reader.

[0195] It should be understood that if the number of times AMF / AIoTNF sends the first request message to the target reader does not reach the preset threshold, AMF / AIoTNF will retransmit the first request message to the target reader. This avoids the situation where the target reader fails to receive the first request message completely due to accidental reasons such as network disconnection between AMF / AIoTNF and the target reader, thus preventing the target reader from failing to connect with multiple AIoT devices.

[0196] In another scenario, if the AMF / AIoTNF determines that the number of times the first request message is sent to the target reader has reached a preset threshold, the AMF / AIoTNF will no longer retransmit the first request message to the target reader. That is, the AMF / AIoTNF will no longer instruct the target reader to establish a connection with multiple AIoT devices, and the process of the target reader establishing a connection with multiple AIoT devices will end.

[0197] It should be understood that if the AMF / AIoTNF sends multiple first request messages to the target reader without the target reader receiving a termination indication, the target reader will fail to establish a connection with multiple AIoT devices because it has not received a complete first request message. Therefore, when the number of times the AMF / AIoTNF sends first request messages to the target reader reaches a preset threshold, the AMF / AIoTNF will stop sending first request messages to the target reader. This avoids the situation where the AMF / AIoTNF continuously retransmits first request messages to the target reader, resulting in high power consumption for both the AMF / AIoTNF and the target reader.

[0198] S512, the target reader sends connection establishment requests to multiple AIoT devices respectively; correspondingly, the multiple AIoT devices receive connection establishment requests from the target reader respectively.

[0199] The connection establishment request is used to request the establishment of a connection with an AIoT device.

[0200] S513, multiple AIoT devices send connection response messages to the target reader respectively; correspondingly, the target reader receives the connection response messages sent by the multiple AIoT devices respectively.

[0201] The connection response message is used to indicate whether the AIoT device and the target reader have successfully established a connection.

[0202] S514, the target reader determines whether the connection with multiple AIoT devices has failed based on the connection response messages sent by the multiple AIoT devices.

[0203] In this embodiment of the application, whether the target reader successfully establishes a connection with multiple AIoT devices includes the following three cases:

[0204] In the first scenario, the target reader receives connection response messages from multiple AIoT devices, all indicating that the AIoT devices have failed to establish a connection with the target reader, meaning that the reader has failed to connect with multiple AIoT devices. In this case, the target reader can send a first response message to the AMF / AIoTNF to instruct the AMF / AIoTNF to retransmit the first request information, thereby instructing the target reader to attempt to establish a connection with the multiple AIoT devices again.

[0205] In some embodiments, the target reader sends connection establishment requests to multiple AIoT devices. Upon receiving these requests, the multiple AIoT devices fail to establish a connection with the target reader due to various reasons (e.g., hardware failure, network problems, or authentication failures). The connection response messages received by the target reader from each of the multiple AIoT devices indicate that the connection between the AIoT devices and the target reader has failed.

[0206] Optionally, the target reader sends connection establishment requests carrying security authentication information to multiple AIoT devices. Upon receiving these requests, the multiple AIoT devices verify the security authentication information. If all AIoT devices fail to verify the security authentication information, each AIoT device sends a connection response message to the target reader. Upon receiving these connection response messages, the target reader determines that all connection attempts with the multiple AIoT devices have failed.

[0207] It should be understood that the reasons for the failure of the target reader to establish a connection with multiple AIoT devices described above are merely examples, and other reasons that cause the target reader to fail to establish a connection with multiple AIoT devices may also be applicable to the embodiments of this application.

[0208] If the target reader fails to establish connections with multiple AIoT devices, the above-mentioned S512 continues to be executed. That is, AMF / AIoTNF instructs the target reader to retry establishing connections with multiple AIoT devices, avoiding situations where the target reader fails to connect with multiple AIoT devices due to network instability, temporary device failures, etc., thereby improving the reliability and stability of establishing connections between the target reader and multiple AIoT devices.

[0209] In the second scenario, the target reader receives connection response messages from multiple AIoT devices, all indicating that a connection has been successfully established between the AIoT devices and the target reader, meaning the reader has successfully connected with multiple AIoT devices. In this case, the target reader executes step S515.

[0210] Optionally, the target reader sends connection establishment requests carrying security authentication information to multiple AIoT devices. Upon receiving the connection establishment requests, the multiple AIoT devices verify the security authentication information. If all multiple AIoT devices successfully verify the security authentication information, they are allowed to establish connections with the target reader. This establishes secure connections between the target reader and multiple AIoT devices, enhancing the security and accuracy of data transmission between the target reader and the multiple AIoT devices.

[0211] For example, assuming the security verification information is a token, the target reader sends connection establishment requests carrying the token information to multiple AIoT devices. Each AIoT device, upon receiving a connection establishment request, verifies the received token information. Optionally, the AIoT device first parses the token information, then verifies the token's signature to ensure the received token has not been tampered with during transmission, confirms the token information has not expired, and that the content of the token information matches the content stored in the AIoT device. If multiple AIoT devices successfully verify the token information, then multiple AIoT devices are allowed to establish connections with the target reader.

[0212] In the third scenario, the target reader receives connection response messages from multiple AIoT devices and determines that some of these messages indicate a successful connection between the AIoT devices and the target reader; that is, the target reader has successfully established a connection with some of the multiple AIoT devices. In this case, the target reader executes step S515.

[0213] S515, the target reader sends a second response message to the AMF / AIoTNF; correspondingly, the AMF / AIoTNF receives the second response message sent by the target reader.

[0214] The second response message is used to indicate the AIoT device list 2, which includes the identification information of the AIoT devices that have successfully established a connection with the target reader.

[0215] In this embodiment of the application, after the AMF / AIoTNF receives the AIoT device list 2 sent by the target reader, it compares the identification information of the AIoT devices in the AIoT device list 2 with the identification information of multiple AIoT devices in the aforementioned AIoT device list 1 to determine whether the target reader has successfully established a connection with the multiple AIoT devices.

[0216] The AMF / AIoTNF determines that the identification information of the AIoT devices in the AIoT device list 2 indicated by the second response message is completely identical to the identification information of multiple AIoT devices in the aforementioned AIoT device list 1. The target reader sends a third request message to the multiple AIoT devices. After receiving the third request message, the multiple AIoT devices send their data information to the target reader. After receiving the data information sent by the multiple AIoT devices, the target reader sends a notification message to the network device. The notification message is used to indicate the data information of the multiple AIoT devices.

[0217] Optionally, in S516, AMF / AIoTNF determines that the identification information of the AIoT devices in AIoT device list 2 is not completely the same as that in AIoT device list 1, and the number of times the first request message is sent to the target reader is less than a preset threshold, and continues to execute S507.

[0218] If AMF / AIoTNF determines that the identification information of an AIoT device in the AIoT device list is not completely identical to the identification information of multiple AIoT devices, and AMF / AIoTNF determines that the number of times the first request message is sent to the target reader is less than a preset threshold, then AMF / AIoTNF sends the first request message to the target reader again to instruct the target reader to try to establish a connection with the multiple AIoT devices again.

[0219] It should be understood that if the target reader fails to establish a connection with some AIoT devices, the AMF / AIoTNF will be unable to obtain data information from those AIoT devices through the target reader. Therefore, the AMF / AIoTNF can send the first request message to the target reader again to instruct the target reader to try to establish a connection with multiple AIoT devices again.

[0220] The communication method provided in this application embodiment, after AMF / AIoTNF determines the target reader, sends a first request message to the target reader so that the target reader can establish a connection with multiple AIoT devices. This eliminates the need for the target reader to send connection requests to multiple AIoT devices sequentially, and enables the target reader to establish a connection with multiple AIoT devices through a single request process, thereby improving the efficiency of establishing a connection between the target reader and multiple AIoT devices.

[0221] The foregoing mainly describes the solutions provided in the embodiments of this application from the perspective of interaction between various devices. It is understood that each device, such as a terminal device, AIoT device, network device, etc., includes corresponding hardware structures and / or software modules to perform the above functions in order to achieve them. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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.

[0222] This application embodiment can group terminal devices, AIoT devices, network devices, etc., into functional modules according to the above method examples. For example, each functional group can correspond to a different functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. The grouping of modules in this application embodiment is illustrative and only represents one logical functional grouping; other grouping methods may be used in actual implementation.

[0223] By way of example, embodiments of this application also provide a communication device.

[0224] Please refer to Figure 7, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0225] As shown in Figure 7, the communication device 700 can exist independently or be integrated into other devices. It can communicate with the network devices mentioned above to implement the operations corresponding to the terminal devices in any of the above method embodiments.

[0226] The communication device 700 may include a transceiver unit 701. The communication device 700 may also include a processing unit. The transceiver unit 701 can implement corresponding communication functions, and the processing unit is used for data processing. The transceiver unit 701 may also be referred to as a communication interface or communication unit.

[0227] Optionally, the communication device 700 may further include a storage unit, which can be used to store instructions and / or data. The processing unit can read the instructions and / or data in the storage unit so that the communication device 700 can implement the aforementioned method embodiments.

[0228] The communication device 700 can be used to perform the actions performed by the terminal device in the preceding method embodiments. The communication device 700 can be the terminal device or a component configurable on the terminal device. The transceiver unit 701 is used to perform reception-related operations of the terminal device in the preceding method embodiments, and the processing unit is used to perform processing-related operations of the terminal device in the preceding method embodiments.

[0229] Optionally, the transceiver unit 701 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the above method embodiments. The receiving unit is used to perform the receiving operation in the above method embodiments.

[0230] It should be noted that the communication device 700 may include a transmitting unit but not a receiving unit. Alternatively, the communication device 700 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme executed by the communication device 700 includes both transmitting and receiving actions.

[0231] As an example, the communication device 700 is used to perform the actions performed by the terminal device in the embodiments shown in Figures 4 and 5 above.

[0232] The communication device 700 may include a transceiver unit 701.

[0233] The transceiver unit 701 is used to receive a first request message from the first network element. The first request message is used to request the terminal device to establish a connection with multiple AIoT devices connected to the environment.

[0234] In some embodiments, the transceiver unit 701 is further configured to send connection establishment requests to multiple AIoT devices respectively, wherein the connection establishment requests are used to request to establish a connection with the AIoT devices.

[0235] In some embodiments, the transceiver unit 701 is further configured to send a first response message to the first network element according to the first request message, wherein the first response message is used to instruct the first network element to retransmit the first request message.

[0236] In some embodiments, the transceiver unit 701 is further configured to send a second response message to the first network element. The second response message is used to indicate an AIoT device list, which includes identification information of AIoT devices that have successfully established a connection with the terminal device.

[0237] It should be understood that the corresponding processes performed by each unit have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0238] The processing unit in the preceding embodiments can be implemented by at least one processor or processor-related circuitry. The transceiver unit 701 can be implemented by a transceiver or transceiver-related circuitry. The transceiver unit can also be referred to as a communication unit or communication interface. The storage unit can be implemented by at least one memory.

[0239] By way of example, this application also provides another communication device.

[0240] Please refer to Figure 8, which is a schematic diagram of another communication device provided in an embodiment of this application.

[0241] As shown in Figure 8, the communication device 800 can exist independently or be integrated into other devices. It can communicate with the terminal devices mentioned above to implement the operation of the network device in any of the above method embodiments.

[0242] The communication device 800 may include a transceiver unit 801. The communication device 800 may also include a processing unit. The transceiver unit 801 can implement corresponding communication functions, and the processing unit is used for data processing. The transceiver unit 801 may also be referred to as a communication interface or communication unit.

[0243] Optionally, the communication device 800 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit can read the instructions and / or data in the storage unit so that the communication device 800 implements the aforementioned method embodiments.

[0244] The communication device 800 can be used to perform the actions performed by the network device in the preceding method embodiments. The communication device 800 can be a network device or a component configurable on a network device. The transceiver unit 801 is used to perform reception-related operations of the network device in the preceding method embodiments, and the processing unit is used to perform processing-related operations of the network device in the preceding method embodiments.

[0245] Optionally, the transceiver unit 801 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the foregoing method embodiments. The receiving unit is used to perform the receiving operation in the foregoing method embodiments.

[0246] It should be noted that the communication device 800 may include a transmitting unit but not a receiving unit. Alternatively, the communication device 800 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme executed by the communication device 800 includes both transmitting and receiving actions.

[0247] As an example, the communication device 800 is used to perform the actions performed by the network device in the embodiments shown in Figures 4-5 above.

[0248] The communication device 800 may include a transceiver unit 801 and a processing unit 802.

[0249] The transceiver unit 801 is used to receive a second request message from the application function network element and then send a first request message to the terminal device; the second request message is used to request data information from multiple AIoT devices; the first request message is used to request the terminal device to establish a connection with multiple AIoT devices.

[0250] In some embodiments, the transceiver unit 801 is further configured to send an end indication to the terminal device; wherein the end indication is used to indicate the end of the transmission of the first request message; the end indication is sent after the first request message is sent, and the end indication and the first request message are the same message or two separate messages.

[0251] In some embodiments, the transceiver unit 801 is further configured to receive a first response message from the terminal device; wherein the first response message is used to instruct the first network element to retransmit the first request message.

[0252] In some embodiments, the processing unit 802 is used to determine whether the number of times the first request message is sent is less than a preset threshold.

[0253] In some embodiments, the transceiver unit 801 is further configured to retransmit the first request message to the terminal device if the number of times the first request message is sent is less than a preset threshold.

[0254] In some embodiments, the transceiver unit 801 is further configured to receive a second response message from the terminal device, the second response message being used to indicate an AIoT device list, the AIoT device list including identification information of AIoT devices that have successfully established a connection with the terminal device;

[0255] In some embodiments, the transceiver unit 801 is further configured to retransmit the first request message to the terminal device when the identification information of the AIoT devices included in the AIoT device list is not completely the same as the identification information corresponding to multiple AIoT devices, and the number of times the first request message is sent is less than a preset threshold.

[0256] In some embodiments, the transceiver unit 801 is further configured to receive first information from multiple terminal devices; wherein the first information of each terminal device is used to indicate the read / write capabilities of the terminal device and the AIoT device associated with the terminal device.

[0257] It should be understood that the corresponding processes performed by each unit have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0258] The processing unit in the preceding embodiments can be implemented by at least one processor or processor-related circuitry. The transceiver unit 801 can be implemented by a transceiver or transceiver-related circuitry. The transceiver unit 801 can also be referred to as a communication unit or communication interface. The storage unit can be implemented by at least one memory.

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

[0260] Figure 9 is a schematic diagram of another communication device provided in an embodiment of this application. As shown in Figure 9, the communication device 900 may include one or more processors 901, memory 902 and communication interface 903.

[0261] The memory 902, communication interface 903, and processor 901 are coupled together. For example, the memory 902, communication interface 903, and processor 901 can be coupled together via bus 904.

[0262] Processor 901 can be the control center of a communication device, and can be a processor or controller. For example, processor 901 can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of embodiments of this application. The processor can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0263] The communication interface 903 is used to communicate with other devices or communication networks, such as Ethernet, RAN, and wireless local area networks (WLAN). The communication interface 903 can also be a transceiver circuit located within the processor 901, used to implement the processor's signal input and signal output.

[0264] Memory 902 can be a device with storage function. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; 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. Memory can exist independently and be connected to the processor via bus 904. Memory can also be integrated with the processor.

[0265] The memory 902 is also used to store computer execution instructions for implementing the scheme of this application, and the execution is controlled by the processor 901. The processor 901 is used to execute the computer execution instructions stored in the memory 902, thereby implementing the method provided in the embodiments of this application.

[0266] Alternatively, in this embodiment, the processor 901 may execute the processing-related functions of the method provided in the following embodiments of this application, and the communication interface 903 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0267] The computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0268] Bus 904 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The aforementioned bus 904 can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 9, but this does not indicate that there is only one bus or one type of bus.

[0269] In some embodiments, processor 901 may include one or more CPUs.

[0270] In some embodiments, the communication device 900 may include multiple processors. Each of these processors may be a single-core processor or a multi-core processor. The processors may include, but are not limited to, at least one of the following: CPU, microprocessor, DSP, microcontroller unit (MCU), or artificial intelligence processor, and other computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0271] This application provides a communication system, and Figure 10 is a schematic diagram of the structure of a communication system provided in this application. As shown in Figure 10, the communication system 1000 may include a terminal device 1001, a first network element 1002, and multiple AIoT devices 1003.

[0272] The terminal device 1001 can receive a first request message from the first network element 1002 and then send connection establishment requests to multiple AIoT devices 1003 respectively according to the first request message. The connection establishment request is used to request to establish a connection with the AIoT devices.

[0273] The first network element 1002 can be used to send a first request message to the terminal device 1001 after receiving the second request message; wherein the second request message is used to request to obtain data information of multiple AIoT devices 1003; and the first request message is used to request the terminal device 1001 to establish a connection with the multiple AIoT devices 1003.

[0274] The terminal device 1001, the first network element 1002, and the multiple AIoT devices 1003 in this application embodiment can also be used to execute the communication method provided in the foregoing embodiment.

[0275] This application also provides a communication device, including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, including computer instructions. When the one or more processors execute the computer instructions, the communication device performs the aforementioned method steps to implement the communication method in the above embodiments.

[0276] Embodiments of this application also provide a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a communication device, the communication device performs the aforementioned related method steps to implement the communication method in the above embodiments.

[0277] Embodiments of this application also provide a chip system including a memory and a processor, wherein programs / instructions stored in the memory are executed by the processor to implement the communication methods described in the above embodiments.

[0278] Embodiments of this application also provide a computer program product, including: a computer program or instructions, which, when the computer program or instructions are run on a computer, implement the communication method described in the above embodiments.

[0279] It is understood that, in order to achieve the above functions, network devices, terminal devices, and multiple AIoT devices include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware 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 implementations should not be considered beyond the scope of the embodiments of this invention.

[0280] This application embodiment can divide the terminal device, satellite, and ground station into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0281] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0282] In the embodiments of this application, the functional units 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0283] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor 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 flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0284] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope 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 by comprising: Applied to a terminal device, the method includes: Receive a first request message from a first network element; wherein the first request message is used to request the terminal device to establish a connection with multiple environmental network-connected AIoT devices; According to the first request message, connection establishment requests are sent to the plurality of AIoT devices respectively; wherein, the connection establishment request is used to request to establish a connection with the AIoT device.

2. The method according to claim 1, characterized in that, The first request message includes security verification information; wherein the security verification information is used for security verification between the terminal device and the plurality of AIoT devices.

3. The method according to claim 1 or 2, characterized in that, After receiving the first request message from the first network element, the method further includes: A first response message is sent to the first network element, which instructs the first network element to retransmit the first request message.

4. The method of claim 3, wherein, Sending the first response message to the first network element includes: If the terminal device does not receive an end indication, it sends the first response message to the first network element; wherein the end indication is used to indicate that the first request information has been sent.

5. The method of claim 3, wherein, Sending the first response message to the first network element includes: If the terminal device fails to establish a connection with the plurality of AIoT devices, a first response message is sent to the first network element.

6. The method according to any one of claims 1 to 5, characterized in that, After sending connection establishment requests to the plurality of AIoT devices respectively, the method further includes: A second response message is sent to the first network element. The second response message is used to indicate a list of AIoT devices, which includes identification information of AIoT devices that have successfully established a connection with the terminal device.

7. The method according to any one of claims 1-6, characterized in that, The terminal device is the device corresponding to the preset identification information among multiple terminal devices within the management scope of the first network element; or, The terminal device is one of the multiple terminal devices within the management scope of the first network element that is associated with all of the multiple AIoT devices and whose distance from each AIoT device is less than a preset distance.

8. A communication method characterized by comprising: Applied to the first network element of a network device, the method includes: Receive a second request message; wherein the second request message is used to request data information from multiple environmental AIoT devices; According to the second request message, a first request message is sent to the terminal device, the first request message being used to request the terminal device to establish a connection with the plurality of AIoT devices.

9. The method according to claim 8, characterized in that, The first request message includes security verification information; The security verification information is used for security verification between the terminal device and the plurality of AIoT devices.

10. The method according to claim 8 or 9, characterized in that, The method further includes: Send an end instruction to the terminal device; The termination indication is used to indicate the end of the first request message transmission.

11. The method according to any one of claims 8-10, characterized in that, After sending the first request message to the terminal device, the method further includes: Receive a first response message from the terminal device; wherein the first response message is used to instruct the first network element to retransmit the first request message; According to the first response message, if the number of times the first request message is sent is less than a preset threshold, the first request message is retransmitted to the terminal device.

12. The method according to any one of claims 8-10, characterized in that, After sending the first request message to the terminal device, the method further includes: Receive a second response message from the terminal device, the second response message being used to indicate an AIoT device list, the AIoT device list including identification information of AIoT devices that have successfully established a connection with the terminal device; If the identification information of the AIoT devices included in the AIoT device list is not completely the same as the identification information corresponding to the multiple AIoT devices, and the number of times the first request message is sent is less than a preset threshold, the first request message is retransmitted to the terminal device.

13. The method according to any one of claims 8-12, characterized in that, The terminal device is the device corresponding to the preset identification information among multiple terminal devices within the management scope of the first network element; or, The terminal device is a device among multiple terminal devices within the management scope of the first network element that is associated with both the network device and the multiple AIoT devices and whose distance from each AIoT device is less than a preset distance.

14. The method according to any one of claims 8-13, characterized in that, Before obtaining the first request message, the method further includes: Receive first information from the plurality of terminal devices; wherein the first information of each terminal device is used to indicate the read and write capabilities of the terminal device and the AIoT device associated with the terminal device.

15. The method according to any one of claims 8-13, characterized in that, The network device receiving the second request message includes: The second network element receives the second request message from the application function network element.

16. The method of claim 15, wherein, Receiving the second request message from the application function network element through the second network element includes: If the second network element successfully authenticates the application function network element, the second network element receives the second request message from the application function network element.

17. The method according to any one of claims 8-16, characterized in that, The second request message includes location information of multiple terminal devices; The first network element is determined based on the Tracking Area (TA) list or cell identification information of the multiple terminal devices.

18. A communication device comprising one or more processors, a memory, and a computer program stored on the memory, wherein the computer program is configured to instruct the one or more processors to perform the method of any one of claims 1-17. The processor executes the computer program to implement the method as described in any one of claims 1-7; and / or, the method as described in any one of claims 8-17.

19. A communication system, characterized by The system includes a first network element and terminal equipment. The terminal device is used to perform the method as described in any one of claims 1-7, and the first network element is used to perform the method as described in any one of claims 8-17.

20. A computer-readable storage medium, characterized in that, It 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-7; and / or cause the computer to perform the method as described in any one of claims 8-17.

21. A chip system comprising a memory and a processor, characterized in that The program / instructions stored in the memory, when executed by the processor, implement the method of any one of claims 1-7; and / or, implement the method of any one of claims 8-17.

22. A computer program product, characterised in that, The computer program product comprises: a computer program or instructions, which, when run on a computer, cause the computer to perform the method of any one of claims 1-7; and / or, cause the computer to perform the method of any one of claims 8-17.