Network element message-based device-card separation diagnosis method and system, device, and medium

Abstract

The present application discloses a network element message-based device-card separation diagnosis method and system, a device, and a medium. The method comprises: acquiring a SOAP session message of a target terminal in real time by means of an HSS / UDM network element, and uploading the SOAP session message to a connection management platform; acquiring a Radius session message of a target Internet of Things card in real time by means of a PGW / SMF network element, and uploading the Radius session message to the connection management platform; and determining a device-card binding state between the target terminal and the target Internet of Things card by means of the connection management platform on the basis of the SOAP session message and the Radius session message, and obtaining a device-card separation diagnosis result on the basis of the device-card binding state. The present application can meet high-concurrency device-card separation query requirements, improves the efficiency of device-card separation diagnosis, ensures the timeliness of device-card separation diagnosis, and can be widely applied to the technical field of Internet of Things.

Description

Machine-card separation diagnosis method, system, device and medium based on network element message Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a machine-card separation diagnosis method and system, device and medium based on network element messages. Background Art

[0002] According to IoT management and control requirements, IoT cards must be bound to the device. If the device is separated and the device is replaced, the card's use will be restricted. Due to the lack of unified standards for IoT terminals in industries such as intercoms and three-meter systems, unexplained device-card binding failures often occur. The IoT connection management platform provides device-card binding diagnosis and rebinding methods to improve operational efficiency for industry customers. Traditional device-card diagnosis solutions rely on HSS / UDM devices to query the device-card separation status, but these solutions cannot meet the requirements of batch and high-concurrency device-card separation queries. This results in customers being unable to obtain the device-card binding status in real time, impacting the efficiency and timeliness of device-card separation diagnosis. Summary of the Invention

[0003] The purpose of this application is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0004] To this end, one purpose of an embodiment of the present application is to provide a machine-card separation diagnosis method based on network element messages, which improves the efficiency of machine-card separation diagnosis and ensures the timeliness of machine-card separation diagnosis.

[0005] Another object of an embodiment of the present application is to provide a machine-card separation diagnostic system based on network element messages.

[0006] In order to achieve the above technical objectives, the technical solutions adopted in the embodiments of the present application include:

[0007] On the one hand, an embodiment of the present application provides a method for diagnosing machine-card separation based on network element messages, comprising the following steps:

[0008] Collect SOAP session messages of the target terminal in real time through HSS / UDM network elements, and upload the SOAP session messages to the connection management platform;

[0009] Collect the Radius session messages of the target IoT card in real time through the PGW / SMF network element, and upload the Radius session messages to the connection management platform;

[0010] The connection management platform determines the machine-card binding status of the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message, and obtains a machine-card separation diagnosis result according to the machine-card binding status.

[0011] Furthermore, in one embodiment of the present application, the machine-card separation diagnosis method further includes a step of binding the target terminal to the target IoT card, which specifically includes:

[0012] When the target IoT card is activated, the device-card binding security management function is started through the connection management platform;

[0013] When the target Internet of Things card goes online for the first time, the first IMEI information of the corresponding target terminal is recorded through the HSS / UDM network element, and the first IMEI information is sent to the connection management platform, so that the connection management platform binds the target terminal and the target Internet of Things card according to the first IMEI information.

[0014] Furthermore, in one embodiment of the present application, the step of determining the machine-card binding state between the target terminal and the target IoT card according to the SOAP session message and the Radius session message specifically includes:

[0015] Determine the device type and regional node of the target terminal according to the SOAP session message and the Radius session message, and extract service topology data of the target terminal and the target Internet of Things card;

[0016] Obtain terminal data information of the target terminal and obtain Internet of Things card data information of the target Internet of Things card;

[0017] The service topology data is analyzed in real time according to the terminal data information and the Internet of Things card data information to obtain the terminal status and the machine-card binding status.

[0018] Furthermore, in one embodiment of the present application, the machine-card separation diagnosis method further includes the following steps:

[0019] Storing the terminal status and the machine-card binding status in the connection management platform;

[0020] The terminal status query request and / or the machine-card binding status query request of the client application platform is received through the connection management platform, and the terminal status and / or the machine-card binding status is returned to the client application platform.

[0021] Furthermore, in one embodiment of the present application, the machine-card separation diagnosis method further includes the following steps:

[0022] Generate machine-card separation alarm information according to a preset rule engine and the machine-card binding status;

[0023] The machine-card separation alarm information is pushed to the client application platform through the connection management platform.

[0024] Furthermore, in one embodiment of the present application, the machine-card separation diagnostic method further includes the step of rebinding the target IoT card to the machine-card, which specifically includes:

[0025] When it is determined that the machine-card separation diagnosis result is that the machine-card has been separated, the PGW / SMF network element is used to monitor in real time whether the target IoT card is online again;

[0026] When the target IoT card comes online again, the second IMEI information of the corresponding re-bound terminal is obtained through the HSS / UDM network element, and the second IMEI information is sent to the connection management platform, so that the connection management platform binds the re-bound terminal to the target IoT card according to the second IMEI information.

[0027] Furthermore, in one embodiment of the present application, the machine-card separation diagnosis method based on network element messages further includes at least one of the following steps:

[0028] When it is determined that the machine-card separation diagnosis result is that the machine-card has been separated, determining whether a location change has occurred based on the SOAP session message, and if so, performing a regional diagnosis based on the SOAP session message and generating a dangerous area alarm, and then pushing the dangerous area alarm to the client application platform through the connection management platform;

[0029] The online and offline time of the target IoT card is determined according to the Radius session message, and an online and offline session alarm and / or a long-term offline alarm is generated according to the online and offline time, and then the online and offline session alarm and / or the long-term offline alarm is pushed to the client application platform through the connection management platform.

[0030] On the other hand, an embodiment of the present application provides a machine-card separation diagnostic system based on network element messages, including:

[0031] A SOAP session message collection module is used to collect SOAP session messages of the target terminal in real time through the HSS / UDM network element and upload the SOAP session messages to the connection management platform;

[0032] A Radius session message collection module is used to collect the Radius session messages of the target IoT card in real time through the PGW / SMF network element, and upload the Radius session messages to the connection management platform;

[0033] The machine-card separation diagnostic module is used to determine the machine-card binding status between the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message through the connection management platform, and obtain a machine-card separation diagnostic result according to the machine-card binding status.

[0034] On the other hand, an embodiment of the present application provides an electronic device, which includes a memory, a processor, a program stored on the memory and runnable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the machine-card separation diagnostic method based on network element messages as described above is realized.

[0035] On the other hand, an embodiment of the present application also provides a storage medium, which is a computer-readable storage medium for computer-readable storage. The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the machine-card separation diagnostic method based on network element messages as described above.

[0036] The advantages and benefits of this application will be partially given in the following description, and partially become apparent from the following description, or learned through practice of this application:

[0037] The embodiment of the present application collects the SOAP session messages of the target terminal in real time through the HSS / UDM network element, and uploads the SOAP session messages to the connection management platform, and then collects the Radius session messages of the target Internet of Things card in real time through the PGW / SMF network element, and uploads the Radius session messages to the connection management platform, and then determines the machine-card binding status of the target terminal and the target Internet of Things card based on the SOAP session messages and the Radius session messages through the connection management platform, and obtains the machine-card separation diagnosis result based on the machine-card binding status. The embodiment of the present application collects the SOAP session messages of the HSS / UDM network element and the Radius session messages of the PGW / SMF network element through the connection management platform, and judges the machine-card binding status of the target terminal and the target Internet of Things card based on the analysis of massive messages from multiple sources and heterogeneity, which can meet the requirements of high-concurrency machine-card separation queries, improve the efficiency of machine-card separation diagnosis, and ensure the timeliness of machine-card separation diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following introduction is made to the drawings required for use in the embodiments of the present application. It should be understood that the drawings introduced below are only for the convenience of clearly describing some embodiments of the technical solutions of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without any creative work.

