Internet of Things communication method, communication system, communication device, chip system, storage medium and computer program product

Abstract

The embodiment of the invention provides an Internet of Things communication method, a communication system, a communication device, a chip system, a storage medium and a computer program product, and relates to the technical field of Internet of Things. 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 based on the first tunnel. Wherein the first tunnel can be understood as a shared tunnel shared by a plurality of Internet of Things devices. The first tunnel is established based on first indication information used for indicating the plurality of Internet of Things devices. By taking the first tunnel comprising the N3 tunnel as an example, the core network does not need to establish a special N3 tunnel for each Internet of Things device in the plurality of Internet of Things devices, and communication with the plurality of Internet of Things devices can be realized, so that the configuration overhead of the core network can be reduced, and the configuration overhead of the access network node can also be reduced.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to an IoT communication method, communication system, communication device, chip system, storage medium, and computer program product. Background Technology

[0002] Some mobile communication systems may include Internet of Things (IoT) devices, access network nodes, a core network, and application function (AF) entities. AF entities can communicate with IoT devices through the core network and access network nodes.

[0003] In scenarios where application functional entities communicate with IoT devices through core network and access network nodes, there is a problem of high core network configuration overhead. Summary of the Invention

[0004] This application provides an IoT communication method, communication system, communication device, chip system, storage medium, and computer program product, which are applied in the field of IoT technology and can reduce the configuration overhead of the core network.

[0005] In a first aspect, embodiments of this application propose an Internet of Things (IoT) communication method applied to a first network element. The method includes: establishing a first tunnel, wherein the first tunnel is a shared tunnel between the first network element and an access network node; communicating with multiple 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, which includes one or more of the following: IoT service area information, information about the IoT device group to which the multiple IoT devices belong, information about the intermediate nodes corresponding to the multiple IoT devices, or information about the intermediate node group to which the intermediate nodes corresponding to the multiple IoT devices belong.

[0006] In this way, the first indication information can correspond to multiple IoT devices, or the first indication information can be used to indicate multiple IoT devices. The first tunnel is established based on the first indication information, which can mean that the first tunnel is a shared tunnel shared by multiple IoT devices corresponding to the first indication information. The first network element can communicate with multiple IoT devices based on the first tunnel, and / or communicate with at least one intermediate node based on the first tunnel. Taking the first tunnel including an N3 tunnel as an example, the first network element does not need to establish a dedicated N3 tunnel for multiple IoT devices to realize communication between the first network element and multiple IoT devices and / or at least one intermediate node. This can reduce the configuration overhead of the first network element, and thus reduce the configuration overhead of the core network to which the first network element belongs. The intermediate node can have relay function and / or reader / writer function. For the specific implementation principle of the embodiments of this application, please refer to the specific implementation principle of the embodiments shown in S501-S502.

[0007] In one possible implementation, one or more IoT devices can be deployed within the IoT business area.

[0008] In one possible implementation, the IoT service area information includes one or more of the following: the geographic location information of the IoT service area, 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.

[0009] Thus, when the first network element establishes the first tunnel based on the IoT service area information, the first tunnel can correspond to one or more of the following: the 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 corresponding to the IoT service area, or one or more base station identifiers corresponding to the IoT service area.

[0010] In one possible implementation, the method further includes: receiving first information, the first information being used to instruct the establishment of a first tunnel, the first information including first instruction information. Establishing the first tunnel includes: establishing the first tunnel based on the first information.

[0011] In this way, by sending the first information to the first network element, the first network element is triggered to establish the first tunnel corresponding to the first indication information in the first information.

[0012] In one possible implementation, the method further includes: receiving second information, the second information being used to instruct the establishment of a second tunnel, the second tunnel being a tunnel between the first network element and the application function entity, the second information including the identifier of the application function entity and the second tunnel address of the application function entity; and establishing the second tunnel based on the second information.

[0013] In this way, sending second information to the first network element triggers the establishment of a second tunnel by the first network element. The second information can be received by the first network element before the establishment of the first tunnel, such as... Figure 9 The illustrated embodiment. The second information may be received by the first network element after establishing the first tunnel, such as... Figure 10 The illustrated embodiment.

[0014] In one possible implementation, the first information is further used to instruct the establishment of a second tunnel, which is a tunnel between the first network element and the application function entity. The first information also includes the identifier of the application function entity and the address of the second tunnel of the application function entity. The method further includes: establishing the second tunnel based on the first information.

[0015] In this way, by sending first information to the first network element, the establishment of the first tunnel and the second tunnel by the first network element is triggered. For a detailed explanation of the implementation principle, please refer to [link to relevant documentation]. Figure 6A The illustrated embodiment Figure 6B The illustrated embodiment Figure 6C The illustrated embodiment or Figure 7 The specific implementation principle of the illustrated embodiment.

[0016] In one possible implementation, the first information is sent by the session management function network element upon receiving third information from the IoT network function network element or fourth information from the network exposure function network element. Both the third and fourth information are used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, where the second tunnel is a tunnel between the first network element and the application function entity. Both the third and fourth information include the first indication information. The third information is sent by the IoT network function network element under any of the following circumstances: receiving an IoT service request from the network exposure function network element or the application function entity; receiving fourth information from the network exposure function network element or fifth information from the application function entity, where the fifth information is used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, and the fifth information includes the first indication information; or receiving registration information from multiple IoT devices.

[0017] In this way, IoT network function elements can trigger the establishment of the first tunnel, or the establishment of the first tunnel and the second tunnel, by sending third information to the session management function element. Similarly, network exposure function elements can trigger the establishment of the first tunnel, or the establishment of the first tunnel and the second tunnel, by sending fourth information to the session management function element. Furthermore, network exposure function elements or application function entities can trigger the IoT network function element to send third information by sending IoT service requests. Application function entities can also trigger the IoT network function element to send third information by sending fifth information. Receiving registration information from multiple IoT devices indicates that multiple IoT devices have completed device registration; this completion can also trigger the IoT network function element to send third information, thereby triggering the establishment of the first tunnel, or the establishment of the first tunnel and the second tunnel.

[0018] In one possible implementation, the first information also includes the IoT service type and the effective duration of the first tunnel. The method further includes dismantling the first tunnel from the moment it is established until the effective duration is reached. The IoT service type includes one or more of the following: inventory, command, or registration.

[0019] This allows the first network element to dismantle the first tunnel based on its effective duration, thereby releasing resources and improving resource utilization. When the first information includes an IoT service type, the first tunnel established based on that first information can be a tunnel used to implement the service corresponding to that IoT service type. For example, the first tunnel can be used to transmit information corresponding to the IoT service type. This information may include service data returned by an IoT service request or an IoT service request indication.

[0020] In one possible implementation, establishing a first tunnel based on the first information includes: sending a first response to a session management function network element, the first response being a response to the first information, 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.

[0021] 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 can transmit the uplink tunnel identifier of the first tunnel to the access network node, thereby realizing the establishment of the first tunnel.

[0022] In one possible implementation, establishing a first tunnel based on the first information further includes receiving the downlink tunnel identifier of the first tunnel.

[0023] In this way, the first network element can obtain the downlink tunnel identifier of the first tunnel, enabling it to subsequently transmit IoT service requests to the access network node through the first tunnel. Specifically, the first network element can receive the downlink tunnel identifier of the first tunnel after sending the first response; see [link to details]. Figure 6A The illustrated embodiment. The first network element can receive the downlink tunnel identifier of the first tunnel before sending the first response; see details below. Figure 6B The illustrated embodiment.

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

[0025] Thus, the first data packet includes first indication information, enabling the first network element to 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 second data packet header carries the first indication information, allowing the access network node to send IoT service requests to the corresponding intermediate node or IoT device based on the first indication information. See details... Figure 11 The illustrated embodiment or Figure 12 The illustrated embodiment.

[0026] In one possible implementation, the first indication information includes information about at least one intermediate node corresponding to multiple IoT devices and / or IoT service area information. Sending a second data packet to the access network node through a first tunnel corresponding to the first indication information includes: sending the second data packet to the access network node through the first tunnel corresponding to the IoT service area information. The first indication information carried in the header of the second data packet instructs the access network node to send a third data packet or a first paging to each of the at least one intermediate node, or instructs the access network node to send a third data packet or a first paging to all intermediate nodes within the IoT service area. Both the third data packet and the first paging contain an IoT service request.

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

[0028] Secondly, this application proposes an Internet of Things (IoT) communication method applied to IoT network functional elements. The method includes: receiving IoT service requests, fourth information, fifth information, or registration information of multiple IoT devices. The fourth and fifth information are both used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel. The IoT service request, fourth information, and fifth information all include first indication information, which includes one or more of the following: IoT service area information, information about the IoT device group to which the multiple IoT devices belong, information about the intermediate nodes corresponding to the multiple IoT devices, or information about the intermediate node group to which the intermediate nodes corresponding to the multiple IoT devices belong. 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 functional entity. Third information is sent, which is used to indicate the establishment of the first tunnel, or to indicate the establishment of the first tunnel and a second tunnel. The third information includes the first indication information, and the first tunnel is established based on the first indication information and used for communication between the first network element and multiple IoT devices.

[0029] In this way, by sending IoT service requests, fourth information, fifth information, or registration information of multiple IoT devices to the IoT network function element, the IoT network function element can be triggered to send third information. This, in turn, triggers the establishment of the first tunnel, or the establishment of the first tunnel and the second tunnel.

[0030] In one possible implementation, the method further includes: receiving a second response, the second response being a response to third information, the second response containing an uplink tunnel identifier and a downlink tunnel identifier of the first tunnel.

[0031] In this way, the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel can be used to indicate that the first tunnel has been successfully established, so as to facilitate the management of the first tunnel by the IoT network function elements, or to instruct the application function entity to communicate with the IoT device through the user plane.

[0032] In one possible implementation, the second response also includes the second tunnel address of the first network element. This facilitates the management of the second tunnel by the IoT network functional elements.

[0033] In one possible implementation, the method further includes: sending a third response, which is a response to the fourth information, the third response containing the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel. Alternatively, sending a fourth response, which is a response to the fifth information, the fourth response containing the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

[0034] Thus, the first tunnel for the network element implementing the fourth notification message was successfully established. The first tunnel for the network element implementing the fifth notification message was also successfully established.

[0035] Thirdly, embodiments of this application propose an Internet of Things (IoT) communication method applied to a session management function network element. The method includes: receiving third information or fourth information, where both the third and fourth information are used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, and both the third and fourth information include first indication information. 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. Sending first information, where the first information is used to indicate the establishment of the first tunnel, or to indicate the establishment of both the first and second tunnels, and the first information includes the first indication information, or the first information includes the first indication information, the identifier of the application function entity, and the second tunnel address of the application function entity.

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

[0037] In one possible implementation, the method further includes: receiving a first response, which is a response to first information, including an uplink tunnel identifier for the first tunnel; sending sixth information to an access and mobility management function (AM) network element or an Internet of Things (IoT) network element, the sixth information indicating the establishment of the first tunnel, including first indication information and the uplink tunnel identifier for the first tunnel; receiving a fifth response from the AM or IoT network element, the fifth response being a response to the sixth information, including a downlink tunnel identifier for the first tunnel; and synchronizing the downlink tunnel identifier for the first tunnel to the first network element. Thus, the establishment of the first tunnel is achieved.

[0038] In one possible implementation, the method further includes: sending a second response to the IoT network function element, the second response being a response to third information, the second response containing the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel. This serves to notify the IoT network function element that the first tunnel has been successfully established, facilitating the IoT network function element's management of the first tunnel.

[0039] In one possible implementation, the second response also includes the second tunnel address of the first network element, to facilitate the management of the second tunnel by the IoT network functional elements.

[0040] In one possible implementation, the first information further includes the second tunnel address of the application functional entity, and the first response further includes the second tunnel address of the first network element. The method also includes: synchronizing the second tunnel address of the first network element to the IoT network functional network element.

[0041] Thus, the first information also includes the second tunnel address of the application function entity, and the first response also includes the second tunnel address of the first network element, enabling the establishment of the second tunnel. The second tunnel address of the first network element is synchronized with the IoT network function network element to facilitate the management of the second tunnel by the IoT network function network element.

[0042] Fourthly, embodiments of this application propose a communication system, including: a first network element, an Internet of Things (IoT) network function network element, and a session management function network element. The first network element is used to execute the method as described in the first aspect or any possible implementation of the first aspect; the IoT network function network element is used to execute the method as described in the second aspect or any possible implementation of the second aspect; and the session management function network element is used to execute the method as described in the third aspect or any possible implementation of the third aspect.

[0043] Fifthly, embodiments of this application propose a communication device, comprising: a module for performing a method as 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.

[0044] Sixthly, embodiments of this application provide a communication device, which includes one or more processors and a memory.

[0045] The memory is coupled to one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, and one or more processors calling the computer instructions to cause the communication device to perform a method such as 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.

[0046] Seventhly, embodiments of this application propose a chip system applied to a communication device. The chip system includes one or more processors and a communication interface. The communication interface and at least one processor are interconnected via a circuit. The one or more processors are used to invoke computer instructions to cause the communication device to execute a method as 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 communication interface in the chip can be an input / output interface, pins, or circuits, etc.

[0047] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0048] Eighthly, embodiments of this application provide a computer-readable storage medium including computer instructions that, when executed on a communication device, cause the communication device to perform a method as 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.

[0049] Ninthly, embodiments of this application provide a computer program product, which includes computer program code. When the computer program code is run on a communication device, it causes the communication device to perform a method such as 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] Tenthly, embodiments of this application provide an Internet of Things (IoT) communication device, which may be an electronic device or a chip or chip system within an electronic device. The IoT communication device may include a display unit and a processing unit. When the IoT communication device is an electronic device, the display unit may be a display screen. The display unit is used to perform display steps to enable the electronic device to implement the IoT 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 IoT communication device is an electronic device, the processing unit may be a processor. The IoT communication device may further include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the electronic device to implement an IoT 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 IoT communication device is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to enable the electronic device to implement an Internet of Things (IoT) 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 may be a storage unit within the chip (e.g., a register, cache, etc.) or a storage unit located outside the chip within the electronic device (e.g., a read-only memory, random access memory, etc.). Attached Figure Description

[0051] Figure 1 A schematic diagram of a communication system architecture provided in an embodiment of this application;

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

[0053] Figure 3 This is a schematic diagram of another communication system architecture provided in the embodiments of this application;

[0054] Figure 4 This is a schematic diagram of another communication system architecture provided in the embodiments of this application;

[0055] Figure 5 A flowchart illustrating an IoT communication method provided in an embodiment of this application;

[0056] Figure 6A Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0057] Figure 6B Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0058] Figure 6C Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0059] Figure 7 Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0060] Figure 8 Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0061] Figure 9 Another flowchart illustrating the communication method provided in an embodiment of this application;

[0062] Figure 10 Another flowchart illustrating the IoT communication method provided in this application embodiment;

[0063] Figure 11 This is a schematic diagram of another communication system architecture provided in the embodiments of this application;

[0064] Figure 12 This is a schematic diagram of another communication system architecture provided in the embodiments of this application;

[0065] Figure 13 This is a schematic diagram of another communication system architecture provided in the embodiments of this application;

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

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

[0068] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with essentially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order of execution. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0069] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0070] In this application embodiment, "at least one" refers to one or more, and "more than one" can be understood as "at least two"; "multiple" can be understood as "at least two items". "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0071] This application can be applied to mobile communication systems. A mobile communication system can be called a mobile communication network. A mobile communication system can be simply referred to as a communication system. Mobile communication systems include, but are not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or new radio (NR) systems, 5.5G systems or future mobile communication systems, vehicle-to-X (V2X) systems (where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), Long Term Evolution-Machine (LTE-M) technology for machine-to-machine (M2M) communication, and machine-to-machine (M2M) communication. Machine (M2M), etc.

[0072] The technical solutions in this application are applicable to communication systems that provide Internet of Things (IoT) services. IoT services include, for example, ambient internet of things (AIoT) services.

[0073] Exemplarily, in some embodiments, the communication system providing IoT services may include IoT devices. IoT devices include, for example, ambient IoT devices (AIoT devices) or ambient IoT (AIoT) terminals. An AIoT terminal can be understood as a terminal capable of providing AIoT services. An ambient IoT device is an IoT device powered by energy harvesting and has limited energy storage capacity. For example, some or all of the characteristics of an ambient IoT device can be referred to the description in 3GPP standard TR 38.769. It should be understood that the description of some or all of the characteristics of an ambient IoT device referred to here in 3GPP standard TR 38.769 is only a possible example description, and the embodiments of this application are not limited thereto. Furthermore, as communication standard protocol versions evolve or are updated, some or all of the characteristics of an ambient IoT device can be referred to the evolved or updated versions; or some or all of the characteristics of an ambient IoT device can also be referred to the descriptions in related technologies.

[0074] The technical solutions of this application embodiment are also applicable to Internet of Things (IoT) communication scenarios and communication scenarios relying on backscatter technology. The aforementioned IoT can be passive IoT, semi-passive IoT, or ambient IoT, etc.

[0075] It should be understood that IoT devices may also have other names or definitions, and this application embodiment does not specifically limit them. IoT services may also have other names or definitions, and ambient IoT services (or AIoT services) may also have other names or definitions, and this application embodiment does not specifically limit them.

[0076] For example, IoT services can also be referred to as IoT businesses. IoT businesses may also include one or more of the following: inventory, command, or registration.

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

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

[0079] The communication system in this application embodiment may include at least one Internet of Things (IoT) device, a radio access network (RAN), a core network (CN), and an application function (AF) entity. The RAN may be referred to as a radio access network.

[0080] Application Function (AF) entities can be entities that provide internal operator applications, such as entities providing LTE voice over LTE application functions (Volte AF). Volte AF entities are similar to 4G LTE voice over LTE application servers (Volte AS). AF entities can also be third-party AFs (such as video servers or game servers). When an AF entity is an internal operator AF and is within a trusted domain with other network functions (NFs), the AF entity can directly interact and access other NFs. When an AF entity is a third-party AF and is not within a trusted domain, the AF entity can access other NFs through NEFs. Other NFs include Internet of Things (IoT) network function elements (IoT NFs) or Ambient Internet of Things (AIoT) network function elements (AIoT NFs).

[0081] The AF entity in this application embodiment can be used to perform Internet of Things (IoT) services or Ambient Internet of Things (AIoT) services.

[0082] Application functional entities can also be used to achieve collaboration between the application layer and the network layer. The application layer can include user equipment (UE), application servers, content delivery networks (CDNs), or cloud service platforms. User equipment (UE) can include IoT devices. The network layer can include radio access networks, core networks, transport networks, and multi-access edge computing (MEC) nodes.

[0083] In this application embodiment, the access network (RAN) can be a RAN node. A RAN node can also be referred to as a RAN entity, access node, access network device, or radio access network device, etc. A RAN node can be a base station, a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (e.g., home evolved NodeB, or homeNode B, HNB), a base band unit (BBU), a radio network controller (RNC) in a cloud radio access network (CRAN) scenario, or a next-generation node B (gNB).

[0084] RAN nodes can also have reader / writer functionality. A RAN node with reader / writer functionality can be called a RAN reader.

[0085] A reader / writer can be used to read and write data to IoT devices or tags. This data can be, for example, IoT data. IoT data can also be environmental data, which may include environmental parameters such as temperature, humidity, light intensity, or air quality. Environmental data falls under the category of AIoT business data. IoT devices can be, for example, AIoT devices. Tags can be tags that collect or receive data. Examples of tags include passive tags, semi-passive tags, active tags, or active tags. In this application embodiment, both IoT devices and AIoT devices can be replaced with tags.

[0086] Application functional entities can communicate with IoT devices through the core network and RAN nodes. It should be understood that communication between application functional entities and IoT devices includes data interaction between the application functional entities and IoT devices.

[0087] For example, application function entities can inventory multiple IoT devices through the core network and RAN nodes, or perform write, read, deactivate, or activate multiple IoT devices.

[0088] To facilitate understanding of the communication system architecture of the embodiments of this application, the following is combined with... Figures 1-4 The communication system architecture provided in the embodiments of this application will be described.

[0089] Figure 1 A schematic diagram of a communication system architecture provided in an embodiment of this application is shown.

[0090] like Figure 1 As shown, the communication system architecture includes application function entities, a core network, RAN nodes, and IoT devices. The core network includes network exposure function (NEF) network elements, IoT network function (IoT NF) network elements, and access and mobility management function (AMF) network elements.

[0091] The IoT NF network element can possess all or part of the functions of the AMF network element, and can also be responsible for handling the logic of IoT services. Specifically, this may include: executing IoT service requests in the network (e.g., inventory, command, or registration), and processing the corresponding non-access stratum (NAS) messages of the IoT service; supporting inventory, command, registration, and message routing for IoT devices; authorizing IoT service requests; performing security authentication for IoT data transmission; verifying the identification of IoT devices and performing operations to protect IoT devices when necessary; collecting IoT data and summarizing reports; collecting billing information; managing IoT devices and IoT services; and so on. Furthermore, the AIoT NF network element can be deployed co-located with the AMF network element or separately; this application embodiment does not impose any limitations. The identification of the IoT device is, for example, an identity identifier (ID).

[0092] IoT NF network elements can also be AIoT network function (AIoT NF) network elements. AIoT NF network elements can possess all or some of the functions of AMF network elements, and can also perform security authentication for environmental IoT data transmission, as well as manage AIoT devices and AIoT services. Application function entities can communicate with IoT devices through NEF network elements, IoTNF network elements, AMF network elements, and RAN nodes.

[0093] In this way, the application functional entity can communicate with IoT devices through the control plane. Figure 1 The communication system architecture shown illustrates a topology link that enables communication between application functional entities and IoT devices.

[0094] It should be understood that the network elements in the embodiments of this application, such as Internet of Things Network Function (IoT NF) network elements, Ambient Internet of Things Network Function (AIoT NF) network elements, or Network Exposure Function (NEF) network elements, may also have other names or definitions, and the embodiments of this application do not specifically limit them. Similarly, the entities in the embodiments of this application, such as AF entities, may also have other names or definitions, and the embodiments of this application do not specifically limit them.

[0095] Figure 2 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0096] like Figure 2 As shown, this communication system architecture includes application function entities, a core network, RAN readers, and IoT devices. The core network includes user plane function (UPF) network elements.

[0097] Application functional entities can communicate with IoT devices through UPF network elements and RAN readers. The RAN reader and IoT devices can be connected via an air interface.

[0098] In this way, the application functional entity can communicate with IoT devices through the user plane. Figure 2 The communication system architecture shown illustrates another topology link that enables communication between application functional entities and IoT devices.

[0099] Figure 3 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0100] Figure 3 and Figure 1 The difference is that, in Figure 3 The communication system architecture shown also includes UE readers deployed between RAN nodes and IoT devices. The UE reader can act as a relay and also has reader / writer functionality. The UE reader can be referred to as an intermediate node. Figure 3 In the communication system architecture shown, the core network may not include AMF network elements or IoT NF network elements.

[0101] Application functional entities can communicate with IoT devices through the core network, RAN nodes, and UE readers. RAN nodes and UE readers can connect via air interface. UE readers and IoT devices can also connect via air interface.

[0102] In this way, the application functional entity can communicate with IoT devices through the control plane. Figure 3The communication system architecture shown illustrates another topology link that enables communication between application functional entities and IoT devices.

[0103] Figure 4 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0104] Figure 4 and Figure 2 The difference is that, in Figure 4 The data includes RAN nodes and UE readers, but excludes RAN readers.

[0105] Application functional entities can communicate with IoT devices through UPF network elements, RAN nodes, and UE readers. RAN nodes and UE readers can connect via air interface. UE readers and IoT devices can also connect via air interface.

[0106] In this way, the application functional entity can communicate with IoT devices through the user plane. Figure 4 The communication system architecture shown illustrates another topology link that enables communication between application functional entities and IoT devices.

[0107] In this embodiment, the AMF network element can be abbreviated as AMF. The UPF network element can be abbreviated as UPF. The IoT NF network element can be abbreviated as IoT NF. The AIoT NF network element can be abbreviated as AIoT NF. The Application Function (AF) entity can be abbreviated as AF.

[0108] In this embodiment, the IoT NF network element can be replaced with the AIoT NF network element. The IoT device can be replaced with the AIoT device.

[0109] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0110] 1. N3 Tunnel

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

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

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

[0114] In some possible implementations, a tunnel can be called a bearer, a connection, or a path, etc.

[0115] 2. N6 Tunnel

[0116] An N6 tunnel can be a tunnel established through the N6 interface.

[0117] In this embodiment, 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. An N6 PTP tunnel can be understood as a point-to-point (PTP) tunnel established through the N6 interface.

[0118] N6 tunnels can be based on the GTP-U protocol or on the Internet Protocol (IP).

[0119] 3. Tunnel endpoint identifier (TEID)

[0120] TEID can be used to identify the endpoints of GPRS Tunneling Protocol (GTP) tunnels, enabling the differentiation of different tunnels and sessions. GPRS Tunneling Protocol tunnels include, for example, tunnels based on the GTP-U protocol. GTP-U-based tunnels can be N3 tunnels or N6 tunnels.

[0121] The tunnel endpoint of an N3 tunnel can also be identified using 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 in this application embodiment can be understood as a node with relay and reader / writer functions. The intermediate node can be an electronic device.

[0124] The electronic devices in this application embodiment may include handheld devices with communication functions, vehicle-mounted devices, etc. For example, some electronic devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0125] By way of example and not limitation, in this embodiment, the electronic device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0126] Furthermore, in this embodiment of the application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0127] The electronic devices in the embodiments of this application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0128] Understandable Figures 1-4 The number of IoT devices can be one or more. When there are multiple IoT devices... Figures 2-4 There can be one or more readers / writers. Examples of readers / writers include RAN readers / writers and UE readers / writers. One reader / writer can communicate with multiple IoT devices.

[0129] For example, taking IoT services as inventory and IoT service requests as inventory instructions, in one possible implementation, using... Figure 2 or Figure 4 The example shown illustrates an application function entity performing inventory checks on m IoT devices via the user plane. The core network can establish a dedicated N3 tunnel for each of the m IoT devices; that is, the core network will establish m N3 tunnels. Through each IoT device's dedicated N3 tunnel, each IoT device can receive inventory checks commands initiated by the application function entity. Through each IoT device's dedicated N3 tunnel, the application function entity can receive information from each IoT device. This information may include the IoT device's identifier and / or its status information. The status information may include information indicating normal operation or information indicating abnormal operation. Here, m is an integer greater than 1.

[0130] Thus, in this possible implementation, in order to enable application functional entities to store data on multiple IoT devices, the core network will establish multiple N3 tunnels, resulting in a large configuration overhead for the core network.

[0131] In view of this, this application proposes an Internet of Things (IoT) communication method. A first network element of the core network establishes a shared tunnel, or first tunnel, between itself and access network nodes, and communicates with multiple IoT devices based on this first tunnel. The first tunnel can be understood as a shared tunnel used by multiple IoT devices. The first tunnel is established based on first indication information used to instruct the multiple IoT devices. For example, the first tunnel may include an N3 tunnel. In this way, the core network does not need to establish a dedicated N3 tunnel for each of the multiple IoT devices to achieve communication with them, thereby reducing the configuration overhead of the core network.

[0132] The following is combined with Figures 5-14 The IoT communication method provided in the embodiments of this application will be described.

[0133] Figure 5 A flowchart illustrating an IoT communication method provided in an embodiment of this application is shown.

[0134] like Figure 5 As shown, the communication method may 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, meaning it can be shared by multiple IoT devices. The first tunnel is established based on the first indication information.

[0137] The first indication information may include one or more of the following: IoT business area information, information on IoT device groups to which multiple IoT devices belong, information on intermediate nodes corresponding to multiple IoT devices, or information on intermediate node groups to which intermediate nodes corresponding to multiple IoT devices belong.

