Network device visualization method, nonvolatile storage medium and computer device

Abstract

The invention discloses a network device visualization method, a nonvolatile storage medium and a computer device. The method comprises the steps that case data of target network equipment and daughter card data of an equipment daughter card are acquired, and the equipment daughter card is inserted into a slot position in the target network equipment; determining a frame module of a case in the target network equipment according to the case data based on a tag language of a scalable vector graph; determining an equipment daughter card module of the equipment daughter card according to the daughter card data based on a tag language of a scalable vector graph; and visualizing the device daughter card module and the frame module to obtain a target network device module. According to the method and the device, the technical problem that the network equipment is difficult to efficiently and flexibly configure because the display of the network equipment is mostly described in the form of characters, tables and the like or is displayed in the form of static pictures at present is solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a network device visualization method, a non-volatile storage medium and a computer device. Background Art

[0002] In common network operation and maintenance systems, the display of device status is mostly described in the form of text or tables, without displaying detailed equipment drawings, and unable to display an intuitive view of the equipment model. Some network operation and maintenance systems can display detailed equipment drawings and can display real-time status according to different equipment. However, due to the complexity of network equipment types, the large number of pluggable interface cards, and the flexible installation methods, the common Web-side presentation or static equipment display with static images cannot meet the needs of flexible configuration and installation. Highly customized development is required, which limits the actual board selection and installation method of the equipment. Some network operation and maintenance systems use a Canvas-based technical framework for functional development. Although they can be visualized according to the actual equipment situation, they have a long development cycle and low development efficiency.

[0003] Therefore, the current network equipment visualization has technical problems such as difficulty in meeting the needs of flexible configuration, long development cycle and low efficiency.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a network device visualization method, a non-volatile storage medium and a computer device, so as to at least solve the technical problem that the current display of network devices is mostly described in the form of text tables, or displayed as static pictures, which is difficult to configure efficiently and flexibly.

[0006] According to one aspect of an embodiment of the present invention, a network device visualization method is provided, comprising: obtaining chassis data of a target network device and subcard data of a device subcard, wherein the device subcard is inserted into a slot in the target network device; determining a framework module of a chassis in the target network device according to the chassis data based on a label language of scalable vector graphics; determining a device subcard module of the device subcard according to the subcard data based on a label language of scalable vector graphics; and visualizing the device subcard module and the framework module to obtain a target network device module.

[0007] Optionally, based on the label language of scalable vector graphics, according to the chassis data, a framework module of the chassis in the target network device is determined, wherein the chassis in the target network device includes an empty chassis and slots, including: according to the chassis size in the chassis data, based on the label language of scalable vector graphics, determining to obtain the empty chassis module of the chassis in the target network device; according to the slot information in the chassis data, based on the label language of scalable vector graphics, in a preset order, sequentially adding slots to the empty chassis module to obtain the framework module, wherein the slots are arranged inside the empty chassis for inserting device sub-cards.

[0008] Optionally, based on a label language of scalable vector graphics, according to the subcard data, a device subcard module of the device subcard is determined, wherein the device subcard includes an empty subcard and subcards of multiple models, including: determining the size of the empty subcard according to the slot size in the chassis data; determining the empty subcard module corresponding to the empty subcard based on the label language of scalable vector graphics according to the size of the empty subcard; determining the subcard modules corresponding to each of the multiple models of subcards based on the label language of scalable vector graphics according to the subcard data corresponding to each of the multiple models of subcards; obtaining the device subcard module of the device subcard based on the empty subcard module and the subcard modules corresponding to each of the multiple models of subcards.

[0009] Optionally, according to the subcard data corresponding to each of the multiple models of subcards and based on the label language of scalable vector graphics, subcard modules corresponding to each of the multiple models of subcards are determined, including: selecting empty subcard modules corresponding to each of the multiple models of subcards according to the subcard sizes corresponding to each of the multiple models of subcards; and adjusting the empty subcard modules corresponding to each of the multiple models of subcards based on the label language of scalable vector graphics according to the subcard data corresponding to each of the multiple models of subcards, so as to obtain subcard modules corresponding to each of the multiple models of subcards.

[0010] Optionally, obtain a slot mapping relationship of the target network device, wherein the slot mapping relationship represents a correspondence between a slot number and slot information; based on the slot mapping relationship, insert an empty subcard module into a framework module to obtain an initial device module of the target network device; visualize the initial device module to display the initial device module.

[0011] Optionally, based on the chassis data, determine the slot distribution and slot information in the target network device, wherein the slot information includes the slot name and slot size; based on the slot distribution, number the slots in the target network device to obtain slot identifiers corresponding to the slots; based on the slot identifiers and the slot information, obtain a slot mapping relationship.

[0012] Optionally, the device sub-card module and the framework module are visualized to obtain the target network device module, including: receiving device requirements based on the target account input, wherein the device requirements include the model of the target sub-card and the slot corresponding to the target sub-card; according to the device requirements, selecting the sub-card module corresponding to the target sub-card from the sub-card modules and inserting it into the framework module, and visualizing the framework module and the target sub-card to obtain the target network device module.

[0013] Optionally, the port status information in the target subcard is obtained; and the port status information of the target subcard and the target network device module are displayed.

[0014] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is provided, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any one of the above-mentioned network device visualization methods.

[0015] According to another aspect of the embodiments of the present invention, a computer device is provided. The computer device includes a processor, and the processor is used to run a program. When the program is run, any one of the above-mentioned network device visualization methods is executed.

[0016] According to yet another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, any one of the above-mentioned network device visualization methods is implemented.

[0017] In an embodiment of the present invention, a network device visualization method is adopted, by acquiring chassis data of a target network device and subcard data of a device subcard; determining a framework module of a chassis in a target network device according to the chassis data based on a label language of scalable vector graphics; determining a device subcard module of a device subcard according to the subcard data based on a label language of scalable vector graphics; generating a target network device module of a target network device according to the device subcard module and the framework module based on a preset slot mapping relationship in the target network device, thereby achieving the purpose of visualizing the device framework and subcard separately, thereby realizing the technical effect of improving the flexibility of network device visualization, and further solving the technical problem that the current display of network devices is mostly described in the form of text tables, etc., or displayed in static pictures, and is difficult to be efficiently and flexibly configured. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0019] Figure 1 A hardware structure block diagram of a computer terminal for implementing a method for visualizing network equipment is shown;

[0020] Figure 2 is a flow chart of a method for visualizing a network device according to an embodiment of the present invention;

[0021] Figure 3 is a schematic diagram of a system framework of a network device visualization method provided according to an optional embodiment of the present invention;

[0022] Figure 4 is a schematic diagram of an empty chassis module according to a network device visualization method provided by an optional embodiment of the present invention;

[0023] Figure 5 It is a schematic diagram of slot distribution of an optional model of a network device in an optional embodiment of the present invention;

[0024] Figure 6 is a schematic diagram of an empty daughter card module of a network device visualization method provided in an optional embodiment of the present invention;

[0025] Figure 7 is an initial device schematic diagram of a network device visualization method provided by an optional embodiment of the present invention;

[0026] Figure 8 is a schematic diagram of a specific device daughter card module of a network device visualization method provided in an optional embodiment of the present invention;

[0027] Fig. 9 is a schematic diagram of a target network device according to a network device visualization method provided by an optional embodiment of the present invention;

[0028] Fig.10 It is a module diagram of a network device visualization method provided according to an optional embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretations:

[0032] Network equipment is the basic unit for building a network. Common equipment components include routers, switches, firewalls, etc. Medium and large equipment usually have multiple slots for installing various pluggable modules and components, such as power modules, interface cards, etc., to achieve basic and extended functions. The operating status of equipment components, equipment ports, etc. can directly reflect the status of network equipment and timely discover network fault points. Therefore, the visualization of equipment component status is particularly important in the network operation and maintenance system.

[0033] SVG (Scalable Vector Graphics) is an XML-based markup language used to describe two-dimensional vector graphics. It can not only display static graphics without distortion, but also display complex animation effects and integrate rich interactive functions. The XML markup language it uses is consistent with Vue's MVVM framework, which facilitates the effect of data-driven view images, achieving the purpose of flexible data configuration and complex and changeable visualization.

[0034] Vue is a web-based JavaScript framework for building user interfaces and single-page applications. It focuses on the view layer and provides responsive and componentized view components, making it easy and efficient to build interactive web interfaces. It can be used as the basic framework for the web interface of a network operation and maintenance system.

[0035] According to an embodiment of the present invention, a method embodiment of a network device visualization method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0036] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing a method for visualizing network devices is shown. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0037] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0038] The memory 104 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the network device visualization method in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the network device visualization method of the above-mentioned application program is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0039] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0040] Figure 2 FIG. 1 is a flow chart of a method for visualizing a network device according to an embodiment of the present invention. Figure 2 As shown, the method comprises the following steps:

[0041] Step S202, obtaining chassis data of the target network device and daughter card data of the daughter card of the device.

[0042] In this step, the target network device can be a router, switch, firewall, etc., wherein multiple slots are designed in this type of network device for installing various device sub-cards. Different network devices involve different appearance styles, models, manufacturers, sub-card slots, interface cards and other information. The device sub-card is a component used to be inserted into the network device to realize different functions. It is installed in the slot of the device and provides the ability of data transmission, processing and management. Among them, the device sub-card also includes multiple types, such as: interface board, this type of sub-card provides physical connection, common ones are Ethernet interface board, fiber optic interface board, serial interface board, etc. Line processing board, used to process data packets, realize data forwarding, filtering, routing and other functions. Routing processing board, responsible for the control plane of the device, performs routing calculation, protocol processing and system management, etc. Power board, used to provide power to the device, usually has redundant design to improve reliability.

[0043] The obtained chassis data can be fixed information of the target network device, such as the appearance style, model, and manufacturer, as well as the specifications and positions of the slots corresponding to the actual sub-card slots in the actual device. The chassis of each model of equipment can correspond to a chassis frame. The sub-card data of the device sub-card can include the sub-card size and type of different device sub-cards, as well as the various ports and power modules integrated on the sub-cards.

[0044] Step S204 , based on the scalable vector graphics tag language and according to the chassis data, a framework module of the chassis in the target network device is determined.

[0045] In this step, according to the chassis data, SVG (Scalable Vector Graphics) language can be used to depict it, and the framework module in the target network device can be obtained. According to the model of the specific device in the chassis data, SVG XML tag language can be used to describe the main body, and the whole is described in <svg>Wrap the label and draw the framework module of the device chassis. The obtained framework module will include an empty chassis and slots, wherein the slots are set inside the empty chassis to receive the sub-cards. The position of each slot presented in the obtained framework module is the same as the structure, specifications and proportions of the real target network device.

[0046] As an optional embodiment, based on a label language of scalable vector graphics, according to chassis data, a framework module of a framework in a target network device is determined, wherein the chassis in the target network device includes an empty chassis and slots, including: according to a chassis size in the chassis data, based on the label language of scalable vector graphics, an empty chassis module of the chassis in the target network device is determined; according to the slot information in the chassis data, based on the label language of scalable vector graphics, slots are added to the empty chassis module in sequence in a preset order to obtain a framework module, wherein the slots are arranged inside the empty chassis for inserting device sub-cards.

[0047] Optionally, the outer frame of the chassis can be drawn in proportion based on the XML tag language of SVG according to the chassis size in the chassis data to obtain an empty chassis module. The model, brand and other information of the device can also be added to facilitate subsequent presentation to the user. Then the slot can be drawn according to the actual slot situation of the device. The slot information can be determined according to the actual frame and slot of the device chassis. The slot information includes the size, location, slot number, etc. of the slot. Based on the slot size and slot distribution in the slot information, slots can be added to the empty chassis module in a preset order to obtain a framework module. When the module is generated in the Vue framework, each generated slot port can use the slot component in the Vue framework to fill each slot, which is convenient for the subsequent replacement and filling of the slot sub-card. Figure 3 is a schematic diagram of a system framework of a network device visualization method provided according to an optional embodiment of the present invention. Figure 3 As shown, the device chassis can be a generated frame module, which includes multiple slots to be inserted into sub-cards.

[0048] Specifically, the slots can be drawn according to the actual slot conditions of the device. Because SVG technology has the principle of "latecomers come first", that is, if there are multiple modules rendered at the same coordinate position on the SVG view, the content of the module drawn later will be presented in the end. Therefore, the slots can be drawn in the order from bottom to top and from right to left according to the actual slot arrangement of the chassis, so that the final presentation of the framework module will be better. For example, when the left slot of the two adjacent slots on the left and right is inserted with a sub-card module with a width of 2 slots, since the left slot is drawn later, the adjacent right slot view will be automatically blocked by the sub-card module and will not be displayed, and the final visual effect of inserting a whole large sub-card into the two slots will be presented; the same applies to the upper and lower adjacent slots.

[0049] Step S206 , determining a device daughter card module of the device daughter card according to the daughter card data based on the scalable vector graphics tag language.

[0050] In this step, the device sub-card model can be drawn based on the SVG tag language. The sub-card data can include the size, model and other information of the device sub-card. The SVG XML description language can be used to draw, completely simulate the view of the real model sub-card, integrate the various electrical ports, network ports, power supply and other view elements in the sub-card, draw and arrange them in proportion to the real pattern, and obtain the device sub-card module. Figure 3 As shown, the device daughter card may include a blank daughter card and daughter cards of various models, and the size of the blank daughter card may cover the sizes of daughter cards of all models.

[0051] Among them, the device sub-cards include empty sub-cards and sub-cards of various models. When no sub-card is inserted into the device chassis slot, the area view is displayed with an empty sub-card module that adapts to the slot view size, that is, the empty sub-card can be inserted into the chassis when no sub-cards of various models are inserted into the chassis, which can better display the chassis to the user. Therefore, the empty sub-card module only draws the background view of the sub-card, without any surface port views. Sub-cards of various models draw various ports, power modules, etc. of the interface card according to the real pattern. At the same time, the port view integrated in the sub-card module of each model of the device can present different view effects according to the actual port usage status, and support user interaction events. Each model of sub-card corresponds to a sub-card module.

[0052] As an optional embodiment, based on a label language of scalable vector graphics, a device subcard module of a device subcard is determined according to subcard data, wherein the device subcard includes an empty subcard and subcards of multiple models, including: determining the size of the empty subcard according to the slot size in the chassis data; determining the empty subcard module corresponding to the empty subcard based on the label language of scalable vector graphics according to the size of the empty subcard; determining the subcard modules corresponding to each of the multiple models of subcards based on the label language of scalable vector graphics according to the subcard data corresponding to each of the multiple models of subcards; obtaining the device subcard module of the device subcard based on the empty subcard module and the subcard modules corresponding to each of the multiple models of subcards.

[0053] Optionally, the size of the empty daughter card can be determined according to the slot size in the target network device. Because the empty daughter card is used to be inserted into the chassis to be presented to the user when the slot of the device chassis does not have any daughter cards of various models inserted. Therefore, the size of the empty daughter card can be determined according to the slot size of the target network device. The SVG XML description language can be used for drawing. <g>The label package can be used as an empty sub-card module inserted into the slot in the framework module. It can be used to replace its slot component in the Vue framework. The empty sub-card view is drawn based on the size of each main frame slot of the device chassis, and the view content such as the border and background of the sub-card is drawn. The slots of the same size can reuse the empty sub-card module components of the same size. Sub-card modules of various models can be drawn based on the corresponding sub-card data and the label data of SVG, and finally the corresponding sub-card modules of various models of sub-cards are obtained. Among them, the sub-card modules of various models can be obtained by adjusting the previously generated empty sub-card modules, or they can be regenerated based on their own corresponding sub-card data. Because the empty sub-card and sub-cards of various models are device sub-card modules to be inserted into the framework module, the size of the empty sub-card module should cover sub-cards of various models.

[0054] As an optional embodiment, a slot mapping relationship of a target network device is obtained, wherein the slot mapping relationship represents a correspondence between a slot number and slot information; based on the slot mapping relationship, an empty subcard module is inserted into a framework module to obtain an initial device module of the target network device; and the initial device module is visualized to display the initial device module.

[0055] Optionally, the slot mapping relationship can be obtained first, and the slot mapping relationship reflects the corresponding relationship between the slot number and the slot information. The slot information may include the size of the slot, so as to determine which sub-card can be inserted into the slot. According to the slot mapping relationship, the generated empty sub-card module can be inserted into the framework module first, and the initial device module of the target network device can be obtained. The initial device module can be displayed to the user. The user can understand the overall framework structure of the target network device based on the initial device module, which is convenient for the user to select a suitable device sub-card to insert, so as to achieve the technical effect of flexible configuration.

[0056] As an optional embodiment, the slot distribution and slot information in the target network device are determined based on the chassis data, wherein the slot information includes the slot name and slot size; based on the slot distribution, the slots in the target network device are numbered to obtain slot identifiers corresponding to the slots; based on the slot identifiers and the slot information, a slot mapping relationship is obtained.

[0057] Optionally, a slot mapping relationship table may be designed, that is, a slot mapping relationship may be determined. The slot mapping relationship may show the distribution of slots in the chassis, so as to facilitate the selection of a suitable subcard for insertion and meet the needs of flexible configuration. The slot distribution and slot information may be determined based on the chassis data, and the slot information may include the name, width, and height of the slot. The slots may be numbered based on the slot distribution, for example, the slots may be numbered in order from top to bottom and from left to right, so that each slot will have a corresponding slot identifier. Then, based on the slot identifier and the slot information, the slot mapping relationship may be obtained.

[0058] Because complex chassis have slots of different sizes and double-width and double-height slots, the slot information of the smallest slot that cannot be further divided can be used as the most basic unit of the relationship table. The slot information includes the name, width and height of the slot. Fill in the slot information according to the order of the device slot number from top to bottom and from left to right. The relationship table is designed as a multidimensional array (MAP is used to refer to the multidimensional array in the following). The first dimension represents the vertical slot distribution from top to bottom. For example, MAP[N] describes the slot situation of the N+1th layer of the device. If there is only one slot in the N+1th layer, MAP[N] is the name of the slot number; if there are only k sub-slots in the horizontal direction inside the N+1th slot, MAP[N] is an array of the k slot number names arranged in order; if there are only j sub-slots in the vertical direction inside the N+1th slot, MAP[N] is j arrays, each of which is used to describe the corresponding distribution in the sub-slot; if there are complex sub-slots distributed vertically and horizontally inside the N+1th slot, the sub-slot layout is recorded recursively according to the above rules until each minimum slot is described. By matching the slot number and the slot information, the slot mapping relationship can be obtained.

[0059] Each slot in the device chassis frame can also be pinpointed. According to the name of each slot number and the slot mapping table corresponding to the device chassis, the position of the slot number in the mapping table is located, and the size information of the previous slot number in the mapping table is recursively superimposed to obtain the view coordinates (x, y) of the slot number. Then, the slot is located at the coordinate position of the SVG view by using the transform change of SVG. In this way, in the subsequent process of sub-card insertion, the position of each slot can be more conveniently located, making the configuration of the sub-card more flexible.

[0060] As an optional embodiment, empty sub-card modules corresponding to the various models of sub-cards can be selected according to the corresponding sub-card sizes of the various models of sub-cards; based on the sub-card data corresponding to the various models of sub-cards and based on the label language of scalable vector graphics, the empty sub-card modules corresponding to the various models of sub-cards can be adjusted to obtain the sub-card modules corresponding to the various models of sub-cards.

[0061] You can first select the corresponding empty daughter card modules according to the daughter card sizes corresponding to the various types of daughter cards. Because compared with the empty daughter cards, the daughter cards of various types will integrate various electrical ports, network ports, power supplies and other elements. Therefore, first select the corresponding empty daughter card modules, and then add corresponding ports and other modules to the empty daughter card modules according to the corresponding daughter card data, and obtain the corresponding daughter card modules of the various types of daughter cards.

[0062] For example, the drawing device sub-card module can completely simulate the interface card view of the real model, integrate various view elements such as electrical ports, network ports, power supplies, etc., and draw and arrange them in proportion to the real pattern. According to the size of the sub-card, the empty sub-card modules of the corresponding size generated above are reused, and on this basis, the XML tag language is used to describe the view modules of the sub-cards such as ports and power supplies. At the same time, the sub-card module also has port status information attributes. Each port can change its corresponding view according to the status information, such as flashing, changing color, etc. At the same time, user interaction events are integrated for each port, such as single-click and double-click operations, to display detailed port information, and obtain the corresponding sub-card modules of various models.