[0039] FIG1 is a flow chart of a method for diagnosing machine-card separation based on network element messages according to an embodiment of the present application;

[0040] FIG2 is a flowchart of binding a target terminal to a target IoT card according to an embodiment of the present application;

[0041] FIG3 is a flow chart of step S103 provided in an embodiment of the present application;

[0042] FIG4 is another flow chart of step S103 provided in an embodiment of the present application;

[0043] FIG5 is another flow chart of step S103 provided in an embodiment of the present application;

[0044] FIG6 is a schematic diagram of the interaction between the connection management platform and the client application platform provided in an embodiment of the present application;

[0045] FIG7 is a flowchart of rebinding a target IoT card to a machine according to an embodiment of the present application;

[0046] FIG8 is another flow chart of a method for diagnosing machine-card separation based on network element messages according to an embodiment of the present application;

[0047] FIG9 is a schematic structural diagram of a machine-card separation diagnostic system based on network element messages according to an embodiment of the present application;

[0048] FIG10 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and are not to be construed as limitations on the present application. It should be noted that, although the functional modules are divided in the system schematic and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order than the module division in the system schematic or the order in the flow chart. For the step numbers in the following embodiments, they are only provided for the convenience of explanation, and the order between the steps is not limited in any way. The execution order of each step in the embodiment can be adaptively adjusted according to the understanding of those skilled in the art.

[0050] In the description of this application, the meaning of "a plurality" is two or more. If there is a description of "first" or "second", it is only for the purpose of distinguishing technical features and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used in this document have the same meaning as commonly understood by those skilled in the art to which this application belongs. The terms used in this document are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0051] The machine-card separation diagnostic method based on network element messages provided in the embodiments of the present application can be applied to a terminal, can be applied to a server, and can also be software running on a terminal or a server. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a set-top box, etc.; the server can be configured as an independent physical server, or as a server cluster or distributed system composed of multiple physical servers, or as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the machine-card separation diagnostic method based on network element messages, etc., but is not limited to the above forms.

[0052] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0053] It should be noted that in each specific embodiment of the present application, when it comes to the need to perform relevant processing based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of such data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0054] The embodiment of the present application performs machine-card separation diagnosis based on multi-source heterogeneity and massive session message analysis based on SOAP messages of HSS / UDM and Radius messages of PGW / SMF, which can meet the future concurrent query performance requirements of massive IoT devices.

[0055] FIG1 is a flowchart of a method for diagnosing machine-card separation based on network element messages provided in an embodiment of the present application. Referring to FIG1 , an embodiment of the present application provides a method for diagnosing machine-card separation based on network element messages, specifically comprising the following steps:

[0056] S101. Collect SOAP session messages of the target terminal in real time through the HSS / UDM network element and upload the SOAP session messages to the connection management platform;

[0057] S102. Collect the Radius session messages of the target IoT card in real time through the PGW / SMF network element, and upload the Radius session messages to the connection management platform;

[0058] S103. Determine the machine-card binding status of the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message through the connection management platform, and obtain a machine-card separation diagnosis result according to the machine-card binding status.

[0059] Specifically, when the IoT card is separated from the machine, HSS / UDM will record the terminal IMEI information and push the SOAP message of IMEI mismatch to the connection management platform in real time within seconds; the connection management platform will also collect the Radius session messages of the IoT card based on PGW / SMF as a compensation for insufficient SOAP message session collection; when the terminal cannot be used due to machine-card separation, the connection management platform will provide a machine-card binding status diagnostic query solution based on SOAP messages and Radius messages to meet customers' high-performance, high-concurrency machine-card binding diagnostic self-service needs.