[0138] An IoT business area can be understood as the area corresponding to an IoT business. IoT business area information can be referred to as IoT business area information. An IoT business area may include one or more IoT devices. For example, one or more IoT devices may be deployed within an IoT business area. Optionally, intermediate nodes may or may not be deployed within an IoT business area. In some possible implementations of this application, the IoT business area may be referred to as an IoT service area, an IoT target area, an inventory area, or a command area.

[0139] When the IoT business is environmental IoT business, the IoT service area can be the AIoT service area. The IoT target area can be the AIoT target area. The IoT target area can be simply referred to as the target area. The environmental IoT target area can also be simply referred to as the target area.

[0140] The IoT service area information may include one or more of the following: the 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 geographic location information can be latitude and longitude information, or street location information (civic location). The tracking area identifier can be called the tracking area ID (TA ID). The tracking area identifier can be the tracking area identity (TAI) or the tracking area code (TAC). The cell identifier can be the physical cell identifier (PCI).

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

[0143] An Internet of Things (IoT) device group can include multiple IoT devices. Information about an IoT device group may include: the identifier of the IoT device group, and / or, the identifiers of each IoT device among the multiple IoT devices included in the IoT device group.

[0144] Intermediate nodes function as both relays and readers. An intermediate node can manage multiple IoT devices. Information about an intermediate node includes its identifier. An example of an intermediate node is a UE (User Equipment) reader.

[0145] An intermediate node group may include one or more intermediate nodes. Information about an intermediate node group may include: an identifier for the intermediate node group, and / or, the identifiers of each intermediate node among the multiple intermediate nodes included in the intermediate node group.

[0146] For example, the first network element can establish a first tunnel based on the first indication information, such that the first tunnel corresponds to multiple IoT devices indicated by the first indication information. The first network element can maintain the correspondence between the first tunnel and the multiple IoT devices.

[0147] The correspondence between the first tunnel and multiple IoT devices can be represented by a mapping table that maps the first tunnel to multiple IoT devices. This mapping table can include the identification (ID) of each IoT device among the multiple IoT devices.

[0148] The mapping between the first tunnel and multiple IoT devices can include: the IoT device context corresponding to the first tunnel. The IoT device context can contain the identifiers of each IoT device among the multiple IoT devices.

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

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

[0151] For example, the first network element can be a User Plane Function (UPF) network element. When the first network element is a UPF network element, the first tunnel can be an N3 tunnel.

[0152] S502, the first network element can communicate with multiple 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] For example, with Figure 2 The illustrated communication system architecture, with the first network element being a UPF network element, the access network node being a RAN reader / writer, and the first tunnel being an N3 tunnel between the UPF network element and the RAN reader / writer, demonstrates that the UPF network element can send IoT service requests from application function entities to the RAN reader / writer through the N3 tunnel. Correspondingly, the RAN reader / writer can receive IoT service requests from the first network element. The RAN reader / writer can then send IoT service requests to multiple IoT devices via the air interface. For example, the RAN reader / writer can use multicast or broadcast methods to send IoT service requests to multiple IoT devices, thus enabling the first network element to communicate with multiple IoT devices based on the first tunnel.

[0154] by Figure 4The illustrated communication system architecture, with the first network element being a UPF network element, the access network node being a RAN node, and the first tunnel being an N3 tunnel between the UPF network element and the RAN node, and multiple intermediate nodes (such as UE readers) as an example, allows the UPF network element to send IoT service requests from application function entities to the RAN node through the N3 tunnel between the UPF network element and the RAN node. Correspondingly, the RAN node can receive IoT service requests from the first network element. The RAN node can send IoT service requests to each of the at least one intermediate node via the air interface. For example, the RAN node can use multicast or broadcast to send IoT service requests to at least one intermediate node. Correspondingly, each of the at least one intermediate node can receive IoT service requests from the RAN node. Each of the at least one intermediate node can use broadcast or multicast to send IoT service requests to the multiple IoT devices it manages. This enables the first network element to communicate with at least one intermediate node based on the first tunnel, and further enables the first network element to communicate with multiple IoT devices based on the first tunnel.

[0155] Multiple IoT devices, for example Figure 5 The IoT devices shown are 1, 2, 3, and 4. At least one intermediate node is included, for example... Figure 5 The intermediate node 1 and intermediate node 2 are shown. It should be understood that... Figure 5 The IoT devices 1, 2, 3 and 4 shown are merely examples and are not intended to limit the specific form or number of IoT devices in the embodiments of this application. Figure 5 The intermediate node 1 and intermediate node 2 shown are merely examples and are not intended to limit the specific form or number of intermediate nodes in the embodiments of this application.

[0156] like Figure 5The illustrated embodiment of the IoT communication method provided in this application establishes a shared tunnel, i.e., a first tunnel, between a first network element and an access network node. This eliminates the need for the core network to establish dedicated N3 tunnels for each IoT device within the multiple first tunnel IoT devices. This enables the first network element to communicate with multiple IoT devices, and / or with at least one intermediate node, thereby facilitating communication between the application function entity and multiple IoT devices. This reduces the configuration overhead of the core network in establishing tunnels and also reduces the configuration overhead of the RAN reader (or RAN node). The first network element communicates with multiple IoT devices based on the first tunnel. Compared to some possible implementations where the first network element transmits IoT service requests sent by the application function entity to the RAN reader (or RAN node) through multiple dedicated N3 tunnels, the IoT communication method provided in this application eliminates the need for the first network element to transmit multiple IoT service requests to the RAN node (or RAN reader), saving resources used for data transmission.

[0157] For example, when the RAN reader sends IoT service requests to multiple IoT devices via the air interface, each of the multiple IoT devices can receive the IoT service request through the RAN reader. Each of the multiple IoT devices can respond to the IoT service request by sending response information to the RAN reader via the air interface. The response information may include data returned by the IoT service request. For example, if the IoT service request is an inventory instruction, the data returned by the IoT service request may include the IoT device's identifier and / or the IoT device's status information.

[0158] Correspondingly, the RAN reader can receive response information from each of the multiple IoT devices. The RAN reader can then send the response information from each of the multiple IoT devices to the first network element via the first tunnel. This allows the first network element to transmit the response information from each of the multiple IoT devices to the application function entity.

[0159] Among them, IoT service requests can be inventory instructions, commands, or registration instructions.

[0160] Commands include, for example, write, read, deactivate, or activate. Write can be understood as a command instructing the writing of data to the IoT device. Read can be understood as a command instructing the reading of data from the IoT device. Deactivate can be understood as a command instructing the deactivation of the IoT device. Activate can be understood as a command instructing the activation of the IoT device.

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

[0162] In this way, the first network element can communicate with multiple 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, thereby enabling the application function entity to communicate with multiple IoT devices.

[0163] S501 will be described below with reference to some embodiments.

[0164] For example, taking the first network element as a User Plane Function (UPF) network element and the first tunnel as an N3 tunnel, the Session Management Function (SMF) network element can send first information to the UPF network element. The first information can be used to instruct the establishment of an N3 tunnel, and may include first instruction information. Correspondingly, the UPF network element can receive the first information from the SMF network element.

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

[0166] In this way, the UPF network element can establish a shared N3 tunnel between the UPF network element and the RAN node, and thus enable the UPF network element to communicate with multiple IoT devices based on an N3 tunnel.

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

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

[0169] The following example continues, using the first network element as the User Plane Functional Network (UPF) element and the first tunnel as the N3 tunnel. Figures 6A-13 ,right Figure 5 The explanation will focus on S501-S502.

[0170] Combination Figures 6A-10 ,right Figure 5 The explanation will focus on S501.

[0171] Figure 6A This paper illustrates another flowchart of the IoT communication method provided in an embodiment of this application.

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

[0173] S601a. ​​The application function entity can send seventh information to the NEF network element. The seventh information may include the application function entity's identifier (ID), 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 piece of 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 piece of information can be either 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 both N3 and N6 tunnels. The N3 tunnel indication information can be simply referred to as the N3 tunnel indication. The N3N6 tunnel indication information can be simply referred to as the N3N6 tunnel indication.

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

[0176] When the second indication information in the seventh information is an N3 tunnel indication, the seventh information can be used to indicate the establishment of an N3 tunnel, and the seventh information may include the N6 tunnel address of the application function entity.

[0177] When the second indication information in the seventh information is an N3N6 tunnel indication, the seventh information can be used to indicate the establishment of N3 tunnel and N6 tunnel. The seventh information may also include the N6 tunnel address of the application functional entity.

[0178] The N6 tunnel address of the application functional entity is the N6 tunnel address on the application functional entity side. The N6 tunnel address of the application functional entity can be the GTP protocol address of the application functional entity, such as the GTP-U protocol address. The N6 tunnel address of the application functional entity can also be the IP address of the application functional entity. The IP address can be an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address.

[0179] If the indication information in the seventh information is an N3 tunnel indication, the seventh information may not include the N6 tunnel address of the application function entity.

[0180] Optionally, the seventh piece of information may also include the IoT service type and tunnel time. The IoT service type can be inventory, command, or registration. The tunnel time may include the start and end times of the session. The tunnel time may include the effective duration of the tunnel. It should be understood that, in the case of an AIoT service, the IoT service type can be an AIoT service type.

[0181] For example, when the seventh information includes an IoT service type, the seventh information indicates that the established first tunnel can realize the service corresponding to the IoT service type. For instance, the seventh information indicates that the established first tunnel can be used to transmit information corresponding to the IoT service type. The information corresponding to the IoT service type may include IoT service requests or service data returned by IoT service requests. The first tunnel may be, for example, the N3 tunnel, or a combination of the N3 tunnel and the N6 tunnel.

[0182] For example, if the IoT service type in the seventh information is inventory, the seventh information indicates that the established first tunnel can be used to transmit inventory instructions or data returned by the IoT device in response to the inventory instructions (such as the IoT device's identifier and / or IoT device's status information).

[0183] In the case where the IoT service type in the seventh message is a command, the seventh message indicates that the established first tunnel can be used to transmit commands or data returned by IoT devices in response to commands.

[0184] If the IoT service type in the seventh information is registration, the seventh information indicates that the established first tunnel can be used to transmit registration instructions or registration information returned by IoT devices in response to registration instructions.

[0185] When the seventh piece of information is used to indicate the establishment of an N3 tunnel, the tunnel time in the seventh piece of information may include the tunnel time of the N3 tunnel. The tunnel time of the N3 tunnel may be, for example, the start and end times of the session corresponding to the N3 tunnel, or the effective duration of the N3 tunnel.

[0186] When the seventh information is used to indicate the establishment of N3 and N6 tunnels, the tunnel time in the seventh information may include the tunnel time of N3 tunnel and the tunnel time of N6 tunnel. The tunnel time of N6 tunnel may be, for example, the start and end times of the session corresponding to N6 tunnel, or the effective duration of N6 tunnel.

[0187] The seventh piece of information includes tunnel time, so that subsequent UPF network elements can dismantle the tunnel when the tunnel establishment is completed and the effective tunnel duration is reached, or at the end time indicated by the tunnel time, in order to release resources and improve resource utilization.

[0188] Optionally, the seventh information may not include the IoT service type. If 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] For example, the seventh piece of information may be an IoT shared session establishment request signaling (Nnef_iot_common_session_creation_request). It should be understood that, in the case of an AIoT service, the seventh piece of information may be an AIoT shared session establishment request signaling (Nnef_aiot_common_session_creation_request).

[0190] S602 and NEF network elements can check the access permissions and tunnel establishment permissions of application function entities.

[0191] For example, a NEF network element can send a request to a unified data management (UDM) network element to instruct on checking the access permissions and tunnel establishment permissions of an application function entity. The request carries the ID of the application function entity. Correspondingly, the UDM network element can receive the request from the NEF network element to instruct on checking the access permissions and tunnel establishment permissions of the application function entity.

[0192] In this embodiment of the application, the UDM network element can be simply referred to as UDM.

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

[0194] The UDM network element can send a check confirmation message to the NEF network element if the registration information set contains the access permissions and tunnel establishment permissions corresponding to the application function entity's ID. Alternatively, the UDM network element can send a check confirmation message to the NEF network element if the registration information set contains the application function entity's ID. The check confirmation message can carry the application function entity's ID. Correspondingly, the NEF network element can receive the check confirmation message from the UDM network element, indicating that the application function entity has access permissions and tunnel establishment permissions. Then, the NEF network element can execute S603a or S603b.

[0195] The UDM network element can send a check denial message to the NEF network element if the registration information set does not contain the access permissions and / or tunnel establishment permissions corresponding to the application function entity's ID. Alternatively, the UDM network element can send a check denial message to the NEF network element if the registration information set does not contain the application function entity's ID. The check denial message may carry the application function entity's ID. Correspondingly, the NEF network element can receive the check denial message from the UDM network element, indicating that the application function entity does not have access permissions and / or tunnel establishment permissions. In this case, the NEF network element may not execute S603a or S603b.

[0196] Optionally, the NEF network element may pre-store a set of registration information or pre-obtain a set of registration information from the core network. The NEF network element may check whether the registration information set contains the access permissions and tunnel establishment permissions 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 permissions and tunnel establishment permissions corresponding to the ID of the application function entity, or contains the ID of the application function entity, it means that the application function entity has access permissions and tunnel establishment permissions, and the NEF network element can execute S603a or S603b.

[0198] If the registration information set does not contain the access permissions and / or tunnel establishment permissions corresponding to the ID of the application function entity, or does not contain the ID of the application function entity, it means that the application function entity does not have access permissions and / or tunnel establishment permissions, and the NEF network element may not execute S603a or S603b.

