Internet-of-things communication method, communication system, communication apparatus, chip system, storage medium and computer program product

Abstract

The embodiments of the present application relate to the technical field of the Internet of Things. Provided are an Internet-of-Things communication method, a communication system, a communication apparatus, a chip system, a storage medium and a computer program product. A first network element of a core network establishes a first tunnel between the first network element and an access network node, and communicates with a plurality of Internet-of-Things devices on the basis of the first tunnel, wherein the first tunnel may be understood as a shared tunnel shared by the plurality of Internet-of-Things devices. The first tunnel is established on the basis of first indication information used for indicating the plurality of Internet-of-Things devices. Taking the first tunnel including an N3 tunnel as an example, in this way, a core network can communicate with a plurality of Internet-of-Things devices without the need for establishing a dedicated N3 tunnel for each Internet-of-Things device among the plurality of Internet-of-Things devices, thereby reducing the configuration overheads of the core network, and also reducing the configuration overheads of access network nodes.

Description

Iot communication method, communication system, communication device, chip system, storage medium and computer program product

[0001] The present application claims priority from the Chinese patent application No. 202411393378.2 filed on September 30, 2024, and entitled "Iot communication method, communication system, communication device, chip system, storage medium and computer program product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the technical field of Iot, and in particular to an Iot communication method, a communication system, a communication device, a chip system, a storage medium and a computer program product. BACKGROUND

[0003] Some mobile communication systems can include Iot devices, access network nodes, core networks and AF entities. The AF entities can communicate with the Iot devices through the core networks and the access network nodes.

[0004] In the scenario where the AF entities communicate with the Iot devices through the core networks and the access network nodes, there is a problem of large configuration overhead of the core networks. SUMMARY

[0005] The embodiments of the present application provide an Iot communication method, a communication system, a communication device, a chip system, a storage medium and a computer program product, which are applied to the technical field of Iot and can reduce the configuration overhead of the core networks.

[0006] In a first aspect, the embodiments of the present application provide an Iot communication method applied to a first network element, the method comprising: establishing a first tunnel, the first tunnel being a shared tunnel between the first network element and an access network node; and communicating with a plurality of Iot devices based on the first tunnel and / or communicating with at least one intermediate node based on the first tunnel. The first tunnel is established based on first indication information, and the first indication information comprises one or more of the following: Iot service area information, information of an Iot device group to which the plurality of Iot devices belong, information of an intermediate node corresponding to the plurality of Iot devices, or information of an intermediate node group to which the intermediate node corresponding to the plurality of Iot devices belongs.

[0007] In this way, the first indication information can correspond to a plurality of Internet of Things devices, or the first indication information can be used to indicate a plurality of Internet of Things devices. The first tunnel is established based on the first indication information, which can mean that the first tunnel is a shared tunnel commonly used by the plurality of Internet of Things devices corresponding to the first indication information. The first network element can communicate with the plurality of Internet of Things devices based on the first tunnel, and / or communicate with at least one intermediate node based on the first tunnel. Taking an example in which the first tunnel includes an N3 tunnel, the first network element does not need to establish a dedicated N3 tunnel for the plurality of Internet of Things devices, and the communication between the first network element and the plurality of Internet of Things devices and / or the communication with at least one intermediate node can be realized. The configuration overhead of the first network element can be reduced, and further the configuration overhead of a core network to which the first network element belongs can be reduced. The intermediate node can have a relay function and / or a reader function. The specific implementation principles of the embodiments of the present application can be referred to the specific implementation principles of the embodiments shown in S501-S502.

[0008] In a possible implementation, one or more Internet of Things devices can be deployed in the Internet of Things service area.

[0009] In a possible implementation, the Internet of Things service area information includes one or more of the following: geographic location information of the Internet of Things service area, one or more tracking area identifiers corresponding to the Internet of Things service area, one or more cell identifiers corresponding to the Internet of Things service area, or one or more base station identifiers corresponding to the Internet of Things service area.

[0010] In this way, in the case where the first network element establishes the first tunnel based on the Internet of Things service area information, the first tunnel can correspond to one or more of the following: the geographic location information of the Internet of Things service area, the one or more tracking area identifiers corresponding to the Internet of Things service area, the one or more cell identifiers corresponding to the Internet of Things service area, or the one or more base station identifiers corresponding to the Internet of Things service area.

[0011] In a possible implementation, the method further includes: receiving first information, the first information being used to indicate the establishment of the first tunnel, and the first information including the first indication information. The establishment of the first tunnel includes: establishing the first tunnel based on the first information.

[0012] In this way, the first information is sent to the first network element to trigger the first network element to establish the first tunnel corresponding to the first indication information in the first information.

[0013] In a possible implementation, the method further includes: receiving second information, the second information being used to indicate the establishment of a second tunnel, the second tunnel being a tunnel between the first network element and an application function entity, and the second information including an identifier of the application function entity and a second tunnel address of the application function entity. The second tunnel is established based on the second information.

[0014] Thus, the first tunnel and the second tunnel are established by sending the first information to the first network element. The second information can be received by the first network element before the first tunnel is established, as shown in the embodiment of FIG. 9. The second information can be received by the first network element after the first tunnel is established, as shown in the embodiment of FIG. 10.

[0015] In a possible implementation, the first information is further used to indicate that the second tunnel is to be established, the second tunnel being a tunnel between the first network element and the application function entity, and the first information further includes an identifier of the application function entity and a second tunnel address of the application function entity. The method further includes: establishing the second tunnel based on the first information.

[0016] Thus, the first tunnel and the second tunnel are established by sending the first information to the first network element. The second information can be received by the first network element before the first tunnel is established, as shown in the embodiment of FIG. 9. The second information can be received by the first network element after the first tunnel is established, as shown in the embodiment of FIG. 10.

[0017] In a possible implementation, the first information is sent by the session management function network element in a case where the third information from the internet of things network function network element is received or the fourth information from the network exposure function network element is received. The third information and the fourth information are both used to indicate that the first tunnel is to be established, or are used to indicate that the first tunnel and the second tunnel are to be established, the second tunnel being a tunnel between the first network element and the application function entity, and the third information and the fourth information both include the first indication information. The third information is sent by the internet of things network function network element in any of the following cases: receiving an internet of things service request from the network exposure function network element or the application function entity. Receiving the fourth information from the network exposure function network element or the fifth information from the application function entity, the fifth information being used to indicate that the first tunnel is to be established, or being used to indicate that the first tunnel and the second tunnel are to be established, and the fifth information including the first indication information. Receiving registration information from a plurality of internet of things devices.

[0018] In this way, the IoT network function network element can send the third information to the session management function network element to trigger establishment of the first tunnel or trigger establishment of the first tunnel and the second tunnel. The network exposure function network element can send the fourth information to the session management function network element to trigger establishment of the first tunnel or trigger establishment of the first tunnel and the second tunnel. The network exposure function network element or the application function entity can send the IoT service request to the IoT network function network element to trigger the IoT network function network element to send the third information. The network exposure function network element can send the fourth information to the IoT network function network element to trigger the IoT network function network element to send the third information. The application function entity can also send the fifth information to the IoT network function network element to trigger the IoT network function network element to send the third information. The registration information from the plurality of IoT devices can indicate that the plurality of IoT devices complete device registration, and the plurality of IoT devices completing device registration can also trigger the IoT network function network element to send the third information, thereby triggering establishment of the first tunnel or triggering establishment of the first tunnel and the second tunnel.

[0019] In a possible implementation, the first information further includes an IoT service type and a valid duration of the first tunnel. The method further includes: tearing down the first tunnel from a time when the first tunnel is established to a time when the valid duration is reached. The IoT service type includes one or more of the following: inventory, command, or registration.

[0020] In this way, the first network element can tear down the first tunnel based on the valid duration of the first tunnel, which can achieve resource release and improve resource utilization. In a case where the first information includes the IoT service type, the first tunnel established based on the first information can be a tunnel used to implement a service corresponding to the IoT service type. For example, the first tunnel can be used to transmit information of a service corresponding to the IoT service type. The information of the service corresponding to the IoT service type can include service data returned by the IoT service request or the IoT service request indication.

[0021] In a possible implementation, based on the first information, the first tunnel is established, including: sending a first response to the session management function network element, the first response being a response to the first information, and the first response including an uplink tunnel identifier of the first tunnel, the uplink tunnel identifier being obtained from the first information or configured by the first network element.

[0022] In this way, the uplink tunnel identifier of the first tunnel is transmitted to the session management function network element, so that the session management function network element transmits the uplink tunnel identifier of the first tunnel to the access network node, thereby establishing the first tunnel.

[0023] In a possible implementation, based on the first information, the first tunnel is established, further including: receiving a downlink tunnel identifier of the first tunnel.

[0024] In this way, the first network element can obtain the downlink tunnel identifier of the first tunnel, so as to facilitate the first network element to subsequently transmit the Internet of Things service request to the access network node through the first tunnel. The first network element can receive the downlink tunnel identifier of the first tunnel after sending the first response, as shown in the embodiment of FIG. 6A. The first network element can receive the downlink tunnel identifier of the first tunnel before sending the first response, as shown in the embodiment of FIG. 6B.

[0025] In a possible implementation, the method further includes: receiving a first data packet, the first data packet including the Internet of Things service request and first indication information. Based on the first tunnel communicating with the plurality of Internet of Things devices and / or based on the first tunnel communicating with the at least one intermediate node, the method includes: sending, to the access network node, a second data packet through the first tunnel corresponding to the first indication information, the second data packet including the Internet of Things service request and the first indication information, the first indication information being carried in a packet header of the second data packet.

[0026] In this way, the first data packet includes the first indication information, so that the first network element can determine the first tunnel through the first indication information, and send the second data packet to the access network node through the determined first tunnel. The first indication information is carried in the packet header of the second data packet, so that the access network node can send the Internet of Things service request to the intermediate node or the Internet of Things device corresponding to the first indication information based on the first indication information. Details can be seen in the embodiments of FIG. 11 or FIG. 12.

[0027] In a possible implementation, the first indication information includes information of at least one intermediate node corresponding to the plurality of Internet of Things devices and / or Internet of Things service area information. The sending, to the access network node, of the second data packet through the first tunnel corresponding to the first indication information includes: sending, to the access network node, the second data packet through the first tunnel corresponding to the Internet of Things service area information. The first indication information carried in the packet header of the second data packet is used to instruct the access network node to send a third data packet or a first paging to each of the at least one intermediate node, or is used to instruct the access network node to send the third data packet or the first paging to all intermediate nodes in the Internet of Things service area. The third data packet and the first paging both include the Internet of Things service request.

[0028] In this way, the first network element can determine the first tunnel based on the Internet of Things service area information, and send the second data packet to the access network node through the determined first tunnel. The first indication information is carried in the packet header of the second data packet, so that the access network node can send the third data packet or the first paging to the intermediate node corresponding to the first indication information.

[0029] In a second aspect, the embodiments of the present application provide a method for Internet of Things (IoT) communication, applied to an IoT network function network element. The method comprises: receiving an IoT service request, fourth information, fifth information, or registration information of a plurality of IoT devices. The fourth information and the fifth information are used to indicate establishment of a first tunnel, or are used to indicate establishment of the first tunnel and a second tunnel. The IoT service request, the fourth information, and the fifth information all comprise first indication information, and the first indication information comprises one or more of the following: IoT service area information, information of an IoT device group to which the plurality of IoT devices belong, information of an intermediate node corresponding to the plurality of IoT devices, or information of an intermediate node group to which an intermediate node corresponding to the plurality of IoT devices belongs. The first tunnel is a shared tunnel between the first network element and an access network node, and the second tunnel is a tunnel between the first network element and an application function entity. Third information is sent, the third information being used to indicate establishment of the first tunnel, or being used to indicate establishment of the first tunnel and the second tunnel, and the third information comprising the first indication information. The first tunnel is established based on the first indication information, and is used for communication between the first network element and the plurality of IoT devices.

[0030] In this way, the IoT network function network element can be triggered to send the third information by sending the IoT service request, the fourth information, the fifth information, or the registration information of the plurality of IoT devices to the IoT network function network element. The establishment of the first tunnel is further triggered, or the establishment of the first tunnel and the second tunnel is further triggered.

[0031] In a possible implementation, the method further comprises: receiving a second response, the second response being a response to the third information, and the second response comprising an uplink tunnel identifier of the first tunnel and a downlink tunnel identifier of the first tunnel.

[0032] In this way, the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel can be used to indicate that the first tunnel is successfully established, so as to facilitate management of the first tunnel by the IoT network function network element, or to indicate that the application function entity communicates with the IoT device through a user plane.

[0033] In a possible implementation, the second response further comprises a second tunnel address of the first network element. In this way, management of the second tunnel by the IoT network function network element is facilitated.

[0034] In a possible implementation, the method further comprises: sending a third response, the third response being a response to the fourth information, and the third response comprising the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel. Alternatively, a fourth response is sent, the fourth response being a response to the fifth information, and the fourth response comprising the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

[0035] In this way, the network element that sends the fourth information is notified that the first tunnel is successfully established. The network element that sends the fifth information is notified that the first tunnel is successfully established.

[0036] In a third aspect, an embodiment of the present application provides a method for Internet of Things communication, applied to a session management function network element, the method comprising: receiving third information or fourth information, the third information and the fourth information both being used to indicate establishment of a first tunnel, or being used to indicate establishment of the first tunnel and a second tunnel, and the third information and the fourth information both comprising first indication information. The first tunnel is a shared tunnel between a first network element and an access network node, and the second tunnel is a tunnel between the first network element and an application function entity. Sending first information, the first information being used to indicate establishment of the first tunnel, or being used to indicate establishment of the first tunnel and the second tunnel, the first information comprising the first indication information, or the first information comprising the first indication information, an identifier of the application function entity, and a second tunnel address of the application function entity.

[0037] In this way, the third information or the fourth information can be sent to the session management function network element to trigger the session management function network element to send the first information, thereby triggering establishment of the first tunnel, or triggering establishment of the first tunnel and the second tunnel.

[0038] In a possible implementation, the method further comprises: receiving a first response, the first response being a response to the first information, and the first response comprising an uplink tunnel identifier of the first tunnel. Sending sixth information to an access and mobility management function network element or an Internet of Things network function network element, the sixth information being used to indicate establishment of the first tunnel, and the sixth information comprising the first indication information and the uplink tunnel identifier of the first tunnel. Receiving a fifth response from the access and mobility management function network element or the Internet of Things network function network element, the fifth response being a response to the sixth information, and the fifth response comprising a downlink tunnel identifier of the first tunnel. Synchronizing the downlink tunnel identifier of the first tunnel with the first network element. In this way, establishment of the first tunnel is realized.

[0039] In a possible implementation, the method further comprises: sending a second response to the Internet of Things network function network element, the second response being a response to the third information, and the second response comprising the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel. In this way, the Internet of Things network function network element is notified of successful establishment of the first tunnel, thereby facilitating management of the first tunnel by the Internet of Things network function network element.

[0040] In a possible implementation, the second response further comprises a second tunnel address of the first network element. In this way, management of the second tunnel by the Internet of Things network function network element is facilitated.

[0041] In a possible implementation, the first information further comprises the second tunnel address of the application function entity, and the first response further comprises the second tunnel address of the first network element. The method further comprises: synchronizing the second tunnel address of the first network element with the Internet of Things network function network element.

[0042] In this way, the first information further comprises the second tunnel address of the application function entity, and the first response further comprises the second tunnel address of the first network element, and establishment of the second tunnel can be implemented. The second tunnel address of the first network element is synchronized to the network function network element of the Internet of Things, so that the network function network element of the Internet of Things manages the second tunnel.

[0043] In a fourth aspect, an embodiment of the present application provides a communication system, comprising: a first network element, a network function network element of the Internet of Things, and a session management function network element. The first network element is configured to perform the method in the first aspect or any possible implementation manner of the first aspect, the network function network element of the Internet of Things is configured to perform the method in the second aspect or any possible implementation manner of the second aspect, and the session management function network element is configured to perform the method in the third aspect or any possible implementation manner of the third aspect.

[0044] In a fifth aspect, an embodiment of the present application provides a communication device, comprising: a module configured to perform the method in the first aspect, any possible implementation manner of the first aspect, the second aspect, any possible implementation manner of the second aspect, the third aspect, or any possible implementation manner of the third aspect.

[0045] In a sixth aspect, an embodiment of the present application provides a communication device, comprising: one or more processors and a memory. The memory is coupled to the one or more processors, and the memory is configured to store computer program codes including computer instructions. The one or more processors are configured to invoke the computer instructions to cause the communication device to perform the method in the first aspect, any possible implementation manner of the first aspect, the second aspect, any possible implementation manner of the second aspect, the third aspect, or any possible implementation manner of the third aspect.

[0046] In a seventh aspect, an embodiment of the present application provides a chip system, which is applied to a communication device, and comprises one or more processors and a communication interface. The communication interface and the at least one processor are connected through a line. The one or more processors are configured to invoke computer instructions to cause the communication device to perform the method in the first aspect, any possible implementation manner of the first aspect, the second aspect, any possible implementation manner of the second aspect, the third aspect, or any possible implementation manner of the third aspect. The communication interface in the chip can be an input / output interface, a pin, or a circuit, etc.

[0047] In a possible implementation, the chip or the chip system described in the present application further comprises at least one memory, and the at least one memory stores instructions. The memory can be a storage unit inside the chip, for example, a register, a cache, etc., or a storage unit of the chip (for example, a read-only memory, a random access memory, etc.).

[0048] In an eighth aspect, the embodiments of the present application provide a computer readable storage medium, which includes computer instructions. When the computer instructions are run on a communication device, the communication device executes the method of the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect.

[0049] In a ninth aspect, the embodiments of the present application provide a computer program product, which includes computer program codes. When the computer program codes are run on a communication device, the communication device executes the method of the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect.

[0050] In a tenth aspect, the embodiments of the present application provide an Internet of Things communication device. The Internet of Things communication device can be an electronic device, or a chip or chip system in the electronic device. The Internet of Things communication device can include a display unit and a processing unit. When the Internet of Things communication device is an electronic device, the display unit can be a display screen. The display unit is configured to perform the displaying, so that the electronic device implements the Internet of Things communication method of the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect. When the Internet of Things communication device is an electronic device, the processing unit can be a processor. The Internet of Things communication device can further include a storage unit, which can be a memory. The storage unit is configured to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the electronic device implements an Internet of Things communication method described in the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect. When the Internet of Things communication device is a chip or chip system in the electronic device, the processing unit can be a processor. The processing unit executes the instructions stored in the storage unit, so that the electronic device implements an Internet of Things communication method described in the first aspect, any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, or any possible implementation of the third aspect. The storage unit can be a storage unit (for example, a register, a cache, etc.) in the chip, or a storage unit (for example, a read-only memory, a random access memory, etc.) outside the chip in the electronic device. BRIEF DESCRIPTION OF DRAWINGS

[0051] FIG. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application;

[0052] FIG. 2 is another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0053] FIG. 3 is still another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0054] FIG. 4 is still another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0055] FIG. 5 is a flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0056] FIG. 6A is another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0057] FIG. 6B is still another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0058] FIG. 6C is still another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0059] FIG. 7 is still another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0060] FIG. 8 is still another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0061] FIG. 9 is still another flow diagram of a method of communication according to an embodiment of the present application;

[0062] FIG. 10 is still another flow diagram of a method of Internet of Things communication according to an embodiment of the present application;

[0063] FIG. 11 is another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0064] FIG. 12 is still another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0065] FIG. 13 is still another schematic diagram of a communication system architecture according to an embodiment of the present application;

[0066] FIG. 14 is a schematic diagram of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0067] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0068] In the embodiments of the present application, the terms "first", "second", and the like are used to distinguish between similar or identical items or components that have substantially the same function and effect. For example, the first chip and the second chip are merely used to distinguish between different chips, and do not limit the sequence. Those skilled in the art can understand that the terms "first", "second", and the like do not limit the quantity and execution sequence, and the terms "first", "second", and the like do not necessarily mean different.

[0069] It should be noted that in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate an example, illustration, or description. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design solutions. Rather, the use of the words "exemplary" or "for example" is intended to present the relevant concept in a specific manner.

[0070] In the embodiments of the present application, "at least one" means one or more, "multiple" can be understood as "at least two", and "multiple items" can be understood as "at least two items". The "and / or" describes the association relationship between the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or the like refers to any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c can represent a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0071] The present application can be applied to a mobile communication system. The mobile communication system can be referred to as a mobile communication network. The mobile communication system can be referred to simply as a communication system. The mobile communication system includes, but is not limited to, the following systems, for example: a long term evolution (LTE) system, a universal mobile telecommunications system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system or new radio (NR), a 5.5G system or a future mobile communication system, vehicle-to-X (V2X), which 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), vehicle networking, machine type communication (MTC), internet of things (IoT), long term evolution-machine (LTE-M), machine to machine (M2M), etc.

[0072] The technical solutions of the embodiments of the present application are applicable to a communication system providing an internet of things (IoT) service. The IoT service, for example, an ambient internet of things (AIoT) service.

[0073] Exemplarily, in some embodiments, a communication system providing an internet of things service can comprise an internet of things device. The internet of things device can be, for example, an ambient internet of things device (AIoT device) or an ambient internet of things (AIoT) terminal. The AIoT terminal can be understood as a terminal capable of providing an AIoT service. The ambient internet of things device is a kind of internet of things device powered by energy harvesting, with limited energy storage capability. For example, some or all characteristics of the ambient internet of things device can refer to the description in TR 38.769 of the 3GPP standard. It should be understood that the description herein of some or all characteristics of the ambient internet of things device referring to the description in TR 38.769 of the 3GPP standard is only one possible example description, and the embodiments of the present application are not limited thereto. For another example, with the evolution or update of the version of the communication standard protocol, some or all of the ambient internet of things device described herein can refer to the evolved or updated version; or some or all characteristics of the ambient internet of things device can also refer to the description in the related art.

[0074] The technical solutions of the embodiments of the present application are also applicable to internet of things (IoT) communication scenarios and communication scenarios relying on backscatter technology. The above-mentioned IoT can be passive IoT, semi-passive IoT, or ambient IoT (AIoT), etc.

[0075] It should be understood that there can be other names or definitions for the internet of things device, and the embodiments of the present application do not make specific limitations thereto. There can be other names or definitions for the internet of things service, and there can be other names or definitions for the ambient internet of things service (ambient IoT services, or AIoT service), and the embodiments of the present application do not make specific limitations thereto.

[0076] Exemplarily, the internet of things service can also be referred to as internet of things business. The internet of things business can comprise one or more of the following: inventory, command, or registration.

[0077] The command can comprise one or more of the following: read, write, disable / kill, or enable.

[0078] The AIoT service (AIoT service) can also be referred to as AIoT business. It should be understood that the AIoT business can also comprise one or more of the following: inventory, command, or registration.

[0079] The communication system of the embodiments of the present application can include at least one IoT device, a radio access network (RAN), a core network (CN), and an application function (AF) entity. The radio access network (RAN) can be referred to as a wireless access network.

[0080] The application function (AF) entity can be an entity that provides an application within an operator, such as an entity of a voice over LTE application function (Volte AF). The Volte AF entity is similar to a voice over LTE application server (Volte As) of 4G. The application function (AF) entity can also be an AF of a third party (such as a video server, a game server). In the case that the AF entity is an AF within an operator and is in a trusted domain with other network functions (NFs), the AF entity can directly interact with other NFs. In the case that the AF entity is an AF of a third party and is not in a trusted domain, the AF entity can access other NFs through a NEF. The other NFs, such as an IoT network function (IoT NF) or an AIoT network function (AIoT NF).

[0081] The AF entity in the embodiments of the present application can be used to perform an IoT (Internet of Things) service or an AIoT (Artificial Intelligence of Things) service.

[0082] The application function entity can also be used to implement the cooperation between the application layer and the network layer. The application layer can include a user equipment (UE), an application server, a content delivery network (CDN), or a cloud service platform, etc. The user equipment (UE) can include an IoT device. The network layer can include a radio access network, a core network, a transport network, a multi-access edge computing (MEC) node, etc.

[0083] The access network (RAN) in the embodiments of the present application can be a RAN node. The RAN node can also be referred to as a RAN entity, an access node, an access network device, or a wireless access network device, etc. The RAN node can be a base station, and can also be a transmission reception point (TRP), and can also be an evolved NodeB (eNB or eNodeB) in an LTE system, and can also be a home evolved NodeB (home NodeB, HNB), a baseband unit (BBU), and can also be a radio network controller (RNC) in a cloud radio access network (CRAN) scenario, and can also be a next generation NodeB (gNB).

[0084] The RAN node can also have a reader function. The RAN node with the reader function can be referred to as a RAN reader.

[0085] The reader can be used to read and write data to an Internet of Things device or a tag. The data can be, for example, Internet of Things data. The Internet of Things data can be environmental data. The environmental data can include environmental parameters such as temperature, humidity, illumination, or air quality. The environmental data belongs to AIoT service data. The Internet of Things device can be, for example, an AIoT device. The tag can be a tag that collects or receives data. The tag can be, for example, a passive tag (passive tag), a semi-passive tag (semi-passive tag), an active tag, or an active tag. The Internet of Things device and the AIoT device in the embodiments of the present application can be replaced by the tag.

[0086] The application function entity can communicate with the Internet of Things device through the core network and the RAN node. It should be understood that the communication between the application function entity and the Internet of Things device includes data interaction between the application function entity and the Internet of Things device.

[0087] Exemplarily, the application function entity can take inventory of a plurality of IoT devices through the core network and the RAN node, or write, read, deactivate, or activate the plurality of IoT devices, etc.

[0088] To facilitate the understanding of the communication system architecture of the embodiments of the present application, the communication system architecture provided by the embodiments of the present application is described below in conjunction with FIGS. 1-4.

[0089] FIG. 1 shows a schematic diagram of a communication system architecture provided by the embodiments of the present application.

[0090] As shown in FIG. 1, the communication system architecture includes an application function entity, a core network, a RAN node and an IoT device. The core network includes a network exposure function (NEF) network element, an IoT network function (IoT NF) network element and an access and mobility management function (AMF) network element.

[0091] The IoT NF network element can have all or part of the functions of the AMF network element, and can also be responsible for processing the logic of IoT services. Specifically, it can include: performing IoT service requests in the network (such as inventory, command or registration, etc.), and processing the non-access stratum (NAS) messages of the corresponding IoT service; supporting the inventory, command, registration and message routing of IoT devices; authorizing IoT service requests; performing security authentication for IoT data transmission; performing verification of the identity of the IoT device and performing operations to protect the IoT device when necessary; collecting IoT data and aggregating reports; collecting charging information; managing IoT devices and IoT services, etc. In addition, the AIoT NF network element can be deployed together with the AMF network element or separately, and the embodiments of the present application do not limit it. The identity of the IoT device, for example, an identification (ID).

[0092] The IoT NF network element can also be an AIoT network function (AIoT NF) network element. The AIoT NF network element can have all or part of the functions of the AMF network element, and can also implement security authentication for AIoT data transmission, and management of AIoT devices and AIoT services, etc. The application function entity can communicate with the IoT device through the NEF network element, the IoT NF network element, the AMF network element and the RAN node.

[0093] In this way, the application function entity implements communication with the IoT device through the control plane. The communication system architecture shown in FIG. 1 shows a topology link that can implement communication between the application function entity and the IoT device.

[0094] It should be understood that the network element in the embodiments of the present application, such as an Internet of Things network function (IoT NF) network element, an Ambient Internet of Things network function (AIoT NF) network element, or a network exposure function (NEF) network element, etc., can also exist other naming or definition, and the embodiments of the present application do not make specific limitation here. The entity in the embodiments of the present application, such as an AF entity, can also exist other naming or definition, and the embodiments of the present application do not make specific limitation here.

[0095] FIG. 2 shows another communication system architecture diagram provided by the embodiments of the present application.

[0096] As shown in FIG. 2, the communication system architecture includes an application function entity, a core network, a RAN reader and an IoT device. The core network includes a user plane function (UPF) network element.

[0097] The application function entity can communicate with the IoT device through the UPF network element and the RAN reader. The RAN reader and the IoT device can be connected through an air interface.

[0098] In this way, the application function entity realizes communication with the IoT device through the user plane. The communication system architecture shown in FIG. 2 shows another topology link that can realize communication between the application function entity and the Internet of Things device.

[0099] FIG. 3 shows another communication system architecture diagram provided by the embodiments of the present application.

[0100] The difference between FIG. 3 and FIG. 1 is that the communication system architecture shown in FIG. 3 further includes a UE reader deployed between the RAN node and the IoT device. The UE reader can act as a relay and has the function of the reader. The UE reader can be referred to as an intermediate node. In the communication system architecture shown in FIG. 3, the AMF network element or the IoT NF network element in the core network can not be included.

[0101] The application function entity can communicate with the IoT device through the core network, the RAN node and the UE reader. The RAN node and the UE reader can be connected through an air interface. The UE reader and the IoT device can be connected through an air interface.

[0102] In this way, the application function entity realizes communication with the IoT device through the control plane. The communication system architecture shown in FIG. 3 shows another topology link that can realize communication between the application function entity and the Internet of Things device.

[0103] FIG. 4 shows another communication system architecture diagram provided by the embodiments of the present application.

[0104] Figure 4 differs from Figure 2 in that in Figure 4, the RAN node and the UE reader are included, and the RAN reader is not included.

[0105] The application function entity can communicate with the IoT device through the UPF network element, the RAN node and the UE reader. The RAN node and the UE reader can be connected through an air interface. The UE reader and the IoT device can be connected through an air interface.

[0106] In this way, the application function entity realizes communication with the IoT device through a user plane. The communication system architecture shown in Figure 4 shows another kind of topology link that can realize communication between the application function entity and the IoT device.

[0107] In the embodiments of the present application, the AMF network element can be referred to as AMF. The UPF network element can be referred to as UPF. The IoT NF network element can be referred to as IoT NF. The AIoT NF network element can be referred to as AIoT NF. The application function (AF) entity can be referred to as AF.

[0108] In the embodiments of the present application, the IoT NF network element can be replaced by the AIoT NF network element. The IoT device can be replaced by the AIoT device.

[0109] In order to clearly describe the technical solutions of the embodiments of the present application, the following briefly introduces some terms and technologies involved in the embodiments of the present application:

[0110] 1. N3 tunnel

[0111] The tunnel can be understood as a data transmission channel.

[0112] The N3 tunnel can be a data transmission channel between the UPF network element and the radio access network established on the N3 interface, and can be used to carry and transmit data flow. The N3 tunnel can encapsulate and transmit data packets using the GPRS Tunneling Protocol-User plane (GTP-U) protocol. That is, the N3 tunnel can be a tunnel based on the GTP-U protocol.

[0113] The N3 interface can be a logical interface, and the N3 interface can define the communication standards and protocols between the radio access network and the UPF network element.

[0114] In some possible implementations, the tunnel can be referred to as a bearer, and can also be referred to as a connection or a path, etc.

[0115] 2. N6 tunnel

[0116] The N6 tunnel can be a tunnel established through an N6 interface.

[0117] In the embodiments of the present application, the N6 tunnel can be a data transmission channel between a UPF network element and an application function entity. The N6 interface can be an interface connecting the UPF network element and the application function entity. The N6 tunnel can be an N6 ptp tunnel. The N6 ptp tunnel can be understood as a point-to-point (ptp) tunnel established through the N6 interface.

[0118] The N6 tunnel can be a tunnel based on the GTP-U protocol or a tunnel based on the internet protocol (IP).

[0119] 3. Tunnel endpoint identifier (TEID)

[0120] The TEID can be used to identify the end point of the GPRS Tunneling Protocol (GTP) tunnel to distinguish different tunnels and sessions. The GPRS Tunneling Protocol tunnel is, for example, a tunnel based on the GTP-U protocol. The tunnel based on the GTP-U protocol can be an N3 tunnel or an N6 tunnel.

[0121] The tunnel end point of the N3 tunnel can also be identified by a fully qualified tunnel endpoint identifier (F-TEID). The F-TEID can include the IP address and port number of the network element (or device).

[0122] 4. Intermediate node

[0123] The intermediate node of the embodiments of the present application can be understood as a node having a relay function and a reader function. The intermediate node can be an electronic device.

[0124] The electronic device of the embodiments of the present applicationapplicationinclude a handheld device with a communication function, a vehicle-mounted device, etc. For example, some electronic devices are a mobile phone, a tablet computer, a palm computer, a notebook computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with a wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0125] By way of example and not limitation, in the embodiments of the present application, the electronic deviceapplicationalso be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that is directly worn on the body or integrated into the clothes or accessories of the user. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes a device with full functions and large size, which can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and a device that focuses on a certain application function and needs to be used in cooperation with other devices such as a smart phone, such as various smart wristbands and smart jewelry for monitoring vital signs.

[0126] In addition, in the embodiments of the present application, the electronic device can also be a terminal device in an Internet of Things (IoT) system. The IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0127] The electronic device in the embodiments of the present application can also be referred to as a terminal device, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile terminal, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus, etc.

[0128] It can be understood that the number of IoT devices in FIGS. 1-4 can be one or multiple. In the case where the number of IoT devices is multiple, the number of readers in FIGS. 2-4 can be one or multiple. The reader is, for example, a RAN reader or a UE reader. One reader can communicate with multiple IoT devices.

[0129] Exemplarily, taking the inventory of IoT services as an example, and taking the inventory instruction as an IoT service request, in a possible implementation, taking the scenario that the application function entity shown in FIG. 2 or FIG. 4 performs inventory on m IoT devices through a user plane as an example. The core network can establish an N3 tunnel dedicated to each IoT device for each IoT device in the m IoT devices, that is, the core network will establish m N3 tunnels. Through the N3 tunnel dedicated to each IoT device, each IoT device can receive the inventory instruction initiated by the application function entity. Through the N3 tunnel dedicated to each IoT device, the application function entity can receive the information of each IoT device. The information of the IoT device can include the identifier of the IoT device and / or the state information of the IoT device. The state information can include information indicating normal operation or information indicating abnormal operation. Wherein, m is an integer greater than 1.

[0130] In this way, in this possible implementation, in order to realize the inventory of the application function entity on multiple IoT devices, the core network will establish multiple N3 tunnels, which in turn leads to a large configuration overhead of the core network.

[0131] Therefore, an Internet of Things (IoT) communication method is provided in the embodiments of the present application. A first network element of a core network establishes a shared tunnel between the first network element and an access network node, i.e., a first tunnel, and communicates with a plurality of IoT devices based on the first tunnel. The first tunnel can be understood as a shared tunnel shared by the plurality of IoT devices. The first tunnel is established based on first indication information used to indicate the plurality of IoT devices. For example, the first tunnel can include an N3 tunnel. In this way, the core network does not need to establish a dedicated N3 tunnel for each IoT device in the plurality of IoT devices, and thus the communication with the plurality of IoT devices can be implemented, and the configuration overhead of the core network can be reduced.

[0132] The IoT communication method provided in the embodiments of the present application will be described below in combination with FIGS. 5-14.

[0133] FIG. 5 shows a flowchart of the IoT communication method provided in the embodiments of the present application.

[0134] As shown in FIG. 5, the communication method can include S501-S502.

[0135] S501, the first network element can establish the first tunnel.

[0136] The first tunnel is a shared tunnel between the first network element and the access network node, i.e., the first tunnel can be a tunnel shared by the plurality of IoT devices. The first tunnel is established based on the first indication information.

[0137] The first indication information can include one or more of the following: IoT service area information, information of an IoT device group to which the plurality of IoT devices belong, information of an intermediate node corresponding to the plurality of IoT devices, or information of an intermediate node group to which the intermediate node corresponding to the plurality of IoT devices belongs.

[0138] The IoT service area can be understood as an area corresponding to an IoT service. The IoT service area information can be referred to as information of the IoT service area. The IoT service area can include one or more IoT devices. For example, one or more IoT devices are deployed in the IoT service area. Optionally, the intermediate node can be deployed in the IoT service area, or can not be deployed in the IoT service area. In some possible implementation manners of the present application, the IoT service area can be referred to as an IoT service area, an IoT target area, an inventory area, or a command area.

[0139] In a case that the IoT service is an environment IoT service, the IoT service area can be an environment IoT service area (AIoT service area). The IoT target area can be an environment IoT target area (AIoT target area). The IoT target area can be referred to as a target area. The environment IoT target area can also be referred to as a target area.

[0140] The IoT service area information can include one or more of the following: geographical location information of the IoT service area, one or more tracking area identifiers corresponding to the IoT service area, one or more cell identifiers (cell IDs) corresponding to the IoT service area, or one or more base station identifiers corresponding to the IoT service area.

[0141] The geographical location information can be longitude and latitude information, or civic location information. The tracking area identifier can be referred to as a tracking area ID (TA ID). The tracking area identifier can be a tracking area identity (TAI) or a tracking area code (TAC). The cell identifier can be a physical cell identifier (PCI).

[0142] The first network element or the core network can predefine the correspondence between the geographical location information of the IoT service area and the plurality of IoT devices, the correspondence between the tracking area identifier and the plurality of IoT devices, the correspondence between the cell identifier and the plurality of IoT devices, and / or the correspondence between the base station identifier and the plurality of IoT devices.

[0143] The IoT device group (IoT device group) can include a plurality of IoT devices. The information of the IoT device group can include: an identifier of the IoT device group, and / or an identifier of each IoT device in the plurality of IoT devices included in the IoT device group.

[0144] The intermediate node has a relay function and a reader / writer function. The intermediate node can manage a plurality of IoT devices. The information of the intermediate node, for example, an identifier of the intermediate node. The intermediate node, for example, a UE reader / writer.

[0145] The intermediate node group can include one or more intermediate nodes. The information of the intermediate node group can include: an identifier of the intermediate node group, and / or an identifier of each intermediate node in the plurality of intermediate nodes included in the intermediate node group.

