CN118041761A - Automatic equipment acquisition method, system, device and medium - Google Patents
Automatic equipment acquisition method, system, device and medium Download PDFInfo
- Publication number
- CN118041761A CN118041761A CN202410139111.4A CN202410139111A CN118041761A CN 118041761 A CN118041761 A CN 118041761A CN 202410139111 A CN202410139111 A CN 202410139111A CN 118041761 A CN118041761 A CN 118041761A
- Authority
- CN
- China
- Prior art keywords
- network element
- information
- configuration table
- equipment
- acquisition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 66
- 238000012545 processing Methods 0.000 claims description 49
- 230000015654 memory Effects 0.000 claims description 11
- 238000003306 harvesting Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 10
- 230000008859 change Effects 0.000 description 9
- 239000002071 nanotube Substances 0.000 description 9
- 238000007726 management method Methods 0.000 description 7
- 238000012512 characterization method Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- ZLIBICFPKPWGIZ-UHFFFAOYSA-N pyrimethanil Chemical compound CC1=CC(C)=NC(NC=2C=CC=CC=2)=N1 ZLIBICFPKPWGIZ-UHFFFAOYSA-N 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
Abstract
The application discloses an automatic equipment acquisition method, an automatic equipment acquisition system, an automatic equipment acquisition device and a storage medium, wherein the method comprises the following steps: acquiring access equipment information sent by an equipment automatic discovery service, wherein the access equipment information comprises first identity information, network element subclass information and logic network elements; inquiring whether a configuration table of the access equipment exists or not from a database according to the first identity information; determining a configuration table of the access equipment in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table; determining that network element subclass information corresponding to the access equipment exists in the configuration table, and inquiring whether logic network elements corresponding to the access equipment exist in the configuration table; determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The application can be widely applied to the technical field of network communication.
Description
Technical Field
The application relates to the technical field of network communication, in particular to an automatic equipment acquisition method, an automatic equipment acquisition system, an automatic equipment acquisition device and a storage medium.
Background
According to the cloud network operation system, the base is the only channel for providing real-time acquisition and operation interaction of the cloud network data, and the acquisition and operation capability of the whole network operation data (configuration, performance, alarm, log and the like) are required to be provided. However, the conventional manual configuration method from the access system to the acquisition task of the network device in the related art is still used, which is difficult to keep up with the construction speed of the network, and the increasingly huge device scale brings unprecedented pressure to the maintenance personnel of the system. When a large number of devices are accessed into the system, the repeated work can be carried out only by the operation support department with a large amount of manpower and time, so that the efficiency is reduced and the cost is increased. Accordingly, there still exists a technical problem in the related art that needs to be solved.
Disclosure of Invention
The present application aims to solve at least one of the technical problems existing in the prior art to a certain extent.
Therefore, an object of the embodiments of the present application is to provide a method, a system, an apparatus, and a storage medium for automatically collecting devices, where the method, the system, the apparatus, and the storage medium can improve efficiency of accessing devices into a system, and reduce cost.
In order to achieve the technical purpose, the technical scheme adopted by the embodiment of the application comprises the following steps: an apparatus auto-acquisition method comprising: acquiring access equipment information sent by an equipment automatic discovery service, wherein the access equipment information comprises first identity information, network element subclass information and logic network elements; inquiring whether a configuration table of the access equipment exists or not from a database according to the first identity information; determining a configuration table of access equipment in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table; determining that network element subclass information corresponding to the access equipment exists in the configuration table, and inquiring whether logic network elements corresponding to the access equipment exist in the configuration table; determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework.
In summary, the embodiment may detect whether the first identity information exists in the configuration table by comparing the access device information with the first identity information sent by the device auto-discovery service with a preset configuration table; if so, detecting whether network element subclass information corresponding to the access equipment exists in the configuration table; if so, detecting whether a logic network element corresponding to the access equipment exists in the configuration table; if the network element information exists, generating network element information, acquisition source information and control interface information corresponding to the access equipment according to the network element detail information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The application can automatically compare and match the accessed access equipment with the preset table, and can generate the network element information, the acquisition source information and the control interface information corresponding to the access equipment for equipment acquisition after successful matching.
In addition, the method for automatically collecting equipment according to the embodiment of the invention can have the following additional technical characteristics:
Further, in an embodiment of the present application, the method further includes: and determining that the configuration table of the access equipment does not exist in the database, storing the access equipment information into the database, and adding the configuration table corresponding to the first identity information into the database.
Further, in an embodiment of the present application, the method further includes: and determining that the network element subclass information corresponding to the access equipment does not exist in the configuration table, storing the access equipment information into a database, and adding the network element subclass information and a new logic network element into the configuration table.
Further, in an embodiment of the present application, the method further includes: and determining that the network element subclass information corresponding to the access equipment does not exist in the configuration table, storing the access equipment information into a database, and adding a new logic network element in the configuration table.
Further, in an embodiment of the present application, the determining that the network element subclass information corresponding to the access device exists in the configuration table includes: and detecting and determining that the equipment specialty, the equipment manufacturer, the equipment type and the equipment model corresponding to the access equipment exist in the configuration table at the same time, or sequentially detecting and determining that the equipment specialty, the equipment manufacturer, the equipment type and the equipment model corresponding to the access equipment exist in the configuration table.
Further, in an embodiment of the present application, the method further includes: and issuing the created acquisition source information and the control interface information to an acquisition control service.
In another aspect, an embodiment of the present application further provides an automatic device acquisition system, including:
the device comprises an acquisition unit, a logic network element and a service discovery unit, wherein the acquisition unit is used for acquiring access device information sent by an automatic discovery service of the device, and the access device information comprises first identity information, network element subclass information and logic network elements;
The first processing unit is used for inquiring whether a configuration table of the access equipment exists in the database according to the first identity information;
The second processing unit is used for determining that a configuration table of the access equipment exists in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table;
a third processing unit, configured to determine that there is network element subclass information corresponding to the access device in the configuration table, and query whether there is a logical network element corresponding to the access device in the configuration table;
And the fourth processing unit is used for determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework.
Further, in an embodiment of the present application, the system further includes a fifth processing unit; the fifth processing unit is configured to determine that a configuration table of the access device does not exist in the database, store the access device information into the database and add first identity information into the configuration table, or determine that network element subclass information corresponding to the access device does not exist in the configuration table, store the access device information into the database and add the network element subclass information and a new logic network element into the configuration table, or determine that network element subclass information corresponding to the access device does not exist in the configuration table, store the access device information into the database and add the new logic network element into the configuration table.
In another aspect, the present application also provides an apparatus for automatically collecting devices, including:
at least one processor;
At least one memory for storing at least one program;
The at least one program, when executed by the at least one processor, causes the at least one processor to implement a device auto-acquisition method as previously described.
Furthermore, the present application provides a computer readable storage medium having stored therein processor executable instructions which, when executed by a processor, are adapted to carry out a device auto-acquisition method as described in the foregoing.
The advantages and benefits of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.
The application can detect whether the first identity information exists in a configuration table by comparing the access equipment information with the first identity information sent by the equipment automatic discovery service with the preset configuration table; if so, detecting whether network element subclass information corresponding to the access equipment exists in the configuration table; if yes, detecting whether a logic network element corresponding to the access equipment exists in the configuration table; and if the network element information exists, generating network element information, acquisition source information and control interface information corresponding to the access equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The application can automatically compare and match the accessed access equipment with the preset table, and can generate the network element information, the acquisition source information and the control interface information corresponding to the access equipment for equipment acquisition after successful matching.
Drawings
FIG. 1 is a schematic diagram illustrating steps of an automatic device acquisition method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating steps of another method for automatically collecting equipment according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating steps of another method for automatically collecting equipment according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating steps of another method for automatically collecting equipment according to an embodiment of the present invention;
FIG. 5 is a schematic diagram illustrating steps of another method for automatically collecting equipment according to an embodiment of the present invention;
Fig. 6 is a schematic diagram of an automatic network element nanotube and an automatic service discovery process according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a system page configured with basic information according to an embodiment of the present invention;
FIG. 8 is a flow chart of the network element automatic nanotubes and other system synchronization in an embodiment of the present invention;
Fig. 9 is a schematic diagram of a network element connection status monitoring flow in an embodiment of the present invention;
fig. 10 is a schematic diagram of a network element automatic acquisition flow in an embodiment of the present invention;
FIG. 11 is a diagram illustrating a cloud network resource directory in accordance with an embodiment of the present invention;
FIG. 12 is a schematic diagram of an automatic device acquisition system according to an embodiment of the present invention;
Fig. 13 is a schematic structural diagram of an automatic device for collecting equipment according to an embodiment of the present invention.
Detailed Description
The following describes in detail the principles and processes of the device automatic acquisition method, system, apparatus and storage medium in the embodiments of the present invention with reference to the accompanying drawings.
The following applies to the terminology used in the present application as follows:
SNMP protocol: the simple network management protocol (Simple Network Management Protocol, SNMP) is named simple gateway monitoring protocol (SIMPLE GATEWAY Monitoring Protocol, SGM P) as original name. The new management information structure and management information base are added on the basis of SGMP protocol, which is proposed by the research group of IETF at the earliest, so that SGMP is more comprehensive. Simplicity and extensibility are embodied in SNMP, which includes Database type (Database Schema), an application layer protocol (Ap plication Layer Protocol) and some profile files. The SNMP management protocol not only can enhance the efficiency of the network management system, but also can be used to manage and monitor resources in the network in real time.
Kafka: kafka is an open source stream processing platform developed by the Apache software foundation, written by scala and Java. Kafka is a high-throughput distributed publish-subscribe messaging system that can handle all action flow data for consumers in a web site. Such actions (web browsing, searching and other user actions) are a key factor in many social functions on modern networks. These data are typically addressed by processing logs and log aggregations due to throughput requirements. This is a viable solution for log data and offline analysis systems like Hadoop, but with the limitation of requiring real-time processing. The purpose of Kafka is to unify on-line and off-line message processing through the Hadoop parallel loading mechanism, and also to provide real-time messages through the clusters.
In the related art, according to the fact that the base of the cloud network operation system is the only channel for providing real-time collection and operation interaction of cloud network data, the collection and operation capability provision of the whole network operation data (configuration, performance, alarm, log and the like) are required to be realized. However, the current mode of manually configuring an access system from access to acquisition task of network equipment still uses the traditional mode, the construction speed of the network is not kept up, and the huge equipment scale brings unprecedented pressure to system maintenance operators. When a large number of devices are accessed, no quick and effective processing means exists, and the repeated work can be carried out only by inputting a large amount of manpower and time by the operation support department. Moreover, when the access device or the system is on line, the access data acquisition and control needs to manually configure information such as network elements, acquisition sources, control interfaces, parameters and the like. By the manual intervention method, the speed is low and the perception is poor. There is still a need to solve the problems in the related art.
In view of the above-mentioned drawbacks of the prior art, referring to fig. 1, fig. 1 is a schematic step diagram of an automatic device collection method according to an embodiment of the present application. In fig. 1, the device automatic acquisition method may include, but is not limited to, step S101 to step S105.
S101, obtaining access equipment information sent by an equipment automatic discovery service, wherein the access equipment information comprises first identity information, network element subclass information and logic network elements.
It may be understood that the first identity information may be sysObjectId, sysObjectId is identity information of a device that uses SNMP protocol for data transmission, and the access device information may include sysObjectId, network element subclass information and a logical network element, where parameters of the logical network element may represent whether the device is a parameter of the access device, the logical network element may be 1 or another number, and when the logical network element is different from a preset parameter, it represents that the device is the access device, and the network element subclass information may be information including manufacturer, specialty, model and device type of the access device.
In some possible embodiments of the application, the user may configure the device auto-discovery service and connect the subsystem performing the device auto-discovery service with the acquisition framework either wired or wireless. The configured device auto-discovery service can scan the devices of the accessed system, and the scanned device conforming to the SNMP protocol sends the device information comprising the first identity information, the network element subclass information and the logic network element to the acquisition framework. The acquisition framework can perform subsequent traversal search operations after receiving the information.
And the process of configuring the device auto discovery service may include performing basic information configuration, SNMP configuration, and IP scan range configuration on a system page. The basic information may include a policy name and an execution period. The SNMP configuration information may include SNMP version, SNMP port, read community word, user name, and password. The IP scan range configuration may include an IP type and an IP address field. The device auto-discovery service discovers the access device by scanning the address field through the SNMP protocol.
It should be noted that the above wired connection manner may include connection between the mobile device and the processing module, and may also include connection between the processing module and the hardware device, and wired connection between other devices known now or developed in the future and the processing module; the wireless connection may include, but is not limited to, 3G/4G/5G connection, wiFi connection, bluetooth connection, wiMAX connection, zigbee connection, UWB (Ultra Wide Band) connection, and other now known or future developed wireless connection.
S102, inquiring whether a configuration table of the access equipment exists in a database according to the first identity information.
It will be appreciated that a device may correspond to a configuration table, or a device may correspond to some sub-items in the configuration table, where the configuration table may include identity information of several connected devices, network element subclass information, and information of multiple sub-items including logical network elements. The configuration table is an exemplary configuration table formed by configuration parameters of 6 devices in the same series, and the identity information is a sub-item in the configuration table, and when the acquisition framework cannot query the database for the corresponding identity information, the configuration table of the access device can be considered to be absent in the database.
In some embodiments of the present application, when a device is accessed, the acquisition framework may find a configuration table corresponding to the device from a database of the system according to identity information of the access device.
S103, determining that a configuration table of the access equipment exists in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table.
It is understood that the network element subclass information may be a device specialty corresponding to the device, a manufacturer of the device, a type of the device, and a model of the device. The expertise of a device may be to characterize whether the device has access to a network metropolitan area network, or an access network, or a core network, or other local or global network. The type of device may be a different type of device, such as a broadband access device, a switch or a router.
In some possible embodiments of the present application, when the acquisition framework determines that the configuration table of the access device exists in the database, the acquisition framework may continuously query whether the network element subclass information corresponding to the access device exists in the configuration table.
S104, determining that network element subclass information corresponding to the access equipment exists in the configuration table, and inquiring whether logic network elements corresponding to the access equipment exist in the configuration table.
It will be appreciated that the logical network element may characterize whether the access device is a new device or an old device that has been previously accessed, and that the logical network element may be mapped by a mapping or algorithm to a number that may be scanned or detected by the acquisition framework or to a symbol that may be scanned or detected.
In some possible embodiments of the present application, after determining that the network element subclass information corresponding to the access device exists in the configuration table, the acquisition framework may query whether the logic network element corresponding to the access device exists in the configuration table.
S105, determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework.
It is understood that the network element information may exist in the database in the form of a table, where the table of network element information is used to store the correspondence between the network element IDs and the network element IPs of all new devices in the domain. The acquisition source information may be information corresponding to a system for acquiring device information, the control interface information may be interface information between the device and the control system, and the interface information may include, but is not limited to, speed of an interface, protocol information of the interface, and the like.
In some possible embodiments of the present application, after determining that the logic network element corresponding to the access device exists in the configuration table, that is, after determining that the network element subclass information and the logic network element exist in the configuration table, the acquisition framework may automatically generate, by using an algorithm, network element information, acquisition source information and control interface information corresponding to the new device according to the network element subclass information, the logic network element, and a protocol parameter configured by the acquisition framework.
In summary, the embodiment may detect whether the first identity information exists in the configuration table by comparing the access device information with the first identity information sent by the device auto-discovery service with a preset configuration table; if so, detecting whether network element subclass information corresponding to the access equipment exists in the configuration table; if so, detecting whether a logic network element corresponding to the access equipment exists in the configuration table; if the network element information exists, generating network element information, acquisition source information and control interface information corresponding to the access equipment according to the network element detail information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The embodiment can automatically compare and match the accessed access equipment with the preset table, and can generate network element information, acquisition source information and control interface information corresponding to the access equipment for equipment acquisition after successful matching.
Further, referring to fig. 2, fig. 2 is a schematic step diagram of another automatic device collection method according to an embodiment of the present application. In fig. 2, the method for automatically collecting devices may further include step S106, determining that no configuration table of the access device exists in the database, storing the access device information into the database, and adding the configuration table corresponding to the first identity information into the database.
In some possible embodiments of the present application, the acquisition framework stores the access device information in the database, and then adds a configuration table corresponding to the first identity information in the database, where the configuration table may include one or all parameters in the network element subclass information or the logical network element.
Further, referring to fig. 3, fig. 3 is a schematic step diagram of another automatic device collection method according to an embodiment of the present application. In fig. 3, the method for automatically collecting devices of the present application may further include step S107, determining that there is no network element subclass information corresponding to the access device in the configuration table, storing the access device information in the database, and adding the network element subclass information and the new logical network element in the configuration table.
In some possible embodiments of the present application, after the configuration table corresponding to the access device is added to the database, the acquisition framework may detect the configuration table, and when it is determined that the network element subclass information corresponding to the access device does not exist in the configuration table, the acquisition framework may store the access device information to the database and add the network element subclass information and a new logical network element to the configuration table.
Further, referring to fig. 4, fig. 4 is a schematic step diagram of another automatic device collection method according to an embodiment of the present application. In fig. 4, the method for automatically collecting devices of the present application may further include S108, determining that there is no network element subclass information corresponding to the access device in the configuration table, storing the access device information in the database, and adding a new logical network element in the configuration table.
In some possible embodiments of the present application, the acquisition framework determines that there is no network element subclass information corresponding to the access device in the configuration table, and the acquisition framework may store the access device information into the database and add a new logical network element in the configuration table, where the new logical network element may characterize that the accessed device information is a new device.
Further, the step of determining that the network element subclass information corresponding to the access device exists in the configuration table may include step S201 or step S202.
S201, detecting and determining that equipment professions, equipment manufacturers, equipment types and equipment models corresponding to the access equipment exist in the configuration table.
Or alternatively
S202, detecting and determining equipment professions, equipment manufacturers, equipment types and equipment models corresponding to the access equipment in the configuration table sequentially.
It will be appreciated that the equipment profession, equipment manufacturer, equipment type, and equipment model may be numbers or characters in the configuration table. If the equipment specialty can be a character a or b or c or d, wherein the character a can correspond to the specialty of the characterization equipment to be a metropolitan area network, b can correspond to the specialty of the characterization equipment to be an access network, c can correspond to the specialty of the characterization equipment to be a core network, and d can correspond to the specialty of the characterization equipment to be a mobile network; and the device type may be a symbol or a string of numbers. If the character 101 may correspond to the model of the token device being a broadband access device, the character 102 may correspond to the model of the token device being a switch, and the character 103 may correspond to the model of the token device being a router. The device manufacturer may correspond to a company and each device model may correspond to a string.
In some possible embodiments of the present application, the acquisition framework may detect and determine that the equipment specialty, the equipment manufacturer, the equipment type and the equipment model corresponding to the access equipment exist in the configuration table at the same time, or sequentially detect and determine that the equipment specialty corresponding to the access equipment exists in the configuration table, then detect and determine that the equipment manufacturer corresponding to the access equipment exists in the configuration table, then detect and determine that the equipment type corresponding to the access equipment exists in the configuration table, and detect and determine that the equipment model corresponding to the access equipment exists in the configuration table.
Further, referring to fig. 5, fig. 5 is a schematic step diagram of another automatic device collection method according to an embodiment of the present application. In fig. 5, the device automatic acquisition method of the present application may further include step S109 of issuing the created acquisition source information and control interface information to the acquisition control service.
In some possible embodiments of the present application, after the acquisition framework obtains the acquisition source information and the control interface information, the acquisition framework may further issue the created acquisition source information and control interface information to the acquisition control service, and the acquisition control service performs final data acquisition and control of the device.
The following describes the specific implementation principle of the application with reference to the drawings:
First, a network element automatic nanotube and service automatic discovery process is performed, and referring to fig. 6, the process may include a first step to a fourth step, and in this embodiment, the system includes at least an acquisition frame and an equipment automatic discovery service.
The first step: the device automatically discovers the service to the network to discover new devices;
Specifically, referring to fig. 7, the system page performs basic information configuration, SNMP configuration and IP scan range configuration, the basic information includes a policy name, an execution period, and the like, the SNMP configuration information includes an SNMP version, an SNMP port, a read group word, a user name, a password, and the like, and the IP scan range configuration includes an IP type, an IP address field, and discovers a new device by scanning the address field through an SNMP protocol.
And a second step of: the device auto-discovery service may report the discovered new network element information to the acquisition framework;
And a third step of: the collection frame performs network batch processing on the reported data, and the process can comprise the following steps: checking, auditing, comparing and processing with the peer logic, and generating information such as acquisition sources, control interfaces and the like. Specifically, steps 1-4 can be included.
Step 1: and the framework receives new equipment information pushed by the service, queries a configuration table according to sysObjectId, and if the configuration table does not exist, can warehouse the equipment information, generates a network element detail non-existence alarm and supplements the configuration information of the configuration table corresponding to sysObjectId.
Step 2: if so, the framework can judge whether the network element subclass exists according to the profession, manufacturer, equipment type and equipment model, if any one or more of the network element subclasses does not exist or all of the network element subclasses do not exist, the framework can store equipment information, generate an alarm for the absence of the network element subclass, and manually add the network element subclasses and the logic network element.
Step 3: if yes, the framework can judge whether the logic network element exists or not, if not, the equipment information is put in storage, an alarm is generated when the logic network element does not exist, and the logic network element is manually added.
Step 4: automatically generating network element information, acquisition source information and control interface information according to the information and additional parameters (such as protocol and protocol parameters, wherein the protocol parameters can comprise user names and passwords of read-write group words of SNMP) configured by the framework.
Fourth step: the acquisition framework transmits the automatically created information such as the acquisition source, the control interface and the like to the acquisition control service.
After completing the network element automatic nanotube and service automatic discovery process, referring to fig. 8, the embodiment may perform a process of synchronizing the network element automatic nanotube with other systems, and specifically may include steps 11 to 13.
Step 11: if other systems manage network element connection information, a full amount of interfaces are required to be provided for frame inquiry, the network element increment information can be informed to the system through the sftp/ftp interface in time through the kafka or http interface. The system is a main body for maintaining network element data, other systems should be notified in time when the network element data is changed, and the system needs to ensure the integrity and accuracy of own network element connection information.
Step 12: when the received network element connection information is inconsistent, the current acquisition source and control interface connection state should be tested, if the connection fails, a new account number and password is used for connection test, and if the connection is successful, the account number and password parameters corresponding to the protocol in the database are modified.
Step 13: and when the network element deleting information is received, testing whether the connection of the acquisition source and the control interface where the network element is positioned is normal. If the connection is impossible, the list is set to be in a pre-deleting state, and the last confirmation is manually carried out to judge whether the network element is deleted.
Step 14: after the process of synchronizing the network element automatic nanotubes with other systems is carried out, the network element connection state can be monitored. Specifically, referring to fig. 9, the network element connection status monitoring may include an acquisition source connection status management function, which is a function of periodically detecting a connection status of an acquisition source by an acquisition service and reporting the detection result to an acquisition frame. The acquisition framework presents this state and serves as a reference condition for whether the acquisition source is acquiring.
When the third party system transmits the resource change data, if the third party system encounters abnormal conditions such as network interruption, unavailable service and the like, the third party system cannot transmit the resource change data to the system, at the moment, the third party system needs to ensure that the information of the resource change data is not lost, and after the network or the service is recovered, the resource change data is transmitted to the system again. In order to ensure that the interface of the data change notification is normal, a heartbeat mechanism is needed to be added into the resource change notification interface, a third party system sends heartbeat every 1 minute, and when the system can not receive the information for a long time, an interrupt alarm with the interface of the third party system needs to be generated in the system and data active synchronization is needed to be carried out once.
The system has interface calling failure when actively synchronizing the data sharing platform or the network element data (generally, full synchronization) of the resource system, and needs to be called again every 10 minutes, and after 3 times of failures, an alarm of failure of the synchronization network element of the XX system is generated.
When the data is abnormal, the system actively synchronizes or receives the data change notification, the key fields are checked, the fields which are found to be inconsistent with the requirements are returned to the other party through the interface, and synchronous data non-standard alarm is generated in the system.
The system can record the information such as data before and after the change, a data source system, time and the like when the network element and the connection data thereof are changed through the interface each time, at least one week of record is reserved, and the subsequent problem analysis and data rollback are convenient.
After network elements are accessed to the network, service scanning discovery is automatically discovered through equipment or a third party system is synchronized to the system, the system performs data verification and parameter verification on the reported network elements, automatically creates the network elements and acquisition sources after verification, and automatically matches acquisition strategies or establishes acquisition strategies according to the characteristics of the acquisition sources to automatically complete data acquisition.
Referring to fig. 10, the network element automatic acquisition (configuration, performance, alarm, log, etc. data) is divided into two types, existing acquisition policy and no acquisition policy: when the acquisition strategy exists, the acquisition strategy is associated with the acquisition source according to the conditions of the area, the manufacturer, the network element type and the like, and if the current newly-added acquisition source meets the conditions of the acquisition strategy associated with the acquisition source, the acquisition strategy is automatically matched with the newly-added acquisition source, and the acquisition service automatically executes the data acquisition and distribution of the newly-added network element. When the acquisition strategy does not exist, the acquisition strategy is automatically established and related to a new acquisition source and issued to corresponding acquisition service execution based on the definition of the cloud network resource catalog, including professions, network element types, data periods and the like, so that full-automatic data acquisition is realized. The cloud resource catalog may provide a unified, standard data list and capability list for each specialty. The data list and the capability list can refer to fig. 11, and the list contains resource data, performance data and alarm data, and provides data formats, acquisition modes and data samples of various data. The capability list may contain descriptions of capabilities, calling means, and capability addresses, etc.
In summary, the automatic equipment collection method of the application has the following advantages:
1. The related technology is to realize the network element nano tube by manual configuration or interface synchronous network element list hard coding mode. With the large-scale construction of the network, the network element receiving workload is multiplied, the time is urgent, and the network element access efficiency degradation of the current technology is obvious on the premise of a plurality of network element devices, a plurality of types, a plurality of protocols and the like. The application adopts the scan address field based on SNMP protocol to realize the automatic discovery of network elements, and the newly added network elements are connected into the system to configure the network element information, collect the source information and control interface information, thereby realizing automation and intellectualization. And the efficiency of the network element nano tube is obviously improved. Through comparison and statistics, the efficiency of the network element nanotubes by using the method of the application is greatly improved.
2. In the related art, network element data acquisition is solidified in an IT system in a hard coding mode, and both the change and the upgrade of data acquisition logic are completed in an IT system upgrading mode, so that the operation cost and the risk are high. According to the method, the network element data is automatically collected in the modes of standardization of cloud network resource directory definition, regularization of collection strategies, scripting of data processing and independent loading of protocol packages. The data acquisition efficiency can be greatly improved by comparison and statistics.
In addition, referring to fig. 12, corresponding to the method of fig. 1, an automatic device acquisition system is further provided in an embodiment of the present application, where the system may include: an acquisition unit 1001, a first processing unit 1002, a second processing unit 1003, and a third processing unit 1004. Wherein the obtaining unit 1001 may be configured to obtain access device information sent by the device auto-discovery service, where the access device information includes first identity information, network element subclass information, and a logical network element; the first processing unit 1002 may be configured to query a database for the presence of a configuration table of the access device according to the first identity information. The second processing unit 1003 is configured to determine that a configuration table of the access device exists in the database, and query whether network element subclass information corresponding to the access device exists in the configuration table. The third processing unit 1004 may be configured to determine that there is network element subclass information corresponding to the access device in the configuration table, and query whether there is a logical network element corresponding to the access device in the configuration table.
The acquiring unit may be any integrated circuit unit or a micro processor unit obtained by integrating a chip with a processing function and its peripheral circuit by the existing integration technology. The first processing unit and the second processing unit may be any integrated circuit module or a micro processor module obtained by integrating a chip with a processing function and a peripheral circuit thereof in the prior art. And the first processing unit and the second processing unit may further comprise one or more memories. One or more memories may be used to store the specific algorithms used in the compression adjustment process of the present application.
In some embodiments of the application, the acquisition unit 1001 may be located in the same gateway or device with a processor as the processing unit 1002. The acquiring unit 1001 may acquire, through a chip inside the system processor, access device information sent by the device auto-discovery service, where the access device information includes first identity information, network element subclass information, and a logical network element. The first processing unit 1002 may receive the access device information, and query whether a configuration table of the access device exists from the database according to the first identity information of the access device information. The second processing unit 1003 may determine that a configuration table of the access device exists in the database, and query whether network element subclass information corresponding to the access device exists in the configuration table. The third processing unit 1004 is configured to determine that there is network element subclass information corresponding to the access device in the configuration table, and query whether there is a logical network element corresponding to the access device in the configuration table. The fourth processing unit 1005 may determine that a logical network element corresponding to the access device exists in the configuration table, and generate network element information, acquisition source information, and control interface information corresponding to the new device according to the network element subclass information, the logical network element, and the protocol parameter configured by the acquisition framework. The acquisition unit 1001 may be any unit connected to a gateway or a processor inside a device. The acquisition unit 1001 may transmit the acquired data to the processor of the processing unit 1002 through a wired or wireless connection with the processor. The processor of the processing unit 1002 may perform data processing through an internal chip, to finally obtain a search result. The connection manner and arrangement of each specific device between the acquisition unit 1001 and the first processing unit 1002 and the second processing unit 1003, and between the second processing unit 1003 and the third processing unit 1004 and between the third processing unit 1004 and the fourth processing unit 1005 are not limited.
In summary, the system of the embodiment may detect whether the first identity information exists in the configuration table by comparing the access device information with the first identity information sent by the device auto-discovery service with a preset configuration table; if so, detecting whether network element subclass information corresponding to the access equipment exists in the configuration table; if so, detecting whether a logic network element corresponding to the access equipment exists in the configuration table; if the network element information exists, generating network element information, acquisition source information and control interface information corresponding to the access equipment according to the network element detail information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The application can automatically compare and match the accessed access equipment with the preset table, and can generate the network element information, the acquisition source information and the control interface information corresponding to the access equipment for equipment acquisition after successful matching.
Corresponding to the method of fig. 1, the embodiment of the application also provides an automatic device acquisition apparatus, the specific structure of which can refer to fig. 13, including:
At least one processor 1011;
at least one memory 1012 for storing at least one program;
When the at least one program is executed by the at least one processor, the at least one processor is caused to implement the device auto-acquisition method.
The device of the embodiment can detect whether the first identity information exists in the configuration table by comparing the access equipment information with the first identity information sent by the equipment automatic discovery service with the preset configuration table; if so, detecting whether network element subclass information corresponding to the access equipment exists in the configuration table; if so, detecting whether a logic network element corresponding to the access equipment exists in the configuration table; if the network element information exists, generating network element information, acquisition source information and control interface information corresponding to the access equipment according to the network element detail information, the logic network element and the protocol and protocol parameters configured by the acquisition framework. The device can automatically compare and match the accessed access equipment with the preset table, and can generate the network element information, the acquisition source information and the control interface information corresponding to the access equipment for equipment acquisition after successful matching.
Corresponding to the method of fig. 1, an embodiment of the present application also provides a computer readable storage medium having stored therein processor executable instructions which, when executed by a processor, are adapted to carry out the device auto-acquisition method.
The content in the embodiment of the automatic equipment acquisition method is applicable to the embodiment of the storage medium, the specific function of the embodiment of the storage medium is the same as that of the embodiment of the automatic equipment acquisition method, and the achieved beneficial effects are the same as those of the embodiment of the automatic equipment acquisition method.
In some alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed, and in which sub-operations described as part of a larger operation are performed independently.
Furthermore, while the application is described in the context of functional modules, it should be appreciated that, unless otherwise indicated, one or more of the functions and/or features may be integrated in a single physical device and/or software module or may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary to an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be apparent to those skilled in the art from consideration of their attributes, functions and internal relationships. Accordingly, one of ordinary skill in the art can implement the application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative and are not intended to be limiting upon the scope of the application, which is to be defined in the appended claims and their full scope of equivalents.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several programs for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable programs for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with a program execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the programs from the program execution system, apparatus, or device and execute the programs. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the program execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable program execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
In the foregoing description of the present specification, reference has been made to the terms "one embodiment/example", "another embodiment/example", "certain embodiments/examples", and the like, means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the application, the scope of which is defined by the claims and their equivalents.
While the preferred embodiment of the present application has been described in detail, the present application is not limited to the embodiments described above, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the present application, and these equivalent modifications and substitutions are intended to be included in the scope of the present application as defined in the appended claims.
Claims (10)
1. An automatic equipment acquisition method is characterized by comprising the following steps:
acquiring access equipment information sent by an equipment automatic discovery service, wherein the access equipment information comprises first identity information, network element subclass information and logic network elements;
Inquiring whether a configuration table of the access equipment exists or not from a database according to the first identity information;
Determining a configuration table of access equipment in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table;
determining that network element subclass information corresponding to the access equipment exists in the configuration table, and inquiring whether logic network elements corresponding to the access equipment exist in the configuration table;
determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework.
2. The method for automatic device acquisition according to claim 1, further comprising:
and determining that the configuration table of the access equipment does not exist in the database, storing the access equipment information into the database, and adding the configuration table corresponding to the first identity information into the database.
3. The method for automatic device acquisition according to claim 1, further comprising:
And determining that the network element subclass information corresponding to the access equipment does not exist in the configuration table, storing the access equipment information into a database, and adding the network element subclass information and a new logic network element into the configuration table.
4. The method for automatic device acquisition according to claim 1, further comprising:
And determining that the network element subclass information corresponding to the access equipment does not exist in the configuration table, storing the access equipment information into a database, and adding a new logic network element in the configuration table.
5. The method for automatically collecting devices according to claim 1, wherein the determining that the network element subclass information corresponding to the access device exists in the configuration table includes: and detecting and determining that the equipment specialty, the equipment manufacturer, the equipment type and the equipment model corresponding to the access equipment exist in the configuration table at the same time, or sequentially detecting and determining that the equipment specialty, the equipment manufacturer, the equipment type and the equipment model corresponding to the access equipment exist in the configuration table.
6. The method for automatic device acquisition according to claim 1, further comprising: and issuing the created acquisition source information and the control interface information to an acquisition control service.
7. An automatic device acquisition system, comprising:
the device comprises an acquisition unit, a logic network element and a service discovery unit, wherein the acquisition unit is used for acquiring access device information sent by an automatic discovery service of the device, and the access device information comprises first identity information, network element subclass information and logic network elements;
The first processing unit is used for inquiring whether a configuration table of the access equipment exists in the database according to the first identity information;
The second processing unit is used for determining that a configuration table of the access equipment exists in the database, and inquiring whether network element subclass information corresponding to the access equipment exists in the configuration table;
a third processing unit, configured to determine that there is network element subclass information corresponding to the access device in the configuration table, and query whether there is a logical network element corresponding to the access device in the configuration table;
And the fourth processing unit is used for determining that a logic network element corresponding to the access equipment exists in the configuration table, and generating network element information, acquisition source information and control interface information corresponding to the new equipment according to the network element subclass information, the logic network element and the protocol and protocol parameters configured by the acquisition framework.
8. The automated equipment harvesting system of claim 7, further comprising a fifth processing unit; the fifth processing unit is configured to determine that a configuration table of the access device does not exist in the database, store the access device information into the database and add first identity information into the configuration table, or determine that network element subclass information corresponding to the access device does not exist in the configuration table, store the access device information into the database and add the network element subclass information and a new logic network element into the configuration table, or determine that network element subclass information corresponding to the access device does not exist in the configuration table, store the access device information into the database and add the new logic network element into the configuration table.
9. An automatic acquisition device for equipment, which is characterized by comprising:
at least one processor;
At least one memory for storing at least one program;
The at least one program, when executed by the at least one processor, causes the at least one processor to implement a device auto-acquisition method as claimed in any one of claims 1-6.
10. A computer readable storage medium having stored therein processor executable instructions which, when executed by a processor, are adapted to perform a device auto-acquisition method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410139111.4A CN118041761A (en) | 2024-01-31 | 2024-01-31 | Automatic equipment acquisition method, system, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410139111.4A CN118041761A (en) | 2024-01-31 | 2024-01-31 | Automatic equipment acquisition method, system, device and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118041761A true CN118041761A (en) | 2024-05-14 |
Family
ID=90985128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410139111.4A Pending CN118041761A (en) | 2024-01-31 | 2024-01-31 | Automatic equipment acquisition method, system, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118041761A (en) |
-
2024
- 2024-01-31 CN CN202410139111.4A patent/CN118041761A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113112086B (en) | Intelligent production system based on edge calculation and identification analysis | |
| US8528039B2 (en) | System for and method of set-top box memory monitoring | |
| CN110659109B (en) | System and method for monitoring openstack virtual machine | |
| CN107612779B (en) | Secondary safety protection network equipment of dispatching data network and service operation monitoring system | |
| CN103118383B (en) | System and method for comprehensively supervising wireless access point state | |
| CN111343029B (en) | Monitoring platform and method based on topology monitoring of data forwarding nodes | |
| CN110209518A (en) | A kind of multi-data source daily record data, which is concentrated, collects storage method and device | |
| CN113849553A (en) | Substation data acquisition and processing method and system based on Internet of things equipment data acquisition | |
| CN114363222A (en) | Network equipment inspection method and system based on Netconf protocol | |
| CN110661811A (en) | Firewall policy management method and device | |
| CN115033657A (en) | Inquiry method, device and equipment based on knowledge graph and storage medium | |
| CN117389830A (en) | Cluster log acquisition method and device, computer equipment and storage medium | |
| CN103888300A (en) | Network failure analysis system and method in Web service system | |
| CN111371570A (en) | Fault detection method and device for NFV network | |
| CN118041761A (en) | Automatic equipment acquisition method, system, device and medium | |
| CN116431324A (en) | Edge system based on Kafka high concurrency data acquisition and distribution | |
| KR20160023356A (en) | Apparatus and method for managing identification of electric power facilities | |
| CN117007098A (en) | Material inspection flow control method and device, storage medium and electronic equipment | |
| CN117376417B (en) | Data acquisition method, system, device, computing equipment and storage medium | |
| CN112436993B (en) | VPN private line discovery method and device based on configuration file analysis | |
| CN113949620B (en) | Special line link monitoring method and system | |
| CN111917609B (en) | Network equipment connectivity monitoring method and system | |
| Doliwa et al. | Network monitoring and management for company with hybrid and distributed infrastructure | |
| CN113505165A (en) | Sensor data processing method and device, computer equipment and storage medium | |
| KR20130095767A (en) | Management of network configuration in telecommunications networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |