Multi-system quick docking method and device, medium and program product

Through unified modeling and custom settings, the network management system and third-party systems are quickly connected, which solves the problems of long custom development cycle and inconsistent alarm formats, and improves the efficiency of multi-system docking and user satisfaction.

CN118972244APending Publication Date: 2024-11-15BEIJING TOPSEC NETWORK SECURITY TECH +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411062699.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-05
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

When existing network management systems connect to different security analysis systems, the custom development cycle is long, the user's alarm definitions of the system are different, and the alarm formats and field keywords of different systems are inconsistent, resulting in inefficient docking.

Method used

By uniformly modeling the alarm information, abstracting the alarm metadata model, creating a custom alarm resolution template, and customizing the alarm content format and field name, it realizes the rapid connection between the network management system and the third-party system to meet the needs of different users Customized requirements.

Benefits of technology

Without upgrading the current network product version, we can achieve rapid docking of multiple systems, shorten the development cycle of custom requirements, improve docking efficiency, and meet the alarm management definition requirements and usage habits of different enterprise users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972244A_ABST
    Figure CN118972244A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a multi-system quick docking method and device, a medium and a program product. The method comprises the following steps: carrying out unified modeling on alarm information to obtain an alarm metadata model; abstracting alarm metadata of a network management system based on the alarm metadata model; creating a self-defined alarm analysis template corresponding to the requirements of a network management system and a third-party system based on the alarm metadata; setting alarm content formats or alarm field names of the network management system and the third-party system in a user-defined manner; and on the basis of the alarm content format or the alarm field name which is set in a user-defined manner, realizing rapid butt joint between the network management system and the third-party system by calling a user-defined alarm interface. According to the method, the multi-system docking efficiency can be improved, and multi-system quick docking is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of network security technology, and in particular to a method, device, medium and program product for rapid docking of multiple systems. Background Art

[0002] As enterprises attach more importance to security management, they begin to introduce systematic security analysis solutions to meet the security analysis needs of their own business. As a tool for enterprises to centrally manage network equipment, the network management platform is integrated into the security solution with its unique management value for network equipment and becomes part of the solution. The network system management platform has its own alarm management system, which collects, stores, queries and analyzes the alarms generated by the system, and realizes the management of the alarm process in this system.

[0003] In the solution, the network management platform provides various alarm logs to the security solution's security analysis system for analysis. As a docking network management system, if it can flexibly realize docking with various security analysis systems, it will be able to shorten the company's future security solution deployment cycle and improve customer satisfaction.

[0004] In the related technologies, the current network management system generally drives the R&D management team to customize the system to meet customer needs through customized requirements when dealing with different docking systems. However, it has the following defects: the customized requirements development cycle is relatively long; different users have different definitions of system alarms; when it comes to docking systems, different systems have inconsistent alarm formats, alarm field keywords, etc., and the other party's products need to be adapted during the docking process, resulting in reduced docking efficiency. Summary of the invention

[0006] In view of this, the embodiments of the present disclosure provide a method, device, medium and program product for rapid docking of multiple systems. By providing users with flexible configuration solutions, the alarm data format requirements for docking different products can be met during the use of the existing network, and the goal of completing system docking can be achieved without upgrading the product version of the existing network. At the same time, it can meet the customized requirements of different enterprise users for alarm query results and meet the usage habits of different users. This can solve the problem of relatively long development and release cycles of customized requirements; solve the problem that different enterprise users have different requirements for the alarm management definition of the system and need customized development; solve the problem of customized development caused by inconsistencies in the alarm format, alarm field keywords, etc. of different systems when docking systems, thereby improving the efficiency of multi-system docking and achieving rapid docking of multiple systems.

[0007] In a first aspect, the present disclosure provides a method for rapid docking of multiple systems, which adopts the following technical solution:

[0008] Model the alarm information in a unified manner to obtain the alarm metadata model;

[0009] Based on the alarm metadata model, abstract the alarm metadata of the network management system;

[0010] Based on the alarm metadata, create a custom alarm parsing template corresponding to the needs of the network management system and the third-party system;

[0011] Customizing the alarm content format or alarm field name of the network management system and the third-party system;

[0012] Based on the custom-set alarm content format or alarm field name, the network management system and the third-party system are quickly connected by calling the custom alarm interface.

[0013] In some embodiments, based on the alarm metadata, a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system is created, including:

[0014] Creating a plurality of first custom alarm templates for the network management system;

[0015] Create a number of second custom alarm templates for third-party systems connected to the network management system.

[0016] In some embodiments, the method further includes: when the custom alarm parsing template is set up, immediately calling the custom alarm parsing template.

[0017] In some embodiments, customizing the alarm content format or alarm field name of the network management system and the third-party system includes:

[0018] Customizing the name of the first alarm field of the network management system;

[0019] Customize the alarm content format and the second alarm field name output to the third-party system when the network management system is connected to the third-party system.

[0020] In some embodiments, the method further comprises:

[0021] Establishing a mapping relationship between each element of the alarm metadata model and the user-defined alarm field;

[0022] Customize the target alert field name based on user preference.

[0023] In some embodiments, the alarm information is uniformly modeled to obtain an alarm metadata model, including:

[0024] Obtaining an alarm metadata model of the network management system through modeling; wherein the number of the alarm metadata model is one;

[0025] The alarm user model of the network management system is obtained through modeling; wherein, the number of the alarm user models is multiple.

[0026] In some embodiments, the method further comprises:

[0027] A 1:N mapping relationship between the alarm metadata model and the alarm user model is established; wherein the alarm metadata model is mapped to the corresponding alarm user model through different custom alarm rules.

[0028] In a second aspect, the embodiment of the present disclosure also provides a device for rapid docking of multiple systems, which adopts the following technical solution:

[0029] A modeling unit is configured to uniformly model the alarm information to obtain an alarm metadata model;

[0030] An extraction unit is configured to abstract the alarm metadata of the network management system based on the alarm metadata model;

[0031] A creation unit configured to create a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system based on the alarm metadata;

[0032] A first setting unit is configured to customize the alarm content format or the alarm field name of the network management system and the third-party system;

[0033] The second setting unit is configured to realize the rapid connection between the network management system and the third-party system by calling the customized alarm interface based on the customized alarm content format or alarm field name.

[0034] In a third aspect, the embodiments of the present disclosure further provide a computer device, which adopts the following technical solution:

[0035] The computer device comprises:

[0036] at least one processor; and,

[0037] a memory communicatively connected to the at least one processor; wherein,

[0038] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any of the above-mentioned methods for rapid docking of multiple systems.

[0039] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute any of the above-mentioned methods for rapid docking of multiple systems.

[0040] In a fifth aspect, an embodiment of the present disclosure further provides a computer program product, including a computer program / instruction, which implements the steps of any of the above methods when executed by a processor.

[0041] The disclosed embodiment provides a method for rapid multi-system docking, which provides users with a flexible configuration solution to meet the alarm data format requirements for docking different products during the use of the existing network, and achieve the goal of completing system docking without upgrading the product version of the existing network. At the same time, it can meet the customized requirements of different enterprise users for alarm query results and meet the usage habits of different users. This can solve the problem of relatively long development and release cycles of customized requirements; solve the problem that different enterprise users have different requirements for the alarm management definition of the system and need customized development; solve the problem of customized development caused by inconsistencies in the alarm format, alarm field keywords, etc. of different systems when docking systems, thereby improving the efficiency of multi-system docking and achieving rapid multi-system docking.

[0042] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the following preferred embodiments are specifically cited and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0044] Figure 1 A flowchart of a method for rapid connection of multiple systems provided by an embodiment of the present disclosure;

[0045] Figure 2 A schematic diagram of a model structure provided for an embodiment of the present disclosure;

[0046] Figure 3 A schematic diagram of the structure of a device for rapid docking of multiple systems provided in an embodiment of the present disclosure;

[0047] Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0048] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0049] It should be clear that the following embodiments of the present disclosure are described by specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other in the absence of conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0050] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.

[0051] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The drawings only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0052] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0053] like Figure 1 As shown, the embodiment of the present disclosure provides a method for rapid docking of multiple systems, including the following steps:

[0054] S101. Model the alarm information in a unified manner to obtain an alarm metadata model.

[0055] Optionally, the network management system uniformly models the alarm information, abstracts the alarm metadata of the network management system, and constructs an alarm metadata model.

[0056] Optionally, the alarm metadata may include: alarm sequence number, alarm ID, alarm name, alarm level, alarm generation time, alarm recovery time, alarm original class, alarm original level, alarm title, alarm generation source, alarm details, alarm handler, etc.