[0146] Exemplarily, the first network element can establish the first tunnel based on the first indication information, so that the first tunnel corresponds to the plurality of IoT devices indicated by the first indication information. The first network element can maintain a correspondence between the first tunnel and the plurality of IoT devices.

[0147] The correspondence between the first tunnel and the plurality of IoT devices can be a mapping table in which the first tunnel maps the plurality of IoT devices. The mapping table can include an identification (ID) of each IoT device in the plurality of IoT devices.

[0148] The correspondence between the first tunnel and the plurality of IoT devices can include an IoT device context corresponding to the first tunnel. The IoT device context can include an identification of each IoT device in the plurality of IoT devices.

[0149] The correspondence between the first tunnel and the plurality of IoT devices can also include a correspondence between the first tunnel and the first indication information.

[0150] Exemplarily, the first indication information can be obtained by the first network element from a core network. For example, the first indication information can be predefined by the core network, or can be carried in information used to indicate establishment of the first tunnel. The information used to indicate establishment of the first tunnel can be sent by an application function entity to the core network, or can be generated by an SMF network element in the core network.

[0151] Exemplarily, the first network element can be a user plane function (UPF) network element. In the case where the first network element is a user plane function network element, the first tunnel can be an N3 tunnel.

[0152] S502, the first network element can communicate with a plurality of Internet of Things (IoT) devices based on the first tunnel, and / or the first network element can communicate with at least one intermediate node based on the first tunnel.

[0153] Exemplarily, with the communication system architecture shown in FIG. 2, and the first network element being a UPF network element and the access network node being a RAN reader, and the first tunnel being an N3 tunnel between the UPF network element and the RAN reader, the UPF network element can send an IoT service request from an application function entity to the RAN reader through the N3 tunnel between the UPF network element and the RAN reader. Correspondingly, the RAN reader can receive the IoT service request from the first network element. The RAN reader can send the IoT service request to the plurality of IoT devices through the air interface respectively. For example, the RAN reader can send the IoT service request to the plurality of IoT devices in a multicast or broadcast manner. In this way, the first network element can communicate with the plurality of IoT devices based on the first tunnel.

[0154] With the communication system architecture shown in FIG. 4, and the first network element being a UPF network element, the access network node being a RAN node, the first tunnel being an N3 tunnel between the UPF network element and the RAN node, and the number of intermediate nodes (e.g., UE readers) being multiple, the UPF network element can send the IoT service request from the application function entity to the RAN node via the N3 tunnel between the UPF network element and the RAN node. Correspondingly, the RAN node can receive the IoT service request from the first network element. The RAN node can send the IoT service request to each of the at least one intermediate node via the air interface, respectively. For example, the RAN node can send the IoT service request to the at least one intermediate node in a multicast or broadcast manner. Correspondingly, each of the at least one intermediate node can receive the IoT service request from the RAN node. Each of the at least one intermediate node can send the IoT service request to the multiple IoT devices managed by the respective intermediate node in a broadcast or multicast manner. In this way, the first network element can communicate with the at least one intermediate node based on the first tunnel, and the first network element can communicate with the multiple IoT devices based on the first tunnel.

[0155] The multiple IoT devices are, for example, IoT device 1, IoT device 2, IoT device 3, and IoT device 4 shown in FIG. 5. The at least one intermediate node is, for example, intermediate node 1 and intermediate node 2 shown in FIG. 5. It should be understood that the IoT device 1, IoT device 2, IoT device 3, and IoT device 4 shown in FIG. 5 are merely examples, and are not a limitation on the specific form or quantity of IoT devices in the embodiments of the present application. The intermediate node 1 and intermediate node 2 shown in FIG. 5 are merely examples, and are not a limitation on the specific form or quantity of intermediate nodes in the embodiments of the present application.

[0156] As shown in the embodiment of FIG. 5, the IoT communication method provided by the present application can establish a shared tunnel between the first network element and the access network node, i.e., the first tunnel, so that the core network does not need to establish a dedicated N3 tunnel for each of the multiple first tunnel IoT devices, thereby enabling the first network element to communicate with the multiple IoT devices and / or enabling the first network element to communicate with the at least one intermediate node, and further enabling the application function entity to communicate with the multiple IoT devices. This can reduce the configuration overhead of the core network for establishing tunnels. It can also reduce the configuration overhead of the RAN reader (or RAN node). The first network element communicates with the multiple IoT devices based on the first tunnel. Compared with some possible implementations in which the first network element transmits the IoT service request sent by the application function entity to the RAN reader (or RAN node) via multiple dedicated N3 tunnels, respectively, the IoT communication method provided by the embodiments of the present application can save resources for data transmission, as the first network element does not need to transmit multiple IoT service requests to the RAN node (or RAN reader).

[0157] Exemplarily, in a case that the RAN reader-writer sends IoT service requests to the plurality of IoT devices through the air interface respectively, correspondingly, each IoT device in the plurality of IoT devices can receive the IoT service request through the RAN reader-writer. Each IoT device in the plurality of IoT devices can send response information to the RAN reader-writer through the air interface in response to the IoT service request. The response information can include data returned by the IoT service request indication. For example, in a case that the IoT service request is an inventory instruction, the data returned by the IoT service request indication can include an identifier of the IoT device and / or state information of the IoT device.

[0158] Correspondingly, the RAN reader-writer can receive the response information from each IoT device in the plurality of IoT devices. The RAN reader-writer can send the response information of each IoT device in the plurality of IoT devices to the first network element through the first tunnel. So that the first network element implements transmitting the response information of each IoT device in the plurality of IoT devices to the application function entity.

[0159] The IoT service request can be an inventory instruction, a command, or a registration instruction.

[0160] The command is, for example, write, read, deactivate, or activate. The write can be understood as a command for instructing to write data to the IoT device. The read can be understood as a command for instructing to read data of the IoT device. The deactivate can be understood as a command for instructing to deactivate the IoT device. The activate can be understood as a command for instructing to activate the IoT device.

[0161] The IoT service request can be sent by the application function entity before the first network element establishes the first tunnel, or can be sent by the application function entity after the first network element establishes the first tunnel.

[0162] In this way, the first network element can communicate with the plurality of IoT devices based on the first tunnel, and / or the first network element communicates with at least one intermediate node based on the first tunnel, thereby realizing the application function entity to communicate with the plurality of IoT devices.

[0163] The S501 will be described in combination with some embodiments.

[0164] Exemplarily, taking the first network element as a user plane function network element (UPF network element) and the first tunnel as an N3 tunnel as an example, a session management function (SMF) network element can send first information to the UPF network element. The first information can be used to instruct to establish the N3 tunnel, and the first information can include first indication information. Correspondingly, the UPF network element can receive the first information from the SMF network element.

[0165] The UPF network element can establish a first tunnel (such as an N3 tunnel) based on the first information.

[0166] In this way, the UPF network element can implement the establishment of the shared N3 tunnel between the UPF network element and the RAN node, and further can implement the communication of the UPF network element with multiple IoT devices based on one N3 tunnel.

[0167] It should be understood that the RAN node can be a RAN reader.

[0168] In the embodiments of the present application, the SMF network element can be referred to as SMF. The IoT communication method can be referred to as the communication method.

[0169] The following still takes the first network element as the user plane function network element (UPF network element) and the first tunnel as the N3 tunnel as an example, and describes S501-S502 in FIG. 5 in combination with FIGS. 6A-13.

[0170] S501 in FIG. 5 is described in combination with FIGS. 6A-10.

[0171] FIG. 6A shows another flowchart of the IoT communication method provided by the embodiments of the present application.

[0172] In an embodiment of the present application, the application function entity can trigger the first network element to establish an N3 tunnel, or to establish an N3 tunnel and an N6 tunnel, before initiating an IoT service request, so as to facilitate the application function entity to communicate with multiple IoT devices through a user plane. As shown in FIG. 6A, the IoT communication method can include S601a-S617.

[0173] S601a, the application function entity can send seventh information to the NEF network element. The seventh information can include an identifier (ID) of the application function entity, first indication information and second indication information. Correspondingly, the NEF network element can receive the seventh information from the application function entity.

[0174] The seventh information can be sent by the application function entity to the NEF network element before initiating an IoT service request. The second indication information in the seventh information can be N3 tunnel indication information or N3N6 tunnel indication information. The N3 tunnel indication information is used to indicate the establishment of an N3 tunnel. The N3N6 tunnel indication information is used to indicate the establishment of an N3 tunnel and an N6 tunnel. The N3 tunnel indication information can be referred to as N3 tunnel indication. The N3N6 tunnel indication information can be referred to as N3N6 tunnel indication.

[0175] For example, the N3 tunnel indication can be 0. The N3N6 tunnel indication can be 1.

[0176] In a case that the second indication information in the seventh information is N3 tunnel indication, the seventh information can be used to indicate to establish an N3 tunnel, and the seventh information can further comprise an N6 tunnel address of the application function entity.

[0177] In a case that the second indication information in the seventh information is N3N6 tunnel indication, the seventh information can be used to indicate to establish an N3 tunnel and an N6 tunnel, and the seventh information can further comprise an N6 tunnel address of the application function entity.

[0178] The N6 tunnel address of the application function entity is an N6 tunnel address on the side of the application function entity. The N6 tunnel address of the application function entity can be a GTP protocol address of the application function entity. The GTP protocol address of the application function entity can be a GTP-U protocol address of the application function entity. The N6 tunnel address of the application function entity can also be an IP address of the application function entity. The IP address can be an IPv4 (internet protocol version 4) address or an IPv6 (internet protocol version 6) address.

[0179] In a case that the indication information in the seventh information is N3 tunnel indication, the seventh information can not comprise the N6 tunnel address of the application function entity.

[0180] Optionally, the seventh information can further comprise an IoT service type and a tunnel time. The IoT service type can be inventory, command or registration. The tunnel time can comprise a start time and an end time of a session. The tunnel time can comprise a valid time length of a tunnel. It should be understood that in a case that the IoT service is an AIoT service, the IoT service type can be an AIoT service type.

[0181] Exemplarily, in a case that the seventh information comprises an IoT service type, the seventh information indicating the established first tunnel can implement a service corresponding to the IoT service type. For example, the seventh information indicating the established first tunnel can be used to transmit information of a service corresponding to the IoT service type. The information of the service corresponding to the IoT service type can comprise IoT service request or service data returned by IoT service request indication. The first tunnel is, for example, an N3 tunnel, or an N3 tunnel and an N6 tunnel.

[0182] Exemplarily, in a case that the IoT service type in the seventh information is inventory, the seventh information indicates that the established first tunnel can be used for transmitting inventory instructions or data (such as the identification of the IoT device and / or the status information of the IoT device) returned by the IoT device in response to the inventory instructions.

[0183] In a case that the IoT service type in the seventh information is command, the seventh information indicates that the established first tunnel can be used for transmitting commands or data returned by the IoT device in response to the commands.

[0184] In a case that the IoT service type in the seventh information is registration, the seventh information indicates that the established first tunnel can be used for transmitting registration instructions or registration information returned by the IoT device in response to the registration instructions.

[0185] In a case that the seventh information is used for indicating the establishment of the N3 tunnel, the tunnel time in the seventh information can include the tunnel time of the N3 tunnel. The tunnel time of the N3 tunnel is, for example, the start time and the end time of the N3 tunnel corresponding session, or the effective duration of the N3 tunnel.

[0186] In a case that the seventh information is used for indicating the establishment of the N3 tunnel and the N6 tunnel, the tunnel time in the seventh information can include the tunnel time of the N3 tunnel and the tunnel time of the N6 tunnel. The tunnel time of the N6 tunnel is, for example, the start time and the end time of the N6 tunnel corresponding session, or the effective duration of the N6 tunnel.

[0187] The seventh information includes the tunnel time, so that the subsequent UPF network element can tear down the tunnel at the tunnel establishment completion time or when the tunnel effective duration is reached, or at the termination time indicated by the tunnel time, to achieve resource release and improve resource utilization.

[0188] Optionally, the seventh information can also not include the IoT service type. In a case that the seventh information does not include the IoT service type, the seventh information indicates that the established tunnel can be used for inventory, command and registration.

[0189] Exemplarily, the seventh information can be an IoT shared session establishment request signaling (Nnef_iot_common_session_creation_request). It should be understood that in a case that the IoT service is an AIoT service, the seventh information can be an AIoT shared session establishment request signaling (Nnef_aiot_common_session_creation_request).

[0190] S602, the NEF network element can check the access permission of the application function entity and the tunnel establishment permission.

[0191] Exemplarily, the NEF network element can send a request for indicating checking access right and tunnel establishment right of the application function entity to a unified data management (UDM) network element. The request for indicating checking access right and tunnel establishment right of the application function entity carries the ID of the application function entity. Correspondingly, the UDM network element can receive the request for indicating checking access right and tunnel establishment right of the application function entity from the NEF network element.

[0192] In the embodiments of the present application, the UDM network element can be referred to as UDM for short.

[0193] The UDM network element can pre-store or pre-acquire, from the core network, a registration information set containing registration information of at least one application function entity.

[0194] The UDM network element can send a check confirmation message to the NEF network element in a case where it is confirmed that the registration information set contains the access right and the tunnel establishment right corresponding to the ID of the application function entity. Alternatively, the UDM network element can send the check confirmation message to the NEF network element in a case where it is confirmed that the registration information set contains the ID of the application function entity. The check confirmation message can carry the ID of the application function entity. Correspondingly, the NEF network element can receive the check confirmation message from the UDM network element, which can indicate that the application function entity has the access right and the tunnel establishment right. Then the NEF network element can perform S603a or S603b.

[0195] The UDM network element can send a check denial message to the NEF network element in a case where it is confirmed that the registration information set does not contain the access right and / or the tunnel establishment right corresponding to the ID of the application function entity. Alternatively, the UDM network element can send the check denial message to the NEF network element in a case where it is confirmed that the registration information set does not contain the ID of the application function entity. The check denial message can carry the ID of the application function entity. Correspondingly, the NEF network element can receive the check denial message from the UDM network element, which can indicate that the application function entity does not have the access right and / or the tunnel establishment right. Then the NEF network element can not perform S603a, nor S603b.

[0196] Optionally, the NEF network element can pre-store the registration information set or pre-acquire the registration information set from the core network. The NEF network element can check whether the registration information set contains the access right and the tunnel establishment right corresponding to the ID of the application function entity, or check whether the registration information set contains the ID of the application function entity.

[0197] If the registration information set contains the access right and the tunnel establishment right corresponding to the ID of the application function entity, or contains the ID of the application function entity, it can be indicated that the application function entity has the access right and the tunnel establishment right, and the NEF network element can perform S603a or S603b.

[0198] If the registration information set does not contain the access right and / or the tunnel establishment right corresponding to the ID of the application function entity, or does not contain the ID of the application function entity, it can be indicated that the application function entity does not have the access right and / or the tunnel establishment right, and the NEF network element can not perform S603a or S603b.

[0199] Optionally, the NEF network element can also send a request for indicating checking the access right and the tunnel establishment right of the application function entity to the IoT NF network element. Correspondingly, the IoT NF network element can receive the request for indicating checking the access right and the tunnel establishment right of the application function entity from the NEF network element. The IoT NF network element can check the access right and the tunnel establishment right of the application function entity based on the registration information set stored in advance or obtained from the core network in advance. The specific implementation principle can be referred to the specific implementation principle of checking the access right and the tunnel establishment right of the application function entity by the UDM network element or the NEF network element based on the registration information set, which will not be described here.

[0200] In the case of checking and confirming that the application function entity has the access right and the tunnel establishment right, the IoT NF network element can send a check confirmation message to the NEF network element. Correspondingly, the NEF network element can receive the check confirmation message from the IoT NF network element, and the NEF network element can perform S603a or S603b.

[0201] In the case of checking and confirming that the application function entity does not have the access right and / or the tunnel establishment right, the IoT NF network element can send a check denial message to the NEF network element. Correspondingly, the NEF network element can receive the check denial message from the IoT NF network element, and the NEF network element can not perform S603a or S603b.

[0202] In this way, by checking the access right and the tunnel establishment right of the application function entity, the probability of establishing a tunnel (such as an N3 tunnel and / or an N6 tunnel) for an application function entity that does not have the access right and / or the tunnel establishment right can be reduced, and thus the impact on the security of IoT service data transmission can be reduced.

[0203] Optionally, in the case that the first indication information carried in the seventh information is information that the core network cannot identify, the NEF network element can convert the first indication information in the seventh information into information that the core network can identify.

[0204] Exemplarily, the first indication information which cannot be recognized by the core network can be: the longitude and latitude information of the IoT service area and / or the street location information of the IoT service area.

[0205] In a case that the first indication information carried in the seventh information is the longitude and latitude information of the IoT service area and / or the street location information of the IoT service area, the NEF network element can convert the longitude and latitude information of the IoT service area and / or the street location information of the IoT service area in the seventh information into the TA ID corresponding to the IoT service area or the cell ID corresponding to the IoT service area.

[0206] S603a, the NEF network element can send the fourth information or the eighth information to the IoT NF network element. The fourth information and the eighth information can both be used to indicate the establishment of an N3 tunnel, or be used to indicate the establishment of an N3 tunnel and an N6 tunnel. Correspondingly, the IoT NF network element can receive the fourth information or the eighth information from the NEF network element.

[0207] Exemplarily, in a case that the NEF network element converts the first indication information in the seventh information into information recognizable by the core network, the NEF network element can send the fourth information to the IoT NF network element. Correspondingly, the IoT NF network element can receive the fourth information from the NEF network element. The IoT NF network element can perform S604.

[0208] The first indication information contained in the fourth information can be the first indication information converted from the first indication information carried in the seventh information. The fourth information can further include information other than the first indication information contained in the seventh information.

[0209] For example, taking an example that the seventh information contains the identifier of the AF entity, the first indication information, the IoT service type, the second indication information, the tunnel time and the N6 tunnel address of the AF entity, the information other than the first indication information contained in the seventh information includes: the identifier of the AF entity, the IoT service type, the second indication information, the tunnel time and the N6 tunnel address of the AF entity.

[0210] In a case that the NEF network element does not convert the first indication information in the seventh information into information recognizable by the core network, the NEF network element can send the eighth information to the IoT NF network element. Correspondingly, the IoT NF network element can receive the eighth information from the NEF network element.

[0211] The first indication information carried in the eighth information sent by the NEF network element to the IoT NF network element is the same as the first indication information in the seventh information. The first indication information carried in the eighth information can be information identifiable by the core network, or information unidentifiable by the core network. The eighth information can further include information other than the first indication information included in the seventh information.

[0212] For the first indication information, the information identifiable by the core network is, for example, information of an IoT device group to which the plurality of IoT devices belong, information of an intermediate node corresponding to the plurality of IoT devices, information of an intermediate node group to which the intermediate node corresponding to the plurality of IoT devices belongs, one or more tracking area identifiers corresponding to the IoT service area, one or more cell identifiers corresponding to the IoT service area, or one or more base station identifiers corresponding to the IoT service area.

[0213] Exemplarily, in a case where the IoT NF network element receives the eighth information from the NEF network element, and the first indication information in the eighth information is information unidentifiable by the core network, the IoT NF network element can convert the first indication information in the eighth information into information identifiable by the core network, and perform S604.

