Path selection method and device, equipment and storage medium

CN118923191APending Publication Date: 2024-11-08GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093621.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-07-19
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the existing technology, there is a lack of clear methods for selecting communication paths between IoT devices. Especially in remote deployment scenarios, it is difficult to ensure normal transmission of services.

Method used

Identify candidate IoT devices through management devices, and select appropriate communication paths, including direct connections, gateways, and cellular network paths, based on the distance between devices, association relationships, and gateway service range.

Benefits of technology

Regardless of whether the device is deployed in a short distance or in a remote location, it can communicate through appropriate communication paths to ensure normal transmission and accessibility of services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923191A_ABST
    Figure CN118923191A_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a path selection method and apparatus, a device, and a storage medium. The method comprises: a management device determining at least one candidate Internet of Things device for a first Internet of Things device (410); the management device is based on at least one of the following. Determining a candidate communication path between each candidate Internet of Things device and the first Internet of Things device: a distance between each candidate Internet of Things device in the at least one candidate Internet of Things device and the first Internet of Things device, and an association relationship between a gateway device associated with each candidate Internet of Things device and the first Internet of Things device; whether each candidate Internet of Things device and the first Internet of Things device are within the service range of the Internet of Things gateway device is determined; the candidate communication path is used for path selection (420).
Need to check novelty before this filing date? Find Prior Art

Description

Path selection method, device, equipment, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a path method and apparatus, device, and storage medium. Background Art

[0002] In practical applications, a user-created Personal IoT Network (PIN) can include three types of devices: ordinary Personal IoT devices (PIN Element, PINE), Personal IoT devices with gateway capabilities (PIN Element with Gateway Capability, PEGC), and IoT devices with management capabilities (PIN Element with Management Capability, PEMC). PINEs have basic communication capabilities and can communicate with each other through direct communication technologies such as Wireless Fidelity (WiFi) and Bluetooth. PINEs can also communicate with each other through PEGC. In addition, PEGC and PEMC have the ability to access cellular networks (such as 5G systems) and can use cellular networks to provide data forwarding and management services between PINEs. Although PINEs can communicate with each other through these three different methods, there is no clear method for selecting the appropriate communication method for PINEs.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a path selection method, apparatus, device, and storage medium.

[0005] In a first aspect, a path selection method is provided, the method comprising:

[0006] The management device determines at least one candidate IoT device for the first IoT device;

[0007] The management device determines, based on at least one of the following: a distance between each candidate IoT device and the first IoT device, an association relationship between a gateway device associated with each candidate IoT device and the first IoT device, and whether each candidate IoT device and the first IoT device are within a service range of an IoT gateway device;

[0008] The candidate communication paths are used for path selection.

[0009] In a second aspect, a path selection method is provided, the method comprising:

[0010] The first Internet of Things device sends first request information, where the first request information is used to request a first service required by the first Internet of Things device and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

[0011] In a third aspect, a path selection method is provided, the method comprising:

[0012] The first Internet of Things gateway device receives a first request message sent by a first Internet of Things device; the first request message is used to request a first service required by the first Internet of Things device, and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

[0013] In a fourth aspect, a path selection method is provided, the method comprising:

[0014] The second Internet of Things device receives second indication information, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

[0015] In a fifth aspect, a path selection device is provided, which is applied to a management device, and the device includes:

[0016] a candidate device determining unit, configured to determine at least one candidate IoT device for the first IoT device;

[0017] a candidate path determining unit configured to determine a candidate communication path between each candidate IoT device and the first IoT device based on at least one of the following: a distance between each candidate IoT device among the at least one candidate IoT device and the first IoT device, an association relationship between a gateway device associated with each candidate IoT device and the first IoT device, and whether each candidate IoT device and the first IoT device are within a service range of an IoT gateway device;

[0018] The candidate communication paths are used for path selection.

[0019] In a sixth aspect, a path selection device is provided, applied to a first IoT device, the device comprising:

[0020] The sending unit is configured to send first request information, where the first request information is used to request a first service required by the first Internet of Things device and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

[0021] In a seventh aspect, a path selection device is provided, applied to a first Internet of Things gateway device, the device comprising:

[0022] A receiving unit is configured to receive a first request message sent by a first Internet of Things device; the first request message is used to request a first service required by the first Internet of Things device, and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

[0023] In an eighth aspect, a path selection device is provided, applied to a second IoT device, the device comprising:

[0024] The receiving unit is configured to receive second indication information, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

[0025] The communication device provided in an embodiment of the present application may be the management device, the first IoT device, the second IoT device, or the first IoT gateway device in the above-described solution. The communication device includes a processor, a memory, and a transceiver. The transceiver is used to implement communication between the communication device and other devices, the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory to perform the above-described path selection method.

[0026] The chip provided in the embodiment of the present application is used to implement the above-mentioned path selection method.

[0027] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned path selection method.

[0028] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned path selection method.

[0029] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned path selection method.

[0030] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned path selection method.

[0031] An embodiment of the present application provides a path selection method, wherein a management device determines at least one candidate IoT device for a first IoT device; further, the management device can determine a candidate communication path between each candidate IoT device and the first IoT device based on the distance between each candidate IoT device in the at least one candidate IoT device and the first IoT device, and / or the relationship between the gateway device associated with each candidate IoT device and the first IoT device, and / or whether each candidate IoT device and the first IoT device are within the service range of the IoT gateway device; wherein the candidate communication path is used for path selection. In other words, the management device can select a suitable communication path for business interaction between IoT devices based on at least one of the three items: the location of the IoT device, the relationship between the IoT device and the IoT gateway device, and whether the IoT device is within the service range of the IoT network element. In this way, whether the IoT devices are in a scenario where they are close to each other or in a scenario where they are deployed in different locations, they can communicate through a suitable communication path, ensuring the normal transmission of the business. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0033] FIG1 is a schematic diagram of an exemplary network architecture of a personal Internet of Things provided in an embodiment of the present application;

[0034] FIG2A is a schematic diagram of a direct communication provided by an embodiment of the present application;

[0035] FIG2B is a schematic diagram of communication via PEGC provided in an embodiment of the present application;

[0036] FIG2C is a schematic diagram of communication via a cellular network provided by an embodiment of the present application;

[0037] FIG3 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0038] FIG4 is a flow chart of a path selection method according to an embodiment of the present application;

[0039] FIG5 is a second flow chart of a path selection method provided in an embodiment of the present application;

[0040] FIG6 is a third flow chart of a path selection method provided in an embodiment of the present application;

[0041] FIG7A is a first schematic diagram of a transmission process of a data forwarding policy configuration request provided in an embodiment of the present application;

[0042] FIG7B is a second schematic diagram of a transmission process of a data forwarding policy configuration request provided in an embodiment of the present application;

[0043] FIG7C is a third schematic diagram of a transmission process of a data forwarding policy configuration request provided in an embodiment of the present application;

[0044] FIG7D is a fourth schematic diagram of a transmission process of a data forwarding policy configuration request provided in an embodiment of the present application;

[0045] FIG8 is a fourth flow chart of a path selection method provided in an embodiment of the present application;

[0046] FIG9 is a fifth flow chart of a path selection method provided in an embodiment of the present application;

[0047] FIG10 is a sixth flow chart of a path selection method according to an embodiment of the present application;

[0048] FIG11 is a flow chart of a path selection method according to an embodiment of the present application;

[0049] FIG12 is a schematic structural diagram of a path selection device 1200 provided in an embodiment of the present application;

[0050] FIG13 is a schematic structural diagram of a path selection device 1300 provided in an embodiment of the present application;

[0051] FIG14 is a schematic structural diagram of a path selection device 1400 provided in an embodiment of the present application;

[0052] FIG15 is a schematic structural diagram of a path selection device 1500 provided in an embodiment of the present application;

[0053] FIG16 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0054] FIG17 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0055] Figure 18 is a schematic block diagram of a communication system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0056] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0057] In practical applications, IoT devices can be wearable devices such as cameras, earphones, watches, headphones, and health monitors; they can also be household appliances such as smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, washing machines, lawn mowers, and robots; and they can also be office or factory equipment such as printers, meters, and sensors. This allows users to create personal IoT networks using these IoT devices in their homes, offices, factories, or surrounding environments.

[0058] Currently, IoT devices can only access the internet through relay devices and gateways, or through cellular networks via smart terminals (such as mobile phones and tablets). In both cases, the cellular core network is unaware that IoT devices are connected to the cellular network. However, in order to fully utilize the cellular network to assist in the management and service support of IoT devices, enabling cellular networks to participate in the personal Internet of Things is essential.

[0059] FIG1 is a schematic diagram of an exemplary network architecture of a personal Internet of Things provided in an embodiment of the present application.

[0060] As shown in Figure 1, the personal Internet of Things (PIoT) 100 may include an IoT device, an IoT gateway device, and an IoT management device. The IoT device may be a standard personal IoT device, such as a PINE. The IoT gateway device refers to an IoT device with gateway capabilities, such as a PEGC. The IoT management device refers to an IoT device with management capabilities, such as a PEMC. In other words, in addition to possessing gateway and management capabilities, both the IoT gateway device and the IoT management device possess the functions of an IoT device. This is not limited in the present embodiment.

[0061] It should be understood that IoT devices can communicate with each other, with IoT gateway devices, and with IoT management devices via direct communication technologies (e.g., WiFi, Bluetooth, etc.). Furthermore, IoT gateway devices and IoT management devices have access to cellular networks (e.g., Long Term Evolution LTE networks, 5G systems, etc.). It is understood that IoT gateway devices and IoT management devices can utilize cellular networks to provide data forwarding and management services to IoT devices within their communication service range.

[0062] Specifically, the communication between IoT devices (PINEs) can be divided into the following three ways.

[0063] Method 1: Direct communication.

[0064] For example, referring to FIG2A , IoT device 1 (PINE-1) and IoT device 2 (PINE-2) may exchange data via direct communication technologies such as WiFi technology and Bluetooth technology.

[0065] Method 2: Forward data through the IoT gateway device.

[0066] Exemplarily, as shown in FIG2B , PINE- 1 and PINE- 2 may be connected to the same PEGC via direct communication technologies such as WiFi technology and Bluetooth technology, and data transmission may be performed via the PEGC.

[0067] Method 3: forwarding data through the cellular network.

[0068] For example, as shown in Figure 2C, PINE-1 and PINE-2 can access the 5G system through the PEGC and connect to the User Plane Function (UPF) network element through the Radio Access Network (RAN) in the 5G system. When the Protocol Data Unit (PDU) session created by the PEGC for PINE-1 and PINE-2 is connected to the same UPF, data between PINE-1 and PINE-2 can be forwarded through the UPF. When the PDU session established by the PEGC for PINE is connected to different UPFs, data can be forwarded through the N19 interface between the UPFs. In addition, data can also be forwarded through the interface N6 between the UPF and the data network (DN).

[0069] That is, the communication paths between PINEs can be divided into a path for communication through a direct connection, a path for communication using a gateway device, and a path for communication through a cellular network.

[0070] It should be understood that while these three methods of inter-PINE communication exist, selecting the appropriate communication path for PINE data transmission remains unclear. Furthermore, current PIN signaling and data exchange primarily targets scenarios where PINEs are close together and located within the same geographic area (i.e., PINEs, PEGCs, and PEMCs can communicate directly). Signaling and data exchange between PINEs deployed in remote locations is less addressed.

[0071] For example, in scenarios such as smart agriculture and smart factories, PINEs are often deployed in different geographical areas and require cross-regional remote business interactions. Referring to Figure 3, a user may need to use a laptop computer (PINE-1) at home or in the office to request a camera (PINE-2) deployed on the farm to provide real-time monitoring video of crops, and use the monitoring video to determine whether to water, fertilize, spray pesticides, and other management measures on the crops. Among them, PINE-1 and PINE-2 belong to the same PIN but are located in different geographical areas. In this scenario, PINE-1 and PINE-2 deployed in different locations may not be able to communicate directly with each other, and cellular networks and multiple remotely deployed PEGCs are needed to provide signaling control and data interaction services for these remotely deployed PINEs. For remotely deployed PINEs, there is no clear explanation on how to ensure the reachability of the target PINE configured by the PEMC for the PINE requesting the service.

[0072] Based on this, an embodiment of the present application provides a path selection method, wherein a management device determines at least one candidate IoT device for a first IoT device; further, the management device can determine a candidate communication path between each candidate IoT device and the first IoT device based on the distance between each candidate IoT device in the at least one candidate IoT device and the first IoT device, and / or the association relationship between the gateway device associated with each candidate IoT device and the first IoT device, and / or whether each candidate IoT device and the first IoT device are within the service range of the IoT gateway device; wherein the candidate communication path is used for path selection. In other words, the management device can select a suitable communication path for business interaction between IoT devices based on at least one of the three items: the location of the IoT device, the association relationship between the IoT device and the IoT gateway device, and whether the IoT device is within the service range of the IoT network element. In this way, whether the IoT devices are in a scenario where they are close to each other or in a scenario where they are deployed in different locations, they can communicate through a suitable communication path, ensuring the normal transmission of the business.

[0073] It should be noted that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of the present application, the “protocol” may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0074] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0075] FIG4 is a flow chart of a path selection method according to an embodiment of the present application. As shown in FIG4 , the method includes the following contents.

[0076] Step 410: The management device determines at least one candidate IoT device for the first IoT device.

[0077] Step 420: The management device determines a candidate communication path between each candidate IoT device and the first IoT device based on at least one of the following:

[0078] The distance between each candidate IoT device and the first IoT device among at least one candidate IoT device, the distance and association relationship between the gateway device associated with each candidate IoT device and the first IoT device, and whether each candidate IoT device and the first IoT device are within the service range of the IoT gateway device;

[0079] The candidate communication paths are used for path selection.

[0080] In the embodiment of the present application, the management device may be an IoT device with management functions, such as a PEMC. The management device may also be a network element in the network, for example, the network element may be a network element dedicated to managing IoT devices, or a core network element in a cellular network, such as a Unified Data Management (UDM) network element or a Unified Data Repository (UDR) network element. The network element may also be an application network element provided by a third party. The embodiment of the present application does not limit the type of management device.