[0199] Optionally, the NEF network element can also send a request to the IoT NF network element to instruct it to check the access permissions and tunnel establishment permissions of the application function entity. Correspondingly, the IoT NF network element can receive the request from the NEF network element to instruct it to check the access permissions and tunnel establishment permissions of the application function entity. The IoT NF network element can check the access permissions and tunnel establishment permissions of the application function entity based on a pre-stored or pre-obtained set of registration information from the core network. For the specific implementation principle, please refer to the specific implementation principle of the UDM network element or NEF network element checking the access permissions and tunnel establishment permissions of the application function entity based on the registration information set, which will not be repeated here.

[0200] After verifying that the application function entity has access permissions and tunnel establishment permissions, the IoT NF network element can send a verification message to the NEF network element. Correspondingly, the NEF network element can receive the verification message from the IoT NF network element and execute S603a or S603b.

[0201] If the check confirms that the application function entity does not have access rights and / or tunnel establishment rights, 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 may choose not to execute S603a or S603b.

[0202] In this way, by checking the access permissions and tunnel establishment permissions of application functional entities, the probability of establishing tunnels (such as N3 tunnels and / or N6 tunnels) for application functional entities that do not have access permissions and / or tunnel establishment permissions can be reduced, thereby reducing the impact on the security of IoT business data transmission.

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

[0204] For example, the first indication information that the core network cannot recognize may be: the latitude and longitude information of the IoT business area and / or the street location information of the IoT business area.

[0205] If the first indication information carried in the seventh information is the latitude and longitude information of the IoT service area and / or the street location information of the IoT service area, the NEF network element can convert the latitude and longitude 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 or the cell ID corresponding to the IoT service area.

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

[0207] For example, when the NEF network element converts the first indication information in the seventh information into information that the core network can recognize, 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 execute S604.

[0208] The first indication information included in the fourth information can be the first indication information that the core network can recognize after converting the first indication information carried in the seventh information. The fourth information may also include information other than the first indication information contained in the seventh information.

[0209] For example, if the seventh information includes 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 included in the seventh information other than the first indication 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] If the NEF network element fails to convert the first indication information in the seventh information into information that the core network can recognize, 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] In this context, the first indication information carried in the eighth message sent by the NEF network element to the IoT NF network element is the same as the first indication information in the seventh message. The first indication information carried in the eighth message can be information that the core network can recognize, or information that the core network cannot recognize. The eighth message may also include information other than the first indication information contained in the seventh message.

[0212] Regarding the first indication information, the information that the core network can identify includes, for example: information about the IoT device group to which multiple IoT devices belong, information about the intermediate nodes corresponding to multiple IoT devices, information about the intermediate node group to which the intermediate nodes corresponding to multiple IoT devices belong, 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] For example, when 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 that the core network cannot recognize, the IoT NF network element can convert the first indication information in the eighth information into information that the core network can recognize, and execute S604.

[0214] The specific implementation principle of the IoT NF network element converting the first indication information in the eighth information into information that the core network can recognize can be found in 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 cell identifier corresponding to the IoT service area, which will not be repeated here.

[0215] For example, when 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 that the core network can recognize, the IoT NF network element can execute S604.

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

[0217] When the SMF network element receives the fourth information from the NEF network element, the SMF network element can execute S605.

[0218] Understandably, S603b is an optional step.

[0219] In one possible implementation, the communication method provided in this application embodiment may include S603b, but excludes S603a and S604.

[0220] In another possible implementation, the communication method provided in this application embodiment may include S603a and S604, but not S603b.

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

[0222] Among them, the first indication information in the third information is information that the core network can recognize.

[0223] When an IoT NF network element receives the fourth information, the third information may include the information contained in the fourth information.

[0224] When an IoT NF network element receives the eighth information, and the eighth information contains first indication information that the core network cannot recognize, the third information may include the first indication information converted from the first indication information in the eighth information, as well as information contained in the eighth information other than the first indication information.

[0225] When an IoT NF network element receives the eighth information, and the eighth information contains first indication information that the core network can recognize, the third information may include the information contained in the eighth information.

[0226] For example, when the third information is used to indicate the establishment of an N3 tunnel, the third information may include the identifier of the application functional entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, and the N3 tunnel indication.

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

[0228] S605 and SMF network elements can send first information to UPF network elements. The first information is used to instruct the establishment of an N3 tunnel, or to instruct the establishment of both an N3 tunnel and an N6 tunnel. The first information may include first instruction information. Correspondingly, UPF network elements can receive the first information from SMF network elements.

[0229] It should be understood that when an SMF network element receives the third information, the first indication information in the first information and the first indication information in the third information can be the same.

[0230] When the SMF network element receives the fourth information, the first indication information in the first information and the first indication information in the fourth information can be the same.

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

[0232] The mapping between the first indication information and the UPF network element can be pre-configured in the core network by the operator based on the service level agreement (SLA). The SMF network element can obtain the mapping 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 identifier of the application function entity in the third or fourth 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 third or fourth information. The SMF network element can then send the first information to the determined UPF network element.

[0234] The mapping between application function entities and UPF network elements can be pre-configured by the operator in the core network based on the Service Level Agreement (SLA). SMF network elements can obtain the mapping between application function entities and UPF network elements from the core network.

[0235] Optionally, the seventh, eighth, fourth, and third information messages may all carry the identifier of the UPF network element. The identifier of the UPF network element can be an application function entity, 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 from the core network or the operator to the application function entity.

[0237] For example, the first information may include second instruction information.

[0238] If the first information includes an N3 tunnel indication, the first information can be used to indicate the establishment of the N3 tunnel.

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

[0240] Optionally, if the first information does not include the N6 tunnel address of the application functional entity, the first information may be used to indicate the establishment of the N3 tunnel.

[0241] If the first information includes the N6 tunnel address of the application functional entity, the first information is used to indicate the establishment of the N3 tunnel and the N6 tunnel.

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

[0243] In cases where the first information is used to indicate the establishment of tunnels N3 and N6, the first information may also include the tunneling time of tunnel N6.

[0244] Optionally, the first information may also include the identifier of the AF entity. This allows the N3 tunnel to correspond to or be bound to the AF entity.

[0245] The S606 and UPF network elements can obtain or assign the uplink tunnel identifier of the N3 tunnel.

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

[0247] For example, the first information may 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, if the first information does not carry the uplink tunnel identifier of the N3 tunnel, the UPF network element can configure or assign the uplink tunnel identifier of the N3 tunnel.

[0249] Optionally, if the first information is used to indicate the establishment of N3 tunnel and 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 execute S607 to establish N6 tunnel.

[0250] Optionally, if the first information is used to instruct the establishment of an N3 tunnel, the UPF network element can execute S607.

[0251] S607 and UPF network elements can interact with application function entities to establish N6 tunnels.

[0252] For example, a UPF network element can be configured with its N6 tunnel address. The N6 tunnel address of the UPF network element is the same as the N6 tunnel address on the UPF network element side. The UPF network element can send its N6 tunnel address to the application function entity based on the application function entity's N6 tunnel address, thereby establishing an N6 PTP tunnel between the UPF network element and the application function entity.

[0253] Optionally, when the first information is used to indicate the establishment of N3 and N6 tunnels, the first information may also carry the N6 tunnel address of the UPF network element configured by the SMF network element. The UPF network element may also obtain the N6 tunnel address of the UPF network element carried in the first information to establish an N6 PTP tunnel between the UPF network element and the application function entity.

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

[0255] Once the N6 tunnel is established, the UPF network element can execute S608.

[0256] The S608 and UPF network elements can send a first response to the SMF network element. The first response is a response to the first information, including 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, if the first information is used to indicate the establishment of N3 and N6 tunnels, the first response may also include the N6 tunnel address on the UPF network element side. Optionally, the first response may also include information indicating that the N6 tunnel has been successfully established.

[0258] Upon receiving the first response from the UPF network element, the SMF network element can execute S610.

[0259] If the first response includes the N6 tunnel address on the UPF network element side, the SMF network element can also execute S609.

[0260] S609 and UPF network elements can synchronize the N6 tunnel address on the UPF network element side with the IoT NF network element to facilitate the IoT NF network element's management of IoT services.

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

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

[0263] Optionally, the sixth information may also include the identifier of the application function entity and the identifier (ID) of the UPF network element, so that the AFM network element can determine the RAN reader based on the identifier of the UPF network element.

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

[0265] S611 and AFM network elements can identify the RAN reader / writer based on the first indication information or the identifier of the UPF network element, and send the sixth information to the RAN reader / writer.

[0266] For example, the AFM network element can determine the RAN reader corresponding to the first indication information in the sixth information based on the 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 UPF network element identifier in the sixth information based on the pre-stored correspondence between the UPF network element identifier and the RAN reader.

[0268] S612. The RAN reader / writer 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 includes the downlink tunnel identifier of the N3 tunnel. Correspondingly, the SMF network element can receive the fifth response sent by the RAN reader / writer through the AFM network element.

[0269] For example, upon receiving the sixth message, the RAN reader can configure the downlink tunnel identifier for the N3 tunnel. The downlink tunnel identifier for the N3 tunnel can be, for example, the downlink tunnel identifier on the RAN reader side or the downlink tunnel identifier on the RAN node side. Still using TEID as an example, the downlink tunnel identifier can be a downlink tunnel endpoint identifier (DL TEID). The downlink tunnel identifier on the RAN reader side can be called RANreader DL TEID, and the downlink tunnel identifier on the RAN node side can be called RAN node DL TEID.

[0270] Thus, for the RAN reader, the N3 tunnel between the RAN reader and the UPF network element is established. It should be understood that this 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 on the correspondence between the N3 tunnel established in this embodiment and the first indication information in the sixth information. This facilitates the RAN reader in determining the shared N3 tunnel corresponding to the IoT device when receiving IoT service data from the IoT device.

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

[0272] An AFM network element can send a fifth response to an SMF network element. Correspondingly, an SMF network element can receive a fifth response from an AFM network element.

[0273] S613, the SMF network element can synchronize the downlink tunnel identifier of the N3 tunnel with 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 execute S614.

[0275] Thus, for the UPF network element, the N3 tunnel between the RAN reader and the UPF network element is established. It should be understood that this 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. This correspondence includes information about the correspondence between the N3 tunnel established in this embodiment and the first indication information in the first information. This allows the UPF network element to determine the shared N3 tunnel corresponding to the first indication information in the IoT service request when it receives such a request.

[0276] S614. The UPF network element can send a synchronization confirmation message to the SMF network element, indicating that the UPF network element has received 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 is successfully established, which indicates that the UPF network element has completed the N3 tunnel establishment.

[0278] UPF network elements can maintain the correspondence between N3 tunnels and the first indication information, as well as the uplink tunnel identifier of N3 tunnels and the identifier of application function entities. When the first indication information in the seventh information is IoT service area information, the correspondence between N3 tunnels and the first indication information is, for example, the correspondence between N3 tunnels and IoT service area information (such as the TA ID or cell identifier corresponding to the IoT service area).

[0279] S615a, 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, containing the uplink tunnel identifier and the downlink tunnel identifier of the N3 tunnel. Correspondingly, the IoT NF network element can receive the second response from the SMF network element. Thus, the IoT NF network element can execute S616.

[0280] In the second response, the uplink tunnel identifier and the downlink tunnel identifier of the N3 tunnel can be used to indicate that the N3 tunnel has been successfully established.

[0281] For example, if the third information is used to indicate the establishment of N3 and N6 tunnels, the second response may also include 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.