[0214] The specific implementation principle of the IoT NF network element converting the first indication information in the eighth information into information identifiable by the core network can refer to the specific implementation principle of the NEF network element converting the latitude and longitude information of the IoT service area into the TA ID or the cell identifier corresponding to the IoT service area, which will not be described herein again.

[0215] Exemplarily, in a case where the IoT NF network element receives the eighth information from the NEF network element, and the first indication information carried in the eighth information is information identifiable by the core network, the IoT NF network element can perform S604.

[0216] S603b, the NEF network element can send fourth information to the SMF network element. The fourth information can be used to indicate the establishment of an N3 tunnel, or used to indicate the establishment of an N3 tunnel and an N6 tunnel. Correspondingly, the SMF network element can receive the fourth information from the NEF network element.

[0217] In a case where the SMF network element receives the fourth information from the NEF network element, the SMF network element can perform S605.

[0218] It can be understood that S603b is an optional step.

[0219] In a possible implementation manner, the communication method provided by the embodiment of the application can include S603b, and does not include S603a and S604.

[0220] In another possible implementation, the communication method provided by the embodiment of the present application can include S603a and S604, and does not include S603b.

[0221] S604, the IoT NF network element can send third information to the SMF network element. The third information can be used to indicate the establishment of the N3 tunnel, or used to indicate the establishment of the N3 tunnel and the N6 tunnel. The third information can include the first indication information. Correspondingly, the SMF network element can receive the third information from the IoT NF network element.

[0222] The first indication information in the third information is information that can be recognized by the core network.

[0223] In the case where the IoT NF network element receives the fourth information, the third information can include the information contained in the fourth information.

[0224] In the case where the IoT NF network element receives the eighth information, and the eighth information contains the first indication information that cannot be recognized by the core network, the third information can include the first indication information converted from the first indication information in the eighth information, and the information contained in the eighth information except the first indication information.

[0225] In the case where the IoT NF network element receives the eighth information, and the eighth information contains the first indication information that can be recognized by the core network, the third information can include the information contained in the eighth information.

[0226] Exemplarily, in the case where the third information is used to indicate the establishment of the N3 tunnel, the third information can include the identifier of the application function entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, and the N3 tunnel indication.

[0227] In the case where the third information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the third information can include the identifier of the application function entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, the tunnel time of the N6 tunnel, the N6 tunnel address of the application function entity (such as the IP address of the application function entity or the GTP protocol address of the application function entity), and the N3N6 tunnel indication.

[0228] S605, the SMF network element can send first information to the UPF network element. The first information is used to indicate the establishment of the N3 tunnel, or used to indicate the establishment of the N3 tunnel and the N6 tunnel, and the first information can include the first indication information. Correspondingly, the UPF network element can receive the first information from the SMF network element.

[0229] It should be understood that, in the case where the SMF network element receives the third information, the first indication information in the first information can be the same as the first indication information in the third information.

[0230] In a case that the SMF network element receives the fourth information, the first indication information in the first information can be the same as the first indication information in the fourth information.

[0231] Exemplarily, the SMF network element can determine the UPF network element corresponding to the first indication information in the third information or the fourth information based on the correspondence between the first indication information and the UPF network element, and the first indication information in the third information or the fourth information. The SMF network element can send the first information to the determined UPF network element.

[0232] The correspondence between the first indication information and the UPF network element can be pre-configured in the core network by the operator based on a service level agreement (SLA). The SMF network element can obtain the correspondence between the first indication information and the UPF network element from the core network.

[0233] Optionally, the SMF network element can determine the UPF network element corresponding to the application function entity based on the correspondence between the application function entity and the UPF network element, and the identifier of the application function entity in the third information or the fourth information. The SMF network element can send the first information to the determined UPF network element.

[0234] The correspondence between the application function entity and the UPF network element can be pre-configured in the core network by the operator based on a service level agreement (SLA). The SMF network element can obtain the correspondence between the application function entity and the UPF network element from the core network.

[0235] Optionally, the seventh information, the eighth information, the fourth information and the third information can all carry the identifier of the UPF network element. The identifier of the UPF network element can be an application function entity, which is determined based on the correspondence between the application function entity and the UPF network element and the identifier of the application function entity. The SMF network element can send the first information to the UPF network element corresponding to the identifier of the UPF network element.

[0236] The correspondence between the application function entity and the UPF network element obtained by the application function entity can be synchronized to the application function entity by the core network or the operator.

[0237] Exemplarily, the first information can include second indication information.

[0238] In a case that the first information includes N3 tunnel indication, the first information can be used to indicate establishment of the N3 tunnel.

[0239] In a case that the first information includes N3N6 tunnel indication and N6 tunnel address of the application function entity, the first information can be used to indicate establishment of the N3 tunnel and the N6 tunnel.

[0240] Optionally, in a case that the first information does not include the N6 tunnel address of the application function entity, the first information can be used to indicate a case that the N3 tunnel is established.

[0241] In a case that the first information includes the N6 tunnel address of the application function entity, the first information is used to indicate a case that the N3 tunnel and the N6 tunnel are established.

[0242] It should be understood that, in a case that the first information is used to indicate the establishment of the N3 tunnel, the first information can also include the tunnel time of the N3 tunnel and / or the IoT service type.

[0243] In a case that the first information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the first information can also include the tunnel time of the N6 tunnel.

[0244] Optionally, the first information can also include the identifier of the AF entity. In this way, the N3 tunnel can be corresponding or bound to the AF entity.

[0245] S606, the UPF network element can obtain or allocate the uplink tunnel identifier of the N3 tunnel.

[0246] The uplink tunnel identifier of the N3 tunnel is the uplink tunnel identifier on the side of the UPF network element. The tunnel identifier can be a TEID or an F-TEID. Taking the tunnel identifier as a TEID as an example, the uplink tunnel identifier can be an uplink tunnel endpoint identifier (UL TEID), and the uplink tunnel identifier on the side of the UPF network element can be referred to as a UPF UL TEID.

[0247] Exemplarily, the first information can also carry the uplink tunnel identifier of the N3 tunnel configured by the SMF network element. The UPF network element can obtain the uplink tunnel identifier of the N3 tunnel carried in the first information.

[0248] Optionally, in a case that the first information does not carry the uplink tunnel identifier of the N3 tunnel, the UPF network element can configure or allocate the uplink tunnel identifier of the N3 tunnel.

[0249] Optionally, in a case that the first information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the UPF network element can also obtain the N6 tunnel address of the application function entity carried in the first information, and the UPF network element can perform S607 to establish the N6 tunnel.

[0250] Optionally, in a case that the first information is used to indicate the establishment of the N3 tunnel, the UPF network element can perform S607.

[0251] S607, the UPF network element can interact with the application function entity to establish the N6 tunnel.

[0252] Exemplarily, the UPF network element can configure the N6 tunnel address of the UPF network element. The N6 tunnel address of the UPF network element is the N6 tunnel address on the UPF network element side. The UPF network element can send the N6 tunnel address of the UPF network element to the application function entity based on the N6 tunnel address of the application function entity, so as to establish the N6 ptp tunnel between the UPF network element and the application function entity.

[0253] Optionally, in the case that the first information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the first information can also carry the N6 tunnel address of the UPF network element configured by the SMF network element. The UPF network element can also obtain the N6 tunnel address of the UPF network element carried in the first information, so as to establish the N6 ptp tunnel between the UPF network element and the application function entity.

[0254] In this way, the UPF network element establishes the N6 tunnel based on the first information.

[0255] In the case that the establishment of the N6 tunnel is completed, the UPF network element can perform S608.

[0256] S608, the UPF network element can send a first response to the SMF network element. The first response is a response to the first information, and the first response includes the uplink tunnel identifier of the N3 tunnel. Correspondingly, the SMF network element can receive the first response from the UPF network element.

[0257] Optionally, in the case that the first information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the first response can also include the N6 tunnel address on the UPF network element side. Optionally, the first response can also include information indicating that the establishment of the N6 tunnel is successful.

[0258] In the case that the first response from the UPF network element is received, the SMF network element can perform S610.

[0259] In the case that the first response includes the N6 tunnel address on the UPF network element side, the SMF network element can also perform S609.

[0260] S609, the UPF network element can synchronize the N6 tunnel address on the UPF network element side to the IoT NF network element, so as to facilitate the management of the IoT service by the IoT NF network element.

[0261] S610, the SMF network element can send sixth information to the AFM network element. The sixth information is used to indicate the establishment of the N3 tunnel, and the sixth information includes the first indication information and the uplink tunnel identifier of the N3 tunnel. Correspondingly, the AFM network element can receive the sixth information from the SMF network element.

[0262] It should be understood that the first indication information in the sixth information can be the same as the first indication information in the first information. The sixth information can also include the information contained in the first information.

[0263] Optionally, the sixth information can further comprise an identification of the application function entity and an identification (ID) of the UPF network element, so as to facilitate the AFM network element to determine the RAN reader based on the identification of the UPF network element.

[0264] Optionally, S609 and S610 can be executed concurrently.

[0265] S611, the AFM network element can determine the RAN reader based on the first indication information or the identification of the UPF network element, and send the sixth information to the RAN reader.

[0266] Illustratively, the AFM network element can determine the RAN reader corresponding to the first indication information in the sixth information based on a pre-stored correspondence between the first indication information and the RAN reader.

[0267] Optionally, the AFM network element can determine the RAN reader corresponding to the identification of the UPF network element in the sixth information based on a pre-stored correspondence between the identification of the UPF network element and the RAN reader.

[0268] S612, the RAN reader can send a fifth response to the SMF network element through the AFM network element. The fifth response is a response to the sixth information, and the fifth response comprises a downlink tunnel identification of the N3 tunnel. Correspondingly, the SMF network element can receive the fifth response sent by the RAN reader through the AFM network element.

[0269] Illustratively, upon receiving the sixth information, the RAN reader can configure a downlink tunnel identification of the N3 tunnel. The downlink tunnel identification of the N3 tunnel is, for example, a downlink tunnel identification on the RAN reader side or a downlink tunnel identification on the RAN node side. Still taking the tunnel identification as an example of TEID, the downlink tunnel identification can be a downlink tunnel endpoint identifier (DL TEID), the downlink tunnel identification on the RAN reader side can be referred to as RAN reader DL TEID, and the downlink tunnel identification on the RAN node side can be referred to as RAN node DL TEID.

[0270] In this way, for the RAN reader, the N3 tunnel establishment between the RAN reader and the UPF network element is completed. It should be understood that the N3 tunnel corresponds to the first indication information in the sixth information. The RAN reader can maintain the correspondence between the N3 tunnel and the first indication information. The RAN reader can also maintain the uplink tunnel identifier of the N3 tunnel, the uplink tunnel identifier of the N3 tunnel, and the identifier of the application function entity. The correspondence between the N3 tunnel and the first indication information includes information about the correspondence between the N3 tunnel established by the embodiment of the application and the first indication information in the sixth information. In order to facilitate the RAN reader to determine the common N3 tunnel corresponding to the IoT device when receiving the IoT service data of the IoT device.

[0271] The RAN reader can send the fifth response to the AFM network element. Correspondingly, the AFM network element can receive the fifth response from the RAN reader.

[0272] The AFM network element can send the fifth response to the SMF network element. Correspondingly, the SMF network element can receive the fifth response from the AFM network element.

[0273] The SMF network element can synchronize the downlink tunnel identifier of the N3 tunnel to the UPF network element. Correspondingly, the UPF network element can receive the downlink tunnel identifier of the N3 tunnel from the SMF network element.

[0274] When the UPF network element receives the downlink tunnel identifier of the N3 tunnel from the SMF network element, the UPF network element can perform S614.

[0275] In this way, for the UPF network element, the N3 tunnel establishment between the RAN reader and the UPF network element is completed. It should be understood that the N3 tunnel corresponds to the first indication information in the first information. The UPF network element can maintain the correspondence between the N3 tunnel and the first indication information. The correspondence between the N3 tunnel and the first indication information includes information about the correspondence between the N3 tunnel established by the embodiment of the application and the first indication information in the first information. In order to facilitate the UPF network element to determine the common N3 tunnel corresponding to the first indication information in the IoT service request when receiving the IoT service request.

[0276] S614, the UPF network element can send a synchronization confirmation message to the SMF network element, indicating that the UPF network element receives the downlink tunnel identifier of the N3 tunnel from the SMF network element. Correspondingly, the SMF network element can receive the synchronization confirmation message from the UPF network element.

[0277] As shown in S606-S614, the N3 tunnel establishment is successful, which can indicate that the UPF network element completes the N3 tunnel establishment.

[0278] The UPF network element can maintain a correspondence between the N3 tunnel and the first indication information, and an uplink tunnel identifier of the N3 tunnel, an uplink tunnel identifier of the N3 tunnel, and an identifier of the application function entity. In the case where the first indication information in the seventh information is IoT service area information, the correspondence between the N3 tunnel and the first indication information is, for example, a correspondence between the N3 tunnel and the IoT service area information (such as a TA ID or a cell identifier corresponding to an IoT service area).

[0279] The SMF network element can send a second response to the IoT NF network element. The second response is a response to the third information, and the second response contains an uplink tunnel identifier of the N3 tunnel and a downlink tunnel identifier of the N3 tunnel. Correspondingly, the IoT NF network element can receive the second response from the SMF network element. In this way, the IoT NF network element can perform S616.

[0280] The uplink tunnel identifier of the N3 tunnel and the downlink tunnel identifier of the N3 tunnel in the second response can be used to indicate that the N3 tunnel is successfully established.

[0281] Exemplarily, in the case where the third information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the second response can further include an N6 tunnel address of the UPF network element. The N6 tunnel address of the UPF network element is the N6 tunnel address on the side of the UPF network element.

[0282] The second response can be an IoT shared session establishment response signaling (Nnef_iot_common_session_creation_response). It should be understood that in the case where the IoT service is an AIoT service, the second response can be an AIoT shared session establishment response signaling (Nnef_aiot_common_session_creation_response).

[0283] The SMF network element can send a third response to the NEF network element. The third response can be a response to the fourth information. The second response contains an uplink tunnel identifier of the N3 tunnel and a downlink tunnel identifier of the N3 tunnel. Correspondingly, the NEF network element can receive the third response from the SMF network element, so that the NEF network element performs S617.

[0284] Exemplarily, in the case where the fourth information is used to indicate the establishment of the N3 tunnel and the N6 tunnel, the third response can further include an N6 tunnel address of the UPF network element.

[0285] It can be understood that S615b is an optional step.

[0286] In the case that the communication method provided by the embodiments of the present application includes S603b, the communication method provided by the embodiments of the present application can include S615b, and can not include S615a and S616.

[0287] In the case that the communication method provided by the embodiments of the present application includes S603a and S604, the communication method provided by the embodiments of the present application can include S615a and S616, and can not include S615b.

[0288] S616, the IoT NF network element can send a third response or a sixth response to the NEF network element. The sixth response can be a response of the eighth information. The sixth response contains the uplink tunnel identifier of the N3 tunnel and the downlink tunnel identifier of the N3 tunnel. Correspondingly, the NEF network element can receive the third response or the sixth response from the IoT NF network element, so as to facilitate the NEF network element to perform S617.

[0289] Exemplarily, in the case that the eighth information is used to indicate that the N3 tunnel and the N6 tunnel are established, the sixth response can further include the N6 tunnel address of the UPF network element.

[0290] S617, the NEF network element can send a seventh response to the application function entity. The seventh response can be a response of the seventh information. The seventh response can contain the uplink tunnel identifier of the N3 tunnel and the downlink tunnel identifier of the N3 tunnel. Correspondingly, the application function entity can receive the second response from the NEF network element.

[0291] Exemplarily, in the case that the seventh information is used to indicate that the N3 tunnel and the N6 tunnel are established, the seventh response can further include the N6 tunnel address of the UPF network element.

[0292] Optionally, the second response, the third response, the sixth response and the seventh response can all further include information indicating that the N3 tunnel is successfully established.

[0293] As shown in FIG. 6, before the application function entity initiates the IoT service, the application function entity can trigger the core network or the first network element (such as the UPF network element) to establish the N3 tunnel or establish the N3 tunnel and the N6 tunnel by sending the seventh information to the NEF network element. Among them, the first indication information in the seventh information, the eighth information, the fourth information, the third information, the first information and the sixth information all correspond to the N3 tunnel, that is, the N3 tunnel in the embodiment of the application is established based on the first indication information. So that the UPF network element can communicate with the plurality of IoT devices through the N3 tunnel, so as to realize that the application function entity communicates with the plurality of IoT devices through the user plane. The N3 tunnel is a shared tunnel shared by the plurality of IoT devices. In this way, the core network does not need to establish a dedicated N3 tunnel for each IoT device in the plurality of IoT devices, thereby reducing the configuration overhead of the core network. It can be understood that the establishment of the N3 tunnel also needs the configuration of the access network node (such as the RAN reader), therefore, compared with the configuration of the access network node when a dedicated N3 tunnel is established for each IoT device in the plurality of IoT devices, the Internet of Things communication method provided by the embodiment of the application can also reduce the configuration overhead of the access network node.

[0294] It can be understood that in the case where the seventh information indicates the establishment of the N3 tunnel, the eighth information, the fourth information, the third information and the first information all indicate the establishment of the N3 tunnel, and the communication method provided by the embodiment of the application can complete the establishment of the N3 tunnel through the processes shown in S601a-S606, S608, S610-S617.

[0295] In the case where the seventh information indicates the establishment of the N3 tunnel and the N6 tunnel, the eighth information, the fourth information, the third information and the first information all indicate the establishment of the N3 tunnel and the N6 tunnel, and the communication method provided by the embodiment of the application can complete the establishment of the N3 tunnel and the N6 tunnel through the processes shown in S601a-S617.

[0296] In the case where the core network or the UPF network element completes the establishment of the N3 tunnel and the N6 tunnel, the application function entity can transmit the IoT service request to the UPF network element through the N6 tunnel between the application function entity and the UPF network element. Correspondingly, the UPF network element can receive the IoT service request from the application function entity. The UPF network element can send the IoT service request to the RAN reader through the N3 tunnel corresponding to the first indication information in the IoT service request, so that the RAN reader sends the IoT service request to the plurality of IoT devices associated with the RAN reader through the air interface respectively.

[0297] Correspondingly, each IoT device in the plurality of IoT devices can receive the IoT service request from the RAN reader.

[0298] Each of the plurality of IoT devices can respond to the IoT service request and send IoT service data to the RAN reader respectively through the air interface. Correspondingly, the RAN reader can receive the IoT service data returned from each of the plurality of IoT devices.

[0299] The RAN reader can send the IoT service data of each of the plurality of IoT devices to the UPF network element through the N3 tunnel corresponding to the first indication information in the IoT service request. Correspondingly, the UPF network element can receive the IoT service data of each of the plurality of IoT devices from the RAN reader. The UPF network element can send the IoT service data of each of the plurality of IoT devices to the application function entity through the N6 tunnel.

[0300] In this way, the application function entity can communicate with the plurality of IoT devices through the user plane.

