Method, device, storage medium and program product for determining internet of things link status

Abstract

This application discloses a method, device, storage medium, and program product for determining the state of an Internet of Things (IoT) link, applied in the field of communications. The method includes obtaining characteristic data of IoT service messages according to the IoT data network name, the characteristic data including source address and destination address; determining the state of the message transmission link based on the source address, destination address, and message transmission direction; sending a probe message to the peer device of the message transmission link based on the state of the message transmission link; and determining the state of the IoT link as the target state upon receiving a response message from the peer device of the message transmission link, thus accurately determining the IoT link state.

Description

Technical Field

[0001] This application belongs to the field of communications, and specifically relates to a method, device, storage medium, and computer program product for determining the state of an Internet of Things (IoT) link. Background Technology

[0002] The Internet of Things (IoT) is an interconnected network comprising a sensing layer, a network layer, a platform layer, and an application layer. Currently, IoT using mobile communication networks as the network layer is applied in numerous social sectors, playing a significant role in improving social productivity. To improve user service quality, the status of IoT links is monitored so that operators can perceive the link status immediately. The IoT link status indicates whether the communication link is abnormal, clarifying the direction for troubleshooting communication anomalies and improving user service quality. However, in related technologies, operators cannot accurately determine the status of IoT links. Summary of the Invention

[0003] This application provides a method, apparatus, device, storage medium, and computer program product for identifying the state of an Internet of Things (IoT) link, which solves the problem of being unable to accurately determine the state of an IoT link.

[0004] In a first aspect, embodiments of this application provide a method for determining the state of an Internet of Things (IoT) link, the method comprising:

[0005] The characteristic data of IoT service messages are obtained according to the data network name of the IoT. The characteristic data includes the source address and the destination address.

[0006] The state of the message transmission link is determined based on the source address, destination address, and message transmission direction.

[0007] Based on the status of the message transmission link, send probe messages to the peer device of the message transmission link;

[0008] Upon receiving a response message from the peer device in the message transmission link, the state of the IoT link is determined to be the target state.

[0009] Secondly, this application provides an apparatus for determining the state of an Internet of Things (IoT) link, the apparatus comprising:

[0010] The acquisition module is used to obtain the characteristic data of IoT service messages according to the data network name of the IoT. The characteristic data includes the source address and the destination address.

[0011] The determination module is used to determine the status of the message transmission link based on the source address, destination address, and message transmission direction.

[0012] The sending module is used to send probe messages to the peer device of the message transmission link based on the status of the message transmission link;

[0013] The determination module is also used to determine the state of the IoT link as the target state when a response message is received from the peer device of the message transmission link.

[0014] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the steps of the method for determining the state of an Internet of Things link as described in the first aspect.

[0015] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method for determining the state of an Internet of Things link as described in the first aspect.

[0016] Fifthly, embodiments of this application provide a chip, which includes a processor and a display interface coupled to the processor. The processor is used to run programs or instructions to implement the steps of the method for determining the state of an Internet of Things link as described in the first aspect.

[0017] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the steps of the method for determining the state of an Internet of Things link as described in the first aspect.

[0018] The method, apparatus, device, storage medium, and computer program product for determining the state of an IoT link in this application embodiment obtains feature data of IoT service messages according to the IoT data network name, and determines the state of the message transmission link based on the source address, destination address, and message direction in the feature data. Then, based on the state of the message transmission link, a probe message is sent to the peer device of the message transmission link to perform link probing. If a response message is received from the peer device of the message transmission link, the state of the IoT link is determined to be normal, i.e., the target state. If no response message is received from the peer device of the message transmission link, the state of the IoT link is determined to be abnormal. This application embodiment can detect whether the IoT link is abnormal. This application embodiment can accurately determine the state of the IoT link. Attached Figure Description

[0019] Figure 1 A schematic diagram of a system for determining the state of an Internet of Things (IoT) link is provided in an embodiment of this application;

[0020] Figure 2 A schematic diagram of an IoT service path provided in an embodiment of this application;

[0021] Figure 3This application provides a flowchart illustrating a method for determining the state of an Internet of Things (IoT) link.

[0022] Figure 4 This application provides another system diagram for determining the state of an IoT link.

[0023] Figure 5 This application provides a flowchart illustrating a method for determining the state of an Internet of Things (IoT) link.

[0024] Figure 6 This is a schematic diagram of an apparatus provided in an embodiment of this application;

[0025] Figure 7 A schematic diagram of an electronic device provided in an embodiment of this application;

[0026] Figure 8 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0028] The terms "first," "second," etc., used in this application's specification are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, in the specification, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0029] As described in the background section, to improve the quality of service to users, the status of IoT link connections is monitored. In related technologies, operators typically monitor the IoT link status on the core network side using KPI detection and data analysis methods to determine the IoT link status. KPI detection uses mathematical statistics, machine learning, or deep learning methods to analyze the KPIs of network elements to identify data mutations. However, due to the significant differences in behavior among different IoT devices and the poor regularity of network indicators—for example, meter reading terminals only go online when reporting data, while video production terminals are consistently online—these discrepancies and irregularities make it difficult for operators to use KPI detection to analyze IoT links, resulting in an inability to accurately determine the IoT link status.

[0030] Data analysis methods require collecting and storing signaling and data from IoT terminals, and using dedicated analysis systems to identify the IoT link status of individual users. The main drawbacks of data analysis methods are high resource consumption and time lag.