[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 of an AIoT service, the second response can be an AIoT shared session establishment response signaling (Nnef_aiot_common_session_creation_response).

[0283] S615b: 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 the uplink tunnel identifier and the 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 can execute S617.

[0284] For example, in the case where the fourth information is used to indicate the establishment of N3 tunnel and N6 tunnel, the third response may also include the N6 tunnel address of the UPF network element.

[0285] Understandably, S615b is an optional step.

[0286] If the communication method provided in the embodiments of this application includes S603b, the communication method provided in the embodiments of this application may include S615b, and may not include S615a and S616.

[0287] When the communication method provided in the embodiments of this application includes S603a and S604, the communication method provided in the embodiments of this application may include S615a and S616, but may not include S615b.

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

[0289] For example, in the case where the eighth information is used to instruct the establishment of N3 tunnel and N6 tunnel, the sixth response may also 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 containing seventh information. The seventh response can include the uplink tunnel identifier and the downlink tunnel identifier of the N3 tunnel. Correspondingly, the application function entity can receive a second response from the NEF network element.

[0291] For example, in the case where the seventh information is used to instruct the establishment of N3 tunnel and N6 tunnel, the seventh response may also include the N6 tunnel address of the UPF network element.

[0292] Optionally, the second, third, sixth, and seventh responses may also include information indicating that the N3 tunnel has been successfully established.

[0293] As shown in Figure 6, before an application function entity initiates an IoT service, it can send a seventh message to the NEF network element to trigger the core network or a first network element (such as a UPF network element) to establish an N3 tunnel or both N3 and N6 tunnels. The seventh, eighth, fourth, third, first, and sixth messages, including the first indication information, all correspond to the N3 tunnel; that is, in this embodiment, the N3 tunnel is established based on the first indication information. This allows the UPF network element to communicate with multiple IoT devices through the N3 tunnel, facilitating communication between the application function entity and multiple IoT devices via the user plane. The N3 tunnel is a shared tunnel used by multiple IoT devices. This eliminates the need for the core network to establish a dedicated N3 tunnel for each IoT device, thus reducing core network configuration overhead. It is understood that establishing the N3 tunnel also requires configuration of the access network node (such as a RAN reader / writer). Therefore, compared to the configuration of the access network node when establishing a dedicated N3 tunnel for each IoT device, the IoT communication method provided in this embodiment further reduces the configuration overhead of the access network node.

[0294] It is understood that when the seventh information indicates the establishment of the N3 tunnel, the eighth, fourth, third and first information all indicate the establishment of the N3 tunnel. The communication method provided in this application embodiment can complete the establishment of the N3 tunnel through the process shown in S601a-S606, S608 and S610-S617.

[0295] When the seventh information indicates the establishment of tunnels N3 and N6, the eighth, fourth, third, and first information all indicate the establishment of tunnels N3 and N6. The communication method provided in this application embodiment can complete the establishment of tunnels N3 and N6 through the process shown in S601a-S617.

[0296] Once the core network or UPF network element has established N3 and N6 tunnels, application function entities can transmit IoT service requests 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 IoT service requests from the application function entity. The UPF network element can send IoT service requests to the RAN reader / writer through the N3 tunnel corresponding to the first indication information in the IoT service request, so that the RAN reader / writer can send IoT service requests to multiple IoT devices associated with the RAN reader / writer via the air interface.

[0297] Correspondingly, each of the multiple IoT devices can receive IoT service requests from the RAN reader / writer.

[0298] Each of the multiple IoT devices can respond to IoT service requests and send IoT service data to the RAN reader / writer via the air interface. Correspondingly, the RAN reader / writer can receive the IoT service data returned by each of the multiple IoT devices.

[0299] The RAN reader / writer can send IoT service data from each of the multiple 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 IoT service data from each of the multiple IoT devices from the RAN reader / writer. The UPF network element can send IoT service data from each of the multiple IoT devices to the application function entity through the N6 tunnel.

[0300] This enables application functional entities to communicate with multiple IoT devices through the user plane.

[0301] When a UPF network element completes communication with multiple IoT devices through the N3 tunnel, the UPF network element can dismantle the N3 tunnel. Alternatively, the UPF network element can dismantle the N3 tunnel from the moment it completes the establishment of the N3 tunnel until the effective duration of the N3 tunnel is reached, or at the moment the N3 tunnel terminates. For example, when a UPF network element completes communication with multiple IoT devices through the N3 tunnel, it receives IoT service data from each of the multiple IoT devices in the RAN reader.

[0302] In this embodiment, since the N3 tunnel is a shared tunnel, its effective duration can be longer than that of a dedicated N3 tunnel in a possible implementation. Compared to a possible implementation where the core network establishes m dedicated N3 tunnels for m IoT devices to enable application functional entities to store data on the m IoT devices, the core network dismantles the dedicated N3 tunnel for an IoT device after completing communication with it. Alternatively, the core network dismantles the dedicated N3 tunnel for an IoT device based on its effective duration or termination time. This dismantles m dedicated N3 tunnels, leading to frequent dismantling of dedicated N3 tunnels by the core network.

[0303] When an application function entity needs to perform inventory checks on n IoT devices the next time it passes through the user plane, similar to the scenario where the application function entity performs inventory checks on m IoT devices, the core network will establish n dedicated N3 tunnels for each of the n IoT devices to enable the application function entity to perform inventory checks on the n IoT devices. Here, n is an integer greater than 1.

[0304] The core network will also dismantle n dedicated N3 tunnels, resulting in frequent dismantling of dedicated N3 tunnels in the core network.

[0305] Thus, in scenarios where application functional entities repeatedly inventory multiple IoT devices, the core network will repeatedly establish and dismantle multiple N3 tunnels, resulting in frequent N3 tunnel creation and dismantling by the core network. This also leads to significant core network configuration overhead.

[0306] Optionally, the N6 tunnel can also be established based on the first indication information, and the UPF network element can maintain the correspondence between the N6 tunnel and the first indication information. For the specific implementation principle of the N6 tunnel removal, please refer to the specific implementation principle of the N3 tunnel removal, which will not be repeated here.

[0307] Figure 6B This illustration shows another flowchart of the IoT communication method provided in an embodiment of this application.

[0308] Figure 6B The process of the IoT communication method shown is as follows: Figure 6A The difference in the flow of the IoT communication methods shown is that: Figure 6A In this context, the RAN reader can configure the downlink tunnel identifier of the first tunnel (e.g., tunnel N3) after receiving the uplink tunnel identifier. Figure 6B In this context, the RAN reader 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). Figure 6BIt may include S618-S622, but does not include S610-S612.

[0309] like Figure 6B As shown, the process of this IoT communication method may include: S601a, S602, S603a, S604, S605, S618-S620, S613-S614, S606-S608, S621-S622, S609, S615a, S616-S617.

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

[0311] The specific implementation principles of each step in S601a, S602, S603a, S604, S603b, S605, S613-S614, S606-S608, S609, S615a, S615b, and S616-S617 can be found in [link to relevant documentation]. Figure 6A The specific implementation principles of the corresponding steps are not elaborated here.

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

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

[0314] Optionally, the ninth information may also include information other than the first indication information contained in the first information. For example, the ninth information may 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 tunneling time of the N3 tunnel.

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

[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 be found in S611.

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

[0318] Optionally, the eighth response may also include the identifier of the RAN reader / writer.

[0319] Optionally, the eighth response may also include the identifier of the AF entity to facilitate the binding of the AF entity to the N3 tunnel.

[0320] When the SMF network element receives the eighth response sent by the RAN reader through the AFM network element, the SMF network element can execute S613.

[0321] S613, the SMF network element can synchronize the downlink tunnel identifier of the N3 tunnel with 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] When the UPF network element receives the downlink tunnel identifier of the N3 tunnel from the SMF network element, the UPF network element can execute 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 has received 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] The S606 and UPF network elements can assign uplink tunnel identifiers to the N3 tunnel.

[0326] Optionally, if the first information is used to instruct the establishment of an N3 tunnel, the UPF network element can execute S607.

[0327] S607 and UPF network elements can interact with application function entities to establish N6 tunnels.

[0328] Optionally, the UPF network element can execute S607 after S622 and before S609. That is, the UPF network element can establish the N6 tunnel after the N3 tunnel has been established.

[0329] The S608 and UPF network elements can send a first response to the SMF network element. The first response is a response to the first information, including 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 the tenth information to the RAN reader through the AMF network element. The tenth information may include the uplink tunnel identifier of the N3 tunnel (such as UPF UL TEID). Correspondingly, the RAN reader can receive the tenth information from the SMF network element through the AMF network element.

[0331] S622. The RAN reader / writer can send a first acknowledgment message to the SMF network element through the AMF network element. The first acknowledgment message indicates that the RAN reader / writer has received the tenth message. Correspondingly, the SMF network element can receive the first acknowledgment message from the RAN reader / writer through the AMF network element.

[0332] When the SMF network element receives the first acknowledgment message from the RAN reader through the AMF network element, the SMF network element can execute S609 and S615a, or execute S609 and S615b.

[0333] S609 and UPF network elements can synchronize the N6 tunnel address on the UPF network element side with the IoT NF network element to facilitate the IoT NF network element's management of IoT services.

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

[0335] Figure 6C This illustration shows another flowchart of the IoT communication method provided in an embodiment of this application.

[0336] Figure 6C and Figure 6A or Figure 6B The difference is: in Figure 6C In this context, the third information is sent by the IoT NF network element upon receiving the fifth information or an IoT service request from the AF entity, and confirming that the AF entity has access permissions and tunnel establishment permissions. The fifth information is used to instruct the establishment of the N3 tunnel, or, to instruct the establishment of both the N3 and N6 tunnels. See S601b and S623 for details.

[0337] like Figure 6C As shown, the flow of this IoT communication method may include: S601b, S623, S604-S614, S615a and S624.

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

[0339] The specific implementation principles of each step in S604-S614 and S615a can be found in [link to relevant documentation]. Figure 6A The specific implementation principles of the corresponding steps are explained below. For the specific implementation principles of each step in S618-S620 and S621-S622, please refer to [link to documentation]. Figure 6B The specific implementation principles of the corresponding steps are not elaborated here.

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

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

[0342] If the second indication information in the fifth information is the N3 tunnel indication, the fifth information may also include the tunneling time of the N3 tunnel.

[0343] In the case where the second indication information in the fifth information is the N3N6 tunnel indication, the fifth information may also include the tunnel time of the N3 tunnel, the tunnel time of the N6 tunnel, and the N6 tunnel address of the AF entity.

[0344] IoT service requests may include the identifier ID of the AF entity, first indication information, IoT service type, and tunnel time of the N3 tunnel. Optionally, IoT service requests may also include tunnel time of the N6 tunnel.

[0345] S623 and IoT NF network elements can check the access permissions and tunnel establishment permissions of AF entities.

[0346] For example, an IoT NF network element can send a request to a UDM network element to instruct on the access permissions and tunnel establishment permissions of the application function entity. Correspondingly, the UDM network element can receive a request from a NEF network element to instruct on the access permissions and tunnel establishment permissions of the application function entity.

[0347] The UDM network element can send a check confirmation message to the IoT NF network element if it confirms that the registration information set contains the access permissions and tunnel establishment permissions corresponding to the application function entity's ID. Alternatively, the UDM network element can send a check confirmation message to the IoT NF network element if it confirms that the registration information set contains the application function entity's ID. Correspondingly, the IoT NF network element can receive the check confirmation message from the UDM network element. Then, the IoT NF network element can execute S604.

[0348] The UDM network element can send a check denial message to the IoT NF network element if the registration information set does not contain the access permissions and / or tunnel establishment permissions corresponding to the application function entity's ID. Alternatively, the UDM network element can send a check denial message to the IoT NF network element if the registration information set does not contain the application function entity's ID. Correspondingly, the IoT NF network element can receive the check denial message from the UDM network element. In this case, the IoT NF network element may not need to execute S604.

[0349] Optionally, the IoT NF network element can pre-store a registration information set or pre-obtain a registration information set from the core network. The IoT NF network element can check whether the registration information set contains the access permissions and tunnel establishment permissions corresponding to the ID of the application function entity, or check whether the registration information set contains the ID of the application function entity.

[0350] If the registration information set contains the access permissions and tunnel establishment permissions corresponding to the ID of the application function entity, or contains the ID of the application function entity, it means that the application function entity has access permissions and tunnel establishment permissions, and the IoT NF network element can execute S604.

[0351] If the registration information set does not contain the access permissions and / or tunnel establishment permissions corresponding to the ID of the application function entity, or does not contain the ID of the application function entity, it can be said that the application function entity does not have access permissions and / or tunnel establishment permissions, and the IoT NF network element does not need to execute S604.

[0352] In this way, by checking the access permissions and tunnel establishment permissions of application functional entities, the probability of establishing tunnels (such as N3 tunnels and / or N6 tunnels) for application functional entities that do not have access permissions and / or tunnel establishment permissions can be reduced, thereby reducing the impact on the security of IoT business data transmission.

[0353] Optionally, if the first indication information carried in the fifth information is information that the core network cannot recognize, the IoT NF network element can convert the first indication information in the fifth information into information that the core network can recognize and execute S604.

[0354] If the first indication information carried in the IoT service request is information that the core network cannot recognize, the IoTNF network element can convert the first indication information in the IoT service request into information that the core network can recognize and execute S604.

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

[0356] The third information may also include information contained in the fifth information other than the first instruction information, or it may include information contained in the IoT service request other than the first instruction information.

[0357] Optionally, S623 is an optional step. When the IoT NF network element receives the fifth information or IoT service request from the AF entity, the IoT NF network element can execute S604 instead of S623.

[0358] For example, if the AF entity and the IoT NF network element are located in the same trusted domain, or if the IoT NF network element determines that the AF entity is trusted, the IoT NF network element can execute S604 instead of S623 when it receives the fifth information or IoT service request from the AF entity.

[0359] S624. If a second response from an SMF network element can be received, the IoT NF network element can send a fourth response to the AF entity. The fourth response may be a response to the fifth information. The fourth response may include the uplink tunnel identifier 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, if the third information is used to indicate the establishment of N3 and N6 tunnels, the fourth response may also include the N6 tunnel address of the UPF network element.

[0361] Figure 7 This illustration shows another flowchart of the IoT communication method provided in an embodiment of this application.

[0362] In another embodiment of this application, the Application Functional Entity (AF entity) can send IoT service requests to multiple IoT devices through control. For example, the AF entity can... Figure 1 The link shown sends IoT service requests to multiple IoT devices. When the IoT NF network element receives an IoT service request, it can trigger the core network to establish an N3 tunnel, or the establishment of both the N3 and N6 tunnels.

[0363] like Figure 7 As shown, the IoT communication method provided in this application embodiment may include S701, S604-S615a.

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

[0365] The specific implementations of S701 and S604 can be found in the following description. The specific implementation principles of S605-S617 can be found in... Figure 6A The specific implementation principles of steps S605-S617 in the embodiment are explained below. For the specific implementation principles of each step in S618-S620 and S621-S622, please refer to [link to documentation]. Figure 6B The specific implementation principles of the corresponding steps are not elaborated here.

[0366] S701. Application function entities can send IoT service requests to multiple IoT devices through NEF network elements, IoT NF network elements, AMF network elements, and RAN readers. Correspondingly, each IoT device can receive IoT service requests.

[0367] Application functional entities can send IoT service requests to multiple IoT devices through NEF network elements, IoT NF network elements, AMF network elements and RAN readers. In other words, application functional entities can send IoT service requests to each IoT device among multiple IoT devices through the control plane.

[0368] The IoT service request may 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] During the process where an application function entity can send IoT service requests to each IoT device among multiple IoT devices through control, the NEF network element can receive IoT service requests from the application function entity. The IoT NF network element can also receive IoT service requests from the NEF network element.

[0370] Upon receiving an IoT service request from a NEF network element, the IoT NF network element can not only send the IoT service request to the AMF network element, but also execute S604.

[0371] For example, upon receiving an IoT service request, the IoT NF network element can obtain the first indication information in the IoT service request.

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

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

[0374] IoT NF network elements can be configured with a second instruction information.

[0375] When the second indication information configured in the IoT NF network element is the N3 tunnel indication, the IoT NF network element can also configure the tunneling time of the N3 tunnel.

[0376] When the second indication information configured in the IoT NF network element is an N3N6 tunnel indication, the IoT NF network element can also configure the tunnel time of the N3 tunnel, the tunnel time of the N6 tunnel, and the N6 tunnel address of the application function entity. When the N6 tunnel address of the application function entity is the IP address of the application function entity, the IoT NF network element can obtain the IP address of the application function entity carried in the IoT service request without needing to configure the N6 tunnel address of the application function entity.