[0063] Step S208: visualize the device daughter card module and the framework module to obtain the target network device module.

[0064] In this step, the device subcard module and the framework module can be visualized to obtain the target network device module. For example, according to the slot mapping relationship, the device subcard module can be inserted into the framework module to obtain the target network device module, that is, the final module to be presented, such as Figure 3 As shown, the device presentation is the target network device module. Specifically, which device sub-card modules are inserted can be configured according to user needs.

[0065] As an optional embodiment, the device sub-card module and the framework module are visualized to obtain the target network device module, including: receiving device requirements based on the target account input, wherein the device requirements include the model of the target sub-card and the slot corresponding to the target sub-card; according to the device requirements, selecting the sub-card module corresponding to the target sub-card from the sub-card modules and inserting it into the framework module, and visualizing the framework module and the target sub-card to obtain the target network device module.

[0066] Optionally, a device requirement input by a target user through a target account may be received, wherein the device requirement may include the model of the target subcard and the corresponding slot. Based on the device requirement, a unit module corresponding to the target subcard may be selected from the generated subcard modules and inserted into the corresponding slot in the framework module to obtain a target network device module.

[0067] As an optional embodiment, the port status information in the target subcard is obtained; and the port status information of the target subcard and the target network device module are displayed.

[0068] Optionally, the port status information in the target subcard can be obtained, wherein the port status information is crucial in the management and monitoring of network devices, and may include physical status, protocol status, traffic information, etc. The port information can be presented to the user together with the target network device module, so that the user can intuitively understand the structure of the network device and the relevant information of the subcard inserted therein. Specifically, a component that can interact with the user can be set at the presented subcard, and the user can query the detailed information of the port on the subcard after performing the corresponding interactive operation. In this way, the network device of the corresponding model can be displayed, the device port status can be displayed in real time, and the operation and maintenance users can be supported to interact with the device at the visualization end, and view and manipulate the various ports of the device.

[0069] Through the above steps, the purpose of visualizing the device framework and sub-cards separately is achieved, thereby realizing the technical effect of improving the flexibility of network device visualization, and further solving the technical problem that the current display of network devices is mostly described in the form of text tables, or displayed as static pictures, which is difficult to configure efficiently and flexibly.

[0070] Taking the generation of NE8000M8 network device module under the Vue framework as an example, an optional embodiment of a network device visualization method is proposed below. The specific steps are as follows:

[0071] Step 1: Draw the main frame module of the NE8000M8 chassis. This includes steps 1.1 to 1.2:

[0072] Step 1.1, draw the empty chassis according to the corresponding size, including the fixed appearance of the chassis, model name, fan power supply, etc. <svg>For the convenience of description, the output is named S1_1. The effect is as follows Figure 4 As shown, Figure 4 It is a schematic diagram of an empty chassis module of a network device visualization method provided according to an optional embodiment of the present invention.

[0073] Step 1.2 Figure 5 1 is a schematic diagram of the slot distribution of an optional model of a network device in an optional embodiment of the present invention, wherein the network device of this model is a device NE8000M8, such as Figure 5 As shown, according to its slot distribution, fill the empty chassis module generated in the previous step with the corresponding label language<slot name="slotN”> ,in, <slot>It is a slot component in Vue, which can be replaced with the required daughter card module in subsequent use. The possible value of slotN is any value from "slot1" to "slot10", representing slot N. According to the principle of "latest come first", the slots are filled in order from right to left and from bottom to top according to slot2, slot1, slot4, slot3, slot9, slot10, slot6, slot5, slot8, slot7.

[0074] Step 2, generate a daughter card adapter module. According to the actual slot distribution, generate a slot mapping table MAP, which is represented in array form, recorded as: [[slot7_info, slot8_info], [slot5_info, slot6_info], [slot10_info], [slot9_info], [slot3_info, slot4_info], [slot1_info, slot2_info]], which is used to specifically describe the NE8000M8 slot distribution. Specifically, the array is a two-dimensional array, the first dimension represents the row slots of the NE8000M8 from top to bottom, and the second dimension represents the subdivided slots within the row slots. It should be clear that the array reflects the slot distribution, and the slotN_info in the array is a form of expression for convenient description, and should actually contain the slot number and size information corresponding to slot N.

[0075] Step 3: Based on the MAP table in step 2 and the internal and external dimensions of the drawn chassis, we can use a unified processing algorithm to calculate the starting position coordinates (xi, yi) of each slot on the overall SVG view.<slot name="slotN”> Before<g transform="translate(xi,yi)”> The label transforms each slot to the corresponding (xi,yi) position.

[0076] Step 4: Generate an empty daughter card module. Focus on the view in the slot area. This area includes two sizes of slots, so two sizes of empty daughter card modules are required. Each empty daughter card module is described with the corresponding appearance size to show the appearance of the chassis when no daughter card is inserted in the slot. The content is all in <g>The label package can be used as a sub-assembly of the chassis module. The two empty daughter card modules are obtained, one is a short view and the other is a long view, such as Figure 6 As shown, Figure 6 It is a schematic diagram of an empty daughter card module of a network device visualization method provided according to an optional embodiment of the present invention.