[0057] S102: Abstracting alarm metadata of the network management system based on the alarm metadata model.

[0058] The first customized alarm template of the network management system itself can be customized; the alarm content format and alarm fields output to the third-party system when the network management system is connected to the third-party system can be customized; the customized alarm template of the existing network can be supported to take effect immediately.

[0059] S103: Based on the alarm metadata, create a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system.

[0060] S104: Customize the alarm content format or the alarm field name of the network management system and the third-party system.

[0061] S105: Based on the custom-set alarm content format or alarm field name, the network management system and the third-party system are quickly connected by calling a custom alarm interface.

[0062] The disclosed embodiment provides an efficient and flexible alarm adaptation solution design idea, which can meet the alarm data format requirements of different products in the current network, and achieve the goal of completing system docking without upgrading the current network product version. At the same time, it can meet the customized requirements of different enterprise users for alarm query results and meet the usage habits of different users.

[0063] The disclosed embodiment provides a method for rapid multi-system docking, which provides users with a flexible configuration solution to meet the alarm data format requirements for docking different products during the use of the existing network, and achieve the goal of completing system docking without upgrading the product version of the existing network. At the same time, it can meet the customized requirements of different enterprise users for alarm query results and meet the usage habits of different users. This can solve the problem of relatively long development and release cycles of customized requirements; solve the problem that different enterprise users have different requirements for the alarm management definition of the system and need customized development; solve the problem of customized development caused by inconsistencies in the alarm format, alarm field keywords, etc. of different systems when docking systems, thereby improving the efficiency of multi-system docking and achieving rapid multi-system docking.

[0064] In some embodiments, based on the alarm metadata, a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system is created, including:

[0065] Creating a plurality of first custom alarm templates for the network management system;

[0066] Create a number of second custom alarm templates for third-party systems connected to the network management system.

[0067] Optionally, multiple copies of the first custom alarm template can be created, and users can choose to use them according to their preferences; multiple copies of the second custom alarm template can be created, and the existing network can select a suitable template according to actual docking needs.

[0068] Optionally, when delivering the network management system to different enterprise customers, different customers generally have their own understanding or usage habits of the alarm management part, and the field names and alarm levels of the alarm information presented in the system default alarm list. When the customer's usage habits or understanding are inconsistent, the customer generally has customized development requirements for alarm management. In order to quickly adapt to this scenario, the alarm management of the network management system supports users to customize the alarm list to present the alarm field name, and supports customization of certain special field contents (such as alarm level).

[0069] Optionally, the network management system often needs to be connected with other management systems that make up the security solution. Different systems have different requirements for the alarm format, field names, etc. The system's default alarm format and the field names and alarm levels related to the alarm information presented in the alarm list may be inconsistent with the customer's usage habits or understanding. Therefore, system connection generally requires customized development of alarm management.

[0070] In order to quickly adapt to this scenario, the alarm management of the network management system supports users to customize the alarm format, alarm field name, etc., and supports customization of certain special field contents (such as alarm level).

[0071] In some embodiments, the method further includes: when the custom alarm parsing template is set up, immediately calling the custom alarm parsing template.

[0072] In some embodiments, customizing the alarm content format or alarm field name of the network management system and the third-party system includes:

[0073] Customizing the name of the first alarm field of the network management system;

[0074] Customize the alarm content format and the second alarm field name output to the third-party system when the network management system is connected to the third-party system.

[0075] In some embodiments, the method further comprises:

[0076] Establishing a mapping relationship between each element of the alarm metadata model and the user-defined alarm field;

[0077] Customize the target alert field name based on user preference.

[0078] In some embodiments, the alarm information is uniformly modeled to obtain an alarm metadata model, including:

[0079] Obtaining an alarm metadata model of the network management system through modeling; wherein the number of the alarm metadata model is one;

[0080] The alarm user model of the network management system is obtained through modeling; wherein, the number of the alarm user models is multiple.

[0082] In some embodiments, the method further comprises:

[0083] A 1:N mapping relationship between the alarm metadata model and the alarm user model is established; wherein the alarm metadata model is mapped to the corresponding alarm user model through different custom alarm rules.

[0084] like Figure 2 As shown in the figure, in order to meet the requirements of alarm content and alarm format in various scenarios, the network management system defines two levels of models for alarms. The first one is called the network management system alarm metamodel, referred to as the alarm metamodel; the other is called the network management system alarm user model, referred to as the alarm user model. There is only one alarm metamodel in the system, and there can be multiple alarm user models. The relationship between the alarm metamodel and the alarm user model is a 1:N relationship. The alarm metamodel is mapped to the corresponding alarm user model through different custom alarm rules.

[0085] A user-defined rule is an alarm template. Users can define the alarm field information they are interested in through customized alarm rules, and can redefine the alarm field name to suit their own usage habits. Therefore, the core functions of the network management platform's customized alarm rules include two: (1) defining the mapping relationship between each element of the alarm metadata model and the user-defined alarm field; (2) users define the alarm field name that suits their usage preferences.

[0086] Optionally, define the mapping relationship between each element of the alarm metamodel and the user-defined alarm field as follows:

[0087] <Alarm meta model field-1, user-defined model field-1>

[0088] <Alarm meta model field-2, user-defined model field-2>

[0089] <Alarm meta model field-3, user-defined model field-3> ...

[0092] <alarm metamodel field-N, user-defined model field-N>.

[0093] The names of [Alarm Meta Model Field-N] and [User-defined Model Field-N] can be the same or different. Users can define alarm fields that suit their own usage habits by changing the name of [User-defined Model Field-N].

[0094] Optionally, when the alarm interface of the network management system is connected to a third-party system, there are also requirements for the alarm format. Therefore, the alarm format needs to be defined in the custom alarm rule for the third-party system connection.

[0095] Optionally, the definition of the alarm format needs to be identified in the alarm template through the following definition:

[0096] AlarmLogRecordFormat=Key_Value

[0097] Among them, the optional options in the Key_Value section are explained as follows:

[0098] 1) AlarmLogRecordFormat = Key_Value. The following is an example of the interconnected alarm log format:

[0099] Alarm field-1 = Value-1 Alarm field-2 = Value-2 Alarm field-3 = Value-3.

[0100] 2) AlarmLogRecordFormat = Value. The interconnected alarm log format is as follows: Value-1Value-2 Value-3.

[0101] The disclosed embodiment adapts to the customization needs of enterprise users of the network management system, and can quickly modify the user interface display content of the alarm module to meet the usage preferences of different users; it adapts to the docking needs in the security solution, and can quickly achieve docking with third-party systems through the ability to customize alarm formats, alarm field names, etc.

[0102] like Figure 3 As shown, the embodiment of the present disclosure also provides a device for rapid docking of multiple systems, including:

[0103] A modeling unit 31 is configured to uniformly model the alarm information to obtain an alarm metadata model;

[0104] An extraction unit 32 is configured to abstract the alarm metadata of the network management system based on the alarm metadata model;

[0105] A creation unit 33, configured to create a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system based on the alarm metadata;

[0106] A first setting unit 34 is configured to customize the alarm content format or alarm field name of the network management system and the third-party system;

[0107] The second setting unit 35 is configured to realize the rapid connection between the network management system and the third-party system by calling the customized alarm interface based on the customized alarm content format or alarm field name.

[0108] The computer device according to the embodiment of the present disclosure includes a memory and a processor. The memory is used to store non-temporary computer-readable instructions. Specifically, the memory may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may, for example, include a random access memory (RAM) and / or a cache memory (cache), etc. The non-volatile memory may, for example, include a read-only memory (ROM), a hard disk, a flash memory, etc.

[0109] The processor may be a central processing unit (CPU) or other forms of processing units with data processing capabilities and / or instruction execution capabilities, and may control other components in the computer device to perform desired functions. In one embodiment of the present disclosure, the processor is used to run the computer-readable instructions stored in the memory, so that the computer device performs all or part of the steps of the method for rapid docking of multiple systems in the aforementioned embodiments of the present disclosure.

[0110] Those skilled in the art should be able to understand that in order to solve the technical problem of how to obtain a good user experience, the present embodiment may also include well-known structures such as a communication bus and an interface, and these well-known structures should also be included in the protection scope of the present disclosure.

[0111] like Figure 4A schematic diagram of the structure of a computer device provided in an embodiment of the present disclosure is shown, which is a schematic diagram of the structure of a computer device suitable for implementing the embodiment of the present disclosure. Figure 4 The computer device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0112] like Figure 4 As shown, the computer device may include a processor (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage device into a random access memory (RAM). In the RAM, various programs and data required for the operation of the computer device are also stored. The processor, ROM, and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.

[0113] Typically, the following devices can be connected to the I / O interface: input devices such as sensors or visual information acquisition devices; output devices such as display screens; storage devices such as tapes, hard disks, etc.; and communication devices. The communication device can allow the computer device to communicate with other devices (such as edge computing devices) wirelessly or by wire to exchange data. Figure 4 A computer device having various devices is shown, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0114] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processor, all or part of the steps of a multi-system rapid docking method of an embodiment of the present disclosure are executed.

[0115] For detailed description of this embodiment, reference may be made to the corresponding descriptions in the aforementioned embodiments, which will not be repeated here.

[0116] According to the computer-readable storage medium of the embodiment of the present disclosure, non-transitory computer-readable instructions are stored thereon. When the non-transitory computer-readable instructions are executed by a processor, all or part of the steps of the method for rapid multi-system docking of the above-mentioned embodiments of the present disclosure are executed.

[0117] The above-mentioned computer-readable storage media include, but are not limited to: optical storage media (e.g., CD-ROM and DVD), magneto-optical storage media (e.g., MO), magnetic storage media (e.g., magnetic tape or mobile hard disk), media with built-in rewritable non-volatile memory (e.g., memory card) and media with built-in ROM (e.g., ROM box).

[0118] For detailed description of this embodiment, reference may be made to the corresponding descriptions in the aforementioned embodiments, which will not be repeated here.

[0119] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0120] In the present disclosure, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. The block diagrams of the devices, devices, equipment, and systems involved in the present disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagram. As will be appreciated by those skilled in the art, these devices, devices, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including", "comprising", "having", etc. are open words, referring to "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used here refer to the words "and / or" and can be used interchangeably with them, unless the context clearly indicates otherwise. The words "such as" used here refer to the phrase "such as but not limited to", and can be used interchangeably with them.

[0121] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0122] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0123] Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

[0124] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0125] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A method for rapid docking of multiple systems, characterized in that: include: Model the alarm information in a unified manner to obtain the alarm metadata model; Based on the alarm metadata model, abstract the alarm metadata of the network management system; Based on the alarm metadata, create a custom alarm parsing template corresponding to the needs of the network management system and the third-party system; Customizing the alarm content format or alarm field name of the network management system and the third-party system; Based on the custom-set alarm content format or alarm field name, the network management system and the third-party system are quickly connected by calling the custom alarm interface.

2. The method for rapid multi-system docking according to claim 1, characterized in that: Based on the alarm metadata, a custom alarm parsing template corresponding to the requirements of the network management system and the third-party system is created, including: Creating a plurality of first custom alarm templates for the network management system; Create a number of second custom alarm templates for third-party systems connected to the network management system.

3. The method for rapid multi-system docking according to claim 2, characterized in that: The method further includes: when the setting of the custom alarm parsing template is completed, immediately calling the custom alarm parsing template.

4. The method for rapid multi-system docking according to claim 2, characterized in that: Customizing the alarm content format or alarm field name of the network management system and the third-party system includes: Customizing the name of the first alarm field of the network management system; Customize the alarm content format and the second alarm field name output to the third-party system when the network management system is connected to the third-party system.

5. The method for rapid multi-system docking according to claim 4, characterized in that: The method further comprises: Establishing a mapping relationship between each element of the alarm metadata model and the user-defined alarm field; Customize the target alert field name based on user preference.

6. The method for rapid multi-system docking according to claim 1, characterized in that: The alarm information is uniformly modeled to obtain the alarm metadata model, including: Obtaining an alarm metadata model of the network management system through modeling; wherein the number of the alarm metadata model is one; The alarm user model of the network management system is obtained through modeling; wherein, the number of the alarm user models is multiple.

7. The method for rapid multi-system docking according to claim 6, characterized in that: The method further comprises: A 1:N mapping relationship between the alarm metadata model and the alarm user model is established; wherein the alarm metadata model is mapped to the corresponding alarm user model through different custom alarm rules.

8. A computer device, characterized in that: The computer device comprises: at least one processor; and, A memory in communication with the at least one processor; wherein YY+242205P The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the multi-system rapid docking method described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the multi-system rapid docking method described in any one of claims 1 to 7.

10. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.