[0301] When the UPF network element completes communication with the plurality of IoT devices through the N3 tunnel, the UPF network element can tear down the N3 tunnel. Alternatively, from the time when the UPF network element completes establishment of the N3 tunnel, to the time when the N3 tunnel reaches the effective duration or at the time of termination of the N3 tunnel, the UPF network element can tear down the N3 tunnel. The UPF network element completes communication with the plurality of IoT devices through the N3 tunnel, for example, the UPF network element receives the IoT service data of each of the plurality of IoT devices from the RAN reader.

[0302] In the N3 tunnel in the embodiments of the present application, since the N3 tunnel is a shared tunnel, the effective duration of the N3 tunnel can be greater than the effective duration of the dedicated N3 tunnel in one possible implementation. Compared with the scenario in one possible implementation, the core network establishes m dedicated N3 tunnels for m IoT devices to implement inventory of the m IoT devices by the application function entity. When the core network completes communication with one IoT device, the core network tears down the dedicated N3 tunnel of the one IoT device. Alternatively, the core network tears down the dedicated N3 tunnel of the one IoT device based on the effective duration or the termination time of the dedicated N3 tunnel of the one IoT device. The core network will tear down the m dedicated N3 tunnels, resulting in the situation that the core network frequently tears down the dedicated N3 tunnels.

[0303] When the application function entity needs to inventory n IoT devices through the user plane next time, similar to the scenario of inventory of the m IoT devices by the application function entity, the core network establishes n dedicated N3 tunnels for each of the n IoT devices to implement inventory of the n IoT devices by the application function entity. Wherein, n is an integer greater than 1.

[0304] The core network also tears down the n special N3 tunnels, resulting in the core network existing in the case of frequently tearing down special N3 tunnels.

[0305] Thus, in the scenario of the application function entity performing inventory on multiple IoT devices multiple times, the core network establishes multiple N3 tunnels multiple times and tears down the multiple N3 tunnels established multiple times, that is, the core network frequently tears down and establishes N3 tunnels. In this way, the core network also has a large configuration overhead.

[0306] Alternatively, the N6 tunnel can also be established based on the first indication information, and the UPF network element can maintain a correspondence between the N6 tunnel and the first indication information. The specific implementation principle of tearing down the N6 tunnel can be referred to the specific implementation principle of tearing down the N3 tunnel, which is not described here.

[0307] FIG. 6B shows another flowchart of the IoT communication method provided by the embodiments of the present application.

[0308] The difference between the flow of the IoT communication method shown in FIG. 6B and the flow of the IoT communication method shown in FIG. 6A is that in FIG. 6A, the RAN reader-writer can configure the downlink tunnel identifier of the first tunnel (such as the N3 tunnel) after receiving the uplink tunnel identifier of the first tunnel (such as the N3 tunnel). In FIG. 6B, the RAN reader-writer can configure the downlink tunnel identifier of the first tunnel (such as the N3 tunnel) before receiving the uplink tunnel identifier of the first tunnel (such as the N3 tunnel). FIG. 6B can include S618-S622 and not include S610-S612.

[0309] As shown in FIG. 6B, the flow of the IoT communication method can include S601a, S602, S603a, S604, S605, S618-S620, S613-S614, S606-S608, S621-S622, S609, S615a, S616-S617.

[0310] Alternatively, the flow of the IoT communication method can include S601a, S602, S603b, S605, S618-S620, S613-S614, S606-S608, S621-S622, S609, S615b, and S617.

[0311] The specific implementation principles of the steps in S601a, S602, S603a, S604, S603b, S605, S613-S614, S606-S608, S609, S615a, S615b, S616-S617 can be referred to the specific implementation principles of the corresponding steps in FIG. 6A, which are not described here.

[0312] S618, after the SMF network element sends the first information to the UPF network element, the SMF network element can send ninth information to the AMF network element. The ninth information is used to indicate the establishment of the N3 tunnel. The ninth information can include the first indication information. Correspondingly, the AMF network element can receive the ninth information from the SMF network element.

[0313] It should be understood that the first indication information in the ninth information is the same as the first indication information in the first information.

[0314] Optionally, the ninth information can also include information contained in the first information other than the first indication information. For example, the ninth information can also include one or more of the following: the identifier of the AF entity, the identifier of the UPF network element, the IoT service type, or the tunnel time of the N3 tunnel.

[0315] S619, the AFM network element can determine the RAN reader based on the first indication information or the identifier of the UPF network element, and send the ninth information to the RAN reader.

[0316] The specific implementation principle of the AFM network element determining the RAN reader based on the first indication information or the identifier of the UPF network element can refer to the specific implementation principle of the AFM network element determining the RAN reader based on the first indication information or the identifier of the UPF network element in S611.

[0317] S620, the RAN reader can send an eighth response to the SMF network element through the AFM network element. The eighth response is a response to the ninth information, and the eighth response can include the downlink tunnel identifier of the N3 tunnel. Correspondingly, the SMF network element can receive the eighth response sent by the RAN reader through the AFM network element.

[0318] Optionally, the eighth response can also include the identifier of the RAN reader.

[0319] Optionally, the eighth response can also include the identifier of the AF entity, so as to realize the binding of the AF entity and the N3 tunnel.

[0320] In the case that the SMF network element receives the eighth response sent by the RAN reader through the AFM network element, the SMF network element can perform S613.

[0321] S613, the SMF network element can synchronize the downlink tunnel identifier of the N3 tunnel to the UPF network element. Correspondingly, the UPF network element can receive the downlink tunnel identifier of the N3 tunnel from the SMF network element.

[0322] In the case that the UPF network element receives the downlink tunnel identifier of the N3 tunnel from the SMF network element, the UPF network element can perform S614 and S606.

[0323] Optionally, S606 and S614 can be executed concurrently or sequentially.

[0324] S614, the UPF network element can send a synchronization confirmation message to the SMF network element, indicating that the UPF network element receives the downlink tunnel identifier of the N3 tunnel from the SMF network element. Correspondingly, the SMF network element can receive the synchronization confirmation message from the UPF network element.

[0325] S606, the UPF network element can allocate the uplink tunnel identifier of the N3 tunnel.

[0326] Optionally, in the case where the first information is used to indicate the establishment of the N3 tunnel, the UPF network element can perform S607.

[0327] S607, the UPF network element can interact with the application function entity to establish the N6 tunnel.

[0328] Optionally, the UPF network element can perform S607 after S622 and before S609. That is, the UPF network element can establish the N6 tunnel after completing the establishment of the N3 tunnel.

[0329] S608, the UPF network element can send a first response to the SMF network element. The first response is a response to the first information, and the first response includes the uplink tunnel identifier of the N3 tunnel. Correspondingly, the SMF network element can receive the first response from the UPF network element.

[0330] S621, the SMF network element can send a tenth information to the RAN reader through the AMF network element. The tenth information can include the uplink tunnel identifier (such as UPF UL TEID) of the N3 tunnel. Correspondingly, the RAN reader can receive the tenth information from the SMF network element through the AMF network element.

[0331] S622, the RAN reader can send a first confirmation message to the SMF network element through the AMF network element. The first confirmation message can indicate that the RAN reader receives the tenth information. Correspondingly, the SMF network element can receive the first confirmation message from the RAN reader through the AMF network element.

[0332] In the case where the SMF network element receives the first confirmation message from the RAN reader through the AMF network element, the SMF network element can perform S609 and S615a, or perform S609 and S615b.

[0333] S609, the UPF network element can synchronize the N6 tunnel address on the UPF network element side to the IoT NF network element, so as to facilitate the management of the IoT service by the IoT NF network element.

[0334] Optionally, S609 can be performed concurrently with S621. S609 can also be performed concurrently with S615a or S615b.

[0335] FIG. 6C shows another flow diagram of the method for IoT communication according to an embodiment of the present application.

[0336] The difference between FIG. 6C and FIG. 6A or FIG. 6B is that in FIG. 6C, the third information is sent by the IoT NF network element in the case that the IoT NF network element receives the fifth information or the IoT service request from the AF entity and confirms that the AF entity has access rights and tunnel establishment rights. The fifth information is used to indicate the establishment of an N3 tunnel, or is used to indicate the establishment of an N3 tunnel and an N6 tunnel. For details, see S601b and S623.

[0337] As shown in FIG. 6C, the flow of the method for IoT communication can include S601b, S623, S604-S614, S615a, and S624.

[0338] Alternatively, the flow of the method for IoT communication can include S601b, S623, S604-S605, S618-S620, S613-S614, S606-S608, S621-S622, S609, S615a, and S624.

[0339] The specific implementation principles of the steps in S604-S614 and S615a can be found in the specific implementation principles of the corresponding steps in FIG. 6A. The specific implementation principles of the steps in S618-S620 and S621-S622 can be found in the specific implementation principles of the corresponding steps in FIG. 6B, which will not be described here.

[0340] S601b, the AF entity can send the fifth information or the IoT service request to the IoT NF network element. Correspondingly, the IoT NF network element can receive the fifth information or the IoT service request from the AF entity.

[0341] The fifth information can include an identifier ID of the AF entity, first indication information, an IoT service type, second indication information, and tunnel time.

[0342] In the case that the second indication information in the fifth information is an N3 tunnel indication, the fifth information can further include tunnel time of the N3 tunnel.

[0343] In the case that the second indication information in the fifth information is an N3N6 tunnel indication, the fifth information can further include tunnel time of the N3 tunnel, tunnel time of the N6 tunnel, and an N6 tunnel address of the AF entity.

[0344] The IoT service request can comprise an identification ID of the AF entity, the first indication information, an IoT service type, a tunnel time of the N3 tunnel. Optionally, the IoT service request can further comprise a tunnel time of the N6 tunnel.

[0345] S623, the IoT NF network element can check the access right and the tunnel establishment right of the AF entity.

[0346] Exemplarily, the IoT NF network element can send a request to the UDM network element for indicating checking the access right and the tunnel establishment right of the AF entity. Correspondingly, the UDM network element can receive the request from the NEF network element for indicating checking the access right and the tunnel establishment right of the AF entity.

[0347] The UDM network element can send a check confirmation message to the IoT NF network element in a case that the access right and the tunnel establishment right corresponding to the ID of the AF entity are contained in the registration information set. Alternatively, the UDM network element can send the check confirmation message to the IoT NF network element in a case that the ID of the AF entity is contained in the registration information set. Correspondingly, the IoT NF network element can receive the check confirmation message from the UDM network element. Then the IoT NF network element can perform S604.

[0348] The UDM network element can send a check denial message to the IoT NF network element in a case that the access right and / or the tunnel establishment right corresponding to the ID of the AF entity are not contained in the registration information set. Alternatively, the UDM network element can send the check denial message to the IoT NF network element in a case that the ID of the AF entity is not contained in the registration information set. Correspondingly, the IoT NF network element can receive the check denial message from the UDM network element. Then the IoT NF network element can not perform S604.

[0349] Optionally, the IoT NF network element can pre-store the registration information set or pre-acquire the registration information set from the core network. The IoT NF network element can check whether the access right and the tunnel establishment right corresponding to the ID of the AF entity are contained in the registration information set, or check whether the ID of the AF entity is contained in the registration information set.

[0350] If the access right and the tunnel establishment right corresponding to the ID of the AF entity are contained in the registration information set, or the ID of the AF entity is contained in the registration information set, it can indicate that the AF entity has the access right and the tunnel establishment right, and the IoT NF network element can perform S604.

[0351] If the access right and / or the tunnel establishment right corresponding to the ID of the application function entity are not contained in the registration information set, or the ID of the application function entity is not contained, it can be indicated that the application function entity does not have the access right and / or the tunnel establishment right, and the IoT NF network element can not perform S604.

[0352] In this way, by checking the access right and the tunnel establishment right of the application function entity, the probability of establishing a tunnel (such as an N3 tunnel and / or an N6 tunnel) for an application function entity that does not have the access right and / or the tunnel establishment right can be reduced, and thus the impact on the security of IoT service data transmission can be reduced.

[0353] Optionally, in a case where the first indication information carried in the fifth information is information that cannot be recognized by the core network, the IoT NF network element can convert the first indication information in the fifth information into information that can be recognized by the core network, and perform S604.

[0354] In a case where the first indication information carried in the IoT service request is information that cannot be recognized by the core network, the IoT NF network element can convert the first indication information in the IoT service request into information that can be recognized by the core network, and perform S604.

[0355] It should be understood that the first indication information in the third information can be information converted from the first indication information in the fifth information, or can be information converted from the first indication information in the IoT service request.

[0356] The third information can further include information other than the first indication information included in the fifth information, or can include information other than the first indication information included in the IoT service request.

[0357] Optionally, S623 is an optional step. In a case where the IoT NF network element receives the fifth information or the IoT service request from the AF entity, the IoT NF network element can perform S604, and not perform S623.

[0358] For example, in a case where the AF entity and the IoT NF network element are located in one trusted domain or the IoT NF network element determines that the AF entity is trusted, in a case where the IoT NF network element receives the fifth information or the IoT service request from the AF entity, the IoT NF network element can perform S604, and not perform S623.

[0359] S624, in a case that the second response from the SMF network element can be received, the IoT NF network element can send a fourth response to the AF entity. The fourth response can be a response of the fifth information. The fourth response can comprise the uplink tunnel identifier of the N3 tunnel and the downlink tunnel identifier of the N3 tunnel. Correspondingly, the AF entity can receive the fourth response from the IoT NF network element.

[0360] Optionally, in a case that the third information is used to indicate that the N3 tunnel and the N6 tunnel are established, the fourth response can further comprise the N6 tunnel address of the UPF network element.

[0361] FIG. 7 shows another flow diagram of the method for IoT communication according to an embodiment of the present application.

[0362] In another embodiment of the present application, an application function entity (AF entity) can send an IoT service request to a plurality of IoT devices through a control plane. For example, the AF entity can send the IoT service request to the plurality of IoT devices through the link shown in FIG. 1. In a case that the IoT NF network element receives the IoT service request, the IoT NF network element can trigger the core network to establish the N3 tunnel, or the N3 tunnel and the N6 tunnel.

[0363] As shown in FIG. 7, the method for IoT communication according to an embodiment of the present application can comprise S701, S604-S615a.

[0364] Alternatively, the method for IoT communication can comprise S701, S604-S605, S618-S620, S613-S614, S606-S608, S621-S622, S609 and S615a.

[0365] The specific implementation of S701 and S604 can be referred to the following description. The specific implementation principle of S605-S617 can be referred to the specific implementation principle of S605-S617 in the embodiment of FIG. 6A. The specific implementation principle of each step in S618-S620 and S621-S622 can be referred to the specific implementation principle of the corresponding step in FIG. 6B, which will not be described here.

[0366] S701, the application function entity can send an IoT service request to a plurality of IoT devices through the NEF network element, the IoT NF network element, the AMF network element and the RAN reader. Correspondingly, each IoT device in the plurality of IoT devices can receive the IoT service request.

[0367] The application function entity can send the IoT service request to the plurality of IoT devices through the NEF network element, the IoT NF network element, the AMF network element and the RAN reader, that is, the application function entity can send the IoT service request to each IoT device in the plurality of IoT devices through the control plane.

[0368] The IoT service request can include the identifier of the application function entity, the first indication information, the IoT service type and the IP address of the application function entity.

[0369] In the process that the application function entity sends the IoT service request to each IoT device in the plurality of IoT devices through the control plane, the NEF network element can receive the IoT service request from the application function entity. The IoT NF network element can receive the IoT service request from the NEF network element.

[0370] In the case that the IoT NF network element receives the IoT service request from the NEF network element, the IoT NF network element can not only send the IoT service request to the AMF network element, but also perform S604.

[0371] Exemplarily, in the case that the IoT NF network element receives the IoT service request, the IoT NF network element can obtain the first indication information in the IoT service request.

[0372] In the case that the obtained first indication information is the longitude and latitude information of the IoT service area or the street location information of the IoT service area, the IoT NF network element can convert the longitude and latitude information of the IoT service area or the street location information of the IoT service area into the TA ID or the cell identifier corresponding to the IoT service area.

[0373] In the case that the obtained first indication information is any one of the TA ID corresponding to the IoT service area, the cell identifier corresponding to the IoT service area, the information of the IoT device group, the information of the intermediate node or the information of the intermediate node group, it can be indicated that the first indication information is information that can be recognized by the core network, and the IoT NF network element can not convert the first indication information.

[0374] The IoT NF network element can configure the second indication information.

[0375] In the case that the second indication information configured by the IoT NF network element is the N3 tunnel indication, the IoT NF network element can further configure the tunnel time of the N3 tunnel.

[0376] In a case where the second indication information configured by the IoT NF network element is an N3N6 tunnel indication, the IoT NF network element can further configure a tunnel time of the N3 tunnel, a tunnel time of the N6 tunnel, and an N6 tunnel address of the application function entity. In a case where the N6 tunnel address of the application function entity is an IP address of the application function entity, the IoT NF network element can obtain the IP address of the application function entity carried by the IoT service request, and does not need to configure the N6 tunnel address of the application function entity.

[0377] In this way, the IoT NF network element can execute S604 after completing the above configuration.

[0378] S604, the IoT NF network element can send third information to the SMF network element. The third information can be used to indicate the establishment of an N3 tunnel, or to indicate the establishment of an N3 tunnel and an N6 tunnel. The third information can include the first indication information. Correspondingly, the SMF network element can receive the third information from the IoT NF network element.

[0379] It should be understood that the first indication information in the third information can be information converted from the first indication information in the IoT service request, or can be the first indication information in the IoT service request that can be recognized by the core network. The third information can further include the second indication information and the tunnel time configured by the IoT NF network element, and information included in the IoT service request other than the first indication information.

[0380] For example, the third information can include the first indication information.

[0381] In a case where the third information is used to indicate the establishment of an N3 tunnel, the third information can further include the identifier of the application function entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, and the N3 tunnel indication.

[0382] In a case where the third information is used to indicate the establishment of an N3 tunnel and an N6 tunnel, the third information can further include the identifier of the application function entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, the tunnel time of the N6 tunnel, the N6 tunnel address of the application function entity (such as the IP address of the application function entity or the GTP protocol address of the application function entity), and the N3N6 tunnel indication.

[0383] As shown in the embodiment of FIG. 7, the application function entity sends the IoT service request to the multiple IoT devices through the control plane, and in the case that the IoT service request is received by the IoT NF network element, the IoT NF network element triggers the core network to establish the N3 tunnel or the N3 tunnel and the N6 tunnel by sending the third information to the SMF network element. In this way, after the establishment of the N3 tunnel, the application function entity can communicate with the multiple IoT devices through the user plane. Moreover, the N3 tunnel established by the core network is a shared tunnel that can be shared by the multiple IoT devices, and there is no need to establish a dedicated N3 tunnel for each IoT device in the multiple IoT devices, which can reduce the configuration overhead of the core network and the configuration overhead of the RAN reader.

[0384] FIG. 8 shows another flowchart of the IoT communication method provided by the embodiments of the present application.

[0385] In another embodiment of the present application, the IoT device can register the device in the core network. In the case that the multiple IoT devices complete the device registration in the core network, the IoT NF network element can obtain the registration information of the multiple IoT devices. The IoT NF network element can trigger the core network to establish a shared N3 tunnel for the multiple IoT devices, so as to facilitate the communication between the application function entity and the multiple IoT devices.