[0377] In this way, IoT NF network elements 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 instruct the establishment of an N3 tunnel, or to instruct the establishment of both an N3 tunnel and an N6 tunnel. The third information may include first instruction 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 it can be the first indication information that the core network can recognize in the IoT service request. The third information may also include the second indication information and tunnel time of the IoT NF network element configuration, as well as information contained in the IoT service request other than the first indication information.

[0380] For example, the third information may include the first instruction information.

[0381] When the third information is used to indicate the establishment of the N3 tunnel, the third information may also include the identifier of the application functional entity, the first indication information, the IoT service type, the tunnel time of the N3 tunnel, and the N3 tunnel indication.

[0382] When the third information is used to indicate the establishment of N3 and N6 tunnels, the third information may also include the identifier of the application functional entity, the first indication information, the IoT service type, the tunnel time of N3 tunnel, the tunnel time of N6 tunnel, the N6 tunnel address of the application functional entity (such as the IP address of the application functional entity or the GTP protocol address of the application functional entity), and the N3N6 tunnel indication.

[0383] like Figure 7 In the illustrated embodiment, the application function entity sends IoT service requests to multiple IoT devices via control. Upon receiving the IoT service request, the IoT NF network element sends third information to the SMF network element to trigger the core network to establish an N3 tunnel, or both an N3 and N6 tunnel. Thus, after the N3 tunnel is established, the application function entity can communicate with multiple IoT devices through the user plane. Furthermore, the N3 tunnel established by the core network is a shared tunnel that can be used by multiple IoT devices, eliminating the need to establish dedicated N3 tunnels for each IoT device, thereby reducing the configuration overhead of the core network and the RAN reader / writer.

[0384] Figure 8 This illustration shows another flowchart of the IoT communication method provided in an embodiment of this application.

[0385] In another embodiment of this application, IoT devices can register on the core network. When multiple IoT devices complete their registration on the core network, the IoT NF network element can obtain the registration information of the multiple IoT devices. The IoTNF network element can trigger the core network to establish a shared N3 tunnel for the multiple IoT devices, facilitating communication between the application function entity and the multiple IoT devices.

[0386] like Figure 8 As shown, the IoT communication method provided in this application embodiment may include: S801, S604-S606, S608, S610-S615a.

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

[0388] The specific implementations of S801 and S604 can be found in the following description. The specific implementation principles of S605-S606, S608, and S610-S615a can be found in... Figure 6A The specific implementation principles of the corresponding steps in the embodiment, and the specific implementation principles of each step in S618-S620 and S621-S622, can be found in [reference needed]. Figure 6BThe specific implementation principles of the corresponding steps are not elaborated here.

[0389] AF entities can trigger IoT devices to register on the core network, thus achieving IoT device registration.

[0390] S801. When multiple IoT devices have completed device registration on 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] For example, the core network can periodically synchronize the registration information of multiple IoT devices registered within a period to the IoT NF network element according to a preset period.

[0392] Optionally, IoT devices can register on the core network or on an IoT NF network element. When multiple IoT devices complete registration, the IoT NF network element can obtain the registration information of all IoT devices.

[0393] The registration information for IoT devices can include the device's identifier.

[0394] When the IoT NF network element obtains the identifiers of each IoT device among multiple IoT devices, the IoT NF network element can configure the N3 tunnel indication and the tunneling time of the N3 tunnel, and execute S604.

[0395] The registration information for IoT devices can also include the service validity period of the IoT devices. The tunnel time of the N3 tunnel can be the longest validity period among the service validity periods of multiple IoT devices.

[0396] Optionally, the registration information for IoT devices may also include the device category. Device categories could include, for example, temperature devices, humidity devices, lighting devices, or air quality devices.

[0397] When an IoT NF network element obtains multiple IoT devices including multiple device categories, the IoT NF network element can group the multiple IoT devices according to the device category to obtain multiple IoT device groups.

[0398] S604, the IoT NF network element can send third information to the SMF network element. This third information can be used to instruct the establishment of an N3 tunnel. The third information may include first instruction 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 may include information about one or more IoT device groups. The information about the IoT device group may be the identifier of the IoT device group. The core network may store the correspondence between the identifier of the IoT device group and the identifiers of each IoT device within that IoT device group, so that the UPF network element and RAN node can determine the IoT device group to which the IoT device belongs based on the identifier of the IoT device, and then determine the N3 tunnel based on the identifier of the IoT device group. This IoT device group may include the identifiers of each IoT device among the multiple IoT devices obtained by the IoT NF network element in S801.

[0400] Optionally, the first indication information in the third information may include the identifier of each IoT device among the multiple 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. This can reduce the configuration overhead of the core network and the RAN reader / writer.

[0402] Understandably, when the first indication information in the third information includes information about each IoT device group within multiple IoT device groups, the core network can establish corresponding N3 tunnels for each IoT device group through S605-S606, S608, S610-S615a, or through S605, S618-S620, S613-S614, S606, S608, S621-S622, and S615a. Since an IoT device group can include multiple IoT devices, the N3 tunnels established for each IoT device group remain shared tunnels. The core network still does not need to establish a dedicated N3 tunnel for each IoT device to enable communication between application function entities and multiple IoT devices, reducing the configuration overhead of the core network and the RAN reader / writer.

[0403] like Figure 8In the illustrated embodiment, when multiple IoT devices have completed device registration in the core network, the IoT NF network element can send third information to the SMF network element to trigger the core network to establish an N3 tunnel corresponding to the IoT device group or multiple IoT devices based on the information of the IoT device group or multiple IoT devices carried in the third information. This enables the application function entity to communicate with the registered multiple IoT devices through the user plane. The core network does not need to establish a dedicated N3 tunnel for each of the multiple IoT devices, which can reduce the configuration overhead of the core network and the RAN reader / writer.

[0404] Figure 9 This illustration shows another flowchart of the communication method provided in an embodiment of this application.

[0405] In another embodiment of this application, before the core network or UPF network element completes the establishment of the N3 tunnel, the N6 tunnel can be established after the seventh, fourth, third and first information all indicate the establishment of the N3 tunnel.

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

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

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

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

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

[0411] The specific implementation principles of each step in S601a-S606, S608, and S610-S617 can be found in [link to relevant documentation]. Figure 6A The specific implementation principles of the corresponding steps in the embodiment are explained below. For the specific implementation principles of each step in S618-S620 and S621-S622, please refer to... Figure 6B The specific implementation principles of the corresponding steps are explained in section S601b and S623-S624. For the detailed implementation principles of each step in S601b and S623-S624, please refer to [link to section S601b]. Figure 6C The specific implementation principle of the corresponding steps is as follows. For steps S604 following S623, please refer to... Figure 6C S604 in the document. Further details will not be provided here.

[0412] S901. The application function entity can send eleventh information to the NEF network element. The eleventh information may include the identifier of the application function entity, first indication information, tunnel time of the N6 tunnel, second indication information, and 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 piece of 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 eleventh piece of information can be N6 tunnel indication information. N6 tunnel indication information can be simply referred to as N6 tunnel indication. N6 tunnel indication is used to indicate the establishment of an N6 tunnel. For example, N6 tunnel indication can be 2.

[0414] Optionally, the eleventh information may also include IoT business types.

[0415] If the IoT service type in the eleventh message is inventory, the eleventh message indicates that the established N6 tunnel can be used to realize the inventory of IoT devices.

[0416] If the IoT service type in the eleventh message is command, the eleventh message indicates that the established N6 tunnel can be used to implement commands to IoT devices.

[0417] If the IoT service type in the eleventh message is registration, the N6 tunnel established by the eleventh message can be used to instruct IoT devices to register.

[0418] Optionally, the eleventh message may not include the IoT service type. If the eleventh message does not include the IoT service type, the N6 tunnel established by the eleventh message can be used to implement inventory, command, and instruction registration for IoT devices.

[0419] S902 and NEF network elements can check the access permissions and tunnel establishment permissions of application function entities.

[0420] For details on the specific implementation principle of NEF network element checking the access permissions and tunnel establishment permissions of application functional entities, please refer to the specific implementation principle of NEF network element checking the access permissions and tunnel establishment permissions of application functional entities in S602.

[0421] If the application function entity is confirmed to have access permissions and tunnel establishment permissions, the NEF network element can execute S903a or S903b.

[0422] If it is confirmed that the application function entity does not have access rights and / or tunnel establishment rights, the NEF network element may not execute S903a or S903b.

[0423] In this way, by checking the access permissions and tunnel establishment permissions of application functional entities, the probability of establishing N6 tunnels for application functional entities that do not have access permissions and / or tunnel establishment permissions can be reduced, thereby reducing the impact on the security of IoT business data transmission.

[0424] Optionally, if the first indication information carried in the eleventh information is information that the core network cannot recognize, the NEF network element can convert the first indication information in the eleventh information into information that the core network can recognize. For 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 recognize, please refer 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 recognize in S602, which will not be repeated here.

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

[0426] For example, if the NEF network element converts the first indication information in the eleventh information, which is not recognizable by the core network, into information that the core network can recognize, 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 execute S904.

[0427] The first indication information included in the twelfth information may be the first indication information that the core network can recognize after converting the first indication information carried in the eleventh information. The twelfth information may also include information other than the first indication information contained in the eleventh information.

[0428] If the NEF network element fails to convert the first indication information in the eleventh message into information recognizable by the core network, the NEF network element can send the thirteenth message to the IoT NF network element. Correspondingly, the IoT NF network element can receive the thirteenth message from the NEF network element.

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

[0430] For example, when an IoT NF network element receives the thirteenth message from a NEF network element, and the first indication information in the thirteenth message is information that the core network cannot recognize, the IoT NF network element can convert the first indication information in the thirteenth message into information that the core network can recognize, and execute S904.

[0431] The specific implementation principle of the IoT NF network element converting the first indication information in the thirteenth information into information that the core network can recognize can be found in 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 recognize, which will not be repeated here.

[0432] For example, when the IoT NF network element receives the thirteenth message from the NEF network element, and the first indication information carried in the thirteenth message is information that the core network can recognize, the IoT NF network element can execute S904.

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

[0434] When the SMF network element receives the twelfth message from the NEF network element, the SMF network element can execute S905.

[0435] Understandably, S903b is an optional step.

[0436] In one possible implementation, the communication method provided in this application embodiment may include S903b, but excludes S903a and S904.

[0437] In another possible implementation, the communication method provided in this application embodiment may include S903a and S904, but not S903b.

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

[0439] Among them, the first instruction information in the fourteenth information is information that the core network can recognize.

[0440] When an IoT NF network element receives the twelfth information, the fourteenth information may include the information contained in the fourth information.

[0441] When an IoT NF network element receives the thirteenth information, and the thirteenth information contains first indication information that the core network cannot recognize, the fourteenth information may include first indication information converted from the first indication information in the thirteenth information, as well as information contained in the thirteenth information other than the first indication information.

[0442] When an IoT NF network element receives the thirteenth message, and the thirteenth message contains first indication information that the core network can recognize, the fourteenth message may include the information contained in the thirteenth message.

[0443] S905 and SMF network elements can send second information to UPF network elements. This second information is used to instruct the establishment of a second tunnel, such as an N6 tunnel. The second information may include the identifier of the application function entity, the 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 when an 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] For example, an SMF network element can determine the UPF network element corresponding to the first indication information in the twelfth or fourteenth information based on the correspondence between the first indication information and the UPF network element, and the first indication information in the twelfth or fourteenth information. The SMF network element can then 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 or 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 or fourteenth information. The SMF network element can then send the second information to the determined UPF network element.

[0447] Optionally, the eleventh, twelfth, thirteenth, and fourteenth messages may all carry the identifier of the UPF network element. The identifier of the UPF network element may 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 may send the second message to the UPF network element corresponding to the identifier of the UPF network element.

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

[0449] S607 and the UPF network element can interact with the application function entity to establish the N6 tunnel. The specific implementation principle of S607 can be found in the embodiment shown in Figure 6, and will not be repeated here. After the N6 tunnel is established, the UPF network element can execute 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 includes the 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 also execute S609.

[0451] S609 and UPF network elements can synchronize the N6 tunnel address on the UPF network element side with the IoT NF network element to facilitate the IoT NF network element's management of IoT services.

[0452] like Figure 9 In the illustrated embodiment, the core network or UPF network element can first establish an N6 tunnel, and then establish an N3 tunnel corresponding to the first indication information, i.e., an N3 tunnel shared by multiple IoT devices. This reduces the configuration overhead of the core network while enabling application function entities to communicate with multiple IoT devices through the user plane.

[0453] Figure 10 This illustration shows another flowchart of the IoT communication method provided in an embodiment of this application.

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

[0455] like Figure 10As shown, the IoT communication method may include: S801, S604-S606, S608, S610-S615a, S901-S905, S607, S906, and S609.

[0456] Alternatively, the IoT communication method may 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 S801, S604-S605, S618-S620, S613-S614, S606, S608, S621-S622, and S615a can all be found in [reference needed]. Figure 8 The specific implementation principle of the illustrated embodiment is explained below. For the specific implementation principles of S901-S905, S607, S906, and S609, please refer to [link to documentation]. Figure 9 The specific implementation principles of S901-S905, S607, S906, and S609 in the illustrated embodiment will not be elaborated here.

[0458] like Figure 10 In the illustrated embodiment, the core network or UPF network element can establish an N3 tunnel after multiple IoT devices have completed device registration in the core network. After the N3 tunnel is established, before the application function entity initiates IoT service requests related to these multiple IoT devices, the UPF network element or core network can establish an N6 tunnel corresponding to these multiple IoT devices. This enables communication between the application function entity and multiple IoT devices through the user plane while reducing the configuration overhead of the core network. Furthermore, since the N3 tunnel is established before the application function entity initiates IoT service requests, only the N6 tunnel needs to be established when the application function entity needs to initiate IoT services, reducing tunnel establishment time and thus reducing the IoT service latency of the application function entity, improving user experience.

[0459] Figures 6A-10 Taking the core network, which includes AMF network elements and IoT NF network elements, as an example, this paper explains how to establish an N3 tunnel, or an N3 tunnel and an N6 tunnel, for the UPF network element.