[0081] It should be noted that the management device can also be a PEMC and a network element, that is, the PEMC and the network element exist at the same time to jointly manage the various IoT devices and IoT gateway devices in the first PIN.

[0082] It should be understood that the management device can manage all currently connected IoT devices of the first PIN. Based on the actual needs of the first IoT device (for ease of understanding, PINE-1 will be used below to represent the first IoT device), the management device can determine at least one candidate IoT device that meets the actual needs of PINE-1 from among the multiple IoT devices it manages. The at least one candidate IoT device selected by the management device for the first IoT device can constitute a candidate PINE list, i.e., a candidate PINE list.

[0083] After obtaining the candidate PINE list, the management device may sequentially analyze and process at least one of the following: the distance between each candidate IoT device and PINE-1, the association relationship between the gateway device associated with each candidate IoT device and PINE-1, and whether each candidate IoT device and PINE-1 are within the service range of the IoT gateway device, to obtain a candidate communication path between each candidate IoT device and PINE-1.

[0084] Optionally, the candidate communication path may include at least one of the following:

[0085] a first communication path representing a path for communicating via a direct connection;

[0086] a second communication path representing a path for communication using the gateway device;

[0087] A third communication path represents a path for communicating using a cellular network.

[0088] The direct connection may be a WiFi connection, a Bluetooth connection, etc. The cellular network may be an LTE network, a 5G network, or a future communication network, etc., which is not limited in the embodiments of the present application.

[0089] In this way, after obtaining the candidate communication path of each candidate IoT device, the management device can select a suitable communication path for PINE-1 according to each candidate IoT device in the candidate PINE list and the candidate communication path of each candidate IoT device.

[0090] In summary, the management device can select an appropriate communication path for service interactions between IoT devices based on at least one of the following: the location of the IoT device, the relationship between the IoT device and the IoT gateway device, and whether the IoT device is within the service range of the IoT network element. This allows IoT devices to communicate via the appropriate communication path, ensuring normal service transmission, regardless of whether they are located close together or deployed remotely.

[0091] Optionally, the management device may store the IoT attribute information (also referred to as PIN attribute information) of the currently connected first PIN, and the IoT PIN attribute information may include relevant attribute information of all devices connected to the first PIN.

[0092] Optionally, the PIN attribute information includes at least one of the following: attribute information of each PINE in the first PIN, attribute information of each PEGC in the first PIN, and attribute information of a management device in the first PIN.

[0093] In addition, the PIN attribute information may also include identification information of the first PIN, such as a PIN ID.

[0094] Optionally, the attribute information of each PINE may include at least one of the following:

[0095] PINE identification information, such as PINE ID;

[0096] PINE's IP address information, such as PINE's IP address;

[0097] Identification information and / or IP address information of the PEGC associated with PINE;

[0098] Identification information and / or IP address information of other PINEs associated with PINE;

[0099] Business types supported by PINE;

[0100] Location information;

[0101] Valid time information; the valid time information is used to indicate the valid time in the first PIN;

[0102] Remaining power information;

[0103] Supported wireless access technologies;

[0104] The maximum communication distance corresponding to each of the above wireless access technologies;

[0105] Supported communication paths.

[0106] It should be understood that PINE can support one or more service types, such as positioning service, speed measurement service, health monitoring service, environmental monitoring service, etc.

[0107] Optionally, when the attribute information of a PINE includes the service types supported by the PINE, the attribute information of the PINE may also include identification information of PINEs that are permitted to use the service and / or identification information of PINEs that are prohibited from using the service. In other words, the attribute information of each PINE may include a whitelist and / or a blacklist, which can be used to inform specific devices whether to provide services and / or not to provide services to specific devices.

[0108] In embodiments of the present application, location information may indicate the geographic location of a PINE. For example, the location information may include GPS coordinates, street address information, cell identification information, tracking area identification information, and the like, although this embodiment of the present application is not limiting. It should be understood that the location information of a PINE can be used to determine the distance to other PINEs.

[0109] The validity time information may indicate the validity time of the PINE joining the first PIN. The validity time may be the time when the PINE joins the first PIN to provide services to other PINEs or obtain services provided by other PINEs. Exemplarily, the validity time information may be the remaining time of the PINE joining the first PIN.

[0110] The wireless access technologies supported by PINE may include one or more of WiFi technology, Bluetooth technology, and 3GPP access technology, which is not limited in the embodiments of the present application.

[0111] The communication paths supported by PINE may include at least one of a first communication path, a second communication path, and a third communication path, wherein the first communication path represents a path for communication via a direct connection, the second communication path represents a path for communication using a gateway device, and the third communication path represents a path for communication using a cellular network.

[0112] Optionally, the attribute information of each PEGC in the embodiment of the present application includes at least one of the following:

[0113] PEGC identification information, such as PEGC ID;

[0114] PEGC's IP address information;

[0115] Identification information and / or IP address information of PINE associated with PEGC;

[0116] Identification information of IoT devices that are allowed to be associated with the PEGC;

[0117] The identification information of IoT devices associated with the PEGC is prohibited;

[0118] Location information, such as GPS coordinates, street address, cell identification, tracking area identification, etc. The location information of a PEGC can be used to determine the distance between the PEGC and a PINE or other PEGCs;

[0119] Validity time information, which is used to indicate the validity period of the PEGC in the first PIN, that is, the time during which the PEGC joins the first PIN to provide services to other PINEs or obtain services provided by other PINEs. Exemplarily, the validity time information may be the remaining time of the PEGC joining the first PIN;

[0120] Remaining power information;

[0121] Supported wireless access technologies, such as one or more of WiFi, Bluetooth, and 3GPP access technologies;

[0122] The maximum communication distance corresponding to each wireless access technology in the wireless access technology.

[0123] Optionally, the attribute information of the management device includes at least one of the following:

[0124] IP address information of the management device;

[0125] Location information, such as GPS coordinates, street address, cell identification, tracking area identification, etc.;

[0126] Validity time information, which is used to indicate the validity period of the management device in the first PIN, that is, the time during which the management device joins the first PIN to provide services to other PINEs or obtain services provided by other PINEs. Exemplarily, the validity time information may be the remaining time of the management device joining the first PIN;

[0127] Supported wireless access technologies, such as one or more of WiFi, Bluetooth, and 3GPP access technologies;

[0128] The maximum communication distance corresponding to each wireless access technology in the wireless access technology.

[0129] Optionally, in step 410, the management device determines at least one candidate IoT device for the first IoT device, which can be implemented in the following manner:

[0130] The management device obtains the PIN attribute information and determines at least one candidate IoT device for PINE-1 based on the PIN attribute information.

[0131] That is, the management device can obtain and retrieve PIN attribute information, and select at least one candidate PINE that matches the actual needs of PINE-1 from multiple PINEs managed by the management device based on the attribute information of each PINE in the PIN attribute information and the attribute information of each PEGC.

[0132] In some embodiments, if the management device is a second network element for managing IoT devices, the IoT attribute information of all PINs can be stored in the second network element. When the management device needs to determine a communication path for the first IoT device, the management device can obtain the IoT attribute information of the currently connected first PIN from the local area, and determine a candidate IoT device for the first IoT device based on the IoT attribute information.

[0133] In other embodiments, if the management device is a PEMC, the management device can obtain the IoT attribute information of the currently connected first PIN from the local or second network element, and determine a candidate IoT device for the first IoT device based on the IoT attribute information.

[0134] In some other embodiments, if the management device is both a PEMC and a second network element, the PEMC of the management device can obtain the IoT attribute information of the currently connected first PIN from the second network element or from its own local area, and determine a candidate IoT device for the first IoT device based on the IoT attribute information.

[0135] Optionally, the actual requirement of PINE-1 may be notified to the management device by PINE-1 in advance through the first request information.

[0136] Optionally, in an embodiment of the present application, referring to FIG5 , the following steps may be performed before step 410:

[0137] Step 400: The management device receives first request information, where the first request information is used to request a first service required by PINE-1 and / or a communication path between PINE-1 and a PINE providing the first service.

[0138] That is, the management device may determine candidate PINEs and candidate communication paths for each candidate PINE according to the request of PINE-1, so as to select a suitable communication path for PINE-1 based on the candidate communication paths of the candidate PINEs.

[0139] It should be noted that the first request information may be service request information of PINE-1.

[0140] Optionally, the first request information may include at least one of the following:

[0141] Identification information of the first PIN, identification information of PINE-1, IP address information of PINE-1, identification information of PEGC-1, IP address information of PEGC-1, service type of the first service, demand information of the first service, access technology preferred by PINE-1, and communication path preferred by PINE-1.

[0142] The demand information of the first service may include information such as quality of service (QoS) requirements and requested service duration, which is not limited in this embodiment of the present application.

[0143] Optionally, the first request information may be sent directly from PINE-1 to the management device, or may be sent from a first IoT gateway device associated with PINE-1 (hereinafter, PEGC-1 is used to represent the first IoT gateway device for ease of understanding). In other words, the management device receives the first request information sent by PINE-1, or the management device receives the first request information sent by PEGC-1.

[0144] It should be understood that PINE-1 only has direct communication capabilities. When PINE-1 is within the direct communication service range of the management device, PINE-1 can directly send the first request message to the management device. When PINE-1 is outside the direct communication service range of the management device, if PINE-1 is associated with an IoT gateway device or there are IoT gateway devices nearby, PINE-1 can connect to a neighboring PEGC-1 and send the first request message to the management device via PEGC-1.

[0145] Optionally, in some embodiments, after PEGC-1 receives the first request information sent by PINE-1, PEGC-1 may determine at least one target PINE from at least one PINE associated with it; and then, based on the at least one target PINE, determine a second IoT device for providing the first service to PINE-1 (for ease of understanding, PINE-2 is used below to represent the second IoT device).

[0146] That is, after receiving the first request message from PINE-1, PEGC-1 can first query at least one of its associated PINEs to see if there is a PINE that meets the requirements of PINE-1 indicated in the first request message. PEGC-1 can use the service type, requirement information, whether the service is permitted for PINE-1, preferred access technology, and preferred communication path in the first request message as filtering criteria to query all associated PINEs. If at least one of PEGC-1's associated PINEs meets the filtering criteria, the PINE that meets the filtering criteria will be directly selected as the target PINE.

[0147] In some embodiments, PEGC-1 may not recommend PINE-1, but may send connection information of all target PINEs that meet the screening criteria to PINE-1 via the second response information.

[0148] In some embodiments, PEGC-1 can also directly select a recommended PINE-2 for PINE-1 and send PINE-2's connection information to PINE-1 via a second response message. Specifically, if PEGC-1 finds that there is only one target PINE that meets the screening criteria, it recommends that target PINE as PINE-2 to PINE-1. If there are multiple target PINEs that meet the screening criteria, PEGC-1 can select any target PINE from the multiple target PINEs, or select a target PINE that meets the second criteria, as the recommended PINE-2.

[0149] The second condition may include at least one of the following:

[0150] The remaining power is the largest, the remaining power is greater than the power threshold, the valid time is the longest, and the valid time is greater than the time threshold.

[0151] It should be understood that the second response information may include connection information of at least one target PINE or connection information of PINE-2.

[0152] In some embodiments, if the second response information includes the recommended PINE-2, PINE-1 may establish a communication connection with PINE-2 recommended in the first response information to exchange data.

[0153] In other embodiments, if the second response information includes multiple target PINEs, PINE-1 may arbitrarily select a target PINE from the multiple target PINEs as PINE-2, or select a target PINE that meets the second condition from the multiple target PINEs as PINE-2, and establish a communication connection with the PINE-2 for data exchange.

[0154] Optionally, the PINE-2 connection information may include at least one of the following:

[0155] PINE-2 identification information, PINE-2 IP address information, a target communication path for communication between PINE-1 and PINE-2, identification information and / or IP address information of PEGC-1 with which PINE-1 needs to be associated in the target communication path, and identification information and / or IP address information of PEGC-2 with which PINE-2 needs to be associated in the target communication path;

[0156] Optionally, the connection information of at least one target PINE includes at least one of the following:

[0157] Identification information and / or IP address information of each target PINE in at least one target PINE, access technologies supported by each target PINE, communication paths supported by each target PINE, identification information and / or IP address information of a PEGC to which each PINE in the communication paths supported by each target PINE needs to be associated, identification information and / or IP address information of a PEGC-1 to which PINE-1 in the communication paths supported by each target PINE needs to be associated.

[0158] Optionally, in some embodiments, if the target PINE does not exist in the at least one PINE associated with PEGC-1, PEGC-1 sends the first request information to the management device.

[0159] That is, after receiving the second request from PINE-1, PEGC-1 can first query at least one of its associated PINEs. If none of the associated PINEs meets PINE-1's requirements, PEGC-1 can send a first request to the management device, requesting the first service required by PINE-1 and / or a communication path between PINE-1 and a PINE providing the first service. This conserves network resources and improves path selection efficiency.

[0160] It should be noted that the first request information can be the same as the second request information mentioned above. That is, when PEGC-1 determines that there is no PINE that meets the requirements of PINE-1 among at least one PINE associated with it, it can directly forward the second request information of PINE-1 to the management device.

[0161] In other embodiments, after receiving the second request information sent by PINE-1, PEGC-1 may not perform any processing and directly forward the second request information as the first request information to the management device for the management device to select the IoT device and the path.

[0162] Furthermore, in an embodiment of the present application, after receiving the first request sent by PINE-1 or PEGC-1, the management device can use the service type, demand information, whether to allow the provision of service to PINE-1, preferred access technology, and preferred communication path in the first request information as screening conditions to select at least one candidate PINE for PINE-1 from the PIN attribute information.

[0163] In the embodiment of the present application, the management device can determine the candidate communication path between each candidate PINE and PINE-1 based on the distance between the candidate PINE and PINE-1, the association relationship between the PEGC associated with the candidate PINE and PINE-1, and whether the candidate PINE and PINE-1 are both within the service range of the PEGC.

[0164] Optionally, the management device may determine the candidate communication path between each candidate PINE and PINE-1 in the following manner:

[0165] In a case where the distance between the candidate PINE and PINE- 1 is less than a specified distance, the candidate communication paths may include a first communication path, the first communication path representing a path for communication through a direct connection;

[0166] In a case where the PEGC associated with the candidate PINE is the same as the PEGC associated with PINE-1, the candidate communication path may include a second communication path representing a path for communication using the PEGC;

[0167] In the case that both the candidate PINE and PINE-1 are within the PEGC service range, the candidate communication path may include a third communication path representing a path for communication using the cellular network.

[0168] The specified distance may be the maximum distance required for direct communication between PINE devices. In other words, if the distance between the candidate PINE and PINE-1 is less than the maximum distance required for direct communication, i.e., the two PINEs are geographically close enough, then service transmission between the candidate PINE and PINE-1 via the first communication path is possible.

[0169] If the candidate PINE and PINE-1 have a common associated PEGC, traffic can be transmitted between the candidate PINE and PINE-1 via the second communication path.

[0170] In addition, the service range of a PEGC may refer to the communication service range of the PEGC. That is, if the candidate PINE and PINE-1 do not have a common associated PEGC, but the candidate PINE and PINE-1 are both located around different PEGCs (for example, the distance between the candidate PINE and its nearest PEGC, and the distance between PINE-1 and its nearest PEGC are both less than a specified distance, i.e., the maximum distance for direct communication between PINE devices), and direct communication with nearby PEGCs is possible, in this case, service transmission between the candidate PINE and PINE-1 can be performed via the third communication path.

[0171] Optionally, after determining the candidate communication between each candidate PINE and PINE-1, referring to FIG5 , the path selection method provided in the embodiment of the present application may further include the following steps:

[0172] Step 430: The management device selects a candidate PINE that meets a first condition from at least one candidate PINE based on the candidate communication path between each candidate PINE and PINE-1, to obtain at least one target PINE.

[0173] The first condition may include at least one of the following:

[0174] The candidate communication paths include the communication path preferred by PINE-1, the candidate communication paths include the communication path with the highest priority, and the candidate communication paths include the default communication path.

[0175] It should be understood that the management device may select a candidate PINE including the preferred communication path specified by PINE-1 in the first request information as the target PINE for PINE-1.

[0176] In addition, the management device may also select, according to the priority order of the communication paths, a candidate PINE including a communication path with the highest priority among the candidate communication paths as the target PINE for PINE-1.

[0177] For example, if PINE-1 specifies a preferred communication path in the first request information, the management device may select a candidate PINE that supports the preferred communication path as the target PINE for PINE-1. If PINE-1 does not specify a preferred communication path, the management device may select a candidate PINE that includes the communication path with the highest priority among the candidate communication paths as the target PINE for PINE-1, based on the priority order of the communication paths.

[0178] Optionally, the priority order of the communication paths can be sorted according to the network resources occupied by the communication paths. For example, if the first communication path occupies the least network resources, the first communication path can be set to the highest priority; if the second communication path occupies a moderate amount of network resources, the second communication path can be set to a medium priority; and if the third communication path occupies the most network resources, the third communication path can be set to the lowest priority.

[0179] In addition, the management device may also select, based on a pre-specified default communication path, a candidate PINE that includes the default communication path as the target PINE for PINE-1. Here, the default communication path may be a pre-specified direct communication path, a path for communication via an IoT gateway device, or a path for communication via a cellular network, and this embodiment of the application is not limited thereto.

[0180] It should be noted that if the number of candidate IoT devices determined by the management device includes only one, and the candidate communication path for the candidate IoT device also includes only one, the management device can directly recommend the candidate IoT device as PINE-2 and instruct PINE-1 to establish a communication connection with PINE-1 through the candidate communication path.

[0181] In some embodiments, the management device may not recommend PINE-2 to PINE-1, but may directly send the connection information of all determined target PINEs to PINE-1 through the first response information.

[0182] In some embodiments, the management device may also make a recommendation for PINE-1, determine a target PINE from at least one target PINE as the recommended PINE-2, and send the connection information of the recommended PINE-2 to PINE-1 via the first response information.

[0183] Optionally, referring to FIG5 , based on step 430, the path selection method may further include the following steps:

[0184] Step 440: The management device determines, based on at least one target IoT device, PINE-2 for providing the first service to PINE-1.

[0185] In this embodiment of the present application, when the number of at least one target PINE is one, the target PINE can be used as the recommended PINE-2 to provide the first service to PINE-1. When the number of at least one target PINE is multiple, a PINE can be randomly selected from the multiple target PINEs, or the best PINE can be selected as the recommended PINE-2 to provide the first service to PINE-1.

[0186] Optionally, if the number of at least one target IoT device includes multiple devices, the management device may further perform the following steps:

[0187] The management device selects a target PINE that meets a second condition from the multiple target PINEs to obtain PINE-2, where the second condition includes at least one of the following:

[0188] The remaining power is the largest, the remaining power is greater than the power threshold, the valid time is the longest, and the valid time is greater than the time threshold.

[0189] Among them, the power threshold and / or time threshold can be determined according to protocol pre-definition, pre-configuration information or network configuration information, and the embodiments of the present application do not limit this.

[0190] Optionally, the power threshold and / or time threshold may be carried in the first request information.

[0191] Optionally, in an embodiment of the present application, referring to FIG5 , the following steps may be performed after step 440:

[0192] Step 450: The management device sends a first response message, where the first response message is used to indicate the connection information of at least one target PINE, or the connection information of PINE-2.

[0193] That is, after selecting at least one target PINE or PINE-2, the management device may inform PINE-1 of the relevant connection information of the at least one PINE or PINE-2 through the first response information.

[0194] It should be understood that if the first request information is sent by PINE-1, the management device sends the first response information to PINE-1. If the first request information is sent by PEGC-1, the management device sends the first response information to PEGC-1.

[0195] In this embodiment of the present application, after PEGC-1 receives the first response information, it can send a second response information to PINE-1 based on the first response information. It should be noted that the second response information can be the same as the first response information, that is, PEGC-1 forwards the first response information to PINE-1.

[0196] Optionally, the PINE-2 connection information includes at least one of the following:

[0197] PINE-2 identification information, PINE-2 IP address information, a target communication path for communication between PINE-1 and PINE-2, identification information and / or IP address information of PEGC-1 with which PINE-1 needs to be associated in the target communication path, and identification information and / or IP address information of PEGC-2 with which PINE-2 needs to be associated in the target communication path;

[0198] Optionally, the connection information of at least one target PINE includes at least one of the following:

[0199] Identification information and / or IP address information of each target PINE in at least one target PINE, access technologies supported by each target PINE, communication paths supported by each target PINE, identification information and / or IP address information of a PEGC that each target PINE needs to be associated with in the communication paths supported by each target PINE, and identification information and / or IP address information of a PEGC that PINE-1 needs to be associated with in the communication paths supported by each target PINE.

[0200] It should be understood that, in the case where the first response information includes the connection information of PINE-2, if the first response information indicates that the target communication path is the first communication path, PINE-1 can establish direct communication with PINE-2 via direct communication technologies such as WiFi and Bluetooth. In this case, the connection information of PINE-2 may not include the identification information and / or IP address information of PEGC-1 that PINE-1 needs to associate with, and the identification information and / or IP address information of PEGC-2 that PINE-2 needs to associate with.

[0201] If the target communication path indicated in the first response information is the second communication path, PINE-1 can establish a communication connection with PINE-2 through PEGC-1 to exchange data. In this case, the PEGC-1 to which PINE-1 needs to associate and the PEGC-2 to which PINE-2 needs to associate can be the same IoT gateway device.

[0202] It should be noted that the PEGC-1 that PINE-1 needs to associate with may be a PEGC that PINE-1 has already associated with or is not associated with, and this embodiment of the application does not limit this.

[0203] If the target communication path indicated in the first response information is the third communication path, PINE-1 can be associated with PEGC-1 based on the identification information and / or IP address information of PEGC-1 carried in the first response information, and PINE-1 and PINE-2 communicate through a cellular network (e.g., a 5G system).

[0204] That is, in some embodiments, if the first response information includes the recommended PINE-2, PINE-1 may establish a communication connection with PINE-2 recommended in the first response information to perform data exchange.

[0205] In other embodiments, when the first response information includes connection information of at least one target PINE, PINE-1 may select a target PINE from the at least one target PINE as PINE-2. Alternatively, PINE-1 may select a target PINE from the at least one target PINE that satisfies a second condition to obtain PINE2, where the second condition includes at least one of the following:

[0206] The remaining power is the largest, the remaining power is greater than the power threshold, the valid time is the longest, and the valid time is greater than the time threshold.

[0207] Among them, the power threshold and / or time threshold can be determined according to protocol pre-definition, pre-configuration information or network configuration information, and the embodiments of the present application do not limit this.

[0208] Optionally, the power threshold and / or time threshold may be carried in the first request information.

[0209] Furthermore, after selecting PINE-2, PINE-1 may establish a communication connection with PINE-2 according to a communication path supported by PINE-2.

[0210] Optionally, after the communication connection between PINE-1 and PINE-2 is successfully established, PINE-1 and PINE-2 can report their association with PEGC-1 and PEGC-2, the selected communication path and access technology to the management device, so that the management device can update the PIN attribute information.

[0211] The following describes in detail the process of configuring the management device for PINE-1 to communicate with PINE-2 via the third communication path (ie, the cellular network).

[0212] It should be understood that the following embodiments primarily focus on the scenario where PINE-1 negotiates with the management device and chooses to communicate with PINE-2 via the third communication path. The negotiation process between PINE-1 and the management device is described in detail in the above embodiments and will not be repeated here for the sake of brevity.

[0213] Optionally, referring to FIG6 , the path selection method provided in the embodiment of the present application may include the following steps:

[0214] Step 601: PINE-1 establishes communication with PEGC-1.

[0215] It should be understood that PINE-1 negotiates with the management device to determine a cellular network path for communication with PINE-2. During the negotiation process, PINE-1 can obtain the identification information and / or IP address of PEGC-1 with which it needs to associate, the identification information and / or IP address of PINE-2, and the identification information and / or IP address of PEGC-2 with which PINE-2 needs to associate.

[0216] After PINE-1 determines that it will communicate with PINE-2 via a cellular network path, PINE-1 can trigger the path configuration process. First, PINE-1 can associate with PEGC-1 based on its identification information and / or IP address information carried in the first response message, so as to leverage PEGC-1's ability to access the cellular network to exchange data with PINE-2.

[0217] It should be noted that if PINE-1 has been associated with PEGC-1 during the negotiation process, step 601 may not be performed.

[0218] Step 602: PINE-1 sends third indication information to PEGC-1. The third indication information may be used to indicate at least one of the following:

[0219] The identification information and / or IP address information of PINE-2, and the communication between PINE-1 and PINE-2 via a third communication path; the third communication path represents a path for communication using a cellular network, and the identification information and / or IP address information of PEGC-2 associated with PINE-2 in the third communication path.

[0220] In an embodiment of the present application, after PINE-1 determines to communicate with PINE-2 using a path of a cellular network, the determined third communication path and relevant information of PINE-2 (e.g., identification information and / or IP address information of PINE-2, and identification information and / or IP address information of PEGC-2 with which PINE-2 needs to be associated) can be notified to PEGC-1 associated with PINE-1 through third indication information.

[0221] Among them, the relevant information of PINE-2 can be determined through the first response information.

[0222] In some embodiments, if during the above negotiation process, PINE-1 is not associated with PEGC-1, or PINE-1 is associated with PEGC-1 but PEGC-1 has not established a PDU session for PINE-1, the third indication information may also instruct PEGC-1 to establish or modify a Protocol Data Unit (PDU) session for PINE-1.

[0223] In other embodiments, if PINE-1 and PEGC-1 have established an association relationship, and PEGC-1 has established a PDU session for PINE-1, and PEGC-2 has established a PDU session for PINE-2, the third indication information may also instruct PEGC-1 to modify the data transmission rules of the PDU session for PINE-1, such as packet detection rules and / or data forwarding behavior rules.

[0224] Step 603a: If PEGC-1 has not established a PDU session for PINE-1, PEGC-1 establishes or modifies a PDU session for PINE-1.

[0225] Step 603b: When PEGC-1 has established a PDU session for PINE-1, PEGC-1 modifies the data transmission rule corresponding to the PDU session.

[0226] The PDU session is used to transmit service data between PINE-1 and PINE-2, and to configure IP address information of PINE-1 and / or PEGC-1.

[0227] It should be understood that after receiving the third indication information, PEGC-1 may perform the above step 603a or step 603b according to the situation of the PDU session established for PINE-1.

[0228] Specifically, if PEGC-1 has not established a PDU session for PINE-1 before PINE-1 requests a service, then after receiving the third indication information, PEGC-1 may establish a PDU session for PINE-1 to transmit service data between PINE-1 and PINE-2. Furthermore, after the PDU session is established, PEGC-1 obtains IP address information of PINE-1 and / or PEGC-1 from a User Plane Function (UPF) network element.

[0229] In addition, if PEGC-1 has established a PDU session for PINE-1 before PINE-1 requests the service, and PEGC-2 has also established a PDU session for PINE-2, then after PEGC-1 receives the third indication information, PEGC-1 can initiate a PDU session modification process for PINE-1 to update the packet detection rules and / or forwarding behavior rules in the N4 rule.

[0230] It should be noted that in step 603b, PEGC-1 may update the packet detection rules and / or forwarding behavior rules in the above-mentioned N4 rule based on one or more of PINE-1's ID and IP address, PINE-2's ID and IP address, and PEGC-2's ID and IP address. Alternatively, PEGC-1 may update the packet detection rules and / or forwarding behavior rules in the above-mentioned N4 rule based on the third indication information, which is not limited in this embodiment of the present application. The ID and IP address of PINE-2, and the ID and IP address of PEGC-2 may be determined during the negotiation process corresponding to FIG. 5 .

[0231] Step 604: PINE-1 / PEGC-1 sends first instruction information to the management device. The first instruction information is used to instruct PINE-1 to communicate with PINE-2 via a third communication path. The third communication path represents a path for communication using a cellular network.

[0232] It should be understood that after the PDU session is established / modified, PINE-1 / PEGC-1 may indicate to the management device through the first indication information that PINE-1 will perform data exchange with PINE-2 through the third communication path.

[0233] Optionally, the first indication information includes at least one of the following:

[0234] PINE-1 identification information, PINE-1 IP address information, PEGC-1 identification information, PEGC-1 IP address information, PINE-2 identification information, PINE-2 IP address information, PEGC-2 identification information, PEGC-2 IP address information, association indication information, path indication information.

[0235] The association indication information is used to indicate that PINE-1 is associated with PEGC-1, and / or that PINE-2 is associated with PINE-2. The path indication information is used for PINE-1 and PINE-2 to communicate through a third communication path.

[0236] Step 605: The management device sends second instruction information to PINE-2, where the second instruction information is used to instruct PINE-2 to communicate with PINE-1 through the third communication path.

[0237] It should be understood that after receiving the first indication information, the management device may send second indication information to PINE-2 to inform PINE-2 to perform data exchange with PINE-1 through the third communication path.

[0238] Optionally, if PINE-2 is within the direct communication service range of the management device, the management device may directly send the second indication information to PINE-2. If PINE-2 is outside the direct communication service range of the management device, the management device may forward the second request information via PEGC-2 associated with PINE-2. This embodiment of the present application does not limit the manner in which the second indication information is sent.

[0239] Optionally, the second indication information includes at least one of the following:

[0240] PINE-1 identification information, PINE-1 IP address information, PEGC-1 identification information, PEGC-1 IP address information, PINE-2 identification information, PINE-2 IP address information, PEGC-2 identification information, PEGC-2 IP address information, association indication information, path indication information.

[0241] The association indication information is used to indicate that PINE-1 is associated with PEGC-1, and / or that PINE-2 is associated with PINE-2; and the path indication information is used for PINE-1 and PINE-2 to communicate through a third communication path.

[0242] It should be noted that the second indication information may also be referred to as path configuration information, which is used to configure the communication path between PINE-2 and PINE-1.

[0243] Step 606: PINE-2 establishes communication with PEGC-2.

[0244] In an embodiment of the present application, after receiving the second indication information, PINE-2 can be associated with PEGC-2 according to the identification information of PEGC-2 and / or the IP address information of PEGC-2 indicated in the second indication information, so as to utilize the ability of PEGC-2 to access the cellular network to interact with PINE-1 for data.

[0245] It should be noted that if PINE-2 has already established a communication connection with PEGC-2, step 606 may not be performed.

[0246] Step 607: PINE-2 sends a second request message to PEGC-2. The second request message is used to request the establishment or modification of a PDU session, or to request the modification of a data transmission rule corresponding to the PDU session. The PDU session is used to transmit service data between PINE-1 and PINE-2, and to configure the IP address information of PINE-2 and / or PEGC-2.

[0247] In an embodiment of the present application, PINE-2 may request PEGC-2 to establish or modify a PDU session for it through a second request message, or request PEGC-2 to modify data transmission rules in a PDU session for it through a second request message.

[0248] Optionally, the data transmission rule may include a packet detection rule and / or a forwarding behavior rule.

[0249] Step 608a: If PEGC-2 has not established a PDU session for PINE-2, the PEGC-2 establishes or modifies a PDU session for PINE-2.

[0250] Step 608b: When PEGC-1 has established a PUD session for PINE-1 and PEGC-2 has established a PDU session for PINE-2, PEGC-2 modifies the data transmission rule corresponding to the PDU session.

[0251] It should be understood that after receiving the second request information, PEGC-2 may perform the above step 608a or step 608b according to the situation of the PDU session established for PINE-2.

[0252] Specifically, in step 608a, if PEGC-2 has not established a PDU session for PINE-2 before PINE-2 sends the second request message, then after receiving the second request message, PEGC-2 may establish a PDU session for PINE-2 to transmit service data between PINE-2 and PINE-1. Furthermore, after the PDU session is established, PEGC-2 obtains IP address information of PINE-2 and / or PEGC-2 from the User Plane Function (UPF) network element.

[0253] In addition, in step 608b, if PEGC-1 has established a PUD session for PINE-1 before PINE-1 requests the service, and PEGC-2 has established a PDU session for PINE-2, then after PEGC-2 receives the second request information, PEGC-2 can initiate a PDU session modification process for PINE-2 to update the packet detection rules and / or forwarding behavior rules in the N4 rule.

[0254] It should be noted that in step 608b, PEGC-2 may update the packet detection rules and / or forwarding behavior rules in the above-mentioned N4 rule based on one or more of PINE-1's ID and IP address, PEGC-1's ID and IP address, and PINE-2's ID and IP address; or PEGC-2 may update the packet detection rules and / or forwarding behavior rules in the above-mentioned N4 rule based on the second indication information, which is not limited in this embodiment of the present application. The ID and IP address of PINE-1, and the ID and IP address of PEGC-1 may be determined during the negotiation process corresponding to FIG. 5 .

[0255] In this embodiment of the present application, step 603a may correspond to step 608a, and step 603b may correspond to step 608b. That is, in one process of configuring the third communication path, steps 603a and 608a may be performed. In another process of configuring the third communication path, steps 603b and 608b may be performed.

[0256] Optionally, after PEGC-2 establishes / modifies a PDU session for PINE-2, or modifies the data transmission rules corresponding to the PDU session corresponding to PINE-2, PINE-2 / PEGC-2 can report its association relationship, PINE-2's identification information and / or IP address information, PEGC-2's identification information and / or IP address information, and path indication information indicating that PINE-1 and PINE-2 transmit through a third communication path to the management device.

[0257] Optionally, in an embodiment of the present application, when PEGC-1 and / or PEGC-2 do not establish a PDU session for PINE-1 and PINE-2, the path selection method provided in the embodiment of the present application may further include the following steps:

[0258] Step 609: The management device sends a data forwarding policy configuration request to the first network element of the cellular network. The data forwarding policy configuration request is used to request configuration of data transmission rules between PINE-1 and PINE-2.

[0259] That is to say, when PEGC-1 and / or PEGC-2 do not establish a PDU session for PINE-1 and PINE-2, after the management device determines that data transmission between PINE-1 and PINE-2 needs to be carried out through the path of the cellular network, it can request the first network element in the cellular network to configure a data forwarding policy.

[0260] Optionally, the first network element may be a control plane network element for managing PDU sessions in a cellular network. Exemplarily, the first network element may be a session management function (SMF) network element in a 5G system.

[0261] Optionally, the data forwarding policy configuration request may include at least one of the following:

[0262] Identification information and / or IP address information of PINE-1, identification information and / or IP address information of PEGC-1, identification information and / or IP address information of PINE-2, identification information and / or IP address information of PEGC-2, and path indication information, wherein the path indication information indicates that PINE-1 and PINE-2 communicate through a third communication path.

[0263] In some embodiments, when the management device is a PEMC, the management device sending the data forwarding policy configuration request to the first network element of the cellular network in step 609 may be implemented in any one of the following ways:

[0264] The PEMC forwards the data forwarding policy configuration request to the first network element through the second network element;

[0265] The PEMC sends a data forwarding policy configuration request to the first network element through the second network element and the Policy Control Function (PCF) network element;

[0266] The PEMC forwards the data forwarding policy configuration request to the first network element through the second network element and the Network Exposure Function (NEF) network element;

[0267] The PEMC sends a data forwarding policy configuration request to the first network element through the second network element, the NEF, and the PCF.

[0268] In an embodiment of the present application, the second network element can be a core network element in a cellular network, such as a UDM network element or a UDR network element, or a network element dedicated to managing IoT devices, or an application network element provided by a third party.

[0269] In one possible implementation, if the first network element is an SMF network element and the second network element is a trusted network element within the core network of the cellular network, as shown in FIG7A , after PEGC-1 establishes / modifies a PDU session for PINE-1, and PEGC-2 establishes / modifies a PDU session for PINE-2, the PEMC can send a policy configuration request to the second network element, and the second network element directly sends the data forwarding policy configuration request to the first network element. In this way, after receiving the forwarding policy configuration request, the first network element can configure data forwarding policies for UPF-1 corresponding to PEGC-1 and UPF-2 corresponding to PEGC-2 based on locally pre-configured policies, such as configuring packet detection rules and / or forwarding behavior rules.

[0270] In another possible implementation, if the first network element is an SMF network element and the second network element is a trusted network element within the core network of the cellular network, as shown in FIG7B , after PEGC-1 establishes / modifies a PDU session for PINE-1, and PEGC-2 establishes / modifies a PDU session for PINE-2, the PEMC may send a policy configuration request to the second network element. Subsequently, the second network element sends the data forwarding policy configuration request to the PCF network element, which in turn sends the policy configuration request to the first network element. Furthermore, after receiving the forwarding policy configuration request, the first network element may configure data forwarding policies for UPF-1 corresponding to PEGC-1 and UPF-2 corresponding to PEGC-2 based on locally pre-configured policies, such as configuring packet detection rules and / or forwarding behavior rules.

[0271] In another possible implementation, if the first network element is an SMF network element and the second network element is a third-party application network element outside the core network, as shown in FIG7C , after PEGC-1 establishes / modifies a PDU session for PINE-1, and PEGC-2 establishes / modifies a PDU session for PINE-2, the PEMC may send a policy configuration request to the second network element. Subsequently, the second network element sends a data forwarding policy configuration request to the NEF, and the NEF sends the received data forwarding policy configuration request to the first network element. In this way, after receiving the forwarding policy configuration request, the first network element may configure a data forwarding policy for the UPF-1 corresponding to PEGC-1 and the UPF-2 corresponding to PEGC-2 based on the locally pre-configured policy, such as configuring packet detection rules and / or forwarding behavior rules.

[0272] In one possible implementation, if the first network element is an SMF network element and the second network element is a third-party application network element outside the core network, as shown in FIG7D , after PEGC-1 establishes / modifies a PDU session for PINE-1, and PEGC-2 establishes / modifies a PDU session for PINE-2, the PEMC may send a policy configuration request to the second network element. Subsequently, the second network element sends a data forwarding policy configuration request to the NEF. The NEF sends the received data forwarding policy configuration request to the PCF network element, and the PCF network element sends the received data forwarding policy configuration request to the first network element. In this way, after receiving the forwarding policy configuration request, the first network element may configure data forwarding policies for the UPF-1 corresponding to PEGC-1 and the UPF-2 corresponding to PEGC-2 based on the locally pre-configured policies, such as configuring packet detection rules and / or forwarding behavior rules.

[0273] It should be understood that UPF-1 and UPF-2 in the above four implementations can be the same network element or two different network elements, and this is not limited in the embodiments of the present application. In addition, packet detection rules are used to filter out data packets that need to be forwarded, and forwarding behavior rules are used to indicate whether data packets should be buffered, discarded, or forwarded, how to encapsulate / decapsulate data packets, and the forwarding destination.

[0274] In other embodiments, when the management device is the second network element, the management device sending the data forwarding policy configuration request to the first network element of the cellular network in step 609 may be implemented in any one of the following ways:

[0275] The second network element sends a data forwarding policy configuration request to the first network element;

[0276] The second network element sends a data forwarding policy configuration request to the first network element through the PCF;

[0277] The second network element forwards the data forwarding policy configuration request to the first network element through the NEF;

[0278] The second network element sends a data forwarding policy configuration request to the first network element through the NEF and the PCF.

[0279] In the embodiment of the present application, the management device may be a network element in the network, and may directly manage the IoT devices in the PIN.

[0280] In this scenario, if the second network element is a trusted network element within the core network, the second network element can directly send a data forwarding policy configuration request to the first network element. If the second network element is a trusted network element within the core network, the second network element can also send a data forwarding policy configuration request to the PCF, which will then send the data forwarding policy configuration request to the first network element. If the second network element is an untrusted network element within the core network, the second network element can send a data forwarding policy configuration request to the NEF, which will then send the data forwarding policy configuration request to the first network element. If the second network element is an untrusted network element within the core network, the second network element can also send a data forwarding policy configuration request to the NEF, which will then send the data forwarding policy configuration request to the PCF, which will then send the received data forwarding policy configuration request to the first network element. In this way, after receiving the forwarding policy configuration request, the first network element can configure data forwarding policies for UPF-1 corresponding to PEGC-1 and UPF-2 corresponding to PEGC-2 based on locally pre-configured policies, such as configuring packet detection rules and / or forwarding behavior rules.

[0281] In some embodiments, when the management device is a PEMC and a second network element, that is, the PEMC and the second network element both exist, the data forwarding policy configuration request can be transmitted in the manner of Figures 7A-7D. For the sake of brevity, no further details are given here.

[0282] In summary, in the embodiment of the present application, the management device can not only allocate PINE-2 that meets the service needs of PINE-1 that initiates the service request, but also ensure the reachability between PINE-1 and PINE-2. When PINE-1 and PINE-2 are unreachable, the management device can configure the associated PEGC-1 for PINE-1 to access the cellular network, and configure the associated PEGC-2 for PINE-2 to access the cellular network. In addition, when multiple PINE devices communicate through the cellular network, the management device can also configure the corresponding data forwarding strategy for the PINE in the core network. The path selection method provided in the embodiment of the present application can provide certain guidelines for the PINE requesting the service to select the target PINE, ensure the reachability between PINEs deployed in different locations, and ensure that the data between PINEs deployed in different locations can be forwarded through the cellular network through the data forwarding strategy configuration scheme.

[0283] The path selection method provided in the embodiment of the present application is described in detail below in conjunction with specific application scenarios.

[0284] In a smart agriculture application scenario, as shown in Figure 3, a user uses a smartphone (PINE-1) at home or in the office to request real-time crop monitoring video from a camera (PINE-2) deployed on the farm. Based on the video, the user determines whether to water, fertilize, or spray the crops, among other management measures. It should be noted that other IoT devices can also be deployed on the farm, such as sensors for collecting environmental information such as farm temperature and / or humidity, or equipment for watering, fertilizing, or spraying crops. In this application scenario, PINE-1 and PINE-2 belong to the same PIN and are managed by the PEMC. PINE-1 and PINE-2 are located in different geographic regions. Furthermore, attribute information for PINE-1, PINE-2, PEGC-1, PEGC-2, and the PEMC can be pre-stored in the PEMC.

[0285] Example 1

[0286] Based on the application scenario shown in Figure 3, PINE-1 is within the service range of PEMC, and PINE-1 can directly initiate a service request to PEMC. Referring to Figure 8, the path selection method provided in the embodiment of the present application may include the following steps:

[0287] Step 1: PINE-1 sends a service request message (that is, the first request message mentioned above) to PEMC.

[0288] The service request information may include at least one of the following: PIN ID, PINE-1 ID, PINE-1 IP address, PEGC-1 ID, PEGC-1 IP address, service type of the requested service, demand information of the requested service, preferred access technology, and preferred communication path.

[0289] It should be noted that if PINE-1 has an associated PEGC, the service request information may include PEGC-1 ID and / or PEGC-1 IP address information; otherwise, the service request information may not carry these two pieces of information.

[0290] Step 2: The PEMC retrieves PIN attribute information (that is, the IoT attribute information mentioned above) from the PEMC local or second network element to determine the target PINE and / or PINE-2.

[0291] Specifically, after receiving the service request information, PEMC can use the PINE-1 ID, service type, demand information, preferred access technology, preferred communication path, etc. in the service request information as screening conditions to select a candidate PINE list for PINE-1 from the PIN attribute information stored locally by PEMC or the second network element.

[0292] In this embodiment of the present application, the PEMC can determine the candidate communication path between each candidate PINE and PINE-1 based on the geographical distance between the candidate PINE and PINE-1, the geographical distance between the PEGC associated with the candidate PINE and PINE-1, and whether the candidate PINE and PINE-1 have the same associated PEGC. Specifically, the candidate communication path determination criteria are as follows:

[0293] In a case where the distance between the candidate PINE and PINE-1 is less than a specified distance (e.g., a maximum distance for direct communication between PINE devices), the candidate communication path may include a first communication path, the first communication path representing a path for communication via a direct connection;

[0294] In a case where the PEGC associated with the candidate PINE is the same as the PEGC associated with PINE-1, the candidate communication path may include a second communication path representing a path for communication using the gateway device;

[0295] When both the candidate PINE and PINE-1 are within the PEGC service range (i.e., the distance between the candidate PINE and its nearest PEGC, and the distance between PINE-1 and its nearest PEGC are both less than the maximum distance for direct communication), the candidate communication path may include a third communication path representing a path for communication using a cellular network.

[0296] Furthermore, if PINE-1 specifies a preferred communication path in its service request, the PEMC selects a candidate PINE that includes its preferred communication path as the target PINE for PINE-1. If PINE-1 does not specify a preferred communication path, the PEMC selects a target PINE based on the priority of the first communication path, the second communication path, and the third communication path (i.e., in descending order of network resource occupancy). If multiple target PINEs exist, the target PINE with the longest active time and the highest remaining battery power can be selected as the recommended PINE-2.

[0297] Step 3: PEMC sends service response information (that is, the first response information mentioned above) to PINE-1.

[0298] The service response information may include at least one of the following:

[0299] PINE-2 ID, PINE-2 IP address information, target communication path for communication between PINE-1 and PINE-2, identification information and / or IP address information of PEGC-1 with which PINE-1 needs to be associated in the target communication path, identification information and / or IP address information of PEGC-2 with which PINE-2 needs to be associated in the target communication path, identification information and / or IP address information of each target PINE in at least one target PINE, access technology supported by each target PINE, communication paths supported by each target PINE, identification information and / or IP address information of the PEGC with which each target PINE needs to be associated in the communication paths supported by each target PINE, and identification information and / or IP address information of the PEGC with which PINE-1 needs to be associated in the communication paths supported by each target PINE.

[0300] Among them, the recommended PINE-2 can be selected from at least one target PINE.

[0301] Step 4a: If the service response information received by PIEN-1 includes the PINE-2 ID and the direct communication indication, PINE-1 can establish a communication connection with PINE-2 via a direct communication technology such as WiFi or Bluetooth to exchange data.

[0302] Step 4b: If the service response information received by PINE-1 includes the PINE-2 ID, the PEGC-1 ID, and an instruction to communicate via PEGC, PINE-1 can establish a communication connection with PINE-2 via PEGC-1 to exchange data.

[0303] Step 4c: If the service request response message received by PINE-1 includes the PINE-2 ID and its associated PEGC-2 ID, PEGC-1 ID, and an indication of communication via the 5G system, PINE-1 can be associated with PEGC-1, and the two can communicate via the 5G system.

[0304] It should be noted that, when the service response information received by PINE-1 includes the connection information of the target PINE, PINE-1 can select a target PINE as PINE-2 and execute the corresponding steps above according to the determined communication path.

[0305] Step 5: After the communication connection between PINE-1 and PINE-2 is successfully established, PINE-1 and PINE-2 report their association with PEGC-1 and PEGC-2, the selected communication path, and the access technology to the PEMC and / or the second network element for updating the stored PIN attribute information.

[0306] Example 2

[0307] Based on the application scenario shown in Figure 3, PINE-1 can initiate a service request to its associated PEGC-1. Referring to Figure 9, the path selection method provided in the embodiment of the present application may include the following steps:

[0308] Step 1: PINE-1 sends a service request message (that is, the first request message mentioned above) to PEGC-1.

[0309] The service request information may include at least one of the following: PIN ID, PINE-1 ID, PINE-1 IP address, service type of the requested service, requirement information of the requested service, preferred access technology, and preferred communication path.

[0310] After receiving the service request information, PEGC-1 can query all PINEs associated with it. If there is a candidate PINE that meets the screening conditions specified by PINE-1 in the service request information, steps 2 to 4 are skipped and the candidate PINE is used as the target PINE.

[0311] If there is no candidate PINE that meets the screening conditions specified in PINE-1 in the service request information, continue to perform the following steps.

[0312] Step 2: PEGC-1 forwards the service request information to PEMC.

[0313] It should be noted that, in addition to the information included in the service request information in step 1, the service request information may also carry PEGC-1 ID and / or PEGC-1 IP address information.

[0314] Step 3: The PEMC retrieves the PIN attribute information (that is, the IoT attribute information mentioned above) from the PEMC local or second network element to determine the target PIN and / or PINE-2.

[0315] This step 3 is the same as step 2 in Example 1 and will not be repeated here for the sake of brevity.

[0316] Step 4: PEMC sends service response information (that is, the first response information mentioned above) to PEGC-1.

[0317] The service response information may include at least one of the following:

[0318] PINE-2 ID, PINE-2 IP address information, target communication path for communication between PINE-1 and PINE-2, identification information and / or IP address information of PEGC-1 with which PINE-1 needs to be associated in the target communication path, identification information and / or IP address information of PEGC-2 with which PINE-2 needs to be associated in the target communication path, identification information and / or IP address information of each target PINE in at least one target PINE, access technology supported by each target PINE, communication paths supported by each target PINE, identification information and / or IP address information of the PEGC with which each target PINE needs to be associated in the communication paths supported by each target PINE, and identification information and / or IP address information of the PEGC with which PINE-1 needs to be associated in the communication paths supported by each target PINE.

[0319] Step 5: PEGC-1 sends service response information (that is, the first response information mentioned above) to PINE-1.

[0320] The service response information in step 5 is similar to the service response information in step 4, and will not be described again for the sake of brevity.

[0321] Step 6a: If the service response information received by PIEN-1 includes the PINE-2 ID and the direct communication indication, PINE-1 and PINE-2 can establish a communication connection through a direct communication technology such as WiFi and Bluetooth to exchange data.

[0322] Step 6b: If the service response information received by PINE-1 includes the PINE-2 ID, the PEGC ID, and an indication of communicating via PEGC, PINE-1 may establish a communication connection with PINE-2 via PEGC-1 to exchange data.

[0323] In the scenario where PEGC-1 selects PINE-2 for PINE-1, the PEGC ID in the service response information may be the ID of PEGC-1. At this time, PINE-1 establishes a communication connection with PINE-2 via PEGC-1 to exchange data.

[0324] In the scenario where the PEMC selects PINE-2 for PINE-1, the PEGC ID in the service response information can be the ID of another PEGC (e.g., PEGC-2). In this case, PINE-1 can be associated with PEGC-2, and PINE-1 can establish a communication connection with PINE-2 through PEGC-2 to exchange data.

[0325] Step 6c: If the service request response message received by PINE-1 includes the PINE-2 ID and its associated PEGC-2 ID, PEGC-1 ID, and an indication of communicating through the 5G system, then PINE-1 can be associated with PEGC-1, and the two can communicate through the 5G system.

[0326] Step 7: After the communication connection between PINE-1 and PINE-2 is successfully established, PINE-1 and PINE-2 report their association with PEGC-1 and PEGC-2, the selected communication path, and the access technology to the PEMC and / or the second network element for updating the stored PIN attribute information.

[0327] Example 3

[0328] It should be noted that Example 3 mainly focuses on the process of PEMC configuring a communication path through the 5G system for PINE-1. Referring to Figure 10, the process of PEMC configuring a communication path through the 5G system for a PINE requesting a service includes the following steps:

[0329] Step 0: PINE-1 negotiates with the PEMC or the second network element and chooses to communicate with PINE-2 via 5GS. This negotiation process may be steps 1 to 3 of Example 1, steps 1 to 5 of Example 2, or another signaling interaction process.

[0330] Step 1: PINE-1 associates with PEGC-1 and sends indication information (ie, the third indication information mentioned above) to PEGC-1.

[0331] The indication information is used to inform PEGC-1 of the relevant information of PINE-2 selected by PINE-1 and the communication path between the two.

[0332] Step 2: PEGC-1 establishes or modifies a PDU session for PINE-1, which is used for data exchange between PINE-1 and PINE-2, and for configuring the PEGC-1 IP address and / or the PINE-1 IP address.

[0333] It should be noted that the PEGC-1 IP address and / or PINE-1 IP address can be configured by the 5G core network element during the establishment or modification of the PDU session. For example, the SMF network element allocates IP addresses to PEGC-1 and / or PINE-1.

[0334] Step 3: PINE-1 or PEGC-1 sends association update notification information (ie, the first indication information mentioned above) to PEMC and / or the second network element.

[0335] The association update notification information may include at least one of a PINE-1 ID, a PEGC-1 ID, a PINE-1 IP address, a PEGC-1 IP address, a PINE-2 ID, a PEGC-2 ID, a PINE-2 IP address, a PEGC-2 IP address, association indication information, and path indication information. The association indication information is used to indicate that PINE-1 is associated with PEGC-1 and that PINE-2 is associated with PEGC-2. In addition, the path indication information is used to indicate to the PEMC and / or the second network element that PINE-1 needs to communicate with PINE-2 through the 5G system.

[0336] Step 4: PEMC sends communication path configuration information (that is, the second indication information mentioned above) to PINE-2.

[0337] The association update notification information may include at least one of a PINE-1 ID, a PEGC-1 ID, a PINE-1 IP address, a PEGC-1 IP address, a PINE-2 ID, a PEGC-2 ID, a PINE-2 IP address, a PEGC-2 IP address, association indication information, and path indication information. The association indication information is used to indicate that PINE-1 is associated with PEGC-1 and that PINE-2 is associated with PEGC-2. In addition, the path indication information is used to indicate to the PEMC and / or the second network element that PINE-1 needs to communicate with PINE-2 through 5GS.

[0338] Step 5: PINE-2 associates with PEGC-2 and sends a request message (ie, the second request message mentioned above) to PEGC-2.

[0339] PINE-2 may establish a communication connection with PEGC-2 according to the PEGC-2 ID and / or PEGC-2 IP address in the path configuration information. In addition, PINE-2 may request PEGC-2 to establish or modify a PDU session for it through the request information.

[0340] It should be noted that if PINE-2 has been associated with PEGC-2 before step 5, step 5 can be skipped.

[0341] Step 6: PEGC-2 establishes or modifies a PDU session for PINE-2 for data exchange between PINE-1 and PINE-2, and for configuring the PEGC-2 IP address and / or PINE-2 IP address.

[0342] It should be noted that the PEGC-2 IP address and / or PINE-2 IP address can be configured by the 5G core network element during the establishment or modification of the PDU session. For example, the SMF network element allocates IP addresses to PEGC-2 and / or PINE-2.

[0343] Step 7: PINE-2 / PEGC-2 sends association update notification information to PEMC and / or the second network element.

[0344] It is understood that PINE-2 / PEGC-2 can report its association relationship, PINE-2 ID, PEGC-2 ID, PINE-2 IP address, PEGC-2 IP address, and path indication information to the PEMC and / or the second network element. The path indication information is used to indicate to the PEMC and / or the second network element that PINE-1 needs to communicate with PINE-2 through the 5G system.

[0345] Step 8. PEMC sends a data forwarding policy configuration request to the SMF network element in the 5G system (that is, the first network element in the above embodiment). The data forwarding policy configuration request is used to request configuration of data transmission rules between PINE-1 and PINE-2.

[0346] It should be noted that the manner in which the PEMC sends the data forwarding policy configuration request to the first network element can be referred to as shown in FIG. 7A to FIG. 7D , which will not be described here for the sake of brevity.

[0347] Example 4

[0348] It should be noted that Example 4 is mainly aimed at the process of PEMC configuring a communication path through the 5G system for PINE-1. In this embodiment, PINE-1's associated PEGC-1 has established a PDU session for it, and PINE-1 and / or PEGC-1 have been assigned PINE-1's IP address information and PEGC-1's IP address information by the 5G core network. At the same time, PINE-2's associated PEGC-2 has also established a PDU session for it, and PINE-1 and / or PEGC-1 have been assigned PINE-2's IP address information and PEGC-2's IP address information by the 5G core network. In this scenario, PEGC-1 and PEGC-2 can directly initiate a PDU session modification process to update data transmission rules (such as N4 rules). Specifically, update the configuration packet detection rules and forwarding behavior rules. Referring to Figure 11, the process of PEMC configuring a communication path through the 5G system for a PINE requesting a service includes the following steps:

[0349] Step 0: PINE-1 negotiates with the PEMC and / or the second network element and chooses to communicate with PINE-2 via the 5G system. This negotiation process may be steps 1 to 3 of Example 1, steps 1 to 5 of Example 2, or another signaling interaction process.

[0350] Step 1: PINE-1 sends a data forwarding policy configuration request (that is, the third indication information mentioned above) to PEGC-1.

[0351] The data forwarding policy configuration request may include a PINE-2 ID, a PINE-2 IP address, and a PEGC-2 ID and a PEGC-2 IP address that the PINE-2 needs to be associated with.

[0352] The data forwarding policy configuration request may also be used to request PEGC-1 to modify the corresponding PDU session for PINE-1 to update data transmission rules.

[0353] Step 2: PEGC-1 modifies the data transmission rules in the PDU session for PINE-1.

[0354] Step 3: PINE-1 / PEGC-1 sends a communication path configuration request message (that is, the first indication message mentioned above) to PEMC.

[0355] The communication path configuration request information may include at least one of the following: PINE-1 ID, PINE-1 IP address, PEGC-1 ID, PEGC-1 IP address, PINE-2 ID, PINE-2 IP address, PEGC-2 ID that PINE-2 needs to associate with, PEGC-2 IP address, and path indication information.

[0356] The path indication information is used to indicate to the PEMC and / or the second network element that PINE-1 needs to communicate with PINE-2 through the 5G system.

[0357] Step 4: PEMC and / or the second network element sends data forwarding policy configuration request information (ie, the second indication information mentioned above) to PINE-2.

[0358] The data forwarding policy configuration request information may include at least one of the following: a PINE-1 ID, a PINE-1 IP address, a PEGC-1 ID, a PEGC-1 IP address, a PINE-2 ID, a PINE-2 IP address, a PEGC-2 ID and a PEGC-2 IP address to be associated with PINE-2, and path indication information. The path indication information is used to indicate to the PEMC and / or the second network element that PINE-1 needs to communicate with PINE-2 through the 5G system.

[0359] In an embodiment of the present application, the data forwarding strategy configuration request information is also used to inform PINE-2 that a corresponding forwarding strategy needs to be configured for communicating with PINE-1 through the 5G system.

[0360] Step 5: PINE-2 sends data forwarding policy configuration request information to PEGC-2.

[0361] It should be understood that PINE-2 requests PEGC-2 to modify the corresponding PDU session to update the data transmission rules through the data forwarding policy configuration request message. The content included in the data forwarding policy configuration request message is similar to that in step 4 and is not repeated here for the sake of brevity.

[0362] Step 6: PEGC-2 initiates a PDU session modification process for PINE-2 to update the data transmission rules.

[0363] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0364] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0365] FIG12 is a schematic diagram of the structure of a path selection device 1200 provided in an embodiment of the present application, which is applied to a management device. As shown in FIG12 , the path selection device 1200 includes:

[0366] The candidate device determining unit 1201 is configured to determine at least one candidate IoT device for the first IoT device;

[0367] The candidate path determining unit 1202 is configured to determine a candidate communication path between each candidate IoT device and the first IoT device based on at least one of the following: a distance between each candidate IoT device in the at least one candidate IoT device and the first IoT device, an association relationship between a gateway device associated with each candidate IoT device and the first IoT device, and whether each candidate IoT device and the first IoT device are within a service range of an IoT gateway device;

[0368] The candidate communication paths are used for path selection.

[0369] Optionally, the candidate communication path includes at least one of the following:

[0370] a first communication path representing a path for communicating via a direct connection;

[0371] a second communication path, wherein the second communication path represents a path for communication using the gateway device;

[0372] A third communication path represents a path for communication using a cellular network.

[0373] Optionally, the path selection device 1200 also includes a receiving unit configured to receive first request information, where the first request information is used to request a first service required by the first Internet of Things device, and / or a communication path between the first Internet of Things device and an Internet of Things device providing the first service, and the at least one candidate Internet of Things device is determined based on the first service.

[0374] Optionally, the receiving unit is further configured to receive first request information sent by the first Internet of Things device;

[0375] Alternatively, a first request message sent by a first Internet of Things gateway device is received, where the first Internet of Things gateway device is associated with the first Internet of Things device.

[0376] Optionally, the first request information includes at least one of the following:

[0377] Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected;

[0378] identification information of the first IoT device;

[0379] IP address information of the first IoT device;

[0380] identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device;

[0381] IP address information of the first IoT gateway device;

[0382] a business type of the first business;

[0383] demand information of the first service;

[0384] an access technology preferred by the first IoT device;

[0385] a communication path preferred by the first IoT device.

[0386] Optionally, the candidate device determination unit 1201 is further configured to obtain IoT attribute information, wherein the IoT attribute information includes at least one of the following: attribute information of each IoT device in the first PIN, attribute information of each IoT gateway device in the first PIN, and attribute information of the management device; the first PIN is a personal IoT to which the first IoT device is connected; and based on the IoT attribute information, determine at least one candidate IoT device for the first IoT device.

[0387] Optionally, the attribute information of each IoT device includes at least one of the following:

[0388] Identification information of the Internet of Things device, IP address information of the Internet of Things device, identification information and / or IP address information of the Internet of Things gateway device associated with the Internet of Things device, identification information and / or IP address information of other Internet of Things devices associated with the Internet of Things device, service types supported by the Internet of Things device, location information, and validity time information; the validity time information is used to indicate the valid time, remaining power information, supported wireless access technology, the maximum communication distance corresponding to each wireless access technology in the wireless access technology, and the supported communication path in the first personal Internet of Things.

[0389] Optionally, the attribute information of each IoT gateway device includes at least one of the following:

[0390] Identification information of the Internet of Things gateway device, IP address information of the Internet of Things gateway device, identification information and / or IP address information of the Internet of Things devices associated with the Internet of Things gateway device, identification information of the Internet of Things devices allowed to be associated with the Internet of Things gateway device, identification information of the Internet of Things devices prohibited from being associated with the Internet of Things gateway device, location information, and valid time information, where the valid time information is used to indicate the valid time, remaining power information, supported wireless access technologies, and the maximum communication distance corresponding to each wireless access technology in the first personal Internet of Things.

[0391] Optionally, the attribute information of the management device includes at least one of the following:

[0392] The IP address information, location information, validity time information, supported wireless access technologies, and the maximum communication distance corresponding to each of the wireless access technologies of the management device.

[0393] Optionally, the candidate path determination unit 1202 is further configured to, when the distance between the candidate IoT device and the first IoT device is less than a specified distance, include a first communication path as the candidate communication path, the first communication path representing a path for communication through a direct connection; when the IoT gateway device associated with the candidate IoT device is the same as the IoT gateway device associated with the first IoT device, include a second communication path, the second communication path representing a path for communication using the gateway device; and when both the candidate IoT device and the first IoT device are within the service range of the IoT gateway device, include a third communication path, the third communication path representing a path for communication using a cellular network.

[0394] Optionally, the path selection device 1200 further includes an IoT device determination unit configured to select a candidate IoT device that meets the first condition from at least one candidate IoT device based on the candidate communication path between each candidate IoT device and the first IoT device, to obtain at least one target IoT device.

[0395] Optionally, the first condition includes at least one of the following:

[0396] The candidate communication paths include the communication path preferred by the first IoT device, the candidate communication paths include the communication path with the highest priority, and the candidate communication paths include the default communication path.

[0397] Optionally, the Internet of Things device determination unit is further configured to determine, based on the at least one target Internet of Things device, a second Internet of Things device for providing the first service to the first Internet of Things device.

[0398] Optionally, the number of the at least one target IoT device includes multiple IoT devices, and the IoT device determination unit is further configured to select a target IoT device that meets a second condition from the multiple target IoT devices to obtain the second IoT device;

[0399] The second condition includes at least one of the following:

[0400] The remaining power is the largest, the remaining power is greater than the power threshold, the valid time is the longest, and the valid time is greater than the time threshold.

[0401] Optionally, the path selection device 1200 further includes a sending unit configured to send first response information, where the first response information is used to indicate at least one of the following:

[0402] The connection information of the at least one target IoT device and the connection information of the second IoT device.

[0403] Optionally, the connection information of the second IoT device includes at least one of the following:

[0404] identification information of the second Internet of Things device, IP address information of the second Internet of Things device, a target communication path for communicating with the second Internet of Things device, identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to associate with in the target communication path, and identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path;

[0405] Furthermore, the connection information of the at least one target IoT device includes at least one of the following:

[0406] Identification information and / or IP address information of each target IoT device in the at least one target IoT device, access technology supported by each target IoT device, communication path supported by each target IoT device, identification information and / or IP address information of the IoT gateway device that each target IoT device needs to be associated with in the communication path supported by each target IoT device, identification information and / or IP address information of the IoT gateway device that the first IoT device needs to be associated with in the communication path supported by each target IoT device.

[0407] Optionally, the receiving unit is further configured to receive first indication information, where the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

[0408] Optionally, the sending unit is further configured to send second indication information to the second Internet of Things device, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path.

[0409] Optionally, the first indication information and / or the second indication information includes at least one of the following:

[0410] The identification information of the first Internet of Things device, the IP address information of the first Internet of Things device, the identification information of the first Internet of Things gateway device, the IP address information of the first Internet of Things gateway device, the identification information of the second Internet of Things device, the IP address information of the second Internet of Things device, the identification information of the second Internet of Things gateway device, the IP address information of the second Internet of Things gateway device, the association indication information, and the path indication information; wherein the association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; and the path indication information is used to indicate that the first Internet of Things device and the second Internet of Things device communicate through a third communication path.

[0411] Optionally, the sending unit is further configured to send a data forwarding policy configuration request to the first network element of the cellular network, where the data forwarding policy configuration request is used to request configuration of data transmission rules between the first Internet of Things device and the second Internet of Things device.

[0412] Optionally, the management device is an Internet of Things device with a management function, the first network element is a session management function SMF network element, and the sending unit is further configured to do at least one of the following:

[0413] Forwarding the data forwarding policy configuration request to the first network element through the second network element; the second network element is used to manage the personal Internet of Things;

[0414] Sending the data forwarding policy configuration request to the first network element through the second network element and the policy control function network element PCF;

[0415] forwarding the data forwarding policy configuration request to the first network element through the second network element and the network exposure function NEF;

[0416] The data forwarding policy configuration request is sent to the first network element through the second network element, the NEF and the PCF.

[0417] Optionally, the management device is a second network element, the first network element is an SMF network element, and the sending unit is further configured to do at least one of the following:

[0418] Sending the data forwarding policy configuration request to the first network element;

[0419] Sending the data forwarding policy configuration request to the first network element through the PCF network element;

[0420] Forwarding the data forwarding policy configuration request to the first network element through the NEF network element;

[0421] The data forwarding policy configuration request is sent to the first network element through the NEF network element and the PCF network element.

[0422] FIG13 is a schematic diagram of the structure of a path selection device 1300 provided in an embodiment of the present application, which is applied to a first IoT device. As shown in FIG13 , the path selection device 1300 includes:

[0423] The sending unit 1301 is configured to send first request information, where the first request information is used to request a first service required by the first IoT device and / or a communication path between the first IoT device and an IoT device that provides the first service.

[0424] Optionally, the first request information includes at least one of the following:

[0425] Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected;

[0426] identification information of the first IoT device;

[0427] IP address information of the first IoT device;

[0428] identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device;

[0429] IP address information of the first IoT gateway device;

[0430] a business type of the first business;

[0431] demand information of the first service;

[0432] an access technology preferred by the first IoT device;

[0433] a communication path preferred by the first IoT device.

[0434] Optionally, the sending unit 1301 is further configured to send the first request information to a management device; or send the first request information to a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the management device.

[0435] Optionally, the path selection device 1300 may further include a receiving unit configured to receive a first response message sent by a management device, or to receive a second response message sent by a first Internet of Things gateway device, wherein the first response information and / or the second response information are used to indicate connection information of at least one target Internet of Things device, and / or connection information of a second Internet of Things device; the at least one target Internet of Things device is determined based on at least one candidate Internet of Things device, and the at least one candidate Internet of Things device is determined based on the first business; the second Internet of Things device is selected based on the at least one target Internet of Things device.

[0436] Optionally, the connection information of the second Internet of Things device includes at least one of the following: identification information of the second Internet of Things device, IP address information of the second Internet of Things device, a target communication path for communicating with the second Internet of Things device, identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to associate with in the target communication path, and identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path;

[0437] Furthermore, the connection information of at least one target IoT device includes at least one of the following:

[0438] Identification information and / or IP address information of each target IoT device in at least one target IoT device, access technology supported by each target IoT device, communication path supported by each target IoT device, identification information and / or IP address information of an IoT gateway device that needs to be associated with each target IoT device in the communication path supported by each target IoT device, identification information and / or IP address information of an IoT gateway device that needs to be associated with the first IoT device in the communication path supported by each target IoT device.

[0439] Optionally, the path selection apparatus 1300 may further include an IoT device determining unit. When the first response information indicates connection information of at least one target IoT device, the IoT device determining unit is configured to select a target IoT device that meets a second condition from the at least one target IoT device to obtain a second IoT device.

[0440] The second condition includes at least one of the following: the remaining power is the largest, the remaining power is greater than a power threshold, the valid time is the longest, and the valid time is greater than a time threshold.

[0441] Optionally, the path selection device 1300 may further include a communication establishing unit configured to establish communication with the first Internet of Things gateway device.

[0442] Optionally, the sending unit 1301 is further configured to send third indication information to the first Internet of Things gateway device, where the third indication information is used to indicate at least one of the following: identification information and / or IP address information of the second Internet of Things device, communication between the first Internet of Things device and the second Internet of Things device through a third communication path, the third communication path representing a path for communication using a cellular network, and identification information and / or IP address information of the second Internet of Things gateway device associated with the second Internet of Things device in the third communication path.

[0443] Optionally, the sending unit 1301 is further configured to send first indication information to the management device; the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, and the third communication path represents a path for communication using a cellular network.

[0444] Optionally, the first indication information includes at least one of the following: identification information of the first Internet of Things device, IP address information of the first Internet of Things device, identification information of the first Internet of Things gateway device, IP address information of the first Internet of Things gateway device, identification information of the second Internet of Things device, IP address information of the second Internet of Things device, identification information of the second Internet of Things gateway device, IP address information of the second Internet of Things gateway device, association indication information, and path indication information; the association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; the path indication information is used to indicate that the first Internet of Things device and the second Internet of Things device communicate through a third communication path.

[0445] FIG14 is a schematic diagram of the structure of a path selection device 1400 provided in an embodiment of the present application, which is applied to a first IoT gateway device. As shown in FIG14 , the path selection device 1400 includes:

[0446] The receiving unit 1401 is configured to receive a first request message sent by a first IoT device; the first request message is used to request a first service required by the first IoT device, and / or a communication path between the first IoT device and an IoT device that provides the first service.

[0447] Optionally, the first request information includes at least one of the following:

[0448] Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected;

[0449] identification information of the first IoT device;

[0450] IP address information of the first IoT device;

[0451] identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device;

[0452] IP address information of the first IoT gateway device;

[0453] a business type of the first business;

[0454] demand information of the first service;

[0455] an access technology preferred by the first IoT device;

[0456] a communication path preferred by the first IoT device.

[0457] Optionally, the path selection device 1400 may further include an IoT device determination unit, configured to determine at least one target IoT device from at least one IoT device associated therewith; and based on the at least one target IoT device, determine a second IoT device for providing the first service to the first IoT device.

[0458] Optionally, the path selection device 1400 may further include a sending unit configured to send the first request information to a management device if the target IoT device does not exist in at least one IoT device associated with the first IoT gateway device.

[0459] Optionally, the receiving unit 1401 is further configured to receive a first response message sent by the management device; the first response information is used to indicate the connection information of at least one target IoT device, and / or the connection information of a second IoT device; wherein, the at least one target IoT device is determined based on at least one candidate IoT device, and the at least one candidate IoT device is determined based on the first service; the second IoT device is selected based on the at least one target IoT device.

[0460] Optionally, the sending unit is further configured to send second response information to the first Internet of Things device.

[0461] Optionally, the connection information of the second IoT device includes at least one of the following:

[0462] identification information of the second Internet of Things device, IP address information of the second Internet of Things device, a target communication path for communicating with the second Internet of Things device, identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to associate with in the target communication path, and identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path;

[0463] In addition, the connection information of the at least one target IoT device includes at least one of the following: identification information and / or IP address information of each target IoT device in the at least one target IoT device, access technology supported by each target IoT device, communication path supported by each target IoT device, identification information and / or IP address information of an IoT gateway device that each target IoT device needs to be associated with in the communication path supported by each target IoT device, and identification information and / or IP address information of an IoT gateway device that the first IoT device needs to be associated with in the communication path supported by each target IoT device.

[0464] Optionally, the receiving unit 1401 is further configured to receive third indication information, wherein the third indication information is used to indicate at least one of the following: identification information and / or IP address information of the second Internet of Things device, communication between the first Internet of Things device and the second Internet of Things device through a third communication path, the third communication path representing a path for communication using a cellular network, and identification information and / or IP address information of a second Internet of Things gateway device associated with the second Internet of Things device in the third communication path.

[0465] Optionally, the path selection device 1400 may further include a PDU session management unit configured to establish or modify a PDU session for the first IoT device if the first IoT gateway device has not established a PDU session for the first IoT device; or to modify a data transmission rule corresponding to the PDU session if the first IoT gateway device has established a PDU session for the first IoT device;

[0466] The PDU session is used to transmit business data between the first IoT device and the second IoT device, and to configure IP address information of the first IoT device and / or the first IoT gateway device.

[0467] Optionally, the sending unit is further configured to send first indication information to the management device, wherein the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, and the third communication path represents a path for communication using a cellular network.

[0468] Optionally, the first indication information includes at least one of the following: identification information of the first Internet of Things device, IP address information of the first Internet of Things device, identification information of the first Internet of Things gateway device, IP address information of the first Internet of Things gateway device, identification information of the second Internet of Things device, IP address information of the second Internet of Things device, identification information of the second Internet of Things gateway device, IP address information of the second Internet of Things gateway device, association indication information, and path indication information; the association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; the path indication information is used to indicate that the first Internet of Things device and the second Internet of Things device communicate through a third communication path.

[0469] FIG15 is a first structural diagram of a path selection device 1500 according to an embodiment of the present application, which is applied to a second IoT device. As shown in FIG15 , the path selection device 1500 includes:

[0470] The receiving unit is configured to receive second indication information, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

[0471] Optionally, the second indication information includes at least one of the following:

[0472] The identification information of the first Internet of Things device, the IP address information of the first Internet of Things device, the identification information of the first Internet of Things gateway device, the IP address information of the first Internet of Things gateway device, the identification information of the second Internet of Things device, the IP address information of the second Internet of Things device, the identification information of the second Internet of Things gateway device, the IP address information of the second Internet of Things gateway device, the association indication information, and the path indication information; the association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; the path indication information is used to indicate that the first Internet of Things device and the second Internet of Things device communicate through a third communication path.

[0473] Optionally, the path selection device 1500 further includes a communication establishing unit configured to establish communication with the second Internet of Things gateway device.

[0474] Optionally, the path selection device 1500 also includes a sending unit, configured to send a second request information to the second Internet of Things gateway device, where the second request information is used to request to establish or modify a PDU session, or to request to modify the data transmission rules corresponding to the PDU session; the PDU session is used to transmit business data between the first Internet of Things device and the second Internet of Things device, and to configure the IP address information of the second Internet of Things device and / or the second Internet of Things gateway device.

[0475] Those skilled in the art should understand that the relevant description of the above-mentioned path selection device in the embodiment of the present application can be understood with reference to the relevant description of the path selection method in the embodiment of the present application.

[0476] Figure 16 is a schematic diagram of a communication device 1600 provided in an embodiment of the present application. The communication device can be a management device, an IoT device, or an IoT gateway device. The communication device 1600 shown in Figure 16 includes a processor 1610, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0477] Optionally, as shown in FIG16 , the communication device 1600 may further include a memory 1620. The processor 1610 may call and execute a computer program from the memory 1620 to implement the method in the embodiment of the present application.

[0478] The memory 1620 may be a separate device independent of the processor 1610 , or may be integrated into the processor 1610 .

[0479] Optionally, as shown in FIG16 , the communication device 1600 may further include a transceiver 1630 , and the processor 1610 may control the transceiver 1630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0480] The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include an antenna, and the number of antennas may be one or more.

[0481] Optionally, the communication device 1600 may specifically be a management device in an embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the management device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0482] Optionally, the communication device 1600 may specifically be an Internet of Things device (including a first Internet of Things device and / or a second Internet of Things device) of an embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the Internet of Things device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0483] Optionally, the communication device 1600 may specifically be an Internet of Things gateway device (including a first Internet of Things gateway device and / or a second Internet of Things gateway device) of an embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the Internet of Things gateway device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0484] Figure 17 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1700 shown in Figure 17 includes a processor 1710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0485] Optionally, as shown in FIG17 , the chip 1700 may further include a memory 1720. The processor 1710 may call and execute a computer program from the memory 1720 to implement the method in the embodiment of the present application.

[0486] The memory 1720 may be a separate device independent of the processor 1710 , or may be integrated into the processor 1910 .

[0487] Optionally, the chip 1700 may further include an input interface 1730. The processor 1710 may control the input interface 1730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0488] Optionally, the chip 1700 may further include an output interface 1740. The processor 1710 may control the output interface 1740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0489] Optionally, the chip can be applied to the management device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the management device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0490] Optionally, the chip can be applied to the Internet of Things devices (including the first Internet of Things device and / or the second Internet of Things device) in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the Internet of Things devices in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0491] Optionally, the chip can be applied to the Internet of Things gateway device (including the first Internet of Things gateway device and / or the second Internet of Things gateway device) in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the Internet of Things gateway device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0492] The chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0493] FIG18 is a schematic block diagram of a communication system 1800 provided in an embodiment of the present application. As shown in FIG18 , the communication system 1800 includes a management device 1810 , an IoT device 1820 , and an IoT gateway device 1830 .

[0494] Among them, the management device 1810 can be used to implement the corresponding functions implemented by the management device in the above method, the Internet of Things device 1820 can be used to implement the corresponding functions implemented by the first Internet of Things device and / or the second Internet of Things device in the above method, and the Internet of Things gateway device 1830 can be used to implement the corresponding functions implemented by the first Internet of Things gateway device and / or the second Internet of Things gateway device in the above method. For the sake of brevity, they will not be repeated here.

[0495] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0496] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0497] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0498] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0499] Optionally, the computer-readable storage medium can be applied to the management device, Internet of Things device, or Internet of Things gateway device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the management device, Internet of Things device, or Internet of Things gateway device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0500] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0501] Optionally, the computer program product can be applied to the management device, Internet of Things device, or Internet of Things gateway device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the management device, Internet of Things device, or Internet of Things gateway device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0502] The present application also provides a computer program. Optionally, the computer program can be applied to the management device, IoT device, or IoT gateway device in the present application. When the computer program is executed on a computer, the computer executes the corresponding processes implemented by the management device, IoT device, or IoT gateway device in the various methods of the present application. For the sake of brevity, these procedures are not further described here.

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

[0504] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0505] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0507] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0508] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0509] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A path selection method, comprising: The management device determines at least one candidate IoT device for the first IoT device; The management device determines, based on at least one of the following: a distance between each candidate IoT device and the first IoT device, an association relationship between a gateway device associated with each candidate IoT device and the first IoT device, and whether each candidate IoT device and the first IoT device are within a service range of an IoT gateway device; The candidate communication paths are used for path selection.

2. The method according to claim 1, wherein The candidate communication paths include at least one of the following: a first communication path representing a path for communicating via a direct connection; a second communication path, wherein the second communication path represents a path for communication using the gateway device; A third communication path represents a path for communication using a cellular network.

3. The method according to claim 1 or 2, wherein: Before the management device determines at least one candidate IoT device for the first IoT device, the method further includes: The management device receives first request information, where the first request information is used to request a first service required by the first IoT device, and / or a communication path between the first IoT device and an IoT device that provides the first service, and the at least one candidate IoT device is determined based on the first service.

4. The method according to claim 3, wherein: The management device receives the first request information, including: The management device receives first request information sent by the first Internet of Things device; or, The management device receives first request information sent by a first Internet of Things gateway device, and the first Internet of Things gateway device is associated with the first Internet of Things device.

5. The method according to claim 3 or 4, wherein: The first request information includes at least one of the following: Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected; identification information of the first IoT device; IP address information of the first IoT device; identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device; IP address information of the first IoT gateway device; a business type of the first business; demand information of the first service; an access technology preferred by the first IoT device; a communication path preferred by the first IoT device.

6. The method according to any one of claims 1 to 5, wherein: The management device determines at least one candidate IoT device for the first IoT device, including: The management device obtains IoT attribute information, where the IoT attribute information includes at least one of the following: attribute information of each IoT device in the first PIN, attribute information of each IoT gateway device in the first PIN, and attribute information of the management device; the first PIN is a personal IoT to which the first IoT device is connected; The management device determines the at least one candidate IoT device for the first IoT device based on the IoT attribute information.

7. The method according to claim 6, wherein: The attribute information of each IoT device includes at least one of the following: Identification information of IoT devices; IP address information of IoT devices; Identification information and / or IP address information of the IoT gateway device associated with the IoT device; Identification information and / or IP address information of other IoT devices associated with the IoT device; The types of services supported by IoT devices; Location information; Valid time information; the valid time information is used to indicate the valid time in the first personal Internet of Things; Remaining power information; Supported wireless access technologies; The maximum communication distance corresponding to each wireless access technology in the wireless access technology; Supported communication paths.

8. The method according to claim 6 or 7, wherein: The attribute information of each IoT gateway device includes at least one of the following: Identification information of the IoT gateway device; IP address information of IoT gateway devices; Identification information and / or IP address information of the IoT device associated with the IoT gateway device; Identification information of IoT devices that are allowed to be associated with the IoT gateway device; The identification information of IoT devices that are prohibited from being associated with the IoT gateway device; Location information; Valid time information; the valid time information is used to indicate the valid time in the first personal Internet of Things; Remaining power information; Supported wireless access technologies; The maximum communication distance corresponding to each wireless access technology in the wireless access technologies.

9. The method according to any one of claims 6 to 8, wherein: The attribute information of the management device includes at least one of the following: IP address information of the management device; Location information; Valid time information; Supported wireless access technologies; The maximum communication distance corresponding to each wireless access technology in the wireless access technologies.

10. The method according to any one of claims 1 to 9, wherein: The determining of a candidate communication path between each candidate IoT device and the first IoT device includes: In a case where the distance between the candidate IoT device and the first IoT device is less than a specified distance, the candidate communication paths include a first communication path, the first communication path representing a path for communication through a direct connection; In a case where the IoT gateway device associated with the candidate IoT device is the same as the IoT gateway device associated with the first IoT device, the candidate communication path includes a second communication path, where the second communication path represents a path for communication using the gateway device; In a case where both the candidate IoT device and the first IoT device are within the service range of the IoT gateway device, the candidate communication path includes a third communication path, where the third communication path represents a path for communication using a cellular network.

11. The method according to any one of claims 1 to 10, wherein: Also includes: The management device selects a candidate IoT device that meets a first condition from the at least one candidate IoT device based on the candidate communication path between each candidate IoT device and the first IoT device, to obtain at least one target IoT device.

12. The method according to claim 10, wherein: The first condition includes at least one of the following: The candidate communication paths include the communication path preferred by the first IoT device; The candidate communication paths include a communication path with the highest priority; The candidate communication paths include a default communication path.

13. The method according to claim 11 or 12, wherein: Also includes: The management device determines, based on the at least one target IoT device, a second IoT device for providing the first service to the first IoT device.

14. The method according to claim 11 or 12, wherein: The number of the at least one target IoT device includes multiple ones, and further includes: The management device selects a target IoT device that meets a second condition from a plurality of target IoT devices to obtain the second IoT device; The second condition includes at least one of the following: The remaining power is the highest; The remaining power is greater than the power threshold; The longest effective time; The valid time is greater than the time threshold.