[0077] Step 5: Integrate the empty daughter card module. Figure 7 is an initial device schematic diagram of a network device visualization method provided by an optional embodiment of the present invention, such as Figure 7 As shown, the empty daughter card module corresponding to the short view and the empty daughter card module corresponding to the long view are filled into the framework module to obtain the initial device module.

[0078] Step 6: Draw the device subcard module. For different subcards that may be used in the system, select the appropriate empty subcard module as the basis according to the size. On this basis, draw the required visual elements according to the actual appearance of the subcard model, such as optical port, power grid port, and various other visual element lights. And add corresponding status views, event interactions, etc. to the ports as needed to display complex and changeable port content. The obtained subcard modules of different models are as follows: Figure 8 As shown, Figure 8 The present invention is a schematic diagram of a specific device daughter card module of a network device visualization method provided according to an optional embodiment of the present invention, wherein the device daughter card includes an optical port.

[0079] Step 7: Integration display. In the interface connected to the server, based on the chassis display of NE8000M8, according to the actual collected sub-card information, including sub-card model and corresponding slot number, the sub-card module corresponding to the model is integrated into the corresponding slot port of the initial device module to form the target network device module, such as Fig. 9 As shown, Fig. 9 is a schematic diagram of a target network device according to a network device visualization method provided by an optional embodiment of the present invention;

[0080] An optional embodiment of a network device visualization method is specifically proposed below. Fig.10 is a schematic diagram of a module of a network device visualization method provided according to an optional embodiment of the present invention, such as Fig.10 As shown,

[0081] Module 1: Chassis framework module, used to build a container for network devices and present the overall chassis appearance. This module includes the following content: fixed information about the device, such as the appearance style, model, and manufacturer, and the corresponding slots reserved for the actual sub-card slots of the actual device. The specifications and positions of each slot are constructed according to the actual device. The chassis of each device corresponds to a chassis framework container.

[0082] Module 2: Device daughter card module, which is used to describe daughter cards used for network device integration and can be introduced as a sub-component of the chassis frame module. Device daughter card modules include empty daughter cards and daughter cards of various models. When no daughter card is inserted into the device chassis slot, the view of this area is displayed with an empty daughter card module that adapts to the slot view size. The empty daughter card module only draws the background view of the daughter card, without any surface port and other views. The daughter cards of various models are based on the corresponding size of the empty daughter card according to the real pattern, and the various ports, power modules, etc. of the daughter card are drawn. At the same time, the port view integrated in the daughter card module of each model can present different view effects according to the actual port usage status, and support user interaction events. Each model of daughter card corresponds to a daughter card module.

[0083] Module three: Subcard adapter module, used to filter and match the main device framework and the corresponding subcard according to the real device to be displayed and the integrated interface card to form the final view presentation. This module mainly consists of two parts: the device slot mapping relationship table and the adaptation algorithm. The corresponding chassis framework module and the corresponding device subcard module can be filtered and matched according to the network device model, the integrated subcard model and the slot number information. The device slot mapping relationship table records the slot distribution information of the device chassis framework module. Each chassis framework corresponds to an independent device slot mapping relationship table. The algorithm in the application adaptation module can obtain the viewport coordinates of the corresponding slot in the main chassis framework according to the relationship table, and finally place the corresponding subcard submodule in the corresponding position of the chassis framework module to restore the real and complete device effect.

[0084] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0085] Through the description of the above implementation methods, those skilled in the art can clearly understand that the network device visualization method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0086] An embodiment of the present invention may provide a computer device. Optionally, in this embodiment, the computer device may be located in at least one network device among multiple network devices of a computer network. The computer device includes a memory and a processor.

[0087] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the network device visualization method and device in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned network device visualization method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0088] The processor can call the information and application programs stored in the memory through the transmission device to execute the following steps: obtain the chassis data of the target network device and the sub-card data of the device sub-card; based on the label language of scalable vector graphics, determine the framework module of the framework in the target network device according to the chassis data; based on the label language of scalable vector graphics, determine the device sub-card module of the device sub-card according to the sub-card data; based on the preset slot mapping relationship in the target network device, generate the target network device module of the target network device according to the device sub-card module and the framework module.

[0089] Optionally, the processor may also execute program code for the following steps: based on a label language of scalable vector graphics and according to chassis data, determining a framework module of a framework in a target network device, wherein the framework in the target network device includes an empty chassis and slots, including: based on a chassis size in the chassis data and based on the label language of scalable vector graphics, determining an empty chassis module of a chassis in the target network device; based on slot information in the chassis data and based on the label language of scalable vector graphics, sequentially adding slots to the empty chassis module in a preset order to obtain a framework module.

[0090] Optionally, the processor may also execute the program code of the following steps: determining the device subcard module of the device subcard according to the subcard data based on the label language of scalable vector graphics, wherein the device subcard includes an empty subcard and subcards of multiple models, including: determining the size of the empty subcard according to the slot size in the chassis data; determining the empty subcard module corresponding to the empty subcard based on the label language of scalable vector graphics according to the size of the empty subcard; determining the subcard modules corresponding to the multiple models of subcards based on the label language of scalable vector graphics according to the subcard data corresponding to each of the multiple models of subcards; obtaining the device subcard module of the device subcard based on the empty subcard module and the subcard modules corresponding to each of the multiple models of subcards.

[0091] Optionally, the processor may also execute program code for the following steps: determining sub-card modules corresponding to each of the multiple models of sub-cards based on sub-card data corresponding to each of the multiple models of sub-cards and based on a label language of scalable vector graphics, including: selecting empty sub-card modules corresponding to each of the multiple models of sub-cards based on sub-card sizes corresponding to each of the multiple models of sub-cards; adjusting empty sub-card modules corresponding to each of the multiple models of sub-cards based on a label language of scalable vector graphics based on sub-card data corresponding to each of the multiple models of sub-cards to obtain sub-card modules corresponding to each of the multiple models of sub-cards.

[0092] Optionally, the processor may also execute program codes of the following steps: based on the slot mapping relationship, insert the empty daughter card module into the framework module to obtain the initial device module of the target network device; and display the initial device module.

[0093] Optionally, the processor may also execute the program code of the following steps: based on a preset slot mapping relationship in the target network device, generating a target network device module of the target network device according to the device sub-card module and the framework module, including: receiving device requirements based on target account input, wherein the device requirements include the model of the target sub-card and the slot corresponding to the target sub-card; according to the device requirements, selecting a sub-card module corresponding to the target sub-card from the sub-card modules and inserting it into the framework module to obtain the target network device module.

[0094] Optionally, the processor may also execute program codes of the following steps: obtaining port status information in the target sub-card; and displaying port status information of the target network device module and the target sub-card.

[0095] Optionally, the processor may also execute the program code of the following steps: determining the slot distribution and slot information in the target network device based on the chassis data, wherein the slot information includes the slot name and slot size; numbering the slots in the target network device based on the slot distribution to obtain slot identifiers corresponding to the slots; and obtaining a slot mapping relationship based on the slot identifiers and slot information.

[0096] By adopting the embodiment of the present invention, a network device visualization method is provided, which obtains chassis data of the target network device and subcard data of the device subcard; determines the framework module of the framework in the target network device according to the chassis data based on the label language of scalable vector graphics; determines the device subcard module of the device subcard according to the subcard data based on the label language of scalable vector graphics; generates the target network device module of the target network device according to the device subcard module and the framework module based on the preset slot mapping relationship in the target network device, thereby achieving the purpose of visualizing the device framework and the subcard separately, thereby realizing the technical effect of improving the flexibility of network device visualization, and further solving the technical problem that the current display of network devices is mostly described in the form of text tables, etc., or displayed in static pictures, which is difficult to be efficiently and flexibly configured.

[0097] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a non-volatile storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0098] The embodiment of the present invention further provides a non-volatile storage medium. Optionally, in this embodiment, the non-volatile storage medium can be used to store the program code executed by the network device visualization method provided in the above embodiment.

[0099] Optionally, in this embodiment, the non-volatile storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0100] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: obtaining chassis data of the target network device and subcard data of the device subcard; determining a framework module of a framework in the target network device based on the chassis data based on a tag language of scalable vector graphics; determining a device subcard module of the device subcard based on the subcard data based on a tag language of scalable vector graphics; and generating a target network device module of the target network device based on a preset slot mapping relationship in the target network device and the device subcard module and the framework module.

[0101] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: based on the label language of scalable vector graphics, according to the chassis data, determining a framework module of the framework in the target network device, wherein the framework in the target network device includes an empty chassis and slots, including: based on the chassis size in the chassis data, based on the label language of scalable vector graphics, determining an empty chassis module of the chassis in the target network device; based on the label language of scalable vector graphics, according to the slot information in the chassis data, in a preset order, adding slots to the empty chassis module in sequence to obtain a framework module.

[0102] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: based on a label language of scalable vector graphics, according to the subcard data, determining a device subcard module of the device subcard, wherein the device subcard includes an empty subcard and subcards of multiple models, including: determining the size of the empty subcard according to the slot size in the chassis data; determining the empty subcard module corresponding to the empty subcard based on the label language of scalable vector graphics according to the size of the empty subcard; determining the subcard modules corresponding to each of the multiple models of subcards based on the label language of scalable vector graphics according to the subcard data corresponding to each of the multiple models of subcards; obtaining the device subcard module of the device subcard based on the empty subcard module and the subcard modules corresponding to each of the multiple models of subcards.

[0103] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: determining sub-card modules corresponding to each of the multiple models of sub-cards based on a label language of scalable vector graphics according to sub-card data corresponding to each of the multiple models of sub-cards, including: selecting empty sub-card modules corresponding to each of the multiple models of sub-cards based on sub-card sizes corresponding to each of the multiple models of sub-cards; adjusting the empty sub-card modules corresponding to each of the multiple models of sub-cards based on a label language of scalable vector graphics according to the sub-card data corresponding to each of the multiple models of sub-cards, so as to obtain sub-card modules corresponding to each of the multiple models of sub-cards.

[0104] Optionally, in this embodiment, the non-volatile storage medium is configured to store program codes for executing the following steps: based on the slot mapping relationship, inserting the empty daughter card module into the framework module to obtain the initial device module of the target network device; and displaying the initial device module.

[0105] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: based on a preset slot mapping relationship in the target network device, generating a target network device module of the target network device according to the device sub-card module and the framework module, including: receiving device requirements based on the target account input, wherein the device requirements include the model of the target sub-card and the slot corresponding to the target sub-card; according to the device requirements, selecting a sub-card module corresponding to the target sub-card from the sub-card modules and inserting it into the framework module to obtain the target network device module.

[0106] Optionally, in this embodiment, the non-volatile storage medium is configured to store program codes for executing the following steps: obtaining port status information in a target daughter card; and displaying port status information of a target network device module and a target daughter card.

[0107] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for executing the following steps: determining the slot distribution and slot information in the target network device based on the chassis data, wherein the slot information includes a slot name and a slot size; numbering the slots in the target network device based on the slot distribution to obtain slot identifiers corresponding to the slots; and obtaining a slot mapping relationship based on the slot identifiers and the slot information.

[0108] An embodiment of the present invention also provides a computer program product, including a computer program. Optionally, in this embodiment, when the computer program is executed by a processor, it can achieve: obtaining chassis data of a target network device and subcard data of a device subcard; determining a framework module of a framework in the target network device according to the chassis data based on a label language of scalable vector graphics; determining a device subcard module of the device subcard according to the subcard data based on a label language of scalable vector graphics; and generating a target network device module of the target network device according to the device subcard module and the framework module based on a preset slot mapping relationship in the target network device.

[0109] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0110] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0111] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0112] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0113] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0114] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0115] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.< / g> < / slot> < / svg> < / g> < / svg>

Claims

1. A network device visualization method, characterized in that: include: Acquire chassis data of a target network device and daughter card data of a device daughter card, wherein the device daughter card is inserted into a slot in the target network device; Determine, based on the scalable vector graphics tag language, a framework module of a chassis in the target network device according to the chassis data; Determining a device daughter card module of the device daughter card according to the daughter card data based on the tag language of the scalable vector graphics; The device daughter card module and the framework module are visualized to obtain the target network device module.

2. The method according to claim 1, characterized in that The scalable vector graphics-based label language determines, according to the chassis data, a framework module of a chassis in the target network device, wherein the chassis in the target network device includes an empty chassis and a slot, including: According to the chassis size in the chassis data, based on the tag language of the scalable vector graphics, determine and obtain an empty chassis module of the chassis in the target network device; According to the slot information in the chassis data and based on the label language of the scalable vector graphics, the slots are added to the empty chassis module in sequence in a preset order to obtain the framework module, wherein the slots are arranged inside the empty chassis for inserting the device sub-cards.

3. The method according to claim 1, characterized in that The tag language based on the scalable vector graphics determines the device daughter card module of the device daughter card according to the daughter card data, wherein the device daughter card includes a blank daughter card and daughter cards of multiple models, including: Determining the size of the empty daughter card according to the slot size in the chassis data; Determining, according to the size of the empty subcard and based on the tag language of the scalable vector graphics, an empty subcard module corresponding to the empty subcard; Determining, according to the daughter card data corresponding to the daughter cards of the plurality of models, daughter card modules corresponding to the daughter cards of the plurality of models based on the label language of the scalable vector graphics; Based on the empty daughter card module and the daughter card modules corresponding to the daughter cards of the multiple models, the device daughter card module of the device daughter card is obtained.

4. The method according to claim 3, characterized in that The method of determining the subcard modules corresponding to the subcards of the plurality of models respectively according to the subcard data corresponding to the subcards of the plurality of models respectively and based on the label language of the scalable vector graphics comprises: Selecting empty daughter card modules corresponding to the daughter cards of the plurality of models according to the daughter card sizes corresponding to the daughter cards of the plurality of models; According to the daughter card data corresponding to the daughter cards of the plurality of models, based on the label language of the scalable vector graphics, the empty daughter card modules corresponding to the daughter cards of the plurality of models are adjusted to obtain the daughter card modules corresponding to the daughter cards of the plurality of models.

5. The method according to claim 3, characterized in that: Also includes: Obtaining a slot mapping relationship of the target network device, wherein the slot mapping relationship represents a corresponding relationship between a slot number and slot information; Based on the slot mapping relationship, inserting the empty daughter card module into the framework module to obtain an initial device module of the target network device; The initial equipment module is visualized to display the initial equipment module.

6. The method according to any one of claim 5, characterized in that: Also includes: Determine, according to the chassis data, the slot distribution and slot information in the target network device, wherein the slot information includes a slot name and a slot size; Based on the slot distribution, number the slots in the target network device to obtain slot identifiers corresponding to the slots; The slot mapping relationship is obtained based on the slot identifier and the slot information.

7. The method according to any one of claims 1 to 6, characterized in that: The step of visualizing the device daughter card module and the framework module to obtain the target network device module includes: Receiving a device requirement based on a target account input, wherein the device requirement includes a model of a target subcard and a slot corresponding to the target subcard; According to the device requirement, a subcard module corresponding to the target subcard is selected from the subcard modules and inserted into the framework module. The framework module and the target subcard are visualized to obtain the target network device module.

8. The method according to claim 7, characterized in that Also includes: Obtaining port status information in the target subcard; The port status information of the target daughter card and the target network device module are displayed.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the network device visualization method according to any one of claims 1 to 8.

10. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and when the computer program is run, the processor executes the network device visualization method according to any one of claims 1 to 8.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the network device visualization method according to any one of claims 1 to 8 is implemented.

Images