[0386] As shown in FIG. 8, the IoT communication method provided by the embodiments of the present application can include S801, S604-S606, S608, S610-S615a.

[0387] Alternatively, the IoT communication method can include S801, S604-S605, S618-S620, S613-S614, S606, S608, S621-S622 and S615a.

[0388] The specific implementation of S801 and S604 can be referred to the following description. The specific implementation principles of S605-S606, S608, S610-S615a can be referred to the specific implementation principles of the corresponding steps in the embodiment of FIG. 6A, and the specific implementation principles of each step in S618-S620 and S621-S622 can be referred to the specific implementation principles of the corresponding steps in FIG. 6B, which will not be described here.

[0389] The AF entity can trigger the IoT device to register the device in the core network through the core network, that is, to implement the IoT device registration.

[0390] S801, in the case that the multiple IoT devices complete the device registration in the core network, the core network can synchronize the registration information of the multiple IoT devices to the IoT NF network element. Correspondingly, the IoT NF network element can receive the registration information of the multiple IoT devices synchronized by the core network.

[0391] Exemplarily, the core network can periodically synchronize, in a preset period, registration information of a plurality of IoT devices registered in the period to the IoT NF network element.

[0392] Optionally, the device registration of the IoT device in the core network can be the registration of the IoT device in the IoT NF network element. In the case that the plurality of IoT devices complete the device registration, the IoT NF network element can obtain the registration information of the plurality of IoT devices.

[0393] The registration information of the IoT device can include an identifier of the IoT device.

[0394] In the case that the IoT NF network element obtains the identifier of each IoT device in the plurality of IoT devices, the IoT NF network element can configure the N3 tunnel indication and the tunnel time of the N3 tunnel, and perform S604.

[0395] The registration information of the IoT device can further include a service valid duration of the IoT device. The tunnel time of the N3 tunnel can be a longest valid duration in the service valid durations of each IoT device in the plurality of IoT devices.

[0396] Optionally, the registration information of the IoT device can further include a device category of the IoT device. The device category can be, for example, a temperature device, a humidity device, an illumination device, or an air quality device, etc.

[0397] In the case that the IoT NF network element obtains the plurality of IoT devices including a plurality of device categories, the IoT NF network element can group the plurality of IoT devices according to the device categories to obtain a plurality of IoT device groups.

[0398] S604, the IoT NF network element can send third information to the SMF network element. The third information can be used to indicate the establishment of the N3 tunnel. The third information can include first indication information. Correspondingly, the SMF network element can receive the third information from the IoT NF network element.

[0399] The first indication information in the third information can include information of one or more IoT device groups. The information of the IoT device group can be an identifier of the IoT device group. The core network can store a correspondence between the identifier of the IoT device group and the identifiers of the plurality of IoT devices included in the IoT device group, so as to facilitate the UPF network element and the RAN node to determine the IoT device group to which the IoT device belongs based on the identifier of the IoT device, and further determine the N3 tunnel based on the identifier of the IoT device group. The IoT device group can include the identifiers of the plurality of IoT devices obtained by the IoT NF network element in S801.

[0400] Optionally, the first indication information in the third information can include the identity of each IoT device in the plurality of IoT devices obtained by the IoT NF network element in S801.

[0401] In this way, the core network can establish the N3 tunnel corresponding to the first indication information based on the first indication information through S605-S606, S608, S610-S615a, or through S605, S618-S620, S613-S614, S606, S608, S621-S622 and S615a. The configuration overhead of the core network and the configuration overhead of the RAN reader can be reduced.

[0402] It can be understood that, in the case where the first indication information in the third information includes the information of each IoT device group in the plurality of IoT device groups, the core network can establish the corresponding N3 tunnel for each IoT device group in the plurality of IoT device groups through S605-S606, S608, S610-S615a, or through S605, S618-S620, S613-S614, S606, S608, S621-S622 and S615a. Since the IoT device group can include a plurality of IoT devices, the establishment of the corresponding N3 tunnel for each IoT device group is still a shared tunnel. The core network still does not need to establish a dedicated N3 tunnel for each IoT device, and the communication between the application function entity and the plurality of IoT devices can be realized, and the configuration overhead of the core network and the configuration overhead of the RAN reader can be reduced.

[0403] As shown in the embodiment of FIG. 8, in the case where the plurality of IoT devices complete the device registration in the core network, the IoT NF network element can send the third information to the SMF network element to trigger the core network to establish the N3 tunnel corresponding to the IoT device group or the plurality of IoT devices based on the information of the IoT device group or the information of the plurality of IoT devices carried in the third information, so as to realize the communication between the application function entity and the registered plurality of IoT devices through the user plane. The core network does not need to establish a dedicated N3 tunnel for each IoT device in the plurality of IoT devices, and the configuration overhead of the core network and the configuration overhead of the RAN reader can be reduced.

[0404] FIG. 9 shows another flow diagram of a communication method according to an embodiment of the present application.

[0405] In another embodiment of the present application, when the seventh information, the fourth information, the third information and the first information all indicate to establish the N3 tunnel, the core network or the UPF network element can establish the N6 tunnel before the core network or the UPF network element completes the establishment of the N3 tunnel.

[0406] As shown in FIG. 9, the communication method can include: S901-S905, S607, S906, S609, S601a-S606, S608, S610-S617.

[0407] Alternatively, the communication method can include: S901-S905, S607, S906, S609, S601a-S605, S618-S620, S613-S614, S606, S608, S621-S622, S615a, S616-S617.

[0408] Alternatively, the communication method can include: S901-S905, S607, S906, S609, S601a-S605, S618-S620, S613-S614, S606, S608, S621-S622, S615b and S617.

[0409] Alternatively, the communication method can include: S901-S905, S607, S906, S609, S601b, S623, S604-S606, S608, S610-S615a and S624.

[0410] Alternatively, the communication method can include: S901-S905, S607, S906, S609, S601b, S623, S604-S605, S618-S620, S613-S614, S606, S608, S621-S622, S615a and S624.

[0411] Wherein, the specific implementation principles of each step in S601a-S606, S608, S610-S617 can refer to the specific implementation principles of the corresponding steps in the embodiment of FIG. 6A. The specific implementation principles of each step in S618-S620, S621-S622 can refer to the specific implementation principles of the corresponding steps in FIG. 6B. The specific implementation principles of each step in S601b, S623-S624 can refer to the specific implementation principles of the corresponding steps in FIG. 6C. The step S604 after S623 can refer to S604 in FIG. 6C. Details are not described herein.

[0412] S901, the application function entity can send the eleventh information to the NEF network element. The eleventh information can include the identifier of the application function entity, the first indication information, the tunnel time of the N6 tunnel, the second indication information and the N6 tunnel address of the application function entity. Correspondingly, the NEF network element can receive the eleventh information from the application function entity.

[0413] The eleventh information can be sent by the application function entity to the NEF network element before initiating the IoT service request. The second indication information in the eleventh information can be N6 tunnel indication information. The N6 tunnel indication information can be referred to as N6 tunnel indication. The N6 tunnel indication is used to indicate the establishment of an N6 tunnel. For example, the N6 tunnel indication can be 2.

[0414] Optionally, the eleventh information can also include an IoT service type.

[0415] In a case where the IoT service type in the eleventh information is inventory, the eleventh information indicates that the established N6 tunnel can be used to implement inventory of the IoT device.

[0416] In a case where the IoT service type in the eleventh information is command, the eleventh information indicates that the established N6 tunnel can be used to implement command of the IoT device.

[0417] In a case where the IoT service type in the eleventh information is registration, the eleventh information indicates that the established N6 tunnel can be used to implement device registration indication of the IoT device.

[0418] Optionally, the eleventh information can also not include the IoT service type. In a case where the eleventh information does not include the IoT service type, the eleventh information indicates that the established N6 tunnel can be used to implement inventory, command, and registration indication of the IoT device.

[0419] S902, the NEF network element can check the access right and the tunnel establishment right of the application function entity.

[0420] The specific implementation principle of the NEF network element checking the access right and the tunnel establishment right of the application function entity can refer to the specific implementation principle of the NEF network element checking the access right and the tunnel establishment right of the application function entity in S602.

[0421] In a case where it is confirmed that the application function entity has the access right and the tunnel establishment right, the NEF network element can perform S903a or S903b.

[0422] In a case where it is confirmed that the application function entity does not have the access right and / or the tunnel establishment right, the NEF network element can not perform S903a or S903b.

[0423] In this way, by checking the access right and the tunnel establishment right of the application function entity, the probability of establishing an N6 tunnel for an application function entity that does not have the access right and / or the tunnel establishment right can be reduced, and thus the influence on the security of IoT service data transmission can be reduced.

[0424] Optionally, in the case that the first indication information carried in the eleventh information is information that the core network cannot identify, the NEF network element can convert the first indication information in the eleventh information into information that the core network can identify. The specific implementation principle of the NEF network element converting the first indication information in the eleventh information into information that the core network can identify can be referred to the specific implementation principle of the NEF network element converting the first indication information in the seventh information into information that the core network can identify in S602, which will not be described here.

[0425] S903a, the NEF network element can send the twelfth information or the thirteenth information to the IoT NF network element. Both the twelfth information and the thirteenth information can be used to indicate the establishment of the N6 tunnel. Correspondingly, the IoT NF network element can receive the twelfth information or the thirteenth information from the NEF network element.

[0426] Exemplarily, in the case that the NEF network element converts the first indication information in the eleventh information that the core network cannot identify into information that the core network can identify, the NEF network element can send the twelfth information to the IoT NF network element. Correspondingly, the IoT NF network element can receive the twelfth information from the NEF network element. The IoT NF network element can perform S904.

[0427] The first indication information contained in the twelfth information can be the first indication information that the core network can identify after conversion of the first indication information carried in the eleventh information. The twelfth information can also include information other than the first indication information contained in the eleventh information.

[0428] In the case that the NEF network element does not convert the first indication information in the eleventh information into information that the core network can identify, the NEF network element can send the thirteenth information to the IoT NF network element. Correspondingly, the IoT NF network element can receive the thirteenth information from the NEF network element.

[0429] The first indication information carried in the thirteenth information sent by the NEF network element to the IoT NF network element is the same as the first indication information in the eleventh information. The first indication information carried in the thirteenth information can be information that the core network can identify, or information that the core network cannot identify. The thirteenth information can also include information other than the first indication information contained in the eleventh information.

[0430] Exemplarily, in the case that the IoT NF network element receives the thirteenth information from the NEF network element, and the first indication information in the thirteenth information is information that the core network cannot identify, the IoT NF network element can convert the first indication information in the thirteenth information into information that the core network can identify, and perform S904.

[0431] The specific implementation principle of the IoT NF network element converting the first indication information in the thirteenth information into information identifiable by the core network can be referred to the specific implementation principle of the NEF network element converting the first indication information in the eleventh information into information identifiable by the core network, which will not be described here.

[0432] Exemplarily, in a case where the IoT NF network element receives the thirteenth information from the NEF network element, and the first indication information carried in the thirteenth information is information identifiable by the core network, the IoT NF network element can perform S904.

[0433] S903b, the NEF network element can send the twelfth information to the SMF network element. Correspondingly, the SMF network element can receive the twelfth information from the NEF network element.

[0434] In a case where the SMF network element receives the twelfth information from the NEF network element, the SMF network element can perform S905.

[0435] It can be understood that S903b is an optional step.

[0436] In a possible implementation manner, the communication method provided by the embodiment of the application can include S903b, and does not include S903a and S904.

[0437] In another possible implementation manner, the communication method provided by the embodiment of the application can include S903a and S904, and does not include S903b.

[0438] S904, the IoT NF network element can send the fourteenth information to the SMF network element. The fourteenth information can be used to indicate the establishment of an N6 tunnel. The fourteenth information can include the first indication information. Correspondingly, the SMF network element can receive the fourteenth information from the IoT NF network element.

[0439] The first indication information in the fourteenth information is information identifiable by the core network.

[0440] In a case where the IoT NF network element receives the twelfth information, the fourteenth information can include the information included in the fourth information.

[0441] In a case where the IoT NF network element receives the thirteenth information, and the thirteenth information includes the first indication information that is not identifiable by the core network, the fourteenth information can include the first indication information converted from the first indication information in the thirteenth information, and the information included in the thirteenth information except the first indication information.

[0442] In a case where the IoT NF network element receives the thirteenth information, and the thirteenth information includes the first indication information that is identifiable by the core network, the fourteenth information can include the information included in the thirteenth information.

[0443] S905、The SMF network element can send second information to the UPF network element. The second information is used to indicate to establish a second tunnel, for example, an N6 tunnel. The second information can include an identifier of the application function entity, an N6 tunnel address of the application function entity, and first indication information. Correspondingly, the UPF network element can receive the second information from the SMF network element.

[0444] It should be understood that, in the case that the SMF network element receives the fourteenth information, the first indication information in the second information can be the same as the first indication information in the fourteenth information.

[0445] Exemplarily, the SMF network element can determine the UPF network element corresponding to the first indication information in the twelfth information or the fourteenth information based on the correspondence between the first indication information and the UPF network element, and the first indication information in the twelfth information or the fourteenth information. The SMF network element can send the second information to the determined UPF network element.

[0446] Optionally, the SMF network element can determine the UPF network element corresponding to the identifier of the application function entity in the twelfth information or the fourteenth information based on the correspondence between the application function entity and the UPF network element, and the identifier of the application function entity in the twelfth information or the fourteenth information. The SMF network element can send the second information to the determined UPF network element.

[0447] Optionally, the eleventh information, the twelfth information, the thirteenth information, and the fourteenth information can all carry an identifier of the UPF network element. The identifier of the UPF network element can be determined by the application function entity based on the correspondence between the application function entity and the UPF network element, and the identifier of the application function entity. The SMF network element can send the second information to the UPF network element corresponding to the identifier of the UPF network element.

[0448] The second information can include an N6 tunnel indication. The UPF network element can use the N6 tunnel address of the application function entity obtained from the second information to establish the N6 tunnel.

[0449] S607、The UPF network element can interact with the application function entity to establish the N6 tunnel. The specific implementation principle of S607 can be referred to the specific implementation principle of S607 in the embodiment of FIG. 6, which will not be described here. In the case that the establishment of the N6 tunnel is completed, the UPF network element can perform S906.

[0450] S906、The UPF network element can send a ninth response to the SMF network element. The ninth response is a response to the second information, and the ninth response includes an N6 tunnel address on the UPF network element side. Correspondingly, the SMF network element can receive the ninth response from the UPF network element. The SMF network element can further perform S609.

[0451] S609, the UPF network element can synchronize the N6 tunnel address at the UPF network element side to the IoT NF network element, so as to facilitate the IoT NF network element to manage the IoT service.

[0452] As shown in the embodiment of FIG. 9, the core network or the UPF network element can first establish the N6 tunnel, and then establish the N3 tunnel corresponding to the first indication information, i.e., the N3 tunnel shared by the plurality of IoT devices. In the case of reducing the configuration overhead of the core network, the application function entity realizes the communication with the plurality of IoT devices through the user plane.

[0453] FIG. 10 shows another flowchart of the IoT communication method provided by the embodiment of the present application.

[0454] In another embodiment of the present application, after the plurality of IoT devices complete the device registration in the core network, the IoT NF network element obtains the registration information of the plurality of IoT devices and triggers the core network to establish the shared N3 tunnel for the plurality of IoT devices, before the application function entity initiates the IoT service request, the core network or the UPF network element can establish the N6 tunnel.

[0455] As shown in FIG. 10, the IoT communication method can include: S801, S604-S606, S608, S610-S615a, S901-S905, S607, S906, S609.

[0456] Alternatively, the IoT communication method can include: S801, S604-S605, S618-S620, S613-S614, S606, S608, S621-S622, S615a, S901-S905, S607, S906, S609.

[0457] The specific implementation principles of S801, S604-S606, S608, S610-S615a, and the specific implementation principles of S801, S604-S605, S618-S620, S613-S614, S606, S608, S621-S622, S615a can be referred to the specific implementation principles of the embodiment shown in FIG. 8. The specific implementation principles of S901-S905, S607, S906, S609 can be referred to the specific implementation principles of S901-S905, S607, S906, S609 in the embodiment shown in FIG. 9, which will not be repeated here.

[0458] As shown in the embodiment of FIG. 10, the core network or the UPF network element can establish the N3 tunnel in the case that a plurality of IoT devices complete device registration at the core network. After the N3 tunnel is established, the UPF network element or the core network can establish the N6 tunnel corresponding to the plurality of IoT devices before the application function entity initiates the IoT service request related to the plurality of IoT devices. The communication of the application function entity with the plurality of IoT devices through the user plane can be implemented in the case of reducing the configuration overhead of the core network. In addition, the N3 tunnel is established before the application function entity initiates the IoT service request, and only the N6 tunnel needs to be established in the case that the application function entity needs to initiate the IoT service, which reduces the tunnel establishment time and further reduces the IoT service time consumption of the application function entity, thereby improving the user experience.

[0459] FIGS. 6A-10 illustrate the establishment of the N3 tunnel or the N3 tunnel and the N6 tunnel by the UPF network element, taking the core network including the AMF network element and the IoT NF network element as an example.

[0460] In an embodiment of the present application, the core network can include the IoT NF network element and does not include the AMF network element. In the case that the core network includes the IoT NF network element and does not include the AMF network element, the specific implementation principle of the UPF network element establishing the N3 tunnel or the N3 tunnel and the N6 tunnel can be referred to the specific implementation principle in the case that the AMF network element in FIGS. 6A-10 is replaced by the IoT NF network element.

[0461] In another embodiment of the present application, the core network can include the AMF network element and does not include the IoT NF network element. In the case that the core network includes the AMF network element and does not include the IoT NF network element, the specific implementation principle of the UPF network element establishing the N3 tunnel or the N3 tunnel and the N6 tunnel can be referred to the specific implementation principle in the case that the IoT NF network element in FIGS. 6A-10 is replaced by the AMF network element.

[0462] Figures 6A-10 illustrate the establishment of the N3 tunnel between the UPF network element and the RAN reader by the UPF network element for the plurality of IoT devices, with reference to the communication system architecture including the RAN reader. It is understood that the UPF network element can also establish the N3 tunnel between the UPF network element and the RAN node for the plurality of IoT devices in the communication system architecture including the RAN node and the UE reader. The communication system architecture including the RAN node and the UE reader is, for example, the architecture shown in Figure 3 or Figure 4. The specific implementation principle of the UPF network element establishing the N3 tunnel between the UPF network element and the RAN node can refer to the specific implementation principle of the UPF network element establishing the N3 tunnel between the UPF network element and the RAN reader shown in any of the embodiments of Figures 6A-10, which will not be described here. For example, the specific implementation principle of establishing the N3 tunnel embodied when the RAN reader in Figures 6A-10 is replaced by the RAN node is the specific implementation principle of the UPF network element establishing the N3 tunnel between the UPF network element and the RAN node in the communication system architecture including the RAN node and the UE reader.