[0031] In practical applications, 3G, 4G, and 5G mobile communication networks are widely used as communication networks for the Internet of Things (IoT), and 6G mobile communication networks will also support more IoT terminals and applications. 3G and 4G mobile communication networks use one or more major Access Point Names (APNs) to manage all IoT terminals and services, while 5G IoT manages individual IoT devices using Data Network Names (DNNs), enabling the development of more granular Quality of Service (QoS) and access control policies for different enterprises and applications; that is, IoT management and operation are gradually being refined from the network element level to the DNN level.

[0032] Most IoT systems managed by Data Networks (DNNs) are characterized by a smaller number of terminals than human networks, high location aggregation, and concentrated business activities. For example, IoT services in a certain industrial park, mining area, or port may have only a few hundred terminals, concentrated locations, simple business actions, and a small number of data servers providing services.

[0033] It should be noted that the Internet of Things (IoT) in this application refers to a specific network serving a certain enterprise or a certain business of an enterprise, which has a corresponding DNN in the mobile core network. Under this business model, the operation and maintenance management of IoT needs to be further refined to the DNN or APN level based on the original network element level. When providing devices, functions and services, the DNN dimension needs to be considered, and it is not excluded that more refined dimensions, such as business dimensions or terminal dimensions, may be provided when applying AI technology or 6G technology.

[0034] This application provides a method, apparatus, device, storage medium, and computer program product for determining the state of an Internet of Things (IoT) link. It obtains characteristic data of IoT service messages according to the IoT data network name, and determines the state of the message transmission link based on the source address, destination address, and message direction in the characteristic data. Then, based on the state of the message transmission link, it sends a probe message to the peer device of the message transmission link to perform link probing. It then checks whether a response message is received from the peer device. If a response message is received, the IoT link state is determined to be normal (i.e., the target state); if no response message is received, the IoT link state is determined to be abnormal. This application embodiment can detect whether an IoT link is abnormal. This application embodiment can accurately determine the IoT link state.

[0035] The methods, apparatus, devices, storage media, and computer program products for determining the status of IoT links provided in this application can be applied to scenarios such as daily IoT link monitoring, IoT link adjustment monitoring, developing new services based on the geographical location of IoT terminals, and developing services based on the access range of IoT services.

[0036] The technical solution of this application will now be described in detail with reference to the accompanying drawings. First, referring to the accompanying drawings... Figure 1 The system for determining the IoT link status in the embodiments of this application is described, such as... Figure 1 As shown, the system includes:

[0037] The Radio Access Network (RAN) primarily controls user equipment's wireless access to the mobile communication network. The RAN is a wireless network. Communication between the RAN and the UPF (User Provider Grid) uses IP and is defined by 3GPP as the N3 interface. The Layer 3 link between the RAN-side peer node and the UPF is an N3 link.

[0038] User Plane Function (UPF) network elements provide data forwarding channels and execute control policies for terminals. UPF network elements are virtualized network elements. User Plane Function (UPF) network elements can also be called user plane UPF devices.

[0039] A Data Network (DN) is a data network that provides data services. The connection between the DN and the UPF is defined as an N6 interface, which can communicate via IP or VPN. The Layer 3 link between the UPF and the DN-side peer node is an N6 link.

[0040] When an IoT terminal performs services, data is transmitted bidirectionally between the RAN, UPF, and DN. The service path defined in this application consists of the IP address of the RAN-side base station equipment and the IP address of the DN-side data node. Each service path includes two links, N3 and N6. For example... Figure 2 As shown, Figure 2 The medium-thick N3 and N6 links constitute a business path for the Internet of Things.

[0041] exist Figure 1 The system provided for determining the status of IoT links can perform [the following actions]. Figure 3 The method shown is for determining the status of an IoT link. For example... Figure 3 As shown, the subject executing this method can be a UPF. This method may include steps S110 to S130.

[0042] S110. Obtain the characteristic data of the IoT service message according to the data network name of the IoT. The characteristic data includes the source address and the destination address.

[0043] S120. Determine the status of the message transmission link based on the source address, destination address, and message transmission direction.

[0044] S130. Send a probe message to the peer device of the message transmission link based on the status of the message transmission link.

[0045] S140. Upon receiving a response message from the peer device of the message transmission link, determine the state of the IoT link as the target state.

[0046] In S110, such as Figure 1 As shown, the UPF device retrieves IoT service packets transmitted bidirectionally between the Radio Access Network (RAN) device and the Data Network (DN) device according to the data network name. These packets can be IP packets. The IP packet can include a tuple containing a source address and a destination address. For example, if the IP packet is sent from the RAN to the data network device, the source address is the address of the base station in the RAN, and the destination address is the address of the data network device. If the IP packet is sent from the data network device to the base station in the RAN, the source address is the address of the data network device, and the destination address is the address of the base station in the RAN.

[0047] In S120, the UPF device determines the message transmission link for IoT service messages based on the source and destination addresses, such as the N3 link or the N6 link. Then, the UPF device senses whether the IoT service message is received via the N3 interface, sent via the N3 interface, received via the N6 interface, or sent via the N6 interface, thus determining the message transmission direction. If the UPF device senses that the IoT service message is received via the N3 interface, the message transmission direction is from the RAN-side device to the UPF device; if the UPF device senses that the IoT service message is sent via the N3 interface, the message transmission direction is from the UPF device to the RAN-side device; if the UPF device senses that the IoT service message is received via the N6 interface, the message transmission direction is from the DN-side device to the UPF device; if the UPF device senses that the IoT service message is sent via the N6 interface, the message transmission direction is from the UPF device to the DN-side device.