[0060] FIG2 is a flowchart of binding a target terminal to a target IoT card according to an embodiment of the present application. Referring to FIG2 , as an optional embodiment, the method for diagnosing device-card separation further includes step S100 of binding the target terminal to the target IoT card, which specifically includes:

[0061] S1001. When the target IoT card is activated, the device-card binding security management function is started through the connection management platform;

[0062] S1002. When the target IoT card goes online for the first time, the first IMEI information of the corresponding target terminal is recorded through the HSS / UDM network element, and the first IMEI information is sent to the connection management platform, so that the connection management platform binds the target terminal and the target IoT card according to the first IMEI information.

[0063] Specifically, the machine-card binding security management function must be enabled when the IoT card is activated. Currently, the most commonly enabled function is the first-call stand-alone card automatic binding function based on HSS / UDM; when the IoT card goes online for the first time, HSS / UDM will record the terminal IMEI information for the first time and push it to the connection management platform in real time to complete the machine-card binding.

[0064] FIG3 is a flowchart of step S103 provided in an embodiment of the present application. Referring to FIG3 , as an optional implementation, the step of determining the machine-card binding state between the target terminal and the target IoT card based on the SOAP session message and the Radius session message specifically includes:

[0065] S1031. Determine the device type and regional node of the target terminal based on the SOAP session message and the Radius session message, and extract the service topology data of the target terminal and the target Internet of Things card;

[0066] S1032. Obtain terminal data information of the target terminal and obtain IoT card data information of the target IoT card;

[0067] S1033. Perform real-time analysis on the service topology data based on the terminal data information and the IoT card data information to obtain the terminal status and the machine-card binding status.

[0068] Specifically, by connecting the management platform to the HSS / UDM network elements to collect SOAP messages of machine-card separation, and connecting to the PGW / SMF network elements to collect Radius messages, we establish and maintain messages for different Huawei and ZTE devices and nodes in different regions, and analyze and extract business topology data related to machine-card separation; based on the data center of IoT customers and IoT cards, we perform real-time calculations on the collected business topology data and analyze data models such as terminal status and machine-card binding status.

[0069] FIG4 is another flowchart of step S103 provided in an embodiment of the present application. Referring to FIG4 , as an optional embodiment, the machine-card separation diagnostic method further includes the following steps:

[0070] S1034. Store the terminal status and the device-card binding status in the connection management platform;

[0071] S1035. Receive the terminal status query request and / or the machine-card binding status query request from the client application platform through the connection management platform, and return the terminal status and / or the machine-card binding status to the client application platform.

[0072] Specifically, the terminal status and machine-card separation status after real-time calculation and processing will be stored in ES, meeting customers' high-performance, high-concurrency machine-card binding status diagnostic query needs.

[0073] FIG5 is another flowchart of step S103 provided in an embodiment of the present application. Referring to FIG5 , as an optional embodiment, the machine-card separation diagnostic method further includes the following steps:

[0074] S1036. Generate machine-card separation alarm information based on a preset rule engine and machine-card binding status;

[0075] S1037. Push the machine-card separation alarm information to the customer application platform through the connection management platform.

[0076] Specifically, the machine-card binding status after real-time processing will generate machine-card separation alarm information through the rule engine and push it to the customer application platform in real time to realize machine-card separation early warning.

[0077] As shown in Figure 6, it is a schematic diagram of the interaction between the connection management platform and the client application platform provided in an embodiment of the present application. It can be understood that the Internet of Things industry client application platform docking with the connection management platform can obtain the machine-card separation status and batch query the machine-card binding status in real time. At the same time, when the connection management platform diagnoses that the target Internet of Things card and the target terminal have machine-card separation, it will also actively push the machine-card separation alarm to the Internet of Things industry client application platform.

[0078] FIG7 is a flowchart of rebinding a target IoT card to a machine provided by an embodiment of the present application. Referring to FIG7 , as an optional embodiment, the machine-card separation diagnosis method further includes the step of rebinding the target IoT card to a machine, which specifically includes:

[0079] S201. When it is determined that the machine-card separation diagnosis result is that the machine-card has been separated, monitor in real time through the PGW / SMF network element whether the target IoT card is online again;

[0080] S202. When the target IoT card comes online again, the second IMEI information of the corresponding re-bound terminal is obtained through the HSS / UDM network element, and the second IMEI information is sent to the connection management platform, so that the connection management platform binds the re-bound terminal to the target IoT card according to the second IMEI information.

[0081] Specifically, based on IMSI, the latest SOAP message and Radius message can be obtained, among which the latest SOAP message can obtain the IMEI information of the terminal bound last time, and the latest Radius message can obtain the IMEI information of the terminal that is online; when the online message occurs, the enhanced customer information and group information judgment rules are used to trigger the message that the machine-card matching can be used online to notify the customer; when re-binding the machine-card, the customer can manually set the selection to rebind the terminal, obtain the second IMEI information of the corresponding rebinding terminal, and send the second IMEI information to the connection management platform, so that the connection management platform binds the rebound terminal to the target Internet of Things card according to the second IMEI information.

[0082] FIG8 is another flow chart of a method for diagnosing machine-card separation based on network element messages according to an embodiment of the present application. Referring to FIG8 , as an optional embodiment, the method for diagnosing machine-card separation based on network element messages further includes at least one of the following steps:

[0083] S104: When the machine-card separation diagnosis result is determined to be machine-card separation, determine whether a location change has occurred based on the SOAP session message. If so, perform regional diagnosis based on the SOAP session message and generate a dangerous area alarm, and then push the dangerous area alarm to the client application platform via the connection management platform;

[0084] S105. Determine the online and offline time of the target IoT card based on the Radius session message, and generate online and offline session alarms and / or long-term offline alarms based on the online and offline time, and then push the online and offline session alarms and / or long-term offline alarms to the client application platform through the connection management platform.

[0085] Specifically, the network element can also provide SOAP messages for location changes. Based on the SOAP messages for location changes, it can provide functions such as regional diagnosis and dangerous area alarms. Based on Radius messages, it can provide network session alarm functions such as online and offline session alarms and long-term offline alarms to meet customers' personalized network monitoring needs.

[0086] The above describes the method steps of the embodiment of the present application. It is understandable that the embodiment of the present application collects SOAP session messages of HSS / UDM network elements and Radius session messages of PGW / SMF network elements through the connection management platform, and determines the machine-card binding status of the target terminal and the target IoT card based on the analysis of massive multi-source heterogeneous messages. This can meet the requirements of high-concurrency machine-card separation queries, improve the efficiency of machine-card separation diagnosis, and ensure the timeliness of machine-card separation diagnosis.

[0087] Compared with the prior art, the embodiments of the present application also have the following advantages:

[0088] 1) High-concurrency batch machine-card binding status query: Currently, the query based on network element devices cannot meet customers' needs for high-concurrency and batch machine-card binding status query.

[0089] 2) Real-time alarm for machine-card separation: When a customer replaces a terminal and the machine-card is separated, the machine-card separation alarm message can be pushed to the customer platform in real time based on the SOAP message of the machine-card separation, thereby improving operational efficiency.

[0090] 3) The proposed method is also applicable to 5G and can provide machine-card binding diagnosis and machine-card separation alarm functions for all 4G / 5G / NB-IOT standards.

[0091] 4) The network element can also provide SOAP messages for location changes. Based on the SOAP messages for location changes, functions such as regional diagnosis and dangerous area alarms can be provided.

[0092] 5) Based on Radius messages, network session alarm functions such as online and offline session alarms and long-term offline alarms can be provided to meet customers' personalized network monitoring needs.