15. The method according to any one of claims 11 to 14, wherein: The method further comprises: The management device sends a first response message, where the first response message is used to indicate the connection information of the at least one target IoT device or the connection information of the second IoT device.

16. The method according to claim 15, wherein The connection information of the second IoT device includes at least one of the following: identification information of the second IoT device; IP address information of the second IoT device; a target communication path for communicating with the second IoT device; identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to be associated with in the target communication path; identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path; Furthermore, the connection information of the at least one target IoT device includes at least one of the following: identification information and / or IP address information of each target IoT device in the at least one target IoT device; The access technology supported by each target IoT device; a communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that each target IoT device needs to be associated with in the communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that the first IoT device needs to be associated with in the communication path supported by each target IoT device.

17. The method according to any one of claims 1 to 16, wherein: Also includes: The management device receives first indication information, where the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

18. The method according to claim 17, wherein Also includes: The management device sends second indication information to the second Internet of Things device, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path.

19. The method according to claim 17 or 18, wherein The first indication information and / or the second indication information includes at least one of the following: identification information of the first IoT device; IP address information of the first IoT device; identification information of the first IoT gateway device; IP address information of the first IoT gateway device; identification information of the second IoT device; IP address information of the second IoT device; identification information of the second IoT gateway device; IP address information of the second IoT gateway device; association instruction information; The association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; Path indication information; The path indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path.

20. The method according to any one of claims 17 to 19, wherein: The management device sends a data forwarding policy configuration request to the first network element of the cellular network, where the data forwarding policy configuration request is used to request configuration of data transmission rules between the first Internet of Things device and the second Internet of Things device.

21. The method according to claim 20, wherein The management device is an Internet of Things device with a management function, the first network element is a session management function SMF network element, and the management device sends a data forwarding policy configuration request to the first network element of the cellular network, including at least one of the following: The management device forwards the data forwarding policy configuration request to the first network element through a second network element; the second network element is used to manage the personal Internet of Things; The management device sends the data forwarding policy configuration request to the first network element through the second network element and the policy control function network element PCF; The management device forwards the data forwarding policy configuration request to the first network element through the second network element and the network exposure function NEF; The management device sends the data forwarding policy configuration request to the first network element through the second network element, NEF and PCF.

22. The method according to claim 20, wherein The management device is a second network element, the second network element is used to manage a personal internet of things, the first network element is a session management function (SMF) network element, and the management device sends a data forwarding policy configuration request to the first network element of the cellular network, including at least one of the following: The management device sends the data forwarding policy configuration request to the first network element; The management device sends the data forwarding policy configuration request to the first network element through the policy control function network element PCF; The management device forwards the data forwarding policy configuration request to the first network element through the network exposure function NEF; The management device sends the data forwarding policy configuration request to the first network element through the NEF and the PCF.

23. A path selection method, the method comprising: The first Internet of Things device sends first request information, where the first request information is used to request a first service required by the first Internet of Things device and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

24. The method according to claim 23, wherein The first request information includes at least one of the following: Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected; identification information of the first IoT device; IP address information of the first IoT device; identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device; IP address information of the first IoT gateway device; a business type of the first business; demand information of the first service; an access technology preferred by the first IoT device; a communication path preferred by the first IoT device.

25. The method according to claim 23 or 24, wherein The first IoT device sends a first request message, including: The first Internet of Things device sends the first request information to the management device; or, The first Internet of Things device sends the first request information to a first Internet of Things gateway device, and the first Internet of Things gateway device is associated with a management device.

26. The method according to any one of claims 23 to 25, wherein: The method further comprises: The first IoT device receives a first response message sent by the management device, or, The first Internet of Things device receives second response information sent by the first Internet of Things gateway device; The first response information and / or the second response information is used to indicate the connection information of at least one target IoT device, or the connection information of a second IoT device; the at least one target IoT device is determined based on at least one candidate IoT device, and the at least one candidate IoT device is determined based on the first service; the second IoT device is selected based on the at least one target IoT device.

27. The method according to claim 26, wherein The connection information of the second IoT device includes at least one of the following: identification information of the second IoT device; IP address information of the second IoT device; a target communication path for communicating with the second IoT device; identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to be associated with in the target communication path; identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path; Furthermore, the connection information of the at least one target IoT device includes at least one of the following: identification information and / or IP address information of each target IoT device in the at least one target IoT device; The access technology supported by each target IoT device; a communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that each target IoT device needs to be associated with in the communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that the first IoT device needs to be associated with in the communication path supported by each target IoT device.

28. The method according to claim 26 or 27, wherein In a case where the first response information is used to indicate connection information of at least one target IoT device, the method further includes: The first Internet of Things device selects a target Internet of Things device that meets a second condition from the at least one target Internet of Things device to obtain a second Internet of Things device; The second condition includes at least one of the following: The remaining power is the highest; The remaining power is greater than the power threshold; The longest effective time; The valid time is greater than the time threshold.

29. The method according to any one of claims 26 to 28, wherein: The method further comprises: The first Internet of Things device establishes communication with the first Internet of Things gateway device.

30. The method according to any one of claims 26 to 29, wherein: The method further comprises: The first IoT device sends third indication information to the first IoT gateway device, where the third indication information is used to indicate at least one of the following: identification information and / or IP address information of the second IoT device; The first IoT device communicates with the second IoT device via a third communication path; the third communication path represents a path for communication using a cellular network; Identification information and / or IP address information of a second Internet of Things gateway device associated with the second Internet of Things device in the third communication path.

31. The method according to any one of claims 26 to 30, wherein: The method further comprises: The first Internet of Things device sends first indication information to the management device; the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, and the third communication path represents a path for communication using a cellular network.

32. The method according to claim 31, wherein The first indication information includes at least one of the following: identification information of the first IoT device; IP address information of the first IoT device; identification information of the first IoT gateway device; IP address information of the first IoT gateway device; identification information of the second IoT device; IP address information of the second IoT device; identification information of the second IoT gateway device; IP address information of the second IoT gateway device; association instruction information; The association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; Path indication information; The path indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path.

33. A path selection method, the method comprising: The first Internet of Things gateway device receives the first request information sent by the first Internet of Things device; The first request information is used to request a first service required by the first IoT device and / or a communication path between the first IoT device and an IoT device that provides the first service.

34. The method according to claim 33, wherein The first request information includes at least one of the following: Identification information of the first personal Internet of Things PIN; the first PIN is the personal Internet of Things to which the first Internet of Things device is connected; identification information of the first IoT device; IP address information of the first IoT device; identification information of a first Internet of Things gateway device, where the first Internet of Things gateway device is associated with the first Internet of Things device; IP address information of the first IoT gateway device; a business type of the first business; demand information of the first service; an access technology preferred by the first IoT device; a communication path preferred by the first IoT device.

35. The method according to claim 33 or 34, wherein Also includes: The first IoT gateway device determines at least one target IoT device from at least one IoT device associated with the first IoT gateway device; The first Internet of Things gateway device determines, based on the at least one target Internet of Things device, a second Internet of Things device for providing the first service to the first Internet of Things device.

36. The method according to claim 35, wherein The method further comprises: If the target IoT device does not exist in at least one IoT device associated with the first IoT gateway device, the first IoT gateway device sends the first request information to the management device.

37. The method according to claim 36, wherein The method further comprises: The first IoT gateway device receives a first response message sent by the management device; the first response message is used to indicate connection information of at least one target IoT device and / or connection information of a second IoT device; Among them, the at least one target Internet of Things device is determined based on at least one candidate Internet of Things device, and the at least one candidate Internet of Things device is determined based on the first business; the second Internet of Things device is selected based on the at least one target Internet of Things device.

38. The method according to claim 36 or 37, wherein The method further comprises: The first Internet of Things gateway device sends second response information to the first Internet of Things device.

39. The method according to claim 37 or 38, wherein The connection information of the second IoT device includes at least one of the following: identification information of the second IoT device; IP address information of the second IoT device; a target communication path for communicating with the second IoT device; identification information and / or IP address information of a first Internet of Things gateway device that the first Internet of Things device needs to be associated with in the target communication path; identification information and / or IP address information of a second Internet of Things gateway device that the second Internet of Things device needs to associate with in the target communication path; Furthermore, the connection information of the at least one target IoT device includes at least one of the following: identification information and / or IP address information of each target IoT device in the at least one target IoT device; The access technology supported by each target IoT device; a communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that each target IoT device needs to be associated with in the communication path supported by each target IoT device; Identification information and / or IP address information of an IoT gateway device that the first IoT device needs to be associated with in the communication path supported by each target IoT device.

40. The method according to any one of claims 33 to 39, wherein: The method further comprises: The first IoT gateway device receives third indication information, where the third indication information is used to indicate at least one of the following: identification information and / or IP address information of the second IoT device; The first IoT device communicates with the second IoT device via a third communication path; the third communication path represents a path for communication using a cellular network; Identification information and / or IP address information of a second Internet of Things gateway device associated with the second Internet of Things device in the third communication path.

41. The method according to claim 40, wherein The method further comprises: In a case where the first Internet of Things gateway device has not established a PDU session for the first Internet of Things device, the first Internet of Things gateway device establishes or modifies a PDU session for the first Internet of Things device; or, In a case where the first Internet of Things gateway device has established a PDU session for the first Internet of Things device, the first Internet of Things gateway device modifies a data transmission rule corresponding to the PDU session; The PDU session is used to transmit business data between the first IoT device and the second IoT device, and to configure IP address information of the first IoT device and / or the first IoT gateway device.

42. The method according to claim 41, wherein The method further comprises: The first Internet of Things gateway device sends first indication information to the management device, where the first indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

43. The method according to claim 42, wherein The first indication information includes at least one of the following: identification information of the first IoT device; IP address information of the first IoT device; identification information of the first IoT gateway device; IP address information of the first IoT gateway device; identification information of the second IoT device; IP address information of the second IoT device; identification information of the second IoT gateway device; IP address information of the second IoT gateway device; association instruction information; The association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; Path indication information; The path indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path.

44. A path selection method, the method comprising: The second Internet of Things device receives second indication information, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

45. The method of claim 44, wherein: The second indication information includes at least one of the following: identification information of the first IoT device; IP address information of the first IoT device; identification information of the first IoT gateway device; IP address information of the first IoT gateway device; identification information of the second IoT device; IP address information of the second IoT device; identification information of the second IoT gateway device; IP address information of the second IoT gateway device; association instruction information; The association indication information is used to indicate that the first Internet of Things device is associated with the first Internet of Things gateway device, and / or that the second Internet of Things device is associated with the second Internet of Things gateway device; Path indication information; The path indication information is used to instruct the first Internet of Things device to communicate with the second Internet of Things device through a third communication path.

46. ​​The method according to claim 44 or 45, wherein The method further comprises: The second Internet of Things device establishes communication with a second Internet of Things gateway device.

47. The method according to any one of claims 44 to 46, wherein: The method further comprises: The second IoT device sends a second request message to the second IoT gateway device, where the second request message is used to request establishment or modification of a PDU session, or to request modification of data transmission rules corresponding to the PDU session; the PDU session is used to transmit business data between the first IoT device and the second IoT device, and to configure IP address information of the second IoT device and / or the second IoT gateway device.

48. A path selection device, applied to a management device, comprising: a candidate device determining unit, configured to determine at least one candidate IoT device for the first IoT device; a candidate path determining unit configured to determine a candidate communication path between each candidate IoT device and the first IoT device based on a distance between each candidate IoT device among the at least one candidate IoT device and the first IoT device, and / or a distance and an association relationship between a gateway device associated with each candidate IoT device and the first IoT device; The candidate communication paths are used for path selection.

49. A path selection device, applied to a first IoT device, comprising: The sending unit is configured to send first request information, where the first request information is used to request a first service required by the first Internet of Things device and / or a communication path between the first Internet of Things device and an Internet of Things device that provides the first service.

50. A path selection device, applied to a first Internet of Things gateway device, comprising: A receiving unit, configured to receive first request information sent by a first IoT device; The first request information is used to request a first service required by the first IoT device and / or a communication path between the first IoT device and an IoT device that provides the first service.

51. A path selection device, applied to a second IoT device, comprising: The receiving unit is configured to receive second indication information, where the second indication information is used to instruct the second Internet of Things device to communicate with the first Internet of Things device through a third communication path, where the third communication path represents a path for communication using a cellular network.

52. A management device comprising: Memory, processors, and transceivers, The transceiver is used to implement communication with the management device; The memory stores a computer program executable on the processor. When the processor executes the program in conjunction with the transceiver, the method according to any one of claims 1 to 22 is implemented.

53. An Internet of Things device comprising a memory, a processor, and a transceiver, The transceiver is used to realize the communication of the Internet of Things device; The memory stores a computer program executable on the processor. When the processor executes the program in conjunction with the transceiver, the method according to any one of claims 23 to 32 or claims 44 to 47 is implemented.

54. An Internet of Things gateway device, comprising a memory, a processor and a transceiver, The transceiver is used to realize the communication of the Internet of Things gateway device; The memory stores a computer program executable on the processor. When the processor executes the program in conjunction with the transceiver, the method according to any one of claims 33 to 43 is implemented.

55. A computer storage medium storing one or more programs, wherein the one or more programs can be executed by one or more processors to implement the method described in any one of claims 1 to 22, or claims 23 to 32, or claims 33 to 43, or claims 44 to 47.

56. A chip, comprising: A processor for calling and running a computer program from a memory so that a device equipped with the chip performs a method as described in any one of claims 1 to 22, or claims 23 to 32, or claims 33 to 43, or claims 44 to 47.

57. A computer program product, comprising a computer storage medium storing a computer program, wherein the computer program comprises instructions executable by at least one processor, and wherein the instructions, when executed by the at least one processor, implement the method of claim 122, or any one of claims 23 to 32, or claims 33 to 43, or claims 44 to 47.

58. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 22, or claims 23 to 32, or claims 33 to 43, or claims 44 to 47.