[0048] Then, the state of the message transmission link is determined based on the message transmission direction. If the UPF device senses IoT service messages received through the N3 interface, the state of the message transmission link from the RAN side device to the UPF device is determined based on the message transmission direction from the RAN side device to the UPF device. If the UPF device senses IoT service messages sent through the N3 interface, the state of the message transmission link from the UPF device to the RAN side device is determined based on the message transmission direction from the UPF device to the RAN side device. If the UPF device senses IoT service messages received through the N6 interface, the state of the message transmission link from the DN side device to the UPF device is determined based on the message transmission direction from the DN side device to the UPF device. If the UPF device senses IoT service messages sent through the N6 interface, the state of the message transmission link from the UPF device to the DN side device is determined based on the message transmission direction from the UPF device to the DN side device.

[0049] For example, if the UPF device receives an IoT service message from the RAN-side device via the N3 interface, the N3 link from the RAN-side device to the UPF device is determined to be active. If the UPF device receives an IoT service message from the DN-side device via the N6 interface, the N6 link from the DN-side device to the UPF device is determined to be active. If the UPF device does not receive an IoT service message via the N3 interface, the N3 link from the RAN-side device to the UPF device is inactive. If the UPF device does not receive an IoT service message via the N6 interface, the N6 link from the DN-side device to the UPF device is inactive.

[0050] In one embodiment, after S120, i.e. after determining the state of the message transmission link based on the source address, destination address, and message transmission direction, the method may further include:

[0051] Add the link information, status, and time of occurrence of the message transmission link to the link table. The link information identifies which link it is.

[0052] Specifically, after the UPF device obtains the IoT service message, it determines the service path, message transmission direction, and the status of the N3 link and the N6 link based on the source address and destination address in the IoT service message. Then, the UPF device will add or update the service path table and the link table.

[0053] In one example, if the UPF device detects that the service path table and link table have not been created, the UPF device will create the path table and link table after receiving the IoT service message. The link table includes the N3 link table and the N6 link table. Both the path table and the link table are full tables.

[0054] In one example, if the UPF device detects that a service path table and a link table have been created, the UPF device updates the path table and link table after receiving the IoT service message.

[0055] To illustrate how to update the link table, take updating the link table as an example: When the UPF device detects that the link table includes the link information of the message transmission link, that is, when the UPF detects that the link table includes the link, it updates the status of the message transmission link corresponding to the link in the link table, as well as the time when the status of the message transmission link occurred.

[0056] If the UPF device detects that a link information for a message transmission link is not included in the link table, that is, the UPF detects that the link table does not include the link, it adds the link information, the status of the message transmission link, and the time when the status of the message transmission link occurred to the link table. In one embodiment, the UPF device can periodically update the service path table and the link table, which can be configured to update once every preset time interval. Specifically, after determining the status of the message transmission link based on the source address, destination address, and message transmission direction, the method may further include:

[0057] The status of the message transmission link is detected at preset intervals to obtain the status of the detected message transmission link; the link table is updated based on the status of the detected message transmission link and the time when the detected message transmission link status occurs.

[0058] In one example, the preset duration can be 3 minutes. Specifically, the UPF device can check the link table (N3 link table and N6 link table) at preset intervals, change the status of the active packet transmission link in the link table to the inactive status, and then probe all inactive packet transmission links in the link table to obtain the status of the packet transmission path. Based on the status of the packet transmission link obtained from the probe and the time when the status of the packet transmission link occurred, the link table is updated.

[0059] In S130, the link is probed based on the status of the message transmission link, and the UPF device sends probe messages to the peer device of the message transmission link.

[0060] In this embodiment, the detection mechanism is not limited, and the UPF device can detect the message transmission link based on the configured adaptive detection mechanism.

[0061] In one embodiment, the UPF device can promptly probe the message transmission link after determining its status.

[0062] In one example, the UPF device can probe both inactive and active packet transmission links, or it can probe only inactive packet transmission links to improve probe efficiency.

[0063] In one embodiment, the UPF device can manually trigger probing of inactive message transmission links. Specifically, sending a probe message to the peer device of the message transmission link based on its state can include:

[0064] Receive the first input; in response to the first input, send a probe message to the peer device of the message transmission link based on the status of the message transmission link.

[0065] Users can input information through the UPF device's control page—the first input—which can be a probe command entered on the control page, a touch probe control, or a press probe button, to trigger the probe of the message transmission link. Upon receiving the first input, the UPF device responds by sending a probe message to the peer device of the inactive message transmission link to perform the probe. This manually triggered probe method improves the flexibility of IoT link probing, meets user needs, and enhances the user experience.

[0066] In one embodiment, the UPF device can also periodically probe inactive message transmission links.

[0067] In S140, if the UPF device receives a response message from the peer device of the message transmission link, it determines that the IoT link is in a normal state, i.e., a normal communication state, i.e., the target state. If the UPF device does not receive a response message from the peer device of the message transmission link within the set detection time, it determines that the IoT link is in an abnormal state.

[0068] In this embodiment, the user plane device obtains the characteristic data of IoT service packets according to the IoT data network name, and determines the state of the packet transmission link based on the source address, destination address, and packet direction in the characteristic data. Then, based on the state of the packet transmission link, it sends a probe packet to the peer device of the packet transmission link to perform link probing. Upon receiving a response packet from the peer device of the packet transmission link, the state of the IoT link is determined to be normal, i.e., the target state. This embodiment can accurately determine the state of the IoT link; moreover, the UPF device itself can determine the state of the IoT link without the need for other auxiliary systems to analyze the IoT link state, enabling timely determination of the IoT link state while reducing resource consumption.