[0463] It is understood that the first tunnel is a shared tunnel. The number of the first tunnels between the first network element and the access network node can be one or more.

[0464] The following describes S502 in Figure 5 with reference to Figures 11-12, taking the communication system architecture including the RAN node and the UE reader as an example.

[0465] Figure 11 shows another communication system architecture according to an embodiment of the present application.

[0466] The difference between Figure 11 and Figure 4 is that a plurality of UE readers and a plurality of IoT devices 1101 are shown in Figure 11. The plurality of UE readers are, for example, the UE reader 1, the UE reader 2, and the UE reader 3 in Figure 11.

[0467] Each UE reader in the plurality of UE readers can be connected to the RAN node through the air interface. Each IoT device 1101 in the plurality of IoT devices 1101 can be linked to the corresponding UE reader through the air interface.

[0468] In the case where the UPF network element completes the establishment of the N6 tunnel and the N3 tunnel, the application function entity can transmit the first data packet to the UPF network element through the N6 tunnel between the application function entity and the UPF network element. The first data packet can include the IoT service request and the first indication information. Correspondingly, the UPF network element can receive the first data packet from the application function entity.

[0469] Exemplarily, the IoT service request can comprise an identifier of the UE reader writer. The first data packet can also comprise the identifier of the UE reader writer. The first indication information and the identifier of the UE reader writer can be carried in a packet header of the first data packet.

[0470] In a case where the N6 tunnel is a tunnel established based on an IP protocol, the packet header of the first data packet can be an IP protocol packet header.

[0471] In a case where the N6 tunnel is a tunnel established based on a GTP-U protocol, the packet header of the first data packet can be a GTP-U protocol packet header.

[0472] Taking the identifier of the UE reader writer in the first data packet or the IoT service request as an example, the identifier of the UE reader writer comprises an identifier of a UE reader writer 1, an identifier of a UE reader writer 2 and an identifier of a UE reader writer 3, the UE reader writer 1, the UE reader writer 2 and the UE reader writer 3 belong to one intermediate node group, and the N6 tunnel is a tunnel established based on a GTP-U protocol, i.e., the N6 tunnel is an N6 GTP tunnel.

[0473] The application function entity can encapsulate the IoT service request into an IoT service request data packet A0, i.e., the first data packet, according to the GTP-U protocol, and carry the identifier of the UE reader writer 1, the identifier of the UE reader writer 2 and the identifier of the UE reader writer 3 in a GTP-U protocol packet header of the IoT service request data packet A0.

[0474] The application function entity can transmit the IoT service request data packet A0 to the UPF network element through an N6 GTP tunnel between the application function entity and the UPF network element. Correspondingly, the UPF network element can receive the IoT service request data packet A0 from the application function entity.

[0475] The UPF network element can parse the IoT service request data packet A0 according to the GTP-U protocol to obtain the identifier of the UE reader writer 1, the identifier of the UE reader writer 2 and the identifier of the UE reader writer 3 carried in the GTP-U protocol packet header.

[0476] In a case where the N3 tunnel is established based on the information of the intermediate node, such as the identifier of the UE reader writer, the UPF network element can determine, based on the identifier of the UE reader writer 1, the identifier of the UE reader writer 2 and the identifier of the UE reader writer 3, an N3 tunnel 1 corresponding to the identifier of the UE reader writer 1, an N3 tunnel 2 corresponding to the identifier of the UE reader writer 2 and an N3 tunnel 3 corresponding to the identifier of the UE reader writer 3.

[0477] The UPF network element can send IoT service request data packet A1 to a RAN node (e.g., gNB) through N3 tunnel 1. The UPF network element can send IoT service request data packet A2 to the RAN node (e.g., gNB) through N3 tunnel 2. The UPF network element can send IoT service request data packet A3 to the RAN node (e.g., gNB) through N3 tunnel 3.

[0478] IoT service request data packet A1, IoT service request data packet A2, and IoT service request data packet A3 all belong to the second data packet. IoT service request data packet A1, IoT service request data packet A2, and IoT service request data packet A3 differ in that IoT service request data packet A1 carries the identifier of UE reader 1 in the GTP-U protocol header, IoT service request data packet A2 carries the identifier of UE reader 2 in the GTP-U protocol header, and IoT service request data packet A3 carries the identifier of UE reader 3 in the GTP-U protocol header.

[0479] Correspondingly, the RAN node can receive IoT service request data packet A1, IoT service request data packet A2, and IoT service request data packet A3 from the UPF network element.

[0480] It should be understood that the N3 tunnel is a tunnel established based on the GTP-U protocol. IoT service request data packet A1, IoT service request data packet A2, and IoT service request data packet A3 are all obtained by the UPF network element encapsulating according to the GTP-U protocol.

[0481] The RAN node parses IoT service request data packet A1, IoT service request data packet A2, and IoT service request data packet A3 according to the GTP-U protocol. The identifier of UE reader 1, the identifier of UE reader 2, the identifier of UE reader 3, and the IoT service request are obtained.

[0482] The RAN node can send a third data packet or initiate a first paging to UE reader 1, UE reader 2, and UE reader 3 in a multicast (PTM) manner. The third data packet and the first paging can both include the IoT service request.

[0483] In this way, the UE reader 1, the UE reader 2 and the UE reader 3 can each receive the third data packet or the first paging from the RAN node, so as to broadcast the third data packet or the first paging to the IoT devices managed by each of the UE reader 1, the UE reader 2 and the UE reader 3. That is, the UE reader 1 sends the third data packet or the first paging to the plurality of IoT devices 1101 managed by the UE reader 1. The UE reader 2 sends the third data packet or the first paging to the plurality of IoT devices 1101 managed by the UE reader 2. The UE reader 3 sends the third data packet or the first paging to the plurality of IoT devices 1101 managed by the UE reader 3.

[0484] In the case where the N3 tunnel is established based on the information of the intermediate node group, the UPF network element can determine the N3 tunnel 4 corresponding to the intermediate node group to which the identifier of the UE reader 1, the identifier of the UE reader 2 and the identifier of the UE reader 3 belong, based on the identifier of the UE reader 1, the identifier of the UE reader 2 and the identifier of the UE reader 3.

[0485] The UPF network element can send the IoT service request data packet A4 to the RAN node (such as a gNB) through the N3 tunnel 4. The IoT service request data packet A4 also belongs to the second data packet. The identifier of the UE reader 1, the identifier of the UE reader 2 and the identifier of the UE reader 3 are carried in the GTP-U protocol packet header of the IoT service request data packet A4. Correspondingly, the RAN node can receive the IoT service request data packet A4 from the UPF network element. The RAN node parses the IoT service request data packet A4 according to the GTP-U protocol. The identifier of the UE reader 1, the identifier of the UE reader 2, the identifier of the UE reader 3 and the IoT service request are obtained. It should be understood that the IoT service request data packet A4 is obtained by the UPF network element encapsulating according to the GTP-U protocol.

[0486] The RAN node can send the third data packet or initiate the first paging to the UE reader 1, the UE reader 2 and the UE reader 3 in a multicast (PTM) manner. So as to broadcast the third data packet or the first paging to the IoT devices managed by each of the UE reader 1, the UE reader 2 and the UE reader 3.

[0487] It can be understood that one UE reader can manage a plurality of IoT devices.

[0488] In this way, the UPF network element can communicate with the plurality of IoT devices managed by each of the UE reader 1, the UE reader 2 and the UE reader 3 based on the N3 tunnel, so as to realize the application function entity to communicate with the plurality of IoT devices through the user plane.

[0489] Optionally, the first indication information comprises information of at least one intermediate node corresponding to the plurality of Internet of Things devices and / or Internet of Things service area information.

[0490] The Internet of Things service area is associated with the at least one intermediate node, and in a case where the first indication information is carried in the packet header of the first data packet, the UPF network element can send the second data packet to the RAN node through an N3 tunnel corresponding to the Internet of Things service area information in the first indication information.

[0491] The packet header of the second data packet carries the first indication information. The first indication information carried in the packet header of the second data packet is used to instruct the access network node to send a third data packet or a first paging to each of the at least one intermediate node, or is used to instruct the access network node to send the third data packet or the first paging to all intermediate nodes in the Internet of Things service area; the third data packet and the first paging both contain an Internet of Things service request.

[0492] For example, the packet header of the second data packet carries information of the at least one intermediate node, or carries information of the at least one intermediate node and Internet of Things service area information. In a case where the second data packet is received, the RAN node can send the third data packet or the first paging to each of the at least one intermediate node corresponding to the information of the at least one intermediate node carried in the packet header of the second data packet.

[0493] Alternatively, the packet header of the second data packet carries Internet of Things service area information, or carries information of the at least one intermediate node and Internet of Things service area information. In a case where the second data packet is received, the RAN node can send the third data packet or the first paging to all intermediate nodes in the Internet of Things service area corresponding to the Internet of Things service area information carried in the packet header of the second data packet.

[0494] The at least one intermediate node can comprise: a UE reader / writer 1, a UE reader / writer 2, and a UE reader / writer 3. In addition to the UE reader / writer 1, the UE reader / writer 2, and the UE reader / writer 3, other UE reader / writers such as a UE reader / writer 4 can also be deployed in the Internet of Things service area. The UE reader / writer 4 is not shown in FIG. 11.

[0495] In this way, the first network element can determine a first tunnel based on the Internet of Things service area information, and send the second data packet to the access network node through the determined first tunnel. The packet header of the second data packet carries the first indication information, so as to instruct the access network node to send the third data packet or the first paging to the intermediate node corresponding to the first indication information.

[0496] FIG. 12 shows another communication system architecture provided by an embodiment of the present application.

[0497] Figure 12 differs from figure 4 in that a plurality of UE readers 1201 is shown in figure 12, and IoT devices are not shown in figure 12. The plurality of UE readers, for example, 5 UE readers 1201 in region 1 in figure 12, and 3 UE readers 1201 in region 2 in figure 12.

[0498] Each UE reader in the plurality of UE readers can be connected with the RAN node through an air interface.

[0499] It should be understood that region 1 and region 2 in figure 12 are only examples of the intermediate node-related regions, and are not a limitation on the number, distribution or form of the intermediate node-related regions. The UE readers shown in region 1 and region 2 in figure 12 are only examples of the UE readers in the regions, and are not a limitation on the number, distribution or form of the UE readers in the regions.

[0500] In the case where the UPF network element completes the establishment of the N6 tunnel and the N3 tunnel, the application function entity can transmit the first data packet to the UPF network element through the N6 tunnel between the application function entity and the UPF network element. Correspondingly, the UPF network element can receive the first data packet from the application function entity.

[0501] Exemplarily, the first indication information in the first data packet or the IoT service request includes an IoT service area identifier (IoT area ID), and the IoT service area identifier corresponds to the cell identifier 1 and the cell identifier 2. The IoT service area identifier can be a TA ID.

[0502] In the case where the N3 tunnel is established based on the IoT service area identifier, the UPF network element can determine the N3 tunnel B0 corresponding to the IoT service area identifier based on the IoT service area identifier.

[0503] The UPF network element can send the IoT service request data packet B0 to the RAN node through the N3 tunnel B0. The IoT service request data packet B0 belongs to the second data packet. Correspondingly, the RAN node can receive the IoT service request data packet B0 from the UPF network element.

[0504] The IoT service request data packet B0 is obtained by the UPF network element encapsulating according to the GTP-U protocol, and the IoT service area identifier is carried in the GTP-U protocol header of the IoT service request data packet B0.

[0505] The RAN node parses the IoT service request data packet B0 according to the GTP-U protocol. The IoT service area identifier and the IoT service request are obtained.

[0506] Exemplarily, in case the UE reader is a mobile UE reader, the RAN node can convert the identity of the IoT service area to corresponding cell identity 1 and cell identity 2.

[0507] The RAN node can broadcast the third data packet or the first paging to cell 1 corresponding to cell identity 1 and cell 2 corresponding to cell identity 2 respectively. Cell 1 is, for example, area 1 in FIG. 12. Cell 2 is, for example, area 2 in FIG. 12.

[0508] In this way, all mobile UE readers in cell 1 can receive the third data packet or the first paging broadcasted by the RAN node. All mobile UE readers in cell 2 can receive the third data packet or the first paging broadcasted by the RAN node.

[0509] Optionally, in case the UE reader is a fixed UE reader, the RAN node can determine the fixed UE readers corresponding to the identity of the IoT service area based on a pre-stored mapping relationship between the identity of the IoT service area and the fixed UE readers and the application function entity.

[0510] The RAN node can send the third data packet or the first paging to the fixed UE readers corresponding to the identity of the IoT service area by way of multicast respectively.

[0511] It should be appreciated that the number of fixed UE readers corresponding to the identity of the IoT service area can be one or more.

[0512] In this way, the fixed UE readers corresponding to the identity of the IoT service area can receive the third data packet or the first paging from the RAN node.

[0513] In case the IoT service area corresponding to the identity of the IoT service area is smaller than the coverage of the cell, the UE reader (e.g. mobile UE reader) receiving the third data packet or the first paging can determine whether it is in the IoT service area.

[0514] If the UE reader is in the IoT service area, the UE reader can respond to the IoT service request indicated by the third data packet or the first paging and broadcast or send the third data packet or the first paging to the IoT devices managed thereby.

[0515] If the UE reader is not in the IoT service area, the UE reader can not respond to the IoT service request indicated by the third data packet or the first paging and not send (e.g. broadcast) the third data packet or the first paging to the IoT devices managed thereby.

[0516] Optionally, in a case where the identified IoT service area corresponds to an IoT service area smaller than the coverage of the cell, the UE reader (such as a mobile UE reader or a fixed reader) receiving the third data packet or the first paging can send (such as broadcast) the third data packet or the first paging to the IoT device managed by the UE reader.

[0517] The IoT device receiving the third data packet or the first paging can determine whether the IoT device is in the IoT service area.

[0518] If the IoT device is in the IoT service area, the IoT device can respond to the IoT service request indicated by the third data packet or the first paging, and return the IoT service data of the IoT device to the corresponding UE reader.

[0519] If the IoT device is not in the IoT service area, the IoT device can not respond to the IoT service request indicated by the third data packet or the first paging, and not return the IoT service data of the IoT device to the corresponding UE reader.

[0520] In this way, the UPF network element can communicate with the plurality of IoT devices managed by the mobile UE reader or the fixed UE reader based on the N3 tunnel, and the application function entity can communicate with the plurality of IoT devices through the user plane.

[0521] It can be understood that the IoT device in FIGS. 1-12 can be an AIoT device. The IoT service request in the embodiments of FIGS. 1-12 can be an AIoT service request. The service data in the embodiments of FIGS. 1-12 can be AIoT service data. The IoT NF network element in FIGS. 1-12 can be an AIoT NF network element. That is, the IoT device in FIGS. 1-12 can be replaced by an AIoT device. The IoT service request in the embodiments of FIGS. 1-12 can be replaced by an AIoT service request. The service data in the embodiments of FIGS. 1-12 can be replaced by AIoT service data. The IoT NF network element in FIGS. 1-12 can be replaced by an AIoT NF network element.

[0522] In a possible implementation, the IoT service request initiated by the AF entity can carry the identification of the intermediate node. In this way, the core network can establish a special PDU (protocol data unit) session for the service communication of each intermediate node in the IoT service request based on the identification of the intermediate node. This way can realize the IoT service request corresponding service when the format of the IoT service request is an AIOT IP data packet, a MAC (media access control) data packet, or a non-architected data packet. See the embodiment shown in FIG. 13.

[0523] FIG. 13 shows another communication system architecture provided by the embodiments of the present application.

[0524] As shown in FIG. 13, the UE reader 1 identifier, the UE reader 2 identifier and the UE reader 3 identifier can be carried in the IoT service request initiated by the AF entity.

[0525] The core network can establish a PDU1 session for the UE reader 1 based on the UE reader 1 identifier, to realize the communication between the UPF network element and the UE reader 1, and further realize the communication between the UPF network element and the multiple IoT devices managed by the UE reader 1. The core network can also establish a PDU2 session for the UE reader 2 based on the UE reader 2 identifier, to realize the communication between the UPF network element and the UE reader 2, and further realize the communication between the UPF network element and the multiple IoT devices managed by the UE reader 2. The core network can also establish a PDU3 session for the UE reader 3 based on the UE reader 3 identifier, to realize the communication between the UPF network element and the UE reader 3, and further realize the communication between the UPF network element and the multiple IoT devices managed by the UE reader 32.

[0526] The IoT communication method of the embodiments of the present application is described in detail above in combination with FIG. 5 to FIG. 13. The communication apparatus of the embodiments of the present application is described in detail below in combination with FIG. 14. The communication apparatus includes modules or units for performing the corresponding steps of each part in the above-described embodiments. The modules or units can be software, hardware, or a combination of software and hardware. The communication apparatus is only briefly exemplified below, and for the details of the scheme implementation, reference can be made to the description of the above-described method embodiments, which will not be described here again.

[0527] FIG. 14 shows a structure diagram of a communication apparatus provided by the embodiments of the present application. As shown in FIG. 14, the communication apparatus can include a transceiver module 1402 and a processing module 1401.

[0528] In a possible implementation, the communication apparatus is configured to implement the steps corresponding to the first network element (such as the UPF network element) in the above-described IoT communication method.

[0529] The processing module 1401 can be configured to establish a first tunnel, the first tunnel being a shared tunnel between the first network element and an access network node.

[0530] The transceiver module 1402 can be configured to communicate with the multiple IoT devices based on the first tunnel, and / or communicate with at least one intermediate node based on the first tunnel.

[0531] The first tunnel is established based on first indication information. The first indication information includes one or more of the following: Internet of Things service area information, information of an Internet of Things device group to which a plurality of Internet of Things devices belong, information of an intermediate node corresponding to the plurality of Internet of Things devices, or information of an intermediate node group to which an intermediate node corresponding to the plurality of Internet of Things devices belongs. The intermediate node has a relay function and / or a reader / writer function.

[0532] Optionally, the Internet of Things service area information includes one or more of the following: geographic location information of the Internet of Things service area, one or more tracking area identifiers corresponding to the Internet of Things service area, one or more cell identifiers corresponding to the Internet of Things service area, or one or more base station identifiers corresponding to the Internet of Things service area.

[0533] Optionally, one or more Internet of Things devices can be deployed in the Internet of Things service area.

[0534] Optionally, the intermediate node can be deployed in the Internet of Things service area or can not be deployed in the Internet of Things service area.

[0535] Optionally, the transceiver 1402 can also be configured to receive first information, the first information being used to indicate establishment of the first tunnel, and the first information including the first indication information.

[0536] The processing module 1401 can also be configured to establish the first tunnel based on the first information.

[0537] Optionally, the transceiver 1402 can also be configured to receive second information, the second information being used to indicate establishment of a second tunnel, the second tunnel being a tunnel between the first network element and an application function entity, and the second information including an identifier of the application function entity and a second tunnel address of the application function entity.

[0538] The processing module 1401 can also be configured to establish the second tunnel based on the second information.

[0539] Optionally, the first information is also used to indicate establishment of the second tunnel, the second tunnel being a tunnel between the first network element and the application function entity, and the first information further including the identifier of the application function entity and the second tunnel address of the application function entity.

