Disclosure of Invention
The embodiment of the application provides a network element management method, a network element management device and a storage medium, which are used for solving the technical problem of low efficiency caused by the fact that the existing SDN network fault needs to be repaired manually.
In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:
an embodiment of the present application provides a network element management method, including:
acquiring target network element information of a target network element, wherein the target network element information comprises a target network element identifier and a target fault identifier of the target network element;
calling a preset fault information dictionary, wherein the fault information dictionary comprises fault identification and fault repair information of at least one fault;
determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification;
and restoring the target network element according to the target network element identification and the target fault restoration information.
In the network element management method provided in the embodiment of the present application, the step of determining, in the fault information dictionary, target fault repair information corresponding to the target network element according to the target fault identifier includes:
confirming a target fault identification related to the target fault identification in the fault information dictionary;
and determining the fault repairing information corresponding to the target fault identification as target fault repairing information.
In the network element management method provided in the embodiment of the present application, the step of obtaining target network element information of a target network element includes:
receiving network element information of a network element, wherein the network element information comprises network element identification and state information;
when the state information comprises the fault identification, determining the network element of which the state information comprises the fault identification as a target network element;
and determining the network element information of the target network element as target network element information.
In the network element management method provided in the embodiment of the present application, the step of obtaining target network element information of a target network element includes:
sending a network element information calling instruction to a network element;
determining the network element which does not respond to the network element information calling instruction as a target network element;
generating a target fault identifier according to the unresponsive state of the target network element;
and generating a target network element identifier of the target network element according to the network element information calling instruction, and generating target network element information according to the target network element identifier and the target fault identifier.
In the network element management method provided in the embodiment of the present application, the step of sending the network element information invoking instruction to the network element includes:
acquiring the reporting state of network element information reported by each network element;
determining the network elements with abnormal reporting states as candidate network elements;
and sending a network element information calling instruction to the candidate network element.
In the network element management method provided in the embodiment of the present application, the step of repairing the target network element according to the target network element identifier and the target fault repair information includes:
determining a replacement network element according to the target network element identifier and the target fault repair information:
acquiring configuration information of the target network element according to the target network element identifier;
and issuing the configuration information to the replacement network element so that the replacement network element performs initialization configuration according to the configuration information.
In the network element management method provided in the embodiment of the present application, the target network element identifier includes a target network element type identifier and a target cluster address identifier; the step of determining a replacement network element according to the target network element identifier and the target fault repair information includes:
and determining the replacement network element according to the target network element type identifier and the target cluster address identifier, wherein the network element type identifier of the replacement network element is the same as the target network element type identifier, and the cluster address identifier of the replacement network element is the same as the target cluster address identifier.
In the network element management method provided in the embodiment of the present application, the step of repairing the target network element according to the target network element identifier and the target fault repair information includes:
generating fault address information according to the target network element identifier, and generating fault content according to the target fault repairing information;
displaying a network element repairing interface, wherein the network element repairing interface comprises a fault information displaying area and a repairing condition setting area, and displaying the fault address information and the fault content through the fault information displaying area;
and acquiring a repair instruction through the repair condition setting area, and repairing the target network element according to the repair instruction.
The application also provides a network element management device, which comprises
A data obtaining unit, configured to obtain target network element information of a target network element, where the target network element information includes a target network element identifier and a target fault identifier of the target network element;
the system comprises a calling unit, a fault information processing unit and a fault recovery unit, wherein the calling unit is used for calling a preset fault information dictionary, and the fault information dictionary comprises at least one fault identifier and fault recovery information of a fault;
the data processing unit is used for determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification;
and the fault repairing unit is used for repairing the target network element according to the target network element identifier and the target fault repairing information.
The present application further provides a storage medium, which stores a plurality of instructions, which can be loaded by a processor to execute the network element management method according to any one of the preceding claims.
The beneficial effect of this application: the application provides a network element management method, a device and a storage medium, the network element management method is characterized in that target network element information of a target network element is obtained, the target network element information comprises a target network element identifier and a target fault identifier of the target network element, the fault type of the target network element is convenient to determine according to the target fault identifier, a preset fault information dictionary is called, the fault information dictionary comprises at least one fault identifier and fault repair information of a fault, then the target fault repair information corresponding to the target network element is determined in the fault information dictionary according to the target fault identifier, and finally the target network element is repaired according to the target network element identifier and the target fault repair information, for example, the service of the target network element with the fault is directly transferred to other network elements, or the service is reconfigured after network topology configuration calculation is carried out on the current normal network element, the method and the device realize the identification of different fault types and the automatic repair aiming at different fault types, avoid the complex operation that technicians need to check and confirm the fault positions and the specific fault types one by one and then repeatedly try to confirm the mode of repairing the network, improve the fault processing efficiency and reduce the network operation and maintenance cost.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application provides a network element management method, a network element management device and a storage medium, wherein the network element management method is used for determining a fault type of a target network element according to a target fault identification and calling a preset fault information dictionary by acquiring target network element information of the target network element, wherein the target network element information comprises the target network element identification and the target fault identification of the target network element, the fault information dictionary comprises at least one fault identification and fault repair information of a fault, then the target fault repair information corresponding to the target network element is determined in the fault information dictionary according to the target fault identification, and finally the target network element is repaired according to the target network element identification and the target fault repair information, so that the identification of different fault types and the automatic repair of different fault types are realized, and technicians are prevented from repeatedly trying to confirm the repair of the fault position and the specific fault type one by one check and then trying to confirm the repair The cumbersome operation of the network approach.
Referring to fig. 1, fig. 1 is a schematic view of a scenario of a network element management system according to an embodiment of the present application. The network element management method of the embodiment of the application is applied to the network element management system, the network element management system may include a device and a server, the device and the server may be connected and communicated in a network or other manners through various playing gateways, the device may include aterminal 11, the server may include adata server 12 and a communication server, the communication server is not shown in fig. 1, and the like, wherein:
the device and the server are specifically applied in a Software Defined Network (SDN) scenario, where theterminal 11 includes, but is not limited to, Network elements such as a Data center Network element, an access Network element, and a service Network element in each Network element cluster in the SDN scenario, specifically, the Data center Network element may be a Data Center Switch (DCSW), the access Network element and the service Network element may be Virtual switches (vSwitch), and theData server 12 may be a controller connected to each Network element.
Thedata server 12 may obtain target network element information of a target network element, where the target network element information includes a target network element identifier and a target fault identifier of the target network element; calling a preset fault information dictionary, wherein the fault information dictionary comprises fault identification and fault repair information of at least one fault; determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification; and restoring the target network element according to the target network element identification and the target fault restoration information.
IT should be noted that in the Network Virtualization technology, many Network element devices are in a software form that is converted from traditional specific hardware to general hardware, such as Network Function Virtualization (NFV), specifically, the Network Function Virtualization technology, and the functions of the traditional communication Network are realized through IT Virtualization. A Virtual Network Function (VNF) is a network element virtualized by a virtualization technology to implement a certain network function unit. VNF refers specifically to a virtual network function, providing some network service, deployed in a virtual machine, container, or a barrel-metal physical machine using the infrastructure provided by NFVI.
It should be noted that the system scenario diagram shown in fig. 1 is an example, and the server and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the occurrence of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
The following describes in detail the processing of the data implemented by the network element management method with reference to a specific embodiment:
referring to fig. 1 and fig. 2, fig. 2 is a schematic block diagram of a flow of a network element management method provided in an embodiment of the present application, where the network element management method is applied to thedata server 12 in the embodiment shown in fig. 1, and the network element management method includes the following steps:
210: acquiring target network element information of a target network element, wherein the target network element information comprises a target network element identifier and a target fault identifier of the target network element;
in an embodiment, the step of obtaining target network element information of a target network element includes:
receiving network element information of a network element, wherein the network element information comprises network element identification and state information;
when the state information comprises the fault identification, determining the network element of which the state information comprises the fault identification as a target network element;
and determining the network element information of the target network element as target network element information.
It can be understood that, in the software-defined network, network elements such as a data center network element, an access network element, a service network element, and the like all send network element information to thedata server 12 during the operation process, specifically, a management address of thedata server 12 is preset in an initialization stage of the software-defined network, and when the network elements are operated online, the network element information is sent to thedata server 12 according to the management address.
It should be noted that, a software-defined network may include a plurality of network element clusters, different network element clusters are distributed in different data center machine rooms, the cluster address identifiers are used to distinguish network elements located at different network element cluster positions, the network element type identifiers are used to distinguish different types of network elements, when the cluster address identifiers of two network elements are the same, different types of network elements in the same network element cluster may be distinguished through the network element type identifiers, the network element address identifiers may distinguish different network elements, when the cluster address identifiers and the network element type identifiers of two network elements are the same, network elements of the same type but different positions in the same network element cluster may be distinguished through the network element address identifiers, wherein the cluster address identifiers may be set according to address information of the data center machine room where the network element cluster is located, and the cluster address identifiers may be physical placement and operation places of various computers and communication devices used by the data center, for example, the cluster address identifier may be "Wuhan", and meanwhile, the network element type identifier may be set according to a specific type of the network element. For example, when the network element is a data center network element type, the network element type identifier of the network element may be "DCSW", the network element address identifier may be set according to a specific device ID of the network element, different network elements have different device IDs, and of course, the cluster address identifier, the network element type identifier, and the network element address identifier in the network element identifier may form a character string, which is not described herein again.
It should be noted that the state information may include operation state information such as flow information and a fault identifier when the network element operates, and when the state information includes the fault identifier, the network element whose state information includes the fault identifier is determined as a target network element, it can be understood that in this embodiment, the target network element is determined by determining whether the fault identifier exists in the state information, specifically, different fault identifiers may be set for different faults and form a fault identifier set, and when the fault identifier which is the same as the fault identifier set exists in the state information, the network element whose state information includes the fault identifier is determined as the target network element, where the fault identifier set may be obtained from a preset fault information dictionary and is not described herein again. Further, the network element information of the target network element is determined as target network element information, that is, the network element information of the target network element is determined as target network element information, a network element identifier in the network element information of the target network element is determined as a target network element identifier, and meanwhile, a fault identifier in the network element information of the target network element is used as a target fault identifier.
It is to be noted that the fault identifier uploaded by the network element may be generated according to a preset policy, specifically, a fault identifier is correspondingly set and stored in the network element in advance for each fault content that may be generated by a known network element, and the network element may generate the fault identifier according to the preset policy and the detected fault content, for example, the fault content may be classified according to the fault identifier, for example: the device fault, the network fault, and the software fault may be classified and identified, where the fault identifier of the device fault includes a "GZ 001" field, specifically, the fault identifier of the power failure in the device fault may be "GZ 001DY 01", in addition, the fault identifier of the network fault may include a "GZ 002" field, and the fault identifier of the software fault may include a "GZ 003" field, which is not described herein again.
When the state information comprises the fault identification, determining the network element of which the state information comprises the fault identification as a target network element;
in an embodiment, the step of obtaining target network element information of a target network element includes:
sending a network element information calling instruction to a network element;
determining the network element which does not respond to the network element information calling instruction as a target network element;
generating a target fault identifier according to the unresponsive state of the target network element;
and generating a target network element identifier of the target network element according to the network element information calling instruction, and generating target network element information according to the target network element identifier and the target fault identifier.
It should be noted that, the data server 12 may obtain the network element information by actively sending a network element information invoking instruction to the network element, specifically, may actively send the network element information invoking instruction to the network element, and determine the network element that does not respond to the network element information invoking instruction as the target network element, obviously, after sending the network element information invoking instruction to the network element, when a response of the network element is not received, it may be determined that the network element that does not respond to the network element information invoking instruction is the target network element, in this embodiment, the network element that does not respond to the network element information invoking instruction is a fault that cannot feed back the network element information to the data server, at this time, the data server 12 conveniently determines the network element that is the target network element by actively sending the network element information invoking instruction to the network element, and further, may generate the target fault identifier according to the non-response state of the target network element, specifically, the unresponsive state of the target network element may individually correspond to a fault identifier, and in addition, the target network element identifier of the target network element may be generated according to the network element information invoking instruction, it may be understood that the network element information invoking instruction includes the network element identifier of the network element, that is, the network element information invoking instruction transmits the content in the network element information invoking instruction to the specified network element through the included network element identifier, and finally, the target network element information is generated according to the target network element identifier and the target fault identifier, so that the target network element information of the target network element is acquired.
In this embodiment, the step of sending the network element information invoking instruction to the network element includes:
acquiring the reporting state of network element information reported by each network element;
determining the network elements with abnormal reporting states as candidate network elements;
and sending a network element information calling instruction to the candidate network element.
It should be noted that, as described above, in the software defined network, the network element may periodically send the network element information to thedata server 12, and thedata server 12 may obtain the reporting state of the network element information reported by each network element according to whether each network element reports the network element information in each period, specifically, the network element that does not report the network element information in one period may be determined as a candidate network element, and then a network element information retrieval instruction is sent to the candidate network element.
It should be noted that, the obtaining of the reporting status of the network element information reported by each network element may also be performed according to the time node reported by the network element, specifically, obtaining the receiving time node that has received the network element information of a network element last time, and obtaining the current time node, when the time difference between the receiving time node and the current time node is greater than the preset time threshold and the next network element information of the network element is not received, determining the reporting state of the network element as abnormal reporting state and determining the network element as a candidate network element, and finally sending a network element information calling instruction to the candidate network element, the network element information retrieval instruction is only sent to the candidate network element, and specifically, the network element identifier of the candidate network element may be obtained from the network element information fed back by the candidate network element last time, so as to determine the network element position sent by the network element information retrieval instruction. Illustratively, the receiving time node for obtaining the network element information of the last receiving network element is "8: 55", the current time node is "8: 59", the preset time threshold may be 3 minutes, at this time, the time difference between the receiving time node and the current time node is 4 minutes and is greater than the preset time threshold, and the network element information of the next time of the network element is not received yet, the reporting state of the network element is determined to be abnormal, and the network element is determined to be a candidate network element.
It should be noted that the current time node is the local time of the server, for example, if the server is set in a place where the beijing time is adopted, the current time is the beijing time, and the server can periodically update the local time through the beijing system to ensure the time accuracy.
220: calling a preset fault information dictionary, wherein the fault information dictionary comprises fault identification and fault repair information of at least one fault;
in an embodiment, the fault information dictionary may be preset in thedata server 12, and specifically, beforestep 210, the method may further include creating a fault information dictionary, where the fault information dictionary includes fault identifiers and fault repair information of at least one fault, where the fault identifiers and the fault repair information may be set in the fault information dictionary in a preset manner, each fault identifier is at least bound with one fault repair information, different fault identifiers correspond to different faults, and the fault information dictionary is adopted to facilitate indexing of the fault repair information of different faults according to the fault identifiers, so as to facilitate efficient confirmation of the fault repair information of different faults.
230: determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification;
in an embodiment, the step of determining, in the fault information dictionary, target fault repair information corresponding to the target network element includes:
confirming a target fault identification related to the target fault identification in the fault information dictionary;
and determining the fault repairing information corresponding to the target fault identification as target fault repairing information.
It should be noted that, the target fault identifier related to the target fault identifier in the fault information dictionary may be determined by traversing the fault identifiers in the fault information dictionary, comparing the fault identifiers in the fault information dictionary with the target fault identifiers one by one, determining the fault identifier in the fault information dictionary that is the same as the target fault identifier field as the target fault identifier, and determining the fault repair information corresponding to the target fault identifier as the target fault repair information, where the target fault identifier and the target fault repair information are bound to each other in the fault information dictionary. Illustratively, when the target fault identifier is "GZ 001DY 01", traversing the fault identifiers in the fault information dictionary, and determining the fault identifier in the fault information dictionary, which is the same as the field of "GZ 001DY 01", as the target fault identifier.
It is to be understood that, as mentioned above, the faults of types such as device fault, network fault and software fault all have specific classification fields in the fault identifications, and in the process of confirming the target fault identification related to the target fault identification in the fault information dictionary, the fault type of the target fault identification may be determined first by the classification fields corresponding to the types such as device fault, network fault and software fault, and then the target fault identification is determined in the fault identifications of the related fault types, illustratively, the classification field corresponding to the device fault is "GZ 001", the classification field corresponding to the network fault is "GZ 002", the classification field corresponding to the software fault is "GZ 003", when the target fault identification is "GZ 001DY 01", the fault corresponding to the target fault identification may be determined to be device fault by "GZ 001" in the target fault identification, and then traversing the fault identifications related to the equipment faults in the fault information dictionary to determine the target fault identifications.
240: and restoring the target network element according to the target network element identification and the target fault restoration information.
In an embodiment, the step of repairing the target network element according to the target network element identifier and the target failure repair information includes:
determining a replacement network element according to the target network element identifier and the target fault repair information:
acquiring configuration information of the target network element according to the target network element identifier;
and issuing the configuration information to the replacement network element so that the replacement network element performs initialization configuration according to the configuration information.
It should be noted that, as mentioned above, the target network element identifier includes a target cluster address identifier, a target network element type identifier, and a target network element address identifier, thedata server 12 can determine the location of the target network element through the target network element identifier, and, the configuration information of the target network element can also be obtained according to the target network element identifier, the replacement network element is used for bearing the function of the target network element in the network, it is understood that thedata server 12 may have the function of automatic networking configuration in the software defined network, the configuration information of each network element may be uniformly managed by thedata server 12, in an initialization stage of the software defined network, thedata server 12 may pre-allocate and store configuration information of each network element, and specifically, the configuration information may include network element type information, link information, and the like of the network element.
In this embodiment, specifically, the replacement network element may perform initialization configuration according to network element type information, link information, and the like in the configuration information, obviously, the type of the replacement network element that completes initialization configuration is the same as the type of the target network element, and the replacement network element configures a link in a software-defined network according to the link information, so as to implement an effect of replacing the target network element with the replacement network element in the software-defined network.
In an embodiment, the target network element identifier includes a target network element type identifier and a target cluster address identifier; the step of determining a replacement network element according to the target network element identifier and the target fault repair information includes:
and determining the replacement network element according to the target network element type identifier and the target cluster address identifier, wherein the network element type identifier of the replacement network element is the same as the target network element type identifier, and the cluster address identifier of the replacement network element is the same as the target cluster address identifier.
It can be understood that, determining the replacement network element according to the target network element type identifier and the target cluster address identifier, that is, taking a network element that is located in the same network element cluster as the target network element and has the same network element type as the target network element as the replacement network element, and in addition, in the process of software-defined network initialization configuration, a standby network element is preset, and determining the replacement network element according to the target network element type identifier and the target cluster address identifier, or taking the standby network element as the replacement network element.
In an embodiment, as shown in fig. 3, the step of repairing the target network element according to the target network element identifier and the target failure repair information includes:
generating fault address information according to the target network element identifier, and generating fault content according to the target fault repairing information;
a network element repairing interface is displayed, the network element repairing interface comprises a faultinformation display area 301 and a repairingcondition setting area 302, and the fault address information and the fault content are displayed through the faultinformation display area 301;
and obtaining a repair instruction through the repaircondition setting area 302, and repairing the target network element according to the repair instruction.
It should be noted that, the data server 12 generates fault address information according to the target network element identifier, generates fault content according to the target fault repairing information, and displays a network element repairing interface in a display unit such as a display, where the network element repairing interface includes a fault information display area 301 and a repairing condition setting area 302, and the fault address information and the fault content are displayed through the fault information display area 301; specifically, the fault address information includes a network element cluster position where the target network element is specifically located, a network element type of the target network element, a specific device ID of the target network element, and the like, and the fault content may be obtained by a target fault identifier corresponding to the target fault repairing information, and in addition, a repairing instruction is obtained by the repairing condition setting area 302, and the target network element is repaired according to the repairing instruction, for example, a control of "one-key recovery" is provided in the repairing condition setting area 302, and a technician may refer to the fault address information and the fault content displayed in the fault information display area 301 in the network element repairing interface, and input a repairing instruction in the repairing condition setting area 302, for example: the technical personnel can click the one-key recovery control, the data server receives the one-key recovery repair instruction, network topology configuration calculation is carried out on the current normal network element again according to the one-key recovery repair instruction, and each network element is reconfigured to recover the normal operation of the software defined network.
Correspondingly, the present application further provides a network element management device, and fig. 4 is a schematic structural diagram of the network element management device provided in the embodiment of the present application; referring to fig. 4, the network element management apparatus includes the following modules:
adata obtaining unit 401, configured to obtain target network element information of a target network element, where the target network element information includes a target network element identifier and a target fault identifier of the target network element;
acalling unit 402, configured to call a preset fault information dictionary, where the fault information dictionary includes fault identifiers and fault repair information of at least one fault;
adata processing unit 403, configured to determine, according to the target fault identifier, target fault repair information corresponding to the target network element in the fault information dictionary;
afault repairing unit 404, configured to repair the target network element according to the target network element identifier and the target fault repairing information.
In an embodiment, thedata processing unit 403 is further configured to identify a target fault identifier in the fault information dictionary, which is related to the target fault identifier; and determining the fault repairing information corresponding to the target fault identification as target fault repairing information.
In an embodiment, thedata obtaining unit 401 is further configured to receive network element information of a network element, where the network element information includes a network element identifier and status information; when the state information comprises the fault identification, determining the network element of which the state information comprises the fault identification as a target network element; and determining the network element information of the target network element as target network element information.
In an embodiment, thedata obtaining unit 401 is further configured to send a network element information retrieving instruction to a network element; determining the network element which does not respond to the network element information calling instruction as a target network element; generating a target fault identifier according to the unresponsive state of the target network element; and generating a target network element identifier of the target network element according to the network element information calling instruction, and generating target network element information according to the target network element identifier and the target fault identifier.
In an embodiment, thedata obtaining unit 401 is further configured to obtain a reporting state of network element information reported by each network element; determining the network elements with abnormal reporting states as candidate network elements; and sending a network element information calling instruction to the candidate network element.
In an embodiment, thefailure recovery unit 404 is further configured to determine, according to the target network element identifier and the target failure recovery information, a replacement network element: acquiring configuration information of the target network element according to the target network element identifier; and issuing the configuration information to the replacement network element so that the replacement network element performs initialization configuration according to the configuration information.
In an embodiment, the target network element identifier includes a target network element type identifier and a target cluster address identifier; thefault repairing unit 404 is further configured to determine the replacement network element according to the target network element type identifier and the target cluster address identifier, where the network element type identifier of the replacement network element is the same as the target network element type identifier, and the cluster address identifier of the replacement network element is the same as the target cluster address identifier.
In an embodiment, thefault repairing unit 404 is further configured to generate fault address information according to the target network element identifier, and generate fault content according to the target fault repairing information; displaying a network element repairing interface, wherein the network element repairing interface comprises a fault information displaying area and a repairing condition setting area, and displaying the fault address information and the fault content through the fault information displaying area; and acquiring a repair instruction through the repair condition setting area, and repairing the target network element according to the repair instruction.
Accordingly, an embodiment of the present application further provides a data server, and as shown in fig. 5, the data server may include Radio Frequency (RF)circuit 501,memory 502 including one or more computer-readable storage media,input unit 503,display unit 504,sensor 505,audio circuit 506, Wireless Fidelity (WiFi)module 507,central processing unit 508 including one or more processing cores, andpower supply 509. Those skilled in the art will appreciate that the data server architecture shown in FIG. 5 does not constitute a limitation of data servers and may include more or fewer components than shown, or some combination of components, or a different arrangement of components. Wherein:
theRF circuit 501 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information from a base station and then sends the received downlink information to one or morecentral processing units 508 for processing; in addition, data relating to uplink is transmitted to the base station. Thememory 502 may be used to store software programs and modules, and thecentral processor 508 executes various functional applications and data processing by operating the software programs and modules stored in thememory 502. Theinput unit 503 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Thedisplay unit 504 may be used to display information input by or provided to the user and various graphical user interfaces of the data server, which may be made up of graphics, text, icons, video, and any combination thereof.
The data server may also include at least onesensor 505, such as light sensors, motion sensors, and other sensors. Theaudio circuitry 506 includes speakers that can provide an audio interface between the user and the data server.
WiFi belongs to short distance wireless transmission technology, and the data server can help the user to send and receive e-mail, browse web page and access streaming media etc. throughWiFi module 507, which provides wireless broadband internet access for the user. Although fig. 5 shows theWiFi module 507, it is understood that it does not belong to the essential constitution of the data server, and may be omitted entirely as needed within the scope of not changing the essence of the application.
Thecpu 508 is a control center of the data server, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the data server and processes data by operating or executing software programs and/or modules stored in thememory 502 and calling data stored in thememory 502, thereby performing overall monitoring of the mobile phone.
The data server also includes a power supply 509 (e.g., a battery) for supplying power to the various components, which may preferably be logically connected to thecentral processor 508 via a power management system, so as to manage charging, discharging, and power consumption via the power management system.
Although not shown, the data server may further include a camera, a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, thecentral processing unit 508 in the data server loads the executable file corresponding to the process of one or more application programs into thememory 502 according to the following instructions, and thecentral processing unit 508 runs the application program stored in thememory 502, so as to implement the following functions:
acquiring target network element information of a target network element, wherein the target network element information comprises a target network element identifier and a target fault identifier of the target network element;
calling a preset fault information dictionary, wherein the fault information dictionary comprises fault identification and fault repair information of at least one fault;
determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification;
and restoring the target network element according to the target network element identification and the target fault restoration information.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description, and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, where the computer program can be loaded by a computer or a processor to implement the following functions:
acquiring target network element information of a target network element, wherein the target network element information comprises a target network element identifier and a target fault identifier of the target network element;
calling a preset fault information dictionary, wherein the fault information dictionary comprises fault identification and fault repair information of at least one fault;
determining target fault repair information corresponding to the target network element in the fault information dictionary according to the target fault identification;
and restoring the target network element according to the target network element identification and the target fault restoration information.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the instructions stored in the storage medium can execute the steps in any method provided in the embodiments of the present application, the beneficial effects that can be achieved by any method provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The network element management method, the network element management device, the data server and the computer-readable storage medium provided by the embodiments of the present application are introduced in detail, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.