[0093] FIG9 is a schematic diagram of the structure of a machine-card separation diagnostic system based on network element messages provided in an embodiment of the present application. Referring to FIG9 , an embodiment of the present application provides a machine-card separation diagnostic system based on network element messages, including:

[0094] The SOAP session message collection module is used to collect the SOAP session messages of the target terminal in real time through the HSS / UDM network element and upload the SOAP session messages to the connection management platform;

[0095] The Radius session message collection module is used to collect the Radius session messages of the target IoT card in real time through the PGW / SMF network element and upload the Radius session messages to the connection management platform;

[0096] The machine-card separation diagnostic module is used to determine the machine-card binding status of the target terminal and the target Internet of Things card based on the SOAP session message and the Radius session message through the connection management platform, and obtain the machine-card separation diagnostic result based on the machine-card binding status.

[0097] The contents of the above method embodiments are all applicable to the present system embodiments. The functions specifically implemented by the present system embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0098] An embodiment of the present application further provides an electronic device comprising: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for enabling communication between the processor and the memory. When the program is executed by the processor, the aforementioned method for diagnosing device-card separation based on network element messages is implemented. The electronic device may be any intelligent terminal, including a tablet computer and an in-vehicle computer.

[0099] FIG10 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. Referring to FIG10 , an electronic device provided in an embodiment of the present application includes:

[0100] The processor 1001 can be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0101] The memory 1002 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program codes are stored in the memory 1002, and the processor 1001 calls and executes the machine-card separation diagnostic method based on network element messages in the embodiments of this application.

[0102] Input / output interface 1003, used to implement information input and output;

[0103] Communication interface 1004, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);

[0104] Bus 1005 , which transmits information between various components of the device (e.g., processor 1001 , memory 1002 , input / output interface 1003 , and communication interface 1004 );

[0105] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via the bus 1005 .

[0106] An embodiment of the present application also provides a storage medium, which is a computer-readable storage medium used for computer-readable storage. The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned machine-card separation diagnostic method based on network element messages.

[0107] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0108] The present application also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the method shown in FIG1 .

[0109] In some optional embodiments, the functions / operations mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the functions / operations involved, the two blocks shown in succession may actually be executed substantially simultaneously or the blocks may sometimes be executed in reverse order. In addition, the embodiments presented and described in the flow chart of the present application are provided in an exemplary manner for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operations and logic flows presented herein. Optional embodiments are contemplated in which the order of the various operations is changed and the sub-operations described as a part of a larger operation are performed independently.

[0110] In addition, although the present application is described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the above-mentioned functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in separate physical devices or software modules. It is also understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present application. More specifically, given the properties, functions, and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the module will be understood within the routine skills of an engineer. Therefore, a person skilled in the art can implement the present application as set forth in the claims using ordinary techniques without undue experimentation. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present application, which is determined by the full scope of the appended claims and their equivalents.

[0111] If the above 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, server, or network device, etc.) to execute all or part of the steps of the above methods of 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.

[0112] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0113] More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic devices), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable media on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, deciphering, or processing in another suitable manner as necessary, and then stored in a computer memory.

[0114] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0115] In the above description of this specification, reference to the terms "one embodiment / example," "another embodiment / example," or "certain embodiments / examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples.

[0116] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions, and variations may be made to the embodiments without departing from the principles and intent of the present application, and that the scope of the present application is defined by the claims and their equivalents.

[0117] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A machine-card separation diagnosis method based on network element messages, characterized in that: The following steps are involved: Collect SOAP session messages of the target terminal in real time through HSS / UDM network elements, and upload the SOAP session messages to the connection management platform; Collect the Radius session message of the target IoT card in real time through the PGW / SMF network element, and upload the Radius session message to the connection management platform; The connection management platform determines the machine-card binding status of the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message, and obtains a machine-card separation diagnosis result according to the machine-card binding status.

2. The method for diagnosing machine-card separation based on network element messages according to claim 1, characterized in that: The machine-card separation diagnosis method further includes a step of binding the target terminal to the target Internet of Things card, which specifically includes: When the target IoT card is activated, the device-card binding security management function is started through the connection management platform; When the target Internet of Things card goes online for the first time, the first IMEI information of the corresponding target terminal is recorded through the HSS / UDM network element, and the first IMEI information is sent to the connection management platform, so that the connection management platform binds the target terminal and the target Internet of Things card according to the first IMEI information.

3. The method for diagnosing machine-card separation based on network element messages according to claim 1, characterized in that: The step of determining the machine-card binding state between the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message specifically includes: Determine the device type and regional node of the target terminal according to the SOAP session message and the Radius session message, and extract the service topology data of the target terminal and the target Internet of Things card; Obtain terminal data information of the target terminal, and obtain Internet of Things card data information of the target Internet of Things card; The service topology data is analyzed in real time according to the terminal data information and the IoT card data information to obtain the terminal status and the machine-card binding status.

4. The method for diagnosing machine-card separation based on network element messages according to claim 3, characterized in that: The machine-card separation diagnosis method further comprises the following steps: Storing the terminal status and the machine-card binding status in the connection management platform; The terminal status query request and / or the machine-card binding status query request of the client application platform is received through the connection management platform, and the terminal status and / or the machine-card binding status is returned to the client application platform.

5. The method for diagnosing machine-card separation based on network element messages according to claim 3, characterized in that: The machine-card separation diagnosis method further comprises the following steps: Generate machine-card separation alarm information according to a preset rule engine and the machine-card binding status; The machine-card separation alarm information is pushed to the client application platform through the connection management platform.

6. The method for diagnosing machine-card separation based on network element messages according to claim 1, characterized in that: The machine-card separation diagnosis method further includes the step of rebinding the target IoT card to the machine-card, which specifically includes: When it is determined that the machine-card separation diagnosis result is that the machine-card has been separated, real-time monitoring is performed through the PGW / SMF network element to determine whether the target IoT card is online again; When the target IoT card comes online again, the second IMEI information of the corresponding re-bound terminal is obtained through the HSS / UDM network element, and the second IMEI information is sent to the connection management platform, so that the connection management platform binds the re-bound terminal to the target IoT card according to the second IMEI information.

7. A machine-card separation diagnosis method based on network element messages according to any one of claims 1 to 6, characterized in that: The machine-card separation diagnosis method based on network element messages further comprises at least one of the following steps: When it is determined that the machine-card separation diagnosis result is that the machine-card has been separated, determining whether a location change has occurred according to the SOAP session message, and if so, performing a regional diagnosis according to the SOAP session message and generating a dangerous area alarm, and then pushing the dangerous area alarm to the client application platform through the connection management platform; The online and offline time of the target IoT card is determined according to the Radius session message, and online and offline session alarms and / or long-term offline alarms are generated according to the online and offline time, and then the online and offline session alarms and / or long-term offline alarms are pushed to the client application platform through the connection management platform.

8. A machine-card separation diagnosis system based on network element messages, characterized in that: include: A SOAP session message collection module is used to collect SOAP session messages of the target terminal in real time through the HSS / UDM network element, and upload the SOAP session messages to the connection management platform; A Radius session message collection module is used to collect the Radius session messages of the target IoT card in real time through the PGW / SMF network element, and upload the Radius session messages to the connection management platform; The machine-card separation diagnostic module is used to determine the machine-card binding status of the target terminal and the target Internet of Things card according to the SOAP session message and the Radius session message through the connection management platform, and obtain the machine-card separation diagnostic result according to the machine-card binding status.

9. An electronic device, characterized in that: The electronic device includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the machine-card separation diagnostic method based on network element messages as described in any one of claims 1 to 7 are realized.

10. A storage medium, the storage medium being a computer-readable storage medium, used for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the machine-card separation diagnostic method based on network element messages as described in any one of claims 1 to 7.

Images