[0069] In one embodiment, an IoT link alarm message is output when an anomaly in the message transmission link is detected.

[0070] In one embodiment, the method may further include:

[0071] Delete information about message transmission links in the link table that exceed a preset time interval. The information includes the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurred.

[0072] The interval duration is the time interval between the change in the status of the message transmission link and the current time. For example, the UPF device checks the link table at the current time and deletes the link information, status, and time of the change in the message transmission link that are a preset time (T0) away from the current time.

[0073] In one embodiment, the link information, status of the message transmission link, and time of occurrence of the inactive and / or active status of the message transmission link that are inactive for a period of time T0 from the current time are deleted from the link table.

[0074] In one example, a UPF device can delete information about message transmission links that have been inactive for more than one hour.

[0075] In one example, a UPF device can delete information about message transmission links that have been active for more than 3 minutes.

[0076] In one example, a UPF device can delete information about active and inactive message transmission links that have been active for more than 15 minutes.

[0077] In this embodiment, the UPF device deletes information about message transmission links of a certain duration from the link table, reducing the size and capacity of the table and the resources required to store the link table.

[0078] In one embodiment, the characteristic data of the IoT service may further include the address of the tunnel endpoint; the method may further include:

[0079] Probe is performed based on the address of the tunnel endpoint; upon receiving a response message from the tunnel endpoint, the state of the IoT link is determined to be the target state.

[0080] In this embodiment, the IoT is configured with a tunnel endpoint address, for example, the IoT is configured with a GRE / L2TP / IPSec tunnel endpoint. The UPF device extracts the tunnel endpoint address from the IoT service packets and probes the IoT link based on the tunnel endpoint address. If a response packet from the IoT tunnel endpoint is received, the IoT link is determined to be in a normal state, i.e., the target state. If no response packet from the IoT tunnel endpoint is received within a preset probe time, the IoT link is determined to be in an abnormal state.

[0081] In this embodiment, the UPF device can probe the message transmission link based on the status of the message transmission link determined by the IoT service message, or it can probe the message transmission link based on the address of the configured tunnel endpoint, thus performing dual probes on the message transmission link and improving the accuracy of determining the IoT link status.

[0082] In one embodiment, the method may further include:

[0083] UPF devices do not probe packet transmission links on packet transmission paths that have been blocked from ping, in order to improve probe efficiency.

[0084] In one embodiment, the UPF device can also stop detecting IoT links that have already been detected as normal, in order to improve detection efficiency.

[0085] In one embodiment, the method may further include:

[0086] The UPF device receives a second input, which includes the data network name;

[0087] In response to the second input, the UPF device outputs the link information of the message transmission link corresponding to the data network name, the status of the message transmission link, and the time when the status of the message transmission link occurred.

[0088] Specifically, the device receives a second input from the control interface of the UPF device, which may include the data network name; in response to the second input, it outputs the link information of the message transmission link corresponding to the data network name.

[0089] In one embodiment, in response to the second input, path information of the service path corresponding to the data network name can also be output.

[0090] In one embodiment, after receiving the second input, the link information of the message transmission link corresponding to the data network name and / or the path information of the service path can be output periodically, thereby improving the acquisition efficiency.

[0091] In this embodiment, link information of the message transmission link and / or path information of the service path are output based on user requirements, so as to develop and apply the service path based on the link information of the message link and / or path information of the service path.

[0092] In one embodiment, the method may further include:

[0093] Obtain business metrics for mobile network functions and IoT applications.

[0094] The status of IoT services is determined based on service metrics of mobile network functions and the corresponding first service metric thresholds; and / or, the status of IoT services is determined based on service metrics of IoT applications and the corresponding second service metric thresholds.

[0095] In this embodiment, the status of IoT services can also be determined. Service metrics for mobile network functions and IoT applications are acquired, and these metrics can be configured according to the specific service to be identified. For example, to determine the communication quality of IoT services, service metrics can be configured as message transmission delay, out-of-order ratio, retransmission ratio, etc.; as another example, to determine the service access status in IoT services, service metrics can be configured as session creation success rate, creation request frequency, service duration, etc.; as yet another example, to identify the service quality of IoT applications, service metrics can be configured as IoT application service quality KPIs.

[0096] The UPF device compares the service metrics of the mobile network function with the corresponding first service metric threshold to determine the status of the IoT service. If the service metrics of the mobile network function meet the first service metric threshold conditions corresponding to the normal state of the IoT service, the IoT service is considered to be in a normal state. If the service metrics of the mobile network function meet the first service metric threshold conditions corresponding to the abnormal state of the IoT service, the IoT service is considered to be in an abnormal state. For example, to determine call quality, the service metric is message transmission delay, and the first service metric threshold is 0.01 seconds. When the message transmission delay is greater than 0.01 seconds, the call quality is considered poor, that is, the IoT service is in an abnormal state.

[0097] The UPF device compares the service metrics of the IoT application with the corresponding second service metric thresholds to determine the status of the IoT service. If the service metrics of the IoT application meet the second service metric threshold conditions corresponding to the normal status of the IoT service, the IoT service is considered to be in a normal state. If the service metrics of the mobile network function meet the second service metric threshold conditions corresponding to the abnormal status of the IoT service, the IoT service is considered to be in an abnormal state.

[0098] UPF devices can determine the status of IoT services beyond just the status of the IoT link, demonstrating the scalability of IoT services.

[0099] In one embodiment, if the status of an IoT service is determined to be abnormal, an IoT service alarm message is output.

[0100] In one embodiment, such as Figure 4 As shown, systems for determining the status of IoT links also include:

[0101] Operation and Management (OAM) systems are used to maintain and manage core network elements and the network itself. OAM systems can also be called OAM devices. OAM refers to virtualized network elements.

[0102] In one embodiment, OAM can be integrated into the UPF device or exist independently of the UPF device.

[0103] exist Figure 4 The system shown can perform the following actions to determine the state of an IoT link: Figure 5 The method shown is for determining the status of an IoT link, such as Figure 5 As shown, before determining the state of the IoT link as the target state upon receiving a response message from the peer device of the message transmission link, i.e. before S140, the method may further include steps S150 to S170.

[0104] S150, the UPF device sends a link table to the OAM device. The link table includes link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurs.

[0105] S160, OAM device update link table.

[0106] S170, the UPF device receives probe information sent by the OAM device, and uses this probe information to probe inactive message transmission links.

[0107] In S150, the UPF sends a link table to the OAM device, which includes the N3 link table and the N6 link table.

[0108] Specifically, the UPF device announces the N3 and N6 links, as well as the status of the N3 and N6 links, to the OAM device.

[0109] In one embodiment, the UPF device can also notify the OAM device of the service path and the status of the service path.

[0110] In one embodiment, the UPF device can periodically (e.g., at intervals of T1) send the link table and service path table, as well as the status of the message transmission link and the service path, to the OAM device.

[0111] Specifically, the UPF device can be set based on the required interval duration T1. In one example, the interval duration can be 5 minutes.

[0112] In another embodiment, the UPF can periodically (e.g., every 10 minutes) send incremental data, including the acquired service path and message transmission link information (N3 and N6 links), as well as the status of the service path and message transmission links (N3 and N6 links), to the OAM device. By sending incremental data to the OAM device, the amount of data transmission is reduced, which can reduce network congestion.

[0113] In S160, after receiving the advertisement messages (N3 link table and N6 link table) sent by the UPF device, the OAM device parses each N3 link and N6 link, determines the status of the message transmission link based on the message direction, where the status of a message transmission link that is sending a message is active, and the status of a link that is not sending a message is inactive. The OAM device then updates the status of the message transmission link and the time when the status occurred in the N3 link table and N6 link table, respectively. Compared to the N3 link table and N6 link table stored by the OAM device, if the N3 link table and N6 link table sent by the UPF device to the OAM device include the link information of a newly added message transmission link, the status of the newly added message transmission link, and the time when the status occurred, then the OAM device adds the link information, the status of the newly added message transmission link, and the time when the status occurred to the N3 link table and N6 link table. Among them, the N3 link table and N6 link table in the OAM device are both full tables.

[0114] For message transmission links that were in the ACTIVE state in the previous notification period but were not reported in the current period or were reported as DETECT in the current period, set them to the DETECT state. Then, notify the UPF device to probe the message transmission links in the DETECT state in the link table; set the message transmission links with normal communication to the CONNECT state, set the message transmission links with abnormal communication to the ALARM state, and issue an alarm for the message transmission links in the ALARM state.

[0115] In one embodiment, the OAM device may also delete information about alarm status links or connection status links that have exceeded T3 duration.

[0116] Specifically, the OAM device can delete links and service paths in the CONNECT and ALARM states that have exceeded a certain duration (e.g., T3 = 1 hour) to prevent the service path table, N3 link table, and N6 link table from expanding indefinitely and to reduce the resource space required to store the link table and service path table.

[0117] In S160, the OAM device notifies the UPF device to probe the message transmission links in the DETECT state in the link table. The specific process is as follows: the OAM device sends probe information to the UPF device, which includes link information for inactive message transmission links, to notify the UPF device to probe the inactive links in the link table. The inactive message transmission links can be either N3 or N6 links.

[0118] In S170, the UPF device receives the probe information sent by the OAM device and probes the inactive message transmission link based on the probe information, that is, sends a probe message to the peer device of the inactive message transmission link, and then executes S140.

[0119] In S140, the UPF device detects whether a response message can be received within a certain detection period. If a response message is received from the peer device of the message transmission link within the detection period, the IoT link is determined to be in normal condition; if no response message is received from the peer device of the message transmission link within the detection period, the IoT link is determined to be in abnormal condition. This embodiment of the application can accurately determine the state of the IoT link.

[0120] An alarm is triggered for IoT links exhibiting abnormal status. In one embodiment, the UPF device sends an IoT link alarm message to the OAM device.

[0121] In one embodiment, the method may further include:

[0122] The OAM device receives a third input, which may include the data network name;

[0123] In response to the third input, the OAM device outputs the link information of the message transmission link corresponding to the data network name, the status of the message transmission link, and the time when the status of the message transmission link occurred.

[0124] Specifically, the device receives a third input from the control interface of the OAM device, which may include the data network name; in response to the third input, it outputs the link information of the message transmission link corresponding to the data network name.

[0125] In one embodiment, path information of the service path corresponding to the data network name can also be output in response to a third input.

[0126] In one embodiment, after receiving a third input, the link information of the message transmission link corresponding to the data network name and / or the path information of the service path can be output periodically, thereby improving the acquisition efficiency.

[0127] In this embodiment, link information of the message transmission link and / or path information of the service path are output based on user requirements, so as to develop and apply the service path based on the link information of the message link and / or path information of the service path.

[0128] In one embodiment, after the OAM device determines the status of the N3 link and the N6 link, the method may further include:

[0129] The OAM device determines the status of the message transmission service link based on the status of the N3 link and the status of the N6 link;