[0460] In one embodiment of this application, the core network may include IoT NF network elements but not AMF network elements. In scenarios where the core network includes IoT NF network elements but not AMF network elements, the specific implementation principle of the UPF network element establishing an N3 tunnel, or establishing both N3 and N6 tunnels, can be found in [link to relevant documentation]. Figures 6A-10The specific implementation principle when the AMF network element is replaced with the IoT NF network element.

[0461] In another embodiment of this application, the core network may include AMF network elements but not IoT NF network elements. In scenarios where the core network includes AMF network elements but not IoT NF network elements, the specific implementation principle of the UPF network element establishing an N3 tunnel, or establishing both N3 and N6 tunnels, can be found in [link to relevant documentation]. Figures 6A-10 The specific implementation principle when the IoT NF network element is replaced with the AMF network element.

[0462] Figures 6A-10 Taking a communication system architecture including a RAN reader as an example, this paper explains how the UPF network element establishes an N3 tunnel shared by multiple IoT devices between the UPF network element and the RAN reader. It is understood that in a communication system architecture including a RAN node and a UE reader, the UPF network element can also establish an N3 tunnel shared by multiple IoT devices between the UPF network element and the RAN node. For example, a communication system architecture including a RAN node and a UE reader... Figure 3 or Figure 4 The architecture shown is illustrated. For the specific implementation principle of the N3 tunnel established between the UPF network element and the RAN node, please refer to [link to relevant documentation]. Figures 6A-10 The specific implementation principle of establishing an N3 tunnel between the UPF network element and the RAN reader as shown in any embodiment is not elaborated here. For example, Figures 6A-10 The specific implementation principle of establishing an N3 tunnel when the RAN reader is replaced by a RAN node is the specific implementation principle of the UPF network element establishing an N3 tunnel between the UPF network element and the RAN node in a communication system architecture that includes RAN nodes and UE readers.

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

[0464] The following example uses a communication system architecture that includes RAN nodes and UE readers, combined with... Figures 11-12 ,right Figure 5 The explanation is provided in S502.

[0465] Figure 11 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0466] Figure 11 and Figure 4 The difference is that, in Figure 11 The image shows multiple UE readers and multiple IoT devices 1101. Multiple UE readers, for example... Figure 11The UE reader / writer 1, UE reader / writer 2, and UE reader / writer 3 are shown in the figure.

[0467] Each of the multiple UE readers can connect to the RAN node via an air interface. Each of the multiple IoT devices 1101 can connect to its corresponding UE reader via an air interface.

[0468] Once the UPF network element has established the N6 and N3 tunnels, the application function entity can transmit a 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 may include an IoT service request and first indication information. Correspondingly, the UPF network element can receive the first data packet from the application function entity.

[0469] For example, an IoT service request may include the identifier of the UE reader / writer. The first data packet may also include the identifier of the UE reader / writer. The first indication information and the identifier of the UE reader / writer may be carried in the header of the first data packet.

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

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

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

[0473] Application functional entities can encapsulate IoT service requests into IoT service request data packets A0, i.e., the first data packet, according to the GTP-U protocol. The GTP-U protocol header of the IoT service request data packet A0 carries the identifiers of UE reader 1, UE reader 2, and UE reader 3.

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

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

[0476] When the N3 tunnel is established based on information from intermediate nodes (such as the identifier of the UE reader / writer), the UPF network element can determine the N3 tunnel 1 corresponding to the identifier of UE reader / writer 1, the N3 tunnel 2 corresponding to the identifier of UE reader / writer 2, and the N3 tunnel 3 corresponding to the identifier of UE reader / writer 3 based on the identifier of UE reader / writer 1, the identifier of UE reader / writer 2, and the identifier of UE reader / writer 3.

[0477] UPF network elements can send IoT service request data packets A1 to RAN nodes (such as gNBs) through N3 tunnel 1. UPF network elements can send IoT service request data packets A2 to RAN nodes (such as gNBs) through N3 tunnel 2. UPF network elements can send IoT service request data packets A3 to RAN nodes (such as gNBs) through N3 tunnel 3.

[0478] IoT service request data packets A1, A2, and A3 all belong to the second data packet category. The difference between IoT service request data packets A1, A2, and A3 is as follows: IoT service request data packet A1 carries the identifier of UE reader 1 in its GTP-U protocol header; IoT service request data packet A2 carries the identifier of UE reader 2 in its GTP-U protocol header; and IoT service request data packet A3 carries the identifier of UE reader 3 in its GTP-U protocol header.

[0479] Correspondingly, the RAN node can receive IoT service request data packets A1, A2, and 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. The IoT service request data packets A1, A2, and A3 are all encapsulated by the UPF network element according to the GTP-U protocol.

[0481] The RAN node parses IoT service request data packets A1, A2, and A3 according to the GTP-U protocol. It then obtains the identifiers of UE reader 1, UE reader 2, and UE reader 3, as well as the IoT service request.

[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 via multicast (PTM). Both the third data packet and the first paging can include IoT service requests.

[0483] In this way, UE reader 1, UE reader 2, and UE reader 3 can all receive third data packets or first paging messages from the RAN node, enabling each of the three UE readers to broadcast the third data packet or first paging message to the IoT devices they manage. Specifically, UE reader 1 sends third data packets or first paging messages to the multiple IoT devices 1101 managed by UE reader 1; UE reader 2 sends third data packets or first paging messages to the multiple IoT devices 1101 managed by UE reader 2; and UE reader 3 sends third data packets or first paging messages to the multiple IoT devices 1101 managed by UE reader 3.

[0484] When 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 identifiers of UE reader 1, UE reader 2, and UE reader 3 belong, based on the identifiers of UE reader 1, UE reader 2, and UE reader 3.

[0485] UPF network elements can send IoT service request data packets A4 to RAN nodes (such as gNBs) through N3 tunnel 4. IoT service request data packet A4 is also a second data packet. The GTP-U protocol header of IoT service request data packet A4 carries the identifiers of UE reader 1, UE reader 2, and UE reader 3. Correspondingly, the RAN node can receive IoT service request data packets A4 from the UPF network element. The RAN node parses IoT service request data packets A4 according to the GTP-U protocol, obtaining the identifiers of UE reader 1, UE reader 2, UE reader 3, and the IoT service request. It should be understood that IoT service request data packets A4 are encapsulated by the UPF network element according to the GTP-U protocol.

[0486] 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 via multicast (PTM). This allows each of the UE readers 1, UE reader 2, and UE reader 3 to broadcast the third data packet or the first paging to the IoT devices they manage.

[0487] Understandably, one UE reader can manage multiple IoT devices.

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

[0489] Optionally, the first indication information includes information about at least one intermediate node corresponding to multiple IoT devices and / or IoT business area information.

[0490] In this context, the IoT service area is associated with at least one intermediate node. When the header of the first data packet carries first indication information, the UPF network element can send the second data packet to the RAN node through the N3 tunnel corresponding to the IoT service area information in the first indication information.

[0491] The header of the second data packet carries first indication 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 of at least one intermediate node, or to instruct the access network node to send a third data packet or a first paging to all intermediate nodes within the IoT service area; both the third data packet and the first paging contain an IoT service request.

[0492] For example, the header of the second data packet carries information about at least one intermediate node, or information about at least one intermediate node and IoT service area information. Upon receiving the second data packet, the RAN node can send a third data packet or a first paging message to each of the at least one intermediate node corresponding to the information about at least one intermediate node carried in the header of the second data packet.

[0493] Alternatively, the header of the second data packet may carry IoT service area information, or information about at least one intermediate node and IoT service area information. Upon receiving the second data packet, the RAN node may send a third data packet or a first paging message to all intermediate nodes within the IoT service area corresponding to the IoT service area information carried in the header of the second data packet.

[0494] At least one intermediate node may include: UE reader 1, UE reader 2, and UE reader 3. In addition to UE reader 1, UE reader 2, and UE reader 3, other UE readers such as UE reader 4 may also be deployed within this IoT service area. UE reader 4 is not... Figure 11 As shown in the image.

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

[0496] Figure 12 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0497] Figure 12and Figure 4 The difference is that, in Figure 12 The image shows multiple UE readers 1201, but no IoT devices are shown. Figure 12 As shown in the image. Multiple UE readers, for example: Figure 12 The five UE readers 1201 in area 1, and, Figure 12 The three UE readers 1201 in area 2.

[0498] Each of the multiple UE readers can connect to the RAN node via the air interface.

[0499] It should be understood that Figure 12 Region 1 and Region 2 in the text are merely examples of regions related to intermediate nodes, and are not a limitation on the number, distribution, or form of regions related to intermediate nodes. Figure 12 The UE readers shown in Region 1 and Region 2 are merely examples of UE readers in the regions and are not a limitation on the number, distribution, or form of UE readers in the regions.

[0500] Once the UPF network element has established the N6 and N3 tunnels, 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] For example, the first indication information in the first data packet or IoT service request includes the identifier of the IoT service area (IoT area ID), which corresponds to cell identifier 1 and cell identifier 2. The identifier of the IoT service area can be a TA ID.

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

[0503] UPF network elements can send IoT service request data packets B0 to RAN nodes through N3 tunnel B0. IoT service request data packets B0 belong to the second data packet category. Correspondingly, RAN nodes can receive IoT service request data packets B0 from UPF network elements.

[0504] Among them, the IoT service request data packet B0 is encapsulated by the UPF network element according to the GTP-U protocol, and the GTP-U protocol header of the IoT service request data packet B0 carries the identifier of the IoT service area.

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

[0506] For example, when the UE reader is a mobile UE reader, the RAN node can convert the identifier of the IoT service area into the corresponding cell identifier 1 and cell identifier 2.

[0507] The RAN node can broadcast a third data packet or a first paging message to cell 1 corresponding to cell identifier 1 and cell 2 corresponding to cell identifier 2, respectively. For example, cell 1... Figure 12 Area 1 in the middle. For example, Residential Area 2. Figure 12 Region 2 in the middle.

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

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

[0510] RAN nodes can send third data packets or first paging messages to the fixed UE readers corresponding to the identifiers of the IoT service areas via multicast.

[0511] It should be understood that the number of fixed UE readers corresponding to the identifier of the IoT business area can be one or more.

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

[0513] If the IoT service area corresponding to the IoT service area identifier is smaller than the coverage area of ​​the cell, the UE reader (such as a mobile UE reader) that receives 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 it manages.

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

[0516] Optionally, if the IoT service area corresponding to the IoT service area identifier is smaller than the coverage area of ​​the cell, the UE reader (such as a mobile UE reader or a fixed reader) that receives 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 it manages.

[0517] IoT devices that receive a third data packet or a first page can determine whether they are in an IoT service area.

[0518] If the IoT device is in the IoT service area, the IoT device can respond to the IoT service request of the third data packet or the first paging indication, 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 may not respond to the IoT service request of the third data packet or the first paging indication, and may 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 multiple IoT devices managed by mobile or fixed UE readers based on the N3 tunnel, thereby enabling application function entities to communicate with multiple IoT devices through the user plane.

[0521] Understandable Figures 1-12 The IoT devices mentioned can be AIoT devices. Figure 1 Example - Figure 12 The IoT service request in the embodiment can be an AIoT service request. Figure 1 Example - Figure 12 The business data in the embodiment can be AIoT business data. Figures 1-12 The IoT NF network element in the code can be an AIoT NF network element. That is, Figures 1-12 The IoT devices in the system can be replaced with AIoT devices. Figure 1 Example - Figure 12 The IoT service request in the embodiment can be replaced with an AIoT service request. Figure 1 Example - Figure 12 The business data in the embodiment can be replaced with AIoT business data. Figures 1-12 The IoT NF network element in the code can be replaced with the AIoT NF network element.

[0522] In one possible implementation, the IoT service request initiated by the AF entity can carry the identifier of the intermediate node. This allows the core network to conduct service communication based on the identifier of the intermediate node, establishing dedicated Protocol Data Unit (PDU) sessions for each intermediate node in the IoT service request. This method can ensure that the IoT service request corresponds to the service even when the format is an AIoT IP packet, a Media Access Control (MAC) packet, or a non-architectural packet. See also... Figure 13 The illustrated embodiment.

[0523] Figure 13 A schematic diagram of another communication system architecture provided in an embodiment of this application is shown.

[0524] like Figure 13 As shown, the IoT service request initiated by the AF entity can carry the identifiers of UE reader 1, UE reader 2, and UE reader 3.

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

[0526] The above text combined Figures 5 to 13 The present application describes in detail the Internet of Things (IoT) communication method according to embodiments of this application. The following is in conjunction with... Figure 14 This application describes in detail the communication apparatus according to embodiments of the present application. The communication apparatus includes modules or units for performing each part of the above embodiments. Modules or units can be software, hardware, or a combination of software and hardware. The following is only a brief illustrative example of the communication apparatus; for details of the implementation, please refer to the description of the foregoing method embodiments, which will not be repeated below.

[0527] Figure 14 A schematic diagram of the structure of a communication device provided in an embodiment of this application is shown. Figure 14 As shown, the communication device may include a transceiver module 1402 and a processing module 1401.

[0528] In one possible implementation, the communication device is used to implement the steps corresponding to the first network element (such as the UPF network element) in the above-described Internet of Things communication method.

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

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

[0531] The first tunnel is established based on first indication information, which includes one or more of the following: IoT business area information, information on IoT device groups to which multiple IoT devices belong, information on intermediate nodes corresponding to multiple IoT devices, or information on intermediate node groups to which intermediate nodes to which multiple IoT devices belong. The intermediate nodes have relay functions and / or reader / writer functions.

[0532] Optionally, the IoT service area information includes one or more of the following: the geographic location information of the IoT service area, 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.

[0533] Optionally, one or more IoT devices may be deployed within the IoT business area.

[0534] Optionally, intermediate nodes may or may not be deployed within the IoT business area.

[0535] Optionally, the transceiver module 1402 can also be used to receive first information, which is used to instruct the establishment of a first tunnel, and the first information includes first instruction information.

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

[0537] Optionally, the transceiver module 1402 can also be used to receive second information, which is used to instruct the establishment of a second tunnel. The second tunnel is a tunnel between the first network element and the application function entity. The second information includes the identifier of the application function entity and the second tunnel address of the application function entity.

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

[0539] Optionally, the first information is also used to instruct the establishment of a second tunnel, which is a tunnel between the first network element and the application function entity. The first information also includes 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 used to establish a second tunnel based on the first information.

[0541] Optionally, the first information is sent by the session management function network element upon receiving the third information from the IoT network function network element or the fourth information from the network exposure function network element. Both the third and fourth information are used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, wherein the second tunnel is a tunnel between the first network element and the application function entity, and both the third and fourth information include the first indication information.

[0542] The third message is sent by IoT network functional elements under any of the following circumstances:

[0543] Receives IoT service requests from network exposed functional elements or application functional entities.

[0544] The system receives fourth information from a network exposure function element or fifth information from an application function entity. The fifth information is used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The fifth information includes first instruction information.

[0545] Registration information was received from multiple IoT devices.

[0546] Optionally, the first information may also include the type of IoT business and the effective duration of the first tunnel.

[0547] The processing module 1401 can also dismantle the first tunnel from the moment the first tunnel is completed until the effective duration is reached.

[0548] IoT business types include one or more of the following: inventory, command, or registration.

[0549] Optionally, the transceiver module 1402 can also be used to send a first response to the session management function network element. The first response is a response to the first information. The first response includes the uplink tunnel identifier of the first tunnel, which is obtained from the first information or configured by the first network element.

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

[0551] Optionally, the transceiver module 1402 can also be used to receive a first data packet, which includes an IoT service request and a first indication information.

[0552] The transceiver module 1402 can also be used 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 includes an IoT service request and the first indication information, with the first indication information carried in the header of the second data packet.

[0553] Optionally, the first indication information includes information about at least one intermediate node corresponding to multiple IoT devices and / or IoT business area information.

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

[0555] In another possible implementation, the communication device is used to implement the steps corresponding to the IoT network functional elements in the above-described IoT communication method.

[0556] The transceiver module 1402 can be used to receive IoT service requests, fourth information, fifth information, or registration information of multiple IoT devices. The fourth and fifth information are both used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The IoT service request, fourth information, and fifth information all include first instruction information, which includes one or more of the following: IoT service area information, information about the IoT device group to which the multiple IoT devices belong, information about the intermediate nodes corresponding to the multiple IoT devices, or information about the intermediate node group to which the intermediate nodes corresponding to the multiple IoT devices belong. 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 used to send third information, which is used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The third information includes first instruction information. The first tunnel is established based on the first instruction information and is used for the first network element to communicate with multiple IoT devices.

[0558] Optionally, the transceiver module 1402 can also be used to receive a second response, which is a response to the third information. The second response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

[0559] Optionally, the second response may also include the second tunnel address of the first network element.

[0560] Optionally, the transceiver module 1402 can also be used to send a third response, which is a response to the fourth information. The third response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

[0561] Alternatively, the transceiver module 1402 can also be used to send a fourth response, which is a response to the fifth information. The fourth response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

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

[0563] The transceiver module 1402 can be used to receive third information or fourth information. Both the third and fourth information are used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel. Both the third and fourth information include 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 used to send first information, which is used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel. The first information includes first indication information, or the first information includes 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 used to receive a first response, which is a response to first information, including the uplink tunnel identifier of the first tunnel.

[0566] The transceiver module 1402 can also be used to send sixth information to access and mobility management function network elements or Internet of Things network function network elements. The sixth information is used to instruct the establishment of a first tunnel. The sixth information includes first instruction information and uplink tunnel identifier of the first tunnel.

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

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

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

[0570] Optionally, the second response may also include the second tunnel address of the first network element.

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

[0572] The transceiver module 1402 can also be used to synchronize the second tunnel address of the first network element to the IoT network functional network element.

[0573] It should be understood that the communication device described here is embodied in the form of a functional module. The term "module" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the communication device can specifically be the terminal device or network device in the above embodiments. The communication device can be used to execute the various processes and / or steps corresponding to the terminal device or network device in the above method embodiments; to avoid repetition, these will not be elaborated further here.

[0574] The aforementioned communication device has the function of implementing the corresponding steps performed by the terminal device or network device in the aforementioned method; the aforementioned function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned function. In the embodiments of this application, Figure 13 The communication device in the text can also be a chip, such as a system-on-a-chip (SoC).

[0575] It should be noted that the module names involved in the embodiments of this application can all be defined as other names, as long as they can achieve the function of each module, and no specific restrictions are placed on the module names.

[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 used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0577] The IoT communication method according to the embodiments of this application has been described above. The apparatus for performing the above method provided in the embodiments of this application is described below. Those skilled in the art will understand that the methods and apparatus can be combined and referenced with each other, and the related apparatus provided in the embodiments of this application can perform the steps in the above method.

[0578] The IoT communication method provided in this application can be applied to electronic devices with communication functions. Electronic devices include terminal devices, and the specific device form of the terminal device can be referred to the above-mentioned descriptions, which will not be repeated here.

[0579] This application provides a communication system, which includes: a first network element, an Internet of Things (IoT) network function network element, and a session management function network element; the first network element is used to execute the steps corresponding to the first network element in the above-described IoT communication method, the IoT network function network element is used to execute the steps corresponding to the IoT network function network element in the above-described IoT communication method, and the session management function network element is used to execute the steps corresponding to the session management function network element in the above-described IoT communication method.

[0580] This application provides an electronic device, which includes a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing a terminal device to perform the above-described method.

[0581] This application provides a chip. The chip includes a processor, which is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to those in the related embodiments described above, and will not be repeated here.

[0582] This application provides a chip system. The chip system includes at least one processor and a communication interface, the communication interface and the at least one processor being interconnected via a circuit, and the at least one processor being used to run computer programs or instructions to perform the above-described method.

[0583] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements the methods described above. The methods described in the above embodiments can be implemented wholly or partially by software, hardware, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted over the computer-readable medium. The computer-readable medium can include computer storage media and communication media, 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 accessible by a computer.

[0584] In one possible implementation, a computer-readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage or other magnetic storage devices, or any other medium targeted to carry or to store the required program code in the form of instructions or data structures, and accessible by a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include optical discs, laser discs, optical discs, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0585] This application provides a computer program product, which includes a computer program that, when run, causes the computer to perform the above-described method.

[0586] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0587] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

1. An Internet of Things (IoT) communication method, characterized in that, Applied to the first network element, the method includes: Establish a first tunnel, which is a shared tunnel between the first network element and the access network node; Communicating with multiple IoT devices via the first tunnel, and / or communicating with at least one intermediate node via the first tunnel; The first tunnel is established based on first indication information, which includes one or more of the following: IoT business area information, information on the IoT device group to which the multiple IoT devices belong, information on the intermediate nodes corresponding to the multiple IoT devices, or information on the intermediate node group to which the intermediate nodes corresponding to the multiple IoT devices belong.

2. The method according to claim 1, characterized in that, The IoT service area information includes one or more of the following: the 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 corresponding to the IoT service area, or one or more base station identifiers corresponding to the IoT service area.

3. The method according to claim 1 or 2, characterized in that, One or more IoT devices are deployed within the IoT business area.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive first information, the first information being used to instruct the establishment of a first tunnel, the first information including the first instruction information; The establishment of the first tunnel includes: establishing the first tunnel based on the first information.

5. The method according to claim 4, characterized in that, The method further includes: Receive second information, the second information being used to instruct the establishment of a second tunnel, the second tunnel being a tunnel between the first network element and the application function entity, the second information including the identifier of the application function entity and the second tunnel address of the application function entity; Based on the second information, the second tunnel is established.

6. The method according to claim 4, characterized in that, The first information is also used to instruct the establishment of a second tunnel, which is a tunnel between the first network element and the application function entity. The first information also includes the identifier of the application function entity and the second tunnel address of the application function entity. The method further includes: establishing a 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 the session management function network element upon receiving the third information from the Internet of Things network function network element or upon receiving the fourth information from the network exposure function network element; the third information and the fourth information are both used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, wherein the second tunnel is 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 piece of information is sent by an IoT network functional element under any of the following circumstances: Receive IoT service requests from network exposed functional elements or application functional entities; The system receives fourth information from a network exposure function element or fifth information from an application function entity. The fifth information is used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The fifth information includes the first instruction information. Registration information was received from the multiple IoT devices.

8. The method according to any one of claims 4-7, characterized in that, The first information also includes the type of IoT service and the effective duration of the first tunnel; The method further includes: dismantling the first tunnel from the moment the first tunnel is completed until the effective duration is reached; The IoT service types include 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 establishment of the first tunnel based on the first information includes: Send a first response to the session management function network element. The first response is a response to the first information. The first response includes the uplink tunnel identifier of the first tunnel, which is obtained from the first information or configured by the first network element.

10. The method according to claim 9, characterized in that, The step of establishing the first tunnel based on the first information further includes: Receive the downlink tunnel identifier of the first tunnel.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: Receive a first data packet, the first data packet including an IoT service request and the first indication information; The communication with multiple IoT devices based on the first tunnel, and / or the communication with at least one intermediate node based on the first tunnel, includes: A second data packet is sent to the access network node through the first tunnel corresponding to the first indication information. The second data packet includes the IoT service request and the first indication information, with the first indication information carried in the header of the second data packet.

12. The method according to claim 11, characterized in that, The first indication information includes information about at least one intermediate node corresponding to the plurality of IoT devices and / or the IoT service area information; Sending the second data packet to the access network node through the first tunnel corresponding to the first indication information includes: The second data packet is sent to the access network node through the first tunnel corresponding to the IoT service area information; The header of the second data packet carries first indication information, which 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 to instruct the access network node to send a third data packet or a first paging to all intermediate nodes within the IoT service area; both the third data packet and the first paging contain the IoT service request.

13. An Internet of Things (IoT) communication method, characterized in that, Network elements used in IoT networks include: The system receives IoT service requests, fourth information, fifth information, or registration information of multiple IoT devices; the fourth and fifth information are both used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel; the IoT service request, the fourth information, and the fifth information all include first instruction information, which includes one or more of the following: IoT service area information, information on the IoT device group to which the multiple IoT devices belong, information on the intermediate nodes corresponding to the multiple IoT devices, or information on the intermediate node group to which the intermediate nodes corresponding to the multiple IoT 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; Send a third message, which is used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The third message includes the first instruction message, the first tunnel is established based on the first instruction message, and is used for the first network element to communicate with the plurality of IoT devices.

14. The method according to claim 13, characterized in that, The method further includes: Receive a second response, which is a response to the third information, and the second response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

15. The method according to claim 14, characterized in that, The second response also includes the second tunnel address of the first network element.

16. The method according to any one of claims 13-15, characterized in that, The method further includes: Send a third response, which is a response to the fourth information, and the third response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel; or, Send a fourth response, which is a response to the fifth information, and the fourth response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

17. An Internet of Things (IoT) communication method, characterized in that, The method, applied to a network element for session management functions, includes: Receive third or fourth information, both of which are used to indicate the establishment of a first tunnel, or to indicate the establishment of a first tunnel and a second tunnel, both of which include 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; Send first information, which is used to instruct the establishment of a first tunnel, or to instruct the establishment of a first tunnel and a second tunnel. The first information includes the first instruction information, or the first information includes the first instruction information, the identifier of the application function entity, and the second tunnel address of the application function entity.

18. The method according to claim 17, characterized in that, The method further includes: Receive a first response, which is a response to the first information, and the first response includes the uplink tunnel identifier of the first tunnel; Send a sixth message to the access and mobility management function network element or the Internet of Things network function network element. The sixth message is used to instruct the establishment of a first tunnel. The sixth message includes the first instruction information and the uplink tunnel identifier of the first tunnel. 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, the fifth response including the downlink tunnel identifier of the first tunnel; Synchronize the downlink tunnel identifier of the first tunnel to the first network element.

19. The method according to claim 18, characterized in that, The method further includes: A second response is sent to the IoT network function element. The second response is a response to the third information. The second response includes the uplink tunnel identifier and the downlink tunnel identifier of the first tunnel.

20. The method according to claim 19, characterized in that, The second response also includes the second tunnel address of the first network element.

21. The method according to any one of claims 18-20, characterized in that, The first information also includes the second tunnel address of the application function entity, and the first response also includes the second tunnel address of the first network element; The method further includes: Synchronize the second tunnel address of the first network element with the IoT network functional element.

22. A communication system, characterized in that, include: A first network element, an IoT network function network element, and a session management function network element; the first network element is used to perform the method as described in any one of claims 1 to 12, the IoT network function network element is used to perform the method as described in any one of claims 13 to 16, and the session management function network element is used to perform the method as described in any one of claims 17 to 21.

23. A communication device, characterized in that, include: It includes modules for performing the method as described in any one of claims 1 to 12, any one of claims 13 to 16, or any one of claims 17 to 21.

24. A communication device, characterized in that, The communication device includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the communication device to perform the method as claimed in any one of claims 1 to 12, the method as claimed in any one of claims 13 to 16, or the method as claimed in any one of claims 17 to 21.

25. A chip system, characterized in that, The chip system is applied to a communication device, the chip system including one or more processors, the one or more processors being configured to invoke computer instructions to cause the communication device to perform the method as described in any one of claims 1 to 12, the method as described in any one of claims 13 to 16, or the method as described in any one of claims 17 to 21.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on a communication device, cause the communication device to perform the method as claimed in any one of claims 1 to 12, the method as claimed in any one of claims 13 to 16, or the method as claimed in any one of claims 17 to 21.

27. A computer program product, characterized in that, The computer program product includes computer program code that, when run on a communication device, causes the communication device to perform the method as described in any one of claims 1 to 12, any one of claims 13 to 16, or any one of claims 17 to 21.

Images