[0540] The processing module 1401 can also be configured to establish the second tunnel based on the first information.

[0541] Optionally, the first information is sent by a session management function network element in a case where third information from an Internet of Things network function network element is received or in a case where fourth information from a network exposure function network element is received. The third information and the fourth information are both used to indicate establishment of the first tunnel, or are used to indicate establishment of the first tunnel and a second tunnel, the second tunnel being a tunnel between the first network element and the application function entity, and the third information and the fourth information both including the first indication information.

[0542] The third information is sent by the Internet of Things network function network element in any of the following cases:

[0543] The Internet of Things service request is received from the network exposure function network element or the application function entity.

[0544] The fourth information is received from the network exposure function network element or the fifth information is received from the application function entity, the fifth information is used to indicate to establish the first tunnel, or is used to indicate to establish the first tunnel and the second tunnel, and the fifth information includes the first indication information.

[0545] The registration information is received from the plurality of Internet of Things devices.

[0546] Optionally, the first information further includes an Internet of Things service type and a valid time length of the first tunnel.

[0547] The processing module 1401 can also remove the first tunnel from the time when the first tunnel is established to the time when the valid time length is reached.

[0548] The Internet of Things service type includes one or more of the following: inventory, command or registration.

[0549] Optionally, the transceiver module 1402 can also be configured to send a first response to the session management function network element, the first response being a response to the first information, and the first response including an uplink tunnel identifier of the first tunnel, the uplink tunnel identifier being obtained from the first information or being configured by the first network element.

[0550] Optionally, the transceiver module 1402 can also be configured to receive a downlink tunnel identifier of the first tunnel.

[0551] Optionally, the transceiver module 1402 can also be configured to receive a first data packet, the first data packet including the Internet of Things service request and the first indication information.

[0552] The transceiver module 1402 can also be configured to send a second data packet to the access network node through the first tunnel corresponding to the first indication information, the second data packet including the Internet of Things service request and the first indication information, and the first indication information being carried in a packet header of the second data packet.

[0553] Optionally, the first indication information includes information of at least one intermediate node corresponding to the plurality of Internet of Things devices and / or Internet of Things service area information.

[0554] The transceiver module 1402 can also be configured to send, to the access network node, a second data packet through a first tunnel corresponding to the Internet of Things service area information. The first indication information carried in the header of the second data packet is used to instruct the access network node to send a third data packet or a first paging to each intermediate node in the at least one intermediate node, or is used to instruct the access network node to send the third data packet or the first paging to all intermediate nodes in the Internet of Things service area. The third data packet and the first paging both contain an Internet of Things service request.

[0555] In another possible implementation, the communication device is configured to implement the steps corresponding to the Internet of Things network function network element in the above-mentioned Internet of Things communication method.

[0556] The transceiver module 1402 can be configured to receive an Internet of Things service request, fourth information, fifth information, or registration information of a plurality of Internet of Things devices. The fourth information and the fifth information are both used to instruct the establishment of a first tunnel, or are used to instruct the establishment of the first tunnel and a second tunnel. The Internet of Things service request, the fourth information, and the fifth information all include first indication information, and the first indication information includes one or more of Internet of Things service area information, information of an Internet of Things device group to which a plurality of Internet of Things devices belong, information of an intermediate node corresponding to the plurality of Internet of Things devices, or information of an intermediate node group to which the intermediate node corresponding to the plurality of Internet of Things devices belongs. The first tunnel is a shared tunnel between the first network element and the access network node, and the second tunnel is a tunnel between the first network element and the application function entity.

[0557] The transceiver module 1402 can also be configured to send third information, the third information being used to instruct the establishment of the first tunnel, or being used to instruct the establishment of the first tunnel and the second tunnel, the third information including the first indication information, and the first tunnel being established based on the first indication information and being used for communication between the first network element and the plurality of Internet of Things devices.

[0558] Optionally, the transceiver module 1402 can also be configured to receive a second response, the second response being a response to the third information, and the second response containing an uplink tunnel identifier of the first tunnel and a downlink tunnel identifier of the first tunnel.

[0559] Optionally, the second response further includes a second tunnel address of the first network element.

[0560] Optionally, the transceiver module 1402 can also be configured to send a third response, the third response being a response to the fourth information, and the third response containing the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

[0561] Alternatively, the transceiver module 1402 can also be configured to send a fourth response, the fourth response being a response to the fifth information, and the fourth response containing the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

[0562] In yet another possible implementation, the communication apparatus is configured to implement the steps corresponding to the session management function network element in the above-mentioned Internet of Things communication method.

[0563] The transceiver module 1402 can be configured to receive third information or fourth information, the third information and the fourth information both being used to indicate establishment of the first tunnel, or being used to indicate establishment of the first tunnel and the second tunnel, and the third information and the fourth information both comprising the first indication information. The first tunnel is a shared tunnel between the first network element and the access network node, and the second tunnel is a tunnel between the first network element and the application function entity.

[0564] The transceiver module 1402 can also be configured to send first information, the first information being used to indicate establishment of the first tunnel, or being used to indicate establishment of the first tunnel and the second tunnel, the first information comprising the first indication information, or the first information comprising the first indication information, the identifier of the application function entity, and the second tunnel address of the application function entity.

[0565] Optionally, the transceiver module 1402 can also be configured to receive a first response, the first response being a response to the first information, and the first response comprising an uplink tunnel identifier of the first tunnel.

[0566] The transceiver module 1402 can also be configured to send sixth information to the access and mobility management function network element or the Internet of Things network function network element, the sixth information being used to indicate establishment of the first tunnel, and the sixth information comprising the first indication information and an uplink tunnel identifier of the first tunnel.

[0567] The transceiver module 1402 can also be configured to receive a fifth response from the access and mobility management function network element or the Internet of Things network function network element, the fifth response being a response to the sixth information, and the fifth response comprising a downlink tunnel identifier of the first tunnel.

[0568] The transceiver module 1402 can also be configured to synchronize the downlink tunnel identifier of the first tunnel with the first network element.

[0569] Optionally, the transceiver module 1402 can also be configured to send a second response to the Internet of Things network function network element, the second response being a response to the third information, and the second response comprising the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

[0570] Optionally, the second response further comprises the second tunnel address of the first network element.

[0571] Optionally, the first information further comprises the second tunnel address of the application function entity, and the first response further comprises the second tunnel address of the first network element.

[0572] The transceiver module 1402 can also be configured to synchronize the second tunnel address of the first network element with the Internet of Things network function network element.

[0573] It should be understood that the communication apparatus herein is embodied in the form of function modules. The term "module" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated or group) and memory for executing one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In an optional example, those skilled in the art can understand that the communication apparatus can be embodied in the terminal device or the network device in the above embodiments, and the communication apparatus can be used to execute the respective processes and / or steps corresponding to the terminal device or the network device in the above method embodiments. To avoid repetition, details are not described here.

[0574] The communication apparatus described above has the function of implementing the respective steps performed by the terminal device or the network device in the above method. The above function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above function. In the embodiments of the present application, the communication apparatus in FIG. 13 can also be a chip, such as a system on a chip (SoC).

[0575] It should be noted that the names of the modules involved in the embodiments of the present application can be defined as other names, as long as the functions of the modules can be implemented, and the names of the modules are not limited specifically.

[0576] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0577] The Internet of Things communication method of the embodiments of the present application has been described above, and the apparatus for executing the above method provided by the embodiments of the present application is described below. Those skilled in the art can understand that the method and the apparatus can be combined and referenced with each other, and the related apparatus provided by the embodiments of the present application can execute the steps in the above method.

[0578] The Internet of Things communication method provided by the embodiments of the present application can be applied in electronic devices with communication function. The electronic device includes a terminal device, and the specific device form of the terminal device can refer to the above related description, which is not described here.

[0579] The embodiment of the present application provides a communication system, the communication system comprises: a first network element, an Internet of Things network function network element and a session management function network element; the first network element is used for executing steps corresponding to the first network element in the above-mentioned Internet of Things communication method, the Internet of Things network function network element is used for executing steps corresponding to the Internet of Things network function network element in the above-mentioned Internet of Things communication method, and the session management function network element is used for executing steps corresponding to the session management function network element in the above-mentioned Internet of Things communication method.

[0580] The embodiment of the present application provides an electronic device, which comprises: a processor and a memory; the memory stores computer execution instructions; and the processor executes the computer execution instructions stored in the memory, so that the terminal device executes the above-mentioned method.

[0581] The embodiment of the present application provides a chip. The chip comprises a processor, and the processor is used for calling a computer program in a memory to execute the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar to those of the above-mentioned related embodiments, and will not be repeated here.

[0582] The embodiment of the present application provides a chip system. The chip system comprises at least one processor and a communication interface, the communication interface and the at least one processor are interconnected through a line, and the at least one processor is used for running a computer program or instructions to execute the above-mentioned method.

[0583] The embodiment of the present application further provides a computer readable storage medium. The computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the above-mentioned method. The method described in the above-mentioned embodiments can be realized by software, hardware, firmware or any combination thereof, in whole or in part. If realized in software, the functions can be stored as one or more instructions or codes on a computer readable medium or transmitted on a computer readable medium. The computer readable medium can include a computer storage medium and a communication medium, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

[0584] In a possible implementation, the computer readable medium can include a RAM, a ROM, a compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that is suitable for storing desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0585] The embodiment of the present application provides a computer program product, which comprises a computer program, and when the computer program is executed, the computer executes the above method.

[0586] The embodiment of the present application is described with reference to the flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiment of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0587] The above detailed description of the specific implementation is further detailed for the purpose of the object, technical solution, and beneficial effects of the present application. It should be understood that the above is only the specific implementation of the present application, and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solution of the present application should be included in the protection scope of the present application.

Claims

1. An Internet of Things communication method, characterized by, The method applied to a first network element comprises: establishing a first tunnel, the first tunnel being a shared tunnel between the first network element and an access network node; communicating with a plurality of Internet of Things devices based on the first tunnel, and / or communicating with at least one intermediate node based on the first tunnel; wherein the first tunnel is established based on first indication information, the first indication information comprising one or more of the following: Internet of Things service area information, information of an Internet of Things device group to which the plurality of Internet of Things devices belong, information of an intermediate node corresponding to the plurality of Internet of Things devices, or information of an intermediate node group to which the intermediate node corresponding to the plurality of Internet of Things devices belongs.

2. The method of claim 1, wherein, The Internet of Things service area information comprises one or more of the following: geographical position information of the Internet of Things service area, one or more tracking area identifiers corresponding to the Internet of Things service area, one or more cell identifiers corresponding to the Internet of Things service area, or one or more base station identifiers corresponding to the Internet of Things service area.

3. The method according to claim 1 or 2, characterized in that, One or more Internet of Things devices are deployed within the Internet of Things service area.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving first information, the first information being used to indicate establishment of the first tunnel, the first information comprising the first indication information; the establishing of the first tunnel comprises establishing the first tunnel based on the first information.

5. The method of claim 4, wherein, The method further comprises: receiving second information, the second information being used to indicate establishment of a second tunnel, the second tunnel being a tunnel between the first network element and an application function entity, the second information comprising an identifier of the application function entity and a second tunnel address of the application function entity; establishing the second tunnel based on the second information.

6. The method of claim 4, wherein, The first information is also used to indicate establishment of the second tunnel, the second tunnel being a tunnel between the first network element and an application function entity, the first information further comprising an identifier of the application function entity and a second tunnel address of the application function entity; The method further comprises establishing the second tunnel based on the first information.

7. The method according to any one of claims 4-6, characterized in that, The first information is sent by a session management function network element in a case where third information from an Internet of Things network function network element is received or in a case where fourth information from a network exposure function network element is received; the third information and the fourth information are both used to indicate establishment of the first tunnel, or are used to indicate establishment of the first tunnel and a second tunnel, the second tunnel being a tunnel between the first network element and an application function entity, the third information and the fourth information both comprising the first indication information; The third information is sent by an Internet of Things network function network element in any of the following cases: receiving an Internet of Things service request from a network exposure function network element or an application function entity; receiving the fourth information from the network exposure function network element or fifth information from the application function entity, the fifth information being used to indicate establishment of the first tunnel, or being used to indicate establishment of the first tunnel and the second tunnel, the fifth information comprising the first indication information; receiving registration information from the plurality of Internet of Things devices.

8. The method according to any one of claims 4-7, characterized in that, The first information further comprises an Internet of Things service type and a valid time length of the first tunnel; The method further comprises: tearing down the first tunnel from a time when the first tunnel establishment is completed to a time when the effective time length is reached. The Internet of Things service type comprises one or more of the following: inventory, command, or registration.

9. The method according to any one of claims 4-8, characterized in that, The establishing the first tunnel based on the first information comprises: sending a first response to a session management function network element, the first response being a response to the first information, the first response comprising an uplink tunnel identifier of the first tunnel, the uplink tunnel identifier being obtained from the first information or configured by the first network element.

10. The method of claim 9, wherein, The establishing the first tunnel based on the first information further comprises: receiving a downlink tunnel identifier of the first tunnel.

11. The method according to any one of claims 1-10, characterized in that, The method further comprises: receiving a first data packet, the first data packet comprising an Internet of Things service request and the first indication information; The communicating with the multiple Internet of Things devices based on the first tunnel and / or the communicating with at least one intermediate node based on the first tunnel comprises: sending a second data packet to the access network node through the first tunnel corresponding to the first indication information, the second data packet comprising the Internet of Things service request and the first indication information, the first indication information being carried in a packet header of the second data packet.

12. The method of claim 11, wherein, The first indication information comprises information of at least one intermediate node corresponding to the multiple Internet of Things devices and / or the Internet of Things service area information; The sending the second data packet to the access network node through the first tunnel corresponding to the first indication information comprises: sending the second data packet to the access network node through the first tunnel corresponding to the Internet of Things service area information; The first indication information carried in the packet header of the second data packet is used to instruct the access network node to send a third data packet or a first paging to each intermediate node of the at least one intermediate node, or is used to instruct the access network node to send the third data packet or the first paging to all intermediate nodes in the Internet of Things service area; the third data packet and the first paging both comprise the Internet of Things service request.

13. An Internet of Things communication method, comprising: The application is applied to an Internet of Things network function network element, and comprises: receiving an Internet of Things service request, fourth information, fifth information, or registration information of multiple Internet of Things devices; the fourth information and the fifth information are both used to instruct to establish a first tunnel, or are both used to instruct to establish the first tunnel and a second tunnel; the Internet of Things service request, the fourth information, and the fifth information all comprise first indication information, the first indication information comprising one or more of the following: Internet of Things service area information, information of an Internet of Things device group to which the multiple Internet of Things devices belong, information of an intermediate node corresponding to the multiple Internet of Things devices, or information of an intermediate node group to which intermediate nodes corresponding to the multiple Internet of Things devices belong; the first tunnel is a shared tunnel between a first network element and an access network node, and the second tunnel is a tunnel between the first network element and an application function entity; sending third information, the third information being used for indicating to establish the first tunnel, or, being used for indicating to establish the first tunnel and the second tunnel, the third information comprising the first indication information, the first tunnel being established based on the first indication information and being used for the first network element to communicate with the plurality of Internet of Things devices.

14. The method of claim 13, wherein, The method further comprises: receiving a second response, the second response being a response to the third information, the second response containing an uplink tunnel identifier of the first tunnel and a downlink tunnel identifier of the first tunnel.

15. The method of claim 14, wherein, The second response further comprises a second tunnel address of the first network element.

16. The method according to any one of claims 13-15, characterized by, The method further comprises: sending a third response, the third response being a response to the fourth information, the third response containing the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel; or, sending a fourth response, the fourth response being a response to the fifth information, the fourth response containing the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

17. An Internet of Things communication method comprising: Applied to a session management function network element, the method comprises: receiving third information or fourth information, the third information and the fourth information both being used for indicating to establish the first tunnel, or, being used for indicating to establish the first tunnel and the second tunnel, the third information and the fourth information both comprising first indication information; the first tunnel being a shared tunnel between a first network element and an access network node, the second tunnel being a tunnel between the first network element and an application function entity; sending first information, the first information being used for indicating to establish the first tunnel, or, being used for indicating to establish the first tunnel and the second tunnel, the first information comprising the first indication information, or, the first information comprising the first indication information, an identifier of the application function entity and a second tunnel address of the application function entity.

18. The method of claim 17, wherein, The method further comprises: receiving a first response, the first response being a response to the first information, the first response comprising an uplink tunnel identifier of the first tunnel; sending sixth information to an access and mobility management function network element or an Internet of Things network function network element, the sixth information being used for indicating to establish the first tunnel, the sixth information comprising the first indication information and the uplink tunnel identifier of the first tunnel; receiving a fifth response from the access and mobility management function network element or the Internet of Things network function network element, the fifth response being a response to the sixth information, the fifth response comprising a downlink tunnel identifier of the first tunnel; synchronizing the downlink tunnel identifier of the first tunnel to the first network element.

19. The method of claim 18, wherein, The method further comprises: sending a second response to the Internet of Things network function network element, the second response being a response to the third information, the second response containing the uplink tunnel identifier of the first tunnel and the downlink tunnel identifier of the first tunnel.

20. The method of claim 19, wherein, The second response further comprises a second tunnel address of the first network element.

21. The method of any one of claims 18-20, wherein, The first information further comprises a second tunnel address of the application function entity, and the first response further comprises a second tunnel address of the first network element; The method further comprises: synchronizing the second tunnel address of the first network element to the Internet of Things network function network element.

22. A communication system, characterized by Comprise: a first network element, an Internet of Things network function network element, and a session management function network element; the first network element is configured to perform the method of any one of claims 1 to 12, the Internet of Things network function network element is configured to perform the method of any one of claims 13 to 16, and the session management function network element is configured to perform the method of any one of claims 17 to 21.

23. A communications device, characterized by comprising: comprising a module for performing the method of any one of claims 1 to 12, the method of any one of claims 13 to 16, or the method of any one of claims 17 to 21.

24. A communications device, characterized by the communication apparatus comprises one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is configured to store computer program codes, the computer program codes comprising computer instructions, and the one or more processors are configured to invoke the computer instructions to cause the communication apparatus to perform the method of any one of claims 1 to 12, the method of any one of claims 13 to 16, or the method of any one of claims 17 to 21.

25. A chip system, characterized by the chip system is applied to a communication apparatus, and the chip system comprises one or more processors configured to invoke computer instructions to cause the communication apparatus to perform the method of any one of claims 1 to 12, the method of any one of claims 13 to 16, or the method of any one of claims 17 to 21.

26. A computer-readable storage medium, characterized in that, the computer readable storage medium comprises computer instructions, and when the computer instructions run on a communication apparatus, the computer instructions cause the communication apparatus to perform the method of any one of claims 1 to 12, the method of any one of claims 13 to 16, or the method of any one of claims 17 to 21.

27. A computer program product, characterised in that, the computer program product comprises computer program codes, and when the computer program codes run on a communication apparatus, the computer program codes cause the communication apparatus to perform the method of any one of claims 1 to 12, the method of any one of claims 13 to 16, or the method of any one of claims 17 to 21.

Images