[0130] When the service link is in an alarm state, the OAM device probes the service link in the alarm state to obtain the probe results, and determines whether to issue an alarm based on the probe results; wherein, the alarm state is a state in which no messages are sent.

[0131] Specifically, the OAM device periodically probes the message transmission links in the ALARM state. In one example, the OAM device probes the message transmission links in the ALARM state at a preset interval (e.g., 5 minutes). Message transmission links with normal communication are set to the CONNECT state, and message transmission links with abnormal communication are set to the ALARM state, and an alarm is generated for message transmission links in the ALARM state.

[0132] In one embodiment, the method may further include:

[0133] When the service link is in the connected state, the service link in the connected state is probed to obtain the probe results, and an alarm is determined based on the probe results; the connected state is the state in which messages are sent.

[0134] Specifically, the OAM device periodically probes the message transmission link of the connection status.

[0135] In one example, the OAM device probes the message transmission links in the CONNECT state at a preset interval (e.g., 20 minutes). Message transmission links with normal communication are set to the CONNECT state, while message transmission links with abnormal communication are set to the ALARM state, and an alarm is issued for message transmission links in the ALARM state.

[0136] The above embodiments all realize the parsing of the DNN's service path and the detection of N3 and N6 links, automatically identifying and presenting communication anomalies. This application does not limit the specific detection method; to effectively detect link status, multiple detection methods can be used simultaneously for a single message transmission link, and different detection methods can be used for different message transmission links. For example, for an N3 link, one can simultaneously PING the RAN-side base station IP address and send GTPU ECHO, or PING the IP address for one DN while using the GRE tunnel self-detection mechanism for another DN.

[0137] It should be noted that, Figures 1 to 5The embodiments described herein use only the data network name dimension as an example to illustrate the determination of IoT link status. The inventive concept of obtaining feature data of IoT service messages according to the data network name and determining IoT link status based on feature data provided in the embodiments of this application is also applicable to the service type dimension and the terminal dimension.

[0138] The service type dimension and terminal dimension can be based on the characteristics of TCP / IP network protocol messages. For example, it can be used for identifying anomalies in IoT services.

[0139] This application is not limited to determining the status of IoT links; it can also be applied to identifying poor-quality IoT devices within the same type of IoT service, or identifying poor-quality users within a specific IoT system. Here, "IoT devices with the same type of service," also known as "similar IoT devices," refers to IoT devices with similar or identical services. Examples of IoT devices with similar services include electricity meter reading IoT devices or gas meter reading IoT devices.

[0140] In the embodiments of this application, the selection of features can be based on the specific service anomalies to be identified. For example, to identify IoT devices with link anomalies, the status of the communication path and link is selected as features; to identify IoT devices with poor quality (such as communication quality) among similar IoT devices, features such as message transmission delay, out-of-order ratio, and retransmission ratio are selected; to identify poor-quality users in IoT devices, features such as session creation success rate, creation request frequency, and service duration are selected; and to identify poor-quality terminals in IoT devices, terminal service quality KPIs are selected as features.

[0141] It should be noted that to identify low-quality (e.g., poor communication quality) IoT devices within the same IoT category, features such as message transmission latency, out-of-order ratio, and retransmission ratio can be selected and obtained at the core network side using a Data Neural Network (DNN) as the dimension. Similarly, to identify low-quality users within the IoT category, features such as session creation success rate, session creation request frequency, and service duration can be selected and obtained at the core network side using a single-user dimension.

[0142] In this embodiment, the logic for identifying business anomalies can be based on business domain knowledge or artificial intelligence algorithms. The specific business anomaly identification logic and algorithm are not limited in this embodiment.

[0143] In one embodiment, to identify low-quality (e.g., poor communication quality) IoT devices within the same IoT category, after selecting features such as message transmission delay, out-of-order ratio, and retransmission ratio, an algorithm can be used to compare and analyze these features of similar DNNs to identify low-quality IoT devices.

[0144] In one embodiment, to identify low-quality users in the Internet of Things (IoT), after selecting features such as session creation success rate, creation request frequency, and service duration, algorithms can be used to compare and analyze these features of DNN terminals to identify low-quality users.

[0145] Based on the same inventive concept, embodiments of this application also provide a device for identifying anomalies in IoT service communication links, see details below. Figure 6 .

[0146] Figure 6 This is a schematic diagram of a device for identifying anomalies in an IoT communication link, provided in an embodiment of this application. Figure 6 As shown, this device is applied to a UPF device. The device 200 may include an acquisition unit 210, a determination module 220, and a transmission module 230.

[0147] The acquisition module 210 is used to acquire the feature data of IoT service messages according to the data network name of the IoT. The feature data includes the source address and the destination address.

[0148] The determination module 220 is used to determine the status of the message transmission link based on the source address, destination address and message transmission direction.

[0149] The sending module 230 is used to send probe messages to the peer device of the message transmission link based on the status of the message transmission link.

[0150] The determination module 240 is also used to determine the state of the IoT link as the target state when it receives a response message sent by the peer device of the message transmission link.

[0151] Therefore, the device obtains the characteristic data of IoT service messages according to the IoT data network name, and determines the status of the message transmission link based on the source address, destination address, and message direction in the characteristic data. Then, based on the status of the message transmission link, it sends a probe message to the peer device of the message transmission link to perform link probing. Upon receiving a response message from the peer device of the message transmission link, the device determines that the IoT link status is normal, i.e., the target status. This embodiment of the application can accurately determine the status of the IoT link; moreover, the user plane device itself can determine the status of the IoT link without the need for other auxiliary systems to analyze the IoT link status, enabling timely determination of the IoT link status while reducing resource consumption.

[0152] In one embodiment, the device may further include: a processing module 240: for adding the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurs to a link table, so as to maintain the status of the message transmission link based on the link table, and to probe the message transmission link based on the status of the message transmission link, so as to further determine the status of the IoT link.

[0153] In one embodiment, the processing module 240 is further configured to:

[0154] The status of the message transmission link is detected at preset intervals to obtain the status of the message transmission link after the detection.

[0155] The link table is updated based on the status of the detected message transmission link and the time when the detected message transmission link status occurs.

[0156] Further maintain the link table to facilitate further determination of the IoT link status of the message transmission link based on the status of the message transmission link in the link table.

[0157] In one embodiment, the processing module 240 is further configured to:

[0158] Delete information about message transmission links in the link table whose interval exceeds a preset time. The information includes the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurred; where the interval is the time interval between the time when the status of the message transmission link changes and the current time.

[0159] Deleting information about message transmission links of a certain duration from the link table reduces the size and capacity of the table, and reduces the resources required to store the link table.

[0160] In one embodiment, the device may further include a receiving module 250.

[0161] The receiving module 250 is used to receive the first input.

[0162] The sending module 230, in response to the first input, sends a probe message to the peer device on the message transmission link based on the status of the message transmission link. This method of manually triggering the probe improves the flexibility of IoT link probing, meets user needs, and enhances the user experience.

[0163] Furthermore, in one embodiment, the feature data also includes the address of the tunnel endpoint.

[0164] The sending module 230 is also used to perform probing based on the address of the tunnel endpoint in order to send a probe message to the address of the tunnel endpoint.

[0165] The determination module 240 is also used to determine the state of the IoT link as the target state upon receiving a response message from the tunnel endpoint.

[0166] The device can detect the message transmission link based on the status of the message transmission link determined by the IoT service message, or it can detect the message transmission link based on the address of the configured tunnel endpoint, thus performing dual detection of the message transmission link and improving the accuracy of determining the status of the IoT link.

[0167] Furthermore, in one embodiment, the device may also include an output module 270.

[0168] The receiving module 250 is also used to receive a second input, which includes the data network name;

[0169] In response to the second input, the output module 270 outputs the link information of the message transmission link corresponding to the data network name, the status of the message transmission link, and the time when the status of the message transmission link occurs.

[0170] Based on user requirements, output link information of message transmission links and / or path information of service paths, so as to develop and apply service paths based on the link information of message links and / or path information of service paths.

[0171] In one embodiment, the acquisition module 210 is further configured to acquire service metrics of mobile network functions and service metrics of Internet of Things applications.

[0172] The determining module 240 is further configured to determine the status of the IoT service based on service metrics of the mobile network function and a first service metric threshold corresponding to the service metrics of the mobile network function; and / or,

[0173] The determination module 240 is also used to determine the status of IoT services based on the business metrics of IoT applications and the second business metric thresholds corresponding to the business metrics of IoT applications.

[0174] The device can also determine the status of IoT services, demonstrating its ability to improve the scalability of IoT services.

[0175] Figure 6 The various modules in the device shown for identifying anomalies in IoT service communication links can achieve... Figure 3 The functions of the UPF device and the corresponding effects will be described briefly and will not be elaborated here.

[0176] In some embodiments, such as Figure 7As shown, this application embodiment also provides an electronic device 300, including a processor 310 and a memory 320. The memory 320 stores a program or instructions that can run on the processor 310. When the program or instructions are executed by the processor 310, they implement the various steps of the above-described embodiment of determining the IoT link status and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0177] It should be noted that the electronic devices in the embodiments of this application include mobile electronic devices and non-mobile electronic devices.

[0178] Figure 8 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0179] The electronic device 400 includes, but is not limited to, components such as: radio frequency unit 401, network module 402, audio output unit 403, input unit 404, sensor 405, display unit 406, user input unit 407, interface unit 408, memory 409, and processor 410.

[0180] Those skilled in the art will understand that the electronic device 400 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 410 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0181] In this embodiment, the processor 410 is configured to obtain feature data of IoT service messages according to the data network name of the IoT, the feature data including source address and destination address; the processor 410 is also configured to determine the state of the message transmission link based on the source address, destination address and message transmission direction; the radio frequency unit 401 is configured to send a probe message to the peer device of the message transmission link based on the state of the message transmission link; when the radio frequency unit 401 receives a response message sent by the peer device of the message transmission link, the processor 410 is configured to determine the state of the IoT link as the target state.

[0182] The electronic device 400 is described in detail below:

[0183] In some embodiments of this application, the processor 410 is further configured to add the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurs to the link table.

[0184] In some embodiments of this application, the processor 410 is further configured to detect the status of the message transmission link at preset intervals to obtain the detected status of the message transmission link; and update the link table based on the detected status of the message transmission link and the time when the detected status of the message transmission link occurs.

[0185] In some embodiments of this application, the processor 410 is further configured to delete information of message transmission links in the link table whose interval exceeds a preset time. The information includes the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurred; wherein, the interval is the time interval between the time when the status of the message transmission link changes and the current time.

[0186] In some embodiments of this application, the radio frequency unit 401 is used to send a probe message to the peer device of the message transmission link based on the status of the message transmission link, specifically including:

[0187] Input unit 404 is used to receive the first input.

[0188] In response to the first input, the radio frequency unit 401 sends a probe message to the peer device of the message transmission link based on the status of the message transmission link.

[0189] In some embodiments of this application, the feature data also includes the address of the tunnel endpoint.

[0190] The radio frequency unit 401 is also used for probing based on the address of the tunnel endpoint.

[0191] When the radio frequency unit 401 receives a response message from the tunnel endpoint, the processor 410 determines that the state of the IoT link is the target state.

[0192] In some embodiments of this application, the input unit 404 is also configured to receive a second input, which includes a data network name.

[0193] In response to the second input, the display unit 406 outputs the link information of the message transmission link corresponding to the data network name, the status of the message transmission link, and the time when the status of the message transmission link occurred.

[0194] In some embodiments of this application, the processor 410 is also used to obtain service metrics of mobile network functions and service metrics of Internet of Things applications.

[0195] The processor 410 is also used to determine the status of the Internet of Things (IoT) service based on service metrics of mobile network functions and a first service metric threshold corresponding to the service metrics of mobile network functions; and / or, to determine the status of the IoT service based on service metrics of IoT applications and a second service metric threshold corresponding to the service metrics of IoT applications.

[0196] The user plane device obtains the characteristic data of IoT service packets according to the IoT data network name, and determines the status of the packet transmission link based on the source address, destination address, and packet direction in the characteristic data. Then, based on the status of the packet transmission link, it sends a probe packet to the peer device of the packet transmission link to perform link probing. Upon receiving a response packet from the peer device of the packet transmission link, the status of the IoT link is determined to be normal, i.e., the target status. This embodiment of the application can accurately determine the status of the IoT link; moreover, the user plane device itself can determine the status of the IoT link without the need for other auxiliary systems to analyze the IoT link status, enabling timely determination of the IoT link status while reducing resource consumption.

[0197] It should be understood that the input unit 404 may include a graphics processing unit (GPU) 4041 and a microphone 4042. The GPU 4041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 406 may include a display panel, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 407 includes at least one of a touch panel 4071 and other input devices 4072. The touch panel 4071 is also called a touch screen. The touch panel 4071 may include a touch detection device and a touch display. Other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume display buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0198] The memory 409 can be used to store software programs and various data. The memory 409 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 409 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 409 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0199] Processor 410 may include one or more processing units; in one embodiment, processor 410 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless display signals, such as a baseband processor. It is understood that the modem processor may also not be integrated into processor 410.

[0200] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method embodiment for determining the state of an IoT link and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0201] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0202] In addition, this application embodiment provides another chip, which includes a processor and a display interface. The display interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described method embodiment for determining the state of the Internet of Things link, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0203] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0204] This application provides a computer program product stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-described embodiment for determining the state of an Internet of Things link, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0205] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0206] Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0207] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0208] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the above-described embodiments. The above-described embodiments are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining the state of an Internet of Things (IoT) link, characterized in that, include: The characteristic data of IoT service messages are obtained according to the data network name of the IoT, and the characteristic data includes the source address and the destination address. The state of the message transmission link is determined based on the source address, the destination address, and the message transmission direction; Based on the status of the message transmission link, a probe message is sent to the peer device of the message transmission link; Upon receiving a response message from the peer device of the message transmission link, the state of the IoT link is determined to be the target state.

2. The method according to claim 1, characterized in that, After determining the state of the message transmission link based on the source address, the destination address, and the message transmission direction, the method further includes: Add the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurred to the link table.

3. The method according to claim 2, characterized in that, After determining the state of the message transmission link based on the source address, the destination address, and the message transmission direction, the method further includes: The status of the message transmission link is detected at preset intervals to obtain the detected status of the message transmission link. The link table is updated based on the detected state of the message transmission link and the time when the detected state of the message transmission link occurs.

4. The method according to claim 2, characterized in that, The method further includes: Delete information about message transmission links in the link table whose interval exceeds a preset time. The information includes the link information of the message transmission link, the status of the message transmission link, and the time when the status of the message transmission link occurred; wherein, the interval is the time interval between the time when the status of the message transmission link changes and the current time.

5. The method according to claim 1, characterized in that, Sending probe messages to the peer device of the message transmission link based on the status of the message transmission link includes: Receive the first input; In response to the first input, a probe message is sent to the peer device of the message transmission link based on the state of the message transmission link.

6. The method according to any one of claims 1 to 5, characterized in that, The feature data also includes the address of the tunnel endpoint; the method further includes: Detection is performed based on the address of the tunnel endpoint; Upon receiving a response message from the tunnel endpoint, the state of the IoT link is determined to be the target state.

7. The method according to claim 2, characterized in that, The method further includes: Receive a second input, which includes the data network name; In response to the second input, the link information of the message transmission link corresponding to the data network name, the status of the message transmission link, and the time when the status of the message transmission link occurred are output.

8. The method according to claim 1, characterized in that, The method further includes: Obtain business metrics for mobile network functions and IoT applications; Based on service metrics of mobile network functions and the corresponding first service metric threshold, the status of the IoT service is determined; and / or, The status of the IoT service is determined based on the business metrics of the IoT application and the second business metric threshold corresponding to the business metrics of the IoT application.

9. A device, characterized in that, The device includes a processor and a memory, the memory storing programs or instructions that, when the processor executes the programs or instructions, implement the method for determining the state of an Internet of Things link as described in any one of claims 1-8.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the method for determining the state of an Internet of Things link as described in any one of claims 1-8.

11. A computer program product, characterized in that, The program product is stored in a storage medium and is executed by at least one processor to implement the method for determining the state of an Internet of Things link as described in any one of claims 1-8.

Images